Cucumber Feature Report

All Scenarios

148

Passed Scenarios

116

Failed Scenarios

2

Skipped Scenarios

30

Execution Time: 71m 35s 473ms

Expand All | Collapse All

Metadata

App Version: Uyuni/Head

Browser: Chrome

Platform: x86_64

Parallel: Disabled

Feature:Sanity checks 43s 908ms 10 2

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

Scenario:
The server is healthy

11s 791ms 19

Then "server" should have a FQDN 403ms

And reverse resolution should work for "server" 620ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@proxy

Scenario:
The proxy is healthy

4s 501ms 4

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

And reverse resolution should work for "proxy" 284ms

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

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

@sle_minion

Scenario:
The minion is healthy

6s 368ms 4

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

And reverse resolution should work for "sle_minion" 426ms

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

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

@build_host

Scenario:
The build host is healthy

3s 927ms 4

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

And reverse resolution should work for "build_host" 220ms

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

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

@ssh_minion

Scenario:
The SSH minion is healthy

6s 240ms 4

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

And reverse resolution should work for "ssh_minion" 409ms

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

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

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 168ms 4

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

And reverse resolution should work for "rhlike_minion" 188ms

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

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

@deblike_minion

Scenario:
The Debian-like minion is healthy

5s 948ms 4

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

And reverse resolution should work for "deblike_minion" 214ms

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

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

@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

659ms 1

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

@no_auth_registry

Scenario:
The registry without authentication is healthy

666ms 1

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

@custom_download_endpoint

Scenario:
The custom download endpoint is working

635ms 1

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

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

667ms 1

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

@skip_if_containerized_server

Scenario:
Create admin user and first organization

< 1ms 12

Given I access the host the first time 0s

When I go to the home page 0s

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

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

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

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

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

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

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

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

And I click on "Create Organization" 0s

Then I am logged in 0s

Scenario:
Log in as admin user

39s 590ms 1

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

Scenario:
Wait for refresh of list of products to finish

4s 16ms 1

When I wait until mgr-sync refresh is finished 4s 16ms

Scenario:
Create testing username

2s 181ms 12

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

And I follow "Create User" 586ms

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

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

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

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

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

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

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

And I click on "Create Login" 938ms

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

And I should see a "testing" link 11ms

Scenario:
Grant testing user administrative priviledges

1s 787ms 10

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

And I follow "testing" 507ms

And I check "role_org_admin" 84ms

And I check "role_system_group_admin" 79ms

And I check "role_channel_admin" 76ms

And I check "role_activation_key_admin" 78ms

And I check "role_config_admin" 77ms

And I click on "Update" 669ms

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

And I should see a "testing" text 71ms

@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

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

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

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

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

@scc_credentials @no_mirror

Scenario:
Enter valid SCC credentials

< 1ms 6

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

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

And I ask to add new credentials 0s

And I enter the SCC credentials 0s

And I click on "Save" 0s

And I wait until the SCC credentials are valid 0s

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

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

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

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

And I click on "Save Preferences" 758ms

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

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

3s 699ms 5

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

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

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

And I click on "Save Preferences" 590ms

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

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

Scenario:
Create a Kiwi user with image administrators rights

3s 831ms 2

New user kiwikiwi created with roles: image_admin

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

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

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

Scenario:
Create a Docker user with image administrators rights

2s 789ms 2

New user docker created with roles: image_admin

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

When I create a user with name "docker" and password "docker" with roles "image_admin" 2s 315ms

@no_auth_registry

Scenario:
Create an image store without credentials

2s 873ms 7

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

And I follow "Create" 505ms

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

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

And I click on "create-btn" 83ms

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

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

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

Scenario:
Log in as admin user

26s 922ms 1

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

Scenario:
Disable scheduled reposyncs

4s 504ms 5

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

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

And I choose "disabled" 57ms

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

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

Scenario:
Disable scheduled Cobbler syncs

4s 611ms 5

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

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

And I choose "disabled" 47ms

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

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

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

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

Scenario:
List available channels

30s 181ms 5

When I refresh SCC 27s 905ms

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

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

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

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

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

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

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

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

And I shouldn't get "ppc64" < 1ms

And I shouldn't get "s390x" < 1ms

Scenario:
Let mgr-sync time out

