Cucumber Feature Report

All Scenarios

201

Passed Scenarios

149

Failed Scenarios

13

Skipped Scenarios

39

Execution Time: 88m 6s 986ms

Expand All | Collapse All

Metadata

App Version: Uyuni/Head

Browser: Chrome

Platform: x86_64

Parallel: Disabled

Feature:Sanity checks 43s 854ms 10 2

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

Scenario:
The server is healthy

11s 819ms 19

Then "server" should have a FQDN 378ms

And reverse resolution should work for "server" 626ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@proxy

Scenario:
The proxy is healthy

4s 381ms 4

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

And reverse resolution should work for "proxy" 274ms

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

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

@sle_minion

Scenario:
The minion is healthy

5s 946ms 4

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

And reverse resolution should work for "sle_minion" 410ms

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

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

@build_host

Scenario:
The build host is healthy

3s 948ms 4

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

And reverse resolution should work for "build_host" 263ms

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

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

@ssh_minion

Scenario:
The SSH minion is healthy

6s 423ms 4

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

And reverse resolution should work for "ssh_minion" 440ms

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

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

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 256ms 4

Then "rhlike_minion" should have a FQDN 2s

And reverse resolution should work for "rhlike_minion" 189ms

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

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

@deblike_minion

Scenario:
The Debian-like minion is healthy

6s 138ms 4

Then "deblike_minion" should have a FQDN 4s 777ms

And reverse resolution should work for "deblike_minion" 218ms

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

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

@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

649ms 1

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

@no_auth_registry

Scenario:
The registry without authentication is healthy

657ms 1

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

@custom_download_endpoint

Scenario:
The custom download endpoint is working

633ms 1

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

Feature:Very first settings 48s 871ms 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

644ms 1

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

@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 869ms 1

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

Scenario:
Wait for refresh of list of products to finish

3s 560ms 1

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

Scenario:
Create testing username

2s 353ms 12

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

And I follow "Create User" 698ms

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

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

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

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

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

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

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

And I click on "Create Login" 921ms

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

And I should see a "testing" link 11ms

Scenario:
Grant testing user administrative priviledges

1s 713ms 10

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

And I follow "testing" 483ms

And I check "role_org_admin" 82ms

And I check "role_system_group_admin" 73ms

And I check "role_channel_admin" 79ms

And I check "role_activation_key_admin" 75ms

And I check "role_config_admin" 74ms

And I click on "Update" 626ms

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

And I should see a "testing" text 71ms

@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

728ms 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" 728ms

Feature:Turn "disable_local_repos" feature on highstate off 3s 693ms 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 693ms 1

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

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 426ms 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

1s 378ms 5

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

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

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

And I click on "Save Preferences" 656ms

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

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

3s 48ms 5

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

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

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

And I click on "Save Preferences" 52ms

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

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

Scenario:
Create a Kiwi user with image administrators rights

4s 115ms 2

New user kiwikiwi created with roles: image_admin

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

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

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

Scenario:
Create a Docker user with image administrators rights

2s 135ms 2

New user docker created with roles: image_admin

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

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

@no_auth_registry

Scenario:
Create an image store without credentials

3s 169ms 7

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

And I follow "Create" 539ms

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

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

And I click on "create-btn" 84ms

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

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

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

Scenario:
Log in as admin user

37s 524ms 1

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

Scenario:
Disable scheduled reposyncs

4s 557ms 5

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

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

And I choose "disabled" 53ms

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

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

Scenario:
Disable scheduled Cobbler syncs

4s 569ms 5

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

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

And I choose "disabled" 46ms

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

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

@scc_credentials
Feature:List available channels and enable them 1m 38s 854ms 5 1

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

Scenario:
List available channels

33s 4ms 5

When I refresh SCC 30s 774ms

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

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 496ms 4

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

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 472ms 2

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

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 444ms 4

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

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 436ms 3

When I remove the mgr-sync cache file 672ms

And I execute mgr-sync refresh 1m 764ms

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

Feature:Synchronize products in the products page of the Setup Wizard 59m 23s 18ms 8 9

@scc_credentials

Scenario:
Refresh SCC

27s 790ms 1

When I refresh SCC 27s 790ms

@scc_credentials

Scenario:
Let the products page appear

2s 830ms 6

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

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

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

Then I should see a "Arch" text 122ms

And I should see a "Channels" text 124ms

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

@scc_credentials

Scenario:
Use the products and architecture filters

2s 374ms 7

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

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

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

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

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

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

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

1m 59s 483ms 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" 7s 765ms

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

And I use spacewalk-repo-sync to sync channel "opensuse_tumbleweed-x86_64" including only client tools dependencies 1m 32s 83ms

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

@containerized_server @proxy @uyuni

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

55s 53ms 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
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" 21s 703ms

And I wait until all synchronized channels for "uyuni-proxy" have finished 33s 350ms

@scc_credentials @uyuni @build_host

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

55m 11s 155ms 20

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
1 minutes out of 102 waiting for 'sles15-sp7' channels to finish 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
2 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
3 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
4 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
5 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
6 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
7 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
8 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
9 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
10 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
11 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-basesystem15-sp7-updates-x86_64 finished reposync
12 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
13 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
14 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
15 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-basesystem15-sp7-pool-x86_64 finished reposync
Channel sle-module-server-applications15-sp7-updates-x86_64 finished reposync
16 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-python3-15-sp7-updates-x86_64 finished reposync
Channel sle-module-server-applications15-sp7-pool-x86_64 finished reposync
17 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-python3-15-sp7-pool-x86_64 finished reposync
18 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-systems-management-15-sp7-pool-x86_64 finished reposync
Channel sle-module-systems-management-15-sp7-updates-x86_64 finished reposync
19 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
20 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
21 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
22 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
23 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
24 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-desktop-applications15-sp7-pool-x86_64 finished reposync
Channel sle-module-desktop-applications15-sp7-updates-x86_64 finished reposync
25 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
26 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-devtools15-sp7-pool-x86_64 finished reposync
27 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
28 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
29 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
30 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
31 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
32 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
33 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
34 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
35 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
36 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
37 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
38 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
39 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-devtools15-sp7-updates-x86_64 finished reposync
All channels for sles15-sp7 have been fully synced

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

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

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

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

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

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

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

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

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

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 24ms

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

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 23ms

