Cucumber Feature Report

All Scenarios

201

Passed Scenarios

156

Failed Scenarios

7

Skipped Scenarios

38

Execution Time: 97m 15s 574ms

Expand All | Collapse All

Metadata

App Version: Uyuni/Head

Browser: Chrome

Platform: x86_64

Parallel: Disabled

Feature:Sanity checks 43s 972ms 10 2

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

Scenario:
The server is healthy

11s 763ms 19

Then "server" should have a FQDN 380ms

And reverse resolution should work for "server" 616ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@proxy

Scenario:
The proxy is healthy

4s 449ms 4

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

And reverse resolution should work for "proxy" 282ms

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

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

@sle_minion

Scenario:
The minion is healthy

6s 400ms 4

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

And reverse resolution should work for "sle_minion" 420ms

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

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

@build_host

Scenario:
The build host is healthy

3s 759ms 4

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

And reverse resolution should work for "build_host" 223ms

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

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

@ssh_minion

Scenario:
The SSH minion is healthy

6s 345ms 4

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

And reverse resolution should work for "ssh_minion" 421ms

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

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

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 195ms 4

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

And reverse resolution should work for "rhlike_minion" 188ms

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

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

@deblike_minion

Scenario:
The Debian-like minion is healthy

6s 112ms 4

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

And reverse resolution should work for "deblike_minion" 213ms

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

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

@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

656ms 1

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

@custom_download_endpoint

Scenario:
The custom download endpoint is working

642ms 1

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

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

670ms 1

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

Scenario:
Log in as admin user

39s 771ms 1

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

Scenario:
Wait for refresh of list of products to finish

3s 924ms 1

When I wait until mgr-sync refresh is finished 3s 924ms

Scenario:
Create testing username

1s 393ms 12

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

And I follow "Create User" 640ms

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

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

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

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

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

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

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

And I click on "Create Login" 63ms

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

And I should see a "testing" link 12ms

Scenario:
Grant testing user administrative priviledges

2s 453ms 10

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

And I follow "testing" 873ms

And I check "role_org_admin" 81ms

And I check "role_system_group_admin" 74ms

And I check "role_channel_admin" 76ms

And I check "role_activation_key_admin" 75ms

And I check "role_config_admin" 76ms

And I click on "Update" 968ms

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

And I should see a "testing" text 74ms

@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

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

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

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

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

@scc_credentials @no_mirror

Scenario:
Enter valid SCC credentials

< 1ms 6

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

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

And I ask to add new credentials 0s

And I enter the SCC credentials 0s

And I click on "Save" 0s

And I wait until the SCC credentials are valid 0s

Feature:Change personal preferences 5s 449ms 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 461ms 5

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

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

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

And I click on "Save Preferences" 630ms

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

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

3s 987ms 5

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

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

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

And I click on "Save Preferences" 795ms

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

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

Scenario:
Create a Kiwi user with image administrators rights

6s 261ms 2

New user kiwikiwi created with roles: image_admin

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

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

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

Scenario:
Create a Docker user with image administrators rights

4s 67ms 2

New user docker created with roles: image_admin

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

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

@no_auth_registry

Scenario:
Create an image store without credentials

2s 773ms 7

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

And I follow "Create" 537ms

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

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

And I click on "create-btn" 85ms

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

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

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

Scenario:
Log in as admin user

37s 752ms 1

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

Scenario:
Disable scheduled reposyncs

4s 636ms 5

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

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

And I choose "disabled" 55ms

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

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

Scenario:
Disable scheduled Cobbler syncs

4s 607ms 5

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

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

And I choose "disabled" 46ms

And I click on "Update Schedule" 53ms

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

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

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

Scenario:
List available channels

35s 432ms 5

When I refresh SCC 33s 66ms

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

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

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

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

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

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

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

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

When I remove the mgr-sync cache file 636ms

And I execute mgr-sync refresh 1m 768ms

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

Feature:Synchronize products in the products page of the Setup Wizard 51m 38s 216ms 9 9

@scc_credentials

Scenario:
Refresh SCC

29s 128ms 1

When I refresh SCC 29s 128ms

@scc_credentials

Scenario:
Let the products page appear

2s 163ms 6

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

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

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

Then I should see a "Arch" text 117ms

And I should see a "Channels" text 117ms

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

@scc_credentials

Scenario:
Use the products and architecture filters

2s 423ms 7

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

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

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

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

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

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

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

@scc_credentials @susemanager

Scenario:
View the channels list in the products page

< 1ms 9

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

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

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

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

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

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

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

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

When I close the modal dialog 0s

@scc_credentials @susemanager

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

< 1ms 30

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

Then the SLE15 SP7 product should be added 0s

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

@uyuni

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

4m 4s 77ms 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 598ms

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

And I use spacewalk-repo-sync to sync channel "opensuse_tumbleweed-x86_64" including only client tools dependencies 2m 48s 518ms

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

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

@containerized_server @proxy @uyuni

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

35s 406ms 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 926ms

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

@scc_credentials @uyuni @build_host

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

