Cucumber Feature Report

All Scenarios

201

Passed Scenarios

146

Failed Scenarios

16

Skipped Scenarios

39

Execution Time: 84m 22s 536ms

Expand All | Collapse All

Metadata

App Version: Uyuni/Head

Browser: Chrome

Platform: x86_64

Parallel: Disabled

Feature:Sanity checks 43s 893ms 10 2

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

Scenario:
The server is healthy

11s 871ms 19

Then "server" should have a FQDN 383ms

And reverse resolution should work for "server" 630ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@proxy

Scenario:
The proxy is healthy

4s 588ms 4

Then "proxy" should have a FQDN 3s 53ms

And reverse resolution should work for "proxy" 288ms

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

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

@sle_minion

Scenario:
The minion is healthy

6s 259ms 4

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

And reverse resolution should work for "sle_minion" 414ms

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

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

@build_host

Scenario:
The build host is healthy

3s 626ms 4

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

And reverse resolution should work for "build_host" 217ms

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

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

@ssh_minion

Scenario:
The SSH minion is healthy

6s 378ms 4

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

And reverse resolution should work for "ssh_minion" 409ms

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

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

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 187ms 4

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

And reverse resolution should work for "rhlike_minion" 190ms

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

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

@deblike_minion

Scenario:
The Debian-like minion is healthy

6s 10ms 4

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

And reverse resolution should work for "deblike_minion" 220ms

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

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

@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

660ms 1

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

@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

652ms 1

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

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

666ms 1

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

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

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

Scenario:
Wait for refresh of list of products to finish

3s 770ms 1

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

Scenario:
Create testing username

2s 236ms 12

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

And I follow "Create User" 520ms

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

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

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

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

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

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

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

And I click on "Create Login" 950ms

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

And I should see a "testing" link 12ms

Scenario:
Grant testing user administrative priviledges

1s 890ms 10

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

And I follow "testing" 579ms

And I check "role_org_admin" 86ms

And I check "role_system_group_admin" 79ms

And I check "role_channel_admin" 81ms

And I check "role_activation_key_admin" 83ms

And I check "role_config_admin" 80ms

And I click on "Update" 668ms

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

And I should see a "testing" text 73ms

@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

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

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

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

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 884ms 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 374ms 5

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

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

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

And I click on "Save Preferences" 635ms

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

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

3s 510ms 5

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

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

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

And I click on "Save Preferences" 604ms

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

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

Scenario:
Create a Kiwi user with image administrators rights

4s 243ms 2

New user kiwikiwi created with roles: image_admin

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

When I create a user with name "kiwikiwi" and password "kiwikiwi" with roles "image_admin" 2s 194ms

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

Scenario:
Create a Docker user with image administrators rights

1s 996ms 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 550ms

@no_auth_registry

Scenario:
Create an image store without credentials

3s 67ms 7

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

And I follow "Create" 507ms

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

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

And I click on "create-btn" 65ms

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

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

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

Scenario:
Log in as admin user

37s 563ms 1

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

Scenario:
Disable scheduled reposyncs

4s 585ms 5

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

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

And I choose "disabled" 71ms

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

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

Scenario:
Disable scheduled Cobbler syncs

4s 534ms 5

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

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

And I choose "disabled" 50ms

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

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

@scc_credentials
Feature:List available channels and enable them 1m 38s 926ms 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 43ms 5

When I refresh SCC 30s 752ms

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

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

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

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

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

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

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

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

When I remove the mgr-sync cache file 643ms

And I execute mgr-sync refresh 1m 776ms

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

Feature:Synchronize products in the products page of the Setup Wizard 44m 17s 229ms 8 9

@scc_credentials

Scenario:
Refresh SCC

27s 634ms 1

When I refresh SCC 27s 634ms

@scc_credentials

Scenario:
Let the products page appear

2s 928ms 6

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

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

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

Then I should see a "Arch" text 124ms

And I should see a "Channels" text 125ms

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

@scc_credentials

Scenario:
Use the products and architecture filters

2s 643ms 7

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

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

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

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

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

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

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

@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 56s 372ms 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 666ms

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

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

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

@containerized_server @proxy @uyuni

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

