All Scenarios

151

Passed Scenarios

120

Failed Scenarios

0

Skipped Scenarios

31

Execution Time: 238m 2s 699ms

Expand All | Collapse All

Metadata

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

Feature:Sanity checks 32s 282ms 10 2

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

Scenario:
The server is healthy
8s 119ms 19

Then "server" should have a FQDN 211ms

And reverse resolution should work for "server" 455ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@proxy
Scenario:
The proxy is healthy
3s 100ms 4

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

And reverse resolution should work for "proxy" 185ms

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

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

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

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

And reverse resolution should work for "sle_minion" 252ms

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

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

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

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

And reverse resolution should work for "build_host" 261ms

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

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

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

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

And reverse resolution should work for "ssh_minion" 244ms

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

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

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

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

And reverse resolution should work for "rhlike_minion" 199ms

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

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

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

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

And reverse resolution should work for "deblike_minion" 214ms

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

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

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

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

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

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

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

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

Feature:Very first settings 46s 471ms 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
435ms 1

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

@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
40s 292ms 1

Given I am authorized for the "Admin" section 40s 292ms

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

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

Scenario:
Create testing username
1s 720ms 12

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

And I follow "Create User" 422ms

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

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

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

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

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

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

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

And I click on "Create Login" 692ms

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

And I should see a "testing" link 11ms

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

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

And I follow "testing" 377ms

And I check "role_org_admin" 78ms

And I check "role_system_group_admin" 70ms

And I check "role_channel_admin" 70ms

And I check "role_activation_key_admin" 70ms

And I check "role_config_admin" 71ms

And I click on "Update" 479ms

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

And I should see a "testing" text 64ms

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

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

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

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 884ms 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 120ms 5

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

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

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

And I click on "Save Preferences" 56ms

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

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

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

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

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

And I click on "Save Preferences" 480ms

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

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

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

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

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

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

And I follow "Create User" 310ms

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

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

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

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

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

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

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

And I click on "Create Login" 50ms

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

And I should see a "kiwikiwi" link 11ms

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

And I follow "kiwikiwi" 264ms

And I check "role_image_admin" 75ms

And I click on "Update" 44ms

Feature:Prepare server for using Docker 4s 801ms 3

Scenario:
Log in as admin user
507ms 1

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

Scenario:
Create a Docker user with image administrators rights
1s 645ms 16

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

And I follow "Create User" 268ms

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

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

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

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

And I click on "Create Login" 414ms

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

And I should see a "docker" link 11ms

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

And I follow "docker" 258ms

And I check "role_image_admin" 65ms

And I click on "Update" 45ms

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

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

And I follow "Create" 529ms

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

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

And I click on "create-btn" 78ms

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

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

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

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

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

Scenario:
Disable scheduled reposyncs
2s 982ms 5

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

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

And I choose "disabled" 53ms

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

And I click on "Disable Schedule" 58ms

Scenario:
Disable scheduled Cobbler syncs
4s 454ms 5

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

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

And I choose "disabled" 43ms

And I click on "Update Schedule" 49ms

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

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

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

Scenario:
List available channels
13s 647ms 5

When I refresh SCC 12s 156ms

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

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

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

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

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

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

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

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

When I remove the mgr-sync cache file 451ms

And I execute mgr-sync refresh 1m 467ms

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 226m 58s 354ms 8 9

@scc_credentials
Scenario:
Refresh SCC
10s 568ms 1

When I refresh SCC 10s 568ms

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

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

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

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

Then I should see a "Arch" text 99ms

And I should see a "Channels" text 99ms

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

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

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

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

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

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

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

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

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

@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 40s 822ms 5

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

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

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

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

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

@containerized_server @proxy @uyuni
Scenario:
Add Uyuni Proxy product for Tumbleweed, including Uyuni Client Tools
130m 52s 118ms 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
/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.
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.
/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.
99 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.
100 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.
101 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.
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/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.
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.
Channel synced, no .new files exist and number of solvables is bigger than 0
Channel opensuse_tumbleweed-x86_64 synchronized in 7162 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 10 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" 18s 997ms