When I click the Add Product button 58ms

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

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

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

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

And I wait until all synchronized channels for "sles15-sp7" have finished 54m 48s 978ms

@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

44s 329ms 7

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

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

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

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

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

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

And I should only see success signs in the product list 40s 33ms

@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 25s 273ms 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

475ms 1

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

Scenario:
Add a fake base channel for x86_64

1s 747ms 10

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

And I follow "Create Channel" 315ms

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

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

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

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

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

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

And I click on "Create Channel" 588ms

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

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

1s 606ms 10

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

And I follow "Create Channel" 309ms

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

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

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

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

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

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

And I click on "Create Channel" 575ms

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

@sle_minion

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

1s 526ms 10

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

And I follow "Create Channel" 322ms

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

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

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

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

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

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

And I click on "Create Channel" 526ms

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

Scenario:
Add a fake base channel for i586

1s 535ms 10

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

And I follow "Create Channel" 317ms

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

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

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

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

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

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

And I click on "Create Channel" 536ms

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

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

1s 535ms 10

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

And I follow "Create Channel" 329ms

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" 63ms

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

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

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

And I click on "Create Channel" 527ms

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

Scenario:
Add a test base channel for x86_64

1s 493ms 10

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

And I follow "Create Channel" 327ms

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

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

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

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

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" 114ms

And I click on "Create Channel" 55ms

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

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

1s 616ms 10

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

And I follow "Create Channel" 364ms

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

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

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

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

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

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

And I click on "Create Channel" 531ms

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

@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

11s 99ms 11

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

And I follow "Create Channel" 256ms

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

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

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" 127ms

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

And I uncheck "gpg_check" 10s 73ms

And I click on "Create Channel" 63ms

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

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 80ms 10

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

And I follow "Create Channel" 342ms

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

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

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

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

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

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

And I click on "Create Channel" 56ms

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

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 556ms 10

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

And I follow "Create Channel" 338ms

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

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

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

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

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

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

And I click on "Create Channel" 522ms

Then I should see a "Channel Fake-Base-Channel-AppStream created." text 76ms

Feature:Create fake repositories for each fake child channel 51s 474ms 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

493ms 1

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

Scenario:
Create a fake repository for distributions using RPM

1s 177ms 7

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

And I follow "Create Repository" 304ms

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

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

And I click on "Create Repository" 474ms

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

And I should see "metadataSigned" as checked 18ms

Scenario:
Disable metadata check for the fake RPM repository

10s 984ms 6

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

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

And I uncheck "metadataSigned" 10s 61ms

And I click on "Update Repository" 452ms

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

650ms 7

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

And I follow "Create Repository" 300ms

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

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

And I click on "Create Repository" 53ms

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

And I should see "metadataSigned" as checked 15ms

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

11s 7ms 6

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

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

And I uncheck "metadataSigned" 10s 72ms

And I click on "Update Repository" 472ms

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

And I should see "metadataSigned" as unchecked 15ms

@sle_minion

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

2s 75ms 9

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

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

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

And I click on "Update Channel" 572ms

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

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

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

And I click on "Save Repositories" 595ms

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

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

2s 630ms 9

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

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

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

And I click on "Update Channel" 615ms

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

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

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

And I click on "Save Repositories" 985ms

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

@rhlike_minion

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

2s 566ms 9

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

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

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

And I click on "Update Channel" 559ms

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 52ms

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

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

@rhlike_minion

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

2s 663ms 9

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

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

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

And I click on "Update Channel" 553ms

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

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

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

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

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

Scenario:
Create a fake repository for i586

11s 132ms 7

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

And I follow "Create Repository" 318ms

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

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

And I uncheck "metadataSigned" 10s 68ms

And I click on "Create Repository" 454ms

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

Scenario:
Add the repository to the i586 channel

1s 905ms 9

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

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

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

And I click on "Update Channel" 506ms

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

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

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

And I click on "Save Repositories" 517ms

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

@sle_minion

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

1s 680ms 6

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

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

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

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

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

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

@deblike_minion

Scenario:
Create a fake repository for Debian-like

1s 115ms 7

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

And I follow "Create Repository" 322ms

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

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

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

And I click on "Create Repository" 52ms

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

@deblike_minion

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

1s 390ms 6

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

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

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

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

And I click on "Save Repositories" 741ms

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

@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 30s 169ms 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

560ms 1

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

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 816ms 10

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

And I follow "Create Channel" 374ms

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" 58ms

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

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

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

And I click on "Create Channel" 616ms

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

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

6s 188ms 1

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

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 586ms 10

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

And I follow "Create Channel" 272ms

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

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

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

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

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

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

And I click on "Create Channel" 603ms

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

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

4s 375ms 1

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

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

1s 528ms 10

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

And I follow "Create Channel" 264ms

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

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

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

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

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

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

And I click on "Create Channel" 531ms

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

@deblike_minion

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

7s 699ms 1

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

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 537ms 10

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

And I follow "Create Channel" 269ms

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

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

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

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

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

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

And I click on "Create Channel" 557ms

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

@rhlike_minion

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

4s 876ms 1

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

Feature:Synchronize fake channels 1m 17s 55ms 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

1s 922ms 2

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

And I enable source package syncing 1s 487ms

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

3s 798ms 9

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

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

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

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

And I follow "Sync" 339ms

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 819ms

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

And I wait until the channel "fake-rpm-suse-channel" has been synced 421ms

@sle_minion

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

4s 788ms 2

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

And solver file for "fake-rpm-suse-channel" should reference "orion-dummy-1.1-1.1.x86_64.rpm" 651ms

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

3s 595ms 9

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

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

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

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

And I follow "Sync" 332ms

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 736ms

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

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

Scenario:
Synchronize Test-Child-Channel-x86_64 channel

4s 223ms 9

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

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

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

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

And I follow "Sync" 874ms

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 815ms

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

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

@sle_minion

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

35s 127ms 9

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

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

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

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

And I follow "Sync" 702ms

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

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

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

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

@deblike_minion

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

