Cucumber Feature Report

All Scenarios

201

Passed Scenarios

133

Failed Scenarios

29

Skipped Scenarios

39

Execution Time: 77m 2s 734ms

Expand All | Collapse All

Metadata

App Version: Uyuni/Head

Browser: Chrome

Platform: x86_64

Parallel: Disabled

Feature:Sanity checks 46s 132ms 10 2

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

Scenario:
The server is healthy

11s 777ms 19

Then "server" should have a FQDN 379ms

And reverse resolution should work for "server" 614ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@proxy

Scenario:
The proxy is healthy

4s 444ms 4

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

And reverse resolution should work for "proxy" 274ms

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

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

@sle_minion

Scenario:
The minion is healthy

7s 265ms 4

Then "sle_minion" should have a FQDN 5s 203ms

And reverse resolution should work for "sle_minion" 505ms

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

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

@build_host

Scenario:
The build host is healthy

3s 980ms 4

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

And reverse resolution should work for "build_host" 308ms

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

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

@ssh_minion

Scenario:
The SSH minion is healthy

7s 187ms 4

Then "ssh_minion" should have a FQDN 5s 98ms

And reverse resolution should work for "ssh_minion" 499ms

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

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

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 196ms 4

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

And reverse resolution should work for "rhlike_minion" 188ms

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

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

@deblike_minion

Scenario:
The Debian-like minion is healthy

6s 343ms 4

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

And reverse resolution should work for "deblike_minion" 253ms

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

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

@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

643ms 1

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

@no_auth_registry

Scenario:
The registry without authentication is healthy

648ms 1

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

@custom_download_endpoint

Scenario:
The custom download endpoint is working

644ms 1

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

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

671ms 1

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

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

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

Scenario:
Wait for refresh of list of products to finish

3s 506ms 1

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

Scenario:
Create testing username

2s 394ms 12

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

And I follow "Create User" 637ms

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

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

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

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

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

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

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

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

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

And I should see a "testing" link 11ms

Scenario:
Grant testing user administrative priviledges

1s 731ms 10

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

And I follow "testing" 496ms

And I check "role_org_admin" 86ms

And I check "role_system_group_admin" 77ms

And I check "role_channel_admin" 77ms

And I check "role_activation_key_admin" 78ms

And I check "role_config_admin" 77ms

And I click on "Update" 608ms

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

And I should see a "testing" text 72ms

@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

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

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

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

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 675ms 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 400ms 5

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

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

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

And I click on "Save Preferences" 672ms

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

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

3s 274ms 5

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

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

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

And I click on "Save Preferences" 669ms

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

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

Scenario:
Create a Kiwi user with image administrators rights

4s 328ms 2

New user kiwikiwi created with roles: image_admin

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

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

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

Scenario:
Create a Docker user with image administrators rights

2s 203ms 2

New user docker created with roles: image_admin

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

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

@no_auth_registry

Scenario:
Create an image store without credentials

3s 11ms 7

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

And I follow "Create" 533ms

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

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

And I click on "create-btn" 61ms

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

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

Feature:Do not let Taskomatic tasks interfere with our CI tests 36s 68ms 3

Scenario:
Log in as admin user

26s 911ms 1

Given I am authorized for the "Admin" section 26s 911ms

Scenario:
Disable scheduled reposyncs

4s 591ms 5

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

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

And I choose "disabled" 60ms

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

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

Scenario:
Disable scheduled Cobbler syncs

4s 566ms 5

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

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

And I choose "disabled" 47ms

And I click on "Update Schedule" 52ms

And I click on "Disable Schedule" 3s 63ms

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

When I refresh SCC 30s 566ms

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

Then I should get "[ ] SLE-Product-SLES15-SP7-Pool for x86_64 SUSE Linux Enterprise Server 15 SP7 x86_64 [sle-product-sles15-sp7-pool-x86_64]" < 1ms

And I should get " [ ] SLE-Product-SLES15-SP7-Updates for x86_64 SUSE Linux Enterprise Server 15 SP7 x86_64 [sle-product-sles15-sp7-updates-x86_64]" < 1ms

And I should get " [ ] SLE15-SP7-Installer-Updates for x86_64 SUSE Linux Enterprise Server 15 SP7 x86_64 [sle15-sp7-installer-updates-x86_64]" < 1ms

Scenario:
List available mandatory channels

1s 488ms 4

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

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

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

Then I should get "[ ] SUSE Linux Enterprise Server 15 SP7 x86_64" < 1ms

@proxy @susemanager

Scenario:
List all products for SUSE Multi-Linux Manager

< 1ms 6

When I execute mgr-sync "list products --expand" 0s

Then I should get "[ ] SUSE Linux Enterprise Server 15 SP7 x86_64" 0s

And I should get " [ ] SUSE Multi-Linux Manager Proxy Extension 5.1 x86_64" 0s

And I should get " [ ] SUSE Multi-Linux Manager Proxy Extension for SLE 5.1 x86_64" 0s

And I should get " [ ] (R) SUSE Multi-Linux Manager Client Tools for SUSE Liberty Linux 7, RHEL and clones 7 x86_64" 0s