And I wait until all synchronized channels for "uyuni-proxy" have finished 130m 33s 121ms

@scc_credentials @uyuni
Scenario:
Synchronize SLES 15 SP4 product with recommended sub-products for Retail feature
92m 18s 17ms 28

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 51ms

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

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

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

And I wait until all synchronized channels for "sles15-sp4" have finished 91m 52s 217ms

@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
53s 296ms 7

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

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

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

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

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

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

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

@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 22s 21ms 11 1

In Order to distribute software to the clients
As an authorized user
I want to create fake channels for each distribution

Scenario:
Log in as admin user
397ms 1

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

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

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

And I follow "Create Channel" 285ms

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

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

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

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

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

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

And I click on "Create Channel" 538ms

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

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

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

And I follow "Create Channel" 294ms

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

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

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

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

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

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

And I click on "Create Channel" 50ms

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

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

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

And I follow "Create Channel" 221ms

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

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

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

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

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

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

And I click on "Create Channel" 52ms

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

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

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

And I follow "Create Channel" 214ms

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

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

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

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

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

And I click on "Create Channel" 405ms

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

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

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

And I follow "Create Channel" 210ms

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

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

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

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

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

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

And I click on "Create Channel" 437ms

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

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

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

And I follow "Create Channel" 218ms

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

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

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

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

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

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

And I click on "Create Channel" 493ms

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

Scenario:
Add a child channel into the test base channel x86_64
900ms 10

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

And I follow "Create Channel" 317ms

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

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

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

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

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

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

And I click on "Create Channel" 52ms

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

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

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

And I follow "Create Channel" 235ms

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

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

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

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

And I uncheck "gpg_check" 10s 70ms

And I click on "Create Channel" 500ms

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

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

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

And I follow "Create Channel" 237ms

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

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

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

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

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

And I click on "Create Channel" 51ms

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

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

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

And I follow "Create Channel" 314ms

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

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

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

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

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

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

And I click on "Create Channel" 412ms

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

Feature:Create fake repositories for each fake child channel 47s 989ms 14 1

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

Scenario:
Log in as admin user
445ms 1

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

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

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

And I follow "Create Repository" 283ms

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

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

And I click on "Create Repository" 428ms

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

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

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

And I uncheck "metadataSigned" 10s 59ms

And I click on "Update Repository" 416ms

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

And I should see "metadataSigned" as unchecked 14ms

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

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

And I follow "Create Repository" 267ms

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

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

And I click on "Create Repository" 49ms

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

And I should see "metadataSigned" as checked 14ms

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

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

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

And I uncheck "metadataSigned" 10s 51ms

And I click on "Update Repository" 393ms

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

And I should see "metadataSigned" as unchecked 15ms

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

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

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

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

And I click on "Update Channel" 58ms

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

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

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

And I click on "Save Repositories" 522ms

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 657ms 9

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

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

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

And I click on "Update Channel" 468ms

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

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

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

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

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

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

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

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

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

And I click on "Update Channel" 51ms

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

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

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

And I click on "Save Repositories" 651ms

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

@rhlike_minion
Scenario:
Add the fake AppStream repository to the AppStream base channel
1s 861ms 9

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

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

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

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

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

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

And I click on "Save Repositories" 634ms

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

Scenario:
Create a fake repository for i586
10s 923ms 7

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

And I follow "Create Repository" 211ms

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

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

And I uncheck "metadataSigned" 10s 73ms

And I click on "Create Repository" 382ms

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

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

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

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

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

And I click on "Update Channel" 58ms

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

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

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

And I click on "Save Repositories" 512ms

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

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

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

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

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

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

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

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

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

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

And I follow "Create Repository" 206ms

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

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

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

And I click on "Create Repository" 396ms

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

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

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

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

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

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

And I click on "Save Repositories" 997ms

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

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

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

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

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

And I click on "Update Channel" 0s

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

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

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

And I click on "Save Repositories" 0s

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