3s 736ms 9

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

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

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

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

And I follow "Sync" 350ms

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 808ms

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

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

@rhlike_minion

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

4s 210ms 9

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

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

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

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

And I follow "Sync" 967ms

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 736ms

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

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

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 189ms 9

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

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

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

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

And I follow "Sync" 796ms

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 813ms

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

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

@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

6s 496ms 6

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

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

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

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

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

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

Scenario:
Refresh the channel's repository data

3s 942ms 6

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

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

And I follow "channel-repodata-bunch" 278ms

And I click on "Single Run Schedule" 329ms

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 976ms

Scenario:
Cleanup disable source package syncing

1s 23ms 1

Then I disable source package syncing 1s 23ms

@skip_if_github_validation
Feature:Synchronize development channels 16s 734ms 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 901ms 9

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

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

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

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

And I follow "Sync" 520ms

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 850ms

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

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

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

4s 165ms 9

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

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

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

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

And I follow "Sync" 771ms

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

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

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

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

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 277ms 9

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

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

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

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

And I follow "Sync" 951ms

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 762ms

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

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

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

4s 389ms 9

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

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

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

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

And I follow "Sync" 887ms

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

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

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 506ms

Feature:Create activation keys 18s 720ms 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

493ms 1

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

@sle_minion

Scenario:
Create an activation key with a channel

2s 33ms 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 507ms

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

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

2s 958ms 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" 1s 959ms

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

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

2s 118ms 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" 1s 157ms

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

@ssh_minion

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

1s 894ms 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" 831ms

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

@ssh_minion

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

2s 486ms 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" 1s 230ms

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

@proxy

Scenario:
Create an activation key for the proxy

1s 944ms 2

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

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

@build_host

Scenario:
Create an activation key for the build host

2s 625ms 3

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

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

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

@scc_credentials

Scenario:
Create an activation key for the terminal

2s 166ms 2

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

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

Feature:Update activation keys 23s 793ms 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

474ms 1

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

@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 523ms 10

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 633ms

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

@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

2s 373ms 10

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 665ms

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

@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 127ms 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 69ms

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

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

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

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

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

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

And I click on "Update Activation Key" 582ms

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

@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 466ms 20

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

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

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

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

And I wait for child channels to appear 535ms

And I include the recommended child channels 229ms

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 18ms

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

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

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 18ms

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

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" 565ms

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

@scc_credentials @uyuni @build_host

Scenario:
Update build host key with Uyuni client tools

2s 159ms 9

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

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

And I wait for child channels to appear 940ms

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

And I wait for child channels to appear 311ms

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

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

And I click on "Update Activation Key" 590ms

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

@skip_if_github_validation @scc_credentials @uyuni @build_host

Scenario:
Update build host key with dev child channel

2s 151ms 9

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

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

And I wait for child channels to appear 925ms

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

And I wait for child channels to appear 311ms

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

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

And I click on "Update Activation Key" 605ms

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 129ms 16

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

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

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

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

And I wait for child channels to appear 444ms

And I include the recommended child channels 171ms

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

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

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

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" 70ms

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" 587ms

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

@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 837ms 6

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

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

And I wait for child channels to appear 984ms

And I check "Devel-SUSE-Channel" 97ms

And I click on "Update Activation Key" 551ms

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

@skip_if_github_validation @deblike_minion

Scenario:
Update Debian-like key with to include dev child channel

1s 776ms 6

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

And I follow "Debian-like Test Key" in the content area 67ms

And I wait for child channels to appear 906ms

And I check "Devel-Debian-like-Channel" 96ms

And I click on "Update Activation Key" 576ms

Then I should see a "Activation key Debian-like Test Key has been modified" text 71ms

@skip_if_github_validation @rhlike_minion

Scenario:
Update RedHat-like key with to include dev child channel

1s 771ms 6

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

And I follow "RedHat like Test Key" in the content area 66ms

And I wait for child channels to appear 896ms

And I check "Devel-RH-like-Channel" 95ms

And I click on "Update Activation Key" 584ms

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

Feature:Create bootstrap repositories 8s 777ms 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 250ms 1

When I create the bootstrap repositories including custom channels 2s 250ms

@sle_minion

Scenario:
Create the bootstrap repository for SUSE Minion

2s 42ms 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 42ms

@proxy

Scenario:
Create the bootstrap repository for Proxy

2s 29ms 1

When I create the bootstrap repository for "proxy" on the server 2s 29ms

@build_host

Scenario:
Create the bootstrap repository for Build Host

2s 455ms 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 455ms

@containerized_server @scope_containerized_proxy @proxy
Feature:Setup containerized proxy 3m 27s 444ms 10 2

In order to use a containerized proxy with the server
As the system administrator
I want to register the containerized proxy on the server

Scenario:
Clean up sumaform leftovers on proxy

6s 465ms 1

When I perform a full salt minion cleanup on "proxy" 6s 465ms

@transactional_server

Scenario:
Reboot after clean up

< 1ms 1

When I reboot the "proxy" host through SSH, waiting until it comes back 0s

Scenario:
Log in as admin user

37s 509ms 1

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

Scenario:
Bootstrap the proxy host as a salt minion

35s 788ms 9

The hostname of proxy is uyuni-master-proxy.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 136ms

Then I should see a "Bootstrap Minions" text 77ms

When I enter the hostname of "proxy" as "hostname" 116ms

And I enter "22" as "port" 49ms

And I enter "root" as "user" 53ms

And I enter "linux" as "password" 52ms

And I select "1-PROXY-KEY-x86_64" from "activationKeys" 72ms

And I click on "Bootstrap" 59ms

And I wait until I see "Bootstrap process initiated." text 35s 170ms

@skip_if_cloud @transactional_server

Scenario:
Reboot the proxy host

< 1ms 1

When I reboot the "proxy" host through SSH, waiting until it comes back 0s

Scenario:
Wait until the proxy host appears

1m 22s 858ms 1

When I wait until onboarding is completed for "proxy" 1m 22s 858ms

Scenario:
Generate containerized proxy configuration

11s 898ms 2

When I generate the configuration "/tmp/proxy_container_config.tar.gz" of containerized proxy on the server 9s 60ms

