Cucumber Feature Report

All Scenarios

201

Passed Scenarios

162

Failed Scenarios

0

Skipped Scenarios

39

Execution Time: 82m 17s 292ms

Expand All | Collapse All

Metadata

App Version: Uyuni/Head

Browser: Chrome

Platform: x86_64

Parallel: Disabled

Feature:Sanity checks 44s 113ms 10 2

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

Scenario:
The server is healthy

11s 737ms 19

Then "server" should have a FQDN 383ms

And reverse resolution should work for "server" 618ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@proxy

Scenario:
The proxy is healthy

4s 476ms 4

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

And reverse resolution should work for "proxy" 280ms

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

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

@sle_minion

Scenario:
The minion is healthy

6s 241ms 4

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

And reverse resolution should work for "sle_minion" 410ms

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

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

@build_host

Scenario:
The build host is healthy

3s 906ms 4

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

And reverse resolution should work for "build_host" 233ms

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

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

@ssh_minion

Scenario:
The SSH minion is healthy

6s 419ms 4

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

And reverse resolution should work for "ssh_minion" 449ms

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

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

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 232ms 4

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

And reverse resolution should work for "rhlike_minion" 207ms

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

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

@deblike_minion

Scenario:
The Debian-like minion is healthy

6s 76ms 4

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

And reverse resolution should work for "deblike_minion" 213ms

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

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

@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

716ms 1

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

@no_auth_registry

Scenario:
The registry without authentication is healthy

667ms 1

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

@custom_download_endpoint

Scenario:
The custom download endpoint is working

638ms 1

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

Feature:Very first settings 49s 72ms 6 2

In order to use the product
As the admin user
I want to create the organisation, the first users and set the HTTP proxy

Scenario:
Cleanup Salt files

666ms 1

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

@skip_if_containerized_server

Scenario:
Create admin user and first organization

< 1ms 12

Given I access the host the first time 0s

When I go to the home page 0s

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

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

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

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

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

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

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

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

And I click on "Create Organization" 0s

Then I am logged in 0s

Scenario:
Log in as admin user

39s 918ms 1

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

Scenario:
Wait for refresh of list of products to finish

3s 513ms 1

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

Scenario:
Create testing username

2s 216ms 12

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

And I follow "Create User" 596ms

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

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

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

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

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

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

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

And I click on "Create Login" 934ms

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

And I should see a "testing" link 13ms

Scenario:
Grant testing user administrative priviledges

1s 878ms 10

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

And I follow "testing" 529ms

And I check "role_org_admin" 86ms

And I check "role_system_group_admin" 79ms

And I check "role_channel_admin" 84ms

And I check "role_activation_key_admin" 83ms

And I check "role_config_admin" 84ms

And I click on "Update" 702ms

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

And I should see a "testing" text 74ms

@server_http_proxy

Scenario:
Setup HTTP proxy

< 1ms 9

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

Then I should see a "HTTP Proxy Hostname" text 0s

And I should see a "HTTP Proxy Username" text 0s

And I should see a "HTTP Proxy Password" text 0s

When I enter the address of the HTTP proxy as "HTTP Proxy Hostname" 0s

And I enter "suma3" as "HTTP Proxy Username" 0s

And I enter "P4$$w/ord With%and&" as "HTTP Proxy Password" 0s

And I click on "Save and Verify" 0s

Then HTTP proxy verification should have succeeded 0s

Scenario:
Detect latest Salt changes on the server

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

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

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

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

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

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

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

And I click on "Save Preferences" 642ms

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

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

3s 466ms 5

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

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

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

And I click on "Save Preferences" 671ms

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

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

Scenario:
Create a Kiwi user with image administrators rights

4s 422ms 2

New user kiwikiwi created with roles: image_admin

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

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

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

Scenario:
Create a Docker user with image administrators rights

2s 52ms 2

New user docker created with roles: image_admin

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

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

@no_auth_registry

Scenario:
Create an image store without credentials