43m 5s 464ms 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: Found channel 'sle-module-basesystem15-sp7-pool-x86_64' at line 65. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-basesystem15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-pool-x86_64' at line 65. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-basesystem15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-pool-x86_64' at line 65. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-basesystem15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-pool-x86_64' at line 65. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-basesystem15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-pool-x86_64' at line 65. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-basesystem15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
1m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-basesystem15-sp7-pool-x86_64' at line 65. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-basesystem15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-pool-x86_64' at line 65. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-basesystem15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-pool-x86_64' at line 65. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-basesystem15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-pool-x86_64' at line 65. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-basesystem15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-pool-x86_64' at line 65. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-basesystem15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-pool-x86_64' at line 65. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-basesystem15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
2m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-basesystem15-sp7-pool-x86_64' at line 65. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-basesystem15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-pool-x86_64' at line 65. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-basesystem15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-pool-x86_64' at line 65. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-basesystem15-sp7-pool-x86_64 at line 69.
SUCCESS: sle-module-basesystem15-sp7-pool-x86_64 is fully synchronized.
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
3m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
4m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
5m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
6m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
7m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Sync for sle-module-basesystem15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-basesystem15-sp7-updates-x86_64' at line 73. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-basesystem15-sp7-updates-x86_64 at line 77.
SUCCESS: sle-module-basesystem15-sp7-updates-x86_64 is fully synchronized.
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-server-applications15-sp7-pool-x86_64' at line 81. Checking for completion...
DEBUG: Sync for sle-module-server-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-server-applications15-sp7-pool-x86_64' at line 81. Checking for completion...
DEBUG: Sync for sle-module-server-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-server-applications15-sp7-pool-x86_64' at line 81. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-server-applications15-sp7-pool-x86_64 at line 85.
SUCCESS: sle-module-server-applications15-sp7-pool-x86_64 is fully synchronized.
DEBUG: Found channel 'sle-module-server-applications15-sp7-updates-x86_64' at line 89. Checking for completion...
DEBUG: Sync for sle-module-server-applications15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-server-applications15-sp7-updates-x86_64' at line 89. Checking for completion...
DEBUG: Sync for sle-module-server-applications15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-server-applications15-sp7-updates-x86_64' at line 89. Checking for completion...
DEBUG: Sync for sle-module-server-applications15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
8m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-server-applications15-sp7-updates-x86_64' at line 89. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-server-applications15-sp7-updates-x86_64 at line 93.
SUCCESS: sle-module-server-applications15-sp7-updates-x86_64 is fully synchronized.
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-python3-15-sp7-updates-x86_64' at line 97. Checking for completion...
DEBUG: Sync for sle-module-python3-15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-python3-15-sp7-updates-x86_64' at line 97. Checking for completion...
DEBUG: Sync for sle-module-python3-15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-python3-15-sp7-pool-x86_64' at line 105. Checking for completion...
DEBUG: Sync for sle-module-python3-15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-python3-15-sp7-updates-x86_64' at line 97. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-python3-15-sp7-updates-x86_64 at line 101.
SUCCESS: sle-module-python3-15-sp7-updates-x86_64 is fully synchronized.
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-python3-15-sp7-pool-x86_64' at line 105. Checking for completion...
DEBUG: Sync for sle-module-python3-15-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: Found channel 'sle-module-python3-15-sp7-pool-x86_64' at line 105. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-python3-15-sp7-pool-x86_64 at line 109.
SUCCESS: sle-module-python3-15-sp7-pool-x86_64 is fully synchronized.
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: 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
9m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-systems-management-15-sp7-pool-x86_64' at line 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: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 129. 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-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: 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: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 129. Checking for completion...
DEBUG: Sync for sle-module-devtools15-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: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 129. Checking for completion...
DEBUG: Sync for sle-module-devtools15-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: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 129. Checking for completion...
DEBUG: Sync for sle-module-devtools15-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
10m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 129. Checking for completion...
DEBUG: Sync for sle-module-devtools15-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: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 129. Checking for completion...
DEBUG: Sync for sle-module-devtools15-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: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 129. Checking for completion...
DEBUG: Sync for sle-module-devtools15-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: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 129. Checking for completion...
DEBUG: Sync for sle-module-devtools15-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: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 129. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-devtools15-sp7-pool-x86_64 at line 133.
SUCCESS: sle-module-devtools15-sp7-pool-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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
11m / 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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel '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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel '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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel '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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel '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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel '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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
12m / 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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel '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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel '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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel '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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel '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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel '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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
13m / 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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel '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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel '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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel '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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel '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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel '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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
14m / 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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel '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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel '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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel '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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel '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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel '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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
15m / 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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel '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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel '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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel '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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel '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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel '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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sles15-sp7-devel-uyuni-client-x86_64' not found in reposync.log
16m / 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: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 137. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-devtools15-sp7-updates-x86_64 at line 141.
SUCCESS: sle-module-devtools15-sp7-updates-x86_64 is fully synchronized.
DEBUG: Found channel 'sles15-sp7-devel-uyuni-client-x86_64' at line 145. Checking for completion...
DEBUG: Sync for sles15-sp7-devel-uyuni-client-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sles15-sp7-devel-uyuni-client-x86_64' at line 145. Checking for completion...
DEBUG: Sync for sles15-sp7-devel-uyuni-client-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-updates-x86_64' at line 153. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sles15-sp7-devel-uyuni-client-x86_64' at line 145. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sles15-sp7-devel-uyuni-client-x86_64 at line 149.
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: Found channel 'sle-module-desktop-applications15-sp7-updates-x86_64' at line 153. 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-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-updates-x86_64' at line 153. 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-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-updates-x86_64' at line 153. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-updates-x86_64 still in progress (no completion message found).
17m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 161. 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 153. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-desktop-applications15-sp7-updates-x86_64 at line 157.
SUCCESS: sle-module-desktop-applications15-sp7-updates-x86_64 is fully synchronized.
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 161. 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-pool-x86_64' at line 161. 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-pool-x86_64' at line 161. 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-pool-x86_64' at line 161. 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-pool-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
18m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 161. 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-pool-x86_64' at line 161. 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-pool-x86_64' at line 161. 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-pool-x86_64' at line 161. 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-pool-x86_64' at line 161. 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-pool-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
19m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 161. 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-pool-x86_64' at line 161. 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-pool-x86_64' at line 161. 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-pool-x86_64' at line 161. 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-pool-x86_64' at line 161. 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-pool-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
20m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 161. 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-pool-x86_64' at line 161. 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-pool-x86_64' at line 161. 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-pool-x86_64' at line 161. 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-pool-x86_64' at line 161. 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-pool-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
21m / 43m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 161. 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-pool-x86_64' at line 161. 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-pool-x86_64' at line 161. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-desktop-applications15-sp7-pool-x86_64 at line 165.
SUCCESS: sle-module-desktop-applications15-sp7-pool-x86_64 is fully synchronized.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 56ms

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

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

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

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 42m 42s 335ms

@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

2m 35s 861ms 2

