Cucumber Feature Report

All Scenarios

148

Passed Scenarios

114

Failed Scenarios

4

Skipped Scenarios

30

Execution Time: 61m 52s 524ms

Expand All | Collapse All

Metadata

App Version: Uyuni/Head

Browser: Chrome

Platform: x86_64

Parallel: Disabled

Feature:Sanity checks 46s 59ms 10 2

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

Scenario:
The server is healthy

11s 715ms 19

Then "server" should have a FQDN 382ms

And reverse resolution should work for "server" 613ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@proxy

Scenario:
The proxy is healthy

4s 373ms 4

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

And reverse resolution should work for "proxy" 276ms

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

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

@sle_minion

Scenario:
The minion is healthy

6s 809ms 4

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

And reverse resolution should work for "sle_minion" 433ms

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

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

@build_host

Scenario:
The build host is healthy

4s 236ms 4

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

And reverse resolution should work for "build_host" 275ms

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

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

@ssh_minion

Scenario:
The SSH minion is healthy

7s 316ms 4

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

And reverse resolution should work for "ssh_minion" 511ms

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

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

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 182ms 4

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

And reverse resolution should work for "rhlike_minion" 186ms

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

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

@deblike_minion

Scenario:
The Debian-like minion is healthy

6s 441ms 4

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

And reverse resolution should work for "deblike_minion" 226ms

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

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

@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

670ms 1

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

@no_auth_registry

Scenario:
The registry without authentication is healthy

666ms 1

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

@custom_download_endpoint

Scenario:
The custom download endpoint is working

646ms 1

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

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

669ms 1

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

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

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

Scenario:
Wait for refresh of list of products to finish

3s 536ms 1

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

Scenario:
Create testing username

2s 224ms 12

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

And I follow "Create User" 573ms

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

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

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

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

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

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

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

And I click on "Create Login" 996ms

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

And I should see a "testing" link 11ms

Scenario:
Grant testing user administrative priviledges

1s 797ms 10

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

And I follow "testing" 578ms

And I check "role_org_admin" 83ms

And I check "role_system_group_admin" 76ms

And I check "role_channel_admin" 74ms

And I check "role_activation_key_admin" 76ms

And I check "role_config_admin" 74ms

And I click on "Update" 611ms

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

And I should see a "testing" text 76ms

@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

680ms 1

