Cucumber Feature Report

All Scenarios

201

Passed Scenarios

133

Failed Scenarios

29

Skipped Scenarios

39

Execution Time: 75m 36s 658ms

Expand All | Collapse All

Metadata

App Version: Uyuni/Head

Browser: Chrome

Platform: x86_64

Parallel: Disabled

Feature:Sanity checks 45s 535ms 10 2

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

Scenario:
The server is healthy

11s 965ms 19

Then "server" should have a FQDN 403ms

And reverse resolution should work for "server" 634ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@proxy

Scenario:
The proxy is healthy

4s 569ms 4

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

And reverse resolution should work for "proxy" 284ms

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

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

@sle_minion

Scenario:
The minion is healthy

6s 584ms 4

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

And reverse resolution should work for "sle_minion" 427ms

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

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

@build_host

Scenario:
The build host is healthy

3s 936ms 4

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

And reverse resolution should work for "build_host" 228ms

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

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

@ssh_minion

Scenario:
The SSH minion is healthy

6s 718ms 4

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

And reverse resolution should work for "ssh_minion" 480ms

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

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

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 759ms 4

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

And reverse resolution should work for "rhlike_minion" 213ms

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

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

@deblike_minion

Scenario:
The Debian-like minion is healthy

6s 12ms 4

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

And reverse resolution should work for "deblike_minion" 229ms

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

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

@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

676ms 1

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

@no_auth_registry

Scenario:
The registry without authentication is healthy

658ms 1

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

@custom_download_endpoint

Scenario:
The custom download endpoint is working

656ms 1

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

Feature:Very first settings 51s 832ms 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

796ms 1

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

@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

41s 552ms 1

Given I am authorized for the "Admin" section 41s 552ms

Scenario:
Wait for refresh of list of products to finish

3s 510ms 1

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

Scenario:
Create testing username

2s 877ms 12

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

And I follow "Create User" 634ms

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

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

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

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

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

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

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

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

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

And I should see a "testing" link 26ms

Scenario:
Grant testing user administrative priviledges

2s 412ms 10

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

And I follow "testing" 677ms

And I check "role_org_admin" 131ms

And I check "role_system_group_admin" 150ms

And I check "role_channel_admin" 143ms

And I check "role_activation_key_admin" 130ms

And I check "role_config_admin" 131ms

And I click on "Update" 734ms

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

And I should see a "testing" text 93ms

@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

683ms 1

* Mon Nov 24 2025 Alexander Graul
- Add minimum_auth_version to enforce security (CVE-2025-62349)
- Backport security fixes for vendored tornado
* BDSA-2024-3438
* BDSA-2024-3439
* BDSA-2024-9026
- Junos module yaml loader fix (CVE-2025-62348)
- Added:
* backport-3006.17-security-fixes-739.patch

* Thu Nov 13 2025 Marek Czernek
- Require Python dependencies only for used Python version

* Tue Nov 11 2025 Marek Czernek
- Fix TLS and x509 modules for OSes with older cryptography module

When I query latest Salt changes on "server" 683ms

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

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

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

@scc_credentials @no_mirror

Scenario:
Enter valid SCC credentials

< 1ms 6

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

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

And I ask to add new credentials 0s

And I enter the SCC credentials 0s

And I click on "Save" 0s

And I wait until the SCC credentials are valid 0s

Feature:Change personal preferences 5s 635ms 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 690ms 5

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

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

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

And I click on "Save Preferences" 784ms

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

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

3s 945ms 5

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

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

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

And I click on "Save Preferences" 815ms

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

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

Scenario:
Create a Kiwi user with image administrators rights

4s 254ms 2

New user kiwikiwi created with roles: image_admin

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

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

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

Scenario:
Create a Docker user with image administrators rights

2s 189ms 2

New user docker created with roles: image_admin

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

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

@no_auth_registry

Scenario:
Create an image store without credentials

3s 394ms 7

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

And I follow "Create" 589ms

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

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

And I click on "create-btn" 104ms

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

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

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

Scenario:
Log in as admin user

27s 252ms 1

Given I am authorized for the "Admin" section 27s 252ms

