Cucumber Feature Report

All Scenarios

201

Passed Scenarios

153

Failed Scenarios

9

Skipped Scenarios

39

Execution Time: 75m 35s 2ms

Expand All | Collapse All

Metadata

App Version: Uyuni/Head

Browser: Chrome

Platform: x86_64

Parallel: Disabled

Feature:Sanity checks 44s 476ms 10 2

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

Scenario:
The server is healthy

11s 778ms 19

Then "server" should have a FQDN 384ms

And reverse resolution should work for "server" 647ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@proxy

Scenario:
The proxy is healthy

4s 443ms 4

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

And reverse resolution should work for "proxy" 279ms

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

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

@sle_minion

Scenario:
The minion is healthy

6s 420ms 4

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

And reverse resolution should work for "sle_minion" 463ms

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

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

@build_host

Scenario:
The build host is healthy

3s 851ms 4

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

And reverse resolution should work for "build_host" 217ms

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

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

@ssh_minion

Scenario:
The SSH minion is healthy

6s 610ms 4

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

And reverse resolution should work for "ssh_minion" 451ms

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

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

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 140ms 4

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

And reverse resolution should work for "rhlike_minion" 194ms

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

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

@deblike_minion

Scenario:
The Debian-like minion is healthy

6s 249ms 4

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

And reverse resolution should work for "deblike_minion" 227ms

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

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

@skip_if_cloud

Scenario:
The external resources can be reached

< 1ms 3

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

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

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

@server_http_proxy

Scenario:
The HTTP proxy is working

< 1ms 1

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

@auth_registry

Scenario:
The registry with authentication is healthy

692ms 1

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

@no_auth_registry

Scenario:
The registry without authentication is healthy

649ms 1

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

@custom_download_endpoint

Scenario:
The custom download endpoint is working

640ms 1

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

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

665ms 1

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

@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

40s 189ms 1

Given I am authorized for the "Admin" section 40s 189ms

Scenario:
Wait for refresh of list of products to finish

3s 172ms 1

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

Scenario:
Create testing username

1s 587ms 12

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

And I follow "Create User" 725ms

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

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

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

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

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

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

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

And I click on "Create Login" 67ms

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

And I should see a "testing" link 12ms

Scenario:
Grant testing user administrative priviledges

1s 822ms 10

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

And I follow "testing" 523ms

And I check "role_org_admin" 91ms

And I check "role_system_group_admin" 87ms

And I check "role_channel_admin" 85ms

And I check "role_activation_key_admin" 87ms

And I check "role_config_admin" 85ms

And I click on "Update" 629ms

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

And I should see a "testing" text 74ms

@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

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

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

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

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 5s 237ms 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 329ms 5

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

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

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

And I click on "Save Preferences" 575ms

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

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

3s 908ms 5

Given I am authorized as "testing" with password "testing" 3s 14ms

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

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

And I click on "Save Preferences" 674ms

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

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

Scenario:
Create a Kiwi user with image administrators rights

4s 414ms 2

New user kiwikiwi created with roles: image_admin

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

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

Feature:Prepare server for using Docker 4s 756ms 2

Scenario:
Create a Docker user with image administrators rights

1s 980ms 2

New user docker created with roles: image_admin

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

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

@no_auth_registry

Scenario:
Create an image store without credentials

2s 776ms 7

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

And I follow "Create" 584ms

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

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

And I click on "create-btn" 68ms

Then I wait until table row contains a "galaxy-registry" text 1s 681ms

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

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

Scenario:
Log in as admin user

37s 571ms 1

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

Scenario:
Disable scheduled reposyncs

4s 600ms 5

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

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

And I choose "disabled" 60ms

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

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

Scenario:
Disable scheduled Cobbler syncs

4s 559ms 5

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

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

And I choose "disabled" 51ms

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

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

@scc_credentials
Feature:List available channels and enable them 1m 37s 930ms 5 1

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

Scenario:
List available channels

32s 29ms 5

When I refresh SCC 29s 746ms

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

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

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

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

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

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

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

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

When I remove the mgr-sync cache file 639ms

And I execute mgr-sync refresh 1m 774ms

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

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