1m 1s 410ms 3

When I remove the mgr-sync cache file 639ms

And I execute mgr-sync refresh 1m 771ms

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

Feature:Synchronize products in the products page of the Setup Wizard 62m 27s 154ms 8 9

@scc_credentials

Scenario:
Refresh SCC

25s 111ms 1

When I refresh SCC 25s 111ms

@scc_credentials

Scenario:
Let the products page appear

2s 138ms 6

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

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

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

Then I should see a "Arch" text 108ms

And I should see a "Channels" text 109ms

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

@scc_credentials

Scenario:
Use the products and architecture filters

2s 559ms 7

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

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

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

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

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

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

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

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

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

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

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

@containerized_server @proxy @uyuni

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

44s 330ms 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" 20s 943ms

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

@scc_credentials @uyuni @build_host

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

57m 4s 278ms 20

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 56ms

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

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

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

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

And I wait until all synchronized channels for "sles15-sp7" have finished 56m 43s 890ms

@proxy @susemanager @transactional_server

Scenario:
Add SL Micro 6.1 as base OS for proxy

< 1ms 13

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

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

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

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

And I enter "SUSE Linux Micro 6.1" as the filtered product description 0s

And I select "SUSE Linux Micro 6.1 x86_64" as a product 0s

Then I should see the "SUSE Linux Micro 6.1 x86_64" selected 0s

When I open the sub-list of the product "SUSE Linux Micro 6.1 x86_64" 0s

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

And I click the Add Product button 0s

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

And I wait until I see "SUSE Linux Micro 6.1 x86_64" product has been added 0s

And I wait until all synchronized channels for "sl-micro-6.1" have finished 0s

@proxy @susemanager @skip_if_transactional_server

Scenario:
Add SLES 15 SP7 as base OS for proxy

< 1ms 11

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

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

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

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

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

And I select "SUSE Linux Enterprise Server 15 SP7 (BETA)" as a product 0s

Then I should see the "SUSE Linux Enterprise Server 15 SP7 (BETA)" selected 0s

When I click the Add Product button 0s

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

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

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

@proxy @susemanager @transactional_server

Scenario:
Add SUSE MLM Proxy Extension 5.1 with SL Micro 6.1 as base OS

< 1ms 13

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

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

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

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

And I enter "SUSE Linux Micro 6.1" as the filtered product description 0s

When I open the sub-list of the product "SUSE Linux Micro 6.1 x86_64" 0s

And I select "SUSE Linux Micro 6.1 x86_64" as a product 0s

And I select "SUSE Multi-Linux Manager Proxy Extension 5.1 x86_64" as a product 0s

Then I should see the "SUSE Multi-Linux Manager Proxy Extension 5.1 x86_64" selected 0s

When I click the Add Product button 0s

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

And I wait until I see "SUSE Multi-Linux Manager Proxy Extension 5.1 x86_64" product has been added 0s

And I wait until all synchronized channels for "suse-multi-linux-manager-proxy-51" have finished 0s

@proxy @susemanager @skip_if_transactional_server

Scenario:
Add SUSE MLM Proxy Extension 5.1 with SLES 15 SP7 as base OS

< 1ms 12

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

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

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

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

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

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

And I select "SUSE Multi-Linux Manager Proxy Extension 5.1 x86_64" as a product 0s

Then I should see the "SUSE Multi-Linux Manager Proxy Extension 5.1 x86_64" selected 0s

When I click the Add Product button 0s

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

And I wait until I see "SUSE Multi-Linux Manager Proxy Extension 5.1 x86_64" product has been added 0s

And I wait until all synchronized channels for "suse-multi-linux-manager-proxy-51-sp7" have finished 0s

@proxy @susemanager @transactional_server

Scenario:
Add SUSE MLM Retail Branch Server Extension 5.1 with SL Micro 6.1 as base OS

< 1ms 13

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

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

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

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

And I enter "SUSE Linux Micro 6.1" as the filtered product description 0s

When I open the sub-list of the product "SUSE Linux Micro 6.1 x86_64" 0s

And I select "SUSE Linux Micro 6.1 x86_64" as a product 0s

And I select "SUSE Multi-Linux Manager Retail Branch Server Extension 5.1 x86_64" as a product 0s

