Cucumber Feature Report

All Scenarios

201

Passed Scenarios

143

Failed Scenarios

19

Skipped Scenarios

39

Execution Time: 102m 1s 18ms

Expand All | Collapse All

Metadata

App Version: Uyuni/Head

Browser: Chrome

Platform: x86_64

Parallel: Disabled

Feature:Sanity checks 44s 929ms 10 2

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

Scenario:
The server is healthy

11s 936ms 19

Then "server" should have a FQDN 393ms

And reverse resolution should work for "server" 636ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@proxy

Scenario:
The proxy is healthy

4s 492ms 4

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

And reverse resolution should work for "proxy" 280ms

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

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

@sle_minion

Scenario:
The minion is healthy

6s 885ms 4

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

And reverse resolution should work for "sle_minion" 454ms

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

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

@build_host

Scenario:
The build host is healthy

3s 961ms 4

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

And reverse resolution should work for "build_host" 223ms

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

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

@ssh_minion

Scenario:
The SSH minion is healthy

6s 378ms 4

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

And reverse resolution should work for "ssh_minion" 439ms

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

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

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 526ms 4

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

And reverse resolution should work for "rhlike_minion" 203ms

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

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

@deblike_minion

Scenario:
The Debian-like minion is healthy

5s 807ms 4

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

And reverse resolution should work for "deblike_minion" 215ms

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

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

@skip_if_cloud

Scenario:
The external resources can be reached

< 1ms 3

Then it should be possible to reach the test packages 0s

And it should be possible to reach the build sources 0s

And it should be possible to reach the Docker profiles 0s

@server_http_proxy

Scenario:
The HTTP proxy is working

< 1ms 1

Then it should be possible to use the HTTP proxy 0s

@auth_registry

Scenario:
The registry with authentication is healthy

652ms 1

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

@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

643ms 1

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

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

674ms 1

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

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

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

Scenario:
Wait for refresh of list of products to finish

3s 611ms 1

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

Scenario:
Create testing username

2s 205ms 12

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

And I follow "Create User" 587ms

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

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

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

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

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

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

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

And I click on "Create Login" 957ms

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

And I should see a "testing" link 12ms

Scenario:
Grant testing user administrative priviledges

1s 687ms 10

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

And I follow "testing" 468ms

And I check "role_org_admin" 84ms

And I check "role_system_group_admin" 79ms

And I check "role_channel_admin" 82ms

And I check "role_activation_key_admin" 80ms

And I check "role_config_admin" 78ms

And I click on "Update" 605ms

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

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

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

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

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

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 299ms 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 302ms 5

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

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

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

And I click on "Save Preferences" 619ms

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

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

2s 996ms 5

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

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

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

And I click on "Save Preferences" 641ms

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

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

Scenario:
Create a Kiwi user with image administrators rights

4s 546ms 2

New user kiwikiwi created with roles: image_admin

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

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

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

Scenario:
Create a Docker user with image administrators rights

2s 285ms 2

New user docker created with roles: image_admin

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

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

@no_auth_registry

Scenario:
Create an image store without credentials

3s 324ms 7

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

And I follow "Create" 573ms

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

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

And I click on "create-btn" 317ms

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

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

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

Scenario:
Log in as admin user

37s 434ms 1

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

Scenario:
Disable scheduled reposyncs

4s 654ms 5

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

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

And I choose "disabled" 54ms

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

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

Scenario:
Disable scheduled Cobbler syncs

4s 531ms 5

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

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

And I choose "disabled" 49ms

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

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

@scc_credentials
Feature:List available channels and enable them 1m 38s 512ms 5 1

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

Scenario:
List available channels

32s 654ms 5

When I refresh SCC 30s 222ms

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

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

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

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

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

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

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

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

When I remove the mgr-sync cache file 678ms

And I execute mgr-sync refresh 1m 769ms

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

Feature:Synchronize products in the products page of the Setup Wizard 63m 28s 970ms 8 9

@scc_credentials

Scenario:
Refresh SCC

26s 498ms 1

When I refresh SCC 26s 498ms

@scc_credentials

Scenario:
Let the products page appear

