Cucumber Feature Report

All Scenarios

148

Passed Scenarios

116

Failed Scenarios

2

Skipped Scenarios

30

Execution Time: 56m 6s 34ms

Expand All | Collapse All

Metadata

App Version: Uyuni/Head

Browser: Chrome

Platform: x86_64

Parallel: Disabled

Feature:Sanity checks 45s 222ms 10 2

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

Scenario:
The server is healthy

12s 45ms 19

Then "server" should have a FQDN 389ms

And reverse resolution should work for "server" 634ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@proxy

Scenario:
The proxy is healthy

4s 407ms 4

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

And reverse resolution should work for "proxy" 277ms

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

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

@sle_minion

Scenario:
The minion is healthy

6s 460ms 4

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

And reverse resolution should work for "sle_minion" 415ms

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

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

@build_host

Scenario:
The build host is healthy

3s 842ms 4

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

And reverse resolution should work for "build_host" 223ms

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

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

@ssh_minion

Scenario:
The SSH minion is healthy

6s 398ms 4

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

And reverse resolution should work for "ssh_minion" 415ms

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

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

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 736ms 4

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

And reverse resolution should work for "rhlike_minion" 196ms

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

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

@deblike_minion

Scenario:
The Debian-like minion is healthy

6s 330ms 4

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

And reverse resolution should work for "deblike_minion" 229ms

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

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

@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

678ms 1

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

@no_auth_registry

Scenario:
The registry without authentication is healthy

672ms 1

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

@custom_download_endpoint

Scenario:
The custom download endpoint is working

650ms 1

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

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

657ms 1

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

@skip_if_containerized_server

Scenario:
Create admin user and first organization

< 1ms 12

Given I access the host the first time 0s

When I go to the home page 0s

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

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

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

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

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

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

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

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

And I click on "Create Organization" 0s

Then I am logged in 0s

Scenario:
Log in as admin user

39s 974ms 1

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

Scenario:
Wait for refresh of list of products to finish

3s 932ms 1

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

Scenario:
Create testing username

2s 269ms 12

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

And I follow "Create User" 656ms

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

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

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

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

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

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

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

And I click on "Create Login" 961ms

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

And I should see a "testing" link 12ms

Scenario:
Grant testing user administrative priviledges

1s 916ms 10

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

And I follow "testing" 610ms

And I check "role_org_admin" 80ms

And I check "role_system_group_admin" 76ms

And I check "role_channel_admin" 77ms

And I check "role_activation_key_admin" 76ms

And I check "role_config_admin" 77ms

And I click on "Update" 703ms

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

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

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

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

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

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

@scc_credentials @no_mirror

Scenario:
Enter valid SCC credentials

< 1ms 6

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

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

And I ask to add new credentials 0s

And I enter the SCC credentials 0s

And I click on "Save" 0s

And I wait until the SCC credentials are valid 0s

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

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

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

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

And I click on "Save Preferences" 707ms

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

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

3s 553ms 5

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

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

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

And I click on "Save Preferences" 56ms

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

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

Scenario:
Create a Kiwi user with image administrators rights

4s 381ms 2

New user kiwikiwi created with roles: image_admin

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

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

Feature:Prepare server for using Docker 6s 161ms 2

Scenario:
Create a Docker user with image administrators rights

2s 229ms 2

New user docker created with roles: image_admin

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

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

@no_auth_registry

Scenario:
Create an image store without credentials

3s 932ms 7

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

And I follow "Create" 625ms

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

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

And I click on "create-btn" 339ms

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

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

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

Scenario:
Log in as admin user

26s 759ms 1

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

Scenario:
Disable scheduled reposyncs

4s 687ms 5

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

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

And I choose "disabled" 56ms

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

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

Scenario:
Disable scheduled Cobbler syncs

4s 486ms 5

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

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

And I choose "disabled" 46ms

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

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

@scc_credentials
Feature:List available channels and enable them 1m 39s 793ms 5 1

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

Scenario:
List available channels

33s 695ms 5

