Cucumber Feature Report

All Scenarios

151

Passed Scenarios

108

Failed Scenarios

12

Skipped Scenarios

31

Execution Time: 251m 4s 516ms

Expand All | Collapse All

Metadata

App Version: Uyuni/Head

Browser: Chrome

Platform: x86_64

Parallel: Disabled

Feature:Sanity checks 33s 744ms 10 2

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

Scenario:
The server is healthy

7s 849ms 19

Then "server" should have a FQDN 198ms

And reverse resolution should work for "server" 428ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@proxy

Scenario:
The proxy is healthy

2s 815ms 4

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

And reverse resolution should work for "proxy" 175ms

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

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

@sle_minion

Scenario:
The minion is healthy

5s 176ms 4

Then "sle_minion" should have a FQDN 3s 647ms

And reverse resolution should work for "sle_minion" 369ms

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

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

@build_host

Scenario:
The build host is healthy

3s 176ms 4

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

And reverse resolution should work for "build_host" 273ms

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

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

@ssh_minion

Scenario:
The SSH minion is healthy

4s 6ms 4

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

And reverse resolution should work for "ssh_minion" 257ms

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

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

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 405ms 4

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

And reverse resolution should work for "rhlike_minion" 213ms

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

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

@deblike_minion

Scenario:
The Debian-like minion is healthy

6s 60ms 4

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

And reverse resolution should work for "deblike_minion" 241ms

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

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

@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

416ms 1

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

@no_auth_registry

Scenario:
The registry without authentication is healthy

401ms 1

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

@custom_download_endpoint

Scenario:
The custom download endpoint is working

436ms 1

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

Feature:Very first settings 44s 971ms 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

440ms 1

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

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

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

Scenario:
Wait for refresh of list of products to finish

2s 209ms 1

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

Scenario:
Create testing username

1s 669ms 12

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

And I follow "Create User" 427ms

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

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

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

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

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

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

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

And I click on "Create Login" 629ms

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

And I should see a "testing" link 11ms

Scenario:
Grant testing user administrative priviledges

1s 515ms 10

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

And I follow "testing" 461ms

And I check "role_org_admin" 76ms

And I check "role_system_group_admin" 72ms

And I check "role_channel_admin" 70ms

And I check "role_activation_key_admin" 69ms

And I check "role_config_admin" 70ms

And I click on "Update" 496ms

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

And I should see a "testing" text 63ms

@server_http_proxy

Scenario:
Setup HTTP proxy

< 1ms 9

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

Then I should see a "HTTP Proxy Hostname" text 0s

And I should see a "HTTP Proxy Username" text 0s

And I should see a "HTTP Proxy Password" text 0s

When I enter the address of the HTTP proxy as "HTTP Proxy Hostname" 0s

And I enter "suma3" as "HTTP Proxy Username" 0s

And I enter "P4$$w/ord With%and&" as "HTTP Proxy Password" 0s

And I click on "Save and Verify" 0s

Then HTTP proxy verification should have succeeded 0s

Scenario:
Detect latest Salt changes on the server

468ms 1

* Mon Aug 11 2025 Victor Zhestkov
- Revert require M2Crypto >= 0.44.0 for SUSE Family distros
- Improve SL Micro 6.2 detection with grains
- Fix functional.states.test_user for SLES 16 and Micro systems
- Fix the tests failing on AlmaLinux 10 and other clones
- Added:
* improve-sl-micro-6.2-detection-with-grains.patch
* fix-functional.states.test_user-for-sles-16-and-micr.patch
* fix-the-tests-failing-on-almalinux-10-and-other-clon.patch

* 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

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

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

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

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

688ms 5

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

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

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

And I click on "Save Preferences" 55ms

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

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

2s 620ms 5

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

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

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

And I click on "Save Preferences" 526ms

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

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

Scenario:
Log in as admin user

1s 770ms 1

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

Scenario:
Create a Kiwi user with image administrators rights

1s 693ms 16

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

And I follow "Create User" 247ms

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

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

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

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

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

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

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

And I click on "Create Login" 450ms

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

And I should see a "kiwikiwi" link 11ms

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

And I follow "kiwikiwi" 255ms

And I check "role_image_admin" 98ms

And I click on "Update" 45ms

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

Scenario:
Log in as admin user

888ms 1

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

Scenario:
Create a Docker user with image administrators rights

1s 724ms 16

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

And I follow "Create User" 313ms

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

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

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

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

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

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

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

And I click on "Create Login" 51ms

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

And I should see a "docker" link 12ms

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

And I follow "docker" 261ms

And I check "role_image_admin" 91ms

And I click on "Update" 406ms

@no_auth_registry

Scenario:
Create an image store without credentials

2s 719ms 7

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

And I follow "Create" 514ms

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

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

And I click on "create-btn" 159ms

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

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

Feature:Do not let Taskomatic tasks interfere with our CI tests 33s 233ms 3

Scenario:
Log in as admin user

26s 585ms 1

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

Scenario:
Disable scheduled reposyncs

3s 76ms 5

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

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

And I choose "disabled" 52ms

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

And I click on "Disable Schedule" 56ms

Scenario:
Disable scheduled Cobbler syncs

3s 571ms 5

When I follow the left menu "Admin > Task Schedules" 1s 621ms

And I follow "cobbler-sync-default" 307ms