And I copy the configuration "/tmp/proxy_container_config.tar.gz" of containerized proxy from the server to the proxy 2s 838ms

Scenario:
Set up the containerized proxy service to support Avahi

< 1ms 1

Record not added - avahi domain was not detected

When I add avahi hosts in containerized proxy configuration < 1ms

Scenario:
Run a containerized proxy

17s 409ms 1

When I run "mgrpxy install podman /tmp/proxy_container_config.tar.gz" on "proxy" 17s 409ms

Scenario:
Wait until containerized proxy service is active

3s 920ms 10

And I wait until "uyuni-proxy-pod" service is active on "proxy" 562ms

And I wait until "uyuni-proxy-httpd" service is active on "proxy" 529ms

And I wait until "uyuni-proxy-salt-broker" service is active on "proxy" 560ms

And I wait until "uyuni-proxy-squid" service is active on "proxy" 383ms

And I wait until "uyuni-proxy-ssh" service is active on "proxy" 344ms

And I wait until "uyuni-proxy-tftpd" service is active on "proxy" 276ms

And I wait until port "8022" is listening on "proxy" container 300ms

And I wait until port "80" is listening on "proxy" container 296ms

And I wait until port "443" is listening on "proxy" container 297ms

And I visit "Proxy" endpoint of this "proxy" 369ms

Scenario:
The containerized proxy should be registered automatically

650ms 2

When I follow the left menu "Systems" 59ms

And I wait until I see the name of "proxy", refreshing the page 591ms

Scenario:
Check if Monitoring can be enabled on the containerized proxy

10s 943ms 3

Given I am on the Systems overview page of this "proxy" 870ms

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

Then the "monitoring_entitled" checkbox should be disabled 10s 4ms

@containerized_server @scope_containerized_proxy @proxy @private_net
Feature:Prepare the containerized branch server for PXE booting < 1ms 3

In order to use a containerized proxy as a Retail Branch server
As the system administrator
I make sure the network setup is as expected

Scenario:
Adapt the proxy for Retail

< 1ms 3

When I rename the proxy for Retail 0s

And I connect the second interface of the proxy to the private network 0s

And I restart all proxy containers 0s

Scenario:
Check the branch network

< 1ms 2

Then the "dhcp_dns" host should be present on private network 0s

And name resolution should work on private network 0s

Scenario:
Let the server know about the new IP and FQDN of the containerized proxy

< 1ms 11

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

When I am on the Systems overview page of this "proxy" 0s

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

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

And I click on "Schedule Hardware Refresh" 0s

Then I should see a "You have successfully scheduled a hardware profile refresh" text 0s

When I wait until event "Hardware List Refresh scheduled by admin" is completed 0s

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "proxy" 0s

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

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

Then I should see a "proxy.example.org" text 0s

@deblike_minion
Feature:Bootstrap a Debian-like minion and do some basic operations on it 4m 19s 548ms 7

Scenario:
Log in as admin user

38s 732ms 1

Given I am authorized for the "Admin" section 38s 732ms

Scenario:
Bootstrap a Debian-like minion

2m 24s 101ms 14

The hostname of deblike_minion is uyuni-master-deblike-minion.sumaci.aws
* 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
* Drop dependency on saltbundlepy-apt
- 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 follow the left menu "Systems > Bootstrapping" 153ms

Then I should see a "Bootstrap Minions" text 92ms

When I enter the hostname of "deblike_minion" as "hostname" 7s 6ms

And I enter "22" as "port" 66ms

And I enter "root" as "user" 86ms

And I enter "linux" as "password" 76ms

And I select "1-DEBLIKE-KEY" from "activationKeys" 106ms

And I select the hostname of "proxy" from "proxies" if present 2s 767ms

And I click on "Bootstrap" 79ms

And I wait until I see "Bootstrap process initiated." text 46s 36ms

And I follow the left menu "Systems > System List > All" 184ms

And I wait until I see the name of "deblike_minion", refreshing the page 44s 743ms

And I wait until onboarding is completed for "deblike_minion" 41s 322ms

And I query latest Salt changes on Debian-like system "deblike_minion" 1s 380ms

@proxy

Scenario:
Check connection from the Debian-like minion to proxy

1s 631ms 4

Given I am on the Systems overview page of this "deblike_minion" 1s 353ms

When I follow "Details" in the content area 101ms

And I follow "Connection" in the content area 89ms

Then I should see "proxy" short hostname 85ms

@proxy

Scenario:
Check registration on proxy of the Debian-like minion

1s 178ms 4

Given I am on the Systems overview page of this "proxy" 835ms

When I follow "Details" in the content area 89ms

And I follow "Proxy" in the content area 119ms

Then I should see "deblike_minion" hostname 134ms

Scenario:
Subscribe the Debian-like minion to a base channel

21s 691ms 11

Warning: Radio button 'Fake-Base-Channel-Debian-like' is already checked

Given I am on the Systems overview page of this "deblike_minion" 1s 132ms

When I follow "Software" in the content area 116ms

And I follow "Software Channels" in the content area 94ms

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

And I check radio button "Fake-Base-Channel-Debian-like" 196ms

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

And I click on "Next" 83ms

Then I should see a "Confirm Software Channel Change" text 86ms

When I click on "Confirm" 73ms

Then I should see a "Changing the channels has been scheduled." text 305ms

And I wait until event "Subscribe channels scheduled by admin" is completed 19s 90ms

Scenario:
Detect latest Salt changes on the Debian-like minion

470ms 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
* Drop dependency on saltbundlepy-apt
- 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 Debian-like system "deblike_minion" 470ms

Scenario:
Check events history for failures on Debian-like minion

51s 743ms 2

Given I am on the Systems overview page of this "deblike_minion" 819ms

Then I check for failed events on history event page 50s 923ms

@rhlike_minion
Feature:Bootstrap a Red Hat-like minion and do some basic operations on it 4m 10s 294ms 7

Scenario:
Log in as admin user

37s 883ms 1

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

Scenario:
Bootstrap a Red Hat-like minion

2m 16s 32ms 13

The hostname of rhlike_minion is uyuni-master-rhlike-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 140ms