3s 136ms 7

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

And I follow "Create" 554ms

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

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

And I click on "create-btn" 192ms

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

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

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

Scenario:
Log in as admin user

37s 605ms 1

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

Scenario:
Disable scheduled reposyncs

4s 700ms 5

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

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

And I choose "disabled" 70ms

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

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

Scenario:
Disable scheduled Cobbler syncs

4s 557ms 5

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

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

And I choose "disabled" 47ms

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

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

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

When I refresh SCC 30s 84ms

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

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

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

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

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

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

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

When I remove the mgr-sync cache file 682ms

And I execute mgr-sync refresh 1m 761ms

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

Feature:Synchronize products in the products page of the Setup Wizard 49m 2s 342ms 8 9

@scc_credentials

Scenario:
Refresh SCC

27s 879ms 1

When I refresh SCC 27s 879ms

@scc_credentials

Scenario:
Let the products page appear

2s 228ms 6

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

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

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

Then I should see a "Arch" text 121ms

And I should see a "Channels" text 123ms

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

@scc_credentials

Scenario:
Use the products and architecture filters

2s 373ms 7

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

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

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

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

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

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

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

3m 16s 866ms 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 543ms

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

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

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

@containerized_server @proxy @uyuni

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

1m 17s 259ms 2

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

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

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

@scc_credentials @uyuni @build_host

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

43m 12s 171ms 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
5 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-basesystem15-sp7-pool-x86_64 finished reposync
6 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
7 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
8 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
9 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
10 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
11 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
12 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
13 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-basesystem15-sp7-updates-x86_64 finished reposync
14 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
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
Channel sle-module-devtools15-sp7-updates-x86_64 finished reposync
19 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-devtools15-sp7-pool-x86_64 finished reposync
Channel sle-module-server-applications15-sp7-pool-x86_64 finished reposync
20 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-server-applications15-sp7-updates-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
Channel sle-module-desktop-applications15-sp7-updates-x86_64 finished reposync
25 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-desktop-applications15-sp7-pool-x86_64 finished reposync
26 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
Channel sle-module-python3-15-sp7-updates-x86_64 finished reposync
27 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-python3-15-sp7-pool-x86_64 finished reposync
All channels for sles15-sp7 have been fully synced

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 59ms

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

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

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

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

And I wait until all synchronized channels for "sles15-sp7" have finished 42m 51s 268ms

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

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

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

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

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

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

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

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

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

503ms 1

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

Scenario:
Add a fake base channel for x86_64

1s 674ms 10

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

And I follow "Create Channel" 326ms

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

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

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

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

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

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

And I click on "Create Channel" 593ms

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

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

973ms 10

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

And I follow "Create Channel" 321ms

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

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

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

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

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

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

And I click on "Create Channel" 55ms

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

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

And I follow "Create Channel" 321ms

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

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

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

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

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

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

And I click on "Create Channel" 552ms

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

Scenario:
Add a fake base channel for i586

1s 462ms 10

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

And I follow "Create Channel" 324ms

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

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

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

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

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

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

And I click on "Create Channel" 560ms

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

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

1s 368ms 10

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

And I follow "Create Channel" 240ms

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

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

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

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

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

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

And I click on "Create Channel" 57ms

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

Scenario:
Add a test base channel for x86_64

1s 336ms 10

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

And I follow "Create Channel" 272ms

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

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

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

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

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

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

And I click on "Create Channel" 495ms

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

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

1s 403ms 10

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

And I follow "Create Channel" 255ms

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

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

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

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

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

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

And I click on "Create Channel" 551ms

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

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

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

And I follow "Create Channel" 338ms

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

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

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

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

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

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

And I uncheck "gpg_check" 10s 85ms

And I click on "Create Channel" 503ms

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

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 366ms 10

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

And I follow "Create Channel" 270ms

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

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

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

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

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

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

And I click on "Create Channel" 529ms

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

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 449ms 10

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

