Cucumber Feature Report

All Scenarios

148

Passed Scenarios

114

Failed Scenarios

4

Skipped Scenarios

30

Execution Time: 72m 4s

Expand All | Collapse All

Metadata

App Version: Uyuni/Head

Browser: Chrome

Platform: x86_64

Parallel: Disabled

Feature:Sanity checks 44s 400ms 10 2

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

Scenario:
The server is healthy

11s 838ms 19

Then "server" should have a FQDN 388ms

And reverse resolution should work for "server" 632ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@proxy

Scenario:
The proxy is healthy

4s 529ms 4

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

And reverse resolution should work for "proxy" 282ms

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

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

@sle_minion

Scenario:
The minion is healthy

6s 235ms 4

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

And reverse resolution should work for "sle_minion" 407ms

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

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

@build_host

Scenario:
The build host is healthy

4s 106ms 4

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

And reverse resolution should work for "build_host" 248ms

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

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

@ssh_minion

Scenario:
The SSH minion is healthy

6s 656ms 4

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

And reverse resolution should work for "ssh_minion" 432ms

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

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

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 86ms 4

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

And reverse resolution should work for "rhlike_minion" 179ms

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

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

@deblike_minion

Scenario:
The Debian-like minion is healthy

5s 999ms 4

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

And reverse resolution should work for "deblike_minion" 231ms

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

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

@skip_if_cloud

Scenario:
The external resources can be reached

< 1ms 3

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

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

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

@server_http_proxy

Scenario:
The HTTP proxy is working

< 1ms 1

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

@auth_registry

Scenario:
The registry with authentication is healthy

657ms 1

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

@no_auth_registry

Scenario:
The registry without authentication is healthy

656ms 1

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

@custom_download_endpoint

Scenario:
The custom download endpoint is working

632ms 1

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

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

682ms 1

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

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

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

Scenario:
Wait for refresh of list of products to finish

3s 704ms 1

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

Scenario:
Create testing username

2s 249ms 12

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

And I follow "Create User" 648ms

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

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

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

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

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

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

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

And I click on "Create Login" 936ms

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

And I should see a "testing" link 11ms

Scenario:
Grant testing user administrative priviledges

1s 724ms 10

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

And I follow "testing" 511ms

And I check "role_org_admin" 83ms

And I check "role_system_group_admin" 78ms

And I check "role_channel_admin" 77ms

And I check "role_activation_key_admin" 80ms

And I check "role_config_admin" 79ms

And I click on "Update" 607ms

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

And I should see a "testing" text 64ms

@server_http_proxy

Scenario:
Setup HTTP proxy

< 1ms 9

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

Then I should see a "HTTP Proxy Hostname" text 0s

And I should see a "HTTP Proxy Username" text 0s

And I should see a "HTTP Proxy Password" text 0s

When I enter the address of the HTTP proxy as "HTTP Proxy Hostname" 0s

And I enter "suma3" as "HTTP Proxy Username" 0s

And I enter "P4$$w/ord With%and&" as "HTTP Proxy Password" 0s

And I click on "Save and Verify" 0s

Then HTTP proxy verification should have succeeded 0s

Scenario:
Detect latest Salt changes on the server

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

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

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

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

@scc_credentials @no_mirror

Scenario:
Enter valid SCC credentials

< 1ms 6

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

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

And I ask to add new credentials 0s

And I enter the SCC credentials 0s

And I click on "Save" 0s

And I wait until the SCC credentials are valid 0s

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

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

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

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

And I click on "Save Preferences" 658ms

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

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

3s 609ms 5

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

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

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

And I click on "Save Preferences" 715ms

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

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

Scenario:
Create a Kiwi user with image administrators rights

4s 157ms 2

New user kiwikiwi created with roles: image_admin

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

When I create a user with name "kiwikiwi" and password "kiwikiwi" with roles "image_admin" 2s 38ms

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

Scenario:
Create a Docker user with image administrators rights

2s 163ms 2

New user docker created with roles: image_admin

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

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

@no_auth_registry

Scenario:
Create an image store without credentials

3s 430ms 7

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

