Cucumber Feature Report

All Scenarios

201

Passed Scenarios

133

Failed Scenarios

29

Skipped Scenarios

39

Execution Time: 84m 49s 730ms

Expand All | Collapse All

Metadata

App Version: Uyuni/Head

Browser: Chrome

Platform: x86_64

Parallel: Disabled

Feature:Sanity checks 43s 847ms 10 2

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

Scenario:
The server is healthy

11s 658ms 19

Then "server" should have a FQDN 383ms

And reverse resolution should work for "server" 619ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@proxy

Scenario:
The proxy is healthy

4s 454ms 4

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

And reverse resolution should work for "proxy" 283ms

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

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

@sle_minion

Scenario:
The minion is healthy

6s 138ms 4

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

And reverse resolution should work for "sle_minion" 430ms

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

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

@build_host

Scenario:
The build host is healthy

3s 803ms 4

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

And reverse resolution should work for "build_host" 220ms

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

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

@ssh_minion

Scenario:
The SSH minion is healthy

6s 22ms 4

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

And reverse resolution should work for "ssh_minion" 386ms

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

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

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 787ms 4

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

And reverse resolution should work for "rhlike_minion" 282ms

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

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

@deblike_minion

Scenario:
The Debian-like minion is healthy

6s 46ms 4

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

And reverse resolution should work for "deblike_minion" 220ms

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

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

@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

657ms 1

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

@no_auth_registry

Scenario:
The registry without authentication is healthy

644ms 1

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

@custom_download_endpoint

Scenario:
The custom download endpoint is working

633ms 1

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

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

675ms 1

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

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

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

Scenario:
Wait for refresh of list of products to finish

3s 603ms 1

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

Scenario:
Create testing username

2s 138ms 12

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

And I follow "Create User" 535ms

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

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

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

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

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

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

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

And I click on "Create Login" 927ms

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

And I should see a "testing" link 12ms

Scenario:
Grant testing user administrative priviledges

1s 699ms 10

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

And I follow "testing" 489ms

And I check "role_org_admin" 87ms

And I check "role_system_group_admin" 81ms

And I check "role_channel_admin" 80ms

And I check "role_activation_key_admin" 85ms

And I check "role_config_admin" 83ms

And I click on "Update" 583ms

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

And I should see a "testing" text 64ms

@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

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

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

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

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 629ms 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 286ms 5

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

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

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

And I click on "Save Preferences" 573ms

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

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

3s 343ms 5

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

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

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

And I click on "Save Preferences" 649ms

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

Feature:Prepare server for using Kiwi 3s 952ms 1

Scenario:
Create a Kiwi user with image administrators rights

3s 952ms 2

New user kiwikiwi created with roles: image_admin

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

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

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

Scenario:
Create a Docker user with image administrators rights

2s 132ms 2

New user docker created with roles: image_admin

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

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

@no_auth_registry

Scenario:
Create an image store without credentials

3s 185ms 7

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

And I follow "Create" 572ms

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

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

And I click on "create-btn" 108ms

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

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

Feature:Do not let Taskomatic tasks interfere with our CI tests 35s 626ms 3

Scenario:
Log in as admin user

26s 703ms 1

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

Scenario:
Disable scheduled reposyncs

4s 459ms 5

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

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

And I choose "disabled" 57ms

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

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

Scenario:
Disable scheduled Cobbler syncs

4s 463ms 5

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

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

And I choose "disabled" 45ms

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

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

@scc_credentials
Feature:List available channels and enable them 1m 35s 180ms 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 381ms 5

When I refresh SCC 26s 967ms

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

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

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

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

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

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

Scenario:
List Server product

1s 481ms 2

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

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

@proxy @susemanager

Scenario:
List all products for SUSE Multi-Linux Manager

< 1ms 6

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

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

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

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

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

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

Scenario:
List products with filter

1s 446ms 4

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

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

When I remove the mgr-sync cache file 642ms

And I execute mgr-sync refresh 1m 767ms

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

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

@scc_credentials

Scenario:
Refresh SCC

24s 426ms 1

When I refresh SCC 24s 426ms

@scc_credentials

Scenario:
Let the products page appear

2s 124ms 6

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

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

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

Then I should see a "Arch" text 105ms

And I should see a "Channels" text 104ms

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

@scc_credentials

Scenario:
Use the products and architecture filters

2s 581ms 7

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

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

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

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

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

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

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

@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

2m 7s 428ms 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 136ms

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

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

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