And I should get " [ ] (R) SUSE Multi-Linux Manager Client Tools for SLE 15 x86_64" 0s

Scenario:
List products with filter

1s 499ms 4

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

Then I should get "[ ] SUSE Linux Enterprise Server 15 SP7 x86_64" < 1ms

And I shouldn't get "ppc64" < 1ms

And I shouldn't get "s390x" < 1ms

Scenario:
Let mgr-sync time out

1m 1s 449ms 3

When I remove the mgr-sync cache file 683ms

And I execute mgr-sync refresh 1m 766ms

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

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

@scc_credentials

Scenario:
Refresh SCC

27s 451ms 1

When I refresh SCC 27s 451ms

@scc_credentials

Scenario:
Let the products page appear

2s 301ms 6

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

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

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

Then I should see a "Arch" text 121ms

And I should see a "Channels" text 121ms

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

@scc_credentials

Scenario:
Use the products and architecture filters

2s 473ms 7

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

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

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

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

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

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

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

@scc_credentials @susemanager

Scenario:
View the channels list in the products page

< 1ms 9

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

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

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

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

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

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

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

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

When I close the modal dialog 0s

@scc_credentials @susemanager

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

< 1ms 30

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

Then the SLE15 SP7 product should be added 0s

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

@uyuni

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

1m 56s 149ms 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 782ms

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

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

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

@containerized_server @proxy @uyuni

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

55s 406ms 2

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

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

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

@scc_credentials @uyuni @build_host

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

53m 10s 642ms 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
1 minutes out of 102 waiting for 'sles15-sp7' channels to finish 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
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
6 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
7 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
8 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
9 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
10 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
11 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-basesystem15-sp7-updates-x86_64 finished reposync
12 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
13 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
14 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-server-applications15-sp7-pool-x86_64 finished reposync
15 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-basesystem15-sp7-pool-x86_64 finished reposync
16 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-python3-15-sp7-pool-x86_64 finished reposync
Channel sle-module-server-applications15-sp7-updates-x86_64 finished reposync
Channel sle-module-python3-15-sp7-updates-x86_64 finished reposync
Channel sle-module-systems-management-15-sp7-pool-x86_64 finished reposync
17 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-systems-management-15-sp7-updates-x86_64 finished reposync
18 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
19 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
20 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
21 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
22 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
23 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-desktop-applications15-sp7-pool-x86_64 finished reposync
24 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-desktop-applications15-sp7-updates-x86_64 finished reposync
25 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
26 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-devtools15-sp7-pool-x86_64 finished reposync
27 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
28 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
29 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
30 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
31 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
32 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
33 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
34 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
35 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
36 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
37 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-devtools15-sp7-updates-x86_64 finished reposync
All channels for sles15-sp7 have been fully synced

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 58ms

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

Then the SLE15 SP7 product should be added 3s 25ms

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

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 52m 48s 966ms

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

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

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

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

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

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

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

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

@scc_credentials @skip_if_github_validation

Scenario:
Report the synchronization duration for SLES 15 SP7

< 1ms 1

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

Feature:Create fake channels 23s 431ms 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

614ms 1

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

Scenario:
Add a fake base channel for x86_64

1s 663ms 10

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

And I follow "Create Channel" 338ms

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

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

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

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

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

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

And I click on "Create Channel" 577ms

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

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

1s 470ms 10

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

And I follow "Create Channel" 330ms

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

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

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

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

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

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

And I click on "Create Channel" 549ms

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

@sle_minion

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

1s 410ms 10

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

And I follow "Create Channel" 263ms

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

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

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

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

And I click on "Create Channel" 571ms

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

Scenario:
Add a fake base channel for i586

888ms 10

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

And I follow "Create Channel" 237ms

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

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

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

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

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

And I click on "Create Channel" 58ms

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

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

982ms 10

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

And I follow "Create Channel" 346ms

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

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

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

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

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

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

And I click on "Create Channel" 56ms

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

Scenario:
Add a test base channel for x86_64

953ms 10

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

And I follow "Create Channel" 324ms

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

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

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

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

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

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

And I click on "Create Channel" 58ms

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

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

1s 52ms 10

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

And I follow "Create Channel" 381ms

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

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

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

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

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

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

And I click on "Create Channel" 58ms

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

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

And I follow "Create Channel" 344ms

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

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

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

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

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

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

And I uncheck "gpg_check" 10s 84ms

And I click on "Create Channel" 510ms

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

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 365ms 10

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

And I follow "Create Channel" 274ms

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

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

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

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

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

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

And I click on "Create Channel" 516ms

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

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 487ms 10

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

And I follow "Create Channel" 364ms

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

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

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

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

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

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

And I click on "Create Channel" 529ms

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

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

503ms 1

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

Scenario:
Create a fake repository for distributions using RPM

1s 227ms 7

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

And I follow "Create Repository" 302ms

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

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

And I click on "Create Repository" 499ms

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

And I should see "metadataSigned" as checked 20ms

Scenario:
Disable metadata check for the fake RPM repository

11s 6

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

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

And I uncheck "metadataSigned" 10s 66ms

And I click on "Update Repository" 456ms

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

And I should see "metadataSigned" as unchecked 17ms

@rhlike_minion