@scc_credentials

Scenario:
Refresh SCC

27s 577ms 1

When I refresh SCC 27s 577ms

@scc_credentials

Scenario:
Let the products page appear

2s 977ms 6

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

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

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

Then I should see a "Arch" text 125ms

And I should see a "Channels" text 127ms

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

@scc_credentials

Scenario:
Use the products and architecture filters

2s 517ms 7

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

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

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

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

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

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

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

3m 14s 731ms 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 657ms

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

And I use spacewalk-repo-sync to sync channel "opensuse_tumbleweed-x86_64" including only client tools dependencies 2m 49s 774ms

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

@containerized_server @proxy @uyuni

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

1m 6s 814ms 2

Channel opensuse_tumbleweed-x86_64 added
Channel opensuse_tumbleweed-uyuni-client-devel-x86_64 added
Channel uyuni-proxy-devel-tumbleweed-x86_64 added
Channel opensuse_tumbleweed-x86_64 finished reposync
Channel opensuse_tumbleweed-uyuni-client-devel-x86_64 finished reposync
Channel uyuni-proxy-devel-tumbleweed-x86_64 finished reposync
All channels for uyuni-proxy have been fully synced

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

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

@scc_credentials @uyuni @build_host

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

40m 38s 690ms 20

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 66ms

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

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

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

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

And I wait until all synchronized channels for "sles15-sp7" have finished 40m 15s 590ms

@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 766ms 7

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

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

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

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

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

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

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

@scc_credentials @skip_if_github_validation

Scenario:
Report the synchronization duration for SLES 15 SP7

< 1ms 1

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

Feature:Create fake channels 25s 123ms 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

491ms 1

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

Scenario:
Add a fake base channel for x86_64

1s 317ms 10

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

And I follow "Create Channel" 339ms

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

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

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

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

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

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

And I click on "Create Channel" 73ms

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

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

1s 153ms 10

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

And I follow "Create Channel" 321ms

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

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

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

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

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

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

And I click on "Create Channel" 64ms

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

@sle_minion

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

1s 547ms 10

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

And I follow "Create Channel" 287ms

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

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

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

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

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

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

And I click on "Create Channel" 544ms

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

Scenario:
Add a fake base channel for i586

1s 616ms 10

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

And I follow "Create Channel" 354ms

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

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

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

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

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

And I click on "Create Channel" 535ms

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

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

1s 54ms 10

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

And I follow "Create Channel" 248ms

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

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

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

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

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

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

And I click on "Create Channel" 62ms

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

Scenario:
Add a test base channel for x86_64

1s 560ms 10

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

And I follow "Create Channel" 337ms

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

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

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

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

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

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

And I click on "Create Channel" 511ms

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 658ms 10

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

And I follow "Create Channel" 349ms

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

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

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

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

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

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

And I click on "Create Channel" 520ms

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

@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 648ms 11

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

And I follow "Create Channel" 261ms

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

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

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

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

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

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

And I uncheck "gpg_check" 10s 105ms

And I click on "Create Channel" 500ms

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

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 583ms 10

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

And I follow "Create Channel" 347ms

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

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

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

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

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

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

And I click on "Create Channel" 507ms

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

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 490ms 10

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

And I follow "Create Channel" 270ms

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

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

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

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

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

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

And I click on "Create Channel" 491ms

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

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

478ms 1

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

Scenario:
Create a fake repository for distributions using RPM

1s 206ms 7

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

And I follow "Create Repository" 337ms

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

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

And I click on "Create Repository" 450ms

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

And I should see "metadataSigned" as checked 26ms

Scenario:
Disable metadata check for the fake RPM repository

11s 25ms 6

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

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

And I uncheck "metadataSigned" 10s 81ms

And I click on "Update Repository" 459ms

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

And I should see "metadataSigned" as unchecked 15ms

@rhlike_minion

Scenario:
Create a fake AppStream repository

1s 51ms 7

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

And I follow "Create Repository" 301ms

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

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

And I click on "Create Repository" 441ms

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

And I should see "metadataSigned" as checked 16ms

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

10s 929ms 6

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

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

