Cucumber Feature Report

All Scenarios

201

Passed Scenarios

155

Failed Scenarios

7

Skipped Scenarios

39

Execution Time: 87m 28s 873ms

Expand All | Collapse All

Metadata

App Version: Uyuni/Head

Browser: Chrome

Platform: x86_64

Parallel: Disabled

Feature:Sanity checks 44s 142ms 10 2

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

Scenario:
The server is healthy

11s 658ms 19

Then "server" should have a FQDN 380ms

And reverse resolution should work for "server" 608ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@proxy

Scenario:
The proxy is healthy

4s 446ms 4

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

And reverse resolution should work for "proxy" 278ms

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

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

@sle_minion

Scenario:
The minion is healthy

6s 465ms 4

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

And reverse resolution should work for "sle_minion" 424ms

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

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

@build_host

Scenario:
The build host is healthy

3s 958ms 4

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

And reverse resolution should work for "build_host" 293ms

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

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

@ssh_minion

Scenario:
The SSH minion is healthy

6s 364ms 4

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

And reverse resolution should work for "ssh_minion" 438ms

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

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

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 191ms 4

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

And reverse resolution should work for "rhlike_minion" 191ms

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

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

@deblike_minion

Scenario:
The Debian-like minion is healthy

6s 137ms 4

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

And reverse resolution should work for "deblike_minion" 217ms

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

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

@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

641ms 1

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

@no_auth_registry

Scenario:
The registry without authentication is healthy

643ms 1

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

@custom_download_endpoint

Scenario:
The custom download endpoint is working

634ms 1

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

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

633ms 1

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

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

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

Scenario:
Wait for refresh of list of products to finish

3s 646ms 1

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

Scenario:
Create testing username

2s 127ms 12

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

And I follow "Create User" 583ms

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

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

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

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

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

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

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

And I click on "Create Login" 811ms

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

And I should see a "testing" link 11ms

Scenario:
Grant testing user administrative priviledges

1s 712ms 10

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

And I follow "testing" 541ms

And I check "role_org_admin" 79ms

And I check "role_system_group_admin" 76ms

And I check "role_channel_admin" 75ms

And I check "role_activation_key_admin" 75ms

And I check "role_config_admin" 74ms

And I click on "Update" 558ms

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

And I should see a "testing" text 75ms

@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

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

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

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

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 403ms 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 412ms 5

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

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

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

And I click on "Save Preferences" 679ms

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

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

2s 990ms 5

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

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

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

And I click on "Save Preferences" 627ms

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

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

Scenario:
Create a Kiwi user with image administrators rights

4s 60ms 2

New user kiwikiwi created with roles: image_admin

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

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

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

Scenario:
Create a Docker user with image administrators rights

1s 995ms 2

New user docker created with roles: image_admin

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

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

@no_auth_registry

Scenario:
Create an image store without credentials

2s 943ms 7

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

And I follow "Create" 501ms

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

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

And I click on "create-btn" 165ms

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

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

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

Scenario:
Log in as admin user

37s 558ms 1

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

Scenario:
Disable scheduled reposyncs

4s 621ms 5

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

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

And I choose "disabled" 53ms

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

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

Scenario:
Disable scheduled Cobbler syncs

4s 581ms 5

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

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

And I choose "disabled" 44ms

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

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

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

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

Scenario:
List available channels

32s 738ms 5

When I refresh SCC 30s 458ms

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

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

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

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

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

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

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

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

When I remove the mgr-sync cache file 663ms

And I execute mgr-sync refresh 1m 760ms

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

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

@scc_credentials

Scenario:
Refresh SCC

27s 664ms 1

When I refresh SCC 27s 664ms

@scc_credentials

Scenario:
Let the products page appear

2s 962ms 6

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

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

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

Then I should see a "Arch" text 122ms

And I should see a "Channels" text 120ms

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

@scc_credentials

Scenario:
Use the products and architecture filters

2s 442ms 7

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

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

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

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

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

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

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

@scc_credentials @susemanager

Scenario:
View the channels list in the products page

< 1ms 9

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

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

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

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

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

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

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

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

