Cucumber Feature Report

All Scenarios

148

Passed Scenarios

114

Failed Scenarios

5

Skipped Scenarios

29

Execution Time: 61m 39s 268ms

Expand All | Collapse All

Metadata

App Version: Uyuni/Head

Browser: Chrome

Platform: x86_64

Parallel: Disabled

Feature:Sanity checks 45s 123ms 10 2

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

Scenario:
The server is healthy

11s 703ms 19

Then "server" should have a FQDN 377ms

And reverse resolution should work for "server" 601ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@proxy

Scenario:
The proxy is healthy

4s 522ms 4

Then "proxy" should have a FQDN 3s 52ms

And reverse resolution should work for "proxy" 285ms

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

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

@sle_minion

Scenario:
The minion is healthy

7s 783ms 4

Then "sle_minion" should have a FQDN 5s 543ms

And reverse resolution should work for "sle_minion" 596ms

And "sle_minion" should communicate with the server using public interface 1s 132ms

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

@build_host

Scenario:
The build host is healthy

3s 725ms 4

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

And reverse resolution should work for "build_host" 216ms

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

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

@ssh_minion

Scenario:
The SSH minion is healthy

6s 74ms 4

Then "ssh_minion" should have a FQDN 4s 222ms

And reverse resolution should work for "ssh_minion" 400ms

And "ssh_minion" should communicate with the server using public interface 1s 60ms

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

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 151ms 4

Then "rhlike_minion" should have a FQDN 1s 925ms

And reverse resolution should work for "rhlike_minion" 188ms

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

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

@deblike_minion

Scenario:
The Debian-like minion is healthy

6s 238ms 4

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

And reverse resolution should work for "deblike_minion" 240ms

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

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

@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

653ms 1

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

@no_auth_registry

Scenario:
The registry without authentication is healthy

648ms 1

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

@custom_download_endpoint

Scenario:
The custom download endpoint is working

622ms 1

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

Feature:Very first settings 51s 310ms 6 1

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

656ms 1

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

Scenario:
Log in as admin user

39s 604ms 1

Given I am authorized for the "Admin" section 39s 604ms

Scenario:
Wait for refresh of list of products to finish

4s 32ms 1

When I wait until mgr-sync refresh is finished 4s 32ms

Scenario:
Create testing username

3s 791ms 12

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

And I follow "Create User" 620ms

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

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

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

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

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

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

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

And I click on "Create Login" 2s 499ms

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

And I should see a "testing" link 11ms

Scenario:
Grant testing user administrative priviledges

2s 403ms 10

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

And I follow "testing" 576ms

And I check "role_org_admin" 86ms

And I check "role_system_group_admin" 79ms

And I check "role_channel_admin" 80ms

And I check "role_activation_key_admin" 80ms

And I check "role_config_admin" 77ms

And I click on "Update" 1s 205ms

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

And I should see a "testing" text 69ms

@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

822ms 1

