Cucumber Feature Report

All Scenarios

142

Passed Scenarios

56

Failed Scenarios

58

Skipped Scenarios

28

Execution Time: 240m 14s 796ms

Expand All | Collapse All

Metadata

App Version: Uyuni/Head

Browser: Chrome

Platform: x86_64

Parallel: Disabled

Feature:Sanity checks 35s 454ms 10 2

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

Scenario:
The server is healthy

7s 944ms 19

Then "server" should have a FQDN 208ms

And reverse resolution should work for "server" 416ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@proxy

Scenario:
The proxy is healthy

2s 992ms 4

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

And reverse resolution should work for "proxy" 185ms

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

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

@sle_minion

Scenario:
The minion is healthy

4s 115ms 4

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

And reverse resolution should work for "sle_minion" 256ms

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

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

@build_host

Scenario:
The build host is healthy

3s 242ms 4

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

And reverse resolution should work for "build_host" 301ms

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

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

@ssh_minion

Scenario:
The SSH minion is healthy

4s 91ms 4

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

And reverse resolution should work for "ssh_minion" 253ms

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

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

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 247ms 4

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

And reverse resolution should work for "rhlike_minion" 196ms

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

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

@deblike_minion

Scenario:
The Debian-like minion is healthy

8s 561ms 4

Then "deblike_minion" should have a FQDN 7s 318ms

And reverse resolution should work for "deblike_minion" 247ms

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

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

@skip_if_cloud

Scenario:
The external resources can be reached

< 1ms 3

Then it should be possible to reach the test packages 0s

And it should be possible to reach the build sources 0s

And it should be possible to reach the Docker profiles 0s

@server_http_proxy

Scenario:
The HTTP proxy is working

< 1ms 1

Then it should be possible to use the HTTP proxy 0s

@auth_registry

Scenario:
The registry with authentication is healthy

416ms 1

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

@no_auth_registry

Scenario:
The registry without authentication is healthy

419ms 1

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

@custom_download_endpoint

Scenario:
The custom download endpoint is working

421ms 1

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

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

456ms 1

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

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

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

Scenario:
Wait for refresh of list of products to finish

2s 302ms 1

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

Scenario:
Create testing username

1s 172ms 12

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

And I follow "Create User" 490ms

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

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

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

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

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

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

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

And I click on "Create Login" 63ms

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

And I should see a "testing" link 11ms

Scenario:
Grant testing user administrative priviledges

1s 503ms 10

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

And I follow "testing" 386ms

And I check "role_org_admin" 77ms

And I check "role_system_group_admin" 70ms

And I check "role_channel_admin" 72ms

And I check "role_activation_key_admin" 71ms

And I check "role_config_admin" 70ms

And I click on "Update" 556ms

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

And I should see a "testing" text 61ms

@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

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

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

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

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 686ms 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 177ms 5

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

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

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

And I click on "Save Preferences" 57ms

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

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

2s 509ms 5

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

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

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

And I click on "Save Preferences" 51ms

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

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

Scenario:
Log in as admin user

1s 845ms 1

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

Scenario:
Create a Kiwi user with image administrators rights

2s 19ms 16

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

And I follow "Create User" 244ms

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

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

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

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

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

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

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

And I click on "Create Login" 420ms

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

And I should see a "kiwikiwi" link 11ms

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

And I follow "kiwikiwi" 253ms

And I check "role_image_admin" 98ms

And I click on "Update" 404ms

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

Scenario:
Log in as admin user

510ms 1

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

Scenario:
Create a Docker user with image administrators rights

1s 742ms 16

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

And I follow "Create User" 318ms

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

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

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

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

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

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

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

And I click on "Create Login" 428ms

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

And I should see a "docker" link 10ms

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

And I follow "docker" 265ms

And I check "role_image_admin" 91ms

And I click on "Update" 45ms

@no_auth_registry

Scenario:
Create an image store without credentials

3s 106ms 7

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

And I follow "Create" 606ms

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

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

And I click on "create-btn" 97ms

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

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

Feature:Do not let Taskomatic tasks interfere with our CI tests 34s 237ms 3

Scenario:
Log in as admin user

26s 639ms 1

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

Scenario:
Disable scheduled reposyncs

4s 629ms 5

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

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

And I choose "disabled" 52ms

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

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

Scenario:
Disable scheduled Cobbler syncs

2s 968ms 5

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

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

And I choose "disabled" 42ms

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

And I click on "Disable Schedule" 50ms

@scc_credentials
Feature:List available channels and enable them 1m 18s 250ms 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 569ms 5

When I refresh SCC 13s 164ms

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

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

995ms 4

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

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

883ms 4

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

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

When I remove the mgr-sync cache file 443ms

And I execute mgr-sync refresh 1m 454ms

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 211m 58s 314ms 6 2 9

@scc_credentials

Scenario:
Refresh SCC

11s 151ms 1

When I refresh SCC 11s 151ms

@scc_credentials

Scenario:
Let the products page appear

1s 638ms 6

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

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

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

Then I should see a "Arch" text 93ms

And I should see a "Channels" text 93ms

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

@scc_credentials

