All Scenarios

148

Passed Scenarios

117

Failed Scenarios

2

Skipped Scenarios

29

Execution Time: 60m 16s 825ms

Expand All | Collapse All

Metadata

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

Feature:Sanity checks 44s 284ms 10 2

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

Scenario:
The server is healthy
11s 629ms 19

Then "server" should have a FQDN 380ms

And reverse resolution should work for "server" 618ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

And reverse resolution should work for "proxy" 281ms

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

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

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

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

And reverse resolution should work for "sle_minion" 402ms

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

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

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

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

And reverse resolution should work for "build_host" 228ms

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

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

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

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

And reverse resolution should work for "ssh_minion" 448ms

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

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

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

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

And reverse resolution should work for "rhlike_minion" 278ms

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

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

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

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

And reverse resolution should work for "deblike_minion" 219ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Feature:Very first settings 49s 419ms 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
665ms 1

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

Scenario:
Log in as admin user
39s 810ms 1

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

Scenario:
Wait for refresh of list of products to finish
4s 155ms 1

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

Scenario:
Create testing username
1s 509ms 12

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

And I follow "Create User" 762ms

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

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

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

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

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

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

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

And I click on "Create Login" 65ms

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

And I should see a "testing" link 13ms

Scenario:
Grant testing user administrative priviledges
2s 441ms 10

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

And I follow "testing" 575ms

And I check "role_org_admin" 89ms

And I check "role_system_group_admin" 76ms

And I check "role_channel_admin" 77ms

And I check "role_activation_key_admin" 75ms

And I check "role_config_admin" 75ms

And I click on "Update" 1s 251ms

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

And I should see a "testing" text 71ms

@server_http_proxy
Scenario:
Setup HTTP proxy
< 1ms 9

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

Then I should see a "HTTP Proxy Hostname" text 0s

And I should see a "HTTP Proxy Username" text 0s

And I should see a "HTTP Proxy Password" text 0s

When I enter the address of the HTTP proxy as "HTTP Proxy Hostname" 0s

And I enter "suma3" as "HTTP Proxy Username" 0s

And I enter "P4$$w/ord With%and&" as "HTTP Proxy Password" 0s

And I click on "Save and Verify" 0s

Then HTTP proxy verification should have succeeded 0s

Scenario:
Detect latest Salt changes on the server
837ms 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" 837ms

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

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

Feature:Organization credentials in the Setup Wizard < 1ms 1

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

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

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

And I ask to add new credentials 0s

And I enter the SCC credentials 0s

And I click on "Save" 0s

And I wait until the SCC credentials are valid 0s

Feature:Change personal preferences 4s 271ms 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 638ms 5

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

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

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

And I click on "Save Preferences" 859ms

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

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

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

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

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

And I click on "Save Preferences" 51ms

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

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

Scenario:
Create a Kiwi user with image administrators rights
5s 703ms 2

New user kiwikiwi created with roles: image_admin

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

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

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

Scenario:
Create a Docker user with image administrators rights
3s 927ms 2

New user docker created with roles: image_admin

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

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

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

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

And I follow "Create" 423ms

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

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

And I click on "create-btn" 168ms

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

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

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

Scenario:
Log in as admin user
37s 669ms 1

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

Scenario:
Disable scheduled reposyncs
4s 555ms 5

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

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

And I choose "disabled" 54ms

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

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

Scenario:
Disable scheduled Cobbler syncs
4s 556ms 5

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

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

And I choose "disabled" 46ms

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

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

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

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

Scenario:
List available channels
33s 890ms 5

When I refresh SCC 31s 539ms

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

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

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

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

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

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

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

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

When I remove the mgr-sync cache file 648ms

And I execute mgr-sync refresh 1m 762ms

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

Feature:Synchronize products in the products page of the Setup Wizard 48m 24s 691ms 9 9

@scc_credentials
Scenario:
Refresh SCC
27s 870ms 1

