Cucumber Feature Report

All Scenarios

148

Passed Scenarios

114

Failed Scenarios

4

Skipped Scenarios

30

Execution Time: 75m 24s 71ms

Expand All | Collapse All

Metadata

App Version: Uyuni/Head

Browser: Chrome

Platform: x86_64

Parallel: Disabled

Feature:Sanity checks 46s 527ms 10 2

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

Scenario:
The server is healthy

12s 116ms 19

Then "server" should have a FQDN 385ms

And reverse resolution should work for "server" 636ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@proxy

Scenario:
The proxy is healthy

4s 470ms 4

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

And reverse resolution should work for "proxy" 281ms

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

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

@sle_minion

Scenario:
The minion is healthy

6s 276ms 4

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

And reverse resolution should work for "sle_minion" 410ms

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

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

@build_host

Scenario:
The build host is healthy

3s 637ms 4

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

And reverse resolution should work for "build_host" 208ms

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

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

@ssh_minion

Scenario:
The SSH minion is healthy

8s 899ms 4

Then "ssh_minion" should have a FQDN 6s 634ms

And reverse resolution should work for "ssh_minion" 481ms

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

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

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 239ms 4

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

And reverse resolution should work for "rhlike_minion" 196ms

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

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

@deblike_minion

Scenario:
The Debian-like minion is healthy

5s 903ms 4

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

And reverse resolution should work for "deblike_minion" 214ms

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

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

@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

663ms 1

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

@no_auth_registry

Scenario:
The registry without authentication is healthy

663ms 1

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

@custom_download_endpoint

Scenario:
The custom download endpoint is working

657ms 1

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

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

662ms 1

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

@skip_if_containerized_server

Scenario:
Create admin user and first organization

< 1ms 12

Given I access the host the first time 0s

When I go to the home page 0s

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

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

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

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

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

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

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

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

And I click on "Create Organization" 0s

Then I am logged in 0s

Scenario:
Log in as admin user

40s 173ms 1

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

Scenario:
Wait for refresh of list of products to finish

3s 490ms 1

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

Scenario:
Create testing username

2s 296ms 12

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

And I follow "Create User" 664ms

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

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

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

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

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

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

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

And I click on "Create Login" 957ms

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

And I should see a "testing" link 13ms

Scenario:
Grant testing user administrative priviledges

1s 804ms 10

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

And I follow "testing" 539ms

And I check "role_org_admin" 87ms

And I check "role_system_group_admin" 78ms

And I check "role_channel_admin" 83ms

And I check "role_activation_key_admin" 85ms

And I check "role_config_admin" 82ms

And I click on "Update" 628ms

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

And I should see a "testing" text 66ms

@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

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

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

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

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 44ms 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 396ms 5

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

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

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

And I click on "Save Preferences" 542ms

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

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

3s 648ms 5

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

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

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

And I click on "Save Preferences" 648ms

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

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

Scenario:
Create a Kiwi user with image administrators rights

4s 69ms 2

New user kiwikiwi created with roles: image_admin

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

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

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

Scenario:
Create a Docker user with image administrators rights

2s 234ms 2

New user docker created with roles: image_admin

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

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

@no_auth_registry

Scenario:
Create an image store without credentials

2s 991ms 7

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

And I follow "Create" 520ms

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

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

And I click on "create-btn" 63ms

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

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

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

Scenario:
Log in as admin user

26s 732ms 1

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

Scenario:
Disable scheduled reposyncs

4s 496ms 5

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

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

And I choose "disabled" 63ms

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

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

Scenario:
Disable scheduled Cobbler syncs

4s 457ms 5

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

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

And I choose "disabled" 48ms

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

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

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

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

Scenario:
List available channels

32s 360ms 5

When I refresh SCC 29s 986ms

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

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

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

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

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

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

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

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

When I remove the mgr-sync cache file 655ms

And I execute mgr-sync refresh 1m 814ms

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