Scenario:
Use the products and architecture filters

2s 226ms 7

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

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

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

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

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

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

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

@scc_credentials @susemanager

Scenario:
View the channels list in the products page

< 1ms 9

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

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

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

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

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

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

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

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

When I close the modal dialog 0s

@scc_credentials @susemanager

Scenario:
Synchronize SLES 15 SP4 product with recommended sub-products, including SUMA Client Tools

< 1ms 33

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

Then the SLE15 SP4 product should be added 0s

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

@uyuni

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

2m 46s 974ms 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
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel opensuse_leap15_6-uyuni-client-x86_64 synchronized in 24 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.
/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.
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 11 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 233ms

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

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

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

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

@containerized_server @proxy @uyuni

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

139m 56s 595ms 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
/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-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.
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel opensuse_tumbleweed-uyuni-client-devel-x86_64 synchronized in 6 seconds
Channel opensuse_tumbleweed-uyuni-client-devel-x86_64 finished syncing
/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.
103 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/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/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/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/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/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/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.
104 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/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/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/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/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/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/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.
105 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/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/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/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/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/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/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.
106 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/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/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/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/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/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/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.
107 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/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/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/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/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/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/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.
108 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/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/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/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/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/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/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.
109 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/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/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/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/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/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/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.
110 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/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/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/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/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/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/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.
111 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/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 7510 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 11 seconds
Channel uyuni-proxy-devel-tumbleweed-x86_64 finished syncing

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

And I wait until all synchronized channels for "uyuni-proxy" have finished 139m 37s 81ms

@scc_credentials @uyuni

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

68m 25s 535ms 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]
WARN: Repository metadata for sle-product-sles15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-product-sles15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle15-sp4-installer-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sle-product-sles15-sp4-pool-x86_64 synchronized in 12 seconds
Channel sle-product-sles15-sp4-pool-x86_64 finished syncing
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sle15-sp4-installer-updates-x86_64 synchronized in 17 seconds
Channel sle15-sp4-installer-updates-x86_64 finished syncing
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sle-product-sles15-sp4-updates-x86_64 synchronized in 4 seconds
Channel sle-product-sles15-sp4-updates-x86_64 finished syncing
/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.
/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 sles15-sp4-devel-uyuni-client-x86_64 synchronized in 30 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
4 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
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
WARN: Repository metadata for sle-module-basesystem15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
12 minutes out of 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-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.
13 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.
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sle-module-basesystem15-sp4-updates-x86_64 synchronized in 1277 seconds
Channel sle-module-basesystem15-sp4-updates-x86_64 finished syncing
14 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.
WARN: Repository metadata for sle-module-server-applications15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-basesystem15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-server-applications15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
15 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-server-applications15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sle-module-basesystem15-sp4-pool-x86_64 synchronized in 293 seconds
Channel sle-module-basesystem15-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-pool-x86_64 synchronized in 39 seconds
Channel sle-module-server-applications15-sp4-pool-x86_64 finished syncing
WARN: Repository metadata for sle-module-server-applications15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-server-applications15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
16 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-server-applications15-sp4-updates-x86_64 synchronized in 108 seconds
Channel sle-module-server-applications15-sp4-updates-x86_64 finished syncing
17 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 167 seconds
Channel sle-module-desktop-applications15-sp4-updates-x86_64 finished syncing
18 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
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.
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 252 seconds
Channel sle-module-desktop-applications15-sp4-pool-x86_64 finished syncing
21 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
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
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.
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.
WARN: Repository metadata for sle-module-devtools15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-devtools15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-devtools15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-devtools15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-devtools15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
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.
31 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-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 800 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.
WARN: Repository metadata for sle-module-containers15-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-containers15-sp4-pool-x86_64 seems not synchronized. Even if the reposync log says it is.
WARN: Repository metadata for sle-module-containers15-sp4-updates-x86_64 seems not synchronized. Even if the reposync log says it is.
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sle-module-devtools15-sp4-pool-x86_64 synchronized in 109 seconds
Channel sle-module-devtools15-sp4-pool-x86_64 finished syncing
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sle-module-containers15-sp4-updates-x86_64 synchronized in 56 seconds
Channel sle-module-containers15-sp4-updates-x86_64 finished syncing
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel sle-module-containers15-sp4-pool-x86_64 synchronized in 7 seconds
Channel sle-module-containers15-sp4-pool-x86_64 finished syncing
32 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
33 minutes out of 130 waiting for 'sles15-sp4' channels to be synchronized
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
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.
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.
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.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 48ms

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

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

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

And I wait until all synchronized channels for "sles15-sp4" have finished 67m 45s 806ms Show Error +

                                            
 FAIL: mgrctl cp server:/var/log/rhn/reposync.log /tmp/reposync.log returned status code = 1.
Output:
2:43PM INF Starting mgrctl cp server:/var/log/rhn/reposync.log /tmp/reposync.log
2:43PM ??? 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)(0xc000284b30), ChmodDirs:(*fs.FileMode)(nil), ChownFiles:(*idtools.IDPair)(0xc000284b40), 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 231ms 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:35:02:000 - 14:43:15: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 191ms 5 1 2

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

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

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

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

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