When I refresh SCC 27s 870ms

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

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

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

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

Then I should see a "Arch" text 123ms

And I should see a "Channels" text 123ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I close the modal dialog 0s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

Then the SLE15 SP7 product should be added 0s

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

@uyuni
Scenario:
Partially add openSUSE Tumbleweed product, only including the required packages to generate the bootstrap repository
2m 50s 84ms 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 701ms

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

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

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

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

@containerized_server @proxy @uyuni
Scenario:
Add Uyuni Proxy product for Tumbleweed, including Uyuni Client Tools
34s 994ms 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 214ms

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

@scc_credentials @uyuni @build_host
Scenario:
Synchronize SLES 15 SP7 product with recommended sub-products for Retail feature
42m 19s 868ms 20

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 54ms

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

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

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

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

And I wait until all synchronized channels for "sles15-sp7" have finished 41m 57s 736ms

@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 24s 52ms 2

SUCCESS: Channel opensuse_tumbleweed-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel opensuse_tumbleweed-x86_64 synchronization took 92 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 12 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 11 seconds.
SUCCESS: Channel opensuse_tumbleweed-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel opensuse_tumbleweed-x86_64 synchronization took 92 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 11 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 354 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 743 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 39 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 42 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 53 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 85 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 286 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 55 seconds.
SUCCESS: Channel sle-module-devtools15-sp7-updates-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-module-devtools15-sp7-updates-x86_64 synchronization took 503 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 156 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 25 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 32 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 23 seconds.

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

Then all channels have been synced without errors < 1ms

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

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

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

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

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

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

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

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

@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 25s 22ms 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
545ms 1

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

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

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

And I follow "Create Channel" 325ms

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

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

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

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

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

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

And I click on "Create Channel" 591ms

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

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

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

And I follow "Create Channel" 433ms

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

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

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

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

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

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

And I click on "Create Channel" 617ms

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

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

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

And I follow "Create Channel" 310ms

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

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

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

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

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

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

Scenario:
Add a fake base channel for i586
958ms 10

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

And I follow "Create Channel" 327ms

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

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

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

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

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

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

And I click on "Create Channel" 53ms

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

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

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

And I follow "Create Channel" 275ms

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

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

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

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

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

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

And I click on "Create Channel" 563ms

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

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

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

And I follow "Create Channel" 374ms

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

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

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

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

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

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

And I click on "Create Channel" 546ms

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

Scenario:
Add a child channel into the test base channel x86_64
1s 548ms 10

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

And I follow "Create Channel" 352ms

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

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

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

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

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

And I click on "Create Channel" 609ms

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

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

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

And I follow "Create Channel" 260ms

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

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

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

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

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

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

And I uncheck "gpg_check" 10s 108ms

And I click on "Create Channel" 545ms

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

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

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

And I follow "Create Channel" 341ms

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

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

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

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

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

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

And I click on "Create Channel" 553ms

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

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

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

And I follow "Create Channel" 348ms

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

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

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

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

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

And I click on "Create Channel" 517ms

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

Feature:Create fake repositories for each fake child channel 50s 375ms 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
534ms 1

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

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

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

And I follow "Create Repository" 311ms

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

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

And I click on "Create Repository" 450ms

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

And I should see "metadataSigned" as checked 19ms

Scenario:
Disable metadata check for the fake RPM repository
10s 966ms 6

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

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

And I uncheck "metadataSigned" 10s 66ms

And I click on "Update Repository" 489ms

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

And I should see "metadataSigned" as unchecked 15ms

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

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

And I follow "Create Repository" 316ms

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

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

And I click on "Create Repository" 57ms

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

And I should see "metadataSigned" as checked 15ms

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

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

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

And I uncheck "metadataSigned" 10s 66ms

And I click on "Update Repository" 458ms

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

And I should see "metadataSigned" as unchecked 16ms

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

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

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

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

And I click on "Update Channel" 719ms

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

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

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

And I click on "Save Repositories" 515ms

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