And I choose "disabled" 43ms

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

And I click on "Disable Schedule" 49ms

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

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

Scenario:
List available channels

13s 358ms 5

When I refresh SCC 11s 938ms

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

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

922ms 4

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

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

874ms 2

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

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 Beta Client Tools for SUSE Liberty Linux 7, RHEL and clones 7 x86_64 (BETA)" 0s

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

Scenario:
List products with filter

880ms 4

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

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

When I remove the mgr-sync cache file 424ms

And I execute mgr-sync refresh 1m 468ms

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 196m 19s 615ms 6 2 9

@scc_credentials

Scenario:
Refresh SCC

10s 385ms 1

When I refresh SCC 10s 385ms

@scc_credentials

Scenario:
Let the products page appear

1s 435ms 6

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

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

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

Then I should see a "Arch" text 106ms

And I should see a "Channels" text 94ms

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

@scc_credentials

Scenario:
Use the products and architecture filters

1s 956ms 7

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

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

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

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

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

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

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

@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" 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" 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

2m 41s 488ms 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
/var/cache/rhn/repodata/opensuse_leap15_6-uyuni-client-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_leap15_6-uyuni-client-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_leap15_6-uyuni-client-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_leap15_6-uyuni-client-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_leap15_6-uyuni-client-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_leap15_6-uyuni-client-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-x86_64 synchronized in 25 seconds
Channel opensuse_leap15_6-uyuni-client-x86_64 finished syncing
1 minutes out of 19 waiting for 'leap15.6-client-tools-x86_64' channels to be synchronized
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 12 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" 6s 213ms

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

And I use spacewalk-repo-sync to sync channel "opensuse_leap15_6-x86_64" including "python3-ply dmidecode libunwind" packages 1m 5s 63ms

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

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

@containerized_server @proxy @uyuni

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

191m 54s 160ms 2

Channel opensuse_tumbleweed-x86_64 added
Channel opensuse_tumbleweed-uyuni-client-devel-x86_64 added
Channel uyuni-proxy-devel-tumbleweed-x86_64 added
1 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
2 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
3 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
4 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
5 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
6 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
7 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
8 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
9 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
10 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
11 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
12 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
13 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
14 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
15 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
16 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
17 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
18 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
19 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
20 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
21 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
22 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
23 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
24 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
25 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
26 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
27 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
28 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
29 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
30 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
31 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
32 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
33 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
34 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
35 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
36 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
37 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
38 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
39 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
40 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
41 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
42 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
43 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
44 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
45 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
46 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
47 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
48 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
49 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
50 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
51 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
52 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
53 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
54 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
55 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
56 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
57 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
58 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
59 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
60 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
61 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
62 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
63 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
64 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
65 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
66 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
67 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
68 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
69 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
70 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
71 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
72 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
73 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
74 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
75 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
76 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
77 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
78 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
79 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
80 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
81 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
82 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
83 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
84 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
85 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
86 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
87 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
88 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
89 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
90 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
91 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
92 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
93 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
94 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
95 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
96 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
97 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
98 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
99 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
100 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
101 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
102 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
103 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
104 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
105 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
106 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
107 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
108 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
109 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
110 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
111 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
112 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
113 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
114 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
115 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
116 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
117 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
118 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
119 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
120 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
121 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
122 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
123 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
124 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
125 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
126 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
127 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
128 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
129 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
130 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
131 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
132 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
133 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
134 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
135 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
136 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
137 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
138 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
139 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
140 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
141 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
142 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
143 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
144 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
145 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
146 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
147 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
148 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
149 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
150 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
151 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
152 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
153 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
154 minutes out of 227 waiting for 'uyuni-proxy' channels to be synchronized
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/opensuse_tumbleweed-uyuni-client-devel-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for opensuse_tumbleweed-uyuni-client-devel-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/uyuni-proxy-devel-tumbleweed-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for uyuni-proxy-devel-tumbleweed-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_tumbleweed-x86_64 synchronized in 10642 seconds
Channel opensuse_tumbleweed-x86_64 finished syncing
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel uyuni-proxy-devel-tumbleweed-x86_64 synchronized in 12 seconds
Channel uyuni-proxy-devel-tumbleweed-x86_64 finished syncing
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel opensuse_tumbleweed-uyuni-client-devel-x86_64 synchronized in 12 seconds
Channel opensuse_tumbleweed-uyuni-client-devel-x86_64 finished syncing

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

And I wait until all synchronized channels for "uyuni-proxy" have finished 191m 34s 778ms

@scc_credentials @uyuni

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

1m 9s 649ms 28 1

Products list: Please enter the credentials of SUSE Multi-Linux Manager Administrator. Login: 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] /usr/lib64/python3.6/getpass.py:91: GetPassWarning: Can not control echo on the terminal. passwd = fallback_getpass(prompt, stream) Warning: Password input may be echoed. Password:
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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 51ms

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

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

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

And I wait until all synchronized channels for "sles15-sp4" have finished 30s 245ms Show Error +

                                            
 FAIL: mgrctl cp server:/var/log/rhn/reposync.log /tmp/reposync.log returned status code = 1.
Output:
1:10PM INF Starting mgrctl cp server:/var/log/rhn/reposync.log /tmp/reposync.log
1:10PM ??? Error: 1 error occurred:
	* copying from container: copier: get: "/var/log/rhn/reposync.log": copying /var/log/rhn/reposync.log: archive/tar: write too long
 (ScriptError)
