Cucumber Feature Report

All Scenarios

148

Passed Scenarios

116

Failed Scenarios

3

Skipped Scenarios

29

Execution Time: 62m 6s 126ms

Expand All | Collapse All

Metadata

App Version: Uyuni/Head

Browser: Chrome

Platform: x86_64

Parallel: Disabled

Feature:Sanity checks 43s 735ms 10 2

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

Scenario:
The server is healthy

12s 16ms 19

Then "server" should have a FQDN 390ms

And reverse resolution should work for "server" 640ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@proxy

Scenario:
The proxy is healthy

4s 495ms 4

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

And reverse resolution should work for "proxy" 287ms

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

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

@sle_minion

Scenario:
The minion is healthy

6s 222ms 4

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

And reverse resolution should work for "sle_minion" 408ms

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

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

@build_host

Scenario:
The build host is healthy

3s 794ms 4

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

And reverse resolution should work for "build_host" 222ms

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

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

@ssh_minion

Scenario:
The SSH minion is healthy

6s 373ms 4

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

And reverse resolution should work for "ssh_minion" 426ms

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

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

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 146ms 4

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

And reverse resolution should work for "rhlike_minion" 191ms

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

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

@deblike_minion

Scenario:
The Debian-like minion is healthy

5s 734ms 4

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

And reverse resolution should work for "deblike_minion" 205ms

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

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

@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

661ms 1

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

@no_auth_registry

Scenario:
The registry without authentication is healthy

648ms 1

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

@custom_download_endpoint

Scenario:
The custom download endpoint is working

642ms 1

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

Feature:Very first settings 52s 134ms 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

666ms 1

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

Scenario:
Log in as admin user

39s 646ms 1

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

Scenario:
Wait for refresh of list of products to finish

4s 438ms 1

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

Scenario:
Create testing username

3s 795ms 12

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

And I follow "Create User" 584ms

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

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

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

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

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

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

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

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

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

And I should see a "testing" link 13ms

Scenario:
Grant testing user administrative priviledges

2s 590ms 10

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

And I follow "testing" 654ms

And I check "role_org_admin" 86ms

And I check "role_system_group_admin" 78ms

And I check "role_channel_admin" 78ms

And I check "role_activation_key_admin" 77ms

And I check "role_config_admin" 79ms

And I click on "Update" 1s 306ms

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

And I should see a "testing" text 75ms

@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

997ms 1

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

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

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

Feature:Turn "disable_local_repos" feature on highstate off 3s 720ms 1

In order to test the product using shortcuts
As root user
I want to add pillar data to disable that feature

Scenario:
Create custom pillar to turn off "disable_local_repos"

3s 720ms 1

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

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 5s 280ms 2

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

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

1s 590ms 5

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

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

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

And I click on "Save Preferences" 731ms

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

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

3s 690ms 5

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

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

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

And I click on "Save Preferences" 752ms

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

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

Scenario:
Create a Kiwi user with image administrators rights

6s 871ms 2

New user kiwikiwi created with roles: image_admin

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

When I create a user with name "kiwikiwi" and password "kiwikiwi" with roles "image_admin" 4s 52ms

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

Scenario:
Create a Docker user with image administrators rights

4s 236ms 2

New user docker created with roles: image_admin

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

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

@no_auth_registry

Scenario:
Create an image store without credentials

2s 966ms 7

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

And I follow "Create" 487ms

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

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

And I click on "create-btn" 61ms

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

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

Feature:Do not let Taskomatic tasks interfere with our CI tests 47s 331ms 3

Scenario:
Log in as admin user

37s 908ms 1

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

Scenario:
Disable scheduled reposyncs

4s 855ms 5

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

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

And I choose "disabled" 55ms

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

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

Scenario:
Disable scheduled Cobbler syncs

4s 567ms 5

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

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

And I choose "disabled" 45ms

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

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

@scc_credentials
Feature:List available channels and enable them 1m 41s 158ms 5 1

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

Scenario:
List available channels

35s 163ms 5

