Cucumber Feature Report

All Scenarios

148

Passed Scenarios

114

Failed Scenarios

4

Skipped Scenarios

30

Execution Time: 71m 34s 979ms

Expand All | Collapse All

Metadata

App Version: Uyuni/Head

Browser: Chrome

Platform: x86_64

Parallel: Disabled

Feature:Sanity checks 44s 983ms 10 2

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

Scenario:
The server is healthy

11s 891ms 19

Then "server" should have a FQDN 395ms

And reverse resolution should work for "server" 632ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@proxy

Scenario:
The proxy is healthy

4s 466ms 4

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

And reverse resolution should work for "proxy" 281ms

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

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

@sle_minion

Scenario:
The minion is healthy

6s 692ms 4

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

And reverse resolution should work for "sle_minion" 419ms

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

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

@build_host

Scenario:
The build host is healthy

3s 807ms 4

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

And reverse resolution should work for "build_host" 219ms

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

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

@ssh_minion

Scenario:
The SSH minion is healthy

6s 251ms 4

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

And reverse resolution should work for "ssh_minion" 433ms

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

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

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 168ms 4

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

And reverse resolution should work for "rhlike_minion" 183ms

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

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

@deblike_minion

Scenario:
The Debian-like minion is healthy

6s 759ms 4

Then "deblike_minion" should have a FQDN 5s 211ms

And reverse resolution should work for "deblike_minion" 314ms

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

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

@skip_if_cloud

Scenario:
The external resources can be reached

< 1ms 3

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

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

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

@server_http_proxy

Scenario:
The HTTP proxy is working

< 1ms 1

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

@auth_registry

Scenario:
The registry with authentication is healthy

652ms 1

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

@no_auth_registry

Scenario:
The registry without authentication is healthy

660ms 1

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

@custom_download_endpoint

Scenario:
The custom download endpoint is working

633ms 1

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

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

666ms 1

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

@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

40s 18ms 1

Given I am authorized for the "Admin" section 40s 18ms

Scenario:
Wait for refresh of list of products to finish

3s 640ms 1

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

Scenario:
Create testing username

2s 89ms 12

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

And I follow "Create User" 543ms

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

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

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

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

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

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

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

And I click on "Create Login" 851ms

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

And I should see a "testing" link 12ms

Scenario:
Grant testing user administrative priviledges

1s 781ms 10

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

And I follow "testing" 572ms

And I check "role_org_admin" 87ms

And I check "role_system_group_admin" 84ms

And I check "role_channel_admin" 86ms

And I check "role_activation_key_admin" 79ms

And I check "role_config_admin" 81ms

And I click on "Update" 575ms

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

And I should see a "testing" text 67ms

@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

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

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

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

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

@scc_credentials @no_mirror

Scenario:
Enter valid SCC credentials

< 1ms 6

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

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

And I ask to add new credentials 0s

And I enter the SCC credentials 0s

And I click on "Save" 0s

And I wait until the SCC credentials are valid 0s

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

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

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

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

And I click on "Save Preferences" 648ms

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

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

3s 309ms 5

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

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

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

And I click on "Save Preferences" 617ms

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

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

Scenario:
Create a Kiwi user with image administrators rights

4s 26ms 2

New user kiwikiwi created with roles: image_admin

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

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

Feature:Prepare server for using Docker 4s 824ms 2

Scenario:
Create a Docker user with image administrators rights

2s 7ms 2

New user docker created with roles: image_admin

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

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

@no_auth_registry

Scenario:
Create an image store without credentials

2s 816ms 7

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

And I follow "Create" 521ms

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

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

And I click on "create-btn" 63ms

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

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

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

Scenario:
Log in as admin user

26s 732ms 1

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

Scenario:
Disable scheduled reposyncs

4s 546ms 5

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

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

And I choose "disabled" 60ms

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

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

Scenario:
Disable scheduled Cobbler syncs

4s 589ms 5

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

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

And I choose "disabled" 48ms

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

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

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

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

Scenario:
List available channels

29s 419ms 5

When I refresh SCC 27s 101ms

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

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

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

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

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

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

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

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

When I remove the mgr-sync cache file 651ms

And I execute mgr-sync refresh 1m 777ms

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 13s 781ms 6 2 9

@scc_credentials

Scenario:
Refresh SCC

24s 961ms 1

When I refresh SCC 24s 961ms

@scc_credentials

Scenario:
Let the products page appear

2s 61ms 6

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

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

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

Then I should see a "Arch" text 110ms

And I should see a "Channels" text 107ms

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

@scc_credentials

Scenario:
Use the products and architecture filters