45s 572ms 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-uyuni-client-devel-x86_64 finished reposync
Channel uyuni-proxy-devel-tumbleweed-x86_64 finished reposync
Channel opensuse_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 999ms

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

@scc_credentials @uyuni @build_host

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

40m 18s 226ms 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 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
Channel sles15-sp7-devel-uyuni-client-x86_64 finished reposync
1 minutes out of 102 waiting for 'sles15-sp7' channels to finish 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
Channel sle-module-basesystem15-sp7-pool-x86_64 finished 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
Channel sle-module-server-applications15-sp7-pool-x86_64 finished reposync
Channel sle-module-python3-15-sp7-updates-x86_64 finished reposync
Channel sle-module-server-applications15-sp7-updates-x86_64 finished reposync
13 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-python3-15-sp7-pool-x86_64 finished 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
14 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-desktop-applications15-sp7-updates-x86_64 finished reposync
15 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
16 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
17 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
18 minutes out of 102 waiting for 'sles15-sp7' channels to finish 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
Channel sle-module-desktop-applications15-sp7-pool-x86_64 finished reposync
Channel sle-module-devtools15-sp7-pool-x86_64 finished 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
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
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
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 461ms

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 59ms

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

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

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

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 39m 56s 953ms

@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

43s 852ms 7

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

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

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

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

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

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

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

@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 24s 701ms 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

486ms 1

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

Scenario:
Add a fake base channel for x86_64

1s 856ms 10

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

And I follow "Create Channel" 336ms

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

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

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

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

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

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

And I click on "Create Channel" 634ms

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

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

1s 129ms 10

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

And I follow "Create Channel" 316ms

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

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

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

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

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

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

And I click on "Create Channel" 59ms

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

@sle_minion

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

1s 615ms 10

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

And I follow "Create Channel" 321ms

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

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

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

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

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

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

And I click on "Create Channel" 574ms

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

Scenario:
Add a fake base channel for i586

1s 612ms 10

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

And I follow "Create Channel" 344ms

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

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

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

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

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

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

And I click on "Create Channel" 542ms

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

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

1s 576ms 10

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

And I follow "Create Channel" 330ms

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

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

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

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

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

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

And I click on "Create Channel" 517ms

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

Scenario:
Add a test base channel for x86_64

1s 106ms 10

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

And I follow "Create Channel" 339ms

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

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

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

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

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

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

And I click on "Create Channel" 59ms

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

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

1s 558ms 10

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

And I follow "Create Channel" 251ms

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

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

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

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

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

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

And I click on "Create Channel" 546ms

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 140ms 11

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

And I follow "Create Channel" 255ms

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

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

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

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

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

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

And I uncheck "gpg_check" 10s 81ms

And I click on "Create Channel" 60ms

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

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 533ms 10

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

And I follow "Create Channel" 270ms

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

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

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

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

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

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

And I click on "Create Channel" 546ms

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

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 85ms 10

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

And I follow "Create Channel" 285ms

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

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

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

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

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

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

And I click on "Create Channel" 62ms

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

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

510ms 1

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

Scenario:
Create a fake repository for distributions using RPM

821ms 7

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

And I follow "Create Repository" 318ms

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

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

And I click on "Create Repository" 65ms

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

And I should see "metadataSigned" as checked 21ms

Scenario:
Disable metadata check for the fake RPM repository

11s 34ms 6

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

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

And I uncheck "metadataSigned" 10s 65ms

And I click on "Update Repository" 462ms

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

And I should see "metadataSigned" as unchecked 19ms

@rhlike_minion

Scenario:
Create a fake AppStream repository

970ms 7

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

And I follow "Create Repository" 231ms

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

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

And I click on "Create Repository" 419ms

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

And I should see "metadataSigned" as checked 17ms

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

10s 939ms 6

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

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

And I uncheck "metadataSigned" 10s 80ms

And I click on "Update Repository" 453ms

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

And I should see "metadataSigned" as unchecked 16ms

@sle_minion

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

2s 146ms 9

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

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

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

And I click on "Update Channel" 622ms

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

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

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

And I click on "Save Repositories" 498ms

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

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