Scenario:
Disable scheduled reposyncs

4s 603ms 5

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

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

And I choose "disabled" 105ms

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

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

Scenario:
Disable scheduled Cobbler syncs

4s 539ms 5

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

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

And I choose "disabled" 99ms

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

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

@scc_credentials
Feature:List available channels and enable them 1m 36s 788ms 5 1

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

Scenario:
List available channels

30s 737ms 5

When I refresh SCC 28s 390ms

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

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

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

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

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

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

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

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

When I remove the mgr-sync cache file 665ms

And I execute mgr-sync refresh 1m 802ms

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

Feature:Synchronize products in the products page of the Setup Wizard 45m 35s 383ms 8 9

@scc_credentials

Scenario:
Refresh SCC

25s 477ms 1

When I refresh SCC 25s 477ms

@scc_credentials

Scenario:
Let the products page appear

2s 269ms 6

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

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

And I wait until I see "Product Description" text 993ms

Then I should see a "Arch" text 115ms

And I should see a "Channels" text 120ms

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

@scc_credentials

Scenario:
Use the products and architecture filters

2s 715ms 7

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

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

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

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

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

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

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

@scc_credentials @susemanager

Scenario:
View the channels list in the products page

< 1ms 9

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

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

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

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

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

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

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

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

When I close the modal dialog 0s

@scc_credentials @susemanager

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

< 1ms 30

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

Then the SLE15 SP7 product should be added 0s

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

@uyuni

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

3m 34s 980ms 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 664ms

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

And I use spacewalk-repo-sync to sync channel "opensuse_tumbleweed-x86_64" including only client tools dependencies 3m 9s 581ms

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

@containerized_server @proxy @uyuni

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

1m 10s 367ms 2

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

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

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

@scc_credentials @uyuni @build_host

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

39m 36s 12ms 20

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 54ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

547ms 1

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

Scenario:
Add a fake base channel for x86_64

2s 195ms 10

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

And I follow "Create Channel" 328ms

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

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

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

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

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

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

And I click on "Create Channel" 683ms

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

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

1s 989ms 10

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

And I follow "Create Channel" 400ms

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

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

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

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

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

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

And I click on "Create Channel" 633ms

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

@sle_minion

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

1s 884ms 10

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

And I follow "Create Channel" 304ms

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

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

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

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

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

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

And I click on "Create Channel" 670ms

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

Scenario:
Add a fake base channel for i586

1s 938ms 10

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

And I follow "Create Channel" 319ms

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

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

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

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

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

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

And I click on "Create Channel" 667ms

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

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

1s 853ms 10

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

And I follow "Create Channel" 297ms

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

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

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

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

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

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

And I click on "Create Channel" 644ms

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

Scenario:
Add a test base channel for x86_64

1s 919ms 10

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

And I follow "Create Channel" 406ms

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

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

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

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

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

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

And I click on "Create Channel" 609ms

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

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

1s 893ms 10

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

And I follow "Create Channel" 292ms

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

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

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

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

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

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

And I click on "Create Channel" 607ms

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

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

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

And I follow "Create Channel" 314ms

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

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

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

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

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

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

And I uncheck "gpg_check" 10s 114ms

And I click on "Create Channel" 493ms

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

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 383ms 10

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

And I follow "Create Channel" 336ms

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

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

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

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

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

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

And I click on "Create Channel" 528ms

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

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 272ms 10

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

And I follow "Create Channel" 254ms

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

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

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

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

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

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

And I click on "Create Channel" 57ms

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

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

491ms 1

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

Scenario:
Create a fake repository for distributions using RPM

1s 113ms 7

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

And I follow "Create Repository" 282ms

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

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

And I click on "Create Repository" 439ms

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

And I should see "metadataSigned" as checked 18ms

Scenario:
Disable metadata check for the fake RPM repository

10s 943ms 6

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

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

And I uncheck "metadataSigned" 10s 66ms

And I click on "Update Repository" 457ms

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

And I should see "metadataSigned" as unchecked 15ms

@rhlike_minion

Scenario:
Create a fake AppStream repository

980ms 7

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

And I follow "Create Repository" 288ms

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

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