SUCCESS: Channel opensuse_tumbleweed-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel opensuse_tumbleweed-x86_64 synchronization took 166 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 10 seconds.
SUCCESS: Channel opensuse_tumbleweed-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel opensuse_tumbleweed-x86_64 synchronization took 166 seconds.
SUCCESS: Channel opensuse_tumbleweed-uyuni-client-devel-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel opensuse_tumbleweed-uyuni-client-devel-x86_64 synchronization took 10 seconds.
SUCCESS: Channel uyuni-proxy-devel-tumbleweed-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel uyuni-proxy-devel-tumbleweed-x86_64 synchronization took 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 339 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 829 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 41 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 43 seconds.
SUCCESS: Channel sle-module-server-applications15-sp7-pool-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-module-server-applications15-sp7-pool-x86_64 synchronization took 54 seconds.
SUCCESS: Channel sle-module-server-applications15-sp7-updates-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-module-server-applications15-sp7-updates-x86_64 synchronization took 82 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 58 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 514 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 149 seconds.
SUCCESS: Channel sle-module-systems-management-15-sp7-pool-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-module-systems-management-15-sp7-pool-x86_64 synchronization took 26 seconds.
SUCCESS: Channel sle-module-systems-management-15-sp7-updates-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-module-systems-management-15-sp7-updates-x86_64 synchronization took 30 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.
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 308 seconds.

When I wait until all synchronized channels have solved their dependencies 2m 35s 861ms

Then all channels have been synced without errors < 1ms

@scc_credentials @skip_if_github_validation

Scenario:
Detect product loading issues from the UI

43s 690ms 7

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

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

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

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

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

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

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

@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 935ms 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

522ms 1

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

Scenario:
Add a fake base channel for x86_64

1s 756ms 10

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

And I follow "Create Channel" 378ms

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

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

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

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

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

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

And I click on "Create Channel" 655ms

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

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

1s 521ms 10

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

And I follow "Create Channel" 329ms

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

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

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

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

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

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

And I click on "Create Channel" 612ms

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

@sle_minion

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

1s 533ms 10

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

And I follow "Create Channel" 275ms

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

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

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

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

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

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

And I click on "Create Channel" 55ms

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

Scenario:
Add a fake base channel for i586

1s 466ms 10

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

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

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

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

And I click on "Create Channel" 572ms

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

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

1s 515ms 10

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

And I follow "Create Channel" 328ms

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

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

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

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

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

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

And I click on "Create Channel" 609ms

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

Scenario:
Add a test base channel for x86_64

1s 605ms 10

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

And I follow "Create Channel" 397ms

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

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

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

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

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

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

And I click on "Create Channel" 649ms

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

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

1s 457ms 10

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

And I follow "Create Channel" 322ms

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

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

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

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

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

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

And I click on "Create Channel" 539ms

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

@pxeboot_minion @uyuni @scc_credentials

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

< 1ms 10

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

And I follow "Create Channel" 0s

And I enter "Fake-RPM-Terminal-Channel" as "Channel Name" 0s

And I enter "fake-rpm-terminal-channel" as "Channel Label" 0s

And I select the parent channel for the "pxeboot_minion" from "Parent Channel" 0s

And I select "x86_64" from "Architecture:" 0s

And I enter "Fake-RPM-Terminal-Channel for testing" as "Channel Summary" 0s

And I enter "Description for Fake-RPM-Terminal-Channel Child Channel." as "Channel Description" 0s

And I click on "Create Channel" 0s

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

@deblike_minion

Scenario:
Add Debian-like AMD64 base channel

11s 590ms 11

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

And I follow "Create Channel" 334ms

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

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

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

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

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

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

And I uncheck "gpg_check" 10s 88ms

And I click on "Create Channel" 580ms

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

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 472ms 10

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

And I follow "Create Channel" 331ms

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

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

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

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

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

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

And I click on "Create Channel" 576ms

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

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 492ms 10

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

And I follow "Create Channel" 328ms

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

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

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

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

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

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

And I click on "Create Channel" 595ms

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

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

517ms 1

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

Scenario:
Create a fake repository for distributions using RPM

1s 320ms 7

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

And I follow "Create Repository" 390ms

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

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

And I click on "Create Repository" 59ms

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

And I should see "metadataSigned" as checked 18ms

Scenario:
Disable metadata check for the fake RPM repository

11s 5ms 6

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

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

And I uncheck "metadataSigned" 10s 73ms

And I click on "Update Repository" 473ms

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

And I should see "metadataSigned" as unchecked 15ms

@rhlike_minion

Scenario:
Create a fake AppStream repository

636ms 7

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

And I follow "Create Repository" 285ms

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

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

And I click on "Create Repository" 54ms

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

And I should see "metadataSigned" as checked 15ms

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

10s 997ms 6

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

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

And I uncheck "metadataSigned" 10s 76ms

And I click on "Update Repository" 461ms

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

And I should see "metadataSigned" as unchecked 15ms

@sle_minion

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

2s 229ms 9

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

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

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

And I click on "Update Channel" 673ms

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

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

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

And I click on "Save Repositories" 637ms

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

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

2s 55ms 9

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

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

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

And I click on "Update Channel" 58ms

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

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

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

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

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

@rhlike_minion

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

2s 599ms 9

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

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

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

And I click on "Update Channel" 54ms

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

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

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

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

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

@rhlike_minion

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

2s 662ms 9

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

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

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

And I click on "Update Channel" 673ms

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

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

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

And I click on "Save Repositories" 945ms

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

Scenario:
Create a fake repository for i586

11s 142ms 7

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

And I follow "Create Repository" 302ms

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

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

And I uncheck "metadataSigned" 10s 65ms

And I click on "Create Repository" 484ms

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

Scenario:
Add the repository to the i586 channel

1s 971ms 9

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

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

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

And I click on "Update Channel" 585ms

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

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

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

And I click on "Save Repositories" 587ms

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

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

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

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

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

And I click on "Save Repositories" 880ms

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

@deblike_minion

Scenario:
Create a fake repository for Debian-like

1s 200ms 7

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

And I follow "Create Repository" 298ms

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

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

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

And I click on "Create Repository" 548ms

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

@deblike_minion

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

1s 915ms 6

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

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

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

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

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

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

@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 31s 502ms 9

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

Scenario:
Log in as admin user

497ms 1

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

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 127ms 10

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

And I follow "Create Channel" 377ms

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

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

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

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

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

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

And I click on "Create Channel" 62ms

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

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

7s 278ms 1

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

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 519ms 10

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

And I follow "Create Channel" 350ms

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

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

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

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

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

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

And I click on "Create Channel" 583ms

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

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

4s 218ms 1

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

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

1s 556ms 10

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

And I follow "Create Channel" 352ms

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

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

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

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

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

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

And I click on "Create Channel" 605ms

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