@containerized_server @proxy @uyuni

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

1m 7s 113ms 2

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

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

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

@scc_credentials @uyuni @build_host

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 57ms

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

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

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

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 57m 4s 893ms

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

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

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

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

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

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

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

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

@scc_credentials @skip_if_github_validation

Scenario:
Report the synchronization duration for SLES 15 SP7

< 1ms 1

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

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

473ms 1

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

Scenario:
Add a fake base channel for x86_64

1s 645ms 10

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

And I follow "Create Channel" 369ms

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

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

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

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

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

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

And I click on "Create Channel" 572ms

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

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

1s 405ms 10

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

And I follow "Create Channel" 283ms

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

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

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

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

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

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

And I click on "Create Channel" 567ms

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

@sle_minion

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

1s 326ms 10

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

And I follow "Create Channel" 281ms

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

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

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

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

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

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

And I click on "Create Channel" 515ms

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

Scenario:
Add a fake base channel for i586

1s 323ms 10

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

And I follow "Create Channel" 271ms

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

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

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

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

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

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

And I click on "Create Channel" 513ms

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

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

988ms 10

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

And I follow "Create Channel" 391ms

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

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

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

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

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

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

And I click on "Create Channel" 55ms

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

Scenario:
Add a test base channel for x86_64

1s 319ms 10

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

And I follow "Create Channel" 305ms

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

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

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

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

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

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

And I click on "Create Channel" 491ms

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

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

939ms 10

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

And I follow "Create Channel" 321ms

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

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

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

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

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

And I click on "Create Channel" 55ms

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

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

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

And I follow "Create Channel" 314ms

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

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

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

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

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

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

And I uncheck "gpg_check" 10s 84ms

And I click on "Create Channel" 535ms

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

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 333ms 10

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

And I follow "Create Channel" 313ms

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

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

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

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

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

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

And I click on "Create Channel" 493ms

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

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 369ms 10

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

And I follow "Create Channel" 311ms

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

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

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

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

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

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

And I click on "Create Channel" 519ms

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

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

487ms 1

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

Scenario:
Create a fake repository for distributions using RPM

1s 123ms 7

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

And I follow "Create Repository" 298ms

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

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

And I click on "Create Repository" 428ms

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

And I should see "metadataSigned" as checked 19ms

Scenario:
Disable metadata check for the fake RPM repository

10s 988ms 6

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

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

And I uncheck "metadataSigned" 10s 87ms

And I click on "Update Repository" 453ms

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

And I should see "metadataSigned" as unchecked 15ms

@rhlike_minion

Scenario:
Create a fake AppStream repository

609ms 7

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

And I follow "Create Repository" 271ms

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

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

And I click on "Create Repository" 55ms

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

And I should see "metadataSigned" as checked 15ms

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

10s 967ms 6

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

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

And I uncheck "metadataSigned" 10s 61ms

And I click on "Update Repository" 463ms

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

And I should see "metadataSigned" as unchecked 15ms

@sle_minion

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

2s 70ms 9

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

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

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

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

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

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

And I click on "Save Repositories" 669ms

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

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

2s 579ms 9

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

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

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

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

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

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

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

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

@rhlike_minion

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

2s 731ms 9

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

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

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

And I click on "Update Channel" 522ms

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

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

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

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

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

@rhlike_minion

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

2s 690ms 9

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

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

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

And I click on "Update Channel" 528ms

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

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

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

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

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

Scenario:
Create a fake repository for i586

11s 74ms 7

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

And I follow "Create Repository" 280ms

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

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

And I uncheck "metadataSigned" 10s 81ms

And I click on "Create Repository" 434ms

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

Scenario:
Add the repository to the i586 channel

1s 369ms 9

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

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

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

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

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

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

And I click on "Save Repositories" 529ms

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

@sle_minion

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

1s 696ms 6

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

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

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

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

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

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

@deblike_minion

Scenario:
Create a fake repository for Debian-like

1s 81ms 7

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

And I follow "Create Repository" 288ms

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

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

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

And I click on "Create Repository" 450ms

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

@deblike_minion

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

1s 400ms 6

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

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

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

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

And I click on "Save Repositories" 808ms

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

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Add the repository to the terminal child channel

< 1ms 9

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

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

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

And I click on "Update Channel" 0s

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

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

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

And I click on "Save Repositories" 0s

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

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

504ms 1

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

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 11ms 10

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

And I follow "Create Channel" 257ms

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

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

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

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

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

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