2s 534ms 9

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

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

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

And I click on "Update Channel" 543ms

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

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

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

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

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

@rhlike_minion

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

2s 798ms 9

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

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

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

And I click on "Update Channel" 570ms

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

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

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

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

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

@rhlike_minion

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

2s 554ms 9

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

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

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

And I click on "Update Channel" 554ms

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

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

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

And I click on "Save Repositories" 1s

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

Scenario:
Create a fake repository for i586

11s 66ms 7

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

And I follow "Create Repository" 239ms

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

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

And I uncheck "metadataSigned" 10s 80ms

And I click on "Create Repository" 439ms

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

Scenario:
Add the repository to the i586 channel

1s 952ms 9

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

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

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

And I click on "Update Channel" 511ms

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

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

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

And I click on "Save Repositories" 509ms

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

@sle_minion

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

1s 644ms 6

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

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

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

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

And I click on "Save Repositories" 1s

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

@deblike_minion

Scenario:
Create a fake repository for Debian-like

1s 123ms 7

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

And I follow "Create Repository" 329ms

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

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

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

And I click on "Create Repository" 421ms

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

@deblike_minion

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

1s 422ms 6

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

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

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

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

And I click on "Save Repositories" 783ms

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

@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 27s 610ms 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

475ms 1

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

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 240ms 10

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

And I follow "Create Channel" 274ms

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

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

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

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

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

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

And I click on "Create Channel" 68ms

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

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

6s 394ms 1

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

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 661ms 10

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

And I follow "Create Channel" 268ms

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

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

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

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

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

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

And I click on "Create Channel" 611ms

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

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

3s 644ms 1

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

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

1s 571ms 10

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

And I follow "Create Channel" 276ms

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

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

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

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

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

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

And I click on "Create Channel" 511ms

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

@deblike_minion

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

7s 106ms 1

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

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 101ms 10

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

And I follow "Create Channel" 276ms

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

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

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

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

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

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

And I click on "Create Channel" 62ms

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

@rhlike_minion

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

4s 414ms 1

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

Feature:Synchronize fake channels 1m 8s 149ms 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 765ms 2

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

And I enable source package syncing 1s 343ms

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

3s 831ms 9

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

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

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

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

And I follow "Sync" 358ms

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

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

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

@sle_minion

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

5s 30ms 2

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

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

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

3s 754ms 9

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

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

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

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

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

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

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

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

Scenario:
Synchronize Test-Child-Channel-x86_64 channel

4s 273ms 9

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

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

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

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

And I follow "Sync" 811ms

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

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

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

@sle_minion

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

24s 778ms 9

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

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

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

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

And I follow "Sync" 699ms

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

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

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

@deblike_minion

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

3s 715ms 9

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

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

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

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

And I follow "Sync" 348ms

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

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

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

@rhlike_minion

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

4s 180ms 9

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

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

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

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

And I follow "Sync" 791ms

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

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

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

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

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 201ms 9

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

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

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

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

And I follow "Sync" 809ms

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

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

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

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

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

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

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

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

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

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

Scenario:
Refresh the channel's repository data

4s 941ms 6

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

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

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

And I click on "Single Run Schedule" 311ms

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

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

Scenario:
Cleanup disable source package syncing

994ms 1

Then I disable source package syncing 994ms

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

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

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

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

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

And I follow "Sync" 524ms

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

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

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

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

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

4s 284ms 9

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

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

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

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

And I follow "Sync" 798ms

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

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

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

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 380ms 9

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

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

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

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

And I follow "Sync" 891ms

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

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

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

4s 174ms 9

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

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

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

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

And I follow "Sync" 706ms

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

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

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

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

515ms 1

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

@sle_minion

Scenario:
Create an activation key with a channel

2s 172ms 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 654ms

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

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

3s 763ms 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" 2s 425ms

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

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

1s 726ms 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" 935ms

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

@ssh_minion

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

1s 671ms 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" 800ms

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

@ssh_minion

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

1s 852ms 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" 871ms

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

@proxy

Scenario:
Create an activation key for the proxy

1s 958ms 2

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

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

@build_host

Scenario:
Create an activation key for the build host

