Cucumber Feature Report

All Scenarios

201

Passed Scenarios

133

Failed Scenarios

29

Skipped Scenarios

39

Execution Time: 68m 9s 345ms

Expand All | Collapse All

Metadata

App Version: Uyuni/Head

Browser: Chrome

Platform: x86_64

Parallel: Disabled

Feature:Sanity checks 43s 673ms 10 2

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

Scenario:
The server is healthy

11s 755ms 19

Then "server" should have a FQDN 382ms

And reverse resolution should work for "server" 630ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@proxy

Scenario:
The proxy is healthy

4s 450ms 4

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

And reverse resolution should work for "proxy" 306ms

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

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

@sle_minion

Scenario:
The minion is healthy

6s 321ms 4

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

And reverse resolution should work for "sle_minion" 415ms

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

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

@build_host

Scenario:
The build host is healthy

3s 722ms 4

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

And reverse resolution should work for "build_host" 231ms

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

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

@ssh_minion

Scenario:
The SSH minion is healthy

6s 232ms 4

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

And reverse resolution should work for "ssh_minion" 396ms

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

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

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 121ms 4

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

And reverse resolution should work for "rhlike_minion" 183ms

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

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

@deblike_minion

Scenario:
The Debian-like minion is healthy

6s 22ms 4

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

And reverse resolution should work for "deblike_minion" 219ms

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

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

@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

733ms 1

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

@no_auth_registry

Scenario:
The registry without authentication is healthy

646ms 1

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

@custom_download_endpoint

Scenario:
The custom download endpoint is working

669ms 1

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

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

663ms 1

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

@skip_if_containerized_server

Scenario:
Create admin user and first organization

< 1ms 12

Given I access the host the first time 0s

When I go to the home page 0s

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

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

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

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

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

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

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

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

And I click on "Create Organization" 0s

Then I am logged in 0s

Scenario:
Log in as admin user

39s 559ms 1

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

Scenario:
Wait for refresh of list of products to finish

3s 541ms 1

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

Scenario:
Create testing username

2s 263ms 12

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

And I follow "Create User" 748ms

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

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

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

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

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

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

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

And I click on "Create Login" 875ms

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

And I should see a "testing" link 11ms

Scenario:
Grant testing user administrative priviledges

1s 744ms 10

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

And I follow "testing" 524ms

And I check "role_org_admin" 82ms

And I check "role_system_group_admin" 75ms

And I check "role_channel_admin" 75ms

And I check "role_activation_key_admin" 77ms

And I check "role_config_admin" 73ms

And I click on "Update" 637ms

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

And I should see a "testing" text 62ms

@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

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

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

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

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

@scc_credentials @no_mirror

Scenario:
Enter valid SCC credentials

< 1ms 6

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

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

And I ask to add new credentials 0s

And I enter the SCC credentials 0s

And I click on "Save" 0s

And I wait until the SCC credentials are valid 0s

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

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

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

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

And I click on "Save Preferences" 662ms

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

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

3s 547ms 5

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

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

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

And I click on "Save Preferences" 748ms

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

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

Scenario:
Create a Kiwi user with image administrators rights

4s 72ms 2

New user kiwikiwi created with roles: image_admin

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

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

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

Scenario:
Create a Docker user with image administrators rights

2s 31ms 2

New user docker created with roles: image_admin

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

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

@no_auth_registry

Scenario:
Create an image store without credentials

3s 175ms 7

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

And I follow "Create" 522ms

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

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

And I click on "create-btn" 192ms

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

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

Feature:Do not let Taskomatic tasks interfere with our CI tests 34s 336ms 3

Scenario:
Log in as admin user

26s 717ms 1

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

Scenario:
Disable scheduled reposyncs

4s 570ms 5

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

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

And I choose "disabled" 55ms

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

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

Scenario:
Disable scheduled Cobbler syncs

3s 49ms 5

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

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

And I choose "disabled" 45ms

And I click on "Update Schedule" 52ms

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

@scc_credentials
Feature:List available channels and enable them 1m 35s 597ms 5 1

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