When I refresh SCC 32s 879ms

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

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

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

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

Scenario:
List available mandatory channels

1s 446ms 4

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

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

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

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

Scenario:
List Server product

1s 585ms 2

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

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

@proxy @susemanager

Scenario:
List all products for SUSE Multi-Linux Manager

< 1ms 6

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

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

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

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

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

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

Scenario:
List products with filter

1s 515ms 4

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

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

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

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

Scenario:
Let mgr-sync time out

1m 1s 447ms 3

When I remove the mgr-sync cache file 677ms

And I execute mgr-sync refresh 1m 769ms

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

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

@scc_credentials

Scenario:
Refresh SCC

29s 868ms 1

When I refresh SCC 29s 868ms

@scc_credentials

Scenario:
Let the products page appear

2s 58ms 6

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

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

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

Then I should see a "Arch" text 120ms

And I should see a "Channels" text 129ms

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

@scc_credentials

Scenario:
Use the products and architecture filters

2s 572ms 7

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

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

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

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

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

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

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

@scc_credentials @susemanager

Scenario:
View the channels list in the products page

< 1ms 9

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

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

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

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

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

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

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

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

When I close the modal dialog 0s

@scc_credentials @susemanager

Scenario:
Synchronize SLES 15 SP7 product with recommended sub-products, including MLM Client Tools

< 1ms 30

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

Then the SLE15 SP7 product should be added 0s

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

@uyuni

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

2m 47s 561ms 5

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

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

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

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

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

When I wait until all synchronized channels for "tumbleweed" have finished 51s 592ms

@containerized_server @proxy @uyuni

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

34s 832ms 2

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

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

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

@scc_credentials @uyuni @build_host

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

43m 41s 65ms 20 1

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 59ms

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

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

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

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

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

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

17s 804ms Show Info +

16:25:02:000 - 17:08:26:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/admin/setup/products

Screenshot +

@proxy @susemanager @transactional_server

Scenario:
Add SL Micro 6.1 as base OS for proxy

< 1ms 13

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

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

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

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

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

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

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

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

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

And I click the Add Product button 0s

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

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

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

@proxy @susemanager @skip_if_transactional_server

Scenario:
Add SLES 15 SP7 as base OS for proxy

< 1ms 11

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

@proxy @susemanager @transactional_server

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

< 1ms 13

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

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

@proxy @susemanager @skip_if_transactional_server

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

< 1ms 12

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

@proxy @susemanager @transactional_server

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

< 1ms 13

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

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

@proxy @susemanager @skip_if_transactional_server

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

< 1ms 12

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

@scc_credentials @susemanager

Scenario:
Installer update channels got enabled when products were added

< 1ms 2

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

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

@scc_credentials

Scenario:
Verify all channels are solved

1m 47s 150ms 2 1

SUCCESS: Channel opensuse_tumbleweed-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel opensuse_tumbleweed-x86_64 synchronization took 88 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 11 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 9 seconds.
SUCCESS: Channel opensuse_tumbleweed-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel opensuse_tumbleweed-x86_64 synchronization took 88 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 9 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 7 seconds.
SUCCESS: Channel sle-product-sles15-sp7-pool-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-product-sles15-sp7-pool-x86_64 synchronization took 7 seconds.
SUCCESS: Channel sle-product-sles15-sp7-updates-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-product-sles15-sp7-updates-x86_64 synchronization took 3 seconds.
SUCCESS: Channel sle15-sp7-installer-updates-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle15-sp7-installer-updates-x86_64 synchronization took 4 seconds.
SUCCESS: Channel sle-module-basesystem15-sp7-pool-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-module-basesystem15-sp7-pool-x86_64 synchronization took 329 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 850 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 35 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 45 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 52 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 83 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 309 seconds.
SUCCESS: Channel sle-module-desktop-applications15-sp7-updates-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-module-desktop-applications15-sp7-updates-x86_64 synchronization took 57 seconds.
SUCCESS: Channel sle-module-devtools15-sp7-pool-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-module-devtools15-sp7-pool-x86_64 synchronization took 148 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 26 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 34 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 26 seconds.