When I close the modal dialog 0s

@scc_credentials @susemanager

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

< 1ms 30

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

Then the SLE15 SP7 product should be added 0s

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

@uyuni

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

1m 59s 26ms 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 580ms

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

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

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

@containerized_server @proxy @uyuni

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

1m 25s 274ms 2

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

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

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

@scc_credentials @uyuni @build_host

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

39m 29s 445ms 20

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 53ms

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

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

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

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

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

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

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

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

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

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

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

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

@scc_credentials @skip_if_github_validation

Scenario:
Report the synchronization duration for SLES 15 SP7

< 1ms 1

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

Feature:Create fake channels 24s 202ms 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

489ms 1

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

Scenario:
Add a fake base channel for x86_64

1s 767ms 10

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

And I follow "Create Channel" 328ms

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

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

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

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

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

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

And I click on "Create Channel" 609ms

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

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

1s 62ms 10

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

And I follow "Create Channel" 303ms

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

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

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

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

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

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

And I click on "Create Channel" 54ms

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

@sle_minion

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

1s 483ms 10

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

And I follow "Create Channel" 242ms

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

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

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

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

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

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

And I click on "Create Channel" 569ms

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

Scenario:
Add a fake base channel for i586

1s 576ms 10

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

And I follow "Create Channel" 315ms

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

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

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

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

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

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

And I click on "Create Channel" 570ms

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

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

1s 44ms 10

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

And I follow "Create Channel" 315ms

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

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

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

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

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

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

And I click on "Create Channel" 55ms

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

Scenario:
Add a test base channel for x86_64

1s 545ms 10

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

And I follow "Create Channel" 319ms

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

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

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

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

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

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

And I click on "Create Channel" 569ms

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

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

1s 575ms 10

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

And I follow "Create Channel" 328ms

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

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

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

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

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

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

And I click on "Create Channel" 534ms

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

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

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

And I follow "Create Channel" 324ms

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

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

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

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

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

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

And I uncheck "gpg_check" 10s 76ms

And I click on "Create Channel" 63ms

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

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 501ms 10

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

And I follow "Create Channel" 341ms

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

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

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

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

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

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

And I click on "Create Channel" 493ms

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

@rhlike_minion

Scenario:
Add a fake AppStream base channel

988ms 10

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

And I follow "Create Channel" 253ms

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

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

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

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

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

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

And I click on "Create Channel" 55ms

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

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

550ms 1

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

Scenario:
Create a fake repository for distributions using RPM

1s 225ms 7

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

And I follow "Create Repository" 317ms

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

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

And I click on "Create Repository" 507ms

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

And I should see "metadataSigned" as checked 18ms

Scenario:
Disable metadata check for the fake RPM repository

11s 24ms 6

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

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

And I uncheck "metadataSigned" 10s 71ms

And I click on "Update Repository" 498ms

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

And I should see "metadataSigned" as unchecked 15ms

@rhlike_minion

Scenario:
Create a fake AppStream repository

943ms 7

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

And I follow "Create Repository" 235ms

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

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

And I click on "Create Repository" 410ms

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

And I should see "metadataSigned" as checked 15ms

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

11s 7ms 6

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

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

And I uncheck "metadataSigned" 10s 73ms

And I click on "Update Repository" 477ms

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

And I should see "metadataSigned" as unchecked 15ms

@sle_minion

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

2s 94ms 9

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

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

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

And I click on "Update Channel" 549ms

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

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

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

And I click on "Save Repositories" 651ms

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

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

2s 668ms 9

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

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

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

And I click on "Update Channel" 541ms

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

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

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

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

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

@rhlike_minion

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

2s 754ms 9

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

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

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

And I click on "Update Channel" 592ms

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

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

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

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

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

@rhlike_minion

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

2s 637ms 9

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

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

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

And I click on "Update Channel" 556ms

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

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

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

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

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

Scenario:
Create a fake repository for i586

11s 42ms 7

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

And I follow "Create Repository" 230ms

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

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

And I uncheck "metadataSigned" 10s 65ms

And I click on "Create Repository" 459ms

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

Scenario:
Add the repository to the i586 channel