Feature:Synchronize products in the products page of the Setup Wizard 56m 3s 599ms 6 2 9

@scc_credentials

Scenario:
Refresh SCC

27s 262ms 1

When I refresh SCC 27s 262ms

@scc_credentials

Scenario:
Let the products page appear

2s 380ms 6

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

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

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

Then I should see a "Arch" text 104ms

And I should see a "Channels" text 104ms

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

@scc_credentials

Scenario:
Use the products and architecture filters

2s 434ms 7

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

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

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

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

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

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

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

@scc_credentials @susemanager

Scenario:
View the channels list in the products page

< 1ms 9

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

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

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

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

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

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

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

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

When I close the modal dialog 0s

@scc_credentials @susemanager

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

< 1ms 30

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

Then the SLE15 SP7 product should be added 0s

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

@uyuni

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

2m 11s 44ms 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 473ms

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

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

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

@containerized_server @proxy @uyuni

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

1m 5s 614ms 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" 21s 664ms

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

@scc_credentials @uyuni @build_host

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

51m 38s 220ms 20 1

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 58ms

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

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

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

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

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

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

17s 261ms Show Info +

11:50:10:000 - 12:41:33:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/admin/setup/products

Screenshot +

@proxy @susemanager @transactional_server

Scenario:
Add SL Micro 6.1 as base OS for proxy

< 1ms 13

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

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

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

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

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

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

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

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

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

And I click the Add Product button 0s

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

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

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

@proxy @susemanager @skip_if_transactional_server

Scenario:
Add SLES 15 SP7 as base OS for proxy

< 1ms 11

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

@proxy @susemanager @transactional_server

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

< 1ms 13

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

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

@proxy @susemanager @skip_if_transactional_server

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

< 1ms 12

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

@proxy @susemanager @transactional_server

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

< 1ms 13

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

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

@proxy @susemanager @skip_if_transactional_server

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

< 1ms 12

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

@scc_credentials @susemanager

Scenario:
Installer update channels got enabled when products were added

< 1ms 2

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

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

@scc_credentials @skip_if_github_validation

Scenario:
Detect product loading issues from the UI

36s 642ms 7 1

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

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

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

And I wait until I do not see "Loading" text 3s 342ms

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

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

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

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

15s 854ms Show Info +

12:41:50:000 - 12:42:12:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/admin/setup/products

Screenshot +

@scc_credentials @skip_if_github_validation

Scenario:
Report the synchronization duration for SLES 15 SP7

< 1ms 1

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

Feature:Create fake channels 26s 696ms 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

957ms 1

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

Scenario:
Add a fake base channel for x86_64

2s 132ms 10

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

And I follow "Create Channel" 506ms

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

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

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

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

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

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

And I click on "Create Channel" 920ms

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

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

1s 131ms 10

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

And I follow "Create Channel" 495ms

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

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

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

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

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

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

And I click on "Create Channel" 58ms

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

@sle_minion

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

1s 306ms 10

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

And I follow "Create Channel" 687ms

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

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

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

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

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

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

And I click on "Create Channel" 60ms

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

Scenario:
Add a fake base channel for i586

1s 987ms 10

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

And I follow "Create Channel" 611ms

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

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

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

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

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

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

And I click on "Create Channel" 806ms

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

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

1s 895ms 10

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

And I follow "Create Channel" 405ms

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

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

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

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

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

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

And I click on "Create Channel" 912ms

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

Scenario:
Add a test base channel for x86_64

1s 705ms 10

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

And I follow "Create Channel" 470ms

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

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

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

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

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

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

And I click on "Create Channel" 680ms

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

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

1s 140ms 10

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

And I follow "Create Channel" 499ms

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

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

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

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

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

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

And I click on "Create Channel" 55ms

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

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

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

And I follow "Create Channel" 479ms

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

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

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

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

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

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