And I select "250" from "pageSize" 11s 22ms 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 353ms 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:43:29:000 - 14:43:51: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 52ms 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 538ms 1

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

Scenario:
Add a fake base channel for x86_64

1s 65ms 10

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

And I follow "Create Channel" 364ms

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

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

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

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

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

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

And I click on "Create Channel" 63ms

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

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

924ms 10

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

And I follow "Create Channel" 348ms

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

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

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

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

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

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

And I click on "Create Channel" 56ms

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

@sle_minion

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

1s 292ms 10

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

And I follow "Create Channel" 279ms

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

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

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

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

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

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

Scenario:
Add a fake base channel for i586

799ms 10

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

And I follow "Create Channel" 229ms

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

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

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

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

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

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

And I click on "Create Channel" 52ms

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

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

1s 255ms 10

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

And I follow "Create Channel" 286ms

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

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

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

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

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

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

And I click on "Create Channel" 474ms

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

Scenario:
Add a test base channel for x86_64

1s 194ms 10

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

And I follow "Create Channel" 214ms

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

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

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

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

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

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

And I click on "Create Channel" 491ms

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

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

1s 183ms 10

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

And I follow "Create Channel" 230ms

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

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

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

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

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

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

And I click on "Create Channel" 52ms

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

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

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

And I follow "Create Channel" 214ms

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

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

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

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

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

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

And I uncheck "gpg_check" 10s 67ms

And I click on "Create Channel" 500ms

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

@rhlike_minion

Scenario:
Add a RedHat-like base channel

23s 491ms 9 2

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

And I follow "Create Channel" 222ms

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

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

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

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

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

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

And I click on "Create Channel" 527ms

Then I should see a "Channel Fake-Base-Channel-RH-like created." text 10s 16ms 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 314ms 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:44:38:000 - 14:44:49: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 9ms 9 1

When I follow the left menu "Software > Manage > Channels" 10s 9ms 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 2m 545ms 7 7 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 559ms 1

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

Scenario:
Create a fake repository for distributions using RPM

725ms 7

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

And I follow "Create Repository" 287ms

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

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

And I click on "Create Repository" 57ms

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

And I should see "metadataSigned" as checked 19ms

Scenario:
Disable metadata check for the fake RPM repository

10s 900ms 6

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

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

And I uncheck "metadataSigned" 10s 80ms

And I click on "Update Repository" 402ms

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

And I should see "metadataSigned" as unchecked 14ms

@rhlike_minion

Scenario:
Create a fake AppStream repository

930ms 7

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

And I follow "Create Repository" 278ms

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

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

And I click on "Create Repository" 376ms

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

And I should see "metadataSigned" as checked 14ms

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

10s 913ms 6

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

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

And I uncheck "metadataSigned" 10s 63ms

And I click on "Update Repository" 428ms

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

And I should see "metadataSigned" as unchecked 14ms

@sle_minion

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

1s 714ms 9

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

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

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

And I click on "Update Channel" 497ms

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

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

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

And I click on "Save Repositories" 498ms

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

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

2s 532ms 9

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

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

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

And I click on "Update Channel" 431ms

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

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

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

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

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

@rhlike_minion

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

22s 231ms 1 7 2

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

And I follow "Fake-Base-Channel-RH-like" 10s 4ms 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

12s 161ms 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:13:000 - 14:46:24: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

10s 11ms 8 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_repositories.feature:89:in `I follow the left menu "Software ) Manage ) Channels"'

And I follow "Fake-Base-Channel-AppStream" 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-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

Scenario:
Create a fake repository for i586

10s 5ms 6 1

When I follow the left menu "Software > Manage > Repositories" 10s 5ms 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_repositories.feature:100:in `I follow the left menu "Software ) Manage ) Repositories"'

And I follow "Create Repository" 0s

And I enter "fake-i586-repo" as "label" 0s

And I enter "file:///srv/www/htdocs/pub/TestRepoRpmUpdates/" as "url" 0s

And I uncheck "metadataSigned" 0s

And I click on "Create Repository" 0s

Then I should see a "Repository created successfully" text 0s

Scenario:
Add the repository to the i586 channel

10s 11ms 8 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_repositories.feature:109:in `I follow the left menu "Software ) Manage ) Channels"'

And I follow "Fake-Child-Channel-i586" 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-Child-Channel-i586 updated" text 0s

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

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

And I click on "Save Repositories" 0s

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

@sle_minion

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

10s 3ms 5 1

When I follow the left menu "Software > Manage > Channels" 10s 3ms 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_repositories.feature:121:in `I follow the left menu "Software ) Manage ) Channels"'

And I follow "Fake-Child-Channel-SUSE-like" 0s

And 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-Child-Channel-SUSE-like repository information was successfully updated" text 0s

@deblike_minion

Scenario:
Create a fake repository for Debian-like

10s 1ms 6 1