When I wait until all synchronized channels have solved their dependencies 1m 31s 398ms

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

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

15s 751ms Show Info +

17:08:44:000 - 17:10:16:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/admin/setup/products

Screenshot +

@scc_credentials @skip_if_github_validation

Scenario:
Detect product loading issues from the UI

32s 379ms 7 1

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

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

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

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

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

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

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

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

16s 860ms Show Info +

17:10:32:000 - 17:10:48:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/admin/setup/products

Screenshot +

@scc_credentials @skip_if_github_validation

Scenario:
Report the synchronization duration for SLES 15 SP7

< 1ms 1

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

Feature:Create fake channels 26s 869ms 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

587ms 1

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

Scenario:
Add a fake base channel for x86_64

1s 871ms 10

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

And I follow "Create Channel" 464ms

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

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

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

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

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

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

And I click on "Create Channel" 677ms

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

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

1s 687ms 10

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

And I follow "Create Channel" 409ms

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

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

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

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

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

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

And I click on "Create Channel" 680ms

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

@sle_minion

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

1s 878ms 10

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

And I follow "Create Channel" 409ms

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

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

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

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

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

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

And I click on "Create Channel" 887ms

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

Scenario:
Add a fake base channel for i586

1s 678ms 10

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

And I follow "Create Channel" 419ms

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

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

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

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

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

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

And I click on "Create Channel" 680ms

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

981ms 10

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

And I follow "Create Channel" 347ms

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

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

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

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

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

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

And I click on "Create Channel" 55ms

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

Scenario:
Add a test base channel for x86_64

1s 785ms 10

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

And I follow "Create Channel" 436ms

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

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

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

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

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

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

And I click on "Create Channel" 781ms

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

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

1s 611ms 10

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

And I follow "Create Channel" 432ms

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

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

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

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

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

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

And I click on "Create Channel" 576ms

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

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

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

And I follow "Create Channel" 356ms

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

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

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

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

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

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

And I uncheck "gpg_check" 10s 87ms

And I click on "Create Channel" 616ms

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

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 477ms 10

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

And I follow "Create Channel" 354ms

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

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

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

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

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

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

And I click on "Create Channel" 559ms

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

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 661ms 10

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

And I follow "Create Channel" 452ms

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

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

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

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

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

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

And I click on "Create Channel" 641ms

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

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

560ms 1

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

Scenario:
Create a fake repository for distributions using RPM

952ms 7

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

And I follow "Create Repository" 474ms

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

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

And I click on "Create Repository" 68ms

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

And I should see "metadataSigned" as checked 20ms

Scenario:
Disable metadata check for the fake RPM repository

11s 113ms 6

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

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

And I uncheck "metadataSigned" 10s 86ms

And I click on "Update Repository" 567ms

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

And I should see "metadataSigned" as unchecked 16ms

@rhlike_minion

Scenario:
Create a fake AppStream repository

656ms 7

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

And I follow "Create Repository" 294ms

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

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

And I click on "Create Repository" 54ms

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

And I should see "metadataSigned" as checked 23ms

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

11s 114ms 6

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

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

And I uncheck "metadataSigned" 10s 68ms

And I click on "Update Repository" 566ms

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

And I should see "metadataSigned" as unchecked 16ms

@sle_minion

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

2s 367ms 9

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

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

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

And I click on "Update Channel" 702ms

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

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

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

And I click on "Save Repositories" 730ms

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

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

2s 219ms 9

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

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

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

And I click on "Update Channel" 586ms

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

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

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

And I click on "Save Repositories" 646ms

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

@rhlike_minion

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

2s 491ms 9

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

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

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

And I click on "Update Channel" 647ms

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

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

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

And I click on "Save Repositories" 974ms

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

@rhlike_minion

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

2s 522ms 9

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

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

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

And I click on "Update Channel" 645ms

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

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

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

And I click on "Save Repositories" 990ms

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

Scenario:
Create a fake repository for i586

