Cucumber Feature Report

All Scenarios

201

Passed Scenarios

162

Failed Scenarios

0

Skipped Scenarios

39

Execution Time: 84m 16s 968ms

Expand All | Collapse All

Metadata

App Version: Uyuni/Head

Browser: Chrome

Platform: x86_64

Parallel: Disabled

Feature:Sanity checks 44s 792ms 10 2

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

Scenario:
The server is healthy

11s 980ms 19

Then "server" should have a FQDN 385ms

And reverse resolution should work for "server" 634ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@proxy

Scenario:
The proxy is healthy

4s 546ms 4

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

And reverse resolution should work for "proxy" 285ms

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

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

@sle_minion

Scenario:
The minion is healthy

6s 697ms 4

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

And reverse resolution should work for "sle_minion" 438ms

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

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

@build_host

Scenario:
The build host is healthy

3s 572ms 4

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

And reverse resolution should work for "build_host" 207ms

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

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

@ssh_minion

Scenario:
The SSH minion is healthy

6s 276ms 4

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

And reverse resolution should work for "ssh_minion" 412ms

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

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

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 554ms 4

Then "rhlike_minion" should have a FQDN 2s 178ms

And reverse resolution should work for "rhlike_minion" 203ms

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

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

@deblike_minion

Scenario:
The Debian-like minion is healthy

6s 179ms 4

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

And reverse resolution should work for "deblike_minion" 235ms

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

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

@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

683ms 1

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

@no_auth_registry

Scenario:
The registry without authentication is healthy

661ms 1

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

@custom_download_endpoint

Scenario:
The custom download endpoint is working

639ms 1

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

Feature:Very first settings 49s 109ms 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

651ms 1

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

@skip_if_containerized_server

Scenario:
Create admin user and first organization

< 1ms 12

Given I access the host the first time 0s

When I go to the home page 0s

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

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

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

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

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

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

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

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

And I click on "Create Organization" 0s

Then I am logged in 0s

Scenario:
Log in as admin user

39s 502ms 1

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

Scenario:
Wait for refresh of list of products to finish

3s 903ms 1

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

Scenario:
Create testing username

2s 351ms 12

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

And I follow "Create User" 649ms

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

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

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

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

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

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

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

And I click on "Create Login" 1s 43ms

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

And I should see a "testing" link 12ms

Scenario:
Grant testing user administrative priviledges

1s 928ms 10

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

And I follow "testing" 591ms

And I check "role_org_admin" 80ms

And I check "role_system_group_admin" 75ms

And I check "role_channel_admin" 77ms

And I check "role_activation_key_admin" 76ms

And I check "role_config_admin" 79ms

And I click on "Update" 715ms

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

And I should see a "testing" text 83ms

@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

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

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

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

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

@scc_credentials @no_mirror

Scenario:
Enter valid SCC credentials

< 1ms 6

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

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

And I ask to add new credentials 0s

And I enter the SCC credentials 0s

And I click on "Save" 0s

And I wait until the SCC credentials are valid 0s

Feature:Change personal preferences 4s 710ms 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 477ms 5

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

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

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

And I click on "Save Preferences" 690ms

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

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

3s 232ms 5

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

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

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

And I click on "Save Preferences" 582ms

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

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

Scenario:
Create a Kiwi user with image administrators rights

4s 26ms 2

New user kiwikiwi created with roles: image_admin

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

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

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

Scenario:
Create a Docker user with image administrators rights

2s 47ms 2

New user docker created with roles: image_admin

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

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

@no_auth_registry

Scenario:
Create an image store without credentials

3s 197ms 7

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

And I follow "Create" 637ms

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

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

And I click on "create-btn" 101ms

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

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

Feature:Do not let Taskomatic tasks interfere with our CI tests 45s 522ms 3

Scenario:
Log in as admin user

37s 736ms 1

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

Scenario:
Disable scheduled reposyncs

4s 811ms 5

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

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

And I choose "disabled" 53ms

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

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

Scenario:
Disable scheduled Cobbler syncs