2s 581ms 3

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

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

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

@scc_credentials

Scenario:
Create an activation key for the terminal

2s 253ms 2

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

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

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

496ms 1

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 657ms

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 613ms

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 572ms

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

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

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

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

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

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

And I wait for child channels to appear 548ms

And I include the recommended child channels 222ms

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

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

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 649ms

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

@scc_credentials @uyuni @build_host

Scenario:
Update build host key with Uyuni client tools

2s 212ms 9

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

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

And I wait for child channels to appear 962ms

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

And I wait for child channels to appear 313ms

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

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

And I click on "Update Activation Key" 598ms

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 246ms 9

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

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

And I wait for child channels to appear 953ms

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

And I wait for child channels to appear 328ms

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

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

And I click on "Update Activation Key" 621ms

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

@scc_credentials @build_host

Scenario:
Update terminal key with synced base product

3s 107ms 16

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

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

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

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

And I wait for child channels to appear 452ms

And I include the recommended child channels 170ms

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 597ms

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

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

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

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

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

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

And I click on "Update Activation Key" 566ms

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

@skip_if_github_validation @deblike_minion

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

1s 815ms 6

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

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

And I wait for child channels to appear 931ms

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

And I click on "Update Activation Key" 568ms

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

@skip_if_github_validation @rhlike_minion

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

1s 672ms 6

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

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

And I wait for child channels to appear 749ms

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

And I click on "Update Activation Key" 608ms

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

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

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

@sle_minion

Scenario:
Create the bootstrap repository for SUSE Minion

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

@proxy

Scenario:
Create the bootstrap repository for Proxy

2s 37ms 1

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

@build_host

Scenario:
Create the bootstrap repository for Build Host

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

@containerized_server @scope_containerized_proxy @proxy
Feature:Setup containerized proxy 3m 30s 622ms 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 708ms 1

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

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

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

Scenario:
Bootstrap the proxy host as a salt minion

35s 989ms 9

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 70ms

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

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

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

Scenario:
Generate containerized proxy configuration

11s 650ms 2

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

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

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

18s 567ms 1

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

Scenario:
Wait until containerized proxy service is active

5s 972ms 10

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

And I wait until "uyuni-proxy-httpd" service is active on "proxy" 2s 851ms

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

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

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

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

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

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

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

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

Scenario:
The containerized proxy should be registered automatically

761ms 2

When I follow the left menu "Systems" 63ms

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

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

10s 954ms 3

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

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

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

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

Scenario:
Log in as admin user

37s 786ms 1

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

Scenario:
Bootstrap a Debian-like minion

2m 13s 722ms 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" 178ms

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

When I enter the hostname of "deblike_minion" as "hostname" 4s 829ms

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

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

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

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

And I select the hostname of "proxy" from "proxies" if present 3s 90ms

And I click on "Bootstrap" 104ms

And I wait until I see "Bootstrap process initiated." text 37s 287ms

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

And I wait until I see the name of "deblike_minion", refreshing the page 45s 247ms

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

And I query latest Salt changes on Debian-like system "deblike_minion" 988ms

@proxy

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

1s 535ms 4

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

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

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

Then I should see "proxy" short hostname 120ms

@proxy

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

1s 597ms 4

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

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

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

Then I should see "deblike_minion" hostname 170ms

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

24s 718ms 11

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

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

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

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

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

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

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

And I click on "Next" 86ms

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

When I click on "Confirm" 98ms

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

And I wait until event "Subscribe channels scheduled by admin" is completed 22s 368ms

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

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

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

51s 908ms 2

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

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

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

Scenario:
Log in as admin user

38s 409ms 1

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

Scenario:
Bootstrap a Red Hat-like minion

2m 6s 373ms 13

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

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

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

When I enter the hostname of "rhlike_minion" as "hostname" 1s 945ms

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

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

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

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

And I select the hostname of "proxy" from "proxies" if present 3s 279ms

And I click on "Bootstrap" 77ms

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

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

And I wait until I see the name of "rhlike_minion", refreshing the page 44s 869ms

And I wait until onboarding is completed for "rhlike_minion" 40s 102ms

@proxy

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