When I follow the left menu "Software > Manage > Repositories" 10s 1ms 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_repositories.feature:130:in `I follow the left menu "Software ) Manage ) Repositories"'

And I follow "Create Repository" 0s

And I enter "fake-debian-repo" as "label" 0s

And I select "deb" from "contenttype" 0s

And I enter "http://localhost/pub/TestRepoDebUpdates/" as "url" 0s

And I click on "Create Repository" 0s

Then I should see a "Repository created successfully" text 0s

@deblike_minion

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

10s 3ms 5 1

When I follow the left menu "Software > Manage > Channels" 10s 3ms 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_repositories.feature:140:in `I follow the left menu "Software ) Manage ) Channels"'

And I follow "Fake-Base-Channel-Debian-like" 0s

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

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

And I click on "Save Repositories" 0s

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

@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 20s 84ms 1 8

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

10s 685ms 1

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

@sle_minion

Scenario:
Create a custom channel for SUSE minions

23s 463ms 9 2

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

And I follow "Create Channel" 316ms

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

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

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

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

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

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

And I click on "Create Channel" 56ms

Then I should see a "Channel Devel-SUSE-Channel created." text 10s 30ms Show Error +

                                            
 Text 'Channel Devel-SUSE-Channel created.' not found (ScriptError)
./features/step_definitions/navigation_steps.rb:641:in `/^I should see a "([^"]*)" text$/'
features/reposync/srv_create_devel_channels.feature:24:in `I should see a "Channel Devel-SUSE-Channel created." text'

12s 496ms 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:49:51:000 - 14:50:03:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/manage/Edit.do

Screenshot +

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

4s 11ms 1

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

                                            
 unknown error - API failure: No such channel: devel-suse-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:28:in `I prepare the development repositories of "sle_minion" as part of "devel-suse-channel" channel'

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

10s 4ms 9 1

When I follow the left menu "Software > Manage > Channels" 10s 4ms 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_devel_channels.feature:33:in `I follow the left menu "Software ) Manage ) Channels"'

And I follow "Create Channel" 0s

And I enter "Devel-Build-Host-Channel" as "Channel Name" 0s

And I enter "devel-build-host-channel" as "Channel Label" 0s

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

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

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

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

2s 807ms 1

When I prepare the development repositories of "build_host" as part of "devel-build-host-channel" channel 2s 807ms Show Error +

                                            
 unknown error - API failure: No such channel: devel-build-host-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:47:in `I prepare the development repositories of "build_host" as part of "devel-build-host-channel" channel'

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

10s 8ms 9 1

When I follow the left menu "Software > Manage > Channels" 10s 8ms 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_devel_channels.feature:51:in `I follow the left menu "Software ) Manage ) Channels"'

And I follow "Create Channel" 0s

And I enter "Devel-Debian-like-Channel" as "Channel Name" 0s

And I enter "devel-debian-like-channel" as "Channel Label" 0s

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

And I select "AMD64 Debian" from "Architecture:" 0s

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

@deblike_minion

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

5s 662ms 1

When I prepare the development repositories of "deblike_minion" as part of "devel-debian-like-channel" channel 5s 662ms Show Error +

                                            
 unknown error - API failure: No such channel: devel-debian-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:64:in `I prepare the development repositories of "deblike_minion" as part of "devel-debian-like-channel" channel'

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

10s 2ms 9 1

When I follow the left menu "Software > Manage > Channels" 10s 2ms 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_devel_channels.feature:68:in `I follow the left menu "Software ) Manage ) Channels"'

And I follow "Create Channel" 0s

And I enter "Devel-RH-like-Channel" as "Channel Name" 0s

And I enter "devel-rh-like-channel" as "Channel Label" 0s

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

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

@rhlike_minion

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

3s 439ms 1

When I prepare the development repositories of "rhlike_minion" as part of "devel-rh-like-channel" channel 3s 439ms 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'

Feature:Synchronize fake channels 7m 22s 369ms 12 2

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

Scenario:
Log in as admin user

24s 418ms 1 2

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

And I enable source package syncing 953ms Show Error +

                                            
 FAIL: mgrctl exec -i 'echo '"'"'server.sync_source_packages = 1'"'"' )) /etc/rhn/rhn.conf' 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:946:in `/^I enable source package syncing$/'
features/reposync/srv_sync_fake_channels.feature:19:in `I enable source package syncing'

12s 858ms 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:53:26:000 - 14:53:37:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/YourRhn.do

Screenshot +

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

26s 456ms 8 2

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

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

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

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

And I follow "Sync" 372ms

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

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

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

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

                                            
 FAIL: mgrctl cp server:/var/log/rhn/reposync.log /tmp/reposync.log returned status code = 1.
Output:
2:54PM INF Starting mgrctl cp server:/var/log/rhn/reposync.log /tmp/reposync.log
2:54PM ??? 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)(0xc0004eddb0), ChmodDirs:(*fs.FileMode)(nil), ChownFiles:(*idtools.IDPair)(0xc0004eddc0), 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:440: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:439: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 378ms 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:53:50:000 - 14:54:06: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

313ms 1 1

Then "orion-dummy-1.1-1.1.x86_64.rpm" package should have been stored 313ms Show Error +

                                            
 FAIL: mgrctl exec -i 'find /var/spacewalk/packages -name orion-dummy-1.1-1.1.x86_64.rpm' 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:415:in `/^"([^"]*)" package should have been stored$/'
features/reposync/srv_sync_fake_channels.feature:35:in `"orion-dummy-1.1-1.1.x86_64.rpm" package should have been stored'

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

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