Scenario:
Create a fake AppStream repository

1s 81ms 7

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

And I follow "Create Repository" 298ms

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

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

And I click on "Create Repository" 465ms

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

And I should see "metadataSigned" as checked 16ms

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

11s 6ms 6

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

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

And I uncheck "metadataSigned" 10s 75ms

And I click on "Update Repository" 444ms

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

And I should see "metadataSigned" as unchecked 16ms

@sle_minion

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

2s 129ms 9

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

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

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

And I click on "Update Channel" 604ms

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

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

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

And I click on "Save Repositories" 663ms

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

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

2s 373ms 9

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

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

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

And I click on "Update Channel" 569ms

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

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

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

And I click on "Save Repositories" 807ms

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

@rhlike_minion

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

2s 318ms 9

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

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

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

And I click on "Update Channel" 57ms

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

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

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

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

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

@rhlike_minion

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

2s 574ms 9

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

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

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

And I click on "Update Channel" 531ms

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

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

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

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

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

Scenario:
Create a fake repository for i586

11s 51ms 7

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

And I follow "Create Repository" 234ms

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

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

And I uncheck "metadataSigned" 10s 71ms

And I click on "Create Repository" 447ms

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

Scenario:
Add the repository to the i586 channel

1s 862ms 9

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

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

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

And I click on "Update Channel" 503ms

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

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

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

And I click on "Save Repositories" 506ms

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

@sle_minion

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

1s 733ms 6

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

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

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

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

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

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

@deblike_minion

Scenario:
Create a fake repository for Debian-like

740ms 7

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

And I follow "Create Repository" 314ms

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

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

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

And I click on "Create Repository" 57ms

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

@deblike_minion

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

1s 297ms 6

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

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

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

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

And I click on "Save Repositories" 656ms

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 29s 73ms 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

486ms 1

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

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 558ms 10

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

And I follow "Create Channel" 282ms

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

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

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

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

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

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

And I click on "Create Channel" 66ms

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

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

6s 598ms 1

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

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

946ms 10

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

And I follow "Create Channel" 263ms

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

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

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

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

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

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

And I click on "Create Channel" 55ms

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

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

3s 994ms 1

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

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

1s 421ms 10

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

And I follow "Create Channel" 269ms

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

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

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

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

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

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

And I click on "Create Channel" 533ms

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

@deblike_minion

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

8s 143ms 1

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

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 451ms 10

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

And I follow "Create Channel" 298ms

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

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

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

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

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

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

And I click on "Create Channel" 545ms

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

@rhlike_minion

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

4s 471ms 1

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

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

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

And I enable source package syncing 1s 606ms

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

3s 885ms 9

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

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

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

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

And I follow "Sync" 344ms

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

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

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

@sle_minion

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

4s 656ms 2

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

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

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

3s 681ms 9

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

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

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

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

And I follow "Sync" 333ms

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

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

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

Scenario:
Synchronize Test-Child-Channel-x86_64 channel

4s 222ms 9

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

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

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

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

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

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

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

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

@sle_minion

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

35s 164ms 9

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

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

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

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

And I follow "Sync" 677ms

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

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 31s 455ms

@deblike_minion

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

3s 561ms 9

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

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

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

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

And I follow "Sync" 347ms

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

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

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

@rhlike_minion

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

4s 319ms 9

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

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

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

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

And I follow "Sync" 962ms

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

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

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

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

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 162ms 9

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

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

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

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

And I follow "Sync" 684ms

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

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

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

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

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

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

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

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

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

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

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

Scenario:
Refresh the channel's repository data

6s 149ms 6

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

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

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

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

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

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

Scenario:
Cleanup disable source package syncing

1s 21ms 1

Then I disable source package syncing 1s 21ms

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

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

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

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

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

And I follow "Sync" 256ms

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

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

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

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

4s 200ms 9

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

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

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

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

And I follow "Sync" 765ms

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

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

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

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

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 346ms 9

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

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

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

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

And I follow "Sync" 849ms

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

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

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

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

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

4s 162ms 9

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

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

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

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

And I follow "Sync" 681ms

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

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

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

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

574ms 1

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

@sle_minion

Scenario:
Create an activation key with a channel

2s 166ms 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 554ms

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

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

2s 270ms 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" 887ms

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

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

2s 417ms 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 465ms

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

@ssh_minion

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

1s 809ms 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" 820ms

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

@ssh_minion

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

2s 223ms 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" 1s 3ms

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

@proxy

Scenario:
Create an activation key for the proxy

2s 432ms 2

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

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

@build_host

Scenario:
Create an activation key for the build host

2s 534ms 3

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

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

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

@scc_credentials

Scenario:
Create an activation key for the terminal

2s 147ms 2

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

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

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

467ms 1

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 600ms

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 575ms

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

@scc_credentials @susemanager

Scenario:
Update SLE SSH tunnel key with synced base product

< 1ms 14

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

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

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

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

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

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

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

And I click on "Update Activation Key" 0s

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

@uyuni

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

2s 163ms 10

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 575ms

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

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

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

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

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

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

And I wait for child channels to appear 546ms

And I include the recommended child channels 173ms

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

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

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 629ms

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