2s 334ms 6

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

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

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

Then I should see a "Arch" text 102ms

And I should see a "Channels" text 101ms

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

@scc_credentials

Scenario:
Use the products and architecture filters

2s 379ms 7

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

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

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

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

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

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

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 1s 543ms 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 870ms

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

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

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

@containerized_server @proxy @uyuni

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

55s 944ms 2

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

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

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

@scc_credentials @uyuni @build_host

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

59m 16s 614ms 20

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 55ms

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

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

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

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

And I wait until all synchronized channels for "sles15-sp7" have finished 58m 55s 508ms

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

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

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

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

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

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

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

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

@scc_credentials @skip_if_github_validation

Scenario:
Report the synchronization duration for SLES 15 SP7

< 1ms 1

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

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

481ms 1

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

Scenario:
Add a fake base channel for x86_64

1s 629ms 10

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

And I follow "Create Channel" 363ms

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

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

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

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

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

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

And I click on "Create Channel" 582ms

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

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

1s 377ms 10

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

And I follow "Create Channel" 280ms

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

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

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

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

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

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

And I click on "Create Channel" 549ms

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

@sle_minion

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

1s 385ms 10

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

And I follow "Create Channel" 316ms

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

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

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

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

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

And I click on "Create Channel" 535ms

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

Scenario:
Add a fake base channel for i586

1s 374ms 10

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

And I follow "Create Channel" 306ms

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

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

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

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

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

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

And I click on "Create Channel" 533ms

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

1s 381ms 10

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

And I follow "Create Channel" 298ms

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

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

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

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

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

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

And I click on "Create Channel" 543ms

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

Scenario:
Add a test base channel for x86_64

1s 324ms 10

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

And I follow "Create Channel" 293ms

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

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

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

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

And I click on "Create Channel" 512ms

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

1s 468ms 10

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

And I follow "Create Channel" 299ms

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

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

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

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

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

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

And I click on "Create Channel" 614ms

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

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

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

And I follow "Create Channel" 299ms

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

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

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

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

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

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

And I uncheck "gpg_check" 10s 104ms

And I click on "Create Channel" 496ms

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

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 335ms 10

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

And I follow "Create Channel" 306ms

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

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

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

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

And I click on "Create Channel" 502ms

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

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 316ms 10

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

And I follow "Create Channel" 303ms

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

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

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

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

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

And I click on "Create Channel" 57ms

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

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

484ms 1

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

Scenario:
Create a fake repository for distributions using RPM

746ms 7

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

And I follow "Create Repository" 291ms

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

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

And I click on "Create Repository" 62ms

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

And I should see "metadataSigned" as checked 18ms

Scenario:
Disable metadata check for the fake RPM repository

10s 947ms 6

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

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

And I uncheck "metadataSigned" 10s 80ms

And I click on "Update Repository" 427ms

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

And I should see "metadataSigned" as unchecked 16ms

@rhlike_minion

Scenario:
Create a fake AppStream repository

994ms 7

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

And I follow "Create Repository" 283ms

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

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

And I click on "Create Repository" 426ms

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

And I should see "metadataSigned" as checked 15ms

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

10s 914ms 6

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

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

And I uncheck "metadataSigned" 10s 63ms

And I click on "Update Repository" 434ms

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

And I should see "metadataSigned" as unchecked 15ms

@sle_minion

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

1s 922ms 9

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

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

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

And I click on "Update Channel" 550ms

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

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

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

And I click on "Save Repositories" 518ms

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

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

2s 843ms 9

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

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

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

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

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

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

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

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

@rhlike_minion

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

2s 700ms 9

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

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

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

And I click on "Update Channel" 534ms

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

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

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

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

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

@rhlike_minion

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

2s 76ms 9

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

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

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

And I click on "Update Channel" 54ms

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

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

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

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

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

Scenario:
Create a fake repository for i586

11s 68ms 7

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

And I follow "Create Repository" 289ms

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

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

And I uncheck "metadataSigned" 10s 70ms

And I click on "Create Repository" 425ms

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

Scenario:
Add the repository to the i586 channel