11s 255ms 7

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

And I follow "Create Repository" 383ms

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

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

And I uncheck "metadataSigned" 10s 85ms

And I click on "Create Repository" 486ms

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

Scenario:
Add the repository to the i586 channel

2s 258ms 9

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

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

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

And I click on "Update Channel" 691ms

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

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

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

And I click on "Save Repositories" 656ms

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

@sle_minion

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

2s 521ms 6

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

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

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

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

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

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

@deblike_minion

Scenario:
Create a fake repository for Debian-like

1s 222ms 7

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

And I follow "Create Repository" 413ms

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

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

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

And I click on "Create Repository" 451ms

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

@deblike_minion

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

2s 138ms 6

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

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

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

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

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

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

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

589ms 1

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

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 702ms 10

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

And I follow "Create Channel" 361ms

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

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

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

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

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

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

And I click on "Create Channel" 63ms

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

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

7s 164ms 1

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

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 652ms 10

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

And I follow "Create Channel" 377ms

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

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

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

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

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

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

And I click on "Create Channel" 681ms

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

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

4s 227ms 1

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

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

1s 489ms 10

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

And I follow "Create Channel" 275ms

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

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

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

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

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

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

And I click on "Create Channel" 581ms

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

@deblike_minion

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

7s 251ms 1

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

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 532ms 10

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

And I follow "Create Channel" 371ms

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

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

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

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

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

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

And I click on "Create Channel" 570ms

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

@rhlike_minion

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

4s 950ms 1

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

Feature:Synchronize fake channels 2m 1s 435ms 12 2

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

Scenario:
Log in as admin user

1s 919ms 2

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

And I enable source package syncing 1s 462ms

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

15s 996ms 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 485ms

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

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

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

And I follow "Sync" 348ms

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

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

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

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

@sle_minion

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

4s 786ms 2

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

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

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

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

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

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

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

And I follow "Sync" 335ms

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

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

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

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

Scenario:
Synchronize Test-Child-Channel-x86_64 channel

16s 129ms 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 430ms

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

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

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

And I follow "Sync" 339ms

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

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

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

@sle_minion

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

15s 793ms 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 442ms

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

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

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

And I follow "Sync" 343ms

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

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

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

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

@deblike_minion

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

4s 543ms 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 434ms

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

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

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

And I follow "Sync" 343ms

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

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

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

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

@rhlike_minion

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

16s 787ms 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 420ms

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

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

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

And I follow "Sync" 1s 124ms

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

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

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

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

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

15s 773ms 9

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

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

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

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

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

And I follow "Sync" 336ms

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

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

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

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

@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

6s 610ms 6

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

And I follow "errata-cache-default" 1s 318ms

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

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

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

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

Scenario:
Refresh the channel's repository data

6s 97ms 6

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

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

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

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

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

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

Scenario:
Cleanup disable source package syncing

990ms 1

Then I disable source package syncing 990ms

@skip_if_github_validation
Feature:Synchronize development channels 1m 15s 594ms 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

15s 964ms 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 427ms

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

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

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

And I follow "Sync" 426ms

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

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

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

15s 953ms 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 445ms

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

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

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

And I follow "Sync" 434ms

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

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

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

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

27s 864ms 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: 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 427ms

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

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

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

And I follow "Sync" 332ms

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

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

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

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

15s 811ms 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 444ms

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

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

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

And I follow "Sync" 261ms

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

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

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

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

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

427ms 1

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

@sle_minion

Scenario:
Create an activation key with a channel

2s 38ms 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 559ms

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

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

1s 496ms 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" 1s 104ms

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

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

1s 255ms 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" 892ms

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

@ssh_minion

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

1s 222ms 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" 845ms

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

@ssh_minion

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

1s 356ms 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" 973ms

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

@proxy

Scenario:
Create an activation key for the proxy

1s 174ms 2

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

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

@build_host

Scenario:
Create an activation key for the build host

1s 598ms 3

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

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

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

@scc_credentials

Scenario:
Create an activation key for the terminal