@scc_credentials @uyuni @build_host

Scenario:
Update build host key with Uyuni client tools

2s 316ms 9

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

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

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

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

And I wait for child channels to appear 310ms

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

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

And I click on "Update Activation Key" 636ms

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

@skip_if_github_validation @scc_credentials @uyuni @build_host

Scenario:
Update build host key with dev child channel

2s 172ms 9

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

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

And I wait for child channels to appear 939ms

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

And I wait for child channels to appear 316ms

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

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

And I click on "Update Activation Key" 564ms

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

@scc_credentials @build_host

Scenario:
Update terminal key with synced base product

3s 47ms 16

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

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

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

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

And I wait for child channels to appear 448ms

And I include the recommended child channels 201ms

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 641ms

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

@susemanager @scc_credentials @build_host

Scenario:
Update terminal key with normal SUSE fake channel

< 1ms 9

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

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

And I wait for child channels to appear 0s

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

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

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

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

And I click on "Update Activation Key" 0s

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

@pxeboot_minion @uyuni @scc_credentials @build_host

Scenario:
Update terminal key with specific fake channel

< 1ms 9

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

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

And I wait for child channels to appear 0s

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

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

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

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

And I click on "Update Activation Key" 0s

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

@skip_if_github_validation @sle_minion

Scenario:
Update SLE key with to include dev child channel

1s 809ms 6

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

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

And I wait for child channels to appear 921ms

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

And I click on "Update Activation Key" 567ms

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

@skip_if_github_validation @deblike_minion

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

1s 786ms 6

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

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

And I wait for child channels to appear 903ms

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

And I click on "Update Activation Key" 570ms

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

@skip_if_github_validation @rhlike_minion

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

1s 844ms 6

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

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

And I wait for child channels to appear 899ms

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

And I click on "Update Activation Key" 637ms

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

Feature:Create bootstrap repositories 11s 725ms 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 332ms 1

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

@sle_minion

Scenario:
Create the bootstrap repository for SUSE Minion

4s 366ms 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 4s 366ms

@proxy

Scenario:
Create the bootstrap repository for Proxy

2s 197ms 1

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

@build_host

Scenario:
Create the bootstrap repository for Build Host

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

@containerized_server @scope_containerized_proxy @proxy
Feature:Setup containerized proxy 3m 16s 464ms 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 483ms 1

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

@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

26s 773ms 1

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

Scenario:
Bootstrap the proxy host as a salt minion

35s 624ms 9

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 62ms

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

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

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

Scenario:
Generate containerized proxy configuration

10s 904ms 2

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

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

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

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

Scenario:
Wait until containerized proxy service is active

3s 856ms 10

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

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

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

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

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

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

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

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

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

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

Scenario:
The containerized proxy should be registered automatically

746ms 2

When I follow the left menu "Systems" 63ms

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

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

11s 47ms 3

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

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

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

@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 52s 29ms 1 6

Scenario:
Log in as admin user

20s 531ms 1

Given I am authorized for the "Admin" section 20s 531ms Show Error +

                                            
 session not created: Chrome instance exited. Examine ChromeDriver verbose log to determine the cause. (Selenium::WebDriver::Error::SessionNotCreatedError)
(internal:kernel):90:in `tap'
./features/step_definitions/navigation_steps.rb:592:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:460:in `/^I am authorized for the "([^"]*)" section$/'
features/init_clients/min_deblike_salt.feature:11:in `I am authorized for the "Admin" section'

Scenario:
Bootstrap a Debian-like minion

20s 408ms 13 1

When I follow the left menu "Systems > Bootstrapping" 20s 408ms Show Error +

                                            
 session not created: Chrome instance exited. Examine ChromeDriver verbose log to determine the cause. (Selenium::WebDriver::Error::SessionNotCreatedError)
(internal:kernel):90:in `tap'
./features/step_definitions/navigation_steps.rb:414:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:406:in `each'
./features/step_definitions/navigation_steps.rb:406:in `each_with_index'
./features/step_definitions/navigation_steps.rb:406:in `/^I follow the left menu "([^"]*)"$/'
features/init_clients/min_deblike_salt.feature:14:in `I follow the left menu "Systems ) Bootstrapping"'

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

When I enter the hostname of "deblike_minion" as "hostname" 0s

And I enter "22" as "port" 0s

And I enter "root" as "user" 0s

And I enter "linux" as "password" 0s

And I select "1-DEBLIKE-KEY" from "activationKeys" 0s

And I select the hostname of "proxy" from "proxies" if present 0s

And I click on "Bootstrap" 0s

And I wait until I see "Bootstrap process initiated." text 0s

And I follow the left menu "Systems > System List > All" 0s

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

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

And I query latest Salt changes on Debian-like system "deblike_minion" 0s

@proxy

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

5s 997ms 3 1

Given I am on the Systems overview page of this "deblike_minion" 5s 997ms Show Error +

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

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

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

Then I should see "proxy" short hostname 0s

@proxy

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

3s 829ms 3 1

Given I am on the Systems overview page of this "proxy" 3s 829ms Show Error +

                                            
 session not created: Chrome instance exited. Examine ChromeDriver verbose log to determine the cause. (Selenium::WebDriver::Error::SessionNotCreatedError)
