Cucumber Feature Report

All Scenarios

148

Passed Scenarios

116

Failed Scenarios

2

Skipped Scenarios

30

Execution Time: 65m 39s 705ms

Expand All | Collapse All

Metadata

App Version: Uyuni/Head

Browser: Chrome

Platform: x86_64

Parallel: Disabled

Feature:Sanity checks 44s 590ms 10 2

In order to use the product
I want to be sure to use a sane environment

Scenario:
The server is healthy

12s 82ms 19

Then "server" should have a FQDN 386ms

And reverse resolution should work for "server" 640ms

And the clock from "server" should be exact 674ms

And service "apache2" is enabled on "server" 730ms

And service "apache2" is active on "server" 632ms

And service "cobblerd" is enabled on "server" 637ms

And service "cobblerd" is active on "server" 640ms

And service "rhn-search" is enabled on "server" 636ms

And service "rhn-search" is active on "server" 638ms

And service "salt-api" is enabled on "server" 680ms

And service "salt-api" is active on "server" 664ms

And service "salt-master" is enabled on "server" 631ms

And service "salt-master" is active on "server" 639ms

And service "taskomatic" is enabled on "server" 659ms

And service "taskomatic" is active on "server" 630ms

And socket "tftp" is enabled on "server" 648ms

And socket "tftp" is active on "server" 640ms

And service "tomcat" is enabled on "server" 639ms

And service "tomcat" is active on "server" 631ms

@proxy

Scenario:
The proxy is healthy

4s 459ms 4

Then "proxy" should have a FQDN 2s 963ms

And reverse resolution should work for "proxy" 277ms

And "proxy" should communicate with the server using public interface 943ms

And the clock from "proxy" should be exact 274ms

@sle_minion

Scenario:
The minion is healthy

6s 238ms 4

Then "sle_minion" should have a FQDN 4s 360ms

And reverse resolution should work for "sle_minion" 414ms

And "sle_minion" should communicate with the server using public interface 1s 51ms

And the clock from "sle_minion" should be exact 411ms

@build_host

Scenario:
The build host is healthy

3s 793ms 4

Then "build_host" should have a FQDN 2s 425ms

And reverse resolution should work for "build_host" 220ms

And "build_host" should communicate with the server using public interface 921ms

And the clock from "build_host" should be exact 225ms

@ssh_minion

Scenario:
The SSH minion is healthy

6s 211ms 4

Then "ssh_minion" should have a FQDN 4s 336ms

And reverse resolution should work for "ssh_minion" 434ms

And "ssh_minion" should communicate with the server using public interface 1s 43ms

And the clock from "ssh_minion" should be exact 397ms

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 133ms 4

Then "rhlike_minion" should have a FQDN 1s 929ms

And reverse resolution should work for "rhlike_minion" 198ms

And "rhlike_minion" should communicate with the server using public interface 825ms

And the clock from "rhlike_minion" should be exact 179ms

@deblike_minion

Scenario:
The Debian-like minion is healthy

6s 636ms 4

Then "deblike_minion" should have a FQDN 5s 339ms

And reverse resolution should work for "deblike_minion" 219ms

And "deblike_minion" should communicate with the server using public interface 861ms

And the clock from "deblike_minion" should be exact 215ms

@skip_if_cloud

Scenario:
The external resources can be reached

< 1ms 3

Then it should be possible to reach the test packages 0s

And it should be possible to reach the build sources 0s

And it should be possible to reach the Docker profiles 0s

@server_http_proxy

Scenario:
The HTTP proxy is working

< 1ms 1

Then it should be possible to use the HTTP proxy 0s

@auth_registry

Scenario:
The registry with authentication is healthy

655ms 1

Then it should be possible to reach the authenticated registry 655ms

@no_auth_registry

Scenario:
The registry without authentication is healthy

675ms 1

Then it should be possible to reach the not authenticated registry 675ms

@custom_download_endpoint

Scenario:
The custom download endpoint is working

703ms 1

Then it should be possible to use the custom download endpoint 703ms

Feature:Very first settings 48s 49ms 6 2

In order to use the product
As the admin user
I want to create the organisation, the first users and set the HTTP proxy

Scenario:
Cleanup Salt files

677ms 1

When I run "rm -Rf /srv/salt/*" on "server" 677ms

@skip_if_containerized_server

Scenario:
Create admin user and first organization

< 1ms 12

Given I access the host the first time 0s

When I go to the home page 0s

And I enter "SUSE Test" as "orgName" 0s

And I enter "admin" as "login" 0s

And I enter "admin" as "desiredpassword" 0s

And I enter "admin" as "desiredpasswordConfirm" 0s

And I select "Mr." from "prefix" 0s

And I enter "Admin" as "firstNames" 0s

And I enter "Admin" as "lastName" 0s

And I enter "galaxy-noise@localhost" as "email" 0s

And I click on "Create Organization" 0s

Then I am logged in 0s

Scenario:
Log in as admin user

39s 739ms 1

Given I am authorized for the "Admin" section 39s 739ms

Scenario:
Wait for refresh of list of products to finish

3s 764ms 1

When I wait until mgr-sync refresh is finished 3s 764ms

Scenario:
Create testing username

1s 439ms 12

When I follow the left menu "Users > User List > Active" 189ms

And I follow "Create User" 638ms

And I enter "testing" as "login" 66ms

And I enter "testing" as "desiredpassword" 63ms

And I enter "testing" as "desiredpasswordConfirm" 71ms

And I select "Mr." from "prefix" 47ms

And I enter "Test" as "firstNames" 59ms

And I enter "User" as "lastName" 57ms

And I enter "galaxy-noise@localhost" as "email" 99ms

And I click on "Create Login" 64ms

Then I should see a "Account testing created, login information sent to galaxy-noise@localhost" text 68ms

And I should see a "testing" link 11ms

Scenario:
Grant testing user administrative priviledges

1s 720ms 10

When I follow the left menu "Users > User List > Active" 73ms

And I follow "testing" 489ms

And I check "role_org_admin" 83ms

And I check "role_system_group_admin" 78ms

And I check "role_channel_admin" 80ms

And I check "role_activation_key_admin" 77ms

And I check "role_config_admin" 77ms

And I click on "Update" 612ms

Then I should see a "User information updated" text 75ms

And I should see a "testing" text 72ms

@server_http_proxy

Scenario:
Setup HTTP proxy

< 1ms 9

When I follow the left menu "Admin > Setup Wizard > HTTP Proxy" 0s

Then I should see a "HTTP Proxy Hostname" text 0s

And I should see a "HTTP Proxy Username" text 0s

And I should see a "HTTP Proxy Password" text 0s

When I enter the address of the HTTP proxy as "HTTP Proxy Hostname" 0s

And I enter "suma3" as "HTTP Proxy Username" 0s

And I enter "P4$$w/ord With%and&" as "HTTP Proxy Password" 0s

And I click on "Save and Verify" 0s

Then HTTP proxy verification should have succeeded 0s

Scenario:
Detect latest Salt changes on the server

707ms 1