* Mon Jan 19 2026 Marek Czernek
- Make syntax in httputil_test compatible with Python 3.6
- Fix KeyError in postgres module with PostgreSQL 17 (bsc#1254325)
- Added:
* fix-tornado-s-httputil_test-syntax-for-python-3.6.patch
* backport-add-maintain-m-privilege-to-postgres-module.patch

* Wed Jan 14 2026 Marek Czernek
- Use internal deb classes instead of external aptsource lib
- Speed up wheel key.finger call (bsc#1240532)
- Backport security patches for Salt vendored tornado:
* CVE-2025-67724: missing validation of supplied reason phrase (bsc#1254903)
* CVE-2025-67725: fix DoS via malicious HTTP request (bsc#1254905)
* CVE-2025-67726: fix HTTP header parameter parsing algorithm (bsc#1254904)
- Simplify and speed up utils.find_json function (bsc#1246130)

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

Feature:Turn "disable_local_repos" feature on highstate off 3s 698ms 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"

3s 698ms 1

When I turn off disable_local_repos for all clients 3s 698ms

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 4s 917ms 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 433ms 5

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

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

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

And I click on "Save Preferences" 673ms

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

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

3s 484ms 5

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

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

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

And I click on "Save Preferences" 649ms

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

Feature:Prepare server for using Kiwi 5s 936ms 1

Scenario:
Create a Kiwi user with image administrators rights

5s 936ms 2

New user kiwikiwi created with roles: image_admin

Given I am authorized for the "Admin" section 2s 209ms

When I create a user with name "kiwikiwi" and password "kiwikiwi" with roles "image_admin" 3s 726ms

Feature:Prepare server for using Docker 6s 883ms 2

Scenario:
Create a Docker user with image administrators rights

3s 918ms 2

New user docker created with roles: image_admin

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

When I create a user with name "docker" and password "docker" with roles "image_admin" 3s 488ms

@no_auth_registry

Scenario:
Create an image store without credentials

2s 964ms 7

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

And I follow "Create" 523ms

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

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

And I click on "create-btn" 187ms

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

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

Feature:Do not let Taskomatic tasks interfere with our CI tests 46s 750ms 3

Scenario:
Log in as admin user

37s 555ms 1

Given I am authorized for the "Admin" section 37s 555ms

Scenario:
Disable scheduled reposyncs

4s 706ms 5

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

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

And I choose "disabled" 53ms

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

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

Scenario:
Disable scheduled Cobbler syncs

4s 488ms 5

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

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

And I choose "disabled" 45ms

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

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

@scc_credentials
Feature:List available channels and enable them 1m 39s 476ms 5 1

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

Scenario:
List available channels

33s 802ms 5

When I refresh SCC 31s 461ms

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

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

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

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

Scenario:
List available mandatory channels

1s 437ms 4

When I execute mgr-sync "list channels -e --no-optional" 1s 437ms

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

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

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

Scenario:
List Server product

1s 424ms 2

When I execute mgr-sync "list products" 1s 424ms

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

@proxy @susemanager

Scenario:
List all products for SUSE Multi-Linux Manager

< 1ms 6

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

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

And I should get " [ ] SUSE Multi-Linux Manager Proxy Extension 5.1 x86_64" 0s

And I should get " [ ] SUSE Multi-Linux Manager Proxy Extension for SLE 5.1 x86_64" 0s

And I should get " [ ] (R) SUSE Multi-Linux Manager Client Tools for SUSE Liberty Linux 7, RHEL and clones 7 x86_64" 0s

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

Scenario:
List products with filter

1s 396ms 4

When I execute mgr-sync "list products --expand --filter x86_64" 1s 396ms

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

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

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

Scenario:
Let mgr-sync time out

1m 1s 415ms 3

When I remove the mgr-sync cache file 657ms

And I execute mgr-sync refresh 1m 758ms

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

Feature:Synchronize products in the products page of the Setup Wizard 49m 50s 263ms 6 3 9

@scc_credentials

Scenario:
Refresh SCC

28s 439ms 1

When I refresh SCC 28s 439ms

@scc_credentials

Scenario:
Let the products page appear

2s 7ms 6

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

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

And I wait until I see "Product Description" text 1s 3ms

Then I should see a "Arch" text 117ms

And I should see a "Channels" text 118ms

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

@scc_credentials

Scenario:
Use the products and architecture filters

2s 348ms 7

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

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

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

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

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

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

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

@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 SP7 product with recommended sub-products, including MLM Client Tools

< 1ms 30

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 wait until I see "SUSE Linux Enterprise Server 15 SP7 x86_64" text 0s

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

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

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

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

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

And I should see that the "Server Applications Module 15 SP7 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 SP7 x86_64" as a product 0s

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

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

And I should see the "Server Applications Module 15 SP7 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 SP7 x86_64" as a product 0s

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

Then the SLE15 SP7 product should be added 0s

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

@uyuni

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

2m 51s 883ms 5

Reposync of channel opensuse_tumbleweed-x86_64 killed
Channel opensuse_tumbleweed-uyuni-client-x86_64 added
Channel opensuse_tumbleweed-uyuni-client-devel-x86_64 added
DEBUG: Found channel 'opensuse_tumbleweed-x86_64' at line 9. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for opensuse_tumbleweed-x86_64 at line 13.
SUCCESS: opensuse_tumbleweed-x86_64 is fully synchronized.
DEBUG: Found channel 'opensuse_tumbleweed-uyuni-client-x86_64' at line 17. Checking for completion...
DEBUG: Sync for opensuse_tumbleweed-uyuni-client-x86_64 still in progress (no completion message found).
DEBUG: Channel 'opensuse_tumbleweed-uyuni-client-devel-x86_64' not found in reposync.log
DEBUG: Found channel 'opensuse_tumbleweed-uyuni-client-x86_64' at line 17. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for opensuse_tumbleweed-uyuni-client-x86_64 at line 21.
SUCCESS: opensuse_tumbleweed-uyuni-client-x86_64 is fully synchronized.
DEBUG: Channel 'opensuse_tumbleweed-uyuni-client-devel-x86_64' not found in reposync.log
DEBUG: Channel 'opensuse_tumbleweed-uyuni-client-devel-x86_64' not found in reposync.log
DEBUG: Found channel 'opensuse_tumbleweed-uyuni-client-devel-x86_64' at line 25. Checking for completion...
DEBUG: Sync for opensuse_tumbleweed-uyuni-client-devel-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'opensuse_tumbleweed-uyuni-client-devel-x86_64' at line 25. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for opensuse_tumbleweed-uyuni-client-devel-x86_64 at line 29.
SUCCESS: opensuse_tumbleweed-uyuni-client-devel-x86_64 is fully synchronized.

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

And I kill running spacewalk-repo-sync for "opensuse_tumbleweed-x86_64" channel 1s 443ms

And I use spacewalk-repo-sync to sync channel "opensuse_tumbleweed-x86_64" including only client tools dependencies 1m 37s 364ms

And I use spacewalk-common-channel to add all "tumbleweed-client-tools-x86_64" channels with arch "x86_64" 14s 665ms

When I wait until all synchronized channels for "tumbleweed" have finished 50s 610ms

@containerized_server @proxy @uyuni

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

34s 276ms 2

Channel opensuse_tumbleweed-x86_64 added
Channel opensuse_tumbleweed-uyuni-client-devel-x86_64 added
Channel uyuni-proxy-devel-tumbleweed-x86_64 added
DEBUG: Found channel 'opensuse_tumbleweed-x86_64' at line 9. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for opensuse_tumbleweed-x86_64 at line 13.
SUCCESS: opensuse_tumbleweed-x86_64 is fully synchronized.
DEBUG: Found channel 'opensuse_tumbleweed-uyuni-client-devel-x86_64' at line 25. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for opensuse_tumbleweed-uyuni-client-devel-x86_64 at line 29.
SUCCESS: opensuse_tumbleweed-uyuni-client-devel-x86_64 is fully synchronized.
DEBUG: Found channel 'uyuni-proxy-devel-tumbleweed-x86_64' at line 33. Checking for completion...
DEBUG: Sync for uyuni-proxy-devel-tumbleweed-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'uyuni-proxy-devel-tumbleweed-x86_64' at line 33. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for uyuni-proxy-devel-tumbleweed-x86_64 at line 37.
SUCCESS: uyuni-proxy-devel-tumbleweed-x86_64 is fully synchronized.

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

And I wait until all synchronized channels for "uyuni-proxy" have finished 14s 154ms

@scc_credentials @uyuni @build_host

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

43m 38s 754ms 20 1

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] [ ] SLE-Product-SLES15-SP4-Pool for x86_64 SUSE Linux Enterprise Server 15 SP4 x86_64 [sle-product-sles15-sp4-pool-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] [I] SLE-Product-SLES15-SP7-Pool for x86_64 SUSE Linux Enterprise Server 15 SP7 x86_64 [sle-product-sles15-sp7-pool-x86_64] [I] SLE-Module-Basesystem15-SP7-Pool for x86_64 Basesystem Module 15 SP7 x86_64 [sle-module-basesystem15-sp7-pool-x86_64] [I] SLE-Module-Basesystem15-SP7-Updates for x86_64 Basesystem Module 15 SP7 x86_64 [sle-module-basesystem15-sp7-updates-x86_64] [ ] SLE-Module-Containers15-SP7-Pool for x86_64 Containers Module 15 SP7 x86_64 [sle-module-containers15-sp7-pool-x86_64] [ ] SLE-Module-Containers15-SP7-Updates for x86_64 Containers Module 15 SP7 x86_64 [sle-module-containers15-sp7-updates-x86_64] [I] SLE-Module-Desktop-Applications15-SP7-Pool for x86_64 Desktop Applications Module 15 SP7 x86_64 [sle-module-desktop-applications15-sp7-pool-x86_64] [I] SLE-Module-Desktop-Applications15-SP7-Updates for x86_64 Desktop Applications Module 15 SP7 x86_64 [sle-module-desktop-applications15-sp7-updates-x86_64] [I] SLE-Module-DevTools15-SP7-Pool for x86_64 Development Tools Module 15 SP7 x86_64 [sle-module-devtools15-sp7-pool-x86_64] [I] SLE-Module-DevTools15-SP7-Updates for x86_64 Development Tools Module 15 SP7 x86_64 [sle-module-devtools15-sp7-updates-x86_64] [ ] SLE-Module-Live-Patching15-SP7-Pool for x86_64 SUSE Linux Enterprise Live Patching 15 SP7 x86_64 [sle-module-live-patching15-sp7-pool-x86_64] [ ] SLE-Module-Live-Patching15-SP7-Updates for x86_64 SUSE Linux Enterprise Live Patching 15 SP7 x86_64 [sle-module-live-patching15-sp7-updates-x86_64] [ ] SLE-Module-Public-Cloud15-SP7-Pool for x86_64 Public Cloud Module 15 SP7 x86_64 [sle-module-public-cloud15-sp7-pool-x86_64] [ ] SLE-Module-Public-Cloud15-SP7-Updates for x86_64 Public Cloud Module 15 SP7 x86_64 [sle-module-public-cloud15-sp7-updates-x86_64] [I] SLE-Module-Python3-15-SP7-Pool for x86_64 Python 3 Module 15 SP7 x86_64 [sle-module-python3-15-sp7-pool-x86_64] [I] SLE-Module-Python3-15-SP7-Updates for x86_64 Python 3 Module 15 SP7 x86_64 [sle-module-python3-15-sp7-updates-x86_64] [I] SLE-Module-Server-Applications15-SP7-Pool for x86_64 Server Applications Module 15 SP7 x86_64 [sle-module-server-applications15-sp7-pool-x86_64] [I] SLE-Module-Server-Applications15-SP7-Updates for x86_64 Server Applications Module 15 SP7 x86_64 [sle-module-server-applications15-sp7-updates-x86_64] [I] SLE-Module-Systems-Management-15-SP7-Pool for x86_64 Systems Management Module 15 SP7 x86_64 [sle-module-systems-management-15-sp7-pool-x86_64] [I] SLE-Module-Systems-Management-15-SP7-Updates for x86_64 Systems Management Module 15 SP7 x86_64 [sle-module-systems-management-15-sp7-updates-x86_64] [ ] SLE-Module-Web-Scripting15-SP7-Pool for x86_64 Web and Scripting Module 15 SP7 x86_64 [sle-module-web-scripting15-sp7-pool-x86_64] [ ] SLE-Module-Web-Scripting15-SP7-Updates for x86_64 Web and Scripting Module 15 SP7 x86_64 [sle-module-web-scripting15-sp7-updates-x86_64] [I] SLE-Product-SLES15-SP7-Updates for x86_64 SUSE Linux Enterprise Server 15 SP7 x86_64 [sle-product-sles15-sp7-updates-x86_64] [I] SLE15-SP7-Installer-Updates for x86_64 SUSE Linux Enterprise Server 15 SP7 x86_64 [sle15-sp7-installer-updates-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]
DEBUG: Found channel 'sle-product-sles15-sp7-pool-x86_64' at line 41. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-product-sles15-sp7-pool-x86_64 at line 45.
SUCCESS: sle-product-sles15-sp7-pool-x86_64 is fully synchronized.
DEBUG: Found channel 'sle-product-sles15-sp7-updates-x86_64' at line 49. Checking for completion...
DEBUG: Sync for sle-product-sles15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle15-sp7-installer-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-basesystem15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-basesystem15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-product-sles15-sp7-updates-x86_64' at line 49. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-product-sles15-sp7-updates-x86_64 at line 53.
SUCCESS: sle-product-sles15-sp7-updates-x86_64 is fully synchronized.
DEBUG: Found channel 'sle15-sp7-installer-updates-x86_64' at line 57. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle15-sp7-installer-updates-x86_64 at line 61.
SUCCESS: sle15-sp7-installer-updates-x86_64 is fully synchronized.
DEBUG: Found channel 'sle-module-basesystem15-sp7-pool-x86_64' at line 65. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-basesystem15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-pool-x86_64' at line 65. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-basesystem15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-pool-x86_64' at line 65. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-basesystem15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-pool-x86_64' at line 65. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-basesystem15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-pool-x86_64' at line 65. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-basesystem15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
1m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-basesystem15-sp7-pool-x86_64' at line 65. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-basesystem15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-pool-x86_64' at line 65. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-basesystem15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-pool-x86_64' at line 65. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-basesystem15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-pool-x86_64' at line 65. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-basesystem15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-pool-x86_64' at line 65. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-basesystem15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-pool-x86_64' at line 65. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-basesystem15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
2m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-basesystem15-sp7-pool-x86_64' at line 65. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-basesystem15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-pool-x86_64' at line 65. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-basesystem15-sp7-pool-x86_64 at line 69.
SUCCESS: sle-module-basesystem15-sp7-pool-x86_64 is fully synchronized.
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
3m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
4m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
5m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
6m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
7m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-basesystem15-sp7-updates-x86_64 at line 77.
SUCCESS: sle-module-basesystem15-sp7-updates-x86_64 is fully synchronized.
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-server-applications15-sp7-pool-x86_64' at line 81. Checking for completion...
DEBUG: Sync for sle-module-server-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-server-applications15-sp7-pool-x86_64' at line 81. Checking for completion...
DEBUG: Sync for sle-module-server-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-server-applications15-sp7-pool-x86_64' at line 81. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-server-applications15-sp7-pool-x86_64 at line 85.
SUCCESS: sle-module-server-applications15-sp7-pool-x86_64 is fully synchronized.
DEBUG: Found channel 'sle-module-server-applications15-sp7-updates-x86_64' at line 89. Checking for completion...
DEBUG: Sync for sle-module-server-applications15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-server-applications15-sp7-updates-x86_64' at line 89. Checking for completion...
DEBUG: Sync for sle-module-server-applications15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
8m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-server-applications15-sp7-updates-x86_64' at line 89. Checking for completion...
DEBUG: Sync for sle-module-server-applications15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-server-applications15-sp7-updates-x86_64' at line 89. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-server-applications15-sp7-updates-x86_64 at line 93.
SUCCESS: sle-module-server-applications15-sp7-updates-x86_64 is fully synchronized.
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-python3-15-sp7-updates-x86_64' at line 97. Checking for completion...
DEBUG: Sync for sle-module-python3-15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-python3-15-sp7-updates-x86_64' at line 97. Checking for completion...
DEBUG: Sync for sle-module-python3-15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-python3-15-sp7-pool-x86_64' at line 105. Checking for completion...
DEBUG: Sync for sle-module-python3-15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-python3-15-sp7-updates-x86_64' at line 97. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-python3-15-sp7-updates-x86_64 at line 101.
SUCCESS: sle-module-python3-15-sp7-updates-x86_64 is fully synchronized.
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-python3-15-sp7-pool-x86_64' at line 105. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-python3-15-sp7-pool-x86_64 at line 109.
SUCCESS: sle-module-python3-15-sp7-pool-x86_64 is fully synchronized.
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
9m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-systems-management-15-sp7-pool-x86_64' at line 113. Checking for completion...
DEBUG: Sync for sle-module-systems-management-15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-systems-management-15-sp7-pool-x86_64' at line 113. Checking for completion...
DEBUG: Sync for sle-module-systems-management-15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-systems-management-15-sp7-pool-x86_64' at line 113. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-systems-management-15-sp7-pool-x86_64 at line 117.
SUCCESS: sle-module-systems-management-15-sp7-pool-x86_64 is fully synchronized.
DEBUG: Found channel 'sle-module-systems-management-15-sp7-updates-x86_64' at line 121. Checking for completion...
DEBUG: Sync for sle-module-systems-management-15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-systems-management-15-sp7-updates-x86_64' at line 121. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-systems-management-15-sp7-updates-x86_64 at line 125.
SUCCESS: sle-module-systems-management-15-sp7-updates-x86_64 is fully synchronized.
DEBUG: Found channel 'sles15-sp7-devel-uyuni-client-x86_64' at line 129. Checking for completion...
DEBUG: Sync for sles15-sp7-devel-uyuni-client-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sles15-sp7-devel-uyuni-client-x86_64' at line 129. Checking for completion...
DEBUG: Sync for sles15-sp7-devel-uyuni-client-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sles15-sp7-devel-uyuni-client-x86_64' at line 129. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sles15-sp7-devel-uyuni-client-x86_64 at line 133.
SUCCESS: sles15-sp7-devel-uyuni-client-x86_64 is fully synchronized.
10m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
11m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
12m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
13m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-desktop-applications15-sp7-pool-x86_64 at line 141.
SUCCESS: sle-module-desktop-applications15-sp7-pool-x86_64 is fully synchronized.
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-updates-x86_64' at line 145. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-updates-x86_64' at line 145. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-updates-x86_64' at line 145. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-updates-x86_64' at line 145. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
14m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-updates-x86_64' at line 145. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-updates-x86_64' at line 145. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-desktop-applications15-sp7-updates-x86_64 at line 149.
SUCCESS: sle-module-desktop-applications15-sp7-updates-x86_64 is fully synchronized.
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 153. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 153. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 153. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 153. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 153. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-pool-x86_64 still in progress (no completion message found).
15m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 153. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 153. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 153. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 153. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 153. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 153. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-pool-x86_64 still in progress (no completion message found).
16m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 153. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 153. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-devtools15-sp7-pool-x86_64 at line 157.
SUCCESS: sle-module-devtools15-sp7-pool-x86_64 is fully synchronized.
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
17m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
18m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
19m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
20m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
21m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
22m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
23m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
Failed channels for product 'sles15-sp7': ["sle-module-devtools15-sp7-updates-x86_64"]. execution expired

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

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

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

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

And I enter "SUSE Linux Enterprise Server 15 SP7 x86_64" as the filtered product description 150ms

And I select "SUSE Linux Enterprise Server 15 SP7 x86_64" as a product 66ms

Then I should see the "SUSE Linux Enterprise Server 15 SP7 x86_64" selected 27ms

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

And I open the sub-list of the product "Basesystem Module 15 SP7 x86_64" 56ms

And I select "Desktop Applications Module 15 SP7 x86_64" as a product 62ms

Then I should see the "Desktop Applications Module 15 SP7 x86_64" selected 23ms

When I open the sub-list of the product "Desktop Applications Module 15 SP7 x86_64" 50ms

And I select "Development Tools Module 15 SP7 x86_64" as a product 62ms

Then I should see the "Development Tools Module 15 SP7 x86_64" selected 23ms

When I click the Add Product button 57ms

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

Then the SLE15 SP7 product should be added 2s 251ms

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

And I wait until I see "SUSE Linux Enterprise Server 15 SP7 x86_64" product has been added 12ms

And I wait until all synchronized channels for "sles15-sp7" have finished 43m 1ms Show Error +

                                            
 execution expired (Timeout::Error)
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/support/commonlib.rb:656:in `wait_for_channels'
./features/step_definitions/command_steps.rb:441:in `/^I wait until all synchronized channels for "([^"]*)" have finished$/'
features/reposync/srv_sync_products.feature:114:in `I wait until all synchronized channels for "sles15-sp7" have finished'

16s 135ms Show Info +

12:54:49:000 - 13:38:12:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/admin/setup/products

Screenshot +

@proxy @susemanager @transactional_server

Scenario:
Add SL Micro 6.1 as base OS for proxy

< 1ms 13

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

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

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

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

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

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

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

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

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

And I click the Add Product button 0s

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

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

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

@proxy @susemanager @skip_if_transactional_server

Scenario:
Add SLES 15 SP7 as base OS for proxy

< 1ms 11

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

@proxy @susemanager @transactional_server

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

< 1ms 13

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

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

@proxy @susemanager @skip_if_transactional_server

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

< 1ms 12

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

@proxy @susemanager @transactional_server

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

< 1ms 13

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

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

@proxy @susemanager @skip_if_transactional_server

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

< 1ms 12

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

@scc_credentials @susemanager

Scenario:
Installer update channels got enabled when products were added

< 1ms 2

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

And I should get " [I] SLE15-SP7-Installer-Updates for x86_64 SUSE Linux Enterprise Server 15 SP7 x86_64 [sle15-sp7-installer-updates-x86_64]" 0s

@scc_credentials

Scenario:
Verify all channels are solved

1m 40s 834ms 2 1

SUCCESS: Channel opensuse_tumbleweed-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel opensuse_tumbleweed-x86_64 synchronization took 95 seconds.
SUCCESS: Channel opensuse_tumbleweed-uyuni-client-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel opensuse_tumbleweed-uyuni-client-x86_64 synchronization took 13 seconds.
SUCCESS: Channel opensuse_tumbleweed-uyuni-client-devel-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel opensuse_tumbleweed-uyuni-client-devel-x86_64 synchronization took 13 seconds.
SUCCESS: Channel opensuse_tumbleweed-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel opensuse_tumbleweed-x86_64 synchronization took 95 seconds.
SUCCESS: Channel opensuse_tumbleweed-uyuni-client-devel-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel opensuse_tumbleweed-uyuni-client-devel-x86_64 synchronization took 13 seconds.
SUCCESS: Channel uyuni-proxy-devel-tumbleweed-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel uyuni-proxy-devel-tumbleweed-x86_64 synchronization took 11 seconds.
SUCCESS: Channel sle-product-sles15-sp7-pool-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-product-sles15-sp7-pool-x86_64 synchronization took 7 seconds.
SUCCESS: Channel sle-product-sles15-sp7-updates-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-product-sles15-sp7-updates-x86_64 synchronization took 3 seconds.
SUCCESS: Channel sle15-sp7-installer-updates-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle15-sp7-installer-updates-x86_64 synchronization took 4 seconds.
SUCCESS: Channel sle-module-basesystem15-sp7-pool-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-module-basesystem15-sp7-pool-x86_64 synchronization took 326 seconds.
SUCCESS: Channel sle-module-basesystem15-sp7-updates-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-module-basesystem15-sp7-updates-x86_64 synchronization took 826 seconds.
SUCCESS: Channel sle-module-python3-15-sp7-pool-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-module-python3-15-sp7-pool-x86_64 synchronization took 34 seconds.
SUCCESS: Channel sle-module-python3-15-sp7-updates-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-module-python3-15-sp7-updates-x86_64 synchronization took 37 seconds.
SUCCESS: Channel sle-module-server-applications15-sp7-pool-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-module-server-applications15-sp7-pool-x86_64 synchronization took 54 seconds.
SUCCESS: Channel sle-module-server-applications15-sp7-updates-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-module-server-applications15-sp7-updates-x86_64 synchronization took 81 seconds.
SUCCESS: Channel sle-module-desktop-applications15-sp7-pool-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-module-desktop-applications15-sp7-pool-x86_64 synchronization took 298 seconds.
SUCCESS: Channel sle-module-desktop-applications15-sp7-updates-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-module-desktop-applications15-sp7-updates-x86_64 synchronization took 57 seconds.
SUCCESS: Channel sle-module-devtools15-sp7-pool-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-module-devtools15-sp7-pool-x86_64 synchronization took 170 seconds.
SUCCESS: Channel sle-module-systems-management-15-sp7-pool-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-module-systems-management-15-sp7-pool-x86_64 synchronization took 34 seconds.
SUCCESS: Channel sle-module-systems-management-15-sp7-updates-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-module-systems-management-15-sp7-updates-x86_64 synchronization took 26 seconds.
SUCCESS: Channel sles15-sp7-devel-uyuni-client-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sles15-sp7-devel-uyuni-client-x86_64 synchronization took 24 seconds.

When I wait until all synchronized channels have solved their dependencies 1m 24s 719ms

Then all channels have been synced without errors < 1ms Show Error +

                                            
 Synchronization encountered errors:
* Download failed for: sle-module-devtools15-sp7-updates-x86_64 (ScriptError)
./features/step_definitions/command_steps.rb:475:in `/^all channels have been synced without errors$/'
features/reposync/srv_sync_products.feature:231:in `all channels have been synced without errors'

16s 114ms Show Info +

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

Screenshot +

@scc_credentials @skip_if_github_validation

Scenario:
Detect product loading issues from the UI

31s 719ms 7 1

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

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

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

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

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

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

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

                                            
 At least one product is not fully synchronized (ScriptError)
./features/step_definitions/navigation_steps.rb:849:in `/^I should only see success signs in the product list$/'
features/reposync/srv_sync_products.feature:242:in `I should only see success signs in the product list'

15s 898ms Show Info +

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

Screenshot +

@scc_credentials @skip_if_github_validation

Scenario:
Report the synchronization duration for SLES 15 SP7

< 1ms 1

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

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

474ms 1

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

Scenario:
Add a fake base channel for x86_64

1s 307ms 10

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

And I follow "Create Channel" 491ms

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

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

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

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

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

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

And I click on "Create Channel" 70ms

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

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

971ms 10

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

And I follow "Create Channel" 306ms

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

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

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

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

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

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

And I click on "Create Channel" 57ms

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

@sle_minion

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

1s 567ms 10

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

And I follow "Create Channel" 385ms

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

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

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

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

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

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

And I click on "Create Channel" 597ms

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

Scenario:
Add a fake base channel for i586

1s 463ms 10

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

And I follow "Create Channel" 320ms

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

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

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

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

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

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

And I click on "Create Channel" 563ms

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

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

1s 530ms 10

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

And I follow "Create Channel" 322ms

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

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

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

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

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

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

And I click on "Create Channel" 613ms

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

Scenario:
Add a test base channel for x86_64

1s 601ms 10

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

And I follow "Create Channel" 402ms

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

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

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

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

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

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

And I click on "Create Channel" 615ms

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

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

1s 87ms 10

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

And I follow "Create Channel" 416ms

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

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

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

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

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

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

And I click on "Create Channel" 57ms

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

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

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

And I follow "Create Channel" 258ms

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

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

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

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

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

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

And I uncheck "gpg_check" 10s 80ms

And I click on "Create Channel" 565ms

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

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 405ms 10

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

And I follow "Create Channel" 283ms

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

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

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

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

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

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

And I click on "Create Channel" 536ms

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

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 472ms 10

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

And I follow "Create Channel" 354ms

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

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

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

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

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

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

And I click on "Create Channel" 531ms

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

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

485ms 1

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

Scenario:
Create a fake repository for distributions using RPM

1s 184ms 7

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

And I follow "Create Repository" 335ms

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

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

And I click on "Create Repository" 426ms

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

And I should see "metadataSigned" as checked 19ms

Scenario:
Disable metadata check for the fake RPM repository

11s 16ms 6

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

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

And I uncheck "metadataSigned" 10s 90ms

And I click on "Update Repository" 452ms

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

And I should see "metadataSigned" as unchecked 16ms

@rhlike_minion

Scenario:
Create a fake AppStream repository

1s 33ms 7

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

And I follow "Create Repository" 310ms

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

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

And I click on "Create Repository" 54ms

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

And I should see "metadataSigned" as checked 17ms

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

10s 955ms 6

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

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

And I uncheck "metadataSigned" 10s 53ms

And I click on "Update Repository" 433ms

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

And I should see "metadataSigned" as unchecked 16ms

@sle_minion

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

2s 182ms 9

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

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

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

And I click on "Update Channel" 629ms

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

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

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

And I click on "Save Repositories" 595ms

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

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

2s 573ms 9

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

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

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

And I click on "Update Channel" 661ms

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

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

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

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

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

@rhlike_minion

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

2s 656ms 9

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

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

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

And I click on "Update Channel" 578ms

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

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

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

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

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

@rhlike_minion

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

2s 538ms 9

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

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

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

And I click on "Update Channel" 570ms

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

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

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

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

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

Scenario:
Create a fake repository for i586

11s 83ms 7

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

And I follow "Create Repository" 236ms

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

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

And I uncheck "metadataSigned" 10s 67ms

And I click on "Create Repository" 478ms

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

Scenario:
Add the repository to the i586 channel

1s 859ms 9

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

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

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

And I click on "Update Channel" 525ms

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

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

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

And I click on "Save Repositories" 508ms

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

@sle_minion

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

1s 706ms 6

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

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

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

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

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

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

@deblike_minion

Scenario:
Create a fake repository for Debian-like

1s 98ms 7

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

And I follow "Create Repository" 308ms

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

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

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

And I click on "Create Repository" 439ms

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

@deblike_minion

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

1s 309ms 6

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

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

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

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

And I click on "Save Repositories" 666ms

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

@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 39s 446ms 8 1

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

543ms 1

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

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 185ms 10

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

And I follow "Create Channel" 380ms

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

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

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

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

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

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

And I click on "Create Channel" 66ms

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

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

16s 955ms 1 1

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

                                            
 No FQDN for 'uyuni-master-suse-minion'. Response code:  (StandardError)
./features/support/remote_node.rb:46:in `initialize'
./features/support/remote_nodes_env.rb:39:in `new'
./features/support/remote_nodes_env.rb:39:in `get_target'
./features/step_definitions/setup_steps.rb:534:in `/^I prepare the development repositories of "([^"]*)" as part of "([^"]*)" channel$/'
features/reposync/srv_create_devel_channels.feature:28:in `I prepare the development repositories of "sle_minion" as part of "devel-suse-channel" channel'

15s 58ms Show Info +

13:42:13:000 - 13:42:15:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/manage/Edit.do?cid=131

Screenshot +

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 32ms 10

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

And I follow "Create Channel" 366ms

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

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

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

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

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

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

And I click on "Create Channel" 56ms

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

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

4s 552ms 1

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

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

1s 611ms 10

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

And I follow "Create Channel" 364ms

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

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

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

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

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

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

And I click on "Create Channel" 594ms

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

@deblike_minion

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

7s 766ms 1

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

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

931ms 10

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

And I follow "Create Channel" 275ms

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

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

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

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

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

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

And I click on "Create Channel" 56ms

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

@rhlike_minion

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

4s 865ms 1

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

Feature:Synchronize fake channels 1m 58s 766ms 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 866ms 2

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

And I enable source package syncing 1s 433ms

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

16s 168ms 9

DEBUG: Found channel 'fake-rpm-suse-channel' at line 225. Checking for completion...
DEBUG: Sync for fake-rpm-suse-channel still in progress (no completion message found).
DEBUG: Found channel 'fake-rpm-suse-channel' at line 225. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for fake-rpm-suse-channel at line 229.
SUCCESS: fake-rpm-suse-channel is fully synchronized.

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

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

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

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

And I follow "Sync" 425ms

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

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

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

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

@sle_minion

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

4s 752ms 2

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

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

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

15s 790ms 9

DEBUG: Found channel 'fake-child-channel-i586' at line 233. Checking for completion...
DEBUG: Sync for fake-child-channel-i586 still in progress (no completion message found).
DEBUG: Found channel 'fake-child-channel-i586' at line 233. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for fake-child-channel-i586 at line 237.
SUCCESS: fake-child-channel-i586 is fully synchronized.

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

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

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

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

And I follow "Sync" 336ms

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

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

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

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

Scenario:
Synchronize Test-Child-Channel-x86_64 channel

15s 674ms 9

DEBUG: Found channel 'test-child-channel-x86_64' at line 241. Checking for completion...
DEBUG: Sync for test-child-channel-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'test-child-channel-x86_64' at line 241. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for test-child-channel-x86_64 at line 245.
SUCCESS: test-child-channel-x86_64 is fully synchronized.

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

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

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

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

And I follow "Sync" 337ms

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

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

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

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

@sle_minion

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

15s 764ms 9

DEBUG: Found channel 'fake-child-channel-suse-like' at line 249. Checking for completion...
DEBUG: Sync for fake-child-channel-suse-like still in progress (no completion message found).
DEBUG: Found channel 'fake-child-channel-suse-like' at line 249. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for fake-child-channel-suse-like at line 253.
SUCCESS: fake-child-channel-suse-like is fully synchronized.

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

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

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

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

And I follow "Sync" 334ms

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

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

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

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

@deblike_minion

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

4s 565ms 9

DEBUG: Found channel 'fake-base-channel-debian-like' at line 257. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for fake-base-channel-debian-like at line 261.
SUCCESS: fake-base-channel-debian-like is fully synchronized.

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

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

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

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

And I follow "Sync" 335ms

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

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

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

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

@rhlike_minion

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

16s 726ms 9

DEBUG: Found channel 'fake-base-channel-rh-like' at line 265. Checking for completion...
DEBUG: Sync for fake-base-channel-rh-like still in progress (no completion message found).
DEBUG: Found channel 'fake-base-channel-rh-like' at line 265. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for fake-base-channel-rh-like at line 269.
SUCCESS: fake-base-channel-rh-like is fully synchronized.

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

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

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

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

And I follow "Sync" 1s 277ms

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

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

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

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

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

15s 747ms 9

DEBUG: Found channel 'fake-base-channel-appstream' at line 273. Checking for completion...
DEBUG: Sync for fake-base-channel-appstream still in progress (no completion message found).
DEBUG: Found channel 'fake-base-channel-appstream' at line 273. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for fake-base-channel-appstream at line 277.
SUCCESS: fake-base-channel-appstream is fully synchronized.

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

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

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

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

And I follow "Sync" 331ms

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

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

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

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

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Synchronize the repository in the terminal channel

< 1ms 9

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

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

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

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

And I follow "Sync" 0s

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

And I click on "Sync Now" 0s

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

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

@pxeboot_minion @uyuni @scc_credentials

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

< 1ms 2

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

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

Scenario:
Refresh the errata cache

5s 591ms 6

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

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

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

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

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

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

Scenario:
Refresh the channel's repository data

5s 160ms 6

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

And I follow "channel-repodata-default" 366ms

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

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

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

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

Scenario:
Cleanup disable source package syncing

958ms 1

Then I disable source package syncing 958ms

@skip_if_github_validation
Feature:Synchronize development channels 1m 50s 273ms 3 1

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

27s 868ms 8 1 1

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

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

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

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

And I follow "Sync" 499ms

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

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

Then I should see a "Repository sync scheduled for Devel-SUSE-Channel." text 10s 19ms Show Error +

                                            
 Text 'Repository sync scheduled for Devel-SUSE-Channel.' not found (ScriptError)
./features/step_definitions/navigation_steps.rb:655:in `/^I should see a "([^"]*)" text$/'
features/reposync/srv_sync_devel_channels.feature:19:in `I should see a "Repository sync scheduled for Devel-SUSE-Channel." text'

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

14s 942ms Show Info +

13:44:59:000 - 13:45:13:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/manage/Sync.do?cid=131

Screenshot +

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

16s 190ms 9

DEBUG: Found channel 'devel-debian-like-channel' at line 281. Checking for completion...
DEBUG: Sync for devel-debian-like-channel still in progress (no completion message found).
DEBUG: Found channel 'devel-debian-like-channel' at line 281. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for devel-debian-like-channel at line 285.
SUCCESS: devel-debian-like-channel is fully synchronized.

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

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

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

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

And I follow "Sync" 762ms

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

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

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

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

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

50s 548ms 9

DEBUG: Found channel 'devel-rh-like-channel' at line 289. Checking for completion...
DEBUG: Sync for devel-rh-like-channel still in progress (no completion message found).
DEBUG: Found channel 'devel-rh-like-channel' at line 289. Checking for completion...
DEBUG: Sync for devel-rh-like-channel still in progress (no completion message found).
DEBUG: Found channel 'devel-rh-like-channel' at line 289. Checking for completion...
DEBUG: Sync for devel-rh-like-channel still in progress (no completion message found).
DEBUG: Found channel 'devel-rh-like-channel' at line 289. Checking for completion...
DEBUG: Sync for devel-rh-like-channel still in progress (no completion message found).
DEBUG: Found channel 'devel-rh-like-channel' at line 289. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for devel-rh-like-channel at line 293.
SUCCESS: devel-rh-like-channel is fully synchronized.

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

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

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

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

And I follow "Sync" 341ms

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

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

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

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

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

15s 667ms 9

DEBUG: Found channel 'devel-build-host-channel' at line 297. Checking for completion...
DEBUG: Sync for devel-build-host-channel still in progress (no completion message found).
DEBUG: Found channel 'devel-build-host-channel' at line 297. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for devel-build-host-channel at line 301.
SUCCESS: devel-build-host-channel is fully synchronized.

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

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

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

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

And I follow "Sync" 341ms

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

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

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

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

Feature:Create activation keys 12s 98ms 9

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

Scenario:
Log in as admin user

419ms 1

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

@sle_minion

Scenario:
Create an activation key with a channel

1s 885ms 2

When I create an activation key with id "SUSE-KEY-x86_64", description "SUSE Test Key x86_64", limit of 20 and contact method "default" 1s 492ms

Then I should get the new activation key "1-SUSE-KEY-x86_64" 392ms

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

1s 320ms 2

When I create an activation key with id "RH-LIKE-KEY", description "RedHat like Test Key", base channel "fake-base-channel-rh-like", limit of 20 and contact method "default" 936ms

Then I should get the new activation key "1-RH-LIKE-KEY" 384ms

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

1s 221ms 2

When I create an activation key with id "DEBLIKE-KEY", description "Debian-like Test Key", base channel "fake-base-channel-debian-like", limit of 20 and contact method "default" 850ms

Then I should get the new activation key "1-DEBLIKE-KEY" 371ms

@ssh_minion

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

1s 193ms 2

When I create an activation key with id "SUSE-SSH-KEY-x86_64", description "SUSE SSH Test Key x86_64", limit of 20 and contact method "ssh-push" 822ms

Then I should get the new activation key "1-SUSE-SSH-KEY-x86_64" 371ms

@ssh_minion

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

1s 531ms 2

When I create an activation key with id "SUSE-SSH-TUNNEL-KEY-x86_64", description "SUSE SSH Tunnel Test Key x86_64", limit of 20 and contact method "ssh-push-tunnel" 969ms

Then I should get the new activation key "1-SUSE-SSH-TUNNEL-KEY-x86_64" 562ms

@proxy

Scenario:
Create an activation key for the proxy

1s 368ms 2

When I create an activation key with id "PROXY-KEY-x86_64", description "Proxy Key x86_64", limit of 1 958ms

Then I should get the new activation key "1-PROXY-KEY-x86_64" 409ms

@build_host

Scenario:
Create an activation key for the build host

1s 759ms 3

When I create an activation key with id "BUILD-HOST-KEY-x86_64", description "Build host Key x86_64" 876ms

And I set the entitlements of the activation key "1-BUILD-HOST-KEY-x86_64" to "container_build_host, osimage_build_host" 454ms

Then I should get the new activation key "1-BUILD-HOST-KEY-x86_64" 428ms

@scc_credentials

Scenario:
Create an activation key for the terminal

1s 398ms 2

When I create an activation key with id "TERMINAL-KEY-x86_64", description "Terminal Key x86_64" 977ms

Then I should get the new activation key "1-TERMINAL-KEY-x86_64" 420ms

Feature:Update activation keys 21s 412ms 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

486ms 1

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

@scc_credentials @susemanager

Scenario:
Update SLE key with synced base product

< 1ms 20

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

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

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

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

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

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

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

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

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

And I wait until "SLE-Module-Containers15-SP7-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 Tumbleweed key with synced base product

2s 387ms 10

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

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

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

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

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

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 847ms

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

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

And I click on "Update Activation Key" 543ms

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

@scc_credentials @susemanager

Scenario:
Update SLE SSH key with synced base product

< 1ms 14

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

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

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

And I wait until "SLE-Module-Desktop-Applications15-SP7-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 Tumbleweed SSH key with synced base product

2s 243ms 10

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

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

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

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

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

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 902ms

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

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

And I click on "Update Activation Key" 485ms

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

@scc_credentials @susemanager

Scenario:
Update SLE SSH tunnel key with synced base product

< 1ms 14

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

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

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

And I wait until "SLE-Module-Desktop-Applications15-SP7-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 Tumbleweed SSH tunnel key with synced base product

1s 973ms 10

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

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

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

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

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

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 571ms

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

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

And I click on "Update Activation Key" 551ms

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

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

Scenario:
Update build host key with synced base product

3s 82ms 20

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

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

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

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

And I wait for child channels to appear 595ms

And I include the recommended child channels 169ms

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

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

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

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

And I check "SLE-Module-DevTools15-SP7-Pool for x86_64" 79ms

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

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

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

And I wait until "SLE-Module-Systems-Management-15-SP7-Pool for x86_64" has been checked 19ms

And I wait until "SLE-Module-Systems-Management-15-SP7-Updates for x86_64" has been checked 19ms

And I wait until "SLE-Module-Python3-15-SP7-Pool for x86_64" has been checked 19ms

And I wait until "SLE-Module-Python3-15-SP7-Updates for x86_64" has been checked 19ms

And I click on "Update Activation Key" 511ms

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

@scc_credentials @uyuni @build_host

Scenario:
Update build host key with Uyuni client tools

2s 5ms 9

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

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

And I wait for child channels to appear 853ms

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

And I wait for child channels to appear 312ms

And I check "Uyuni Client Tools for SLES15 SP7 x86_64 (Development)" 81ms

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

And I click on "Update Activation Key" 491ms

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

@skip_if_github_validation @scc_credentials @uyuni @build_host

Scenario:
Update build host key with dev child channel

2s 32ms 9

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

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

And I wait for child channels to appear 944ms

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

And I wait for child channels to appear 311ms

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

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

And I click on "Update Activation Key" 458ms

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

@scc_credentials @build_host

Scenario:
Update terminal key with synced base product

2s 778ms 16

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

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

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

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

And I wait for child channels to appear 515ms

And I include the recommended child channels 160ms

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

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

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

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

And I check "SLE-Module-DevTools15-SP7-Pool for x86_64" 71ms

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

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

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

And I click on "Update Activation Key" 486ms

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

@susemanager @scc_credentials @build_host

Scenario:
Update terminal key with normal SUSE 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 "SLE-Module-Containers15-SP7-Pool for x86_64" 0s

And I wait until "SLE-Module-Containers15-SP7-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 Terminal Key x86_64 has been modified" text 0s

@pxeboot_minion @uyuni @scc_credentials @build_host

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 SP7 x86_64 (Development)" 0s

And I wait until "Uyuni Client Tools for SLES15 SP7 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 495ms 6

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

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

And I wait for child channels to appear 741ms

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

And I click on "Update Activation Key" 439ms

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

@skip_if_github_validation @deblike_minion

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

1s 483ms 6

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

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

And I wait for child channels to appear 737ms

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

And I click on "Update Activation Key" 435ms

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

@skip_if_github_validation @rhlike_minion

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

1s 444ms 6

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

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

And I wait for child channels to appear 672ms

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

And I click on "Update Activation Key" 461ms

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

Feature:Create bootstrap repositories 8s 502ms 4

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

Scenario:
Create the bootstrap repositories including custom channels

2s 151ms 1

When I create the bootstrap repositories including custom channels 2s 151ms

@sle_minion

Scenario:
Create the bootstrap repository for SUSE Minion

2s 33ms 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 "sle_minion" on the server 2s 33ms

@proxy

Scenario:
Create the bootstrap repository for Proxy

2s 37ms 1

When I create the bootstrap repository for "proxy" on the server 2s 37ms

@build_host

Scenario:
Create the bootstrap repository for Build Host

2s 279ms 1

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

When I create the bootstrap repository for "build_host" on the server 2s 279ms

@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 16s 635ms 5

Scenario:
Call spacewalk-debug on server

12s 997ms 1

When I execute spacewalk-debug on the server 12s 997ms

Scenario:
Check the tomcat logs on server

636ms 1

Then the tomcat logs should not contain errors 636ms

Scenario:
Check salt event log for failures on server

1s 683ms 1

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

Scenario:
Check the taskomatic logs on server

683ms 1

Then the taskomatic logs should not contain errors 683ms

Scenario:
Check for out of memory errors

634ms 1

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

Feature:Debug the clients after the testsuite has run 41s 697ms 1

Scenario:
Extract the logs from all our clients

41s 697ms 1

When I extract the log files from all our active nodes 41s 697ms

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

Scenario:
Count UI SCC accesses in rhn_web_ui.log

< 1ms 1

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

Scenario:
Count Taskomatic SCC accesses in rhn_taskomatic_daemon.log

< 1ms 1

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

All Scenarios

148

Passed Scenarios

114

Failed Scenarios

5

Skipped Scenarios

29

@proxy Scenario:The proxy is healthy 4s 522ms 4

@sle_minion Scenario:The minion is healthy 7s 783ms 4

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

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

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

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

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

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

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

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

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

@server_http_proxy Scenario:Setup HTTP proxy < 1ms 9

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

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

@scc_credentials Feature:List available channels and enable them 1m 39s 476ms 5 1

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

@scc_credentials Scenario:Refresh SCC 28s 439ms 1

@scc_credentials Scenario:Let the products page appear 2s 7ms 6

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

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

@scc_credentials @susemanager Scenario:Synchronize SLES 15 SP7 product with recommended sub-products, including MLM Client Tools < 1ms 30

@uyuni Scenario:Partially add openSUSE Tumbleweed product, only including the required packages to generate the bootstrap repository 2m 51s 883ms 5

@containerized_server @proxy @uyuni Scenario:Add Uyuni Proxy product for Tumbleweed, including Uyuni Client Tools 34s 276ms 2

@scc_credentials @uyuni @build_host Scenario:Synchronize SLES 15 SP7 product with recommended sub-products for Retail feature 43m 38s 754ms 20 1

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

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

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

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

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

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

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

@scc_credentials Scenario:Verify all channels are solved 1m 40s 834ms 2 1

@scc_credentials @skip_if_github_validation Scenario:Detect product loading issues from the UI 31s 719ms 7 1

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

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

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

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

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

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

@rhlike_minion Scenario:Create a fake AppStream repository 1s 33ms 7

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

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

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

@rhlike_minion Scenario:Add the fake AppStream repository to the AppStream base channel 2s 538ms 9

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

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

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

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

@skip_if_github_validation Feature:Create custom channels with development repositories 39s 446ms 8 1

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

@sle_minion Scenario:Create custom repositories inside the SUSE custom channel 16s 955ms 1 1

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

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

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

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

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

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

@sle_minion Scenario:Synchronize Fake-RPM-SUSE-Channel channel 16s 168ms 9

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

@skip_if_github_validation Scenario:Synchronize Fake-Child-Channel-i586 channel 15s 790ms 9

@sle_minion Scenario:Synchronize Fake-Child-Channel-SUSE-like channel 15s 764ms 9

@deblike_minion Scenario:Synchronize Fake-Base-Channel-Debian-like channel 4s 565ms 9

@rhlike_minion Scenario:Synchronize Fake-Base-Channel-RH-like channel 16s 726ms 9

@rhlike_minion Scenario:Synchronize Fake-Base-Channel-AppStream channel 15s 747ms 9

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

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

@skip_if_github_validation Feature:Synchronize development channels 1m 50s 273ms 3 1

@sle_minion Scenario:Synchronize Devel-SUSE-Channel channel 27s 868ms 8 1 1

@proxy

Scenario:
The proxy is healthy

4s 522ms 4

@sle_minion

Scenario:
The minion is healthy

7s 783ms 4

@build_host

Scenario:
The build host is healthy

3s 725ms 4

@ssh_minion

Scenario:
The SSH minion is healthy

6s 74ms 4

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 151ms 4

@deblike_minion

Scenario:
The Debian-like minion is healthy

6s 238ms 4

@skip_if_cloud

Scenario:
The external resources can be reached

< 1ms 3

@server_http_proxy

Scenario:
The HTTP proxy is working

< 1ms 1

@auth_registry

Scenario:
The registry with authentication is healthy

653ms 1

@no_auth_registry

Scenario:
The registry without authentication is healthy

648ms 1

@custom_download_endpoint

Scenario:
The custom download endpoint is working

622ms 1

@server_http_proxy

Scenario:
Setup HTTP proxy

< 1ms 9

@scc_credentials @no_mirror

Scenario:
Enter valid SCC credentials

< 1ms 6

@no_auth_registry

Scenario:
Create an image store without credentials

2s 964ms 7

@scc_credentials
Feature:List available channels and enable them 1m 39s 476ms 5 1

@proxy @susemanager

Scenario:
List all products for SUSE Multi-Linux Manager

< 1ms 6

@scc_credentials

Scenario:
Refresh SCC

28s 439ms 1

@scc_credentials

Scenario:
Let the products page appear

2s 7ms 6

@scc_credentials

Scenario:
Use the products and architecture filters

2s 348ms 7

@scc_credentials @susemanager

Scenario:
View the channels list in the products page

< 1ms 9

@scc_credentials @susemanager

Scenario:
Synchronize SLES 15 SP7 product with recommended sub-products, including MLM Client Tools

< 1ms 30

@uyuni

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

2m 51s 883ms 5

@containerized_server @proxy @uyuni

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

34s 276ms 2

@scc_credentials @uyuni @build_host

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

43m 38s 754ms 20 1

@proxy @susemanager @transactional_server

Scenario:
Add SL Micro 6.1 as base OS for proxy

< 1ms 13

@proxy @susemanager @skip_if_transactional_server

Scenario:
Add SLES 15 SP7 as base OS for proxy

< 1ms 11

@proxy @susemanager @transactional_server

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

< 1ms 13

@proxy @susemanager @skip_if_transactional_server

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

< 1ms 12

@proxy @susemanager @transactional_server

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

< 1ms 13

@proxy @susemanager @skip_if_transactional_server

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

< 1ms 12

@scc_credentials @susemanager

Scenario:
Installer update channels got enabled when products were added

< 1ms 2

@scc_credentials

Scenario:
Verify all channels are solved

1m 40s 834ms 2 1

@scc_credentials @skip_if_github_validation

Scenario:
Detect product loading issues from the UI

31s 719ms 7 1

@scc_credentials @skip_if_github_validation

Scenario:
Report the synchronization duration for SLES 15 SP7

< 1ms 1

@sle_minion

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

1s 567ms 10

@pxeboot_minion @uyuni @scc_credentials

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

< 1ms 10

@deblike_minion

Scenario:
Add Debian-like AMD64 base channel

11s 508ms 11

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 405ms 10

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 472ms 10

@rhlike_minion

Scenario:
Create a fake AppStream repository

1s 33ms 7

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

10s 955ms 6

@sle_minion

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

2s 182ms 9

@rhlike_minion

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

2s 656ms 9

@rhlike_minion

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

2s 538ms 9

@sle_minion

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

1s 706ms 6

@deblike_minion

Scenario:
Create a fake repository for Debian-like

1s 98ms 7

@deblike_minion

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

1s 309ms 6

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Add the repository to the terminal child channel

< 1ms 9

@skip_if_github_validation
Feature:Create custom channels with development repositories 39s 446ms 8 1

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 185ms 10

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

16s 955ms 1 1

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 32ms 10

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

4s 552ms 1

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

1s 611ms 10

@deblike_minion

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

7s 766ms 1

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

931ms 10

@rhlike_minion

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

4s 865ms 1

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

16s 168ms 9

@sle_minion

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

4s 752ms 2

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

15s 790ms 9

@sle_minion

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

15s 764ms 9

@deblike_minion

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

4s 565ms 9

@rhlike_minion

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

16s 726ms 9

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

15s 747ms 9

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Synchronize the repository in the terminal channel

< 1ms 9

@pxeboot_minion @uyuni @scc_credentials

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

< 1ms 2

@skip_if_github_validation
Feature:Synchronize development channels 1m 50s 273ms 3 1

@sle_minion

Scenario:
Synchronize Devel-SUSE-Channel channel

27s 868ms 8 1 1