1s 367ms 4

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

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

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

Then I should see "proxy" short hostname 153ms

@proxy

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

1s 591ms 4

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

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

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

Then I should see "rhlike_minion" hostname 114ms

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

25s 864ms 11

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

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

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

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

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

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

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

And I click on "Next" 111ms

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

When I click on "Confirm" 137ms

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

And I wait until event "Subscribe channels scheduled by admin" is completed 23s 72ms

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

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

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

51s 673ms 2

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

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

@build_host
Feature:Bootstrap a build host via the GUI 15m 8s 660ms 2 7

Scenario:
Clean up sumaform leftovers on build host

8s 184ms 1

When I perform a full salt minion cleanup on "build_host" 8s 184ms

Scenario:
Log in as admin user

37s 796ms 1

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

Scenario:
Bootstrap a build host

4m 27s 643ms 10 1

The hostname of build_host is uyuni-master-build-host.sumaci.aws

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

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

When I enter the hostname of "build_host" as "hostname" 215ms

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

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

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

And I select "1-BUILD-HOST-KEY-x86_64" from "activationKeys" 112ms

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

And I click on "Bootstrap" 107ms

And I wait until I see "Bootstrap process initiated." text 4m 10s 79ms Show Error +

                                            
 Text 'Bootstrap process initiated.' not found (ScriptError)
./features/step_definitions/navigation_steps.rb:40:in `/^I wait until I see "([^"]*)" text$/'
features/init_clients/buildhost_bootstrap.feature:23:in `I wait until I see "Bootstrap process initiated." text'

13s 725ms Show Info +

12:56:52:000 - 13:01:06:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/systems/bootstrap

Screenshot +

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

8m 34s 334ms 4 2 1

When I follow the left menu "Salt > Keys" 134ms

Then I should see a "accepted" text 355ms

When I follow the left menu "Systems > System List > All" 189ms

And I wait at most 500 seconds until I see the name of "build_host", refreshing the page 8m 20s Show Error +

                                            
 execution expired (Timeout::Error)
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/step_definitions/setup_steps.rb:209:in `/^I wait at most (\d+) seconds until I see the name of "([^"]*)", refreshing the page$/'
features/init_clients/buildhost_bootstrap.feature:30:in `I wait at most 500 seconds until I see the name of "build_host", refreshing the page'

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

Then the Salt master can reach "build_host" 0s

13s 654ms Show Info +

13:01:20:000 - 13:09:41:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/systems/list/all

Screenshot +

@proxy

Scenario:
Check connection from build host to proxy

13s 890ms 1 3 1

Given I am on the Systems overview page of this "build_host" 309ms 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

13s 580ms Show Info +

13:09:55:000 - 13:09:55:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/systems/list/all

Screenshot +

@proxy

Scenario:
Check registration on build host of minion

24s 857ms 4 1

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

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

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

Then I should see "build_host" hostname 10s 54ms Show Error +

                                            
 Hostname uyuni-master-build-host.sumaci.aws is not present (ScriptError)
./features/step_definitions/navigation_steps.rb:676:in `/^I should see "([^"]*)" hostname$/'
features/init_clients/buildhost_bootstrap.feature:46:in `I should see "build_host" hostname'

13s 803ms Show Info +

13:10:09:000 - 13:10:21:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/ProxyClients.do?sid=1000010000&

Screenshot +

Scenario:
Detect latest Salt changes on the SLES build host

14s 89ms 1 1

When I query latest Salt changes on "build_host" 519ms 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"'

13s 569ms Show Info +

13:10:35:000 - 13:10:35:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/ProxyClients.do?sid=1000010000&

Screenshot +

Scenario:
Check that the build host is a build host

14s 42ms 1 2 1

Given I am on the Systems overview page of this "build_host" 293ms 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

13s 749ms Show Info +

13:10:49:000 - 13:10:49:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/ProxyClients.do?sid=1000010000&

Screenshot +

Scenario:
Check events history for failures on SLES build host

13s 822ms 1 1 1

Given I am on the Systems overview page of this "build_host" 297ms 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

13s 524ms Show Info +

13:11:03:000 - 13:11:03:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/ProxyClients.do?sid=1000010000&