2s 974ms 5

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

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

And I choose "disabled" 45ms

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

And I click on "Disable Schedule" 50ms

@scc_credentials
Feature:List available channels and enable them 1m 39s 220ms 5 1

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

Scenario:
List available channels

33s 225ms 5

When I refresh SCC 30s 911ms

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

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

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

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

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

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

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

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

When I remove the mgr-sync cache file 673ms

And I execute mgr-sync refresh 1m 822ms

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

Feature:Synchronize products in the products page of the Setup Wizard 50m 58s 512ms 8 9

@scc_credentials

Scenario:
Refresh SCC

28s 524ms 1

When I refresh SCC 28s 524ms

@scc_credentials

Scenario:
Let the products page appear

2s 259ms 6

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

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

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

Then I should see a "Arch" text 120ms

And I should see a "Channels" text 119ms

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

@scc_credentials

Scenario:
Use the products and architecture filters

2s 525ms 7

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

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

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

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

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

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

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

2m 55ms 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 946ms

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

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

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

@containerized_server @proxy @uyuni

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

1m 17s 467ms 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 563ms

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

@scc_credentials @uyuni @build_host

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

46m 24s 455ms 20

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 54ms

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

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

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

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

And I wait until all synchronized channels for "sles15-sp7" have finished 46m 2s 141ms

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

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

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

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

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

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

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

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

@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 23s 506ms 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

449ms 1

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

Scenario:
Add a fake base channel for x86_64

1s 727ms 10

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

And I follow "Create Channel" 413ms

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

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

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

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

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

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

And I click on "Create Channel" 599ms

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

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

And I follow "Create Channel" 341ms

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

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

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

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

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

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

And I click on "Create Channel" 555ms

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

@sle_minion

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

1s 426ms 10

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

And I follow "Create Channel" 345ms

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

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

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

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

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

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

And I click on "Create Channel" 53ms

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

Scenario:
Add a fake base channel for i586

1s 402ms 10

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

And I follow "Create Channel" 326ms

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

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

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

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

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

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

And I click on "Create Channel" 523ms

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

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

933ms 10

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

And I follow "Create Channel" 321ms

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

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

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

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

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

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

And I click on "Create Channel" 54ms

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

Scenario:
Add a test base channel for x86_64

1s 333ms 10

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

And I follow "Create Channel" 243ms

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

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

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

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

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

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

And I click on "Create Channel" 54ms

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

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

1s 408ms 10

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

And I follow "Create Channel" 269ms

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

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

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

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

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

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

And I click on "Create Channel" 55ms

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

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

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

And I follow "Create Channel" 355ms

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

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

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

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

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

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

And I uncheck "gpg_check" 10s 89ms

And I click on "Create Channel" 529ms

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

@rhlike_minion

Scenario:
Add a RedHat-like base channel

872ms 10

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

And I follow "Create Channel" 271ms

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

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

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

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

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

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

And I click on "Create Channel" 54ms

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

@rhlike_minion

Scenario:
Add a fake AppStream base channel

955ms 10

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

And I follow "Create Channel" 342ms

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

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

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

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

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

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

And I click on "Create Channel" 55ms

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

Feature:Create fake repositories for each fake child channel 51s 315ms 14 1

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

Scenario:
Log in as admin user

493ms 1

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

Scenario:
Create a fake repository for distributions using RPM

1s 176ms 7

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

And I follow "Create Repository" 344ms

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

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

And I click on "Create Repository" 432ms

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

And I should see "metadataSigned" as checked 23ms

Scenario:
Disable metadata check for the fake RPM repository

10s 897ms 6

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

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

And I uncheck "metadataSigned" 10s 70ms

And I click on "Update Repository" 441ms

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

And I should see "metadataSigned" as unchecked 15ms

@rhlike_minion

Scenario:
Create a fake AppStream repository

993ms 7

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

And I follow "Create Repository" 297ms

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

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

And I click on "Create Repository" 405ms

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

And I should see "metadataSigned" as checked 16ms

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