And I click on "Create Channel" 66ms

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

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

6s 252ms 1

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

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 395ms 10

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

And I follow "Create Channel" 336ms

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

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

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

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

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

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

And I click on "Create Channel" 505ms

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

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

3s 823ms 1

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

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

969ms 10

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

And I follow "Create Channel" 315ms

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

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

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

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

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

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

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

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

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 591ms 10

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

And I follow "Create Channel" 422ms

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

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

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

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

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

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

And I click on "Create Channel" 602ms

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

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

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

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

And I enable source package syncing 1s 394ms

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

3s 710ms 9

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

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

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

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

And I follow "Sync" 311ms

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

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

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

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

@sle_minion

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

4s 807ms 2

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

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

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

3s 598ms 9

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

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

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

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

And I follow "Sync" 303ms

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

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

Scenario:
Synchronize Test-Child-Channel-x86_64 channel

4s 197ms 9

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

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

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

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

And I follow "Sync" 842ms

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

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

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

@sle_minion

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

35s 68ms 9

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

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

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

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

And I follow "Sync" 844ms

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

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

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

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

@deblike_minion

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

3s 639ms 9

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

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

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

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

And I follow "Sync" 400ms

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

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

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

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

@rhlike_minion

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

4s 291ms 9

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

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

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

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

And I follow "Sync" 941ms

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

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

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

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

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 313ms 9

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

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

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

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

And I follow "Sync" 949ms

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

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

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

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Synchronize the repository in the terminal channel

< 1ms 9

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

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

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

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

And I follow "Sync" 0s

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

And I click on "Sync Now" 0s

Then I should see a "Repository sync scheduled for Fake-RPM-Terminal-Channel." text 0s

And I wait until the channel "fake-rpm-terminal-channel" has been synced 0s

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Verify state of Fake-RPM-Terminal-Channel custom channel

< 1ms 2

Then "orion-dummy-1.1-1.1.x86_64.rpm" package should have been stored 0s

And solver file for "fake-rpm-terminal-channel" should reference "orion-dummy-1.1-1.1.x86_64.rpm" 0s

Scenario:
Refresh the errata cache

6s 492ms 6

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

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

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

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

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

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

Scenario:
Refresh the channel's repository data

6s 165ms 6

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

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

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

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

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

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

Scenario:
Cleanup disable source package syncing

978ms 1

Then I disable source package syncing 978ms

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

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

@sle_minion

Scenario:
Synchronize Devel-SUSE-Channel channel

3s 870ms 9

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

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

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

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

And I follow "Sync" 536ms

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

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

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

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

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

4s 248ms 9

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

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

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

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

And I follow "Sync" 867ms

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

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

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

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 129ms 9

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

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

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

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

And I follow "Sync" 764ms

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

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

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

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

4s 220ms 9

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

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

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

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

And I follow "Sync" 777ms

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

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

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

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

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

530ms 1

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

@sle_minion

Scenario:
Create an activation key with a channel

2s 128ms 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 574ms

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

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

2s 817ms 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 212ms

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

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

2s 349ms 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 369ms

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

@ssh_minion

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

1s 793ms 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" 854ms

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

@ssh_minion

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

2s 37ms 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" 774ms

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

@proxy

Scenario:
Create an activation key for the proxy

2s 521ms 2

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

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

@build_host

Scenario:
Create an activation key for the build host

2s 646ms 3

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

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

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

@scc_credentials

Scenario:
Create an activation key for the terminal

2s 169ms 2

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

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

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

472ms 1

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 620ms

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 562ms

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 570ms

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

@scc_credentials @susemanager @proxy @containerized_server @transactional_server

Scenario:
Update the SLE Micro proxy key with synced base product

< 1ms 11

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

And I wait until "ManagerTools-SL-Micro-6.1 for x86_64" has been checked 0s

And I check "SUSE-Multi-Linux-Manager-Proxy-5.1 for x86_64" 0s

And I check "SUSE-Multi-Linux-Manager-Retail-Branch-Server-5.1 for x86_64" 0s

And I click on "Update Activation Key" 0s

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

@scc_credentials @susemanager @proxy @containerized_server @skip_if_transactional_server

Scenario:
Update the SLES proxy key with synced base product

< 1ms 11

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

And I wait until "ManagerTools-SLE15-Pool for x86_64 SP7" has been checked 0s

And I check "SUSE-Manager-Proxy-5.1-Pool for x86_64" 0s