Screenshot +

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

Scenario:
Clean up sumaform leftovers on SLES minion

9s 967ms 1

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

Scenario:
Log in as admin user

21s 774ms 1

Given I am authorized for the "Admin" section 21s 774ms 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

42s 773ms 10 1

When I follow the left menu "Systems > Bootstrapping" 42s 773ms 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/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

430ms 7 1

When I follow the left menu "Salt > Keys" 430ms 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/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

301ms 3 1

Given I am on the Systems overview page of this "sle_minion" 301ms 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

3s 721ms 3 1

Given I am on the Systems overview page of this "proxy" 3s 721ms 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/sle_minion.feature:54: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 "sle_minion" hostname 0s

@ssh_minion
Feature:Bootstrap a Salt host managed via salt-ssh 1m 44s 992ms 1 4 2

Scenario:
Clean up sumaform leftovers on SLES SSH minion

9s 622ms 1

When I perform a full salt minion cleanup on "ssh_minion" 9s 622ms

Scenario:
Log in as admin user

41s 791ms 1

Given I am authorized for the "Admin" section 41s 791ms 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_ssh_minion.feature:11:in `I am authorized for the "Admin" section'

Scenario:
Bootstrap a SLES SSH minion

24s 59ms 10 1

When I follow the left menu "Systems > Bootstrapping" 24s 59ms 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_ssh_minion.feature:14:in `I follow the left menu "Systems ) Bootstrapping"'

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

When I check "manageWithSSH" 0s

And I enter the hostname of "ssh_minion" as "hostname" 0s

And I enter "linux" as "password" 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 follow the left menu "Systems > System List > All" 0s

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

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

@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

295ms 3 1

Given I am on the Systems overview page of this "ssh_minion" 295ms Show Error +

                                            
 No system found for hostname: uyuni-master-suse-sshminion.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_ssh_minion.feature:37:in `I am on the Systems overview page of this "ssh_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 SSH minion

29s 223ms 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 999ms

When I follow "Details" in the content area 10s 37ms 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_ssh_minion.feature:45:in `I follow "Details" in the content area'

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

Then I should see "ssh_minion" hostname 0s

14s 186ms Show Info +

12:58:50:000 - 12:59:05: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 +

@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 582ms 5

Scenario:
Call spacewalk-debug on server

13s 621ms 1

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

Scenario:
Check the tomcat logs on server

670ms 1

Then the tomcat logs should not contain errors 670ms

Scenario:
Check salt event log for failures on server

1s 904ms 1

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

Scenario:
Check the taskomatic logs on server

721ms 1

Then the taskomatic logs should not contain errors 721ms

Scenario:
Check for out of memory errors

664ms 1

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

Feature:Debug the clients after the testsuite has run 1m 30s 946ms 1

Scenario:
Extract the logs from all our clients

1m 30s 946ms 1

When I extract the log files from all our active nodes 1m 30s 946ms

@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

146

Failed Scenarios

16

Skipped Scenarios

39

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

@sle_minion Scenario:The minion is healthy 6s 259ms 4

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

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

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

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

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

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

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

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

@scc_credentials Scenario:Refresh SCC 27s 634ms 1

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

@scc_credentials Scenario:Use the products and architecture filters 2s 643ms 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 56s 372ms 4

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

@scc_credentials @uyuni @build_host Scenario:Synchronize SLES 15 SP7 product with recommended sub-products for Retail feature 40m 18s 226ms 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 43s 852ms 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 615ms 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 140ms 11

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

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

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

@rhlike_minion Scenario:Disable metadata check for the fake AppStream repository 10s 939ms 6

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

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

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

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

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

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

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

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

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

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

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

@deblike_minion Scenario:Create custom repositories inside the Debian-like custom channel 7s 106ms 1

@rhlike_minion Scenario:Create a custom channel for RH-like minions 1s 101ms 10

@rhlike_minion Scenario:Create custom repositories inside the RH-like custom channel 4s 414ms 1

@sle_minion Scenario:Synchronize Fake-RPM-SUSE-Channel channel 3s 831ms 9

