All Scenarios

142

Passed Scenarios

71

Failed Scenarios

43

Skipped Scenarios

28

Execution Time: 317m 6s 933ms

Expand All | Collapse All

Metadata

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

Feature:Sanity checks 32s 798ms 10 2

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

Scenario:
The server is healthy
8s 174ms 19

Then "server" should have a FQDN 207ms

And reverse resolution should work for "server" 430ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

And reverse resolution should work for "proxy" 178ms

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

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

@sle_minion
Scenario:
The minion is healthy
4s 186ms 4

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

And reverse resolution should work for "sle_minion" 250ms

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

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

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

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

And reverse resolution should work for "build_host" 199ms

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

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

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

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

And reverse resolution should work for "ssh_minion" 280ms

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

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

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

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

And reverse resolution should work for "rhlike_minion" 195ms

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

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

@deblike_minion
Scenario:
The Debian-like minion is healthy
5s 854ms 4

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

And reverse resolution should work for "deblike_minion" 235ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Scenario:
Create testing username
1s 812ms 12

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

And I follow "Create User" 490ms

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

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

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

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

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

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

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

And I click on "Create Login" 697ms

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

And I should see a "testing" link 11ms

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

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

And I follow "testing" 435ms

And I check "role_org_admin" 97ms

And I check "role_system_group_admin" 72ms

And I check "role_channel_admin" 70ms

And I check "role_activation_key_admin" 74ms

And I check "role_config_admin" 72ms

And I click on "Update" 559ms

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

And I should see a "testing" text 62ms

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

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

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

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

In order to set up my personal preferences
As admin
I want to navigate through "Home" submenus changing some settings

Scenario:
Change page size to 100 per page in admin user
1s 183ms 5

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

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

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

And I click on "Save Preferences" 525ms

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

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

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

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

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

And I click on "Save Preferences" 455ms

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

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

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

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

Scenario:
Create a Kiwi user with image administrators rights
2s 94ms 16

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

And I follow "Create User" 254ms

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

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

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

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

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

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

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

And I click on "Create Login" 456ms

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

And I should see a "kiwikiwi" link 12ms

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

And I follow "kiwikiwi" 265ms

And I check "role_image_admin" 74ms

And I click on "Update" 434ms

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

Scenario:
Log in as admin user
534ms 1

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

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

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

And I follow "Create User" 266ms

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

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

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

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

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

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

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

And I click on "Create Login" 491ms

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

And I should see a "docker" link 13ms

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

And I follow "docker" 305ms

And I check "role_image_admin" 121ms

And I click on "Update" 438ms

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

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

And I follow "Create" 607ms

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

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

And I click on "create-btn" 148ms

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

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

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

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

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

Scenario:
Disable scheduled reposyncs
3s 50ms 5

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

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

And I choose "disabled" 54ms

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

And I click on "Disable Schedule" 65ms

Scenario:
Disable scheduled Cobbler syncs
3s 582ms 5

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

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

And I choose "disabled" 44ms

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

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

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

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

Scenario:
List available channels
14s 42ms 5

When I refresh SCC 12s 612ms

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

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

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

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

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

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

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

When I remove the mgr-sync cache file 461ms

And I execute mgr-sync refresh 1m 479ms

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 265m 24s 195ms 6 2 9

@scc_credentials
Scenario:
Refresh SCC
11s 313ms 1

When I refresh SCC 11s 313ms

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

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

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

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

Then I should see a "Arch" text 94ms

And I should see a "Channels" text 97ms

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

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

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

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

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

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

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

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

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

@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
3m 14s 492ms 5

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

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

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

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

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

@containerized_server @proxy @uyuni
Scenario:
Add Uyuni Proxy product for Tumbleweed, including Uyuni Client Tools
182m 8s 567ms 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
/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.
/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.
138 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.
139 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.
140 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.
141 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.
142 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.
143 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.
144 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.
145 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 9993 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 7 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 676ms

And I wait until all synchronized channels for "uyuni-proxy" have finished 181m 48s 891ms

@scc_credentials @uyuni
Scenario:
Synchronize SLES 15 SP4 product with recommended sub-products for Retail feature
79m 11s 763ms 27 2