@skip_if_github_validation
Feature:Create custom channels with development repositories 24s 317ms 9

In Order to use product packages in development to the clients
As an authorized user
I want to create custom channels for each distribution

Scenario:
Log in as admin user
420ms 1

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

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

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

And I follow "Create Channel" 333ms

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

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

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

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

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

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

And I click on "Create Channel" 58ms

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

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

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

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

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

And I follow "Create Channel" 312ms

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

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

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

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

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

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

And I click on "Create Channel" 504ms

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

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

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

@deblike_minion
Scenario:
Create a custom channel for Debian-like minions
924ms 10

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

And I follow "Create Channel" 313ms

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

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

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

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

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

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

And I click on "Create Channel" 51ms

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

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

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

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

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

And I follow "Create Channel" 245ms

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

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

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

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

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

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

And I click on "Create Channel" 51ms

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

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

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

Feature:Synchronize fake channels 1m 22s 163ms 12 2

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

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

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

And I enable source package syncing 979ms

@sle_minion
Scenario:
Synchronize Fake-RPM-SUSE-Channel channel
5s 300ms 9

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

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

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

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

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

And I follow "Sync" 305ms

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

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

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

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

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

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

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

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

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

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

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

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

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

And I follow "Sync" 293ms

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

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

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

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

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

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

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

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

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

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

And I follow "Sync" 286ms

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

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

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

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

@sle_minion
Scenario:
Synchronize Fake-Child-Channel-SUSE-like channel
28s 87ms 9

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

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

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

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

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

And I follow "Sync" 445ms

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

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

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

@deblike_minion
Scenario:
Synchronize Fake-Base-Channel-Debian-like channel
3s 866ms 9

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

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

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

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

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

And I follow "Sync" 293ms

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

And I click on "Sync Now" 585ms

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

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

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

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

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

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

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

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

And I follow "Sync" 585ms

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

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

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

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

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

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

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

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

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

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

And I follow "Sync" 512ms

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

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

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

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

@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
4s 436ms 6

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

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

And I follow "errata-cache-bunch" 339ms

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

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

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

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

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

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

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

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

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

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

Scenario:
Cleanup disable source package syncing
653ms 1

Then I disable source package syncing 653ms

@skip_if_github_validation
Feature:Synchronize development channels 2m 22s 967ms 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
28s 96ms 9

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

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

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

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

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

And I follow "Sync" 899ms

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

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

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

And I wait until the channel "devel-suse-channel" has been synced 24s 728ms

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

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

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

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

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

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

And I follow "Sync" 298ms

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

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

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

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

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

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

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

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

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

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

And I follow "Sync" 221ms

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

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

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

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

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

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

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

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

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

And I follow "Sync" 310ms

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

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

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

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

Feature:Create activation keys 12s 72ms 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
367ms 1

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

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

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

And I follow "Create Key" 306ms

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

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

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

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

And I click on "Create Activation Key" 670ms

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

And I should see a "Details" link 14ms

And I should see a "Packages" link 13ms

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

And I should see a "Groups" link 11ms

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

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

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

And I follow "Create Key" 255ms

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

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

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

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

And I click on "Create Activation Key" 55ms

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

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

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

And I follow "Create Key" 336ms

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

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

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

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

And I click on "Create Activation Key" 885ms

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

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

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

And I follow "Create Key" 330ms

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

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

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

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

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

And I click on "Create Activation Key" 56ms

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

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

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

And I follow "Create Key" 279ms

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

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

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

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

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

And I click on "Create Activation Key" 461ms

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

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

And I follow "Create Key" 276ms

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

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

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

And I click on "Create Activation Key" 677ms

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

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

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

And I follow "Create Key" 277ms

And I wait for child channels to appear 935ms

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

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

And I check "Container Build Host" 125ms

And I check "OS Image Build Host" 76ms

And I click on "Create Activation Key" 55ms

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

@scc_credentials
Scenario:
Create an activation key for the terminal
1s 582ms 7

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

And I follow "Create Key" 274ms