And I uncheck "gpg_check" 10s 75ms

And I click on "Create Channel" 683ms

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

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 559ms 10

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

And I follow "Create Channel" 335ms

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

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

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

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

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

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

And I click on "Create Channel" 659ms

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

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 60ms 10

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

And I follow "Create Channel" 430ms

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

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

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

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

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

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

And I click on "Create Channel" 58ms

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

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

656ms 1

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

Scenario:
Create a fake repository for distributions using RPM

1s 568ms 7

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

And I follow "Create Repository" 575ms

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

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

And I click on "Create Repository" 592ms

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

And I should see "metadataSigned" as checked 20ms

Scenario:
Disable metadata check for the fake RPM repository

11s 70ms 6

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

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

And I uncheck "metadataSigned" 10s 74ms

And I click on "Update Repository" 478ms

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

And I should see "metadataSigned" as unchecked 17ms

@rhlike_minion

Scenario:
Create a fake AppStream repository

1s 132ms 7

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

And I follow "Create Repository" 361ms

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

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

And I click on "Create Repository" 467ms

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

And I should see "metadataSigned" as checked 16ms

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

11s 23ms 6

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

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

And I uncheck "metadataSigned" 10s 64ms

And I click on "Update Repository" 502ms

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

And I should see "metadataSigned" as unchecked 15ms

@sle_minion

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

2s 303ms 9

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

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

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

And I click on "Update Channel" 665ms

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

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

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

And I click on "Save Repositories" 688ms

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

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

2s 586ms 9

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

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

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

And I click on "Update Channel" 613ms

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

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

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

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

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

@rhlike_minion

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

2s 694ms 9

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

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

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

And I click on "Update Channel" 571ms

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

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

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

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

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

@rhlike_minion

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

2s 186ms 9

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

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

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

And I click on "Update Channel" 57ms

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

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

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

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

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

Scenario:
Create a fake repository for i586

11s 163ms 7

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

And I follow "Create Repository" 288ms

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

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

And I uncheck "metadataSigned" 10s 86ms

And I click on "Create Repository" 497ms

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

Scenario:
Add the repository to the i586 channel

2s 99ms 9

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

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

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

And I click on "Update Channel" 640ms

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

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

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

And I click on "Save Repositories" 598ms

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

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

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

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

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

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

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

@deblike_minion

Scenario:
Create a fake repository for Debian-like

703ms 7

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

And I follow "Create Repository" 293ms

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

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

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

And I click on "Create Repository" 55ms

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

@deblike_minion

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

1s 269ms 6

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

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

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

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

And I click on "Save Repositories" 632ms

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 38s 86ms 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

564ms 1

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

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 85ms 10

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

And I follow "Create Channel" 333ms

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

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

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

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

And I click on "Create Channel" 66ms

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

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

15s 185ms 1 1

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

12:44:07:000 - 12:44:09: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 458ms 10

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

And I follow "Create Channel" 326ms

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

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

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

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

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

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

And I click on "Create Channel" 530ms

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

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

4s 374ms 1

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

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

1s 540ms 10

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

And I follow "Create Channel" 333ms

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

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

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

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

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

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

And I click on "Create Channel" 595ms

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

@deblike_minion

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

7s 549ms 1

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

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 528ms 10

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

And I follow "Create Channel" 350ms

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

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

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

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

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

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

And I click on "Create Channel" 580ms

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

@rhlike_minion

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

4s 798ms 1

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

Feature:Synchronize fake channels 10m 42s 845ms 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 941ms 2

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

And I enable source package syncing 1s 466ms

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

3s 954ms 9

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

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

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

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

And I follow "Sync" 469ms

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

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

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

@sle_minion

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

7m 11s 714ms 2

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

And solver file for "fake-rpm-suse-channel" should reference "orion-dummy-1.1-1.1.x86_64.rpm" 7m 6s 587ms

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

4s 559ms 9

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

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

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

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