And I follow "Create" 670ms

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

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

And I click on "create-btn" 90ms

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

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

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

Scenario:
Log in as admin user

26s 772ms 1

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

Scenario:
Disable scheduled reposyncs

4s 680ms 5

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

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

And I choose "disabled" 57ms

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

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

Scenario:
Disable scheduled Cobbler syncs

3s 583ms 5

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

And I follow "cobbler-sync-default" 321ms

And I choose "disabled" 50ms

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

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

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

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

Scenario:
List available channels

30s 196ms 5

When I refresh SCC 27s 834ms

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

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

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

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

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

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

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

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

When I remove the mgr-sync cache file 667ms

And I execute mgr-sync refresh 1m 785ms

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

Feature:Synchronize products in the products page of the Setup Wizard 57m 21s 546ms 6 2 9

@scc_credentials

Scenario:
Refresh SCC

25s 186ms 1

When I refresh SCC 25s 186ms

@scc_credentials

Scenario:
Let the products page appear

2s 324ms 6

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

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

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

Then I should see a "Arch" text 104ms

And I should see a "Channels" text 104ms

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

@scc_credentials

Scenario:
Use the products and architecture filters

2s 277ms 7

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

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

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

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

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

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

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

@scc_credentials @susemanager

Scenario:
View the channels list in the products page

< 1ms 9

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

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

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

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

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

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

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

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

When I close the modal dialog 0s

@scc_credentials @susemanager

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

< 1ms 30

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

Then the SLE15 SP7 product should be added 0s

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

@uyuni

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

3m 22s 550ms 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 242ms

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

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

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

@containerized_server @proxy @uyuni

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

1m 18s 466ms 2

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

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

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

@scc_credentials @uyuni @build_host

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

51m 37s 75ms 20 1

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Then I should see the "Development Tools Module 15 SP7 x86_64" selected 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 168ms

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

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

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

And I wait until all synchronized channels for "sles15-sp7" have finished 51m Show Error +

                                            
 Hit timeout during reposync. These channels did not complete:
 ["sle-module-devtools15-sp7-updates-x86_64", "sle-module-devtools15-sp7-pool-x86_64"] (ScriptError)