When I refresh SCC 31s 394ms

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

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

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

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

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

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

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

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

When I remove the mgr-sync cache file 687ms

And I execute mgr-sync refresh 1m 836ms

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

Feature:Synchronize products in the products page of the Setup Wizard 46m 22s 270ms 8 9

@scc_credentials

Scenario:
Refresh SCC

26s 866ms 1

When I refresh SCC 26s 866ms

@scc_credentials

Scenario:
Let the products page appear

2s 156ms 6

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

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

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

Then I should see a "Arch" text 106ms

And I should see a "Channels" text 106ms

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

@scc_credentials

Scenario:
Use the products and architecture filters

2s 472ms 7

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

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

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

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

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

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

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

@scc_credentials @susemanager

Scenario:
View the channels list in the products page

< 1ms 9

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

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

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

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

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

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

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

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

When I close the modal dialog 0s

@scc_credentials @susemanager

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

< 1ms 30

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

Then the SLE15 SP7 product should be added 0s

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

@uyuni

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

2m 10s 894ms 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 324ms

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

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

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

@containerized_server @proxy @uyuni

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

1m 36s 988ms 2

Channel opensuse_tumbleweed-x86_64 added
Channel opensuse_tumbleweed-uyuni-client-devel-x86_64 added
Channel uyuni-proxy-devel-tumbleweed-x86_64 added
Channel opensuse_tumbleweed-uyuni-client-devel-x86_64 finished reposync
Channel opensuse_tumbleweed-x86_64 finished reposync
1 minutes out of 229 waiting for 'uyuni-proxy' channels to finish 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 650ms

And I wait until all synchronized channels for "uyuni-proxy" have finished 1m 15s 338ms

@scc_credentials @uyuni @build_host

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

41m 19s 578ms 20

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 53ms

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

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

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

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

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

@proxy @susemanager @transactional_server

Scenario:
Add SL Micro 6.1 as base OS for proxy

< 1ms 13

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

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

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

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

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

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

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

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

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

And I click the Add Product button 0s

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

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

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

@proxy @susemanager @skip_if_transactional_server

Scenario:
Add SLES 15 SP7 as base OS for proxy

< 1ms 11

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

@proxy @susemanager @transactional_server

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

< 1ms 13

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

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

@proxy @susemanager @skip_if_transactional_server

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

< 1ms 12

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

@proxy @susemanager @transactional_server

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

< 1ms 13

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

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

@proxy @susemanager @skip_if_transactional_server

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

< 1ms 12

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

@scc_credentials @susemanager

Scenario:
Installer update channels got enabled when products were added

< 1ms 2

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

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

@scc_credentials @skip_if_github_validation

Scenario:
Detect product loading issues from the UI

43s 313ms 7

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

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

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

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

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

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

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

@scc_credentials @skip_if_github_validation

Scenario:
Report the synchronization duration for SLES 15 SP7

< 1ms 1

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

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

490ms 1

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

Scenario:
Add a fake base channel for x86_64

1s 651ms 10

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

And I follow "Create Channel" 378ms

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

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

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

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

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

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

And I click on "Create Channel" 574ms

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

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

1s 529ms 10

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

And I follow "Create Channel" 363ms

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

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

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

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

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

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

And I click on "Create Channel" 609ms

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

@sle_minion

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

1s 394ms 10

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

And I follow "Create Channel" 283ms

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

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

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

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

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

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

And I click on "Create Channel" 580ms

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

Scenario:
Add a fake base channel for i586

1s 396ms 10

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

And I follow "Create Channel" 265ms

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

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

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

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

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

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

And I click on "Create Channel" 55ms

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

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

1s 417ms 10

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

And I follow "Create Channel" 315ms

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

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

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

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

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

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

And I click on "Create Channel" 57ms

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

Scenario:
Add a test base channel for x86_64

1s 391ms 10

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

And I follow "Create Channel" 325ms

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

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

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

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

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

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

And I click on "Create Channel" 543ms

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

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

1s 465ms 10

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