Then I should see the "SUSE Multi-Linux Manager Retail Branch Server Extension 5.1 x86_64" selected 0s

When I click the Add Product button 0s

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

And I wait until I see "SUSE Multi-Linux Manager Retail Branch Server Extension 5.1 x86_64" product has been added 0s

And I wait until all synchronized channels for "suse-multi-linux-manager-retail-branch-server-51" have finished 0s

@proxy @susemanager @skip_if_transactional_server

Scenario:
Add SUSE MLM Retail Branch Server Extension 5.1 with SLES 15 SP7 as base OS

< 1ms 12

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

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

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

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

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

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

And I select "SUSE Multi-Linux Manager Retail Branch Server Extension 5.1 x86_64" as a product 0s

Then I should see the "SUSE Multi-Linux Manager Retail Branch Server Extension 5.1 x86_64" selected 0s

When I click the Add Product button 0s

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

And I wait until I see "SUSE Multi-Linux Manager Retail Branch Server Extension 5.1 x86_64" product has been added 0s

And I wait until all synchronized channels for "suma-retail-branch-server-extension-51-sp7" have finished 0s

@scc_credentials @susemanager

Scenario:
Installer update channels got enabled when products were added

< 1ms 2

When I execute mgr-sync "list channels" with user "admin" and password "admin" 0s

And I should get " [I] SLE15-SP7-Installer-Updates for x86_64 SUSE Linux Enterprise Server 15 SP7 x86_64 [sle15-sp7-installer-updates-x86_64]" 0s

@scc_credentials @skip_if_github_validation

Scenario:
Detect product loading issues from the UI

43s 237ms 7

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

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

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

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

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

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

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

@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 22s 954ms 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

516ms 1

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

Scenario:
Add a fake base channel for x86_64

1s 745ms 10

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

And I follow "Create Channel" 361ms

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

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

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

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

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

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

And I click on "Create Channel" 663ms

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

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

1s 415ms 10

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

And I follow "Create Channel" 303ms

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

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

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

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

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

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

And I click on "Create Channel" 551ms

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

@sle_minion

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

912ms 10

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

And I follow "Create Channel" 311ms

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

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

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

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

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

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

And I click on "Create Channel" 58ms

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

Scenario:
Add a fake base channel for i586

904ms 10

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

And I follow "Create Channel" 288ms

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

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

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

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

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

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

And I click on "Create Channel" 62ms

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

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

1s 366ms 10

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

And I follow "Create Channel" 288ms

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

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

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

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

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

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

And I click on "Create Channel" 532ms

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

Scenario:
Add a test base channel for x86_64

930ms 10

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

And I follow "Create Channel" 336ms

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

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

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

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

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

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

And I click on "Create Channel" 55ms

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

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

1s 416ms 10

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

And I follow "Create Channel" 333ms

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

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

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

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

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

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

And I click on "Create Channel" 516ms

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

@pxeboot_minion @uyuni @scc_credentials

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

< 1ms 10

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

And I follow "Create Channel" 0s

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

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

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

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

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

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

And I click on "Create Channel" 0s

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

@deblike_minion

Scenario:
Add Debian-like AMD64 base channel

11s 461ms 11

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

And I follow "Create Channel" 308ms

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

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

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

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

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

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

And I uncheck "gpg_check" 10s 80ms

And I click on "Create Channel" 514ms

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

@rhlike_minion

Scenario:
Add a RedHat-like base channel

923ms 10

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

And I follow "Create Channel" 333ms

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

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

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

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

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

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

And I click on "Create Channel" 57ms

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

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 362ms 10

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

And I follow "Create Channel" 329ms

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

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

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

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

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

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

And I click on "Create Channel" 490ms

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

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

478ms 1

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

Scenario:
Create a fake repository for distributions using RPM

760ms 7

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

And I follow "Create Repository" 303ms

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

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

And I click on "Create Repository" 62ms

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

And I should see "metadataSigned" as checked 18ms

Scenario:
Disable metadata check for the fake RPM repository

10s 961ms 6

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

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

And I uncheck "metadataSigned" 10s 87ms

And I click on "Update Repository" 437ms

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

And I should see "metadataSigned" as unchecked 15ms

@rhlike_minion

Scenario:
Create a fake AppStream repository

610ms 7

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

And I follow "Create Repository" 272ms

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

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