./features/support/remote_node.rb:132:in `run_local'
./features/support/remote_node.rb:231:in `extract'
./features/support/commonlib.rb:599:in `channel_sync_completed?'
./features/step_definitions/command_steps.rb:475:in `block (3 levels) in (top (required))'
./features/step_definitions/command_steps.rb:474:in `each'
./features/step_definitions/command_steps.rb:474:in `block (2 levels) in (top (required))'
./features/support/commonlib.rb:106:in `block in repeat_until_timeout'
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/step_definitions/command_steps.rb:473:in `/^I wait until all synchronized channels for "([^"]*)" have finished$/'
features/reposync/srv_sync_products.feature:127:in `I wait until all synchronized channels for "sles15-sp4" have finished'

13s 424ms Show Info +

13:09:10:000 - 13:10:07:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/admin/setup/products

Screenshot +

@proxy @susemanager @transactional_server

Scenario:
Add SL Micro 6.1 as base OS for proxy

< 1ms 13

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

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

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

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

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

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

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

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

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

And I click the Add Product button 0s

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

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

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

@proxy @susemanager @skip_if_transactional_server

Scenario:
Add SLES 15 SP7 as base OS for proxy

< 1ms 11

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

@proxy @susemanager @transactional_server

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

< 1ms 13

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

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

@proxy @susemanager @skip_if_transactional_server

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

< 1ms 12

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

@proxy @susemanager @transactional_server

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

< 1ms 13

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

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

@proxy @susemanager @skip_if_transactional_server

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

< 1ms 12

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

@scc_credentials @susemanager

Scenario:
Installer update channels got enabled when products were added

< 1ms 2

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

And I should get " [I] SLE15-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

20s 539ms 7 1

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

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

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

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

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

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

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

                                            
 No product synchronized (ScriptError)
./features/step_definitions/navigation_steps.rb:834:in `/^I should only see success signs in the product list$/'
features/reposync/srv_sync_products.feature:251:in `I should only see success signs in the product list'

13s 493ms Show Info +

13:10:21:000 - 13:10:29:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/admin/setup/products

Screenshot +

@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 23s 740ms 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

612ms 1

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

Scenario:
Add a fake base channel for x86_64

1s 758ms 10

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

And I follow "Create Channel" 452ms

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

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

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

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

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

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

And I click on "Create Channel" 670ms

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

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

1s 468ms 10

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

And I follow "Create Channel" 340ms

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

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

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

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

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

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

And I click on "Create Channel" 50ms

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

@sle_minion

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

1s 325ms 10

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

And I follow "Create Channel" 282ms

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

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

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

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

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

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

And I click on "Create Channel" 539ms

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

Scenario:
Add a fake base channel for i586

1s 272ms 10

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

And I follow "Create Channel" 286ms

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

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

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

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

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

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

And I click on "Create Channel" 475ms

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

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

1s 275ms 10

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

And I follow "Create Channel" 305ms

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

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

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

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

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

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

And I click on "Create Channel" 463ms

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

Scenario:
Add a test base channel for x86_64

1s 221ms 10

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

And I follow "Create Channel" 232ms

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

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

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

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

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

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

And I click on "Create Channel" 51ms

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

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

1s 273ms 10

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

And I follow "Create Channel" 295ms

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

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

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

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

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

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

And I click on "Create Channel" 455ms

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

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

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

And I follow "Create Channel" 316ms

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

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

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

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

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

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

And I uncheck "gpg_check" 10s 67ms

And I click on "Create Channel" 509ms

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

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 252ms 10

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

And I follow "Create Channel" 235ms

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

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

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

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

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

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

And I click on "Create Channel" 472ms

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

@rhlike_minion

Scenario:
Add a fake AppStream base channel

866ms 10

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

And I follow "Create Channel" 302ms

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

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

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

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

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

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

And I click on "Create Channel" 54ms

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

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

462ms 1

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

Scenario:
Create a fake repository for distributions using RPM

713ms 7

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

And I follow "Create Repository" 285ms

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

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

And I click on "Create Repository" 57ms

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

And I should see "metadataSigned" as checked 19ms

Scenario:
Disable metadata check for the fake RPM repository

10s 929ms 6

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

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

And I uncheck "metadataSigned" 10s 60ms

And I click on "Update Repository" 435ms

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

And I should see "metadataSigned" as unchecked 15ms

@rhlike_minion

Scenario:
Create a fake AppStream repository

664ms 7

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

And I follow "Create Repository" 342ms

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

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

And I click on "Create Repository" 49ms

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

And I should see "metadataSigned" as checked 15ms

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

10s 954ms 6

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

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

And I uncheck "metadataSigned" 10s 60ms

And I click on "Update Repository" 475ms

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

And I should see "metadataSigned" as unchecked 14ms

@sle_minion

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

1s 670ms 9

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

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

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

And I click on "Update Channel" 483ms

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

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

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

And I click on "Save Repositories" 447ms

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

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

1s 726ms 9

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

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

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

And I click on "Update Channel" 54ms

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

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

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

And I click on "Save Repositories" 578ms

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

@rhlike_minion

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

1s 588ms 9

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

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

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

And I click on "Update Channel" 446ms

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

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

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

And I click on "Save Repositories" 440ms

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

@rhlike_minion

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

1s 800ms 9

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

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

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

And I click on "Update Channel" 428ms

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

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

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

And I click on "Save Repositories" 658ms

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

Scenario:
Create a fake repository for i586

11s 4ms 7

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

And I follow "Create Repository" 273ms

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

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

And I uncheck "metadataSigned" 10s 79ms

And I click on "Create Repository" 387ms

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

Scenario:
Add the repository to the i586 channel

1s 593ms 9

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

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

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

And I click on "Update Channel" 463ms

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

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

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

And I click on "Save Repositories" 381ms

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

@sle_minion

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

1s 852ms 6

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

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

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

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

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

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

@deblike_minion

Scenario:
Create a fake repository for Debian-like

659ms 7

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

And I follow "Create Repository" 279ms

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

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

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

And I click on "Create Repository" 52ms

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

@deblike_minion

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

1s 560ms 6

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

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

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

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

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

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

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Add the repository to the terminal child channel

< 1ms 9

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

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

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

And I click on "Update Channel" 0s

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

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

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

And I click on "Save Repositories" 0s

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

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

434ms 1

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

@sle_minion

Scenario:
Create a custom channel for SUSE minions

933ms 10

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

And I follow "Create Channel" 243ms

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

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

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

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

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

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

And I click on "Create Channel" 60ms

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

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

5s 218ms 1

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

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 270ms 10

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

And I follow "Create Channel" 303ms

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

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

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

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

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

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

And I click on "Create Channel" 447ms

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

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

3s 106ms 1

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

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

1s 233ms 10

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

And I follow "Create Channel" 232ms

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

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

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

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

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

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

And I click on "Create Channel" 445ms

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

@deblike_minion

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

6s 987ms 1

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

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

820ms 10

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

And I follow "Create Channel" 250ms

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

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

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

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

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

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

And I click on "Create Channel" 52ms

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

@rhlike_minion

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

4s 131ms 1

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

Feature:Synchronize fake channels 36m 27s 618ms 6 6 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 400ms 2

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

And I enable source package syncing 955ms

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

2m 17s 469ms 9 1

1 minutes out of 2 waiting for 'fake-rpm-suse-channel' channel to be synchronized
execution expired

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

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

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

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

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

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

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

And I wait until the channel "fake-rpm-suse-channel" has been synced 2m Show Error +

                                            
 This channel was not fully synced: fake-rpm-suse-channel (ScriptError)
./features/step_definitions/command_steps.rb:449:in `rescue in block in (top (required))'
./features/step_definitions/command_steps.rb:438:in `/^I wait until the channel "([^"]*)" has been synced$/'
features/reposync/srv_sync_fake_channels.feature:31:in `I wait until the channel "fake-rpm-suse-channel" has been synced'