1s 147ms 2

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

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

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

425ms 1

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 508ms

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

@scc_credentials @susemanager

Scenario:
Update SLE SSH key with synced base product

< 1ms 14

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

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

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

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

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

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

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

And I click on "Update Activation Key" 0s

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

@uyuni

Scenario:
Update openSUSE Tumbleweed SSH key with synced base product

1s 928ms 10

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 490ms

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

@scc_credentials @susemanager

Scenario:
Update SLE SSH tunnel key with synced base product

< 1ms 14

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

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

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

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

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

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

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

And I click on "Update Activation Key" 0s

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

@uyuni

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

2s 992ms 10

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

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

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

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

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

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 1s 17ms

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

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

And I click on "Update Activation Key" 695ms

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

@scc_credentials @susemanager @proxy @containerized_server @transactional_server

Scenario:
Update the SLE Micro proxy key with synced base product

< 1ms 11

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

And I wait until "ManagerTools-SL-Micro-6.1 for x86_64" has been checked 0s

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

And I check "SUSE-Multi-Linux-Manager-Retail-Branch-Server-5.1 for x86_64" 0s

And I click on "Update Activation Key" 0s

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

@scc_credentials @susemanager @proxy @containerized_server @skip_if_transactional_server

Scenario:
Update the SLES proxy key with synced base product

< 1ms 11

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

And I wait until "ManagerTools-SLE15-Pool for x86_64 SP7" has been checked 0s

And I check "SUSE-Manager-Proxy-5.1-Pool for x86_64" 0s

And I check "SUSE-Manager-Proxy-5.1-Updates for x86_64" 0s

And I click on "Update Activation Key" 0s

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

@uyuni @proxy @containerized_server @skip_if_cloud

Scenario:
Update the openSUSE Tumbleweed Proxy Host key with synced base product

< 1ms 8

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 0s

And I click on "Update Activation Key" 0s

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

@scc_credentials @build_host

Scenario:
Update build host key with synced base product

3s 158ms 20

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

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

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

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

And I wait for child channels to appear 516ms

And I include the recommended child channels 170ms

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

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

And I wait until "SLE-Module-Server-Applications15-SP7-Pool for x86_64" has been checked 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 19ms

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

And I click on "Update Activation Key" 515ms

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

@scc_credentials @uyuni @build_host

Scenario:
Update build host key with Uyuni client tools

1s 955ms 9

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

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

And I wait for child channels to appear 864ms

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

And I wait for child channels to appear 299ms

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

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

And I click on "Update Activation Key" 462ms

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

@skip_if_github_validation @scc_credentials @uyuni @build_host

Scenario:
Update build host key with dev child channel

1s 944ms 9

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

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

And I wait for child channels to appear 845ms

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

And I wait for child channels to appear 308ms

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

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

And I click on "Update Activation Key" 464ms

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

@scc_credentials @build_host

Scenario:
Update terminal key with synced base product

2s 819ms 16

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

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

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

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

And I wait for child channels to appear 517ms

And I include the recommended child channels 160ms

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

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

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

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

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

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

And I click on "Update Activation Key" 531ms

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

@susemanager @scc_credentials @build_host

Scenario:
Update terminal key with normal SUSE fake channel

< 1ms 9

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

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

And I wait for child channels to appear 0s

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

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

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

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

And I click on "Update Activation Key" 0s

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

@pxeboot_minion @uyuni @scc_credentials @build_host

Scenario:
Update terminal key with specific fake channel

< 1ms 9

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

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

And I wait for child channels to appear 0s

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

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

And I check "Uyuni Client Tools for SLES15 SP7 x86_64 (Development)" 0s

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

And I click on "Update Activation Key" 0s

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

@skip_if_github_validation @sle_minion

Scenario:
Update SLE key with to include dev child channel

1s 499ms 6

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

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

And I wait for child channels to appear 743ms

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

And I click on "Update Activation Key" 442ms

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

@skip_if_github_validation @deblike_minion

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

1s 498ms 6

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

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