And I follow "Create Channel" 309ms

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

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

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

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

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

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

And I click on "Create Channel" 594ms

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

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

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

And I follow "Create Channel" 306ms

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

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

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

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

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

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

And I uncheck "gpg_check" 10s 81ms

And I click on "Create Channel" 538ms

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

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 383ms 10

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

And I follow "Create Channel" 315ms

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

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

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

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

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

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

And I click on "Create Channel" 538ms

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

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 360ms 10

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

And I follow "Create Channel" 311ms

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

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

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

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

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

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

And I click on "Create Channel" 518ms

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

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

528ms 1

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

Scenario:
Create a fake repository for distributions using RPM

1s 158ms 7

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

And I follow "Create Repository" 286ms

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

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

And I click on "Create Repository" 480ms

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

And I should see "metadataSigned" as checked 19ms

Scenario:
Disable metadata check for the fake RPM repository

10s 944ms 6

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

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

And I uncheck "metadataSigned" 10s 59ms

And I click on "Update Repository" 458ms

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

And I should see "metadataSigned" as unchecked 15ms

@rhlike_minion

Scenario:
Create a fake AppStream repository

988ms 7

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

And I follow "Create Repository" 280ms

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

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

And I click on "Create Repository" 428ms

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

And I should see "metadataSigned" as checked 15ms

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

10s 937ms 6

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

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

And I uncheck "metadataSigned" 10s 76ms

And I click on "Update Repository" 427ms

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

And I should see "metadataSigned" as unchecked 15ms

@sle_minion

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

1s 848ms 9

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

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

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

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

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

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

And I click on "Save Repositories" 516ms

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

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

2s 636ms 9

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

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

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

And I click on "Update Channel" 562ms

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

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

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

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

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

@rhlike_minion

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

2s 215ms 9

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

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

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

And I click on "Update Channel" 56ms

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

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

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

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

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

@rhlike_minion

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

2s 213ms 9

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

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

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

And I click on "Update Channel" 55ms

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

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

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

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

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

Scenario:
Create a fake repository for i586

11s 135ms 7

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

And I follow "Create Repository" 360ms

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

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

And I uncheck "metadataSigned" 10s 68ms

And I click on "Create Repository" 431ms

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

Scenario:
Add the repository to the i586 channel

1s 806ms 9

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

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

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

And I click on "Update Channel" 499ms

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

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

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

And I click on "Save Repositories" 546ms

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

@sle_minion

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

1s 668ms 6

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

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

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

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

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

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

1s 177ms 7

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

And I follow "Create Repository" 288ms

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

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

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

And I click on "Create Repository" 55ms

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

@deblike_minion

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

1s 293ms 6

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

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

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

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

And I click on "Save Repositories" 604ms

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

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Add the repository to the terminal child channel

< 1ms 9

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

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

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

And I click on "Update Channel" 0s

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

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

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

And I click on "Save Repositories" 0s

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

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

496ms 1

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

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 567ms 10

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

And I follow "Create Channel" 272ms

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

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

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

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

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

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

And I click on "Create Channel" 629ms

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

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

15s 692ms 1 1

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

14s 127ms Show Info +

16:36:45:000 - 16:36:47: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 184ms 10

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

And I follow "Create Channel" 584ms

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

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

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

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

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

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

And I click on "Create Channel" 55ms

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

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

4s 67ms 1

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

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

982ms 10

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

And I follow "Create Channel" 326ms

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

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

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

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

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

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

And I click on "Create Channel" 54ms

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

@deblike_minion

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

7s 136ms 1

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

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 326ms 10

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

And I follow "Create Channel" 259ms

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

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

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

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

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

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

And I click on "Create Channel" 508ms

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

@rhlike_minion

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

4s 372ms 1

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

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

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

And I enable source package syncing 1s 379ms

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

3s 704ms 9

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

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

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

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

And I follow "Sync" 310ms

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

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

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

@sle_minion

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

4s 514ms 2

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

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

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

3s 724ms 9

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

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

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

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

And I follow "Sync" 302ms

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

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

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

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