8s 358ms 1

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

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 632ms 10

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

And I follow "Create Channel" 377ms

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

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

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

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

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

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

And I click on "Create Channel" 648ms

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

@rhlike_minion

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

5s 314ms 1

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

Feature:Synchronize fake channels 2m 1s 308ms 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 939ms 2

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

And I enable source package syncing 1s 432ms

@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 502ms

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

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

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

And I follow "Sync" 438ms

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

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

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

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

@sle_minion

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

4s 393ms 2

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

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

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

16s 701ms 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 491ms

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

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

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

And I follow "Sync" 340ms

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

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

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

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

Scenario:
Synchronize Test-Child-Channel-x86_64 channel

15s 999ms 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 468ms

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

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

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

And I follow "Sync" 426ms

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

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

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

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

@sle_minion

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

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

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

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

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

And I follow "Sync" 339ms

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

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

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

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

@deblike_minion

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

4s 738ms 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 466ms

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

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

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

And I follow "Sync" 336ms

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

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

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

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

@rhlike_minion

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

16s 659ms 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 442ms

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

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

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

And I follow "Sync" 1s 94ms

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

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

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

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

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

15s 972ms 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 451ms

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

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

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

And I follow "Sync" 328ms

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

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

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

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

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

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

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

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

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

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

Scenario:
Refresh the channel's repository data

5s 134ms 6

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

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

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

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

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

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

Scenario:
Cleanup disable source package syncing

1s 35ms 1

Then I disable source package syncing 1s 35ms

@skip_if_github_validation
Feature:Synchronize development channels 1m 27s 390ms 4

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

@sle_minion

Scenario:
Synchronize Devel-SUSE-Channel channel

16s 90ms 9

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

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

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

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

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

And I follow "Sync" 425ms

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

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

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

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

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

15s 903ms 9

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

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

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

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

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

And I follow "Sync" 330ms

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

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

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

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

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

39s 231ms 9

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

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

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

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

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

And I follow "Sync" 328ms

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

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

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

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

16s 164ms 9

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

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

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

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

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

And I follow "Sync" 341ms

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

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

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

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

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

507ms 1

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

@sle_minion

Scenario:
Create an activation key with a channel

2s 288ms 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 778ms

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

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

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

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

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

1s 326ms 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" 957ms

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

@ssh_minion

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

1s 230ms 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" 869ms

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

@ssh_minion

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

1s 263ms 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" 897ms

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

@proxy

Scenario:
Create an activation key for the proxy

1s 193ms 2

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

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

@build_host

Scenario:
Create an activation key for the build host

1s 601ms 3

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

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

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

@scc_credentials

Scenario:
Create an activation key for the terminal

1s 338ms 2

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

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

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

464ms 1

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 535ms

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

@scc_credentials @susemanager

Scenario:
Update SLE SSH key with synced base product

< 1ms 14

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

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

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

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

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

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

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

And I click on "Update Activation Key" 0s

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

@uyuni

Scenario:
Update openSUSE Tumbleweed SSH key with synced base product

1s 900ms 10

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 482ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

And I wait for child channels to appear 608ms

And I include the recommended child channels 172ms

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

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

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

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

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

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

@scc_credentials @uyuni @build_host

Scenario:
Update build host key with Uyuni client tools

2s 139ms 9

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

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

And I wait for child channels to appear 937ms

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

And I wait for child channels to appear 301ms

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

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

And I click on "Update Activation Key" 586ms

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

@skip_if_github_validation @scc_credentials @uyuni @build_host

Scenario:
Update build host key with dev child channel

1s 986ms 9

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

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

And I wait for child channels to appear 852ms

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

And I wait for child channels to appear 310ms

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

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

And I click on "Update Activation Key" 503ms

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

@scc_credentials @build_host

Scenario:
Update terminal key with synced base product

2s 982ms 16

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

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

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

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

And I wait for child channels to appear 525ms

And I include the recommended child channels 162ms

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

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

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

And I click on "Update Activation Key" 635ms

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

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

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

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

And I wait for child channels to appear 736ms

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

And I click on "Update Activation Key" 481ms

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

@skip_if_github_validation @deblike_minion

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

1s 512ms 6

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

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

And I wait for child channels to appear 736ms

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

And I click on "Update Activation Key" 471ms

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

@skip_if_github_validation @rhlike_minion

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

1s 490ms 6

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

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

And I wait for child channels to appear 731ms

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

And I click on "Update Activation Key" 460ms

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

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

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

@sle_minion

Scenario:
Create the bootstrap repository for SUSE Minion

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

@proxy

Scenario:
Create the bootstrap repository for Proxy

2s 210ms 1

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

@build_host

Scenario:
Create the bootstrap repository for Build Host

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

@containerized_server @scope_containerized_proxy @proxy
Feature:Setup containerized proxy 3m 28s 178ms 10 2

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

Scenario:
Clean up sumaform leftovers on proxy

6s 562ms 1

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

@transactional_server

Scenario:
Reboot after clean up

< 1ms 1

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

Scenario:
Log in as admin user

37s 729ms 1

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

Scenario:
Bootstrap the proxy host as a salt minion

35s 744ms 9

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 63ms

And I wait until I see "Bootstrap process initiated." text 35s 109ms

@skip_if_cloud @transactional_server

Scenario:
Reboot the proxy host

< 1ms 1

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

Scenario:
Wait until the proxy host appears

1m 23s 131ms 1

When I wait until onboarding is completed for "proxy" 1m 23s 131ms

Scenario:
Generate containerized proxy configuration

13s 25ms 2

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

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

Scenario:
Set up the containerized proxy service to support Avahi

< 1ms 1

Record not added - avahi domain was not detected

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

Scenario:
Run a containerized proxy

16s 168ms 1

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

Scenario:
Wait until containerized proxy service is active

3s 888ms 10

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

And I wait until "uyuni-proxy-httpd" service is active on "proxy" 465ms

And I wait until "uyuni-proxy-salt-broker" service is active on "proxy" 484ms

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

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

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

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

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

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

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

Scenario:
The containerized proxy should be registered automatically

725ms 2

When I follow the left menu "Systems" 60ms

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

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

11s 201ms 3

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

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

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

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

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

Scenario:
Adapt the proxy for Retail

< 1ms 3