10s 977ms 6

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

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

And I uncheck "metadataSigned" 10s 75ms

And I click on "Update Repository" 442ms

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

And I should see "metadataSigned" as unchecked 15ms

@sle_minion

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

1s 882ms 9

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

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

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

And I click on "Update Channel" 551ms

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

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

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

And I click on "Save Repositories" 498ms

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

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

2s 318ms 9

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

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

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

And I click on "Update Channel" 52ms

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

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

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

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

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

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

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

And I click on "Update Channel" 55ms

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

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

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

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

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

@rhlike_minion

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

2s 708ms 9

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

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

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

And I click on "Update Channel" 524ms

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

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

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

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

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

Scenario:
Create a fake repository for i586

11s 48ms 7

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

And I follow "Create Repository" 240ms

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

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

And I uncheck "metadataSigned" 10s 82ms

And I click on "Create Repository" 435ms

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

Scenario:
Add the repository to the i586 channel

1s 922ms 9

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

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

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

And I click on "Update Channel" 53ms

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

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

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

And I click on "Save Repositories" 589ms

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

@sle_minion

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

1s 651ms 6

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

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

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

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

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

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

@deblike_minion

Scenario:
Create a fake repository for Debian-like

1s 82ms 7

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

And I follow "Create Repository" 316ms

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

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

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

And I click on "Create Repository" 420ms

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

@deblike_minion

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

1s 451ms 6

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

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

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

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

And I click on "Save Repositories" 826ms

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

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Add the repository to the terminal child channel

< 1ms 9

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

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

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

And I click on "Update Channel" 0s

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

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

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

And I click on "Save Repositories" 0s

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

@skip_if_github_validation
Feature:Create custom channels with development repositories 27s 763ms 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

459ms 1

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

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 15ms 10

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

And I follow "Create Channel" 282ms

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

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

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

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

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

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

And I click on "Create Channel" 60ms

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

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

6s 869ms 1

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

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 381ms 10

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

And I follow "Create Channel" 279ms

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

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

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

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

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

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

And I click on "Create Channel" 537ms

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

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

3s 748ms 1

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

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

907ms 10

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

And I follow "Create Channel" 277ms

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

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

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

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

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

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

And I click on "Create Channel" 54ms

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

@deblike_minion

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

7s 399ms 1

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

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 388ms 10

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

And I follow "Create Channel" 297ms

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

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

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

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

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

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

And I click on "Create Channel" 502ms

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

@rhlike_minion

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

4s 593ms 1

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

Feature:Synchronize fake channels 1m 19s 211ms 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 979ms 2

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

And I enable source package syncing 1s 536ms

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

3s 757ms 9

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

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

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

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

And I follow "Sync" 337ms

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

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

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

@sle_minion

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

4s 984ms 2

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

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

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

3s 697ms 9

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

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

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

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

And I follow "Sync" 343ms

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

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

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

Scenario:
Synchronize Test-Child-Channel-x86_64 channel

4s 144ms 9

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

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

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

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

And I follow "Sync" 855ms

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

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

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

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

@sle_minion

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

34s 923ms 9

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

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

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

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

And I follow "Sync" 591ms

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

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

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

@deblike_minion

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

3s 703ms 9

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

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

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

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

And I follow "Sync" 338ms

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

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

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

@rhlike_minion

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

4s 345ms 9

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

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

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

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

And I follow "Sync" 944ms

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

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

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

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

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 159ms 9

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

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

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

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

And I follow "Sync" 773ms

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

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

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

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

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

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

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

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

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

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

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

Scenario:
Refresh the channel's repository data

5s 892ms 6

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

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

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

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

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

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

Scenario:
Cleanup disable source package syncing

1s 88ms 1

Then I disable source package syncing 1s 88ms

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

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

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

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

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

And I follow "Sync" 337ms

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

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

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

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

4s 297ms 9

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

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

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

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

And I follow "Sync" 841ms

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

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

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

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 209ms 9

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

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

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

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