And I check "SUSE-Manager-Proxy-5.1-Updates for x86_64" 0s

And I click on "Update Activation Key" 0s

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

@uyuni @proxy @containerized_server @skip_if_cloud

Scenario:
Update the openSUSE Tumbleweed Proxy Host key with synced base product

< 1ms 8

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 0s

And I click on "Update Activation Key" 0s

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

@scc_credentials @build_host

Scenario:
Update build host key with synced base product

3s 213ms 20

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

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

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

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

And I wait for child channels to appear 473ms

And I include the recommended child channels 160ms

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 619ms

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

@scc_credentials @uyuni @build_host

Scenario:
Update build host key with Uyuni client tools

2s 31ms 9

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

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

And I wait for child channels to appear 902ms

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

And I wait for child channels to appear 273ms

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

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

And I click on "Update Activation Key" 551ms

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

@skip_if_github_validation @scc_credentials @uyuni @build_host

Scenario:
Update build host key with dev child channel

2s 112ms 9

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

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

And I wait for child channels to appear 925ms

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

And I wait for child channels to appear 279ms

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

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

And I click on "Update Activation Key" 563ms

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

@scc_credentials @build_host

Scenario:
Update terminal key with synced base product

2s 897ms 16

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

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

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

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

And I wait for child channels to appear 477ms

And I include the recommended child channels 146ms

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

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

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

And I click on "Update Activation Key" 591ms

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 758ms 6

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

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

And I wait for child channels to appear 892ms

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

And I click on "Update Activation Key" 593ms

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

@skip_if_github_validation @deblike_minion

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

1s 702ms 6

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

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

And I wait for child channels to appear 863ms

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

And I click on "Update Activation Key" 541ms

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

@skip_if_github_validation @rhlike_minion

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

1s 725ms 6

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

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

And I wait for child channels to appear 881ms

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

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 35ms 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 267ms 1

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

@sle_minion

Scenario:
Create the bootstrap repository for SUSE Minion

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

@proxy

Scenario:
Create the bootstrap repository for Proxy

2s 153ms 1

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

@build_host

Scenario:
Create the bootstrap repository for Build Host

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

@containerized_server @scope_containerized_proxy @proxy
Feature:Setup containerized proxy 3m 15s 361ms 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 539ms 1

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

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

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

Scenario:
Bootstrap the proxy host as a salt minion

35s 799ms 9

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 60ms

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

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

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

Scenario:
Generate containerized proxy configuration

11s 852ms 2

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

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

Scenario:
Set up the containerized proxy service to support Avahi

< 1ms 1

Record not added - avahi domain was not detected

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

Scenario:
Run a containerized proxy

17s 71ms 1

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

Scenario:
Wait until containerized proxy service is active

3s 920ms 10

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

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

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

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

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

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

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

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

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

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

Scenario:
The containerized proxy should be registered automatically

652ms 2

When I follow the left menu "Systems" 59ms

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

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

10s 932ms 3

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

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

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

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

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

Scenario:
Adapt the proxy for Retail

< 1ms 3

When I rename the proxy for Retail 0s

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

And I restart all proxy containers 0s

Scenario:
Check the branch network

< 1ms 2

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

And name resolution should work on private network 0s

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

< 1ms 11

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

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

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

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

And I click on "Schedule Hardware Refresh" 0s

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

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

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

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

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

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

@deblike_minion
Feature:Bootstrap a Debian-like minion and do some basic operations on it 1m 59s 994ms 1 6

Scenario:
Log in as admin user

21s 742ms 1

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

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

18s 782ms 1 3 1

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

13s 694ms Show Info +

14:09:53:000 - 14:09:58:000 | Current URL: https://uyuni-master-server.sumaci.aws/

Screenshot +

@proxy

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

27s 736ms 4 1

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

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

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

Then I should see "deblike_minion" hostname 10s 21ms 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 332ms Show Info +

14:10:12:000 - 14:10:27:000 | Current URL: https://uyuni-master-server.sumaci.aws/

Screenshot +

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

15s 884ms 1 10 1

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

15s 556ms Show Info +

14:10:41:000 - 14:10:41:000 | Current URL: https://uyuni-master-server.sumaci.aws/

Screenshot +

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

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

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

14s 340ms 1 1 1

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

14s 9ms Show Info +

14:10:58:000 - 14:10:58:000 | Current URL: https://uyuni-master-server.sumaci.aws/

Screenshot +

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

Scenario:
Log in as admin user