And I click on "Create Repository" 409ms

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

And I should see "metadataSigned" as checked 15ms

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

10s 937ms 6

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

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

And I uncheck "metadataSigned" 10s 52ms

And I click on "Update Repository" 465ms

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

And I should see "metadataSigned" as unchecked 15ms

@sle_minion

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

1s 844ms 9

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

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

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

And I click on "Update Channel" 531ms

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

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

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

And I click on "Save Repositories" 519ms

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

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

2s 163ms 9

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

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

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

And I click on "Update Channel" 55ms

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

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

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

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

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

@rhlike_minion

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

2s 724ms 9

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

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

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

And I click on "Update Channel" 547ms

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

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

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

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

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

@rhlike_minion

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

2s 702ms 9

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

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

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

And I click on "Update Channel" 54ms

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

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

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

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

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

Scenario:
Create a fake repository for i586

11s 84ms 7

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

And I follow "Create Repository" 270ms

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

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

And I uncheck "metadataSigned" 10s 95ms

And I click on "Create Repository" 439ms

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

Scenario:
Add the repository to the i586 channel

1s 865ms 9

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

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

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

And I click on "Update Channel" 495ms

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

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

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

And I click on "Save Repositories" 591ms

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

@sle_minion

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

1s 498ms 6

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

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

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

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

And I click on "Save Repositories" 862ms

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

@deblike_minion

Scenario:
Create a fake repository for Debian-like

662ms 7

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

And I follow "Create Repository" 275ms

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

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

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

And I click on "Create Repository" 52ms

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

@deblike_minion

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

1s 321ms 6

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

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

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

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

And I click on "Save Repositories" 729ms

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

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Add the repository to the terminal child channel

< 1ms 9

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

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

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

And I click on "Update Channel" 0s

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

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

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

And I click on "Save Repositories" 0s

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

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

480ms 1

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

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 540ms 10

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

And I follow "Create Channel" 265ms

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

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

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

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

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

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

And I click on "Create Channel" 612ms

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

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

6s 556ms 1

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

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 403ms 10

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

And I follow "Create Channel" 325ms

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

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

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

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

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

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

And I click on "Create Channel" 533ms

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

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

4s 39ms 1

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

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

1s 410ms 10

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

And I follow "Create Channel" 331ms

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

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

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

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

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

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

And I click on "Create Channel" 515ms

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

@deblike_minion

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

6s 912ms 1

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

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

942ms 10

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

And I follow "Create Channel" 340ms

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

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

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

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

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

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

And I click on "Create Channel" 54ms

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

@rhlike_minion

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

4s 713ms 1

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

Feature:Synchronize fake channels 1m 6s 484ms 12 2

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

Scenario:
Log in as admin user

1s 988ms 2

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

And I enable source package syncing 1s 537ms

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

3s 711ms 9

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

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

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

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

And I follow "Sync" 379ms

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

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

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

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

@sle_minion

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

4s 740ms 2

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

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

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

3s 648ms 9

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

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

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

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

And I follow "Sync" 298ms

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

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

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

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

Scenario:
Synchronize Test-Child-Channel-x86_64 channel

24s 614ms 9

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

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

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

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

And I follow "Sync" 687ms

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

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

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

And I wait until the channel "test-child-channel-x86_64" has been synced 21s 11ms

@sle_minion

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

3s 683ms 9

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

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

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

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

And I follow "Sync" 400ms

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

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

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

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

@deblike_minion

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

4s 154ms 9

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

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

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

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

And I follow "Sync" 853ms

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

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

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

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

@rhlike_minion

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

4s 293ms 9

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

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

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

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

And I follow "Sync" 914ms

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

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

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

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

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 112ms 9

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

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

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

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

And I follow "Sync" 760ms

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

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

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

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

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

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

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

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

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

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

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

Scenario:
Refresh the channel's repository data

4s 53ms 6

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

And I follow "channel-repodata-default" 315ms

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

And I click on "Single Run Schedule" 449ms

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

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

Scenario:
Cleanup disable source package syncing

991ms 1

Then I disable source package syncing 991ms

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

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

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

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

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