And I uncheck "metadataSigned" 10s 74ms

And I click on "Update Repository" 451ms

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

And I should see "metadataSigned" as unchecked 17ms

@sle_minion

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

2s 156ms 9

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

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

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

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

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

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

And I click on "Save Repositories" 636ms

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

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

2s 566ms 9

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

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

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

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

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

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

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

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

@rhlike_minion

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

2s 47ms 9

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

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

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

And I click on "Update Channel" 63ms

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

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

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

And I click on "Save Repositories" 994ms

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

@rhlike_minion

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

2s 670ms 9

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

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

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

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

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

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

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

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

Scenario:
Create a fake repository for i586

11s 87ms 7

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

And I follow "Create Repository" 241ms

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

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

And I uncheck "metadataSigned" 10s 77ms

And I click on "Create Repository" 455ms

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

Scenario:
Add the repository to the i586 channel

2s 47ms 9

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

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

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

And I click on "Update Channel" 505ms

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

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

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

And I click on "Save Repositories" 633ms

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

@sle_minion

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

1s 651ms 6

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

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

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

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

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

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

@deblike_minion

Scenario:
Create a fake repository for Debian-like

734ms 7

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

And I follow "Create Repository" 317ms

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

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

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

And I click on "Create Repository" 55ms

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

@deblike_minion

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

1s 402ms 6

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

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

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

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

And I click on "Save Repositories" 759ms

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

@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 28s 474ms 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

529ms 1

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

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 318ms 10

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

And I follow "Create Channel" 400ms

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

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

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

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

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

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

And I click on "Create Channel" 67ms

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

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

6s 487ms 1

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

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 652ms 10

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

And I follow "Create Channel" 285ms

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

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

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

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

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

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

And I click on "Create Channel" 602ms

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

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

4s 16ms 1

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

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

1s 98ms 10

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

And I follow "Create Channel" 268ms

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

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

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

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

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

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

And I click on "Create Channel" 57ms

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

@deblike_minion

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

7s 563ms 1

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

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 568ms 10

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

And I follow "Create Channel" 269ms

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

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

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

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

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

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

And I click on "Create Channel" 544ms

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

@rhlike_minion

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

4s 239ms 1

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

Feature:Synchronize fake channels 58s 765ms 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 801ms 2

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

And I enable source package syncing 1s 381ms

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

3s 873ms 9

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

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

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

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

And I follow "Sync" 354ms

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

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

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

@sle_minion

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

4s 639ms 2

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

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

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

3s 628ms 9

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

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

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

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

And I follow "Sync" 349ms

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

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

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

Scenario:
Synchronize Test-Child-Channel-x86_64 channel

4s 255ms 9

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

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

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

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

And I follow "Sync" 877ms

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

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

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

@sle_minion

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

14s 821ms 9

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

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

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

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

And I follow "Sync" 799ms

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

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

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 11s 9ms

@deblike_minion

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

3s 632ms 9

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

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

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

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

And I follow "Sync" 341ms

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

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

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

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

@rhlike_minion

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

4s 311ms 9

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

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

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

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

And I follow "Sync" 892ms

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

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

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

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 140ms 9

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

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

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

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

And I follow "Sync" 743ms

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

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

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

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

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

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

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

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

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

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

Scenario:
Refresh the channel's repository data

6s 90ms 6

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

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

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

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

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

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

Scenario:
Cleanup disable source package syncing

989ms 1

Then I disable source package syncing 989ms

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

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

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

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

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

And I follow "Sync" 634ms

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

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

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

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

4s 222ms 9

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

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

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

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

And I follow "Sync" 785ms

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

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

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

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 373ms 9

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

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

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

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

And I follow "Sync" 873ms

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

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

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

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

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

4s 238ms 9

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

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

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

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

And I follow "Sync" 696ms

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

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

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

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

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

547ms 1

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

@sle_minion

Scenario:
Create an activation key with a channel

1s 938ms 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 487ms

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

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

3s 39ms 2

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

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

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

1s 880ms 2

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

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

@ssh_minion

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

2s 217ms 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" 1s 209ms

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

@ssh_minion

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

1s 884ms 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" 849ms

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