./features/step_definitions/command_steps.rb:482:in `rescue in block in (top (required))'
./features/step_definitions/command_steps.rb:462:in `/^I wait until all synchronized channels for "([^"]*)" have finished$/'
features/reposync/srv_sync_products.feature:113:in `I wait until all synchronized channels for "sles15-sp7" have finished'

16s 821ms Show Info +

10:48:05:000 - 11:39:26:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/admin/setup/products

Screenshot +

@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

33s 665ms 7 1

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

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

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

And I wait until I do not see "Loading" text 1s 495ms

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

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

And I should only see success signs in the product list 14s 286ms Show Error +

                                            
 At least one product is not fully synchronized (ScriptError)
./features/step_definitions/navigation_steps.rb:855:in `/^I should only see success signs in the product list$/'
features/reposync/srv_sync_products.feature:236:in `I should only see success signs in the product list'

15s 440ms Show Info +

11:39:43:000 - 11:40:03:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/admin/setup/products

Screenshot +

@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 26s 181ms 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

882ms 1

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

Scenario:
Add a fake base channel for x86_64

2s 121ms 10

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

And I follow "Create Channel" 558ms

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

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

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

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

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

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

And I click on "Create Channel" 869ms

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

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

1s 74ms 10

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

And I follow "Create Channel" 453ms

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

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

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

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

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

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

And I click on "Create Channel" 56ms

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

@sle_minion

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

1s 758ms 10

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

And I follow "Create Channel" 508ms

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

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

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

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

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

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

And I click on "Create Channel" 708ms

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

Scenario:
Add a fake base channel for i586

965ms 10

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

And I follow "Create Channel" 359ms

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

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

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

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

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

And I click on "Create Channel" 55ms

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

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

1s 764ms 10

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

And I follow "Create Channel" 527ms

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

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

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

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

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

And I click on "Create Channel" 694ms

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

Scenario:
Add a test base channel for x86_64

1s 531ms 10

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

And I follow "Create Channel" 385ms

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

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

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

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

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

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

And I click on "Create Channel" 618ms

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

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

1s 665ms 10

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

And I follow "Create Channel" 390ms

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

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

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

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

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

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

And I click on "Create Channel" 713ms

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

@pxeboot_minion @uyuni @scc_credentials

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

< 1ms 10

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

And I follow "Create Channel" 0s

And I enter "Fake-RPM-Terminal-Channel" as "Channel Name" 0s

And I enter "fake-rpm-terminal-channel" as "Channel Label" 0s

And I select the parent channel for the "pxeboot_minion" from "Parent Channel" 0s

And I select "x86_64" from "Architecture:" 0s

And I enter "Fake-RPM-Terminal-Channel for testing" as "Channel Summary" 0s

And I enter "Description for Fake-RPM-Terminal-Channel Child Channel." as "Channel Description" 0s

And I click on "Create Channel" 0s

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

@deblike_minion

Scenario:
Add Debian-like AMD64 base channel

11s 495ms 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" 74ms

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

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

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

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

And I uncheck "gpg_check" 10s 91ms

And I click on "Create Channel" 545ms

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

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 377ms 10

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

And I follow "Create Channel" 311ms

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

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

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

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

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

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

And I click on "Create Channel" 524ms

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

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 546ms 10

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

And I follow "Create Channel" 412ms

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

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

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

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

565ms 1

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

Scenario:
Create a fake repository for distributions using RPM

1s 283ms 7

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

And I follow "Create Repository" 364ms

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

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

And I click on "Create Repository" 517ms

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

And I should see "metadataSigned" as checked 20ms

Scenario:
Disable metadata check for the fake RPM repository

10s 973ms 6

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

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

And I uncheck "metadataSigned" 10s 82ms

And I click on "Update Repository" 459ms

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

And I should see "metadataSigned" as unchecked 16ms

@rhlike_minion

Scenario:
Create a fake AppStream repository

1s 21ms 7

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

And I follow "Create Repository" 289ms

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

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

And I click on "Create Repository" 441ms

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

And I should see "metadataSigned" as checked 15ms

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

10s 962ms 6

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

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

And I uncheck "metadataSigned" 10s 53ms

And I click on "Update Repository" 471ms

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

And I should see "metadataSigned" as unchecked 15ms

@sle_minion

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

2s 249ms 9

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

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

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

And I click on "Update Channel" 66ms

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

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

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

And I click on "Save Repositories" 602ms

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

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

2s 511ms 9

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

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

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

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

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

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

And I click on "Save Repositories" 932ms

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

@rhlike_minion

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

1s 985ms 9

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

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

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

And I click on "Update Channel" 55ms

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

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

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

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

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

@rhlike_minion

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

2s 203ms 9

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

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

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

And I click on "Update Channel" 58ms

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

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

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

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

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

Scenario:
Create a fake repository for i586

11s 176ms 7

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

And I follow "Create Repository" 359ms

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

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

And I uncheck "metadataSigned" 10s 65ms

And I click on "Create Repository" 475ms

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

Scenario:
Add the repository to the i586 channel

1s 878ms 9

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

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

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

And I click on "Update Channel" 529ms

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

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

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

And I click on "Save Repositories" 474ms

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

@sle_minion

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

1s 824ms 6

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

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

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

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

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

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

@deblike_minion

Scenario:
Create a fake repository for Debian-like

686ms 7

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

And I follow "Create Repository" 284ms

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

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

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

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

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

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

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

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

And I click on "Save Repositories" 825ms

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

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Add the repository to the terminal child channel

< 1ms 9

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

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

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

And I click on "Update Channel" 0s

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

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

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

And I click on "Save Repositories" 0s

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

@skip_if_github_validation
Feature:Create custom channels with development repositories 54s 677ms 8 1

In Order to use product packages in development to the clients
As an authorized user
I want to create custom channels for each distribution

Scenario:
Log in as admin user

486ms 1

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

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 589ms 10

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

And I follow "Create Channel" 332ms

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

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

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

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

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

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

And I click on "Create Channel" 580ms

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

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

17s 509ms 1 1

When I prepare the development repositories of "sle_minion" as part of "devel-suse-channel" channel 1s 564ms Show Error +

                                            
 No FQDN for 'uyuni-master-suse-minion'. Response code:  (StandardError)
./features/support/remote_node.rb:46:in `initialize'
./features/support/remote_nodes_env.rb:39:in `new'
./features/support/remote_nodes_env.rb:39:in `get_target'
./features/step_definitions/setup_steps.rb:534:in `/^I prepare the development repositories of "([^"]*)" as part of "([^"]*)" channel$/'
features/reposync/srv_create_devel_channels.feature:28:in `I prepare the development repositories of "sle_minion" as part of "devel-suse-channel" channel'