And I follow "Sync" 466ms

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

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

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

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

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

4s 378ms 9

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

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

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

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

And I follow "Sync" 907ms

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

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

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

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

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 143ms 9

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

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

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

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

And I follow "Sync" 605ms

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

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

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

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

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

4s 229ms 9

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

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

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

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

And I follow "Sync" 604ms

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

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

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

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

525ms 1

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

@sle_minion

Scenario:
Create an activation key with a channel

2s 293ms 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 734ms

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

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

2s 84ms 2

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

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

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

3s 131ms 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 850ms

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

@ssh_minion

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

1s 754ms 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" 869ms

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

@ssh_minion

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

1s 911ms 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" 792ms

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

@proxy

Scenario:
Create an activation key for the proxy

1s 960ms 2

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

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

@build_host

Scenario:
Create an activation key for the build host

2s 538ms 3

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

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

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

@scc_credentials

Scenario:
Create an activation key for the terminal

2s 169ms 2

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

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

Feature:Update activation keys 22s 876ms 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

464ms 1

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 707ms

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 631ms

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 567ms

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

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

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

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

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

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

And I wait for child channels to appear 522ms

And I include the recommended child channels 155ms

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 644ms

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

@scc_credentials @uyuni @build_host

Scenario:
Update build host key with Uyuni client tools

2s 14ms 9

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

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

And I wait for child channels to appear 824ms

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

And I wait for child channels to appear 263ms

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

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

And I click on "Update Activation Key" 591ms

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

@skip_if_github_validation @scc_credentials @uyuni @build_host

Scenario:
Update build host key with dev child channel

2s 57ms 9

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

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

And I wait for child channels to appear 911ms

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

And I wait for child channels to appear 266ms

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

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

And I click on "Update Activation Key" 565ms

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

@scc_credentials @build_host

Scenario:
Update terminal key with synced base product

2s 879ms 16

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

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

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

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

And I wait for child channels to appear 452ms

And I include the recommended child channels 157ms

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

And I wait until "SLE-Module-Basesystem15-SP7-Updates for x86_64" has been checked 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" 69ms

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

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

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

And I click on "Update Activation Key" 596ms

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

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

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

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

And I wait for child channels to appear 851ms

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

And I click on "Update Activation Key" 608ms

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

@skip_if_github_validation @deblike_minion

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

1s 609ms 6

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

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

And I wait for child channels to appear 788ms

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

And I click on "Update Activation Key" 532ms

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

@skip_if_github_validation @rhlike_minion

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

1s 673ms 6

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

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

And I wait for child channels to appear 793ms

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

And I click on "Update Activation Key" 590ms

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

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

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

@sle_minion

Scenario:
Create the bootstrap repository for SUSE Minion

2s 310ms 1

base_channel: openSUSE Tumbleweed (x86_64)
channel: openSUSE-Tumbleweed-x86_64-uyuni
parent_channel:
Creating the bootstrap repository on the server:
mgr-create-bootstrap-repo --create openSUSE-Tumbleweed-x86_64-uyuni --with-custom-channels

When I create the bootstrap repository for "sle_minion" on the server 2s 310ms

@proxy

Scenario:
Create the bootstrap repository for Proxy

2s 180ms 1

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

@build_host

Scenario:
Create the bootstrap repository for Build Host

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

@containerized_server @scope_containerized_proxy @proxy
Feature:Setup containerized proxy 3m 21s 558ms 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 625ms 1

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

@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

27s 75ms 1

Given I am authorized for the "Admin" section 27s 75ms

Scenario:
Bootstrap the proxy host as a salt minion

37s 155ms 9

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 112ms

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

@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 24s 61ms 1

When I wait until onboarding is completed for "proxy" 1m 24s 61ms

Scenario:
Generate containerized proxy configuration

11s 338ms 2

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

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

Scenario:
Set up the containerized proxy service to support Avahi

< 1ms 1

Record not added - avahi domain was not detected

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

Scenario:
Run a containerized proxy

17s 649ms 1

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

Scenario:
Wait until containerized proxy service is active

5s 818ms 10

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

And I wait until "uyuni-proxy-httpd" service is active on "proxy" 2s 772ms

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

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

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

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

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

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

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

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