@proxy

Scenario:
Create an activation key for the proxy

1s 935ms 2

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

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

@build_host

Scenario:
Create an activation key for the build host

2s 641ms 3

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

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

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

@scc_credentials

Scenario:
Create an activation key for the terminal

2s 270ms 2

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

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

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

502ms 1

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 660ms

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 580ms

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 151ms 10

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 589ms

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

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

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

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

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

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

And I wait for child channels to appear 578ms

And I include the recommended child channels 181ms

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

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

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

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

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

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

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

And I click on "Update Activation Key" 700ms

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

@scc_credentials @uyuni @build_host

Scenario:
Update build host key with Uyuni client tools

2s 162ms 9

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

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

And I wait for child channels to appear 898ms

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

And I wait for child channels to appear 327ms

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

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

And I click on "Update Activation Key" 587ms

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

@skip_if_github_validation @scc_credentials @uyuni @build_host

Scenario:
Update build host key with dev child channel

2s 291ms 9

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

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

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

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

And I wait for child channels to appear 324ms

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

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

And I click on "Update Activation Key" 580ms

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

@scc_credentials @build_host

Scenario:
Update terminal key with synced base product

3s 164ms 16

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

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

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

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

And I wait for child channels to appear 460ms

And I include the recommended child channels 184ms

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

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

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

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

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

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

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

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

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

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

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

And I wait for child channels to appear 931ms

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

And I click on "Update Activation Key" 53ms

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

@skip_if_github_validation @deblike_minion

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

1s 735ms 6

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

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

And I wait for child channels to appear 860ms

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

And I click on "Update Activation Key" 554ms

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

@skip_if_github_validation @rhlike_minion

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

1s 766ms 6

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

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

And I wait for child channels to appear 850ms

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

And I click on "Update Activation Key" 605ms

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

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

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

@sle_minion

Scenario:
Create the bootstrap repository for SUSE Minion

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

@proxy

Scenario:
Create the bootstrap repository for Proxy

2s 24ms 1

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

@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 26s 763ms 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 527ms 1

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

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

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

Scenario:
Bootstrap the proxy host as a salt minion

35s 327ms 9

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 63ms

And I wait until I see "Bootstrap process initiated." text 34s 682ms

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

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

Scenario:
Generate containerized proxy configuration

12s 429ms 2

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

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

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

16s 704ms 1

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

Scenario:
Wait until containerized proxy service is active

3s 884ms 10

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

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

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

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

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

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

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

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

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

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

Scenario:
The containerized proxy should be registered automatically

692ms 2

When I follow the left menu "Systems" 63ms

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

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

11s 24ms 3

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

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

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

@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 712ms 7

Scenario:
Log in as admin user

38s 443ms 1

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

Scenario:
Bootstrap a Debian-like minion

2m 16s 66ms 14

The hostname of deblike_minion is uyuni-master-deblike-minion.sumaci.aws
* Mon Feb 2 2026 Michael Calmer
- Rebuild because of maintenance release
* 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:

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 88ms

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

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

And I wait until I see the name of "deblike_minion", refreshing the page 58s 909ms

And I wait until onboarding is completed for "deblike_minion" 30s 51ms

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

@proxy

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

1s 512ms 4

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

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

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

Then I should see "proxy" short hostname 111ms

@proxy

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

1s 298ms 4

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

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

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

Then I should see "deblike_minion" hostname 145ms

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

21s 809ms 11

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

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

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

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

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

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

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

And I click on "Next" 90ms

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

When I click on "Confirm" 76ms

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

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

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

492ms 1

* Mon Feb 2 2026 Michael Calmer
- Rebuild because of maintenance release
* 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:

When I query latest Salt changes on Debian-like system "deblike_minion" 492ms

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

52s 90ms 2

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

Then I check for failed events on history event page 51s 154ms

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

Scenario:
Log in as admin user

37s 773ms 1

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

Scenario:
Bootstrap a Red Hat-like minion

2m 6s 792ms 13

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

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 70ms

And I wait until I see "Bootstrap process initiated." text 32s 155ms

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

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

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

@proxy

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

1s 157ms 4

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

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

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