@sle_minion Scenario:Verify state of Fake-RPM-SUSE-Channel channel 5s 30ms 2

@skip_if_github_validation Scenario:Synchronize Fake-Child-Channel-i586 channel 3s 754ms 9

@sle_minion Scenario:Synchronize Fake-Child-Channel-SUSE-like channel 24s 778ms 9

@deblike_minion Scenario:Synchronize Fake-Base-Channel-Debian-like channel 3s 715ms 9

@rhlike_minion Scenario:Synchronize Fake-Base-Channel-RH-like channel 4s 180ms 9

@rhlike_minion Scenario:Synchronize Fake-Base-Channel-AppStream channel 4s 201ms 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 828ms 4

@sle_minion Scenario:Synchronize Devel-SUSE-Channel channel 3s 988ms 9

@deblike_minion Scenario:Synchronize Devel-Debian-like-Channel channel 4s 284ms 9

@rhlike_minion Scenario:Synchronize Devel-RH-like-Channel channel 4s 380ms 9

@build_host @uyuni Scenario:Synchronize Devel-Build-Host-Channel channel 4s 174ms 9

@sle_minion Scenario:Create an activation key with a channel 2s 172ms 2

@proxy

Scenario:
The proxy is healthy

4s 588ms 4

@sle_minion

Scenario:
The minion is healthy

6s 259ms 4

@build_host

Scenario:
The build host is healthy

3s 626ms 4

@ssh_minion

Scenario:
The SSH minion is healthy

6s 378ms 4

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 187ms 4

@deblike_minion

Scenario:
The Debian-like minion is healthy

6s 10ms 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

660ms 1

@no_auth_registry

Scenario:
The registry without authentication is healthy

657ms 1

@custom_download_endpoint

Scenario:
The custom download endpoint is working

652ms 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 67ms 7

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

@proxy @susemanager

Scenario:
List all products for SUSE Multi-Linux Manager

< 1ms 6

@scc_credentials

Scenario:
Refresh SCC

27s 634ms 1

@scc_credentials

Scenario:
Let the products page appear

2s 928ms 6

@scc_credentials

Scenario:
Use the products and architecture filters

2s 643ms 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 56s 372ms 4

@containerized_server @proxy @uyuni

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

45s 572ms 2

@scc_credentials @uyuni @build_host

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

40m 18s 226ms 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

43s 852ms 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 615ms 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 140ms 11

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 533ms 10

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 85ms 10

@rhlike_minion

Scenario:
Create a fake AppStream repository

970ms 7

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

10s 939ms 6

@sle_minion

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

2s 146ms 9

@rhlike_minion

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

2s 798ms 9

@rhlike_minion

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

2s 554ms 9

@sle_minion

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

1s 644ms 6

@deblike_minion

Scenario:
Create a fake repository for Debian-like

1s 123ms 7

@deblike_minion

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

1s 422ms 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 27s 610ms 9

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 240ms 10

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

6s 394ms 1

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 661ms 10

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

3s 644ms 1

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

1s 571ms 10

@deblike_minion

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

7s 106ms 1

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 101ms 10

@rhlike_minion

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

4s 414ms 1

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

3s 831ms 9

@sle_minion

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

5s 30ms 2

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

3s 754ms 9

@sle_minion

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

24s 778ms 9

@deblike_minion

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

3s 715ms 9

@rhlike_minion

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

4s 180ms 9

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 201ms 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 828ms 4

@sle_minion

Scenario:
Synchronize Devel-SUSE-Channel channel

3s 988ms 9

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

4s 284ms 9

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 380ms 9

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

4s 174ms 9

@sle_minion

Scenario:
Create an activation key with a channel

2s 172ms 2

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

3s 763ms 2

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

1s 726ms 2

@ssh_minion

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

1s 671ms 2

@ssh_minion

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

1s 852ms 2

@proxy

Scenario:
Create an activation key for the proxy

1s 958ms 2

@build_host

Scenario:
Create an activation key for the build host

2s 581ms 3

@scc_credentials

Scenario:
Create an activation key for the terminal

2s 253ms 2

@scc_credentials @susemanager

Scenario:
Update SLE key with synced base product

< 1ms 20