And I follow "Sync" 701ms

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

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

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

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

4s 193ms 9

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

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

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

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

And I follow "Sync" 695ms

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

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

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

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

451ms 1

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

@sle_minion

Scenario:
Create an activation key with a channel

2s 358ms 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 731ms

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

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

1s 540ms 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" 856ms

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

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

3s 35ms 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 740ms

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

@ssh_minion

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

2s 69ms 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 60ms

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

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

@proxy

Scenario:
Create an activation key for the proxy

1s 927ms 2

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

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

@build_host

Scenario:
Create an activation key for the build host

2s 636ms 3

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

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

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

@scc_credentials

Scenario:
Create an activation key for the terminal

2s 680ms 2

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

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

Feature:Update activation keys 22s 967ms 11 8

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

Scenario:
Log in as admin user

474ms 1

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

@scc_credentials @susemanager

Scenario:
Update SLE key with synced base product

< 1ms 20

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

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

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

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 0s

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

@uyuni

Scenario:
Update openSUSE Tumbleweed key with synced base product

2s 408ms 10

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 592ms

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 564ms

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

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

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

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

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

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

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

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

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

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 227ms 20

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

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

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

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

And I wait for child channels to appear 513ms

And I include the recommended child channels 170ms

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

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

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 600ms

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

@scc_credentials @uyuni @build_host

Scenario:
Update build host key with Uyuni client tools

2s 214ms 9

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

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

And I wait for child channels to appear 1s

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

And I wait for child channels to appear 315ms

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

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

And I click on "Update Activation Key" 579ms

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

@skip_if_github_validation @scc_credentials @uyuni @build_host

Scenario:
Update build host key with dev child channel

2s 131ms 9

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

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

And I wait for child channels to appear 919ms

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

And I wait for child channels to appear 306ms

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

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

And I click on "Update Activation Key" 552ms

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

@scc_credentials @build_host

Scenario:
Update terminal key with synced base product

2s 985ms 16

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

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

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

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

And I wait for child channels to appear 511ms

And I include the recommended child channels 159ms

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 591ms

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

@susemanager @scc_credentials @build_host

Scenario:
Update terminal key with normal SUSE fake channel

< 1ms 9

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

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

And I wait for child channels to appear 0s

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

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

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

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

And I click on "Update Activation Key" 0s

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

@pxeboot_minion @uyuni @scc_credentials @build_host

Scenario:
Update terminal key with specific fake channel

< 1ms 9

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

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

And I wait for child channels to appear 0s

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

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

And I check "Uyuni Client Tools for SLES15 SP7 x86_64 (Development)" 0s

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

And I click on "Update Activation Key" 0s

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

@skip_if_github_validation @sle_minion

Scenario:
Update SLE key with to include dev child channel

1s 686ms 6

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

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

And I wait for child channels to appear 820ms

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

And I click on "Update Activation Key" 562ms

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

@skip_if_github_validation @deblike_minion

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

1s 733ms 6

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

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

And I wait for child channels to appear 893ms

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

And I click on "Update Activation Key" 544ms

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

@skip_if_github_validation @rhlike_minion

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

1s 766ms 6

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

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

And I wait for child channels to appear 890ms

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

And I click on "Update Activation Key" 572ms

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

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

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

@sle_minion

Scenario:
Create the bootstrap repository for SUSE Minion

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

@proxy

Scenario:
Create the bootstrap repository for Proxy

2s 59ms 1

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

@build_host

Scenario:
Create the bootstrap repository for Build Host

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

@containerized_server @scope_containerized_proxy @proxy
Feature:Setup containerized proxy 3m 25s 426ms 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 648ms 1

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

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

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

Scenario:
Bootstrap the proxy host as a salt minion

35s 317ms 9

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 61ms

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 254ms 1

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

Scenario:
Generate containerized proxy configuration

10s 601ms 2

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

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

Scenario:
Set up the containerized proxy service to support Avahi

< 1ms 1

Record not added - avahi domain was not detected

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

Scenario:
Run a containerized proxy