Then I should see "proxy" short hostname 76ms

@proxy

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

1s 173ms 4

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

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

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

Then I should see "rhlike_minion" hostname 120ms

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

22s 561ms 11

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

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

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

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

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

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

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

And I click on "Next" 110ms

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

When I click on "Confirm" 86ms

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

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

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

337ms 1

* Mon Feb 02 2026 Michael Calmer
- Rebuild because of maintenance release

* 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)

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

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

52s 51ms 2

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

Then I check for failed events on history event page 51s 89ms

@build_host
Feature:Bootstrap a build host via the GUI 4m 34s 672ms 9

Scenario:
Clean up sumaform leftovers on build host

8s 289ms 1

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

Scenario:
Log in as admin user

37s 932ms 1

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

Scenario:
Bootstrap a build host

46s 302ms 10

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

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 89ms

And I wait until I see "Bootstrap process initiated." text 42s 561ms

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

1m 45s 531ms 6

It took 2 seconds to contact the minion

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

Then I should see a "accepted" text 545ms

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

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

And I wait at most 500 seconds until onboarding is completed for "build_host" 1m 1s 94ms

Then the Salt master can reach "build_host" 1s 554ms

@proxy

Scenario:
Check connection from build host to proxy

1s 332ms 4

Given I am on the Systems overview page of this "build_host" 1s 60ms

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

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

Then I should see "proxy" short hostname 84ms

@proxy

Scenario:
Check registration on build host of minion

1s 301ms 4

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

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

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

Then I should see "build_host" hostname 101ms

Scenario:
Detect latest Salt changes on the SLES build host

579ms 1

* Mon Feb 02 2026 mc@suse.com
- Rebuild because of maintenance release

* Mon Jan 19 2026 marek.czernek@suse.com
- 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@suse.com
- 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)

When I query latest Salt changes on "build_host" 579ms

Scenario:
Check that the build host is a build host

1s 464ms 3

Given I am on the Systems overview page of this "build_host" 1s 195ms

Then I should see a "[Container Build Host]" text 143ms

Then I should see a "[OS Image Build Host]" text 125ms

Scenario:
Check events history for failures on SLES build host

1m 11s 939ms 2

Given I am on the Systems overview page of this "build_host" 983ms

Then I check for failed events on history event page 1m 10s 956ms

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

Scenario:
Clean up sumaform leftovers on SLES minion

9s 976ms 1

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

Scenario:
Log in as admin user

21s 790ms 1

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

43s 587ms 10 1

When I follow the left menu "Systems > Bootstrapping" 43s 587ms 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

531ms 7 1

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

490ms 3 1

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

Given I am on the Systems overview page of this "proxy" 3s 571ms 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 501ms 1 4 2

Scenario:
Clean up sumaform leftovers on SLES SSH minion

10s 295ms 1

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

Scenario:
Log in as admin user

41s 982ms 1

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

22s 278ms 10 1

When I follow the left menu "Systems > Bootstrapping" 22s 278ms 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

432ms 3 1

Given I am on the Systems overview page of this "ssh_minion" 432ms 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 512ms 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 762ms

When I follow "Details" in the content area 10s 24ms 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 725ms Show Info +

17:24:42:000 - 17:24:56: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 18s 259ms 5

Scenario:
Call spacewalk-debug on server

14s 272ms 1

When I execute spacewalk-debug on the server 14s 272ms

Scenario:
Check the tomcat logs on server

635ms 1

Then the tomcat logs should not contain errors 635ms

Scenario:
Check salt event log for failures on server

1s 892ms 1

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

Scenario:
Check the taskomatic logs on server

701ms 1

Then the taskomatic logs should not contain errors 701ms

Scenario:
Check for out of memory errors

756ms 1

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

Feature:Debug the clients after the testsuite has run 1m 33s 717ms 1

Scenario:
Extract the logs from all our clients

1m 33s 717ms 1

When I extract the log files from all our active nodes 1m 33s 717ms

@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

153

Failed Scenarios

9

Skipped Scenarios

39

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

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

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

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

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

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

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

@custom_download_endpoint Scenario:The custom download endpoint is working 640ms 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 2s 776ms 7