And I click on "Create Repository" 56ms

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

And I should see "metadataSigned" as checked 14ms

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

10s 917ms 6

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

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

And I uncheck "metadataSigned" 10s 64ms

And I click on "Update Repository" 421ms

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

And I should see "metadataSigned" as unchecked 16ms

@sle_minion

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

1s 880ms 9

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

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

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

And I click on "Update Channel" 66ms

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

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

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

And I click on "Save Repositories" 527ms

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

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

2s 644ms 9

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

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

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

And I click on "Update Channel" 60ms

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

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

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

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

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

@rhlike_minion

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

2s 101ms 9

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

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

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

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

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

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

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

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

@rhlike_minion

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

2s 206ms 9

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

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

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

And I click on "Update Channel" 59ms

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

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

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

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

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

Scenario:
Create a fake repository for i586

11s 53ms 7

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

And I follow "Create Repository" 282ms

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

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

And I uncheck "metadataSigned" 10s 64ms

And I click on "Create Repository" 430ms

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

Scenario:
Add the repository to the i586 channel

1s 691ms 9

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

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

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

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

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

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

And I click on "Save Repositories" 441ms

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

@sle_minion

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

1s 802ms 6

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

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

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

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

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

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

@deblike_minion

Scenario:
Create a fake repository for Debian-like

1s 58ms 7

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

And I follow "Create Repository" 286ms

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

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

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

And I click on "Create Repository" 433ms

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

@deblike_minion

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

1s 397ms 6

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

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

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

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

And I click on "Save Repositories" 803ms

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

@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 36s 444ms 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

529ms 1

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

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 634ms 10

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

And I follow "Create Channel" 329ms

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

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

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

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

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

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

And I click on "Create Channel" 626ms

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

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

14s 826ms 1 1

When I prepare the development repositories of "sle_minion" as part of "devel-suse-channel" channel 1s 576ms 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'

13s 249ms Show Info +

14:46:31:000 - 14:46:32:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/manage/Edit.do?cid=131

Screenshot +

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 380ms 10

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

And I follow "Create Channel" 319ms

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

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

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

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

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

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

And I click on "Create Channel" 487ms

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

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

4s 161ms 1

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

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

970ms 10

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

And I follow "Create Channel" 328ms

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

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

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

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

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

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

And I click on "Create Channel" 56ms

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

@deblike_minion

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

7s 571ms 1

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

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 125ms 10

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

And I follow "Create Channel" 512ms

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

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

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

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

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

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

And I click on "Create Channel" 56ms

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

@rhlike_minion

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

4s 245ms 1

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

Feature:Synchronize fake channels 46s 924ms 12 2

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

Scenario:
Log in as admin user

1s 335ms 2

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

And I enable source package syncing 922ms

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

3s 760ms 9

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

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

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

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

And I follow "Sync" 388ms

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

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

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

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

@sle_minion

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

4s 603ms 2

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

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

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

3s 679ms 9

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

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

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

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

And I follow "Sync" 298ms

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

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

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

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

Scenario:
Synchronize Test-Child-Channel-x86_64 channel

4s 219ms 9

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

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

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

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

And I follow "Sync" 903ms

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

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

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

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

@sle_minion

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

4s 437ms 9

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

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

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

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

And I follow "Sync" 927ms

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

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

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

@deblike_minion

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

3s 892ms 9

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

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

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

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

And I follow "Sync" 614ms

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

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

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

@rhlike_minion

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

4s 424ms 9

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

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

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

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

And I follow "Sync" 1s 85ms

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

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

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

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 228ms 9

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

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

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

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

And I follow "Sync" 770ms

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

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

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

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

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

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

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

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

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

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

Scenario:
Refresh the channel's repository data

5s 181ms 6

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

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

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

And I click on "Single Run Schedule" 301ms

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

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

Scenario:
Cleanup disable source package syncing

653ms 1

Then I disable source package syncing 653ms

@skip_if_github_validation
Feature:Synchronize development channels 39s 84ms 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 298ms 8 1 1

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

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

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

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

And I follow "Sync" 766ms

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

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

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

14:48:02:000 - 14:48:16: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 434ms 9

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

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

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

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

And I follow "Sync" 1s 71ms

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

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

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

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

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 169ms 9

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

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

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

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