Then I should see a "Bootstrap Minions" text 78ms

When I enter the hostname of "rhlike_minion" as "hostname" 2s 251ms

And I enter "22" as "port" 58ms

And I enter "root" as "user" 60ms

And I enter "linux" as "password" 58ms

And I select "1-RH-LIKE-KEY" from "activationKeys" 82ms

And I select the hostname of "proxy" from "proxies" if present 2s 773ms

And I click on "Bootstrap" 66ms

And I wait until I see "Bootstrap process initiated." text 40s 997ms

And I follow the left menu "Systems > System List > All" 223ms

And I wait until I see the name of "rhlike_minion", refreshing the page 58s 286ms

And I wait until onboarding is completed for "rhlike_minion" 30s 954ms

@proxy

Scenario:
Check connection from Red Hat-like minion to proxy

1s 198ms 4

Given I am on the Systems overview page of this "rhlike_minion" 940ms

When I follow "Details" in the content area 94ms

And I follow "Connection" in the content area 78ms

Then I should see "proxy" short hostname 85ms

@proxy

Scenario:
Check registration on proxy of Red Hat-like minion

1s 368ms 4

Given I am on the Systems overview page of this "proxy" 1s 65ms

When I follow "Details" in the content area 76ms

And I follow "Proxy" in the content area 89ms

Then I should see "rhlike_minion" hostname 136ms

Scenario:
Subscribe the Red Hat-like minion to a base channel

21s 694ms 11

Warning: Radio button 'Fake-Base-Channel-RH-like' is already checked

Given I am on the Systems overview page of this "rhlike_minion" 1s 78ms

When I follow "Software" in the content area 100ms

And I follow "Software Channels" in the content area 86ms

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

And I check radio button "Fake-Base-Channel-RH-like" 194ms

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

And I click on "Next" 83ms

Then I should see a "Confirm Software Channel Change" text 66ms

When I click on "Confirm" 79ms

Then I should see a "Changing the channels has been scheduled." text 321ms

And I wait until event "Subscribe channels scheduled by admin" is completed 19s 152ms

Scenario:
Detect latest Salt changes on the Red Hat-like minion

378ms 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
* Drop dependency on saltbundlepy-apt
- 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

When I query latest Salt changes on "rhlike_minion" 378ms

Scenario:
Check events history for failures on Red Hat-like minion

51s 738ms 2

Given I am on the Systems overview page of this "rhlike_minion" 845ms

Then I check for failed events on history event page 50s 892ms

@build_host
Feature:Bootstrap a build host via the GUI 1m 19s 755ms 1 8

Scenario:
Clean up sumaform leftovers on build host

9s 255ms 1

When I perform a full salt minion cleanup on "build_host" 9s 255ms

Scenario:
Log in as admin user

21s 772ms 1

Given I am authorized for the "Admin" section 21s 772ms Show Error +

                                            
 session not created: Chrome instance exited. Examine ChromeDriver verbose log to determine the cause. (Selenium::WebDriver::Error::SessionNotCreatedError)
(internal:kernel):90:in `tap'
./features/step_definitions/navigation_steps.rb:592:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:460:in `/^I am authorized for the "([^"]*)" section$/'
features/init_clients/buildhost_bootstrap.feature:11:in `I am authorized for the "Admin" section'

Scenario:
Bootstrap a build host

43s 70ms 9 1

When I follow the left menu "Systems > Bootstrapping" 43s 70ms Show Error +

                                            
 session not created: Chrome instance exited. Examine ChromeDriver verbose log to determine the cause. (Selenium::WebDriver::Error::SessionNotCreatedError)
(internal:kernel):90:in `tap'
./features/step_definitions/navigation_steps.rb:414:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:406:in `each'
./features/step_definitions/navigation_steps.rb:406:in `each_with_index'
./features/step_definitions/navigation_steps.rb:406:in `/^I follow the left menu "([^"]*)"$/'
features/init_clients/buildhost_bootstrap.feature:14:in `I follow the left menu "Systems ) Bootstrapping"'

Then I should see a "Bootstrap Minions" text 0s

When I enter the hostname of "build_host" as "hostname" 0s

And I enter "22" as "port" 0s

And I enter "root" as "user" 0s

And I enter "linux" as "password" 0s

And I select "1-BUILD-HOST-KEY-x86_64" from "activationKeys" 0s

And I select the hostname of "proxy" from "proxies" if present 0s

And I click on "Bootstrap" 0s

And I wait until I see "Bootstrap process initiated." text 0s

Scenario:
Check the new bootstrapped build host in System Overview page

475ms 5 1

When I follow the left menu "Salt > Keys" 475ms Show Error +

                                            
 session not created: Chrome instance exited. Examine ChromeDriver verbose log to determine the cause. (Selenium::WebDriver::Error::SessionNotCreatedError)
(internal:kernel):90:in `tap'
./features/step_definitions/navigation_steps.rb:414:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:406:in `each'
./features/step_definitions/navigation_steps.rb:406:in `each_with_index'
./features/step_definitions/navigation_steps.rb:406:in `/^I follow the left menu "([^"]*)"$/'
features/init_clients/buildhost_bootstrap.feature:26:in `I follow the left menu "Salt ) Keys"'

Then I should see a "accepted" text 0s

When I follow the left menu "Systems > System List > All" 0s

And I wait at most 500 seconds until I see the name of "build_host", refreshing the page 0s

And I wait at most 500 seconds until onboarding is completed for "build_host" 0s

Then the Salt master can reach "build_host" 0s

@proxy

Scenario:
Check connection from build host to proxy

317ms 3 1

Given I am on the Systems overview page of this "build_host" 317ms Show Error +

                                            
 No system found for hostname: uyuni-master-build-host.sumaci.aws (RuntimeError)
./features/support/commonlib.rb:421:in `get_system_id'
./features/step_definitions/navigation_steps.rb:473:in `/^I am on the Systems overview page of this "([^"]*)"$/'
features/init_clients/buildhost_bootstrap.feature:36:in `I am on the Systems overview page of this "build_host"'

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

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

Then I should see "proxy" short hostname 0s

@proxy

Scenario:
Check registration on build host of minion

3s 686ms 3 1