Scenario:
Add the fake RPM repository to the Test child channel
2s 97ms 9

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

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

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

And I click on "Update Channel" 54ms

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

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

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

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

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

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

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

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

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

And I click on "Update Channel" 688ms

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

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

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

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

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

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

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

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

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

And I click on "Update Channel" 566ms

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

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

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

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

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

Scenario:
Create a fake repository for i586
11s 127ms 7

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

And I follow "Create Repository" 309ms

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

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

And I uncheck "metadataSigned" 10s 84ms

And I click on "Create Repository" 438ms

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

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

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

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

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

And I click on "Update Channel" 55ms

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

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

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

And I click on "Save Repositories" 522ms

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

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

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

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

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

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

And I click on "Save Repositories" 822ms

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

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

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

And I follow "Create Repository" 315ms

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

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

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

And I click on "Create Repository" 56ms

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

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

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

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

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

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

And I click on "Save Repositories" 579ms

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

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

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

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

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

And I click on "Update Channel" 0s

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

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

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

And I click on "Save Repositories" 0s

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

@skip_if_github_validation
Feature:Create custom channels with development repositories 41s 463ms 8 1

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

Scenario:
Log in as admin user
468ms 1

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

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

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

And I follow "Create Channel" 392ms

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

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

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

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

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

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

And I click on "Create Channel" 61ms

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

@sle_minion
Scenario:
Create custom repositories inside the SUSE custom channel
16s 736ms 1 1

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

15s 166ms Show Info + 
15:36:16:000 - 15:36:18:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/manage/Edit.do?cid=131
Screenshot +

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

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

And I follow "Create Channel" 365ms

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

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

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

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

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

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

And I click on "Create Channel" 593ms

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

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

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

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

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

And I follow "Create Channel" 364ms

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

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

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

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

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

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

And I click on "Create Channel" 667ms

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

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

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

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

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

And I follow "Create Channel" 397ms

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

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

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

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

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

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

And I click on "Create Channel" 531ms

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
5s 248ms 1

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

Feature:Synchronize fake channels 1m 59s 923ms 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 837ms 2

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

And I enable source package syncing 1s 417ms

@sle_minion
Scenario:
Synchronize Fake-RPM-SUSE-Channel channel
16s 231ms 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 421ms

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

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

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

And I follow "Sync" 821ms

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

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

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

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

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

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

@skip_if_github_validation
Scenario:
Synchronize Fake-Child-Channel-i586 channel
15s 859ms 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 439ms

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

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

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

And I follow "Sync" 333ms

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

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

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

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

Scenario:
Synchronize Test-Child-Channel-x86_64 channel
15s 849ms 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 429ms

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

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

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

And I follow "Sync" 422ms

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

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

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

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

@sle_minion
Scenario:
Synchronize Fake-Child-Channel-SUSE-like channel
15s 882ms 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 432ms

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

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

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

And I follow "Sync" 428ms

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

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

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

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

@deblike_minion
Scenario:
Synchronize Fake-Base-Channel-Debian-like channel
4s 442ms 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 422ms

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

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

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

And I follow "Sync" 351ms

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

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

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

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

@rhlike_minion
Scenario:
Synchronize Fake-Base-Channel-RH-like channel
16s 692ms 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 426ms

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

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

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

And I follow "Sync" 1s 290ms

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

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

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

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

@rhlike_minion
Scenario:
Synchronize Fake-Base-Channel-AppStream channel
15s 819ms 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 437ms

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

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

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

And I follow "Sync" 331ms

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

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

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

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

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

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

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

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

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

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

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

Scenario:
Refresh the channel's repository data
5s 133ms 6

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

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

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

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

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

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

Scenario:
Cleanup disable source package syncing
1s 11ms 1

Then I disable source package syncing 1s 11ms

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

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

@sle_minion
Scenario:
Synchronize Devel-SUSE-Channel channel
27s 841ms 8 1 1

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

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

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

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