Scenario:
Synchronize Test-Child-Channel-x86_64 channel

4s 205ms 9

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

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

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

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

And I follow "Sync" 758ms

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

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

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

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

@sle_minion

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

24s 687ms 9

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

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

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

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

And I follow "Sync" 691ms

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

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

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

@deblike_minion

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

3s 631ms 9

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

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

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

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

And I follow "Sync" 305ms

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

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

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

@rhlike_minion

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

4s 207ms 9

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

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

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

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

And I follow "Sync" 773ms

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

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

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

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

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 152ms 9

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

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

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

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

And I follow "Sync" 777ms

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

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

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

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

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Synchronize the repository in the terminal channel

< 1ms 9

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

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

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

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

And I follow "Sync" 0s

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

And I click on "Sync Now" 0s

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

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

@pxeboot_minion @uyuni @scc_credentials

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

< 1ms 2

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

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

Scenario:
Refresh the errata cache

5s 546ms 6

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

And I follow "errata-cache-default" 320ms

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

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

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

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

Scenario:
Refresh the channel's repository data

4s 967ms 6

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

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

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

And I click on "Single Run Schedule" 442ms

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

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

Scenario:
Cleanup disable source package syncing

1s 33ms 1

Then I disable source package syncing 1s 33ms

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

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

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

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

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

And I follow "Sync" 610ms

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

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

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

16:38:37:000 - 16:38:50:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/manage/Sync.do?cid=131

Screenshot +

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

4s 50ms 9

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

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

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

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

And I follow "Sync" 615ms

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

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

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

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 105ms 9

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

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

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

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

And I follow "Sync" 691ms

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

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

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

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

4s 264ms 9

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

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

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

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

And I follow "Sync" 855ms

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

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

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

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

Feature:Create activation keys 17s 609ms 9

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

Scenario:
Log in as admin user

458ms 1

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

@sle_minion

Scenario:
Create an activation key with a channel

2s 110ms 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 562ms

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

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

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

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

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

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

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

@ssh_minion

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

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

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

@ssh_minion

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

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

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

@proxy

Scenario:
Create an activation key for the proxy

2s 936ms 2

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

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

@build_host

Scenario:
Create an activation key for the build host

3s 218ms 3

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

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

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

@scc_credentials

Scenario:
Create an activation key for the terminal

2s 293ms 2

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

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

Feature:Update activation keys 27s 280ms 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

521ms 1

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 639ms

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

@scc_credentials @susemanager

Scenario:
Update SLE SSH key with synced base product

< 1ms 14

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

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

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

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

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

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

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

And I click on "Update Activation Key" 0s

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

@uyuni

Scenario:
Update openSUSE Tumbleweed SSH key with synced base product

2s 476ms 10

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 687ms

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 595ms

Then I should see a "Activation key SUSE SSH 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 350ms 20

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

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

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

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

And I wait for child channels to appear 635ms

And I include the recommended child channels 161ms

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

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

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

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

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

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

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

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

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

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

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

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

@scc_credentials @uyuni @build_host

Scenario:
Update build host key with Uyuni client tools

3s 83ms 9

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

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

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

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

And I wait for child channels to appear 273ms

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

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

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

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

@skip_if_github_validation @scc_credentials @uyuni @build_host

Scenario:
Update build host key with dev child channel

2s 891ms 9

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

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

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

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

And I wait for child channels to appear 272ms

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

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

And I click on "Update Activation Key" 776ms

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

4s 148ms 16

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

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

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

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

And I wait for child channels to appear 769ms

And I include the recommended child channels 151ms

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

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

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

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

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

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

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

And I click on "Update Activation Key" 860ms

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

@susemanager @scc_credentials @build_host

Scenario:
Update terminal key with normal SUSE fake channel

< 1ms 9

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

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

And I wait for child channels to appear 0s

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

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

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

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

And I click on "Update Activation Key" 0s

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

@pxeboot_minion @uyuni @scc_credentials @build_host

Scenario:
Update terminal key with specific fake channel