17s 636ms 1

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

Scenario:
Wait until containerized proxy service is active

3s 843ms 10

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

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

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

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

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

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

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

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

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

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

Scenario:
The containerized proxy should be registered automatically

652ms 2

When I follow the left menu "Systems" 60ms

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

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

10s 994ms 3

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

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

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

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

Scenario:
Log in as admin user

38s 187ms 1

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

Scenario:
Bootstrap a Debian-like minion

2m 19s 811ms 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" 227ms

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

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

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

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

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

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

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

And I click on "Bootstrap" 106ms

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

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

And I wait until I see the name of "deblike_minion", refreshing the page 46s 66ms

And I wait until onboarding is completed for "deblike_minion" 42s 545ms

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

@proxy

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

2s 148ms 4

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

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

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

Then I should see "proxy" short hostname 114ms

@proxy

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

2s 4

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

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

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

Then I should see "deblike_minion" hostname 247ms

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

23s 227ms 11

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

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

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

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

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

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

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

And I click on "Next" 102ms

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

When I click on "Confirm" 129ms

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

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

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

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

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

51s 752ms 2

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

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

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

Scenario:
Log in as admin user

38s 337ms 1

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

Scenario:
Bootstrap a Red Hat-like minion

2m 11s 699ms 13

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

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 105ms

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

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

And I wait until I see the name of "rhlike_minion", refreshing the page 59s 289ms

And I wait until onboarding is completed for "rhlike_minion" 31s 469ms

@proxy

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

1s 137ms 4

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

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

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

Then I should see "proxy" short hostname 93ms

@proxy

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

1s 310ms 4

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

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

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

Then I should see "rhlike_minion" hostname 136ms

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

25s 350ms 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 649ms

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

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

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

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

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

And I click on "Next" 85ms

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

When I click on "Confirm" 93ms

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

And I wait until event "Subscribe channels scheduled by admin" is completed 21s 768ms

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

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

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

52s 306ms 2

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

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

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

Scenario:
Clean up sumaform leftovers on build host

7s 549ms 1

When I perform a full salt minion cleanup on "build_host" 7s 549ms

Scenario:
Log in as admin user

38s 209ms 1

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

Scenario:
Bootstrap a build host

45s 177ms 10

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

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 122ms

And I wait until I see "Bootstrap process initiated." text 41s 439ms

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

1m 32s 461ms 6

It took 4 seconds to contact the minion

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

Then I should see a "accepted" text 509ms

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

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

And I wait at most 500 seconds until onboarding is completed for "build_host" 44s 25ms

Then the Salt master can reach "build_host" 4s 329ms

@proxy

Scenario:
Check connection from build host to proxy

2s 40ms 4

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

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

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

Then I should see "proxy" short hostname 90ms

@proxy

Scenario:
Check registration on build host of minion

2s 703ms 4

Given I am on the Systems overview page of this "proxy" 2s 358ms

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

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

Then I should see "build_host" hostname 128ms

Scenario:
Detect latest Salt changes on the SLES build host

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

Scenario:
Check that the build host is a build host

2s 64ms 3

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

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

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

Scenario:
Check events history for failures on SLES build host

1m 12s 40ms 2

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

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

@sle_minion
Feature:Bootstrap a Salt minion via the GUI 3m 11s 874ms 6 2

Scenario:
Clean up sumaform leftovers on SLES minion

10s 452ms 1

When I perform a full salt minion cleanup on "sle_minion" 10s 452ms

Scenario:
Log in as admin user

38s 748ms 1

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

Scenario:
Bootstrap a SLES minion

45s 662ms 11

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

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

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

When I enter the hostname of "sle_minion" as "hostname" 328ms

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

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

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

And I select "1-SUSE-KEY-x86_64" from "activationKeys" 213ms

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

And I click on "Bootstrap" 110ms

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

And I report the bootstrap duration for "sle_minion" < 1ms

Scenario:
Check the new bootstrapped minion in System List page

1m 32s 559ms 8

It took 2 seconds to contact the minion

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

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