20s 515ms 1

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

20s 459ms 12 1

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

16s 598ms 1 3 1

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

14s 293ms Show Info +

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

Screenshot +

@proxy

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

29s 119ms 4 1

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

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

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

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

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

14s 806ms Show Info +

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

Screenshot +

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

15s 159ms 1 10 1

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

14s 806ms Show Info +

14:10:40:000 - 14:10:40:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/YourRhn.do

Screenshot +

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

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

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

15s 291ms 1 1 1

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

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

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

14s 717ms Show Info +

14:10:55:000 - 14:10:56:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/YourRhn.do

Screenshot +

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

Scenario:
Clean up sumaform leftovers on build host

8s 190ms 1

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

Scenario:
Log in as admin user

32s 565ms 1

Given I am authorized for the "Admin" section 32s 565ms 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 492ms 9 1

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

13s 803ms 5 1

When I follow the left menu "Salt > Keys" 13s 803ms 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

549ms 3 1

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

4s 575ms 3 1

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

527ms 1

When I query latest Salt changes on "build_host" 527ms 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

309ms 2 1

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

929ms 1 1

Given I am on the Systems overview page of this "build_host" 929ms 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 3m 65ms 1 5 2

Scenario:
Clean up sumaform leftovers on SLES minion

9s 654ms 1

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

Scenario:
Log in as admin user

10s 876ms 1

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

41s 711ms 10 1

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

1m 16s 195ms 4 3 1

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

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

Then I should see a "accepted" text 53ms

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

And I wait until I see the name of "sle_minion", refreshing the page 1m 15s 364ms Show Error +

                                            
 stale element reference: stale element not found
  (Session info: chrome=143.0.7499.192); For documentation on this error, please visit: https://www.selenium.dev/documentation/webdriver/troubleshooting/errors#staleelementreferenceexception (Selenium::WebDriver::Error::StaleElementReferenceError)
./features/step_definitions/navigation_steps.rb:60:in `block (2 levels) in (top (required))'
./features/support/commonlib.rb:106:in `block in repeat_until_timeout'
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/step_definitions/navigation_steps.rb:59:in `/^I wait until I see "([^"]*)" (text|regex), refreshing the page$/'
./features/step_definitions/navigation_steps.rb:117:in `/^I wait until I see the "([^"]*)" system, refreshing the page$/'
./features/step_definitions/navigation_steps.rb:113:in `/^I wait until I see the name of "([^"]*)", refreshing the page$/'
features/init_clients/sle_minion.feature:31:in `I wait until I see the name of "sle_minion", refreshing the page'

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

Then the Salt master can reach "sle_minion" 0s

And I report the onboarding duration for "sle_minion" 0s

@susemanager

Scenario:
Use correct kernel image on the SLES minion

< 1ms 2

When I remove package "kernel-default-base" from this "sle_minion" 0s

And I install package "kernel-default" on this "sle_minion" 0s

@susemanager

Scenario:
Reboot the SLES minion to use the new kernel

< 1ms 1

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

@proxy

Scenario:
Check connection from minion to proxy

14s 213ms 1 3 1

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

13s 886ms Show Info +

14:11:49:000 - 14:11:49:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/YourRhn.do

Screenshot +

@proxy

Scenario:
Check registration on proxy of minion

27s 416ms 4 1

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

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

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

Then I should see "sle_minion" hostname 10s 87ms Show Error +

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

13s 628ms Show Info +

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

Screenshot +

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

Scenario:
Clean up sumaform leftovers on SLES SSH minion

9s 176ms 1

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

Scenario:
Log in as admin user

33s 137ms 1

Given I am authorized for the "Admin" section 33s 137ms Show Error +

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

Scenario:
Bootstrap a SLES SSH minion

41s 574ms 10 1

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

551ms 3 1

Given I am on the Systems overview page of this "ssh_minion" 551ms Show Error +

                                            
 No system found for hostname: uyuni-master-suse-sshminion.sumaci.aws (RuntimeError)