35s 216ms 7 1 2

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

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

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

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

And I follow "Sync" 351ms

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

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

Then I should see a "Repository sync scheduled for Fake-Child-Channel-i586." text 10s 35ms Show Error +

                                            
 Text 'Repository sync scheduled for Fake-Child-Channel-i586.' not found (ScriptError)
./features/step_definitions/navigation_steps.rb:641:in `/^I should see a "([^"]*)" text$/'
features/reposync/srv_sync_fake_channels.feature:47:in `I should see a "Repository sync scheduled for Fake-Child-Channel-i586." text'

And I wait until the channel "fake-child-channel-i586" has been synced 0s

12s 387ms 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:54:39:000 - 14:55:03: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

1m 26s 848ms 5 3 2

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

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

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

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

And I follow "Sync" 288ms

And I wait at most 60 seconds until I do not see "Repository sync is running." text, refreshing the page 1m 3s 69ms Show Error +

                                            
 execution expired (Timeout::Error)
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/step_definitions/navigation_steps.rb:69:in `/^I wait at most (\d+) seconds until I do not see "([^"]*)" text, refreshing the page$/'
features/reposync/srv_sync_fake_channels.feature:56:in `I wait at most 60 seconds until I do not see "Repository sync is running." text, refreshing the page'

And I click on "Sync Now" 0s

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

And I wait until the channel "test-child-channel-x86_64" has been synced 0s

12s 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 +

14:55:15:000 - 14:56:31: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

35s 104ms 7 1 2

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

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

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

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

And I follow "Sync" 368ms

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

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

Then I should see a "Repository sync scheduled for Fake-Child-Channel-SUSE-like." text 10s 75ms Show Error +

                                            
 Text 'Repository sync scheduled for Fake-Child-Channel-SUSE-like.' not found (ScriptError)
./features/step_definitions/navigation_steps.rb:641:in `/^I should see a "([^"]*)" text$/'
features/reposync/srv_sync_fake_channels.feature:70:in `I should see a "Repository sync scheduled for Fake-Child-Channel-SUSE-like." text'

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

12s 361ms 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:56:43:000 - 14:57:07:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/manage/Sync.do?cid=123

Screenshot +

@deblike_minion

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

34s 71ms 7 1 2

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

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

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

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

And I follow "Sync" 290ms

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

And I click on "Sync Now" 329ms

Then I should see a "Repository sync scheduled for Fake-Base-Channel-Debian-like." text 10s 19ms Show Error +

                                            
 Text 'Repository sync scheduled for Fake-Base-Channel-Debian-like.' not found (ScriptError)
./features/step_definitions/navigation_steps.rb:641:in `/^I should see a "([^"]*)" text$/'
features/reposync/srv_sync_fake_channels.feature:82:in `I should see a "Repository sync scheduled for Fake-Base-Channel-Debian-like." text'

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

12s 327ms 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:57:19:000 - 14:57:42:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/manage/Sync.do?cid=129

Screenshot +

@rhlike_minion

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

1m 5s 988ms 8 2

Given I am authorized for the "Admin" section 40s 279ms Show Error +

                                            
 User is not logged in (ScriptError)
./features/step_definitions/navigation_steps.rb:607:in `/^I should be logged in$/'
./features/step_definitions/navigation_steps.rb:587: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_fake_channels.feature:87:in `I am authorized for the "Admin" section'

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

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

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

25s 708ms 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 `ensure in block in (top (required))'
./features/support/env.rb:165:in `After'

Show Info +

14:57:54:000 - 14:58:34:000 | Current URL: https://uyuni-master-server.sumaci.aws/

Screenshot +

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

1m 53s 570ms 8 2

Given I am authorized for the "Admin" section 55s 855ms Show Error +

                                            
 Login page is not correctly loaded (ScriptError)
./features/step_definitions/navigation_steps.rb:581: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_fake_channels.feature:99:in `I am authorized for the "Admin" section'

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

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

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

57s 715ms 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 `ensure in block in (top (required))'
./features/support/env.rb:165:in `After'

Show Info +

14:59:00:000 - 14:59:56:000 | Current URL: https://uyuni-master-server.sumaci.aws/

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

10s 4ms 5 1

When I follow the left menu "Admin > Task Schedules" 10s 4ms Show Error +

                                            
 Unable to find xpath "//aside/div[@id='nav']/nav/ul/li/div/a[contains(.,'Admin')]/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_sync_fake_channels.feature:131:in `I follow the left menu "Admin ) Task Schedules"'

And I follow "errata-cache-default" 0s

And I follow "errata-cache-bunch" 0s

And I click on "Single Run Schedule" 0s

Then I should see a "bunch was scheduled" text 0s

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

Scenario:
Refresh the channel's repository data

10s 5 1

When I follow the left menu "Admin > Task Schedules" 10s Show Error +

                                            
 Unable to find xpath "//aside/div[@id='nav']/nav/ul/li/div/a[contains(.,'Admin')]/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_sync_fake_channels.feature:139:in `I follow the left menu "Admin ) Task Schedules"'