Scenario:
The containerized proxy should be registered automatically

727ms 2

When I follow the left menu "Systems" 106ms

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

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

11s 105ms 3

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

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

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

@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 548ms 1 6

Scenario:
Log in as admin user

20s 731ms 1

Given I am authorized for the "Admin" section 20s 731ms 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:591:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:459: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 556ms 13 1

When I follow the left menu "Systems > Bootstrapping" 20s 556ms 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:413:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:405:in `each'
./features/step_definitions/navigation_steps.rb:405:in `each_with_index'
./features/step_definitions/navigation_steps.rb:405: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

4s 835ms 3 1

Given I am on the Systems overview page of this "deblike_minion" 4s 835ms 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:472: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

4s 884ms 3 1

Given I am on the Systems overview page of this "proxy" 4s 884ms 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:474: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

743ms 10 1

Given I am on the Systems overview page of this "deblike_minion" 743ms 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:472: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

497ms 1

* Mon Nov 24 2025 Alexander Graul
- Add minimum_auth_version to enforce security (CVE-2025-62349)
- Backport security fixes for vendored tornado
* BDSA-2024-3438
* BDSA-2024-3439
* BDSA-2024-9026
- Junos module yaml loader fix (CVE-2025-62348)
- Added:
* backport-3006.17-security-fixes-739.patch
* Tue Nov 11 2025 Marek Czernek
- Fix TLS and x509 modules for OSes with older cryptography module
- Added:
* fix-tls-and-x509-modules-for-older-cryptography-modu.patch
* Fri Nov 7 2025 Pablo Suárez Hernández
- Fix Salt for Python > 3.11 (bsc#1252285) (bsc#1252244)

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

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

299ms 1 1

Given I am on the Systems overview page of this "deblike_minion" 299ms 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:472: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 2m 2s 875ms 1 6

Scenario:
Log in as admin user

21s 853ms 1

Given I am authorized for the "Admin" section 21s 853ms 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:591:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:459: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

45s 775ms 12 1

When I follow the left menu "Systems > Bootstrapping" 45s 775ms Show Error +

                                            
 Unable to find xpath "//aside/div[@id='nav']/nav/ul/li/div/a[contains(.,'Systems')]/parent::div/parent::li" (Capybara::ElementNotFound)
./features/step_definitions/navigation_steps.rb:413:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:405:in `each'
./features/step_definitions/navigation_steps.rb:405:in `each_with_index'
./features/step_definitions/navigation_steps.rb:405: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 465ms 3 1

Given I am on the Systems overview page of this "rhlike_minion" 2s 465ms 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:472: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

23s 355ms 4 1

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

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

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

Then I should see "rhlike_minion" hostname 10s 29ms Show Error +

                                            
 Hostname uyuni-master-rhlike-minion.sumaci.aws is not present (ScriptError)
./features/step_definitions/navigation_steps.rb:675:in `/^I should see "([^"]*)" hostname$/'
features/init_clients/min_rhlike_salt.feature:40:in `I should see "rhlike_minion" hostname'

8s 893ms Show Info +

12:03:39:000 - 12:03:55:000 | Current URL: https://uyuni-master-server.sumaci.aws/

Screenshot +

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

14s 241ms 1 10 1

Given I am on the Systems overview page of this "rhlike_minion" 328ms 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:472: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

13s 912ms Show Info +

12:04:03:000 - 12:04:04:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/YourRhn.do

Screenshot +

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

341ms 1

* Mon Nov 24 2025 Alexander Graul
- Add minimum_auth_version to enforce security (CVE-2025-62349)
- Backport security fixes for vendored tornado
* BDSA-2024-3438
* BDSA-2024-3439
* BDSA-2024-9026
- Junos module yaml loader fix (CVE-2025-62348)
- Added:
* backport-3006.17-security-fixes-739.patch

* Tue Nov 11 2025 Marek Czernek
- Fix TLS and x509 modules for OSes with older cryptography module
- Added:
* fix-tls-and-x509-modules-for-older-cryptography-modu.patch

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

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

14s 842ms 1 1 1

Given I am on the Systems overview page of this "rhlike_minion" 332ms 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:472: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

14s 510ms Show Info +

12:05:07:000 - 12:05:08:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/YourRhn.do

Screenshot +

@build_host
Feature:Bootstrap a build host via the GUI 10m 50s 100ms 1 8

Scenario:
Clean up sumaform leftovers on build host

8s 650ms 1

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

Scenario:
Log in as admin user

13s 463ms 1

Given I am authorized for the "Admin" section 13s 463ms 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:591:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:459: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

41s 419ms 9 1

When I follow the left menu "Systems > Bootstrapping" 41s 419ms 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:413:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:405:in `each'
./features/step_definitions/navigation_steps.rb:405:in `each_with_index'
./features/step_definitions/navigation_steps.rb:405: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

8m 21s 95ms 3 2 1

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

Then I should see a "accepted" text 438ms

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

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

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

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

Then the Salt master can reach "build_host" 0s

@proxy

Scenario:
Check connection from build host to proxy

14s 474ms 1 3 1

Given I am on the Systems overview page of this "build_host" 334ms 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:472: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

14s 140ms Show Info +

12:11:32:000 - 12:11:33:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/YourRhn.do

Screenshot +

@proxy

Scenario:
Check registration on build host of minion

27s 954ms 4 1

Given I am on the Systems overview page of this "proxy" 3s 708ms

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

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

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

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

13s 942ms Show Info +

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

Screenshot +

Scenario:
Detect latest Salt changes on the SLES build host

14s 482ms 1 1

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

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

13s 959ms Show Info +

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

Screenshot +

Scenario:
Check that the build host is a build host

14s 267ms 1 2 1

Given I am on the Systems overview page of this "build_host" 304ms 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:472:in `/^I am on the Systems overview page of this "([^"]*)"$/'
features/init_clients/buildhost_bootstrap.feature:52:in `I am on the Systems overview page of this "build_host"'

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

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

13s 962ms Show Info +

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

Screenshot +

Scenario:
Check events history for failures on SLES build host

14s 293ms 1 1 1

Given I am on the Systems overview page of this "build_host" 372ms 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:472:in `/^I am on the Systems overview page of this "([^"]*)"$/'
features/init_clients/buildhost_bootstrap.feature:57:in `I am on the Systems overview page of this "build_host"'

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

13s 920ms Show Info +

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

Screenshot +

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

Scenario:
Clean up sumaform leftovers on SLES minion

10s 457ms 1

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

Scenario:
Log in as admin user

31s 563ms 1

Given I am authorized for the "Admin" section 31s 563ms 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:591:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:459: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

45s 436ms 10 1

When I follow the left menu "Systems > Bootstrapping" 45s 436ms Show Error +

                                            
 Unable to find xpath "//aside/div[@id='nav']/nav/ul/li/div/a[contains(.,'Systems')]/parent::div/parent::li" (Capybara::ElementNotFound)
./features/step_definitions/navigation_steps.rb:413:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:405:in `each'
./features/step_definitions/navigation_steps.rb:405:in `each_with_index'
./features/step_definitions/navigation_steps.rb:405: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

10s 7ms 7 1

When I follow the left menu "Salt > Keys" 10s 7ms Show Error +

                                            
 Unable to find xpath "//aside/div[@id='nav']/nav/ul/li/div/a[contains(.,'Salt')]/parent::div/parent::li" (Capybara::ElementNotFound)
./features/step_definitions/navigation_steps.rb:413:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:405:in `each'
./features/step_definitions/navigation_steps.rb:405:in `each_with_index'
./features/step_definitions/navigation_steps.rb:405: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

14s 949ms 1 3 1

Given I am on the Systems overview page of this "sle_minion" 306ms 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:472: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

14s 642ms Show Info +

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

Screenshot +

@proxy

Scenario:
Check registration on proxy of minion

14s 277ms 1 2 1

Requested /rhn/systems/details/Overview.do?sid=1000010000, got https://uyuni-master-server.sumaci.aws/rhn/manager/login?url_bounce=%2Frhn%2Fsystems%2Fdetails%2FOverview.do%3Fsid%3D1000010000&request_method=GET

Given I am on the Systems overview page of this "proxy" 3s 640ms

When I follow "Details" in the content area 10s 636ms Show Error +

                                            
 stale element reference: stale element not found
  (Session info: chrome=143.0.7499.192); For documentation on this error, please visit: https://www.selenium.dev/documentation/webdriver/troubleshooting/errors#staleelementreferenceexception (Selenium::WebDriver::Error::StaleElementReferenceError)
./features/support/commonlib.rb:198:in `click_link_and_wait'
./features/step_definitions/navigation_steps.rb:338:in `/^I follow "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:360:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:359:in `/^I follow "([^"]*)" in the (.+)$/'
features/init_clients/sle_minion.feature:55:in `I follow "Details" in the content area'

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 46s 71ms 1 4 2

Scenario:
Clean up sumaform leftovers on SLES SSH minion

11s 289ms 1

When I perform a full salt minion cleanup on "ssh_minion" 11s 289ms

Scenario:
Log in as admin user

10s 148ms 1

Given I am authorized for the "Admin" section 10s 148ms 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:591:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:459: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

19s 684ms 10 1

When I follow the left menu "Systems > Bootstrapping" 19s 684ms 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:413:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:405:in `each'
./features/step_definitions/navigation_steps.rb:405:in `each_with_index'
./features/step_definitions/navigation_steps.rb:405: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

317ms 3 1

Given I am on the Systems overview page of this "ssh_minion" 317ms 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:472:in `/^I am on the Systems overview page of this "([^"]*)"$/'
features/init_clients/sle_ssh_minion.feature:37:in `I am on the Systems overview page of this "ssh_minion"'

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

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

Then I should see "proxy" short hostname 0s

@proxy

Scenario:
Check registration on proxy of SSH minion

4s 631ms 3 1

Given I am on the Systems overview page of this "proxy" 4s 631ms 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:474:in `/^I am on the Systems overview page of this "([^"]*)"$/'
features/init_clients/sle_ssh_minion.feature:44: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 "ssh_minion" hostname 0s