And I follow "Sync" 773ms

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

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

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

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

4s 183ms 9

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

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

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

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

And I follow "Sync" 855ms

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

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

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

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

Feature:Create activation keys 17s 104ms 9

In order to register systems to the server
As the testing user
I want to use activation keys

Scenario:
Log in as admin user

458ms 1

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

@sle_minion

Scenario:
Create an activation key with a channel

1s 978ms 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 441ms

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

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

1s 785ms 2

When I create an activation key with id "RH-LIKE-KEY", description "RedHat like Test Key", base channel "fake-base-channel-rh-like", limit of 20 and contact method "default" 1s 64ms

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

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

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

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

@ssh_minion

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

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

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

@ssh_minion

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

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

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

@proxy

Scenario:
Create an activation key for the proxy

2s 427ms 2

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

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

@build_host

Scenario:
Create an activation key for the build host

3s 506ms 3

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

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

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

@scc_credentials

Scenario:
Create an activation key for the terminal

2s 218ms 2

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

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

Feature:Update activation keys 25s 420ms 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

453ms 1

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 596ms

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

@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

1s 578ms 10

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 56ms

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

@scc_credentials @susemanager

Scenario:
Update SLE SSH tunnel key with synced base product

< 1ms 14

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

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

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

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

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

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

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

And I click on "Update Activation Key" 0s

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

@uyuni

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

3s 403ms 10

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

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

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

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

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 1s 749ms

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

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

And I click on "Update Activation Key" 605ms

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

@scc_credentials @susemanager @proxy @containerized_server @transactional_server

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

< 1ms 11

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

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

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

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

And I click on "Update Activation Key" 0s

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

@scc_credentials @susemanager @proxy @containerized_server @skip_if_transactional_server

Scenario:
Update the SLES proxy key with synced base product

< 1ms 11

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

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

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

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

And I click on "Update Activation Key" 0s

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

@uyuni @proxy @containerized_server @skip_if_cloud

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

< 1ms 8

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

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

And I click on "Update Activation Key" 0s

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

@scc_credentials @build_host

Scenario:
Update build host key with synced base product

3s 157ms 20

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

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

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

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

And I wait for child channels to appear 495ms

And I include the recommended child channels 157ms

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

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

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

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

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

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

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

And I click on "Update Activation Key" 624ms

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

@scc_credentials @uyuni @build_host

Scenario:
Update build host key with Uyuni client tools

2s 617ms 9

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

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

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

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

And I wait for child channels to appear 272ms

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

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

And I click on "Update Activation Key" 984ms

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

@skip_if_github_validation @scc_credentials @uyuni @build_host

Scenario:
Update build host key with dev child channel

2s 645ms 9

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

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

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

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

And I wait for child channels to appear 278ms

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

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

And I click on "Update Activation Key" 624ms

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

@scc_credentials @build_host

Scenario:
Update terminal key with synced base product

3s 369ms 16

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

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

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

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

And I wait for child channels to appear 496ms

And I include the recommended child channels 151ms

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 671ms

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

@susemanager @scc_credentials @build_host

Scenario:
Update terminal key with normal SUSE fake channel

< 1ms 9

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

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

And I wait for child channels to appear 0s

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

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

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

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

And I click on "Update Activation Key" 0s

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

@pxeboot_minion @uyuni @scc_credentials @build_host

Scenario:
Update terminal key with specific fake channel

< 1ms 9

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

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

And I wait for child channels to appear 0s

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

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

And I check "Uyuni Client Tools for SLES15 SP7 x86_64 (Development)" 0s

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

And I click on "Update Activation Key" 0s

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

@skip_if_github_validation @sle_minion

Scenario:
Update SLE key with to include dev child channel

2s 138ms 6

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

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

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

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

And I click on "Update Activation Key" 755ms

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

@skip_if_github_validation @deblike_minion

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

1s 826ms 6

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

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

And I wait for child channels to appear 962ms

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

And I click on "Update Activation Key" 588ms

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

@skip_if_github_validation @rhlike_minion

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

1s 764ms 6

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

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

And I wait for child channels to appear 885ms

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

And I click on "Update Activation Key" 577ms

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

Feature:Create bootstrap repositories 8s 962ms 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 263ms 1

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

@sle_minion