2s 377ms 7

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

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

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

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

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

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

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

@scc_credentials @susemanager

Scenario:
View the channels list in the products page

< 1ms 9

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

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

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

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

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

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

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

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

When I close the modal dialog 0s

@scc_credentials @susemanager

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

< 1ms 30

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

Then the SLE15 SP7 product should be added 0s

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

@uyuni

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

3m 25s 696ms 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 46ms

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

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

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

@containerized_server @proxy @uyuni

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

1m 6s 795ms 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" 22s 690ms

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

@scc_credentials @uyuni @build_host

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

51m 37s 158ms 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 sle-product-sles15-sp7-pool-x86_64 finished reposync
Channel sle-product-sles15-sp7-updates-x86_64 finished reposync
Channel sle15-sp7-installer-updates-x86_64 finished reposync
Channel sles15-sp7-devel-uyuni-client-x86_64 finished reposync
1 minutes out of 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
Channel sle-module-basesystem15-sp7-updates-x86_64 finished reposync
12 minutes out of 51 waiting for 'sles15-sp7' channels to finish 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
17 minutes out of 51 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-server-applications15-sp7-updates-x86_64 finished reposync
Channel sle-module-python3-15-sp7-updates-x86_64 finished reposync
Channel sle-module-server-applications15-sp7-pool-x86_64 finished reposync
Channel sle-module-python3-15-sp7-pool-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-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
Channel sle-module-desktop-applications15-sp7-pool-x86_64 finished reposync
26 minutes out of 51 waiting for 'sles15-sp7' channels to finish 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
Channel sle-module-devtools15-sp7-pool-x86_64 finished 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
35 minutes out of 51 waiting for 'sles15-sp7' channels to finish reposync

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 60ms

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

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

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

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

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"] (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 471ms Show Info +

16:11:10:000 - 17:02:32: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

34s 729ms 7 1

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

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

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

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

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

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

And I should only see success signs in the product list 13s 979ms 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'

17s 84ms Show Info +

17:02:48:000 - 17:03:08: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 29s 896ms 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

818ms 1

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

Scenario:
Add a fake base channel for x86_64

2s 389ms 10

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

And I follow "Create Channel" 586ms

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

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

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

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

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

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

And I click on "Create Channel" 1s 91ms

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

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

1s 276ms 10

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

And I follow "Create Channel" 637ms

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

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

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

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

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

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

And I click on "Create Channel" 57ms

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

@sle_minion

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

1s 308ms 10

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

And I follow "Create Channel" 692ms

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

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

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

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

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

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

And I click on "Create Channel" 54ms

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

Scenario:
Add a fake base channel for i586

2s 391ms 10

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

And I follow "Create Channel" 633ms

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

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

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

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

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

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

And I click on "Create Channel" 56ms

Then I should see a "Channel Fake-Base-Channel-i586 created." text 1s 169ms

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

2s 242ms 10

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

And I follow "Create Channel" 551ms

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

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

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

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

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

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

And I click on "Create Channel" 57ms

Then I should see a "Channel Fake-Child-Channel-i586 created." text 1s 132ms

Scenario:
Add a test base channel for x86_64

1s 935ms 10

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

And I follow "Create Channel" 552ms

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

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

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

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

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

And I click on "Create Channel" 836ms

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

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

1s 831ms 10

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

And I follow "Create Channel" 385ms

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

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

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

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

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

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

And I click on "Create Channel" 858ms

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

@pxeboot_minion @uyuni @scc_credentials

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

< 1ms 10

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

And I follow "Create Channel" 0s

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

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

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

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

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

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

And I click on "Create Channel" 0s

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

@deblike_minion

Scenario:
Add Debian-like AMD64 base channel

12s 364ms 11

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

And I follow "Create Channel" 492ms

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

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

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

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

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

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

And I uncheck "gpg_check" 10s 94ms

And I click on "Create Channel" 1s 209ms

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

@rhlike_minion

Scenario:
Add a RedHat-like base channel

2s 136ms 10

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

And I follow "Create Channel" 648ms

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

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

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

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

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

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

And I click on "Create Channel" 940ms

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

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 199ms 10

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

And I follow "Create Channel" 586ms

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

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

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

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

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

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

And I click on "Create Channel" 59ms

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

Feature:Create fake repositories for each fake child channel 1m 2s 632ms 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

1s 299ms 1

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

Scenario:
Create a fake repository for distributions using RPM

2s 133ms 7

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

And I follow "Create Repository" 847ms

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

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

And I click on "Create Repository" 871ms

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

And I should see "metadataSigned" as checked 22ms

Scenario:
Disable metadata check for the fake RPM repository