Then I should see a "accepted" text 135ms

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

And I wait until I see the name of "sle_minion", refreshing the page 31s 422ms

And I wait until onboarding is completed for "sle_minion" 57s 356ms

Then the Salt master can reach "sle_minion" 2s 680ms

And I report the onboarding duration for "sle_minion" < 1ms

@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

2s 607ms 4

Given I am on the Systems overview page of this "sle_minion" 2s 235ms

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

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

Then I should see "proxy" short hostname 105ms

@proxy

Scenario:
Check registration on proxy of minion

1s 843ms 4

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

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

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

Then I should see "sle_minion" hostname 132ms

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

Scenario:
Clean up sumaform leftovers on SLES SSH minion

9s 910ms 1

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

Scenario:
Log in as admin user

40s 210ms 1

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

Scenario:
Bootstrap a SLES SSH minion

2m 32s 705ms 11

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

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

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

When I check "manageWithSSH" 166ms

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

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

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

And I click on "Bootstrap" 180ms

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

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

And I wait until I see the name of "ssh_minion", refreshing the page 17s 881ms

And I wait until onboarding is completed for "ssh_minion" 1m 15s 652ms

@susemanager

Scenario:
Use correct kernel image on the SSH minion

< 1ms 2

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

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

@susemanager

Scenario:
Reboot the SSH minion to use the new kernel

< 1ms 1

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

@proxy

Scenario:
Check connection from SSH minion to proxy

1s 331ms 4

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

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

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

Then I should see "proxy" short hostname 88ms

@proxy

Scenario:
Check registration on proxy of SSH minion

1s 178ms 4

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

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

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

Then I should see "ssh_minion" hostname 124ms

@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 19s 528ms 5

Scenario:
Call spacewalk-debug on server

15s 369ms 1

When I execute spacewalk-debug on the server 15s 369ms

Scenario:
Check the tomcat logs on server

678ms 1

Then the tomcat logs should not contain errors 678ms

Scenario:
Check salt event log for failures on server

2s 37ms 1

Then the salt event log on server should contain no failures 2s 37ms

Scenario:
Check the taskomatic logs on server

746ms 1

Then the taskomatic logs should not contain errors 746ms

Scenario:
Check for out of memory errors

696ms 1

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

Feature:Debug the clients after the testsuite has run 1m 40s 399ms 1

Scenario:
Extract the logs from all our clients

1m 40s 399ms 1

When I extract the log files from all our active nodes 1m 40s 399ms

@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

162

Failed Scenarios

0

Skipped Scenarios

39

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

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

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

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

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

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

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

@custom_download_endpoint Scenario:The custom download endpoint is working 639ms 1

@skip_if_containerized_server Scenario:Create admin user and first organization < 1ms 12

@server_http_proxy Scenario:Setup HTTP proxy < 1ms 9

@scc_credentials @no_mirror Scenario:Enter valid SCC credentials < 1ms 6

@no_auth_registry Scenario:Create an image store without credentials 3s 197ms 7

@scc_credentials Feature:List available channels and enable them 1m 39s 220ms 5 1

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

@scc_credentials Scenario:Refresh SCC 28s 524ms 1

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

@scc_credentials Scenario:Use the products and architecture filters 2s 525ms 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 2m 55ms 4

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

@scc_credentials @uyuni @build_host Scenario:Synchronize SLES 15 SP7 product with recommended sub-products for Retail feature 46m 24s 455ms 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 224ms 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 426ms 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 539ms 11

@rhlike_minion Scenario:Add a RedHat-like base channel 872ms 10

@rhlike_minion Scenario:Add a fake AppStream base channel 955ms 10

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

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

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

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

@rhlike_minion Scenario:Add the fake AppStream repository to the AppStream base channel 2s 708ms 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 1s 82ms 7

@deblike_minion Scenario:Add the repository to the Debian-like base channel 1s 451ms 6

@pxeboot_minion @uyuni @scc_credentials Scenario:Add the repository to the terminal child channel < 1ms 9