1s 877ms 9

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

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

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

And I click on "Update Channel" 492ms

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

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

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

And I click on "Save Repositories" 488ms

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

@sle_minion

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

1s 660ms 6

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

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

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

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

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

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

@deblike_minion

Scenario:
Create a fake repository for Debian-like

1s 137ms 7

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

And I follow "Create Repository" 317ms

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

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

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

And I click on "Create Repository" 470ms

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

@deblike_minion

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

1s 285ms 6

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

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

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

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

And I click on "Save Repositories" 660ms

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

@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 29s 464ms 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

527ms 1

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

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 855ms 10

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

And I follow "Create Channel" 380ms

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

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

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

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

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

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

And I click on "Create Channel" 669ms

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

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

6s 414ms 1

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

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 597ms 10

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

And I follow "Create Channel" 357ms

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

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

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

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

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

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

And I click on "Create Channel" 67ms

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

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

4s 294ms 1

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

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

1s 717ms 10

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

And I follow "Create Channel" 467ms

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

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

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

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

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

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

And I click on "Create Channel" 55ms

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

@deblike_minion

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

7s 133ms 1

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

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 533ms 10

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

And I follow "Create Channel" 265ms

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

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

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

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

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

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

And I click on "Create Channel" 532ms

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

@rhlike_minion

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

4s 389ms 1

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

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

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

And I enable source package syncing 1s 443ms

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

3s 871ms 9

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

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

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

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

And I follow "Sync" 342ms

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

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

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

@sle_minion

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

4s 775ms 2

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

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

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

3s 682ms 9

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

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

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

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

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

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

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

Scenario:
Synchronize Test-Child-Channel-x86_64 channel

4s 24ms 9

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

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

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

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

And I follow "Sync" 584ms

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

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

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

@sle_minion

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

24s 858ms 9

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

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

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

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

And I follow "Sync" 680ms

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

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

@deblike_minion

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

3s 702ms 9

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

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

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

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

And I follow "Sync" 339ms

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

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

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

@rhlike_minion

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

4s 252ms 9

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

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

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

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

And I follow "Sync" 779ms

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

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

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

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 176ms 9

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

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

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

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

And I follow "Sync" 787ms

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

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

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

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

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

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

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

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

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

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

Scenario:
Refresh the channel's repository data

5s 786ms 6

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

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

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

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

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

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

Scenario:
Cleanup disable source package syncing

1s 4ms 1

Then I disable source package syncing 1s 4ms

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

4s 26ms 9

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

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

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

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

And I follow "Sync" 607ms

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

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

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

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

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

4s 90ms 9

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

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

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

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

And I follow "Sync" 683ms

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

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

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

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

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 348ms 9

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

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

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

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

And I follow "Sync" 954ms

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

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

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

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

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

4s 424ms 9

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

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

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

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

And I follow "Sync" 870ms

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

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

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

Feature:Create activation keys 20s 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

514ms 1

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

@sle_minion

Scenario:
Create an activation key with a channel

2s 182ms 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 508ms

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

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

4s 453ms 2

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

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

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

1s 695ms 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" 936ms

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

@ssh_minion

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

2s 140ms 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" 969ms

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

@ssh_minion

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

2s 9ms 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" 874ms

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

@proxy

Scenario:
Create an activation key for the proxy

2s 213ms 2

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

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

@build_host

Scenario:
Create an activation key for the build host

2s 641ms 3

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

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

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

@scc_credentials

Scenario:
Create an activation key for the terminal

2s 149ms 2

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

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

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

437ms 1

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 627ms

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 570ms

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

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

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

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

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

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)" 543ms

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

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

And I click on "Update Activation Key" 620ms

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

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

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

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

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

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

And I wait for child channels to appear 545ms

And I include the recommended child channels 178ms

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

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

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 648ms

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

@scc_credentials @uyuni @build_host

Scenario:
Update build host key with Uyuni client tools

1s 728ms 9

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

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

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

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

And I wait for child channels to appear 308ms

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

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

And I click on "Update Activation Key" 54ms

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

@skip_if_github_validation @scc_credentials @uyuni @build_host