15s 944ms Show Info +

11:41:53:000 - 11:41:55:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/manage/Edit.do?cid=131

Screenshot +

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 695ms 10

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

And I follow "Create Channel" 419ms

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

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

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

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

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

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

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

5s 458ms 1

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

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

1s 654ms 10

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

And I follow "Create Channel" 430ms

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

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

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

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

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

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

And I click on "Create Channel" 658ms

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

@deblike_minion

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

11s 910ms 1

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

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

2s 867ms 10

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

And I follow "Create Channel" 588ms

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

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

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

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

And I enter "Devel-RH-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" 1s 720ms

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

@rhlike_minion

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

11s 505ms 1

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

Feature:Synchronize fake channels 5m 50s 428ms 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

3s 415ms 2

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

And I enable source package syncing 2s 305ms

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

7s 878ms 9

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

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

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

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

And I follow "Sync" 1s 20ms

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" 3s 172ms

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

And I wait until the channel "fake-rpm-suse-channel" has been synced 1s 503ms

@sle_minion

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

5m 1s 899ms 2

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

And solver file for "fake-rpm-suse-channel" should reference "orion-dummy-1.1-1.1.x86_64.rpm" 4m 54s 768ms

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

4s 73ms 9

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

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

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

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

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

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

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

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

Scenario:
Synchronize Test-Child-Channel-x86_64 channel

3s 965ms 9

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

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

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

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

And I follow "Sync" 467ms

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

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

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

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

@sle_minion

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

3s 962ms 9

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

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

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

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

And I follow "Sync" 543ms

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

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

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

@deblike_minion

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

3s 982ms 9

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

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

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

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

And I follow "Sync" 526ms

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

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

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

@rhlike_minion

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

4s 185ms 9

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

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

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

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

And I follow "Sync" 778ms

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

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

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

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

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 221ms 9

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

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

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

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

And I follow "Sync" 778ms

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

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

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

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

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Synchronize the repository in the terminal channel

< 1ms 9

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

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

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

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

And I follow "Sync" 0s

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

And I click on "Sync Now" 0s

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

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

@pxeboot_minion @uyuni @scc_credentials

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

< 1ms 2

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

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

Scenario:
Refresh the errata cache

6s 626ms 6

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

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

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

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

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

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

Scenario:
Refresh the channel's repository data

5s 154ms 6

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

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

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

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

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

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

Scenario:
Cleanup disable source package syncing

1s 61ms 1

Then I disable source package syncing 1s 61ms

@skip_if_github_validation
Feature:Synchronize development channels 39s 873ms 3 1

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

27s 637ms 8 1 1

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

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

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

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

And I follow "Sync" 387ms

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

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

Then I should see a "Repository sync scheduled for Devel-SUSE-Channel." text 10s 44ms Show Error +

                                            
 Text 'Repository sync scheduled for Devel-SUSE-Channel.' not found (ScriptError)
./features/step_definitions/navigation_steps.rb:661:in `/^I should see a "([^"]*)" text$/'
features/reposync/srv_sync_devel_channels.feature:19:in `I should see a "Repository sync scheduled for Devel-SUSE-Channel." text'

And I wait until the channel "devel-suse-channel" has been synced 0s

14s 883ms Show Info +

11:48:49:000 - 11:49:02:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/manage/Sync.do?cid=131

Screenshot +

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

3s 919ms 9

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

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

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

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