And I follow "Sync" 638ms

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

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

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

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

Scenario:
Synchronize Test-Child-Channel-x86_64 channel

4s 567ms 9

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

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

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

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

And I follow "Sync" 552ms

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

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

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

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

@sle_minion

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

2m 50s 363ms 9

1 minutes out of 4 waiting for 'fake-child-channel-suse-like' channel to be synchronized
2 minutes out of 4 waiting for 'fake-child-channel-suse-like' channel to be synchronized

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

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

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

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

And I follow "Sync" 765ms

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

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

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

And I wait until the channel "fake-child-channel-suse-like" has been synced 2m 46s 299ms

@deblike_minion

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

3s 863ms 9

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

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

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

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

And I follow "Sync" 399ms

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

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

@rhlike_minion

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

4s 35ms 9

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

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

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

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

And I follow "Sync" 631ms

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

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

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

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

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 31ms 9

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

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

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

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

And I follow "Sync" 490ms

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

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

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

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

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

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

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

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

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

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

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

Scenario:
Refresh the channel's repository data

6s 175ms 6

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

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

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

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

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

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

Scenario:
Cleanup disable source package syncing

1s 13ms 1

Then I disable source package syncing 1s 13ms

@skip_if_github_validation
Feature:Synchronize development channels 38s 305ms 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 235ms 8 1 1

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

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

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

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

And I follow "Sync" 317ms

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

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

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

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

Screenshot +

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

3s 839ms 9

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

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

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

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

And I follow "Sync" 393ms

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

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

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

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

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 27ms 9

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

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

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

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

And I follow "Sync" 690ms

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

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

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

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

4s 203ms 9

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

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

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

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

And I follow "Sync" 850ms

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

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

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

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

Feature:Create activation keys 17s 540ms 9

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

Scenario:
Log in as admin user

473ms 1

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

@sle_minion

Scenario:
Create an activation key with a channel

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

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

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

1s 796ms 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 154ms

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

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

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

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

@ssh_minion

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

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

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

@ssh_minion

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

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

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

@proxy

Scenario:
Create an activation key for the proxy

2s 475ms 2

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

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

@build_host

Scenario:
Create an activation key for the build host

3s 372ms 3

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

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

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

@scc_credentials

Scenario:
Create an activation key for the terminal

2s 345ms 2

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

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

Feature:Update activation keys 24s 545ms 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

491ms 1

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 803ms

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

@scc_credentials @susemanager

Scenario:
Update SLE SSH key with synced base product

< 1ms 14

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

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

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

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

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

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

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

And I click on "Update Activation Key" 0s

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

@uyuni

Scenario:
Update openSUSE Tumbleweed SSH key with synced base product

2s 368ms 10

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 740ms

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

@scc_credentials @susemanager

Scenario:
Update SLE SSH tunnel key with synced base product

< 1ms 14

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

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

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

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

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

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

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

And I click on "Update Activation Key" 0s

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

@uyuni

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

2s 498ms 10

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 611ms

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

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

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

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

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

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

And I wait for child channels to appear 488ms

And I include the recommended child channels 156ms

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

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

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

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

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

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

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

And I wait until "SLE-Module-Systems-Management-15-SP7-Updates for x86_64" has been checked 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 18ms

And I click on "Update Activation Key" 595ms

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

@scc_credentials @uyuni @build_host

Scenario:
Update build host key with Uyuni client tools

2s 174ms 9

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

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

And I wait for child channels to appear 919ms

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

And I wait for child channels to appear 273ms

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

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

And I click on "Update Activation Key" 636ms

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

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

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

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

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

And I wait for child channels to appear 281ms

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

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

And I click on "Update Activation Key" 783ms

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

@scc_credentials @build_host

Scenario:
Update terminal key with synced base product

3s 472ms 16

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

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

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

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

And I wait for child channels to appear 488ms

And I include the recommended child channels 157ms

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

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

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

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

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

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

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