@transactional_server
Feature:SELinux debugging < 1ms 1

In order for the server to behave correctly after a reboot
I want to be sure that there is no wrong SELinux label

Scenario:
No previous operation has created wrong SELinux label

< 1ms 1

Then files on container volumes should all have the proper SELinux label 0s

@new_issue
Feature:Debug the server after the testsuite has run 18s 288ms 5

Scenario:
Call spacewalk-debug on server

14s 416ms 1

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

Scenario:
Check the tomcat logs on server

689ms 1

Then the tomcat logs should not contain errors 689ms

Scenario:
Check salt event log for failures on server

1s 794ms 1

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

Scenario:
Check the taskomatic logs on server

735ms 1

Then the taskomatic logs should not contain errors 735ms

Scenario:
Check for out of memory errors

652ms 1

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

Feature:Debug the clients after the testsuite has run 1m 32s 387ms 1

Scenario:
Extract the logs from all our clients

1m 32s 387ms 1

When I extract the log files from all our active nodes 1m 32s 387ms

@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 569ms 4

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

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

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

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

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

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

@custom_download_endpoint Scenario:The custom download endpoint is working 656ms 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 394ms 7

@scc_credentials Feature:List available channels and enable them 1m 36s 788ms 5 1

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

@scc_credentials Scenario:Refresh SCC 25s 477ms 1

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