@skip_if_github_validation Feature:Create custom channels with development repositories 27s 763ms 9

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

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

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

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

@deblike_minion Scenario:Create a custom channel for Debian-like minions 907ms 10

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

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

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

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

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

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

@sle_minion Scenario:Synchronize Fake-Child-Channel-SUSE-like channel 34s 923ms 9

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

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

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

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

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

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

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

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

@proxy

Scenario:
The proxy is healthy

4s 546ms 4

@sle_minion

Scenario:
The minion is healthy

6s 697ms 4

@build_host

Scenario:
The build host is healthy

3s 572ms 4

@ssh_minion

Scenario:
The SSH minion is healthy

6s 276ms 4

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 554ms 4

@deblike_minion

Scenario:
The Debian-like minion is healthy

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

683ms 1

@no_auth_registry

Scenario:
The registry without authentication is healthy

661ms 1

@custom_download_endpoint

Scenario:
The custom download endpoint is working

639ms 1

@skip_if_containerized_server

Scenario:
Create admin user and first organization

< 1ms 12

@server_http_proxy

Scenario:
Setup HTTP proxy

< 1ms 9

@scc_credentials @no_mirror

Scenario:
Enter valid SCC credentials

< 1ms 6

@no_auth_registry

Scenario:
Create an image store without credentials

3s 197ms 7

@scc_credentials
Feature:List available channels and enable them 1m 39s 220ms 5 1

@proxy @susemanager

Scenario:
List all products for SUSE Multi-Linux Manager

< 1ms 6

@scc_credentials

Scenario:
Refresh SCC

28s 524ms 1

@scc_credentials

Scenario:
Let the products page appear

2s 259ms 6

@scc_credentials

Scenario:
Use the products and architecture filters

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

2m 55ms 4

@containerized_server @proxy @uyuni

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

1m 17s 467ms 2

@scc_credentials @uyuni @build_host

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

46m 24s 455ms 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 224ms 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 426ms 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 539ms 11

@rhlike_minion

Scenario:
Add a RedHat-like base channel

872ms 10

@rhlike_minion

Scenario:
Add a fake AppStream base channel

955ms 10

@rhlike_minion

Scenario:
Create a fake AppStream repository

993ms 7

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

10s 977ms 6

@sle_minion

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

1s 882ms 9

@rhlike_minion

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

2s 709ms 9

@rhlike_minion

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

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

1s 82ms 7

@deblike_minion

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

1s 451ms 6

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Add the repository to the terminal child channel

< 1ms 9

@skip_if_github_validation
Feature:Create custom channels with development repositories 27s 763ms 9

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 15ms 10

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

6s 869ms 1

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 381ms 10

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

3s 748ms 1

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

907ms 10

@deblike_minion

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

7s 399ms 1

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 388ms 10

@rhlike_minion

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

4s 593ms 1

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

3s 757ms 9

@sle_minion

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

4s 984ms 2

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

3s 697ms 9

@sle_minion

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

34s 923ms 9

@deblike_minion

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

3s 703ms 9

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-RH-like channel

4s 345ms 9

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 159ms 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 405ms 4

@sle_minion

Scenario:
Synchronize Devel-SUSE-Channel channel

3s 704ms 9

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

4s 297ms 9

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 209ms 9

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

4s 193ms 9

@sle_minion

Scenario:
Create an activation key with a channel

2s 358ms 2

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

1s 540ms 2

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

3s 35ms 2

@ssh_minion

Scenario:
Create an activation key with a channel for salt-ssh

2s 69ms 2

@ssh_minion

Scenario:
Create an activation key with a channel for salt-ssh via tunnel

1s 838ms 2

@proxy

Scenario:
Create an activation key for the proxy

1s 927ms 2

@build_host

Scenario:
Create an activation key for the build host

2s 636ms 3

@scc_credentials

Scenario:
Create an activation key for the terminal

2s 680ms 2

@scc_credentials @susemanager

Scenario:
Update SLE key with synced base product

< 1ms 20