Scenario:
Update build host key with dev child channel

2s 148ms 9

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

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

And I wait for child channels to appear 937ms

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

And I wait for child channels to appear 308ms

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

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

And I click on "Update Activation Key" 568ms

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

@scc_credentials @build_host

Scenario:
Update terminal key with synced base product

2s 910ms 16

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

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

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

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

And I wait for child channels to appear 438ms

And I include the recommended child channels 164ms

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

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

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

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

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

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

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

@susemanager @scc_credentials @build_host

Scenario:
Update terminal key with normal SUSE fake channel

< 1ms 9

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

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

And I wait for child channels to appear 0s

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

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

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

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

And I click on "Update Activation Key" 0s

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

@pxeboot_minion @uyuni @scc_credentials @build_host

Scenario:
Update terminal key with specific fake channel

< 1ms 9

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

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

And I wait for child channels to appear 0s

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

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

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

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

And I click on "Update Activation Key" 0s

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

@skip_if_github_validation @sle_minion

Scenario:
Update SLE key with to include dev child channel

1s 890ms 6

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

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

And I wait for child channels to appear 974ms

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

And I click on "Update Activation Key" 619ms

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

@skip_if_github_validation @deblike_minion

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

1s 850ms 6

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

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

And I wait for child channels to appear 962ms

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

And I click on "Update Activation Key" 592ms

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

@skip_if_github_validation @rhlike_minion

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

1s 948ms 6

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

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

And I wait for child channels to appear 971ms

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

And I click on "Update Activation Key" 678ms

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

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

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

@sle_minion

Scenario:
Create the bootstrap repository for SUSE Minion

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

@proxy

Scenario:
Create the bootstrap repository for Proxy

2s 36ms 1

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

@build_host

Scenario:
Create the bootstrap repository for Build Host

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

@containerized_server @scope_containerized_proxy @proxy
Feature:Setup containerized proxy 3m 27s 829ms 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 565ms 1

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

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

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

Scenario:
Bootstrap the proxy host as a salt minion

35s 879ms 9

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

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

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

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

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

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

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

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 35s 257ms

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

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

Scenario:
Generate containerized proxy configuration

11s 389ms 2

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

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

Scenario:
Set up the containerized proxy service to support Avahi

< 1ms 1

Record not added - avahi domain was not detected

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

Scenario:
Run a containerized proxy

18s 52ms 1

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

Scenario:
Wait until containerized proxy service is active

4s 37ms 10

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

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

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

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

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

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

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

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

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

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

Scenario:
The containerized proxy should be registered automatically

744ms 2

When I follow the left menu "Systems" 58ms

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

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

10s 950ms 3

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

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

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

@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 10s 718ms 7

Scenario:
Log in as admin user

38s 291ms 1

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

Scenario:
Bootstrap a Debian-like minion

2m 14s 304ms 14