Scenario:
List available channels

29s 774ms 5

When I refresh SCC 27s 529ms

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

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

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

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

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

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

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

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

When I remove the mgr-sync cache file 629ms

And I execute mgr-sync refresh 1m 770ms

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

Feature:Synchronize products in the products page of the Setup Wizard 47m 41s 650ms 8 9

@scc_credentials

Scenario:
Refresh SCC

25s 34ms 1

When I refresh SCC 25s 34ms

@scc_credentials

Scenario:
Let the products page appear

2s 49ms 6

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

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

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

Then I should see a "Arch" text 102ms

And I should see a "Channels" text 102ms

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

@scc_credentials

Scenario:
Use the products and architecture filters

2s 301ms 7

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

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

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

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

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

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

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

@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 25s 861ms 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 361ms

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

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

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

@containerized_server @proxy @uyuni

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

1m 25s 300ms 2

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

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

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

@scc_credentials @uyuni @build_host

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

And I wait until all synchronized channels for "sles15-sp7" have finished 41m 16s 779ms

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

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

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

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

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

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

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

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

@scc_credentials @skip_if_github_validation

Scenario:
Report the synchronization duration for SLES 15 SP7

< 1ms 1

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

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

472ms 1

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

Scenario:
Add a fake base channel for x86_64

1s 627ms 10

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

And I follow "Create Channel" 371ms

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

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

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

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

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

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

And I click on "Create Channel" 561ms

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

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

1s 372ms 10

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

And I follow "Create Channel" 297ms

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

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

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

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

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

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

And I click on "Create Channel" 531ms

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

@sle_minion

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

1s 357ms 10

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

And I follow "Create Channel" 297ms

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

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

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

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

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

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

And I click on "Create Channel" 538ms

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

Scenario:
Add a fake base channel for i586

1s 381ms 10

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

And I follow "Create Channel" 296ms

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

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

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

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

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

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

And I click on "Create Channel" 550ms

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

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

1s 451ms 10

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

And I follow "Create Channel" 396ms

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

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

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

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

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

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

And I click on "Create Channel" 527ms

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

Scenario:
Add a test base channel for x86_64

946ms 10

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

And I follow "Create Channel" 378ms

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

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

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

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

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

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

And I click on "Create Channel" 54ms

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

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

1s 382ms 10

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

And I follow "Create Channel" 307ms

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

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

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

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

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

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

And I click on "Create Channel" 521ms

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

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

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

And I follow "Create Channel" 301ms

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

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

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

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

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

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

And I uncheck "gpg_check" 10s 63ms

And I click on "Create Channel" 532ms

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

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 312ms 10

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

And I follow "Create Channel" 315ms

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

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

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

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

And I click on "Create Channel" 475ms

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

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 321ms 10

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

And I follow "Create Channel" 306ms

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:" 33ms

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

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

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

461ms 1

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

Scenario:
Create a fake repository for distributions using RPM

1s 177ms 7

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

And I follow "Create Repository" 350ms

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

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

And I click on "Create Repository" 61ms

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

And I should see "metadataSigned" as checked 18ms

Scenario:
Disable metadata check for the fake RPM repository

10s 948ms 6

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

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

And I uncheck "metadataSigned" 10s 75ms

And I click on "Update Repository" 453ms

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

And I should see "metadataSigned" as unchecked 16ms

@rhlike_minion

Scenario:
Create a fake AppStream repository

1s 8ms 7

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

And I follow "Create Repository" 278ms

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

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

And I click on "Create Repository" 53ms

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

And I should see "metadataSigned" as checked 15ms

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

10s 915ms 6

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

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

And I uncheck "metadataSigned" 10s 69ms

And I click on "Update Repository" 416ms

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

And I should see "metadataSigned" as unchecked 15ms

@sle_minion

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

1s 907ms 9

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

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

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

And I click on "Update Channel" 518ms

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

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

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

And I click on "Save Repositories" 595ms

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

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

2s 516ms 9

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

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

And I click on "Update Channel" 54ms

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

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

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

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

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

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

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

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