11s 863ms 6

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

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

And I uncheck "metadataSigned" 10s 76ms

And I click on "Update Repository" 996ms

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

And I should see "metadataSigned" as unchecked 15ms

@rhlike_minion

Scenario:
Create a fake AppStream repository

2s 372ms 7

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

And I follow "Create Repository" 905ms

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

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

And I click on "Create Repository" 1s 177ms

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

And I should see "metadataSigned" as checked 17ms

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

11s 579ms 6

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

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

And I uncheck "metadataSigned" 10s 72ms

And I click on "Update Repository" 839ms

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

And I should see "metadataSigned" as unchecked 18ms

@sle_minion

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

3s 642ms 9

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

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

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

And I click on "Update Channel" 1s 295ms

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

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

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

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

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

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

3s 503ms 9

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

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

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

And I click on "Update Channel" 1s 464ms

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

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

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

And I click on "Save Repositories" 959ms

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

@rhlike_minion

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

3s 299ms 9

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

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

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

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

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

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

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

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

@rhlike_minion

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

3s 553ms 9

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

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

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

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

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

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

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

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

Scenario:
Create a fake repository for i586

11s 565ms 7

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

And I follow "Create Repository" 439ms

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

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

And I uncheck "metadataSigned" 10s 91ms

And I click on "Create Repository" 743ms

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

Scenario:
Add the repository to the i586 channel

2s 163ms 9

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

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

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

And I click on "Update Channel" 67ms

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

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

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

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

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

@sle_minion

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

2s 200ms 6

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

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

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

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

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

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

@deblike_minion

Scenario:
Create a fake repository for Debian-like

1s 522ms 7

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

And I follow "Create Repository" 372ms

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

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

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

And I click on "Create Repository" 789ms

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

@deblike_minion

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

1s 933ms 6

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

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

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

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

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

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

@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 49s 408ms 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

792ms 1

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

@sle_minion

Scenario:
Create a custom channel for SUSE minions

2s 83ms 10

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

And I follow "Create Channel" 497ms

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

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

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

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

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

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

And I click on "Create Channel" 888ms

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

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

16s 745ms 1 1

When I prepare the development repositories of "sle_minion" as part of "devel-suse-channel" channel 1s 551ms 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 193ms Show Info +

17:05:25:000 - 17:05:26: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

2s 196ms 10

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

And I follow "Create Channel" 585ms

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

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

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

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

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

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

And I click on "Create Channel" 1s 51ms

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

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

6s 590ms 1

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

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

2s 211ms 10

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

And I follow "Create Channel" 693ms

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

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

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

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

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

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

And I click on "Create Channel" 868ms

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

@deblike_minion

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

10s 410ms 1

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

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 903ms 10

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

And I follow "Create Channel" 533ms

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

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

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

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

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

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

And I click on "Create Channel" 778ms

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

@rhlike_minion

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

6s 476ms 1

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

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

2s 343ms 2

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

And I enable source package syncing 1s 500ms

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

5s 106ms 9

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

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

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

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

And I follow "Sync" 637ms

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

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

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

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

@sle_minion

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

2m 57s 192ms 2

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

And solver file for "fake-rpm-suse-channel" should reference "orion-dummy-1.1-1.1.x86_64.rpm" 2m 51s 824ms

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

1m 47s 362ms 9

1 minutes out of 5 waiting for 'fake-child-channel-i586' channel to be synchronized

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

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

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

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

And I follow "Sync" 487ms

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

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

And I wait until the channel "fake-child-channel-i586" has been synced 1m 43s 733ms

Scenario:
Synchronize Test-Child-Channel-x86_64 channel

3s 635ms 9

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

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

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

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

And I follow "Sync" 326ms

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

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

@sle_minion

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

4s 159ms 9

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

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

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

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

And I follow "Sync" 725ms

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

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

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

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

@deblike_minion

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

4s 133ms 9

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

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

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

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

And I follow "Sync" 788ms

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

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

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

@rhlike_minion

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

4s 360ms 9

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

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

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

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

And I follow "Sync" 930ms

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

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

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

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 90ms 9

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

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

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

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

And I follow "Sync" 625ms

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

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

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

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

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

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

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

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

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

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

Scenario:
Refresh the channel's repository data

5s 343ms 6

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

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

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

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

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

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

Scenario:
Cleanup disable source package syncing

978ms 1

Then I disable source package syncing 978ms

@skip_if_github_validation
Feature:Synchronize development channels 38s 977ms 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

26s 444ms 8 1 1

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

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

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

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

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

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

Then I should see a "Repository sync scheduled for Devel-SUSE-Channel." text 10s 75ms 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