* Mon Jan 19 2026 Marek Czernek
- Make syntax in httputil_test compatible with Python 3.6
- Fix KeyError in postgres module with PostgreSQL 17 (bsc#1254325)
- Added:
* fix-tornado-s-httputil_test-syntax-for-python-3.6.patch
* backport-add-maintain-m-privilege-to-postgres-module.patch

* Wed Jan 14 2026 Marek Czernek
- Use internal deb classes instead of external aptsource lib
- Speed up wheel key.finger call (bsc#1240532)
- Add security patches (bsc#1254903,bsc#1254905,bsc#1254904)
- Simplify and speed up utils.find_json function (bsc#1246130)
- Added:
* use-internal-salt.utils.pkg.deb-classes-instead-of-a.patch
* speedup-wheel-key.finger-call-bsc-1240532-713.patch

When I query latest Salt changes on "server" 707ms

Feature:Turn "disable_local_repos" feature on highstate off 3s 691ms 1

In order to test the product using shortcuts
As root user
I want to add pillar data to disable that feature

Scenario:
Create custom pillar to turn off "disable_local_repos"

3s 691ms 1

When I turn off disable_local_repos for all clients 3s 691ms

Feature:Organization credentials in the Setup Wizard < 1ms 1

@scc_credentials @no_mirror

Scenario:
Enter valid SCC credentials

< 1ms 6

Given I am authorized for the "Admin" section 0s

When I follow the left menu "Admin > Setup Wizard > Organization Credentials" 0s

And I ask to add new credentials 0s

And I enter the SCC credentials 0s

And I click on "Save" 0s

And I wait until the SCC credentials are valid 0s

Feature:Change personal preferences 4s 476ms 2

In order to set up my personal preferences
As admin
I want to navigate through "Home" submenus changing some settings

Scenario:
Change page size to 100 per page in admin user

803ms 5

Given I am authorized as "admin" with password "admin" 511ms

When I follow the left menu "Home > My Preferences" 64ms

And I select "100" from "pagesize" 66ms

And I click on "Save Preferences" 59ms

Then I should see a "Preferences modified" text 101ms

Scenario:
Change page size to 100 per page in testing user

3s 672ms 5

Given I am authorized as "testing" with password "testing" 2s 804ms

When I follow the left menu "Home > My Preferences" 59ms

And I select "100" from "pagesize" 49ms

And I click on "Save Preferences" 660ms

Then I should see a "Preferences modified" text 97ms

Feature:Prepare server for using Kiwi 4s 468ms 1

Scenario:
Create a Kiwi user with image administrators rights

4s 468ms 2

New user kiwikiwi created with roles: image_admin

Given I am authorized for the "Admin" section 2s 475ms

When I create a user with name "kiwikiwi" and password "kiwikiwi" with roles "image_admin" 1s 992ms

Feature:Prepare server for using Docker 5s 626ms 2

Scenario:
Create a Docker user with image administrators rights

2s 185ms 2

New user docker created with roles: image_admin

Given I am authorized for the "Admin" section 484ms

When I create a user with name "docker" and password "docker" with roles "image_admin" 1s 701ms

@no_auth_registry

Scenario:
Create an image store without credentials

3s 440ms 7

When I follow the left menu "Images > Stores" 113ms

And I follow "Create" 532ms

And I enter "galaxy-registry" as "label" 132ms

And I enter the URI of the registry as "uri" 136ms

And I click on "create-btn" 100ms

Then I wait until table row contains a "galaxy-registry" text 2s 364ms

And I should see a "Items 1 - 1 of 1" text 60ms

Feature:Do not let Taskomatic tasks interfere with our CI tests 46s 552ms 3

Scenario:
Log in as admin user

37s 536ms 1

Given I am authorized for the "Admin" section 37s 536ms

Scenario:
Disable scheduled reposyncs

4s 431ms 5

When I follow the left menu "Admin > Task Schedules" 133ms

And I follow "mgr-sync-refresh-default" 1s 168ms

And I choose "disabled" 52ms

And I click on "Update Schedule" 1s 410ms

And I click on "Disable Schedule" 1s 666ms

Scenario:
Disable scheduled Cobbler syncs

4s 584ms 5

When I follow the left menu "Admin > Task Schedules" 61ms

And I follow "cobbler-sync-default" 1s 316ms

And I choose "disabled" 46ms

And I click on "Update Schedule" 1s 519ms

And I click on "Disable Schedule" 1s 639ms

@scc_credentials
Feature:List available channels and enable them 1m 42s 895ms 5 1

In order to use software channels
As root user
I want to list available channels and enable them

Scenario:
List available channels

36s 797ms 5

When I refresh SCC 34s 302ms

And I execute mgr-sync "list channels -e" with user "admin" and password "admin" 2s 494ms

Then I should get "[ ] SLE-Product-SLES15-SP7-Pool for x86_64 SUSE Linux Enterprise Server 15 SP7 x86_64 [sle-product-sles15-sp7-pool-x86_64]" < 1ms

And I should get " [ ] SLE-Product-SLES15-SP7-Updates for x86_64 SUSE Linux Enterprise Server 15 SP7 x86_64 [sle-product-sles15-sp7-updates-x86_64]" < 1ms

And I should get " [ ] SLE15-SP7-Installer-Updates for x86_64 SUSE Linux Enterprise Server 15 SP7 x86_64 [sle15-sp7-installer-updates-x86_64]" < 1ms

Scenario:
List available mandatory channels

1s 608ms 4

When I execute mgr-sync "list channels -e --no-optional" 1s 608ms

Then I should get "[ ] SLE-Product-SLES15-SP7-Pool for x86_64 SUSE Linux Enterprise Server 15 SP7 x86_64 [sle-product-sles15-sp7-pool-x86_64]" < 1ms

And I should get " [ ] SLE-Product-SLES15-SP7-Updates for x86_64 SUSE Linux Enterprise Server 15 SP7 x86_64 [sle-product-sles15-sp7-updates-x86_64]" < 1ms

And I shouldn't get " [ ] SLE15-SP7-Installer-Updates for x86_64 SUSE Linux Enterprise Server 15 SP7 x86_64 [sle15-sp7-installer-updates-x86_64]" < 1ms

Scenario:
List Server product

1s 529ms 2

When I execute mgr-sync "list products" 1s 529ms

Then I should get "[ ] SUSE Linux Enterprise Server 15 SP7 x86_64" < 1ms

@proxy @susemanager

Scenario:
List all products for SUSE Multi-Linux Manager

< 1ms 6

When I execute mgr-sync "list products --expand" 0s

Then I should get "[ ] SUSE Linux Enterprise Server 15 SP7 x86_64" 0s

And I should get " [ ] SUSE Multi-Linux Manager Proxy Extension 5.1 x86_64" 0s

And I should get " [ ] SUSE Multi-Linux Manager Proxy Extension for SLE 5.1 x86_64" 0s

And I should get " [ ] (R) SUSE Multi-Linux Manager Client Tools for SUSE Liberty Linux 7, RHEL and clones 7 x86_64" 0s

And I should get " [ ] (R) SUSE Multi-Linux Manager Client Tools for SLE 15 x86_64" 0s

Scenario:
List products with filter

1s 498ms 4

When I execute mgr-sync "list products --expand --filter x86_64" 1s 498ms

Then I should get "[ ] SUSE Linux Enterprise Server 15 SP7 x86_64" < 1ms

And I shouldn't get "ppc64" < 1ms

And I shouldn't get "s390x" < 1ms

Scenario:
Let mgr-sync time out

1m 1s 461ms 3

When I remove the mgr-sync cache file 649ms

And I execute mgr-sync refresh 1m 811ms

Then I should get "Timeout. No user input for 60 seconds. Exiting..." < 1ms

Feature:Synchronize products in the products page of the Setup Wizard 45m 9s 469ms 6 2 9

@scc_credentials

Scenario:
Refresh SCC

29s 812ms 1

When I refresh SCC 29s 812ms

@scc_credentials

Scenario:
Let the products page appear

3s 138ms 6

Given I am authorized for the "Admin" section 497ms

When I follow the left menu "Admin > Setup Wizard > Products" 922ms

And I wait until I see "Product Description" text 1s 342ms

Then I should see a "Arch" text 137ms

And I should see a "Channels" text 118ms

And I should not see a "WebYaST 1.3" text 120ms

@scc_credentials

Scenario:
Use the products and architecture filters

2s 537ms 7

When I follow the left menu "Admin > Setup Wizard > Products" 68ms

And I wait until I do not see "currently running" text 85ms

And I wait until I do not see "Loading" text 913ms

And I enter "RHEL and Liberty" as the filtered product description 162ms

Then I should see a "RHEL and Liberty 8 Base" text 84ms

When I select "x86_64" from "product-arch-filter" 1s 127ms

Then I should see a "RHEL and Liberty 8 Base" text 94ms

@scc_credentials @susemanager

Scenario:
View the channels list in the products page

< 1ms 9

When I follow the left menu "Admin > Setup Wizard > Products" 0s

And I wait until I do not see "currently running" text 0s

And I wait until I do not see "Loading" text 0s

And I enter "SUSE Linux Enterprise Server for SAP Applications 15 x86_64" as the filtered product description 0s

And I click the channel list of product "SUSE Linux Enterprise Server for SAP Applications 15 x86_64" 0s

Then I should see a "Product Channels" text 0s

And I should see a "Mandatory Channels" text 0s

And I should see a "Optional Channels" text 0s

When I close the modal dialog 0s

@scc_credentials @susemanager

Scenario:
Synchronize SLES 15 SP7 product with recommended sub-products, including MLM Client Tools

< 1ms 30

Given I am authorized for the "Admin" section 0s

When I follow the left menu "Admin > Setup Wizard > Products" 0s

And I wait until I do not see "currently running" text 0s

And I wait until I do not see "Loading" text 0s

And I enter "SUSE Linux Enterprise Server 15 SP7" as the filtered product description 0s

And I wait until I see "SUSE Linux Enterprise Server 15 SP7 x86_64" text 0s

And I open the sub-list of the product "SUSE Linux Enterprise Server 15 SP7 x86_64" 0s

And I open the sub-list of the product "Basesystem Module 15 SP7 x86_64" 0s

And I open the sub-list of the product "Desktop Applications Module 15 SP7 x86_64" 0s

And I open the sub-list of the product "SUSE Multi-Linux Manager Client Tools for SLE 15 x86_64" if present 0s

Then I should see that the "Basesystem Module 15 SP7 x86_64" product is "recommended" 0s

And I should see that the "Server Applications Module 15 SP7 x86_64" product is "recommended" 0s

And I should see that the "SUSE Multi-Linux Manager Client Tools for SLE 15 x86_64" product is "recommended" 0s

When I select "SUSE Linux Enterprise Server 15 SP7 x86_64" as a product 0s

Then I should see the "SUSE Linux Enterprise Server 15 SP7 x86_64" selected 0s

And I should see the "Basesystem Module 15 SP7 x86_64" selected 0s

And I should see the "Server Applications Module 15 SP7 x86_64" selected 0s

And I should see the "SUSE Multi-Linux Manager Client Tools for SLE 15 x86_64" selected 0s

When I select "Desktop Applications Module 15 SP7 x86_64" as a product 0s

And I select "Development Tools Module 15 SP7 x86_64" as a product 0s

Then I should see the "Desktop Applications Module 15 SP7 x86_64" selected 0s

And I should see the "Development Tools Module 15 SP7 x86_64" selected 0s

When I select "Python 3 Module 15 SP7 x86_64" as a product 0s

Then I should see the "Python 3 Module 15 SP7 x86_64" selected 0s

When I select "Containers Module 15 SP7 x86_64" as a product 0s

Then I should see the "Containers Module 15 SP7 x86_64" selected 0s

When I click the Add Product button 0s

And I wait until I see "SUSE Linux Enterprise Server 15 SP7 x86_64" product has been added 0s

Then the SLE15 SP7 product should be added 0s

When I wait until all synchronized channels for "sles15-sp7" have finished 0s

@uyuni

Scenario:
Partially add openSUSE Tumbleweed product, only including the required packages to generate the bootstrap repository

50s 668ms 4

Reposync of channel opensuse_tumbleweed-x86_64 killed
Channel opensuse_tumbleweed-uyuni-client-x86_64 added
Channel opensuse_tumbleweed-uyuni-client-devel-x86_64 added

When I use spacewalk-common-channel to add channel "opensuse_tumbleweed" with arch "x86_64" 8s 462ms

And I kill running spacewalk-repo-sync for "opensuse_tumbleweed-x86_64" channel 1s 495ms

And I use spacewalk-repo-sync to sync channel "opensuse_tumbleweed-x86_64" including only client tools dependencies 23s 931ms

And I use spacewalk-common-channel to add all "tumbleweed-client-tools-x86_64" channels with arch "x86_64" 16s 779ms

@containerized_server @proxy @uyuni

Scenario:
Add Uyuni Proxy product for Tumbleweed, including Uyuni Client Tools

1m 26s 387ms 2

Channel opensuse_tumbleweed-x86_64 added
Channel opensuse_tumbleweed-uyuni-client-devel-x86_64 added
Channel uyuni-proxy-devel-tumbleweed-x86_64 added
Channel opensuse_tumbleweed-x86_64 finished reposync
Channel opensuse_tumbleweed-uyuni-client-devel-x86_64 finished reposync
1 minutes out of 229 waiting for 'uyuni-proxy' channels to finish reposync
Channel uyuni-proxy-devel-tumbleweed-x86_64 finished reposync
All channels for uyuni-proxy have been fully synced

When I use spacewalk-common-channel to add all "uyuni-proxy" channels with arch "x86_64" 22s 674ms

And I wait until all synchronized channels for "uyuni-proxy" have finished 1m 3s 713ms

@scc_credentials @uyuni @build_host

Scenario:
Synchronize SLES 15 SP7 product with recommended sub-products for Retail feature

41m 40s 930ms 20 1

Products list: Available Channels: Status: - [I] - channel is installed - [ ] - channel is not installed, but is available - [U] - channel is unavailable [ ] EL9-Pool for x86_64 RHEL and Liberty 9 Base [el9-pool-x86_64] [ ] RHEL7-Pool for x86_64 RHEL7 Base x86_64 [rhel7-pool-x86_64] [ ] RHEL8-Pool for x86_64 RHEL and Liberty 8 Base [rhel8-pool-x86_64] [ ] SLE-Micro-5.3-Pool for x86_64 SUSE Linux Enterprise Micro 5.3 x86_64 [sle-micro-5.3-pool-x86_64] [ ] SLE-Product-SLED15-SP4-Pool for x86_64 SUSE Linux Enterprise Desktop 15 SP4 x86_64 [sle-product-sled15-sp4-pool-x86_64] [ ] SLE-Product-SLES15-SP4-Pool for x86_64 SUSE Linux Enterprise Server 15 SP4 x86_64 [sle-product-sles15-sp4-pool-x86_64] [ ] SLE-Product-SLES15-SP5-Pool for x86_64 SUSE Linux Enterprise Server 15 SP5 x86_64 [sle-product-sles15-sp5-pool-x86_64] [ ] SLE-Product-SLES15-SP6-Pool for x86_64 SUSE Linux Enterprise Server 15 SP6 x86_64 [sle-product-sles15-sp6-pool-x86_64] [I] SLE-Product-SLES15-SP7-Pool for x86_64 SUSE Linux Enterprise Server 15 SP7 x86_64 [sle-product-sles15-sp7-pool-x86_64] [I] SLE-Module-Basesystem15-SP7-Pool for x86_64 Basesystem Module 15 SP7 x86_64 [sle-module-basesystem15-sp7-pool-x86_64] [I] SLE-Module-Basesystem15-SP7-Updates for x86_64 Basesystem Module 15 SP7 x86_64 [sle-module-basesystem15-sp7-updates-x86_64] [ ] SLE-Module-Containers15-SP7-Pool for x86_64 Containers Module 15 SP7 x86_64 [sle-module-containers15-sp7-pool-x86_64] [ ] SLE-Module-Containers15-SP7-Updates for x86_64 Containers Module 15 SP7 x86_64 [sle-module-containers15-sp7-updates-x86_64] [I] SLE-Module-Desktop-Applications15-SP7-Pool for x86_64 Desktop Applications Module 15 SP7 x86_64 [sle-module-desktop-applications15-sp7-pool-x86_64] [I] SLE-Module-Desktop-Applications15-SP7-Updates for x86_64 Desktop Applications Module 15 SP7 x86_64 [sle-module-desktop-applications15-sp7-updates-x86_64] [I] SLE-Module-DevTools15-SP7-Pool for x86_64 Development Tools Module 15 SP7 x86_64 [sle-module-devtools15-sp7-pool-x86_64] [I] SLE-Module-DevTools15-SP7-Updates for x86_64 Development Tools Module 15 SP7 x86_64 [sle-module-devtools15-sp7-updates-x86_64] [ ] SLE-Module-Live-Patching15-SP7-Pool for x86_64 SUSE Linux Enterprise Live Patching 15 SP7 x86_64 [sle-module-live-patching15-sp7-pool-x86_64] [ ] SLE-Module-Live-Patching15-SP7-Updates for x86_64 SUSE Linux Enterprise Live Patching 15 SP7 x86_64 [sle-module-live-patching15-sp7-updates-x86_64] [ ] SLE-Module-Public-Cloud15-SP7-Pool for x86_64 Public Cloud Module 15 SP7 x86_64 [sle-module-public-cloud15-sp7-pool-x86_64] [ ] SLE-Module-Public-Cloud15-SP7-Updates for x86_64 Public Cloud Module 15 SP7 x86_64 [sle-module-public-cloud15-sp7-updates-x86_64] [I] SLE-Module-Python3-15-SP7-Pool for x86_64 Python 3 Module 15 SP7 x86_64 [sle-module-python3-15-sp7-pool-x86_64] [I] SLE-Module-Python3-15-SP7-Updates for x86_64 Python 3 Module 15 SP7 x86_64 [sle-module-python3-15-sp7-updates-x86_64] [I] SLE-Module-Server-Applications15-SP7-Pool for x86_64 Server Applications Module 15 SP7 x86_64 [sle-module-server-applications15-sp7-pool-x86_64] [I] SLE-Module-Server-Applications15-SP7-Updates for x86_64 Server Applications Module 15 SP7 x86_64 [sle-module-server-applications15-sp7-updates-x86_64] [I] SLE-Module-Systems-Management-15-SP7-Pool for x86_64 Systems Management Module 15 SP7 x86_64 [sle-module-systems-management-15-sp7-pool-x86_64] [I] SLE-Module-Systems-Management-15-SP7-Updates for x86_64 Systems Management Module 15 SP7 x86_64 [sle-module-systems-management-15-sp7-updates-x86_64] [ ] SLE-Module-Web-Scripting15-SP7-Pool for x86_64 Web and Scripting Module 15 SP7 x86_64 [sle-module-web-scripting15-sp7-pool-x86_64] [ ] SLE-Module-Web-Scripting15-SP7-Updates for x86_64 Web and Scripting Module 15 SP7 x86_64 [sle-module-web-scripting15-sp7-updates-x86_64] [I] SLE-Product-SLES15-SP7-Updates for x86_64 SUSE Linux Enterprise Server 15 SP7 x86_64 [sle-product-sles15-sp7-updates-x86_64] [I] SLE15-SP7-Installer-Updates for x86_64 SUSE Linux Enterprise Server 15 SP7 x86_64 [sle15-sp7-installer-updates-x86_64] [ ] SUSE-MicroOS-5.2-Pool for x86_64 SUSE Linux Enterprise Micro 5.2 x86_64 [suse-microos-5.2-pool-x86_64]
Channel sles15-sp7-devel-uyuni-client-x86_64 finished reposync
Channel sle-product-sles15-sp7-pool-x86_64 finished reposync
Channel sle-product-sles15-sp7-updates-x86_64 finished reposync
Channel sle15-sp7-installer-updates-x86_64 finished reposync
1 minutes out of 41 waiting for 'sles15-sp7' channels to finish reposync
2 minutes out of 41 waiting for 'sles15-sp7' channels to finish reposync
3 minutes out of 41 waiting for 'sles15-sp7' channels to finish reposync
4 minutes out of 41 waiting for 'sles15-sp7' channels to finish reposync
5 minutes out of 41 waiting for 'sles15-sp7' channels to finish reposync
6 minutes out of 41 waiting for 'sles15-sp7' channels to finish reposync
7 minutes out of 41 waiting for 'sles15-sp7' channels to finish reposync
8 minutes out of 41 waiting for 'sles15-sp7' channels to finish reposync
9 minutes out of 41 waiting for 'sles15-sp7' channels to finish reposync
10 minutes out of 41 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-basesystem15-sp7-updates-x86_64 finished reposync
11 minutes out of 41 waiting for 'sles15-sp7' channels to finish reposync
12 minutes out of 41 waiting for 'sles15-sp7' channels to finish reposync
13 minutes out of 41 waiting for 'sles15-sp7' channels to finish reposync
14 minutes out of 41 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-basesystem15-sp7-pool-x86_64 finished reposync
15 minutes out of 41 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-server-applications15-sp7-updates-x86_64 finished reposync
Channel sle-module-server-applications15-sp7-pool-x86_64 finished reposync
16 minutes out of 41 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-python3-15-sp7-updates-x86_64 finished reposync
Channel sle-module-systems-management-15-sp7-updates-x86_64 finished reposync
Channel sle-module-python3-15-sp7-pool-x86_64 finished reposync
17 minutes out of 41 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-systems-management-15-sp7-pool-x86_64 finished reposync
18 minutes out of 41 waiting for 'sles15-sp7' channels to finish reposync
19 minutes out of 41 waiting for 'sles15-sp7' channels to finish reposync
20 minutes out of 41 waiting for 'sles15-sp7' channels to finish reposync
21 minutes out of 41 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-desktop-applications15-sp7-updates-x86_64 finished reposync
22 minutes out of 41 waiting for 'sles15-sp7' channels to finish reposync
23 minutes out of 41 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-desktop-applications15-sp7-pool-x86_64 finished reposync
24 minutes out of 41 waiting for 'sles15-sp7' channels to finish reposync
25 minutes out of 41 waiting for 'sles15-sp7' channels to finish reposync

Given I am authorized for the "Admin" section 523ms

When I follow the left menu "Admin > Setup Wizard > Products" 1s 125ms

And I wait until I do not see "currently running" text 76ms

And I wait until I do not see "Loading" text 832ms

And I enter "SUSE Linux Enterprise Server 15 SP7 x86_64" as the filtered product description 127ms

And I select "SUSE Linux Enterprise Server 15 SP7 x86_64" as a product 70ms

Then I should see the "SUSE Linux Enterprise Server 15 SP7 x86_64" selected 37ms

When I open the sub-list of the product "SUSE Linux Enterprise Server 15 SP7 x86_64" 57ms

And I open the sub-list of the product "Basesystem Module 15 SP7 x86_64" 57ms

And I select "Desktop Applications Module 15 SP7 x86_64" as a product 64ms

Then I should see the "Desktop Applications Module 15 SP7 x86_64" selected 23ms

When I open the sub-list of the product "Desktop Applications Module 15 SP7 x86_64" 50ms

And I select "Development Tools Module 15 SP7 x86_64" as a product 62ms

Then I should see the "Development Tools Module 15 SP7 x86_64" selected 22ms

When I click the Add Product button 53ms

And I wait until I see "Selected channels/products were scheduled successfully for syncing." text 7s 660ms

Then the SLE15 SP7 product should be added 2s 975ms

When I use spacewalk-common-channel to add channel "sles15-sp7-devel-uyuni-client" with arch "x86_64" 9s 143ms

And I wait until I see "SUSE Linux Enterprise Server 15 SP7 x86_64" product has been added 12ms

And I wait until all synchronized channels for "sles15-sp7" have finished 41m Show Error +

                                            
 Hit timeout during reposync. These channels did not complete:
 ["sle-module-devtools15-sp7-updates-x86_64", "sle-module-devtools15-sp7-pool-x86_64"] (ScriptError)
./features/step_definitions/command_steps.rb:482:in `rescue in block in (top (required))'
./features/step_definitions/command_steps.rb:462:in `/^I wait until all synchronized channels for "([^"]*)" have finished$/'
features/reposync/srv_sync_products.feature:113:in `I wait until all synchronized channels for "sles15-sp7" have finished'

17s 953ms Show Info +

19:19:01:000 - 20:00:24:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/admin/setup/products

Screenshot +

@proxy @susemanager @transactional_server

Scenario:
Add SL Micro 6.1 as base OS for proxy

< 1ms 13

Given I am authorized for the "Admin" section 0s

When I follow the left menu "Admin > Setup Wizard > Products" 0s

And I wait until I do not see "currently running" text 0s

And I wait until I do not see "Loading" text 0s

And I enter "SUSE Linux Micro 6.1" as the filtered product description 0s

And I select "SUSE Linux Micro 6.1 x86_64" as a product 0s

Then I should see the "SUSE Linux Micro 6.1 x86_64" selected 0s

When I open the sub-list of the product "SUSE Linux Micro 6.1 x86_64" 0s

And I open the sub-list of the product "SUSE Multi-Linux Manager Client Tools for SL Micro 6 x86_64" if present 0s

And I click the Add Product button 0s

And I wait until I see "Selected channels/products were scheduled successfully for syncing." text 0s

And I wait until I see "SUSE Linux Micro 6.1 x86_64" product has been added 0s

And I wait until all synchronized channels for "sl-micro-6.1" have finished 0s

@proxy @susemanager @skip_if_transactional_server

Scenario:
Add SLES 15 SP7 as base OS for proxy

< 1ms 11

Given I am authorized for the "Admin" section 0s

When I follow the left menu "Admin > Setup Wizard > Products" 0s

And I wait until I do not see "currently running" text 0s

And I wait until I do not see "Loading" text 0s

And I enter "SUSE Linux Enterprise Server 15 SP7" as the filtered product description 0s

And I select "SUSE Linux Enterprise Server 15 SP7 (BETA)" as a product 0s

Then I should see the "SUSE Linux Enterprise Server 15 SP7 (BETA)" selected 0s

When I click the Add Product button 0s

And I wait until I see "Selected channels/products were scheduled successfully for syncing." text 0s

And I wait until I see "SUSE Linux Enterprise Server 15 SP7 (BETA)" product has been added 0s

And I wait until all synchronized channels for "sles15-sp7" have finished 0s

@proxy @susemanager @transactional_server

Scenario:
Add SUSE MLM Proxy Extension 5.1 with SL Micro 6.1 as base OS

< 1ms 13

Given I am authorized for the "Admin" section 0s

When I follow the left menu "Admin > Setup Wizard > Products" 0s

And I wait until I do not see "currently running" text 0s

And I wait until I do not see "Loading" text 0s

And I enter "SUSE Linux Micro 6.1" as the filtered product description 0s

When I open the sub-list of the product "SUSE Linux Micro 6.1 x86_64" 0s

And I select "SUSE Linux Micro 6.1 x86_64" as a product 0s

And I select "SUSE Multi-Linux Manager Proxy Extension 5.1 x86_64" as a product 0s

Then I should see the "SUSE Multi-Linux Manager Proxy Extension 5.1 x86_64" selected 0s

When I click the Add Product button 0s

And I wait until I see "Selected channels/products were scheduled successfully for syncing." text 0s

And I wait until I see "SUSE Multi-Linux Manager Proxy Extension 5.1 x86_64" product has been added 0s

And I wait until all synchronized channels for "suse-multi-linux-manager-proxy-51" have finished 0s

@proxy @susemanager @skip_if_transactional_server

Scenario:
Add SUSE MLM Proxy Extension 5.1 with SLES 15 SP7 as base OS

< 1ms 12

Given I am authorized for the "Admin" section 0s

When I follow the left menu "Admin > Setup Wizard > Products" 0s

And I wait until I do not see "currently running" text 0s

And I wait until I do not see "Loading" text 0s

And I enter "SUSE Linux Enterprise Server 15 SP7" as the filtered product description 0s

When I open the sub-list of the product "SUSE Linux Enterprise Server 15 SP7 x86_64" 0s

And I select "SUSE Multi-Linux Manager Proxy Extension 5.1 x86_64" as a product 0s

Then I should see the "SUSE Multi-Linux Manager Proxy Extension 5.1 x86_64" selected 0s

When I click the Add Product button 0s

And I wait until I see "Selected channels/products were scheduled successfully for syncing." text 0s

And I wait until I see "SUSE Multi-Linux Manager Proxy Extension 5.1 x86_64" product has been added 0s

And I wait until all synchronized channels for "suse-multi-linux-manager-proxy-51-sp7" have finished 0s

@proxy @susemanager @transactional_server

Scenario:
Add SUSE MLM Retail Branch Server Extension 5.1 with SL Micro 6.1 as base OS

< 1ms 13

Given I am authorized for the "Admin" section 0s

When I follow the left menu "Admin > Setup Wizard > Products" 0s

And I wait until I do not see "currently running" text 0s

And I wait until I do not see "Loading" text 0s

And I enter "SUSE Linux Micro 6.1" as the filtered product description 0s

When I open the sub-list of the product "SUSE Linux Micro 6.1 x86_64" 0s

And I select "SUSE Linux Micro 6.1 x86_64" as a product 0s

And I select "SUSE Multi-Linux Manager Retail Branch Server Extension 5.1 x86_64" as a product 0s

Then I should see the "SUSE Multi-Linux Manager Retail Branch Server Extension 5.1 x86_64" selected 0s

When I click the Add Product button 0s

And I wait until I see "Selected channels/products were scheduled successfully for syncing." text 0s

And I wait until I see "SUSE Multi-Linux Manager Retail Branch Server Extension 5.1 x86_64" product has been added 0s

And I wait until all synchronized channels for "suse-multi-linux-manager-retail-branch-server-51" have finished 0s

@proxy @susemanager @skip_if_transactional_server

Scenario:
Add SUSE MLM Retail Branch Server Extension 5.1 with SLES 15 SP7 as base OS

< 1ms 12

Given I am authorized for the "Admin" section 0s

When I follow the left menu "Admin > Setup Wizard > Products" 0s

And I wait until I do not see "currently running" text 0s

And I wait until I do not see "Loading" text 0s

And I enter "SUSE Linux Enterprise Server 15 SP7" as the filtered product description 0s

When I open the sub-list of the product "SUSE Linux Enterprise Server 15 SP7 x86_64" 0s

And I select "SUSE Multi-Linux Manager Retail Branch Server Extension 5.1 x86_64" as a product 0s

Then I should see the "SUSE Multi-Linux Manager Retail Branch Server Extension 5.1 x86_64" selected 0s

When I click the Add Product button 0s

And I wait until I see "Selected channels/products were scheduled successfully for syncing." text 0s

And I wait until I see "SUSE Multi-Linux Manager Retail Branch Server Extension 5.1 x86_64" product has been added 0s

And I wait until all synchronized channels for "suma-retail-branch-server-extension-51-sp7" have finished 0s

@scc_credentials @susemanager

Scenario:
Installer update channels got enabled when products were added

< 1ms 2

When I execute mgr-sync "list channels" with user "admin" and password "admin" 0s

And I should get " [I] SLE15-SP7-Installer-Updates for x86_64 SUSE Linux Enterprise Server 15 SP7 x86_64 [sle15-sp7-installer-updates-x86_64]" 0s

@scc_credentials @skip_if_github_validation

Scenario:
Detect product loading issues from the UI

35s 995ms 7 1

Given I am authorized for the "Admin" section 1s 14ms

When I follow the left menu "Admin > Setup Wizard > Products" 1s 774ms

And I wait until I see "Setup Wizard" text 76ms

And I wait until I do not see "Loading" text 1s 508ms

Then I should not see a "Operation not successful" text 136ms

And I select "250" from "pageSize" 1s 138ms

And I should only see success signs in the product list 14s 131ms Show Error +

                                            
 At least one product is not fully synchronized (ScriptError)
./features/step_definitions/navigation_steps.rb:856:in `/^I should only see success signs in the product list$/'
features/reposync/srv_sync_products.feature:236:in `I should only see success signs in the product list'

16s 214ms Show Info +

20:00:42:000 - 20:01:03:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/admin/setup/products

Screenshot +

@scc_credentials @skip_if_github_validation

Scenario:
Report the synchronization duration for SLES 15 SP7

< 1ms 1

When I report the synchronization duration for "sles15-sp7" < 1ms

Feature:Create fake channels 33s 292ms 11 1

In Order to distribute software to the clients
As an authorized user
I want to create fake channels for each distribution

Scenario:
Log in as admin user

1s 233ms 1

Given I am authorized for the "Admin" section 1s 233ms

Scenario:
Add a fake base channel for x86_64

2s 876ms 10

When I follow the left menu "Software > Manage > Channels" 178ms

And I follow "Create Channel" 696ms

And I enter "Fake-Base-Channel-SUSE-like" as "Channel Name" 122ms

And I enter "fake-base-channel-suse-like" as "Channel Label" 111ms

And I select "None" from "Parent Channel" 57ms

And I select "x86_64" from "Architecture:" 50ms

And I enter "Base channel for testing" as "Channel Summary" 110ms

And I enter "No more description for base channel." as "Channel Description" 152ms

And I click on "Create Channel" 1s 321ms

Then I should see a "Channel Fake-Base-Channel-SUSE-like created." text 75ms

Scenario:
Add a fake child channel into the fake base channel x86_64

2s 253ms 10

When I follow the left menu "Software > Manage > Channels" 76ms

And I follow "Create Channel" 552ms

And I enter "Fake-Child-Channel-SUSE-like" as "Channel Name" 116ms

And I enter "fake-child-channel-suse-like" as "Channel Label" 104ms

And I select "Fake-Base-Channel-SUSE-like" from "Parent Channel" 67ms

And I select "x86_64" from "Architecture:" 35ms

And I enter "Child channel for testing" as "Channel Summary" 99ms

And I enter "Description for Fake Child Channel SUSE like." as "Channel Description" 131ms

And I click on "Create Channel" 993ms

Then I should see a "Channel Fake-Child-Channel-SUSE-like created." text 74ms

@sle_minion

Scenario:
Add a SUSE fake child channel to the SUSE Product base channel

1s 387ms 10

When I follow the left menu "Software > Manage > Channels" 70ms

And I follow "Create Channel" 641ms

And I enter "Fake-RPM-SUSE-Channel" as "Channel Name" 98ms

And I enter "fake-rpm-suse-channel" as "Channel Label" 91ms

And I select the parent channel for the "sle_minion" from "Parent Channel" 49ms

And I select "x86_64" from "Architecture:" 36ms

And I enter "Fake-RPM-SUSE-Channel for testing" as "Channel Summary" 117ms

And I enter "Description for Fake-RPM-SUSE-Channel Child Channel." as "Channel Description" 149ms

And I click on "Create Channel" 56ms

Then I should see a "Channel Fake-RPM-SUSE-Channel created." text 75ms

Scenario:
Add a fake base channel for i586

2s 112ms 10

When I follow the left menu "Software > Manage > Channels" 74ms

And I follow "Create Channel" 558ms

And I enter "Fake-Base-Channel-i586" as "Channel Name" 96ms

And I enter "fake-base-channel-i586" as "Channel Label" 92ms

And I select "None" from "Parent Channel" 40ms

And I select "IA-32" from "Architecture:" 61ms

And I enter "Fake-Base-Channel-i586 channel for testing" as "Channel Summary" 132ms

And I enter "No more description for base channel." as "Channel Description" 118ms

And I click on "Create Channel" 863ms

Then I should see a "Channel Fake-Base-Channel-i586 created." text 74ms

Scenario:
Add a fake child channel into the fake base channel i586

2s 284ms 10

When I follow the left menu "Software > Manage > Channels" 70ms

And I follow "Create Channel" 663ms

And I enter "Fake-Child-Channel-i586" as "Channel Name" 97ms

And I enter "fake-child-channel-i586" as "Channel Label" 94ms

And I select "Fake-Base-Channel-i586" from "Parent Channel" 65ms

And I select "IA-32" from "Architecture:" 38ms

And I enter "Fake Child Channel i586 for testing" as "Channel Summary" 118ms

And I enter "Description for Fake Child Channel i586." as "Channel Description" 122ms

And I click on "Create Channel" 939ms

Then I should see a "Channel Fake-Child-Channel-i586 created." text 73ms

Scenario:
Add a test base channel for x86_64

1s 413ms 10

When I follow the left menu "Software > Manage > Channels" 72ms

And I follow "Create Channel" 668ms

And I enter "Test-Base-Channel-x86_64" as "Channel Name" 99ms

And I enter "test-base-channel-x86_64" as "Channel Label" 97ms

And I select "None" from "Parent Channel" 39ms

And I select "x86_64" from "Architecture:" 37ms

And I enter "Test-Base-Channel-x86_64 channel for testing" as "Channel Summary" 134ms

And I enter "No more description for base channel." as "Channel Description" 127ms

And I click on "Create Channel" 58ms

Then I should see a "Channel Test-Base-Channel-x86_64 created." text 75ms

Scenario:
Add a child channel into the test base channel x86_64

2s 340ms 10

When I follow the left menu "Software > Manage > Channels" 69ms

And I follow "Create Channel" 509ms

And I enter "Test-Child-Channel-x86_64" as "Channel Name" 101ms

And I enter "test-child-channel-x86_64" as "Channel Label" 99ms

And I select "Test-Base-Channel-x86_64" from "Parent Channel" 65ms

And I select "x86_64" from "Architecture:" 38ms

And I enter "Test-Child-Channel-x86_64 channel for testing" as "Channel Summary" 137ms

And I enter "Description for Test-Child-Channel-x86_64 Channel." as "Channel Description" 146ms

And I click on "Create Channel" 1s 97ms

Then I should see a "Channel Test-Child-Channel-x86_64 created." text 75ms

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Add a fake terminal child channel to the SUSE Product base channel

< 1ms 10

When I follow the left menu "Software > Manage > Channels" 0s

And I follow "Create Channel" 0s

And I enter "Fake-RPM-Terminal-Channel" as "Channel Name" 0s

And I enter "fake-rpm-terminal-channel" as "Channel Label" 0s

And I select the parent channel for the "pxeboot_minion" from "Parent Channel" 0s

And I select "x86_64" from "Architecture:" 0s

And I enter "Fake-RPM-Terminal-Channel for testing" as "Channel Summary" 0s

And I enter "Description for Fake-RPM-Terminal-Channel Child Channel." as "Channel Description" 0s

And I click on "Create Channel" 0s

Then I should see a "Channel Fake-RPM-Terminal-Channel created." text 0s

@deblike_minion

Scenario:
Add Debian-like AMD64 base channel

12s 434ms 11

When I follow the left menu "Software > Manage > Channels" 72ms

And I follow "Create Channel" 516ms

And I enter "Fake-Base-Channel-Debian-like" as "Channel Name" 112ms

And I enter "fake-base-channel-debian-like" as "Channel Label" 109ms

And I select "None" from "Parent Channel" 39ms

And I select "AMD64 Debian" from "Architecture:" 56ms

And I enter "Fake-Base-Channel-Debian-like for testing" as "Channel Summary" 130ms

And I enter "No more description for base channel." as "Channel Description" 116ms

And I uncheck "gpg_check" 10s 92ms

And I click on "Create Channel" 64ms

Then I should see a "Channel Fake-Base-Channel-Debian-like created." text 1s 124ms

@rhlike_minion

Scenario:
Add a RedHat-like base channel

2s 556ms 10

When I follow the left menu "Software > Manage > Channels" 91ms

And I follow "Create Channel" 608ms

And I enter "Fake-Base-Channel-RH-like" as "Channel Name" 114ms

And I enter "fake-base-channel-rh-like" as "Channel Label" 103ms

And I select "None" from "Parent Channel" 54ms

And I select "x86_64" from "Architecture:" 43ms

And I enter "Fake-Base-Channel-RH-like for testing" as "Channel Summary" 125ms

And I enter "No more description for base channel." as "Channel Description" 145ms

And I click on "Create Channel" 55ms

Then I should see a "Channel Fake-Base-Channel-RH-like created." text 1s 214ms

@rhlike_minion

Scenario:
Add a fake AppStream base channel

2s 399ms 10

When I follow the left menu "Software > Manage > Channels" 73ms

And I follow "Create Channel" 691ms

And I enter "Fake-Base-Channel-AppStream" as "Channel Name" 108ms

And I enter "fake-base-channel-appstream" as "Channel Label" 105ms

And I select "None" from "Parent Channel" 41ms

And I select "x86_64" from "Architecture:" 34ms

And I enter "Fake-Base-Channel-AppStream for testing" as "Channel Summary" 123ms

And I enter "Description for Fake-Base-Channel-AppStream." as "Channel Description" 129ms

And I click on "Create Channel" 60ms

Then I should see a "Channel Fake-Base-Channel-AppStream created." text 1s 31ms

Feature:Create fake repositories for each fake child channel 59s 752ms 14 1

In order to distribute software to the clients
As an authorized user
I want to create a fake repository per fake child channel

Scenario:
Log in as admin user

1s 75ms 1

Given I am authorized for the "Admin" section 1s 75ms

Scenario:
Create a fake repository for distributions using RPM

1s 57ms 7

When I follow the left menu "Software > Manage > Repositories" 171ms

And I follow "Create Repository" 598ms

And I enter "fake-rpm-repo" as "label" 61ms

And I enter "http://localhost/pub/TestRepoRpmUpdates/" as "url" 85ms

And I click on "Create Repository" 59ms

Then I should see a "Repository created successfully" text 63ms

And I should see "metadataSigned" as checked 18ms

Scenario:
Disable metadata check for the fake RPM repository

11s 493ms 6

When I follow the left menu "Software > Manage > Repositories" 72ms

And I follow "fake-rpm-repo" 469ms

And I uncheck "metadataSigned" 10s 67ms

And I click on "Update Repository" 803ms

Then I should see a "Repository updated successfully" text 64ms

And I should see "metadataSigned" as unchecked 15ms

@rhlike_minion

Scenario:
Create a fake AppStream repository

1s 485ms 7

When I follow the left menu "Software > Manage > Repositories" 68ms

And I follow "Create Repository" 446ms

And I enter "fake-appstream-repo" as "label" 63ms

And I enter "http://localhost/pub/TestRepoAppStream/" as "url" 81ms

And I click on "Create Repository" 748ms

Then I should see a "Repository created successfully" text 62ms

And I should see "metadataSigned" as checked 15ms

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

11s 356ms 6

When I follow the left menu "Software > Manage > Repositories" 69ms

And I follow "fake-appstream-repo" 399ms

And I uncheck "metadataSigned" 10s 66ms

And I click on "Update Repository" 743ms

Then I should see a "Repository updated successfully" text 62ms

And I should see "metadataSigned" as unchecked 15ms

@sle_minion

Scenario:
Add the fake RPM repository to the SUSE fake child channel

4s 152ms 9

When I follow the left menu "Software > Manage > Channels" 78ms

And I follow "Fake-RPM-SUSE-Channel" 784ms

And I enter "file:///etc/pki/rpm-gpg/uyuni-tools-gpg-pubkey-0d20833e.key" as "GPG key URL" 183ms

And I click on "Update Channel" 1s 391ms

Then I should see a "Channel Fake-RPM-SUSE-Channel updated" text 77ms

When I follow "Repositories" in the content area 69ms

And I select the "fake-rpm-repo" repo 70ms

And I click on "Save Repositories" 1s 425ms

Then I should see a "Fake-RPM-SUSE-Channel repository information was successfully updated" text 72ms

Scenario:
Add the fake RPM repository to the Test child channel

3s 219ms 9

When I follow the left menu "Software > Manage > Channels" 65ms

And I follow "Test-Child-Channel-x86_64" 702ms

And I enter "file:///etc/pki/rpm-gpg/uyuni-tools-gpg-pubkey-0d20833e.key" as "GPG key URL" 169ms

And I click on "Update Channel" 969ms

Then I should see a "Channel Test-Child-Channel-x86_64 updated" text 75ms

When I follow "Repositories" in the content area 62ms

And I select the "fake-rpm-repo" repo 53ms

And I click on "Save Repositories" 1s 48ms

Then I should see a "Test-Child-Channel-x86_64 repository information was successfully updated" text 72ms

@rhlike_minion

Scenario:
Add the fake RPM repository to the RedHat-like base channel

3s 86ms 9

When I follow the left menu "Software > Manage > Channels" 68ms

And I follow "Fake-Base-Channel-RH-like" 798ms

And I enter "file:///etc/pki/rpm-gpg/uyuni-tools-gpg-pubkey-0d20833e.key" as "GPG key URL" 170ms

And I click on "Update Channel" 849ms

Then I should see a "Channel Fake-Base-Channel-RH-like updated" text 76ms

When I follow "Repositories" in the content area 61ms

And I select the "fake-rpm-repo" repo 54ms

And I click on "Save Repositories" 935ms

Then I should see a "Fake-Base-Channel-RH-like repository information was successfully updated" text 71ms

@rhlike_minion

Scenario:
Add the fake AppStream repository to the AppStream base channel

2s 114ms 9

When I follow the left menu "Software > Manage > Channels" 68ms

And I follow "Fake-Base-Channel-AppStream" 603ms

And I enter "file:///etc/pki/rpm-gpg/uyuni-tools-gpg-pubkey-0d20833e.key" as "GPG key URL" 163ms

And I click on "Update Channel" 74ms

Then I should see a "Channel Fake-Base-Channel-AppStream updated" text 74ms

When I follow "Repositories" in the content area 62ms

And I select the "fake-appstream-repo" repo 56ms

And I click on "Save Repositories" 938ms

Then I should see a "Fake-Base-Channel-AppStream repository information was successfully updated" text 72ms

Scenario:
Create a fake repository for i586

12s 91ms 7

When I follow the left menu "Software > Manage > Repositories" 72ms

And I follow "Create Repository" 911ms

And I enter "fake-i586-repo" as "label" 60ms

And I enter "file:///srv/www/htdocs/pub/TestRepoRpmUpdates/" as "url" 93ms

And I uncheck "metadataSigned" 10s 75ms

And I click on "Create Repository" 814ms

Then I should see a "Repository created successfully" text 62ms

Scenario:
Add the repository to the i586 channel

2s 951ms 9

When I follow the left menu "Software > Manage > Channels" 73ms

And I follow "Fake-Child-Channel-i586" 529ms

And I enter "file:///etc/pki/rpm-gpg/uyuni-tools-gpg-pubkey-0d20833e.key" as "GPG key URL" 177ms

And I click on "Update Channel" 1s 10ms

Then I should see a "Channel Fake-Child-Channel-i586 updated" text 76ms

When I follow "Repositories" in the content area 72ms

And I select the "fake-i586-repo" repo 55ms

And I click on "Save Repositories" 883ms

Then I should see a "Fake-Child-Channel-i586 repository information was successfully updated" text 72ms

@sle_minion

Scenario:
Add the repository to the SUSE-like child channel

2s 795ms 6

When I follow the left menu "Software > Manage > Channels" 66ms

And I follow "Fake-Child-Channel-SUSE-like" 711ms

And I follow "Repositories" in the content area 61ms

And I select the "fake-rpm-repo" repo 56ms

And I click on "Save Repositories" 1s 825ms

Then I should see a "Fake-Child-Channel-SUSE-like repository information was successfully updated" text 73ms

@deblike_minion

Scenario:
Create a fake repository for Debian-like

931ms 7

When I follow the left menu "Software > Manage > Repositories" 72ms

And I follow "Create Repository" 533ms

And I enter "fake-debian-repo" as "label" 62ms

And I select "deb" from "contenttype" 63ms

And I enter "http://localhost/pub/TestRepoDebUpdates/" as "url" 83ms

And I click on "Create Repository" 52ms

Then I should see a "Repository created successfully" text 63ms

@deblike_minion

Scenario:
Add the repository to the Debian-like base channel

1s 939ms 6

When I follow the left menu "Software > Manage > Channels" 69ms

And I follow "Fake-Base-Channel-Debian-like" 623ms

And I follow "Repositories" in the content area 57ms

And I select the "fake-debian-repo" repo 54ms

And I click on "Save Repositories" 1s 61ms

Then I should see a "Fake-Base-Channel-Debian-like repository information was successfully updated" text 72ms

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Add the repository to the terminal child channel

< 1ms 9

When I follow the left menu "Software > Manage > Channels" 0s

And I follow "Fake-RPM-Terminal-Channel" 0s

And I enter "file:///etc/pki/rpm-gpg/uyuni-tools-gpg-pubkey-0d20833e.key" as "GPG key URL" 0s

And I click on "Update Channel" 0s

Then I should see a "Channel Fake-RPM-Terminal-Channel updated" text 0s

When I follow "Repositories" in the content area 0s

And I select the "fake-rpm-repo" repo 0s

And I click on "Save Repositories" 0s

Then I should see a "Fake-RPM-Terminal-Channel repository information was successfully updated" text 0s

@skip_if_github_validation
Feature:Create custom channels with development repositories 43s 849ms 9

In Order to use product packages in development to the clients
As an authorized user
I want to create custom channels for each distribution

Scenario:
Log in as admin user

1s 102ms 1

Given I am authorized for the "Admin" section 1s 102ms

@sle_minion

Scenario:
Create a custom channel for SUSE minions

2s 517ms 10

When I follow the left menu "Software > Manage > Channels" 179ms

And I follow "Create Channel" 618ms

And I enter "Devel-SUSE-Channel" as "Channel Name" 95ms

And I enter "devel-suse-channel" as "Channel Label" 97ms

And I select the parent channel for the "sle_minion" from "Parent Channel" 55ms

And I select "x86_64" from "Architecture:" 47ms

And I enter "Devel-SUSE-Channel for development repositories" as "Channel Summary" 154ms

And I enter "Channel containing development repositories" as "Channel Description" 147ms

And I click on "Create Channel" 1s 46ms

Then I should see a "Channel Devel-SUSE-Channel created." text 74ms

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

9s 941ms 1

When I prepare the development repositories of "sle_minion" as part of "devel-suse-channel" channel 9s 941ms

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 210ms 10

When I follow the left menu "Software > Manage > Channels" 69ms

And I follow "Create Channel" 436ms

And I enter "Devel-Build-Host-Channel" as "Channel Name" 107ms

And I enter "devel-build-host-channel" as "Channel Label" 99ms

And I select the parent channel for the "build_host" from "Parent Channel" 50ms

And I select "x86_64" from "Architecture:" 35ms

And I enter "Devel-Build-Host-Channel for development repositories" as "Channel Summary" 151ms

And I enter "Channel containing development repositories" as "Channel Description" 128ms

And I click on "Create Channel" 55ms

Then I should see a "Channel Devel-Build-Host-Channel created." text 75ms

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

5s 618ms 1

When I prepare the development repositories of "build_host" as part of "devel-build-host-channel" channel 5s 618ms

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

1s 458ms 10

When I follow the left menu "Software > Manage > Channels" 72ms

And I follow "Create Channel" 632ms

And I enter "Devel-Debian-like-Channel" as "Channel Name" 99ms

And I enter "devel-debian-like-channel" as "Channel Label" 99ms

And I select "Fake-Base-Channel-Debian-like" from "Parent Channel" 68ms

And I select "AMD64 Debian" from "Architecture:" 50ms

And I enter "Devel-Debian-like-Channel for development repositories" as "Channel Summary" 165ms

And I enter "Channel containing development repositories" as "Channel Description" 128ms

And I click on "Create Channel" 63ms

Then I should see a "Channel Devel-Debian-like-Channel created." text 77ms

@deblike_minion

Scenario:
Create custom repositories inside the Debian-like custom channel

10s 969ms 1

When I prepare the development repositories of "deblike_minion" as part of "devel-debian-like-channel" channel 10s 969ms

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

2s 609ms 10

When I follow the left menu "Software > Manage > Channels" 71ms

And I follow "Create Channel" 634ms

And I enter "Devel-RH-like-Channel" as "Channel Name" 97ms

And I enter "devel-rh-like-channel" as "Channel Label" 92ms

And I select "Fake-Base-Channel-RH-like" from "Parent Channel" 63ms

And I select "x86_64" from "Architecture:" 36ms

And I enter "Devel-RH-like-Channel for development repositories" as "Channel Summary" 168ms

And I enter "Channel containing development repositories" as "Channel Description" 127ms

And I click on "Create Channel" 1s 238ms

Then I should see a "Channel Devel-RH-like-Channel created." text 78ms

@rhlike_minion

Scenario:
Create custom repositories inside the RH-like custom channel

8s 419ms 1

When I prepare the development repositories of "rhlike_minion" as part of "devel-rh-like-channel" channel 8s 419ms

Feature:Synchronize fake channels 10m 52s 639ms 12 2

In order to use the content provided inside the repositories of the fake channels
As admin
I want to synchronize the fake channels

Scenario:
Log in as admin user

2s 690ms 2

Given I am authorized for the "Admin" section 784ms

And I enable source package syncing 1s 906ms

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

7s 613ms 9

Given I am authorized for the "Admin" section 1s 137ms

When I follow the left menu "Software > Manage > Channels" 168ms

And I follow "Fake-RPM-SUSE-Channel" 774ms

And I follow "Repositories" in the content area 68ms

And I follow "Sync" 872ms

And I wait at most 60 seconds until I do not see "Repository sync is running." text, refreshing the page 66ms

And I click on "Sync Now" 2s 917ms

Then I should see a "Repository sync scheduled for Fake-RPM-SUSE-Channel." text 69ms

And I wait until the channel "fake-rpm-suse-channel" has been synced 1s 538ms

@sle_minion

Scenario:
Verify state of Fake-RPM-SUSE-Channel channel

9m 43s 264ms 2

Then "orion-dummy-1.1-1.1.x86_64.rpm" package should have been stored 5s 719ms

And solver file for "fake-rpm-suse-channel" should reference "orion-dummy-1.1-1.1.x86_64.rpm" 9m 37s 544ms

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

4s 379ms 9

Given I am authorized for the "Admin" section 676ms

When I follow the left menu "Software > Manage > Channels" 189ms

And I follow "Fake-Child-Channel-i586" 480ms

And I follow "Repositories" in the content area 69ms

And I follow "Sync" 425ms

And I wait at most 60 seconds until I do not see "Repository sync is running." text, refreshing the page 64ms

And I click on "Sync Now" 1s 862ms

Then I should see a "Repository sync scheduled for Fake-Child-Channel-i586." text 67ms

And I wait until the channel "fake-child-channel-i586" has been synced 544ms

Scenario:
Synchronize Test-Child-Channel-x86_64 channel

4s 870ms 9

Given I am authorized for the "Admin" section 567ms

When I follow the left menu "Software > Manage > Channels" 171ms

And I follow "Test-Child-Channel-x86_64" 575ms

And I follow "Repositories" in the content area 60ms

And I follow "Sync" 954ms

And I wait at most 60 seconds until I do not see "Repository sync is running." text, refreshing the page 66ms

And I click on "Sync Now" 1s 858ms

Then I should see a "Repository sync scheduled for Test-Child-Channel-x86_64." text 71ms

And I wait until the channel "test-child-channel-x86_64" has been synced 545ms

@sle_minion

Scenario:
Synchronize Fake-Child-Channel-SUSE-like channel

4s 688ms 9

Given I am authorized for the "Admin" section 542ms

When I follow the left menu "Software > Manage > Channels" 151ms

And I follow "Fake-Child-Channel-SUSE-like" 582ms

And I follow "Repositories" in the content area 62ms

And I follow "Sync" 864ms

And I wait at most 60 seconds until I do not see "Repository sync is running." text, refreshing the page 65ms

And I click on "Sync Now" 1s 863ms

Then I should see a "Repository sync scheduled for Fake-Child-Channel-SUSE-like." text 67ms

And I wait until the channel "fake-child-channel-suse-like" has been synced 487ms

@deblike_minion

Scenario:
Synchronize Fake-Base-Channel-Debian-like channel

4s 882ms 9

Given I am authorized for the "Admin" section 527ms

When I follow the left menu "Software > Manage > Channels" 153ms

And I follow "Fake-Base-Channel-Debian-like" 559ms

And I follow "Repositories" in the content area 57ms

And I follow "Sync" 1s 36ms

And I wait at most 60 seconds until I do not see "Repository sync is running." text, refreshing the page 68ms

And I click on "Sync Now" 1s 853ms

Then I should see a "Repository sync scheduled for Fake-Base-Channel-Debian-like." text 66ms

And I wait until the channel "fake-base-channel-debian-like" has been synced 559ms

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-RH-like channel

4s 954ms 9

Given I am authorized for the "Admin" section 572ms

When I follow the left menu "Software > Manage > Channels" 152ms

And I follow "Fake-Base-Channel-RH-like" 479ms

And I follow "Repositories" in the content area 56ms

And I follow "Sync" 1s 210ms

And I wait at most 60 seconds until I do not see "Repository sync is running." text, refreshing the page 71ms

And I click on "Sync Now" 1s 772ms

Then I should see a "Repository sync scheduled for Fake-Base-Channel-RH-like." text 68ms

And I wait until the channel "fake-base-channel-rh-like" has been synced 571ms

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 980ms 9

Given I am authorized for the "Admin" section 535ms

When I follow the left menu "Software > Manage > Channels" 150ms

And I follow "Fake-Base-Channel-AppStream" 480ms

And I follow "Repositories" in the content area 56ms

And I follow "Sync" 1s 213ms

And I wait at most 60 seconds until I do not see "Repository sync is running." text, refreshing the page 68ms

And I click on "Sync Now" 1s 849ms

Then I should see a "Repository sync scheduled for Fake-Base-Channel-AppStream." text 79ms

And I wait until the channel "fake-base-channel-appstream" has been synced 547ms

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Synchronize the repository in the terminal channel

< 1ms 9

Given I am authorized for the "Admin" section 0s

And I follow the left menu "Software > Manage > Channels" 0s

And I follow "Fake-RPM-Terminal-Channel" 0s

And I follow "Repositories" in the content area 0s

And I follow "Sync" 0s

And I wait at most 60 seconds until I do not see "Repository sync is running." text, refreshing the page 0s

And I click on "Sync Now" 0s

Then I should see a "Repository sync scheduled for Fake-RPM-Terminal-Channel." text 0s

And I wait until the channel "fake-rpm-terminal-channel" has been synced 0s

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Verify state of Fake-RPM-Terminal-Channel custom channel

< 1ms 2

Then "orion-dummy-1.1-1.1.x86_64.rpm" package should have been stored 0s

And solver file for "fake-rpm-terminal-channel" should reference "orion-dummy-1.1-1.1.x86_64.rpm" 0s

Scenario:
Refresh the errata cache

23s 47ms 6

When I follow the left menu "Admin > Task Schedules" 114ms

And I follow "errata-cache-default" 1s 287ms

And I follow "errata-cache-bunch" 1s 326ms

And I click on "Single Run Schedule" 1s 246ms

Then I should see a "bunch was scheduled" text 265ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 18s 807ms

Scenario:
Refresh the channel's repository data

6s 154ms 6

When I follow the left menu "Admin > Task Schedules" 79ms

And I follow "channel-repodata-default" 1s 353ms

And I follow "channel-repodata-bunch" 1s 261ms

And I click on "Single Run Schedule" 1s 453ms

Then I should see a "bunch was scheduled" text 229ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 1s 776ms

Scenario:
Cleanup disable source package syncing

1s 112ms 1

Then I disable source package syncing 1s 112ms

@skip_if_github_validation
Feature:Synchronize development channels 16s 318ms 4

In order to use the content provided inside the repositories of the dev channels
As admin
I want to synchronize the dev channels

@sle_minion

Scenario:
Synchronize Devel-SUSE-Channel channel

3s 759ms 9

Given I am authorized for the "Admin" section 488ms

When I follow the left menu "Software > Manage > Channels" 183ms

And I follow "Devel-SUSE-Channel" 383ms

And I follow "Repositories" in the content area 72ms

And I follow "Sync" 341ms

And I wait at most 60 seconds until I do not see "Repository sync is running." text, refreshing the page 66ms

And I click on "Sync Now" 1s 749ms

Then I should see a "Repository sync scheduled for Devel-SUSE-Channel." text 66ms

And I wait until the channel "devel-suse-channel" has been synced 406ms

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

4s 259ms 9

Given I am authorized for the "Admin" section 478ms

When I follow the left menu "Software > Manage > Channels" 152ms

And I follow "Devel-Debian-like-Channel" 403ms

And I follow "Repositories" in the content area 55ms

And I follow "Sync" 772ms

And I wait at most 60 seconds until I do not see "Repository sync is running." text, refreshing the page 67ms

And I click on "Sync Now" 1s 818ms

Then I should see a "Repository sync scheduled for Devel-Debian-like-Channel." text 70ms

And I wait until the channel "devel-debian-like-channel" has been synced 442ms

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 53ms 9

Given I am authorized for the "Admin" section 543ms

When I follow the left menu "Software > Manage > Channels" 156ms

And I follow "Devel-RH-like-Channel" 381ms

And I follow "Repositories" in the content area 59ms

And I follow "Sync" 508ms

And I wait at most 60 seconds until I do not see "Repository sync is running." text, refreshing the page 66ms

And I click on "Sync Now" 1s 837ms

Then I should see a "Repository sync scheduled for Devel-RH-like-Channel." text 68ms

And I wait until the channel "devel-rh-like-channel" has been synced 429ms

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

4s 246ms 9

Given I am authorized for the "Admin" section 459ms

When I follow the left menu "Software > Manage > Channels" 154ms

And I follow "Devel-Build-Host-Channel" 493ms

And I follow "Repositories" in the content area 56ms

And I follow "Sync" 683ms

And I wait at most 60 seconds until I do not see "Repository sync is running." text, refreshing the page 65ms

And I click on "Sync Now" 1s 866ms

Then I should see a "Repository sync scheduled for Devel-Build-Host-Channel." text 66ms

And I wait until the channel "devel-build-host-channel" has been synced 399ms

Feature:Create activation keys 16s 367ms 9

In order to register systems to the server
As the testing user
I want to use activation keys

Scenario:
Log in as admin user

476ms 1

Given I am authorized for the "Admin" section 476ms

@sle_minion

Scenario:
Create an activation key with a channel

2s 449ms 2

When I create an activation key with id "SUSE-KEY-x86_64", description "SUSE Test Key x86_64", limit of 20 and contact method "default" 1s 837ms

Then I should get the new activation key "1-SUSE-KEY-x86_64" 611ms

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

1s 640ms 2

When I create an activation key with id "RH-LIKE-KEY", description "RedHat like Test Key", base channel "fake-base-channel-rh-like", limit of 20 and contact method "default" 953ms

Then I should get the new activation key "1-RH-LIKE-KEY" 686ms

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

1s 542ms 2

When I create an activation key with id "DEBLIKE-KEY", description "Debian-like Test Key", base channel "fake-base-channel-debian-like", limit of 20 and contact method "default" 826ms

Then I should get the new activation key "1-DEBLIKE-KEY" 716ms

@ssh_minion

Scenario:
Create an activation key with a channel for salt-ssh

1s 594ms 2

When I create an activation key with id "SUSE-SSH-KEY-x86_64", description "SUSE SSH Test Key x86_64", limit of 20 and contact method "ssh-push" 769ms

Then I should get the new activation key "1-SUSE-SSH-KEY-x86_64" 824ms

@ssh_minion

Scenario:
Create an activation key with a channel for salt-ssh via tunnel

1s 961ms 2

When I create an activation key with id "SUSE-SSH-TUNNEL-KEY-x86_64", description "SUSE SSH Tunnel Test Key x86_64", limit of 20 and contact method "ssh-push-tunnel" 828ms

Then I should get the new activation key "1-SUSE-SSH-TUNNEL-KEY-x86_64" 1s 133ms

@proxy

Scenario:
Create an activation key for the proxy

1s 977ms 2

When I create an activation key with id "PROXY-KEY-x86_64", description "Proxy Key x86_64", limit of 1 831ms

Then I should get the new activation key "1-PROXY-KEY-x86_64" 1s 145ms

@build_host

Scenario:
Create an activation key for the build host

2s 510ms 3

When I create an activation key with id "BUILD-HOST-KEY-x86_64", description "Build host Key x86_64" 782ms

And I set the entitlements of the activation key "1-BUILD-HOST-KEY-x86_64" to "container_build_host, osimage_build_host" 453ms

Then I should get the new activation key "1-BUILD-HOST-KEY-x86_64" 1s 273ms

@scc_credentials

Scenario:
Create an activation key for the terminal

2s 214ms 2

When I create an activation key with id "TERMINAL-KEY-x86_64", description "Terminal Key x86_64" 827ms

Then I should get the new activation key "1-TERMINAL-KEY-x86_64" 1s 387ms

Feature:Update activation keys 26s 960ms 11 8

In order to register systems to the spacewalk server
As admin
I want to update activation keys to use synchronized base products

Scenario:
Log in as admin user

469ms 1

Given I am authorized for the "Admin" section 469ms

@scc_credentials @susemanager

Scenario:
Update SLE key with synced base product

< 1ms 20

When I follow the left menu "Systems > Activation Keys" 0s

And I follow "SUSE Test Key x86_64" in the content area 0s

And I wait for child channels to appear 0s

And I select the parent channel for the "sle_minion" from "selectedBaseChannel" 0s

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

And I wait until "SLE-Module-Basesystem15-SP7-Pool for x86_64" has been checked 0s

And I wait until "SLE-Module-Basesystem15-SP7-Updates for x86_64" has been checked 0s

And I wait until "SLE-Module-Server-Applications15-SP7-Pool for x86_64" has been checked 0s

And I wait until "SLE-Module-Server-Applications15-SP7-Updates for x86_64" has been checked 0s

And I check "SLE-Module-DevTools15-SP7-Pool for x86_64" 0s

And I wait until "SLE-Module-DevTools15-SP7-Updates for x86_64" has been checked 0s

And I wait until "SLE-Module-Desktop-Applications15-SP7-Pool for x86_64" has been checked 0s

And I wait until "SLE-Module-Desktop-Applications15-SP7-Updates for x86_64" has been checked 0s

And I check "SLE-Module-Containers15-SP7-Pool for x86_64" 0s

And I wait until "SLE-Module-Containers15-SP7-Updates for x86_64" has been checked 0s

And I check "Fake-RPM-SUSE-Channel" 0s

And I wait until "Fake-RPM-SUSE-Channel" has been checked 0s

And I click on "Update Activation Key" 0s

Then I should see a "Activation key SUSE Test Key x86_64 has been modified" text 0s

@uyuni

Scenario:
Update openSUSE Tumbleweed key with synced base product

2s 644ms 10

When I follow the left menu "Systems > Activation Keys" 121ms

And I follow "SUSE Test Key x86_64" in the content area 71ms

And I wait until I do not see "Loading..." text 653ms

And I select the parent channel for the "sle_minion" from "selectedBaseChannel" 61ms

And I wait until I do not see "Loading..." text 79ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 768ms

And I check "Fake-RPM-SUSE-Channel" 89ms

And I wait until "Fake-RPM-SUSE-Channel" has been checked 16ms

And I click on "Update Activation Key" 711ms

Then I should see a "Activation key SUSE Test Key x86_64 has been modified" text 71ms

@scc_credentials @susemanager

Scenario:
Update SLE SSH key with synced base product

< 1ms 14

When I follow the left menu "Systems > Activation Keys" 0s

And I follow "SUSE SSH Test Key x86_64" in the content area 0s

And I wait for child channels to appear 0s

And I select the parent channel for the "sle_minion" from "selectedBaseChannel" 0s

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

And I check "SLE-Module-DevTools15-SP7-Pool for x86_64" 0s

And I wait until "SLE-Module-DevTools15-SP7-Updates for x86_64" has been checked 0s

And I wait until "SLE-Module-Desktop-Applications15-SP7-Pool for x86_64" has been checked 0s

And I wait until "SLE-Module-Desktop-Applications15-SP7-Updates for x86_64" has been checked 0s

And I check "Fake-RPM-SUSE-Channel" 0s

And I wait until "Fake-RPM-SUSE-Channel" has been checked 0s

And I click on "Update Activation Key" 0s

Then I should see a "Activation key SUSE SSH Test Key x86_64 has been modified" text 0s

@uyuni

Scenario:
Update openSUSE Tumbleweed SSH key with synced base product

1s 762ms 10

When I follow the left menu "Systems > Activation Keys" 61ms

And I follow "SUSE SSH Test Key x86_64" in the content area 67ms

And I wait until I do not see "Loading..." text 566ms

And I select the parent channel for the "sle_minion" from "selectedBaseChannel" 41ms

And I wait until I do not see "Loading..." text 72ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 727ms

And I check "Fake-RPM-SUSE-Channel" 74ms

And I wait until "Fake-RPM-SUSE-Channel" has been checked 17ms

And I click on "Update Activation Key" 58ms

Then I should see a "Activation key SUSE SSH Test Key x86_64 has been modified" text 74ms

@scc_credentials @susemanager

Scenario:
Update SLE SSH tunnel key with synced base product

< 1ms 14

When I follow the left menu "Systems > Activation Keys" 0s

And I follow "SUSE SSH Tunnel Test Key x86_64" in the content area 0s

And I wait for child channels to appear 0s

And I select the parent channel for the "sle_minion" from "selectedBaseChannel" 0s

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

And I check "SLE-Module-DevTools15-SP7-Pool for x86_64" 0s

And I wait until "SLE-Module-DevTools15-SP7-Updates for x86_64" has been checked 0s

And I wait until "SLE-Module-Desktop-Applications15-SP7-Pool for x86_64" has been checked 0s

And I wait until "SLE-Module-Desktop-Applications15-SP7-Updates for x86_64" has been checked 0s

And I check "Fake-RPM-SUSE-Channel" 0s

And I wait until "Fake-RPM-SUSE-Channel" has been checked 0s

And I click on "Update Activation Key" 0s

Then I should see a "Activation key SUSE SSH Tunnel Test Key x86_64 has been modified" text 0s

@uyuni

Scenario:
Update openSUSE Tumbleweed SSH tunnel key with synced base product

2s 856ms 10

When I follow the left menu "Systems > Activation Keys" 62ms

And I follow "SUSE SSH Tunnel Test Key x86_64" in the content area 67ms

And I wait until I do not see "Loading..." text 810ms

And I select the parent channel for the "sle_minion" from "selectedBaseChannel" 40ms

And I wait until I do not see "Loading..." text 70ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 972ms

And I check "Fake-RPM-SUSE-Channel" 84ms

And I wait until "Fake-RPM-SUSE-Channel" has been checked 16ms

And I click on "Update Activation Key" 659ms

Then I should see a "Activation key SUSE SSH Tunnel Test Key x86_64 has been modified" text 71ms

@scc_credentials @susemanager @proxy @containerized_server @transactional_server

Scenario:
Update the SLE Micro proxy key with synced base product

< 1ms 11

When I follow the left menu "Systems > Activation Keys" 0s

And I follow "Proxy Key x86_64" in the content area 0s

And I wait for child channels to appear 0s

And I select the parent channel for the "proxy_container" from "selectedBaseChannel" 0s

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

And I wait until "ManagerTools-SL-Micro-6.1 for x86_64" has been checked 0s

And I check "SUSE-Multi-Linux-Manager-Proxy-5.1 for x86_64" 0s

And I check "SUSE-Multi-Linux-Manager-Retail-Branch-Server-5.1 for x86_64" 0s

And I click on "Update Activation Key" 0s

Then I should see a "Activation key Proxy Key x86_64 has been modified" text 0s

@scc_credentials @susemanager @proxy @containerized_server @skip_if_transactional_server

Scenario:
Update the SLES proxy key with synced base product

< 1ms 11

When I follow the left menu "Systems > Activation Keys" 0s

And I follow "Proxy Key x86_64" in the content area 0s

And I wait for child channels to appear 0s

And I select the parent channel for the "proxy_nontransactional" from "selectedBaseChannel" 0s

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

And I wait until "ManagerTools-SLE15-Pool for x86_64 SP7" has been checked 0s

And I check "SUSE-Manager-Proxy-5.1-Pool for x86_64" 0s

And I check "SUSE-Manager-Proxy-5.1-Updates for x86_64" 0s

And I click on "Update Activation Key" 0s

Then I should see a "Activation key Proxy Key x86_64 has been modified" text 0s

@uyuni @proxy @containerized_server @skip_if_cloud

Scenario:
Update the openSUSE Tumbleweed Proxy Host key with synced base product

< 1ms 8

When I follow the left menu "Systems > Activation Keys" 0s

And I follow "Proxy Key x86_64" in the content area 0s

And I wait for child channels to appear 0s

And I select the parent channel for the "proxy_container" from "selectedBaseChannel" 0s

And I wait for child channels to appear 0s

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 0s

And I click on "Update Activation Key" 0s

Then I should see a "Activation key Proxy Key x86_64 has been modified" text 0s

@scc_credentials @build_host

Scenario:
Update build host key with synced base product

3s 722ms 20

When I follow the left menu "Systems > Activation Keys" 58ms

And I follow "Build host Key x86_64" in the content area 67ms

And I wait for child channels to appear 1s 679ms

And I select the parent channel for the "build_host" from "selectedBaseChannel" 50ms

And I wait for child channels to appear 631ms

And I include the recommended child channels 174ms

And I wait until "SLE-Module-Basesystem15-SP7-Pool for x86_64" has been checked 19ms

And I wait until "SLE-Module-Basesystem15-SP7-Updates for x86_64" has been checked 19ms

And I wait until "SLE-Module-Server-Applications15-SP7-Pool for x86_64" has been checked 19ms

And I wait until "SLE-Module-Server-Applications15-SP7-Updates for x86_64" has been checked 19ms

And I check "SLE-Module-DevTools15-SP7-Pool for x86_64" 80ms

And I wait until "SLE-Module-DevTools15-SP7-Updates for x86_64" has been checked 18ms

And I wait until "SLE-Module-Desktop-Applications15-SP7-Pool for x86_64" has been checked 18ms

And I wait until "SLE-Module-Desktop-Applications15-SP7-Updates for x86_64" has been checked 19ms

And I wait until "SLE-Module-Systems-Management-15-SP7-Pool for x86_64" has been checked 18ms

And I wait until "SLE-Module-Systems-Management-15-SP7-Updates for x86_64" has been checked 18ms

And I wait until "SLE-Module-Python3-15-SP7-Pool for x86_64" has been checked 18ms

And I wait until "SLE-Module-Python3-15-SP7-Updates for x86_64" has been checked 18ms

And I click on "Update Activation Key" 699ms

Then I should see a "Activation key Build host Key x86_64 has been modified" text 71ms

@scc_credentials @uyuni @build_host

Scenario:
Update build host key with Uyuni client tools

2s 870ms 9

When I follow the left menu "Systems > Activation Keys" 61ms

And I follow "Build host Key x86_64" in the content area 60ms

And I wait for child channels to appear 1s 255ms

And I select the parent channel for the "build_host" from "selectedBaseChannel" 23ms

And I wait for child channels to appear 318ms

And I check "Uyuni Client Tools for SLES15 SP7 x86_64 (Development)" 85ms

And I wait until "Uyuni Client Tools for SLES15 SP7 x86_64 (Development)" has been checked 15ms

And I click on "Update Activation Key" 979ms

Then I should see a "Activation key Build host Key x86_64 has been modified" text 70ms

@skip_if_github_validation @scc_credentials @uyuni @build_host

Scenario:
Update build host key with dev child channel

3s 76ms 9

When I follow the left menu "Systems > Activation Keys" 58ms

And I follow "Build host Key x86_64" in the content area 61ms

And I wait for child channels to appear 1s 711ms

And I select the parent channel for the "build_host" from "selectedBaseChannel" 23ms

And I wait for child channels to appear 320ms

And I check "Devel-Build-Host-Channel" 106ms

And I wait until "Devel-Build-Host-Channel" has been checked 15ms

And I click on "Update Activation Key" 706ms

Then I should see a "Activation key Build host Key x86_64 has been modified" text 72ms

@scc_credentials @build_host

Scenario:
Update terminal key with synced base product

3s 620ms 16

When I follow the left menu "Systems > Activation Keys" 64ms

And I follow "Terminal Key x86_64" in the content area 70ms

And I wait for child channels to appear 1s 717ms

And I select the parent channel for the "pxeboot_minion" from "selectedBaseChannel" 49ms

And I wait for child channels to appear 602ms

And I include the recommended child channels 162ms

And I wait until "SLE-Module-Basesystem15-SP7-Pool for x86_64" has been checked 16ms

And I wait until "SLE-Module-Basesystem15-SP7-Updates for x86_64" has been checked 16ms

And I wait until "SLE-Module-Server-Applications15-SP7-Pool for x86_64" has been checked 16ms

And I wait until "SLE-Module-Server-Applications15-SP7-Updates for x86_64" has been checked 15ms

And I check "SLE-Module-DevTools15-SP7-Pool for x86_64" 71ms

And I wait until "SLE-Module-DevTools15-SP7-Updates for x86_64" has been checked 15ms

And I wait until "SLE-Module-Desktop-Applications15-SP7-Pool for x86_64" has been checked 15ms

And I wait until "SLE-Module-Desktop-Applications15-SP7-Updates for x86_64" has been checked 15ms

And I click on "Update Activation Key" 699ms

Then I should see a "Activation key Terminal Key x86_64 has been modified" text 72ms

@susemanager @scc_credentials @build_host

Scenario:
Update terminal key with normal SUSE fake channel

< 1ms 9

When I follow the left menu "Systems > Activation Keys" 0s

And I follow "Terminal Key x86_64" in the content area 0s

And I wait for child channels to appear 0s

And I check "SLE-Module-Containers15-SP7-Pool for x86_64" 0s

And I wait until "SLE-Module-Containers15-SP7-Updates for x86_64" has been checked 0s

And I check "Fake-RPM-SUSE-Channel" 0s

And I wait until "Fake-RPM-SUSE-Channel" has been checked 0s

And I click on "Update Activation Key" 0s

Then I should see a "Activation key Terminal Key x86_64 has been modified" text 0s

@pxeboot_minion @uyuni @scc_credentials @build_host

Scenario:
Update terminal key with specific fake channel

< 1ms 9

When I follow the left menu "Systems > Activation Keys" 0s

And I follow "Terminal Key x86_64" in the content area 0s

And I wait for child channels to appear 0s

And I check "Fake-RPM-Terminal-Channel" 0s

And I wait until "Fake-RPM-Terminal-Channel" has been checked 0s

And I check "Uyuni Client Tools for SLES15 SP7 x86_64 (Development)" 0s

And I wait until "Uyuni Client Tools for SLES15 SP7 x86_64 (Development)" has been checked 0s

And I click on "Update Activation Key" 0s

Then I should see a "Activation key Terminal Key x86_64 has been modified" text 0s

@skip_if_github_validation @sle_minion

Scenario:
Update SLE key with to include dev child channel

1s 984ms 6

When I follow the left menu "Systems > Activation Keys" 58ms

And I follow "SUSE Test Key x86_64" in the content area 76ms

And I wait for child channels to appear 1s 64ms

And I check "Devel-SUSE-Channel" 76ms

And I click on "Update Activation Key" 635ms

Then I should see a "Activation key SUSE Test Key x86_64 has been modified" text 73ms

@skip_if_github_validation @deblike_minion

Scenario:
Update Debian-like key with to include dev child channel

1s 999ms 6

When I follow the left menu "Systems > Activation Keys" 63ms

And I follow "Debian-like Test Key" in the content area 73ms

And I wait for child channels to appear 1s 45ms

And I check "Devel-Debian-like-Channel" 78ms

And I click on "Update Activation Key" 667ms

Then I should see a "Activation key Debian-like Test Key has been modified" text 70ms

@skip_if_github_validation @rhlike_minion

Scenario:
Update RedHat-like key with to include dev child channel

1s 954ms 6

When I follow the left menu "Systems > Activation Keys" 61ms

And I follow "RedHat like Test Key" in the content area 73ms

And I wait for child channels to appear 969ms

And I check "Devel-RH-like-Channel" 77ms

And I click on "Update Activation Key" 693ms

Then I should see a "Activation key RedHat like Test Key has been modified" text 78ms

Feature:Create bootstrap repositories 9s 324ms 4

In order to be able to enroll clients with MU repositories
As the system administrator
I create all bootstrap repos with --with-custom-channels option

Scenario:
Create the bootstrap repositories including custom channels

2s 420ms 1

When I create the bootstrap repositories including custom channels 2s 420ms

@sle_minion

Scenario:
Create the bootstrap repository for SUSE Minion

2s 210ms 1

base_channel: openSUSE Tumbleweed (x86_64)
channel: openSUSE-Tumbleweed-x86_64-uyuni
parent_channel:
Creating the bootstrap repository on the server:
mgr-create-bootstrap-repo --create openSUSE-Tumbleweed-x86_64-uyuni --with-custom-channels

When I create the bootstrap repository for "sle_minion" on the server 2s 210ms

@proxy

Scenario:
Create the bootstrap repository for Proxy

2s 185ms 1

When I create the bootstrap repository for "proxy" on the server 2s 185ms

@build_host

Scenario:
Create the bootstrap repository for Build Host

2s 508ms 1

base_channel: SLE-Product-SLES15-SP7-Pool for x86_64
channel: SLE-15-SP7-x86_64
parent_channel: sle-product-sles15-sp7-pool-x86_64
Creating the bootstrap repository on the server:
mgr-create-bootstrap-repo --create SLE-15-SP7-x86_64 --with-parent-channel sle-product-sles15-sp7-pool-x86_64 --with-custom-channels

When I create the bootstrap repository for "build_host" on the server 2s 508ms

@transactional_server
Feature:SELinux debugging < 1ms 1

In order for the server to behave correctly after a reboot
I want to be sure that there is no wrong SELinux label

Scenario:
No previous operation has created wrong SELinux label

< 1ms 1

Then files on container volumes should all have the proper SELinux label 0s

@new_issue
Feature:Debug the server after the testsuite has run 18s 381ms 5

Scenario:
Call spacewalk-debug on server

14s 565ms 1

When I execute spacewalk-debug on the server 14s 565ms

Scenario:
Check the tomcat logs on server

665ms 1

Then the tomcat logs should not contain errors 665ms

Scenario:
Check salt event log for failures on server

1s 755ms 1

Then the salt event log on server should contain no failures 1s 755ms

Scenario:
Check the taskomatic logs on server

709ms 1

Then the taskomatic logs should not contain errors 709ms

Scenario:
Check for out of memory errors

685ms 1

Then the log messages should not contain out of memory errors 685ms

Feature:Debug the clients after the testsuite has run 1m 33s 1ms 1

Scenario:
Extract the logs from all our clients

1m 33s 1ms 1

When I extract the log files from all our active nodes 1m 33s 1ms

@srv_scc_access_logging
Feature:Test for excessive SCC accesses < 1ms 2

Scenario:
Count UI SCC accesses in rhn_web_ui.log

< 1ms 1

Then the word "scc.suse.com" does not occur more than 100 times in "/var/log/rhn/rhn_web_ui.log" on "server" 0s

Scenario:
Count Taskomatic SCC accesses in rhn_taskomatic_daemon.log

< 1ms 1

Then the word "scc.suse.com" does not occur more than 50 times in "/var/log/rhn/rhn_taskomatic_daemon.log" on "server" 0s

All Scenarios

148

Passed Scenarios

116

Failed Scenarios

2

Skipped Scenarios

30

@proxy Scenario:The proxy is healthy 4s 459ms 4

@sle_minion Scenario:The minion is healthy 6s 238ms 4

@build_host Scenario:The build host is healthy 3s 793ms 4

@ssh_minion Scenario:The SSH minion is healthy 6s 211ms 4

@rhlike_minion Scenario:The Red Hat-like minion is healthy 3s 133ms 4

@deblike_minion Scenario:The Debian-like minion is healthy 6s 636ms 4

@skip_if_cloud Scenario:The external resources can be reached < 1ms 3

@server_http_proxy Scenario:The HTTP proxy is working < 1ms 1

@auth_registry Scenario:The registry with authentication is healthy 655ms 1

@no_auth_registry Scenario:The registry without authentication is healthy 675ms 1

@custom_download_endpoint Scenario:The custom download endpoint is working 703ms 1

@skip_if_containerized_server Scenario:Create admin user and first organization < 1ms 12

@server_http_proxy Scenario:Setup HTTP proxy < 1ms 9

@scc_credentials @no_mirror Scenario:Enter valid SCC credentials < 1ms 6

@no_auth_registry Scenario:Create an image store without credentials 3s 440ms 7

@scc_credentials Feature:List available channels and enable them 1m 42s 895ms 5 1

@proxy @susemanager Scenario:List all products for SUSE Multi-Linux Manager < 1ms 6

@scc_credentials Scenario:Refresh SCC 29s 812ms 1

@scc_credentials Scenario:Let the products page appear 3s 138ms 6

@scc_credentials Scenario:Use the products and architecture filters 2s 537ms 7

@scc_credentials @susemanager Scenario:View the channels list in the products page < 1ms 9

@scc_credentials @susemanager Scenario:Synchronize SLES 15 SP7 product with recommended sub-products, including MLM Client Tools < 1ms 30

@uyuni Scenario:Partially add openSUSE Tumbleweed product, only including the required packages to generate the bootstrap repository 50s 668ms 4

@containerized_server @proxy @uyuni Scenario:Add Uyuni Proxy product for Tumbleweed, including Uyuni Client Tools 1m 26s 387ms 2

@scc_credentials @uyuni @build_host Scenario:Synchronize SLES 15 SP7 product with recommended sub-products for Retail feature 41m 40s 930ms 20 1

@proxy @susemanager @transactional_server Scenario:Add SL Micro 6.1 as base OS for proxy < 1ms 13

@proxy @susemanager @skip_if_transactional_server Scenario:Add SLES 15 SP7 as base OS for proxy < 1ms 11

@proxy @susemanager @transactional_server Scenario:Add SUSE MLM Proxy Extension 5.1 with SL Micro 6.1 as base OS < 1ms 13

@proxy @susemanager @skip_if_transactional_server Scenario:Add SUSE MLM Proxy Extension 5.1 with SLES 15 SP7 as base OS < 1ms 12

@proxy @susemanager @transactional_server Scenario:Add SUSE MLM Retail Branch Server Extension 5.1 with SL Micro 6.1 as base OS < 1ms 13

@proxy @susemanager @skip_if_transactional_server Scenario:Add SUSE MLM Retail Branch Server Extension 5.1 with SLES 15 SP7 as base OS < 1ms 12

@scc_credentials @susemanager Scenario:Installer update channels got enabled when products were added < 1ms 2

@scc_credentials @skip_if_github_validation Scenario:Detect product loading issues from the UI 35s 995ms 7 1

@scc_credentials @skip_if_github_validation Scenario:Report the synchronization duration for SLES 15 SP7 < 1ms 1

@sle_minion Scenario:Add a SUSE fake child channel to the SUSE Product base channel 1s 387ms 10

@pxeboot_minion @uyuni @scc_credentials Scenario:Add a fake terminal child channel to the SUSE Product base channel < 1ms 10

@deblike_minion Scenario:Add Debian-like AMD64 base channel 12s 434ms 11

@rhlike_minion Scenario:Add a RedHat-like base channel 2s 556ms 10

@rhlike_minion Scenario:Add a fake AppStream base channel 2s 399ms 10

@rhlike_minion Scenario:Create a fake AppStream repository 1s 485ms 7

@rhlike_minion Scenario:Disable metadata check for the fake AppStream repository 11s 356ms 6

@sle_minion Scenario:Add the fake RPM repository to the SUSE fake child channel 4s 152ms 9

@rhlike_minion Scenario:Add the fake RPM repository to the RedHat-like base channel 3s 86ms 9

@rhlike_minion Scenario:Add the fake AppStream repository to the AppStream base channel 2s 114ms 9

@sle_minion Scenario:Add the repository to the SUSE-like child channel 2s 795ms 6

@deblike_minion Scenario:Create a fake repository for Debian-like 931ms 7

@deblike_minion Scenario:Add the repository to the Debian-like base channel 1s 939ms 6

@pxeboot_minion @uyuni @scc_credentials Scenario:Add the repository to the terminal child channel < 1ms 9

@skip_if_github_validation Feature:Create custom channels with development repositories 43s 849ms 9

@sle_minion Scenario:Create a custom channel for SUSE minions 2s 517ms 10

@sle_minion Scenario:Create custom repositories inside the SUSE custom channel 9s 941ms 1

@uyuni @build_host Scenario:Create a custom channel for Build Host 1s 210ms 10

@uyuni @build_host Scenario:Create custom repositories inside the Build Host custom channel 5s 618ms 1

@deblike_minion Scenario:Create a custom channel for Debian-like minions 1s 458ms 10

@deblike_minion Scenario:Create custom repositories inside the Debian-like custom channel 10s 969ms 1

@rhlike_minion Scenario:Create a custom channel for RH-like minions 2s 609ms 10

@rhlike_minion Scenario:Create custom repositories inside the RH-like custom channel 8s 419ms 1

@sle_minion Scenario:Synchronize Fake-RPM-SUSE-Channel channel 7s 613ms 9

@sle_minion Scenario:Verify state of Fake-RPM-SUSE-Channel channel 9m 43s 264ms 2

@skip_if_github_validation Scenario:Synchronize Fake-Child-Channel-i586 channel 4s 379ms 9

@sle_minion Scenario:Synchronize Fake-Child-Channel-SUSE-like channel 4s 688ms 9

@deblike_minion Scenario:Synchronize Fake-Base-Channel-Debian-like channel 4s 882ms 9

@rhlike_minion Scenario:Synchronize Fake-Base-Channel-RH-like channel 4s 954ms 9

@rhlike_minion Scenario:Synchronize Fake-Base-Channel-AppStream channel 4s 980ms 9

@pxeboot_minion @uyuni @scc_credentials Scenario:Synchronize the repository in the terminal channel < 1ms 9

@pxeboot_minion @uyuni @scc_credentials Scenario:Verify state of Fake-RPM-Terminal-Channel custom channel < 1ms 2

@skip_if_github_validation Feature:Synchronize development channels 16s 318ms 4

@sle_minion Scenario:Synchronize Devel-SUSE-Channel channel 3s 759ms 9

@deblike_minion Scenario:Synchronize Devel-Debian-like-Channel channel 4s 259ms 9

@rhlike_minion Scenario:Synchronize Devel-RH-like-Channel channel 4s 53ms 9

@build_host @uyuni Scenario:Synchronize Devel-Build-Host-Channel channel 4s 246ms 9

@sle_minion Scenario:Create an activation key with a channel 2s 449ms 2

@proxy

Scenario:
The proxy is healthy

4s 459ms 4

@sle_minion

Scenario:
The minion is healthy

6s 238ms 4

@build_host

Scenario:
The build host is healthy

3s 793ms 4

@ssh_minion

Scenario:
The SSH minion is healthy

6s 211ms 4

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 133ms 4

@deblike_minion

Scenario:
The Debian-like minion is healthy

6s 636ms 4

@skip_if_cloud

Scenario:
The external resources can be reached

< 1ms 3

@server_http_proxy

Scenario:
The HTTP proxy is working

< 1ms 1

@auth_registry

Scenario:
The registry with authentication is healthy

655ms 1

@no_auth_registry

Scenario:
The registry without authentication is healthy

675ms 1

@custom_download_endpoint

Scenario:
The custom download endpoint is working

703ms 1

@skip_if_containerized_server

Scenario:
Create admin user and first organization

< 1ms 12

@server_http_proxy

Scenario:
Setup HTTP proxy

< 1ms 9

@scc_credentials @no_mirror

Scenario:
Enter valid SCC credentials

< 1ms 6

@no_auth_registry

Scenario:
Create an image store without credentials

3s 440ms 7

@scc_credentials
Feature:List available channels and enable them 1m 42s 895ms 5 1

@proxy @susemanager

Scenario:
List all products for SUSE Multi-Linux Manager

< 1ms 6

@scc_credentials

Scenario:
Refresh SCC

29s 812ms 1

@scc_credentials

Scenario:
Let the products page appear

3s 138ms 6

@scc_credentials

Scenario:
Use the products and architecture filters

2s 537ms 7

@scc_credentials @susemanager

Scenario:
View the channels list in the products page

< 1ms 9

@scc_credentials @susemanager

Scenario:
Synchronize SLES 15 SP7 product with recommended sub-products, including MLM Client Tools

< 1ms 30

@uyuni

Scenario:
Partially add openSUSE Tumbleweed product, only including the required packages to generate the bootstrap repository

50s 668ms 4

@containerized_server @proxy @uyuni

Scenario:
Add Uyuni Proxy product for Tumbleweed, including Uyuni Client Tools

1m 26s 387ms 2

@scc_credentials @uyuni @build_host

Scenario:
Synchronize SLES 15 SP7 product with recommended sub-products for Retail feature

41m 40s 930ms 20 1

@proxy @susemanager @transactional_server

Scenario:
Add SL Micro 6.1 as base OS for proxy

< 1ms 13

@proxy @susemanager @skip_if_transactional_server

Scenario:
Add SLES 15 SP7 as base OS for proxy

< 1ms 11

@proxy @susemanager @transactional_server

Scenario:
Add SUSE MLM Proxy Extension 5.1 with SL Micro 6.1 as base OS

< 1ms 13

@proxy @susemanager @skip_if_transactional_server

Scenario:
Add SUSE MLM Proxy Extension 5.1 with SLES 15 SP7 as base OS

< 1ms 12

@proxy @susemanager @transactional_server

Scenario:
Add SUSE MLM Retail Branch Server Extension 5.1 with SL Micro 6.1 as base OS

< 1ms 13

@proxy @susemanager @skip_if_transactional_server

Scenario:
Add SUSE MLM Retail Branch Server Extension 5.1 with SLES 15 SP7 as base OS

< 1ms 12

@scc_credentials @susemanager

Scenario:
Installer update channels got enabled when products were added

< 1ms 2

@scc_credentials @skip_if_github_validation

Scenario:
Detect product loading issues from the UI

35s 995ms 7 1

@scc_credentials @skip_if_github_validation

Scenario:
Report the synchronization duration for SLES 15 SP7

< 1ms 1

@sle_minion

Scenario:
Add a SUSE fake child channel to the SUSE Product base channel

1s 387ms 10

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Add a fake terminal child channel to the SUSE Product base channel

< 1ms 10

@deblike_minion

Scenario:
Add Debian-like AMD64 base channel

12s 434ms 11

@rhlike_minion

Scenario:
Add a RedHat-like base channel

2s 556ms 10

@rhlike_minion

Scenario:
Add a fake AppStream base channel

2s 399ms 10

@rhlike_minion

Scenario:
Create a fake AppStream repository

1s 485ms 7

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

11s 356ms 6

@sle_minion

Scenario:
Add the fake RPM repository to the SUSE fake child channel

4s 152ms 9

@rhlike_minion

Scenario:
Add the fake RPM repository to the RedHat-like base channel

3s 86ms 9

@rhlike_minion

Scenario:
Add the fake AppStream repository to the AppStream base channel

2s 114ms 9

@sle_minion

Scenario:
Add the repository to the SUSE-like child channel

2s 795ms 6

@deblike_minion

Scenario:
Create a fake repository for Debian-like

931ms 7

@deblike_minion

Scenario:
Add the repository to the Debian-like base channel

1s 939ms 6

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Add the repository to the terminal child channel

< 1ms 9

@skip_if_github_validation
Feature:Create custom channels with development repositories 43s 849ms 9

@sle_minion

Scenario:
Create a custom channel for SUSE minions

2s 517ms 10

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

9s 941ms 1

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 210ms 10

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

5s 618ms 1

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

1s 458ms 10

@deblike_minion

Scenario:
Create custom repositories inside the Debian-like custom channel

10s 969ms 1

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

2s 609ms 10

@rhlike_minion

Scenario:
Create custom repositories inside the RH-like custom channel

8s 419ms 1

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

7s 613ms 9

@sle_minion

Scenario:
Verify state of Fake-RPM-SUSE-Channel channel

9m 43s 264ms 2

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

4s 379ms 9

@sle_minion

Scenario:
Synchronize Fake-Child-Channel-SUSE-like channel

4s 688ms 9

@deblike_minion

Scenario:
Synchronize Fake-Base-Channel-Debian-like channel

4s 882ms 9

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-RH-like channel

4s 954ms 9

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 980ms 9

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Synchronize the repository in the terminal channel

< 1ms 9

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Verify state of Fake-RPM-Terminal-Channel custom channel

< 1ms 2

@skip_if_github_validation
Feature:Synchronize development channels 16s 318ms 4

@sle_minion

Scenario:
Synchronize Devel-SUSE-Channel channel

3s 759ms 9

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

4s 259ms 9

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 53ms 9

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

4s 246ms 9

@sle_minion

Scenario:
Create an activation key with a channel

2s 449ms 2

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

1s 640ms 2

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

1s 542ms 2

@ssh_minion

Scenario:
Create an activation key with a channel for salt-ssh

1s 594ms 2

@ssh_minion

Scenario:
Create an activation key with a channel for salt-ssh via tunnel

1s 961ms 2

@proxy

Scenario:
Create an activation key for the proxy

1s 977ms 2

@build_host

Scenario:
Create an activation key for the build host

2s 510ms 3