Scenario:
Create the bootstrap repository for SUSE Minion

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

@proxy

Scenario:
Create the bootstrap repository for Proxy

2s 95ms 1

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

@build_host

Scenario:
Create the bootstrap repository for Build Host

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

@transactional_server
Feature:SELinux debugging < 1ms 1

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

Scenario:
No previous operation has created wrong SELinux label

< 1ms 1

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

@new_issue
Feature:Debug the server after the testsuite has run 17s 756ms 5

Scenario:
Call spacewalk-debug on server

14s 27ms 1

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

Scenario:
Check the tomcat logs on server

651ms 1

Then the tomcat logs should not contain errors 651ms

Scenario:
Check salt event log for failures on server

1s 742ms 1

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

Scenario:
Check the taskomatic logs on server

641ms 1

Then the taskomatic logs should not contain errors 641ms

Scenario:
Check for out of memory errors

693ms 1

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

Feature:Debug the clients after the testsuite has run 40s 585ms 1

Scenario:
Extract the logs from all our clients

40s 585ms 1

When I extract the log files from all our active nodes 40s 585ms

@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

116

Failed Scenarios

2

Skipped Scenarios

30

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

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

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

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

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

@deblike_minion Scenario:The Debian-like minion is healthy 5s 948ms 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 659ms 1

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

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

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

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

@scc_credentials Scenario:Refresh SCC 25s 111ms 1

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

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

@containerized_server @proxy @uyuni Scenario:Add Uyuni Proxy product for Tumbleweed, including Uyuni Client Tools 44s 330ms 2

@scc_credentials @uyuni @build_host Scenario:Synchronize SLES 15 SP7 product with recommended sub-products for Retail feature 57m 4s 278ms 20

@proxy @susemanager @transactional_server Scenario:Add SL Micro 6.1 as base OS for proxy < 1ms 13

@proxy @susemanager @skip_if_transactional_server Scenario:Add SLES 15 SP7 as base OS for proxy < 1ms 11

@proxy @susemanager @transactional_server Scenario:Add SUSE MLM Proxy Extension 5.1 with SL Micro 6.1 as base OS < 1ms 13

@proxy @susemanager @skip_if_transactional_server Scenario:Add SUSE MLM Proxy Extension 5.1 with SLES 15 SP7 as base OS < 1ms 12

@proxy @susemanager @transactional_server Scenario:Add SUSE MLM Retail Branch Server Extension 5.1 with SL Micro 6.1 as base OS < 1ms 13

@proxy @susemanager @skip_if_transactional_server Scenario:Add SUSE MLM Retail Branch Server Extension 5.1 with SLES 15 SP7 as base OS < 1ms 12

@scc_credentials @susemanager Scenario:Installer update channels got enabled when products were added < 1ms 2

@scc_credentials @skip_if_github_validation Scenario:Detect product loading issues from the UI 43s 237ms 7

@scc_credentials @skip_if_github_validation Scenario:Report the synchronization duration for SLES 15 SP7 < 1ms 1

@sle_minion Scenario:Add a SUSE fake child channel to the SUSE Product base channel 912ms 10

@pxeboot_minion @uyuni @scc_credentials Scenario:Add a fake terminal child channel to the SUSE Product base channel < 1ms 10

@deblike_minion Scenario:Add Debian-like AMD64 base channel 11s 461ms 11

@rhlike_minion Scenario:Add a RedHat-like base channel 923ms 10

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

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

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

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

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

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

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

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

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

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

@sle_minion Scenario:Create custom repositories inside the SUSE custom channel 14s 826ms 1 1

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

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

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

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

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

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

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

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

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

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

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

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

@rhlike_minion Scenario:Synchronize Fake-Base-Channel-AppStream channel 4s 228ms 9

@pxeboot_minion @uyuni @scc_credentials Scenario:Synchronize the repository in the terminal channel < 1ms 9

@pxeboot_minion @uyuni @scc_credentials Scenario:Verify state of Fake-RPM-Terminal-Channel custom channel < 1ms 2

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

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

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

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

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

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

@proxy

Scenario:
The proxy is healthy

4s 501ms 4

@sle_minion

Scenario:
The minion is healthy

6s 368ms 4

@build_host

Scenario:
The build host is healthy

3s 927ms 4

@ssh_minion