And I click on "Update Channel" 521ms

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

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

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

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

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

@rhlike_minion

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

2s 708ms 9

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

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

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

And I click on "Update Channel" 573ms

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

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

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

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

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

Scenario:
Create a fake repository for i586

11s 140ms 7

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

And I follow "Create Repository" 359ms

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

And I click on "Create Repository" 427ms

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

Scenario:
Add the repository to the i586 channel

1s 783ms 9

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

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

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

And I click on "Update Channel" 494ms

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

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

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

And I click on "Save Repositories" 518ms

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

@sle_minion

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

1s 758ms 6

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

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

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

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

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

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

@deblike_minion

Scenario:
Create a fake repository for Debian-like

1s 139ms 7

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

And I follow "Create Repository" 285ms

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

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

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

And I click on "Create Repository" 523ms

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

@deblike_minion

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

1s 338ms 6

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

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

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

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

And I click on "Save Repositories" 665ms

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

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

537ms 1

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

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 526ms 10

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

And I follow "Create Channel" 330ms

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

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

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

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

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

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

And I click on "Create Channel" 542ms

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

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

6s 576ms 1

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

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 816ms 10

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

And I follow "Create Channel" 499ms

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

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

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

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

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

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

And I click on "Create Channel" 775ms

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

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

4s 9ms 1

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

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

872ms 10

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

And I follow "Create Channel" 258ms

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

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

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

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

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

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

And I click on "Create Channel" 55ms

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

7s 101ms 1

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

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 370ms 10

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

And I follow "Create Channel" 339ms

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

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

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

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

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

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

And I click on "Create Channel" 484ms

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

@rhlike_minion

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

4s 345ms 1

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

Feature:Synchronize fake channels 1m 6s 549ms 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 853ms 2

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

And I enable source package syncing 1s 429ms

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

3s 881ms 9

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

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

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

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

And I follow "Sync" 304ms

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

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

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

@sle_minion

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

4s 745ms 2

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

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

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

3s 656ms 9

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

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

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

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

And I follow "Sync" 380ms

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

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

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

Scenario:
Synchronize Test-Child-Channel-x86_64 channel

4s 256ms 9

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

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

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

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

And I follow "Sync" 778ms

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

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

@sle_minion

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

24s 651ms 9

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

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

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

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

And I follow "Sync" 761ms

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

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

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

@deblike_minion

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

3s 658ms 9

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

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

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

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

And I follow "Sync" 307ms

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

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

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

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

@rhlike_minion

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

4s 127ms 9

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

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

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

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

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

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

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 230ms 9

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

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

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

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

And I follow "Sync" 860ms

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

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

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

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

@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

5s 489ms 6

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

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

And I follow "errata-cache-bunch" 349ms

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

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

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

Scenario:
Refresh the channel's repository data

5s 15ms 6

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

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

And I follow "channel-repodata-bunch" 354ms

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

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

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

Scenario:
Cleanup disable source package syncing

984ms 1

Then I disable source package syncing 984ms

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

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

@sle_minion

Scenario:
Synchronize Devel-SUSE-Channel channel

4s 3ms 9

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

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

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

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

And I follow "Sync" 725ms

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

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

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

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

4s 223ms 9

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

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

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

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

And I follow "Sync" 836ms

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

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

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

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

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 148ms 9

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

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

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

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

And I follow "Sync" 758ms

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

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

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

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

3s 974ms 9

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

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

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

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

And I follow "Sync" 674ms

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

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

Feature:Create activation keys 19s 249ms 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

538ms 1

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

@sle_minion

Scenario:
Create an activation key with a channel

2s 361ms 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 608ms

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

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

2s 833ms 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 464ms

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

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

2s 308ms 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 497ms

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

@ssh_minion

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

2s 22ms 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" 830ms

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

@ssh_minion

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

2s 188ms 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" 954ms

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

@proxy

Scenario:
Create an activation key for the proxy

2s 205ms 2

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

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

@build_host

Scenario:
Create an activation key for the build host