13s 625ms Show Info +

17:11:47:000 - 17:12:01: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

4s 11ms 9

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

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

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

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

And I follow "Sync" 633ms

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

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

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

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

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 279ms 9

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

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

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

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

And I follow "Sync" 955ms

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

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

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

4s 241ms 9

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

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

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

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

And I follow "Sync" 849ms

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

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

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

Feature:Create activation keys 16s 540ms 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

454ms 1

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

@sle_minion

Scenario:
Create an activation key with a channel

1s 880ms 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 382ms

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

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

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

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

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

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

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

@ssh_minion

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

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

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

@ssh_minion

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

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

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

@proxy

Scenario:
Create an activation key for the proxy

1s 789ms 2

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

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

@build_host

Scenario:
Create an activation key for the build host

3s 209ms 3

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

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

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

@scc_credentials

Scenario:
Create an activation key for the terminal

2s 892ms 2

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

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

Feature:Update activation keys 26s 43ms 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

456ms 1

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 612ms

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 595ms

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

@scc_credentials @susemanager

Scenario:
Update SLE SSH tunnel key with synced base product

< 1ms 14

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

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

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

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

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

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

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

And I click on "Update Activation Key" 0s

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

@uyuni

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

1s 862ms 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 68ms

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

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

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

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

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

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

And I click on "Update Activation Key" 61ms

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

3s 328ms 20

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

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

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

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

And I wait for child channels to appear 493ms

And I include the recommended child channels 165ms

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 708ms

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

@scc_credentials @uyuni @build_host

Scenario:
Update build host key with Uyuni client tools

2s 505ms 9

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

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

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

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

And I wait for child channels to appear 277ms

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

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

And I click on "Update Activation Key" 616ms

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

@skip_if_github_validation @scc_credentials @uyuni @build_host

Scenario:
Update build host key with dev child channel

3s 501ms 9

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

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

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

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

And I wait for child channels to appear 295ms

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

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

And I click on "Update Activation Key" 891ms

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

@scc_credentials @build_host

Scenario:
Update terminal key with synced base product

3s 620ms 16

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

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

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

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

And I wait for child channels to appear 547ms

And I include the recommended child channels 158ms

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

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

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

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

And I click on "Update Activation Key" 642ms

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

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

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

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

And I wait for child channels to appear 902ms

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

And I click on "Update Activation Key" 589ms

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

@skip_if_github_validation @deblike_minion

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

2s 132ms 6

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

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

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

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

And I click on "Update Activation Key" 636ms

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

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

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

And I wait for child channels to appear 909ms

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

And I click on "Update Activation Key" 620ms

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

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

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

@sle_minion

Scenario:
Create the bootstrap repository for SUSE Minion

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

@proxy

Scenario:
Create the bootstrap repository for Proxy

2s 270ms 1

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

@build_host

Scenario:
Create the bootstrap repository for Build Host

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

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

Scenario:
Call spacewalk-debug on server

14s 392ms 1

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

Scenario:
Check the tomcat logs on server

676ms 1

Then the tomcat logs should not contain errors 676ms

Scenario:
Check salt event log for failures on server

1s 881ms 1

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

Scenario:
Check the taskomatic logs on server

730ms 1

Then the taskomatic logs should not contain errors 730ms

Scenario:
Check for out of memory errors

664ms 1

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

Feature:Debug the clients after the testsuite has run 42s 549ms 1

Scenario:
Extract the logs from all our clients

42s 549ms 1

When I extract the log files from all our active nodes 42s 549ms

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

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

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

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

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

@deblike_minion Scenario:The Debian-like minion is healthy 6s 759ms 4

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

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

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

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

@custom_download_endpoint Scenario:The custom download endpoint is working 633ms 1

@skip_if_containerized_server Scenario:Create admin user and first organization < 1ms 12

@server_http_proxy Scenario:Setup HTTP proxy < 1ms 9

@scc_credentials @no_mirror Scenario:Enter valid SCC credentials < 1ms 6

@no_auth_registry Scenario:Create an image store without credentials 2s 816ms 7

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

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

@scc_credentials Scenario:Refresh SCC 24s 961ms 1

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

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

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

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

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

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

@scc_credentials @uyuni @build_host Scenario:Synchronize SLES 15 SP7 product with recommended sub-products for Retail feature 51m 37s 158ms 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 34s 729ms 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 308ms 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 12s 364ms 11

@rhlike_minion Scenario:Add a RedHat-like base channel 2s 136ms 10

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

@rhlike_minion Scenario:Create a fake AppStream repository 2s 372ms 7