And I click on "Update Activation Key" 775ms

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

@susemanager @scc_credentials @build_host

Scenario:
Update terminal key with normal SUSE fake channel

< 1ms 9

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

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

And I wait for child channels to appear 0s

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

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

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

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

And I click on "Update Activation Key" 0s

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

@pxeboot_minion @uyuni @scc_credentials @build_host

Scenario:
Update terminal key with specific fake channel

< 1ms 9

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

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

And I wait for child channels to appear 0s

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

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

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

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

And I click on "Update Activation Key" 0s

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

@skip_if_github_validation @sle_minion

Scenario:
Update SLE key with to include dev child channel

1s 714ms 6

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

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

And I wait for child channels to appear 816ms

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

And I click on "Update Activation Key" 585ms

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

@skip_if_github_validation @deblike_minion

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

1s 783ms 6

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

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

And I wait for child channels to appear 890ms

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

And I click on "Update Activation Key" 591ms

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

@skip_if_github_validation @rhlike_minion

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

1s 714ms 6

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

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

And I wait for child channels to appear 816ms

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

And I click on "Update Activation Key" 592ms

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

Feature:Create bootstrap repositories 10s 2ms 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 280ms 1

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

@sle_minion

Scenario:
Create the bootstrap repository for SUSE Minion

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

@proxy

Scenario:
Create the bootstrap repository for Proxy

2s 140ms 1

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

@build_host

Scenario:
Create the bootstrap repository for Build Host

3s 379ms 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 3s 379ms

@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 19s 386ms 5

Scenario:
Call spacewalk-debug on server

15s 384ms 1

When I execute spacewalk-debug on the server 15s 384ms

Scenario:
Check the tomcat logs on server

719ms 1

Then the tomcat logs should not contain errors 719ms

Scenario:
Check salt event log for failures on server

1s 917ms 1

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

Scenario:
Check the taskomatic logs on server

697ms 1

Then the taskomatic logs should not contain errors 697ms

Scenario:
Check for out of memory errors

666ms 1

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

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

Scenario:
Extract the logs from all our clients

42s 596ms 1

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

@srv_scc_access_logging
Feature:Test for excessive SCC accesses < 1ms 2

Scenario:
Count UI SCC accesses in rhn_web_ui.log

< 1ms 1

Then the word "scc.suse.com" does not occur more than 100 times in "/var/log/rhn/rhn_web_ui.log" on "server" 0s

Scenario:
Count Taskomatic SCC accesses in rhn_taskomatic_daemon.log

< 1ms 1

Then the word "scc.suse.com" does not occur more than 50 times in "/var/log/rhn/rhn_taskomatic_daemon.log" on "server" 0s

All Scenarios

148

Passed Scenarios

114

Failed Scenarios

4

Skipped Scenarios

30

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

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

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

@ssh_minion Scenario:The SSH minion is healthy 8s 899ms 4

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

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

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

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

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

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

@scc_credentials Scenario:Refresh SCC 27s 262ms 1

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

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

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

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

@uyuni Scenario:Partially add openSUSE Tumbleweed product, only including the required packages to generate the bootstrap repository 2m 11s 44ms 4

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

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

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

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

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

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

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

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

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

@scc_credentials @skip_if_github_validation Scenario:Detect product loading issues from the UI 36s 642ms 7 1

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

@sle_minion Scenario:Add a SUSE fake child channel to the SUSE Product base channel 1s 306ms 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 820ms 11

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

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

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

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

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

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

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

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

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

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

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

@sle_minion Scenario:Create custom repositories inside the SUSE custom channel 15s 185ms 1 1

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

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

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

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

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

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

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

@sle_minion Scenario:Verify state of Fake-RPM-SUSE-Channel channel 7m 11s 714ms 2

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

@sle_minion Scenario:Synchronize Fake-Child-Channel-SUSE-like channel 2m 50s 363ms 9

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

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

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

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

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