And I follow "Sync" 320ms

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

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

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

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 296ms 9

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

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

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

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

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

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

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

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

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

4s 19ms 9

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

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

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

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

And I follow "Sync" 697ms

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

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

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

Feature:Create activation keys 17s 172ms 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

458ms 1

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

@sle_minion

Scenario:
Create an activation key with a channel

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

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

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

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

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

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

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

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

@ssh_minion

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

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

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

@ssh_minion

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

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

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

@proxy

Scenario:
Create an activation key for the proxy

2s 489ms 2

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

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

@build_host

Scenario:
Create an activation key for the build host

3s 396ms 3

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

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

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

@scc_credentials

Scenario:
Create an activation key for the terminal

2s 298ms 2

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

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

Feature:Update activation keys 28s 414ms 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

462ms 1

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 661ms

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 623ms

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

@scc_credentials @susemanager

Scenario:
Update SLE SSH tunnel key with synced base product

< 1ms 14

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

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

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

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

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

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

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

And I click on "Update Activation Key" 0s

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

@uyuni

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

2s 984ms 10

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 1s 154ms

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

@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

4s 152ms 20

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

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

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

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

And I wait for child channels to appear 776ms

And I include the recommended child channels 169ms

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

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

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 773ms

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

@scc_credentials @uyuni @build_host

Scenario:
Update build host key with Uyuni client tools

4s 281ms 9

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

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

And I wait for child channels to appear 2s 634ms

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

And I wait for child channels to appear 270ms

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

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

And I click on "Update Activation Key" 1s 62ms

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

@skip_if_github_validation @scc_credentials @uyuni @build_host

Scenario:
Update build host key with dev child channel

2s 762ms 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 1s 373ms

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

And I wait for child channels to appear 266ms

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

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

And I click on "Update Activation Key" 793ms

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

@scc_credentials @build_host

Scenario:
Update terminal key with synced base product

3s 382ms 16

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

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

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

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

And I wait for child channels to appear 541ms

And I include the recommended child channels 164ms

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

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

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

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

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

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

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

And I click on "Update Activation Key" 642ms

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

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

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

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

And I wait for child channels to appear 807ms

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

And I click on "Update Activation Key" 55ms

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

@skip_if_github_validation @deblike_minion

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

1s 849ms 6

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

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

And I wait for child channels to appear 959ms

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

And I click on "Update Activation Key" 596ms

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

@skip_if_github_validation @rhlike_minion

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

1s 767ms 6

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

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

And I wait for child channels to appear 886ms

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

And I click on "Update Activation Key" 602ms

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

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

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

@sle_minion

Scenario:
Create the bootstrap repository for SUSE Minion

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

@proxy

Scenario:
Create the bootstrap repository for Proxy

2s 140ms 1

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

@build_host

Scenario:
Create the bootstrap repository for Build Host

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

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

Scenario:
Call spacewalk-debug on server

14s 440ms 1

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

Scenario:
Check the tomcat logs on server

654ms 1

Then the tomcat logs should not contain errors 654ms

Scenario:
Check salt event log for failures on server

1s 732ms 1

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

Scenario:
Check the taskomatic logs on server

697ms 1

Then the taskomatic logs should not contain errors 697ms

Scenario:
Check for out of memory errors

656ms 1

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

Feature:Debug the clients after the testsuite has run 44s 686ms 1

Scenario:
Extract the logs from all our clients

44s 686ms 1

When I extract the log files from all our active nodes 44s 686ms

@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

148

Passed Scenarios

114

Failed Scenarios

4

Skipped Scenarios

30

@proxy Scenario:The proxy is healthy 4s 529ms 4

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

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

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

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

@deblike_minion Scenario:The Debian-like minion is healthy 5s 999ms 4

@skip_if_cloud Scenario:The external resources can be reached < 1ms 3

@server_http_proxy Scenario:The HTTP proxy is working < 1ms 1

@auth_registry Scenario:The registry with authentication is healthy 657ms 1

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

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

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

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

@scc_credentials Scenario:Refresh SCC 25s 186ms 1

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

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

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

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

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

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