And I follow "Create Channel" 351ms

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

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

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

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

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

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

And I click on "Create Channel" 525ms

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

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

505ms 1

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

Scenario:
Create a fake repository for distributions using RPM

1s 234ms 7

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

And I follow "Create Repository" 341ms

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

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

And I click on "Create Repository" 476ms

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

And I should see "metadataSigned" as checked 19ms

Scenario:
Disable metadata check for the fake RPM repository

11s 29ms 6

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

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

And I uncheck "metadataSigned" 10s 74ms

And I click on "Update Repository" 470ms

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

And I should see "metadataSigned" as unchecked 17ms

@rhlike_minion

Scenario:
Create a fake AppStream repository

1s 48ms 7

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

And I follow "Create Repository" 307ms

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

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

And I click on "Create Repository" 435ms

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

And I should see "metadataSigned" as checked 16ms

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

10s 884ms 6

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

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

And I uncheck "metadataSigned" 10s 74ms

And I click on "Update Repository" 425ms

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

And I should see "metadataSigned" as unchecked 15ms

@sle_minion

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

2s 43ms 9

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

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

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

And I click on "Update Channel" 65ms

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

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

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

And I click on "Save Repositories" 487ms

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

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

1s 992ms 9

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

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

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

And I click on "Update Channel" 55ms

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

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

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

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

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

@rhlike_minion

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

2s 634ms 9

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

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

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

And I click on "Update Channel" 554ms

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

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

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

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

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

@rhlike_minion

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

2s 605ms 9

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

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

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

And I click on "Update Channel" 556ms

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

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

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

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

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

Scenario:
Create a fake repository for i586

11s 67ms 7

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

And I follow "Create Repository" 230ms

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

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

And I uncheck "metadataSigned" 10s 85ms

And I click on "Create Repository" 450ms

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

Scenario:
Add the repository to the i586 channel

1s 505ms 9

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

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

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

And I click on "Update Channel" 67ms

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

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

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

And I click on "Save Repositories" 591ms

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

@sle_minion

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

1s 621ms 6

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

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

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

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

And I click on "Save Repositories" 996ms

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

@deblike_minion

Scenario:
Create a fake repository for Debian-like

1s 134ms 7

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

And I follow "Create Repository" 326ms

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

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

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

And I click on "Create Repository" 444ms

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

@deblike_minion

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

1s 315ms 6

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

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

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

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

And I click on "Save Repositories" 661ms

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

@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 26s 940ms 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

511ms 1

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

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 76ms 10

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

And I follow "Create Channel" 281ms

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

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

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

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

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

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

And I click on "Create Channel" 63ms

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

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

6s 391ms 1

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

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

897ms 10

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

And I follow "Create Channel" 266ms

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

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

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

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

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

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

And I click on "Create Channel" 58ms

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

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

4s 158ms 1

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

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

958ms 10

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

And I follow "Create Channel" 298ms

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

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

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

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

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

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

And I click on "Create Channel" 56ms

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

@deblike_minion

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

6s 961ms 1

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

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 409ms 10

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

And I follow "Create Channel" 274ms

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

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

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

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

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

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

And I click on "Create Channel" 506ms

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

@rhlike_minion

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

4s 573ms 1

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

Feature:Synchronize fake channels 50s 244ms 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

2s 438ms 2

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

And I enable source package syncing 2s 10ms

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

4s 547ms 9

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

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

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

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

And I follow "Sync" 348ms

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

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

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

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

@sle_minion

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

4s 902ms 2

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

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

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

3s 672ms 9

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

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

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

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

And I follow "Sync" 336ms

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

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

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

Scenario:
Synchronize Test-Child-Channel-x86_64 channel

4s 166ms 9

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

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

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

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

And I follow "Sync" 793ms

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

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

@sle_minion

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

4s 9ms 9

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

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

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

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

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

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

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

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

@deblike_minion

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

4s 265ms 9

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

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

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

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

And I follow "Sync" 875ms

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

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

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