And I wait for child channels to appear 741ms

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

And I click on "Update Activation Key" 450ms

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

@skip_if_github_validation @rhlike_minion

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

1s 549ms 6

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

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

And I wait for child channels to appear 748ms

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

And I click on "Update Activation Key" 494ms

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

Feature:Create bootstrap repositories 8s 582ms 4

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

Scenario:
Create the bootstrap repositories including custom channels

2s 119ms 1

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

@sle_minion

Scenario:
Create the bootstrap repository for SUSE Minion

2s 32ms 1

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

When I create the bootstrap repository for "sle_minion" on the server 2s 32ms

@proxy

Scenario:
Create the bootstrap repository for Proxy

2s 108ms 1

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

@build_host

Scenario:
Create the bootstrap repository for Build Host

2s 322ms 1

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

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

@transactional_server
Feature:SELinux debugging < 1ms 1

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

Scenario:
No previous operation has created wrong SELinux label

< 1ms 1

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

@new_issue
Feature:Debug the server after the testsuite has run 16s 985ms 5

Scenario:
Call spacewalk-debug on server

13s 151ms 1

When I execute spacewalk-debug on the server 13s 151ms

Scenario:
Check the tomcat logs on server

681ms 1

Then the tomcat logs should not contain errors 681ms

Scenario:
Check salt event log for failures on server

1s 771ms 1

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

Scenario:
Check the taskomatic logs on server

676ms 1

Then the taskomatic logs should not contain errors 676ms

Scenario:
Check for out of memory errors

703ms 1

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

Feature:Debug the clients after the testsuite has run 1m 34s 143ms 1

Scenario:
Extract the logs from all our clients

1m 34s 143ms 1

When I extract the log files from all our active nodes 1m 34s 143ms

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

Scenario:
Count UI SCC accesses in rhn_web_ui.log

< 1ms 1

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

Scenario:
Count Taskomatic SCC accesses in rhn_taskomatic_daemon.log

< 1ms 1

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

All Scenarios

148

Passed Scenarios

116

Failed Scenarios

3

Skipped Scenarios

29

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

@sle_minion Scenario:The minion is healthy 6s 222ms 4

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

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

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

@deblike_minion Scenario:The Debian-like minion is healthy 5s 734ms 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 661ms 1

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

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

@server_http_proxy Scenario:Setup HTTP proxy < 1ms 9

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

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

@scc_credentials Feature:List available channels and enable them 1m 41s 158ms 5 1

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

@scc_credentials Scenario:Refresh SCC 29s 868ms 1

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@scc_credentials Scenario:Verify all channels are solved 1m 47s 150ms 2 1

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

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

@sle_minion Scenario:Add a SUSE fake child channel to the SUSE Product base channel 1s 878ms 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 648ms 11

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

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

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

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

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

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

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

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

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

@deblike_minion Scenario:Add the repository to the Debian-like base channel 2s 138ms 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 30s 558ms 9

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

@sle_minion Scenario:Create custom repositories inside the SUSE custom channel 7s 164ms 1

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

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

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

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

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

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

@sle_minion Scenario:Synchronize Fake-RPM-SUSE-Channel channel 15s 996ms 9

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

@skip_if_github_validation Scenario:Synchronize Fake-Child-Channel-i586 channel 16s 7ms 9

@sle_minion Scenario:Synchronize Fake-Child-Channel-SUSE-like channel 15s 793ms 9

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

@rhlike_minion Scenario:Synchronize Fake-Base-Channel-RH-like channel 16s 787ms 9

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

@sle_minion Scenario:Synchronize Devel-SUSE-Channel channel 15s 964ms 9

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

@rhlike_minion Scenario:Synchronize Devel-RH-like-Channel channel 27s 864ms 9

@build_host @uyuni Scenario:Synchronize Devel-Build-Host-Channel channel 15s 811ms 9

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

@proxy

Scenario:
The proxy is healthy

4s 495ms 4

@sle_minion

Scenario:
The minion is healthy

6s 222ms 4

@build_host