< 1ms 9

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

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

And I wait for child channels to appear 0s

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

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

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

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

And I click on "Update Activation Key" 0s

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

@skip_if_github_validation @sle_minion

Scenario:
Update SLE key with to include dev child channel

2s 37ms 6

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

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

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

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

And I click on "Update Activation Key" 668ms

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

@skip_if_github_validation @deblike_minion

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

1s 843ms 6

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

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

And I wait for child channels to appear 955ms

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

And I click on "Update Activation Key" 616ms

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

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

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

And I wait for child channels to appear 939ms

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

And I click on "Update Activation Key" 578ms

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

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

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

@sle_minion

Scenario:
Create the bootstrap repository for SUSE Minion

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

@proxy

Scenario:
Create the bootstrap repository for Proxy

2s 121ms 1

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

@build_host

Scenario:
Create the bootstrap repository for Build Host

2s 368ms 1

base_channel: SLE-Product-SLES15-SP7-Pool for x86_64
channel: SLE-15-SP7-x86_64
parent_channel: sle-product-sles15-sp7-pool-x86_64
Creating the bootstrap repository on the server:
mgr-create-bootstrap-repo --create SLE-15-SP7-x86_64 --with-parent-channel sle-product-sles15-sp7-pool-x86_64 --with-custom-channels

When I create the bootstrap repository for "build_host" on the server 2s 368ms

@transactional_server
Feature:SELinux debugging < 1ms 1

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

Scenario:
No previous operation has created wrong SELinux label

< 1ms 1

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

@new_issue
Feature:Debug the server after the testsuite has run 18s 603ms 5

Scenario:
Call spacewalk-debug on server

14s 452ms 1

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

Scenario:
Check the tomcat logs on server

821ms 1

Then the tomcat logs should not contain errors 821ms

Scenario:
Check salt event log for failures on server

1s 993ms 1

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

Scenario:
Check the taskomatic logs on server

654ms 1

Then the taskomatic logs should not contain errors 654ms

Scenario:
Check for out of memory errors

681ms 1

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

Feature:Debug the clients after the testsuite has run 43s 645ms 1

Scenario:
Extract the logs from all our clients

43s 645ms 1

When I extract the log files from all our active nodes 43s 645ms

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

Scenario:
Count UI SCC accesses in rhn_web_ui.log

< 1ms 1

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

Scenario:
Count Taskomatic SCC accesses in rhn_taskomatic_daemon.log

< 1ms 1

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

All Scenarios

148

Passed Scenarios

116

Failed Scenarios

2

Skipped Scenarios

30

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

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

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

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

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

@deblike_minion Scenario:The Debian-like minion is healthy 6s 330ms 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 678ms 1

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

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

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

@server_http_proxy Scenario:Setup HTTP proxy < 1ms 9

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

@no_auth_registry Scenario:Create an image store without credentials 3s 932ms 7

@scc_credentials Feature:List available channels and enable them 1m 39s 793ms 5 1

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

@scc_credentials Scenario:Refresh SCC 26s 866ms 1

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

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

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

@scc_credentials @uyuni @build_host Scenario:Synchronize SLES 15 SP7 product with recommended sub-products for Retail feature 41m 19s 578ms 20

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@deblike_minion Scenario:Add the repository to the Debian-like base channel 1s 293ms 6

@pxeboot_minion @uyuni @scc_credentials Scenario:Add the repository to the terminal child channel < 1ms 9

@skip_if_github_validation Feature:Create custom channels with development repositories 36s 825ms 8 1

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

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

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

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

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

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

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

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

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

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

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

@sle_minion Scenario:Synchronize Fake-Child-Channel-SUSE-like channel 24s 687ms 9

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

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

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

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

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

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

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

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

@proxy

Scenario:
The proxy is healthy

4s 407ms 4

@sle_minion

Scenario:
The minion is healthy

6s 460ms 4

@build_host

Scenario:
The build host is healthy

3s 842ms 4

@ssh_minion

Scenario:
The SSH minion is healthy