(internal:kernel):90:in `tap'
./features/step_definitions/navigation_steps.rb:475:in `/^I am on the Systems overview page of this "([^"]*)"$/'
features/init_clients/min_deblike_salt.feature:38:in `I am on the Systems overview page of this "proxy"'

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

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

Then I should see "deblike_minion" hostname 0s

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

401ms 10 1

Given I am on the Systems overview page of this "deblike_minion" 401ms Show Error +

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

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

And I follow "Software Channels" in the content area 0s

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

And I check radio button "Fake-Base-Channel-Debian-like" 0s

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

And I click on "Next" 0s

Then I should see a "Confirm Software Channel Change" text 0s

When I click on "Confirm" 0s

Then I should see a "Changing the channels has been scheduled." text 0s

And I wait until event "Subscribe channels scheduled by admin" is completed 0s

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

554ms 1

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

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

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

306ms 1 1

Given I am on the Systems overview page of this "deblike_minion" 306ms Show Error +

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

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

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

Scenario:
Log in as admin user

21s 757ms 1

Given I am authorized for the "Admin" section 21s 757ms Show Error +

                                            
 session not created: Chrome instance exited. Examine ChromeDriver verbose log to determine the cause. (Selenium::WebDriver::Error::SessionNotCreatedError)
(internal:kernel):90:in `tap'
./features/step_definitions/navigation_steps.rb:592:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:460:in `/^I am authorized for the "([^"]*)" section$/'
features/init_clients/min_rhlike_salt.feature:11:in `I am authorized for the "Admin" section'

Scenario:
Bootstrap a Red Hat-like minion

40s 636ms 12 1

When I follow the left menu "Systems > Bootstrapping" 40s 636ms Show Error +

                                            
 session not created: Chrome instance exited. Examine ChromeDriver verbose log to determine the cause. (Selenium::WebDriver::Error::SessionNotCreatedError)
(internal:kernel):90:in `tap'
./features/step_definitions/navigation_steps.rb:414:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:406:in `each'
./features/step_definitions/navigation_steps.rb:406:in `each_with_index'
./features/step_definitions/navigation_steps.rb:406:in `/^I follow the left menu "([^"]*)"$/'
features/init_clients/min_rhlike_salt.feature:14:in `I follow the left menu "Systems ) Bootstrapping"'

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

When I enter the hostname of "rhlike_minion" as "hostname" 0s

And I enter "22" as "port" 0s

And I enter "root" as "user" 0s

And I enter "linux" as "password" 0s

And I select "1-RH-LIKE-KEY" from "activationKeys" 0s

And I select the hostname of "proxy" from "proxies" if present 0s

And I click on "Bootstrap" 0s

And I wait until I see "Bootstrap process initiated." text 0s

And I follow the left menu "Systems > System List > All" 0s

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

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

@proxy

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

2s 326ms 3 1

Given I am on the Systems overview page of this "rhlike_minion" 2s 326ms Show Error +

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

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

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

Then I should see "proxy" short hostname 0s

@proxy

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

4s 957ms 3 1

Given I am on the Systems overview page of this "proxy" 4s 957ms Show Error +

                                            
 session not created: Chrome instance exited. Examine ChromeDriver verbose log to determine the cause. (Selenium::WebDriver::Error::SessionNotCreatedError)
(internal:kernel):90:in `tap'
./features/step_definitions/navigation_steps.rb:475:in `/^I am on the Systems overview page of this "([^"]*)"$/'
features/init_clients/min_rhlike_salt.feature:37:in `I am on the Systems overview page of this "proxy"'

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

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

Then I should see "rhlike_minion" hostname 0s

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

477ms 10 1

Given I am on the Systems overview page of this "rhlike_minion" 477ms Show Error +

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

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

And I follow "Software Channels" in the content area 0s

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

And I check radio button "Fake-Base-Channel-RH-like" 0s

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

And I click on "Next" 0s

Then I should see a "Confirm Software Channel Change" text 0s

When I click on "Confirm" 0s

Then I should see a "Changing the channels has been scheduled." text 0s

And I wait until event "Subscribe channels scheduled by admin" is completed 0s

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

325ms 1

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

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

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

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

462ms 1 1

Given I am on the Systems overview page of this "rhlike_minion" 462ms Show Error +

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

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

@build_host
Feature:Bootstrap a build host via the GUI 1m 30s 581ms 1 8

Scenario:
Clean up sumaform leftovers on build host

10s 263ms 1

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

Scenario:
Log in as admin user

32s 404ms 1

Given I am authorized for the "Admin" section 32s 404ms Show Error +

                                            
 session not created: Chrome instance exited. Examine ChromeDriver verbose log to determine the cause. (Selenium::WebDriver::Error::SessionNotCreatedError)