@scc_credentials Scenario:Use the products and architecture filters 2s 715ms 7

@scc_credentials @susemanager Scenario:View the channels list in the products page < 1ms 9

@scc_credentials @susemanager Scenario:Synchronize SLES 15 SP7 product with recommended sub-products, including MLM Client Tools < 1ms 30

@uyuni Scenario:Partially add openSUSE Tumbleweed product, only including the required packages to generate the bootstrap repository 3m 34s 980ms 4

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

@scc_credentials @uyuni @build_host Scenario:Synchronize SLES 15 SP7 product with recommended sub-products for Retail feature 39m 36s 12ms 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 560ms 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 884ms 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 880ms 11

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

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

@rhlike_minion Scenario:Create a fake AppStream repository 980ms 7

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

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

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

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

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

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

@deblike_minion Scenario:Add the repository to the Debian-like base channel 1s 321ms 6

@pxeboot_minion @uyuni @scc_credentials Scenario:Add the repository to the terminal child channel < 1ms 9

@skip_if_github_validation Feature:Create custom channels with development repositories 27s 999ms 9

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

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

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

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

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

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

@rhlike_minion Scenario:Create a custom channel for RH-like minions 942ms 10

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

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

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

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

@sle_minion Scenario:Synchronize Fake-Child-Channel-SUSE-like channel 3s 683ms 9