When I rename the proxy for Retail 0s

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

And I restart all proxy containers 0s

Scenario:
Check the branch network

< 1ms 2

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

And name resolution should work on private network 0s

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

< 1ms 11

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

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

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

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

And I click on "Schedule Hardware Refresh" 0s

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

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

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

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

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

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

@deblike_minion
Feature:Bootstrap a Debian-like minion and do some basic operations on it 4m 19s 327ms 7

Scenario:
Log in as admin user

38s 217ms 1

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

Scenario:
Bootstrap a Debian-like minion

2m 19s 412ms 14

The hostname of deblike_minion is uyuni-master-deblike-minion
* Mon Feb 16 2026 Victor Zhestkov
- Fix the typo causing buiding EL9 bundle without binary dependencies
* Mon Feb 2 2026 Michael Calmer
- Rebuild because of maintenance release
* 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
* Drop dependency on saltbundlepy-apt
- Speed up wheel key.finger call (bsc#1240532)
- Backport security patches for Salt vendored tornado:

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

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

When I enter the hostname of "deblike_minion" as "hostname" 4s 761ms

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

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

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

And I select "1-DEBLIKE-KEY" from "activationKeys" 87ms

And I select the hostname of "proxy" from "proxies" if present 3s 312ms

And I click on "Bootstrap" 109ms

And I wait until I see "Bootstrap process initiated." text 40s 952ms

And I follow the left menu "Systems > System List > All" 288ms

And I wait until I see the name of "deblike_minion", refreshing the page 32s 52ms

And I wait until onboarding is completed for "deblike_minion" 56s 153ms

And I query latest Salt changes on Debian-like system "deblike_minion" 1s 169ms

@proxy

Scenario:
Check connection from the Debian-like minion to proxy

1s 713ms 4

Given I am on the Systems overview page of this "deblike_minion" 1s 379ms

When I follow "Details" in the content area 110ms

And I follow "Connection" in the content area 95ms

Then I should see "proxy" short hostname 128ms

@proxy

Scenario:
Check registration on proxy of the Debian-like minion

2s 916ms 4

Given I am on the Systems overview page of this "proxy" 2s 420ms

When I follow "Details" in the content area 115ms

And I follow "Proxy" in the content area 170ms

Then I should see "deblike_minion" hostname 208ms

Scenario:
Subscribe the Debian-like minion to a base channel

24s 430ms 11

Warning: Radio button 'Fake-Base-Channel-Debian-like' is already checked

Given I am on the Systems overview page of this "deblike_minion" 1s 568ms

When I follow "Software" in the content area 145ms

And I follow "Software Channels" in the content area 137ms

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

And I check radio button "Fake-Base-Channel-Debian-like" 89ms

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

And I click on "Next" 99ms

Then I should see a "Confirm Software Channel Change" text 140ms

When I click on "Confirm" 113ms

Then I should see a "Changing the channels has been scheduled." text 768ms

And I wait until event "Subscribe channels scheduled by admin" is completed 20s 627ms

Scenario:
Detect latest Salt changes on the Debian-like minion

460ms 1

* Mon Feb 16 2026 Victor Zhestkov
- Fix the typo causing buiding EL9 bundle without binary dependencies
* Mon Feb 2 2026 Michael Calmer
- Rebuild because of maintenance release
* 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
* Drop dependency on saltbundlepy-apt
- Speed up wheel key.finger call (bsc#1240532)
- Backport security patches for Salt vendored tornado:

When I query latest Salt changes on Debian-like system "deblike_minion" 460ms

Scenario:
Check events history for failures on Debian-like minion

52s 176ms 2

Given I am on the Systems overview page of this "deblike_minion" 1s 71ms

Then I check for failed events on history event page 51s 104ms

@rhlike_minion
Feature:Bootstrap a Red Hat-like minion and do some basic operations on it 4m 9s 495ms 7

Scenario:
Log in as admin user

39s 440ms 1

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

Scenario:
Bootstrap a Red Hat-like minion

2m 9s 592ms 13

The hostname of rhlike_minion is uyuni-master-rhlike-minion.sumaci.aws

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

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

When I enter the hostname of "rhlike_minion" as "hostname" 1s 987ms

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

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

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

And I select "1-RH-LIKE-KEY" from "activationKeys" 89ms

And I select the hostname of "proxy" from "proxies" if present 3s 528ms

And I click on "Bootstrap" 117ms

And I wait until I see "Bootstrap process initiated." text 34s 457ms

And I follow the left menu "Systems > System List > All" 380ms

And I wait until I see the name of "rhlike_minion", refreshing the page 45s 949ms

And I wait until onboarding is completed for "rhlike_minion" 42s 623ms

@proxy

Scenario:
Check connection from Red Hat-like minion to proxy

1s 784ms 4

Given I am on the Systems overview page of this "rhlike_minion" 1s 408ms

When I follow "Details" in the content area 120ms

And I follow "Connection" in the content area 108ms

Then I should see "proxy" short hostname 147ms

@proxy

Scenario:
Check registration on proxy of Red Hat-like minion

2s 2ms 4

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

When I follow "Details" in the content area 86ms

And I follow "Proxy" in the content area 94ms

Then I should see "rhlike_minion" hostname 121ms

Scenario:
Subscribe the Red Hat-like minion to a base channel

23s 668ms 11

Warning: Radio button 'Fake-Base-Channel-RH-like' is already checked

Given I am on the Systems overview page of this "rhlike_minion" 1s 199ms

When I follow "Software" in the content area 99ms

And I follow "Software Channels" in the content area 74ms

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

And I check radio button "Fake-Base-Channel-RH-like" 213ms

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

And I click on "Next" 119ms

Then I should see a "Confirm Software Channel Change" text 166ms

When I click on "Confirm" 123ms

Then I should see a "Changing the channels has been scheduled." text 460ms

And I wait until event "Subscribe channels scheduled by admin" is completed 20s 504ms

Scenario:
Detect latest Salt changes on the Red Hat-like minion

354ms 1

* Mon Feb 16 2026 Victor Zhestkov
- Fix the typo causing buiding EL9 bundle without binary dependencies

* Mon Feb 02 2026 Michael Calmer
- Rebuild because of maintenance release

* 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

When I query latest Salt changes on "rhlike_minion" 354ms

Scenario:
Check events history for failures on Red Hat-like minion

52s 652ms 2

Given I am on the Systems overview page of this "rhlike_minion" 1s 242ms

Then I check for failed events on history event page 51s 410ms

@build_host
Feature:Bootstrap a build host via the GUI 14m 53s 822ms 2 7

Scenario:
Clean up sumaform leftovers on build host

8s 498ms 1

When I perform a full salt minion cleanup on "build_host" 8s 498ms

Scenario:
Log in as admin user

38s 492ms 1

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

Scenario:
Bootstrap a build host

4m 30s 331ms 10 1

The hostname of build_host is uyuni-master-build-host.sumaci.aws

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

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

When I enter the hostname of "build_host" as "hostname" 359ms

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

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

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

And I select "1-BUILD-HOST-KEY-x86_64" from "activationKeys" 141ms

And I select the hostname of "proxy" from "proxies" if present 3s 230ms

And I click on "Bootstrap" 88ms

And I wait until I see "Bootstrap process initiated." text 4m 10s 36ms Show Error +

                                            
 Text 'Bootstrap process initiated.' not found (ScriptError)
./features/step_definitions/navigation_steps.rb:40:in `/^I wait until I see "([^"]*)" text$/'
features/init_clients/buildhost_bootstrap.feature:23:in `I wait until I see "Bootstrap process initiated." text'

15s 699ms Show Info +

20:14:58:000 - 20:19:14:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/systems/bootstrap

Screenshot +

Scenario:
Check the new bootstrapped build host in System Overview page

8m 20s 660ms 3 2 1

When I follow the left menu "Salt > Keys" 131ms

Then I should see a "accepted" text 348ms

When I follow the left menu "Systems > System List > All" 179ms

And I wait at most 500 seconds until I see the name of "build_host", refreshing the page 8m 20s Show Error +

                                            
 execution expired (Timeout::Error)
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/step_definitions/setup_steps.rb:209:in `/^I wait at most (\d+) seconds until I see the name of "([^"]*)", refreshing the page$/'
features/init_clients/buildhost_bootstrap.feature:30:in `I wait at most 500 seconds until I see the name of "build_host", refreshing the page'

And I wait at most 500 seconds until onboarding is completed for "build_host" 0s

Then the Salt master can reach "build_host" 0s

@proxy

Scenario:
Check connection from build host to proxy

369ms 3 1

Given I am on the Systems overview page of this "build_host" 369ms Show Error +

                                            
 No system found for hostname: uyuni-master-build-host.sumaci.aws (RuntimeError)
./features/support/commonlib.rb:421:in `get_system_id'
./features/step_definitions/navigation_steps.rb:488:in `/^I am on the Systems overview page of this "([^"]*)"$/'
features/init_clients/buildhost_bootstrap.feature:36:in `I am on the Systems overview page of this "build_host"'

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

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

Then I should see "proxy" short hostname 0s

@proxy

Scenario:
Check registration on build host of minion

27s 312ms 4 1

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

When I follow "Details" in the content area 80ms

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

Then I should see "build_host" hostname 10s 12ms Show Error +

                                            
 Hostname uyuni-master-build-host.sumaci.aws is not present (ScriptError)
./features/step_definitions/navigation_steps.rb:691:in `/^I should see "([^"]*)" hostname$/'
features/init_clients/buildhost_bootstrap.feature:46:in `I should see "build_host" hostname'

15s 957ms Show Info +

20:27:55:000 - 20:28:08:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/ProxyClients.do?sid=1000010000&

Screenshot +

Scenario:
Detect latest Salt changes on the SLES build host

16s 183ms 1 1

When I query latest Salt changes on "build_host" 506ms Show Error +

                                            
 FAIL: LANG=en_US.UTF-8 rpm -q --changelog venv-salt-minion returned status code = 1.
Output:
package venv-salt-minion is not installed
 (ScriptError)
./features/support/remote_node.rb:169:in `run_local'
./features/support/remote_node.rb:117:in `run'
./features/step_definitions/command_steps.rb:251:in `/^I query latest Salt changes on "(.*?)"$/'
features/init_clients/buildhost_bootstrap.feature:49:in `I query latest Salt changes on "build_host"'

15s 676ms Show Info +

20:28:24:000 - 20:28:25:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/ProxyClients.do?sid=1000010000&

Screenshot +

Scenario:
Check that the build host is a build host

16s 25ms 1 2 1

Given I am on the Systems overview page of this "build_host" 410ms Show Error +

                                            
 No system found for hostname: uyuni-master-build-host.sumaci.aws (RuntimeError)
./features/support/commonlib.rb:421:in `get_system_id'
./features/step_definitions/navigation_steps.rb:488:in `/^I am on the Systems overview page of this "([^"]*)"$/'
features/init_clients/buildhost_bootstrap.feature:52:in `I am on the Systems overview page of this "build_host"'