And I wait for child channels to appear 933ms

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

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

And I click on "Create Activation Key" 57ms

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

Feature:Update activation keys 19s 603ms 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
640ms 1

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

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

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 0s

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

@uyuni
Scenario:
Update openSUSE Leap key with synced base product
1s 737ms 10

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 526ms

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

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

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 0s

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

@uyuni
Scenario:
Update openSUSE Leap SSH key with synced base product
1s 710ms 10

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 499ms

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

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

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 0s

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

@uyuni
Scenario:
Update openSUSE Leap SSH tunnel key with synced base product
1s 831ms 10

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 484ms

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

@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
2s 856ms 20

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

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

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

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

And I wait for child channels to appear 361ms

And I include the recommended child channels 153ms

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

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

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 563ms

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

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

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

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

And I wait for child channels to appear 764ms

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

And I wait for child channels to appear 246ms

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

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

And I click on "Update Activation Key" 489ms

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

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

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

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

And I wait for child channels to appear 710ms

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

And I wait for child channels to appear 248ms

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

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

And I click on "Update Activation Key" 471ms

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

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

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

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

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

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

And I wait for child channels to appear 387ms

And I include the recommended child channels 142ms

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 465ms

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

@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
1s 578ms 6

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

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

And I wait for child channels to appear 759ms

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

And I click on "Update Activation Key" 553ms

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

@skip_if_github_validation @deblike_minion
Scenario:
Update Debian-like key with to include dev child channel
1s 519ms 6

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

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

And I wait for child channels to appear 754ms

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

And I click on "Update Activation Key" 461ms

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

@skip_if_github_validation @rhlike_minion
Scenario:
Update RedHat-like key with to include dev child channel
1s 515ms 6

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

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

And I wait for child channels to appear 753ms

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

And I click on "Update Activation Key" 481ms

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

Feature:Create bootstrap repositories 6s 289ms 4

In order to be able to enroll clients with MU repositories
As the system administrator
I create all bootstrap repos with --with-custom-channels option

Scenario:
Create the bootstrap repositories including custom channels
1s 364ms 1

When I create the bootstrap repositories including custom channels 1s 364ms

@sle_minion
Scenario:
Create the bootstrap repository for SUSE Minion
1s 614ms 1

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

When I create the bootstrap repository for "sle_minion" on the server 1s 614ms

@proxy
Scenario:
Create the bootstrap repository for Proxy
1s 640ms 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 1s 640ms

@build_host
Scenario:
Create the bootstrap repository for Build Host
1s 669ms 1

base_channel: SLE-Product-SLES15-SP4-Pool for x86_64
channel: SLE-15-SP4-x86_64
parent_channel: sle-product-sles15-sp4-pool-x86_64
Creating the bootstrap repository on the server:
mgr-create-bootstrap-repo --create SLE-15-SP4-x86_64 --with-parent-channel sle-product-sles15-sp4-pool-x86_64 --with-custom-channels

When I create the bootstrap repository for "build_host" on the server 1s 669ms

@transactional_server
Feature:SELinux debugging < 1ms 1

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

Scenario:
No previous operation has created wrong SELinux label
< 1ms 1

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

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

Scenario:
Call spacewalk-debug on server
14s 513ms 1

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

Scenario:
Check the tomcat logs on server
468ms 1

Then the tomcat logs should not contain errors 468ms

Scenario:
Check salt event log for failures on server
1s 114ms 1

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

Scenario:
Check the taskomatic logs on server
920ms 1

Then the taskomatic logs should not contain errors 920ms

Scenario:
Check for out of memory errors
459ms 1

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

Feature:Debug the clients after the testsuite has run 1m 24s 254ms 1

Scenario:
Extract the logs from all our clients
1m 24s 254ms 1

When I extract the log files from all our active nodes 1m 24s 254ms

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

Scenario:
Count UI SCC accesses in rhn_web_ui.log
< 1ms 1

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

Scenario:
Count Taskomatic SCC accesses in rhn_taskomatic_daemon.log
< 1ms 1

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