@rhlike_minion

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

4s 304ms 9

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

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

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

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

And I follow "Sync" 871ms

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

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

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

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 239ms 9

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

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

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

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

And I follow "Sync" 701ms

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

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

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

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

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

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

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

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

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

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

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

Scenario:
Refresh the channel's repository data

6s 98ms 6

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

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

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

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

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

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

Scenario:
Cleanup disable source package syncing

1s 14ms 1

Then I disable source package syncing 1s 14ms

@skip_if_github_validation
Feature:Synchronize development channels 16s 406ms 4

In order to use the content provided inside the repositories of the dev channels
As admin
I want to synchronize the dev channels

@sle_minion

Scenario:
Synchronize Devel-SUSE-Channel channel

3s 815ms 9

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

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

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

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

And I follow "Sync" 424ms

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

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

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

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

4s 147ms 9

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

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

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

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

And I follow "Sync" 790ms

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

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

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

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 332ms 9

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

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

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

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

And I follow "Sync" 955ms

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

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

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

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

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

4s 110ms 9

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

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

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

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

And I follow "Sync" 702ms

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

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

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

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

Feature:Create activation keys 17s 746ms 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

478ms 1

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

@sle_minion

Scenario:
Create an activation key with a channel

1s 910ms 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 370ms

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

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

1s 562ms 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" 867ms

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

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

2s 707ms 2

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

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

@ssh_minion

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

2s 222ms 2

When I create an activation key with id "SUSE-SSH-KEY-x86_64", description "SUSE SSH Test Key x86_64", limit of 20 and contact method "ssh-push" 1s 208ms

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

@ssh_minion

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

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

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

@proxy

Scenario:
Create an activation key for the proxy

2s 53ms 2

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

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

@build_host

Scenario:
Create an activation key for the build host

2s 695ms 3

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

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

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

@scc_credentials

Scenario:
Create an activation key for the terminal

2s 245ms 2

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

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

Feature:Update activation keys 24s 233ms 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

499ms 1

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 640ms

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

@scc_credentials @susemanager

Scenario:
Update SLE SSH key with synced base product

< 1ms 14

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

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

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

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

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

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

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

And I click on "Update Activation Key" 0s

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

@uyuni

Scenario:
Update openSUSE Tumbleweed SSH key with synced base product

2s 240ms 10

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 565ms

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

@scc_credentials @susemanager

Scenario:
Update SLE SSH tunnel key with synced base product

< 1ms 14

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

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

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

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

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

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

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

And I click on "Update Activation Key" 0s

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

@uyuni

Scenario:
Update openSUSE Tumbleweed SSH tunnel key with synced base product

2s 137ms 10

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 570ms

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

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

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

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

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

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

And I wait for child channels to appear 526ms

And I include the recommended child channels 185ms

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

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

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

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

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

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

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

And I wait until "SLE-Module-Systems-Management-15-SP7-Pool for x86_64" has been checked 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" 667ms

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

@scc_credentials @uyuni @build_host

Scenario:
Update build host key with Uyuni client tools

2s 240ms 9

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

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

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

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

And I wait for child channels to appear 314ms

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

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

And I click on "Update Activation Key" 593ms

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

@skip_if_github_validation @scc_credentials @uyuni @build_host

Scenario:
Update build host key with dev child channel

2s 68ms 9

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

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

And I wait for child channels to appear 862ms

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

And I wait for child channels to appear 313ms

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

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

And I click on "Update Activation Key" 564ms

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

@scc_credentials @build_host

Scenario:
Update terminal key with synced base product

3s 37ms 16

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

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

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

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

And I wait for child channels to appear 519ms

And I include the recommended child channels 165ms

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 606ms

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

@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

2s 81ms 6

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

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

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

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

And I click on "Update Activation Key" 623ms

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

@skip_if_github_validation @deblike_minion

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

1s 868ms 6

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

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

And I wait for child channels to appear 930ms

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