(internal:kernel):90:in `tap'
./features/step_definitions/navigation_steps.rb:592:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:460:in `/^I am authorized for the "([^"]*)" section$/'
features/init_clients/buildhost_bootstrap.feature:11:in `I am authorized for the "Admin" section'

Scenario:
Bootstrap a build host

40s 872ms 9 1

When I follow the left menu "Systems > Bootstrapping" 40s 872ms Show Error +

                                            
 session not created: Chrome instance exited. Examine ChromeDriver verbose log to determine the cause. (Selenium::WebDriver::Error::SessionNotCreatedError)
(internal:kernel):90:in `tap'
./features/step_definitions/navigation_steps.rb:414:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:406:in `each'
./features/step_definitions/navigation_steps.rb:406:in `each_with_index'
./features/step_definitions/navigation_steps.rb:406:in `/^I follow the left menu "([^"]*)"$/'
features/init_clients/buildhost_bootstrap.feature:14:in `I follow the left menu "Systems ) Bootstrapping"'

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

When I enter the hostname of "build_host" as "hostname" 0s

And I enter "22" as "port" 0s

And I enter "root" as "user" 0s

And I enter "linux" as "password" 0s

And I select "1-BUILD-HOST-KEY-x86_64" from "activationKeys" 0s

And I select the hostname of "proxy" from "proxies" if present 0s

And I click on "Bootstrap" 0s

And I wait until I see "Bootstrap process initiated." text 0s

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

404ms 5 1

When I follow the left menu "Salt > Keys" 404ms Show Error +

                                            
 session not created: Chrome instance exited. Examine ChromeDriver verbose log to determine the cause. (Selenium::WebDriver::Error::SessionNotCreatedError)
(internal:kernel):90:in `tap'
./features/step_definitions/navigation_steps.rb:414:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:406:in `each'
./features/step_definitions/navigation_steps.rb:406:in `each_with_index'
./features/step_definitions/navigation_steps.rb:406:in `/^I follow the left menu "([^"]*)"$/'
features/init_clients/buildhost_bootstrap.feature:26:in `I follow the left menu "Salt ) Keys"'

Then I should see a "accepted" text 0s

When I follow the left menu "Systems > System List > All" 0s

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

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

Then the Salt master can reach "build_host" 0s

@proxy

Scenario:
Check connection from build host to proxy

355ms 3 1

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

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

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

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

Then I should see "proxy" short hostname 0s

@proxy

Scenario:
Check registration on build host of minion

4s 870ms 3 1

Given I am on the Systems overview page of this "proxy" 4s 870ms Show Error +

                                            
 session not created: Chrome instance exited. Examine ChromeDriver verbose log to determine the cause. (Selenium::WebDriver::Error::SessionNotCreatedError)
(internal:kernel):90:in `tap'
./features/step_definitions/navigation_steps.rb:475:in `/^I am on the Systems overview page of this "([^"]*)"$/'
features/init_clients/buildhost_bootstrap.feature:43:in `I am on the Systems overview page of this "proxy"'

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

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

Then I should see "build_host" hostname 0s

Scenario:
Detect latest Salt changes on the SLES build host

624ms 1

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

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

Scenario:
Check that the build host is a build host

367ms 2 1

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

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

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

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

Scenario:
Check events history for failures on SLES build host

417ms 1 1

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

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

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

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

Scenario:
Clean up sumaform leftovers on SLES minion

10s 443ms 1

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

Scenario:
Log in as admin user

9s 783ms 1

Given I am authorized for the "Admin" section 9s 783ms Show Error +

                                            
 session not created: Chrome instance exited. Examine ChromeDriver verbose log to determine the cause. (Selenium::WebDriver::Error::SessionNotCreatedError)
(internal:kernel):90:in `tap'
./features/step_definitions/navigation_steps.rb:592:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:460:in `/^I am authorized for the "([^"]*)" section$/'
features/init_clients/sle_minion.feature:11:in `I am authorized for the "Admin" section'

Scenario:
Bootstrap a SLES minion

20s 421ms 10 1

When I follow the left menu "Systems > Bootstrapping" 20s 421ms Show Error +

                                            
 session not created: Chrome instance exited. Examine ChromeDriver verbose log to determine the cause. (Selenium::WebDriver::Error::SessionNotCreatedError)
(internal:kernel):90:in `tap'
./features/step_definitions/navigation_steps.rb:414:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:406:in `each'
./features/step_definitions/navigation_steps.rb:406:in `each_with_index'
./features/step_definitions/navigation_steps.rb:406:in `/^I follow the left menu "([^"]*)"$/'
features/init_clients/sle_minion.feature:14:in `I follow the left menu "Systems ) Bootstrapping"'

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

When I enter the hostname of "sle_minion" as "hostname" 0s

And I enter "22" as "port" 0s

And I enter "root" as "user" 0s

And I enter "linux" as "password" 0s

And I select "1-SUSE-KEY-x86_64" from "activationKeys" 0s

And I select the hostname of "proxy" from "proxies" if present 0s

And I click on "Bootstrap" 0s

And I wait until I see "Bootstrap process initiated." text 0s

And I report the bootstrap duration for "sle_minion" 0s

Scenario:
Check the new bootstrapped minion in System List page

14s 822ms 7 1

When I follow the left menu "Salt > Keys" 14s 822ms Show Error +

                                            
 session not created: Chrome instance exited. Examine ChromeDriver verbose log to determine the cause. (Selenium::WebDriver::Error::SessionNotCreatedError)