@scc_credentials Feature:List available channels and enable them 1m 37s 930ms 5 1

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

@scc_credentials Scenario:Refresh SCC 27s 577ms 1

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

@scc_credentials Scenario:Use the products and architecture filters 2s 517ms 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 3m 14s 731ms 4

@containerized_server @proxy @uyuni Scenario:Add Uyuni Proxy product for Tumbleweed, including Uyuni Client Tools 1m 6s 814ms 2

@scc_credentials @uyuni @build_host Scenario:Synchronize SLES 15 SP7 product with recommended sub-products for Retail feature 40m 38s 690ms 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 766ms 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 547ms 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 648ms 11

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

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

@rhlike_minion Scenario:Create a fake AppStream repository 1s 51ms 7

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

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

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

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

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

@deblike_minion Scenario:Create a fake repository for Debian-like 734ms 7

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

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

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

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

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

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

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

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

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

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

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

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

@sle_minion Scenario:Synchronize Fake-Child-Channel-SUSE-like channel 14s 821ms 9

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

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

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

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

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

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

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

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

@proxy

Scenario:
The proxy is healthy

4s 443ms 4

@sle_minion

Scenario:
The minion is healthy

6s 420ms 4

@build_host

Scenario:
The build host is healthy

3s 851ms 4

@ssh_minion

Scenario:
The SSH minion is healthy

6s 610ms 4

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 140ms 4

@deblike_minion

Scenario:
The Debian-like minion is healthy

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

692ms 1

@no_auth_registry

Scenario:
The registry without authentication is healthy

649ms 1

@custom_download_endpoint

Scenario:
The custom download endpoint is working

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

2s 776ms 7

@scc_credentials
Feature:List available channels and enable them 1m 37s 930ms 5 1

@proxy @susemanager

Scenario:
List all products for SUSE Multi-Linux Manager

< 1ms 6

@scc_credentials

Scenario:
Refresh SCC

27s 577ms 1

@scc_credentials

Scenario:
Let the products page appear

2s 977ms 6

@scc_credentials

Scenario:
Use the products and architecture filters

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

3m 14s 731ms 4

@containerized_server @proxy @uyuni

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

1m 6s 814ms 2

@scc_credentials @uyuni @build_host

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

40m 38s 690ms 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 766ms 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 547ms 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 648ms 11

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 583ms 10

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 490ms 10

@rhlike_minion

Scenario:
Create a fake AppStream repository

1s 51ms 7

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

10s 929ms 6

@sle_minion

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

2s 156ms 9

@rhlike_minion

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

2s 47ms 9

@rhlike_minion

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

2s 670ms 9

@sle_minion

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

1s 651ms 6

@deblike_minion

Scenario:
Create a fake repository for Debian-like

734ms 7

@deblike_minion

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

1s 402ms 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 28s 474ms 9

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 318ms 10

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

6s 487ms 1

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 652ms 10

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

4s 16ms 1

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

1s 98ms 10

@deblike_minion

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

7s 563ms 1

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 568ms 10

@rhlike_minion

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

4s 239ms 1

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

3s 873ms 9

@sle_minion

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

4s 639ms 2

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

3s 628ms 9

@sle_minion

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

14s 821ms 9

@deblike_minion

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

3s 632ms 9

@rhlike_minion

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

4s 311ms 9

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 140ms 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 816ms 4

@sle_minion

Scenario:
Synchronize Devel-SUSE-Channel channel

3s 981ms 9

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

4s 222ms 9

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 373ms 9

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

4s 238ms 9

@sle_minion

Scenario:
Create an activation key with a channel

1s 938ms 2

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

3s 39ms 2

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

1s 880ms 2

@ssh_minion

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

2s 217ms 2

@ssh_minion

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

1s 884ms 2

@proxy

Scenario:
Create an activation key for the proxy

1s 935ms 2

@build_host

Scenario:
Create an activation key for the build host

2s 641ms 3

@scc_credentials

Scenario:
Create an activation key for the terminal

2s 270ms 2

@scc_credentials @susemanager

Scenario:
Update SLE key with synced base product

< 1ms 20