* Mon Jan 19 2026 Marek Czernek
- Make syntax in httputil_test compatible with Python 3.6
- Fix KeyError in postgres module with PostgreSQL 17 (bsc#1254325)
- Added:
* fix-tornado-s-httputil_test-syntax-for-python-3.6.patch
* backport-add-maintain-m-privilege-to-postgres-module.patch

* Wed Jan 14 2026 Marek Czernek
- Use internal deb classes instead of external aptsource lib
- Speed up wheel key.finger call (bsc#1240532)
- Add security patches (bsc#1254903,bsc#1254905,bsc#1254904)
- Simplify and speed up utils.find_json function (bsc#1246130)
- Added:
* use-internal-salt.utils.pkg.deb-classes-instead-of-a.patch
* speedup-wheel-key.finger-call-bsc-1240532-713.patch

When I query latest Salt changes on "server" 680ms

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

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

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 742ms 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 440ms 5

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

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

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

And I click on "Save Preferences" 681ms

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

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

3s 301ms 5

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

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

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

And I click on "Save Preferences" 643ms

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

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

Scenario:
Create a Kiwi user with image administrators rights

4s 297ms 2

New user kiwikiwi created with roles: image_admin

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

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

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

Scenario:
Create a Docker user with image administrators rights

2s 76ms 2

New user docker created with roles: image_admin

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

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

@no_auth_registry

Scenario:
Create an image store without credentials

3s 161ms 7

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

And I follow "Create" 588ms

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

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

And I click on "create-btn" 158ms

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

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

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

Scenario:
Log in as admin user

26s 755ms 1

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

Scenario:
Disable scheduled reposyncs

4s 512ms 5

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

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

And I choose "disabled" 58ms

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

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

Scenario:
Disable scheduled Cobbler syncs

4s 584ms 5

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

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

And I choose "disabled" 45ms

And I click on "Update Schedule" 51ms

And I click on "Disable Schedule" 3s 117ms

@scc_credentials
Feature:List available channels and enable them 1m 39s 477ms 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 555ms 5

When I refresh SCC 31s 257ms

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

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

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

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

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

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

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

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

When I remove the mgr-sync cache file 667ms

And I execute mgr-sync refresh 1m 758ms

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

Feature:Synchronize products in the products page of the Setup Wizard 47m 25s 347ms 6 2 9

@scc_credentials

Scenario:
Refresh SCC

28s 43ms 1

When I refresh SCC 28s 43ms

@scc_credentials

Scenario:
Let the products page appear

2s 886ms 6

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

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

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

Then I should see a "Arch" text 120ms

And I should see a "Channels" text 120ms

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

@scc_credentials

Scenario:
Use the products and architecture filters

2s 749ms 7

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

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

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

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

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

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

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

@scc_credentials @susemanager

Scenario:
View the channels list in the products page

< 1ms 9

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

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

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

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

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

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

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

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

When I close the modal dialog 0s

@scc_credentials @susemanager

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

< 1ms 30

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

Then the SLE15 SP7 product should be added 0s

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

@uyuni

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

3m 11s 294ms 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 862ms

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

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

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

@containerized_server @proxy @uyuni

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

1m 28s 390ms 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" 24s 179ms

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

@scc_credentials @uyuni @build_host

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

41m 38s 679ms 20 1

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 54ms

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

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

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

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

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

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

17s 423ms Show Info +

14:04:08:000 - 14:45:30:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/admin/setup/products

Screenshot +

@proxy @susemanager @transactional_server

Scenario:
Add SL Micro 6.1 as base OS for proxy

< 1ms 13

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

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

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

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

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

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

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

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

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

And I click the Add Product button 0s

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

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

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

@proxy @susemanager @skip_if_transactional_server

Scenario:
Add SLES 15 SP7 as base OS for proxy

< 1ms 11

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

@proxy @susemanager @transactional_server

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

< 1ms 13

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

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

@proxy @susemanager @skip_if_transactional_server

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

< 1ms 12

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

@proxy @susemanager @transactional_server

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

< 1ms 13

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

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

@proxy @susemanager @skip_if_transactional_server

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

< 1ms 12

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

@scc_credentials @susemanager

Scenario:
Installer update channels got enabled when products were added

< 1ms 2

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

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

@scc_credentials @skip_if_github_validation

Scenario:
Detect product loading issues from the UI

33s 303ms 7 1

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

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

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

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

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

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

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

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

15s 808ms Show Info +

14:45:48:000 - 14:46:07:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/admin/setup/products

Screenshot +

@scc_credentials @skip_if_github_validation

Scenario:
Report the synchronization duration for SLES 15 SP7

< 1ms 1

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

Feature:Create fake channels 31s 841ms 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

956ms 1

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

Scenario:
Add a fake base channel for x86_64

2s 122ms 10

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

And I follow "Create Channel" 539ms

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

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

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

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

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

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

And I click on "Create Channel" 886ms

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

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

2s 302ms 10

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

And I follow "Create Channel" 706ms

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

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

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

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

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

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

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

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

@sle_minion

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

1s 610ms 10

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

And I follow "Create Channel" 1s 7ms

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

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

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

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

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

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

And I click on "Create Channel" 54ms

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

Scenario:
Add a fake base channel for i586

2s 418ms 10

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

And I follow "Create Channel" 698ms

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

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

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

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

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

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

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

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

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

2s 418ms 10

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

And I follow "Create Channel" 662ms

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

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

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

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

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

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

And I click on "Create Channel" 53ms

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

Scenario:
Add a test base channel for x86_64

994ms 10

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

And I follow "Create Channel" 403ms

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

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

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

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

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

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

And I click on "Create Channel" 56ms

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

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

1s 999ms 10

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

And I follow "Create Channel" 513ms

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

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

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

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

And I click on "Create Channel" 910ms

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

@pxeboot_minion @uyuni @scc_credentials

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

< 1ms 10

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

And I follow "Create Channel" 0s

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

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

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

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

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

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

And I click on "Create Channel" 0s

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

@deblike_minion

Scenario:
Add Debian-like AMD64 base channel

12s 451ms 11

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

And I follow "Create Channel" 760ms

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

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

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

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

And I uncheck "gpg_check" 10s 83ms

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

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

@rhlike_minion

Scenario:
Add a RedHat-like base channel

2s 628ms 10

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

And I follow "Create Channel" 849ms

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

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

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

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

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

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

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

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

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 938ms 10

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

And I follow "Create Channel" 541ms

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

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

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

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

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

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

And I click on "Create Channel" 851ms

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

Feature:Create fake repositories for each fake child channel 1m 779ms 14 1

In order to distribute software to the clients
As an authorized user
I want to create a fake repository per fake child channel

Scenario:
Log in as admin user

1s 178ms 1

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

Scenario:
Create a fake repository for distributions using RPM

1s 871ms 7

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

And I follow "Create Repository" 593ms

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

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

And I click on "Create Repository" 870ms

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

And I should see "metadataSigned" as checked 19ms

Scenario:
Disable metadata check for the fake RPM repository

11s 612ms 6

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

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

And I uncheck "metadataSigned" 10s 62ms

And I click on "Update Repository" 802ms

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

And I should see "metadataSigned" as unchecked 15ms

@rhlike_minion

Scenario:
Create a fake AppStream repository

1s 569ms 7

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

And I follow "Create Repository" 439ms

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

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

And I click on "Create Repository" 839ms

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

And I should see "metadataSigned" as checked 15ms

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

11s 536ms 6

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

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

And I uncheck "metadataSigned" 10s 60ms

And I click on "Update Repository" 783ms

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

And I should see "metadataSigned" as unchecked 15ms

@sle_minion

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

3s 674ms 9

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

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

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

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

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

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

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

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

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

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

3s 485ms 9

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

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

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

And I click on "Update Channel" 995ms

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

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

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

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

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

@rhlike_minion

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

1s 956ms 9

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

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

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

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

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

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

And I click on "Save Repositories" 862ms

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

@rhlike_minion

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

3s 287ms 9

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

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

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

And I click on "Update Channel" 994ms

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

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

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

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

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

Scenario:
Create a fake repository for i586

11s 756ms 7

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

And I follow "Create Repository" 460ms

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

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

And I uncheck "metadataSigned" 10s 81ms

And I click on "Create Repository" 932ms

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

Scenario:
Add the repository to the i586 channel

3s 15ms 9

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

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

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

And I click on "Update Channel" 867ms

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

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

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

And I click on "Save Repositories" 977ms

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

@sle_minion

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

2s 410ms 6

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

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

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

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

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

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

@deblike_minion

Scenario:
Create a fake repository for Debian-like

1s 619ms 7

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

And I follow "Create Repository" 459ms

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

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

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

And I click on "Create Repository" 801ms

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

@deblike_minion

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

1s 805ms 6

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

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

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

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

And I click on "Save Repositories" 999ms

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

@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 46s 998ms 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

889ms 1

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

@sle_minion

Scenario:
Create a custom channel for SUSE minions

2s 40ms 10

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

And I follow "Create Channel" 532ms

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

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

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

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

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

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

And I click on "Create Channel" 830ms

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

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

16s 904ms 1 1

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

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

15s 217ms Show Info +

14:48:22:000 - 14:48:24: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 260ms 10

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

And I follow "Create Channel" 624ms

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

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

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

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

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

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

And I click on "Create Channel" 55ms

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

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

6s 380ms 1

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

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

1s 202ms 10

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

And I follow "Create Channel" 550ms

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

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

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

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

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

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

And I click on "Create Channel" 54ms

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

@deblike_minion

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

9s 865ms 1

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

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 957ms 10

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

And I follow "Create Channel" 573ms

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

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

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

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

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

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

And I click on "Create Channel" 815ms

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

@rhlike_minion

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

6s 498ms 1

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

Feature:Synchronize fake channels 5m 28s 358ms 12 2

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

Scenario:
Log in as admin user

2s 301ms 2

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

And I enable source package syncing 1s 567ms

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

6s 449ms 9

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

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

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

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

And I follow "Sync" 588ms

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

And I click on "Sync Now" 2s 979ms

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

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

@sle_minion

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

2m 57s 875ms 2

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

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

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

1m 47s 620ms 9

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

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

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

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

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

And I follow "Sync" 330ms

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

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

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

Scenario:
Synchronize Test-Child-Channel-x86_64 channel

3s 763ms 9

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

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

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

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

And I follow "Sync" 338ms

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

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

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

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

@sle_minion

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

4s 100ms 9

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

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

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

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

And I follow "Sync" 763ms

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

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

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

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

@deblike_minion

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

4s 80ms 9

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

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

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

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

And I follow "Sync" 684ms

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

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

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

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

@rhlike_minion

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

4s 239ms 9

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

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

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

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

And I follow "Sync" 845ms

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

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

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

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 233ms 9

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

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

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

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

And I follow "Sync" 769ms

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

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

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

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Synchronize the repository in the terminal channel

< 1ms 9

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

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

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

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

And I follow "Sync" 0s

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

And I click on "Sync Now" 0s

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

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

@pxeboot_minion @uyuni @scc_credentials

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

< 1ms 2

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

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

Scenario:
Refresh the errata cache

6s 583ms 6

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

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

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

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

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

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

Scenario:
Refresh the channel's repository data

6s 104ms 6

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

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

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

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

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

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

Scenario:
Cleanup disable source package syncing

1s 8ms 1

Then I disable source package syncing 1s 8ms

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

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

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

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

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

And I follow "Sync" 329ms

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

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

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

                                            
 Text 'Repository sync scheduled for Devel-SUSE-Channel.' not found (ScriptError)
./features/step_definitions/navigation_steps.rb:662: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 386ms Show Info +

14:54:48:000 - 14:55:01:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/manage/Sync.do?cid=131

Screenshot +

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

4s 170ms 9

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

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

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

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

And I follow "Sync" 775ms

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

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

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

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

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 142ms 9

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

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

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

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

And I follow "Sync" 859ms

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

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

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

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

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

4s 250ms 9

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

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

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

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

And I follow "Sync" 850ms

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

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

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

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

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

461ms 1

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

@sle_minion

Scenario:
Create an activation key with a channel

2s 267ms 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 651ms

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

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

1s 458ms 2

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

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

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

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

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

@ssh_minion

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

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

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

@ssh_minion

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

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

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

@proxy

Scenario:
Create an activation key for the proxy

3s 41ms 2

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

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

@build_host

Scenario:
Create an activation key for the build host

2s 716ms 3

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

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

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

@scc_credentials

Scenario:
Create an activation key for the terminal

2s 237ms 2

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

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

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

621ms 1

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 591ms

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 614ms

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 668ms

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

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

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

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

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

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

And I wait for child channels to appear 684ms

And I include the recommended child channels 203ms

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

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

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

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

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

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

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

And I click on "Update Activation Key" 734ms

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

@scc_credentials @uyuni @build_host

Scenario:
Update build host key with Uyuni client tools

4s 181ms 9

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

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

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

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

And I wait for child channels to appear 313ms

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

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

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

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

@skip_if_github_validation @scc_credentials @uyuni @build_host

Scenario:
Update build host key with dev child channel

2s 295ms 9

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

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

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

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

And I wait for child channels to appear 303ms

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

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

And I click on "Update Activation Key" 586ms

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

@scc_credentials @build_host

Scenario:
Update terminal key with synced base product

3s 598ms 16

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

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

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

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

And I wait for child channels to appear 507ms

And I include the recommended child channels 163ms

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

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

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

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

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

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

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

And I click on "Update Activation Key" 743ms

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

@susemanager @scc_credentials @build_host

Scenario:
Update terminal key with normal SUSE fake channel

< 1ms 9

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

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

And I wait for child channels to appear 0s

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

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

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

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

And I click on "Update Activation Key" 0s

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

@pxeboot_minion @uyuni @scc_credentials @build_host

Scenario:
Update terminal key with specific fake channel

< 1ms 9

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

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

And I wait for child channels to appear 0s

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

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

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

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

And I click on "Update Activation Key" 0s

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

@skip_if_github_validation @sle_minion

Scenario:
Update SLE key with to include dev child channel

1s 816ms 6

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

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

And I wait for child channels to appear 906ms

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

And I click on "Update Activation Key" 605ms

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

@skip_if_github_validation @deblike_minion

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

1s 900ms 6

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

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

And I wait for child channels to appear 993ms

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

And I click on "Update Activation Key" 613ms

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

@skip_if_github_validation @rhlike_minion

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

1s 323ms 6

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

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

And I wait for child channels to appear 975ms

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

And I click on "Update Activation Key" 50ms

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

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

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

@sle_minion

Scenario:
Create the bootstrap repository for SUSE Minion

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

@proxy

Scenario:
Create the bootstrap repository for Proxy

2s 32ms 1

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

@build_host

Scenario:
Create the bootstrap repository for Build Host

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

@transactional_server
Feature:SELinux debugging < 1ms 1

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

Scenario:
No previous operation has created wrong SELinux label

< 1ms 1

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

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

Scenario:
Call spacewalk-debug on server

14s 35ms 1

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

Scenario:
Check the tomcat logs on server

641ms 1

Then the tomcat logs should not contain errors 641ms

Scenario:
Check salt event log for failures on server

1s 743ms 1

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

Scenario:
Check the taskomatic logs on server

677ms 1

Then the taskomatic logs should not contain errors 677ms

Scenario:
Check for out of memory errors

613ms 1

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

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

Scenario:
Extract the logs from all our clients

42s 352ms 1

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

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

Scenario:
Count UI SCC accesses in rhn_web_ui.log

< 1ms 1

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

Scenario:
Count Taskomatic SCC accesses in rhn_taskomatic_daemon.log

< 1ms 1

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

All Scenarios

148

Passed Scenarios

114

Failed Scenarios

4

Skipped Scenarios

30

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

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

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

@ssh_minion Scenario:The SSH minion is healthy 7s 316ms 4

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

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

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

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

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

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

@scc_credentials Scenario:Refresh SCC 28s 43ms 1

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@sle_minion Scenario:Synchronize Fake-RPM-SUSE-Channel channel 6s 449ms 9

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

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

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

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

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

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

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

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

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

@proxy

Scenario:
The proxy is healthy

4s 373ms 4

@sle_minion

Scenario:
The minion is healthy

6s 809ms 4

@build_host

Scenario:
The build host is healthy

4s 236ms 4

@ssh_minion

Scenario:
The SSH minion is healthy

7s 316ms 4

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 182ms 4

@deblike_minion

Scenario:
The Debian-like minion is healthy

6s 441ms 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

670ms 1

@no_auth_registry

Scenario:
The registry without authentication is healthy

666ms 1

@custom_download_endpoint

Scenario:
The custom download endpoint is working

646ms 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 161ms 7

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

@proxy @susemanager

Scenario:
List all products for SUSE Multi-Linux Manager

< 1ms 6

@scc_credentials

Scenario:
Refresh SCC

28s 43ms 1

@scc_credentials

Scenario:
Let the products page appear

2s 886ms 6

@scc_credentials

Scenario:
Use the products and architecture filters

2s 749ms 7

@scc_credentials @susemanager

Scenario:
View the channels list in the products page

< 1ms 9

@scc_credentials @susemanager

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

< 1ms 30

@uyuni

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

3m 11s 294ms 4

@containerized_server @proxy @uyuni

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

1m 28s 390ms 2

@scc_credentials @uyuni @build_host

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

41m 38s 679ms 20 1

@proxy @susemanager @transactional_server

Scenario:
Add SL Micro 6.1 as base OS for proxy

< 1ms 13

@proxy @susemanager @skip_if_transactional_server

Scenario:
Add SLES 15 SP7 as base OS for proxy

< 1ms 11

@proxy @susemanager @transactional_server

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

< 1ms 13

@proxy @susemanager @skip_if_transactional_server

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

< 1ms 12

@proxy @susemanager @transactional_server

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

< 1ms 13

@proxy @susemanager @skip_if_transactional_server

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

< 1ms 12

@scc_credentials @susemanager

Scenario:
Installer update channels got enabled when products were added

< 1ms 2

@scc_credentials @skip_if_github_validation

Scenario:
Detect product loading issues from the UI

33s 303ms 7 1

@scc_credentials @skip_if_github_validation

Scenario:
Report the synchronization duration for SLES 15 SP7

< 1ms 1

@sle_minion

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

1s 610ms 10

@pxeboot_minion @uyuni @scc_credentials

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

< 1ms 10

@deblike_minion

Scenario:
Add Debian-like AMD64 base channel

12s 451ms 11

@rhlike_minion

Scenario:
Add a RedHat-like base channel

2s 628ms 10

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 938ms 10

@rhlike_minion

Scenario:
Create a fake AppStream repository

1s 569ms 7

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

11s 536ms 6

@sle_minion

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

3s 674ms 9

@rhlike_minion

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

1s 956ms 9

@rhlike_minion

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

3s 287ms 9

@sle_minion

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

2s 410ms 6

@deblike_minion

Scenario:
Create a fake repository for Debian-like

1s 619ms 7

@deblike_minion

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

1s 805ms 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 46s 998ms 8 1

@sle_minion

Scenario:
Create a custom channel for SUSE minions

2s 40ms 10

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

16s 904ms 1 1

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 260ms 10

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

6s 380ms 1

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

1s 202ms 10

@deblike_minion

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

9s 865ms 1

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 957ms 10

@rhlike_minion

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

6s 498ms 1

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

6s 449ms 9

@sle_minion

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

2m 57s 875ms 2

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

1m 47s 620ms 9

@sle_minion

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

4s 100ms 9

@deblike_minion

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

4s 80ms 9

@rhlike_minion

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

4s 239ms 9

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

4s 233ms 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 730ms 3 1

@sle_minion

Scenario:
Synchronize Devel-SUSE-Channel channel

26s 167ms 8 1 1

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

4s 170ms 9

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

4s 142ms 9