Given I am on the Systems overview page of this "proxy" 3s 686ms Show Error +

                                            
 session not created: Chrome instance exited. Examine ChromeDriver verbose log to determine the cause. (Selenium::WebDriver::Error::SessionNotCreatedError)
(internal:kernel):90:in `tap'
./features/step_definitions/navigation_steps.rb:475:in `/^I am on the Systems overview page of this "([^"]*)"$/'
features/init_clients/buildhost_bootstrap.feature:43:in `I am on the Systems overview page of this "proxy"'

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

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

Then I should see "build_host" hostname 0s

Scenario:
Detect latest Salt changes on the SLES build host

562ms 1

When I query latest Salt changes on "build_host" 562ms Show Error +

                                            
 FAIL: LANG=en_US.UTF-8 rpm -q --changelog venv-salt-minion returned status code = 1.
Output:
package venv-salt-minion is not installed
 (ScriptError)
./features/support/remote_node.rb:169:in `run_local'
./features/support/remote_node.rb:117:in `run'
./features/step_definitions/command_steps.rb:246:in `/^I query latest Salt changes on "(.*?)"$/'
features/init_clients/buildhost_bootstrap.feature:49:in `I query latest Salt changes on "build_host"'

Scenario:
Check that the build host is a build host

313ms 2 1

Given I am on the Systems overview page of this "build_host" 313ms Show Error +

                                            
 No system found for hostname: uyuni-master-build-host.sumaci.aws (RuntimeError)
./features/support/commonlib.rb:421:in `get_system_id'
./features/step_definitions/navigation_steps.rb:473:in `/^I am on the Systems overview page of this "([^"]*)"$/'
features/init_clients/buildhost_bootstrap.feature:52:in `I am on the Systems overview page of this "build_host"'

Then I should see a "[Container Build Host]" text 0s

Then I should see a "[OS Image Build Host]" text 0s

Scenario:
Check events history for failures on SLES build host

301ms 1 1

Given I am on the Systems overview page of this "build_host" 301ms Show Error +

                                            
 No system found for hostname: uyuni-master-build-host.sumaci.aws (RuntimeError)
./features/support/commonlib.rb:421:in `get_system_id'
./features/step_definitions/navigation_steps.rb:473:in `/^I am on the Systems overview page of this "([^"]*)"$/'
features/init_clients/buildhost_bootstrap.feature:57:in `I am on the Systems overview page of this "build_host"'

Then I check for failed events on history event page 0s

@sle_minion
Feature:Bootstrap a Salt minion via the GUI 1m 53s 400ms 1 5 2

Scenario:
Clean up sumaform leftovers on SLES minion

9s 409ms 1

When I perform a full salt minion cleanup on "sle_minion" 9s 409ms

Scenario:
Log in as admin user

41s 870ms 1

Given I am authorized for the "Admin" section 41s 870ms Show Error +

                                            
 session not created: Chrome instance exited. Examine ChromeDriver verbose log to determine the cause. (Selenium::WebDriver::Error::SessionNotCreatedError)
(internal:kernel):90:in `tap'
./features/step_definitions/navigation_steps.rb:592:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:460:in `/^I am authorized for the "([^"]*)" section$/'
features/init_clients/sle_minion.feature:11:in `I am authorized for the "Admin" section'

Scenario:
Bootstrap a SLES minion

23s 518ms 10 1

When I follow the left menu "Systems > Bootstrapping" 23s 518ms Show Error +

                                            
 Unable to find xpath "//aside/div[@id='nav']/nav/ul/li/div/a[contains(.,'Systems')]/parent::div/parent::li" (Capybara::ElementNotFound)
./features/step_definitions/navigation_steps.rb:414:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:406:in `each'
./features/step_definitions/navigation_steps.rb:406:in `each_with_index'
./features/step_definitions/navigation_steps.rb:406:in `/^I follow the left menu "([^"]*)"$/'
features/init_clients/sle_minion.feature:14:in `I follow the left menu "Systems ) Bootstrapping"'

Then I should see a "Bootstrap Minions" text 0s

When I enter the hostname of "sle_minion" as "hostname" 0s

And I enter "22" as "port" 0s

And I enter "root" as "user" 0s

And I enter "linux" as "password" 0s

And I select "1-SUSE-KEY-x86_64" from "activationKeys" 0s

And I select the hostname of "proxy" from "proxies" if present 0s

And I click on "Bootstrap" 0s

And I wait until I see "Bootstrap process initiated." text 0s

And I report the bootstrap duration for "sle_minion" 0s

Scenario:
Check the new bootstrapped minion in System List page

10s 11ms 7 1

When I follow the left menu "Salt > Keys" 10s 11ms Show Error +

                                            
 Unable to find xpath "//aside/div[@id='nav']/nav/ul/li/div/a[contains(.,'Salt')]/parent::div/parent::li" (Capybara::ElementNotFound)
./features/step_definitions/navigation_steps.rb:414:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:406:in `each'
./features/step_definitions/navigation_steps.rb:406:in `each_with_index'
./features/step_definitions/navigation_steps.rb:406:in `/^I follow the left menu "([^"]*)"$/'
features/init_clients/sle_minion.feature:27:in `I follow the left menu "Salt ) Keys"'

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

Then I should see a "accepted" text 0s

When I follow the left menu "Systems > System List > All" 0s

And I wait until I see the name of "sle_minion", refreshing the page 0s

And I wait until onboarding is completed for "sle_minion" 0s

Then the Salt master can reach "sle_minion" 0s

And I report the onboarding duration for "sle_minion" 0s

@susemanager

Scenario:
Use correct kernel image on the SLES minion

< 1ms 2

When I remove package "kernel-default-base" from this "sle_minion" 0s

And I install package "kernel-default" on this "sle_minion" 0s

@susemanager

Scenario:
Reboot the SLES minion to use the new kernel

< 1ms 1

When I reboot the "sle_minion" host through SSH, waiting until it comes back 0s

@proxy

Scenario:
Check connection from minion to proxy

456ms 3 1

Given I am on the Systems overview page of this "sle_minion" 456ms Show Error +

                                            
 No system found for hostname: uyuni-master-suse-minion.sumaci.aws (RuntimeError)