@deblike_minion Scenario:Synchronize Fake-Base-Channel-Debian-like channel 4s 154ms 9

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

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

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

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

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

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

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

@proxy

Scenario:
The proxy is healthy

4s 569ms 4

@sle_minion

Scenario:
The minion is healthy

6s 584ms 4

@build_host

Scenario:
The build host is healthy

3s 936ms 4

@ssh_minion

Scenario:
The SSH minion is healthy

6s 718ms 4

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 759ms 4

@deblike_minion

Scenario:
The Debian-like minion is healthy

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

676ms 1

@no_auth_registry

Scenario:
The registry without authentication is healthy

658ms 1

@custom_download_endpoint

Scenario:
The custom download endpoint is working

656ms 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 394ms 7

@scc_credentials
Feature:List available channels and enable them 1m 36s 788ms 5 1

@proxy @susemanager

Scenario:
List all products for SUSE Multi-Linux Manager

< 1ms 6

@scc_credentials

Scenario:
Refresh SCC

25s 477ms 1

@scc_credentials

Scenario:
Let the products page appear

2s 269ms 6

@scc_credentials

Scenario:
Use the products and architecture filters

2s 715ms 7

@scc_credentials @susemanager

Scenario:
View the channels list in the products page

< 1ms 9

@scc_credentials @susemanager

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

< 1ms 30

@uyuni

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

3m 34s 980ms 4

@containerized_server @proxy @uyuni

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

1m 10s 367ms 2

@scc_credentials @uyuni @build_host

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

39m 36s 12ms 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 560ms 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 884ms 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 880ms 11

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 383ms 10

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 272ms 10

@rhlike_minion

Scenario:
Create a fake AppStream repository

980ms 7

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

10s 937ms 6

@sle_minion

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

1s 844ms 9

@rhlike_minion

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

2s 724ms 9

@rhlike_minion

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

2s 702ms 9

@sle_minion

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

1s 498ms 6

@deblike_minion

Scenario:
Create a fake repository for Debian-like

662ms 7

@deblike_minion

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

1s 321ms 6

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Add the repository to the terminal child channel

< 1ms 9

@skip_if_github_validation
Feature:Create custom channels with development repositories 27s 999ms 9

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 540ms 10

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

6s 556ms 1

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 403ms 10

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

4s 39ms 1

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

1s 410ms 10

@deblike_minion

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

6s 912ms 1

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

942ms 10

@rhlike_minion

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

4s 713ms 1

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

3s 711ms 9

@sle_minion

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

4s 740ms 2

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

3s 648ms 9

@sle_minion

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

3s 683ms 9

@deblike_minion

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

4s 154ms 9

@rhlike_minion

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

4s 293ms 9

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 112ms 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 679ms 4

@sle_minion

Scenario:
Synchronize Devel-SUSE-Channel channel

3s 927ms 9

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

4s 378ms 9

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 143ms 9

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

4s 229ms 9

@sle_minion

Scenario:
Create an activation key with a channel

2s 293ms 2

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

2s 84ms 2

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

3s 131ms 2

@ssh_minion

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

1s 754ms 2

@ssh_minion

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

1s 911ms 2

@proxy

Scenario:
Create an activation key for the proxy

1s 960ms 2

@build_host

Scenario:
Create an activation key for the build host

2s 538ms 3

@scc_credentials

Scenario:
Create an activation key for the terminal

2s 169ms 2

@scc_credentials @susemanager

Scenario:
Update SLE key with synced base product

< 1ms 20