Cucumber Feature Report

All Scenarios

163

Passed Scenarios

128

Failed Scenarios

1

Skipped Scenarios

34

Execution Time: 88m 2s 630ms

Expand All | Collapse All

Metadata

App Version: Uyuni/Head

Browser: Chrome

Platform: x86_64

Parallel: Disabled

Feature:Sanity checks 1m 19s 889ms 10 2

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

Scenario:
The server is healthy

27s 112ms 11

Then "server" should have a FQDN 399ms

And reverse resolution should work for "server" 2s 493ms

And the clock from "server" should be exact 2s 519ms

And service "apache2" is active on "server" 2s 446ms

And service "cobblerd" is active on "server" 2s 506ms

And service "rhn-search" is active on "server" 2s 620ms

And service "salt-api" is active on "server" 4s 47ms

And service "salt-master" is active on "server" 2s 512ms

And service "taskomatic" is active on "server" 2s 497ms

And socket "tftp" is active on "server" 2s 594ms

And service "tomcat" is active on "server" 2s 473ms

@proxy

Scenario:
The proxy is healthy

6s 329ms 4

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

And reverse resolution should work for "proxy" 284ms

And "proxy" should communicate with the server using public interface 2s 795ms

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

@sle_minion

Scenario:
The minion is healthy

8s 155ms 4

Then "sle_minion" should have a FQDN 4s 388ms

And reverse resolution should work for "sle_minion" 416ms

And "sle_minion" should communicate with the server using public interface 2s 945ms

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

@build_host

Scenario:
The build host is healthy

6s 420ms 4

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

And reverse resolution should work for "build_host" 226ms

And "build_host" should communicate with the server using public interface 3s 354ms

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

@ssh_minion

Scenario:
The SSH minion is healthy

8s 71ms 4

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

And reverse resolution should work for "ssh_minion" 418ms

And "ssh_minion" should communicate with the server using public interface 2s 932ms

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

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

7s 195ms 4

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

And reverse resolution should work for "rhlike_minion" 184ms

And "rhlike_minion" should communicate with the server using public interface 4s 909ms

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

@deblike_minion

Scenario:
The Debian-like minion is healthy

7s 465ms 4

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

And reverse resolution should work for "deblike_minion" 208ms

And "deblike_minion" should communicate with the server using public interface 2s 708ms

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

@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

2s 507ms 1

Then it should be possible to reach the authenticated registry 2s 507ms

@no_auth_registry

Scenario:
The registry without authentication is healthy

4s 171ms 1

Then it should be possible to reach the not authenticated registry 4s 171ms

@custom_download_endpoint

Scenario:
The custom download endpoint is working

2s 459ms 1

Then it should be possible to use the custom download endpoint 2s 459ms

Feature:Very first settings 1m 3s 960ms 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

4s 389ms 1

When I run "rm -Rf /srv/salt/*" on "server" 4s 389ms

Scenario:
Log in as admin user

40s 738ms 1

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

Scenario:
Wait for refresh of list of products to finish

8s 14ms 1

When I wait until mgr-sync refresh is finished 8s 14ms

Scenario:
Create testing username

4s 87ms 12

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

And I follow "Create User" 916ms

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

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

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

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

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

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

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

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

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

And I should see a "testing" link 11ms

Scenario:
Grant testing user administrative priviledges

2s 130ms 10

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

And I follow "testing" 587ms

And I check "role_org_admin" 85ms

And I check "role_system_group_admin" 77ms

And I check "role_channel_admin" 83ms

And I check "role_activation_key_admin" 80ms

And I check "role_config_admin" 79ms

And I click on "Update" 910ms

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

And I should see a "testing" text 71ms

@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

4s 601ms 1