./features/support/commonlib.rb:421:in `get_system_id'
./features/step_definitions/navigation_steps.rb:472:in `/^I am on the Systems overview page of this "([^"]*)"$/'
features/init_clients/sle_ssh_minion.feature:37:in `I am on the Systems overview page of this "ssh_minion"'

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

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

Then I should see "proxy" short hostname 0s

@proxy

Scenario:
Check registration on proxy of SSH minion

4s 503ms 3 1

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

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

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

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

Then I should see "ssh_minion" hostname 0s

@transactional_server
Feature:SELinux debugging < 1ms 1

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

Scenario:
No previous operation has created wrong SELinux label

< 1ms 1

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

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

Scenario:
Call spacewalk-debug on server

14s 321ms 1

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

Scenario:
Check the tomcat logs on server

674ms 1

Then the tomcat logs should not contain errors 674ms

Scenario:
Check salt event log for failures on server

1s 864ms 1

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

Scenario:
Check the taskomatic logs on server

655ms 1

Then the taskomatic logs should not contain errors 655ms

Scenario:
Check for out of memory errors

664ms 1

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

Feature:Debug the clients after the testsuite has run 1m 26s 568ms 1

Scenario:
Extract the logs from all our clients

1m 26s 568ms 1

When I extract the log files from all our active nodes 1m 26s 568ms

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

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

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

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

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

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

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

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

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

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

@scc_credentials Scenario:Refresh SCC 24s 426ms 1

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

@scc_credentials Scenario:Use the products and architecture filters 2s 581ms 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 2m 7s 428ms 4

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

@scc_credentials @uyuni @build_host Scenario:Synchronize SLES 15 SP7 product with recommended sub-products for Retail feature 57m 25s 86ms 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 297ms 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 326ms 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 491ms 11

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@sle_minion Scenario:Synchronize Fake-Child-Channel-SUSE-like channel 35s 68ms 9

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

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

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

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

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

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

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

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

@proxy

Scenario:
The proxy is healthy

4s 454ms 4

@sle_minion

Scenario:
The minion is healthy

6s 138ms 4

@build_host

Scenario:
The build host is healthy

3s 803ms 4

@ssh_minion

Scenario:
The SSH minion is healthy

6s 22ms 4

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 787ms 4

@deblike_minion

Scenario:
The Debian-like minion is healthy

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

657ms 1

@no_auth_registry

Scenario:
The registry without authentication is healthy

644ms 1

@custom_download_endpoint

Scenario:
The custom download endpoint is working

633ms 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 185ms 7

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

@proxy @susemanager

Scenario:
List all products for SUSE Multi-Linux Manager

< 1ms 6

@scc_credentials

Scenario:
Refresh SCC

24s 426ms 1

@scc_credentials

Scenario:
Let the products page appear

2s 124ms 6

@scc_credentials

Scenario:
Use the products and architecture filters

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

2m 7s 428ms 4

@containerized_server @proxy @uyuni

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

1m 7s 113ms 2

@scc_credentials @uyuni @build_host

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

57m 25s 86ms 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 297ms 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 326ms 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 491ms 11

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 333ms 10

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 369ms 10

@rhlike_minion

Scenario:
Create a fake AppStream repository

609ms 7

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

10s 967ms 6

@sle_minion

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

2s 70ms 9

@rhlike_minion

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

2s 731ms 9

@rhlike_minion

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

2s 690ms 9

@sle_minion

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

1s 696ms 6

@deblike_minion

Scenario:
Create a fake repository for Debian-like

1s 81ms 7

@deblike_minion

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

1s 400ms 6

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Add the repository to the terminal child channel

< 1ms 9

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

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 11ms 10

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

6s 252ms 1

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 395ms 10

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

3s 823ms 1

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

969ms 10

@deblike_minion

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

7s 772ms 1

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 591ms 10

@rhlike_minion

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

4s 641ms 1

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

3s 710ms 9

@sle_minion

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

4s 807ms 2

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

3s 598ms 9

@sle_minion

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

35s 68ms 9

@deblike_minion

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

3s 639ms 9

@rhlike_minion

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

4s 291ms 9

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 313ms 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 468ms 4

@sle_minion

Scenario:
Synchronize Devel-SUSE-Channel channel

3s 870ms 9

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

4s 248ms 9

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 129ms 9

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

4s 220ms 9

@sle_minion

Scenario:
Create an activation key with a channel

2s 128ms 2

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

2s 817ms 2

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

2s 349ms 2

@ssh_minion

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

1s 793ms 2

@ssh_minion

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

2s 37ms 2

@proxy

Scenario:
Create an activation key for the proxy

2s 521ms 2

@build_host

Scenario:
Create an activation key for the build host

2s 646ms 3

@scc_credentials

Scenario:
Create an activation key for the terminal

2s 169ms 2

@scc_credentials @susemanager

Scenario:
Update SLE key with synced base product

< 1ms 20