@skip_if_github_validation Feature:Synchronize development channels 38s 305ms 3 1

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

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

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

@proxy

Scenario:
The proxy is healthy

4s 470ms 4

@sle_minion

Scenario:
The minion is healthy

6s 276ms 4

@build_host

Scenario:
The build host is healthy

3s 637ms 4

@ssh_minion

Scenario:
The SSH minion is healthy

8s 899ms 4

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 239ms 4

@deblike_minion

Scenario:
The Debian-like minion is healthy

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

663ms 1

@no_auth_registry

Scenario:
The registry without authentication is healthy

663ms 1

@custom_download_endpoint

Scenario:
The custom download endpoint is working

657ms 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 991ms 7

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

@proxy @susemanager

Scenario:
List all products for SUSE Multi-Linux Manager

< 1ms 6

@scc_credentials

Scenario:
Refresh SCC

27s 262ms 1

@scc_credentials

Scenario:
Let the products page appear

2s 380ms 6

@scc_credentials

Scenario:
Use the products and architecture filters

2s 434ms 7

@scc_credentials @susemanager

Scenario:
View the channels list in the products page

< 1ms 9

@scc_credentials @susemanager

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

< 1ms 30

@uyuni

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

2m 11s 44ms 4

@containerized_server @proxy @uyuni

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

1m 5s 614ms 2

@scc_credentials @uyuni @build_host

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

51m 38s 220ms 20 1

@proxy @susemanager @transactional_server

Scenario:
Add SL Micro 6.1 as base OS for proxy

< 1ms 13

@proxy @susemanager @skip_if_transactional_server

Scenario:
Add SLES 15 SP7 as base OS for proxy

< 1ms 11

@proxy @susemanager @transactional_server

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

< 1ms 13

@proxy @susemanager @skip_if_transactional_server

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

< 1ms 12

@proxy @susemanager @transactional_server

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

< 1ms 13

@proxy @susemanager @skip_if_transactional_server

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

< 1ms 12

@scc_credentials @susemanager

Scenario:
Installer update channels got enabled when products were added

< 1ms 2

@scc_credentials @skip_if_github_validation

Scenario:
Detect product loading issues from the UI

36s 642ms 7 1

@scc_credentials @skip_if_github_validation

Scenario:
Report the synchronization duration for SLES 15 SP7

< 1ms 1

@sle_minion

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

1s 306ms 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 820ms 11

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 559ms 10

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 60ms 10

@rhlike_minion

Scenario:
Create a fake AppStream repository

1s 132ms 7

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

11s 23ms 6

@sle_minion

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

2s 303ms 9

@rhlike_minion

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

2s 694ms 9

@rhlike_minion

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

2s 186ms 9

@sle_minion

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

1s 800ms 6

@deblike_minion

Scenario:
Create a fake repository for Debian-like

703ms 7

@deblike_minion

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

1s 269ms 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 38s 86ms 8 1

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 85ms 10

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

15s 185ms 1 1

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 458ms 10

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

4s 374ms 1

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

1s 540ms 10

@deblike_minion

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

7s 549ms 1

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 528ms 10

@rhlike_minion

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

4s 798ms 1

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

3s 954ms 9

@sle_minion

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

7m 11s 714ms 2

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

4s 559ms 9

@sle_minion

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

2m 50s 363ms 9

@deblike_minion

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

3s 863ms 9

@rhlike_minion

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

4s 35ms 9

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 31ms 9

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Synchronize the repository in the terminal channel

< 1ms 9

@pxeboot_minion @uyuni @scc_credentials

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

< 1ms 2

@skip_if_github_validation
Feature:Synchronize development channels 38s 305ms 3 1

@sle_minion

Scenario:
Synchronize Devel-SUSE-Channel channel

26s 235ms 8 1 1

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

3s 839ms 9

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 27ms 9