All Scenarios

152

Passed Scenarios

120

Failed Scenarios

2

Skipped Scenarios

30

Execution Time: 109m 16s 522ms

Expand All | Collapse All

Metadata

App Version: Uyuni/Head
Browser: Chrome
Platform: x86_64
Parallel: Disabled

Feature:Sanity checks 32s 287ms 10 2

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

Scenario:
The server is healthy
7s 424ms 19

Then "server" should have a FQDN 182ms

And reverse resolution should work for "server" 426ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@proxy
Scenario:
The proxy is healthy
2s 792ms 4

Then "proxy" should have a FQDN 1s 837ms

And reverse resolution should work for "proxy" 190ms

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

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

@sle_minion
Scenario:
The minion is healthy
3s 822ms 4

Then "sle_minion" should have a FQDN 2s 646ms

And reverse resolution should work for "sle_minion" 228ms

And "sle_minion" should communicate with the server using public interface 718ms

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

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

Then "build_host" should have a FQDN 1s 964ms

And reverse resolution should work for "build_host" 183ms

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

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

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

Then "ssh_minion" should have a FQDN 2s 882ms

And reverse resolution should work for "ssh_minion" 261ms

And "ssh_minion" should communicate with the server using public interface 739ms

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

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

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

And reverse resolution should work for "rhlike_minion" 218ms

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

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

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

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

And reverse resolution should work for "deblike_minion" 239ms

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

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

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

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

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

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

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

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

Feature:Very first settings 45s 926ms 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
410ms 1

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

@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
38s 767ms 1

Given I am authorized for the "Admin" section 38s 767ms

Scenario:
Wait for refresh of list of products to finish
2s 251ms 1

When I wait until mgr-sync refresh is finished 2s 251ms

Scenario:
Create testing username
2s 473ms 12

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

And I follow "Create User" 495ms

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

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

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

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

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

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

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

And I click on "Create Login" 1s 245ms

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

And I should see a "testing" link 13ms

Scenario:
Grant testing user administrative priviledges
1s 625ms 10

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

And I follow "testing" 452ms

And I check "role_org_admin" 86ms

And I check "role_system_group_admin" 78ms

And I check "role_channel_admin" 78ms

And I check "role_activation_key_admin" 79ms

And I check "role_config_admin" 81ms

And I click on "Update" 508ms

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

And I should see a "testing" text 85ms

@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 "suma2" as "HTTP Proxy Username" 0s

And I enter "P4$$wordWith%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
399ms 1

* Fri Jul 04 2025 Victor Zhestkov
- Add `minion_legacy_req_warnings` option to avoid noisy warnings
- Require M2Crypto >= 0.44.0 for SUSE Family distros
- Added:
* add-minion_legacy_req_warnings-option-to-avoid-noisy.patch

* Fri Jun 27 2025 Pablo Suárez Hernández
- Prevent tests failures when pygit2 is not present
- Added:
* fix-tests-issues-in-salt-shaker-environments-721.patch