6s 398ms 4

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 736ms 4

@deblike_minion

Scenario:
The Debian-like minion is healthy

6s 330ms 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

678ms 1

@no_auth_registry

Scenario:
The registry without authentication is healthy

672ms 1

@custom_download_endpoint

Scenario:
The custom download endpoint is working

650ms 1

@skip_if_containerized_server

Scenario:
Create admin user and first organization

< 1ms 12

@server_http_proxy

Scenario:
Setup HTTP proxy

< 1ms 9

@scc_credentials @no_mirror

Scenario:
Enter valid SCC credentials

< 1ms 6

@no_auth_registry

Scenario:
Create an image store without credentials

3s 932ms 7

@scc_credentials
Feature:List available channels and enable them 1m 39s 793ms 5 1

@proxy @susemanager

Scenario:
List all products for SUSE Multi-Linux Manager

< 1ms 6

@scc_credentials

Scenario:
Refresh SCC

26s 866ms 1

@scc_credentials

Scenario:
Let the products page appear

2s 156ms 6

@scc_credentials

Scenario:
Use the products and architecture filters

2s 472ms 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 10s 894ms 4

@containerized_server @proxy @uyuni

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

1m 36s 988ms 2

@scc_credentials @uyuni @build_host

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

41m 19s 578ms 20

@proxy @susemanager @transactional_server

Scenario:
Add SL Micro 6.1 as base OS for proxy

< 1ms 13

@proxy @susemanager @skip_if_transactional_server

Scenario:
Add SLES 15 SP7 as base OS for proxy

< 1ms 11

@proxy @susemanager @transactional_server

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

< 1ms 13

@proxy @susemanager @skip_if_transactional_server

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

< 1ms 12

@proxy @susemanager @transactional_server

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

< 1ms 13

@proxy @susemanager @skip_if_transactional_server

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

< 1ms 12

@scc_credentials @susemanager

Scenario:
Installer update channels got enabled when products were added

< 1ms 2

@scc_credentials @skip_if_github_validation

Scenario:
Detect product loading issues from the UI

43s 313ms 7

@scc_credentials @skip_if_github_validation

Scenario:
Report the synchronization duration for SLES 15 SP7

< 1ms 1

@sle_minion

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

1s 394ms 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 481ms 11

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 383ms 10

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 360ms 10

@rhlike_minion

Scenario:
Create a fake AppStream repository

988ms 7

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

10s 937ms 6

@sle_minion

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

1s 848ms 9

@rhlike_minion

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

2s 215ms 9

@rhlike_minion

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

2s 213ms 9

@sle_minion

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

1s 668ms 6

@deblike_minion

Scenario:
Create a fake repository for Debian-like

1s 177ms 7

@deblike_minion

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

1s 293ms 6

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Add the repository to the terminal child channel

< 1ms 9

@skip_if_github_validation
Feature:Create custom channels with development repositories 36s 825ms 8 1

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 567ms 10

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

15s 692ms 1 1

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 184ms 10

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

4s 67ms 1

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

982ms 10

@deblike_minion

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

7s 136ms 1

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 326ms 10

@rhlike_minion

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

4s 372ms 1

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

3s 704ms 9

@sle_minion

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

4s 514ms 2

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

3s 724ms 9

@sle_minion

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

24s 687ms 9

@deblike_minion

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

3s 631ms 9

@rhlike_minion

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

4s 207ms 9

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 152ms 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 952ms 3 1

@sle_minion

Scenario:
Synchronize Devel-SUSE-Channel channel

26s 532ms 8 1 1

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

4s 50ms 9

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 105ms 9

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

4s 264ms 9

@sle_minion

Scenario:
Create an activation key with a channel

2s 110ms 2

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

1s 611ms 2

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

1s 587ms 2

@ssh_minion

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

1s 641ms 2

@ssh_minion

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

1s 752ms 2

@proxy

Scenario:
Create an activation key for the proxy

2s 936ms 2

@build_host

Scenario:
Create an activation key for the build host

3s 218ms 3