And I click on "Update Activation Key" 630ms

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

@skip_if_github_validation @rhlike_minion

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

2s 372ms 6

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

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

And I wait for child channels to appear 980ms

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

And I click on "Update Activation Key" 1s 82ms

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

Feature:Create bootstrap repositories 9s 64ms 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 457ms 1

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

@sle_minion

Scenario:
Create the bootstrap repository for SUSE Minion

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

@proxy

Scenario:
Create the bootstrap repository for Proxy

2s 89ms 1

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

@build_host

Scenario:
Create the bootstrap repository for Build Host

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

@containerized_server @scope_containerized_proxy @proxy
Feature:Setup containerized proxy 3m 26s 465ms 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 562ms 1

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

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

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

Scenario:
Bootstrap the proxy host as a salt minion

35s 594ms 9

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 65ms

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

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

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

Scenario:
Generate containerized proxy configuration

10s 793ms 2

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

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

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

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

Scenario:
Wait until containerized proxy service is active

3s 949ms 10

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

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

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

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

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

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

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

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

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

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

Scenario:
The containerized proxy should be registered automatically

746ms 2

When I follow the left menu "Systems" 58ms

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

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

11s 105ms 3

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

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

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

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

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

Scenario:
Adapt the proxy for Retail

< 1ms 3

When I rename the proxy for Retail 0s

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

And I restart all proxy containers 0s

Scenario:
Check the branch network

< 1ms 2

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

And name resolution should work on private network 0s

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

< 1ms 11

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

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

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

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

And I click on "Schedule Hardware Refresh" 0s

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

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

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

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

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

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

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

Scenario:
Log in as admin user

38s 584ms 1

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

Scenario:
Bootstrap a Debian-like minion

2m 19s 235ms 14

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

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 104ms

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

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

And I wait until I see the name of "deblike_minion", refreshing the page 18s 231ms

And I wait until onboarding is completed for "deblike_minion" 1m 13s 102ms

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

@proxy

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

2s 446ms 4

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

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

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

Then I should see "proxy" short hostname 162ms

@proxy

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

2s 182ms 4

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

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

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

Then I should see "deblike_minion" hostname 196ms

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

23s 983ms 11

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

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

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

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

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

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

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

And I click on "Next" 111ms

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

When I click on "Confirm" 90ms

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

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

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

461ms 1

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

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

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

52s 402ms 2

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

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

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

Scenario:
Log in as admin user

39s 718ms 1

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

Scenario:
Bootstrap a Red Hat-like minion

2m 7s 868ms 13

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

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 110ms

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

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

And I wait until I see the name of "rhlike_minion", refreshing the page 32s 202ms

And I wait until onboarding is completed for "rhlike_minion" 54s 220ms

@proxy

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

1s 678ms 4

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

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

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

Then I should see "proxy" short hostname 133ms

@proxy

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

3s 216ms 4

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

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

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

Then I should see "rhlike_minion" hostname 204ms

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

24s 541ms 11

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

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

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

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

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

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

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

And I click on "Next" 124ms

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

When I click on "Confirm" 134ms

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

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

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

382ms 1

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

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