1s 894ms 9

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

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

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

And I click on "Update Channel" 63ms

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

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

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

And I click on "Save Repositories" 597ms

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

@sle_minion

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

1s 826ms 6

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

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

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

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

@deblike_minion

Scenario:
Create a fake repository for Debian-like

672ms 7

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

And I follow "Create Repository" 280ms

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

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

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

And I click on "Create Repository" 53ms

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

@deblike_minion

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

1s 369ms 6

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

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

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

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

And I click on "Save Repositories" 793ms

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

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Add the repository to the terminal child channel

< 1ms 9

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

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

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

And I click on "Update Channel" 0s

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

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

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

And I click on "Save Repositories" 0s

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

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

530ms 1

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

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 531ms 10

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

And I follow "Create Channel" 324ms

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

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

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

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

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

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

And I click on "Create Channel" 540ms

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

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

6s 506ms 1

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

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 444ms 10

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

And I follow "Create Channel" 315ms

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

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

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

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

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

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

And I click on "Create Channel" 571ms

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

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

5s 62ms 1

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

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

963ms 10

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

And I follow "Create Channel" 329ms

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

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

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

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

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

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

And I click on "Create Channel" 54ms

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

@deblike_minion

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

6s 909ms 1

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

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 309ms 10

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

And I follow "Create Channel" 255ms

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

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

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

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

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

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

And I click on "Create Channel" 498ms

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

@rhlike_minion

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

4s 673ms 1

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

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

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

And I enable source package syncing 1s 515ms

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

3s 603ms 9

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

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

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

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

And I follow "Sync" 306ms

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

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

@sle_minion

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

4s 704ms 2

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

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

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

3s 600ms 9

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

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

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

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

And I follow "Sync" 299ms

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

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

Scenario:
Synchronize Test-Child-Channel-x86_64 channel

4s 282ms 9

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

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

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

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

And I follow "Sync" 839ms

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

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

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

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

@sle_minion

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

24s 410ms 9

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

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

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

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

And I follow "Sync" 289ms

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

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

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

@deblike_minion

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

3s 598ms 9

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

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

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

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

And I follow "Sync" 307ms

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

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

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

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

@rhlike_minion

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

4s 311ms 9

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

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

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

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

And I follow "Sync" 923ms

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

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

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

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

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 216ms 9

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

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

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

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

And I follow "Sync" 762ms

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

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

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

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Synchronize the repository in the terminal channel

< 1ms 9

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

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

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

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

And I follow "Sync" 0s

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

And I click on "Sync Now" 0s

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

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

@pxeboot_minion @uyuni @scc_credentials

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

< 1ms 2

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

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

Scenario:
Refresh the errata cache

5s 529ms 6

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

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

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

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

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

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

Scenario:
Refresh the channel's repository data

5s 251ms 6

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

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

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

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

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

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

Scenario:
Cleanup disable source package syncing

997ms 1

Then I disable source package syncing 997ms

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

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

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

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

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

And I follow "Sync" 394ms

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

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

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

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

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

4s 271ms 9

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

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

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

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

And I follow "Sync" 825ms

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

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

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

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

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

3s 945ms 9

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

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

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

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

And I follow "Sync" 529ms

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

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

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

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

4s 121ms 9

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

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

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

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

And I follow "Sync" 768ms

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

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

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

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

545ms 1

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

@sle_minion

Scenario:
Create an activation key with a channel

2s 142ms 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 488ms

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

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

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

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

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

2s 431ms 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 20ms

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

@ssh_minion

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

2s 924ms 2

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

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

@ssh_minion

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

2s 3ms 2

When I create an activation key with id "SUSE-SSH-TUNNEL-KEY-x86_64", description "SUSE SSH Tunnel Test Key x86_64", limit of 20 and contact method "ssh-push-tunnel" 779ms

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

@proxy

Scenario:
Create an activation key for the proxy

2s 390ms 2

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

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

@build_host

Scenario:
Create an activation key for the build host

2s 987ms 3

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

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

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

@scc_credentials

Scenario:
Create an activation key for the terminal

2s 192ms 2

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

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

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