Scenario:
The build host is healthy

3s 794ms 4

@ssh_minion

Scenario:
The SSH minion is healthy

6s 373ms 4

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 146ms 4

@deblike_minion

Scenario:
The Debian-like minion is healthy

5s 734ms 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

661ms 1

@no_auth_registry

Scenario:
The registry without authentication is healthy

648ms 1

@custom_download_endpoint

Scenario:
The custom download endpoint is working

642ms 1

@server_http_proxy

Scenario:
Setup HTTP proxy

< 1ms 9

@scc_credentials @no_mirror

Scenario:
Enter valid SCC credentials

< 1ms 6

@no_auth_registry

Scenario:
Create an image store without credentials

2s 966ms 7

@scc_credentials
Feature:List available channels and enable them 1m 41s 158ms 5 1

@proxy @susemanager

Scenario:
List all products for SUSE Multi-Linux Manager

< 1ms 6

@scc_credentials

Scenario:
Refresh SCC

29s 868ms 1

@scc_credentials

Scenario:
Let the products page appear

2s 58ms 6

@scc_credentials

Scenario:
Use the products and architecture filters

2s 572ms 7

@scc_credentials @susemanager

Scenario:
View the channels list in the products page

< 1ms 9

@scc_credentials @susemanager

Scenario:
Synchronize SLES 15 SP7 product with recommended sub-products, including MLM Client Tools

< 1ms 30

@uyuni

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

2m 47s 561ms 5

@containerized_server @proxy @uyuni

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

34s 832ms 2

@scc_credentials @uyuni @build_host

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

43m 41s 65ms 20 1

@proxy @susemanager @transactional_server

Scenario:
Add SL Micro 6.1 as base OS for proxy

< 1ms 13

@proxy @susemanager @skip_if_transactional_server

Scenario:
Add SLES 15 SP7 as base OS for proxy

< 1ms 11

@proxy @susemanager @transactional_server

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

< 1ms 13

@proxy @susemanager @skip_if_transactional_server

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

< 1ms 12

@proxy @susemanager @transactional_server

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

< 1ms 13

@proxy @susemanager @skip_if_transactional_server

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

< 1ms 12

@scc_credentials @susemanager

Scenario:
Installer update channels got enabled when products were added

< 1ms 2

@scc_credentials

Scenario:
Verify all channels are solved

1m 47s 150ms 2 1

@scc_credentials @skip_if_github_validation

Scenario:
Detect product loading issues from the UI

32s 379ms 7 1

@scc_credentials @skip_if_github_validation

Scenario:
Report the synchronization duration for SLES 15 SP7

< 1ms 1

@sle_minion

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

1s 878ms 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 648ms 11

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 477ms 10

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 661ms 10

@rhlike_minion

Scenario:
Create a fake AppStream repository

656ms 7

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

11s 114ms 6

@sle_minion

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

2s 367ms 9

@rhlike_minion

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

2s 491ms 9

@rhlike_minion

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

2s 522ms 9

@sle_minion

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

2s 521ms 6

@deblike_minion

Scenario:
Create a fake repository for Debian-like

1s 222ms 7

@deblike_minion

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

2s 138ms 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 30s 558ms 9

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 702ms 10

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

7s 164ms 1

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 652ms 10

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

4s 227ms 1

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

1s 489ms 10

@deblike_minion

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

7s 251ms 1

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 532ms 10

@rhlike_minion

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

4s 950ms 1

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

15s 996ms 9

@sle_minion

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

4s 786ms 2

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

16s 7ms 9

@sle_minion

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

15s 793ms 9

@deblike_minion

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

4s 543ms 9

@rhlike_minion

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

16s 787ms 9

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

15s 773ms 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 15s 594ms 4

@sle_minion

Scenario:
Synchronize Devel-SUSE-Channel channel

15s 964ms 9

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

15s 953ms 9

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

27s 864ms 9

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

15s 811ms 9

@sle_minion

Scenario:
Create an activation key with a channel

2s 38ms 2

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

1s 496ms 2