2s 483ms 3

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

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

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

@scc_credentials

Scenario:
Create an activation key for the terminal

2s 306ms 2

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

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

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

461ms 1

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 58ms

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

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

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

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

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

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

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

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

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

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

@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 106ms 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 69ms

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

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

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

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

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

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

And I click on "Update Activation Key" 587ms

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

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

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

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

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

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

And I wait for child channels to appear 540ms

And I include the recommended child channels 190ms

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 603ms

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

@scc_credentials @uyuni @build_host

Scenario:
Update build host key with Uyuni client tools

2s 70ms 9

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

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

And I wait for child channels to appear 892ms

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

And I wait for child channels to appear 273ms

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

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

And I click on "Update Activation Key" 603ms

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

@skip_if_github_validation @scc_credentials @uyuni @build_host

Scenario:
Update build host key with dev child channel

2s 45ms 9

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

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

And I wait for child channels to appear 894ms

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

And I wait for child channels to appear 265ms

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

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

And I click on "Update Activation Key" 585ms

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

@scc_credentials @build_host

Scenario:
Update terminal key with synced base product

3s 79ms 16

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

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

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

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

And I wait for child channels to appear 456ms

And I include the recommended child channels 169ms

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 569ms

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

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

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

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

And I wait for child channels to appear 787ms

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

And I click on "Update Activation Key" 593ms

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

@skip_if_github_validation @deblike_minion

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

1s 679ms 6

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

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

And I wait for child channels to appear 787ms

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

And I click on "Update Activation Key" 603ms

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

@skip_if_github_validation @rhlike_minion

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

1s 633ms 6

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

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

And I wait for child channels to appear 796ms

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

And I click on "Update Activation Key" 554ms

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

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

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

@sle_minion

Scenario:
Create the bootstrap repository for SUSE Minion

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

@proxy

Scenario:
Create the bootstrap repository for Proxy

2s 193ms 1

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

@build_host

Scenario:
Create the bootstrap repository for Build Host

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

@containerized_server @scope_containerized_proxy @proxy
Feature:Setup containerized proxy 3m 14s 813ms 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 502ms 1

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

@transactional_server

Scenario:
Reboot after clean up

< 1ms 1

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

Scenario:
Log in as admin user

26s 772ms 1

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

Scenario:
Bootstrap the proxy host as a salt minion

35s 58ms 9

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 60ms

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

@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 21s 774ms 1

When I wait until onboarding is completed for "proxy" 1m 21s 774ms

Scenario:
Generate containerized proxy configuration

10s 870ms 2

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

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

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

16s 872ms 1

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

Scenario:
Wait until containerized proxy service is active

5s 371ms 10

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

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

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

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

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

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

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

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

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

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

Scenario:
The containerized proxy should be registered automatically

651ms 2

When I follow the left menu "Systems" 59ms

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

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

10s 939ms 3

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

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

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

@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 1m 56s 658ms 1 6

Scenario:
Log in as admin user

20s 534ms 1

Given I am authorized for the "Admin" section 20s 534ms 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 484ms 13 1

When I follow the left menu "Systems > Bootstrapping" 20s 484ms 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

19s 348ms 1 3 1

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

14s 568ms Show Info +

18:27:54:000 - 18:27:59:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/YourRhn.do

Screenshot +

@proxy

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

27s 399ms 4 1

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

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

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

Then I should see "deblike_minion" hostname 10s 7ms Show Error +

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

13s 663ms Show Info +

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

Screenshot +

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

13s 897ms 1 10 1

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

13s 592ms Show Info +

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

Screenshot +

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

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

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

14s 13ms 1 1 1

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

13s 696ms Show Info +

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

Screenshot +

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

Scenario:
Log in as admin user

21s 771ms 1

Given I am authorized for the "Admin" section 21s 771ms 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

41s 373ms 12 1

When I follow the left menu "Systems > Bootstrapping" 41s 373ms 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_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 196ms 3 1

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

6s 520ms 3 1