And I follow "channel-repodata-default" 0s

And I follow "channel-repodata-bunch" 0s

And I click on "Single Run Schedule" 0s

Then I should see a "bunch was scheduled" text 0s

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

Scenario:
Cleanup disable source package syncing

376ms 1

Then I disable source package syncing 376ms Show Error +

                                            
 FAIL: mgrctl exec -i 'sed -i '"'"'s/^server.sync_source_packages = 1.*//g'"'"' /etc/rhn/rhn.conf' 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:951:in `/^I disable source package syncing$/'
features/reposync/srv_sync_fake_channels.feature:147:in `I disable source package syncing'

@skip_if_github_validation
Feature:Synchronize development channels 6m 35s 223ms 4

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

@sle_minion

Scenario:
Synchronize Devel-SUSE-Channel channel

1m 36s 344ms 8 2

Given I am authorized for the "Admin" section 40s 397ms Show Error +

                                            
 Login page is not correctly loaded (ScriptError)
./features/step_definitions/navigation_steps.rb:581: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

55s 946ms 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 `ensure in block in (top (required))'
./features/support/env.rb:165:in `After'

Show Info +

15:02:17:000 - 15:02:57:000 | Current URL: https://uyuni-master-server.sumaci.aws/

Screenshot +

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

1m 35s 831ms 8 2

Given I am authorized for the "Admin" section 56s 606ms Show Error +

                                            
 Login page is not correctly loaded (ScriptError)
./features/step_definitions/navigation_steps.rb:581: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

39s 225ms 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 `ensure in block in (top (required))'
./features/support/env.rb:165:in `After'

Show Info +

15:03:53:000 - 15:04:50:000 | Current URL: https://uyuni-master-server.sumaci.aws/

Screenshot +

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

1m 30s 628ms 8 2

Given I am authorized for the "Admin" section 55s 390ms Show Error +

                                            
 Login page is not correctly loaded (ScriptError)
./features/step_definitions/navigation_steps.rb:581: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

35s 238ms 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 `ensure in block in (top (required))'
./features/support/env.rb:165:in `After'

Show Info +

15:05:29:000 - 15:06:24:000 | Current URL: https://uyuni-master-server.sumaci.aws/

Screenshot +

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

1m 52s 418ms 8 2

Given I am authorized for the "Admin" section 55s 369ms Show Error +

                                            
 Login page is not correctly loaded (ScriptError)
./features/step_definitions/navigation_steps.rb:581: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

57s 49ms 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 `ensure in block in (top (required))'
./features/support/env.rb:165:in `After'

Show Info +

15:06:59:000 - 15:07:55:000 | Current URL: https://uyuni-master-server.sumaci.aws/

Screenshot +

Feature:Create activation keys 2m 51s 11ms 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

1m 30s 950ms 2

Given I am authorized for the "Admin" section 34s 219ms Show Error +

                                            
 Login page is not correctly loaded (ScriptError)
./features/step_definitions/navigation_steps.rb:581: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'

56s 730ms 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 `ensure in block in (top (required))'
./features/support/env.rb:165:in `After'

Show Info +

15:08:52:000 - 15:09:26:000 | Current URL: https://uyuni-master-server.sumaci.aws/

Screenshot +

Scenario:
Create an activation key with a channel

10s 5ms 12 1

When I follow the left menu "Systems > Activation Keys" 10s 5ms Show Error +

                                            
 Unable to find xpath "//aside/div[@id='nav']/nav/ul/li/div/a[contains(.,'Systems')]/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_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

10s 10ms 7 1

When I follow the left menu "Systems > Activation Keys" 10s 10ms Show Error +

                                            
 Unable to find xpath "//aside/div[@id='nav']/nav/ul/li/div/a[contains(.,'Systems')]/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_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

10s 5ms 7 1

When I follow the left menu "Systems > Activation Keys" 10s 5ms Show Error +

                                            
 Unable to find xpath "//aside/div[@id='nav']/nav/ul/li/div/a[contains(.,'Systems')]/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_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

10s 8ms 8 1

When I follow the left menu "Systems > Activation Keys" 10s 8ms Show Error +

                                            
 Unable to find xpath "//aside/div[@id='nav']/nav/ul/li/div/a[contains(.,'Systems')]/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_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

10s 3ms 7 1

When I follow the left menu "Systems > Activation Keys" 10s 3ms Show Error +

                                            
 Unable to find xpath "//aside/div[@id='nav']/nav/ul/li/div/a[contains(.,'Systems')]/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_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

10s 13ms 6 1

When I follow the left menu "Systems > Activation Keys" 10s 13ms Show Error +

                                            
 Unable to find xpath "//aside/div[@id='nav']/nav/ul/li/div/a[contains(.,'Systems')]/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_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

10s 10ms 8 1

When I follow the left menu "Systems > Activation Keys" 10s 10ms Show Error +

                                            
 Unable to find xpath "//aside/div[@id='nav']/nav/ul/li/div/a[contains(.,'Systems')]/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_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