(internal:kernel):90:in `tap'
./features/step_definitions/navigation_steps.rb:414:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:406:in `each'
./features/step_definitions/navigation_steps.rb:406:in `each_with_index'
./features/step_definitions/navigation_steps.rb:406:in `/^I follow the left menu "([^"]*)"$/'
features/init_clients/sle_minion.feature:27:in `I follow the left menu "Salt ) Keys"'

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

Then I should see a "accepted" text 0s

When I follow the left menu "Systems > System List > All" 0s

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

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

Then the Salt master can reach "sle_minion" 0s

And I report the onboarding duration for "sle_minion" 0s

@susemanager

Scenario:
Use correct kernel image on the SLES minion

< 1ms 2

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

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

@susemanager

Scenario:
Reboot the SLES minion to use the new kernel

< 1ms 1

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

@proxy

Scenario:
Check connection from minion to proxy

363ms 3 1

Given I am on the Systems overview page of this "sle_minion" 363ms Show Error +

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

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

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

Then I should see "proxy" short hostname 0s

@proxy

Scenario:
Check registration on proxy of minion

4s 882ms 3 1

Given I am on the Systems overview page of this "proxy" 4s 882ms Show Error +

                                            
 session not created: Chrome instance exited. Examine ChromeDriver verbose log to determine the cause. (Selenium::WebDriver::Error::SessionNotCreatedError)
(internal:kernel):90:in `tap'
./features/step_definitions/navigation_steps.rb:475:in `/^I am on the Systems overview page of this "([^"]*)"$/'
features/init_clients/sle_minion.feature:54:in `I am on the Systems overview page of this "proxy"'

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

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

Then I should see "sle_minion" hostname 0s

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

Scenario:
Clean up sumaform leftovers on SLES SSH minion

10s 458ms 1

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

Scenario:
Log in as admin user

9s 920ms 1

Given I am authorized for the "Admin" section 9s 920ms Show Error +

                                            
 session not created: Chrome instance exited. Examine ChromeDriver verbose log to determine the cause. (Selenium::WebDriver::Error::SessionNotCreatedError)
(internal:kernel):90:in `tap'
./features/step_definitions/navigation_steps.rb:592:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:460:in `/^I am authorized for the "([^"]*)" section$/'
features/init_clients/sle_ssh_minion.feature:11:in `I am authorized for the "Admin" section'

Scenario:
Bootstrap a SLES SSH minion

40s 801ms 10 1

When I follow the left menu "Systems > Bootstrapping" 40s 801ms Show Error +

                                            
 session not created: Chrome instance exited. Examine ChromeDriver verbose log to determine the cause. (Selenium::WebDriver::Error::SessionNotCreatedError)
(internal:kernel):90:in `tap'
./features/step_definitions/navigation_steps.rb:414:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:406:in `each'
./features/step_definitions/navigation_steps.rb:406:in `each_with_index'
./features/step_definitions/navigation_steps.rb:406:in `/^I follow the left menu "([^"]*)"$/'
features/init_clients/sle_ssh_minion.feature:14:in `I follow the left menu "Systems ) Bootstrapping"'

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

When I check "manageWithSSH" 0s

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

And I enter "linux" as "password" 0s

And I select the hostname of "proxy" from "proxies" if present 0s

And I click on "Bootstrap" 0s

And I wait until I see "Bootstrap process initiated." text 0s

And I follow the left menu "Systems > System List > All" 0s

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

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

@susemanager

Scenario:
Use correct kernel image on the SSH minion

< 1ms 2

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

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

@susemanager

Scenario:
Reboot the SSH minion to use the new kernel

< 1ms 1

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

@proxy

Scenario:
Check connection from SSH minion to proxy

15s 300ms 1 3 1

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

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

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

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

Then I should see "proxy" short hostname 0s

14s 936ms Show Info +

11:46:07:000 - 11:46:07:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/YourRhn.do

Screenshot +

@proxy

Scenario:
Check registration on proxy of SSH minion

27s 410ms 4 1

Given I am on the Systems overview page of this "proxy" 3s 549ms

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

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

Then I should see "ssh_minion" hostname 10s 89ms Show Error +

                                            
 Hostname uyuni-master-suse-sshminion.sumaci.aws is not present (ScriptError)
./features/step_definitions/navigation_steps.rb:676:in `/^I should see "([^"]*)" hostname$/'
features/init_clients/sle_ssh_minion.feature:47:in `I should see "ssh_minion" hostname'

13s 605ms Show Info +

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

Screenshot +

@transactional_server
Feature:SELinux debugging < 1ms 1

In order for the server to behave correctly after a reboot
I want to be sure that there is no wrong SELinux label

Scenario:
No previous operation has created wrong SELinux label

< 1ms 1

Then files on container volumes should all have the proper SELinux label 0s

@new_issue
Feature:Debug the server after the testsuite has run 17s 366ms 5

Scenario:
Call spacewalk-debug on server

13s 606ms 1

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

Scenario:
Check the tomcat logs on server

650ms 1

Then the tomcat logs should not contain errors 650ms

Scenario:
Check salt event log for failures on server

1s 748ms 1

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

Scenario:
Check the taskomatic logs on server

694ms 1