@rhlike_minion Scenario:Disable metadata check for the fake AppStream repository 11s 579ms 6

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

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

@rhlike_minion Scenario:Add the fake AppStream repository to the AppStream base channel 3s 553ms 9

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

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

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

@sle_minion Scenario:Create a custom channel for SUSE minions 2s 83ms 10

@sle_minion Scenario:Create custom repositories inside the SUSE custom channel 16s 745ms 1 1

@uyuni @build_host Scenario:Create a custom channel for Build Host 2s 196ms 10

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

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

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

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

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

@sle_minion Scenario:Synchronize Fake-RPM-SUSE-Channel channel 5s 106ms 9

@sle_minion Scenario:Verify state of Fake-RPM-SUSE-Channel channel 2m 57s 192ms 2

@skip_if_github_validation Scenario:Synchronize Fake-Child-Channel-i586 channel 1m 47s 362ms 9

@sle_minion Scenario:Synchronize Fake-Child-Channel-SUSE-like channel 4s 159ms 9

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

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

@rhlike_minion Scenario:Synchronize Fake-Base-Channel-AppStream channel 4s 90ms 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 38s 977ms 3 1

@sle_minion Scenario:Synchronize Devel-SUSE-Channel channel 26s 444ms 8 1 1

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

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

@proxy

Scenario:
The proxy is healthy

4s 466ms 4

@sle_minion

Scenario:
The minion is healthy

6s 692ms 4

@build_host

Scenario:
The build host is healthy

3s 807ms 4

@ssh_minion

Scenario:
The SSH minion is healthy

6s 251ms 4

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 168ms 4

@deblike_minion

Scenario:
The Debian-like minion is healthy

6s 759ms 4

@skip_if_cloud

Scenario:
The external resources can be reached

< 1ms 3

@server_http_proxy

Scenario:
The HTTP proxy is working

< 1ms 1

@auth_registry

Scenario:
The registry with authentication is healthy

652ms 1

@no_auth_registry

Scenario:
The registry without authentication is healthy

660ms 1

@custom_download_endpoint

Scenario:
The custom download endpoint is working

633ms 1

@skip_if_containerized_server

Scenario:
Create admin user and first organization

< 1ms 12

@server_http_proxy

Scenario:
Setup HTTP proxy

< 1ms 9

@scc_credentials @no_mirror

Scenario:
Enter valid SCC credentials

< 1ms 6

@no_auth_registry

Scenario:
Create an image store without credentials

2s 816ms 7

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

@proxy @susemanager

Scenario:
List all products for SUSE Multi-Linux Manager

< 1ms 6

@scc_credentials

Scenario:
Refresh SCC

24s 961ms 1

@scc_credentials

Scenario:
Let the products page appear

2s 61ms 6

@scc_credentials

Scenario:
Use the products and architecture filters

2s 377ms 7

@scc_credentials @susemanager

Scenario:
View the channels list in the products page

< 1ms 9

@scc_credentials @susemanager

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

< 1ms 30

@uyuni

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

3m 25s 696ms 4

@containerized_server @proxy @uyuni

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

1m 6s 795ms 2

@scc_credentials @uyuni @build_host

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

51m 37s 158ms 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

34s 729ms 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 308ms 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

12s 364ms 11

@rhlike_minion

Scenario:
Add a RedHat-like base channel

2s 136ms 10

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 199ms 10

@rhlike_minion

Scenario:
Create a fake AppStream repository

2s 372ms 7

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

11s 579ms 6

@sle_minion

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

3s 642ms 9

@rhlike_minion

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

3s 299ms 9

@rhlike_minion

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

3s 553ms 9

@sle_minion

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

2s 200ms 6

@deblike_minion

Scenario:
Create a fake repository for Debian-like

1s 522ms 7

@deblike_minion

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

1s 933ms 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 49s 408ms 8 1

@sle_minion

Scenario:
Create a custom channel for SUSE minions

2s 83ms 10

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

16s 745ms 1 1

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

2s 196ms 10

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

6s 590ms 1

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

2s 211ms 10

@deblike_minion

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

10s 410ms 1

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 903ms 10

@rhlike_minion

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

6s 476ms 1

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

5s 106ms 9

@sle_minion

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

2m 57s 192ms 2

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

1m 47s 362ms 9

@sle_minion

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

4s 159ms 9

@deblike_minion

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

4s 133ms 9

@rhlike_minion

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

4s 360ms 9

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 90ms 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 38s 977ms 3 1

@sle_minion

Scenario:
Synchronize Devel-SUSE-Channel channel

26s 444ms 8 1 1

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

4s 11ms 9

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 279ms 9