* Tue Mar 17 2026 Victor Zhestkov
- Backport security patch for Salt vendored tornado (bsc#1259554):
* CVE-2026-31958: Add limits on multipart form data parsing
- Added:
* backport-of-the-cve-2026-31958-fix-bsc-1259554.patch

* Fri Mar 13 2026 Victor Zhestkov
- Add x86_64_v2 as a possible rpm package architecture
- Make users with backslash working for salt-ssh (bsc#1254629)
- Fix ansible.playbooks extra-vars quoting (bsc#1257831)
- Fix virtualenv call in test helper to use proper python version
- Added:
* add-x86_64_v2-as-a-possible-rpm-package-architecture.patch
* make-users-with-backslash-working-for-salt-ssh-bsc-1.patch
* fix-ansible.playbooks-extra-vars-quoting-bsc-1257831.patch

When I query latest Salt changes on "server" 4s 601ms

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

7s 161ms 1

When I turn off disable_local_repos for all clients 7s 161ms

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 6s 715ms 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

2s 199ms 5

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

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

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

And I click on "Save Preferences" 1s 437ms

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

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

4s 516ms 5

Given I am authorized as "testing" with password "testing" 3s 479ms

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

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

And I click on "Save Preferences" 823ms

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

Feature:Prepare server for using Kiwi 6s 481ms 1

Scenario:
Create a Kiwi user with image administrators rights

6s 481ms 2

New user kiwikiwi created with roles: image_admin

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

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

Feature:Prepare server for using Docker 7s 353ms 2

Scenario:
Create a Docker user with image administrators rights

4s 297ms 2

New user docker created with roles: image_admin

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

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

@no_auth_registry

Scenario:
Create an image store without credentials

3s 56ms 7

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

And I follow "Create" 593ms

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

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

And I click on "create-btn" 85ms

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

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

Feature:Do not let Taskomatic tasks interfere with our CI tests 29s 648ms 3

Scenario:
Log in as admin user

20s 465ms 1

Given I am authorized for the "Admin" section 20s 465ms

Scenario:
Disable scheduled reposyncs

4s 739ms 5

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

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

And I choose "disabled" 54ms

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

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

Scenario:
Disable scheduled Cobbler syncs

4s 444ms 5

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

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

And I choose "disabled" 46ms

And I click on "Update Schedule" 53ms

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

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

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

Scenario:
List available channels

47s 20ms 5

When I refresh SCC 40s 261ms

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

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

3s 282ms 4

When I execute mgr-sync "list channels -e --no-optional" 3s 282ms

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

5s 117ms 2

When I execute mgr-sync "list products" 5s 117ms

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

3s 383ms 4

When I execute mgr-sync "list products --expand --filter x86_64" 3s 383ms

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 5s 123ms 3

When I remove the mgr-sync cache file 2s 500ms

And I execute mgr-sync refresh 1m 2s 623ms

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

Feature:Synchronize products in the products page of the Setup Wizard 66m 39s 36ms 9 9

@scc_credentials

Scenario:
Refresh SCC

37s 418ms 1

When I refresh SCC 37s 418ms

@scc_credentials

Scenario:
Let the products page appear

2s 315ms 6

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

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

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

Then I should see a "Arch" text 121ms

And I should see a "Channels" text 121ms

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

@scc_credentials

Scenario:
Use the products and architecture filters

2s 565ms 7

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

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

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

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

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

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

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

@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

4m 36s 298ms 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: 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" 10s 208ms

And I kill running spacewalk-repo-sync for "opensuse_tumbleweed-x86_64" channel 6s 648ms

And I use spacewalk-repo-sync to sync channel "opensuse_tumbleweed-x86_64" including only client tools dependencies 3m 9s 614ms

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

When I wait until all synchronized channels for "tumbleweed" have finished 45s 247ms

@containerized_server @proxy @uyuni

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

41s 259ms 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" 26s 800ms

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

@scc_credentials @uyuni @build_host

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

54m 58s 118ms 20

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: Found channel 'sle15-sp7-installer-updates-x86_64' at line 57. Checking for completion...
DEBUG: Sync for sle15-sp7-installer-updates-x86_64 still in progress (no completion message found).
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 / 64m 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 / 64m waiting for product 'sles15-sp7' synchronization
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
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 / 64m 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 / 64m 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 / 64m 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 / 64m 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 / 64m 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: 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: Found channel 'sles15-sp7-devel-uyuni-client-x86_64' at line 81. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sles15-sp7-devel-uyuni-client-x86_64 at line 85.
SUCCESS: sles15-sp7-devel-uyuni-client-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: Found channel 'sle-module-systems-management-15-sp7-updates-x86_64' at line 89. Checking for completion...
DEBUG: Sync for sle-module-systems-management-15-sp7-updates-x86_64 still in progress (no completion message found).
8m / 64m 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: 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: Found channel 'sle-module-systems-management-15-sp7-updates-x86_64' at line 89. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-systems-management-15-sp7-updates-x86_64 at line 93.
SUCCESS: sle-module-systems-management-15-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: Found channel 'sle-module-systems-management-15-sp7-pool-x86_64' at line 97. 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-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: Found channel 'sle-module-systems-management-15-sp7-pool-x86_64' at line 97. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-systems-management-15-sp7-pool-x86_64 at line 101.
SUCCESS: sle-module-systems-management-15-sp7-pool-x86_64 is fully synchronized.
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: 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: 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: 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: 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: Found channel 'sle-module-python3-15-sp7-updates-x86_64' at line 113. 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-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
9m / 64m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-python3-15-sp7-updates-x86_64' at line 113. 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-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: Found channel 'sle-module-python3-15-sp7-updates-x86_64' at line 113. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-python3-15-sp7-updates-x86_64 at line 117.
SUCCESS: sle-module-python3-15-sp7-updates-x86_64 is fully synchronized.
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-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: Found channel 'sle-module-desktop-applications15-sp7-updates-x86_64' at line 121. 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: 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: Found channel 'sle-module-desktop-applications15-sp7-updates-x86_64' at line 121. 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: 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: Found channel 'sle-module-desktop-applications15-sp7-updates-x86_64' at line 121. 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: 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: Found channel 'sle-module-desktop-applications15-sp7-updates-x86_64' at line 121. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-desktop-applications15-sp7-updates-x86_64 at line 125.
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: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
10m / 64m waiting for product 'sles15-sp7' synchronization
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: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 129. 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-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-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: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 129. 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-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-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: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 129. 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-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-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: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 129. 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-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-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: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 129. 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-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-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: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 129. 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-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 / 64m waiting for product 'sles15-sp7' synchronization
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: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 129. 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-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-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: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 129. 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-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-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: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 129. 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-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-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: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 129. 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-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-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: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 129. 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-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-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: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 129. 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-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 / 64m waiting for product 'sles15-sp7' synchronization
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: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 129. 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-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-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: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 129. 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-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-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: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 129. 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-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-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: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 129. 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-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-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: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 129. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-desktop-applications15-sp7-pool-x86_64 at line 133.
SUCCESS: sle-module-desktop-applications15-sp7-pool-x86_64 is fully synchronized.
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-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-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 / 64m waiting for product 'sles15-sp7' synchronization
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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
14m / 64m waiting for product 'sles15-sp7' synchronization
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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
15m / 64m waiting for product 'sles15-sp7' synchronization
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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
16m / 64m waiting for product 'sles15-sp7' synchronization
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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
17m / 64m waiting for product 'sles15-sp7' synchronization
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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
18m / 64m waiting for product 'sles15-sp7' synchronization
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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
19m / 64m waiting for product 'sles15-sp7' synchronization
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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
20m / 64m waiting for product 'sles15-sp7' synchronization
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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-devtools15-sp7-updates-x86_64 at line 141.
SUCCESS: sle-module-devtools15-sp7-updates-x86_64 is fully synchronized.
DEBUG: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 145. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-pool-x86_64 still in progress (no completion message found).
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: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 145. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-pool-x86_64 still in progress (no completion message found).
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: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 145. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-pool-x86_64 still in progress (no completion message found).
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: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 145. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-pool-x86_64 still in progress (no completion message found).
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: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 145. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-pool-x86_64 still in progress (no completion message found).
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: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 145. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-pool-x86_64 still in progress (no completion message found).
21m / 64m waiting for product 'sles15-sp7' synchronization
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: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 145. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-pool-x86_64 still in progress (no completion message found).
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: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 145. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-pool-x86_64 still in progress (no completion message found).
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: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 145. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-pool-x86_64 still in progress (no completion message found).
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: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 145. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-pool-x86_64 still in progress (no completion message found).
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: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 145. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-pool-x86_64 still in progress (no completion message found).
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: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 145. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-devtools15-sp7-pool-x86_64 at line 149.
SUCCESS: sle-module-devtools15-sp7-pool-x86_64 is fully synchronized.
22m / 64m waiting for product 'sles15-sp7' synchronization
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: Found channel 'sle-module-server-applications15-sp7-pool-x86_64' at line 153. 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: Found channel 'sle-module-server-applications15-sp7-pool-x86_64' at line 153. 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: Found channel 'sle-module-server-applications15-sp7-pool-x86_64' at line 153. 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: Found channel 'sle-module-server-applications15-sp7-pool-x86_64' at line 153. 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: Found channel 'sle-module-server-applications15-sp7-pool-x86_64' at line 153. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-server-applications15-sp7-pool-x86_64 at line 157.
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 161. Checking for completion...
DEBUG: Sync for sle-module-server-applications15-sp7-updates-x86_64 still in progress (no completion message found).
23m / 64m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-server-applications15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-server-applications15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-server-applications15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-server-applications15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-server-applications15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-server-applications15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-server-applications15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-server-applications15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-server-applications15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-server-applications15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-server-applications15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-server-applications15-sp7-updates-x86_64 still in progress (no completion message found).
24m / 64m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-server-applications15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-server-applications15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-server-applications15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-server-applications15-sp7-updates-x86_64 at line 165.
SUCCESS: sle-module-server-applications15-sp7-updates-x86_64 is fully synchronized.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 56ms

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

Then the SLE15 SP7 product should be added 7s 641ms

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

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

And I wait until all synchronized channels for "sles15-sp7" have finished 54m 25s 982ms

@proxy @susemanager @transactional_server

Scenario:
Add SL Micro 6.2 as base OS for proxy

< 1ms 14

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.2" as the filtered product description 0s

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

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

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

And I select "SUSE Multi-Linux Manager Client Tools for SLE 16 x86_64" as a product 0s

And I should see the "SUSE Multi-Linux Manager Client Tools for SLE 16 x86_64" selected 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.2 x86_64" product has been added 0s

And I wait until all synchronized channels for "sl-micro-6.2" 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" as a product 0s

Then I should see the "SUSE Linux Enterprise Server 15 SP7" 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" 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.2 with SL Micro 6.2 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.2" as the filtered product description 0s

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

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

And I select "SUSE Multi-Linux Manager Proxy Extension 5.2 x86_64 (BETA)" as a product 0s

Then I should see the "SUSE Multi-Linux Manager Proxy Extension 5.2 x86_64 (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 Multi-Linux Manager Proxy Extension 5.2 x86_64 (BETA)" product has been added 0s

And I wait until all synchronized channels for "suse-multi-linux-manager-proxy-52" 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.2 with SL Micro 6.2 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.2" as the filtered product description 0s

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

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

And I select "SUSE Multi-Linux Manager Retail Branch Server Extension 5.2 x86_64 (BETA)" as a product 0s

Then I should see the "SUSE Multi-Linux Manager Retail Branch Server Extension 5.2 x86_64 (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 Multi-Linux Manager Retail Branch Server Extension 5.2 x86_64 (BETA)" product has been added 0s

And I wait until all synchronized channels for "suse-multi-linux-manager-retail-branch-server-52" 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

4m 57s 277ms 2

SUCCESS: Channel opensuse_tumbleweed-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel opensuse_tumbleweed-x86_64 synchronization took 186 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 16 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 10 seconds.
SUCCESS: Channel opensuse_tumbleweed-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel opensuse_tumbleweed-x86_64 synchronization took 186 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 10 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 8 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 12 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 4 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 5 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 358 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 1090 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 45 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 44 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 49 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 103 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 314 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 73 seconds.
SUCCESS: Channel sle-module-devtools15-sp7-updates-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-module-devtools15-sp7-updates-x86_64 synchronization took 738 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 191 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 30 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 38 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 29 seconds.

When I wait until all synchronized channels have solved their dependencies 4m 57s 277ms

Then all channels have been synced without errors < 1ms

@scc_credentials @skip_if_github_validation

Scenario:
Detect product loading issues from the UI

43s 783ms 7

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

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

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

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

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

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

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

@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 26s 320ms 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

505ms 1

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

Scenario:
Add a fake base channel for x86_64

1s 826ms 10

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

And I follow "Create Channel" 419ms

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

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

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

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

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

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

And I click on "Create Channel" 640ms

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

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

1s 540ms 10

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

And I follow "Create Channel" 318ms

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

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

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

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

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

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

And I click on "Create Channel" 604ms

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

@sle_minion

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

1s 510ms 10

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

And I follow "Create Channel" 316ms

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

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

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

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

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

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

And I click on "Create Channel" 604ms

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

Scenario:
Add a fake base channel for i586

2s 727ms 10

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

And I follow "Create Channel" 437ms

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

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

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

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

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

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

And I click on "Create Channel" 1s 676ms

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

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

1s 429ms 10

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

And I follow "Create Channel" 330ms

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

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

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

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

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

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

And I click on "Create Channel" 498ms

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

Scenario:
Add a test base channel for x86_64

1s 493ms 10

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

And I follow "Create Channel" 335ms

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

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

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

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

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

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

And I click on "Create Channel" 562ms

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

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

1s 648ms 10

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

And I follow "Create Channel" 374ms

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

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

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

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

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

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

And I click on "Create Channel" 597ms

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

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

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

And I follow "Create Channel" 354ms

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

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

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

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

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

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

And I uncheck "gpg_check" 10s 70ms

And I click on "Create Channel" 545ms

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

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 9ms 10

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

And I follow "Create Channel" 367ms

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

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

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

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

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

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

And I click on "Create Channel" 58ms

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

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 35ms 10

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

And I follow "Create Channel" 382ms

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

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

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

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

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

And I click on "Create Channel" 57ms

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

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

519ms 1

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

Scenario:
Create a fake repository for distributions using RPM

1s 560ms 7

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

And I follow "Create Repository" 405ms

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

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

And I click on "Create Repository" 66ms

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

And I should see "metadataSigned" as checked 20ms

Scenario:
Disable metadata check for the fake RPM repository

11s 50ms 6

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

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

And I uncheck "metadataSigned" 10s 61ms

And I click on "Update Repository" 508ms

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

And I should see "metadataSigned" as unchecked 16ms

@rhlike_minion

Scenario:
Create a fake AppStream repository

1s 138ms 7

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

And I follow "Create Repository" 316ms

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

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

And I click on "Create Repository" 511ms

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

And I should see "metadataSigned" as checked 17ms

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

11s 88ms 6

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

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

And I uncheck "metadataSigned" 10s 56ms

And I click on "Update Repository" 472ms

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

And I should see "metadataSigned" as unchecked 16ms

@sle_minion

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

2s 553ms 9

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

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

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

And I click on "Update Channel" 795ms

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

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

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

And I click on "Save Repositories" 899ms

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

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

1s 721ms 9

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

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

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

And I click on "Update Channel" 58ms

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

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

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

And I click on "Save Repositories" 749ms

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

@rhlike_minion

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

2s 724ms 9

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

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

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

And I click on "Update Channel" 662ms

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

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

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

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

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

@rhlike_minion

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

2s 519ms 9

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

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

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

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

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

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

And I click on "Save Repositories" 897ms

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

Scenario:
Create a fake repository for i586

11s 144ms 7

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

And I follow "Create Repository" 322ms

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

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

And I uncheck "metadataSigned" 10s 79ms

And I click on "Create Repository" 439ms

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

Scenario:
Add the repository to the i586 channel

1s 577ms 9

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

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

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

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

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

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

And I click on "Save Repositories" 662ms

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

2s 700ms 6

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

And I follow "Fake-Child-Channel-SUSE-like" 1s 4ms

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

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

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

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

@deblike_minion

Scenario:
Create a fake repository for Debian-like

910ms 7

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

And I follow "Create Repository" 475ms

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

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

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

And I click on "Create Repository" 58ms

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

@deblike_minion

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

1s 575ms 6

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

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

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

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

And I click on "Save Repositories" 924ms

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

@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 33s 557ms 9

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

Scenario:
Log in as admin user

513ms 1

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

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 820ms 10

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

And I follow "Create Channel" 385ms

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

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

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

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

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

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

And I click on "Create Channel" 703ms

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

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

8s 316ms 1

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

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 548ms 10

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

And I follow "Create Channel" 378ms

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

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

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

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

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

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

And I click on "Create Channel" 541ms

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

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

4s 567ms 1

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

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

1s 701ms 10

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

And I follow "Create Channel" 491ms

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

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

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

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

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

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

And I click on "Create Channel" 589ms

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

@deblike_minion

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

8s 6ms 1

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

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 655ms 10

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

And I follow "Create Channel" 400ms

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

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

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

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

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

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

And I click on "Create Channel" 638ms

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

@rhlike_minion

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

5s 428ms 1

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

Feature:Synchronize fake channels 2m 18s 414ms 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

5s 683ms 2

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

And I enable source package syncing 5s 193ms

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

16s 992ms 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 479ms

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

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

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

And I follow "Sync" 446ms

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

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

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

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

@sle_minion

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

8s 724ms 2

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

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

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

17s 451ms 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 457ms

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

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

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

And I follow "Sync" 430ms

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

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

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

Scenario:
Synchronize Test-Child-Channel-x86_64 channel

16s 819ms 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 518ms

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

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

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

And I follow "Sync" 422ms

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

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

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

@sle_minion

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

16s 957ms 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 488ms

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

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

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

And I follow "Sync" 346ms

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

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

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

@deblike_minion

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

4s 555ms 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 504ms

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

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

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

And I follow "Sync" 366ms

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

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

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

@rhlike_minion

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

20s 288ms 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 448ms

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

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

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

And I follow "Sync" 1s 150ms

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" 2s 835ms

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

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

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

15s 916ms 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 522ms

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

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

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

And I follow "Sync" 362ms

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

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

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

@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 689ms 6

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

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

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

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

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

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

Scenario:
Refresh the channel's repository data

6s 399ms 6

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

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

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

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

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

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

Scenario:
Cleanup disable source package syncing

2s 936ms 1

Then I disable source package syncing 2s 936ms

@skip_if_github_validation
Feature:Synchronize development channels 1m 29s 251ms 4

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

@sle_minion

Scenario:
Synchronize Devel-SUSE-Channel channel

16s 926ms 9

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

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

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

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

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

And I follow "Sync" 349ms

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" 2s 772ms

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

And I wait until the channel "devel-suse-channel" has been synced 12s 549ms

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

15s 696ms 9

DEBUG: Found channel 'devel-debian-like-channel' at line 289. 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 289. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for devel-debian-like-channel at line 293.
SUCCESS: devel-debian-like-channel is fully synchronized.

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

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

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

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

And I follow "Sync" 365ms

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

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

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

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

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

39s 288ms 9

DEBUG: Found channel 'devel-rh-like-channel' at line 297. 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 297. 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 297. 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 297. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for devel-rh-like-channel at line 301.
SUCCESS: devel-rh-like-channel is fully synchronized.

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

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

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

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

And I follow "Sync" 340ms

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

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

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

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

17s 340ms 9

DEBUG: Found channel 'devel-build-host-channel' at line 305. 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 305. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for devel-build-host-channel at line 309.
SUCCESS: devel-build-host-channel is fully synchronized.

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

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

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

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

And I follow "Sync" 368ms

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

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

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

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

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

556ms 1

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

@sle_minion

Scenario:
Create an activation key with a channel

2s 75ms 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 687ms

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

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

1s 380ms 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" 951ms

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

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

1s 226ms 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" 861ms

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

@ssh_minion

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

1s 205ms 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" 836ms

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

@ssh_minion

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

1s 477ms 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" 921ms

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

@proxy

Scenario:
Create an activation key for the proxy

1s 628ms 2

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

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

@build_host

Scenario:
Create an activation key for the build host

1s 744ms 3

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

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

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

@scc_credentials

Scenario:
Create an activation key for the terminal

1s 412ms 2

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

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

Feature:Update activation keys 24s 405ms 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

506ms 1

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

@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 180ms 10

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 531ms

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

@scc_credentials @susemanager @ssh_minion

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

Scenario:
Update openSUSE Tumbleweed SSH key with synced base product

1s 890ms 10

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

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

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

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

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

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

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

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

@scc_credentials @susemanager @ssh_minion

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

Scenario:
Update openSUSE Tumbleweed SSH tunnel key with synced base product

2s 349ms 10

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 660ms

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

@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 "Multi-Linux-ManagerTools-SLE-16 for x86_64 6.2" has been checked 0s

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

And I check "SUSE-Multi-Linux-Manager-Retail-Branch-Server-5.2 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

5s 233ms 20

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

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

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

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

And I wait for child channels to appear 703ms

And I include the recommended child channels 177ms

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 728ms

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

@scc_credentials @uyuni @build_host

Scenario:
Update build host key with Uyuni client tools

2s 135ms 9

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

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

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

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

And I wait for child channels to appear 307ms

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

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

And I click on "Update Activation Key" 444ms

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

@skip_if_github_validation @scc_credentials @uyuni @build_host

Scenario:
Update build host key with dev child channel

1s 995ms 9

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

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

And I wait for child channels to appear 862ms

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

And I wait for child channels to appear 315ms

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

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

And I click on "Update Activation Key" 461ms

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

@scc_credentials @build_host

Scenario:
Update terminal key with synced base product

2s 808ms 16

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

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

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

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

And I wait for child channels to appear 525ms

And I include the recommended child channels 205ms

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

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

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

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

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

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

And I click on "Update Activation Key" 470ms

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

@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

2s 34ms 6

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

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

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

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

And I click on "Update Activation Key" 528ms

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

@skip_if_github_validation @deblike_minion

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

1s 767ms 6

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

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

And I wait for child channels to appear 984ms

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

And I click on "Update Activation Key" 470ms

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

@skip_if_github_validation @rhlike_minion

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

1s 504ms 6

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

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

And I wait for child channels to appear 834ms

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

And I click on "Update Activation Key" 352ms

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

Feature:Create bootstrap repositories 25s 288ms 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

5s 782ms 1

When I create the bootstrap repositories including custom channels 5s 782ms

@sle_minion

Scenario:
Create the bootstrap repository for SUSE Minion

7s 321ms 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 7s 321ms

@proxy

Scenario:
Create the bootstrap repository for Proxy

6s 145ms 1

When I create the bootstrap repository for "proxy" on the server 6s 145ms

@build_host

Scenario:
Create the bootstrap repository for Build Host

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

@containerized_server @scope_containerized_proxy @proxy @bug_reported
Feature:Setup containerized proxy 7m 1s 398ms 9 1 2

In order to use a containerized proxy with the server
As the system administrator
I want to register the containerized proxy on the server

Scenario:
Clean up sumaform leftovers on proxy

6s 698ms 1

When I perform a full salt minion cleanup on "proxy" 6s 698ms

@transactional_server

Scenario:
Reboot after clean up

< 1ms 1

When I reboot the "proxy" host through SSH, waiting until it comes back 0s

Scenario:
Log in as admin user

38s 2ms 1

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

Scenario:
Bootstrap the proxy host as a salt minion

38s 652ms 9

The hostname of proxy is uyuni-master-proxy.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 140ms

Then I should see a "Bootstrap Minions" text 81ms

When I enter the hostname of "proxy" as "hostname" 116ms

And I enter "22" as "port" 55ms

And I enter "root" as "user" 60ms

And I enter "linux" as "password" 58ms

And I select "1-PROXY-KEY-x86_64" from "activationKeys" 78ms

And I click on "Bootstrap" 64ms

And I wait until I see "Bootstrap process initiated." text 37s 997ms

@skip_if_cloud @transactional_server

Scenario:
Reboot the proxy host

< 1ms 1

When I reboot the "proxy" host through SSH, waiting until it comes back 0s

Scenario:
Wait until the proxy host appears

4m 34s 743ms 1 1

When I wait until onboarding is completed for "proxy" 4m 14s 201ms Show Error +

                                            
 execution expired (Timeout::Error)
./features/support/commonlib.rb:80:in `repeat_until_timeout'
./features/step_definitions/navigation_steps.rb:70:in `/^I wait until I see "([^"]*)" (text|regex), refreshing the page$/'
./features/step_definitions/navigation_steps.rb:133:in `/^I wait until I see the "([^"]*)" system, refreshing the page$/'
./features/step_definitions/navigation_steps.rb:129:in `/^I wait until I see the name of "([^"]*)", refreshing the page$/'
./features/step_definitions/setup_steps.rb:218:in `/^I wait at most (\d+) seconds until onboarding is completed for "([^"]*)"$/'
./features/step_definitions/setup_steps.rb:230:in `/^I wait until onboarding is completed for "([^"]*)"$/'
features/proxy/proxy_container.feature:47:in `I wait until onboarding is completed for "proxy"'

20s 542ms Show Info +

16:27:42:000 - 16:31:56:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/systems/list/all

Screenshot +

Scenario:
Generate containerized proxy configuration

13s 116ms 2

When I generate the configuration "/tmp/proxy_container_config.tar.gz" of containerized proxy on the server 10s 265ms

And I copy the configuration "/tmp/proxy_container_config.tar.gz" of containerized proxy from the server to the proxy 2s 850ms

Scenario:
Set up the containerized proxy service to support Avahi

< 1ms 1

Record not added - avahi domain was not detected

When I add avahi hosts in containerized proxy configuration < 1ms

Scenario:
Run a containerized proxy

24s 915ms 1

When I run "mgrpxy install podman /tmp/proxy_container_config.tar.gz" on "proxy" 24s 915ms

Scenario:
Wait until containerized proxy service is active

12s 938ms 10

And I wait until "uyuni-proxy-pod" service is active on "proxy" 450ms

And I wait until "uyuni-proxy-httpd" service is active on "proxy" 7s 647ms

And I wait until "uyuni-proxy-salt-broker" service is active on "proxy" 2s 642ms

And I wait until "uyuni-proxy-squid" service is active on "proxy" 276ms

And I wait until "uyuni-proxy-ssh" service is active on "proxy" 278ms

And I wait until "uyuni-proxy-tftpd" service is active on "proxy" 279ms

And I wait until port "8022" is listening on "proxy" container 297ms

And I wait until port "80" is listening on "proxy" container 294ms

And I wait until port "443" is listening on "proxy" container 292ms

And I visit "Proxy" endpoint of this "proxy" 479ms

Scenario:
The containerized proxy should be registered automatically

763ms 2

When I follow the left menu "Systems" 66ms

And I wait until I see the name of "proxy", refreshing the page 697ms

Scenario:
Check if Monitoring can be enabled on the containerized proxy

11s 567ms 3

Given I am on the Systems overview page of this "proxy" 1s 481ms

When I follow "Properties" in the content area 74ms

Then the "monitoring_entitled" checkbox should be disabled 10s 11ms

@containerized_server @scope_containerized_proxy @proxy @private_net
Feature:Prepare the containerized branch server for PXE booting < 1ms 3

In order to use a containerized proxy as a Retail Branch server
As the system administrator
I make sure the network setup is as expected

Scenario:
Adapt the proxy for Retail

< 1ms 3

When I rename the proxy for Retail 0s

And I connect the second interface of the proxy to the private network 0s

And I restart all proxy containers 0s

Scenario:
Check the branch network

< 1ms 2

Then the "dhcp_dns" host should be present on private network 0s

And name resolution should work on private network 0s

Scenario:
Let the server know about the new IP and FQDN of the containerized proxy

< 1ms 11

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

When I am on the Systems overview page of this "proxy" 0s

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

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

And I click on "Schedule Hardware Refresh" 0s

Then I should see a "You have successfully scheduled a hardware profile refresh" text 0s

When I wait until event "Hardware List Refresh scheduled by admin" is completed 0s

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "proxy" 0s

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

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

Then I should see a "proxy.example.org" text 0s

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

Scenario:
Call spacewalk-debug on server

16s 935ms 1

When I execute spacewalk-debug on the server 16s 935ms

Scenario:
Check the tomcat logs on server

2s 644ms 1

Then the tomcat logs should not contain errors 2s 644ms

Scenario:
Check salt event log for failures on server

3s 786ms 1

Then the salt event log on server should contain no failures 3s 786ms

Scenario:
Check the taskomatic logs on server

2s 507ms 1

Then the taskomatic logs should not contain errors 2s 507ms

Scenario:
Check for out of memory errors

4s 513ms 1

Then the log messages should not contain out of memory errors 4s 513ms

Feature:Debug the clients after the testsuite has run 1m 43s 936ms 1

Scenario:
Extract the logs from all our clients

1m 43s 936ms 1

When I extract the log files from all our active nodes 1m 43s 936ms

@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

163

Passed Scenarios

128

Failed Scenarios

1

Skipped Scenarios

34

@proxy Scenario:The proxy is healthy 6s 329ms 4

@sle_minion Scenario:The minion is healthy 8s 155ms 4

@build_host Scenario:The build host is healthy 6s 420ms 4

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

@rhlike_minion Scenario:The Red Hat-like minion is healthy 7s 195ms 4

@deblike_minion Scenario:The Debian-like minion is healthy 7s 465ms 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 2s 507ms 1

@no_auth_registry Scenario:The registry without authentication is healthy 4s 171ms 1

@custom_download_endpoint Scenario:The custom download endpoint is working 2s 459ms 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 3s 56ms 7

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

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

@scc_credentials Scenario:Refresh SCC 37s 418ms 1

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

@scc_credentials Scenario:Use the products and architecture filters 2s 565ms 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 4m 36s 298ms 5

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

@scc_credentials @uyuni @build_host Scenario:Synchronize SLES 15 SP7 product with recommended sub-products for Retail feature 54m 58s 118ms 20

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

@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.2 with SL Micro 6.2 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.2 with SL Micro 6.2 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 4m 57s 277ms 2

@scc_credentials @skip_if_github_validation Scenario:Detect product loading issues from the UI 43s 783ms 7

@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 510ms 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 594ms 11

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

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

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

@rhlike_minion Scenario:Disable metadata check for the fake AppStream repository 11s 88ms 6

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

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

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

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

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

@deblike_minion Scenario:Add the repository to the Debian-like base channel 1s 575ms 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 33s 557ms 9

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

@sle_minion Scenario:Create custom repositories inside the SUSE custom channel 8s 316ms 1

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

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

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

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

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

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

@sle_minion Scenario:Synchronize Fake-RPM-SUSE-Channel channel 16s 992ms 9

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

@skip_if_github_validation Scenario:Synchronize Fake-Child-Channel-i586 channel 17s 451ms 9

@sle_minion Scenario:Synchronize Fake-Child-Channel-SUSE-like channel 16s 957ms 9

@deblike_minion Scenario:Synchronize Fake-Base-Channel-Debian-like channel 4s 555ms 9

@rhlike_minion Scenario:Synchronize Fake-Base-Channel-RH-like channel 20s 288ms 9

@rhlike_minion Scenario:Synchronize Fake-Base-Channel-AppStream channel 15s 916ms 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 29s 251ms 4

@sle_minion Scenario:Synchronize Devel-SUSE-Channel channel 16s 926ms 9

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

@rhlike_minion Scenario:Synchronize Devel-RH-like-Channel channel 39s 288ms 9

@build_host @uyuni Scenario:Synchronize Devel-Build-Host-Channel channel 17s 340ms 9

@sle_minion Scenario:Create an activation key with a channel 2s 75ms 2

@proxy

Scenario:
The proxy is healthy

6s 329ms 4

@sle_minion

Scenario:
The minion is healthy

8s 155ms 4

@build_host

Scenario:
The build host is healthy

6s 420ms 4

@ssh_minion

Scenario:
The SSH minion is healthy

8s 71ms 4

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

7s 195ms 4

@deblike_minion

Scenario:
The Debian-like minion is healthy

7s 465ms 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

2s 507ms 1

@no_auth_registry

Scenario:
The registry without authentication is healthy

4s 171ms 1

@custom_download_endpoint

Scenario:
The custom download endpoint is working

2s 459ms 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

3s 56ms 7

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

@proxy @susemanager

Scenario:
List all products for SUSE Multi-Linux Manager

< 1ms 6

@scc_credentials

Scenario:
Refresh SCC

37s 418ms 1

@scc_credentials

Scenario:
Let the products page appear

2s 315ms 6

@scc_credentials

Scenario:
Use the products and architecture filters

2s 565ms 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

4m 36s 298ms 5

@containerized_server @proxy @uyuni

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

41s 259ms 2

@scc_credentials @uyuni @build_host

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

54m 58s 118ms 20

@proxy @susemanager @transactional_server

Scenario:
Add SL Micro 6.2 as base OS for proxy

< 1ms 14

@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.2 with SL Micro 6.2 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.2 with SL Micro 6.2 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

4m 57s 277ms 2

@scc_credentials @skip_if_github_validation

Scenario:
Detect product loading issues from the UI

43s 783ms 7

@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 510ms 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 594ms 11

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 9ms 10

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 35ms 10

@rhlike_minion

Scenario:
Create a fake AppStream repository

1s 138ms 7

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

11s 88ms 6

@sle_minion

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

2s 553ms 9

@rhlike_minion

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

2s 724ms 9

@rhlike_minion

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

2s 519ms 9

@sle_minion

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

2s 700ms 6

@deblike_minion

Scenario:
Create a fake repository for Debian-like

910ms 7

@deblike_minion

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

1s 575ms 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 33s 557ms 9

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 820ms 10

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

8s 316ms 1

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 548ms 10

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

4s 567ms 1

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

1s 701ms 10

@deblike_minion

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

8s 6ms 1

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 655ms 10

@rhlike_minion

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

5s 428ms 1

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

16s 992ms 9

@sle_minion

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

8s 724ms 2

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

17s 451ms 9

@sle_minion

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

16s 957ms 9

@deblike_minion

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

4s 555ms 9

@rhlike_minion

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

20s 288ms 9

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

15s 916ms 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 29s 251ms 4

@sle_minion

Scenario:
Synchronize Devel-SUSE-Channel channel

16s 926ms 9

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

15s 696ms 9

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

39s 288ms 9

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

17s 340ms 9

@sle_minion

Scenario:
Create an activation key with a channel

2s 75ms 2

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

1s 380ms 2

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

1s 226ms 2

@ssh_minion

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

1s 205ms 2

@ssh_minion

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

1s 477ms 2

@proxy

Scenario:
Create an activation key for the proxy

1s 628ms 2

@build_host

Scenario:
Create an activation key for the build host

1s 744ms 3

@scc_credentials

Scenario:
Create an activation key for the terminal

1s 412ms 2

@scc_credentials @susemanager

Scenario:
Update SLE key with synced base product

< 1ms 20