The hostname of deblike_minion is uyuni-master-deblike-minion.sumaci.aws
* Mon Jan 19 2026 Marek Czernek
- Make syntax in httputil_test compatible with Python 3.6
- Fix KeyError in postgres module with PostgreSQL 17 (bsc#1254325)
- Added:
* fix-tornado-s-httputil_test-syntax-for-python-3.6.patch
* backport-add-maintain-m-privilege-to-postgres-module.patch
* Wed Jan 14 2026 Marek Czernek
- Use internal deb classes instead of external aptsource lib
* Drop dependency on saltbundlepy-apt
- Speed up wheel key.finger call (bsc#1240532)
- Add security patches (bsc#1254903,bsc#1254905,bsc#1254904)
- Simplify and speed up utils.find_json function (bsc#1246130)
- Added:
* use-internal-salt.utils.pkg.deb-classes-instead-of-a.patch
* speedup-wheel-key.finger-call-bsc-1240532-713.patch

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 99ms

And I wait until I see "Bootstrap process initiated." text 38s 470ms

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

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

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

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

@proxy

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

1s 77ms 4

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

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

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

Then I should see "proxy" short hostname 77ms

@proxy

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

1s 79ms 4

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

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

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

Then I should see "deblike_minion" hostname 105ms

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

23s 100ms 11

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

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

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

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

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

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

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

And I click on "Next" 166ms

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

When I click on "Confirm" 96ms

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

And I wait until event "Subscribe channels scheduled by admin" is completed 20s 302ms

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

475ms 1

* Mon Jan 19 2026 Marek Czernek
- Make syntax in httputil_test compatible with Python 3.6
- Fix KeyError in postgres module with PostgreSQL 17 (bsc#1254325)
- Added:
* fix-tornado-s-httputil_test-syntax-for-python-3.6.patch
* backport-add-maintain-m-privilege-to-postgres-module.patch
* Wed Jan 14 2026 Marek Czernek
- Use internal deb classes instead of external aptsource lib
* Drop dependency on saltbundlepy-apt
- Speed up wheel key.finger call (bsc#1240532)
- Add security patches (bsc#1254903,bsc#1254905,bsc#1254904)
- Simplify and speed up utils.find_json function (bsc#1246130)
- Added:
* use-internal-salt.utils.pkg.deb-classes-instead-of-a.patch
* speedup-wheel-key.finger-call-bsc-1240532-713.patch

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

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

52s 390ms 2

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

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

@rhlike_minion
Feature:Bootstrap a Red Hat-like minion and do some basic operations on it 3m 50s 948ms 7

Scenario:
Log in as admin user

38s 1ms 1

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

Scenario:
Bootstrap a Red Hat-like minion

1m 53s 695ms 13

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

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 83ms

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

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

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

And I wait until onboarding is completed for "rhlike_minion" 13s 473ms

@proxy

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

1s 338ms 4

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

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

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

Then I should see "proxy" short hostname 89ms

@proxy

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

1s 379ms 4

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

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

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

Then I should see "rhlike_minion" hostname 165ms

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

22s 816ms 11

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

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

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

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

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

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

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

And I click on "Next" 69ms

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

When I click on "Confirm" 84ms

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

And I wait until event "Subscribe channels scheduled by admin" is completed 20s 675ms

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

339ms 1

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

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

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

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

53s 376ms 2

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

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

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

Scenario:
Clean up sumaform leftovers on build host

8s 263ms 1

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

Scenario:
Log in as admin user

37s 841ms 1

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

Scenario:
Bootstrap a build host

4m 28s 436ms 10 1

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

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 90ms

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

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

14s 77ms Show Info +

17:05:49:000 - 17:10:04:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/systems/bootstrap

Screenshot +

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

8m 34s 454ms 4 2 1

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

Then I should see a "accepted" text 262ms

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

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

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

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

Then the Salt master can reach "build_host" 0s

13s 893ms Show Info +

17:10:18:000 - 17:18:39:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/systems/list/all

Screenshot +

@proxy

Scenario:
Check connection from build host to proxy

13s 906ms 1 3 1

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

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

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

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

Then I should see "proxy" short hostname 0s

13s 581ms Show Info +

17:18:53:000 - 17:18:53:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/systems/list/all

Screenshot +

@proxy

Scenario:
Check registration on build host of minion

24s 550ms 4 1

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

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

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

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

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

13s 511ms Show Info +

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

Screenshot +

Scenario:
Detect latest Salt changes on the SLES build host

14s 216ms 1 1

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

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

13s 687ms Show Info +

17:19:32:000 - 17:19:33:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/ProxyClients.do?sid=1000010000&

Screenshot +

Scenario:
Check that the build host is a build host

13s 817ms 1 2 1

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

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

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

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

13s 512ms Show Info +

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

Screenshot +

Scenario:
Check events history for failures on SLES build host

13s 747ms 1 1 1

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

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

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

13s 447ms Show Info +

17:20:00:000 - 17:20:01:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/ProxyClients.do?sid=1000010000&

Screenshot +

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

Scenario:
Clean up sumaform leftovers on SLES minion

10s 190ms 1

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

Scenario:
Log in as admin user

39s 72ms 1

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

Scenario:
Bootstrap a SLES minion

44s 884ms 11

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

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 99ms

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

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

Scenario:
Check the new bootstrapped minion in System List page

1m 31s 670ms 8

It took 2 seconds to contact the minion

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

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

Then I should see a "accepted" text 113ms

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

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

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

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

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

1s 364ms 4

Given I am on the Systems overview page of this "sle_minion" 931ms

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

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

Then I should see "proxy" short hostname 130ms

@proxy

Scenario:
Check registration on proxy of minion

1s 450ms 4

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

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

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

Then I should see "sle_minion" hostname 184ms

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

Scenario:
Clean up sumaform leftovers on SLES SSH minion

10s 483ms 1

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

Scenario:
Log in as admin user

38s 320ms 1

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

Scenario:
Bootstrap a SLES SSH minion

2m 33s 540ms 11

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

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

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

When I check "manageWithSSH" 147ms

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

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

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

And I click on "Bootstrap" 111ms

And I wait until I see "Bootstrap process initiated." text 53s 824ms

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

And I wait until I see the name of "ssh_minion", refreshing the page 31s 768ms

And I wait until onboarding is completed for "ssh_minion" 1m 2s 842ms

@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 225ms 4

Given I am on the Systems overview page of this "ssh_minion" 910ms

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

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

Then I should see "proxy" short hostname 117ms

@proxy

Scenario:
Check registration on proxy of SSH minion

1s 502ms 4

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

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

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

Then I should see "ssh_minion" hostname 135ms

@transactional_server
Feature:SELinux debugging < 1ms 1

In order for the server to behave correctly after a reboot
I want to be sure that there is no wrong SELinux label

Scenario:
No previous operation has created wrong SELinux label

< 1ms 1

Then files on container volumes should all have the proper SELinux label 0s

@new_issue
Feature:Debug the server after the testsuite has run 17s 545ms 5

Scenario:
Call spacewalk-debug on server

13s 690ms 1

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

Scenario:
Check the tomcat logs on server

628ms 1

Then the tomcat logs should not contain errors 628ms

Scenario:
Check salt event log for failures on server

1s 881ms 1

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

Scenario:
Check the taskomatic logs on server

671ms 1

Then the taskomatic logs should not contain errors 671ms

Scenario:
Check for out of memory errors

672ms 1

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

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

Scenario:
Extract the logs from all our clients

1m 30s 623ms 1

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

@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

155

Failed Scenarios

7

Skipped Scenarios

39

@proxy Scenario:The proxy is healthy 4s 446ms 4

@sle_minion Scenario:The minion is healthy 6s 465ms 4

@build_host Scenario:The build host is healthy 3s 958ms 4

@ssh_minion Scenario:The SSH minion is healthy 6s 364ms 4

@rhlike_minion Scenario:The Red Hat-like minion is healthy 3s 191ms 4

@deblike_minion Scenario:The Debian-like minion is healthy 6s 137ms 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 641ms 1

@no_auth_registry Scenario:The registry without authentication is healthy 643ms 1

@custom_download_endpoint Scenario:The custom download endpoint is working 634ms 1

@skip_if_containerized_server Scenario:Create admin user and first organization < 1ms 12

@server_http_proxy Scenario:Setup HTTP proxy < 1ms 9

@scc_credentials @no_mirror Scenario:Enter valid SCC credentials < 1ms 6

@no_auth_registry Scenario:Create an image store without credentials 2s 943ms 7

@scc_credentials Feature:List available channels and enable them 1m 38s 605ms 5 1

@proxy @susemanager Scenario:List all products for SUSE Multi-Linux Manager < 1ms 6

@scc_credentials Scenario:Refresh SCC 27s 664ms 1

@scc_credentials Scenario:Let the products page appear 2s 962ms 6

@scc_credentials Scenario:Use the products and architecture filters 2s 442ms 7

@scc_credentials @susemanager Scenario:View the channels list in the products page < 1ms 9

@scc_credentials @susemanager Scenario:Synchronize SLES 15 SP7 product with recommended sub-products, including MLM Client Tools < 1ms 30

@uyuni Scenario:Partially add openSUSE Tumbleweed product, only including the required packages to generate the bootstrap repository 1m 59s 26ms 4

@containerized_server @proxy @uyuni Scenario:Add Uyuni Proxy product for Tumbleweed, including Uyuni Client Tools 1m 25s 274ms 2

@scc_credentials @uyuni @build_host Scenario:Synchronize SLES 15 SP7 product with recommended sub-products for Retail feature 39m 29s 445ms 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 588ms 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 483ms 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 169ms 11

@rhlike_minion Scenario:Add a RedHat-like base channel 1s 501ms 10

@rhlike_minion Scenario:Add a fake AppStream base channel 988ms 10

@rhlike_minion Scenario:Create a fake AppStream repository 943ms 7

@rhlike_minion Scenario:Disable metadata check for the fake AppStream repository 11s 7ms 6

@sle_minion Scenario:Add the fake RPM repository to the SUSE fake child channel 2s 94ms 9

@rhlike_minion Scenario:Add the fake RPM repository to the RedHat-like base channel 2s 754ms 9

@rhlike_minion Scenario:Add the fake AppStream repository to the AppStream base channel 2s 637ms 9

@sle_minion Scenario:Add the repository to the SUSE-like child channel 1s 660ms 6

@deblike_minion Scenario:Create a fake repository for Debian-like 1s 137ms 7

@deblike_minion Scenario:Add the repository to the Debian-like base channel 1s 285ms 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 29s 464ms 9

@sle_minion Scenario:Create a custom channel for SUSE minions 1s 855ms 10

@sle_minion Scenario:Create custom repositories inside the SUSE custom channel 6s 414ms 1

@uyuni @build_host Scenario:Create a custom channel for Build Host 1s 597ms 10

@uyuni @build_host Scenario:Create custom repositories inside the Build Host custom channel 4s 294ms 1

@deblike_minion Scenario:Create a custom channel for Debian-like minions 1s 717ms 10

@deblike_minion Scenario:Create custom repositories inside the Debian-like custom channel 7s 133ms 1

@rhlike_minion Scenario:Create a custom channel for RH-like minions 1s 533ms 10

@rhlike_minion Scenario:Create custom repositories inside the RH-like custom channel 4s 389ms 1

@sle_minion Scenario:Synchronize Fake-RPM-SUSE-Channel channel 3s 871ms 9

@sle_minion Scenario:Verify state of Fake-RPM-SUSE-Channel channel 4s 775ms 2

@skip_if_github_validation Scenario:Synchronize Fake-Child-Channel-i586 channel 3s 682ms 9

@sle_minion Scenario:Synchronize Fake-Child-Channel-SUSE-like channel 24s 858ms 9

@deblike_minion Scenario:Synchronize Fake-Base-Channel-Debian-like channel 3s 702ms 9

@rhlike_minion Scenario:Synchronize Fake-Base-Channel-RH-like channel 4s 252ms 9

@rhlike_minion Scenario:Synchronize Fake-Base-Channel-AppStream channel 4s 176ms 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 890ms 4

@sle_minion Scenario:Synchronize Devel-SUSE-Channel channel 4s 26ms 9

@deblike_minion Scenario:Synchronize Devel-Debian-like-Channel channel 4s 90ms 9

@rhlike_minion Scenario:Synchronize Devel-RH-like-Channel channel 4s 348ms 9

@build_host @uyuni Scenario:Synchronize Devel-Build-Host-Channel channel 4s 424ms 9

@sle_minion Scenario:Create an activation key with a channel 2s 182ms 2

@proxy

Scenario:
The proxy is healthy

4s 446ms 4

@sle_minion

Scenario:
The minion is healthy

6s 465ms 4

@build_host

Scenario:
The build host is healthy

3s 958ms 4

@ssh_minion

Scenario:
The SSH minion is healthy

6s 364ms 4

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 191ms 4

@deblike_minion

Scenario:
The Debian-like minion is healthy

6s 137ms 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

641ms 1

@no_auth_registry

Scenario:
The registry without authentication is healthy

643ms 1

@custom_download_endpoint

Scenario:
The custom download endpoint is working

634ms 1

@skip_if_containerized_server

Scenario:
Create admin user and first organization

< 1ms 12

@server_http_proxy

Scenario:
Setup HTTP proxy

< 1ms 9

@scc_credentials @no_mirror

Scenario:
Enter valid SCC credentials

< 1ms 6

@no_auth_registry

Scenario:
Create an image store without credentials

2s 943ms 7

@scc_credentials
Feature:List available channels and enable them 1m 38s 605ms 5 1

@proxy @susemanager

Scenario:
List all products for SUSE Multi-Linux Manager

< 1ms 6

@scc_credentials

Scenario:
Refresh SCC

27s 664ms 1

@scc_credentials

Scenario:
Let the products page appear

2s 962ms 6

@scc_credentials

Scenario:
Use the products and architecture filters

2s 442ms 7

@scc_credentials @susemanager

Scenario:
View the channels list in the products page

< 1ms 9

@scc_credentials @susemanager

Scenario:
Synchronize SLES 15 SP7 product with recommended sub-products, including MLM Client Tools

< 1ms 30

@uyuni

Scenario:
Partially add openSUSE Tumbleweed product, only including the required packages to generate the bootstrap repository

1m 59s 26ms 4

@containerized_server @proxy @uyuni

Scenario:
Add Uyuni Proxy product for Tumbleweed, including Uyuni Client Tools

1m 25s 274ms 2

@scc_credentials @uyuni @build_host

Scenario:
Synchronize SLES 15 SP7 product with recommended sub-products for Retail feature

39m 29s 445ms 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 588ms 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 483ms 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 169ms 11

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 501ms 10

@rhlike_minion

Scenario:
Add a fake AppStream base channel

988ms 10

@rhlike_minion

Scenario:
Create a fake AppStream repository

943ms 7

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

11s 7ms 6

@sle_minion

Scenario:
Add the fake RPM repository to the SUSE fake child channel

2s 94ms 9

@rhlike_minion

Scenario:
Add the fake RPM repository to the RedHat-like base channel

2s 754ms 9

@rhlike_minion

Scenario:
Add the fake AppStream repository to the AppStream base channel

2s 637ms 9

@sle_minion

Scenario:
Add the repository to the SUSE-like child channel

1s 660ms 6

@deblike_minion

Scenario:
Create a fake repository for Debian-like

1s 137ms 7

@deblike_minion

Scenario:
Add the repository to the Debian-like base channel

1s 285ms 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 29s 464ms 9

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 855ms 10

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

6s 414ms 1

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 597ms 10

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

4s 294ms 1

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

1s 717ms 10

@deblike_minion

Scenario:
Create custom repositories inside the Debian-like custom channel

7s 133ms 1

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 533ms 10

@rhlike_minion

Scenario:
Create custom repositories inside the RH-like custom channel

4s 389ms 1

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

3s 871ms 9

@sle_minion

Scenario:
Verify state of Fake-RPM-SUSE-Channel channel

4s 775ms 2

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

3s 682ms 9

@sle_minion

Scenario:
Synchronize Fake-Child-Channel-SUSE-like channel

24s 858ms 9

@deblike_minion

Scenario:
Synchronize Fake-Base-Channel-Debian-like channel

3s 702ms 9

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-RH-like channel

4s 252ms 9

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 176ms 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 890ms 4

@sle_minion

Scenario:
Synchronize Devel-SUSE-Channel channel

4s 26ms 9

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

4s 90ms 9

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 348ms 9

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

4s 424ms 9

@sle_minion

Scenario:
Create an activation key with a channel

2s 182ms 2

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

4s 453ms 2

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

1s 695ms 2

@ssh_minion

Scenario:
Create an activation key with a channel for salt-ssh

2s 140ms 2

@ssh_minion

Scenario:
Create an activation key with a channel for salt-ssh via tunnel

2s 9ms 2

@proxy

Scenario:
Create an activation key for the proxy

2s 213ms 2

@build_host

Scenario:
Create an activation key for the build host

2s 641ms 3

@scc_credentials

Scenario:
Create an activation key for the terminal

2s 149ms 2

@scc_credentials @susemanager

Scenario:
Update SLE key with synced base product

< 1ms 20