465ms 1

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 600ms

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 583ms

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

@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

1s 635ms 10

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

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

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

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)" 587ms

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

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

And I click on "Update Activation Key" 60ms

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

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

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

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

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

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

And I wait for child channels to appear 546ms

And I include the recommended child channels 162ms

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 661ms

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

@scc_credentials @uyuni @build_host

Scenario:
Update build host key with Uyuni client tools

2s 123ms 9

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

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

And I wait for child channels to appear 957ms

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

And I wait for child channels to appear 265ms

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

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

And I click on "Update Activation Key" 597ms

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

@skip_if_github_validation @scc_credentials @uyuni @build_host

Scenario:
Update build host key with dev child channel

2s 94ms 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 953ms

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

And I wait for child channels to appear 263ms

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

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

And I click on "Update Activation Key" 561ms

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

@scc_credentials @build_host

Scenario:
Update terminal key with synced base product

2s 882ms 16

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

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

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

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

And I wait for child channels to appear 454ms

And I include the recommended child channels 158ms

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 582ms

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

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

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

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

And I wait for child channels to appear 787ms

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

And I click on "Update Activation Key" 563ms

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

@skip_if_github_validation @deblike_minion

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

1s 799ms 6

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

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

And I wait for child channels to appear 930ms

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

And I click on "Update Activation Key" 579ms

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

@skip_if_github_validation @rhlike_minion

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

1s 775ms 6

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

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

And I wait for child channels to appear 930ms

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

And I click on "Update Activation Key" 552ms

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

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

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

@sle_minion

Scenario:
Create the bootstrap repository for SUSE Minion

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

@proxy

Scenario:
Create the bootstrap repository for Proxy

2s 202ms 1

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

@build_host

Scenario:
Create the bootstrap repository for Build Host

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

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

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

@transactional_server

Scenario:
Reboot after clean up

< 1ms 1

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

Scenario:
Log in as admin user

37s 612ms 1

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

Scenario:
Bootstrap the proxy host as a salt minion

34s 792ms 9

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 66ms

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

@skip_if_cloud @transactional_server

Scenario:
Reboot the proxy host

< 1ms 1

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

Scenario:
Wait until the proxy host appears

1m 22s 68ms 1

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

Scenario:
Generate containerized proxy configuration

10s 986ms 2

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

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

Scenario:
Set up the containerized proxy service to support Avahi

< 1ms 1

Record not added - avahi domain was not detected

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

Scenario:
Run a containerized proxy

16s 840ms 1

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

Scenario:
Wait until containerized proxy service is active

5s 842ms 10

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

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

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

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

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

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

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

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

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

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

Scenario:
The containerized proxy should be registered automatically

661ms 2

When I follow the left menu "Systems" 60ms

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

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

11s 83ms 3

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

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

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

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

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

Scenario:
Adapt the proxy for Retail

< 1ms 3

When I rename the proxy for Retail 0s

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

And I restart all proxy containers 0s

Scenario:
Check the branch network

< 1ms 2

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

And name resolution should work on private network 0s

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

< 1ms 11

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

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

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

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

And I click on "Schedule Hardware Refresh" 0s

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

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

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

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

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

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

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

Scenario:
Log in as admin user

42s 12ms 1

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

33s 278ms 13 1

When I follow the left menu "Systems > Bootstrapping" 33s 278ms Show Error +

                                            
 Unable to find xpath "//aside/div[@id='nav']/nav/ul/li/div/a[contains(.,'Systems')]/parent::div/parent::li" (Capybara::ElementNotFound)
./features/step_definitions/navigation_steps.rb:413:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:405:in `each'
./features/step_definitions/navigation_steps.rb:405:in `each_with_index'
./features/step_definitions/navigation_steps.rb:405:in `/^I follow the left menu "([^"]*)"$/'
features/init_clients/min_deblike_salt.feature:14:in `I follow the left menu "Systems ) Bootstrapping"'

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

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

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

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

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

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

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

And I click on "Bootstrap" 0s

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

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

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

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

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

@proxy

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

4s 923ms 3 1

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

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

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

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

Then I should see "proxy" short hostname 0s