* Wed Jan 14 2026 Marek Czernek
- Use internal deb classes instead of external aptsource lib
* Drop dependency on saltbundlepy-apt
- Speed up wheel key.finger call (bsc#1240532)
- Add security patches (bsc#1254903,bsc#1254905,bsc#1254904)

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

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

52s 598ms 2

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

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

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

Scenario:
Clean up sumaform leftovers on build host

8s 721ms 1

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

Scenario:
Log in as admin user

37s 760ms 1

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

Scenario:
Bootstrap a build host

50s 664ms 10

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

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 113ms

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

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

1m 51s 587ms 6

It took 3 seconds to contact the minion

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

Then I should see a "accepted" text 632ms

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

And I wait at most 500 seconds until I see the name of "build_host", refreshing the page 1m 10s 472ms

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

Then the Salt master can reach "build_host" 2s 72ms

@proxy

Scenario:
Check connection from build host to proxy

1s 143ms 4

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

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

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

Then I should see "proxy" short hostname 85ms

@proxy

Scenario:
Check registration on build host of minion

1s 104ms 4

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

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

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

Then I should see "build_host" hostname 119ms

Scenario:
Detect latest Salt changes on the SLES build host

620ms 1

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

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

* Wed Jan 14 2026 marek.czernek@suse.com
- Use internal deb classes instead of external aptsource lib
* Drop dependency on saltbundlepy-apt
- Speed up wheel key.finger call (bsc#1240532)
- Add security patches (bsc#1254903,bsc#1254905,bsc#1254904)

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

Scenario:
Check that the build host is a build host

1s 749ms 3

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

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

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

Scenario:
Check events history for failures on SLES build host

1m 12s 310ms 2

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

Then I check for failed events on history event page 1m 11s 176ms

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

Scenario:
Clean up sumaform leftovers on SLES minion

9s 949ms 1

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

Scenario:
Log in as admin user

38s 938ms 1

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

Scenario:
Bootstrap a SLES minion

43s 703ms 11

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

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 163ms

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

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

Scenario:
Check the new bootstrapped minion in System List page

1m 35s 593ms 8

It took 4 seconds to contact the minion

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

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

Then I should see a "accepted" text 140ms

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

And I wait until I see the name of "sle_minion", refreshing the page 1m 12s 738ms

And I wait until onboarding is completed for "sle_minion" 17s 969ms

Then the Salt master can reach "sle_minion" 3s 698ms

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

Given I am on the Systems overview page of this "sle_minion" 1s 163ms

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

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

Then I should see "proxy" short hostname 131ms

@proxy

Scenario:
Check registration on proxy of minion

2s 66ms 4

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

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

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

Then I should see "sle_minion" hostname 120ms

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

Scenario:
Clean up sumaform leftovers on SLES SSH minion

9s 925ms 1

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

Scenario:
Log in as admin user

38s 593ms 1

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

Scenario:
Bootstrap a SLES SSH minion

2m 32s 698ms 11

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

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

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

When I check "manageWithSSH" 187ms

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

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

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

And I click on "Bootstrap" 104ms

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

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

And I wait until I see the name of "ssh_minion", refreshing the page 58s 731ms

And I wait until onboarding is completed for "ssh_minion" 34s 950ms

@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 316ms 4

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

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

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

Then I should see "proxy" short hostname 79ms

@proxy

Scenario:
Check registration on proxy of SSH minion

1s 493ms 4

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

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

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

Then I should see "ssh_minion" hostname 141ms

@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 20s 439ms 5

Scenario:
Call spacewalk-debug on server

16s 304ms 1

When I execute spacewalk-debug on the server 16s 304ms

Scenario:
Check the tomcat logs on server

714ms 1

Then the tomcat logs should not contain errors 714ms

Scenario:
Check salt event log for failures on server

2s 48ms 1

Then the salt event log on server should contain no failures 2s 48ms

Scenario:
Check the taskomatic logs on server

685ms 1

Then the taskomatic logs should not contain errors 685ms

Scenario:
Check for out of memory errors

685ms 1

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

Feature:Debug the clients after the testsuite has run 1m 40s 999ms 1

Scenario:
Extract the logs from all our clients

1m 40s 999ms 1

When I extract the log files from all our active nodes 1m 40s 999ms

@srv_scc_access_logging
Feature:Test for excessive SCC accesses < 1ms 2

Scenario:
Count UI SCC accesses in rhn_web_ui.log

< 1ms 1

Then the word "scc.suse.com" does not occur more than 100 times in "/var/log/rhn/rhn_web_ui.log" on "server" 0s

Scenario:
Count Taskomatic SCC accesses in rhn_taskomatic_daemon.log

< 1ms 1

Then the word "scc.suse.com" does not occur more than 50 times in "/var/log/rhn/rhn_taskomatic_daemon.log" on "server" 0s

All Scenarios

201

Passed Scenarios

162

Failed Scenarios

0

Skipped Scenarios

39

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

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

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

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

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

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

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

@custom_download_endpoint Scenario:The custom download endpoint is working 638ms 1

@skip_if_containerized_server Scenario:Create admin user and first organization < 1ms 12

@server_http_proxy Scenario:Setup HTTP proxy < 1ms 9

@scc_credentials @no_mirror Scenario:Enter valid SCC credentials < 1ms 6

@no_auth_registry Scenario:Create an image store without credentials 3s 136ms 7

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

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

@scc_credentials Scenario:Refresh SCC 27s 879ms 1

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

@scc_credentials Scenario:Use the products and architecture filters 2s 373ms 7

@scc_credentials @susemanager Scenario:View the channels list in the products page < 1ms 9

@scc_credentials @susemanager Scenario:Synchronize SLES 15 SP7 product with recommended sub-products, including MLM Client Tools < 1ms 30

@uyuni Scenario:Partially add openSUSE Tumbleweed product, only including the required packages to generate the bootstrap repository 3m 16s 866ms 4

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

@scc_credentials @uyuni @build_host Scenario:Synchronize SLES 15 SP7 product with recommended sub-products for Retail feature 43m 12s 171ms 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 563ms 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 446ms 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 517ms 11

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

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

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

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

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

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

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

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

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

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

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

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

@uyuni @build_host Scenario:Create a custom channel for Build Host 897ms 10

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

@deblike_minion Scenario:Create a custom channel for Debian-like minions 958ms 10

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

@rhlike_minion Scenario:Create a custom channel for RH-like minions 1s 409ms 10

@rhlike_minion Scenario:Create custom repositories inside the RH-like custom channel 4s 573ms 1

@sle_minion Scenario:Synchronize Fake-RPM-SUSE-Channel channel 4s 547ms 9

@sle_minion Scenario:Verify state of Fake-RPM-SUSE-Channel channel 4s 902ms 2

@skip_if_github_validation Scenario:Synchronize Fake-Child-Channel-i586 channel 3s 672ms 9

@sle_minion Scenario:Synchronize Fake-Child-Channel-SUSE-like channel 4s 9ms 9

@deblike_minion Scenario:Synchronize Fake-Base-Channel-Debian-like channel 4s 265ms 9

@rhlike_minion Scenario:Synchronize Fake-Base-Channel-RH-like channel 4s 304ms 9

@rhlike_minion Scenario:Synchronize Fake-Base-Channel-AppStream channel 4s 239ms 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 406ms 4

@sle_minion Scenario:Synchronize Devel-SUSE-Channel channel 3s 815ms 9

@deblike_minion Scenario:Synchronize Devel-Debian-like-Channel channel 4s 147ms 9

@rhlike_minion Scenario:Synchronize Devel-RH-like-Channel channel 4s 332ms 9

@build_host @uyuni Scenario:Synchronize Devel-Build-Host-Channel channel 4s 110ms 9

@sle_minion Scenario:Create an activation key with a channel 1s 910ms 2

@proxy

Scenario:
The proxy is healthy

4s 476ms 4

@sle_minion

Scenario:
The minion is healthy

6s 241ms 4

@build_host

Scenario:
The build host is healthy

3s 906ms 4

@ssh_minion

Scenario:
The SSH minion is healthy

6s 419ms 4

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 232ms 4

@deblike_minion

Scenario:
The Debian-like minion is healthy

6s 76ms 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

716ms 1

@no_auth_registry

Scenario:
The registry without authentication is healthy

667ms 1

@custom_download_endpoint

Scenario:
The custom download endpoint is working

638ms 1

@skip_if_containerized_server

Scenario:
Create admin user and first organization

< 1ms 12

@server_http_proxy

Scenario:
Setup HTTP proxy

< 1ms 9

@scc_credentials @no_mirror

Scenario:
Enter valid SCC credentials

< 1ms 6

@no_auth_registry

Scenario:
Create an image store without credentials

3s 136ms 7

@scc_credentials
Feature:List available channels and enable them 1m 38s 223ms 5 1

@proxy @susemanager

Scenario:
List all products for SUSE Multi-Linux Manager

< 1ms 6

@scc_credentials

Scenario:
Refresh SCC

27s 879ms 1

@scc_credentials

Scenario:
Let the products page appear

2s 228ms 6

@scc_credentials

Scenario:
Use the products and architecture filters

2s 373ms 7

@scc_credentials @susemanager

Scenario:
View the channels list in the products page

< 1ms 9

@scc_credentials @susemanager

Scenario:
Synchronize SLES 15 SP7 product with recommended sub-products, including MLM Client Tools

< 1ms 30

@uyuni

Scenario:
Partially add openSUSE Tumbleweed product, only including the required packages to generate the bootstrap repository

3m 16s 866ms 4

@containerized_server @proxy @uyuni

Scenario:
Add Uyuni Proxy product for Tumbleweed, including Uyuni Client Tools

1m 17s 259ms 2

@scc_credentials @uyuni @build_host

Scenario:
Synchronize SLES 15 SP7 product with recommended sub-products for Retail feature

43m 12s 171ms 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 563ms 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 446ms 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 517ms 11

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 366ms 10

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 449ms 10

@rhlike_minion

Scenario:
Create a fake AppStream repository

1s 48ms 7

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

10s 884ms 6

@sle_minion

Scenario:
Add the fake RPM repository to the SUSE fake child channel

2s 43ms 9

@rhlike_minion

Scenario:
Add the fake RPM repository to the RedHat-like base channel

2s 634ms 9

@rhlike_minion

Scenario:
Add the fake AppStream repository to the AppStream base channel

2s 605ms 9

@sle_minion

Scenario:
Add the repository to the SUSE-like child channel

1s 621ms 6

@deblike_minion

Scenario:
Create a fake repository for Debian-like

1s 134ms 7

@deblike_minion

Scenario:
Add the repository to the Debian-like base channel

1s 315ms 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 26s 940ms 9

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 76ms 10

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

6s 391ms 1

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

897ms 10

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

4s 158ms 1

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

958ms 10

@deblike_minion

Scenario:
Create custom repositories inside the Debian-like custom channel

6s 961ms 1

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 409ms 10

@rhlike_minion

Scenario:
Create custom repositories inside the RH-like custom channel

4s 573ms 1

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

4s 547ms 9

@sle_minion

Scenario:
Verify state of Fake-RPM-SUSE-Channel channel

4s 902ms 2

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

3s 672ms 9

@sle_minion

Scenario:
Synchronize Fake-Child-Channel-SUSE-like channel

4s 9ms 9

@deblike_minion

Scenario:
Synchronize Fake-Base-Channel-Debian-like channel

4s 265ms 9

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-RH-like channel

4s 304ms 9

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 239ms 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 406ms 4

@sle_minion

Scenario:
Synchronize Devel-SUSE-Channel channel

3s 815ms 9

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

4s 147ms 9

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 332ms 9

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

4s 110ms 9

@sle_minion

Scenario:
Create an activation key with a channel

1s 910ms 2

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

1s 562ms 2

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

2s 707ms 2

@ssh_minion

Scenario:
Create an activation key with a channel for salt-ssh

2s 222ms 2

@ssh_minion

Scenario:
Create an activation key with a channel for salt-ssh via tunnel

1s 871ms 2

@proxy

Scenario:
Create an activation key for the proxy

2s 53ms 2

@build_host

Scenario:
Create an activation key for the build host

2s 695ms 3

@scc_credentials

Scenario:
Create an activation key for the terminal

2s 245ms 2

@scc_credentials @susemanager

Scenario:
Update SLE key with synced base product

< 1ms 20