Scenario:
The SSH minion is healthy

6s 240ms 4

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 168ms 4

@deblike_minion

Scenario:
The Debian-like minion is healthy

5s 948ms 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

659ms 1

@no_auth_registry

Scenario:
The registry without authentication is healthy

666ms 1

@custom_download_endpoint

Scenario:
The custom download endpoint is working

635ms 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 873ms 7

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

@proxy @susemanager

Scenario:
List all products for SUSE Multi-Linux Manager

< 1ms 6

@scc_credentials

Scenario:
Refresh SCC

25s 111ms 1

@scc_credentials

Scenario:
Let the products page appear

2s 138ms 6

@scc_credentials

Scenario:
Use the products and architecture filters

2s 559ms 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 498ms 4

@containerized_server @proxy @uyuni

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

44s 330ms 2

@scc_credentials @uyuni @build_host

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

57m 4s 278ms 20

@proxy @susemanager @transactional_server

Scenario:
Add SL Micro 6.1 as base OS for proxy

< 1ms 13

@proxy @susemanager @skip_if_transactional_server

Scenario:
Add SLES 15 SP7 as base OS for proxy

< 1ms 11

@proxy @susemanager @transactional_server

Scenario:
Add SUSE MLM Proxy Extension 5.1 with SL Micro 6.1 as base OS

< 1ms 13

@proxy @susemanager @skip_if_transactional_server

Scenario:
Add SUSE MLM Proxy Extension 5.1 with SLES 15 SP7 as base OS

< 1ms 12

@proxy @susemanager @transactional_server

Scenario:
Add SUSE MLM Retail Branch Server Extension 5.1 with SL Micro 6.1 as base OS

< 1ms 13

@proxy @susemanager @skip_if_transactional_server

Scenario:
Add SUSE MLM Retail Branch Server Extension 5.1 with SLES 15 SP7 as base OS

< 1ms 12

@scc_credentials @susemanager

Scenario:
Installer update channels got enabled when products were added

< 1ms 2

@scc_credentials @skip_if_github_validation

Scenario:
Detect product loading issues from the UI

43s 237ms 7

@scc_credentials @skip_if_github_validation

Scenario:
Report the synchronization duration for SLES 15 SP7

< 1ms 1

@sle_minion

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

912ms 10

@pxeboot_minion @uyuni @scc_credentials

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

< 1ms 10

@deblike_minion

Scenario:
Add Debian-like AMD64 base channel

11s 461ms 11

@rhlike_minion

Scenario:
Add a RedHat-like base channel

923ms 10

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 362ms 10

@rhlike_minion

Scenario:
Create a fake AppStream repository

610ms 7

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

10s 917ms 6

@sle_minion

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

1s 880ms 9

@rhlike_minion

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

2s 101ms 9

@rhlike_minion

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

2s 206ms 9

@sle_minion

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

1s 802ms 6

@deblike_minion

Scenario:
Create a fake repository for Debian-like

1s 58ms 7

@deblike_minion

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

1s 397ms 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 36s 444ms 8 1

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 634ms 10

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

14s 826ms 1 1

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 380ms 10

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

4s 161ms 1

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

970ms 10

@deblike_minion

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

7s 571ms 1

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 125ms 10

@rhlike_minion

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

4s 245ms 1

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

3s 760ms 9

@sle_minion

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

4s 603ms 2

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

3s 679ms 9

@sle_minion

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

4s 437ms 9

@deblike_minion

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

3s 892ms 9

@rhlike_minion

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

4s 424ms 9

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 228ms 9

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Synchronize the repository in the terminal channel

< 1ms 9

@pxeboot_minion @uyuni @scc_credentials

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

< 1ms 2

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

@sle_minion

Scenario:
Synchronize Devel-SUSE-Channel channel

26s 298ms 8 1 1

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

4s 434ms 9

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 169ms 9

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

4s 183ms 9

@sle_minion

Scenario:
Create an activation key with a channel

1s 978ms 2

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

1s 785ms 2

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

1s 514ms 2

@ssh_minion

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

1s 547ms 2

@ssh_minion

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

1s 666ms 2

@proxy

Scenario:
Create an activation key for the proxy

2s 427ms 2

@build_host

Scenario:
Create an activation key for the build host

3s 506ms 3