@proxy

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

29s 371ms 2 2 1

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

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

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

                                            
 Unable to find link "Details" within #(Capybara::Node::Element tag="section" path="/HTML/BODY[1]/DIV[1]/DIV[1]/SECTION[1]") (Capybara::ElementNotFound)
./features/support/commonlib.rb:198:in `click_link_and_wait'
./features/step_definitions/navigation_steps.rb:338:in `/^I follow "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:360:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:359:in `/^I follow "([^"]*)" in the (.+)$/'
features/init_clients/min_deblike_salt.feature:39:in `I follow "Details" in the content area'

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

Then I should see "deblike_minion" hostname 0s

15s 297ms Show Info +

15:41:46:000 - 15:42:00:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/login?url_bounce=%2Frhn%2Fsystems%2Fdetails%2FOverview.do%3Fsid%3D1000010000&request_method=GET

Screenshot +

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

14s 608ms 1 10 1

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

14s 244ms Show Info +

15:42:15:000 - 15:42:16:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/Overview.do?sid=1000010000

Screenshot +

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

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

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

14s 212ms 1 1 1

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

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

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

13s 922ms Show Info +

15:42:31:000 - 15:42:31:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/Overview.do?sid=1000010000

Screenshot +

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

Scenario:
Log in as admin user

21s 696ms 1

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

42s 882ms 12 1

When I follow the left menu "Systems > Bootstrapping" 42s 882ms Show Error +

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 0s

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

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

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

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

@proxy

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

2s 149ms 3 1

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

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

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

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

Then I should see "proxy" short hostname 0s

@proxy

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

3s 515ms 3 1

Given I am on the Systems overview page of this "proxy" 3s 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:474:in `/^I am on the Systems overview page of this "([^"]*)"$/'
features/init_clients/min_rhlike_salt.feature:37:in `I am on the Systems overview page of this "proxy"'

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

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

Then I should see "rhlike_minion" hostname 0s

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

355ms 10 1

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

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

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

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

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

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

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

And I click on "Next" 0s

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

When I click on "Confirm" 0s

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

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

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

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

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

308ms 1 1

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

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

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

@build_host
Feature:Bootstrap a build host via the GUI 15m 10s 808ms 2 7

Scenario:
Clean up sumaform leftovers on build host

8s 807ms 1

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

Scenario:
Log in as admin user

37s 569ms 1

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

Scenario:
Bootstrap a build host

4m 28s 118ms 10 1

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

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 62ms

And I wait until I see "Bootstrap process initiated." text 4m 10s 48ms Show Error +

                                            
 Text 'Bootstrap process initiated.' not found (ScriptError)
./features/step_definitions/navigation_steps.rb:40:in `/^I wait until I see "([^"]*)" text$/'
features/init_clients/buildhost_bootstrap.feature:23:in `I wait until I see "Bootstrap process initiated." text'

13s 802ms Show Info +

15:39:44:000 - 15:43:59:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/systems/bootstrap

Screenshot +

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

8m 34s 931ms 4 2 1

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

Then I should see a "accepted" text 334ms

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

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

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

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

Then the Salt master can reach "build_host" 0s

14s 292ms Show Info +

15:44:12:000 - 15:52:34:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/systems/list/all

Screenshot +

@proxy

Scenario:
Check connection from build host to proxy

14s 170ms 1 3 1

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

13s 821ms Show Info +

15:52:48:000 - 15:52:48:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/systems/list/all

Screenshot +

@proxy

Scenario:
Check registration on build host of minion

24s 866ms 4 1

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

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

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

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

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

13s 811ms Show Info +

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

Screenshot +

Scenario:
Detect latest Salt changes on the SLES build host

14s 363ms 1 1

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

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

13s 841ms Show Info +

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

Screenshot +

Scenario:
Check that the build host is a build host

13s 955ms 1 2 1

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

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

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

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

13s 644ms Show Info +

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

Screenshot +

Scenario:
Check events history for failures on SLES build host

14s 24ms 1 1 1

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

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

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

13s 722ms Show Info +

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

Screenshot +

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

Scenario:
Clean up sumaform leftovers on SLES minion

10s 837ms 1

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

Scenario:
Log in as admin user

38s 820ms 1

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

Scenario:
Bootstrap a SLES minion

47s 969ms 11

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

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 93ms

And I wait until I see "Bootstrap process initiated." text 43s 449ms

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

Scenario:
Check the new bootstrapped minion in System List page

1m 27s 290ms 8

It took 2 seconds to contact the minion

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

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

Then I should see a "accepted" text 82ms

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

And I wait until I see the name of "sle_minion", refreshing the page 44s 676ms

And I wait until onboarding is completed for "sle_minion" 39s 659ms

Then the Salt master can reach "sle_minion" 1s 935ms

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

@susemanager

Scenario:
Use correct kernel image on the SLES minion

< 1ms 2

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

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

@susemanager

Scenario:
Reboot the SLES minion to use the new kernel

< 1ms 1

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

@proxy

Scenario:
Check connection from minion to proxy

1s 150ms 4

Given I am on the Systems overview page of this "sle_minion" 891ms

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

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

Then I should see "proxy" short hostname 71ms

@proxy

Scenario:
Check registration on proxy of minion

1s 249ms 4

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

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

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

Then I should see "sle_minion" hostname 110ms

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

Scenario:
Clean up sumaform leftovers on SLES SSH minion

9s 979ms 1

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

Scenario:
Log in as admin user

37s 934ms 1

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

Scenario:
Bootstrap a SLES SSH minion

2m 24s 410ms 11

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

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

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

When I check "manageWithSSH" 126ms

And I enter the hostname of "ssh_minion" as "hostname" 184ms

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

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

And I click on "Bootstrap" 89ms

And I wait until I see "Bootstrap process initiated." text 55s 904ms

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

And I wait until I see the name of "ssh_minion", refreshing the page 30s 857ms

And I wait until onboarding is completed for "ssh_minion" 52s 837ms

@susemanager

Scenario:
Use correct kernel image on the SSH minion

< 1ms 2

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

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

@susemanager

Scenario:
Reboot the SSH minion to use the new kernel

< 1ms 1

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

@proxy

Scenario:
Check connection from SSH minion to proxy

1s 963ms 4

Given I am on the Systems overview page of this "ssh_minion" 1s 727ms

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

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

Then I should see "proxy" short hostname 63ms

@proxy

Scenario:
Check registration on proxy of SSH minion

1s 241ms 4

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

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

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

Then I should see "ssh_minion" hostname 115ms

@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 603ms 5

Scenario:
Call spacewalk-debug on server

14s 723ms 1

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

Scenario:
Check the tomcat logs on server

664ms 1

Then the tomcat logs should not contain errors 664ms

Scenario:
Check salt event log for failures on server

1s 870ms 1

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

Scenario:
Check the taskomatic logs on server

693ms 1

Then the taskomatic logs should not contain errors 693ms

Scenario:
Check for out of memory errors

652ms 1

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

Feature:Debug the clients after the testsuite has run 1m 28s 539ms 1

Scenario:
Extract the logs from all our clients

1m 28s 539ms 1

When I extract the log files from all our active nodes 1m 28s 539ms

@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

143

Failed Scenarios

19

Skipped Scenarios

39

@proxy Scenario:The proxy is healthy 4s 492ms 4

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

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

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

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

@deblike_minion Scenario:The Debian-like minion is healthy 5s 807ms 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 652ms 1

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

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

@scc_credentials Feature:List available channels and enable them 1m 38s 512ms 5 1

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

@scc_credentials Scenario:Refresh SCC 26s 498ms 1

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

@scc_credentials Scenario:Use the products and architecture filters 2s 379ms 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 1s 543ms 4

@containerized_server @proxy @uyuni Scenario:Add Uyuni Proxy product for Tumbleweed, including Uyuni Client Tools 55s 944ms 2

@scc_credentials @uyuni @build_host Scenario:Synchronize SLES 15 SP7 product with recommended sub-products for Retail feature 59m 16s 614ms 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 656ms 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 385ms 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 461ms 11

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

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

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

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

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

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

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

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

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

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

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

@skip_if_github_validation Feature:Create custom channels with development repositories 28s 932ms 9

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@rhlike_minion Scenario:Synchronize Devel-RH-like-Channel channel 3s 945ms 9

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

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

@proxy

Scenario:
The proxy is healthy

4s 492ms 4

@sle_minion

Scenario:
The minion is healthy

6s 885ms 4

@build_host

Scenario:
The build host is healthy

3s 961ms 4

@ssh_minion

Scenario:
The SSH minion is healthy

6s 378ms 4

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 526ms 4

@deblike_minion

Scenario:
The Debian-like minion is healthy

5s 807ms 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

652ms 1

@no_auth_registry

Scenario:
The registry without authentication is healthy

644ms 1

@custom_download_endpoint

Scenario:
The custom download endpoint is working

643ms 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 324ms 7

@scc_credentials
Feature:List available channels and enable them 1m 38s 512ms 5 1

@proxy @susemanager

Scenario:
List all products for SUSE Multi-Linux Manager

< 1ms 6

@scc_credentials

Scenario:
Refresh SCC

26s 498ms 1

@scc_credentials

Scenario:
Let the products page appear

2s 334ms 6

@scc_credentials

Scenario:
Use the products and architecture filters

2s 379ms 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 1s 543ms 4

@containerized_server @proxy @uyuni

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

55s 944ms 2

@scc_credentials @uyuni @build_host

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

59m 16s 614ms 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 656ms 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 385ms 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 461ms 11

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 335ms 10

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 316ms 10

@rhlike_minion

Scenario:
Create a fake AppStream repository

994ms 7

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

10s 914ms 6

@sle_minion

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

1s 922ms 9

@rhlike_minion

Scenario:
Add the fake RPM repository to the RedHat-like base channel

2s 700ms 9

@rhlike_minion

Scenario:
Add the fake AppStream repository to the AppStream base channel

2s 76ms 9

@sle_minion

Scenario:
Add the repository to the SUSE-like child channel

1s 826ms 6

@deblike_minion

Scenario:
Create a fake repository for Debian-like

672ms 7

@deblike_minion

Scenario:
Add the repository to the Debian-like base channel

1s 369ms 6

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Add the repository to the terminal child channel

< 1ms 9

@skip_if_github_validation
Feature:Create custom channels with development repositories 28s 932ms 9

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 531ms 10

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

6s 506ms 1

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 444ms 10

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

5s 62ms 1

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

963ms 10

@deblike_minion

Scenario:
Create custom repositories inside the Debian-like custom channel

6s 909ms 1

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 309ms 10

@rhlike_minion

Scenario:
Create custom repositories inside the RH-like custom channel

4s 673ms 1

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

3s 603ms 9

@sle_minion

Scenario:
Verify state of Fake-RPM-SUSE-Channel channel

4s 704ms 2

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

3s 600ms 9

@sle_minion

Scenario:
Synchronize Fake-Child-Channel-SUSE-like channel

24s 410ms 9

@deblike_minion

Scenario:
Synchronize Fake-Base-Channel-Debian-like channel

3s 598ms 9

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-RH-like channel

4s 311ms 9

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 216ms 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 128ms 4

@sle_minion

Scenario:
Synchronize Devel-SUSE-Channel channel

3s 790ms 9

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

4s 271ms 9

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

3s 945ms 9

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

4s 121ms 9

@sle_minion

Scenario:
Create an activation key with a channel

2s 142ms 2

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

1s 375ms 2

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

2s 431ms 2

@ssh_minion

Scenario:
Create an activation key with a channel for salt-ssh

2s 924ms 2

@ssh_minion

Scenario:
Create an activation key with a channel for salt-ssh via tunnel

2s 3ms 2

@proxy

Scenario:
Create an activation key for the proxy

2s 390ms 2

@build_host

Scenario:
Create an activation key for the build host

2s 987ms 3

@scc_credentials

Scenario:
Create an activation key for the terminal

2s 192ms 2

@scc_credentials @susemanager

Scenario:
Update SLE key with synced base product

< 1ms 20