10s 4ms 6 1

When I follow the left menu "Systems > Activation Keys" 10s 4ms Show Error +

                                            
 Unable to find xpath "//aside/div[@id='nav']/nav/ul/li/div/a[contains(.,'Systems')]/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_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 3m 32s 571ms 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

1m 52s 496ms 2

Given I am authorized for the "Admin" section 55s 465ms Show Error +

                                            
 Login page is not correctly loaded (ScriptError)
./features/step_definitions/navigation_steps.rb:581: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'

57s 31ms 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 `ensure in block in (top (required))'
./features/support/env.rb:165:in `After'

Show Info +

15:14:29:000 - 15:15:24:000 | Current URL: https://uyuni-master-server.sumaci.aws/

Screenshot +

@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

10s 9 1

When I follow the left menu "Systems > Activation Keys" 10s Show Error +

                                            
 Unable to find xpath "//aside/div[@id='nav']/nav/ul/li/div/a[contains(.,'Systems')]/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/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

10s 9ms 9 1

When I follow the left menu "Systems > Activation Keys" 10s 9ms Show Error +

                                            
 Unable to find xpath "//aside/div[@id='nav']/nav/ul/li/div/a[contains(.,'Systems')]/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/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

10s 12ms 9 1

When I follow the left menu "Systems > Activation Keys" 10s 12ms Show Error +

                                            
 Unable to find xpath "//aside/div[@id='nav']/nav/ul/li/div/a[contains(.,'Systems')]/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/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

10s 7ms 19 1

When I follow the left menu "Systems > Activation Keys" 10s 7ms Show Error +

                                            
 Unable to find xpath "//aside/div[@id='nav']/nav/ul/li/div/a[contains(.,'Systems')]/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/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

10s 1ms 8 1

When I follow the left menu "Systems > Activation Keys" 10s 1ms Show Error +

                                            
 Unable to find xpath "//aside/div[@id='nav']/nav/ul/li/div/a[contains(.,'Systems')]/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/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

10s 9ms 8 1

When I follow the left menu "Systems > Activation Keys" 10s 9ms Show Error +

                                            
 Unable to find xpath "//aside/div[@id='nav']/nav/ul/li/div/a[contains(.,'Systems')]/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/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

10s 13ms 17 1

When I follow the left menu "Systems > Activation Keys" 10s 13ms Show Error +

                                            
 Unable to find xpath "//aside/div[@id='nav']/nav/ul/li/div/a[contains(.,'Systems')]/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/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

10s 1ms 5 1

When I follow the left menu "Systems > Activation Keys" 10s 1ms Show Error +

                                            
 Unable to find xpath "//aside/div[@id='nav']/nav/ul/li/div/a[contains(.,'Systems')]/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/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

10s 12ms 5 1

When I follow the left menu "Systems > Activation Keys" 10s 12ms Show Error +

                                            
 Unable to find xpath "//aside/div[@id='nav']/nav/ul/li/div/a[contains(.,'Systems')]/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/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

10s 7ms 5 1

When I follow the left menu "Systems > Activation Keys" 10s 7ms Show Error +

                                            
 Unable to find xpath "//aside/div[@id='nav']/nav/ul/li/div/a[contains(.,'Systems')]/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/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 3s 213ms 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

948ms 1

When I create the bootstrap repositories including custom channels 948ms

@sle_minion

Scenario:
Create the bootstrap repository for SUSE Minion

712ms 1

base_channel: openSUSE Leap 15.6 (x86_64)
channel: openSUSE-Leap-15.6-x86_64-uyuni
parent_channel:
Creating the bootstrap repository on the server:
mgr-create-bootstrap-repo --create openSUSE-Leap-15.6-x86_64-uyuni --with-custom-channels