@scc_credentials @uyuni @build_host Scenario:Synchronize SLES 15 SP7 product with recommended sub-products for Retail feature 51m 37s 75ms 20 1

@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 33s 665ms 7 1

@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 758ms 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 495ms 11

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

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

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

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

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

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

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

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

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

@deblike_minion Scenario:Add the repository to the Debian-like base channel 1s 429ms 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 54s 677ms 8 1

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

@sle_minion Scenario:Create custom repositories inside the SUSE custom channel 17s 509ms 1 1

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

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

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

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

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

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

@sle_minion Scenario:Synchronize Fake-RPM-SUSE-Channel channel 7s 878ms 9

@sle_minion Scenario:Verify state of Fake-RPM-SUSE-Channel channel 5m 1s 899ms 2

@skip_if_github_validation Scenario:Synchronize Fake-Child-Channel-i586 channel 4s 73ms 9

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

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

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

@rhlike_minion Scenario:Synchronize Fake-Base-Channel-AppStream channel 4s 221ms 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 39s 873ms 3 1

@sle_minion Scenario:Synchronize Devel-SUSE-Channel channel 27s 637ms 8 1 1

@deblike_minion Scenario:Synchronize Devel-Debian-like-Channel channel 3s 919ms 9

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

@proxy

Scenario:
The proxy is healthy

4s 529ms 4

@sle_minion

Scenario:
The minion is healthy

6s 235ms 4

@build_host

Scenario:
The build host is healthy

4s 106ms 4

@ssh_minion

Scenario:
The SSH minion is healthy

6s 656ms 4

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 86ms 4

@deblike_minion

Scenario:
The Debian-like minion is healthy

5s 999ms 4

@skip_if_cloud

Scenario:
The external resources can be reached

< 1ms 3

@server_http_proxy

Scenario:
The HTTP proxy is working

< 1ms 1

@auth_registry

Scenario:
The registry with authentication is healthy

657ms 1

@no_auth_registry

Scenario:
The registry without authentication is healthy

656ms 1

@custom_download_endpoint

Scenario:
The custom download endpoint is working

632ms 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 430ms 7

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

@proxy @susemanager

Scenario:
List all products for SUSE Multi-Linux Manager

< 1ms 6

@scc_credentials

Scenario:
Refresh SCC

25s 186ms 1

@scc_credentials

Scenario:
Let the products page appear

2s 324ms 6

@scc_credentials

Scenario:
Use the products and architecture filters

2s 277ms 7

@scc_credentials @susemanager

Scenario:
View the channels list in the products page

< 1ms 9

@scc_credentials @susemanager

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

< 1ms 30

@uyuni

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

3m 22s 550ms 4

@containerized_server @proxy @uyuni

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

1m 18s 466ms 2

@scc_credentials @uyuni @build_host

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

51m 37s 75ms 20 1

@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

33s 665ms 7 1

@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 758ms 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 495ms 11

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 377ms 10

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 546ms 10

@rhlike_minion

Scenario:
Create a fake AppStream repository

1s 21ms 7

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

10s 962ms 6

@sle_minion

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

2s 249ms 9

@rhlike_minion

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

1s 985ms 9

@rhlike_minion

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

2s 203ms 9

@sle_minion

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

1s 824ms 6

@deblike_minion

Scenario:
Create a fake repository for Debian-like

686ms 7

@deblike_minion

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

1s 429ms 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 54s 677ms 8 1

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 589ms 10

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

17s 509ms 1 1

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 695ms 10

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

5s 458ms 1

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

1s 654ms 10

@deblike_minion

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

11s 910ms 1

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

2s 867ms 10

@rhlike_minion

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

11s 505ms 1

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

7s 878ms 9

@sle_minion

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

5m 1s 899ms 2

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

4s 73ms 9

@sle_minion

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

3s 962ms 9

@deblike_minion

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

3s 982ms 9

@rhlike_minion

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

4s 185ms 9

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 221ms 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 39s 873ms 3 1

@sle_minion

Scenario:
Synchronize Devel-SUSE-Channel channel

27s 637ms 8 1 1

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

3s 919ms 9

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 296ms 9