And I follow "Sync" 427ms

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

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

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

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

14s 948ms Show Info + 
15:39:04:000 - 15:39:18:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/manage/Sync.do?cid=131
Screenshot +

@deblike_minion
Scenario:
Synchronize Devel-Debian-like-Channel channel
16s 95ms 9

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

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

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

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

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

And I follow "Sync" 607ms

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

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

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

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

@rhlike_minion
Scenario:
Synchronize Devel-RH-like-Channel channel
51s 65ms 9

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

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

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

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

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

And I follow "Sync" 431ms

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

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

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

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

@build_host @uyuni
Scenario:
Synchronize Devel-Build-Host-Channel channel
15s 742ms 9

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

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

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

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

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

And I follow "Sync" 338ms

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

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

Feature:Create activation keys 13s 891ms 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
425ms 1

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

@sle_minion
Scenario:
Create an activation key with a channel
2s 431ms 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 978ms

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

@rhlike_minion
Scenario:
Create an activation key for RedHat-like minion
1s 544ms 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 52ms

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

@deblike_minion
Scenario:
Create an activation key for Debian-like minion
1s 426ms 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" 1s 3ms

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

@ssh_minion
Scenario:
Create an activation key with a channel for salt-ssh
1s 528ms 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" 1s 59ms

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

@ssh_minion
Scenario:
Create an activation key with a channel for salt-ssh via tunnel
1s 628ms 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" 1s 179ms

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

@proxy
Scenario:
Create an activation key for the proxy
1s 593ms 2

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

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

@build_host
Scenario:
Create an activation key for the build host
1s 944ms 3

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

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

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

@scc_credentials
Scenario:
Create an activation key for the terminal
1s 368ms 2

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

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

Feature:Update activation keys 22s 461ms 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
454ms 1

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 513ms

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

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

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

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

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

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

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

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

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

And I click on "Update Activation Key" 0s

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

@uyuni
Scenario:
Update openSUSE Tumbleweed SSH key with synced base product
2s 498ms 10

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 587ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

And I wait for child channels to appear 613ms

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

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 527ms

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

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

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

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

And I wait for child channels to appear 787ms

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

And I wait for child channels to appear 316ms

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

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

And I click on "Update Activation Key" 467ms

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

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

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

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

And I wait for child channels to appear 868ms

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

And I wait for child channels to appear 316ms

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

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

And I click on "Update Activation Key" 461ms

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

@scc_credentials @build_host
Scenario:
Update terminal key with synced base product
2s 832ms 16

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

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

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

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

And I wait for child channels to appear 530ms

And I include the recommended child channels 159ms

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 469ms

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

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

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

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

And I wait for child channels to appear 751ms

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

And I click on "Update Activation Key" 432ms

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

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

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

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

And I wait for child channels to appear 668ms

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

And I click on "Update Activation Key" 455ms

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

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

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

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

And I wait for child channels to appear 751ms

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

And I click on "Update Activation Key" 456ms

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

Feature:Create bootstrap repositories 8s 607ms 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 116ms 1

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

@sle_minion
Scenario:
Create the bootstrap repository for SUSE Minion
2s 104ms 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 104ms

@proxy
Scenario:
Create the bootstrap repository for Proxy
2s 40ms 1

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

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

@build_host
Scenario:
Create the bootstrap repository for Build Host
2s 346ms 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 346ms

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

Scenario:
Call spacewalk-debug on server
13s 122ms 1

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

Scenario:
Check the tomcat logs on server
670ms 1

Then the tomcat logs should not contain errors 670ms

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

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

Scenario:
Check the taskomatic logs on server
661ms 1

Then the taskomatic logs should not contain errors 661ms

Scenario:
Check for out of memory errors
647ms 1

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

Feature:Debug the clients after the testsuite has run 42s 364ms 1

Scenario:
Extract the logs from all our clients
42s 364ms 1

When I extract the log files from all our active nodes 42s 364ms

@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