Then I should see a "[Container Build Host]" text 0s

Then I should see a "[OS Image Build Host]" text 0s

15s 615ms Show Info +

20:28:40:000 - 20:28:41:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/ProxyClients.do?sid=1000010000&

Screenshot +

Scenario:
Check events history for failures on SLES build host

15s 948ms 1 1 1

Given I am on the Systems overview page of this "build_host" 388ms Show Error +

                                            
 No system found for hostname: uyuni-master-build-host.sumaci.aws (RuntimeError)
./features/support/commonlib.rb:421:in `get_system_id'
./features/step_definitions/navigation_steps.rb:488:in `/^I am on the Systems overview page of this "([^"]*)"$/'
features/init_clients/buildhost_bootstrap.feature:57:in `I am on the Systems overview page of this "build_host"'

Then I check for failed events on history event page 0s

15s 560ms Show Info +

20:28:56:000 - 20:28:57:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/ProxyClients.do?sid=1000010000&

Screenshot +

@sle_minion
Feature:Bootstrap a Salt minion via the GUI 3m 14s 616ms 6 2

Scenario:
Clean up sumaform leftovers on SLES minion

10s 186ms 1

When I perform a full salt minion cleanup on "sle_minion" 10s 186ms

Scenario:
Log in as admin user

39s 133ms 1

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

Scenario:
Bootstrap a SLES minion

46s 562ms 11

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

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

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

When I enter the hostname of "sle_minion" as "hostname" 238ms

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

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

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

And I select "1-SUSE-KEY-x86_64" from "activationKeys" 120ms

And I select the hostname of "proxy" from "proxies" if present 3s 755ms

And I click on "Bootstrap" 110ms

And I wait until I see "Bootstrap process initiated." text 41s 497ms

And I report the bootstrap duration for "sle_minion" < 1ms

Scenario:
Check the new bootstrapped minion in System List page

1m 34s 40ms 8

It took 2 seconds to contact the minion

When I follow the left menu "Salt > Keys" 300ms

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

Then I should see a "accepted" text 132ms

When I follow the left menu "Systems > System List > All" 400ms

And I wait until I see the name of "sle_minion", refreshing the page 31s 322ms

And I wait until onboarding is completed for "sle_minion" 58s 746ms

Then the Salt master can reach "sle_minion" 2s 710ms

And I report the onboarding duration for "sle_minion" < 1ms

@susemanager

Scenario:
Use correct kernel image on the SLES minion

< 1ms 2

When I remove package "kernel-default-base" from this "sle_minion" 0s

And I install package "kernel-default" on this "sle_minion" 0s

@susemanager

Scenario:
Reboot the SLES minion to use the new kernel

< 1ms 1

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

@proxy

Scenario:
Check connection from minion to proxy

2s 930ms 4

Given I am on the Systems overview page of this "sle_minion" 2s 463ms

When I follow "Details" in the content area 150ms

And I follow "Connection" in the content area 143ms

Then I should see "proxy" short hostname 173ms

@proxy

Scenario:
Check registration on proxy of minion

1s 763ms 4

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

When I follow "Details" in the content area 110ms

And I follow "Proxy" in the content area 113ms

Then I should see "sle_minion" hostname 185ms

@ssh_minion
Feature:Bootstrap a Salt host managed via salt-ssh 3m 21s 76ms 5 2

Scenario:
Clean up sumaform leftovers on SLES SSH minion

10s 356ms 1

When I perform a full salt minion cleanup on "ssh_minion" 10s 356ms

Scenario:
Log in as admin user

39s 389ms 1

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

Scenario:
Bootstrap a SLES SSH minion

2m 28s 443ms 11

The hostname of ssh_minion is uyuni-master-suse-sshminion.sumaci.aws

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

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

When I check "manageWithSSH" 143ms

And I enter the hostname of "ssh_minion" as "hostname" 222ms

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

And I select the hostname of "proxy" from "proxies" if present 3s 399ms

And I click on "Bootstrap" 145ms

And I wait until I see "Bootstrap process initiated." text 56s 646ms

And I follow the left menu "Systems > System List > All" 202ms

And I wait until I see the name of "ssh_minion", refreshing the page 1m 12s 610ms

And I wait until onboarding is completed for "ssh_minion" 14s 569ms

@susemanager

Scenario:
Use correct kernel image on the SSH minion

< 1ms 2

When I remove package "kernel-default-base" from this "ssh_minion" 0s

And I install package "kernel-default" on this "ssh_minion" 0s

@susemanager

Scenario:
Reboot the SSH minion to use the new kernel

< 1ms 1

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

@proxy

Scenario:
Check connection from SSH minion to proxy

1s 449ms 4

Given I am on the Systems overview page of this "ssh_minion" 1s 135ms

When I follow "Details" in the content area 117ms

And I follow "Connection" in the content area 88ms

Then I should see "proxy" short hostname 107ms

@proxy

Scenario:
Check registration on proxy of SSH minion

1s 437ms 4

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

When I follow "Details" in the content area 78ms

And I follow "Proxy" in the content area 121ms

Then I should see "ssh_minion" hostname 134ms

@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 18s 336ms 5

Scenario:
Call spacewalk-debug on server

14s 332ms 1

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

Scenario:
Check the tomcat logs on server

665ms 1

Then the tomcat logs should not contain errors 665ms

Scenario:
Check salt event log for failures on server

1s 926ms 1

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

Scenario:
Check the taskomatic logs on server

755ms 1

Then the taskomatic logs should not contain errors 755ms

Scenario:
Check for out of memory errors

656ms 1

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

Feature:Debug the clients after the testsuite has run 1m 28s 122ms 1

Scenario:
Extract the logs from all our clients

1m 28s 122ms 1

When I extract the log files from all our active nodes 1m 28s 122ms

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

Scenario:
Count UI SCC accesses in rhn_web_ui.log

< 1ms 1

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

Scenario:
Count Taskomatic SCC accesses in rhn_taskomatic_daemon.log

< 1ms 1

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

All Scenarios

201

Passed Scenarios

156

Failed Scenarios

7

Skipped Scenarios

38

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

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

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

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

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

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

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

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

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

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

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

@server_http_proxy Scenario:Setup HTTP proxy < 1ms 9

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

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

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

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

@scc_credentials Scenario:Refresh SCC 29s 128ms 1

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@scc_credentials Scenario:Verify all channels are solved 2m 35s 861ms 2

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@skip_if_github_validation Feature:Create custom channels with development repositories 31s 502ms 9

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

@sle_minion Scenario:Create custom repositories inside the SUSE custom channel 7s 278ms 1

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

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

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

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

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

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

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

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

@skip_if_github_validation Scenario:Synchronize Fake-Child-Channel-i586 channel 16s 701ms 9

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

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

@rhlike_minion Scenario:Synchronize Fake-Base-Channel-RH-like channel 16s 659ms 9

@rhlike_minion Scenario:Synchronize Fake-Base-Channel-AppStream channel 15s 972ms 9

@pxeboot_minion @uyuni @scc_credentials Scenario:Synchronize the repository in the terminal channel < 1ms 9

@pxeboot_minion @uyuni @scc_credentials Scenario:Verify state of Fake-RPM-Terminal-Channel custom channel < 1ms 2

@skip_if_github_validation Feature:Synchronize development channels 1m 27s 390ms 4

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

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

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

@build_host @uyuni Scenario:Synchronize Devel-Build-Host-Channel channel 16s 164ms 9

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

@proxy

Scenario:
The proxy is healthy

4s 449ms 4

@sle_minion

Scenario:
The minion is healthy

6s 400ms 4

@build_host

Scenario:
The build host is healthy

3s 759ms 4

@ssh_minion

Scenario:
The SSH minion is healthy

6s 345ms 4

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

3s 195ms 4

@deblike_minion

Scenario:
The Debian-like minion is healthy

6s 112ms 4

@skip_if_cloud

Scenario:
The external resources can be reached

< 1ms 3

@server_http_proxy

Scenario:
The HTTP proxy is working

< 1ms 1

@auth_registry

Scenario:
The registry with authentication is healthy

646ms 1

@no_auth_registry

Scenario:
The registry without authentication is healthy

656ms 1

@custom_download_endpoint

Scenario:
The custom download endpoint is working

642ms 1

@server_http_proxy

Scenario:
Setup HTTP proxy

< 1ms 9

@scc_credentials @no_mirror

Scenario:
Enter valid SCC credentials

< 1ms 6

@no_auth_registry

Scenario:
Create an image store without credentials

2s 773ms 7

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

@proxy @susemanager

Scenario:
List all products for SUSE Multi-Linux Manager

< 1ms 6

@scc_credentials

Scenario:
Refresh SCC

29s 128ms 1

@scc_credentials

Scenario:
Let the products page appear

2s 163ms 6

@scc_credentials

Scenario:
Use the products and architecture filters

2s 423ms 7

@scc_credentials @susemanager

Scenario:
View the channels list in the products page

< 1ms 9

@scc_credentials @susemanager

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

< 1ms 30

@uyuni

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

4m 4s 77ms 5

@containerized_server @proxy @uyuni

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

35s 406ms 2

@scc_credentials @uyuni @build_host

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

43m 5s 464ms 20

@proxy @susemanager @transactional_server

Scenario:
Add SL Micro 6.1 as base OS for proxy

< 1ms 13

@proxy @susemanager @skip_if_transactional_server

Scenario:
Add SLES 15 SP7 as base OS for proxy

< 1ms 11

@proxy @susemanager @transactional_server

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

< 1ms 13

@proxy @susemanager @skip_if_transactional_server

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

< 1ms 12

@proxy @susemanager @transactional_server

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

< 1ms 13

@proxy @susemanager @skip_if_transactional_server

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

< 1ms 12

@scc_credentials @susemanager

Scenario:
Installer update channels got enabled when products were added

< 1ms 2

@scc_credentials

Scenario:
Verify all channels are solved

2m 35s 861ms 2

@scc_credentials @skip_if_github_validation

Scenario:
Detect product loading issues from the UI

43s 690ms 7

@scc_credentials @skip_if_github_validation

Scenario:
Report the synchronization duration for SLES 15 SP7

< 1ms 1

@sle_minion

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

1s 533ms 10

@pxeboot_minion @uyuni @scc_credentials

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

< 1ms 10

@deblike_minion

Scenario:
Add Debian-like AMD64 base channel

11s 590ms 11

@rhlike_minion

Scenario:
Add a RedHat-like base channel

1s 472ms 10

@rhlike_minion

Scenario:
Add a fake AppStream base channel

1s 492ms 10

@rhlike_minion

Scenario:
Create a fake AppStream repository

636ms 7

@rhlike_minion

Scenario:
Disable metadata check for the fake AppStream repository

10s 997ms 6

@sle_minion

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

2s 229ms 9

@rhlike_minion

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

2s 599ms 9

@rhlike_minion

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

2s 662ms 9

@sle_minion

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

1s 647ms 6

@deblike_minion

Scenario:
Create a fake repository for Debian-like

1s 200ms 7

@deblike_minion

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

1s 915ms 6

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Add the repository to the terminal child channel

< 1ms 9

@skip_if_github_validation
Feature:Create custom channels with development repositories 31s 502ms 9

@sle_minion

Scenario:
Create a custom channel for SUSE minions

1s 127ms 10

@sle_minion

Scenario:
Create custom repositories inside the SUSE custom channel

7s 278ms 1

@uyuni @build_host

Scenario:
Create a custom channel for Build Host

1s 519ms 10

@uyuni @build_host

Scenario:
Create custom repositories inside the Build Host custom channel

4s 218ms 1

@deblike_minion

Scenario:
Create a custom channel for Debian-like minions

1s 556ms 10

@deblike_minion

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

8s 358ms 1

@rhlike_minion

Scenario:
Create a custom channel for RH-like minions

1s 632ms 10

@rhlike_minion

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

5s 314ms 1

@sle_minion

Scenario:
Synchronize Fake-RPM-SUSE-Channel channel

16s 231ms 9

@sle_minion

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

4s 393ms 2

@skip_if_github_validation

Scenario:
Synchronize Fake-Child-Channel-i586 channel

16s 701ms 9

@sle_minion

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

16s 89ms 9

@deblike_minion

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

4s 738ms 9

@rhlike_minion

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

16s 659ms 9

@rhlike_minion

Scenario:
Synchronize Fake-Base-Channel-AppStream channel

15s 972ms 9

@pxeboot_minion @uyuni @scc_credentials

Scenario:
Synchronize the repository in the terminal channel

< 1ms 9

@pxeboot_minion @uyuni @scc_credentials

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

< 1ms 2

@skip_if_github_validation
Feature:Synchronize development channels 1m 27s 390ms 4

@sle_minion

Scenario:
Synchronize Devel-SUSE-Channel channel

16s 90ms 9

@deblike_minion

Scenario:
Synchronize Devel-Debian-like-Channel channel

15s 903ms 9

@rhlike_minion

Scenario:
Synchronize Devel-RH-like-Channel channel

39s 231ms 9

@build_host @uyuni

Scenario:
Synchronize Devel-Build-Host-Channel channel

16s 164ms 9

@sle_minion

Scenario:
Create an activation key with a channel

2s 288ms 2

@rhlike_minion

Scenario:
Create an activation key for RedHat-like minion

1s 670ms 2

@deblike_minion

Scenario:
Create an activation key for Debian-like minion

1s 326ms 2

@ssh_minion

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

1s 230ms 2

@ssh_minion

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

1s 263ms 2

@proxy

Scenario:
Create an activation key for the proxy

1s 193ms 2

@build_host

Scenario:
Create an activation key for the build host

1s 601ms 3

@scc_credentials

Scenario:
Create an activation key for the terminal

1s 338ms 2

@scc_credentials @susemanager

Scenario:
Update SLE key with synced base product

< 1ms 20