./features/support/commonlib.rb:421:in `get_system_id'
./features/step_definitions/navigation_steps.rb:473:in `/^I am on the Systems overview page of this "([^"]*)"$/'
features/init_clients/sle_minion.feature:47:in `I am on the Systems overview page of this "sle_minion"'

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

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

Then I should see "proxy" short hostname 0s

@proxy

Scenario:
Check registration on proxy of minion

28s 135ms 2 2 1

Requested /rhn/systems/details/Overview.do?sid=1000010000, got https://uyuni-master-server.sumaci.aws/rhn/manager/login?url_bounce=%2Frhn%2Fsystems%2Fdetails%2FOverview.do%3Fsid%3D1000010000&request_method=GET

Given I am on the Systems overview page of this "proxy" 4s 84ms

When I follow "Details" in the content area 10s 19ms Show Error +

                                            
 Unable to find link "Details" within #(Capybara::Node::Element tag="section" path="/HTML/BODY[1]/DIV[1]/DIV[1]/SECTION[1]") (Capybara::ElementNotFound)
./features/support/commonlib.rb:198:in `click_link_and_wait'
./features/step_definitions/navigation_steps.rb:339:in `/^I follow "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:361:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:360:in `/^I follow "([^"]*)" in the (.+)$/'
features/init_clients/sle_minion.feature:55:in `I follow "Details" in the content area'

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

Then I should see "sle_minion" hostname 0s

14s 31ms Show Info +

11:48:13:000 - 11:48:28:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/login?url_bounce=%2Frhn%2Fsystems%2Fdetails%2FOverview.do%3Fsid%3D1000010000&request_method=GET

Screenshot +

@ssh_minion
Feature:Bootstrap a Salt host managed via salt-ssh 3m 15s 27ms 5 2

Scenario:
Clean up sumaform leftovers on SLES SSH minion

10s 715ms 1

When I perform a full salt minion cleanup on "ssh_minion" 10s 715ms

Scenario:
Log in as admin user

37s 823ms 1

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

Scenario:
Bootstrap a SLES SSH minion

2m 23s 879ms 11

The hostname of ssh_minion is uyuni-master-suse-sshminion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 189ms

Then I should see a "Bootstrap Minions" text 100ms

When I check "manageWithSSH" 119ms

And I enter the hostname of "ssh_minion" as "hostname" 178ms

And I enter "linux" as "password" 70ms

And I select the hostname of "proxy" from "proxies" if present 2s 777ms

And I click on "Bootstrap" 92ms

And I wait until I see "Bootstrap process initiated." text 54s 676ms

And I follow the left menu "Systems > System List > All" 156ms

And I wait until I see the name of "ssh_minion", refreshing the page 30s 971ms

And I wait until onboarding is completed for "ssh_minion" 54s 547ms

@susemanager

Scenario:
Use correct kernel image on the SSH minion

< 1ms 2

When I remove package "kernel-default-base" from this "ssh_minion" 0s

And I install package "kernel-default" on this "ssh_minion" 0s

@susemanager

Scenario:
Reboot the SSH minion to use the new kernel

< 1ms 1

When I reboot the "ssh_minion" host through SSH, waiting until it comes back 0s

@proxy

Scenario:
Check connection from SSH minion to proxy

1s 415ms 4

Given I am on the Systems overview page of this "ssh_minion" 1s 140ms

When I follow "Details" in the content area 93ms

And I follow "Connection" in the content area 95ms

Then I should see "proxy" short hostname 85ms

@proxy

Scenario:
Check registration on proxy of SSH minion

1s 193ms 4

Given I am on the Systems overview page of this "proxy" 920ms

When I follow "Details" in the content area 84ms

And I follow "Proxy" in the content area 81ms

Then I should see "ssh_minion" hostname 107ms

@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 17s 751ms 5

Scenario:
Call spacewalk-debug on server

13s 784ms 1

When I execute spacewalk-debug on the server 13s 784ms

Scenario:
Check the tomcat logs on server

669ms 1

Then the tomcat logs should not contain errors 669ms

Scenario:
Check salt event log for failures on server

1s 912ms 1

Then the salt event log on server should contain no failures 1s 912ms

Scenario:
Check the taskomatic logs on server

725ms 1

Then the taskomatic logs should not contain errors 725ms

Scenario:
Check for out of memory errors

658ms 1

Then the log messages should not contain out of memory errors 658ms

Feature:Debug the clients after the testsuite has run 1m 32s 977ms 1

Scenario:
Extract the logs from all our clients

1m 32s 977ms 1

When I extract the log files from all our active nodes 1m 32s 977ms

@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

201

Passed Scenarios

149

Failed Scenarios

13

Skipped Scenarios

39

@proxy Scenario:The proxy is healthy 4s 381ms 4

@sle_minion Scenario:The minion is healthy 5s 946ms 4

@build_host Scenario:The build host is healthy 3s 948ms 4

@ssh_minion Scenario:The SSH minion is healthy 6s 423ms 4

@rhlike_minion Scenario:The Red Hat-like minion is healthy 3s 256ms 4

@deblike_minion Scenario:The Debian-like minion is healthy 6s 138ms 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 649ms 1

@no_auth_registry Scenario:The registry without authentication is healthy 657ms 1

@custom_download_endpoint Scenario:The custom download endpoint is working 633ms 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 169ms 7

@scc_credentials Feature:List available channels and enable them 1m 38s 854ms 5 1

@proxy @susemanager Scenario:List all products for SUSE Multi-Linux Manager < 1ms 6

@scc_credentials Scenario:Refresh SCC 27s 790ms 1

@scc_credentials Scenario:Let the products page appear 2s 830ms 6

@scc_credentials Scenario:Use the products and architecture filters 2s 374ms 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 1m 59s 483ms 4

@containerized_server @proxy @uyuni Scenario:Add Uyuni Proxy product for Tumbleweed, including Uyuni Client Tools 55s 53ms 2

@scc_credentials @uyuni @build_host Scenario:Synchronize SLES 15 SP7 product with recommended sub-products for Retail feature 55m 11s 155ms 20

@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 44s 329ms 7

@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 526ms 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 11s 99ms 11

@rhlike_minion Scenario:Add a RedHat-like base channel 1s 80ms 10

@rhlike_minion Scenario:Add a fake AppStream base channel 1s 556ms 10

@rhlike_minion Scenario:Create a fake AppStream repository 650ms 7

@rhlike_minion Scenario:Disable metadata check for the fake AppStream repository 11s 7ms 6

@sle_minion Scenario:Add the fake RPM repository to the SUSE fake child channel 2s 75ms 9

@rhlike_minion Scenario:Add the fake RPM repository to the RedHat-like base channel 2s 566ms 9

@rhlike_minion Scenario:Add the fake AppStream repository to the AppStream base channel 2s 663ms 9

@sle_minion Scenario:Add the repository to the SUSE-like child channel 1s 680ms 6

@deblike_minion Scenario:Create a fake repository for Debian-like 1s 115ms 7

@deblike_minion Scenario:Add the repository to the Debian-like base channel 1s 390ms 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 30s 169ms 9

@sle_minion Scenario:Create a custom channel for SUSE minions 1s 816ms 10

@sle_minion Scenario:Create custom repositories inside the SUSE custom channel 6s 188ms 1

@uyuni @build_host Scenario:Create a custom channel for Build Host 1s 586ms 10

@uyuni @build_host Scenario:Create custom repositories inside the Build Host custom channel 4s 375ms 1

@deblike_minion Scenario:Create a custom channel for Debian-like minions 1s 528ms 10

@deblike_minion Scenario:Create custom repositories inside the Debian-like custom channel 7s 699ms 1

@rhlike_minion Scenario:Create a custom channel for RH-like minions 1s 537ms 10

@rhlike_minion Scenario:Create custom repositories inside the RH-like custom channel 4s 876ms 1

@sle_minion Scenario:Synchronize Fake-RPM-SUSE-Channel channel 3s 798ms 9

@sle_minion Scenario:Verify state of Fake-RPM-SUSE-Channel channel 4s 788ms 2

@skip_if_github_validation Scenario:Synchronize Fake-Child-Channel-i586 channel 3s 595ms 9

@sle_minion Scenario:Synchronize Fake-Child-Channel-SUSE-like channel 35s 127ms 9

@deblike_minion Scenario:Synchronize Fake-Base-Channel-Debian-like channel 3s 736ms 9

@rhlike_minion Scenario:Synchronize Fake-Base-Channel-RH-like channel 4s 210ms 9

@rhlike_minion Scenario:Synchronize Fake-Base-Channel-AppStream channel 4s 189ms 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 734ms 4

@sle_minion Scenario:Synchronize Devel-SUSE-Channel channel 3s 901ms 9

@deblike_minion Scenario:Synchronize Devel-Debian-like-Channel channel 4s 165ms 9

@rhlike_minion Scenario:Synchronize Devel-RH-like-Channel channel 4s 277ms 9

@build_host @uyuni Scenario:Synchronize Devel-Build-Host-Channel channel 4s 389ms 9

@sle_minion Scenario:Create an activation key with a channel 2s 33ms 2

@proxy

Scenario:
The proxy is healthy

4s 381ms 4

@sle_minion

Scenario:
The minion is healthy

5s 946ms 4

@build_host

Scenario:
The build host is healthy

3s 948ms 4

@ssh_minion

Scenario:
The SSH minion is healthy

6s 423ms 4

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 256ms 4

@deblike_minion

Scenario:
The Debian-like minion is healthy

6s 138ms 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

649ms 1

@no_auth_registry

Scenario:
The registry without authentication is healthy

657ms 1

@custom_download_endpoint

Scenario:
The custom download endpoint is working

633ms 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 169ms 7

@scc_credentials
Feature:List available channels and enable them 1m 38s 854ms 5 1

@proxy @susemanager

Scenario:
List all products for SUSE Multi-Linux Manager

< 1ms 6

@scc_credentials

Scenario:
Refresh SCC

27s 790ms 1

@scc_credentials

Scenario:
Let the products page appear

2s 830ms 6

@scc_credentials

Scenario:
Use the products and architecture filters

2s 374ms 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

1m 59s 483ms 4

@containerized_server @proxy @uyuni

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

55s 53ms 2

@scc_credentials @uyuni @build_host

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

55m 11s 155ms 20

@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

44s 329ms 7

@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 526ms 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

11s 99ms 11

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 80ms 10

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 556ms 10

@rhlike_minion

Scenario:
Create a fake AppStream repository

650ms 7

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

11s 7ms 6

@sle_minion

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

2s 75ms 9

@rhlike_minion

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

2s 566ms 9

@rhlike_minion

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

2s 663ms 9

@sle_minion

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

1s 680ms 6

@deblike_minion

Scenario:
Create a fake repository for Debian-like

1s 115ms 7

@deblike_minion

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

1s 390ms 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 30s 169ms 9

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 816ms 10

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

6s 188ms 1

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 586ms 10

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

4s 375ms 1

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

1s 528ms 10

@deblike_minion

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

7s 699ms 1

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 537ms 10

@rhlike_minion

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

4s 876ms 1

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

3s 798ms 9

@sle_minion

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

4s 788ms 2

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

3s 595ms 9

@sle_minion

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

35s 127ms 9

@deblike_minion

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

3s 736ms 9

@rhlike_minion

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

4s 210ms 9

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 189ms 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 734ms 4

@sle_minion

Scenario:
Synchronize Devel-SUSE-Channel channel

3s 901ms 9

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

4s 165ms 9

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 277ms 9

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

4s 389ms 9

@sle_minion

Scenario:
Create an activation key with a channel

2s 33ms 2

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

2s 958ms 2

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

2s 118ms 2

@ssh_minion

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

1s 894ms 2

@ssh_minion

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

2s 486ms 2

@proxy

Scenario:
Create an activation key for the proxy

1s 944ms 2

@build_host

Scenario:
Create an activation key for the build host

2s 625ms 3

@scc_credentials

Scenario:
Create an activation key for the terminal

2s 166ms 2

@scc_credentials @susemanager

Scenario:
Update SLE key with synced base product

< 1ms 20