Then the taskomatic logs should not contain errors 694ms

Scenario:
Check for out of memory errors

666ms 1

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

Feature:Debug the clients after the testsuite has run 1m 32s 321ms 1

Scenario:
Extract the logs from all our clients

1m 32s 321ms 1

When I extract the log files from all our active nodes 1m 32s 321ms

@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

133

Failed Scenarios

29

Skipped Scenarios

39

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

@sle_minion Scenario:The minion is healthy 7s 265ms 4

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

@ssh_minion Scenario:The SSH minion is healthy 7s 187ms 4

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

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

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

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

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

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

@scc_credentials Scenario:Refresh SCC 27s 451ms 1

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

@scc_credentials Scenario:Use the products and architecture filters 2s 473ms 7

@scc_credentials @susemanager Scenario:View the channels list in the products page < 1ms 9

@scc_credentials @susemanager Scenario:Synchronize SLES 15 SP7 product with recommended sub-products, including MLM Client Tools < 1ms 30

@uyuni Scenario:Partially add openSUSE Tumbleweed product, only including the required packages to generate the bootstrap repository 1m 56s 149ms 4

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

@scc_credentials @uyuni @build_host Scenario:Synchronize SLES 15 SP7 product with recommended sub-products for Retail feature 53m 10s 642ms 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 307ms 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 410ms 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 542ms 11

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

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

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

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

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

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

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

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

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

@deblike_minion Scenario:Add the repository to the Debian-like base channel 1s 297ms 6

@pxeboot_minion @uyuni @scc_credentials Scenario:Add the repository to the terminal child channel < 1ms 9

@skip_if_github_validation Feature:Create custom channels with development repositories 29s 73ms 9

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

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

@uyuni @build_host Scenario:Create a custom channel for Build Host 946ms 10

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

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

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

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

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

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

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

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

@sle_minion Scenario:Synchronize Fake-Child-Channel-SUSE-like channel 35s 164ms 9

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

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

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

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

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

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

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

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

@proxy

Scenario:
The proxy is healthy

4s 444ms 4

@sle_minion

Scenario:
The minion is healthy

7s 265ms 4

@build_host

Scenario:
The build host is healthy

3s 980ms 4

@ssh_minion

Scenario:
The SSH minion is healthy

7s 187ms 4

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 196ms 4

@deblike_minion

Scenario:
The Debian-like minion is healthy

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

643ms 1

@no_auth_registry

Scenario:
The registry without authentication is healthy

648ms 1

@custom_download_endpoint

Scenario:
The custom download endpoint is working

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

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

@proxy @susemanager

Scenario:
List all products for SUSE Multi-Linux Manager

< 1ms 6

@scc_credentials

Scenario:
Refresh SCC

27s 451ms 1

@scc_credentials

Scenario:
Let the products page appear

2s 301ms 6

@scc_credentials

Scenario:
Use the products and architecture filters

2s 473ms 7

@scc_credentials @susemanager

Scenario:
View the channels list in the products page

< 1ms 9

@scc_credentials @susemanager

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

< 1ms 30

@uyuni

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

1m 56s 149ms 4

@containerized_server @proxy @uyuni

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

55s 406ms 2

@scc_credentials @uyuni @build_host

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

53m 10s 642ms 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 307ms 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 410ms 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 542ms 11

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 365ms 10

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 487ms 10

@rhlike_minion

Scenario:
Create a fake AppStream repository

1s 81ms 7

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

11s 6ms 6

@sle_minion

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

2s 129ms 9

@rhlike_minion

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

2s 318ms 9

@rhlike_minion

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

2s 574ms 9

@sle_minion

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

1s 733ms 6

@deblike_minion

Scenario:
Create a fake repository for Debian-like

740ms 7

@deblike_minion

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

1s 297ms 6

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Add the repository to the terminal child channel

< 1ms 9

@skip_if_github_validation
Feature:Create custom channels with development repositories 29s 73ms 9

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 558ms 10

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

6s 598ms 1

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

946ms 10

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

3s 994ms 1

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

1s 421ms 10

@deblike_minion

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

8s 143ms 1

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 451ms 10

@rhlike_minion

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

4s 471ms 1

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

3s 885ms 9

@sle_minion

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

4s 656ms 2

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

3s 681ms 9

@sle_minion

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

35s 164ms 9

@deblike_minion

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

3s 561ms 9

@rhlike_minion

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

4s 319ms 9

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 162ms 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 341ms 4

@sle_minion

Scenario:
Synchronize Devel-SUSE-Channel channel

3s 632ms 9

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

4s 200ms 9

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 346ms 9

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

4s 162ms 9

@sle_minion

Scenario:
Create an activation key with a channel

2s 166ms 2

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

2s 270ms 2

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

2s 417ms 2

@ssh_minion

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

1s 809ms 2

@ssh_minion

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

2s 223ms 2

@proxy

Scenario:
Create an activation key for the proxy

2s 432ms 2

@build_host

Scenario:
Create an activation key for the build host

2s 534ms 3

@scc_credentials

Scenario:
Create an activation key for the terminal

2s 147ms 2

@scc_credentials @susemanager

Scenario:
Update SLE key with synced base product

< 1ms 20