14s 747ms Show Info +

13:12:33:000 - 13:14:36:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/manage/Sync.do?cid=124

Screenshot +

@sle_minion

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

10m 32s 752ms 2 1

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

And solver file for "fake-rpm-suse-channel" should reference "orion-dummy-1.1-1.1.x86_64.rpm" 10m Show Error +

                                            
 execution expired (Timeout::Error)
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/step_definitions/command_steps.rb:419:in `/^solver file for "([^"]*)" should reference "([^"]*)"$/'
features/reposync/srv_sync_fake_channels.feature:36:in `solver file for "fake-rpm-suse-channel" should reference "orion-dummy-1.1-1.1.x86_64.rpm"'

13s 749ms Show Info +

13:14:51:000 - 13:25:10:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/manage/Sync.do?cid=124

Screenshot +

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

5m 21s 38ms 9 1

1 minutes out of 5 waiting for 'fake-child-channel-i586' channel to be synchronized
2 minutes out of 5 waiting for 'fake-child-channel-i586' channel to be synchronized
3 minutes out of 5 waiting for 'fake-child-channel-i586' channel to be synchronized
4 minutes out of 5 waiting for 'fake-child-channel-i586' channel to be synchronized
execution expired

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

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

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

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

And I follow "Sync" 1s 280ms

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

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

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

And I wait until the channel "fake-child-channel-i586" has been synced 5m Show Error +

                                            
 This channel was not fully synced: fake-child-channel-i586 (ScriptError)
./features/step_definitions/command_steps.rb:449:in `rescue in block in (top (required))'
./features/step_definitions/command_steps.rb:438:in `/^I wait until the channel "([^"]*)" has been synced$/'
features/reposync/srv_sync_fake_channels.feature:48:in `I wait until the channel "fake-child-channel-i586" has been synced'

16s 888ms Show Info +

13:25:24:000 - 13:30:29:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/manage/Sync.do?cid=126

Screenshot +

Scenario:
Synchronize Test-Child-Channel-x86_64 channel

6m 20s 418ms 9 1

1 minutes out of 6 waiting for 'test-child-channel-x86_64' channel to be synchronized
2 minutes out of 6 waiting for 'test-child-channel-x86_64' channel to be synchronized
3 minutes out of 6 waiting for 'test-child-channel-x86_64' channel to be synchronized
4 minutes out of 6 waiting for 'test-child-channel-x86_64' channel to be synchronized
5 minutes out of 6 waiting for 'test-child-channel-x86_64' channel to be synchronized
execution expired

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

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

And I follow "Test-Child-Channel-x86_64" 1s 18ms

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

And I follow "Sync" 1s 103ms

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

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

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

And I wait until the channel "test-child-channel-x86_64" has been synced 6m Show Error +

                                            
 This channel was not fully synced: test-child-channel-x86_64 (ScriptError)
./features/step_definitions/command_steps.rb:449:in `rescue in block in (top (required))'
./features/step_definitions/command_steps.rb:438:in `/^I wait until the channel "([^"]*)" has been synced$/'
features/reposync/srv_sync_fake_channels.feature:59:in `I wait until the channel "test-child-channel-x86_64" has been synced'