When I create the bootstrap repository for "sle_minion" on the server 712ms 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:
 (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'

@proxy

Scenario:
Create the bootstrap repository for Proxy

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

728ms 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 728ms 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'

All Scenarios

142

Passed Scenarios

56

Failed Scenarios

58

Skipped Scenarios

28

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

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

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

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

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

@deblike_minion Scenario:The Debian-like minion is healthy 8s 561ms 4

@skip_if_cloud Scenario:The external resources can be reached < 1ms 3

@server_http_proxy Scenario:The HTTP proxy is working < 1ms 1

@auth_registry Scenario:The registry with authentication is healthy 416ms 1

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

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

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

@server_http_proxy Scenario:Setup HTTP proxy < 1ms 9

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

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

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

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

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

@test_issue Feature:Synchronize products in the products page of the Setup Wizard 211m 58s 314ms 6 2 9

@scc_credentials Scenario:Refresh SCC 11s 151ms 1

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

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

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

@scc_credentials @susemanager Scenario:Synchronize SLES 15 SP4 product with recommended sub-products, including SUMA Client Tools < 1ms 33

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

@containerized_server @proxy @uyuni Scenario:Add Uyuni Proxy product for Tumbleweed, including Uyuni Client Tools 139m 56s 595ms 2

@scc_credentials @uyuni Scenario:Synchronize SLES 15 SP4 product with recommended sub-products for Retail feature 68m 25s 535ms 27 2

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

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

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

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

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

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

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

@scc_credentials Scenario:Detect product loading issues from the UI 34s 191ms 5 1 2

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

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

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

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

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

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

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

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

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

@rhlike_minion Scenario:Add the fake RPM repository to the RedHat-like base channel 22s 231ms 1 7 2

@rhlike_minion Scenario:Add the fake AppStream repository to the AppStream base channel 10s 11ms 8 1

@sle_minion Scenario:Add the repository to the SUSE-like child channel 10s 3ms 5 1

@deblike_minion Scenario:Create a fake repository for Debian-like 10s 1ms 6 1

@deblike_minion Scenario:Add the repository to the Debian-like base channel 10s 3ms 5 1

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

@skip_if_github_validation Feature:Create custom channels with development repositories 1m 20s 84ms 1 8

@sle_minion Scenario:Create a custom channel for SUSE minions 23s 463ms 9 2

@proxy

Scenario:
The proxy is healthy

2s 992ms 4

@sle_minion

Scenario:
The minion is healthy

4s 115ms 4

@build_host

Scenario:
The build host is healthy

3s 242ms 4

@ssh_minion

Scenario:
The SSH minion is healthy

4s 91ms 4

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 247ms 4

@deblike_minion

Scenario:
The Debian-like minion is healthy

8s 561ms 4

@skip_if_cloud

Scenario:
The external resources can be reached

< 1ms 3

@server_http_proxy

Scenario:
The HTTP proxy is working

< 1ms 1

@auth_registry

Scenario:
The registry with authentication is healthy

416ms 1

@no_auth_registry

Scenario:
The registry without authentication is healthy

419ms 1

@custom_download_endpoint

Scenario:
The custom download endpoint is working

421ms 1

@skip_if_containerized_server

Scenario:
Create admin user and first organization

< 1ms 12

@server_http_proxy

Scenario:
Setup HTTP proxy

< 1ms 9

@scc_credentials @no_mirror

Scenario:
Enter valid SCC credentials

< 1ms 6

@no_auth_registry

Scenario:
Create an image store without credentials

3s 106ms 7

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

@proxy @susemanager

Scenario:
List Proxy product

< 1ms 2

@proxy @susemanager

Scenario:
List all products for SUSE Multi-Linux Manager

< 1ms 5

@test_issue
Feature:Synchronize products in the products page of the Setup Wizard 211m 58s 314ms 6 2 9

@scc_credentials

Scenario:
Refresh SCC

11s 151ms 1

@scc_credentials

Scenario:
Let the products page appear

1s 638ms 6

@scc_credentials

Scenario:
Use the products and architecture filters

2s 226ms 7

@scc_credentials @susemanager

Scenario:
View the channels list in the products page

< 1ms 9

@scc_credentials @susemanager

Scenario:
Synchronize SLES 15 SP4 product with recommended sub-products, including SUMA Client Tools

< 1ms 33

@uyuni

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

2m 46s 974ms 5

@containerized_server @proxy @uyuni

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

139m 56s 595ms 2

@scc_credentials @uyuni

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

68m 25s 535ms 27 2

@proxy @susemanager @transactional_server

Scenario:
Add SL Micro 6.1 as base OS for proxy

< 1ms 13

@proxy @susemanager @skip_if_transactional_server

Scenario:
Add SLES 15 SP7 as base OS for proxy

< 1ms 11

@proxy @susemanager @transactional_server

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

< 1ms 13

@proxy @susemanager @skip_if_transactional_server

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

< 1ms 12

@proxy @susemanager @transactional_server

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

< 1ms 13

@proxy @susemanager @skip_if_transactional_server

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

< 1ms 12

@scc_credentials @susemanager

Scenario:
Installer update channels got enabled when products were added

< 1ms 2

@scc_credentials

Scenario:
Detect product loading issues from the UI

34s 191ms 5 1 2

@scc_credentials

Scenario:
Report the synchronization duration for SLES 15 SP4

< 1ms 1

@sle_minion

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

1s 292ms 10

@pxeboot_minion @uyuni @scc_credentials

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

< 1ms 10

@deblike_minion

Scenario:
Add Debian-like AMD64 base channel

11s 296ms 11

@rhlike_minion

Scenario:
Add a RedHat-like base channel

23s 491ms 9 2

@rhlike_minion

Scenario:
Add a fake AppStream base channel

10s 9ms 9 1

@rhlike_minion

Scenario:
Create a fake AppStream repository

930ms 7

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

10s 913ms 6

@sle_minion

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

1s 714ms 9

@rhlike_minion

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

22s 231ms 1 7 2

@rhlike_minion

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

10s 11ms 8 1

@sle_minion

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

10s 3ms 5 1

@deblike_minion

Scenario:
Create a fake repository for Debian-like

10s 1ms 6 1

@deblike_minion

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

10s 3ms 5 1

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Add the repository to the terminal child channel

< 1ms 9

@skip_if_github_validation
Feature:Create custom channels with development repositories 1m 20s 84ms 1 8

@sle_minion

Scenario:
Create a custom channel for SUSE minions

23s 463ms 9 2