* Thu Jun 26 2025 Pablo Suárez Hernández
- Several fixes for security issues
(bsc#1244561, CVE-2024-38822)
(bsc#1244564, CVE-2024-38823)

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

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

When I turn off disable_local_repos for all clients 2s 828ms

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 3s 933ms 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 239ms 5

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

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

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

And I click on "Save Preferences" 557ms

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

Scenario:
Change page size to 100 per page in testing user
2s 694ms 5

Given I am authorized as "testing" with password "testing" 1s 971ms

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

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

And I click on "Save Preferences" 480ms

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

Feature:Prepare server for using Kiwi 3s 744ms 2

Scenario:
Log in as admin user
1s 763ms 1

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

Scenario:
Create a Kiwi user with image administrators rights
1s 981ms 16

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

And I follow "Create User" 382ms

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

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

And I enter "kiwikiwi" as "desiredpasswordConfirm" 68ms

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

And I enter "TestKiwi" as "firstNames" 56ms

And I enter "TestKiwi" as "lastName" 64ms

And I enter "kiwi@susy.de" as "email" 62ms

And I click on "Create Login" 57ms

Then I should see a "Account kiwikiwi created" text 84ms

And I should see a "kiwikiwi" link 15ms

And I should see a "normal user" text 74ms

And I follow "kiwikiwi" 249ms

And I check "role_image_admin" 83ms

And I click on "Update" 472ms

Feature:Prepare server for using Docker 5s 601ms 3

Scenario:
Log in as admin user
520ms 1

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

Scenario:
Create a Docker user with image administrators rights
2s 403ms 16

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

And I follow "Create User" 263ms

And I enter "docker" as "login" 68ms

And I enter "docker" as "desiredpassword" 54ms

And I enter "docker" as "desiredpasswordConfirm" 63ms

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

And I enter "TestDocky" as "firstNames" 58ms

And I enter "TestDocky" as "lastName" 58ms

And I enter "gino-ginae@susy.de" as "email" 68ms

And I click on "Create Login" 58ms

Then I should see a "Account docker created" text 652ms

And I should see a "docker" link 13ms

And I should see a "normal user" text 75ms

And I follow "docker" 258ms

And I check "role_image_admin" 74ms

And I click on "Update" 399ms

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

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

And I follow "Create" 478ms

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

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

And I click on "create-btn" 133ms

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

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

Feature:Do not let Taskomatic tasks interfer with our tests 35s 811ms 3

Scenario:
Log in as admin user
26s 785ms 1

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

Scenario:
Disable scheduled reposyncs
4s 575ms 5

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

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

And I choose "disabled" 62ms

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

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

Scenario:
Disable scheduled Cobbler syncs
4s 450ms 5

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

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

And I choose "disabled" 49ms

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

And I click on "Delete Schedule" 1s 623ms

@scc_credentials
Feature:List available channels and enable them 1m 18s 661ms 5 2

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

Scenario:
List available channels
15s 150ms 5

When I refresh SCC 13s 724ms

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

Then I should get "[ ] SLE-Product-SLES15-SP4-Pool for x86_64 SUSE Linux Enterprise Server 15 SP4 x86_64 [sle-product-sles15-sp4-pool-x86_64]" < 1ms

And I should get " [ ] SLE-Product-SLES15-SP4-Updates for x86_64 SUSE Linux Enterprise Server 15 SP4 x86_64 [sle-product-sles15-sp4-updates-x86_64]" < 1ms

And I should get " [ ] SLE15-SP4-Installer-Updates for x86_64 SUSE Linux Enterprise Server 15 SP4 x86_64 [sle15-sp4-installer-updates-x86_64]" < 1ms

Scenario:
List available mandatory channels
862ms 4

When I execute mgr-sync "list channels -e --no-optional" 862ms

Then I should get "[ ] SLE-Product-SLES15-SP4-Pool for x86_64 SUSE Linux Enterprise Server 15 SP4 x86_64 [sle-product-sles15-sp4-pool-x86_64]" < 1ms

And I should get " [ ] SLE-Product-SLES15-SP4-Updates for x86_64 SUSE Linux Enterprise Server 15 SP4 x86_64 [sle-product-sles15-sp4-updates-x86_64]" < 1ms

And I shouldn't get " [ ] SLE15-SP4-Installer-Updates for x86_64 SUSE Linux Enterprise Server 15 SP4 x86_64 [sle15-sp4-installer-updates-x86_64]" < 1ms

Scenario:
List Server product
854ms 2

When I execute mgr-sync "list products" 853ms

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

@proxy @susemanager
Scenario:
List Proxy product
< 1ms 2

When I execute mgr-sync "list products" 0s

Then I should get "[ ] SUSE Manager Proxy 4.3 x86_64" 0s

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

When I execute mgr-sync "list products --expand" 0s

Then I should get "[ ] SUSE Linux Enterprise Server 15 SP4 x86_64" 0s

And I should get "[ ] SUSE Manager Proxy 4.3 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 (BETA)" 0s

And I should get " [ ] (R) SUSE Multi-Linux Manager Client Tools for SLE 15 x86_64 (BETA)" 0s

Scenario:
List products with filter
866ms 4

When I execute mgr-sync "list products --expand --filter x86_64" 866ms

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

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

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

Scenario:
Let mgr-sync time out
1m 927ms 3

When I remove the mgr-sync cache file 424ms

And I execute mgr-sync refresh 1m 503ms

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

@test_issue
Feature:Synchronize products in the products page of the Setup Wizard 97m 25s 48ms 8 9

@scc_credentials
Scenario:
Refresh SCC
11s 640ms 1

When I refresh SCC 11s 640ms

@scc_credentials
Scenario:
Let the products page appear
1s 733ms 6

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

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

And I wait until I see "Product Description" text 723ms

Then I should see a "Arch" text 142ms

And I should see a "Channels" text 139ms

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

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

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

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

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

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

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

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

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

@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 SP4 product with recommended sub-products, including SUMA Client Tools
< 1ms 33

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 SP4" as the filtered product description 0s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I select or deselect "SUSE Multi-Linux Manager Beta Client Tools for SLE 15 x86_64 (BETA)" beta client tools 0s

And I select "SUSE Linux Enterprise Server LTSS 15 SP4 x86_64" as a product 0s

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

When I click the Add Product button 0s

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

Then the SLE15 SP4 product should be added 0s

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

@uyuni
Scenario:
Partially add openSUSE Leap 15.6 product, only including the required packages to generate the bootstrap repository
3m 12s 389ms 5

Reposync of channel opensuse_leap15_6-x86_64 killed
Channel opensuse_leap15_6-uyuni-client-x86_64 added
Channel opensuse_leap15_6-uyuni-client-devel-x86_64 added
WARN: Repository metadata for opensuse_leap15_6-uyuni-client-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for opensuse_leap15_6-uyuni-client-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for opensuse_leap15_6-uyuni-client-x86_64 seems not synchronized. Even if the reposync log says it is.
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel opensuse_leap15_6-uyuni-client-x86_64 synchronized in 14 seconds
Channel opensuse_leap15_6-uyuni-client-x86_64 finished syncing
/var/cache/rhn/repodata/opensuse_leap15_6-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_leap15_6-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
1 minutes out of 19 waiting for 'leap15.6-client-tools-x86_64' channels to be synchronized
/var/cache/rhn/repodata/opensuse_leap15_6-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_leap15_6-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_leap15_6-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_leap15_6-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_leap15_6-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_leap15_6-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel opensuse_leap15_6-uyuni-client-devel-x86_64 synchronized in 30 seconds
Channel opensuse_leap15_6-uyuni-client-devel-x86_64 finished syncing

When I use spacewalk-common-channel to add channel "opensuse_leap15_6" with arch "x86_64" 7s 809ms

And I kill running spacewalk-repo-sync for "opensuse_leap15_6-x86_64" channel 852ms

And I use spacewalk-repo-sync to sync channel "opensuse_leap15_6-x86_64" including "python3-ply dmidecode libunwind" packages 59s 587ms

And I use spacewalk-common-channel to add all "leap15.6-client-tools" channels with arch "x86_64" 16s 126ms

And I wait until all synchronized channels for "leap15.6-client-tools-x86_64" have finished 1m 48s 14ms

@containerized_server @proxy @uyuni
Scenario:
Add openSUSE Leap Micro 5.5 Proxy, including Uyuni Client Tools
11m 8s 441ms 2

Channel opensuse_micro5_5-x86_64 added
Channel opensuse_micro5_5-x86_64-sle-updates added
Channel opensuse_micro5_5-uyuni-client-x86_64 added
Channel opensuse_micro5_5-uyuni-client-devel-x86_64 added
/var/cache/rhn/repodata/opensuse_micro5_5-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_micro5_5-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_micro5_5-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_micro5_5-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_micro5_5-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_micro5_5-x86_64 seems not synchronized. Even if the reposync log says it is.
1 minutes out of 113 waiting for 'uyuni-proxy' channels to be synchronized
/var/cache/rhn/repodata/opensuse_micro5_5-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_micro5_5-x86_64 seems not synchronized. Even if the reposync log says it is.
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel opensuse_micro5_5-x86_64 synchronized in 62 seconds
Channel opensuse_micro5_5-x86_64 finished syncing
2 minutes out of 113 waiting for 'uyuni-proxy' channels to be synchronized
3 minutes out of 113 waiting for 'uyuni-proxy' channels to be synchronized
4 minutes out of 113 waiting for 'uyuni-proxy' channels to be synchronized
5 minutes out of 113 waiting for 'uyuni-proxy' channels to be synchronized
/var/cache/rhn/repodata/opensuse_micro5_5-x86_64-sle-updates/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_micro5_5-x86_64-sle-updates seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_micro5_5-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_micro5_5-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
6 minutes out of 113 waiting for 'uyuni-proxy' channels to be synchronized
/var/cache/rhn/repodata/opensuse_micro5_5-x86_64-sle-updates/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_micro5_5-x86_64-sle-updates seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_micro5_5-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_micro5_5-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_micro5_5-x86_64-sle-updates/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_micro5_5-x86_64-sle-updates seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_micro5_5-uyuni-client-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_micro5_5-uyuni-client-x86_64 seems not synchronized. Even if the reposync log says it is.
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel opensuse_micro5_5-uyuni-client-devel-x86_64 synchronized in 2 seconds
Channel opensuse_micro5_5-uyuni-client-devel-x86_64 finished syncing
/var/cache/rhn/repodata/opensuse_micro5_5-x86_64-sle-updates/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_micro5_5-x86_64-sle-updates seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_micro5_5-uyuni-client-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_micro5_5-uyuni-client-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_micro5_5-x86_64-sle-updates/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_micro5_5-x86_64-sle-updates seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_micro5_5-uyuni-client-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_micro5_5-uyuni-client-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_micro5_5-x86_64-sle-updates/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_micro5_5-x86_64-sle-updates seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_micro5_5-uyuni-client-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_micro5_5-uyuni-client-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_micro5_5-x86_64-sle-updates/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_micro5_5-x86_64-sle-updates seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_micro5_5-uyuni-client-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_micro5_5-uyuni-client-x86_64 seems not synchronized. Even if the reposync log says it is.
7 minutes out of 113 waiting for 'uyuni-proxy' channels to be synchronized
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel opensuse_micro5_5-x86_64-sle-updates synchronized in 435 seconds
Channel opensuse_micro5_5-x86_64-sle-updates finished syncing
/var/cache/rhn/repodata/opensuse_micro5_5-uyuni-client-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_micro5_5-uyuni-client-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_micro5_5-uyuni-client-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_micro5_5-uyuni-client-x86_64 seems not synchronized. Even if the reposync log says it is.
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel opensuse_micro5_5-uyuni-client-x86_64 synchronized in 3 seconds
Channel opensuse_micro5_5-uyuni-client-x86_64 finished syncing

When I use spacewalk-common-channel to add all "uyuni-proxy" channels with arch "x86_64" 32s 251ms

And I wait until all synchronized channels for "uyuni-proxy" have finished 10m 36s 190ms

@scc_credentials @uyuni
Scenario:
Synchronize SLES 15 SP4 product with recommended sub-products for Retail feature
81m 55s 995ms 28

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] [I] SLE-Product-SLES15-SP4-Pool for x86_64 SUSE Linux Enterprise Server 15 SP4 x86_64 [sle-product-sles15-sp4-pool-x86_64] [ ] SLE-15-SP4-Desktop-NVIDIA-Driver for x86_64 WE SUSE Linux Enterprise Workstation Extension 15 SP4 x86_64 [sle-15-sp4-desktop-nvidia-driver-x86_64-we] [I] SLE-Module-Basesystem15-SP4-Pool for x86_64 Basesystem Module 15 SP4 x86_64 [sle-module-basesystem15-sp4-pool-x86_64] [I] SLE-Module-Basesystem15-SP4-Updates for x86_64 Basesystem Module 15 SP4 x86_64 [sle-module-basesystem15-sp4-updates-x86_64] [I] SLE-Module-Containers15-SP4-Pool for x86_64 Containers Module 15 SP4 x86_64 [sle-module-containers15-sp4-pool-x86_64] [I] SLE-Module-Containers15-SP4-Updates for x86_64 Containers Module 15 SP4 x86_64 [sle-module-containers15-sp4-updates-x86_64] [I] SLE-Module-Desktop-Applications15-SP4-Pool for x86_64 Desktop Applications Module 15 SP4 x86_64 [sle-module-desktop-applications15-sp4-pool-x86_64] [I] SLE-Module-Desktop-Applications15-SP4-Updates for x86_64 Desktop Applications Module 15 SP4 x86_64 [sle-module-desktop-applications15-sp4-updates-x86_64] [I] SLE-Module-DevTools15-SP4-Pool for x86_64 Development Tools Module 15 SP4 x86_64 [sle-module-devtools15-sp4-pool-x86_64] [I] SLE-Module-DevTools15-SP4-Updates for x86_64 Development Tools Module 15 SP4 x86_64 [sle-module-devtools15-sp4-updates-x86_64] [ ] SLE-Module-Live-Patching15-SP4-Pool for x86_64 SUSE Linux Enterprise Live Patching 15 SP4 x86_64 [sle-module-live-patching15-sp4-pool-x86_64] [ ] SLE-Module-Live-Patching15-SP4-Updates for x86_64 SUSE Linux Enterprise Live Patching 15 SP4 x86_64 [sle-module-live-patching15-sp4-updates-x86_64] [ ] SLE-Module-Public-Cloud15-SP4-Pool for x86_64 Public Cloud Module 15 SP4 x86_64 [sle-module-public-cloud15-sp4-pool-x86_64] [ ] SLE-Module-Public-Cloud15-SP4-Updates for x86_64 Public Cloud Module 15 SP4 x86_64 [sle-module-public-cloud15-sp4-updates-x86_64] [I] SLE-Module-Server-Applications15-SP4-Pool for x86_64 Server Applications Module 15 SP4 x86_64 [sle-module-server-applications15-sp4-pool-x86_64] [I] SLE-Module-Server-Applications15-SP4-Updates for x86_64 Server Applications Module 15 SP4 x86_64 [sle-module-server-applications15-sp4-updates-x86_64] [ ] SLE-Module-Web-Scripting15-SP4-Pool for x86_64 Web and Scripting Module 15 SP4 x86_64 [sle-module-web-scripting15-sp4-pool-x86_64] [ ] SLE-Module-Web-Scripting15-SP4-Updates for x86_64 Web and Scripting Module 15 SP4 x86_64 [sle-module-web-scripting15-sp4-updates-x86_64] [I] SLE-Product-SLES15-SP4-LTSS-Updates for x86_64 SUSE Linux Enterprise Server LTSS 15 SP4 x86_64 [sle-product-sles15-sp4-ltss-updates-x86_64] [I] SLE-Product-SLES15-SP4-Updates for x86_64 SUSE Linux Enterprise Server 15 SP4 x86_64 [sle-product-sles15-sp4-updates-x86_64] [ ] SLE-Product-WE15-SP4-Pool for x86_64 SUSE Linux Enterprise Workstation Extension 15 SP4 x86_64 [sle-product-we15-sp4-pool-x86_64] [ ] SLE-Product-WE15-SP4-Updates for x86_64 SUSE Linux Enterprise Workstation Extension 15 SP4 x86_64 [sle-product-we15-sp4-updates-x86_64] [I] SLE15-SP4-Installer-Updates for x86_64 SUSE Linux Enterprise Server 15 SP4 x86_64 [sle15-sp4-installer-updates-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] [ ] SUSE-MicroOS-5.2-Pool for x86_64 SUSE Linux Enterprise Micro 5.2 x86_64 [suse-microos-5.2-pool-x86_64]
WARN: Repository metadata for sle-product-sles15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle15-sp4-installer-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle15-sp4-installer-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sle-product-sles15-sp4-pool-x86_64 synchronized in 4 seconds
Channel sle-product-sles15-sp4-pool-x86_64 finished syncing
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sle15-sp4-installer-updates-x86_64 synchronized in 10 seconds
Channel sle15-sp4-installer-updates-x86_64 finished syncing
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sle-product-sles15-sp4-updates-x86_64 synchronized in 4 seconds
Channel sle-product-sles15-sp4-updates-x86_64 finished syncing
1 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
2 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
3 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
4 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
5 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
6 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
7 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
8 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
9 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
10 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-module-basesystem15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
11 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-module-basesystem15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-basesystem15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-basesystem15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-basesystem15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-basesystem15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-basesystem15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
12 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-module-basesystem15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-basesystem15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-basesystem15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-basesystem15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-basesystem15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-basesystem15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-basesystem15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
13 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-module-basesystem15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sle-module-basesystem15-sp4-updates-x86_64 synchronized in 1223 seconds
Channel sle-module-basesystem15-sp4-updates-x86_64 finished syncing
WARN: Repository metadata for sle-module-server-applications15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-basesystem15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-server-applications15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sle-module-basesystem15-sp4-pool-x86_64 synchronized in 260 seconds
Channel sle-module-basesystem15-sp4-pool-x86_64 finished syncing
WARN: Repository metadata for sle-module-server-applications15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sle-module-server-applications15-sp4-pool-x86_64 synchronized in 34 seconds
Channel sle-module-server-applications15-sp4-pool-x86_64 finished syncing
14 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-module-server-applications15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-server-applications15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-server-applications15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-server-applications15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sle-module-server-applications15-sp4-updates-x86_64 synchronized in 98 seconds
Channel sle-module-server-applications15-sp4-updates-x86_64 finished syncing
15 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-module-desktop-applications15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
16 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-module-desktop-applications15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-desktop-applications15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-desktop-applications15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-desktop-applications15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sle-module-desktop-applications15-sp4-updates-x86_64 synchronized in 161 seconds
Channel sle-module-desktop-applications15-sp4-updates-x86_64 finished syncing
17 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
18 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-module-desktop-applications15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-desktop-applications15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-desktop-applications15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-desktop-applications15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-desktop-applications15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-desktop-applications15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
19 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sle-module-desktop-applications15-sp4-pool-x86_64 synchronized in 211 seconds
Channel sle-module-desktop-applications15-sp4-pool-x86_64 finished syncing
20 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
21 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
22 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
23 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
24 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
25 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
26 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-module-devtools15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-devtools15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-devtools15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-devtools15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
27 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-module-devtools15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-devtools15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-devtools15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-devtools15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-devtools15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-devtools15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/sles15-sp4-devel-uyuni-client-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for sles15-sp4-devel-uyuni-client-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-devtools15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-devtools15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-containers15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/sles15-sp4-devel-uyuni-client-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for sles15-sp4-devel-uyuni-client-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-devtools15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-devtools15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-containers15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/sles15-sp4-devel-uyuni-client-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for sles15-sp4-devel-uyuni-client-x86_64 seems not synchronized. Even if the reposync log says it is.
28 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-module-devtools15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-devtools15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-containers15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/sles15-sp4-devel-uyuni-client-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for sles15-sp4-devel-uyuni-client-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-devtools15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sle-module-devtools15-sp4-updates-x86_64 synchronized in 745 seconds
Channel sle-module-devtools15-sp4-updates-x86_64 finished syncing
WARN: Repository metadata for sle-module-containers15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/sles15-sp4-devel-uyuni-client-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for sles15-sp4-devel-uyuni-client-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-devtools15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-containers15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-containers15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/sles15-sp4-devel-uyuni-client-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for sles15-sp4-devel-uyuni-client-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-devtools15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-containers15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-containers15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sles15-sp4-devel-uyuni-client-x86_64 synchronized in 12 seconds
Channel sles15-sp4-devel-uyuni-client-x86_64 finished syncing
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sle-module-devtools15-sp4-pool-x86_64 synchronized in 98 seconds
Channel sle-module-devtools15-sp4-pool-x86_64 finished syncing
WARN: Repository metadata for sle-module-containers15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sle-module-containers15-sp4-pool-x86_64 synchronized in 6 seconds
Channel sle-module-containers15-sp4-pool-x86_64 finished syncing
29 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sle-module-containers15-sp4-updates-x86_64 synchronized in 51 seconds
Channel sle-module-containers15-sp4-updates-x86_64 finished syncing
30 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
31 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
32 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
33 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
34 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
35 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
36 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
37 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
38 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
39 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
40 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
41 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
42 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
43 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
44 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
45 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
46 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
47 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
48 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
49 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
50 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
51 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
52 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
53 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
54 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
55 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
56 minutes out of 114 waiting for 'sles15-sp4' channels to be synchronized
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sle-product-sles15-sp4-ltss-updates-x86_64 synchronized in 1609 seconds
Channel sle-product-sles15-sp4-ltss-updates-x86_64 finished syncing

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

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

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

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

And I enter "SUSE Linux Enterprise Server 15 SP4" as the filtered product description 130ms

And I wait until I see "SUSE Linux Enterprise Server 15 SP4 x86_64" text 100ms

And I open the sub-list of the product "SUSE Linux Enterprise Server 15 SP4 x86_64" 76ms

And I open the sub-list of the product "Basesystem Module 15 SP4 x86_64" 57ms

And I open the sub-list of the product "Desktop Applications Module 15 SP4 x86_64" 57ms

Then I should see that the "Basesystem Module 15 SP4 x86_64" product is "recommended" 13ms

And I should see that the "Server Applications Module 15 SP4 x86_64" product is "recommended" 13ms

When I select "SUSE Linux Enterprise Server 15 SP4 x86_64" as a product 76ms

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

And I should see the "Basesystem Module 15 SP4 x86_64" selected 23ms

And I should see the "Server Applications Module 15 SP4 x86_64" selected 24ms

When I select "Desktop Applications Module 15 SP4 x86_64" as a product 65ms

And I select "Development Tools Module 15 SP4 x86_64" as a product 67ms

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

And I should see the "Development Tools Module 15 SP4 x86_64" selected 22ms

When I select "Containers Module 15 SP4 x86_64" as a product 78ms

Then I should see the "Containers Module 15 SP4 x86_64" selected 23ms

When I select "SUSE Linux Enterprise Server LTSS 15 SP4 x86_64" as a product 63ms

Then I should see the "SUSE Linux Enterprise Server LTSS 15 SP4 x86_64" selected 24ms

When I click the Add Product button 59ms

And I wait until I see "SUSE Linux Enterprise Server 15 SP4 x86_64" product has been added 5s 370ms

Then the SLE15 SP4 product should be added 1s 101ms

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

And I wait until all synchronized channels for "sles15-sp4" have finished 81m 38s 714ms

@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 (BETA)" as a product 0s

Then I should see the "SUSE Multi-Linux Manager Proxy Extension 5.1 x86_64 (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 Multi-Linux Manager Proxy Extension 5.1 x86_64 (BETA)" 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 (BETA)" as a product 0s

Then I should see the "SUSE Multi-Linux Manager Proxy Extension 5.1 x86_64 (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 Multi-Linux Manager Proxy Extension 5.1 x86_64 (BETA)" 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 (BETA)" as a product 0s

Then I should see the "SUSE Multi-Linux Manager Retail Branch Server Extension 5.1 x86_64 (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 Multi-Linux Manager Retail Branch Server Extension 5.1 x86_64 (BETA)" 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 (BETA)" 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-SP4-Installer-Updates for x86_64 SUSE Linux Enterprise Server 15 SP4 x86_64 [sle15-sp4-installer-updates-x86_64]" 0s

@scc_credentials
Scenario:
Detect product loading issues from the UI
52s 616ms 7

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

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

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

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

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

And I select "250" from "pageSize" 84ms

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

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

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

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

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

Scenario:
Add a fake base channel for x86_64
1s 708ms 10

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

And I follow "Create Channel" 406ms

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

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

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

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

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

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

And I click on "Create Channel" 539ms

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

Scenario:
Add a fake child channel into the fake base channel x86_64
1s 507ms 10

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

And I follow "Create Channel" 284ms

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

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

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

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

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

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

And I click on "Create Channel" 593ms

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

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

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

And I follow "Create Channel" 268ms

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

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

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

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

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

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

And I click on "Create Channel" 467ms

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

Scenario:
Add a fake base channel for i586
1s 352ms 10

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

And I follow "Create Channel" 273ms

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

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

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

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

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

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

And I click on "Create Channel" 463ms

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

Scenario:
Add a fake child channel into the fake base channel i586
1s 392ms 10

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

And I follow "Create Channel" 284ms

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

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

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

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

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

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

And I click on "Create Channel" 482ms

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

Scenario:
Add a test base channel for x86_64
1s 318ms 10

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

And I follow "Create Channel" 279ms

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

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

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

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

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

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

And I click on "Create Channel" 453ms

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

Scenario:
Add a child channel into the test base channel x86_64
1s 388ms 10

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

And I follow "Create Channel" 287ms

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

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

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

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

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

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

And I click on "Create Channel" 454ms

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

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

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

And I follow "Create Channel" 0s

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

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

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

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

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

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

And I click on "Create Channel" 0s

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

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

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

And I follow "Create Channel" 283ms

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

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

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

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

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

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

And I uncheck "gpg_check" 10s 68ms

And I click on "Create Channel" 483ms

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

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

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

And I follow "Create Channel" 301ms

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

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

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

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

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

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

And I click on "Create Channel" 457ms

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

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

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

And I follow "Create Channel" 293ms

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

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

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

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

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

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

And I click on "Create Channel" 452ms

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

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

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

Scenario:
Create a fake repository for distributions using RPM
1s 262ms 7

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

And I follow "Create Repository" 382ms

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

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

And I click on "Create Repository" 443ms

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

And I should see "metadataSigned" as checked 20ms

Scenario:
Disable metadata check for the fake RPM repository
10s 980ms 6

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

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

And I uncheck "metadataSigned" 10s 86ms

And I click on "Update Repository" 438ms

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

And I should see "metadataSigned" as unchecked 17ms

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

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

And I follow "Create Repository" 257ms

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

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

And I click on "Create Repository" 57ms

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

And I should see "metadataSigned" as checked 17ms

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

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

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

And I uncheck "metadataSigned" 10s 62ms

And I click on "Update Repository" 410ms

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

And I should see "metadataSigned" as unchecked 17ms

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

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

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

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

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

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

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

And I click on "Save Repositories" 512ms

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

Scenario:
Add the fake RPM repository to the Test child channel
2s 707ms 9

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

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

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

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

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

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

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

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

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

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

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

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

And I click on "Update Channel" 62ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Scenario:
Create a fake repository for i586
11s 51ms 7

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

And I follow "Create Repository" 263ms

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

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

And I uncheck "metadataSigned" 10s 72ms

And I click on "Create Repository" 404ms

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

Scenario:
Add the repository to the i586 channel
1s 716ms 9

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

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

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

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

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

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

And I click on "Save Repositories" 470ms

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

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

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

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

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

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

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

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

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

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

And I follow "Create Repository" 261ms

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

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

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

And I click on "Create Repository" 58ms

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

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

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

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

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

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

And I click on "Save Repositories" 876ms

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

@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 24s 83ms 9

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
455ms 1

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

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

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

And I follow "Create Channel" 304ms

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

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

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

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

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

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

And I click on "Create Channel" 65ms

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

@sle_minion
Scenario:
Create custom repositories inside the SUSE custom channel
4s 184ms 1

When I prepare the development repositories of "sle_minion" as part of "devel-suse-channel" channel 4s 184ms

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

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

And I follow "Create Channel" 296ms

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

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

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

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

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

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

And I click on "Create Channel" 459ms

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

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

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

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

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

And I follow "Create Channel" 314ms

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

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

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

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

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

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

And I click on "Create Channel" 435ms

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

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

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

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

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

And I follow "Create Channel" 309ms

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

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

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

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

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

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

And I click on "Create Channel" 59ms

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

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

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

Feature:Synchronize fake channels 54s 956ms 12 2

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

Scenario:
Log in as admin user
1s 320ms 2

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

And I enable source package syncing 961ms

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

Channel synced, no .new files exist and number of solvables is bigger than 0
Channel fake-rpm-suse-channel synchronized in 0 seconds

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

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

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

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

And I follow "Sync" 289ms

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

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

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

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

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

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

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

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

Channel synced, no .new files exist and number of solvables is bigger than 0
Channel fake-child-channel-i586 synchronized in 0 seconds

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

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

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

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

And I follow "Sync" 280ms

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

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

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

And I wait until the channel "fake-child-channel-i586" has been synced 2s 7ms

Scenario:
Synchronize Test-Child-Channel-x86_64 channel
4s 930ms 9

Channel synced, no .new files exist and number of solvables is bigger than 0
Channel test-child-channel-x86_64 synchronized in 0 seconds

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

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

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

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

And I follow "Sync" 382ms

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

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

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

And I wait until the channel "test-child-channel-x86_64" has been synced 1s 935ms

@sle_minion
Scenario:
Synchronize Fake-Child-Channel-SUSE-like channel
5s 39ms 9

Channel synced, no .new files exist and number of solvables is bigger than 0
Channel fake-child-channel-suse-like synchronized in 0 seconds

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

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

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

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

And I follow "Sync" 487ms

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

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

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

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

@deblike_minion
Scenario:
Synchronize Fake-Base-Channel-Debian-like channel
5s 110ms 9

Debian-like channel synced, if Release and Packages files exist
Channel fake-base-channel-debian-like synchronized in 0 seconds

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

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

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

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

And I follow "Sync" 581ms

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

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

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

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

@rhlike_minion
Scenario:
Synchronize Fake-Base-Channel-RH-like channel
5s 218ms 9

Channel synced, no .new files exist and number of solvables is bigger than 0
Channel fake-base-channel-rh-like synchronized in 0 seconds

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

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

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

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

And I follow "Sync" 590ms

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

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

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

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

@rhlike_minion
Scenario:
Synchronize Fake-Base-Channel-AppStream channel
5s 335ms 9

Channel synced, no .new files exist and number of solvables is bigger than 0
Channel fake-base-channel-appstream synchronized in 0 seconds

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

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

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

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

And I follow "Sync" 487ms

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

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

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

And I wait until the channel "fake-base-channel-appstream" has been synced 1s 894ms

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

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

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

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

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

And I follow "Sync" 0s

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

And I click on "Sync Now" 0s

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

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

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

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

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

Scenario:
Refresh the errata cache
5s 632ms 6

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

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

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

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

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

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

Scenario:
Refresh the channel's repository data
6s 388ms 6

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

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

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

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

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

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

Scenario:
Cleanup disable source package syncing
522ms 1

Then I disable source package syncing 522ms

@skip_if_github_validation
Feature:Synchronize development channels 3m 8s 415ms 4

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
1m 12s 911ms 9

/var/cache/rhn/repodata/devel-suse-channel/*primary.xml.gz contains 0 packages
WARN: Repository metadata for devel-suse-channel seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/devel-suse-channel/*primary.xml.gz contains 0 packages
WARN: Repository metadata for devel-suse-channel seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/devel-suse-channel/*primary.xml.gz contains 0 packages
WARN: Repository metadata for devel-suse-channel seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/devel-suse-channel/*primary.xml.gz contains 0 packages
WARN: Repository metadata for devel-suse-channel seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/devel-suse-channel/*primary.xml.gz contains 0 packages
WARN: Repository metadata for devel-suse-channel seems not synchronized. Even if the reposync log says it is.
1 minutes out of 2 waiting for 'devel-suse-channel' channel to be synchronized
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel devel-suse-channel synchronized in 1 seconds

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

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

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

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

And I follow "Sync" 498ms

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

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

Then I should see a "Repository sync scheduled for Devel-SUSE-Channel." text 80ms

And I wait until the channel "devel-suse-channel" has been synced 1m 9s 673ms

@deblike_minion
Scenario:
Synchronize Devel-Debian-like-Channel channel
15s 789ms 9

Debian-like channel synced, if Release and Packages files exist
Channel devel-debian-like-channel synchronized in 2 seconds

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

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

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

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

And I follow "Sync" 286ms

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

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

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

And I wait until the channel "devel-debian-like-channel" has been synced 12s 861ms

@rhlike_minion
Scenario:
Synchronize Devel-RH-like-Channel channel
37s 958ms 9

/var/cache/rhn/repodata/devel-rh-like-channel/*primary.xml.gz contains 0 packages
WARN: Repository metadata for devel-rh-like-channel seems not synchronized. Even if the reposync log says it is.
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel devel-rh-like-channel synchronized in 13 seconds

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

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

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

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

And I follow "Sync" 291ms

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

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

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

And I wait until the channel "devel-rh-like-channel" has been synced 35s 89ms

@build_host @uyuni
Scenario:
Synchronize Devel-Build-Host-Channel channel
1m 1s 756ms 9

/var/cache/rhn/repodata/devel-build-host-channel/*primary.xml.gz contains 0 packages
WARN: Repository metadata for devel-build-host-channel seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/devel-build-host-channel/*primary.xml.gz contains 0 packages
WARN: Repository metadata for devel-build-host-channel seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/devel-build-host-channel/*primary.xml.gz contains 0 packages
WARN: Repository metadata for devel-build-host-channel seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/devel-build-host-channel/*primary.xml.gz contains 0 packages
WARN: Repository metadata for devel-build-host-channel seems not synchronized. Even if the reposync log says it is.
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel devel-build-host-channel synchronized in 1 seconds

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

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

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

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

And I follow "Sync" 295ms

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

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

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

And I wait until the channel "devel-build-host-channel" has been synced 58s 881ms

Feature:Create activation keys 13s 80ms 9

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

Scenario:
Log in as admin user
399ms 1

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

Scenario:
Create an activation key with a channel
1s 236ms 13

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

And I follow "Create Key" 323ms

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

And I enter "SUSE Test Key x86_64" as "description" 82ms

And I enter "SUSE-KEY-x86_64" as "key" 113ms

And I enter "20" as "usageLimit" 60ms

And I click on "Create Activation Key" 87ms

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

And I should see a "Details" link 16ms

And I should see a "Packages" link 14ms

And I should see a "Configuration" link in the content area 24ms

And I should see a "Groups" link 12ms

And I should see a "Activated Systems" link 12ms

@rhlike_minion
Scenario:
Create an activation key for RedHat-like minion
995ms 8

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

And I follow "Create Key" 251ms

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

And I enter "RedHat like Test Key" as "description" 70ms

And I enter "RH-LIKE-KEY" as "key" 95ms

And I select "Fake-Base-Channel-RH-like" from "selectedBaseChannel" 89ms

And I click on "Create Activation Key" 62ms

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

@deblike_minion
Scenario:
Create an activation key for Debian-like minion
1s 526ms 8

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

And I follow "Create Key" 361ms

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

And I enter "Debian-like Test Key" as "description" 69ms

And I enter "DEBLIKE-KEY" as "key" 91ms

And I select "Fake-Base-Channel-Debian-like" from "selectedBaseChannel" 71ms

And I click on "Create Activation Key" 606ms

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

Scenario:
Create an activation key with a channel for salt-ssh
1s 497ms 9

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

And I follow "Create Key" 276ms

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

And I enter "SUSE SSH Test Key x86_64" as "description" 74ms

And I enter "SUSE-SSH-KEY-x86_64" as "key" 114ms

And I enter "20" as "usageLimit" 57ms

And I select "Push via SSH" from "contact-method" 77ms

And I click on "Create Activation Key" 480ms

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

Scenario:
Create an activation key with a channel for salt-ssh via tunnel
1s 442ms 8

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

And I follow "Create Key" 269ms

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

And I enter "SUSE SSH Tunnel Test Key x86_64" as "description" 84ms

And I enter "SUSE-SSH-TUNNEL-KEY-x86_64" as "key" 128ms

And I enter "20" as "usageLimit" 57ms

And I select "Push via SSH tunnel" from "contact-method" 73ms

And I click on "Create Activation Key" 500ms

Scenario:
Create an activation key for the proxy
1s 572ms 7

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

And I follow "Create Key" 359ms

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

And I enter "Proxy Key x86_64" as "description" 69ms

And I enter "PROXY-KEY-x86_64" as "key" 111ms

And I click on "Create Activation Key" 607ms

Then I should see a "Activation key Proxy Key x86_64 has been created" text 90ms

Scenario:
Create an activation key for the build host
2s 270ms 9

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

And I follow "Create Key" 278ms

And I wait for child channels to appear 987ms

And I enter "Build host Key x86_64" as "description" 109ms

And I enter "BUILD-HOST-KEY-x86_64" as "key" 118ms

And I check "Container Build Host" 129ms

And I check "OS Image Build Host" 83ms

And I click on "Create Activation Key" 409ms

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

@scc_credentials
Scenario:
Create an activation key for the terminal
2s 139ms 7

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

And I follow "Create Key" 274ms

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

And I enter "Terminal Key x86_64" as "description" 113ms

And I enter "TERMINAL-KEY-x86_64" as "key" 113ms

And I click on "Create Activation Key" 417ms

Then I should see a "Activation key Terminal Key x86_64 has been created" text 92ms

Feature:Update activation keys 46s 453ms 11 1 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
500ms 1

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

@scc_credentials @susemanager
Scenario:
Update SLE key with synced base product
< 1ms 22

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-SP4-Pool for x86_64" has been checked 0s

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

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

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

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

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

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

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

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

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

And I check "SLE-Product-SLES15-SP4-LTSS-Updates for x86_64" 0s

And I wait until "SLE-Product-SLES15-SP4-LTSS-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 Leap key with synced base product
1s 916ms 10

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

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

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

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

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

And I check "Uyuni Client Tools for openSUSE Leap 15.6 (x86_64) (Development)" 329ms

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

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

And I click on "Update Activation Key" 523ms

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

@scc_credentials @susemanager
Scenario:
Update SLE SSH key with synced base product
< 1ms 16

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-SP4-Pool for x86_64" 0s

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

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

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

And I check "SLE-Product-SLES15-SP4-LTSS-Updates for x86_64" 0s

And I wait until "SLE-Product-SLES15-SP4-LTSS-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 Leap SSH key with synced base product
1s 841ms 10

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

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

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

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

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

And I check "Uyuni Client Tools for openSUSE Leap 15.6 (x86_64) (Development)" 427ms

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

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

And I click on "Update Activation Key" 489ms

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

@scc_credentials @susemanager
Scenario:
Update SLE SSH tunnel key with synced base product
< 1ms 16

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-SP4-Pool for x86_64" 0s

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

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

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

And I check "SLE-Product-SLES15-SP4-LTSS-Updates for x86_64" 0s

And I wait until "SLE-Product-SLES15-SP4-LTSS-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 Leap SSH tunnel key with synced base product
1s 803ms 10

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

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

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

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

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

And I check "Uyuni Client Tools for openSUSE Leap 15.6 (x86_64) (Development)" 279ms

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

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

And I click on "Update Activation Key" 509ms

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

@scc_credentials @susemanager @proxy @containerized_server @transactional_server
Scenario:
Update the SLE Micro proxy key with synced base product
< 1ms 9

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 "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 @cloud
Scenario:
Update the openSUSE Leap proxy key with synced base product
25s 137ms 7 2 1

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

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

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

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

And I wait for child channels to appear 461ms

And I check "Uyuni Client Tools for openSUSE Leap 15.6 (x86_64) (Development)" 95ms

And I check "Uyuni Proxy Devel for openSUSE Leap 15.6 (x86_64)" 10s 3ms Show Error + 
                                            
 Unable to find checkbox "Uyuni Proxy Devel for openSUSE Leap 15.6 (x86_64)" that is not disabled (Capybara::ElementNotFound)
./features/step_definitions/navigation_steps.rb:155:in `/^I check "([^"]*)"$/'
features/reposync/allcli_update_activationkeys.feature:164:in `I check "Uyuni Proxy Devel for openSUSE Leap 15.6 (x86_64)"'

And I click on "Update Activation Key" 0s

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

13s 82ms Show Info + 
00:17:35:000 - 00:17:47:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/activationkeys/Edit.do?tid=6
Screenshot +

@uyuni @proxy @containerized_server @skip_if_cloud
Scenario:
Update the openSUSE Leap Micro 5.5 Proxy Host key with synced base product
< 1ms 10

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 "SLE Micro 5.5 Update Repository (x86_64)" 0s

And I check "Uyuni Client Tools for openSUSE Leap Micro 5.5 (x86_64)" 0s

And I check "Uyuni Client Tools for openSUSE Leap Micro 5.5 (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
Scenario:
Update build host key with synced base product
3s 191ms 20

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

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

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

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

And I wait for child channels to appear 482ms

And I include the recommended child channels 189ms

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

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

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

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

And I check "SLE-Module-DevTools15-SP4-Pool for x86_64" 88ms

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

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

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

And I check "SLE-Module-Containers15-SP4-Pool for x86_64" 85ms

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

And I check "SLE-Product-SLES15-SP4-LTSS-Updates for x86_64" 82ms

And I wait until "SLE-Product-SLES15-SP4-LTSS-Updates for x86_64" has been checked 37ms

And I click on "Update Activation Key" 524ms

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

@scc_credentials @uyuni
Scenario:
Update build host key with Uyuni client tools
2s 99ms 9

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

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

And I wait for child channels to appear 872ms

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

And I wait for child channels to appear 343ms

And I check "Uyuni Client Tools for SLES15 SP4 x86_64 (Development)" 101ms

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

And I click on "Update Activation Key" 524ms

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

@skip_if_github_validation @scc_credentials @uyuni
Scenario:
Update build host key with dev child channel
2s 158ms 9

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

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

And I wait for child channels to appear 949ms

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

And I wait for child channels to appear 354ms

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

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

And I click on "Update Activation Key" 492ms

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

@scc_credentials
Scenario:
Update terminal key with synced base product
2s 911ms 18

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

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

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

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

And I wait for child channels to appear 483ms

And I include the recommended child channels 174ms

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

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

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

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

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

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

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

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

And I check "SLE-Module-Containers15-SP4-Pool for x86_64" 73ms

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

And I click on "Update Activation Key" 506ms

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

@susemanager @scc_credentials
Scenario:
Update terminal key with normal SUSE fake channel
< 1ms 7

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-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
Scenario:
Update terminal key with specific fake channel
< 1ms 7

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

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

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

And I wait for child channels to appear 830ms

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

And I click on "Update Activation Key" 500ms

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

@skip_if_github_validation @deblike_minion
Scenario:
Update Debian-like key with to include dev child channel
1s 654ms 6

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

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

And I wait for child channels to appear 838ms

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

And I click on "Update Activation Key" 495ms

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

@skip_if_github_validation @rhlike_minion
Scenario:
Update RedHat-like key with to include dev child channel
1s 572ms 6

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

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

And I wait for child channels to appear 748ms

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

And I click on "Update Activation Key" 494ms

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

Feature:Create bootstrap repositories 18s 53ms 3 1

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
1s 248ms 1

When I create the bootstrap repositories including custom channels 1s 248ms

@sle_minion
Scenario:
Create the bootstrap repository for SUSE Minion
1s 385ms 1

base_channel: openSUSE Leap 15.6 (x86_64)
channel: openSUSE-Leap-15.6-x86_64-uyuni
parent_channel:
Creating the bootstrap repository on the server:
mgr-create-bootstrap-repo --create openSUSE-Leap-15.6-x86_64-uyuni --with-custom-channels

When I create the bootstrap repository for "sle_minion" on the server 1s 385ms

@proxy
Scenario:
Create the bootstrap repository for Proxy
13s 906ms 1 1

base_channel:
channel:
parent_channel:
Creating the bootstrap repository on the server:
mgr-create-bootstrap-repo --create --with-custom-channels

When I create the bootstrap repository for "proxy" on the server 1s 4ms Show Error + 
                                            
 FAIL: mgrctl exec -it 'mgr-create-bootstrap-repo --create  --with-custom-channels' returned status code = 1.
Output:
'--with-custom-channels' not found
 (ScriptError)
./features/support/remote_node.rb:123:in `run_local'
./features/support/remote_node.rb:107:in `run'
./features/step_definitions/command_steps.rb:1150:in `/^I create the bootstrap repository for "([^"]*)" on the server((?: without flushing)?)$/'
features/reposync/srv_create_bootstrap_repositories.feature:18:in `I create the bootstrap repository for "proxy" on the server'

12s 901ms Show Info + 
00:18:22:000 - 00:18:23:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/activationkeys/Edit.do?tid=2
Screenshot +

@build_host
Scenario:
Create the bootstrap repository for Build Host
1s 512ms 1

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

When I create the bootstrap repository for "build_host" on the server 1s 512ms

Feature:SELinux debugging 182ms 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
182ms 1

Then files on container volumes should all have the proper SELinux label 182ms

@under_debugging
Feature:Debug the server after the testsuite has run 12s 516ms 5

Scenario:
Call spacewalk-debug on server
10s 123ms 1

When I execute spacewalk-debug on the server 10s 123ms

Scenario:
Check the tomcat logs on server
451ms 1

Then the tomcat logs should not contain errors 451ms

Scenario:
Check salt event log for failures on server
972ms 1

Then the salt event log on server should contain no failures 972ms

Scenario:
Check the taskomatic logs on server
501ms 1

Then the taskomatic logs should not contain errors 501ms

Scenario:
Check for out of memory errors
466ms 1

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

Feature:Debug the clients after the testsuite has run 1m 9s 929ms 1

Scenario:
Extract the logs from all our clients
1m 9s 929ms 1

When I extract the log files from all our active nodes 1m 9s 929ms

@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