13s 747ms Show Info +

13:30:46:000 - 13:36:56:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/manage/Sync.do?cid=128

Screenshot +

@sle_minion

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

4m 16s 663ms 9 1

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

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

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

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

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

And I follow "Sync" 601ms

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

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

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

And I wait until the channel "fake-child-channel-suse-like" has been synced 4m Show Error +

                                            
 This channel was not fully synced: fake-child-channel-suse-like (ScriptError)
./features/step_definitions/command_steps.rb:449:in `rescue in block in (top (required))'
./features/step_definitions/command_steps.rb:438:in `/^I wait until the channel "([^"]*)" has been synced$/'
features/reposync/srv_sync_fake_channels.feature:71:in `I wait until the channel "fake-child-channel-suse-like" has been synced'

13s 96ms Show Info +

13:37:10:000 - 13:41:14:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/manage/Sync.do?cid=123

Screenshot +

@deblike_minion

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

5m 21s 999ms 9 1

1 minutes out of 5 waiting for 'fake-base-channel-debian-like' channel to be synchronized
2 minutes out of 5 waiting for 'fake-base-channel-debian-like' channel to be synchronized
3 minutes out of 5 waiting for 'fake-base-channel-debian-like' channel to be synchronized
4 minutes out of 5 waiting for 'fake-base-channel-debian-like' channel to be synchronized
execution expired

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

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

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

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

And I follow "Sync" 1s 55ms

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

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

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

And I wait until the channel "fake-base-channel-debian-like" has been synced 5m Show Error +

                                            
 This channel was not fully synced: fake-base-channel-debian-like (ScriptError)
./features/step_definitions/command_steps.rb:449:in `rescue in block in (top (required))'
./features/step_definitions/command_steps.rb:438:in `/^I wait until the channel "([^"]*)" has been synced$/'
features/reposync/srv_sync_fake_channels.feature:83:in `I wait until the channel "fake-base-channel-debian-like" has been synced'

18s 78ms Show Info +

13:41:27:000 - 13:46:32:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/manage/Sync.do?cid=129

Screenshot +

@rhlike_minion

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

1m 53s 901ms 9