Products list: Available Channels: Status: - [I] - channel is installed - [ ] - channel is not installed, but is available - [U] - channel is unavailable [ ] EL9-Pool for x86_64 RHEL and Liberty 9 Base [el9-pool-x86_64] [ ] RHEL7-Pool for x86_64 RHEL7 Base x86_64 [rhel7-pool-x86_64] [ ] RHEL8-Pool for x86_64 RHEL and Liberty 8 Base [rhel8-pool-x86_64] [ ] SLE-Micro-5.3-Pool for x86_64 SUSE Linux Enterprise Micro 5.3 x86_64 [sle-micro-5.3-pool-x86_64] [ ] SLE-Product-SLED15-SP4-Pool for x86_64 SUSE Linux Enterprise Desktop 15 SP4 x86_64 [sle-product-sled15-sp4-pool-x86_64] [I] SLE-Product-SLES15-SP4-Pool for x86_64 SUSE Linux Enterprise Server 15 SP4 x86_64 [sle-product-sles15-sp4-pool-x86_64] [ ] SLE-15-SP4-Desktop-NVIDIA-Driver for x86_64 WE SUSE Linux Enterprise Workstation Extension 15 SP4 x86_64 [sle-15-sp4-desktop-nvidia-driver-x86_64-we] [I] SLE-Module-Basesystem15-SP4-Pool for x86_64 Basesystem Module 15 SP4 x86_64 [sle-module-basesystem15-sp4-pool-x86_64] [I] SLE-Module-Basesystem15-SP4-Updates for x86_64 Basesystem Module 15 SP4 x86_64 [sle-module-basesystem15-sp4-updates-x86_64] [I] SLE-Module-Containers15-SP4-Pool for x86_64 Containers Module 15 SP4 x86_64 [sle-module-containers15-sp4-pool-x86_64] [I] SLE-Module-Containers15-SP4-Updates for x86_64 Containers Module 15 SP4 x86_64 [sle-module-containers15-sp4-updates-x86_64] [I] SLE-Module-Desktop-Applications15-SP4-Pool for x86_64 Desktop Applications Module 15 SP4 x86_64 [sle-module-desktop-applications15-sp4-pool-x86_64] [I] SLE-Module-Desktop-Applications15-SP4-Updates for x86_64 Desktop Applications Module 15 SP4 x86_64 [sle-module-desktop-applications15-sp4-updates-x86_64] [I] SLE-Module-DevTools15-SP4-Pool for x86_64 Development Tools Module 15 SP4 x86_64 [sle-module-devtools15-sp4-pool-x86_64] [I] SLE-Module-DevTools15-SP4-Updates for x86_64 Development Tools Module 15 SP4 x86_64 [sle-module-devtools15-sp4-updates-x86_64] [ ] SLE-Module-Live-Patching15-SP4-Pool for x86_64 SUSE Linux Enterprise Live Patching 15 SP4 x86_64 [sle-module-live-patching15-sp4-pool-x86_64] [ ] SLE-Module-Live-Patching15-SP4-Updates for x86_64 SUSE Linux Enterprise Live Patching 15 SP4 x86_64 [sle-module-live-patching15-sp4-updates-x86_64] [ ] SLE-Module-Public-Cloud15-SP4-Pool for x86_64 Public Cloud Module 15 SP4 x86_64 [sle-module-public-cloud15-sp4-pool-x86_64] [ ] SLE-Module-Public-Cloud15-SP4-Updates for x86_64 Public Cloud Module 15 SP4 x86_64 [sle-module-public-cloud15-sp4-updates-x86_64] [I] SLE-Module-Server-Applications15-SP4-Pool for x86_64 Server Applications Module 15 SP4 x86_64 [sle-module-server-applications15-sp4-pool-x86_64] [I] SLE-Module-Server-Applications15-SP4-Updates for x86_64 Server Applications Module 15 SP4 x86_64 [sle-module-server-applications15-sp4-updates-x86_64] [ ] SLE-Module-Web-Scripting15-SP4-Pool for x86_64 Web and Scripting Module 15 SP4 x86_64 [sle-module-web-scripting15-sp4-pool-x86_64] [ ] SLE-Module-Web-Scripting15-SP4-Updates for x86_64 Web and Scripting Module 15 SP4 x86_64 [sle-module-web-scripting15-sp4-updates-x86_64] [I] SLE-Product-SLES15-SP4-LTSS-Updates for x86_64 SUSE Linux Enterprise Server LTSS 15 SP4 x86_64 [sle-product-sles15-sp4-ltss-updates-x86_64] [I] SLE-Product-SLES15-SP4-Updates for x86_64 SUSE Linux Enterprise Server 15 SP4 x86_64 [sle-product-sles15-sp4-updates-x86_64] [ ] SLE-Product-WE15-SP4-Pool for x86_64 SUSE Linux Enterprise Workstation Extension 15 SP4 x86_64 [sle-product-we15-sp4-pool-x86_64] [ ] SLE-Product-WE15-SP4-Updates for x86_64 SUSE Linux Enterprise Workstation Extension 15 SP4 x86_64 [sle-product-we15-sp4-updates-x86_64] [I] SLE15-SP4-Installer-Updates for x86_64 SUSE Linux Enterprise Server 15 SP4 x86_64 [sle15-sp4-installer-updates-x86_64] [ ] SLE-Product-SLES15-SP5-Pool for x86_64 SUSE Linux Enterprise Server 15 SP5 x86_64 [sle-product-sles15-sp5-pool-x86_64] [ ] SLE-Product-SLES15-SP6-Pool for x86_64 SUSE Linux Enterprise Server 15 SP6 x86_64 [sle-product-sles15-sp6-pool-x86_64] [ ] SUSE-MicroOS-5.2-Pool for x86_64 SUSE Linux Enterprise Micro 5.2 x86_64 [suse-microos-5.2-pool-x86_64]
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sle-product-sles15-sp4-pool-x86_64 synchronized in 15 seconds
Channel sle-product-sles15-sp4-pool-x86_64 finished syncing
WARN: Repository metadata for sle15-sp4-installer-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sle-product-sles15-sp4-updates-x86_64 synchronized in 4 seconds
Channel sle-product-sles15-sp4-updates-x86_64 finished syncing
WARN: Repository metadata for sle15-sp4-installer-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle15-sp4-installer-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
/var/cache/rhn/repodata/sles15-sp4-devel-uyuni-client-x86_64/*primary.xml.gz contains 0 packages
WARN: Repository metadata for sles15-sp4-devel-uyuni-client-x86_64 seems not synchronized. Even if the reposync log says it is.
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sle15-sp4-installer-updates-x86_64 synchronized in 16 seconds
Channel sle15-sp4-installer-updates-x86_64 finished syncing
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sles15-sp4-devel-uyuni-client-x86_64 synchronized in 31 seconds
Channel sles15-sp4-devel-uyuni-client-x86_64 finished syncing
1 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
2 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
3 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-module-basesystem15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-basesystem15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-basesystem15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-basesystem15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
4 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-module-basesystem15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-basesystem15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sle-module-basesystem15-sp4-pool-x86_64 synchronized in 296 seconds
Channel sle-module-basesystem15-sp4-pool-x86_64 finished syncing
5 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
6 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
7 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
8 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
9 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
10 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
11 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
12 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
13 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
14 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
15 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-module-basesystem15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-basesystem15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-basesystem15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-server-applications15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-basesystem15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-server-applications15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
16 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-module-basesystem15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-server-applications15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-basesystem15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-server-applications15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-basesystem15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-server-applications15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-basesystem15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-server-applications15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-basesystem15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-server-applications15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-server-applications15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-basesystem15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-server-applications15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-server-applications15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
17 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-module-basesystem15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-server-applications15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-server-applications15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sle-module-basesystem15-sp4-updates-x86_64 synchronized in 1344 seconds
Channel sle-module-basesystem15-sp4-updates-x86_64 finished syncing
WARN: Repository metadata for sle-module-server-applications15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-server-applications15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sle-module-server-applications15-sp4-pool-x86_64 synchronized in 42 seconds
Channel sle-module-server-applications15-sp4-pool-x86_64 finished syncing
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sle-module-server-applications15-sp4-updates-x86_64 synchronized in 119 seconds
Channel sle-module-server-applications15-sp4-updates-x86_64 finished syncing
18 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-module-desktop-applications15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-desktop-applications15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-desktop-applications15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sle-module-desktop-applications15-sp4-updates-x86_64 synchronized in 172 seconds
Channel sle-module-desktop-applications15-sp4-updates-x86_64 finished syncing
19 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
20 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-module-desktop-applications15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-desktop-applications15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
21 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-module-desktop-applications15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-desktop-applications15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-desktop-applications15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sle-module-desktop-applications15-sp4-pool-x86_64 synchronized in 253 seconds
Channel sle-module-desktop-applications15-sp4-pool-x86_64 finished syncing
22 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
23 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
24 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
25 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
26 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
27 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
28 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
29 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
30 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-module-devtools15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-devtools15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
31 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-module-devtools15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-devtools15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-devtools15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-devtools15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-devtools15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-devtools15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-devtools15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
32 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-module-devtools15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-devtools15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-containers15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-devtools15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-devtools15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-containers15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-devtools15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-devtools15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-containers15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-devtools15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sle-module-devtools15-sp4-updates-x86_64 synchronized in 858 seconds
Channel sle-module-devtools15-sp4-updates-x86_64 finished syncing
WARN: Repository metadata for sle-module-devtools15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sle-module-containers15-sp4-pool-x86_64 synchronized in 9 seconds
Channel sle-module-containers15-sp4-pool-x86_64 finished syncing
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sle-module-devtools15-sp4-pool-x86_64 synchronized in 116 seconds
Channel sle-module-devtools15-sp4-pool-x86_64 finished syncing
33 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sle-module-containers15-sp4-updates-x86_64 synchronized in 60 seconds
Channel sle-module-containers15-sp4-updates-x86_64 finished syncing
34 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
35 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
36 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
37 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
38 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
39 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
40 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
41 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
42 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
43 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
44 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
45 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
46 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
47 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
48 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
49 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
50 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
51 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-ltss-updates-x86_64 seems not synchronized. Even if the reposync log says it is.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 63ms

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

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

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

And I wait until all synchronized channels for "sles15-sp4" have finished 78m 31s 783ms Show Error + 
                                            
 FAIL: mgrctl cp server:/var/log/rhn/reposync.log /tmp/reposync.log returned status code = 1.
Output:
2:45PM INF Starting mgrctl cp server:/var/log/rhn/reposync.log /tmp/reposync.log
2:45PM ??? Error: 1 error occurred:
	* copying to host: error during bulk transfer for copier.request{Request:"PUT", Root:"/", preservedRoot:"/tmp", rootPrefix:"/tmp", Directory:"/", preservedDirectory:"/tmp", Globs:[]string{}, preservedGlobs:[]string{}, StatOptions:copier.StatOptions{CheckForArchives:false, Excludes:[]string(nil)}, GetOptions:copier.GetOptions{UIDMap:[]idtools.IDMap(nil), GIDMap:[]idtools.IDMap(nil), Excludes:[]string(nil), ExpandArchives:false, ChownDirs:(*idtools.IDPair)(nil), ChmodDirs:(*fs.FileMode)(nil), ChownFiles:(*idtools.IDPair)(nil), ChmodFiles:(*fs.FileMode)(nil), StripSetuidBit:false, StripSetgidBit:false, StripStickyBit:false, StripXattrs:false, KeepDirectoryNames:false, Rename:map[string]string(nil), NoDerefSymlinks:false, IgnoreUnreadable:false, NoCrossDevice:false}, PutOptions:copier.PutOptions{UIDMap:[]idtools.IDMap(nil), GIDMap:[]idtools.IDMap(nil), DefaultDirOwner:(*idtools.IDPair)(nil), DefaultDirMode:(*fs.FileMode)(nil), ChownDirs:(*idtools.IDPair)(0xc0004775c0), ChmodDirs:(*fs.FileMode)(nil), ChownFiles:(*idtools.IDPair)(0xc0004775d0), ChmodFiles:(*fs.FileMode)(nil), StripSetuidBit:false, StripSetgidBit:false, StripStickyBit:false, StripXattrs:false, IgnoreXattrErrors:false, IgnoreDevices:true, NoOverwriteDirNonDir:true, NoOverwriteNonDirDir:true, Rename:map[string]string{"reposync.log":"reposync.log"}}, MkdirOptions:copier.MkdirOptions{UIDMap:[]idtools.IDMap(nil), GIDMap:[]idtools.IDMap(nil), ChownNew:(*idtools.IDPair)(nil), ChmodNew:(*fs.FileMode)(nil)}, RemoveOptions:copier.RemoveOptions{All:false}}: copier: put: error creating "/reposync.log": copier: put: error opening file "/reposync.log" for writing: open /reposync.log: no space left on device
 (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 355ms Show Error + 
                                            
 FAIL: mgrctl exec -i 'tail -n20 /var/log/rhn/rhn_web_ui.log | awk -v limit="$(date --date="5 minutes ago" "+%Y-%m-%d %H:%M:%S")" " $0 ) limit"' returned status code = 255.
Output:
 (ScriptError)
./features/support/remote_node.rb:132:in `run_local'
./features/support/remote_node.rb:116:in `run'
./features/support/env.rb:746:in `print_server_logs'
./features/support/env.rb:165:in `After'
Show Info + 
13:26:22:000 - 14:45:21: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
34s 363ms 5 1 2

Given I am authorized for the "Admin" section 10s 526ms

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

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

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

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

And I select "250" from "pageSize" 11s 23ms Show Error + 
                                            
 Unable to find xpath "//*[contains(@class, 'data-testid-pageSize-child__control')]" (Capybara::ElementNotFound)
./features/step_definitions/navigation_steps.rb:182:in `/^I select "([^"]*)" from "([^"]*)"$/'
features/reposync/srv_sync_products.feature:250:in `I select "250" from "pageSize"'

And I should only see success signs in the product list 0s

12s 493ms Show Error + 
                                            
 FAIL: mgrctl exec -i 'tail -n20 /var/log/rhn/rhn_web_ui.log | awk -v limit="$(date --date="5 minutes ago" "+%Y-%m-%d %H:%M:%S")" " $0 ) limit"' returned status code = 255.
Output:
 (ScriptError)
./features/support/remote_node.rb:132:in `run_local'
./features/support/remote_node.rb:116:in `run'
./features/support/env.rb:746:in `print_server_logs'
./features/support/env.rb:165:in `After'
Show Info + 
14:45:35:000 - 14:45:57: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 1m 3s 650ms 9 2 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
10s 507ms 1

Given I am authorized for the "Admin" section 10s 507ms

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

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

And I follow "Create Channel" 291ms

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

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

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

And I click on "Create Channel" 543ms

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

Scenario:
Add a fake child channel into the fake base channel x86_64
866ms 10

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

And I follow "Create Channel" 272ms

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

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

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

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

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

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

And I click on "Create Channel" 52ms

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

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

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

And I follow "Create Channel" 323ms

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

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

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

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

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

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

And I click on "Create Channel" 52ms

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

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

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

And I follow "Create Channel" 317ms

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

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

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

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

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

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

And I click on "Create Channel" 454ms

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

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

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

And I follow "Create Channel" 223ms

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

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

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

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

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

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

And I click on "Create Channel" 53ms

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

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

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

And I follow "Create Channel" 308ms

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

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

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

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

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

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

And I click on "Create Channel" 443ms

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

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

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

And I follow "Create Channel" 237ms

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

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:" 33ms

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

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

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

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

And I follow "Create Channel" 229ms

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

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

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

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

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

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

And I uncheck "gpg_check" 10s 79ms

And I click on "Create Channel" 477ms

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

@rhlike_minion
Scenario:
Add a RedHat-like base channel
23s 616ms 9 2

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

And I follow "Create Channel" 321ms

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

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

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

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

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

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

And I click on "Create Channel" 428ms

Then I should see a "Channel Fake-Base-Channel-RH-like created." text 10s 20ms Show Error + 
                                            
 Text 'Channel Fake-Base-Channel-RH-like created.' not found (ScriptError)
./features/step_definitions/navigation_steps.rb:641:in `/^I should see a "([^"]*)" text$/'
features/reposync/srv_create_fake_channels.feature:160:in `I should see a "Channel Fake-Base-Channel-RH-like created." text'

12s 416ms Show Error + 
                                            
 FAIL: mgrctl exec -i 'tail -n20 /var/log/rhn/rhn_web_ui.log | awk -v limit="$(date --date="5 minutes ago" "+%Y-%m-%d %H:%M:%S")" " $0 ) limit"' returned status code = 255.
Output:
 (ScriptError)
./features/support/remote_node.rb:132:in `run_local'
./features/support/remote_node.rb:116:in `run'
./features/support/env.rb:746:in `print_server_logs'
./features/support/env.rb:165:in `After'
Show Info + 
14:46:44:000 - 14:46:55:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/manage/Edit.do
Screenshot +

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

When I follow the left menu "Software > Manage > Channels" 10s 11ms Show Error + 
                                            
 Unable to find xpath "//aside/div[@id='nav']/nav/ul/li/div/a[contains(.,'Software')]/parent::div/parent::li" (Capybara::ElementNotFound)
./features/step_definitions/navigation_steps.rb:393:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:385:in `each'
./features/step_definitions/navigation_steps.rb:385:in `each_with_index'
./features/step_definitions/navigation_steps.rb:385:in `/^I follow the left menu "([^"]*)"$/'
features/reposync/srv_create_fake_channels.feature:164:in `I follow the left menu "Software ) Manage ) Channels"'

And I follow "Create Channel" 0s

And I enter "Fake-Base-Channel-AppStream" as "Channel Name" 0s

And I enter "fake-base-channel-appstream" as "Channel Label" 0s

And I select "None" from "Parent Channel" 0s

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

And I enter "Fake-Base-Channel-AppStream for testing" as "Channel Summary" 0s

And I enter "Description for Fake-Base-Channel-AppStream." as "Channel Description" 0s

And I click on "Create Channel" 0s

Then I should see a "Channel Fake-Base-Channel-AppStream created." text 0s

Feature:Create fake repositories for each fake child channel 1m 42s 769ms 12 2 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
10s 606ms 1

Given I am authorized for the "Admin" section 10s 606ms

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

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

And I follow "Create Repository" 342ms

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

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

And I click on "Create Repository" 410ms

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

And I should see "metadataSigned" as checked 20ms

Scenario:
Disable metadata check for the fake RPM repository
11s 13ms 6

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

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

And I uncheck "metadataSigned" 10s 83ms

And I click on "Update Repository" 506ms

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

And I should see "metadataSigned" as unchecked 14ms

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

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

And I follow "Create Repository" 271ms

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

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

And I click on "Create Repository" 405ms

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

And I should see "metadataSigned" as checked 14ms

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

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

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

And I uncheck "metadataSigned" 10s 59ms

And I click on "Update Repository" 494ms

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

And I should see "metadataSigned" as unchecked 15ms

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

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

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

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

And I click on "Update Channel" 552ms

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

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

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

And I click on "Save Repositories" 762ms

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

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

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

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

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

And I click on "Update Channel" 468ms

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

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

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

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

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
23s 148ms 2 7 1

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

And I follow "Fake-Base-Channel-RH-like" 10s 7ms Show Error + 
                                            
 Unable to find link "Fake-Base-Channel-RH-like" (Capybara::ElementNotFound)
./features/support/commonlib.rb:194:in `click_link_and_wait'
./features/step_definitions/navigation_steps.rb:318:in `/^I follow "([^"]*)"$/'
features/reposync/srv_create_fake_repositories.feature:78:in `I follow "Fake-Base-Channel-RH-like"'

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-Base-Channel-RH-like 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-Base-Channel-RH-like repository information was successfully updated" text 0s

13s 75ms Show Info + 
14:48:24:000 - 14:48:34:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/manage/Manage.do
Screenshot +

@rhlike_minion
Scenario:
Add the fake AppStream repository to the AppStream base channel
23s 80ms 2 7 1

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

And I follow "Fake-Base-Channel-AppStream" 10s 16ms Show Error + 
                                            
 Unable to find link "Fake-Base-Channel-AppStream" (Capybara::ElementNotFound)
./features/support/commonlib.rb:194:in `click_link_and_wait'
./features/step_definitions/navigation_steps.rb:318:in `/^I follow "([^"]*)"$/'
features/reposync/srv_create_fake_repositories.feature:90:in `I follow "Fake-Base-Channel-AppStream"'

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-Base-Channel-AppStream updated" text 0s

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

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

And I click on "Save Repositories" 0s

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

12s 977ms Show Info + 
14:48:47:000 - 14:48:57:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/manage/Manage.do
Screenshot +

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

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

And I follow "Create Repository" 275ms

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

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

And I uncheck "metadataSigned" 10s 68ms

And I click on "Create Repository" 402ms

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

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

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

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

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

And I click on "Update Channel" 469ms

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

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

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

And I click on "Save Repositories" 581ms

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

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

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

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

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

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

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

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

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

And I follow "Create Repository" 289ms

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

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

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

And I click on "Create Repository" 53ms

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

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

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

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

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

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

And I click on "Save Repositories" 873ms

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

@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 1m 380ms 7 2

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

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

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

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

And I follow "Create Channel" 325ms

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

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

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

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

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

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

And I click on "Create Channel" 60ms

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

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

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

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

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

And I follow "Create Channel" 306ms

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

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

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

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

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

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

And I click on "Create Channel" 438ms

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

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

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

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

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

And I follow "Create Channel" 230ms

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

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

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

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

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

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

And I click on "Create Channel" 494ms

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

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

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

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

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

And I follow "Create Channel" 266ms

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

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

And I select "Fake-Base-Channel-RH-like" from "Parent Channel" 11s 19ms Show Error + 
                                            
 Unable to find xpath "//*[contains(@class, 'data-testid-Parent Channel-child__control')]" (Capybara::ElementNotFound)
./features/step_definitions/navigation_steps.rb:182:in `/^I select "([^"]*)" from "([^"]*)"$/'
features/reposync/srv_create_devel_channels.feature:72:in `I select "Fake-Base-Channel-RH-like" from "Parent Channel"'

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

And I enter "Devel-RH-like-Channel for development repositories" as "Channel Summary" 0s

And I enter "Channel containing development repositories" as "Channel Description" 0s

And I click on "Create Channel" 0s

Then I should see a "Channel Devel-RH-like-Channel created." text 0s

12s 863ms Show Info + 
14:49:51:000 - 14:50:03:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/manage/Edit.do
Screenshot +

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

When I prepare the development repositories of "rhlike_minion" as part of "devel-rh-like-channel" channel 2s 935ms Show Error + 
                                            
 unknown error - API failure: No such channel: devel-rh-like-channel (SystemCallError)
./features/support/http_client.rb:110:in `call'
./features/support/api_test.rb:95:in `make_api_call'
./features/support/api_test.rb:65:in `block (2 levels) in call'
./features/support/api_test.rb:62:in `synchronize'
./features/support/api_test.rb:62:in `block in call'
features/reposync/srv_create_devel_channels.feature:81:in `I prepare the development repositories of "rhlike_minion" as part of "devel-rh-like-channel" channel'

12s 791ms Show Info + 
14:50:16:000 - 14:50:19:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/manage/Edit.do
Screenshot +

Feature:Synchronize fake channels 43m 55s 884ms 4 8 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 196ms 2

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

And I enable source package syncing 821ms

@sle_minion
Scenario:
Synchronize Fake-RPM-SUSE-Channel channel
2m 15s 812ms 9 1

WARN: Repository metadata for fake-rpm-suse-channel seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-rpm-suse-channel seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-rpm-suse-channel seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-rpm-suse-channel seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-rpm-suse-channel seems not synchronized. Even if the reposync log says it is.
1 minutes out of 2 waiting for 'fake-rpm-suse-channel' channel to be synchronized
WARN: Repository metadata for fake-rpm-suse-channel seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-rpm-suse-channel seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-rpm-suse-channel seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-rpm-suse-channel seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-rpm-suse-channel seems not synchronized. Even if the reposync log says it is.
execution expired

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

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

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

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

And I follow "Sync" 270ms

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

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

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

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'

12s 976ms Show Info + 
14:50:33:000 - 14:52: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 25s 413ms 2 1

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

And solver file for "fake-rpm-suse-channel" should reference "orion-dummy-1.1-1.1.x86_64.rpm" 10m 134ms 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 276ms Show Info + 
14:52:49:000 - 15:03:02: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 17s 469ms 9 1

WARN: Repository metadata for fake-child-channel-i586 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-child-channel-i586 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-child-channel-i586 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-child-channel-i586 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-child-channel-i586 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-child-channel-i586 seems not synchronized. Even if the reposync log says it is.
1 minutes out of 5 waiting for 'fake-child-channel-i586' channel to be synchronized
WARN: Repository metadata for fake-child-channel-i586 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-child-channel-i586 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-child-channel-i586 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-child-channel-i586 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-child-channel-i586 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-child-channel-i586 seems not synchronized. Even if the reposync log says it is.
2 minutes out of 5 waiting for 'fake-child-channel-i586' channel to be synchronized
WARN: Repository metadata for fake-child-channel-i586 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-child-channel-i586 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-child-channel-i586 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-child-channel-i586 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-child-channel-i586 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-child-channel-i586 seems not synchronized. Even if the reposync log says it is.
3 minutes out of 5 waiting for 'fake-child-channel-i586' channel to be synchronized
WARN: Repository metadata for fake-child-channel-i586 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-child-channel-i586 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-child-channel-i586 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-child-channel-i586 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-child-channel-i586 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-child-channel-i586 seems not synchronized. Even if the reposync log says it is.
4 minutes out of 5 waiting for 'fake-child-channel-i586' channel to be synchronized
WARN: Repository metadata for fake-child-channel-i586 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-child-channel-i586 seems not synchronized. Even if the reposync log says it is.
execution expired

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

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

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

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

And I follow "Sync" 1s 140ms

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

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

And I wait until the channel "fake-child-channel-i586" has been synced 5m 238ms 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'

13s 131ms Show Info + 
15:03:15:000 - 15:08:20: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 17s 202ms 9 1

WARN: Repository metadata for test-child-channel-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for test-child-channel-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for test-child-channel-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for test-child-channel-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for test-child-channel-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for test-child-channel-x86_64 seems not synchronized. Even if the reposync log says it is.
1 minutes out of 6 waiting for 'test-child-channel-x86_64' channel to be synchronized
WARN: Repository metadata for test-child-channel-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for test-child-channel-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for test-child-channel-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for test-child-channel-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for test-child-channel-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for test-child-channel-x86_64 seems not synchronized. Even if the reposync log says it is.
2 minutes out of 6 waiting for 'test-child-channel-x86_64' channel to be synchronized
WARN: Repository metadata for test-child-channel-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for test-child-channel-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for test-child-channel-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for test-child-channel-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for test-child-channel-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for test-child-channel-x86_64 seems not synchronized. Even if the reposync log says it is.
3 minutes out of 6 waiting for 'test-child-channel-x86_64' channel to be synchronized
WARN: Repository metadata for test-child-channel-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for test-child-channel-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for test-child-channel-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for test-child-channel-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for test-child-channel-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for test-child-channel-x86_64 seems not synchronized. Even if the reposync log says it is.
4 minutes out of 6 waiting for 'test-child-channel-x86_64' channel to be synchronized
WARN: Repository metadata for test-child-channel-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for test-child-channel-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for test-child-channel-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for test-child-channel-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for test-child-channel-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for test-child-channel-x86_64 seems not synchronized. Even if the reposync log says it is.
5 minutes out of 6 waiting for 'test-child-channel-x86_64' channel to be synchronized
WARN: Repository metadata for test-child-channel-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for test-child-channel-x86_64 seems not synchronized. Even if the reposync log says it is.
execution expired

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

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

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

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

And I follow "Sync" 1s 101ms

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

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 116ms Show Info + 
15:08:33:000 - 15:14:38: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
6s 191ms 9

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

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

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

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

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

And I follow "Sync" 1s 131ms

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

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

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

@deblike_minion
Scenario:
Synchronize Fake-Base-Channel-Debian-like channel
5m 16s 430ms 9 1

WARN: Repository metadata for fake-base-channel-debian-like seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-base-channel-debian-like seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-base-channel-debian-like seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-base-channel-debian-like seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-base-channel-debian-like seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-base-channel-debian-like seems not synchronized. Even if the reposync log says it is.
1 minutes out of 5 waiting for 'fake-base-channel-debian-like' channel to be synchronized
WARN: Repository metadata for fake-base-channel-debian-like seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-base-channel-debian-like seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-base-channel-debian-like seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-base-channel-debian-like seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-base-channel-debian-like seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-base-channel-debian-like seems not synchronized. Even if the reposync log says it is.
2 minutes out of 5 waiting for 'fake-base-channel-debian-like' channel to be synchronized
WARN: Repository metadata for fake-base-channel-debian-like seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-base-channel-debian-like seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-base-channel-debian-like seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-base-channel-debian-like seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-base-channel-debian-like seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-base-channel-debian-like seems not synchronized. Even if the reposync log says it is.
3 minutes out of 5 waiting for 'fake-base-channel-debian-like' channel to be synchronized
WARN: Repository metadata for fake-base-channel-debian-like seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-base-channel-debian-like seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-base-channel-debian-like seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-base-channel-debian-like seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-base-channel-debian-like seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-base-channel-debian-like seems not synchronized. Even if the reposync log says it is.
4 minutes out of 5 waiting for 'fake-base-channel-debian-like' channel to be synchronized
WARN: Repository metadata for fake-base-channel-debian-like seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for fake-base-channel-debian-like seems not synchronized. Even if the reposync log says it is.
execution expired

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

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

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

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

And I follow "Sync" 294ms

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

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

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'

13s 229ms Show Info + 
15:14:59:000 - 15:20:03: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
23s 534ms 3 6 1

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

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

And I follow "Fake-Base-Channel-RH-like" 10s 8ms Show Error + 
                                            
 Unable to find link "Fake-Base-Channel-RH-like" (Capybara::ElementNotFound)
./features/support/commonlib.rb:194:in `click_link_and_wait'
./features/step_definitions/navigation_steps.rb:318:in `/^I follow "([^"]*)"$/'
features/reposync/srv_sync_fake_channels.feature:89:in `I follow "Fake-Base-Channel-RH-like"'

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-Base-Channel-RH-like." text 0s

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

12s 959ms Show Info + 
15:20:16:000 - 15:20:28:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/manage/Manage.do
Screenshot +

@rhlike_minion
Scenario:
Synchronize Fake-Base-Channel-AppStream channel
23s 685ms 3 6 1

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

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

And I follow "Fake-Base-Channel-AppStream" 10s 11ms Show Error + 
                                            
 Unable to find link "Fake-Base-Channel-AppStream" (Capybara::ElementNotFound)
./features/support/commonlib.rb:194:in `click_link_and_wait'
./features/step_definitions/navigation_steps.rb:318:in `/^I follow "([^"]*)"$/'
features/reposync/srv_sync_fake_channels.feature:101:in `I follow "Fake-Base-Channel-AppStream"'

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-Base-Channel-AppStream." text 0s

And I wait until the channel "fake-base-channel-appstream" has been synced 0s

13s 73ms Show Info + 
15:20:40:000 - 15:20:52:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/manage/Manage.do
Screenshot +

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

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

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

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

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

And I follow "Sync" 0s

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

And I click on "Sync Now" 0s

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

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

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

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

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

Scenario:
Refresh the errata cache
5s 450ms 6

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

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

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

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

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

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

Scenario:
Refresh the channel's repository data
13m 23s 26ms 5 1

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

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

And I follow "channel-repodata-bunch" 345ms

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

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

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 13m 20s Show Error + 
                                            
 execution expired (Timeout::Error)
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/step_definitions/navigation_steps.rb:763:in `/^I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows$/'
features/reposync/srv_sync_fake_channels.feature:144:in `I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows'

Scenario:
Cleanup disable source package syncing
471ms 1

Then I disable source package syncing 471ms

@skip_if_github_validation
Feature:Synchronize development channels 1s 525ms 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
360ms 8 1

Given I am authorized for the "Admin" section 360ms Show Error + 
                                            
 undefined method `map' for nil (NoMethodError)
./features/step_definitions/navigation_steps.rb:573:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:439:in `/^I am authorized for the "([^"]*)" section$/'
features/reposync/srv_sync_devel_channels.feature:12:in `I am authorized for the "Admin" section'

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

And I follow "Devel-SUSE-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 Devel-SUSE-Channel." text 0s

And I wait until the channel "devel-suse-channel" has been synced 0s

@deblike_minion
Scenario:
Synchronize Devel-Debian-like-Channel channel
408ms 8 1

Given I am authorized for the "Admin" section 408ms Show Error + 
                                            
 undefined method `map' for nil (NoMethodError)
./features/step_definitions/navigation_steps.rb:573:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:439:in `/^I am authorized for the "([^"]*)" section$/'
features/reposync/srv_sync_devel_channels.feature:24:in `I am authorized for the "Admin" section'

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

And I follow "Devel-Debian-like-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 Devel-Debian-like-Channel." text 0s

And I wait until the channel "devel-debian-like-channel" has been synced 0s

@rhlike_minion
Scenario:
Synchronize Devel-RH-like-Channel channel
389ms 8 1

Given I am authorized for the "Admin" section 389ms Show Error + 
                                            
 undefined method `map' for nil (NoMethodError)
./features/step_definitions/navigation_steps.rb:573:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:439:in `/^I am authorized for the "([^"]*)" section$/'
features/reposync/srv_sync_devel_channels.feature:36:in `I am authorized for the "Admin" section'

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

And I follow "Devel-RH-like-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 Devel-RH-like-Channel." text 0s

And I wait until the channel "devel-rh-like-channel" has been synced 0s

@build_host @uyuni
Scenario:
Synchronize Devel-Build-Host-Channel channel
366ms 8 1

Given I am authorized for the "Admin" section 366ms Show Error + 
                                            
 undefined method `map' for nil (NoMethodError)
./features/step_definitions/navigation_steps.rb:573:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:439:in `/^I am authorized for the "([^"]*)" section$/'
features/reposync/srv_sync_devel_channels.feature:49:in `I am authorized for the "Admin" section'

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

And I follow "Devel-Build-Host-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 Devel-Build-Host-Channel." text 0s

And I wait until the channel "devel-build-host-channel" has been synced 0s

Feature:Create activation keys 3s 320ms 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
346ms 1

Given I am authorized for the "Admin" section 346ms Show Error + 
                                            
 undefined method `map' for nil (NoMethodError)
./features/step_definitions/navigation_steps.rb:573:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:439:in `/^I am authorized for the "([^"]*)" section$/'
features/reposync/srv_create_activationkey.feature:36:in `I am authorized for the "Admin" section'

Scenario:
Create an activation key with a channel
376ms 12 1

The browser session could not be cleaned because there is no browser available: undefined method `first' for an instance of String

When I follow the left menu "Systems > Activation Keys" 376ms Show Error + 
                                            
 undefined method `map' for nil (NoMethodError)
./features/step_definitions/navigation_steps.rb:573:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:439:in `/^I am authorized for the "([^"]*)" section$/'
./features/step_definitions/navigation_steps.rb:399:in `rescue in block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:392:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:385:in `each'
./features/step_definitions/navigation_steps.rb:385:in `each_with_index'
./features/step_definitions/navigation_steps.rb:385:in `/^I follow the left menu "([^"]*)"$/'
features/reposync/srv_create_activationkey.feature:39:in `I follow the left menu "Systems ) Activation Keys"'

And I follow "Create Key" 0s

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

And I enter "SUSE Test Key x86_64" as "description" 0s

And I enter "SUSE-KEY-x86_64" as "key" 0s

And I enter "20" as "usageLimit" 0s

And I click on "Create Activation Key" 0s

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

And I should see a "Details" link 0s

And I should see a "Packages" link 0s

And I should see a "Configuration" link in the content area 0s

And I should see a "Groups" link 0s

And I should see a "Activated Systems" link 0s

@rhlike_minion
Scenario:
Create an activation key for RedHat-like minion
363ms 7 1

The browser session could not be cleaned because there is no browser available: undefined method `first' for an instance of String

When I follow the left menu "Systems > Activation Keys" 363ms Show Error + 
                                            
 undefined method `map' for nil (NoMethodError)
./features/step_definitions/navigation_steps.rb:573:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:439:in `/^I am authorized for the "([^"]*)" section$/'
./features/step_definitions/navigation_steps.rb:399:in `rescue in block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:392:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:385:in `each'
./features/step_definitions/navigation_steps.rb:385:in `each_with_index'
./features/step_definitions/navigation_steps.rb:385:in `/^I follow the left menu "([^"]*)"$/'
features/reposync/srv_create_activationkey.feature:55:in `I follow the left menu "Systems ) Activation Keys"'

And I follow "Create Key" 0s

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

And I enter "RedHat like Test Key" as "description" 0s

And I enter "RH-LIKE-KEY" as "key" 0s

And I select "Fake-Base-Channel-RH-like" from "selectedBaseChannel" 0s

And I click on "Create Activation Key" 0s

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

@deblike_minion
Scenario:
Create an activation key for Debian-like minion
365ms 7 1

The browser session could not be cleaned because there is no browser available: undefined method `first' for an instance of String

When I follow the left menu "Systems > Activation Keys" 365ms Show Error + 
                                            
 undefined method `map' for nil (NoMethodError)
./features/step_definitions/navigation_steps.rb:573:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:439:in `/^I am authorized for the "([^"]*)" section$/'
./features/step_definitions/navigation_steps.rb:399:in `rescue in block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:392:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:385:in `each'
./features/step_definitions/navigation_steps.rb:385:in `each_with_index'
./features/step_definitions/navigation_steps.rb:385:in `/^I follow the left menu "([^"]*)"$/'
features/reposync/srv_create_activationkey.feature:66:in `I follow the left menu "Systems ) Activation Keys"'

And I follow "Create Key" 0s

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

And I enter "Debian-like Test Key" as "description" 0s

And I enter "DEBLIKE-KEY" as "key" 0s

And I select "Fake-Base-Channel-Debian-like" from "selectedBaseChannel" 0s

And I click on "Create Activation Key" 0s

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

Scenario:
Create an activation key with a channel for salt-ssh
358ms 8 1

The browser session could not be cleaned because there is no browser available: undefined method `first' for an instance of String

When I follow the left menu "Systems > Activation Keys" 358ms Show Error + 
                                            
 undefined method `map' for nil (NoMethodError)
./features/step_definitions/navigation_steps.rb:573:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:439:in `/^I am authorized for the "([^"]*)" section$/'
./features/step_definitions/navigation_steps.rb:399:in `rescue in block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:392:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:385:in `each'
./features/step_definitions/navigation_steps.rb:385:in `each_with_index'
./features/step_definitions/navigation_steps.rb:385:in `/^I follow the left menu "([^"]*)"$/'
features/reposync/srv_create_activationkey.feature:76:in `I follow the left menu "Systems ) Activation Keys"'

And I follow "Create Key" 0s

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

And I enter "SUSE SSH Test Key x86_64" as "description" 0s

And I enter "SUSE-SSH-KEY-x86_64" as "key" 0s

And I enter "20" as "usageLimit" 0s

And I select "Push via SSH" from "contact-method" 0s

And I click on "Create Activation Key" 0s

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

Scenario:
Create an activation key with a channel for salt-ssh via tunnel
386ms 7 1

The browser session could not be cleaned because there is no browser available: undefined method `first' for an instance of String

When I follow the left menu "Systems > Activation Keys" 386ms Show Error + 
                                            
 undefined method `map' for nil (NoMethodError)
./features/step_definitions/navigation_steps.rb:573:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:439:in `/^I am authorized for the "([^"]*)" section$/'
./features/step_definitions/navigation_steps.rb:399:in `rescue in block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:392:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:385:in `each'
./features/step_definitions/navigation_steps.rb:385:in `each_with_index'
./features/step_definitions/navigation_steps.rb:385:in `/^I follow the left menu "([^"]*)"$/'
features/reposync/srv_create_activationkey.feature:87:in `I follow the left menu "Systems ) Activation Keys"'

And I follow "Create Key" 0s

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

And I enter "SUSE SSH Tunnel Test Key x86_64" as "description" 0s

And I enter "SUSE-SSH-TUNNEL-KEY-x86_64" as "key" 0s

And I enter "20" as "usageLimit" 0s

And I select "Push via SSH tunnel" from "contact-method" 0s

And I click on "Create Activation Key" 0s

Scenario:
Create an activation key for the proxy
366ms 6 1

The browser session could not be cleaned because there is no browser available: undefined method `first' for an instance of String

When I follow the left menu "Systems > Activation Keys" 366ms Show Error + 
                                            
 undefined method `map' for nil (NoMethodError)
./features/step_definitions/navigation_steps.rb:573:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:439:in `/^I am authorized for the "([^"]*)" section$/'
./features/step_definitions/navigation_steps.rb:399:in `rescue in block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:392:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:385:in `each'
./features/step_definitions/navigation_steps.rb:385:in `each_with_index'
./features/step_definitions/navigation_steps.rb:385:in `/^I follow the left menu "([^"]*)"$/'
features/reposync/srv_create_activationkey.feature:97:in `I follow the left menu "Systems ) Activation Keys"'

And I follow "Create Key" 0s

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

And I enter "Proxy Key x86_64" as "description" 0s

And I enter "PROXY-KEY-x86_64" as "key" 0s

And I click on "Create Activation Key" 0s

Then I wait until I see "Activation key Proxy Key x86_64 has been created" text 0s

Scenario:
Create an activation key for the build host
370ms 8 1

The browser session could not be cleaned because there is no browser available: undefined method `first' for an instance of String

When I follow the left menu "Systems > Activation Keys" 370ms Show Error + 
                                            
 undefined method `map' for nil (NoMethodError)
./features/step_definitions/navigation_steps.rb:573:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:439:in `/^I am authorized for the "([^"]*)" section$/'
./features/step_definitions/navigation_steps.rb:399:in `rescue in block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:392:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:385:in `each'
./features/step_definitions/navigation_steps.rb:385:in `each_with_index'
./features/step_definitions/navigation_steps.rb:385:in `/^I follow the left menu "([^"]*)"$/'
features/reposync/srv_create_activationkey.feature:106:in `I follow the left menu "Systems ) Activation Keys"'

And I follow "Create Key" 0s

And I wait for child channels to appear 0s

And I enter "Build host Key x86_64" as "description" 0s

And I enter "BUILD-HOST-KEY-x86_64" as "key" 0s

And I check "Container Build Host" 0s

And I check "OS Image Build Host" 0s

And I click on "Create Activation Key" 0s

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

@scc_credentials
Scenario:
Create an activation key for the terminal
387ms 6 1

The browser session could not be cleaned because there is no browser available: undefined method `first' for an instance of String

When I follow the left menu "Systems > Activation Keys" 387ms Show Error + 
                                            
 undefined method `map' for nil (NoMethodError)
./features/step_definitions/navigation_steps.rb:573:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:439:in `/^I am authorized for the "([^"]*)" section$/'
./features/step_definitions/navigation_steps.rb:399:in `rescue in block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:392:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:385:in `each'
./features/step_definitions/navigation_steps.rb:385:in `each_with_index'
./features/step_definitions/navigation_steps.rb:385:in `/^I follow the left menu "([^"]*)"$/'
features/reposync/srv_create_activationkey.feature:118:in `I follow the left menu "Systems ) Activation Keys"'

And I follow "Create Key" 0s

And I wait for child channels to appear 0s

And I enter "Terminal Key x86_64" as "description" 0s

And I enter "TERMINAL-KEY-x86_64" as "key" 0s

And I click on "Create Activation Key" 0s

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

Feature:Update activation keys 4s 134ms 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
356ms 1

Given I am authorized for the "Admin" section 356ms Show Error + 
                                            
 undefined method `map' for nil (NoMethodError)
./features/step_definitions/navigation_steps.rb:573:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:439:in `/^I am authorized for the "([^"]*)" section$/'
features/reposync/allcli_update_activationkeys.feature:10:in `I am authorized for the "Admin" section'

@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
365ms 9 1

The browser session could not be cleaned because there is no browser available: undefined method `first' for an instance of String

When I follow the left menu "Systems > Activation Keys" 365ms Show Error + 
                                            
 undefined method `map' for nil (NoMethodError)
./features/step_definitions/navigation_steps.rb:573:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:439:in `/^I am authorized for the "([^"]*)" section$/'
./features/step_definitions/navigation_steps.rb:399:in `rescue in block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:392:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:385:in `each'
./features/step_definitions/navigation_steps.rb:385:in `each_with_index'
./features/step_definitions/navigation_steps.rb:385:in `/^I follow the left menu "([^"]*)"$/'
features/reposync/allcli_update_activationkeys.feature:40:in `I follow the left menu "Systems ) Activation Keys"'

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

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

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

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

And I check "Uyuni Client Tools for openSUSE Leap 15.6 (x86_64) (Development)" 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

@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
378ms 9 1

The browser session could not be cleaned because there is no browser available: undefined method `first' for an instance of String

When I follow the left menu "Systems > Activation Keys" 378ms Show Error + 
                                            
 undefined method `map' for nil (NoMethodError)
./features/step_definitions/navigation_steps.rb:573:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:439:in `/^I am authorized for the "([^"]*)" section$/'
./features/step_definitions/navigation_steps.rb:399:in `rescue in block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:392:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:385:in `each'
./features/step_definitions/navigation_steps.rb:385:in `each_with_index'
./features/step_definitions/navigation_steps.rb:385:in `/^I follow the left menu "([^"]*)"$/'
features/reposync/allcli_update_activationkeys.feature:73:in `I follow the left menu "Systems ) Activation Keys"'

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

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

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

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

And I check "Uyuni Client Tools for openSUSE Leap 15.6 (x86_64) (Development)" 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

@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
356ms 9 1

The browser session could not be cleaned because there is no browser available: undefined method `first' for an instance of String

When I follow the left menu "Systems > Activation Keys" 356ms Show Error + 
                                            
 undefined method `map' for nil (NoMethodError)
./features/step_definitions/navigation_steps.rb:573:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:439:in `/^I am authorized for the "([^"]*)" section$/'
./features/step_definitions/navigation_steps.rb:399:in `rescue in block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:392:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:385:in `each'
./features/step_definitions/navigation_steps.rb:385:in `each_with_index'
./features/step_definitions/navigation_steps.rb:385:in `/^I follow the left menu "([^"]*)"$/'
features/reposync/allcli_update_activationkeys.feature:106:in `I follow the left menu "Systems ) Activation Keys"'

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

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

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

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

And I check "Uyuni Client Tools for openSUSE Leap 15.6 (x86_64) (Development)" 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

@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
365ms 19 1

The browser session could not be cleaned because there is no browser available: undefined method `first' for an instance of String

When I follow the left menu "Systems > Activation Keys" 365ms Show Error + 
                                            
 undefined method `map' for nil (NoMethodError)
./features/step_definitions/navigation_steps.rb:573:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:439:in `/^I am authorized for the "([^"]*)" section$/'
./features/step_definitions/navigation_steps.rb:399:in `rescue in block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:392:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:385:in `each'
./features/step_definitions/navigation_steps.rb:385:in `each_with_index'
./features/step_definitions/navigation_steps.rb:385:in `/^I follow the left menu "([^"]*)"$/'
features/reposync/allcli_update_activationkeys.feature:169:in `I follow the left menu "Systems ) Activation Keys"'

And I follow "Build host 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 "build_host" 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 click on "Update Activation Key" 0s

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

@scc_credentials @uyuni
Scenario:
Update build host key with Uyuni client tools
379ms 8 1

The browser session could not be cleaned because there is no browser available: undefined method `first' for an instance of String

When I follow the left menu "Systems > Activation Keys" 379ms Show Error + 
                                            
 undefined method `map' for nil (NoMethodError)
./features/step_definitions/navigation_steps.rb:573:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:439:in `/^I am authorized for the "([^"]*)" section$/'
./features/step_definitions/navigation_steps.rb:399:in `rescue in block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:392:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:385:in `each'
./features/step_definitions/navigation_steps.rb:385:in `each_with_index'
./features/step_definitions/navigation_steps.rb:385:in `/^I follow the left menu "([^"]*)"$/'
features/reposync/allcli_update_activationkeys.feature:193:in `I follow the left menu "Systems ) Activation Keys"'

And I follow "Build host 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 "build_host" from "selectedBaseChannel" 0s

And I wait for child channels to appear 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 Build host Key x86_64 has been modified" text 0s

@skip_if_github_validation @scc_credentials @uyuni
Scenario:
Update build host key with dev child channel
393ms 8 1

The browser session could not be cleaned because there is no browser available: undefined method `first' for an instance of String

When I follow the left menu "Systems > Activation Keys" 393ms Show Error + 
                                            
 undefined method `map' for nil (NoMethodError)
./features/step_definitions/navigation_steps.rb:573:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:439:in `/^I am authorized for the "([^"]*)" section$/'
./features/step_definitions/navigation_steps.rb:399:in `rescue in block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:392:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:385:in `each'
./features/step_definitions/navigation_steps.rb:385:in `each_with_index'
./features/step_definitions/navigation_steps.rb:385:in `/^I follow the left menu "([^"]*)"$/'
features/reposync/allcli_update_activationkeys.feature:207:in `I follow the left menu "Systems ) Activation Keys"'

And I follow "Build host 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 "build_host" from "selectedBaseChannel" 0s

And I wait for child channels to appear 0s

And I check "Devel-Build-Host-Channel" 0s

And I wait until "Devel-Build-Host-Channel" has been checked 0s

And I click on "Update Activation Key" 0s

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

@scc_credentials
Scenario:
Update terminal key with synced base product
399ms 17 1

The browser session could not be cleaned because there is no browser available: undefined method `first' for an instance of String

When I follow the left menu "Systems > Activation Keys" 399ms Show Error + 
                                            
 undefined method `map' for nil (NoMethodError)
./features/step_definitions/navigation_steps.rb:573:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:439:in `/^I am authorized for the "([^"]*)" section$/'
./features/step_definitions/navigation_steps.rb:399:in `rescue in block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:392:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:385:in `each'
./features/step_definitions/navigation_steps.rb:385:in `each_with_index'
./features/step_definitions/navigation_steps.rb:385:in `/^I follow the left menu "([^"]*)"$/'
features/reposync/allcli_update_activationkeys.feature:219:in `I follow the left menu "Systems ) Activation Keys"'

And I follow "Terminal 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 "pxeboot_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 click on "Update Activation Key" 0s

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

@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
387ms 5 1

The browser session could not be cleaned because there is no browser available: undefined method `first' for an instance of String

When I follow the left menu "Systems > Activation Keys" 387ms Show Error + 
                                            
 undefined method `map' for nil (NoMethodError)
./features/step_definitions/navigation_steps.rb:573:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:439:in `/^I am authorized for the "([^"]*)" section$/'
./features/step_definitions/navigation_steps.rb:399:in `rescue in block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:392:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:385:in `each'
./features/step_definitions/navigation_steps.rb:385:in `each_with_index'
./features/step_definitions/navigation_steps.rb:385:in `/^I follow the left menu "([^"]*)"$/'
features/reposync/allcli_update_activationkeys.feature:266:in `I follow the left menu "Systems ) Activation Keys"'

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

And I wait for child channels to appear 0s

And I check "Devel-SUSE-Channel" 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

@skip_if_github_validation @deblike_minion
Scenario:
Update Debian-like key with to include dev child channel
379ms 5 1

The browser session could not be cleaned because there is no browser available: undefined method `first' for an instance of String

When I follow the left menu "Systems > Activation Keys" 379ms Show Error + 
                                            
 undefined method `map' for nil (NoMethodError)
./features/step_definitions/navigation_steps.rb:573:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:439:in `/^I am authorized for the "([^"]*)" section$/'
./features/step_definitions/navigation_steps.rb:399:in `rescue in block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:392:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:385:in `each'
./features/step_definitions/navigation_steps.rb:385:in `each_with_index'
./features/step_definitions/navigation_steps.rb:385:in `/^I follow the left menu "([^"]*)"$/'
features/reposync/allcli_update_activationkeys.feature:276:in `I follow the left menu "Systems ) Activation Keys"'

And I follow "Debian-like Test Key" in the content area 0s

And I wait for child channels to appear 0s

And I check "Devel-Debian-like-Channel" 0s

And I click on "Update Activation Key" 0s

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

@skip_if_github_validation @rhlike_minion
Scenario:
Update RedHat-like key with to include dev child channel
372ms 5 1

The browser session could not be cleaned because there is no browser available: undefined method `first' for an instance of String

When I follow the left menu "Systems > Activation Keys" 372ms Show Error + 
                                            
 undefined method `map' for nil (NoMethodError)
./features/step_definitions/navigation_steps.rb:573:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:439:in `/^I am authorized for the "([^"]*)" section$/'
./features/step_definitions/navigation_steps.rb:399:in `rescue in block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:392:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:385:in `each'
./features/step_definitions/navigation_steps.rb:385:in `each_with_index'
./features/step_definitions/navigation_steps.rb:385:in `/^I follow the left menu "([^"]*)"$/'
features/reposync/allcli_update_activationkeys.feature:286:in `I follow the left menu "Systems ) Activation Keys"'

And I follow "RedHat like Test Key" in the content area 0s

And I wait for child channels to appear 0s

And I check "Devel-RH-like-Channel" 0s

And I click on "Update Activation Key" 0s

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

Feature:Create bootstrap repositories 25s 759ms 1 3

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

When I create the bootstrap repositories including custom channels 992ms

@sle_minion
Scenario:
Create the bootstrap repository for SUSE Minion
23s 546ms 2

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 11s 73ms Show Error + 
                                            
 FAIL: mgrctl exec -it 'mgr-create-bootstrap-repo --create openSUSE-Leap-15.6-x86_64-uyuni --with-custom-channels' returned status code = 255.
Output:
Traceback (most recent call last):
  File "/usr/sbin/mgr-create-bootstrap-repo", line 1086, in (module)
    sys.exit(abs(main() or 0))
  File "/usr/sbin/mgr-create-bootstrap-repo", line 1079, in main
    r = create_repo(opts.create, opts, mgr_bootstrap_data, additional=args)
  File "/usr/sbin/mgr-create-bootstrap-repo", line 658, in create_repo
    shutil.copytree(destdir, destdirtmp)
  File "/usr/lib64/python3.6/shutil.py", line 365, in copytree
    raise Error(errors)
shutil.Error: [('/srv/www/htdocs/pub/repositories/opensuse/15/6/bootstrap/x86_64/venv-salt-minion-3006.0-47.1.uyuni.x86_64.rpm', '/srv/www/htdocs/pub/repositories/opensuse/15/6/bootstrap.tmp/x86_64/venv-salt-minion-3006.0-47.1.uyuni.x86_64.rpm', '[Errno 28] No space left on device'), ('/srv/www/htdocs/pub/repositories/opensuse/15/6/bootstrap/repodata', '/srv/www/htdocs/pub/repositories/opensuse/15/6/bootstrap.tmp/repodata', "[Errno 28] No space left on device: '/srv/www/htdocs/pub/repositories/opensuse/15/6/bootstrap.tmp/repodata'"), ('/srv/www/htdocs/pub/repositories/opensuse/15/6/bootstrap/venv-enabled-x86_64.txt', '/srv/www/htdocs/pub/repositories/opensuse/15/6/bootstrap.tmp/venv-enabled-x86_64.txt', "[Errno 28] No space left on device: '/srv/www/htdocs/pub/repositories/opensuse/15/6/bootstrap.tmp/venv-enabled-x86_64.txt'")]
 (ScriptError)
./features/support/remote_node.rb:132:in `run_local'
./features/support/remote_node.rb:116:in `run'
./features/step_definitions/command_steps.rb:1154:in `/^I create the bootstrap repository for "([^"]*)" on the server((?: without flushing)?)$/'
features/reposync/srv_create_bootstrap_repositories.feature:14:in `I create the bootstrap repository for "sle_minion" on the server'

12s 473ms Show Error + 
                                            
 FAIL: mgrctl exec -i 'tail -n20 /var/log/rhn/rhn_web_ui.log | awk -v limit="$(date --date="5 minutes ago" "+%Y-%m-%d %H:%M:%S")" " $0 ) limit"' returned status code = 255.
Output:
 (ScriptError)
./features/support/remote_node.rb:132:in `run_local'
./features/support/remote_node.rb:116:in `run'
./features/support/env.rb:746:in `print_server_logs'
./features/support/env.rb:165:in `After'
Show Info + 
15:35:39:000 - 15:35:50:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/YourRhn.do
Screenshot +

@proxy
Scenario:
Create the bootstrap repository for Proxy
610ms 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 610ms Show Error + 
                                            
 FAIL: mgrctl exec -it 'mgr-create-bootstrap-repo --create openSUSE-Tumbleweed-x86_64-uyuni --with-custom-channels' returned status code = 255.
Output:
 (ScriptError)
./features/support/remote_node.rb:132:in `run_local'
./features/support/remote_node.rb:116:in `run'
./features/step_definitions/command_steps.rb:1154:in `/^I create the bootstrap repository for "([^"]*)" on the server((?: without flushing)?)$/'
features/reposync/srv_create_bootstrap_repositories.feature:18:in `I create the bootstrap repository for "proxy" on the server'

@build_host
Scenario:
Create the bootstrap repository for Build Host
609ms 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 609ms Show Error + 
                                            
 FAIL: mgrctl exec -it 'mgr-create-bootstrap-repo --create SLE-15-SP4-x86_64 --with-parent-channel sle-product-sles15-sp4-pool-x86_64 --with-custom-channels' returned status code = 255.
Output:
 (ScriptError)
./features/support/remote_node.rb:132:in `run_local'
./features/support/remote_node.rb:116:in `run'
./features/step_definitions/command_steps.rb:1154:in `/^I create the bootstrap repository for "([^"]*)" on the server((?: without flushing)?)$/'
features/reposync/srv_create_bootstrap_repositories.feature:22:in `I create the bootstrap repository for "build_host" on the server'