Given I am on the Systems overview page of this "proxy" 6s 520ms 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_rhlike_salt.feature:37:in `I am on the Systems overview page of this "proxy"'

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

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

Then I should see "rhlike_minion" hostname 0s

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

320ms 10 1

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

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

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

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

540ms 1 1

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

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

Scenario:
Clean up sumaform leftovers on build host

8s 121ms 1

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

Scenario:
Log in as admin user

33s 788ms 1

Given I am authorized for the "Admin" section 33s 788ms 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

20s 38ms 9 1

When I follow the left menu "Systems > Bootstrapping" 20s 38ms 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

12s 902ms 5 1

When I follow the left menu "Salt > Keys" 12s 902ms 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:26:in `I follow the left menu "Salt ) Keys"'

Then I should see a "accepted" text 0s

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

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

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

Then the Salt master can reach "build_host" 0s

@proxy

Scenario:
Check connection from build host to proxy

430ms 3 1

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

@proxy

Scenario:
Check registration on build host of minion

6s 331ms 3 1

Given I am on the Systems overview page of this "proxy" 6s 331ms 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/buildhost_bootstrap.feature:43:in `I am on the Systems overview page of this "proxy"'

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

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

Then I should see "build_host" hostname 0s

Scenario:
Detect latest Salt changes on the SLES build host

494ms 1

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

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

Scenario:
Check that the build host is a build host

337ms 2 1

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

Scenario:
Check events history for failures on SLES build host

343ms 1 1

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

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

Scenario:
Clean up sumaform leftovers on SLES minion

9s 916ms 1

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

Scenario:
Log in as admin user

10s 766ms 1

Given I am authorized for the "Admin" section 10s 766ms 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

42s 56ms 10 1

When I follow the left menu "Systems > Bootstrapping" 42s 56ms 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_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

12s 886ms 7 1

When I follow the left menu "Salt > Keys" 12s 886ms 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_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

491ms 3 1

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

@proxy

Scenario:
Check registration on proxy of minion

6s 343ms 3 1

Given I am on the Systems overview page of this "proxy" 6s 343ms 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_minion.feature:54:in `I am on the Systems overview page of this "proxy"'

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

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

Then I should see "sle_minion" hostname 0s

@ssh_minion
Feature:Bootstrap a Salt host managed via salt-ssh 1m 35s 555ms 1 4 2

Scenario:
Clean up sumaform leftovers on SLES SSH minion

9s 565ms 1

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

Scenario:
Log in as admin user

1m 468ms 1

Given I am authorized for the "Admin" section 1m 468ms Show Error +

                                            
 session not created