/var/cache/rhn/repodata/fake-base-channel-rh-like/*primary.xml.gz contains 0 packages
WARN: Repository metadata for fake-base-channel-rh-like seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/fake-base-channel-rh-like/*primary.xml.gz contains 0 packages
WARN: Repository metadata for fake-base-channel-rh-like seems not synchronized. Even if the reposync log says it is.
1 minutes out of 6 waiting for 'fake-base-channel-rh-like' channel to be synchronized
/var/cache/rhn/repodata/fake-base-channel-rh-like/*primary.xml.gz contains 0 packages
WARN: Repository metadata for fake-base-channel-rh-like seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/fake-base-channel-rh-like/*primary.xml.gz contains 0 packages
WARN: Repository metadata for fake-base-channel-rh-like seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/fake-base-channel-rh-like/*primary.xml.gz contains 0 packages
WARN: Repository metadata for fake-base-channel-rh-like 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 fake-base-channel-rh-like synchronized in 2 seconds

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

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

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

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

And I follow "Sync" 459ms

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

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

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

And I wait until the channel "fake-base-channel-rh-like" has been synced 1m 49s 767ms

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

7s 855ms 9

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

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

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

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

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

And I follow "Sync" 741ms

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

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

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

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

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Synchronize the repository in the terminal channel

< 1ms 9

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

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

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

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

And I follow "Sync" 0s

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

And I click on "Sync Now" 0s

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

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

@pxeboot_minion @uyuni @scc_credentials

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

< 1ms 2

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

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

Scenario:
Refresh the errata cache

6s 924ms 6

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

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

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

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

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

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

Scenario:
Refresh the channel's repository data

6s 433ms 6

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

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

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

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

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

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

Scenario:
Cleanup disable source package syncing

761ms 1

Then I disable source package syncing 761ms

@skip_if_github_validation
Feature:Synchronize development channels 9m 14s 196ms 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

2m 16s 471ms 9 1

1 minutes out of 2 waiting for 'devel-suse-channel' channel to be synchronized
2 minutes out of 2 waiting for 'devel-suse-channel' channel to be synchronized
execution expired

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

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

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

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

And I follow "Sync" 368ms

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

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

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

And I wait until the channel "devel-suse-channel" has been synced 2m Show Error +

                                            
 This channel was not fully synced: devel-suse-channel (ScriptError)
./features/step_definitions/command_steps.rb:449:in `rescue in block in (top (required))'
./features/step_definitions/command_steps.rb:438:in `/^I wait until the channel "([^"]*)" has been synced$/'
features/reposync/srv_sync_devel_channels.feature:20:in `I wait until the channel "devel-suse-channel" has been synced'

12s 973ms Show Info +

13:49:12:000 - 13:51:17:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/manage/Sync.do?cid=132

Screenshot +

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

2m 17s 163ms 9 1

1 minutes out of 2 waiting for 'devel-debian-like-channel' channel to be synchronized
2 minutes out of 2 waiting for 'devel-debian-like-channel' channel to be synchronized
execution expired

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

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

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

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

And I follow "Sync" 1s 283ms

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

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

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

And I wait until the channel "devel-debian-like-channel" has been synced 2m Show Error +

                                            
 This channel was not fully synced: devel-debian-like-channel (ScriptError)
./features/step_definitions/command_steps.rb:449:in `rescue in block in (top (required))'
./features/step_definitions/command_steps.rb:438:in `/^I wait until the channel "([^"]*)" has been synced$/'
features/reposync/srv_sync_devel_channels.feature:32:in `I wait until the channel "devel-debian-like-channel" has been synced'

12s 965ms Show Info +

13:51:30:000 - 13:53:35:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/manage/Sync.do?cid=134

Screenshot +

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

2m 21s 502ms 9 1

1 minutes out of 2 waiting for 'devel-rh-like-channel' channel to be synchronized
2 minutes out of 2 waiting for 'devel-rh-like-channel' channel to be synchronized
execution expired

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

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

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

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

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

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

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

And I wait until the channel "devel-rh-like-channel" has been synced 2m Show Error +

                                            
 This channel was not fully synced: devel-rh-like-channel (ScriptError)
./features/step_definitions/command_steps.rb:449:in `rescue in block in (top (required))'
./features/step_definitions/command_steps.rb:438:in `/^I wait until the channel "([^"]*)" has been synced$/'
features/reposync/srv_sync_devel_channels.feature:44:in `I wait until the channel "devel-rh-like-channel" has been synced'

18s 186ms Show Info +

13:53:48:000 - 13:55:52:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/manage/Sync.do?cid=135

Screenshot +

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

2m 19s 59ms 9 1

1 minutes out of 2 waiting for 'devel-build-host-channel' channel to be synchronized
execution expired

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

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

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

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

And I follow "Sync" 534ms

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

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

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

And I wait until the channel "devel-build-host-channel" has been synced 2m 1ms Show Error +

                                            
 This channel was not fully synced: devel-build-host-channel (ScriptError)
./features/step_definitions/command_steps.rb:449:in `rescue in block in (top (required))'
./features/step_definitions/command_steps.rb:438:in `/^I wait until the channel "([^"]*)" has been synced$/'
features/reposync/srv_sync_devel_channels.feature:57:in `I wait until the channel "devel-build-host-channel" has been synced'

14s 729ms Show Info +

13:56:10:000 - 13:58:16:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/manage/Sync.do?cid=133

Screenshot +

Feature:Create activation keys 26s 241ms 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

1s 335ms 1

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

Scenario:
Create an activation key with a channel

2s 947ms 13

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

And I follow "Create Key" 758ms

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

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

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

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

And I click on "Create Activation Key" 1s 150ms

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

And I should see a "Details" link 14ms

And I should see a "Packages" link 13ms

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

And I should see a "Groups" link 10ms

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

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

2s 798ms 8

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

And I follow "Create Key" 565ms

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

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

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

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

And I click on "Create Activation Key" 1s 411ms

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

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

1s 965ms 8

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

And I follow "Create Key" 578ms

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

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

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

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

And I click on "Create Activation Key" 50ms

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

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

2s 641ms 9

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

And I follow "Create Key" 655ms

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

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

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

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

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

And I click on "Create Activation Key" 49ms

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

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

1s 520ms 8

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

And I follow "Create Key" 531ms

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

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

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

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

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

And I click on "Create Activation Key" 57ms

Scenario:
Create an activation key for the proxy

4s 471ms 7

When I follow the left menu "Systems > Activation Keys" 1s 627ms

And I follow "Create Key" 563ms

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

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

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

And I click on "Create Activation Key" 1s 370ms

Then I wait until I see "Activation key Proxy Key x86_64 has been created" text 75ms

Scenario:
Create an activation key for the build host

4s 817ms 9

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

And I follow "Create Key" 696ms

And I wait for child channels to appear 3s 559ms

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

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

And I check "Container Build Host" 88ms

And I check "OS Image Build Host" 76ms

And I click on "Create Activation Key" 59ms

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

@scc_credentials

Scenario:
Create an activation key for the terminal

3s 742ms 7

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

And I follow "Create Key" 357ms

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

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

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

And I click on "Create Activation Key" 948ms

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

Feature:Update activation keys 46s 26ms 11 8

In order to register systems to the spacewalk server
As admin
I want to update activation keys to use synchronized base products

Scenario:
Log in as admin user

1s 434ms 1

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

@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

3s 659ms 10

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 931ms

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

@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

5s 109ms 10

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 50ms

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

@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

3s 885ms 10

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

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

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

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

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

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

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

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

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

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

@scc_credentials @susemanager @proxy @containerized_server @transactional_server

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

< 1ms 11

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

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

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

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

And I click on "Update Activation Key" 0s

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

@scc_credentials @susemanager @proxy @containerized_server @skip_if_transactional_server

Scenario:
Update the SLES proxy key with synced base product

< 1ms 11

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

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

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

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

And I click on "Update Activation Key" 0s

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

@uyuni @proxy @containerized_server @skip_if_cloud

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

< 1ms 8

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

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

And I click on "Update Activation Key" 0s

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

@scc_credentials

Scenario:
Update build host key with synced base product

6s 739ms 20

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

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

And I wait for child channels to appear 4s 84ms

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

And I wait for child channels to appear 926ms

And I include the recommended child channels 152ms

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

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 936ms

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

@scc_credentials @uyuni

Scenario:
Update build host key with Uyuni client tools

4s 337ms 9

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

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

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

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

And I wait for child channels to appear 251ms

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

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

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

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

@skip_if_github_validation @scc_credentials @uyuni

Scenario:
Update build host key with dev child channel

4s 594ms 9

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

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

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

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

And I wait for child channels to appear 256ms

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

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

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

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

@scc_credentials

Scenario:
Update terminal key with synced base product

5s 683ms 18

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

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

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

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

And I wait for child channels to appear 641ms

And I include the recommended child channels 179ms

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

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

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

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

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

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

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

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

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

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

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

@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 9

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

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

And I wait for child channels to appear 0s

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

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

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

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

And I click on "Update Activation Key" 0s

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

@skip_if_github_validation @sle_minion

Scenario:
Update SLE key with to include dev child channel

3s 566ms 6

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

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

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

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

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

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

@skip_if_github_validation @deblike_minion

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

3s 120ms 6

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

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

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

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

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

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

@skip_if_github_validation @rhlike_minion

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

3s 894ms 6

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

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

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

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

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

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

Feature:Create bootstrap repositories 15s 830ms 4

In order to be able to enroll clients with MU repositories
As the system administrator
I create all bootstrap repos with --with-custom-channels option

Scenario:
Create the bootstrap repositories including custom channels

2s 940ms 1

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

@sle_minion

Scenario:
Create the bootstrap repository for SUSE Minion

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

@proxy

Scenario:
Create the bootstrap repository for Proxy

3s 875ms 1

base_channel: openSUSE Tumbleweed (x86_64)
channel: openSUSE-Tumbleweed-x86_64-uyuni
parent_channel:
Creating the bootstrap repository on the server:
mgr-create-bootstrap-repo --create openSUSE-Tumbleweed-x86_64-uyuni --with-custom-channels

When I create the bootstrap repository for "proxy" on the server 3s 875ms

@build_host

Scenario:
Create the bootstrap repository for Build Host

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

@transactional_server
Feature:SELinux debugging < 1ms 1

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

Scenario:
No previous operation has created wrong SELinux label

< 1ms 1

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

@new_issue
Feature:Debug the server after the testsuite has run 35s 597ms 5

Scenario:
Call spacewalk-debug on server

29s 169ms 1

When I execute spacewalk-debug on the server 29s 169ms

Scenario:
Check the tomcat logs on server

1s 299ms 1

Then the tomcat logs should not contain errors 1s 299ms

Scenario:
Check salt event log for failures on server

2s 533ms 1

Then the salt event log on server should contain no failures 2s 533ms

Scenario:
Check the taskomatic logs on server

1s 443ms 1

Then the taskomatic logs should not contain errors 1s 443ms

Scenario:
Check for out of memory errors

1s 152ms 1

Then the log messages should not contain out of memory errors 1s 152ms

Feature:Debug the clients after the testsuite has run 2m 421ms 1

Scenario:
Extract the logs from all our clients

2m 421ms 1

When I extract the log files from all our active nodes 2m 421ms

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

Scenario:
Count UI SCC accesses in rhn_web_ui.log

< 1ms 1

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

Scenario:
Count Taskomatic SCC accesses in rhn_taskomatic_daemon.log

< 1ms 1

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

All Scenarios

151

Passed Scenarios

108

Failed Scenarios

12

Skipped Scenarios

31

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

@sle_minion Scenario:The minion is healthy 5s 176ms 4

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

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

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

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

@skip_if_cloud Scenario:The external resources can be reached < 1ms 3

@server_http_proxy Scenario:The HTTP proxy is working < 1ms 1

@auth_registry Scenario:The registry with authentication is healthy 416ms 1

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

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

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

@server_http_proxy Scenario:Setup HTTP proxy < 1ms 9

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

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

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

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

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

@test_issue Feature:Synchronize products in the products page of the Setup Wizard 196m 19s 615ms 6 2 9

@scc_credentials Scenario:Refresh SCC 10s 385ms 1

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

@scc_credentials Scenario:Use the products and architecture filters 1s 956ms 7

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

@scc_credentials @susemanager Scenario:Synchronize SLES 15 SP4 product with recommended sub-products, including SUMA Client Tools < 1ms 33

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

@containerized_server @proxy @uyuni Scenario:Add Uyuni Proxy product for Tumbleweed, including Uyuni Client Tools 191m 54s 160ms 2

@scc_credentials @uyuni Scenario:Synchronize SLES 15 SP4 product with recommended sub-products for Retail feature 1m 9s 649ms 28 1

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

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

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

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

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

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

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

@scc_credentials Scenario:Detect product loading issues from the UI 20s 539ms 7 1

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

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

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

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

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

@rhlike_minion Scenario:Add a fake AppStream base channel 866ms 10

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

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

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

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

@rhlike_minion Scenario:Add the fake AppStream repository to the AppStream base channel 1s 800ms 9

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

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

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

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

@skip_if_github_validation Feature:Create custom channels with development repositories 24s 136ms 9

@sle_minion Scenario:Create a custom channel for SUSE minions 933ms 10

@sle_minion Scenario:Create custom repositories inside the SUSE custom channel 5s 218ms 1

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

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

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

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

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

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

@sle_minion Scenario:Synchronize Fake-RPM-SUSE-Channel channel 2m 17s 469ms 9 1

@sle_minion Scenario:Verify state of Fake-RPM-SUSE-Channel channel 10m 32s 752ms 2 1

@skip_if_github_validation Scenario:Synchronize Fake-Child-Channel-i586 channel 5m 21s 38ms 9 1

@proxy

Scenario:
The proxy is healthy

2s 815ms 4

@sle_minion

Scenario:
The minion is healthy

5s 176ms 4

@build_host

Scenario:
The build host is healthy

3s 176ms 4

@ssh_minion

Scenario:
The SSH minion is healthy

4s 6ms 4

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 405ms 4

@deblike_minion

Scenario:
The Debian-like minion is healthy

6s 60ms 4

@skip_if_cloud

Scenario:
The external resources can be reached

< 1ms 3

@server_http_proxy

Scenario:
The HTTP proxy is working

< 1ms 1

@auth_registry

Scenario:
The registry with authentication is healthy

416ms 1

@no_auth_registry

Scenario:
The registry without authentication is healthy

401ms 1

@custom_download_endpoint

Scenario:
The custom download endpoint is working

436ms 1

@skip_if_containerized_server

Scenario:
Create admin user and first organization

< 1ms 12

@server_http_proxy

Scenario:
Setup HTTP proxy

< 1ms 9

@scc_credentials @no_mirror

Scenario:
Enter valid SCC credentials

< 1ms 6

@no_auth_registry

Scenario:
Create an image store without credentials

2s 719ms 7

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

@proxy @susemanager

Scenario:
List Proxy product

< 1ms 2

@proxy @susemanager

Scenario:
List all products for SUSE Multi-Linux Manager

< 1ms 5

@test_issue
Feature:Synchronize products in the products page of the Setup Wizard 196m 19s 615ms 6 2 9

@scc_credentials

Scenario:
Refresh SCC

10s 385ms 1

@scc_credentials

Scenario:
Let the products page appear

1s 435ms 6

@scc_credentials

Scenario:
Use the products and architecture filters

1s 956ms 7

@scc_credentials @susemanager

Scenario:
View the channels list in the products page

< 1ms 9

@scc_credentials @susemanager

Scenario:
Synchronize SLES 15 SP4 product with recommended sub-products, including SUMA Client Tools

< 1ms 33

@uyuni

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

2m 41s 488ms 5

@containerized_server @proxy @uyuni

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

191m 54s 160ms 2

@scc_credentials @uyuni

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

1m 9s 649ms 28 1

@proxy @susemanager @transactional_server

Scenario:
Add SL Micro 6.1 as base OS for proxy

< 1ms 13

@proxy @susemanager @skip_if_transactional_server

Scenario:
Add SLES 15 SP7 as base OS for proxy

< 1ms 11

@proxy @susemanager @transactional_server

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

< 1ms 13

@proxy @susemanager @skip_if_transactional_server

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

< 1ms 12

@proxy @susemanager @transactional_server

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

< 1ms 13

@proxy @susemanager @skip_if_transactional_server

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

< 1ms 12

@scc_credentials @susemanager

Scenario:
Installer update channels got enabled when products were added

< 1ms 2

@scc_credentials

Scenario:
Detect product loading issues from the UI

20s 539ms 7 1

@scc_credentials

Scenario:
Report the synchronization duration for SLES 15 SP4

< 1ms 1

@sle_minion

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

1s 325ms 10

@pxeboot_minion @uyuni @scc_credentials

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

< 1ms 10

@deblike_minion

Scenario:
Add Debian-like AMD64 base channel

11s 413ms 11

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 252ms 10

@rhlike_minion

Scenario:
Add a fake AppStream base channel

866ms 10

@rhlike_minion

Scenario:
Create a fake AppStream repository

664ms 7

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

10s 954ms 6

@sle_minion

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

1s 670ms 9

@rhlike_minion

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

1s 588ms 9

@rhlike_minion

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

1s 800ms 9

@sle_minion

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

1s 852ms 6

@deblike_minion

Scenario:
Create a fake repository for Debian-like

659ms 7

@deblike_minion

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

1s 560ms 6

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Add the repository to the terminal child channel

< 1ms 9

@skip_if_github_validation
Feature:Create custom channels with development repositories 24s 136ms 9

@sle_minion

Scenario:
Create a custom channel for SUSE minions

933ms 10

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

5s 218ms 1

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 270ms 10

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

3s 106ms 1

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

1s 233ms 10

@deblike_minion

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

6s 987ms 1

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

820ms 10

@rhlike_minion

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

4s 131ms 1

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

2m 17s 469ms 9 1

@sle_minion

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

10m 32s 752ms 2 1

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

5m 21s 38ms 9 1