from chrome not reachable (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

18s 789ms 10 1

When I follow the left menu "Systems > Bootstrapping" 18s 789ms 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

460ms 3 1

Given I am on the Systems overview page of this "ssh_minion" 460ms 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

6s 271ms 3 1

Given I am on the Systems overview page of this "proxy" 6s 271ms 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 17s 513ms 5

Scenario:
Call spacewalk-debug on server

13s 864ms 1

When I execute spacewalk-debug on the server 13s 864ms

Scenario:
Check the tomcat logs on server

632ms 1

Then the tomcat logs should not contain errors 632ms

Scenario:
Check salt event log for failures on server

1s 728ms 1

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

Scenario:
Check the taskomatic logs on server

642ms 1

Then the taskomatic logs should not contain errors 642ms

Scenario:
Check for out of memory errors

645ms 1

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

Feature:Debug the clients after the testsuite has run 1m 27s 319ms 1

Scenario:
Extract the logs from all our clients

1m 27s 319ms 1

When I extract the log files from all our active nodes 1m 27s 319ms

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

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

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

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

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

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

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

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

@scc_credentials Feature:List available channels and enable them 1m 35s 597ms 5 1

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

@scc_credentials Scenario:Refresh SCC 25s 34ms 1

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

@scc_credentials Scenario:Use the products and architecture filters 2s 301ms 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 25s 861ms 4

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

@scc_credentials @uyuni @build_host Scenario:Synchronize SLES 15 SP7 product with recommended sub-products for Retail feature 41m 37s 685ms 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 418ms 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 357ms 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 436ms 11

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

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

@rhlike_minion Scenario:Create a fake AppStream repository 1s 8ms 7

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

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

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

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

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

@deblike_minion Scenario:Create a fake repository for Debian-like 1s 139ms 7

@deblike_minion Scenario:Add the repository to the Debian-like base channel 1s 338ms 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 28s 156ms 9

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

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

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

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

@deblike_minion Scenario:Create a custom channel for Debian-like minions 872ms 10

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

@rhlike_minion Scenario:Create a custom channel for RH-like minions 1s 370ms 10

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

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

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

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

@sle_minion Scenario:Synchronize Fake-Child-Channel-SUSE-like channel 24s 651ms 9

@deblike_minion Scenario:Synchronize Fake-Base-Channel-Debian-like channel 3s 658ms 9

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

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

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

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

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

@build_host @uyuni Scenario:Synchronize Devel-Build-Host-Channel channel 3s 974ms 9

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

@proxy

Scenario:
The proxy is healthy

4s 450ms 4

@sle_minion

Scenario:
The minion is healthy

6s 321ms 4

@build_host

Scenario:
The build host is healthy

3s 722ms 4

@ssh_minion

Scenario:
The SSH minion is healthy

6s 232ms 4

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 121ms 4

@deblike_minion

Scenario:
The Debian-like minion is healthy

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

733ms 1

@no_auth_registry

Scenario:
The registry without authentication is healthy

646ms 1

@custom_download_endpoint

Scenario:
The custom download endpoint is working

669ms 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 175ms 7

@scc_credentials
Feature:List available channels and enable them 1m 35s 597ms 5 1

@proxy @susemanager

Scenario:
List all products for SUSE Multi-Linux Manager

< 1ms 6

@scc_credentials

Scenario:
Refresh SCC

25s 34ms 1

@scc_credentials

Scenario:
Let the products page appear

2s 49ms 6

@scc_credentials

Scenario:
Use the products and architecture filters

2s 301ms 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 25s 861ms 4

@containerized_server @proxy @uyuni

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

1m 25s 300ms 2

@scc_credentials @uyuni @build_host

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

41m 37s 685ms 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 418ms 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 357ms 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 436ms 11

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 312ms 10

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 321ms 10

@rhlike_minion

Scenario:
Create a fake AppStream repository

1s 8ms 7

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

10s 915ms 6

@sle_minion

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

1s 907ms 9

@rhlike_minion

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

2s 698ms 9

@rhlike_minion

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

2s 708ms 9

@sle_minion

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

1s 758ms 6

@deblike_minion

Scenario:
Create a fake repository for Debian-like

1s 139ms 7

@deblike_minion

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

1s 338ms 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 28s 156ms 9

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 526ms 10

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

6s 576ms 1

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 816ms 10

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

4s 9ms 1

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

872ms 10

@deblike_minion

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

7s 101ms 1

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 370ms 10

@rhlike_minion

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

4s 345ms 1

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

3s 881ms 9

@sle_minion

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

4s 745ms 2

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

3s 656ms 9

@sle_minion

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

24s 651ms 9

@deblike_minion

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

3s 658ms 9

@rhlike_minion

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

4s 127ms 9

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 230ms 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 349ms 4

@sle_minion

Scenario:
Synchronize Devel-SUSE-Channel channel

4s 3ms 9

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

4s 223ms 9

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 148ms 9

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

3s 974ms 9

@sle_minion

Scenario:
Create an activation key with a channel

2s 361ms 2

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

2s 833ms 2

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

2s 308ms 2

@ssh_minion

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

2s 22ms 2

@ssh_minion

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

2s 188ms 2

@proxy

Scenario:
Create an activation key for the proxy

2s 205ms 2

@build_host

Scenario:
Create an activation key for the build host

2s 483ms 3

@scc_credentials

Scenario:
Create an activation key for the terminal

2s 306ms 2

@scc_credentials @susemanager

Scenario:
Update SLE key with synced base product

< 1ms 20