All Scenarios

1525

Passed Scenarios

1260

Failed Scenarios

47

Skipped Scenarios

218

Execution Time: 436m 23s 90ms

Expand All | Collapse All

Metadata

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

Feature:Sanity checks 43s 775ms 10 2

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

Scenario:
The server is healthy
11s 696ms 19

Then "server" should have a FQDN 390ms

And reverse resolution should work for "server" 629ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

And reverse resolution should work for "proxy" 280ms

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

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

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

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

And reverse resolution should work for "sle_minion" 443ms

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

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

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

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

And reverse resolution should work for "build_host" 225ms

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

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

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

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

And reverse resolution should work for "ssh_minion" 397ms

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

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

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

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

And reverse resolution should work for "rhlike_minion" 188ms

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

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

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

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

And reverse resolution should work for "deblike_minion" 206ms

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

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

@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
652ms 1

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

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

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

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

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

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

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

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

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

Scenario:
Create testing username
1s 497ms 12

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

And I follow "Create User" 677ms

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

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

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

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

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

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

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

And I click on "Create Login" 71ms

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

And I should see a "testing" link 14ms

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

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

And I follow "testing" 564ms

And I check "role_org_admin" 95ms

And I check "role_system_group_admin" 90ms

And I check "role_channel_admin" 89ms

And I check "role_activation_key_admin" 88ms

And I check "role_config_admin" 89ms

And I click on "Update" 1s 178ms

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

And I should see a "testing" text 80ms

@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
793ms 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" 793ms

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

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

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

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

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

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

And I ask to add new credentials 0s

And I enter the SCC credentials 0s

And I click on "Save" 0s

And I wait until the SCC credentials are valid 0s

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

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

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

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

And I click on "Save Preferences" 686ms

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

Scenario:
Change page size to 100 per page in testing user
3s 363ms 5

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

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

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

And I click on "Save Preferences" 637ms

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

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

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

New user kiwikiwi created with roles: image_admin

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

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

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

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

New user docker created with roles: image_admin

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

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

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

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

And I follow "Create" 520ms

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

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

And I click on "create-btn" 75ms

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

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

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

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

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

Scenario:
Disable scheduled reposyncs
4s 697ms 5

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

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

And I choose "disabled" 74ms

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

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

Scenario:
Disable scheduled Cobbler syncs
4s 644ms 5

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

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

And I choose "disabled" 49ms

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

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

@scc_credentials
Feature:List available channels and enable them 1m 38s 916ms 5 1

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

Scenario:
List available channels
33s 10ms 5

When I refresh SCC 30s 676ms

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

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

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

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

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

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

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

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

When I remove the mgr-sync cache file 686ms

And I execute mgr-sync refresh 1m 782ms

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

Feature:Synchronize products in the products page of the Setup Wizard 63m 14s 763ms 9 9

@scc_credentials
Scenario:
Refresh SCC
27s 636ms 1

When I refresh SCC 27s 636ms

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

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

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

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

Then I should see a "Arch" text 120ms

And I should see a "Channels" text 120ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I close the modal dialog 0s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

Then the SLE15 SP7 product should be added 0s

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

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

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

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

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

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

@containerized_server @proxy @uyuni
Scenario:
Add Uyuni Proxy product for Tumbleweed, including Uyuni Client Tools
33s 949ms 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" 19s 473ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 59ms

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

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

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

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

And I wait until all synchronized channels for "sles15-sp7" have finished 56m 37s 847ms

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

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

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

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

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

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

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

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

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

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

And I click the Add Product button 0s

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

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

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

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

@scc_credentials
Scenario:
Verify all channels are solved
1m 36s 919ms 2

SUCCESS: Channel opensuse_tumbleweed-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel opensuse_tumbleweed-x86_64 synchronization took 90 seconds.
SUCCESS: Channel opensuse_tumbleweed-uyuni-client-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel opensuse_tumbleweed-uyuni-client-x86_64 synchronization took 11 seconds.
SUCCESS: Channel opensuse_tumbleweed-uyuni-client-devel-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel opensuse_tumbleweed-uyuni-client-devel-x86_64 synchronization took 10 seconds.
SUCCESS: Channel opensuse_tumbleweed-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel opensuse_tumbleweed-x86_64 synchronization took 90 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 4 seconds.
SUCCESS: Channel sle15-sp7-installer-updates-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle15-sp7-installer-updates-x86_64 synchronization took 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 413 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 1215 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 42 seconds.
SUCCESS: Channel sle-module-python3-15-sp7-updates-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-module-python3-15-sp7-updates-x86_64 synchronization took 37 seconds.
SUCCESS: Channel sle-module-server-applications15-sp7-pool-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-module-server-applications15-sp7-pool-x86_64 synchronization took 53 seconds.
SUCCESS: Channel sle-module-server-applications15-sp7-updates-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-module-server-applications15-sp7-updates-x86_64 synchronization took 87 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 300 seconds.
SUCCESS: Channel sle-module-desktop-applications15-sp7-updates-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-module-desktop-applications15-sp7-updates-x86_64 synchronization took 57 seconds.
SUCCESS: Channel sle-module-devtools15-sp7-updates-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-module-devtools15-sp7-updates-x86_64 synchronization took 809 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 28 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 24 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 21 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 222 seconds.

When I wait until all synchronized channels have solved their dependencies 1m 36s 919ms

Then all channels have been synced without errors < 1ms

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

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

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

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

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

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

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

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

@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 23s 586ms 11 1

In Order to distribute software to the clients
As an authorized user
I want to create fake channels for each distribution

Scenario:
Log in as admin user
505ms 1

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

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

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

And I follow "Create Channel" 327ms

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

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

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

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

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

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

And I click on "Create Channel" 606ms

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

Scenario:
Add a fake child channel into the fake base channel x86_64
971ms 10

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

And I follow "Create Channel" 308ms

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

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

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

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

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

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

And I click on "Create Channel" 56ms

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

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

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

And I follow "Create Channel" 311ms

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

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

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

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

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

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

Scenario:
Add a fake base channel for i586
1s 443ms 10

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

And I follow "Create Channel" 273ms

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

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

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

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

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

And I click on "Create Channel" 573ms

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

Scenario:
Add a fake child channel into the fake base channel i586
1s 461ms 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" 74ms

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

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

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

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

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

And I click on "Create Channel" 558ms

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

Scenario:
Add a test base channel for x86_64
978ms 10

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

And I follow "Create Channel" 330ms

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

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

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

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

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

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

And I click on "Create Channel" 63ms

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

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

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

And I follow "Create Channel" 336ms

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

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

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

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

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

And I click on "Create Channel" 558ms

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

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

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

And I follow "Create Channel" 332ms

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

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

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

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

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

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

And I uncheck "gpg_check" 10s 71ms

And I click on "Create Channel" 529ms

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

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

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

And I follow "Create Channel" 350ms

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

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

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

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

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

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

And I click on "Create Channel" 56ms

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

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

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

And I follow "Create Channel" 347ms

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

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

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

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

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

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

And I click on "Create Channel" 57ms

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

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

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

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

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

And I follow "Create Repository" 327ms

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

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

And I click on "Create Repository" 573ms

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

And I should see "metadataSigned" as checked 19ms

Scenario:
Disable metadata check for the fake RPM repository
11s 36ms 6

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

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

And I uncheck "metadataSigned" 10s 80ms

And I click on "Update Repository" 458ms

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

And I should see "metadataSigned" as unchecked 19ms

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

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

And I follow "Create Repository" 322ms

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

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

And I click on "Create Repository" 60ms

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

And I should see "metadataSigned" as checked 18ms

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

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

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

And I uncheck "metadataSigned" 10s 71ms

And I click on "Update Repository" 432ms

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

And I should see "metadataSigned" as unchecked 16ms

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

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

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

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

And I click on "Update Channel" 63ms

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

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

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

And I click on "Save Repositories" 511ms

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

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

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

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

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

And I click on "Update Channel" 627ms

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

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

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

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

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

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

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

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

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

And I click on "Update Channel" 596ms

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

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

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

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

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

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

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

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

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

And I click on "Update Channel" 610ms

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

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

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

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

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

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

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

And I follow "Create Repository" 315ms

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

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

And I uncheck "metadataSigned" 10s 68ms

And I click on "Create Repository" 443ms

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

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

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

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

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

And I click on "Update Channel" 518ms

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

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

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

And I click on "Save Repositories" 618ms

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

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

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

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

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

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

And I click on "Save Repositories" 896ms

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

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

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

And I follow "Create Repository" 327ms

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

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

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

And I click on "Create Repository" 436ms

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

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

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

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

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

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

And I click on "Save Repositories" 750ms

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

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

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

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

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

And I click on "Update Channel" 0s

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

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

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

And I click on "Save Repositories" 0s

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

@skip_if_github_validation
Feature:Create custom channels with development repositories 30s 176ms 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
491ms 1

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

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

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

And I follow "Create Channel" 291ms

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

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

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

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

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

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

And I click on "Create Channel" 64ms

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

@sle_minion
Scenario:
Create custom repositories inside the SUSE custom channel
6s 959ms 1

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

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

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

And I follow "Create Channel" 380ms

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

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

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

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

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

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

And I click on "Create Channel" 565ms

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

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

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

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

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

And I follow "Create Channel" 362ms

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

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

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

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

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

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

And I click on "Create Channel" 529ms

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

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

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

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

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

And I follow "Create Channel" 269ms

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

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

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

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

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

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

And I click on "Create Channel" 570ms

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

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

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

Feature:Synchronize fake channels 2m 10s 551ms 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 764ms 2

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

And I enable source package syncing 1s 337ms

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

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

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

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

And I follow "Sync" 352ms

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

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

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

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

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

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

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

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

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

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

And I follow "Sync" 343ms

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

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

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

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

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

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

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

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

And I follow "Sync" 357ms

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

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

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

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

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

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

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

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

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

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

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

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

@deblike_minion
Scenario:
Synchronize Fake-Base-Channel-Debian-like channel
15s 905ms 9

DEBUG: Found channel 'fake-base-channel-debian-like' at line 257. Checking for completion...
DEBUG: Sync for fake-base-channel-debian-like still in progress (no completion message found).
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 437ms

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

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

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

And I follow "Sync" 429ms

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

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

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

@rhlike_minion
Scenario:
Synchronize Fake-Base-Channel-RH-like channel
15s 986ms 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 495ms

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

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

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

And I follow "Sync" 363ms

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

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

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

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

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

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

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

And I follow "Sync" 358ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

And I click on "Single Run Schedule" 359ms

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

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

Scenario:
Cleanup disable source package syncing
997ms 1

Then I disable source package syncing 997ms

@skip_if_github_validation
Feature:Synchronize development channels 1m 15s 236ms 4

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

@sle_minion
Scenario:
Synchronize Devel-SUSE-Channel channel
15s 947ms 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 441ms

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

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

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

And I follow "Sync" 344ms

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

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

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

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

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

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

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

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

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

And I follow "Sync" 334ms

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

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

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

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

@rhlike_minion
Scenario:
Synchronize Devel-RH-like-Channel channel
27s 510ms 9

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

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

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

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

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

And I follow "Sync" 348ms

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

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

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

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

@build_host @uyuni
Scenario:
Synchronize Devel-Build-Host-Channel channel
15s 846ms 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 460ms

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

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

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

And I follow "Sync" 348ms

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

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

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

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

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

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

@sle_minion
Scenario:
Create an activation key with a channel
1s 834ms 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 427ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 537ms

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

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

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

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

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

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

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

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

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

And I click on "Update Activation Key" 0s

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

@uyuni @ssh_minion
Scenario:
Update openSUSE Tumbleweed SSH key with synced base product
1s 866ms 10

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 470ms

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

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

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

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

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

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

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

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

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

And I click on "Update Activation Key" 0s

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 506ms

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

@scc_credentials @susemanager @proxy @containerized_server @transactional_server
Scenario:
Update the SLE Micro proxy key with synced base product
< 1ms 11

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

And I wait until "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 14ms 20

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

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

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

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

And I wait for child channels to appear 526ms

And I include the recommended child channels 181ms

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 479ms

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

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

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

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

And I wait for child channels to appear 779ms

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

And I wait for child channels to appear 322ms

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

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

And I click on "Update Activation Key" 492ms

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

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

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

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

And I wait for child channels to appear 856ms

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

And I wait for child channels to appear 302ms

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

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

And I click on "Update Activation Key" 515ms

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

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

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

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

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

And I wait for child channels to appear 539ms

And I include the recommended child channels 193ms

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

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

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

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

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

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

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

And I click on "Update Activation Key" 484ms

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

@susemanager @scc_credentials @build_host
Scenario:
Update terminal key with normal SUSE fake channel
< 1ms 9

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

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

And I wait for child channels to appear 0s

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

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

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

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

And I click on "Update Activation Key" 0s

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

@pxeboot_minion @uyuni @scc_credentials @build_host
Scenario:
Update terminal key with specific fake channel
< 1ms 9

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

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

And I wait for child channels to appear 0s

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

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

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

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

And I click on "Update Activation Key" 0s

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

@skip_if_github_validation @sle_minion
Scenario:
Update SLE key with to include dev child channel
1s 512ms 6

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

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

And I wait for child channels to appear 759ms

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

And I click on "Update Activation Key" 439ms

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

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

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

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

And I wait for child channels to appear 671ms

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

And I click on "Update Activation Key" 453ms

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

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

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

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

And I wait for child channels to appear 679ms

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

And I click on "Update Activation Key" 443ms

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

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

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

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

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

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

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

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

@containerized_server @scope_containerized_proxy @proxy
Feature:Setup containerized proxy 3m 27s 577ms 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 659ms 1

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

@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 672ms 1

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

Scenario:
Bootstrap the proxy host as a salt minion
35s 884ms 9

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 63ms

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

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

When I wait until onboarding is completed for "proxy" 1m 22s 528ms

Scenario:
Generate containerized proxy configuration
11s 399ms 2

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

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

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
17s 636ms 1

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

Scenario:
Wait until containerized proxy service is active
3s 951ms 10

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

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

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

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

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

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

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

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

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

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

Scenario:
The containerized proxy should be registered automatically
747ms 2

When I follow the left menu "Systems" 67ms

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

Scenario:
Check if Monitoring can be enabled on the containerized proxy
11s 96ms 3

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

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

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

@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 20s 999ms 7

Scenario:
Log in as admin user
38s 201ms 1

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

Scenario:
Bootstrap a Debian-like minion
2m 15s 650ms 14

The hostname of deblike_minion is uyuni-master-deblike-minion
* Wed Mar 4 2026 Victor Zhestkov
- Fix the issue preventing SELinux profile to be loaded on SLES 16
deployed using cloud images (bsc#1258957)
* 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

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

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

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

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

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

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

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

And I select the hostname of "proxy" from "proxies" if present 2s 715ms

And I click on "Bootstrap" 113ms

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

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

And I wait until I see the name of "deblike_minion", refreshing the page 46s 125ms

And I wait until onboarding is completed for "deblike_minion" 46s 217ms

And I query latest Salt changes on Debian-like system "deblike_minion" 869ms

@proxy
Scenario:
Check connection from the Debian-like minion to proxy
2s 240ms 4

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

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

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

Then I should see "proxy" short hostname 94ms

@proxy
Scenario:
Check registration on proxy of the Debian-like minion
1s 835ms 4

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

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

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

Then I should see "deblike_minion" hostname 141ms

Scenario:
Subscribe the Debian-like minion to a base channel
30s 440ms 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 635ms

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

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

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

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

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

And I click on "Next" 177ms

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

When I click on "Confirm" 170ms

Then I should see a "Changing the channels has been scheduled." text 1s 151ms

And I wait until event "Subscribe channels scheduled by admin" is completed 25s 413ms

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

* Wed Mar 4 2026 Victor Zhestkov
- Fix the issue preventing SELinux profile to be loaded on SLES 16
deployed using cloud images (bsc#1258957)
* 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

When I query latest Salt changes on Debian-like system "deblike_minion" 430ms

Scenario:
Check events history for failures on Debian-like minion
52s 201ms 2

Given I am on the Systems overview page of this "deblike_minion" 1s 182ms

Then I check for failed events on history event page 51s 19ms

@rhlike_minion
Feature:Bootstrap a Red Hat-like minion and do some basic operations on it 4m 32s 687ms 7

Scenario:
Log in as admin user
38s 456ms 1

Given I am authorized for the "Admin" section 38s 456ms

Scenario:
Bootstrap a Red Hat-like minion
2m 19s 25ms 13

The hostname of rhlike_minion is uyuni-master-rhlike-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 239ms

Then I should see a "Bootstrap Minions" text 225ms

When I enter the hostname of "rhlike_minion" as "hostname" 2s 37ms

And I enter "22" as "port" 68ms

And I enter "root" as "user" 75ms

And I enter "linux" as "password" 72ms

And I select "1-RH-LIKE-KEY" from "activationKeys" 94ms

And I select the hostname of "proxy" from "proxies" if present 2s 862ms

And I click on "Bootstrap" 76ms

And I wait until I see "Bootstrap process initiated." text 39s 745ms

And I follow the left menu "Systems > System List > All" 333ms

And I wait until I see the name of "rhlike_minion", refreshing the page 45s 761ms

And I wait until onboarding is completed for "rhlike_minion" 47s 433ms

@proxy
Scenario:
Check connection from Red Hat-like minion to proxy
1s 822ms 4

Given I am on the Systems overview page of this "rhlike_minion" 1s 566ms

When I follow "Details" in the content area 110ms

And I follow "Connection" in the content area 76ms

Then I should see "proxy" short hostname 69ms

@proxy
Scenario:
Check registration on proxy of Red Hat-like minion
1s 816ms 4

Given I am on the Systems overview page of this "proxy" 1s 481ms

When I follow "Details" in the content area 90ms

And I follow "Proxy" in the content area 101ms

Then I should see "rhlike_minion" hostname 142ms

Scenario:
Subscribe the Red Hat-like minion to a base channel
39s 90ms 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 653ms

When I follow "Software" in the content area 142ms

And I follow "Software Channels" in the content area 147ms

And I wait until I do not see "Loading..." text 267ms

And I check radio button "Fake-Base-Channel-RH-like" 375ms

And I wait until I do not see "Loading..." text 855ms

And I click on "Next" 128ms

Then I should see a "Confirm Software Channel Change" text 311ms

When I click on "Confirm" 140ms

Then I should see a "Changing the channels has been scheduled." text 736ms

And I wait until event "Subscribe channels scheduled by admin" is completed 34s 332ms

Scenario:
Detect latest Salt changes on the Red Hat-like minion
347ms 1

* Wed Mar 04 2026 Victor Zhestkov
- Fix the issue preventing SELinux profile to be loaded on SLES 16
deployed using cloud images (bsc#1258957)

* 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

When I query latest Salt changes on "rhlike_minion" 347ms

Scenario:
Check events history for failures on Red Hat-like minion
52s 128ms 2

Given I am on the Systems overview page of this "rhlike_minion" 1s 62ms

Then I check for failed events on history event page 51s 66ms

@build_host
Feature:Bootstrap a build host via the GUI 6m 5s 7ms 9

Scenario:
Clean up sumaform leftovers on build host
8s 477ms 1

When I perform a full salt minion cleanup on "build_host" 8s 477ms

Scenario:
Log in as admin user
39s 20ms 1

Given I am authorized for the "Admin" section 39s 20ms

Scenario:
Bootstrap a build host
46s 537ms 10

The hostname of build_host is uyuni-master-build-host.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 301ms

Then I should see a "Bootstrap Minions" text 131ms

When I enter the hostname of "build_host" as "hostname" 236ms

And I enter "22" as "port" 117ms

And I enter "root" as "user" 183ms

And I enter "linux" as "password" 118ms

And I select "1-BUILD-HOST-KEY-x86_64" from "activationKeys" 173ms

And I select the hostname of "proxy" from "proxies" if present 3s 216ms

And I click on "Bootstrap" 96ms

And I wait until I see "Bootstrap process initiated." text 41s 958ms

Scenario:
Check the new bootstrapped build host in System Overview page
3m 4s 283ms 6

It took 2 seconds to contact the minion

When I follow the left menu "Salt > Keys" 237ms

Then I should see a "accepted" text 555ms

When I follow the left menu "Systems > System List > All" 446ms

And I wait at most 500 seconds until I see the name of "build_host", refreshing the page 29s 139ms

And I wait at most 500 seconds until onboarding is completed for "build_host" 2m 32s 26ms

Then the Salt master can reach "build_host" 1s 877ms

@proxy
Scenario:
Check connection from build host to proxy
1s 498ms 4

Given I am on the Systems overview page of this "build_host" 1s 268ms

When I follow "Details" in the content area 83ms

And I follow "Connection" in the content area 78ms

Then I should see "proxy" short hostname 69ms

@proxy
Scenario:
Check registration on build host of minion
1s 278ms 4

Given I am on the Systems overview page of this "proxy" 1s 30ms

When I follow "Details" in the content area 69ms

And I follow "Proxy" in the content area 75ms

Then I should see "build_host" hostname 103ms

Scenario:
Detect latest Salt changes on the SLES build host
554ms 1

* Wed Mar 04 2026 vzhestkov@suse.com
- Fix the issue preventing SELinux profile to be loaded on SLES 16
deployed using cloud images (bsc#1258957)

* Mon Feb 16 2026 vzhestkov@suse.com
- Fix the typo causing buiding EL9 bundle without binary dependencies

* Mon Feb 02 2026 mc@suse.com
- Rebuild because of maintenance release

* Mon Jan 19 2026 marek.czernek@suse.com
- 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

When I query latest Salt changes on "build_host" 554ms

Scenario:
Check that the build host is a build host
1s 254ms 3

Given I am on the Systems overview page of this "build_host" 1s 60ms

Then I should see a "[Container Build Host]" text 97ms

Then I should see a "[OS Image Build Host]" text 96ms

Scenario:
Check events history for failures on SLES build host
1m 22s 102ms 2

Given I am on the Systems overview page of this "build_host" 1s 174ms

Then I check for failed events on history event page 1m 20s 928ms

@sle_minion
Feature:Bootstrap a Salt minion via the GUI 3m 18s 602ms 6 2

Scenario:
Clean up sumaform leftovers on SLES minion
9s 982ms 1

When I perform a full salt minion cleanup on "sle_minion" 9s 982ms

Scenario:
Log in as admin user
40s 386ms 1

Given I am authorized for the "Admin" section 40s 386ms

Scenario:
Bootstrap a SLES minion
45s 514ms 11

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 326ms

Then I should see a "Bootstrap Minions" text 267ms

When I enter the hostname of "sle_minion" as "hostname" 295ms

And I enter "22" as "port" 81ms

And I enter "root" as "user" 100ms

And I enter "linux" as "password" 81ms

And I select "1-SUSE-KEY-x86_64" from "activationKeys" 117ms

And I select the hostname of "proxy" from "proxies" if present 3s 771ms

And I click on "Bootstrap" 120ms

And I wait until I see "Bootstrap process initiated." text 40s 352ms

And I report the bootstrap duration for "sle_minion" < 1ms

Scenario:
Check the new bootstrapped minion in System List page
1m 38s 679ms 8

It took 3 seconds to contact the minion

When I follow the left menu "Salt > Keys" 262ms

And I wait until I do not see "Loading..." text 985ms

Then I should see a "accepted" text 115ms

When I follow the left menu "Systems > System List > All" 261ms

And I wait until I see the name of "sle_minion", refreshing the page 31s 82ms

And I wait until onboarding is completed for "sle_minion" 1m 3s 474ms

Then the Salt master can reach "sle_minion" 2s 496ms

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 85ms 4

Given I am on the Systems overview page of this "sle_minion" 1s 582ms

When I follow "Details" in the content area 222ms

And I follow "Connection" in the content area 192ms

Then I should see "proxy" short hostname 87ms

@proxy
Scenario:
Check registration on proxy of minion
1s 953ms 4

Given I am on the Systems overview page of this "proxy" 1s 564ms

When I follow "Details" in the content area 145ms

And I follow "Proxy" in the content area 93ms

Then I should see "sle_minion" hostname 149ms

@ssh_minion
Feature:Bootstrap a Salt host managed via salt-ssh 3m 21s 708ms 5 2

Scenario:
Clean up sumaform leftovers on SLES SSH minion
9s 460ms 1

When I perform a full salt minion cleanup on "ssh_minion" 9s 460ms

Scenario:
Log in as admin user
40s 530ms 1

Given I am authorized for the "Admin" section 40s 530ms

Scenario:
Bootstrap a SLES SSH minion
2m 28s 237ms 11

The hostname of ssh_minion is uyuni-master-suse-sshminion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 285ms

Then I should see a "Bootstrap Minions" text 174ms

When I check "manageWithSSH" 205ms

And I enter the hostname of "ssh_minion" as "hostname" 307ms

And I enter "linux" as "password" 105ms

And I select the hostname of "proxy" from "proxies" if present 3s 955ms

And I click on "Bootstrap" 134ms

And I wait until I see "Bootstrap process initiated." text 52s 825ms

And I follow the left menu "Systems > System List > All" 163ms

And I wait until I see the name of "ssh_minion", refreshing the page 1m 13s 557ms

And I wait until onboarding is completed for "ssh_minion" 16s 523ms

@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
2s 35ms 4

Given I am on the Systems overview page of this "ssh_minion" 1s 722ms

When I follow "Details" in the content area 94ms

And I follow "Connection" in the content area 112ms

Then I should see "proxy" short hostname 105ms

@proxy
Scenario:
Check registration on proxy of SSH minion
1s 443ms 4

Given I am on the Systems overview page of this "proxy" 1s 167ms

When I follow "Details" in the content area 93ms

And I follow "Proxy" in the content area 73ms

Then I should see "ssh_minion" hostname 110ms

@scope_visualization
Feature:Secure connection 259ms 4

Scenario:
Connecting to the server insecurely
2ms 2

Error: 302 302

When I connect to the server insecurely 2ms

Then the connection should redirect to the secured channel < 1ms

Scenario:
Connecting to the server securely
90ms 3

When I connect to the server securely 90ms

Then the connection should be secured < 1ms

And the page title should contain "Sign In" text < 1ms

Scenario:
Connecting to the server securely while using CA certificate file
80ms 3

ssl_ca_cert_file: /etc/ssl/certs/uyuni-master-server.sumaci.aws.pem

When I connect to the server securely while using CA certificate file 80ms

Then the connection should be secured < 1ms

And the page title should contain "Sign In" text < 1ms

Scenario:
Connecting to the server securely while using incorrect CA certificate file
85ms 2

When I connect to the server securely while using incorrect certificate as a CA certificate file 85ms

Then the secure connection should fail due to unverified certificate signature < 1ms

Feature:List available products 2s 693ms 1 2

In order to use software channels
As root user
I want to list available products from command line

@susemanager
Scenario:
List available products
< 1ms 2

When I execute mgr-sync "list products" with user "admin" and password "admin" 0s

Then I should get "[ ] SUSE Linux Enterprise Desktop 15 SP3 x86_64" 0s

@uyuni
Scenario:
List available products
2s 693ms 1 1

When I execute mgr-sync "list products" with user "admin" and password "admin" 2s 693ms

Then I should get "[ ] openSUSE Leap 15.6 x86_64" < 1ms Show Error + 
                                            
 '[ ] openSUSE Leap 15.6 x86_64' not found in output 'Available Products:

(R) - recommended extension

Status:
  - [I] - product is installed
  - [ ] - product is not installed, but is available
  - [U] - product is unavailable

[ ] RHEL and Liberty 8 Base
[ ] RHEL and Liberty 9 Base
[ ] RHEL7 Base x86_64
[ ] SUSE Linux Enterprise Desktop 15 SP4 x86_64
[ ] SUSE Linux Enterprise Micro 5.2 x86_64
[ ] SUSE Linux Enterprise Micro 5.3 x86_64
[ ] SUSE Linux Enterprise Server 15 SP4 x86_64
[ ] SUSE Linux Enterprise Server 15 SP5 x86_64
[ ] SUSE Linux Enterprise Server 15 SP6 x86_64
[I] SUSE Linux Enterprise Server 15 SP7 x86_64
  [I] (R) Basesystem Module 15 SP7 x86_64
  [ ] Containers Module 15 SP7 x86_64
  [I] Desktop Applications Module 15 SP7 x86_64
  [I] Development Tools Module 15 SP7 x86_64
  [ ] Public Cloud Module 15 SP7 x86_64
  [I] (R) Python 3 Module 15 SP7 x86_64
  [I] (R) Server Applications Module 15 SP7 x86_64
  [I] (R) Systems Management Module 15 SP7 x86_64
  [ ] Web and Scripting Module 15 SP7 x86_64
  [ ] SUSE Linux Enterprise Live Patching 15 SP7 x86_64
' (ScriptError)
./features/step_definitions/command_steps.rb:196:in `/^I should get "([^"]*)"$/'
features/secondary/srv_mgr_sync_list_products.feature:17:in `I should get "[ ] openSUSE Leap 15.6 x86_64"'

@susemanager
Scenario:
List all available products
< 1ms 4

When I execute mgr-sync "list products -e" 0s

Then I should get "[ ] SUSE Linux Enterprise Desktop 15 SP3 x86_64" 0s

And I should get " [ ] (R) Basesystem Module 15 SP3 x86_64" 0s

And I should get " [ ] Desktop Applications Module 15 SP3 x86_64" 0s

@skip_if_containerized_server @skip_if_github_validation @scope_monitoring
Feature:Disable and re-enable monitoring of the server < 1ms 7

Scenario:
Log in as admin user
< 1ms 1

Given I am authorized for the "Admin" section 0s

Scenario:
Disable monitoring from the UI
< 1ms 11

When I follow the left menu "Admin > Manager Configuration > Monitoring" 0s

And I wait until I see "Server self monitoring" text 0s

And I click on "Disable" 0s

And I wait until button "Disable" becomes enabled 0s

Then I should see a "Monitoring disabled successfully." text 0s

And I should see a list item with text "System" and a failing bullet 0s

And I should see a list item with text "PostgreSQL database" and a failing bullet 0s

And I should see a list item with text "Server self monitoring" and a warning bullet 0s

And I should see a list item with text "Taskomatic (Java JMX)" and a warning bullet 0s

And I should see a list item with text "Tomcat (Java JMX)" and a warning bullet 0s

And I should see a "Restarting Tomcat and Taskomatic is needed for the configuration changes to take effect." text 0s

Scenario:
Restart spacewalk services to apply config changes after disabling monitoring
< 1ms 1

When I restart the spacewalk service 0s

Scenario:
Check that monitoring is disabled
< 1ms 18

Given I am authorized for the "Admin" section 0s

When I follow the left menu "Admin > Manager Configuration > Monitoring" 0s

And I wait until I see "Server self monitoring" text 0s

Then I should see a "Enable" button 0s

And I should see a "Disable" button 0s

And I should see a list item with text "System" and a failing bullet 0s

And I should see a list item with text "PostgreSQL database" and a failing bullet 0s

And I should see a list item with text "Server self monitoring" and a failing bullet 0s

And I should see a list item with text "Taskomatic (Java JMX)" and a failing bullet 0s

And I should see a list item with text "Tomcat (Java JMX)" and a failing bullet 0s

And I should not see a "Restarting Tomcat and Taskomatic is needed for the configuration changes to take effect." text 0s

And file "/etc/rhn/rhn.conf" should contain "prometheus_monitoring_enabled = 0" on server 0s

And file "/etc/sysconfig/tomcat/systemd/jmx.conf" should not exist on server 0s

And file "/etc/sysconfig/taskomatic/systemd/jmx.conf" should not exist on server 0s

And port "3333" should be closed 0s

And port "3334" should be closed 0s

And port "5556" should be closed 0s

And port "5557" should be closed 0s

Scenario:
Enable monitoring from the UI
< 1ms 11

When I follow the left menu "Admin > Manager Configuration > Monitoring" 0s

And I wait until I see "Server self monitoring" text 0s

And I click on "Enable" 0s

And I wait until button "Enable" becomes enabled 0s

Then I should see a "Monitoring enabled successfully." text 0s

And I should see a list item with text "System" and a success bullet 0s

And I should see a list item with text "PostgreSQL database" and a success bullet 0s

And I should see a list item with text "Server self monitoring" and a pending bullet 0s

And I should see a list item with text "Taskomatic (Java JMX)" and a pending bullet 0s

And I should see a list item with text "Tomcat (Java JMX)" and a pending bullet 0s

And I should see a "Restarting Tomcat and Taskomatic is needed for the configuration changes to take effect." text 0s

Scenario:
Restart spacewalk services to apply config changes after enabling monitoring
< 1ms 1

When I restart the spacewalk service 0s

Scenario:
Check that monitoring is enabled
< 1ms 18

Given I am authorized for the "Admin" section 0s

When I follow the left menu "Admin > Manager Configuration > Monitoring" 0s

And I wait until I see "Server self monitoring" text 0s

Then I should see a "Enable" button 0s

And I should see a "Disable" button 0s

And I should see a list item with text "System" and a success bullet 0s

And I should see a list item with text "PostgreSQL database" and a success bullet 0s

And I should see a list item with text "Server self monitoring" and a success bullet 0s

And I should see a list item with text "Taskomatic (Java JMX)" and a success bullet 0s

And I should see a list item with text "Tomcat (Java JMX)" and a success bullet 0s

And I should not see a "Restarting Tomcat and Taskomatic is needed for the configuration changes to take effect." text 0s

And file "/etc/rhn/rhn.conf" should contain "prometheus_monitoring_enabled = 1" on server 0s

And file "/etc/sysconfig/tomcat/systemd/jmx.conf" should contain "jmx_prometheus_javaagent.jar=5556" on server 0s

And file "/etc/sysconfig/taskomatic/systemd/jmx.conf" should contain "jmx_prometheus_javaagent.jar=5557" on server 0s

And port "3333" should be closed 0s

And port "3334" should be closed 0s

And port "5556" should be open 0s

And port "5557" should be open 0s

@skip_if_github_validation @skip_if_cloud @scope_virtual_host_manager
Feature:Virtual host manager web UI < 1ms 9

Scenario:
Log in as org admin user
< 1ms 1

Given I am authorized 0s

Scenario:
Check the VHM page
< 1ms 3

When I follow the left menu "Systems > Virtual Host Managers" 0s

Then I should see a "Virtual Host Managers" text 0s

And I should see a "No Virtual Host Managers." text 0s

Scenario:
Check VMware page
< 1ms 8

When I click on "Create" 0s

And I follow "VMWare-based" 0s

Then I should see a "Add a VMWare-based Virtual Host Manager" text 0s

And I should see a "Label" text 0s

And I should see a "Hostname" text 0s

And I should see a "Port" text 0s

And I should see a "Username" text 0s

And I should see a "Password" text 0s

Scenario:
Create Virtual Host
< 1ms 9

When I follow the left menu "Systems > Virtual Host Managers" 0s

And I copy vCenter configuration file on server 0s

And I click on "Create" 0s

When I follow "File-based" 0s

Then I should see a "Add a File-based Virtual Host Manager" text 0s

When I enter "file-vmware" as "label" 0s

And I enter "file:///var/tmp/vCenter.json" as "module_url" 0s

And I click on "Create" 0s

Then I should see a "file-vmware" link 0s

Scenario:
Run virtual-host-gatherer
< 1ms 6

When I follow the left menu "Systems > Virtual Host Managers" 0s

And I follow "file-vmware" 0s

Then I should see a "file:///var/tmp/vCenter.json" text 0s

And I should see a "SUSE Test" text 0s

When I click on "Refresh Data" 0s

Then I should see a "Refreshing the data for this Virtual Host Manager has been triggered." text 0s

Scenario:
Check new virtual hosts
< 1ms 7

Given I am on the Systems page 0s

And I wait until I see "10.162.186.111" text, refreshing the page 0s

When I follow "10.162.186.111" 0s

Then I should see a "OS: VMware ESXi" text 0s

When I follow the left menu "Systems > System List > Virtual Systems" 0s

Then I should see a "vCenter" text 0s

And I should see a "NSX-l3gateway" text 0s

Scenario:
Delete Virtual Host Manager
< 1ms 7

When I follow the left menu "Systems > Virtual Host Managers" 0s

And I follow "file-vmware" 0s

Then I should see a "file:///var/tmp/vCenter.json" text 0s

When I click on "Delete" in element "virtual-host-managers" 0s

And I click on "Delete" in "Delete Virtual Host Manager" modal 0s

And I wait until I see "Virtual Host Manager has been deleted." text 0s

Then I should see a "No Virtual Host Managers." text 0s

Scenario:
Cleanup: delete virtual host 10.162.186.111
< 1ms 5

Given I am on the Systems page 0s

When I follow "10.162.186.111" 0s

And I follow "Delete System" 0s

And I click on "Delete Profile" 0s

And I wait until I see "has been deleted" text 0s

Scenario:
Cleanup: delete virtual host 10.162.186.112
< 1ms 5

Given I am on the Systems page 0s

When I follow "10.162.186.112" 0s

And I follow "Delete System" 0s

And I click on "Delete Profile" 0s

And I wait until I see "has been deleted" text 0s

@skip_if_github_validation @scope_power_management @scope_cobbler @sle_minion
Feature:IPMI Power management 1m 45s 559ms 12

Scenario:
Fake an IPMI host
9s 892ms 1

When the server starts mocking an IPMI host 9s 892ms

Scenario:
Log in as admin user
37s 741ms 1

Given I am authorized for the "Admin" section 37s 741ms

Scenario:
Start Cobbler monitoring
6s 608ms 1

When I start local monitoring of Cobbler 6s 608ms

Scenario:
Check the power management page
5s 411ms 6

Given I am on the Systems overview page of this "sle_minion" 5s 82ms

When I follow "Provisioning" in the content area 86ms

And I follow "Power Management" in the content area 72ms

Then I should see a "Power Management Settings" text 76ms

And I should see a "IPMI" text 65ms

And I should see a "Save" button 27ms

Scenario:
Save power management values
6s 611ms 9

When I enter "fakeipmi" as "powerAddress" 58ms

And I enter "ipmiusr" as "powerUsername" 56ms

And I enter "test" as "powerPassword" 53ms

And I click on "Save" 648ms

Then I should see a "Power settings saved" text 77ms

And the cobbler report should contain "Power Management Address : fakeipmi" for "sle_minion" 1s 719ms

And the cobbler report should contain "Power Management Username : ipmiusr" for "sle_minion" 1s 337ms

And the cobbler report should contain "Power Management Password : test" for "sle_minion" 1s 321ms

And the cobbler report should contain "Power Management Type : ipmilan" for "sle_minion" 1s 339ms

Scenario:
Test IPMI functions
18s 518ms 18

When I follow "Provisioning" in the content area 68ms

And I follow "Power Management" in the content area 54ms

And I click on "Power On" 2s 854ms

And I click on "Get status" 751ms

Then I should see the power is "On" 31ms

When I click on "Power Off" 2s 831ms

Then I should see a "system has been powered off" text 72ms

And I should see the power is "Unknown" 24ms

When I click on "Get status" 58ms

Then I should see the power is "Off" 23ms

When I click on "Power On" 56ms

Then I should see a "system has been powered on" text 78ms

When I click on "Get status" 695ms

Then I should see the power is "On" 24ms

When I click on "Reboot" 10s 107ms

Then I should see a "system has been rebooted" text 77ms

When I click on "Get status" 682ms

Then I should see the power is "On" 24ms

Scenario:
Check power management SSM configuration
8s 216ms 21

When I follow the left menu "Systems > System List > All" 161ms

And I click on the clear SSM button 143ms

And I check the "sle_minion" client 425ms

And I follow the left menu "Systems > System Set Manager > Overview" 536ms

And I follow "Configure power management" in the content area 71ms

Then I should see "sle_minion" as link 17ms

And I should see a "Change Power Management Configuration" text 83ms

And I should see a "Type" text 76ms

And I should see a "Network address" text 76ms

And I should see a "Username" text 77ms

And I should see a "Password" text 76ms

And I should see a "System identifier" text 74ms

And I should see a "Update" button 19ms

When I enter "testing" as "powerUsername" 55ms

And I enter "qwertz" as "powerPassword" 57ms

And I click on "Update" 447ms

Then I should see a "Configuration successfully saved for 1 system(s)" text 83ms

And the cobbler report should contain "Power Management Username : testing" for "sle_minion" 1s 734ms

And the cobbler report should contain "Power Management Password : qwertz" for "sle_minion" 1s 322ms

And the cobbler report should contain "Power Management Address : fakeipmi" for "sle_minion" 1s 344ms

And the cobbler report should contain "Power Management Type : ipmilan" for "sle_minion" 1s 331ms

Scenario:
Check power management SSM operation
222ms 6

And I follow the left menu "Systems > System Set Manager > Overview" 81ms

When I follow "power management operations" in the content area 72ms

Then I should see "sle_minion" as link 11ms

And I should see a "Power On" button 18ms

And I should see a "Power Off" button 18ms

And I should see a "Reboot" button 18ms

Scenario:
Cleanup: reset IPMI values
6s 982ms 8

Given I want to operate on this "sle_minion" 368ms

When I set power management value "" for "powerAddress" 405ms

And I set power management value "" for "powerUsername" 391ms

And I set power management value "" for "powerPassword" 394ms

Then the cobbler report should contain "Power Management Address :" for "sle_minion" 1s 329ms

And the cobbler report should contain "Power Management Username :" for "sle_minion" 1s 347ms

And the cobbler report should contain "Power Management Password :" for "sle_minion" 1s 348ms

And the cobbler report should contain "Power Management Type : ipmilan" for "sle_minion" 1s 398ms

Scenario:
Cleanup: tear down the IPMI host
475ms 1

When the server stops mocking an IPMI host 475ms

Scenario:
Cleanup: remove remaining systems from SSM after power management tests
59ms 1

When I click on the clear SSM button 59ms

Scenario:
Check for errors in Cobbler monitoring
4s 819ms 1

Then the local logs for Cobbler should not contain errors 4s 819ms

@skip_if_github_validation @scope_api @sle_minion
Feature:IPMI Power management API 30s 447ms 6

Scenario:
Setup an IPMI host for API test
996ms 2

When the server starts mocking an IPMI host 630ms

And I want to operate on this "sle_minion" 366ms

Scenario:
Check the power management settings for API test
411ms 2

When I fetch power management values 411ms

Then power management results should have "ipmilan" for "powerType" < 1ms

Scenario:
Save power management values for API test
6s 945ms 8

When I set power management value "fakeipmi" for "powerAddress" 386ms

And I set power management value "ipmiusr" for "powerUsername" 405ms

And I set power management value "test" for "powerPassword" 464ms

And I set power management value "ipmilan" for "powerType" 380ms

Then the cobbler report should contain "Power Management Address : fakeipmi" for "sle_minion" 1s 316ms

And the cobbler report should contain "Power Management Username : ipmiusr" for "sle_minion" 1s 315ms

And the cobbler report should contain "Power Management Password : test" for "sle_minion" 1s 346ms

And the cobbler report should contain "Power Management Type : ipmilan" for "sle_minion" 1s 329ms

Scenario:
Test IPMI functions for API test
14s 746ms 6

When I turn power on 2s 671ms

Then the power status is "on" 537ms

When I turn power off 2s 648ms

Then the power status is "off" 534ms

When I do power management reboot 7s 823ms

Then the power status is "on" 530ms

Scenario:
Cleanup: reset IPMI values for API test
6s 848ms 7

When I set power management value "" for "powerAddress" 398ms

And I set power management value "" for "powerUsername" 385ms

And I set power management value "" for "powerPassword" 391ms

Then the cobbler report should contain "Power Management Address :" for "sle_minion" 1s 668ms

And the cobbler report should contain "Power Management Username :" for "sle_minion" 1s 347ms

And the cobbler report should contain "Power Management Password :" for "sle_minion" 1s 329ms

And the cobbler report should contain "Power Management Type : ipmilan" for "sle_minion" 1s 328ms

Scenario:
Cleanup: tear down the IPMI host for API test
499ms 1

When the server stops mocking an IPMI host 499ms

@skip_if_github_validation @scope_power_management @scope_cobbler @sle_minion
Feature:Redfish Power management 52s 359ms 11

Scenario:
Setup a Redfish host
7s 507ms 1

When the controller starts mocking a Redfish host 7s 507ms

Scenario:
Log in as admin user
459ms 1

Given I am authorized for the "Admin" section 459ms

Scenario:
Start Cobbler monitoring
6s 396ms 1

When I start local monitoring of Cobbler 6s 396ms

Scenario:
Save power management values for Redfish
7s 683ms 13

Given I am on the Systems overview page of this "sle_minion" 1s 230ms

When I follow "Provisioning" in the content area 78ms

And I follow "Power Management" in the content area 68ms

And I enter the controller hostname as the redfish server address 102ms

And I enter "ipmiusr" as "powerUsername" 55ms

And I enter "test" as "powerPassword" 53ms

And I select "Redfish" from "powerType" 81ms

And I click on "Save" 66ms

Then I should see a "Power settings saved" text 568ms

And the cobbler report should contain ":8443" for "sle_minion" 1s 374ms

And the cobbler report should contain "Power Management Username : ipmiusr" for "sle_minion" 1s 331ms

And the cobbler report should contain "Power Management Password : test" for "sle_minion" 1s 319ms

And the cobbler report should contain "Power Management Type : redfish" for "sle_minion" 1s 352ms

Scenario:
Test Redfish functions
11s 302ms 18

When I follow "Provisioning" in the content area 73ms

And I follow "Power Management" in the content area 59ms

And I click on "Power On" 840ms

And I click on "Get status" 895ms

Then I should see the power is "On" 26ms

When I click on "Power Off" 969ms

Then I should see a "system has been powered off" text 71ms

And I should see the power is "Unknown" 26ms

When I click on "Get status" 834ms

Then I should see the power is "Off" 24ms

When I click on "Power On" 60ms

Then I should see a "system has been powered on" text 71ms

When I click on "Get status" 58ms

Then I should see the power is "On" 24ms

When I click on "Reboot" 6s 339ms

Then I should see a "system has been rebooted" text 70ms

When I click on "Get status" 834ms

Then I should see the power is "On" 22ms

Scenario:
Check power management SSM configuration for Redfish
7s 995ms 21

When I follow the left menu "Systems > System List > All" 153ms

And I click on the clear SSM button 55ms

And I check the "sle_minion" client 432ms

And I follow the left menu "Systems > System Set Manager > Overview" 491ms

And I follow "Configure power management" in the content area 76ms

Then I should see "sle_minion" as link 13ms

And I should see a "Change Power Management Configuration" text 73ms

And I should see a "Type" text 74ms

And I should see a "Network address" text 81ms

And I should see a "Username" text 71ms

And I should see a "Password" text 73ms

And I should see a "System identifier" text 74ms

And I should see a "Update" button 17ms

When I enter "testing" as "powerUsername" 50ms

And I enter "qwertz" as "powerPassword" 50ms

And I click on "Update" 433ms

Then I should see a "Configuration successfully saved for 1 system(s)" text 80ms

And the cobbler report should contain "Power Management Username : testing" for "sle_minion" 1s 738ms

And the cobbler report should contain "Power Management Password : qwertz" for "sle_minion" 1s 320ms

And the cobbler report should contain ":8443" for "sle_minion" 1s 309ms

And the cobbler report should contain "Power Management Type : redfish" for "sle_minion" 1s 323ms

Scenario:
Check power management SSM operation for Redfish
253ms 6

And I follow the left menu "Systems > System Set Manager > Overview" 80ms

When I follow "power management operations" in the content area 98ms

Then I should see "sle_minion" as link 14ms

And I should see a "Power On" button 20ms

And I should see a "Power Off" button 19ms

And I should see a "Reboot" button 20ms

Scenario:
Cleanup: reset Redfish values
7s 171ms 9

Given I want to operate on this "sle_minion" 353ms

When I set power management value "" for "powerAddress" 389ms

And I set power management value "" for "powerUsername" 384ms

And I set power management value "" for "powerPassword" 369ms

And I set power management value "ipmilan" for "powerType" 366ms

Then the cobbler report should contain "Power Management Address :" for "sle_minion" 1s 323ms

And the cobbler report should contain "Power Management Username :" for "sle_minion" 1s 315ms

And the cobbler report should contain "Power Management Password :" for "sle_minion" 1s 327ms

And the cobbler report should contain "Power Management Type : ipmilan" for "sle_minion" 1s 340ms

Scenario:
Cleanup: tear down the Redfish host
45ms 1

When the controller stops mocking a Redfish host 45ms

Scenario:
Cleanup: remove remaining systems from SSM after Redfish power management tests
64ms 1

When I click on the clear SSM button 64ms

Scenario:
Check for errors in Cobbler monitoring
3s 477ms 1

Then the local logs for Cobbler should not contain errors 3s 477ms

@scope_configuration_channels
Feature:Delete channels with child or clone is not allowed 16s 857ms 9

Using the UI, we cannot delete a channel if it has a child
or a clone created from it

Scenario:
Log in as org admin user
1s 771ms 1

Given I am authorized 1s 771ms

Scenario:
Clone the first channel before deletion from UI test
2s 88ms 8

When I follow the left menu "Software > Manage > Channels" 199ms

And I follow "Clone Channel" 378ms

And I select "Fake-Base-Channel-SUSE-like" as the origin channel 71ms

And I click on "Clone Channel" 475ms

Then I should see a "Create Software Channel" text 77ms

And I should see a "Current state of the channel" text 72ms

When I click on "Clone Channel" 737ms

Then I should see a "Clone of Fake-Base-Channel-SUSE-like" text 74ms

Scenario:
Clone the second channel using first channel as base
1s 904ms 8

When I follow the left menu "Software > Manage > Channels" 80ms

And I follow "Clone Channel" 378ms

And I select "Clone of Fake-Base-Channel-SUSE-like" as the origin channel 47ms

And I click on "Clone Channel" 404ms

Then I should see a "Create Software Channel" text 79ms

And I should see a "Current state of the channel" text 73ms

When I click on "Clone Channel" 766ms

Then I should see a "Clone of Clone of Fake-Base-Channel-SUSE-like" text 74ms

Scenario:
Try to delete channel with clone
1s 654ms 7

When I follow the left menu "Software > Manage > Channels" 76ms

And I follow "Clone of Fake-Base-Channel-SUSE-like" 471ms

And I follow "Delete Channel" 418ms

And I check "unsubscribeSystems" 88ms

And I click on "Delete Channel" 477ms

Then I should see a "Clone of Fake-Base-Channel-SUSE-like" text 61ms

And I should see a "Unable to delete channel" text 60ms

Scenario:
Delete channel without clones neither children
1s 765ms 7

When I follow the left menu "Software > Manage > Channels" 77ms

And I follow "Clone of Clone of Fake-Base-Channel-SUSE-like" 481ms

And I follow "Delete Channel" 390ms

And I check "unsubscribeSystems" 70ms

And I click on "Delete Channel" 560ms

Then I should see a "Clone of Clone of Fake-Base-Channel-SUSE-like" text 91ms

And I should see a "has been deleted" text 93ms

Scenario:
Clone a child channel to the clone of x86_64 test channel
2s 666ms 9

When I follow the left menu "Software > Manage > Channels" 78ms

And I follow "Clone Channel" 376ms

And I select "Fake-RPM-SUSE-Channel" as the origin channel 67ms

And I click on "Clone Channel" 406ms

Then I should see a "Create Software Channel" text 78ms

And I should see a "Current state of the channel" text 75ms

When I select "Clone of Fake-Base-Channel-SUSE-like" from "Parent Channel" 72ms

And I click on "Clone Channel" 1s 434ms

Then I should see a "Clone of Fake-RPM-SUSE-Channel" text 77ms

Scenario:
Try delete channel with child
1s 271ms 8

When I follow the left menu "Software > Manage > Channels" 83ms

And I follow "Clone of Fake-Base-Channel-SUSE-like" 486ms

And I follow "Delete Channel" 392ms

And I check "unsubscribeSystems" 67ms

And I click on "Delete Channel" 52ms

Then I should see a "Clone of Fake-Base-Channel-SUSE-like" text 67ms

And I should see a "channel has child channels associated" text 63ms

And I should see a "must delete those channels first before deleting the parent." text 58ms

Scenario:
Cleanup: remove cloned child channel
1s 898ms 7

When I follow the left menu "Software > Manage > Channels" 80ms

And I follow "Clone of Fake-RPM-SUSE-Channel" 394ms

And I follow "Delete Channel" 396ms

And I check "unsubscribeSystems" 75ms

And I click on "Delete Channel" 830ms

Then I should see a "Clone of Fake-RPM-SUSE-Channel" text 63ms

And I should see a "has been deleted." text 57ms

Scenario:
Cleanup: remove cloned parent channel
1s 835ms 7

When I follow the left menu "Software > Manage > Channels" 80ms

And I follow "Clone of Fake-Base-Channel-SUSE-like" 476ms

And I follow "Delete Channel" 380ms

And I check "unsubscribeSystems" 69ms

And I click on "Delete Channel" 650ms

Then I should see a "Clone of Fake-Base-Channel-SUSE-like" text 91ms

And I should see a "has been deleted." text 86ms

@scope_configuration_channels
Feature:Deleting channels with children or clones is not allowed 9s 838ms 6

Using the tool spacewalk-remove-channel, we cannot delete a channel if it has a child
or a clone created from it

Scenario:
Log in as org admin user
1s 846ms 1

Given I am authorized 1s 846ms

Scenario:
Clone the first channel before deletion from tool test
1s 792ms 8

When I follow the left menu "Software > Manage > Channels" 191ms

And I follow "Clone Channel" 446ms

And I select "Fake-RPM-SUSE-Channel" as the origin channel 57ms

And I click on "Clone Channel" 54ms

Then I should see a "Create Software Channel" text 79ms

And I should see a "Current state of the channel" text 74ms

When I click on "Clone Channel" 809ms

Then I should see a "Clone of Fake-RPM-SUSE-Channel" text 78ms

Scenario:
Clone a second channel using first channel as base
1s 939ms 8

When I follow the left menu "Software > Manage > Channels" 82ms

And I follow "Clone Channel" 395ms

And I select "Clone of Fake-RPM-SUSE-Channel" as the origin channel 73ms

And I click on "Clone Channel" 412ms

Then I should see a "Create Software Channel" text 81ms

And I should see a "Current state of the channel" text 77ms

When I click on "Clone Channel" 738ms

Then I should see a "Clone of Clone of Fake-RPM-SUSE-Channel" text 78ms

Scenario:
Verify if both clone channels exists
1s 348ms 3

When I list channels with spacewalk-remove-channel 1s 348ms

Then I should get "clone-fake-rpm-suse-channel" < 1ms

And I should get "clone-clone-fake-rpm-suse-channel" < 1ms

Scenario:
Delete channel with one clone
945ms 5

When I delete these channels with spacewalk-remove-channel: 945ms
clone-fake-rpm-suse-channel

Then I should get "Error: cannot remove channel" < 1ms

And I should get "clone channel(s) exist" < 1ms

And I should get "clone-fake-rpm-suse-channel" < 1ms

And I should get "clone-clone-fake-rpm-suse-channel" < 1ms

Scenario:
Delete base channel and clone
1s 966ms 4

When I delete these channels with spacewalk-remove-channel: 1s 20ms
clone-fake-rpm-suse-channel
clone-clone-fake-rpm-suse-channel

And I list channels with spacewalk-remove-channel 945ms

Then I shouldn't get "clone-fake-rpm-suse-channel" < 1ms

And I shouldn't get "clone-clone-fake-rpm-suse-channel" < 1ms

@skip_if_github_validation @scope_maintenance_windows @sle_minion @rhlike_minion
Feature:Maintenance windows 58s 51ms 14 1

Scenario:
Log in as org admin user
1s 703ms 1

Given I am authorized 1s 703ms

Scenario:
Create a single calendar
4s 441ms 9

URL: https://uyuni-master-server.sumaci.aws/pub/maintenance-windows-exchange.ics

When I follow the left menu "Schedule > Maintenance Windows > Calendars" 944ms

And I wait for "1" second 1s

Then I should see a "No calendars created" text 56ms

When I click on "Create" in element "maintenance-windows" 82ms

Then I should see a "Calendar Name" text 55ms

When I enter "singlecalendar" as "name" 80ms

And I add "maintenance-windows-exchange.ics" calendar file as url 1s 888ms

And I click on "Create Calendar" 65ms

Then I should see a "Calendar successfully created" text 268ms

Scenario:
Create a multi calendar
3s 585ms 9

URL: https://uyuni-master-server.sumaci.aws/pub/maintenance-windows-multi-exchange-1.ics

When I follow the left menu "Schedule > Maintenance Windows > Calendars" 91ms

And I wait for "1" second 1s

Then I should see a "Items 1 - 1 of 1" text 61ms

When I click on "Create" in element "maintenance-windows" 67ms

Then I should see a "Calendar Name" text 54ms

When I enter "multicalendar" as "name" 68ms

And I add "maintenance-windows-multi-exchange-1.ics" calendar file as url 1s 917ms

And I click on "Create Calendar" 55ms

Then I should see a "Calendar successfully created" text 270ms

Scenario:
Create a single schedule
2s 884ms 11

When I follow the left menu "Schedule > Maintenance Windows > Schedules" 89ms

And I wait for "1" second 1s

Then I should see a "No schedules created" text 56ms

When I click on "Create" in element "maintenance-windows" 70ms

Then I should see a "Schedule Name" text 55ms

When I enter "singleschedule" as "name" 72ms

And I choose "SINGLE" 58ms

And I click on "Add Calendar" 79ms

And I select "singlecalendar" from "calendarSelect" 1s 124ms

And I click on "Create Schedule" 63ms

Then I should see a "Schedule successfully created" text 213ms

Scenario:
Create a multi schedule
2s 841ms 11

When I follow the left menu "Schedule > Maintenance Windows > Schedules" 80ms

And I wait for "1" second 1s

Then I should see a "Items 1 - 1 of 1" text 59ms

When I click on "Create" in element "maintenance-windows" 66ms

Then I should see a "Schedule Name" text 61ms

When I enter "SAP Maintenance Window" as "name" 89ms

And I choose "MULTI" 58ms

And I click on "Add Calendar" 57ms

And I select "multicalendar" from "calendarSelect" 1s 120ms

And I click on "Create Schedule" 62ms

Then I should see a "Schedule successfully created" text 183ms

Scenario:
Create another multi schedule
2s 758ms 10

When I follow the left menu "Schedule > Maintenance Windows > Schedules" 94ms

And I wait for "1" second 1s

Then I should see a "Items 1 - 2 of 2" text 63ms

When I click on "Create" 60ms

And I enter "Core Server Window" as "name" 79ms

And I choose "MULTI" 53ms

And I click on "Add Calendar" 66ms

And I select "multicalendar" from "calendarSelect" 1s 106ms

And I click on "Create Schedule" 56ms

Then I should see a "Schedule successfully created" text 178ms

Scenario:
Assign a single system to the single schedule
2s 286ms 5

Given I am on the Systems overview page of this "sle_minion" 997ms

When I follow "Properties" in the content area 78ms

And I select "singleschedule" from "maintenance-schedule" 68ms

And I click on "Update Properties" 1s 59ms

Then I should see a "System properties changed" text 82ms

Scenario:
Assign systems to the multi schedule using SSM
4s 369ms 10

When I follow the left menu "Systems > System List > All" 149ms

And I click on the clear SSM button 62ms

And I check the "rhlike_minion" client 1s 997ms

And I follow the left menu "Systems > System Set Manager > Overview" 516ms

And I follow "Assign" in the content area 83ms

And I select "SAP Maintenance Window" from "scheduleId" 1s 139ms

And I check "cancelActions" 95ms

And I click on "Assign All" 76ms

And I click on "Confirm" 70ms

Then I should see a "Maintenance schedule has been assigned" text 177ms

@susemanager
Scenario:
Schedule channel change action
< 1ms 13

Given I am on the Systems overview page of this "sle_minion" 0s

When I follow "Software" in the content area 0s

And I follow "Software Channels" in the content area 0s

And I wait until I do not see "Loading..." text 0s

Then radio button "SLE-Product-SLES15-SP7-Pool for x86_64" should be checked 0s

When I wait until I do not see "Loading..." text 0s

Then I should see "SLE15-SP7-Installer-Updates for x86_64" as unchecked 0s

When I check "SLE15-SP7-Installer-Updates for x86_64" 0s

And I click on "Next" 0s

Then I should see a "Confirm Software Channel Change" text 0s

When I pick "17:30" as time 0s

And I click on "Confirm" 0s

Then I should see a "Changing the channels has been scheduled." text 0s

Scenario:
Remove a package and update package list
21s 348ms 3

When I remove package "virgo-dummy" from this "rhlike_minion" without error control 1s 565ms

And I refresh packages list via spacecmd on "rhlike_minion" 2s 702ms

And I wait until refresh package list on "rhlike_minion" is finished 17s 80ms

Scenario:
Schedule package installation action
4s 744ms 10

Given I am on the Systems overview page of this "rhlike_minion" 1s 68ms

When I follow "Software" in the content area 80ms

And I follow "Install" 584ms

And I enter "virgo-dummy" as the filtered package name 56ms

And I click on the filter button 643ms

And I check "virgo-dummy" in the list 64ms

And I click on "Install Packages" 1s 261ms

And I select the next maintenance window 22ms

And I click on "Confirm" 900ms

Then I should see a "1 package install has been scheduled for" text 62ms

Scenario:
Detach systems from schedules
2s 564ms 8

When I follow the left menu "Systems > System List > All" 121ms

And I click on the clear SSM button 54ms

And I check the "sle_minion" client 415ms

And I follow the left menu "Systems > System Set Manager > Overview" 513ms

And I follow "Assign" in the content area 66ms

And I select "None - clear schedule" from "scheduleId" 1s 143ms

And I click on "Clear All" 69ms

Then I should see a "Maintenance schedule has been cleared" text 179ms

Scenario:
Cleanup: cancel all scheduled actions
1s 202ms 1

- Try to cancel "Package Install/Upgrade scheduled by srv_maintenance_windows" action
- Removed "Package Install/Upgrade scheduled by srv_maintenance_windows" action

When I cancel all scheduled actions via API 1s 202ms

Scenario:
Delete maintenance schedules
2s 139ms 13

When I follow the left menu "Schedule > Maintenance Windows > Schedules" 537ms

And I click the "Core Server Window" item delete button 337ms

Then I should see a "Delete maintenance schedule" text 67ms

When I click on the red confirmation button 69ms

And I wait until I see "Schedule 'Core Server Window' has been deleted." text 187ms

And I click the "SAP Maintenance Window" item delete button 167ms

Then I should see a "Delete maintenance schedule" text 64ms

When I click on the red confirmation button 60ms

And I wait until I see "Schedule 'SAP Maintenance Window' has been deleted." text 177ms

And I click the "singleschedule" item delete button 136ms

Then I should see a "Delete maintenance schedule" text 67ms

When I click on the red confirmation button 64ms

And I wait until I see "singleschedule' has been deleted." text 201ms

Scenario:
Delete maintenance calendars
1s 180ms 9

When I follow the left menu "Schedule > Maintenance Windows > Calendars" 81ms

And I click the "singlecalendar" item delete button 197ms

Then I should see a "Delete maintenance calendar" text 78ms

When I click on the red confirmation button 63ms

And I wait until I see "Calendar 'singlecalendar' has been deleted." text 180ms

And I click the "multicalendar" item delete button 155ms

Then I should see a "Delete maintenance calendar" text 65ms

When I click on the red confirmation button 61ms

And I wait until I see "Calendar 'multicalendar' has been deleted." text 295ms

@flaky @scope_visualization @scope_salt
Feature:Create organizations, users, groups, and activation keys using Salt states 38s 799ms 13 2

Scenario:
Log in as org admin user
2s 27ms 1

Given I am authorized 2s 27ms

@skip_if_containerized_server
Scenario:
Apply configuration salt state to server
< 1ms 1

When I manually install the "uyuni-config" formula on the server 0s

Scenario:
Apply setup_users_configuration state to server
14s 98ms 1

When I apply "setup_users_configuration" local salt state on "server" 14s 98ms

Scenario:
Organization my_org was correctly created
2s 152ms 5

Given I am authorized as "my_org_user" with password "my_org_user" 1s 943ms

When I follow the left menu "Home > My Organization" 72ms

Then I should see a "my_org" text in the content area 28ms

When I follow the left menu "Home > My Organization > Organization Trusts" 80ms

Then I should see a "my_org2" text in the content area 27ms

Scenario:
Organization my_org2 was correctly created
1s 984ms 5

Given I am authorized as "my_org_user2" with password "my_org_user2" 1s 777ms

When I follow the left menu "Home > My Organization" 69ms

Then I should see a "my_org2" text in the content area 25ms

When I follow the left menu "Home > My Organization > Organization Trusts" 70ms

Then I should see a "my_org" text in the content area 41ms

Scenario:
Group was correctly created
2s 268ms 5

Given I am authorized for the "Admin" section 1s 618ms

When I follow the left menu "Systems > System Groups" 126ms

When I follow "minions_group" 393ms

Then I should see a "minions_group" text 65ms

And I should see a "System Group Status" text 64ms

Scenario:
User was correctly created
2s 95ms 5

Given I am authorized as "user2" with password "user2" 1s 481ms

When I follow the left menu "Systems > System Groups" 115ms

And I follow "minions_group" 378ms

Then I should see a "minions_group" text 61ms

And I should see a "System Group Status" text 58ms

Scenario:
User channels permissions were assigned
3s 371ms 5

Given I am authorized as "user2" with password "user2" 419ms

When I follow the left menu "Software > Channel List > All" 228ms

And I follow "Show All Child Channels" 84ms

And I follow "Fake-RPM-SUSE-Channel" 415ms

And I follow "Managers" 2s 224ms

Scenario:
User Roles were assigned
2s 62ms 9

Given I am authorized for the "Admin" section 1s 360ms

When I follow the left menu "Users > User List > Active" 194ms

And I follow "user2" 320ms

Then I should see a "User Details" text 77ms

And I should see "role_activation_key_admin" as checked 24ms

And I should see "role_image_admin" as unchecked 21ms

And I should see "role_config_admin" as checked 22ms

And I should see "role_channel_admin" as unchecked 20ms

And I should see "role_system_group_admin" as unchecked 20ms

Scenario:
Activation Key was correctly created
528ms 6

When I follow the left menu "Systems > Activation Keys" 118ms

And I follow "My Activation Key created via Salt" 268ms

Then I should see "10" in field identified by "usageLimit" 24ms

And I should see "virtualization_host" as checked 20ms

And I should see a "Push via SSH" text 73ms

And I should see "enable-config-auto-deploy" as checked 23ms

Scenario:
Cleanup: apply configuration teardown salt state to server
7s 501ms 1

When I apply "teardown_users_configuration" local salt state on "server" 7s 501ms

@skip_if_containerized_server
Scenario:
Cleanup: uninstall the uyuni-config formula from the server
< 1ms 1

And I manually uninstall the "uyuni-config" formula from the server 0s

Scenario:
Cleanup: all organizations were successfully removed
261ms 3

When I follow the left menu "Admin > Organizations" 137ms

Then I should not see a "my_org" text 64ms

And I should not see a "my_org2" text 59ms

Scenario:
Cleanup: user was successfully removed
256ms 2

When I follow the left menu "Users > User List > Active" 159ms

Then I should not see a "user2" text 96ms

Scenario:
Cleanup: activation key was successfully removed
189ms 2

When I follow the left menu "Systems > Activation Keys" 111ms

Then I should not see a "My Activation Key created via Salt" text 78ms

@flaky
Feature:Export and import software channels with new ISS implementation 44s 10

Distribute software between servers
Run export and import with ISS v2

Scenario:
Install inter server sync package
2s 728ms 2

When I install packages "inter-server-sync" on this "server" 2s 90ms

Then "inter-server-sync" should be installed on "server" 637ms

Scenario:
Log in as org admin user
1s 659ms 1

Given I am authorized 1s 659ms

Scenario:
Clone a channel with patches
2s 111ms 9

When I follow the left menu "Software > Manage > Channels" 211ms

And I follow "Clone Channel" 375ms

And I select "Fake-RPM-SUSE-Channel" as the origin channel 85ms

And I choose "current" 60ms

And I click on "Clone Channel" 426ms

And I should see a "Create Software Channel" text 82ms

And I should see a "Current state of the channel" text 74ms

And I click on "Clone Channel" 715ms

Then I should see a "Clone of Fake-RPM-SUSE-Channel" text 78ms

Scenario:
Check that this channel has patches
1s 248ms 8

When I follow the left menu "Software > Manage > Channels" 83ms

And I follow "Clone of Fake-RPM-SUSE-Channel" 487ms

And I follow "Patches" in the content area 73ms

And I follow "List/Remove Patches" 560ms

Then I should see a "CL-hoag-dummy-7890" link 12ms

And I should see a "CL-virgo-dummy-3456" link 10ms

And I should see a "CL-milkyway-dummy-2345" link 10ms

And I should see a "CL-andromeda-dummy-6789" link 10ms

Scenario:
Export data with ISS v2
16s 879ms 3

When I ensure folder "/tmp/export_iss_v2" doesn't exist on "server" 679ms

When I export software channels "clone-fake-rpm-suse-channel" with ISS v2 to "/tmp/export_iss_v2" 15s 543ms

Then "/tmp/export_iss_v2" folder on server is ISS v2 export directory 656ms

Scenario:
Cleanup: remove cloned channels
1s 832ms 6

When I follow the left menu "Software > Manage > Channels" 69ms

And I follow "Clone of Fake-RPM-SUSE-Channel" 480ms

And I follow "Delete Channel" 387ms

And I check "unsubscribeSystems" 96ms

And I click on "Delete Channel" 734ms

Then I should see a "Clone of Fake-RPM-SUSE-Channel" text 63ms

Scenario:
Import data with ISS v2
13s 128ms 1

When I import data with ISS v2 from "/tmp/export_iss_v2" 13s 128ms

Scenario:
Check that this channel was imported and has patches
1s 217ms 8

When I follow the left menu "Software > Manage > Channels" 80ms

And I follow "Clone of Fake-RPM-SUSE-Channel" 467ms

And I follow "Patches" in the content area 65ms

And I follow "List/Remove Patches" 572ms

Then I should see a "CL-hoag-dummy-7890" link 8ms

And I should see a "CL-virgo-dummy-3456" link 7ms

And I should see a "CL-milkyway-dummy-2345" link 7ms

And I should see a "CL-andromeda-dummy-6789" link 7ms

Scenario:
Cleanup: remove imported channel
1s 777ms 6

When I follow the left menu "Software > Manage > Channels" 72ms

When I follow "Clone of Fake-RPM-SUSE-Channel" 463ms

And I follow "Delete Channel" 331ms

And I check "unsubscribeSystems" 68ms

And I click on "Delete Channel" 776ms

Then I should see a "Clone of Fake-RPM-SUSE-Channel" text 65ms

Scenario:
Cleanup: remove ISS v2 export folder
1s 417ms 1

When I ensure folder "/tmp/export_iss_v2" doesn't exist on "server" 1s 417ms

Feature:Export and import configuration channels with new ISS implementation 24s 203ms 10

Distribute configuration between servers
Run export and import with ISS v2

Scenario:
Install inter server sync package
1s 517ms 2

When I install packages "inter-server-sync" on this "server" 877ms

Then "inter-server-sync" should be installed on "server" 640ms

Scenario:
Log in as org admin user
1s 836ms 1

Given I am authorized 1s 836ms

Scenario:
Create a configuration channel
1s 488ms 7

When I follow the left menu "Configuration > Channels" 125ms

And I follow "Create Config Channel" 328ms

And I enter "Test Config Channel" as "cofName" 78ms

And I enter "testconfigchannel" as "cofLabel" 67ms

And I enter "This is a test configuration channel" as "cofDescription" 87ms

And I click on "Create Config Channel" 736ms

Then I should see a "Test Config Channel" text 64ms

Scenario:
Add a configuration file to the test configuration channel
2s 555ms 9

When I follow the left menu "Configuration > Channels" 68ms

And I follow "Test Config Channel" 447ms

And I follow "Create Configuration File or Directory" 403ms

And I enter "/etc/s-mgr/config" as "cffPath" 73ms

And I enter "COLOR=white" in the editor 5ms

And I click on "Create Configuration File" 74ms

Then I should see a "Revision 1 of /etc/s-mgr/config from channel Test Config Channel" text 100ms

And file "/srv/susemanager/salt/manager_org_1/testconfigchannel/init.sls" should exist on server 708ms

And file "/srv/susemanager/salt/manager_org_1/testconfigchannel/etc/s-mgr/config" should exist on server 672ms

Scenario:
Export data with ISS v2
7s 100ms 3

When I ensure folder "/tmp/export_iss_v2" doesn't exist on "server" 691ms

When I export config channels "testconfigchannel" with ISS v2 to "/tmp/export_iss_v2" 5s 707ms

Then "/tmp/export_iss_v2" folder on server is ISS v2 export directory 701ms

Scenario:
Cleanup: remove the test configuration channel
2s 267ms 6

When I follow the left menu "Configuration > Channels" 63ms

And I follow "Test Config Channel" 492ms

And I follow "Delete Channel" 352ms

And I click on "Delete Config Channel" 612ms

Then file "/srv/susemanager/salt/manager_org_1/testconfigchannel/init.sls" should not exist on server 737ms

And I should not see a "Test Config Channel" link 8ms

Scenario:
Import data with ISS v2
2s 870ms 1

When I import data with ISS v2 from "/tmp/export_iss_v2" 2s 870ms

Scenario:
Check that the config channel was imported
1s 457ms 4

When I follow the left menu "Configuration > Channels" 63ms

Then I should see a "Test Config Channel" link 8ms

And file "/srv/susemanager/salt/manager_org_1/testconfigchannel/init.sls" should exist on server 719ms

And file "/srv/susemanager/salt/manager_org_1/testconfigchannel/etc/s-mgr/config" should exist on server 665ms

Scenario:
Cleanup: remove the test configuration channel
1s 719ms 6

When I follow the left menu "Configuration > Channels" 59ms

And I follow "Test Config Channel" 483ms

And I follow "Delete Channel" 343ms

And I click on "Delete Config Channel" 56ms

Then file "/srv/susemanager/salt/manager_org_1/testconfigchannel/init.sls" should not exist on server 771ms

And I should not see a "Test Config Channel" link 5ms

Scenario:
Cleanup: remove ISS v2 export folder
1s 391ms 1

When I ensure folder "/tmp/export_iss_v2" doesn't exist on "server" 1s 391ms

@skip_if_github_validation @sle_minion @scope_salt @new_issue @flaky
Feature:Salt master integration with Git pillar 56s 815ms 6

Scenario:
Pre-requisite: Enabling repositories for installing git-core
1s 491ms 2

When I add repository "SLE-Module-Basesystem15-SP7-Updates" with url "http://minima-mirror-ci-bv.mgr.suse.de/SUSE/Updates/SLE-Module-Basesystem/15-SP7/x86_64/update/" on "server" without error control 738ms

And I add repository "SLE-Module-Basesystem15-SP7-Pool" with url "http://minima-mirror-ci-bv.mgr.suse.de/SUSE/Products/SLE-Module-Basesystem/15-SP7/x86_64/product/" on "server" without error control 753ms

Scenario:
Preparing Git pillar configuration for Salt master
19s 489ms 3

When I setup a git_pillar environment on the Salt master 5s 805ms

And I wait until Salt master can reach "sle_minion" 12s 928ms

Then file "/etc/salt/master.d/zz-testing-gitpillar.conf" should exist on server 755ms

Scenario:
Check for the expected pillar data after enabling Git pillar
11s 378ms 5

When I refresh the pillar data 2s 417ms

And I wait until there is no pillar refresh salt job active 2s 988ms

Then the pillar data for "org_id" should be "1" on "sle_minion" 1s 568ms

And the pillar data for "git_pillar_foobar" should be "12345" on "sle_minion" 1s 549ms

And the pillar data for "git_pillar_foobar" should be "12345" on the Salt master 2s 854ms

Scenario:
Cleanup: Remove Git pillar configuration for Salt master
15s 211ms 3

When I clean up the git_pillar environment on the Salt master 1s 858ms

And I wait until Salt master can reach "sle_minion" 12s 605ms

Then file "/etc/salt/master.d/zz-testing-gitpillar.conf" should not exist on server 747ms

Scenario:
Cleanup: Check for the expected pillar data after disabling Git pillar
7s 937ms 4

When I refresh the pillar data 2s 144ms

Then the pillar data for "git_pillar_foobar" should be empty on "sle_minion" 1s 551ms

And the pillar data for "org_id" should be "1" on "sle_minion" 1s 552ms

And the pillar data for "git_pillar_foobar" should be empty on the Salt master 2s 688ms

Scenario:
Pre-Cleanup: Disabling repositories for uninstalling git-core
1s 306ms 2

When I remove repository "SLE-Module-Basesystem15-SP7-Updates" on "server" without error control 650ms

And I remove repository "SLE-Module-Basesystem15-SP7-Pool" on "server" without error control 656ms

@skip_if_github_validation @skip_if_cloud @build_host @scope_retail @scope_building_container_images @scc_credentials
Feature:Build OS images < 1ms 9

Scenario:
Log in as org admin user
< 1ms 1

Given I am authorized 0s

Scenario:
Create an OS image profile with activation key
< 1ms 8

When I follow the left menu "Images > Profiles" 0s

And I follow "Create" 0s

And I enter "suse_os_image" as "label" 0s

And I select "Kiwi" from "imageType" 0s

And I select "1-TERMINAL-KEY-x86_64" from "activationKey" 0s

And I enter the image filename for "pxeboot_minion" relative to profiles as "path" 0s

And I click on "create-btn" 0s

And I wait until no Salt job is running on "build_host" 0s

Scenario:
Login as Kiwi image administrator and build an image
< 1ms 5

Given I am authorized for the "Images" section 0s

When I follow the left menu "Images > Build" 0s

And I select "suse_os_image" from "profileId" 0s

And I select the hostname of "build_host" from "buildHostId" 0s

And I click on "submit-btn" 0s

Scenario:
Log in as admin user
< 1ms 1

Given I am authorized for the "Admin" section 0s

Scenario:
Wait for the built OS image
< 1ms 7

Given I am on the Systems overview page of this "build_host" 0s

Then I should see a "[OS Image Build Host]" text 0s

When I wait until the image build "suse_os_image" is completed 0s

And I wait until the image inspection for "pxeboot_minion" is completed 0s

And I wait until no Salt job is running on "build_host" 0s

And I follow the left menu "Images > Image List" 0s

Then I should see the image for "pxeboot_minion" is built 0s

Scenario:
Check the built OS image
< 1ms 2

When I open the details page of the image for "pxeboot_minion" 0s

Then I should see a link to download the image for "pxeboot_minion" 0s

Scenario:
Cleanup: remove remaining systems from SSM after OS image tests
< 1ms 2

When I go to the home page 0s

And I click on the clear SSM button 0s

Scenario:
Cleanup: remove OS image profile
< 1ms 6

When I follow the left menu "Images > Profiles" 0s

And I check "suse_os_image" in the list 0s

And I click on "Delete" 0s

And I should see a "Are you sure you want to delete the selected profile?" text 0s

And I click on the red confirmation button 0s

And I wait until I see "Image profile has been deleted" text 0s

Scenario:
Cleanup: Make sure no job is left running on buildhost
< 1ms 1

When I wait until no Salt job is running on "build_host" 0s

@skip_if_github_validation @scope_onboarding
Feature:Reboot systems managed by Uyuni 16m 89ms 5

Scenario:
Log in as org admin user
1s 787ms 1

Given I am authorized 1s 787ms

@ssh_minion
Scenario:
Reboot the SSH-managed SLES minion
3m 56s 116ms 6

Given I am on the Systems overview page of this "ssh_minion" 4s 983ms

When I follow first "Schedule System Reboot" 568ms

Then I should see a "System Reboot Confirmation" text 69ms

And I should see a "Reboot system" button 17ms

When I click on "Reboot system" 921ms

Then I wait and check that "ssh_minion" has rebooted 3m 49s 556ms

Scenario:
Schedule a reboot on a SLES Salt minion
4m 15s 830ms 8

2026-03-06 12:21:53 +0100 Still waiting for action to complete...

Given I am on the Systems overview page of this "sle_minion" 983ms

When I follow first "Schedule System Reboot" 473ms

Then I should see a "System Reboot Confirmation" text 71ms

And I should see a "Reboot system" button 14ms

And I click on "Reboot system" 862ms

Then I should see a "Reboot scheduled for system" text 88ms

When I wait at most 600 seconds until event "System reboot scheduled" is completed 4m 13s 277ms

And I should see a "Reboot completed." text 59ms

@rhlike_minion
Scenario:
Reboot the Red Hat-like minion and wait until reboot is completed
3m 59s 474ms 8

2026-03-06 12:26:09 +0100 Still waiting for action to complete...

Given I am on the Systems overview page of this "rhlike_minion" 1s 4ms

When I follow first "Schedule System Reboot" 484ms

Then I should see a "System Reboot Confirmation" text 69ms

And I should see a "Reboot system" button 20ms

When I click on "Reboot system" 880ms

Then I should see a "Reboot scheduled for system" text 85ms

When I wait at most 600 seconds until event "System reboot scheduled" is completed 3m 56s 872ms

Then I should see a "Reboot completed." text 56ms

@deblike_minion
Scenario:
Reboot the Debian-like minion and wait until reboot is completed
3m 46s 880ms 8

2026-03-06 12:30:13 +0100 Still waiting for action to complete...

Given I am on the Systems overview page of this "deblike_minion" 5s 167ms

When I follow first "Schedule System Reboot" 486ms

Then I should see a "System Reboot Confirmation" text 74ms

And I should see a "Reboot system" button 19ms

When I click on "Reboot system" 891ms

Then I should see a "Reboot scheduled for system" text 86ms

When I wait at most 600 seconds until event "System reboot scheduled" is completed 3m 40s 94ms

Then I should see a "Reboot completed." text 58ms

@skip_if_github_validation @sle_minion @scope_cve_audit
Feature:CVE Audit on SLE Salt Minions 1m 42s 296ms 12

In order to check if systems are patched against certain vulnerabilities
As an authorized user
I want to see the Salt Minions that need to be patched

Scenario:
Log in as admin user
2s 199ms 1

Given I am authorized for the "Admin" section 2s 199ms

Scenario:
Pre-requisite: downgrade milkyway-dummy to lower version
39s 910ms 9

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 969ms

And I install old package "milkyway-dummy-1.0" on this "sle_minion" 1s 764ms

And I refresh the metadata for "sle_minion" 850ms

And I follow the left menu "Admin > Task Schedules" 136ms

And I follow "errata-cache-default" 1s 214ms

And I follow "errata-cache-bunch" 1s 277ms

And I click on "Single Run Schedule" 1s 556ms

Then I should see a "bunch was scheduled" text 269ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 31s 871ms

Scenario:
Schedule channel data refresh
4s 200ms 6

When I follow the left menu "Admin > Task Schedules" 94ms

And I follow "cve-server-channels-default" 1s 208ms

And I follow "cve-server-channels-bunch" 1s 225ms

And I click on "Single Run Schedule" 348ms

Then I should see a "bunch was scheduled" text 59ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 1s 263ms

Scenario:
Display CVE audit page
225ms 3

When I follow the left menu "Audit > CVE Audit" 126ms

Then I should see a "CVE Audit" link in the left menu 24ms

And I should see a "CVE Audit" text 74ms

Scenario:
Search for a known CVE number
21s 459ms 14

When I follow the left menu "Audit > CVE Audit" 59ms

And I select "1999" from "cveIdentifierYear" 70ms

And I enter "9999" as "cveIdentifierId" 69ms

And I click on "Audit Servers" 60ms

Then I should see "sle_minion" as link 777ms

And I should see a "Affected, at least one patch available in an assigned channel" text 95ms

And I should see a "Install a new patch on this system" link 11ms

And I should see a "milkyway-dummy-2345" text 85ms

And I should see a "Download CSV" link 11ms

And I should see a "Status" button 17ms

And I should see a "Name" button 16ms

And I should see a "extra CVE data update" link 10ms

Then I follow "Install a new patch on this system" on "sle_minion" row 20s 90ms

And I should see a "Relevant Patches" text 84ms

Scenario:
Search for an unknown CVE number
497ms 5

When I follow the left menu "Audit > CVE Audit" 115ms

And I select "2012" from "cveIdentifierYear" 63ms

And I enter "2806" as "cveIdentifierId" 60ms

And I click on "Audit Servers" 58ms

Then I should see a "The specified CVE number was not found" text 199ms

Scenario:
Select a system for the System Set Manager
1s 988ms 11

And I click on the clear SSM button 65ms

And I follow the left menu "Audit > CVE Audit" 65ms

And I select "1999" from "cveIdentifierYear" 64ms

And I enter "9999" as "cveIdentifierId" 57ms

And I click on "Audit Servers" 57ms

Then I should see a "Affected, at least one patch available in an assigned channel" text 75ms

When I check the "sle_minion" client 680ms

Then I should see a "system selected" text 224ms

When I follow the left menu "Systems > System List > All" 200ms

Then I should see "sle_minion" as link 445ms

And I click on the clear SSM button 51ms

Scenario:
List systems by patch status via API before patch
6s 115ms 12

Result list: [{"errata_advisories"=>[], "system_id"=>1000010003, "channel_labels"=>[], "patch_status"=>"NOT_AFFECTED"}, {"errata_advisories"=>[], "system_id"=>1000010002, "channel_labels"=>[], "patch_status"=>"NOT_AFFECTED"}, {"errata_advisories"=>[], "system_id"=>1000010004, "channel_labels"=>[], "patch_status"=>"NOT_AFFECTED"}, {"errata_advisories"=>[], "system_id"=>1000010005, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}, {"errata_advisories"=>[], "system_id"=>1000010000, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}, {"errata_advisories"=>[], "system_id"=>1000010001, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}]
Result list: [{"errata_advisories"=>["milkyway-dummy-2345"], "system_id"=>1000010002, "channel_labels"=>["fake-base-channel-rh-like"], "patch_status"=>"AFFECTED_FULL_PATCH_APPLICABLE"}, {"errata_advisories"=>["milkyway-dummy-2345"], "system_id"=>1000010004, "channel_labels"=>["fake-rpm-suse-channel"], "patch_status"=>"AFFECTED_FULL_PATCH_APPLICABLE"}, {"errata_advisories"=>[], "system_id"=>1000010003, "channel_labels"=>[], "patch_status"=>"NOT_AFFECTED"}, {"errata_advisories"=>[], "system_id"=>1000010005, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}, {"errata_advisories"=>[], "system_id"=>1000010000, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}, {"errata_advisories"=>[], "system_id"=>1000010001, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}]
result: {"errata_advisories"=>["milkyway-dummy-2345"], "system_id"=>1000010004, "channel_labels"=>["fake-rpm-suse-channel"], "patch_status"=>"AFFECTED_FULL_PATCH_APPLICABLE"}

When I follow the left menu "Admin > Task Schedules" 131ms

And I follow "cve-server-channels-default" 1s 349ms

And I follow "cve-server-channels-bunch" 1s 167ms

And I click on "Single Run Schedule" 309ms

Then I should see a "bunch was scheduled" text 65ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 324ms

When I call audit.list_systems_by_patch_status() with CVE identifier "CVE-1999-9979" 1s 22ms

Then I should get status "NOT_AFFECTED" for "sle_minion" 384ms

When I call audit.list_systems_by_patch_status() with CVE identifier "CVE-1999-9999" 990ms

Then I should get status "AFFECTED_FULL_PATCH_APPLICABLE" for "sle_minion" 367ms

And I should get the "fake-rpm-suse-channel" channel label < 1ms

And I should get the "milkyway-dummy-2345" patch < 1ms

Scenario:
Apply patches
22s 126ms 10

Given I am on the Systems overview page of this "sle_minion" 980ms

When I follow "Software" in the content area 76ms

And I follow "Patches" in the content area 65ms

And I enter "milkyway" as the filtered synopsis 54ms

And I click on the filter button 513ms

And I check "milkyway-dummy-2345" in the list 61ms

And I click on "Apply Patches" 614ms

And I click on "Confirm" 772ms

Then I should see a "patch update has been scheduled" text 82ms

And I wait until event "Patch Update: milkyway-dummy-2345" is completed 18s 905ms

Scenario:
List systems by patch status via API after patch
1s 233ms 2

Result list: [{"errata_advisories"=>["milkyway-dummy-2345"], "system_id"=>1000010002, "channel_labels"=>["fake-base-channel-rh-like"], "patch_status"=>"AFFECTED_FULL_PATCH_APPLICABLE"}, {"errata_advisories"=>[], "system_id"=>1000010003, "channel_labels"=>[], "patch_status"=>"NOT_AFFECTED"}, {"errata_advisories"=>[], "system_id"=>1000010004, "channel_labels"=>[], "patch_status"=>"PATCHED"}, {"errata_advisories"=>[], "system_id"=>1000010005, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}, {"errata_advisories"=>[], "system_id"=>1000010000, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}, {"errata_advisories"=>[], "system_id"=>1000010001, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}]

And I call audit.list_systems_by_patch_status() with CVE identifier "CVE-1999-9999" 869ms

Then I should get status "PATCHED" for "sle_minion" 364ms

Scenario:
Cleanup: remove installed packages
2s 280ms 2

When I disable repository "test_repo_rpm_pool" on this "sle_minion" without error control 779ms

And I remove package "milkyway-dummy" from this "sle_minion" without error control 1s 500ms

Scenario:
Cleanup: remove remaining systems from SSM after CVE audit tests
59ms 1

When I click on the clear SSM button 59ms

@scope_openscap @scope_res @rhlike_minion
Feature:OpenSCAP audit of Red Hat-like Salt minion 3m 44s 465ms 10

In order to audit a Red Hat-like Salt minion
As an authorized user
I want to run an OpenSCAP scan on it

Scenario:
Log in as admin user
435ms 1

Given I am authorized for the "Admin" section 435ms

@skip_if_github_validation
Scenario:
Enable repositories for openSCAP on the Red Hat-like minion
34s 91ms 2

When I enable the repositories "Rocky-BaseOS Rocky-AppStream" on this "rhlike_minion" 402ms

And I refresh the metadata for "rhlike_minion" 33s 689ms

@skip_if_github_validation
Scenario:
Install the OpenSCAP packages on the Red Hat-like minion
1m 21s 929ms 5

Given I am on the Systems overview page of this "rhlike_minion" 1s 113ms

And I install OpenSCAP dependencies on "rhlike_minion" 41s 736ms

And I follow "Software" in the content area 77ms

And I click on "Update Package List" 609ms

And I wait until event "Package List Refresh" is completed 38s 393ms

Scenario:
Schedule an OpenSCAP audit job on the Red Hat-like minion
1m 13s 527ms 10

Given I am on the Systems overview page of this "rhlike_minion" 998ms

When I follow "Audit" in the content area 78ms

And I follow "OpenSCAP" in the content area 75ms

And I follow "Schedule" in the content area 65ms

And I wait at most 30 seconds until I do not see "This system does not yet have OpenSCAP scan capability." text, refreshing the page 68ms

And I enter "--profile xccdf_org.ssgproject.content_profile_anssi_bp28_intermediary" as "params" 127ms

And I enter "/usr/share/xml/scap/ssg/content/ssg-rhel8-ds.xml" as "path" 94ms

And I click on "Schedule" 685ms

Then I should see a "XCCDF scan has been scheduled" text 73ms

And I wait at most 500 seconds until event "OpenSCAP xccdf scanning" is completed 1m 11s 260ms

Scenario:
Check the results of the OpenSCAP scan on the Red Hat-like minion
2s 867ms 7

Given I am on the Systems overview page of this "rhlike_minion" 1s 4ms

When I follow "Audit" in the content area 86ms

And I follow "OpenSCAP" in the content area 79ms

And I follow "xccdf_org.open-scap_testresult" 1s 53ms

Then I should see a "Details of XCCDF Scan" text 231ms

And I should see a "RHEL-8" text 205ms

And I should see a "XCCDF Rule Results" text 206ms

Scenario:
Cleanup: remove audit scans retention period from Red Hat-like minion
814ms 6

When I follow the left menu "Admin > Organizations" 133ms

When I follow "SUSE Test" in the content area 70ms

And I follow "Configuration" in the content area 63ms

And I enter "0" as "scap_retention_period" 58ms

And I click on "Update Organization" 422ms

Then I should see a "Organization SUSE Test was successfully updated." text 66ms

Scenario:
Cleanup: delete audit results from Red Hat-like minion
3s 556ms 8

Given I am on the Systems overview page of this "rhlike_minion" 1s 72ms

When I follow "Audit" in the content area 59ms

And I follow "OpenSCAP" in the content area 59ms

And I follow "List Scans" in the content area 72ms

And I click on "Select All" 425ms

And I click on "Remove" 590ms

And I click on "Confirm" 1s 205ms

Then I should see a " SCAP Scan(s) deleted. 0 SCAP Scan(s) retained" text 70ms

Scenario:
Cleanup: restore audit scans retention period on Red Hat-like minion
774ms 6

When I follow the left menu "Admin > Organizations" 103ms

When I follow "SUSE Test" in the content area 62ms

And I follow "Configuration" in the content area 64ms

And I enter "90" as "scap_retention_period" 61ms

And I click on "Update Organization" 55ms

Then I should see a "Organization SUSE Test was successfully updated." text 427ms

@skip_if_github_validation
Scenario:
Cleanup: remove the OpenSCAP packages from the Red Hat-like minion
5s 475ms 2

When I remove OpenSCAP dependencies from "rhlike_minion" 5s 282ms

And I disable repository "Rocky-BaseOS" on this "rhlike_minion" 192ms

@skip_if_github_validation
Scenario:
Cleanup: restore the base channel for the Red Hat-like minion
20s 991ms 11

Warning: Radio button 'Fake-Base-Channel-RH-like' is already checked

Given I am on the Systems overview page of this "rhlike_minion" 957ms

When I follow "Software" in the content area 70ms

And I follow "Software Channels" in the content area 68ms

And I wait until I do not see "Loading..." text 71ms

And I check radio button "Fake-Base-Channel-RH-like" 179ms

And I wait until I do not see "Loading..." text 426ms

And I click on "Next" 63ms

Then I should see a "Confirm Software Channel Change" text 62ms

When I click on "Confirm" 74ms

Then I should see a "Changing the channels has been scheduled." text 297ms

And I wait until event "Subscribe channels scheduled" is completed 18s 719ms

@skip_if_github_validation @scope_res @rhlike_minion @new_issue
Feature:Remote command on the Red Hat-like Salt minion 28s 958ms 2

In order to manage a Red Hat-like Salt minion
As an authorized user
I want to run a remote command on it

Scenario:
Log in as org admin user
2s 82ms 1

Given I am authorized 2s 82ms

Scenario:
Run a remote command on the Red Hat-like minion
26s 875ms 11

When I follow the left menu "Salt > Remote Commands" 127ms

Then I should see a "Remote Commands" text in the content area 21ms

When I enter command "cat /etc/os-release" 88ms

And I enter target "rhlike_minion" 115ms

And I click on preview 11s 257ms

And I click on run 48ms

Then I should see "rhlike_minion" hostname 52ms

When I wait for "15" seconds 15s

And I expand the results for "rhlike_minion" 53ms

Then I should see a "rhel centos fedora" text 57ms

And I should see a "ROCKY_SUPPORT_PRODUCT" text 52ms

@skip_if_github_validation @scope_res @rhlike_minion
Feature:Bootstrap a SSH-managed Red Hat-like minion and do some basic operations on it 12m 59s 400ms 12

Scenario:
Log in as org admin user
1s 974ms 1

Given I am authorized 1s 974ms

Scenario:
Delete the Red Hat-like minion before SSH minion tests
4m 6s 998ms 7

When I am on the Systems overview page of this "rhlike_minion" 1s 671ms

And I follow "Delete System" 470ms

Then I should see a "Confirm System Profile Deletion" text 60ms

When I click on "Delete Profile" 63ms

And I wait until I see "has been deleted" text 4m 4s 10ms

And I wait until Salt client is inactive on "rhlike_minion" 329ms

Then "rhlike_minion" should not be registered 392ms

Scenario:
Bootstrap a SSH-managed Red Hat-like minion
2m 28s 372ms 11

The hostname of rhlike_minion is uyuni-master-rhlike-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 79ms

Then I should see a "Bootstrap Minions" text 62ms

When I check "manageWithSSH" 91ms

And I enter the hostname of "rhlike_minion" as "hostname" 139ms

And I enter "linux" as "password" 62ms

And I select the hostname of "proxy" from "proxies" if present 2s 854ms

And I click on "Bootstrap" 63ms

And I wait at most 480 seconds until I see "Bootstrap process initiated." text 49s 833ms

And I follow the left menu "Systems > System List > All" 140ms

And I wait until I see the name of "rhlike_minion", refreshing the page 17s 139ms

And I wait until onboarding is completed for "rhlike_minion" 1m 17s 905ms

@proxy
Scenario:
Check connection from SSH-managed Red Hat-like minion to proxy
1s 315ms 4

Given I am on the Systems overview page of this "rhlike_minion" 1s 83ms

When I follow "Details" in the content area 77ms

And I follow "Connection" in the content area 83ms

Then I should see "proxy" short hostname 71ms

@proxy
Scenario:
Check registration on proxy of SSH-managed Red Hat-like minion
1s 253ms 4

Given I am on the Systems overview page of this "proxy" 1s 29ms

When I follow "Details" in the content area 61ms

And I follow "Proxy" in the content area 67ms

Then I should see "rhlike_minion" hostname 95ms

Scenario:
Subscribe the SSH-managed Red Hat-like minion to a base channel
1m 7s 817ms 11

Given I am on the Systems overview page of this "rhlike_minion" 1s 26ms

When I follow "Software" in the content area 76ms

And I follow "Software Channels" in the content area 73ms

And I wait until I do not see "Loading..." text 66ms

And I check radio button "Fake-Base-Channel-RH-like" 10s 74ms

And I wait until I do not see "Loading..." text 417ms

And I click on "Next" 64ms

Then I should see a "Confirm Software Channel Change" text 60ms

When I click on "Confirm" 77ms

Then I should see a "Changing the channels has been scheduled." text 305ms

And I wait until event "Subscribe channels scheduled" is completed 55s 572ms

Scenario:
Check events history for failures on SSH-managed Red Hat-like minion
1m 2s 53ms 2

Given I am on the Systems overview page of this "rhlike_minion" 1s 56ms

Then I check for failed events on history event page 1m 996ms

Scenario:
Run a remote command on the SSH-managed Red Hat-like minion
29s 845ms 11

When I follow the left menu "Salt > Remote Commands" 129ms

Then I should see a "Remote Commands" text in the content area 21ms

When I enter command "cat /etc/os-release" 96ms

And I enter target "rhlike_minion" 108ms

And I click on preview 14s 219ms

And I click on run 48ms

Then I should see "rhlike_minion" hostname 60ms

When I wait for "15" seconds 15s

And I expand the results for "rhlike_minion" 51ms

Then I should see a "rhel centos fedora" text 54ms

And I should see a "ROCKY_SUPPORT_PRODUCT" text 55ms

Scenario:
Check events history for failures on SSH-managed Red Hat-like minion
1m 12s 6ms 2

Given I am on the Systems overview page of this "rhlike_minion" 1s 14ms

Then I check for failed events on history event page 1m 10s 991ms

Scenario:
Cleanup: delete the SSH-managed Red Hat-like minion
14s 861ms 6

When I am on the Systems overview page of this "rhlike_minion" 1s 95ms

And I follow "Delete System" 455ms

Then I should see a "Confirm System Profile Deletion" text 62ms

When I click on "Delete Profile" 62ms

And I wait until I see "has been deleted" text 12s 749ms

Then "rhlike_minion" should not be registered 434ms

Scenario:
Cleanup: bootstrap a Red Hat-like minion after SSH minion tests
1m 41s 422ms 12

The hostname of rhlike_minion is uyuni-master-rhlike-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 82ms

Then I should see a "Bootstrap Minions" text 62ms

When I enter the hostname of "rhlike_minion" as "hostname" 147ms

And I enter "22" as "port" 52ms

And I enter "root" as "user" 59ms

And I enter "linux" as "password" 61ms

And I select the hostname of "proxy" from "proxies" if present 74ms

And I click on "Bootstrap" 61ms

And I wait at most 480 seconds until I see "Bootstrap process initiated." text 20s 786ms

And I follow the left menu "Systems > System List > All" 140ms

And I wait until I see the name of "rhlike_minion", refreshing the page 1m 11s 538ms

And I wait until onboarding is completed for "rhlike_minion" 8s 354ms

Scenario:
Cleanup: re-subscribe the Red Hat-like minion to a base channel
31s 479ms 11

Given I am on the Systems overview page of this "rhlike_minion" 1s 45ms

When I follow "Software" in the content area 74ms

And I follow "Software Channels" in the content area 68ms

And I wait until I do not see "Loading..." text 68ms

And I check radio button "Fake-Base-Channel-RH-like" 10s 70ms

And I wait until I do not see "Loading..." text 409ms

And I click on "Next" 68ms

Then I should see a "Confirm Software Channel Change" text 57ms

When I click on "Confirm" 77ms

Then I should see a "Changing the channels has been scheduled." text 377ms

And I wait until event "Subscribe channels scheduled" is completed 19s 161ms

@skip_if_github_validation @scope_deblike @deblike_minion
Feature:Remote command on Debian-like Salt minion 15s 247ms 2

In order to manage a Debian-like Salt minion
As an authorized user
I want to run a remote command on it

Scenario:
Log in as org admin user
1s 694ms 1

Given I am authorized 1s 694ms

Scenario:
Run a remote command on the Debian-like minion
13s 553ms 10

When I follow the left menu "Salt > Remote Commands" 125ms

Then I should see a "Remote Commands" text in the content area 21ms

When I enter command "cat /etc/os-release" 88ms

And I enter target "deblike_minion" 92ms

And I click on preview 11s 387ms

And I click on run 47ms

Then I should see "deblike_minion" hostname 55ms

When I wait until I see "show response" text 1s 629ms

And I expand the results for "deblike_minion" 51ms

Then I should see a "ID=ubuntu" text 54ms

@skip_if_github_validation @scope_deblike @scope_salt_ssh @deblike_minion
Feature:Bootstrap a SSH-managed Debian-like minion and do some basic operations on it 12m 29s 406ms 12

Scenario:
Log in as org admin user
1s 715ms 1

Given I am authorized 1s 715ms

Scenario:
Delete the Debian-like minion
4m 8s 71ms 7

When I am on the Systems overview page of this "deblike_minion" 1s 633ms

And I follow "Delete System" 477ms

Then I should see a "Confirm System Profile Deletion" text 60ms

When I click on "Delete Profile" 64ms

And I wait until I see "has been deleted" text 4m 4s 219ms

And I wait until Salt client is inactive on "deblike_minion" 1s 245ms

Then "deblike_minion" should not be registered 369ms

Scenario:
Bootstrap a SSH-managed Debian-like minion
2m 22s 802ms 11

The hostname of deblike_minion is uyuni-master-deblike-minion

When I follow the left menu "Systems > Bootstrapping" 88ms

Then I should see a "Bootstrap Minions" text 71ms

When I check "manageWithSSH" 117ms

And I enter the hostname of "deblike_minion" as "hostname" 132ms

And I enter "linux" as "password" 61ms

And I select the hostname of "proxy" from "proxies" if present 78ms

And I click on "Bootstrap" 63ms

And I wait at most 480 seconds until I see "Bootstrap process initiated." text 39s 65ms

And I follow the left menu "Systems > System List > All" 137ms

And I wait until I see the name of "deblike_minion", refreshing the page 58s 29ms

And I wait until onboarding is completed for "deblike_minion" 44s 957ms

@proxy
Scenario:
Check connection from SSH-managed Debian-like minion to proxy
1s 418ms 4

Given I am on the Systems overview page of this "deblike_minion" 1s 213ms

When I follow "Details" in the content area 74ms

And I follow "Connection" in the content area 64ms

Then I should see "proxy" short hostname 66ms

@proxy
Scenario:
Check registration on proxy of SSH-managed Debian-like minion
1s 326ms 4

Given I am on the Systems overview page of this "proxy" 1s 102ms

When I follow "Details" in the content area 60ms

And I follow "Proxy" in the content area 66ms

Then I should see "deblike_minion" hostname 96ms

Scenario:
Subscribe the SSH-managed Debian-like minion to a base channel
51s 100ms 11

Given I am on the Systems overview page of this "deblike_minion" 1s 198ms

When I follow "Software" in the content area 70ms

And I follow "Software Channels" in the content area 73ms

And I wait until I do not see "Loading..." text 66ms

And I check radio button "Fake-Base-Channel-Debian-like" 10s 81ms

And I wait until I do not see "Loading..." text 403ms

And I click on "Next" 71ms

Then I should see a "Confirm Software Channel Change" text 61ms

When I click on "Confirm" 82ms

Then I should see a "Changing the channels has been scheduled." text 282ms

And I wait until event "Subscribe channels scheduled" is completed 38s 707ms

Scenario:
Check events history for failures on SSH-managed Debian-like minion
1m 2s 212ms 2

Given I am on the Systems overview page of this "deblike_minion" 1s 174ms

Then I check for failed events on history event page 1m 1s 37ms

Scenario:
Run a remote command on the SSH-managed Debian-like minion
19s 671ms 10

When I follow the left menu "Salt > Remote Commands" 122ms

Then I should see a "Remote Commands" text in the content area 21ms

When I enter command "cat /etc/os-release" 93ms

And I enter target "deblike_minion" 94ms

And I click on preview 14s 599ms

And I click on run 47ms

Then I should see "deblike_minion" hostname 62ms

When I wait until I see "show response" text 4s 524ms

And I expand the results for "deblike_minion" 50ms

Then I should see a "ID=ubuntu" text 53ms

Scenario:
Check events history for failures on SSH-managed Debian-like minion
1m 12s 267ms 2

Given I am on the Systems overview page of this "deblike_minion" 1s 271ms

Then I check for failed events on history event page 1m 10s 995ms

Scenario:
Cleanup: delete the SSH-managed Debian-like minion
14s 789ms 6

When I am on the Systems overview page of this "deblike_minion" 1s 205ms

And I follow "Delete System" 468ms

Then I should see a "Confirm System Profile Deletion" text 68ms

When I click on "Delete Profile" 63ms

And I wait until I see "has been deleted" text 12s 292ms

Then "deblike_minion" should not be registered 690ms

Scenario:
Cleanup: bootstrap a Debian-like minion
1m 42s 722ms 12

The hostname of deblike_minion is uyuni-master-deblike-minion

When I follow the left menu "Systems > Bootstrapping" 85ms

Then I should see a "Bootstrap Minions" text 68ms

When I enter the hostname of "deblike_minion" as "hostname" 127ms

And I enter "22" as "port" 55ms

And I enter "root" as "user" 59ms

And I enter "linux" as "password" 64ms

And I select the hostname of "proxy" from "proxies" if present 83ms

And I click on "Bootstrap" 62ms

And I wait at most 480 seconds until I see "Bootstrap process initiated." text 22s 143ms

And I follow the left menu "Systems > System List > All" 147ms

And I wait until I see the name of "deblike_minion", refreshing the page 1m 11s 302ms

And I wait until onboarding is completed for "deblike_minion" 8s 522ms

Scenario:
Cleanup: re-subscribe the Debian-like minion to a base channel
31s 307ms 11

Given I am on the Systems overview page of this "deblike_minion" 1s 56ms

When I follow "Software" in the content area 74ms

And I follow "Software Channels" in the content area 67ms

And I wait until I do not see "Loading..." text 73ms

And I check radio button "Fake-Base-Channel-Debian-like" 10s 125ms

And I wait until I do not see "Loading..." text 386ms

And I click on "Next" 69ms

Then I should see a "Confirm Software Channel Change" text 62ms

When I click on "Confirm" 86ms

Then I should see a "Changing the channels has been scheduled." text 300ms

And I wait until event "Subscribe channels scheduled" is completed 19s 5ms

@scope_salt_ssh @scope_onboarding @ssh_minion @skip_if_github_validation
Feature:Register a salt-ssh system via API 4m 10s 262ms 11 1

Scenario:
Log in as org admin user
2s 59ms 1

Given I am authorized 2s 59ms

Scenario:
Delete SSH minion system profile before API bootstrap test
16s 788ms 6

Given I am on the Systems overview page of this "ssh_minion" 1s 858ms

When I follow "Delete System" 459ms

Then I should see a "Confirm System Profile Deletion" text 63ms

When I click on "Delete Profile" 65ms

And I wait until I see "has been deleted" text 13s 861ms

Then "ssh_minion" should not be registered 479ms

@proxy
Scenario:
Block direct access from server to sshminion to test proxy as jumphost
815ms 1

Given I block connections from "server" on "ssh_minion" 815ms

Scenario:
Bootstrap a SLES SSH minion via API
41s 481ms 1

When I call system.bootstrap() on host "ssh_minion" and salt-ssh "enabled" 41s 481ms

Scenario:
Check new API bootstrapped salt-ssh system in System Overview page
1m 39s 70ms 3

When I follow the left menu "Systems > System List > All" 98ms

And I wait until I see the name of "ssh_minion", refreshing the page 1m 11s 59ms

And I wait until onboarding is completed for "ssh_minion" 27s 912ms

Scenario:
Check contact method of this Salt SSH system
1s 147ms 2

Given I am on the Systems overview page of this "ssh_minion" 1s 65ms

Then I should see a "Push via SSH" text 82ms

@proxy
Scenario:
Check registration on proxy of SSH minion bootstrapped via API
1s 336ms 4

Given I am on the Systems overview page of this "proxy" 1s 68ms

When I follow "Details" in the content area 75ms

And I follow "Proxy" in the content area 97ms

Then I should see "ssh_minion" hostname 95ms

Scenario:
Check spacecmd system ID of SSH minion bootstrapped via API
3s 799ms 2

Given I am on the Systems overview page of this "ssh_minion" 1s 85ms

Then I run spacecmd listeventhistory for "ssh_minion" 2s 713ms

Scenario:
Check events history for failures on SSH minion after API bootstrap
42s 60ms 2

Given I am on the Systems overview page of this "ssh_minion" 1s 44ms

Then I check for failed events on history event page 41s 16ms

@susemanager
Scenario:
API bootstrap: subscribe SSH minion to base channel
< 1ms 14

Given I am on the Systems overview page of this "ssh_minion" 0s

When I follow "Software" in the content area 0s

And I follow "Software Channels" in the content area 0s

And I wait until I do not see "Loading..." text 0s

And I check radio button "SLE-Product-SLES15-SP7-Pool for x86_64" 0s

And I wait until I do not see "Loading..." text 0s

And I include the recommended child channels 0s

And I check "SLE-Module-DevTools15-SP7-Pool for x86_64" 0s

And I check "Fake-RPM-SUSE-Channel" 0s

And I click on "Next" 0s

Then I should see a "Confirm Software Channel Change" text 0s

When I click on "Confirm" 0s

Then I should see a "Changing the channels has been scheduled." text 0s

And I wait until event "Subscribe channels scheduled" is completed 0s

@uyuni
Scenario:
API bootstrap: subscribe SSH minion to base channel
40s 989ms 13

Warning: Radio button 'openSUSE Tumbleweed (x86_64)' is already checked

Given I am on the Systems overview page of this "ssh_minion" 1s 42ms

When I follow "Software" in the content area 72ms

And I follow "Software Channels" in the content area 68ms

And I wait until I do not see "Loading..." text 69ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 172ms

And I wait until I do not see "Loading..." text 425ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 44ms

And I check "Fake-RPM-SUSE-Channel" 43ms

And I click on "Next" 66ms

Then I should see a "Confirm Software Channel Change" text 62ms

When I click on "Confirm" 82ms

Then I should see a "Changing the channels has been scheduled." text 312ms

And I wait until event "Subscribe channels scheduled" is completed 38s 526ms

@proxy
Scenario:
Cleanup and flush the firewall rules
713ms 1

When I flush firewall on "ssh_minion" 713ms

@skip_if_github_validation @scope_onboarding
Feature:Bootstrap a Salt minion via the GUI using SSH key 7m 1s 380ms 7 1

Scenario:
Log in as org admin user
2s 133ms 1

Given I am authorized 2s 133ms

Scenario:
Delete SLES minion system profile before bootstrap with SSH key test
4m 7s 298ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 570ms

When I follow "Delete System" 491ms

Then I should see a "Confirm System Profile Deletion" text 61ms

When I click on "Delete Profile" 76ms

And I wait until I see "has been deleted" text 4m 3s 971ms

And I wait until Salt client is inactive on "sle_minion" 750ms

Then "sle_minion" should not be registered 376ms

Scenario:
Prepare the minion for SSH key authentication
1s 287ms 2

When I backup the SSH authorized_keys file of host "sle_minion" 413ms

And I add pre-generated SSH public key to authorized_keys of host "sle_minion" 873ms

Scenario:
Bootstrap a SLES minion using SSH key with wrong passphrase
38s 543ms 14 1 1

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 81ms

Then I should see a "Bootstrap Minions" text 64ms

When I enter the hostname of "sle_minion" as "hostname" 157ms

And I enter "22" as "port" 64ms

And I enter "root" as "user" 69ms

And I check radio button "SSH Private Key" 10s 73ms

And I attach the file "ssh_keypair/id_rsa_bootstrap-passphrase_linux" to "privKeyFile" 38ms

And I enter "you-shall-not-pass" as "privKeyPwd" 90ms

And I click on "Bootstrap" 65ms

And I wait until I see "An error has occurred during salt execution: unable to establish ssh connection." text 7s 623ms

Then I should see a "Details" button 18ms

When I click on "Details" 80ms

And I wait at most 10 seconds until I see modal containing "Error Details" text 12ms

Then I should see a "Standard Error" text 69ms

And I should see "Permission denied, no authentication information" or "Permission denied (publickey,password,keyboard-interactive)" in the stderr textarea 20s 31ms Show Error + 
                                            
 Text 'Permission denied, no authentication information' and 'Permission denied (publickey,password,keyboard-interactive)' not found (ScriptError)
./features/step_definitions/navigation_steps.rb:722:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:721:in `/^I should see "([^"]*)" or "([^"]*)" in the ([^ ]+) textarea$/'
features/secondary/min_bootstrap_ssh_key.feature:44:in `I should see "Permission denied, no authentication information" or "Permission denied (publickey,password,keyboard-interactive)" in the stderr textarea'

When I close the modal dialog 0s

Scenario:
Bootstrap a SLES minion using SSH key
44s 381ms 11

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 76ms

Then I should see a "Bootstrap Minions" text 65ms

When I enter the hostname of "sle_minion" as "hostname" 137ms

And I enter "22" as "port" 51ms

And I enter "root" as "user" 56ms

And I check radio button "SSH Private Key" 10s 89ms

And I attach the file "ssh_keypair/id_rsa_bootstrap-passphrase_linux" to "privKeyFile" 43ms

And I enter "linux" as "privKeyPwd" 75ms

And I select the hostname of "proxy" from "proxies" if present 83ms

And I click on "Bootstrap" 71ms

And I wait at most 480 seconds until I see "Bootstrap process initiated." text 33s 631ms

Scenario:
Check new minion bootstrapped with SSH key in System Overview page
1m 25s 475ms 6

It took 2 seconds to contact the minion

When I follow the left menu "Salt > Keys" 132ms

Then I should see a "accepted" text 335ms

When I am on the Systems page 264ms

And I wait until I see the name of "sle_minion", refreshing the page 44s 236ms

And I wait until onboarding is completed for "sle_minion" 38s 594ms

Then the Salt master can reach "sle_minion" 1s 912ms

Scenario:
Also check contact method of this minion
1s 83ms 2

Given I am on the Systems overview page of this "sle_minion" 998ms

Then I should see a "Default" text 84ms

Scenario:
Cleanup: restore authorized keys
1s 178ms 1

When I restore the SSH authorized_keys file of host "sle_minion" 1s 178ms

@skip_if_containerized_server @skip_if_github_validation @sle_minion @scope_onboarding
Feature:Register a Salt minion with a bootstrap script < 1ms 11

1) delete SLES minion and register again with bootstrap script
2) subscribe minion to a base channels
3) install and remove a package

Scenario:
Log in as org admin user
< 1ms 1

Given I am authorized 0s

Scenario:
Delete SLES minion system profile before script bootstrap test
< 1ms 7

Given I am on the Systems overview page of this "sle_minion" 0s

When I follow "Delete System" 0s

Then I should see a "Confirm System Profile Deletion" text 0s

When I click on "Delete Profile" 0s

And I wait until I see "has been deleted" text 0s

And I wait until Salt client is inactive on "sle_minion" 0s

Then "sle_minion" should not be registered 0s

Scenario:
Bootstrap the minion using the script
< 1ms 4

When I bootstrap "sle_minion" using bootstrap script with activation key "1-SUSE-KEY-x86_64" from the proxy 0s

And I wait at most 10 seconds until Salt master sees "sle_minion" as "unaccepted" 0s

And I accept "sle_minion" key in the Salt master 0s

Then I should see "sle_minion" via spacecmd 0s

Scenario:
Check if onboarding for the script-bootstrapped minion was successful
< 1ms 3

When I follow the left menu "Systems > System List > All" 0s

And I wait until I see the name of "sle_minion", refreshing the page 0s

And I wait until onboarding is completed for "sle_minion" 0s

Scenario:
Detect latest Salt changes on the script-bootstrapped SLES minion
< 1ms 1

When I query latest Salt changes on "sle_minion" 0s

@susemanager
Scenario:
Subscribe the script-bootstrapped SLES minion to a base channel
< 1ms 14

Given I am on the Systems overview page of this "sle_minion" 0s

When I follow "Software" in the content area 0s

And I follow "Software Channels" in the content area 0s

And I wait until I do not see "Loading..." text 0s

And I check radio button "SLE-Product-SLES15-SP7-Pool for x86_64" 0s

And I wait until I do not see "Loading..." text 0s

And I include the recommended child channels 0s

And I check "SLE-Module-DevTools15-SP7-Pool for x86_64" 0s

And I check "Fake-RPM-SUSE-Channel" 0s

And I click on "Next" 0s

Then I should see a "Confirm Software Channel Change" text 0s

When I click on "Confirm" 0s

Then I should see a "Changing the channels has been scheduled." text 0s

And I wait until event "Subscribe channels scheduled" is completed 0s

@uyuni
Scenario:
Subscribe the script-bootstrapped SLES minion to a base channel
< 1ms 13

Given I am on the Systems overview page of this "sle_minion" 0s

When I follow "Software" in the content area 0s

And I follow "Software Channels" in the content area 0s

And I wait until I do not see "Loading..." text 0s

And I check radio button "openSUSE Tumbleweed (x86_64)" 0s

And I wait until I do not see "Loading..." text 0s

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 0s

And I check "Fake-RPM-SUSE-Channel" 0s

And I click on "Next" 0s

Then I should see a "Confirm Software Channel Change" text 0s

When I click on "Confirm" 0s

Then I should see a "Changing the channels has been scheduled." text 0s

And I wait until event "Subscribe channels scheduled" is completed 0s

Scenario:
Install a package to the script-bootstrapped SLES minion
< 1ms 11

Given I am on the Systems overview page of this "sle_minion" 0s

When I follow "Software" in the content area 0s

And I follow "Install" 0s

And I enter "orion-dummy" as the filtered package name 0s

And I click on the filter button 0s

And I check row with "orion-dummy" and arch of "sle_minion" 0s

And I click on "Install Packages" 0s

And I click on "Confirm" 0s

Then I should see a "1 package install has been scheduled for" text 0s

When I wait until event "Package Install/Upgrade scheduled" is completed 0s

Then "orion-dummy-1.1-1.1" should be installed on "sle_minion" 0s

Scenario:
Run a remote command on normal SLES minion
< 1ms 10

When I follow the left menu "Salt > Remote Commands" 0s

Then I should see a "Remote Commands" text in the content area 0s

When I enter command "file /tmp" 0s

And I click on preview 0s

Then I should see "sle_minion" hostname 0s

And I wait until I do not see "pending" text 0s

When I click on run 0s

And I wait until I do not see "pending" text 0s

And I expand the results for "sle_minion" 0s

Then I should see "/tmp: sticky, directory" in the command output for "sle_minion" 0s

Scenario:
Check spacecmd system ID of bootstrapped minion
< 1ms 2

Given I am on the Systems overview page of this "sle_minion" 0s

Then I run spacecmd listeventhistory for "sle_minion" 0s

Scenario:
Cleanup: remove package from script-bootstrapped SLES minion
< 1ms 2

When I remove package "orion-dummy-1.1-1.1" from this "sle_minion" 0s

Then "orion-dummy-1.1-1.1" should not be installed on "sle_minion" 0s

@skip_if_github_validation @scope_salt_ssh @ssh_minion
Feature:Register a Salt system to be managed via SSH tunnel 10m 46s 925ms 8 2

Scenario:
Log in as org admin user
1s 769ms 1

Given I am authorized 1s 769ms

Scenario:
Pre-requisite: remove package before ssh tunnel test
1s 585ms 1

When I remove package "milkyway-dummy" from this "ssh_minion" without error control 1s 585ms

Scenario:
Delete the Salt minion for SSH tunnel bootstrap
15s 603ms 6

Given I am on the Systems overview page of this "ssh_minion" 1s 92ms

When I follow "Delete System" 487ms

Then I should see a "Confirm System Profile Deletion" text 61ms

When I click on "Delete Profile" 67ms

And I wait until I see "has been deleted" text 13s 455ms

Then "ssh_minion" should not be registered 439ms

Scenario:
Register this minion for push via SSH tunnel
6m 9s 166ms 12 1

The hostname of ssh_minion is uyuni-master-suse-sshminion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 80ms

Then I should see a "Bootstrap Minions" text 71ms

And I enter the hostname of "ssh_minion" as "hostname" 149ms

And I enter "22" as "port" 51ms

And I enter "root" as "user" 57ms

And I enter "linux" as "password" 61ms

And I select "1-SUSE-SSH-TUNNEL-KEY-x86_64" from "activationKeys" 72ms

And I select the hostname of "proxy" from "proxies" if present 60ms

And I check "manageWithSSH" 84ms

And I click on "Bootstrap" 59ms

And I wait at most 480 seconds until I see "Bootstrap process initiated." text 39s 282ms

And I wait until onboarding is completed for "ssh_minion" 5m 13s 485ms Show Error + 
                                            
 execution expired (Timeout::Error)
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/step_definitions/navigation_steps.rb:70:in `/^I wait until I see "([^"]*)" (text|regex), refreshing the page$/'
./features/step_definitions/common_steps.rb:157:in `/^I wait (\d+) seconds until the event is picked up and (\d+) seconds until the event "([^"]*)" is completed$/'
./features/step_definitions/setup_steps.rb:218:in `/^I wait at most (\d+) seconds until onboarding is completed for "([^"]*)"$/'
./features/step_definitions/setup_steps.rb:230:in `/^I wait until onboarding is completed for "([^"]*)"$/'
features/secondary/minssh_tunnel.feature:40:in `I wait until onboarding is completed for "ssh_minion"'

15s 650ms Show Info + 
13:16:33:000 - 13:22:27:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/History.do?sid=1000010012&
Screenshot +

Scenario:
The contact method is SSH tunnel on this minion
1s 121ms 2

Given I am on the Systems overview page of this "ssh_minion" 1s 37ms

Then I should see a "Push via SSH tunnel" text 84ms

Scenario:
Install a package from this SSH tunnel minion
59s 129ms 11

Given I am on the Systems overview page of this "ssh_minion" 1s 95ms

When I follow "Software" in the content area 80ms

And I follow "Install" 587ms

And I enter "milkyway-dummy" as the filtered package name 55ms

And I click on the filter button 597ms

And I wait until I see "milkyway-dummy" text 71ms

And I check row with "milkyway-dummy" and arch of "ssh_minion" 63ms

And I click on "Install Packages" 648ms

And I click on "Confirm" 738ms

Then I should see a "1 package install has been scheduled for" text 62ms

Then I wait until event "Package Install/Upgrade scheduled" is completed 55s 128ms

@flaky
Scenario:
Remove a package from this SSH tunnel minion
27s 173ms 4 7 1

Given I am on the Systems overview page of this "ssh_minion" 1s 55ms

And I follow "Software" in the content area 80ms

And I follow "List / Remove" 498ms

And I enter "milkyway-dummy" as the filtered package name 10s 8ms Show Error + 
                                            
 Unable to find css "input[placeholder='Filter by Package Name: ']" (Capybara::ElementNotFound)
./features/support/navigation_step_helper.rb:45:in `filter_by_package_name'
./features/step_definitions/navigation_steps.rb:944:in `/^I enter "([^"]*)" as the filtered package name$/'
features/secondary/minssh_tunnel.feature:64:in `I enter "milkyway-dummy" as the filtered package name'

And I click on the filter button 0s

And I wait until I see "milkyway-dummy" text 0s

And I check "milkyway-dummy" in the list 0s

And I click on "Remove Packages" 0s

And I click on "Confirm" 0s

Then I should see a "1 package removal has been scheduled" text 0s

Then I wait until event "Package Removal scheduled" is completed 0s

15s 530ms Show Info + 
13:23:43:000 - 13:23:55:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/packages/PackageList.do?sid=1000010012&
Screenshot +

Scenario:
Run a remote command on this SSH tunnel minion
27s 939ms 11

The hostname of ssh_minion is uyuni-master-suse-sshminion.sumaci.aws

When I follow the left menu "Salt > Remote Commands" 120ms

Then I should see a "Remote Commands" text in the content area 21ms

When I enter command "echo 'My remote command output'" 104ms

And I enter the hostname of "ssh_minion" as "target" 111ms

And I click on preview 18s 506ms

Then I should see a "Target systems (1)" text 61ms

When I wait until I do not see "pending" text 50ms

And I click on run 48ms

And I wait until I see "show response" text 8s 847ms

And I expand the results for "ssh_minion" 49ms

Then I should see "My remote command output" in the command output for "ssh_minion" 17ms

Scenario:
Cleanup: delete the SSH tunnel minion
21s 286ms 6

Given I am on the Systems overview page of this "ssh_minion" 1s 38ms

When I follow "Delete System" 461ms

Then I should see a "Confirm System Profile Deletion" text 59ms

When I click on "Delete Profile" 61ms

And I wait until I see "has been deleted" text 19s 255ms

Then "ssh_minion" should not be registered 410ms

Scenario:
Cleanup: register a SSH minion after SSH tunnel tests
2m 2s 150ms 4

When I call system.bootstrap() on host "ssh_minion" and salt-ssh "enabled" 39s 627ms

And I follow the left menu "Systems > System List > All" 95ms

And I wait until I see the name of "ssh_minion", refreshing the page 30s 755ms

And I wait until onboarding is completed for "ssh_minion" 51s 672ms

@skip_if_github_validation @scope_onboarding
Feature:Bootstrap a Salt minion via the GUI with an activation key 7m 14s 71ms 14 2

Scenario:
Log in as org admin user
1s 726ms 1

Given I am authorized 1s 726ms

Scenario:
Delete SLES minion system profile
4m 7s 90ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 549ms

When I follow "Delete System" 465ms

Then I should see a "Confirm System Profile Deletion" text 59ms

When I click on "Delete Profile" 87ms

And I wait until I see "has been deleted" text 4m 3s 762ms

And I wait until Salt client is inactive on "sle_minion" 766ms

Then "sle_minion" should not be registered 399ms

Scenario:
Create a configuration channel for the activation key
1s 415ms 7

When I follow the left menu "Configuration > Channels" 140ms

And I follow "Create Config Channel" 320ms

And I enter "Key Channel" as "cofName" 73ms

And I enter "keychannel" as "cofLabel" 56ms

And I enter "This is a configuration channel for the activation key" as "cofDescription" 92ms

And I click on "Create Config Channel" 69ms

Then I should see a "Key Channel" text 661ms

Scenario:
Add a configuration file to the key configuration channel
1s 624ms 6

When I follow the left menu "Configuration > Channels" 67ms

And I follow "Key Channel" 451ms

And I follow "Create Configuration File or Directory" 375ms

And I enter "/etc/euler.conf" as "cffPath" 67ms

And I enter "e^i.pi=-1" in the editor 5ms

And I click on "Create Configuration File" 657ms

@susemanager
Scenario:
Create a complete minion activation key
< 1ms 20

When I follow the left menu "Systems > Activation Keys" 0s

And I follow "Create Key" 0s

And I wait for child channels to appear 0s

And I enter "Minion testing" as "description" 0s

And I enter "MINION-TEST" as "key" 0s

And I enter "20" as "usageLimit" 0s

And I select "SLE-Product-SLES15-SP7-Pool for x86_64" 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 check "Fake-RPM-SUSE-Channel" 0s

And I click on "Create Activation Key" 0s

And I follow "Configuration" in the content area 0s

And I follow first "Subscribe to Channels" in the content area 0s

And I check "Key Channel" in the list 0s

And I click on "Continue" 0s

And I follow "Packages" 0s

And I enter "orion-dummy perseus-dummy" as "packages" 0s

And I click on "Update Activation Key" 0s

Then I should see a "Activation key Minion testing has been modified" text 0s

@uyuni
Scenario:
Create a complete minion activation key
4s 773ms 19

When I follow the left menu "Systems > Activation Keys" 127ms

And I follow "Create Key" 351ms

And I wait for child channels to appear 1s 168ms

And I enter "Minion testing" as "description" 90ms

And I enter "MINION-TEST" as "key" 92ms

And I enter "20" as "usageLimit" 59ms

And I select "openSUSE Tumbleweed (x86_64)" from "selectedBaseChannel" 83ms

And I wait for child channels to appear 397ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 84ms

And I check "Fake-RPM-SUSE-Channel" 77ms

And I click on "Create Activation Key" 619ms

And I follow "Configuration" in the content area 71ms

And I follow first "Subscribe to Channels" in the content area 66ms

And I check "Key Channel" in the list 65ms

And I click on "Continue" 506ms

And I follow "Packages" 324ms

And I enter "orion-dummy perseus-dummy" as "packages" 71ms

And I click on "Update Activation Key" 60ms

Then I should see a "Activation key Minion testing has been modified" text 455ms

Scenario:
Bootstrap a SLES minion with an activation key
1m 46s 886ms 13

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 72ms

Then I should see a "Bootstrap Minions" text 75ms

When I enter the hostname of "sle_minion" as "hostname" 147ms

And I enter "22" as "port" 58ms

And I enter "root" as "user" 62ms

And I enter "linux" as "password" 66ms

And I select "1-MINION-TEST" from "activationKeys" 68ms

And I select the hostname of "proxy" from "proxies" if present 75ms

And I click on "Bootstrap" 66ms

And I wait until I see "Bootstrap process initiated." text 23s 435ms

And I follow the left menu "Systems > System List > All" 153ms

And I wait until I see the name of "sle_minion", refreshing the page 17s 307ms

And I wait until onboarding is completed for "sle_minion" 1m 5s 296ms

Scenario:
Verify that minion bootstrapped with Salt key and packages
4s 352ms 5

It took 2 seconds to contact the minion

When I follow the left menu "Salt > Keys" 127ms

Then I should see a "accepted" text 333ms

And the Salt master can reach "sle_minion" 1s 915ms

When I wait for "orion-dummy" to be installed on "sle_minion" 1s 153ms

And I wait for "perseus-dummy" to be installed on "sle_minion" 823ms

Scenario:
Check system ID of bootstrapped minion
3s 366ms 2

Given I am on the Systems overview page of this "sle_minion" 1s 5ms

Then I run spacecmd listeventhistory for "sle_minion" 2s 361ms

@susemanager
Scenario:
Verify that minion bootstrapped with base channel
< 1ms 2

Given I am on the Systems page 0s

Then I should see a "SLE-Product-SLES15-SP7-Pool for x86_64" text 0s

@uyuni
Scenario:
Verify that minion bootstrapped with base channel
756ms 2

Given I am on the Systems page 243ms

Then I should see a "openSUSE Tumbleweed (x86_64)" text 512ms

Scenario:
Verify that minion bootstrapped with configuration channel
1s 354ms 6

Given I am on the Systems overview page of this "sle_minion" 1s 6ms

When I follow "Configuration" in the content area 69ms

Then I should see a "1 configuration channel" text 69ms

When I follow "View Files" in the content area 66ms

Then I should see a "/etc/euler.conf" text 74ms

And I should see a "Key Channel" text 67ms

Scenario:
Cleanup: remove the package states
6s 62ms 12

Given I am on the Systems overview page of this "sle_minion" 981ms

When I follow "States" in the content area 72ms

And I follow "Packages" 559ms

Then I should see a "Package States" text 59ms

When I change the state of "orion-dummy" to "Unmanaged" and "" 131ms

And I change the state of "perseus-dummy" to "Unmanaged" and "" 45ms

Then I should see a "2 Changes" text 65ms

When I click save 52ms

Then I wait until I see "Package states have been saved." text 276ms

And I click apply 49ms

And I remove package "orion-dummy" from this "sle_minion" 1s 686ms

And I remove package "perseus-dummy" from this "sle_minion" 2s 81ms

Scenario:
Cleanup: remove the key configuration channel
1s 390ms 4

When I follow the left menu "Configuration > Channels" 113ms

And I follow "Key Channel" 489ms

And I follow "Delete Channel" 299ms

And I click on "Delete Config Channel" 487ms

Scenario:
Cleanup: delete the activation key
1s 182ms 5

When I follow the left menu "Systems > Activation Keys" 129ms

And I follow "Minion testing" in the content area 65ms

And I follow "Delete Key" 311ms

And I click on "Delete Activation Key" 589ms

Then I should see a "Activation key Minion testing has been deleted." text 86ms

Scenario:
Check events history for failures on SLES minion with activation key
52s 86ms 2

Given I am on the Systems overview page of this "sle_minion" 1s 18ms

Then I check for failed events on history event page 51s 67ms

@skip_if_github_validation @scope_onboarding
Feature:Register a Salt minion via API 7m 20s 667ms 11 1

Scenario:
Log in as org admin user
2s 101ms 1

Given I am authorized 2s 101ms

Scenario:
Delete SLES minion system profile before API bootstrap test
4m 7s 137ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 649ms

When I follow "Delete System" 496ms

Then I should see a "Confirm System Profile Deletion" text 64ms

When I click on "Delete Profile" 63ms

And I wait until I see "has been deleted" text 4m 3s 769ms

And I wait until Salt client is inactive on "sle_minion" 731ms

Then "sle_minion" should not be registered 361ms

Scenario:
Bootstrap a SLES minion via API
23s 119ms 1

When I call system.bootstrap() on host "sle_minion" and salt-ssh "disabled" 23s 119ms

Scenario:
Check new minion bootstrapped via API in System Overview page
1m 25s 472ms 6

It took 2 seconds to contact the minion

When I follow the left menu "Salt > Keys" 148ms

Then I should see a "accepted" text 364ms

When I follow the left menu "Systems > System List > All" 198ms

And I wait until I see the name of "sle_minion", refreshing the page 57s 754ms

And I wait until onboarding is completed for "sle_minion" 25s 92ms

Then the Salt master can reach "sle_minion" 1s 913ms

Scenario:
Check contact method of this minion
1s 114ms 2

Given I am on the Systems overview page of this "sle_minion" 1s 28ms

Then I should see a "Default" text 85ms

@proxy
Scenario:
Check registration on proxy of minion bootstrapped via API
1s 315ms 4

Given I am on the Systems overview page of this "proxy" 1s 38ms

When I follow "Details" in the content area 80ms

And I follow "Proxy" in the content area 99ms

Then I should see "sle_minion" hostname 97ms

Scenario:
Check spacecmd system ID of minion bootstrapped via API
3s 392ms 2

Given I am on the Systems overview page of this "sle_minion" 1s 12ms

Then I run spacecmd listeventhistory for "sle_minion" 2s 379ms

@susemanager
Scenario:
API bootstrap: subscribe to base channel
< 1ms 14

Given I am on the Systems overview page of this "sle_minion" 0s

When I follow "Software" in the content area 0s

And I follow "Software Channels" in the content area 0s

And I wait until I do not see "Loading..." text 0s

And I check radio button "SLE-Product-SLES15-SP7-Pool for x86_64" 0s

And I wait until I do not see "Loading..." text 0s

And I include the recommended child channels 0s

And I check "SLE-Module-DevTools15-SP7-Pool for x86_64" 0s

And I check "Fake-RPM-SUSE-Channel" 0s

And I click on "Next" 0s

Then I should see a "Confirm Software Channel Change" text 0s

When I click on "Confirm" 0s

Then I should see a "Changing the channels has been scheduled." text 0s

And I wait until event "Subscribe channels scheduled" is completed 0s

@uyuni
Scenario:
API bootstrap: subscribe to base channel
21s 213ms 13

Warning: Radio button 'openSUSE Tumbleweed (x86_64)' is already checked

Given I am on the Systems overview page of this "sle_minion" 1s 11ms

When I follow "Software" in the content area 82ms

And I follow "Software Channels" in the content area 71ms

And I wait until I do not see "Loading..." text 65ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 180ms

And I wait until I do not see "Loading..." text 430ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 42ms

And I check "Fake-RPM-SUSE-Channel" 44ms

And I click on "Next" 71ms

Then I should see a "Confirm Software Channel Change" text 64ms

When I click on "Confirm" 84ms

Then I should see a "Changing the channels has been scheduled." text 309ms

And I wait until event "Subscribe channels scheduled" is completed 18s 752ms

Scenario:
Check events history for failures on SLES minion after API bootstrap
52s 4ms 2

Given I am on the Systems overview page of this "sle_minion" 969ms

Then I check for failed events on history event page 51s 35ms

Scenario:
Bootstrap via API a non-existing system
3s 49ms 1

When I call system.bootstrap() on unknown host, I should get an API fault 3s 49ms

Scenario:
Bootstrap a salt-ssh system with activation key and default contact method
747ms 1

When I call system.bootstrap() on a Salt minion with saltSSH = true, but with activation key with default contact method, I should get an API fault 747ms

@skip_if_github_validation @sle_minion @scope_onboarding
Feature:Bootstrapping with reactivation key 7m 55s 36ms 8

In order to re-register valid minions
As an authorized user
I want to avoid re-registration with invalid input parameters

Scenario:
Log in as org admin user
2s 268ms 1

Given I am authorized 2s 268ms

Scenario:
Generate a re-activation key
3s 28ms 4

Given I am on the Systems overview page of this "sle_minion" 1s 713ms

When I follow "Reactivation" 481ms

And I click on "Generate New Key" 767ms

Then I should see a "Key:" text 65ms

Scenario:
Bootstrap should fail when minion already exists
896ms 10

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 78ms

Then I should see a "Bootstrap Minions" text 62ms

When I enter the hostname of "sle_minion" as "hostname" 144ms

And I enter "22" as "port" 50ms

And I enter "root" as "user" 57ms

And I enter "linux" as "password" 57ms

And I click on "Bootstrap" 63ms

And I wait until I see "A salt key for this host" text 259ms

Then I should not see a "GenericSaltError" text 62ms

And I should see a "seems to already exist, please check!" text 59ms

Scenario:
Bootstrap should fail when system already exists in the server
2s 803ms 11

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

Given I delete "sle_minion" key in the Salt master 1s 923ms

When I follow the left menu "Systems > Bootstrapping" 63ms

Then I should see a "Bootstrap Minions" text 61ms

When I enter the hostname of "sle_minion" as "hostname" 126ms

And I enter "22" as "port" 50ms

And I enter "root" as "user" 56ms

And I enter "linux" as "password" 62ms

And I click on "Bootstrap" 62ms

And I wait until I see "seems to already exist, please check!" text 259ms

Then I should not see a "GenericSaltError" text 60ms

And I should see a "with minion id" text 76ms

Scenario:
Bootstrap a SLES minion with reactivation key
1m 50s 831ms 13

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws
Reactivation Key: re-1-ba0295628f8f4020ae8a5183b61219a7

When I follow the left menu "Systems > Bootstrapping" 63ms

Then I should see a "Bootstrap Minions" text 62ms

When I enter the hostname of "sle_minion" as "hostname" 120ms

And I enter "22" as "port" 45ms

And I enter "root" as "user" 54ms

And I enter "linux" as "password" 57ms

And I enter the reactivation key of "sle_minion" 1s 73ms

And I select "1-SUSE-KEY-x86_64" from "activationKeys" 72ms

And I click on "Bootstrap" 54ms

And I wait until I see "Bootstrap process initiated." text 28s 587ms

And I follow the left menu "Systems > System List > All" 169ms

And I wait until I see the name of "sle_minion", refreshing the page 706ms

And I wait until onboarding is completed for "sle_minion" 1m 19s 763ms

Scenario:
Check the events history for the reactivation
3s 587ms 5

Given I am on the Systems overview page of this "sle_minion" 1s 37ms

When I follow "Events" in the content area 74ms

And I follow "History" in the content area 72ms

And I wait until I see "Server reactivated as Salt minion" text, refreshing the page 89ms

And I wait until event "Apply states [certs, channels, packages, services.salt-minion] scheduled" is completed 2s 313ms

Scenario:
Cleanup: delete SLES minion after reactivation tests
4m 5s 413ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 11ms

When I follow "Delete System" 465ms

Then I should see a "Confirm System Profile Deletion" text 62ms

When I click on "Delete Profile" 64ms

And I wait until I see "has been deleted" text 4m 2s 695ms

And I wait until Salt client is inactive on "sle_minion" 739ms

Then "sle_minion" should not be registered 374ms

Scenario:
Cleanup: bootstrap a SLES minion after reactivation tests
1m 46s 208ms 13

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 81ms

Then I should see a "Bootstrap Minions" text 70ms

When I enter the hostname of "sle_minion" as "hostname" 160ms

And I enter "22" as "port" 55ms

And I enter "root" as "user" 61ms

And I enter "linux" as "password" 64ms

And I select "1-SUSE-KEY-x86_64" from "activationKeys" 75ms

And I select the hostname of "proxy" from "proxies" if present 63ms

And I click on "Bootstrap" 64ms

And I wait until I see "Bootstrap process initiated." text 22s 535ms

And I follow the left menu "Systems > System List > All" 146ms

And I wait until I see the name of "sle_minion", refreshing the page 30s 847ms

And I wait until onboarding is completed for "sle_minion" 51s 978ms

@skip_if_github_validation @sle_minion @scope_salt
Feature:Management of minion keys 8m 7s 585ms 9

In Order to validate the minion onboarding page
As an authorized user
I want to verify all the minion key management features in the UI

Scenario:
Log in as org admin user
2s 230ms 1

Given I am authorized 2s 230ms

Scenario:
Delete SLES minion system profile before exploring the onboarding page
4m 7s 331ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 843ms

When I follow "Delete System" 509ms

Then I should see a "Confirm System Profile Deletion" text 61ms

When I click on "Delete Profile" 67ms

And I wait until I see "has been deleted" text 4m 3s 667ms

And I wait until Salt client is inactive on "sle_minion" 760ms

Then "sle_minion" should not be registered 422ms

Scenario:
Completeness of the onboarding page
156ms 2

When I follow the left menu "Salt > Keys" 133ms

Then I should see a "Keys" text in the content area 23ms

Scenario:
Minion is visible in the Pending section
15s 202ms 8

When I configure salt minion on "sle_minion" 405ms

And I restart salt-minion on "sle_minion" 642ms

And I wait at most 10 seconds until Salt master sees "sle_minion" as "unaccepted" 1s 815ms

And I follow the left menu "Salt > Keys" 60ms

And I refresh page until I see "sle_minion" hostname as text 10s 131ms

Then I should see a "Fingerprint" text 66ms

And I see "sle_minion" fingerprint 2s 8ms

And I should see a "pending" text 71ms

Scenario:
Reject and delete the pending key
18s 912ms 7

And I follow the left menu "Salt > Keys" 62ms

And I reject "sle_minion" from the Pending section 267ms

And I wait at most 10 seconds until Salt master sees "sle_minion" as "rejected" 1s 873ms

Then I should see a "rejected" text 71ms

When I stop salt-minion on "sle_minion" 2s 987ms

And I delete "sle_minion" from the Rejected section 46ms

And I refresh page until I do not see "sle_minion" hostname as text 13s 602ms

Scenario:
Accepted minion shows up as a registered system
1m 24s 986ms 9

When I start salt-minion on "sle_minion" 982ms

And I wait at most 10 seconds until Salt master sees "sle_minion" as "unaccepted" 1s 801ms

Then "sle_minion" should not be registered 438ms

When I follow the left menu "Salt > Keys" 78ms

Then I should see a "pending" text 268ms

When I accept "sle_minion" key 54ms

And I wait at most 10 seconds until Salt master sees "sle_minion" as "accepted" 1s 502ms

And I wait until onboarding is completed for "sle_minion" 1m 19s 459ms

Then "sle_minion" should be registered 400ms

Scenario:
The minion communicates with the Salt master
3s 449ms 3

It took 2 seconds to contact the minion

Then the Salt master can reach "sle_minion" 1s 891ms

When I get OS information of "sle_minion" from the Master 1s 558ms

Then it should contain the OS of "sle_minion" < 1ms

Scenario:
Delete profile of unreacheable minion
13s 185ms 9

Given I am on the Systems overview page of this "sle_minion" 1s 33ms

When I stop salt-minion on "sle_minion" 1s 210ms

And I follow "Delete System" 452ms

Then I should see a "Confirm System Profile Deletion" text 59ms

When I click on "Delete Profile" 64ms

Then I wait until I see "Cleanup timed out. Please check if the machine is reachable." text 7s 692ms

When I click on "Delete Profile Without Cleanup" in "An error occurred during cleanup" modal 2s 46ms

And I wait until I see "has been deleted" text 73ms

Then "sle_minion" should not be registered 553ms

Scenario:
Cleanup: bootstrap again the minion
1m 42s 129ms 11

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 85ms

Then I should see a "Bootstrap Minions" text 61ms

When I enter the hostname of "sle_minion" as "hostname" 139ms

And I enter "22" as "port" 54ms

And I enter "root" as "user" 61ms

And I enter "linux" as "password" 63ms

And I select "1-SUSE-KEY-x86_64" from "activationKeys" 74ms

And I select the hostname of "proxy" from "proxies" if present 59ms

And I click on "Bootstrap" 60ms

And I wait until I see "Bootstrap process initiated." text 22s 639ms

And I wait until onboarding is completed for "sle_minion" 1m 18s 830ms

@skip_if_github_validation @scope_salt
Feature:Install a package and a patch on the SUSE client via Salt through the UI 1m 59s 581ms 11

Scenario:
Pre-requisite: enable test_repo_rpm_pool repository on SLE minion
786ms 1

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 786ms

Scenario:
Pre-requisite: install virgo-dummy-1.0 package on SLE minion
1s 886ms 2

When I refresh the metadata for "sle_minion" 1s 16ms

And I install old package "virgo-dummy-1.0" on this "sle_minion" without error control 870ms

Scenario:
Pre-requisite: remove andromeda-dummy package from SLE minion
12s 853ms 4

When I remove package "andromeda-dummy" from this "sle_minion" without error control 1s 469ms

And I refresh the metadata for "sle_minion" 835ms

And I refresh packages list via spacecmd on "sle_minion" 3s 165ms

And I wait until refresh package list on "sle_minion" is finished 7s 383ms

Scenario:
Pre-requisite: refresh package list and check old packages installed on SLE minion
15s 723ms 4

When I refresh packages list via spacecmd on "sle_minion" 2s 403ms

And I wait until refresh package list on "sle_minion" is finished 7s 392ms

Then spacecmd should show packages "virgo-dummy-1.0" installed on "sle_minion" 2s 456ms

And I wait until package "andromeda-dummy-2.0-1.1" is removed from "sle_minion" via spacecmd 3s 471ms

Scenario:
Log in as org admin user
1s 884ms 1

Given I am authorized for the "Admin" section 1s 884ms

Scenario:
Pre-requisite: ensure the errata cache is computed before patching Salt minion
19s 510ms 11

Given I am on the Systems overview page of this "sle_minion" 1s 519ms

When I follow "Software" in the content area 71ms

And I follow "List / Remove" in the content area 80ms

And I enter "virgo-dummy" as the filtered package name 130ms

And I click on the filter button until page does contain "virgo-dummy" text 11s 153ms

When I follow the left menu "Admin > Task Schedules" 116ms

And I follow "errata-cache-default" 1s 325ms

And I follow "errata-cache-bunch" 1s 333ms

And I click on "Single Run Schedule" 1s 492ms

Then I should see a "bunch was scheduled" text 269ms

When I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 2s 16ms

Scenario:
Install a patch on the SLE minion
22s 762ms 12

Given I am on the Systems overview page of this "sle_minion" 991ms

When I follow "Software" in the content area 71ms

And I follow "Patches" in the content area 76ms

And I enter "virgo" as the filtered synopsis 49ms

And I click on the filter button 10s 156ms

And I check "virgo-dummy-3456" in the list 81ms

And I check "allowVendorChange" 74ms

And I click on "Apply Patches" 601ms

And I click on "Confirm" 655ms

Then I should see a "1 patch update has been scheduled for" text 74ms

When I wait for "virgo-dummy-2.0-1.1" to be installed on "sle_minion" 8s 871ms

Then vendor change should be enabled for package actions on "sle_minion" 1s 56ms

Scenario:
Install a package on the SLE minion
13s 717ms 12

Given I am on the Systems overview page of this "sle_minion" 1s 15ms

When I follow "Software" in the content area 75ms

And I follow "Packages" 426ms

And I follow "Install" 556ms

And I enter "andromeda" as the filtered package name 128ms

And I click on the filter button 696ms

And I check "andromeda-dummy-2.0-1.1" in the list 53ms

And I click on "Install Packages" 590ms

And I click on "Confirm" 759ms

Then I should see a "1 package install has been scheduled" text 63ms

When I wait for "andromeda-dummy-2.0-1.1" to be installed on "sle_minion" 8s 518ms

Then vendor change should be enabled for package actions on "sle_minion" 833ms

Scenario:
Cleanup: disable test_repo_rpm_pool on SLE minion
459ms 1

When I disable repository "test_repo_rpm_pool" on this "sle_minion" 459ms

Scenario:
Cleanup: remove virgo-dummy package from SLE minion
17s 713ms 4

When I remove package "virgo-dummy" from this "sle_minion" without error control 1s 450ms

And I refresh the metadata for "sle_minion" 812ms

And I refresh packages list via spacecmd on "sle_minion" 3s 470ms

And I wait until refresh package list on "sle_minion" is finished 11s 980ms

Scenario:
Cleanup: remove andromeda-dummy package from SLE minion
12s 282ms 4

When I remove package "andromeda-dummy" from this "sle_minion" without error control 1s 792ms

And I refresh the metadata for "sle_minion" 814ms

And I refresh packages list via spacecmd on "sle_minion" 2s 378ms

And I wait until refresh package list on "sle_minion" is finished 7s 296ms

@skip_if_github_validation @sle_minion @scope_content_staging
Feature:Install a package on the SLES minion with staging enabled 6m 23s 304ms 8

Scenario:
Pre-requisite: install virgo-dummy-1.0 package, make sure orion-dummy is not present
3s 370ms 3

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 768ms

And I remove package "orion-dummy" from this "sle_minion" without error control 803ms

And I install package "virgo-dummy-1.0" on this "sle_minion" 1s 798ms

Scenario:
Pre-requisite: refresh package list
12s 670ms 3

When I refresh packages list via spacecmd on "sle_minion" 2s 849ms

And I wait until refresh package list on "sle_minion" is finished 7s 409ms

Then spacecmd should show packages "virgo-dummy-1.0" installed on "sle_minion" 2s 411ms

Scenario:
Log in as admin user
462ms 1

Given I am authorized for the "Admin" section 462ms

Scenario:
Pre-requisite: ensure the errata cache is computed before staging tests
6s 527ms 6

When I follow the left menu "Admin > Task Schedules" 122ms

And I follow "errata-cache-default" 1s 367ms

And I follow "errata-cache-bunch" 1s 243ms

Then I click on "Single Run Schedule" 1s 512ms

And I should see a "bunch was scheduled" text 279ms

Then I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 2s 2ms

Scenario:
Enable content staging
1s 171ms 6

When I follow the left menu "Admin > Organizations" 81ms

And I follow first "SUSE Test" 287ms

And I follow first "Configuration" 265ms

And I check "staging_content_enabled" 79ms

And I click on "Update Organization" 390ms

Then I should see a "was successfully updated." text 66ms

Scenario:
Install package in the future and check for staging
2m 54s 584ms 13

Given I am on the Systems overview page of this "sle_minion" 1s 74ms

When I follow "Software" in the content area 67ms

And I follow "Packages" in the content area 83ms

And I follow "Install" in the content area 61ms

And I enter "orion-dummy-1.1-1.1" as the filtered package name 180ms

And I click on the filter button 694ms

And I check row with "orion-dummy-1.1-1.1" and arch of "sle_minion" 56ms

And I click on "Install Packages" 593ms

And I pick 3 minutes from now as schedule time 84ms

And I click on "Confirm" 903ms

Then I should see a "1 package install has been scheduled for" text 61ms

And I wait until the package "orion-dummy-1.1-1.1" has been cached on this "sle_minion" 1m 46s 733ms

And I wait for "orion-dummy-1.1-1.1" to be installed on "sle_minion" 1m 3s 989ms

Scenario:
Install patch in the future and check for staging
3m 153ms 11

When I follow "Software" in the content area 62ms

And I follow "Patches" in the content area 63ms

And I enter "virgo" as the filtered synopsis 39ms

And I click on the filter button 10s 92ms

And I check "virgo-dummy-3456" in the list 78ms

And I click on "Apply Patches" 610ms

And I pick 3 minutes from now as schedule time 84ms

And I click on "Confirm" 993ms

Then I should see a "1 patch update has been scheduled for" text 74ms

And I wait until the package "virgo-dummy-2.0-1.1.noarch" has been cached on this "sle_minion" 50s 427ms

And I wait for "virgo-dummy-2.0-1.1" to be installed on "sle_minion" 1m 57s 625ms

Scenario:
Cleanup: remove virgo-dummy package from SLES minion
4s 362ms 11

When I follow "Software" in the content area 75ms

And I follow "List / Remove" 1s 98ms

And I enter "orion-dummy" as the filtered package name 156ms

And I click on the filter button 868ms

And I check row with "orion-dummy" and arch of "sle_minion" 67ms

And I enter "virgo-dummy" as the filtered package name 44ms

And I click on the filter button 131ms

And I check "virgo-dummy" in the list 59ms

And I click on "Remove Packages" 615ms

And I click on "Confirm" 691ms

And I disable repository "test_repo_rpm_pool" on this "sle_minion" 553ms

@skip_if_github_validation @scope_salt
Feature:Salt package states 2m 7s 517ms 15

Scenario:
Pre-requisite: install old packages on SLES minion
20s 310ms 6

Salt command: salt uyuni-master-suse-minion.sumaci.aws state.highstate

When I apply highstate on "sle_minion" 12s 776ms

And I enable repository "test_repo_rpm_pool" on this "sle_minion" 773ms

And I refresh the metadata for "sle_minion" 839ms

And I install old package "milkyway-dummy-1.0" on this "sle_minion" without error control 1s 764ms

And I install old package "virgo-dummy-1.0" on this "sle_minion" without error control 2s 312ms

And I install old package "andromeda-dummy-1.0" on this "sle_minion" without error control 1s 844ms

Scenario:
Pre-requisite: refresh package list and check installed packages on SLE minion
14s 750ms 3

When I refresh packages list via spacecmd on "sle_minion" 2s 389ms

And I wait until refresh package list on "sle_minion" is finished 9s 932ms

Then spacecmd should show packages "milkyway-dummy-1.0 virgo-dummy-1.0 andromeda-dummy-1.0" installed on "sle_minion" 2s 428ms

Scenario:
Log in as admin user
920ms 1

Given I am authorized for the "Admin" section 920ms

Scenario:
Pre-requisite: ensure the errata cache is computed before software states tests
7s 412ms 11

Given I am on the Systems overview page of this "sle_minion" 1s 237ms

When I follow "Software" in the content area 73ms

And I follow "List / Remove" in the content area 65ms

And I enter "andromeda-dummy" as the filtered package name 180ms

And I click on the filter button until page does contain "andromeda-dummy-1.0" text 288ms

When I follow the left menu "Admin > Task Schedules" 149ms

And I follow "errata-cache-default" 1s 203ms

And I follow "errata-cache-bunch" 611ms

Then I click on "Single Run Schedule" 1s 222ms

And I should see a "bunch was scheduled" text 268ms

Then I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 2s 111ms

Scenario:
Accepted minion has a base channel
1s 284ms 4

Given I am on the Systems overview page of this "sle_minion" 1s 58ms

When I follow "Software" in the content area 61ms

And I follow "Software Channels" in the content area 84ms

Then the system should have a base channel set 80ms

Scenario:
Remove a package through the UI
9s 662ms 13

When I follow "States" in the content area 66ms

And I follow "Packages" 496ms

And I follow "Search" 66ms

And I should see a "Package States" text 64ms

And I list packages with "dummy" 1s 149ms

And I wait until I see "milkyway-dummy" text 431ms

Then "milkyway-dummy" should be installed on "sle_minion" 749ms

And I change the state of "milkyway-dummy" to "Removed" and "" 61ms

Then I should see a "1 Change" text 88ms

And I click save 51ms

Then I wait until I see "Package states have been saved." text 204ms

And I click apply 47ms

And I wait for "milkyway-dummy" to be uninstalled on "sle_minion" 6s 183ms

Scenario:
Install a package through the UI
14s 411ms 13

When I follow "States" in the content area 62ms

And I follow "Packages" 477ms

And I follow "Search" 58ms

And I should see a "Package States" text 72ms

And I list packages with "dummy" 1s 134ms

And I wait until I see "milkyway-dummy" text 454ms

Then "milkyway-dummy" should not be installed on "sle_minion" 412ms

And I change the state of "milkyway-dummy" to "Installed" and "" 44ms

Then I should see a "1 Change" text 90ms

And I click save 44ms

Then I wait until I see "Package states have been saved." text 209ms

And I click apply 39ms

And I wait for "milkyway-dummy" to be installed on "sle_minion" 11s 311ms

Scenario:
Install an already installed package through the UI
4s 489ms 13

When I follow "States" in the content area 64ms

And I follow "Packages" 490ms

And I follow "Search" 59ms

And I should see a "Package States" text 70ms

And I list packages with "dummy" 1s 130ms

And I wait until I see "virgo-dummy" text 473ms

Then "virgo-dummy-1.0" should be installed on "sle_minion" 608ms

And I change the state of "virgo-dummy" to "Installed" and "Any" 108ms

Then I should see a "1 Change" text 100ms

And I click save 52ms

Then I wait until I see "Package states have been saved." text 214ms

And I click apply 48ms

And I wait for "virgo-dummy-1.0" to be installed on "sle_minion" 1s 69ms

Scenario:
Upgrade a package through the UI
20s 86ms 13

When I follow "States" in the content area 72ms

And I follow "Packages" 557ms

And I follow "Search" 65ms

And I should see a "Package States" text 72ms

And I list packages with "dummy" 1s 150ms

And I wait until I see "andromeda-dummy" text 482ms

Then "andromeda-dummy-1.0" should be installed on "sle_minion" 507ms

And I change the state of "andromeda-dummy" to "Installed" and "Latest" 88ms

Then I should see a "1 Change" text 104ms

And I click save 51ms

Then I wait until I see "Package states have been saved." text 223ms

And I click apply 49ms

And I wait for "andromeda-dummy-2.0-1.1" to be installed on "sle_minion" 16s 660ms

Scenario:
Verify the package states
976ms 6

When I follow "States" in the content area 74ms

And I follow "Packages" 489ms

And I should see a "Package States" text 66ms

And I should see a "milkyway-dummy" text 194ms

And I should see a "andromeda-dummy" text 75ms

And I should see a "virgo-dummy" text 74ms

Scenario:
Use Salt presence mechanism on an active minion
6s 441ms 5

When I follow "States" in the content area 57ms

And I follow "Highstate" in the content area 72ms

And I click on "Show full highstate output" 266ms

And I wait for "6" seconds 6s

And I should see a "pkg_removed" or "running as PID" text in element "highstate" 45ms

Scenario:
Use Salt presence mechanism on an unreachable minion
16s 293ms 6

When I follow "States" in the content area 60ms

And I run "pkill salt-minion" on "sle_minion" without error control 440ms

And I run "pkill python.original" on "sle_minion" without error control 422ms

And I follow "Highstate" in the content area 57ms

And I click on "Show full highstate output" 248ms

And I wait until I see "No reply from minion" text 15s 63ms

Scenario:
Cleanup: restart the salt service on SLES minion
983ms 1

When I restart salt-minion on "sle_minion" 983ms

Scenario:
Cleanup: set the package states as unmanaged
3s 751ms 11

Given I am on the Systems overview page of this "sle_minion" 998ms

When I follow "States" in the content area 78ms

And I follow "Packages" 549ms

And I follow "Search" 65ms

And I should see a "Package States" text 70ms

And I list packages with "dummy" 1s 152ms

And I wait until I see "andromeda-dummy" text 462ms

And I change the state of "virgo-dummy" to "Unmanaged" and "" 63ms

And I change the state of "andromeda-dummy" to "Unmanaged" and "" 45ms

And I click save 52ms

Then I wait until I see "Package states have been saved." text 213ms

Scenario:
Cleanup: remove old packages from SLES minion
5s 742ms 5

When I disable repository "test_repo_rpm_pool" on this "sle_minion" 450ms

And I remove package "milkyway-dummy" from this "sle_minion" without error control 1s 424ms

And I remove package "virgo-dummy" from this "sle_minion" without error control 1s 469ms

And I remove package "andromeda-dummy" from this "sle_minion" without error control 1s 476ms

And I refresh the metadata for "sle_minion" 921ms

@skip_if_github_validation @sle_minion @scope_salt
Feature:Verify that Salt mgrcompat state works when the new module.run syntax is enabled 13m 23s 52ms 10

Scenario:
Log in as org admin user
1s 767ms 1

Given I am authorized 1s 767ms

Scenario:
Remove mgrcompat module from minion synced modules and schedule Hardware Refresh
28s 119ms 8

Given I remove "minion/extmods/states/mgrcompat.py" from salt cache on "sle_minion" 740ms

And I remove "minion/extmods/states/__pycache__/mgrcompat*" from salt cache on "sle_minion" 394ms

And I am on the Systems overview page of this "sle_minion" 1s 53ms

When I follow "Hardware" 679ms

And I click on "Schedule Hardware Refresh" 839ms

Then I should see a "You have successfully scheduled a hardware profile refresh" text 116ms

When I wait until event "Hardware List Refresh scheduled" is completed 22s 86ms

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "sle_minion" 2s 208ms

Scenario:
Remove saltutil grain and mgrcompat module from minion and schedule Hardware Refresh
29s 913ms 10

Given I remove "minion/extmods/states/mgrcompat.py" from salt cache on "sle_minion" 400ms

And I remove "minion/extmods/states/__pycache__/mgrcompat*" from salt cache on "sle_minion" 427ms

And I store "grains: {__suse_reserved_saltutil_states_support: False}" into file "custom_grains.conf" in salt minion config directory on "sle_minion" 398ms

And I refresh salt-minion grains on "sle_minion" 1s 911ms

And I am on the Systems overview page of this "sle_minion" 1s 58ms

When I follow "Hardware" 573ms

And I click on "Schedule Hardware Refresh" 757ms

Then I should see a "You have successfully scheduled a hardware profile refresh" text 118ms

When I wait until event "Hardware List Refresh scheduled" is completed 22s 48ms

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "sle_minion" 2s 220ms

Scenario:
Delete SLES minion system profile before mgrcompat test
4m 6s 466ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 3ms

When I follow "Delete System" 475ms

Then I should see a "Confirm System Profile Deletion" text 62ms

When I click on "Delete Profile" 66ms

And I wait until I see "has been deleted" text 4m 3s 739ms

And I wait until Salt client is inactive on "sle_minion" 733ms

Then "sle_minion" should not be registered 386ms

Scenario:
Enable new module.run syntax on the minion and perform registration
1m 45s 780ms 11

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

Given I store "use_superseded: [module.run]" into file "custom_modulerun.conf" in salt minion config directory on "sle_minion" 407ms

When I follow the left menu "Systems > Bootstrapping" 83ms

Then I should see a "Bootstrap Minions" text 66ms

When I enter the hostname of "sle_minion" as "hostname" 145ms

And I enter "22" as "port" 55ms

And I enter "root" as "user" 59ms

And I enter "linux" as "password" 88ms

And I select the hostname of "proxy" from "proxies" if present 79ms

And I click on "Bootstrap" 66ms

And I wait until I see "Bootstrap process initiated." text 22s 848ms

And I wait until onboarding is completed for "sle_minion" 1m 21s 880ms

Scenario:
Check if onboarding for the minion with the new module.run syntax was successful
8s 952ms 3

When I follow the left menu "Systems > System List > All" 139ms

And I wait until I see the name of "sle_minion", refreshing the page 717ms

And I wait until onboarding is completed for "sle_minion" 8s 94ms

Scenario:
Check that installed packages are visible with the new module.run syntax
2s 77ms 4

Given I am on the Systems overview page of this "sle_minion" 996ms

When I follow "Software" in the content area 74ms

And I follow "List / Remove" 888ms

Then I should see a "aaa_base" text 117ms

Scenario:
Check that Hardware Refresh button works on a SLE minion with new module.run syntax
26s 698ms 6

Given I am on the Systems overview page of this "sle_minion" 1s 56ms

And I follow "Hardware" 555ms

And I click on "Schedule Hardware Refresh" 776ms

Then I should see a "You have successfully scheduled a hardware profile refresh" text 118ms

When I wait until event "Hardware List Refresh scheduled" is completed 21s 922ms

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "sle_minion" 2s 270ms

Scenario:
Cleanup: Delete profile of the minion and disable new module.run syntax
4m 7s 322ms 9

Given I am on the Systems overview page of this "sle_minion" 978ms

And I remove "custom_modulerun.conf" from salt minion config directory on "sle_minion" 412ms

And I remove "custom_grains.conf" from salt minion config directory on "sle_minion" 427ms

When I follow "Delete System" 464ms

Then I should see a "Confirm System Profile Deletion" text 61ms

When I click on "Delete Profile" 67ms

And I wait until I see "has been deleted" text 4m 3s 774ms

And I wait until Salt client is inactive on "sle_minion" 772ms

Then "sle_minion" should not be registered 361ms

Scenario:
Cleanup: bootstrap again the minion after mgrcompat tests
1m 45s 954ms 11

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 82ms

Then I should see a "Bootstrap Minions" text 67ms

When I enter the hostname of "sle_minion" as "hostname" 143ms

And I enter "22" as "port" 55ms

And I enter "root" as "user" 59ms

And I enter "linux" as "password" 64ms

And I select "1-SUSE-KEY-x86_64" from "activationKeys" 73ms

And I select the hostname of "proxy" from "proxies" if present 61ms

And I click on "Bootstrap" 61ms

And I wait until I see "Bootstrap process initiated." text 23s 318ms

And I wait until onboarding is completed for "sle_minion" 1m 21s 966ms

@skip_if_github_validation @sle_minion @scope_salt @flaky
Feature:Lock packages on SLES salt minion 3m 32s 717ms 10

Scenario:
Log in as org admin user
2s 130ms 1

Given I am authorized 2s 130ms

Scenario:
Pre-requisite: install packages needed for locking test
4s 474ms 3

When I install package "orion-dummy" on this "sle_minion" 1s 990ms

And I install package "milkyway-dummy" on this "sle_minion" 1s 685ms

And I remove package "hoag-dummy" from this "sle_minion" without error control 798ms

Scenario:
Lock a package on the client
24s 699ms 13

Given I am on the Systems overview page of this "sle_minion" 1s 188ms

When I follow "Software" in the content area 77ms

And I follow "Lock / Unlock" 746ms

And I enter "hoag-dummy-1.1-1.1" as the filtered package name 54ms

And I click on the filter button 613ms

And I check row with "hoag-dummy-1.1-1.1" and arch of "sle_minion" 64ms

And I click on "Lock" 1s 370ms

Then I should see a "Packages has been requested for being locked." text 75ms

When I wait until event "Lock packages scheduled" is completed 18s 810ms

Then "hoag-dummy-1.1-1.1" is locked on "sle_minion" 1s 10ms

When I follow "Software" in the content area 70ms

And I follow "Lock / Unlock" 586ms

Then package "hoag-dummy-1.1-1.1" is reported as locked 30ms

Scenario:
Attempt to install a locked package on the client
28s 460ms 17

Given I am on the Systems overview page of this "sle_minion" 1s 84ms

When I follow "Software" in the content area 59ms

And I follow "Lock / Unlock" 584ms

And package "hoag-dummy-1.1-1.1" is reported as locked 26ms

And I follow "Install" 592ms

And I enter "hoag-dummy-1.1-1.1" as the filtered package name 66ms

And I click on the filter button 622ms

And I check row with "hoag-dummy-1.1-1.1" and arch of "sle_minion" 63ms

And I click on "Install Packages" 590ms

And I click on "Confirm" 826ms

Then I should see a "1 package install has been scheduled for" text 61ms

When I follow "Events" 485ms

And I follow "History" 361ms

And I wait until I see the event "Package Install/Upgrade scheduled" completed during last minute, refreshing the page 22s 884ms

And I follow the event "Package Install/Upgrade scheduled" completed during last minute 61ms

Then the package scheduled is "hoag-dummy-1.1-1.1" 17ms

And the action status is "Failed" 70ms

Scenario:
Unlock a package on the client
34s 491ms 16

Given I am on the Systems overview page of this "sle_minion" 1s 59ms

When I follow "Software" in the content area 72ms

And I follow "Lock / Unlock" 576ms

And package "hoag-dummy-1.1-1.1" is reported as locked 33ms

And I enter "hoag-dummy-1.1-1.1" as the filtered package name 65ms

And I click on the filter button 638ms

And I check row with "hoag-dummy-1.1-1.1" and arch of "sle_minion" 21ms

And I click on "Unlock" 716ms

Then I should see a "Packages has been requested for being unlocked." text 75ms

When I wait until event "Lock packages scheduled" is completed 18s 748ms

Then "hoag-dummy-1.1-1.1" is unlocked on "sle_minion" 1s 55ms

When I follow "Software" in the content area 68ms

And I follow "Lock / Unlock" 645ms

And I enter "hoag-dummy-1.1-1.1" as the filtered package name 62ms

And I click on the filter button 629ms

Then package "hoag-dummy-1.1-1.1" is reported as unlocked 10s 23ms

Scenario:
Schedule a package lock
2s 999ms 9

Given I am on the Systems overview page of this "sle_minion" 1s 37ms

When I follow "Software" in the content area 57ms

And I follow "Lock / Unlock" 503ms

And I enter "hoag-dummy-1.1-1.1" as the filtered package name 53ms

And I click on the filter button 601ms

And I check row with "hoag-dummy-1.1-1.1" and arch of "sle_minion" 65ms

And I click on "Lock" 589ms

Then I should see a "Packages has been requested for being locked." text 79ms

And package "hoag-dummy-1.1-1.1" is reported as pending to be locked 11ms

Scenario:
Schedule another package lock
25s 58ms 16

Given I am on the Systems overview page of this "sle_minion" 1s 148ms

When I follow "Software" in the content area 61ms

And I follow "Lock / Unlock" 505ms

And I enter "milkyway-dummy-2.0-1.1" as the filtered package name 58ms

And I click on the filter button 611ms

When I check row with "milkyway-dummy-2.0-1.1" and arch of "sle_minion" 63ms

And I click on "Lock" 1s 191ms

Then I should see a "Packages has been requested for being locked." text 84ms

And package "milkyway-dummy-2.0-1.1" is reported as pending to be locked 11ms

When I wait until event "Lock packages scheduled" is completed 18s 759ms

Then "hoag-dummy-1.1-1.1" is locked on "sle_minion" 1s 54ms

And "milkyway-dummy-2.0-1.1" is locked on "sle_minion" 803ms

When I follow "Software" in the content area 72ms

And I follow "Lock / Unlock" 570ms

Then package "hoag-dummy-1.1-1.1" is reported as locked 28ms

And package "milkyway-dummy-2.0-1.1" is reported as locked 33ms

Scenario:
Mix package locks and unlock events
38s 540ms 32

Given I am on the Systems overview page of this "sle_minion" 1s 32ms

When I follow "Software" in the content area 59ms

And I follow "Lock / Unlock" 585ms

And package "hoag-dummy-1.1-1.1" is reported as locked 22ms

And package "milkyway-dummy-2.0-1.1" is reported as locked 28ms

And I enter "orion-dummy-1.1-1.1" as the filtered package name 67ms

And I click on the filter button 613ms

When I check row with "orion-dummy-1.1-1.1" and arch of "sle_minion" 64ms

And I click on "Lock" 584ms

Then I should see a "Packages has been requested for being locked." text 79ms

And package "orion-dummy-1.1-1.1" is reported as pending to be locked 11ms

When I follow "Lock / Unlock" 516ms

And I enter "hoag-dummy-1.1-1.1" as the filtered package name 60ms

And I click on the filter button 755ms

And I uncheck row with "hoag-dummy-1.1-1.1" and arch of "sle_minion" 59ms

And I enter "milkyway-dummy-2.0-1.1" as the filtered package name 55ms

And I click on the filter button 134ms

And I check row with "milkyway-dummy-2.0-1.1" and arch of "sle_minion" 23ms

And I click on "Unlock" 1s 39ms

Then I should see a "Packages has been requested for being unlocked." text 76ms

And package "milkyway-dummy-2.0-1.1" is reported as pending to be unlocked 11ms

When I wait until event "Lock packages scheduled" is completed 18s 804ms

Then "hoag-dummy-1.1-1.1" is locked on "sle_minion" 1s 43ms

And "milkyway-dummy-2.0-1.1" is unlocked on "sle_minion" 669ms

And "orion-dummy-1.1-1.1" is locked on "sle_minion" 664ms

When I follow "Software" in the content area 72ms

And I follow "Lock / Unlock" 610ms

Then package "hoag-dummy-1.1-1.1" is reported as locked 27ms

And package "orion-dummy-1.1-1.1" is reported as locked 31ms

And I enter "milkyway-dummy-2.0-1.1" as the filtered package name 78ms

And I click on the filter button 632ms

And package "milkyway-dummy-2.0-1.1" is reported as unlocked 10s 22ms

Scenario:
Mix package locks and unlock events part 2
48s 508ms 18

Given I am on the Systems overview page of this "sle_minion" 1s 37ms

And I follow "Software" in the content area 75ms

And I follow "Lock / Unlock" 598ms

When I click on "Select All" 594ms

And I click on "Unlock" 849ms

Then I should see a "Packages has been requested for being unlocked." text 128ms

And only packages "hoag-dummy-1.1-1.1, orion-dummy-1.1-1.1" are reported as pending to be unlocked 36ms

When I wait until event "Lock packages scheduled" is completed 21s 913ms

Then "hoag-dummy-1.1-1.1" is unlocked on "sle_minion" 1s 78ms

And "orion-dummy-1.1-1.1" is unlocked on "sle_minion" 722ms

When I follow "Software" in the content area 61ms

And I follow "Lock / Unlock" 513ms

And I enter "hoag-dummy-1.1-1.1" as the filtered package name 68ms

And I click on the filter button 609ms

Then package "hoag-dummy-1.1-1.1" is reported as unlocked 10s 15ms

And I enter "orion-dummy-1.1-1.1" as the filtered package name 55ms

And I click on the filter button 133ms

And package "orion-dummy-1.1-1.1" is reported as unlocked 10s 18ms

Scenario:
Cleanup: remove packages after testing locks
3s 353ms 2

Then I remove package "orion-dummy" from this "sle_minion" 1s 810ms

And I remove package "milkyway-dummy" from this "sle_minion" 1s 543ms

@scope_onboarding
Feature:Empty minion profile operations 1m 9s 516ms 8

Scenario:
Log in as org admin user
2s 62ms 1

Given I am authorized 2s 62ms

Scenario:
Create an empty minion profile with HW address via API
1s 295ms 1

When I call system.create_system_profile() with name "empty-profile" and HW address "00:11:22:33:44:55" 1s 295ms

Scenario:
Create an empty minion profile with hostname via API
603ms 1

When I call system.create_system_profile() with name "empty-profile-hostname" and hostname "min-retail.mgr.suse.de" 603ms

Scenario:
Check the created empty minion profiles in Unprovisioned Systems page
455ms 4

And I follow the left menu "System > System List > Unprovisioned Systems" 216ms

And I wait until I see "empty-profile" text, refreshing the page 84ms

And I wait until I see "00:11:22:33:44:55" text 77ms

And I wait until I see "empty-profile-hostname" text 76ms

Scenario:
Check the empty profiles has the hostname set
758ms 3

And I follow the left menu "System > System List > Unprovisioned Systems" 72ms

And I follow "empty-profile-hostname" 610ms

Then I wait until I see "min-retail.mgr.suse.de" text, refreshing the page 76ms

Scenario:
Check the empty minion profiles visible via API
408ms 3

When I call system.list_empty_system_profiles() 408ms

Then "empty-profile" should be present in the result < 1ms

And "empty-profile-hostname" should be present in the result < 1ms

Scenario:
Cleanup: Delete first empty minion profile
59s 893ms 7

When I follow the left menu "Systems > System List" 68ms

And I wait until I see the "empty-profile" system, refreshing the page 57s 723ms

And I follow "empty-profile" 639ms

And I follow "Delete System" 486ms

Then I should see a "Confirm System Profile Deletion" text 59ms

When I click on "Delete Profile" 77ms

And I wait until I see "has been deleted" text 838ms

Scenario:
Cleanup: Delete second empty minion profiles
4s 38ms 7

When I follow the left menu "Systems > System List" 77ms

And I wait until I see the "empty-profile-hostname" system, refreshing the page 722ms

And I follow "empty-profile-hostname" 563ms

And I follow "Delete System" 487ms

Then I should see a "Confirm System Profile Deletion" text 59ms

When I click on "Delete Profile" 54ms

And I wait until I see "has been deleted" text 2s 75ms

@scope_onboarding @custom_download_endpoint
Feature:Repos file generation based on custom pillar data 1m 27s 929ms 9 3

Scenario:
Log in as org admin user
1s 736ms 1

Given I am authorized 1s 736ms

@susemanager
Scenario:
Select the channels of the SLES minion
< 1ms 13

Given I am on the Systems overview page of this "sle_minion" 0s

When I follow "Software" in the content area 0s

And I follow "Software Channels" in the content area 0s

And I wait until I do not see "Loading..." text 0s

And I check radio button "SLE-Product-SLES15-SP7-Pool for x86_64" 0s

And I wait until I see "SLE-Module-Basesystem15-SP7-Pool for x86_64" text 0s

And I uncheck "SLE-Module-Basesystem15-SP7-Pool for x86_64" 0s

And I click on "Next" 0s

Then I should see a "Confirm Software Channel Change" text 0s

When I click on "Confirm" 0s

Then I should see a "Changing the channels has been scheduled." text 0s

When I follow "scheduled" in the content area 0s

And I wait until I see "1 system successfully completed this action." text, refreshing the page 0s

@uyuni
Scenario:
Select the channels of the openSUSE minion
19s 512ms 11

Warning: Radio button 'openSUSE Tumbleweed (x86_64)' is already checked

Given I am on the Systems overview page of this "sle_minion" 1s 638ms

When I follow "Software" in the content area 71ms

And I follow "Software Channels" in the content area 65ms

And I wait until I do not see "Loading..." text 70ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 245ms

And I click on "Next" 400ms

Then I should see a "Confirm Software Channel Change" text 70ms

When I click on "Confirm" 75ms

Then I should see a "Changing the channels has been scheduled." text 408ms

When I follow "scheduled" in the content area 78ms

And I wait until I see "1 system successfully completed this action." text, refreshing the page 16s 387ms

Scenario:
Check the default RPM download point values
2s 359ms 3

Real protocol: https host: uyuni-master-proxy.sumaci.aws port: 443
Expected protocol: https host: uyuni-master-proxy.sumaci.aws port: 443

Given I am on the Systems overview page of this "sle_minion" 1s 162ms

Then the susemanager repo file should exist on the "sle_minion" 794ms

And the repo file should contain the normal download endpoint on the "sle_minion" 402ms

Scenario:
Set the custom RPM download point
6s 940ms 5

Given I am on the Systems overview page of this "sle_minion" 1s 23ms

When I install a salt pillar top file for "pkg_endpoint" with target "*" on the server 2s 164ms

And I wait for "1" seconds 1s

And I install the package download endpoint pillar file on the server 641ms

And I refresh the pillar data 2s 110ms

@susemanager
Scenario:
Select the channels of the SLES minion again so new RPM end point will be taken into account
< 1ms 10

When I follow "Software" in the content area 0s

And I follow "Software Channels" in the content area 0s

And I wait until I do not see "Loading..." text 0s

And I wait until I see "SLE-Module-Basesystem15-SP7-Pool for x86_64" text 0s

And I click on "Next" 0s

Then I should see a "Confirm Software Channel Change" text 0s

When I click on "Confirm" 0s

Then I should see a "Changing the channels has been scheduled." text 0s

When I follow "scheduled" in the content area 0s

And I wait until I see "1 system successfully completed this action." text, refreshing the page 0s

@uyuni
Scenario:
Select the channels of the openSUSE minion again so new RPM end point will be taken into account
31s 293ms 10

Warning: Radio button 'openSUSE Tumbleweed (x86_64)' is already checked

When I follow "Software" in the content area 64ms

And I follow "Software Channels" in the content area 67ms

And I wait until I do not see "Loading..." text 74ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 153ms

And I click on "Next" 394ms

Then I should see a "Confirm Software Channel Change" text 72ms

When I click on "Confirm" 76ms

Then I should see a "Changing the channels has been scheduled." text 425ms

When I follow "scheduled" in the content area 73ms

And I wait until I see "1 system successfully completed this action." text, refreshing the page 29s 891ms

Scenario:
Check the channel.repo file to see the custom RPM download point
2s 243ms 3

Real protocol: ftp host: mirror.sumaci.aws port: 445
Expected protocol: ftp host: mirror.sumaci.aws port: 445

Given I am on the Systems overview page of this "sle_minion" 1s 60ms

Then the susemanager repo file should exist on the "sle_minion" 764ms

And the repo file should contain the custom download endpoint on the "sle_minion" 417ms

Scenario:
Cleanup: remove the custom RPM download point
4s 853ms 3

When I delete the package download endpoint pillar file from the server 1s 4ms

And I install a salt pillar top file for "disable_local_repos_off, salt_bundle_config" with target "*" on the server 1s 739ms

And I refresh the pillar data 2s 109ms

@susemanager
Scenario:
Cleanup: select the channels of the SLES minion as before
< 1ms 15

When I follow "Software" in the content area 0s

And I follow "Software Channels" in the content area 0s

And I wait until I do not see "Loading..." text 0s

And I check radio button "SLE-Product-SLES15-SP7-Pool for x86_64" 0s

And I wait until I see "SLE15-SP7-Installer-Updates for x86_64" text 0s

And I include the recommended child channels 0s

And I check "SLE-Module-DevTools15-SP7-Pool for x86_64" 0s

And I check "Fake-RPM-SUSE-Channel" 0s

And I check "SLE-Module-Containers15-SP7-Pool for x86_64" 0s

And I click on "Next" 0s

Then I should see a "Confirm Software Channel Change" text 0s

When I click on "Confirm" 0s

Then I should see a "Changing the channels has been scheduled." text 0s

When I follow "scheduled" in the content area 0s

And I wait until I see "1 system successfully completed this action." text, refreshing the page 0s

@uyuni
Scenario:
Cleanup: select the channels of the openSUSE minion as before
17s 800ms 12

Warning: Radio button 'openSUSE Tumbleweed (x86_64)' is already checked

When I follow "Software" in the content area 80ms

And I follow "Software Channels" in the content area 65ms

And I wait until I do not see "Loading..." text 66ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 195ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 330ms

And I check "Fake-RPM-SUSE-Channel" 38ms

And I click on "Next" 62ms

Then I should see a "Confirm Software Channel Change" text 67ms

When I click on "Confirm" 75ms

Then I should see a "Changing the channels has been scheduled." text 310ms

When I follow "scheduled" in the content area 74ms

And I wait until I see "1 system successfully completed this action." text, refreshing the page 16s 432ms

Scenario:
Cleanup: recheck the default RPM download point values
1s 191ms 2

Real protocol: https host: uyuni-master-proxy.sumaci.aws port: 443
Expected protocol: https host: uyuni-master-proxy.sumaci.aws port: 443

Then the susemanager repo file should exist on the "sle_minion" 774ms

And the repo file should contain the normal download endpoint on the "sle_minion" 416ms

@skip_if_github_validation @sle_minion @scope_action_chains @flaky
Feature:Action chains on Salt minions 9m 8s 23ms 33

Scenario:
Log in as admin user
1s 796ms 1

Given I am authorized for the "Admin" section 1s 796ms

Scenario:
Pre-requisite: downgrade repositories to lower version on Salt minion
6s 900ms 6

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 782ms

And I remove package "andromeda-dummy" from this "sle_minion" without error control 800ms

And I remove package "virgo-dummy" from this "sle_minion" without error control 804ms

And I install package "milkyway-dummy" on this "sle_minion" without error control 1s 681ms

And I install old package "andromeda-dummy-1.0" on this "sle_minion" 1s 686ms

And I refresh the metadata for "sle_minion" 1s 145ms

Scenario:
Pre-requisite: refresh package list and check installed packages after downgrade on SLE minion
12s 773ms 3

When I refresh packages list via spacecmd on "sle_minion" 2s 919ms

And I wait until refresh package list on "sle_minion" is finished 7s 341ms

Then spacecmd should show packages "milkyway-dummy andromeda-dummy-1.0" installed on "sle_minion" 2s 512ms

Scenario:
Pre-requisite: wait until downgrade is finished on SLE minion
1s 652ms 5

Given I am on the Systems overview page of this "sle_minion" 1s 11ms

When I follow "Software" in the content area 71ms

And I follow "List / Remove" in the content area 67ms

And I enter "andromeda-dummy" as the filtered package name 216ms

And I click on the filter button until page does contain "andromeda-dummy-1.0" text 285ms

Scenario:
Pre-requisite: ensure the errata cache is computed before testing on Salt minion
28s 698ms 6

When I follow the left menu "Admin > Task Schedules" 147ms

And I follow "errata-cache-default" 1s 208ms

And I follow "errata-cache-bunch" 311ms

And I click on "Single Run Schedule" 1s 544ms

Then I should see a "bunch was scheduled" text 272ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 25s 212ms

Scenario:
Create a custom action chain for the Salt minion
578ms 3

When I create an action chain with label "salt_minion_action_chain" via API 349ms

And I follow the left menu "Schedule > Action Chains" 163ms

Then I should see a "salt_minion_action_chain" text 65ms

Scenario:
Add a patch installation to the action chain on Salt minion
22s 821ms 10

Given I am on the Systems overview page of this "sle_minion" 947ms

When I follow "Software" in the content area 71ms

And I follow "Patches" in the content area 65ms

And I enter "andromeda" as the filtered synopsis 55ms

And I click on the filter button 10s 132ms

And I check "andromeda-dummy-6789" in the list 62ms

And I click on "Apply Patches" 643ms

And I check radio button "schedule-by-action-chain" 10s 62ms

And I click on "Confirm" 700ms

Then I should see a "Action has been successfully added to the Action Chain" text 80ms

Scenario:
Add a package removal to the action chain on Salt minion
13s 494ms 10

Given I am on the Systems overview page of this "sle_minion" 988ms

When I follow "Software" in the content area 76ms

And I follow "List / Remove" in the content area 82ms

And I enter "milkyway-dummy" as the filtered package name 161ms

And I click on the filter button 812ms

And I check row with "milkyway-dummy" and arch of "sle_minion" 58ms

And I click on "Remove Packages" 597ms

And I check radio button "schedule-by-action-chain" 10s 60ms

And I click on "Confirm" 592ms

Then I should see a "Action has been successfully added to the Action Chain" text 63ms

Scenario:
Add a package installation to an action chain on Salt minion
12s 379ms 9

When I follow "Software" in the content area 68ms

And I follow "Install New Packages" in the content area 67ms

And I enter "virgo-dummy" as the filtered package name 152ms

And I click on the filter button 705ms

And I check "virgo-dummy" in the list 52ms

And I click on "Install Packages" 601ms

And I check radio button "schedule-by-action-chain" 10s 70ms

And I click on "Confirm" 594ms

Then I should see a "Action has been successfully added to the Action Chain" text 65ms

Scenario:
Create a configuration channel for testing action chain on Salt minion
720ms 7

When I follow the left menu "Configuration > Channels" 123ms

And I follow "Create Config Channel" 265ms

And I enter "Action Chain Channel" as "cofName" 70ms

And I enter "actionchainchannel" as "cofLabel" 63ms

And I enter "This is a test channel" as "cofDescription" 66ms

And I click on "Create Config Channel" 66ms

Then I should see a "Action Chain Channel" text 64ms

Scenario:
Add a configuration file to configuration channel for testing action chain on Salt minion
1s 721ms 8

When I follow the left menu "Configuration > Channels" 71ms

And I follow "Action Chain Channel" 440ms

And I follow "Create Configuration File or Directory" 317ms

And I enter "/etc/action-chain.cnf" as "cffPath" 71ms

And I enter "Testchain=YES_PLEASE" in the editor 7ms

And I click on "Create Configuration File" 700ms

Then I should see a "Revision 1 of /etc/action-chain.cnf from channel Action Chain Channel" text 95ms

And I should see a "Update Configuration File" button 17ms

Scenario:
Download the configuration file from configuration channel
2s 16ms 7

When I follow the left menu "Configuration > Channels" 65ms

And I follow "Action Chain Channel" 434ms

And I follow "List/Remove Files" 373ms

And I follow "/etc/action-chain.cnf" 403ms

And I follow "Download File" 212ms

And I wait until file "/tmp/downloads/action-chain.cnf" exists on "localhost" 178ms

Then file "/tmp/downloads/action-chain.cnf" should contain "Testchain=YES_PLEASE" on "localhost" 349ms

Scenario:
Subscribe system to configuration channel for testing action chain on Salt minion
2s 683ms 8

Given I am on the Systems overview page of this "sle_minion" 960ms

When I follow "Configuration" in the content area 73ms

And I follow "Manage Configuration Channels" in the content area 63ms

And I follow first "Subscribe to Channels" in the content area 65ms

And I check "Action Chain Channel" in the list 58ms

And I click on "Continue" 611ms

And I click on "Update Channel Rankings" 771ms

Then I should see a "Channel Subscriptions successfully changed for" text 79ms

Scenario:
Add a configuration file deployment to the action chain on Salt minion
12s 829ms 9

When I follow the left menu "Configuration > Channels" 112ms

And I follow "Action Chain Channel" 420ms

And I follow "Deploy Files" in the content area 66ms

And I click on "Deploy All Files" 639ms

And I check the "sle_minion" client 59ms

And I click on "Confirm & Deploy to Selected Systems" 692ms

And I check radio button "schedule-by-action-chain" 10s 74ms

And I click on "Deploy Files to Selected Systems" 693ms

Then I should see a "Action has been successfully added to the Action Chain" text 67ms

Scenario:
Add apply highstate to action chain on Salt minion
11s 189ms 4

Given I am on the Systems overview page of this "sle_minion" 1s 4ms

When I follow "States" in the content area 69ms

And I check radio button "schedule-by-action-chain" 10s 55ms

And I click on "Apply Highstate" 59ms

Scenario:
Add a reboot action to the action chain on Salt minion
12s 291ms 5

Given I am on the Systems overview page of this "sle_minion" 964ms

When I follow first "Schedule System Reboot" 391ms

And I check radio button "schedule-by-action-chain" 10s 74ms

And I click on "Reboot system" 768ms

Then I should see a "Action has been successfully added to the Action Chain" text 91ms

Scenario:
Add a remote command to the action chain on Salt minion
10s 911ms 6

When I follow "Details" in the content area 83ms

And I follow "Remote Command" in the content area 87ms

And I enter as remote command this script in #!/bin/bash touch /tmp/action_chain_one_system_done 72ms

And I check radio button "schedule-by-action-chain" 10s 74ms

And I click on "Schedule" 510ms

Then I should see a "Action has been successfully added to the Action Chain" text 82ms

Scenario:
Verify the action chain list on Salt minion
1s 718ms 10

When I follow "Schedule" 330ms

And I follow "Action Chains" 265ms

And I follow "salt_minion_action_chain" 528ms

Then I should see a "1. Apply patch(es) andromeda-dummy-6789 on 1 system" text 95ms

And I should see a "2. Remove milkyway-dummy from 1 system" text 88ms

And I should see a "3. Install or update virgo-dummy on 1 system" text 83ms

And I should see a text like "4. Deploy.*/etc/action-chain.cnf.*to 1 system" 79ms

And I should see a "5. Apply Highstate" text 79ms

And I should see a "6. Reboot 1 system" text 82ms

And I should see a "7. Run a remote command on 1 system" text 85ms

Scenario:
Check that a different user cannot see the action chain for Salt minion
2s 863ms 4

Given I am authorized as "testing" with password "testing" 1s 723ms

When I follow "Schedule" 877ms

And I follow "Action Chains" 254ms

Then I should not see a "salt_minion_action_chain" link 8ms

Scenario:
Execute the action chain from the web UI on Salt minion
4m 30s 390ms 9

Given I am authorized for the "Admin" section 1s 760ms

When I am on the Systems overview page of this "sle_minion" 1s 758ms

And I follow "Schedule" 385ms

And I follow "Action Chains" 282ms

And I follow "salt_minion_action_chain" 302ms

And I click on "Save and Schedule" 58ms

Then I should see a "Action Chain salt_minion_action_chain has been scheduled for execution." text 800ms

When I wait for "virgo-dummy" to be installed on "sle_minion" 24s 544ms

And I wait at most 300 seconds until file "/tmp/action_chain_one_system_done" exists on "sle_minion" 4m 496ms

Scenario:
Create a custom action chain for the Salt minion
512ms 3

When I create an action chain with label "salt_minion_action_chain_to_delete" via API 367ms

And I follow the left menu "Schedule > Action Chains" 76ms

Then I should see a "salt_minion_action_chain_to_delete" text 67ms

Scenario:
Add a remote command to the action chain on Salt minion
11s 755ms 6

Given I am on the Systems overview page of this "sle_minion" 981ms

When I follow "Remote Command" 505ms

And I enter as remote command this script in #!/bin/bash uptime 51ms

And I check radio button "schedule-by-action-chain" 10s 69ms

And I click on "Schedule" 59ms

Then I should see a "Action has been successfully added to the Action Chain" text 87ms

Scenario:
Delete the action chain for Salt minion
1s 293ms 5

When I follow "Schedule" 258ms

And I follow "Action Chains" 236ms

And I follow "salt_minion_action_chain_to_delete" 322ms

And I follow "Delete Action Chains" in the content area 79ms

And I click on "Delete" 397ms

Scenario:
Downgrade again repositories to lower version on Salt minion
7s 582ms 4

When I remove package "andromeda-dummy" from this "sle_minion" without error control 2s 445ms

And I remove package "virgo-dummy" from this "sle_minion" without error control 1s 520ms

And I install package "milkyway-dummy" on this "sle_minion" without error control 1s 734ms

And I install old package "andromeda-dummy-1.0" on this "sle_minion" 1s 883ms

Scenario:
Refresh package list and check installed packages after second downgrade on SLE minion
12s 663ms 3

When I refresh packages list via spacecmd on "sle_minion" 2s 874ms

And I wait until refresh package list on "sle_minion" is finished 7s 312ms

Then spacecmd should show packages "milkyway-dummy andromeda-dummy-1.0" installed on "sle_minion" 2s 476ms

Scenario:
Ensure again the errata cache is computed before testing on Salt minion
58s 451ms 6

When I follow the left menu "Admin > Task Schedules" 139ms

And I follow "errata-cache-default" 376ms

And I follow "errata-cache-bunch" 1s 306ms

And I click on "Single Run Schedule" 1s 259ms

Then I should see a "bunch was scheduled" text 273ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 55s 95ms

Scenario:
Add operations to the action chain via API for Salt minions
6s 854ms 11

Running actions:
- System reboot
- Run an arbitrary script
- Package Install/Upgrade
- Package Install/Upgrade
- Package Removal
- Removed "System reboot" action
- Removed "Run an arbitrary script" action
- Removed "Package Install/Upgrade" action
- Removed "Package Install/Upgrade" action
- Removed "Package Removal" action

Given I want to operate on this "sle_minion" 337ms

When I create an action chain with label "salt_minion_api_chain" via API 347ms

And I add a package install to the action chain via API 785ms

And I add a package removal to the action chain via API 797ms

And I add a package upgrade to the action chain via API 827ms

And I add the script "exit 1;" to the action chain via API 356ms

And I add a system reboot to the action chain via API 362ms

Then I should be able to see all these actions in the action chain via API 331ms

When I remove each action within the chain via API 2s 40ms

Then the current action chain should be empty 333ms

And I delete the action chain via API 334ms

Scenario:
Run an action chain via API on Salt minion
8s 364ms 12

Running actions:
- Run an arbitrary script
- Run an arbitrary script
- Run an arbitrary script
- Run an arbitrary script

Given I want to operate on this "sle_minion" 328ms

When I create an action chain with label "salt_minion_multiple_scripts" via API 333ms

And I add the script "echo -n 1 >> /tmp/action_chain.log" to the action chain via API 349ms

And I add the script "echo -n 2 >> /tmp/action_chain.log" to the action chain via API 354ms

And I add the script "echo -n 3 >> /tmp/action_chain.log" to the action chain via API 352ms

And I add the script "touch /tmp/action_chain_done" to the action chain via API 376ms

Then I should be able to see all these actions in the action chain via API 345ms

When I schedule the action chain via API 434ms

And I wait until there are no more action chains listed via API 358ms

And I wait until file "/tmp/action_chain_done" exists on "sle_minion" 3s 954ms

Then file "/tmp/action_chain.log" should contain "123" on "sle_minion" 838ms

When I wait until there are no more scheduled actions listed via API 337ms

Scenario:
Cleanup: remove Salt minion from configuration channel
1s 550ms 6

When I follow the left menu "Configuration > Channels" 161ms

And I follow "Action Chain Channel" 521ms

And I follow "Systems" in the content area 67ms

And I check the "sle_minion" client 71ms

And I click on "Unsubscribe systems" 665ms

Then I should see a "Successfully unsubscribed 1 system(s)." text 63ms

Scenario:
Cleanup: remove configuration channel for Salt minion
1s 205ms 4

When I follow the left menu "Configuration > Channels" 64ms

And I follow "Action Chain Channel" 359ms

And I follow "Delete Channel" 294ms

And I click on "Delete Config Channel" 487ms

Scenario:
Cleanup: remove packages and repository used in action chain for Salt minion
4s 826ms 4

When I remove package "andromeda-dummy" from this "sle_minion" without error control 1s 615ms

And I remove package "virgo-dummy" from this "sle_minion" without error control 834ms

And I remove package "milkyway-dummy" from this "sle_minion" without error control 1s 689ms

And I disable repository "test_repo_rpm_pool" on this "sle_minion" without error control 687ms

Scenario:
Cleanup: remove temporary files for testing action chains on Salt minion
2s 365ms 4

When I run "rm -f /tmp/action_chain.log" on "sle_minion" without error control 678ms

And I run "rm -f /tmp/action_chain_done" on "sle_minion" without error control 697ms

And I run "rm -f /etc/action-chain.cnf" on "sle_minion" without error control 496ms

And I run "rm -f /tmp/action_chain_one_system_done" on "sle_minion" without error control 493ms

Scenario:
Cleanup: remove downloaded files
163ms 1

When I run "rm -f /tmp/downloads/action-chain.cnf" on "localhost" without error control 163ms

@skip_if_github_validation @ssh_minion @scope_action_chains @scope_salt_ssh
Feature:Salt SSH action chain 10m 53s 621ms 30

Scenario:
Log in as org admin user
428ms 1

Given I am authorized for the "Admin" section 428ms

Scenario:
Pre-requisite: downgrade repositories to lower version on SSH minion
6s 797ms 6

When I enable repository "test_repo_rpm_pool" on this "ssh_minion" 833ms

And I remove package "andromeda-dummy" from this "ssh_minion" without error control 1s 286ms

And I remove package "virgo-dummy" from this "ssh_minion" without error control 1s 270ms

And I install package "milkyway-dummy" on this "ssh_minion" without error control 1s 230ms

And I install old package "andromeda-dummy-1.0" on this "ssh_minion" 1s 302ms

And I refresh the metadata for "ssh_minion" 873ms

Scenario:
Pre-requisite: refresh package list and check newly installed packages on SSH minion
26s 883ms 3

When I refresh packages list via spacecmd on "ssh_minion" 2s 805ms

And I wait until refresh package list on "ssh_minion" is finished 21s 692ms

Then spacecmd should show packages "milkyway-dummy andromeda-dummy-1.0" installed on "ssh_minion" 2s 385ms

Scenario:
Pre-requisite: wait until downgrade is finished on SSH minion
1s 622ms 5

Given I am on the Systems overview page of this "ssh_minion" 988ms

When I follow "Software" in the content area 71ms

And I follow "List / Remove" in the content area 65ms

And I enter "andromeda-dummy" as the filtered package name 220ms

And I click on the filter button until page does contain "andromeda-dummy-1.0" text 276ms

Scenario:
Pre-requisite: ensure the errata cache is computed before testing on SSH minion
46s 125ms 6

When I follow the left menu "Admin > Task Schedules" 142ms

And I follow "errata-cache-default" 1s 212ms

And I follow "errata-cache-bunch" 1s 266ms

And I click on "Single Run Schedule" 1s 543ms

Then I should see a "bunch was scheduled" text 265ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 41s 694ms

Scenario:
Create a custom action chain for the SSH minion
572ms 3

When I create an action chain with label "minssh_action_chain" via API 355ms

And I follow the left menu "Schedule > Action Chains" 151ms

Then I wait until I see "minssh_action_chain" text 65ms

Scenario:
Add a patch installation to the action chain on SSH minion
22s 917ms 10

Given I am on the Systems overview page of this "ssh_minion" 1s 42ms

When I follow "Software" in the content area 70ms

And I follow "Patches" in the content area 64ms

And I enter "andromeda" as the filtered synopsis 55ms

And I click on the filter button 10s 147ms

And I check "andromeda-dummy-6789" in the list 62ms

And I click on "Apply Patches" 634ms

And I check radio button "schedule-by-action-chain" 10s 66ms

And I click on "Confirm" 690ms

Then I should see a "Action has been successfully added to the Action Chain" text 82ms

Scenario:
Add a package removal to the action chain on SSH minion
12s 529ms 9

When I follow "Software" in the content area 72ms

And I follow "List / Remove" in the content area 64ms

And I enter "milkyway-dummy" as the filtered package name 148ms

And I click on the filter button 854ms

And I check row with "milkyway-dummy" and arch of "ssh_minion" 59ms

And I click on "Remove Packages" 585ms

And I check radio button "schedule-by-action-chain" 10s 80ms

And I click on "Confirm" 601ms

Then I should see a "Action has been successfully added to the Action Chain" text 63ms

Scenario:
Add a package installation to an action chain on SSH minion
12s 213ms 9

When I follow "Software" in the content area 69ms

And I follow "Install New Packages" in the content area 65ms

And I enter "virgo-dummy" as the filtered package name 96ms

And I click on the filter button 620ms

And I check "virgo-dummy" in the list 53ms

And I click on "Install Packages" 590ms

And I check radio button "schedule-by-action-chain" 10s 63ms

And I click on "Confirm" 590ms

Then I should see a "Action has been successfully added to the Action Chain" text 63ms

Scenario:
Create a configuration channel for testing action chain on SSH minion
723ms 7

When I follow the left menu "Configuration > Channels" 123ms

And I follow "Create Config Channel" 267ms

And I enter "Action Chain Channel" as "cofName" 68ms

And I enter "actionchainchannel" as "cofLabel" 64ms

And I enter "This is a test channel" as "cofDescription" 68ms

And I click on "Create Config Channel" 65ms

Then I should see a "Action Chain Channel" text 65ms

Scenario:
Add a configuration file to configuration channel for testing action chain on SSH minion
1s 543ms 8

When I follow the left menu "Configuration > Channels" 65ms

And I follow "Action Chain Channel" 354ms

And I follow "Create Configuration File or Directory" 333ms

And I enter "/etc/action-chain.cnf" as "cffPath" 73ms

And I enter "Testchain=YES_PLEASE" in the editor 5ms

And I click on "Create Configuration File" 66ms

Then I should see a "Revision 1 of /etc/action-chain.cnf from channel Action Chain Channel" text 626ms

And I should see a "Update Configuration File" button 18ms

Scenario:
Subscribe system to configuration channel for testing action chain on SSH minion
2s 743ms 8

Given I am on the Systems overview page of this "ssh_minion" 982ms

When I follow "Configuration" in the content area 76ms

And I follow "Manage Configuration Channels" in the content area 66ms

And I follow first "Subscribe to Channels" in the content area 64ms

And I check "Action Chain Channel" in the list 57ms

And I click on "Continue" 603ms

And I click on "Update Channel Rankings" 814ms

Then I should see a "Channel Subscriptions successfully changed for" text 78ms

Scenario:
Add a configuration file deployment to the action chain on SSH minion
12s 747ms 9

When I follow the left menu "Configuration > Channels" 113ms

And I follow "Action Chain Channel" 415ms

And I follow "Deploy Files" in the content area 65ms

And I click on "Deploy All Files" 581ms

And I check the "ssh_minion" client 59ms

And I click on "Confirm & Deploy to Selected Systems" 672ms

And I check radio button "schedule-by-action-chain" 10s 69ms

And I click on "Deploy Files to Selected Systems" 688ms

Then I should see a "Action has been successfully added to the Action Chain" text 81ms

Scenario:
Add apply highstate to action chain on SSH minion
11s 279ms 4

Given I am on the Systems overview page of this "ssh_minion" 1s 59ms

When I follow "States" in the content area 69ms

And I check radio button "schedule-by-action-chain" 10s 69ms

And I click on "Apply Highstate" 80ms

Scenario:
Add a reboot action to the action chain on SSH minion
12s 433ms 5

Given I am on the Systems overview page of this "ssh_minion" 960ms

When I follow first "Schedule System Reboot" 479ms

And I check radio button "schedule-by-action-chain" 10s 67ms

And I click on "Reboot system" 833ms

Then I should see a "Action has been successfully added to the Action Chain" text 93ms

Scenario:
Add a remote command to the action chain on SSH minion
10s 926ms 6

When I follow "Details" in the content area 84ms

When I follow "Remote Command" in the content area 67ms

And I enter as remote command this script in #!/bin/bash touch /tmp/action_chain_one_system_done 68ms

And I check radio button "schedule-by-action-chain" 10s 75ms

And I click on "Schedule" 545ms

Then I should see a "Action has been successfully added to the Action Chain" text 85ms

Scenario:
Verify the action chain list on SSH minion
1s 34ms 9

When I follow the left menu "Schedule > Action Chains" 130ms

And I follow "minssh_action_chain" 310ms

Then I should see a "1. Apply patch(es) andromeda-dummy-6789 on 1 system" text 86ms

And I should see a "2. Remove milkyway-dummy from 1 system" text 85ms

And I should see a "3. Install or update virgo-dummy on 1 system" text 92ms

And I should see a text like "4. Deploy.*/etc/action-chain.cnf.*to 1 system" 80ms

And I should see a "5. Apply Highstate" text 82ms

And I should see a "6. Reboot 1 system" text 81ms

And I should see a "7. Run a remote command on 1 system" text 84ms

Scenario:
Check that a different user cannot see the action chain for SSH minion
1s 886ms 3

Given I am authorized as "testing" with password "testing" 1s 769ms

When I follow the left menu "Schedule > Action Chains" 106ms

Then I should not see a "minssh_action_chain" link 10ms

Scenario:
Execute the action chain from the web UI on SSH minion
3s 101ms 6

Given I am authorized for the "Admin" section 1s 868ms

When I follow the left menu "Schedule > Action Chains" 105ms

And I wait until I see "minssh_action_chain" text 59ms

And I follow "minssh_action_chain" 335ms

Then I click on "Save and Schedule" 56ms

And I should see a "Action Chain minssh_action_chain has been scheduled for execution." text 675ms

Scenario:
Verify that the action chain was executed successfully
5m 26s 594ms 2

When I wait for "virgo-dummy" to be installed on "ssh_minion" 48s 902ms

And I wait at most 300 seconds until file "/tmp/action_chain_one_system_done" exists on "ssh_minion" 4m 37s 691ms

Scenario:
Create a custom action chain for the SSH minion
545ms 3

When I create an action chain with label "minssh_action_chain_to_delete" via API 419ms

And I follow the left menu "Schedule > Action Chains" 63ms

Then I should see a "minssh_action_chain_to_delete" text 62ms

Scenario:
Add a remote command to the action chain on SSH minion
11s 775ms 6

Given I am on the Systems overview page of this "ssh_minion" 1s 53ms

When I follow "Remote Command" 455ms

And I enter as remote command this script in #!/bin/bash uptime 53ms

And I check radio button "schedule-by-action-chain" 10s 70ms

And I click on "Schedule" 57ms

Then I should see a "Action has been successfully added to the Action Chain" text 85ms

Scenario:
Delete the action chain for SSH minion
862ms 4

When I follow the left menu "Schedule > Action Chains" 128ms

And I follow "minssh_action_chain_to_delete" 258ms

And I follow "Delete Action Chains" in the content area 70ms

Then I click on "Delete" 405ms

Scenario:
Cleanup: roll back action chain effects on SSH minion
1m 22s 235ms 21

Given I am on the Systems overview page of this "ssh_minion" 1s 193ms

When I run "rm /tmp/action_chain_done" on "ssh_minion" without error control 395ms

And I enable repository "test_repo_rpm_pool" on this "ssh_minion" 506ms

And I remove package "andromeda-dummy" from this "ssh_minion" without error control 1s 740ms

And I remove package "virgo-dummy" from this "ssh_minion" without error control 1s 259ms

And I install package "milkyway-dummy" on this "ssh_minion" without error control 1s 495ms

And I install old package "andromeda-dummy-1.0" on this "ssh_minion" 1s 341ms

And I follow "Software" in the content area 67ms

And I click on "Update Package List" 701ms

And I follow "Events" in the content area 64ms

And I wait until I do not see "Package List Refresh scheduled" text, refreshing the page 13s 650ms

And I follow "Software" in the content area 59ms

And I follow "List / Remove" in the content area 63ms

And I enter "andromeda-dummy" as the filtered package name 259ms

And I click on the filter button until page does contain "andromeda-dummy-1.0" text 10s 918ms

When I follow the left menu "Admin > Task Schedules" 119ms

And I follow "errata-cache-default" 365ms

And I follow "errata-cache-bunch" 1s 263ms

And I click on "Single Run Schedule" 1s 529ms

Then I should see a "bunch was scheduled" text 269ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 44s 969ms

Scenario:
Add operations to the action chain via API for SSH minions
6s 250ms 10

Running actions:
- Run an arbitrary script
- Package Install/Upgrade
- Package Removal
- Package Install/Upgrade
- Removed "Run an arbitrary script" action
- Removed "Package Install/Upgrade" action
- Removed "Package Removal" action
- Removed "Package Install/Upgrade" action

Given I want to operate on this "ssh_minion" 368ms

When I create an action chain with label "minssh_api_chain" via API 360ms

And I add a package install to the action chain via API 833ms

And I add a package removal to the action chain via API 788ms

And I add a package upgrade to the action chain via API 836ms

And I add the script "exit 1;" to the action chain via API 383ms

Then I should be able to see all these actions in the action chain via API 345ms

When I remove each action within the chain via API 1s 675ms

Then the current action chain should be empty 325ms

And I delete the action chain via API 333ms

Scenario:
Run an action chain via API on SSH minion
28s 927ms 12

Running actions:
- Run an arbitrary script
- Run an arbitrary script
- Run an arbitrary script
- Run an arbitrary script

And I want to operate on this "ssh_minion" 337ms

When I create an action chain with label "minssh_multiple_scripts" via API 329ms

And I add the script "echo -n 1 >> /tmp/action_chain.log" to the action chain via API 366ms

And I add the script "echo -n 2 >> /tmp/action_chain.log" to the action chain via API 355ms

And I add the script "echo -n 3 >> /tmp/action_chain.log" to the action chain via API 358ms

And I add the script "touch /tmp/action_chain_done" to the action chain via API 370ms

Then I should be able to see all these actions in the action chain via API 342ms

When I schedule the action chain via API 437ms

Then I wait until there are no more action chains listed via API 364ms

When I wait until file "/tmp/action_chain_done" exists on "ssh_minion" 24s 496ms

Then file "/tmp/action_chain.log" should contain "123" on "ssh_minion" 827ms

When I wait until there are no more scheduled actions listed via API 339ms

Scenario:
Cleanup: remove SSH minion from configuration channel
1s 318ms 6

When I follow the left menu "Configuration > Channels" 148ms

And I follow "Action Chain Channel" 425ms

And I follow "Systems" in the content area 80ms

And I check the "ssh_minion" client 64ms

And I click on "Unsubscribe systems" 535ms

Then I should see a "Successfully unsubscribed 1 system(s)." text 63ms

Scenario:
Cleanup: remove configuration channel for SSH minion
1s 160ms 4

When I follow the left menu "Configuration > Channels" 61ms

And I follow "Action Chain Channel" 357ms

And I follow "Delete Channel" 294ms

And I click on "Delete Config Channel" 446ms

Scenario:
Cleanup: remove packages and repository used in action chain for SSH minion
3s 847ms 4

When I remove package "andromeda-dummy" from this "ssh_minion" without error control 1s 277ms

And I remove package "virgo-dummy" from this "ssh_minion" without error control 808ms

And I remove package "milkyway-dummy" from this "ssh_minion" without error control 1s 311ms

And I disable repository "test_repo_rpm_pool" on this "ssh_minion" without error control 450ms

Scenario:
Cleanup: remove temporary files for testing action chains on SSH minion
1s 592ms 4

When I run "rm -f /tmp/action_chain.log" on "ssh_minion" without error control 393ms

And I run "rm -f /tmp/action_chain_done" on "ssh_minion" without error control 402ms

And I run "rm -f /etc/action-chain.cnf" on "ssh_minion" without error control 401ms

And I run "rm -f /tmp/action_chain_one_system_done" on "ssh_minion" without error control 393ms

@skip_if_github_validation @ssh_minion @sle_minion @scope_action_chains
Feature:Action chains on several systems at once 2m 19s 129ms 12

Scenario:
Log in as admin user
419ms 1

Given I am authorized for the "Admin" section 419ms

Scenario:
Pre-requisite: downgrade packages before action chain test on several systems
8s 606ms 8

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 783ms

And I enable repository "test_repo_rpm_pool" on this "ssh_minion" 831ms

And I remove package "andromeda-dummy" from this "ssh_minion" without error control 789ms

And I remove package "andromeda-dummy" from this "sle_minion" without error control 839ms

And I install package "andromeda-dummy-1.0" on this "sle_minion" 1s 883ms

And I install package "andromeda-dummy-1.0" on this "ssh_minion" 1s 620ms

And I refresh the metadata for "sle_minion" 856ms

And I refresh the metadata for "ssh_minion" 1s 1ms

Scenario:
Pre-requisite: refresh package list and check installed packages before action chain test on several systems
38s 732ms 6

When I refresh packages list via spacecmd on "sle_minion" 3s 87ms

And I wait until refresh package list on "sle_minion" is finished 7s 250ms

Then spacecmd should show packages "andromeda-dummy-1.0" installed on "sle_minion" 2s 389ms

When I refresh packages list via spacecmd on "ssh_minion" 2s 334ms

And I wait until refresh package list on "ssh_minion" is finished 21s 289ms

Then spacecmd should show packages "andromeda-dummy-1.0" installed on "ssh_minion" 2s 380ms

Scenario:
Pre-requisite: wait until downgrade is finished before action chain test on several systems
1s 551ms 5

Given I am on the Systems overview page of this "sle_minion" 967ms

When I follow "Software" in the content area 72ms

And I follow "List / Remove" in the content area 65ms

And I enter "andromeda-dummy" as the filtered package name 170ms

And I click on the filter button until page does contain "andromeda-dummy-1.0" text 275ms

Scenario:
Pre-requisite: ensure the errata cache is computed before action chain test on several systems
20s 951ms 13

When I follow the left menu "Admin > Task Schedules" 142ms

And I follow "errata-cache-default" 1s 196ms

And I follow "errata-cache-bunch" 296ms

And I click on "Single Run Schedule" 1s 552ms

Then I should see a "bunch was scheduled" text 276ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 11s 977ms

Given I am on the Systems overview page of this "ssh_minion" 1s 46ms

When I follow the left menu "Admin > Task Schedules" 123ms

And I follow "errata-cache-default" 1s 159ms

And I follow "errata-cache-bunch" 309ms

And I click on "Single Run Schedule" 414ms

Then I should see a "bunch was scheduled" text 266ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 2s 190ms

Scenario:
Create a custom action chain for two systems
535ms 3

When I create an action chain with label "two_systems_action_chain" via API 338ms

And I follow the left menu "Schedule > Action Chains" 135ms

Then I should see a "two_systems_action_chain" text 61ms

Scenario:
Add an action chain using system set manager for SSH minion and SLE minion
24s 59ms 22

When I follow the left menu "Systems > System List > All" 178ms

And I check the "sle_minion" client 520ms

And I check the "ssh_minion" client 60ms

And I follow the left menu "Systems > System Set Manager > Overview" 458ms

And I follow "Install" in the content area 84ms

And I follow "Fake-RPM-SUSE-Channel" in the content area 66ms

And I enter "andromeda-dummy" as the filtered package name 55ms

And I click on the filter button 406ms

And I check "andromeda-dummy" in the list 55ms

And I click on "Install Packages" 325ms

Then I should see "sle_minion" hostname 75ms

And I should see "ssh_minion" hostname 75ms

When I check radio button "schedule-by-action-chain" 10s 56ms

And I click on "Confirm" 470ms

Then I should see a "Package installations are being scheduled" text 67ms

When I follow the left menu "Systems > System Set Manager > Overview" 68ms

And I follow "remote commands" in the content area 66ms

And I enter as remote command this script in #!/bin/bash touch /tmp/action_chain_done 70ms

And I check radio button "schedule-by-action-chain" 10s 74ms

And I click on "Schedule" 640ms

Then I should see "sle_minion" hostname 94ms

And I should see "ssh_minion" hostname 87ms

Scenario:
Verify action chain for two systems
2s 743ms 8

Given I am on the Systems overview page of this "sle_minion" 1s 10ms

When I follow "Schedule" 356ms

And I follow "Action Chains" 255ms

And I follow "two_systems_action_chain" 323ms

And I should see a "1. Install or update andromeda-dummy on 2 systems" text 65ms

And I should see a "2. Run a remote command on 2 systems" text 68ms

And I click on "Save and Schedule" 88ms

Then I should see a "Action Chain two_systems_action_chain has been scheduled for execution." text 573ms

Scenario:
Verify that the action chain from the system set manager was executed successfully
36s 510ms 4

When I wait until file "/tmp/action_chain_done" exists on "ssh_minion" 34s 876ms

And I wait until file "/tmp/action_chain_done" exists on "sle_minion" 746ms

Then "andromeda-dummy" should be installed on "ssh_minion" 446ms

And "andromeda-dummy" should be installed on "sle_minion" 440ms

Scenario:
Cleanup: remove package and repository used in action chain for several systems
4s 126ms 4

When I remove package "andromeda-dummy" from this "sle_minion" without error control 1s 505ms

And I remove package "andromeda-dummy" from this "ssh_minion" without error control 1s 532ms

And I disable repository "test_repo_rpm_pool" on this "sle_minion" without error control 464ms

And I disable repository "test_repo_rpm_pool" on this "ssh_minion" without error control 624ms

Scenario:
Cleanup: remove temporary files for testing action chains on several systems
822ms 2

When I run "rm /tmp/action_chain_done" on "sle_minion" without error control 413ms

And I run "rm /tmp/action_chain_done" on "ssh_minion" without error control 408ms

Scenario:
Cleanup: remove remaining systems from SSM after action chain tests on several systems
70ms 1

When I click on the clear SSM button 70ms

@skip_if_cloud @scope_building_container_images @no_auth_registry
Feature:API "image" namespace for containers and sub-namespaces < 1ms 3

Scenario:
Test "image.store" namespace
< 1ms 3

When I create and delete an image store via API 0s

And I list image store types and image stores via API 0s

And I set and get details of image store via API 0s

@scc_credentials
Scenario:
Test "image.profiles" namespace
< 1ms 4

When I create and delete profiles via API 0s

And I create and delete profile custom values via API 0s

And I list image profiles via API 0s

And I set and get profile details via API 0s

@scc_credentials
Scenario:
Cleanup: remove custom system info
< 1ms 5

Given I am authorized 0s

When I follow the left menu "Systems > Custom System Info" 0s

And I follow "arancio" 0s

And I follow "Delete Key" 0s

And I click on "Delete Key" 0s

@scope_recurring_actions
Feature:Recurring Actions 9m 57s 790ms 31 1

Scenario:
Log in as admin user
485ms 1

Given I am authorized for the "Admin" section 485ms

Scenario:
Create an IP forwarding config state channel
1s 9ms 10

When I follow the left menu "Configuration > Channels" 124ms

And I follow "Create State Channel" 359ms

And I wait until I see "New Config State Channel" text 56ms

And I enter "My State Channel for Recurring Actions" as "cofName" 92ms

And I enter "statechannel-recurring" as "cofLabel" 71ms

And I enter "This is a state channel to be used in recurring actions" as "cofDescription" 95ms

And I enter "enable_ip_forwarding:\n cmd.run:\n - name: echo 1 > /proc/sys/net/ipv4/conf/all/forwarding" in the editor 5ms

And I click on "Create Config State Channel" 67ms

Then I wait until I see "Channel Properties" text 70ms

And I wait until I see "My State Channel for Recurring Actions" text 65ms

Scenario:
Enable IP forwarding through a custom state recurring action
35s 248ms 21

Execution time: 14:54

When I am on the "Recurring Actions" page of this "sle_minion" 1s 40ms

Then I should see a "No schedules created. Use Create to add a schedule" text 64ms

When I click on "Create" 90ms

And I wait until I see "Action Type" text 93ms

And I enter "IP forwarding custom state recurring action" as "scheduleName" 271ms

And I select "Custom state" from "actionTypeDescription" 1s 134ms

And I wait until I see "Configure states to execute" text 101ms

And I check radio button "schedule-daily" 10s 82ms

And I enter 1 minutes from now as "time-daily_time" 104ms

And I check "statechannel-recurring-cbox" 84ms

And I click on "Save Changes" 65ms

And I wait until I see "Edit State Ranks" text 98ms

And I click on "Confirm" 73ms

And I click on "Create Schedule" 62ms

Then I wait until I see "Schedule successfully created" text 455ms

And I should see a "IP forwarding custom state recurring action" text 85ms

And I should see a "Minion" text 66ms

When I follow "Events" 464ms

And I follow "History" 464ms

Then I wait at most 420 seconds until event "Apply recurring states [manager_org_1.statechannel-recurring] schedule" is completed 19s 158ms

And file "/proc/sys/net/ipv4/conf/all/forwarding" should contain "1" on "sle_minion" 1s 185ms

Scenario:
Edit the IP forwarding custom state recurring action
1m 989ms 19

Execution time: 14:55

When I am on the "Recurring Actions" page of this "sle_minion" 1s 140ms

Then I should see a "IP forwarding custom state recurring action" text 272ms

When I click the "IP forwarding custom state recurring action" item edit button 63ms

And I wait until I see "Update Schedule" text 299ms

And I enter "custom_state_schedule_name_changed" as "scheduleName" 556ms

And I enter 1 minutes from now as "time-daily_time" 95ms

And I uncheck "statechannel-recurring-cbox" 10s 80ms

And I check "Sync States-cbox" 80ms

And I click on "Save Changes" 66ms

And I wait until I see "Edit State Ranks" text 92ms

And I click on "Confirm" 74ms

And I click on "Update Schedule" 62ms

Then I wait until I see "Schedule successfully updated" text 592ms

And I should see a "custom_state_schedule_name_changed" text 186ms

And I should see a "Minion" text 70ms

When I follow "Events" 395ms

And I follow "History" 486ms

Then I wait at most 420 seconds until event "Apply recurring states [util.syncstates] scheduled" is completed 46s 310ms

And I wait until I see "SLS: util.syncstates" text 62ms

@skip_if_github_validation
Scenario:
Cleanup: Disable IP forwarding
14s 526ms 9

When I follow the left menu "Salt > Remote Commands" 119ms

Then I should see a "Remote Commands" text in the content area 24ms

When I enter command "echo 0 > /proc/sys/net/ipv4/conf/all/forwarding" 134ms

And I enter target "sle_minion" 120ms

And I click on preview 11s 739ms

And I click on run 47ms

Then I should see "sle_minion" hostname 57ms

And I wait until I see "show response" text 1s 83ms

And file "/proc/sys/net/ipv4/conf/all/forwarding" should contain "0" on "sle_minion" 1s 198ms

Scenario:
Cleanup: Delete the minion Custom state Recurring Action
1s 946ms 6

When I am on the "Recurring Actions" page of this "sle_minion" 1s 156ms

Then I should see a "custom_state_schedule_name_changed" text 257ms

When I click the "custom_state_schedule_name_changed" item delete button 75ms

And I wait until I see "Delete Recurring Action Schedule" text 69ms

And I click on the red confirmation button 93ms

Then I wait until I see "Schedule 'custom_state_schedule_name_changed' has been deleted." text 294ms

Scenario:
Create a minion Highstate Recurring Action
48s 504ms 16

Execution time: 14:56

When I am on the "Recurring Actions" page of this "sle_minion" 1s 22ms

Then I should see a "No schedules created. Use Create to add a schedule" text 69ms

When I click on "Create" 108ms

And I wait until I see "Schedule Name" text 89ms

And I enter "Minion Highstate Recurring Action" as "scheduleName" 234ms

And I select "Highstate" from "actionTypeDescription" 1s 121ms

And I check radio button "schedule-daily" 10s 84ms

And I enter 1 minutes from now as "time-daily_time" 92ms

And I click on the "disabled" toggler 58ms

And I click on "Create Schedule" 60ms

Then I wait until I see "Schedule successfully created" text 197ms

And I should see a "Minion Highstate Recurring Action" text 177ms

And I should see a "Minion" text 67ms

When I follow "Events" 330ms

And I follow "History" 445ms

And I wait until I see the event "Apply highstate in test-mode scheduled" completed during last minute, refreshing the page 34s 343ms

Scenario:
Edit the minion Highstate Recurring Action
14s 139ms 13

When I am on the "Recurring Actions" page of this "sle_minion" 1s 57ms

Then I should see a "Minion Highstate Recurring Action" text 173ms

When I click the "Minion Highstate Recurring Action" item edit button 65ms

And I wait until I see "Update Schedule" text 308ms

And I enter "schedule_name_minion" as "scheduleName" 342ms

And I check radio button "schedule-weekly" 10s 90ms

And I select "Wednesday" from "date_weekly" 1s 123ms

And I enter "01:35" as "time-weekly_time" 98ms

And I click on "Update Schedule" 61ms

Then I wait until I see "Schedule successfully updated" text 509ms

And I should see a "schedule_name_minion" text 170ms

And I should see a "Minion" text 69ms

And I should see a "0 35 1 ? * 4" text 67ms

Scenario:
View the minion Highstate Recurring Action details
1s 771ms 6

When I am on the "Recurring Actions" page of this "sle_minion" 1s 43ms

Then I should see a "schedule_name_minion" text 269ms

When I click the "schedule_name_minion" item details button 65ms

Then I should see a "Every Wednesday at 01:35" text 266ms

When I click on "Back" 66ms

Then I should see a "Schedules" text 59ms

Scenario:
Create a System group for testing
3s 507ms 11

When I follow the left menu "Systems > System Groups" 91ms

And I follow "Create Group" 273ms

And I enter "Recurring-Action-test-group" as "name" 70ms

And I enter "This is for testing" as "description" 63ms

And I click on "Create Group" 60ms

Then I should see a "System group Recurring-Action-test-group created." text 68ms

When I am on the "Groups" page of this "sle_minion" 1s 101ms

And I follow first "Join" 465ms

And I check the first row in the list 73ms

And I click on "Join Groups" 1s 166ms

Then I wait until I see "1 system groups added" text 72ms

Scenario:
Pre-requisite: subscribe system to Fake Channel
31s 590ms 12

Given I am on the Systems overview page of this "sle_minion" 967ms

When I follow "Software" in the content area 86ms

And I follow "Software Channels" in the content area 66ms

And I wait until I do not see "Loading..." text 82ms

And I check radio button "Fake-Base-Channel-SUSE-like" 10s 74ms

And I wait until I do not see "Loading..." text 421ms

And I check "Fake-Child-Channel-SUSE-like" 77ms

And I click on "Next" 60ms

Then I should see a "Confirm Software Channel Change" text 60ms

When I click on "Confirm" 70ms

Then I should see a "Changing the channels has been scheduled." text 387ms

And I wait until event "Subscribe channels scheduled" is completed 19s 234ms

@skip_if_github_validation
Scenario:
Pre-requisite: downgrade milkyway-dummy to lower version
1m 42s 175ms 9

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 824ms

And I install old package "milkyway-dummy-1.0" on this "sle_minion" 2s 190ms

And I refresh the metadata for "sle_minion" 737ms

And I follow the left menu "Admin > Task Schedules" 142ms

And I follow "errata-cache-default" 386ms

And I follow "errata-cache-bunch" 1s 364ms

And I click on "Single Run Schedule" 1s 248ms

Then I should see a "bunch was scheduled" text 266ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 1m 35s 12ms

Scenario:
Pre-requisite: check that there are updates available
1s 60ms 2

Given I am on the Systems overview page of this "sle_minion" 968ms

And I wait until I see "Software Updates Available" text, refreshing the page 91ms

Scenario:
Create a recurring action to apply "uptodate" state to a system group
1m 24s 529ms 24

Execution time: 15:00

When I follow the left menu "Systems > System Groups" 82ms

And I follow "Recurring-Action-test-group" 305ms

And I follow "Recurring Actions" in the content area 66ms

Then I should see a "No schedules created. Use Create to add a schedule" text 106ms

When I click on "Create" 98ms

And I wait until I see "Schedule Name" text 92ms

And I enter "Recurring action to keep Recurring-Action-test-group uptodate" as "scheduleName" 365ms

And I select "Custom state" from "actionTypeDescription" 1s 132ms

And I wait until I see "Configure states to execute" text 99ms

And I check radio button "schedule-daily" 10s 84ms

And I enter 1 minutes from now as "time-daily_time" 88ms

And I check "Update System-cbox" 88ms

And I click on "Save Changes" 69ms

And I wait until I see "Edit State Ranks" text 96ms

And I click on "Confirm" 76ms

And I click on "Create Schedule" 64ms

Then I wait until I see "Schedule successfully created" text 251ms

And I should see a "Recurring action to keep Recurring-Action-test-group uptodate" text 87ms

And I should see a "Group" text 79ms

When I am on the "Events" page of this "sle_minion" 1s 75ms

And I follow "History" 380ms

Then I wait until I see the event "Apply recurring states [uptodate] scheduled" completed during last minute, refreshing the page 1m 8s 670ms

When I am on the Systems overview page of this "sle_minion" 975ms

Then I wait at most 500 seconds until I do not see "System is up to date" text, refreshing the page 90ms

@susemanager
Scenario:
Cleanup: subscribe system back to default base channel
< 1ms 24

Given I am on the Systems overview page of this "sle_minion" 0s

When I follow "Software" in the content area 0s

And I disable repository "test_repo_rpm_pool" on this "sle_minion" without error control 0s

And I follow "Software Channels" in the content area 0s

And I wait until I do not see "Loading..." text 0s

And I check default base channel radio button of this "sle_minion" 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 click on "Next" 0s

Then I should see a "Confirm Software Channel Change" text 0s

When I click on "Confirm" 0s

Then I should see a "Changing the channels has been scheduled." text 0s

And I wait until event "Subscribe channels scheduled" is completed 0s

@uyuni
Scenario:
Cleanup: subscribe system back to default base channel
23s 205ms 14

Given I am on the Systems overview page of this "sle_minion" 994ms

When I follow "Software" in the content area 74ms

And I disable repository "test_repo_rpm_pool" on this "sle_minion" without error control 796ms

And I follow "Software Channels" in the content area 66ms

And I wait until I do not see "Loading..." text 68ms

And I check default base channel radio button of this "sle_minion" 554ms

And I wait for child channels to appear 624ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 82ms

And I check "Fake-RPM-SUSE-Channel" 74ms

And I click on "Next" 60ms

Then I should see a "Confirm Software Channel Change" text 64ms

When I click on "Confirm" 72ms

Then I should see a "Changing the channels has been scheduled." text 415ms

And I wait until event "Subscribe channels scheduled" is completed 19s 256ms

Scenario:
Edit the group Recurring Action
12s 341ms 14

When I follow the left menu "Systems > System Groups" 73ms

And I follow "Recurring-Action-test-group" 304ms

And I follow "Recurring Actions" in the content area 68ms

Then I should see a "Recurring action to keep Recurring-Action-test-group uptodate" text 169ms

When I click the "Recurring action to keep Recurring-Action-test-group uptodate" item edit button 64ms

And I wait until I see "Update Schedule" text 219ms

And I enter "schedule_name_group" as "scheduleName" 564ms

And I check radio button "schedule-hourly" 10s 75ms

And I enter "35" as "minutes" 65ms

And I click on "Update Schedule" 68ms

Then I wait until I see "Schedule successfully updated" text 459ms

And I should see a "schedule_name_group" text 70ms

And I should see a "Group" text 67ms

And I should see a "0 35 * ? * *" text 69ms

Scenario:
View the group recurring actions details
1s 116ms 10

When I follow the left menu "Systems > System Groups" 59ms

And I follow "Recurring-Action-test-group" 296ms

And I follow "Recurring Actions" in the content area 57ms

Then I should see a "schedule_name" text 263ms

When I click the "schedule_name" item details button 63ms

Then I should see a "Every hour at minute 35" text 166ms

And I should see a "Recurring-Action-test-group" link 12ms

And I should see a "Update System" text 71ms

When I click on "Back" 65ms

Then I should see a "Schedules" text 59ms

Scenario:
Create a yourorg Recurring Action
1m 11s 643ms 21

Execution time: 15:02

When I follow the left menu "Home > My Organization > Recurring Actions" 188ms

Then I should see a "No schedules created. Use Create to add a schedule" text 58ms

When I click on "Create" 81ms

And I wait until I see "Schedule Name" text 86ms

And I enter "schedule_name" as "scheduleName" 103ms

And I select "Custom state" from "actionTypeDescription" 1s 126ms

And I wait until I see "Configure states to execute" text 98ms

And I check radio button "schedule-daily" 10s 78ms

And I enter 1 minutes from now as "time-daily_time" 88ms

And I click on the "disabled" toggler 55ms

And I check "Package Profile Update-cbox" 86ms

And I click on "Save Changes" 64ms

And I wait until I see "Edit State Ranks" text 93ms

And I click on "Confirm" 74ms

And I click on "Create Schedule" 63ms

Then I wait until I see "Schedule successfully created" text 243ms

And I should see a "schedule_name" text 70ms

And I should see a "Organization" text 68ms

When I am on the "Events" page of this "sle_minion" 1s 173ms

And I follow "History" 494ms

Then I wait until I see the event "Apply recurring states [packages.profileupdate] scheduled" completed during last minute, refreshing the page 57s 244ms

Scenario:
Edit the yourorg Recurring Action
13s 114ms 13

When I follow the left menu "Home > My Organization > Recurring Actions" 226ms

Then I should see a "schedule_name" text 173ms

When I click the "schedule_name" item edit button 65ms

And I wait until I see "Update Schedule" text 311ms

And I enter "schedule_name_edit" as "scheduleName" 280ms

And I check radio button "schedule-monthly" 10s 72ms

And I select "7" from "date_monthly" 1s 153ms

And I enter "05:17" as "time-monthly_time" 103ms

And I click on "Update Schedule" 66ms

Then I wait until I see "Schedule successfully updated" text 461ms

And I should see a "schedule_name_edit" text 67ms

And I should see a "Organization" text 64ms

And I should see a "0 17 5 7 * ?" text 65ms

Scenario:
View the yourorg recurring actions details
759ms 7

When I follow the left menu "Home > My Organization > Recurring Actions" 86ms

Then I should see a "schedule_name" text 251ms

When I click the "schedule_name" item details button 68ms

Then I should see a "Every 7th of the month at 05:17" text 164ms

And I should see a "Package Profile Update" text 65ms

When I click on "Back" 67ms

Then I should see a "Schedules" text 56ms

Scenario:
Cleanup: Delete the yourorg Recurring Action
1s 590ms 7

When I follow the left menu "Home > My Organization > Recurring Actions" 79ms

Then I should see a "schedule_name_edit" text 253ms

When I click the "schedule_name" item delete button 76ms

And I wait until I see "Delete Recurring Action Schedule" text 66ms

And I click on the red confirmation button 63ms

Then I wait until I see "Schedule 'schedule_name_edit' has been deleted." text 984ms

And I should see a "No schedules created. Use Create to add a schedule" text 66ms

Scenario:
Create an admin org Recurring Action
48s 606ms 23

Execution time: 15:03

When I follow the left menu "Admin > Organizations" 113ms

And I follow "SUSE Test" in the content area 69ms

And I follow "Recurring Actions" in the content area 63ms

Then I should see a "No schedules created. Use Create to add a schedule" text 58ms

When I click on "Create" 84ms

And I wait until I see "Schedule Name" text 88ms

And I select "Custom state" from "actionTypeDescription" 1s 119ms

And I wait until I see "Configure states to execute" text 100ms

And I enter "schedule_name" as "scheduleName" 131ms

And I check radio button "schedule-daily" 10s 82ms

And I enter 1 minutes from now as "time-daily_time" 85ms

And I click on the "disabled" toggler 60ms

And I check "Hardware Profile Update-cbox" 86ms

And I click on "Save Changes" 65ms

And I wait until I see "Edit State Ranks" text 94ms

And I click on "Confirm" 92ms

And I click on "Create Schedule" 63ms

Then I wait until I see "Schedule successfully created" text 255ms

And I should see a "schedule_name" text 66ms

And I should see a "Organization" text 70ms

When I am on the "Events" page of this "sle_minion" 1s 10ms

And I follow "History" 394ms

Then I wait until I see the event "Apply recurring states [hardware.profileupdate] scheduled" completed during last minute, refreshing the page 34s 351ms

Scenario:
Edit the admin org Recurring Action
12s 157ms 14

When I follow the left menu "Admin > Organizations" 131ms

And I follow "SUSE Test" in the content area 74ms

And I follow "Recurring Actions" in the content area 66ms

Then I should see a "schedule_name" text 265ms

When I click the "schedule_name" item edit button 63ms

And I wait until I see "Update Schedule" text 304ms

And I enter "schedule_name_org" as "scheduleName" 256ms

And I check radio button "schedule-cron" 10s 94ms

And I enter "0 0 15 3 * ?" as "cron" 202ms

And I click on "Update Schedule" 67ms

Then I wait until I see "Schedule successfully updated" text 427ms

And I should see a "schedule_name_org" text 68ms

And I should see a "Organization" text 68ms

And I should see a "0 0 15 3 * ?" text 67ms

Scenario:
View the admin org recurring actions details
788ms 8

When I follow the left menu "Admin > Organizations" 68ms

And I follow "SUSE Test" in the content area 63ms

And I follow "Recurring Actions" in the content area 58ms

Then I should see a "schedule_name" text 256ms

When I click the "schedule_name" item details button 59ms

Then I should see a "Every 3rd of the month at 15:00" text 159ms

When I click on "Back" 63ms

Then I should see a "Schedules" text 58ms

Scenario:
View all types of recurring actions in the list of all actions
959ms 8

When I follow the left menu "Schedule > Recurring Actions" 124ms

Then I should not see a "Create" text 55ms

And I should see a "schedule_name_minion" text 422ms

And I should see a "Minion" text 72ms

And I should see a "schedule_name_group" text 71ms

And I should see a "Group" text 71ms

And I should see a "schedule_name_org" text 69ms

And I should see a "Organization" text 72ms

Scenario:
View details in list of all actions
1s 278ms 6

When I follow the left menu "Schedule > Recurring Actions" 57ms

And I click the "schedule_name_minion" item details button 464ms

Then I should see a "Every Wednesday at 01:35" text 146ms

And I should not see a "Schedules" text in the content area 26ms

When I click on "Back" 56ms

Then I should see a "schedule_name_group" text 525ms

Scenario:
Cleanup: Delete the admin org Recurring Action
880ms 8

When I follow the left menu "Admin > Organizations" 104ms

And I follow "SUSE Test" in the content area 67ms

And I follow "Recurring Actions" in the content area 57ms

Then I should see a "schedule_name_org" text 259ms

When I click the "schedule_name_org" item delete button 77ms

And I wait until I see "Delete Recurring Action Schedule" text 67ms

And I click on the red confirmation button 62ms

Then I wait until I see "Schedule 'schedule_name_org' has been deleted." text 185ms

Scenario:
Cleanup: Delete the group Recurring Action
1s 941ms 9

When I follow the left menu "Systems > System Groups" 120ms

And I follow "Recurring-Action-test-group" 331ms

And I follow "Recurring Actions" in the content area 60ms

Then I should see a "schedule_name_group" text 268ms

When I click the "schedule_name_group" item delete button 65ms

And I wait until I see "Delete Recurring Action Schedule" text 69ms

And I click on the red confirmation button 57ms

Then I wait until I see "Schedule 'schedule_name_group' has been deleted." text 795ms

And I should see a "No schedules created. Use Create to add a schedule" text 172ms

Scenario:
Cleanup: Delete the minion Highstate Recurring Action
2s 743ms 7

When I am on the "Recurring Actions" page of this "sle_minion" 1s 87ms

Then I should see a "schedule_name_minion" text 173ms

When I click the "schedule_name_minion" item delete button 63ms

And I wait until I see "Delete Recurring Action Schedule" text 69ms

And I click on the red confirmation button 49ms

Then I wait until I see "Schedule 'schedule_name_minion' has been deleted." text 1s 234ms

And I should see a "No schedules created. Use Create to add a schedule" text 65ms

Scenario:
Cleanup: Delete the system group created for group recurring action tests
1s 725ms 5

When I follow the left menu "Systems > System Groups" 58ms

And I follow "Recurring-Action-test-group" 301ms

And I follow "Delete Group" 302ms

And I click on "Confirm Deletion" 1s 3ms

Then I should see a "Your organization has no system groups." text 59ms

Scenario:
Cleanup: Remove "My State Channel for Recurring Actions" config channel
1s 451ms 5

When I follow the left menu "Configuration > Channels" 128ms

And I follow "My State Channel for Recurring Actions" 506ms

And I follow "Delete Channel" 290ms

And I click on "Delete Config Channel" 474ms

Then I should see a "Channel 'My State Channel for Recurring Actions' has been deleted" text 52ms

@skip_if_github_validation @scc_credentials @scope_changing_software_channels @sle_minion
Feature:Assign child channel to a system 1m 26s 684ms 8 6

Scenario:
Log in as org admin user
1s 921ms 1

Given I am authorized 1s 921ms

@susemanager
Scenario:
Pre-requisite: unsubscribe from old channels
< 1ms 13

Given I am on the Systems overview page of this "sle_minion" 0s

When I follow "Software" in the content area 0s

And I follow "Software Channels" in the content area 0s

And I wait until I do not see "Loading..." text 0s

And I check radio button "SLE-Product-SLES15-SP7-Pool for x86_64" 0s

Then radio button "SLE-Product-SLES15-SP7-Pool for x86_64" should be checked 0s

And I wait until I do not see "Loading..." text 0s

When I uncheck "SLE15-SP7-Installer-Updates for x86_64" 0s

And I should see "SLE15-SP7-Installer-Updates for x86_64" as unchecked 0s

And I click on "Next" 0s

Then I should see a "Confirm Software Channel Change" text 0s

When I click on "Confirm" 0s

Then I should see a "Changing the channels has been scheduled." text 0s

@uyuni
Scenario:
Pre-requisite: unsubscribe from old channels
3s 220ms 15

Warning: Radio button 'openSUSE Tumbleweed (x86_64)' is already checked

Given I am on the Systems overview page of this "sle_minion" 1s 713ms

When I follow "Software" in the content area 65ms

And I follow "Software Channels" in the content area 63ms

And I wait until I do not see "Loading..." text 87ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 203ms

Then radio button "openSUSE Tumbleweed (x86_64)" should be checked 15ms

When I wait until I do not see "Loading..." text 419ms

And I uncheck "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" by label 35ms

Then I should see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" as unchecked 14ms

When I uncheck "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" by label 76ms

Then I should see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" as unchecked 14ms

When I click on "Next" 61ms

Then I should see a "Confirm Software Channel Change" text 65ms

When I click on "Confirm" 78ms

Then I should see a "Changing the channels has been scheduled." text 304ms

@susemanager
Scenario:
Pre-requisite: check via API that the system is unsubscribed from old channels
< 1ms 3

When I refresh the metadata for "sle_minion" 0s

Then channel "SLE-Product-SLES15-SP7-Pool for x86_64" should be enabled on "sle_minion" 0s

And channel "SLE15-SP7-Installer-Updates for x86_64" should be disabled on "sle_minion" 0s

@uyuni
Scenario:
Pre-requisite: check via API that the system is unsubscribed from old channels
9s 390ms 3

When I refresh the metadata for "sle_minion" 7s 701ms

Then channel "openSUSE Tumbleweed (x86_64)" should be enabled on "sle_minion" 833ms

And channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" should be disabled on "sle_minion" 855ms

@susemanager
Scenario:
Assign a child channel to the system
< 1ms 13

When I follow "Software" in the content area 0s

And I follow "Software Channels" in the content area 0s

And I wait until I do not see "Loading..." text 0s

Then radio button "SLE-Product-SLES15-SP7-Pool for x86_64" should be checked 0s

And I wait until I do not see "Loading..." text 0s

And I check "SLE15-SP7-Installer-Updates for x86_64" 0s

And I click on "Next" 0s

Then I should see a "Confirm Software Channel Change" text 0s

And I click on "Confirm" 0s

Then I should see a "Changing the channels has been scheduled." text 0s

When I follow "scheduled" in the content area 0s

And I wait until I see "1 system successfully completed this action." text, refreshing the page 0s

Then channel "SLE15-SP7-Installer-Updates for x86_64" should be enabled on "sle_minion" 0s

@uyuni
Scenario:
Assign a child channel to the system
32s 222ms 14

When I follow "Software" in the content area 58ms

And I follow "Software Channels" in the content area 58ms

And I wait until I do not see "Loading..." text 68ms

Then radio button "openSUSE Tumbleweed (x86_64)" should be checked 214ms

When I wait until I do not see "Loading..." text 417ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" by label 68ms

Then I should see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" as checked 15ms

When I click on "Next" 54ms

Then I should see a "Confirm Software Channel Change" text 65ms

When I click on "Confirm" 62ms

Then I should see a "Changing the channels has been scheduled." text 319ms

When I follow "scheduled" in the content area 74ms

And I wait until I see "1 system successfully completed this action." text, refreshing the page 29s 938ms

Then channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" should be enabled on "sle_minion" 805ms

Scenario:
Check channel change has completed for the system
3s 713ms 3

Given I am on the Systems overview page of this "sle_minion" 1s 147ms

When I wait until event "Subscribe channels scheduled" is completed 2s 508ms

Then I should see a "The client completed this action on" text 57ms

@susemanager
Scenario:
Check the system is subscribed to the new channels
< 1ms 6

When I follow "Software" in the content area 0s

And I follow "Software Channels" in the content area 0s

And I wait until I do not see "Loading..." text 0s

Then radio button "SLE-Product-SLES15-SP7-Pool for x86_64" should be checked 0s

And I wait until I do not see "Loading..." text 0s

And I should see "SLE15-SP7-Installer-Updates for x86_64" as checked 0s

@uyuni
Scenario:
Check the system is subscribed to the new channels
829ms 6

When I follow "Software" in the content area 72ms

And I follow "Software Channels" in the content area 64ms

And I wait until I do not see "Loading..." text 64ms

Then radio button "openSUSE Tumbleweed (x86_64)" should be checked 182ms

And I wait until I do not see "Loading..." text 412ms

And I should see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" as checked 32ms

@susemanager
Scenario:
Check via API the new channels are enabled on the system
< 1ms 3

When I refresh the metadata for "sle_minion" 0s

Then channel "SLE-Product-SLES15-SP7-Pool for x86_64" should be enabled on "sle_minion" 0s

And channel "SLE15-SP7-Installer-Updates for x86_64" should be enabled on "sle_minion" 0s

@uyuni
Scenario:
Check via API the new channels are enabled on the system
3s 2ms 3

When I refresh the metadata for "sle_minion" 1s 438ms

Then channel "openSUSE Tumbleweed (x86_64)" should be enabled on "sle_minion" 781ms

And channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" should be enabled on "sle_minion" 783ms

@susemanager
Scenario:
Cleanup: subscribe the system back to previous channels
< 1ms 17

When I follow "Software" in the content area 0s

And I follow "Software Channels" in the content area 0s

And I wait until I do not see "Loading..." text 0s

Then radio button "SLE-Product-SLES15-SP7-Pool for x86_64" should be checked 0s

And I wait until I do not see "Loading..." text 0s

And I wait until I see "ManagerTools-SLE15-Pool for x86_64 SP7" text 0s

And I include the recommended child channels 0s

And I check "SLE-Module-DevTools15-SP7-Pool for x86_64" 0s

And I check "Fake-RPM-SUSE-Channel" 0s

And I uncheck "SLE15-SP7-Installer-Updates for x86_64" 0s

And I click on "Next" 0s

Then I should see a "Confirm Software Channel Change" text 0s

When I click on "Confirm" 0s

Then I should see a "Changing the channels has been scheduled." text 0s

When I follow "scheduled" in the content area 0s

And I wait until I see "1 system successfully completed this action." text, refreshing the page 0s

Then channel "SLE15-SP7-Installer-Updates for x86_64" should be disabled on "sle_minion" 0s

@uyuni
Scenario:
Cleanup: subscribe the system back to previous channels
32s 384ms 18

When I follow "Software" in the content area 58ms

And I follow "Software Channels" in the content area 57ms

And I wait until I do not see "Loading..." text 64ms

Then radio button "openSUSE Tumbleweed (x86_64)" should be checked 163ms

And I wait until I do not see "Loading..." text 409ms

And I wait until I see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" text 75ms

And I uncheck "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" by label 81ms

Then I should see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" as unchecked 14ms

When I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" by label 72ms

Then I should see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" as checked 14ms

When I check "Fake-RPM-SUSE-Channel" 36ms

And I click on "Next" 62ms

Then I should see a "Confirm Software Channel Change" text 66ms

When I click on "Confirm" 79ms

And I wait until I see "Changing the channels has been scheduled." text 418ms

And I follow "scheduled" in the content area 73ms

And I wait until I see "1 system successfully completed this action." text, refreshing the page 29s 844ms

Then channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" should be disabled on "sle_minion" 791ms

@scope_retracted_patches
Feature:Retracted patches 2m 8s 979ms 12

Scenario:
Log in as org admin user
1s 938ms 1

Given I am authorized 1s 938ms

Scenario:
Installed retracted package should show icon in the system packages list
38s 53ms 12

When I install package "rute-dummy=2.1-1.1" on this "sle_minion" 2s 370ms

And I refresh packages list via spacecmd on "sle_minion" 3s 184ms

And I wait until refresh package list on "sle_minion" is finished 7s 748ms

And I am on the "Software" page of this "sle_minion" 1s 95ms

And I follow "Packages" 481ms

And I follow "List / Remove" 731ms

And I enter "rute-dummy" as the filtered package name 47ms

And I click on the filter button until page does contain "rute-dummy" text 11s 11ms

Then the table row for "rute-dummy-2.1-1.1" should contain "retracted" icon 22ms

When I remove package "rute-dummy" from this "sle_minion" 1s 889ms

And I refresh packages list via spacecmd on "sle_minion" 3s 571ms

And I wait until package "rute-dummy" is removed from "sle_minion" via spacecmd 5s 899ms

Scenario:
Retracted package should not be available for installation
12s 971ms 7

When I am on the "Software" page of this "sle_minion" 1s 99ms

And I follow "Packages" 409ms

And I follow "Install" 521ms

And I enter "rute-dummy" as the filtered package name 56ms

And I click on the filter button until page does contain "rute-dummy" text 10s 743ms

Then I should see a "rute-dummy-2.0-1.2" text 68ms

And I should not see a "rute-dummy-2.1-1.1" text 71ms

Scenario:
Retracted package should not be available for upgrade
27s 44ms 10

When I install old package "rute-dummy=2.0-1.2" on this "sle_minion" 2s 66ms

And I refresh packages list via spacecmd on "sle_minion" 2s 690ms

And I wait until refresh package list on "sle_minion" is finished 9s 831ms

And I am on the "Software" page of this "sle_minion" 1s 64ms

And I follow "Packages" 413ms

And I follow "Upgrade" 573ms

Then I should not see a "rute-dummy-2.1-1.1" text 124ms

When I remove package "rute-dummy" from this "sle_minion" 1s 856ms

And I refresh packages list via spacecmd on "sle_minion" 2s 538ms

And I wait until package "rute-dummy" is removed from "sle_minion" via spacecmd 5s 885ms

Scenario:
Retracted patch should not affect any system
25s 846ms 13

When I install package "rute-dummy=2.0-1.2" on this "sle_minion" 1s 756ms

And I refresh packages list via spacecmd on "sle_minion" 2s 435ms

And I wait until refresh package list on "sle_minion" is finished 9s 741ms

And I follow the left menu "Software > Channel List > All" 205ms

And I follow "Show All Child Channels" 56ms

And I follow "Fake-RPM-SUSE-Channel" 574ms

And I follow "Patches" in the content area 66ms

And I follow "rute-dummy-0817" 425ms

And I follow "Affected Systems" 285ms

Then I should see a "No systems." text 56ms

When I remove package "rute-dummy" from this "sle_minion" 1s 938ms

And I refresh packages list via spacecmd on "sle_minion" 2s 391ms

And I wait until package "rute-dummy" is removed from "sle_minion" via spacecmd 5s 913ms

Scenario:
Target systems for stable packages should not be empty
2s 210ms 7

When I follow the left menu "Software > Channel List > All" 153ms

And I follow "Show All Child Channels" 61ms

And I follow "Fake-RPM-SUSE-Channel" 749ms

And I follow "Packages" in the content area 67ms

And I follow "rute-dummy-2.0-1.2.x86_64" 569ms

And I follow "Target Systems" 469ms

And I refresh page until I see "sle_minion" hostname as text 139ms

Scenario:
Target systems for retracted packages should be empty
11s 626ms 7

When I follow the left menu "Software > Channel List > All" 127ms

And I follow "Show All Child Channels" 59ms

And I follow "Fake-RPM-SUSE-Channel" 582ms

And I follow "Packages" in the content area 66ms

And I follow "rute-dummy-2.1-1.1.x86_64" 462ms

And I follow "Target Systems" 309ms

Then I should not see "sle_minion" hostname 10s 17ms

Scenario:
Retracted packages in the patch detail
4s 572ms 15

When I follow the left menu "Patches > Patch List > All" 184ms

And I enter "dummy" as the filtered synopsis 58ms

And I click on the filter button 649ms

And I follow "rute-dummy-0815" 444ms

Then I should see a "Status: Retracted" text 62ms

When I go back 504ms

And I enter "dummy" as the filtered synopsis 36ms

And I click on the filter button 514ms

And I follow "rute-dummy-0816" 444ms

Then I should see a "Status: Stable" text 71ms

When I go back 476ms

And I enter "dummy" as the filtered synopsis 38ms

And I click on the filter button 660ms

And I follow "rute-dummy-0817" 365ms

Then I should see a "Status: Retracted" text 63ms

Scenario:
Retracted packages in the patches list
662ms 6

When I follow the left menu "Patches > Patch List > All" 82ms

And I enter "dummy" as the filtered synopsis 37ms

And I click on the filter button 486ms

Then the table row for "rute-dummy-0815" should contain "retracted" icon 24ms

And the table row for "rute-dummy-0816" should not contain "retracted" icon 14ms

And the table row for "rute-dummy-0817" should contain "retracted" icon 17ms

Scenario:
Retracted patches in the channel patches list
948ms 7

When I follow the left menu "Software > Channel List > All" 178ms

And I follow "Show All Child Channels" 67ms

And I follow "Fake-RPM-SUSE-Channel" 593ms

And I follow "Patches" in the content area 68ms

Then the table row for "rute-dummy-0815" should contain "retracted" icon 15ms

And the table row for "rute-dummy-0816" should not contain "retracted" icon 11ms

And the table row for "rute-dummy-0817" should contain "retracted" icon 13ms

Scenario:
Retracted packages in the channel packages list
803ms 7

When I follow the left menu "Software > Channel List > All" 69ms

And I follow "Show All Child Channels" 46ms

And I follow "Fake-RPM-SUSE-Channel" 572ms

And I follow "Packages" in the content area 62ms

Then the table row for "rute-dummy-2.0-1.1.x86_64" should contain "retracted" icon 18ms

Then the table row for "rute-dummy-2.0-1.2.x86_64" should not contain "retracted" icon 14ms

Then the table row for "rute-dummy-2.1-1.1.x86_64" should contain "retracted" icon 18ms

Scenario:
SSM: Retracted package should not be available for installation
2s 300ms 10

When I follow the left menu "Systems > System List > All" 199ms

And I click on the clear SSM button 61ms

And I check the "sle_minion" client 450ms

And I follow the left menu "Systems > System Set Manager > Overview" 466ms

And I follow "Packages" in the content area 58ms

And I follow "Install" 480ms

And I follow "Fake-RPM-SUSE-Channel" 363ms

Then I should see a "rute-dummy-2.0-1.2" text 86ms

And I should not see a "rute-dummy-2.1-1.1" text 85ms

And I click on the clear SSM button 48ms

@skip_if_github_validation @containerized_server @proxy @build_host @private_net @pxeboot_minion @scope_cobbler @under_debugging
Feature:PXE boot a terminal with Cobbler and containerized proxy < 1ms 19

In order to automate client system installations with a containerized proxy
As the system administrator
I want to PXE boot one host with Cobbler

Scenario:
Log in as admin user
< 1ms 1

Given I am authorized for the "Admin" section 0s

Scenario:
Start Cobbler monitoring
< 1ms 1

When I start local monitoring of Cobbler 0s

Scenario:
Prepare the autoinstallation files on the server
< 1ms 3

When I install packages "tftpboot-installation-SLE-15-SP7-x86_64 expect" on this "build_host" 0s

And I copy "/usr/share/tftpboot-installation" from "build_host" to "server" via scp in the path "/tmp" 0s

And I copy the distribution inside the container on the server 0s

Scenario:
Create auto installation distribution
< 1ms 9

When I follow the left menu "Systems > Autoinstallation > Distributions" 0s

And I follow "Create Distribution" 0s

And I enter "SLE-15-SP7-TFTP" as "label" 0s

And I enter "/srv/www/distributions/SLE-15-SP7-TFTP/" as "basepath" 0s

And I select "SLE-Product-SLES15-SP7-Pool for x86_64" from "channelid" 0s

And I select "SUSE Linux Enterprise 15" from "installtype" 0s

And I click on "Create Autoinstallable Distribution" 0s

Then I should see a "Autoinstallable Distributions" text 0s

And I should see a "SLE-15-SP7-TFTP" link 0s

Scenario:
Fix kernel parameters
< 1ms 5

When I follow the left menu "Systems > Autoinstallation > Distributions" 0s

And I follow "SLE-15-SP7-TFTP" 0s

And I enter "useonlinerepo insecure=1 install=http://proxy.example.org/ks/dist/SLE-15-SP7-TFTP self_update=http://proxy.example.org/ks/dist/child/sle15-sp7-installer-updates-x86_64/SLE-15-SP7-TFTP" as "kernelopts" 0s

And I click on "Update Autoinstallable Distribution" 0s

Then I should see a "Autoinstallable Distribution Updated" text 0s

@susemanager
Scenario:
Create auto installation profile
< 1ms 8

When I follow the left menu "Systems > Autoinstallation > Profiles" 0s

And I follow "Upload Kickstart/AutoYaST File" 0s

And I enter "15-sp7-cobbler" as "kickstartLabel" 0s

And I select "SLE-15-SP7-TFTP" from "kstreeId" 0s

And I attach the file "/sle-15-sp7-autoyast.xml" to "fileUpload" 0s

And I click on "Create" 0s

Then I should see a "Autoinstallation: 15-sp7-cobbler" text 0s

And I should see a "Autoinstallation Details" text 0s

@uyuni
Scenario:
Create auto installation profile
< 1ms 8

When I follow the left menu "Systems > Autoinstallation > Profiles" 0s

And I follow "Upload Kickstart/AutoYaST File" 0s

And I enter "15-sp7-cobbler" as "kickstartLabel" 0s

And I select "SLE-15-SP7-TFTP" from "kstreeId" 0s

And I attach the file "/sle-15-sp7-autoyast-uyuni.xml" to "fileUpload" 0s

And I click on "Create" 0s

Then I should see a "Autoinstallation: 15-sp7-cobbler" text 0s

And I should see a "Autoinstallation Details" text 0s

Scenario:
Configure auto installation profile
< 1ms 7

When I enter "self_update=0" as "kernel_options" 0s

And I click on "Update" 0s

And I follow "Variables" 0s

And I enter "distrotree=SLE-15-SP7-TFTP\nregistration_key=1-TERMINAL-KEY-x86_64\nredhat_management_server=proxy.example.org" as "variables" text area 0s

And I click on "Update Variables" 0s

And I follow "Autoinstallation File" 0s

Then I should see a "SLE-15-SP7-TFTP" text 0s

Scenario:
Migration of Cobbler settings
< 1ms 4

Given cobblerd is running 0s

And cobbler settings are successfully migrated 0s

When I restart cobbler on the server 0s

Then service "cobblerd" is active on "server" 0s

Scenario:
PXE boot the PXE boot minion
< 1ms 6

When I set the default PXE menu entry to the target profile on the "server" 0s

And I reboot the Cobbler terminal "pxeboot_minion" 0s

And I wait for "60" seconds 0s

And I set the default PXE menu entry to the local boot on the "server" 0s

And I wait at most 1200 seconds until Salt master sees "pxeboot_minion" as "unaccepted" 0s

And I accept "pxeboot_minion" key in the Salt master 0s

Scenario:
Assure the PXE boot minion is onboarded
< 1ms 4

Given I am on the Systems page 0s

When I wait until I see the name of "pxeboot_minion", refreshing the page 0s

And I wait until onboarding is completed for "pxeboot_minion" 0s

Then "pxeboot_minion" should have been reformatted 0s

Scenario:
Check connection from PXE boot minion to the proxy
< 1ms 3

When I follow "Details" in the content area 0s

And I follow "Connection" in the content area 0s

Then I should see a "proxy.example.org" text 0s

Scenario:
Install a package on the PXE boot minion
< 1ms 10

When I install the GPG key of the test packages repository on the PXE boot minion 0s

And I follow "Software" in the content area 0s

And I follow "Install" 0s

And I enter "virgo-dummy-2.0-1.1" as the filtered package name 0s

And I click on the filter button 0s

And I check "virgo-dummy-2.0-1.1" in the list 0s

And I click on "Install Packages" 0s

And I click on "Confirm" 0s

Then I should see a "1 package install has been scheduled" text 0s

When I wait until event "Package Install/Upgrade scheduled by admin" is completed 0s

Scenario:
Download the profile from the UI
< 1ms 5

When I follow the left menu "Systems > Autoinstallation > Profiles" 0s

And I follow "15-sp7-cobbler" 0s

And I follow "Autoinstallation File" in the content area 0s

And I follow "Download Autoinstallation File" 0s

Then I should see a "<profile " text 0s

Scenario:
Cleanup: remove the auto installation profile
< 1ms 6

When I follow the left menu "Systems > Autoinstallation > Profiles" 0s

And I follow "15-sp7-cobbler" 0s

And I follow "Delete Autoinstallation" 0s

And I click on "Delete Autoinstallation" 0s

And I wait until I do not see "15-sp7-cobbler" text 0s

And I wait up to 5 minutes to see "TASK COMPLETE" in the last lines of "var/log/cobbler/cobbler.log" on "server" 0s

Scenario:
Cleanup: remove the auto installation distribution
< 1ms 6

When I follow the left menu "Systems > Autoinstallation > Distributions" 0s

And I follow "SLE-15-SP7-TFTP" 0s

And I follow "Delete Distribution" 0s

And I click on "Delete Distribution" 0s

And I wait until I do not see "SLE-15-SP7-TFTP" text 0s

And I wait up to 5 minutes to see "TASK COMPLETE" in the last lines of "var/log/cobbler/cobbler.log" on "server" 0s

Scenario:
Cleanup: remove the auto installation files
< 1ms 2

When I remove packages "tftpboot-installation-SLE-15-SP7-x86_64 expect" from this "build_host" 0s

And I remove the autoinstallation files from the server 0s

Scenario:
Cleanup: delete the PXE boot minion
< 1ms 3

When I delete "pxeboot_minion" system using the api 0s

And I wait until Salt client is inactive on the PXE boot minion 0s

Then "pxeboot_minion" should not be registered 0s

@flaky
Scenario:
Check for errors in Cobbler monitoring
< 1ms 1

Then the local logs for Cobbler should not contain errors 0s

@containerized_server @skip_if_github_validation @build_host @proxy @private_net @pxeboot_minion @scope_retail
Feature:PXE boot a Retail terminal behind a containerized proxy < 1ms 17

In order to manage my terminals in a Retail context
As the system administrator
I PXE boot one of the terminals

Scenario:
Log in as admin user
< 1ms 1

Given I am authorized for the "Admin" section 0s

Scenario:
Create hardware type group
< 1ms 6

When I follow the left menu "Systems > System Groups" 0s

And I follow "Create Group" 0s

And I enter "HWTYPE:Intel-Genuine" as "name" 0s

And I enter "Terminal hardware type: genuine Intel" as "description" 0s

And I click on "Create Group" 0s

Then I should see a "System group HWTYPE:Intel-Genuine created." text 0s

Scenario:
Create branch terminals group
< 1ms 6

When I follow the left menu "Systems > System Groups" 0s

And I follow "Create Group" 0s

And I enter "example" as "name" 0s

And I enter "Terminal branch: example.org" as "description" 0s

And I click on "Create Group" 0s

Then I should see a "System group example created." text 0s

Scenario:
Create all terminals group
< 1ms 6

When I follow the left menu "Systems > System Groups" 0s

And I follow "Create Group" 0s

And I enter "TERMINALS" as "name" 0s

And I enter "All terminals" as "description" 0s

And I click on "Create Group" 0s

Then I should see a "System group TERMINALS created." text 0s

Scenario:
Create all branch servers group
< 1ms 6

When I follow the left menu "Systems > System Groups" 0s

And I follow "Create Group" 0s

And I enter "SERVERS" as "name" 0s

And I enter "All branch servers" as "description" 0s

And I click on "Create Group" 0s

Then I should see a "System group SERVERS created." text 0s

Scenario:
Enable Saltboot Group formula for branch terminals group
< 1ms 7

When I follow the left menu "Systems > System Groups" 0s

And I follow "example" in the content area 0s

And I follow "Formulas" in the content area 0s

And I check the "saltboot-group" formula 0s

And I click on "Save" 0s

And I wait until I see "Formula saved." text 0s

Then the "saltboot-group" formula should be checked 0s

Scenario:
Parametrize the Saltboot Group formula
< 1ms 8

When I follow the left menu "Systems > System Groups" 0s

And I follow "example" in the content area 0s

And I follow "Formulas" in the content area 0s

And I follow first "Saltboot Group" in the content area 0s

And I enter "proxy.example.org" as "Image download server" 0s

And I check containerized proxy box 0s

And I click on "Save Formula" 0s

Then I should see a "Formula saved" text 0s

Scenario:
Enable Saltboot formula for hardware type group
< 1ms 7

When I follow the left menu "Systems > System Groups" 0s

And I follow "HWTYPE:Intel-Genuine" in the content area 0s

And I follow "Formulas" in the content area 0s

And I check the "saltboot" formula 0s

And I click on "Save" 0s

And I wait until I see "Formula saved." text 0s

Then the "saltboot" formula should be checked 0s

Scenario:
Parametrize the Saltboot formula
< 1ms 23

When I follow the left menu "Systems > System Groups" 0s

And I follow "HWTYPE:Intel-Genuine" in the content area 0s

And I follow "Formulas" in the content area 0s

And I follow first "Saltboot" in the content area 0s

And I click on "Expand All Sections" 0s

And I enter "disk1" in disk id field 0s

And I enter "/dev/vda" in disk device field 0s

And I select "msdos" in disk label field 0s

And I enter "p1" in first partition id field 0s

And I enter "256" in first partition size field 0s

And I select "swap" in first filesystem format field 0s

And I select "swap" in first partition flags field 0s

And I press "Add Item" in partitions section 0s

And I enter "p2" in second partition id field 0s

And I enter "/data" in second mount point field 0s

And I select "xfs" in second filesystem format field 0s

And I enter "secret-password" in second partition password field 0s

And I press "Add Item" in partitions section 0s

And I enter "p3" in third partition id field 0s

And I enter "/" in third mount point field 0s

And I enter the image name for "pxeboot_minion" in third OS image field 0s

And I click on "Save Formula" 0s

Then I should see a "Formula saved" text 0s

Scenario:
PXE boot the PXE boot minion
< 1ms 3

When I reboot the Retail terminal "pxeboot_minion" 0s

And I wait at most 180 seconds until Salt master sees "pxeboot_minion" as "unaccepted" 0s

And I accept "pxeboot_minion" key in the Salt master 0s

Scenario:
Assure the PXE boot minion is onboarded
< 1ms 12

Given I am on the Systems page 0s

When I wait until I see the name of "pxeboot_minion", refreshing the page 0s

And I follow this "pxeboot_minion" link 0s

And I follow "Events" 0s

And I follow "History" 0s

And I wait until I see "added system entitlement" text, refreshing the page 0s

And I wait until event "Apply states [saltboot]" is completed 0s

And I follow "Software" in the content area 0s

And I follow "Software Channels" in the content area 0s

And I wait until radio button "SLE-Product-SLES15-SP7-Pool for x86_64" is checked, refreshing the page 0s

And I wait until event "Package List Refresh" is completed 0s

Then "pxeboot_minion" should have been reformatted 0s

Scenario:
Check connection from terminal to branch server
< 1ms 4

When I navigate to the Systems overview page of this "pxeboot_minion" 0s

And I follow "Details" in the content area 0s

And I follow "Connection" in the content area 0s

Then I should see a "proxy.example.org" text 0s

Scenario:
Install a package on the new Retail terminal
< 1ms 11

When I navigate to the Systems overview page of this "pxeboot_minion" 0s

And I install the GPG key of the test packages repository on the PXE boot minion 0s

And I follow "Software" in the content area 0s

And I follow "Install" 0s

And I enter "virgo" as the filtered package name 0s

And I click on the filter button 0s

And I check "virgo-dummy-2.0-1.1" in the list 0s

And I click on "Install Packages" 0s

And I click on "Confirm" 0s

Then I should see a "1 package install has been scheduled" text 0s

When I wait until event "Package Install/Upgrade scheduled by admin" is completed 0s

Scenario:
Remove the package from the new Retail terminal
< 1ms 10

When I navigate to the Systems overview page of this "pxeboot_minion" 0s

And I follow "Software" in the content area 0s

And I follow "List / Remove" 0s

And I enter "virgo" as the filtered package name 0s

And I click on the filter button 0s

And I check "virgo-dummy-2.0-1.1" in the list 0s

And I click on "Remove Packages" 0s

And I click on "Confirm" 0s

Then I should see a "1 package removal has been scheduled" text 0s

When I wait until event "Package Removal scheduled by admin" is completed 0s

Scenario:
Cleanup: let the terminal be reinstalled again
< 1ms 6

When I navigate to the Systems overview page of this "pxeboot_minion" 0s

And I follow "Remote Command" 0s

And I enter "#!/bin/sh\nrm /etc/ImageVersion*" as "script_body" text area 0s

And I click on "Schedule" 0s

Then I should see a "Remote Command has been scheduled" text 0s

When I wait until event "Remote Command" is completed 0s

Scenario:
Cleanup: delete the new Retail terminal
< 1ms 7

When I navigate to the Systems overview page of this "pxeboot_minion" 0s

And I follow "Delete System" 0s

Then I should see a "Confirm System Profile Deletion" text 0s

When I click on "Delete Profile" 0s

And I wait until I see "has been deleted" text 0s

And I wait until Salt client is inactive on the PXE boot minion 0s

Then "pxeboot_minion" should not be registered 0s

Scenario:
Cleanup: delete the terminal groups
< 1ms 17

When I follow the left menu "Systems > System Groups" 0s

And I follow "HWTYPE:Intel-Genuine" in the content area 0s

And I follow "Delete Group" in the content area 0s

And I click on "Confirm Deletion" 0s

Then I should see a "deleted" text 0s

When I follow "example" in the content area 0s

And I follow "Delete Group" in the content area 0s

And I click on "Confirm Deletion" 0s

Then I should see a "deleted" text 0s

When I follow "TERMINALS" in the content area 0s

And I follow "Delete Group" in the content area 0s

And I click on "Confirm Deletion" 0s

Then I should see a "deleted" text 0s

When I follow "SERVERS" in the content area 0s

And I follow "Delete Group" in the content area 0s

And I click on "Confirm Deletion" 0s

Then I should see a "deleted" text 0s

@containerized_server @skip_if_github_validation @proxy @private_net @pxeboot_minion @scope_retail
Feature:Mass import of Retail terminals behind a containerized proxy < 1ms 9

In order to manage my terminals in a Retail context
As the system administrator
I perform a mass import of several virtual terminals and one real minion

Scenario:
Log in as admin user
< 1ms 1

Given I am authorized for the "Admin" section 0s

Scenario:
Mass import of terminals
< 1ms 4

When I prepare the retail configuration file on server 0s

And I import the retail configuration using retail_yaml command 0s

And I am on the Systems page 0s

Then I should see the terminals imported from the configuration file 0s

Scenario:
Bootstrap the PXE boot minion
< 1ms 6

When I create the bootstrap script for "proxy.example.org" hostname and "1-TERMINAL-KEY-x86_64" activation key on "server" 0s

And I bootstrap pxeboot minion via bootstrap script on the proxy 0s

And I wait at most 350 seconds until Salt master sees "pxeboot_minion" as "unaccepted" 0s

And I accept key of pxeboot minion in the Salt master 0s

Then I follow the left menu "Systems > System List > All" 0s

And I wait until I see the name of "pxeboot_minion", refreshing the page 0s

Scenario:
Check connection from bootstrapped terminal to proxy
< 1ms 5

Given I am on the Systems page 0s

When I follow "pxeboot" terminal 0s

And I follow "Details" in the content area 0s

And I follow "Connection" in the content area 0s

Then I should see a "proxy.example.org" text 0s

Scenario:
Install a package on the bootstrapped terminal
< 1ms 11

Given I am on the Systems page 0s

When I follow "pxeboot" terminal 0s

And I follow "Software" in the content area 0s

And I follow "Install" 0s

And I enter "virgo" as the filtered package name 0s

And I click on the filter button 0s

And I check "virgo-dummy-2.0-1.1" in the list 0s

And I click on "Install Packages" 0s

And I click on "Confirm" 0s

Then I should see a "1 package install has been scheduled" text 0s

When I wait until event "Package Install/Upgrade scheduled by admin" is completed 0s

Scenario:
Remove the package from the bootstrapped terminal
< 1ms 11

Given I am on the Systems page 0s

When I follow "pxeboot" terminal 0s

And I follow "Software" in the content area 0s

And I follow "List / Remove" 0s

And I enter "virgo" as the filtered package name 0s

And I click on the filter button 0s

And I check "virgo-dummy-2.0-1.1" in the list 0s

And I click on "Remove Packages" 0s

And I click on "Confirm" 0s

Then I should see a "1 package removal has been scheduled" text 0s

When I wait until event "Package Removal scheduled by admin" is completed 0s

Scenario:
Cleanup: make sure salt-minion is stopped after mass import
< 1ms 1

When I wait until Salt client is inactive on the PXE boot minion 0s

Scenario:
Cleanup: delete all imported Retail terminals
< 1ms 3

Given I am on the Systems page 0s

When I delete all the imported terminals 0s

Then I should not see any terminals imported from the configuration file 0s

Scenario:
Cleanup: delete the terminal groups generated by retail_yaml command
< 1ms 17

When I follow the left menu "Systems > System Groups" 0s

And I follow "HWTYPE:Intel-Genuine" in the content area 0s

And I follow "Delete Group" in the content area 0s

And I click on "Confirm Deletion" 0s

Then I should see a "deleted" text 0s

When I follow "example.org" in the content area 0s

And I follow "Delete Group" in the content area 0s

And I click on "Confirm Deletion" 0s

Then I should see a "deleted" text 0s

When I follow "TERMINALS" in the content area 0s

And I follow "Delete Group" in the content area 0s

And I click on "Confirm Deletion" 0s

Then I should see a "deleted" text 0s

When I follow "SERVERS" in the content area 0s

And I follow "Delete Group" in the content area 0s

And I click on "Confirm Deletion" 0s

Then I should see a "deleted" text 0s

@skip_if_github_validation @skip_if_containerized_server
Feature:Restart the spacewalk services via UI < 1ms 1

Scenario:
Restart the SUSE Multi-Linux Manager through the WebUI Admin option
< 1ms 8

Given I am authorized for the "Admin" section 0s

When I follow the left menu "Admin > Manager Configuration > Restart" 0s

And I check "restart" 0s

And I click on "Restart" 0s

And I wait until I see "restarting. If this page" text 0s

And I wait at most "300" seconds until I do not see "restarting. If this page" text 0s

And I refresh the page 0s

Then I follow the left menu "Admin > Manager Configuration > Restart" 0s

@skip_if_github_validation @scope_visualization @sle_minion @flaky
Feature:Correct timezone display 54s 868ms 11

Scenario:
Log in as admin user
1s 821ms 1

Given I am authorized for the "Admin" section 1s 821ms

Scenario:
Create a new user in a timezone different than server's timezone
1s 7ms 11

When I follow the left menu "Users > User List > Active" 178ms

And I follow "Create User" 273ms

And I enter "MalaysianUser" as "login" 67ms

And I enter "MalaysianUser" as "desiredpassword" 63ms

And I enter "MalaysianUser" as "desiredpasswordConfirm" 66ms

And I select "Mr." from "prefix" 48ms

And I enter "Test" as "firstNames" 54ms

And I enter "User" as "lastName" 55ms

And I enter "galaxy-noise@localhost" as "email" 73ms

And I select "(GMT+0800) Malaysia" from "timezone" 63ms

And I click on "Create Login" 62ms

Scenario:
Add roles for the Malaysian user
11s 621ms 9

When I follow the left menu "Users > User List > Active" 91ms

And I follow "MalaysianUser" 378ms

And the "role_satellite_admin" checkbox should be disabled 10s

And I check "role_org_admin" 77ms

And I check "role_system_group_admin" 74ms

And I check "role_channel_admin" 74ms

And I check "role_activation_key_admin" 75ms

And I check "role_config_admin" 75ms

And I click on "Update" 773ms

Scenario:
Login as the new Malaysian user
1s 804ms 2

Given I am authorized as "MalaysianUser" with password "MalaysianUser" 1s 793ms

Then I should see a "MalaysianUser" link 11ms

Scenario:
Schedule a remote script to run now and see the correct timezone details in history
19s 880ms 10

Given I am on the Systems overview page of this "sle_minion" 1s 711ms

When I follow "Remote Command" in the content area 69ms

And I enter as remote command this script in #!/bin/bash ls 49ms

And I click on "Schedule" 58ms

And I follow "Events" in the content area 716ms

And I follow "Pending" in the content area 64ms

And I wait at most 180 seconds until I do not see "Remote Command on" text, refreshing the page 16s 596ms

And I follow "History" in the content area 71ms

And I follow first "scheduled by MalaysianUser" 479ms

Then I should see a "MYT" text 61ms

Scenario:
Login as the new Malaysian user if the previous scenario failed
507ms 2

Given I am authorized as "MalaysianUser" with password "MalaysianUser" 499ms

Then I should see a "MalaysianUser" link 7ms

Scenario:
Schedule a remote script in the future and see the correct timezone as a pop up
2s 385ms 6

Given I am on the Systems overview page of this "sle_minion" 1s 497ms

When I follow "Remote Command" in the content area 59ms

And I enter as remote command this script in #!/bin/bash ls 48ms

And I enter "00:00" as "date_timepicker_widget_input" 70ms

And I click on "Schedule" 631ms

Then I should see a "00:00:00 MYT" text 77ms

Scenario:
Login as the new Malaysian user if the previous scenario failed
506ms 2

Given I am authorized as "MalaysianUser" with password "MalaysianUser" 497ms

Then I should see a "MalaysianUser" link 8ms

Scenario:
Cleanup: Log in as admin user again and remove scheduled actions
3s 419ms 2

- Try to cancel "Remote Command on uyuni-master-suse-minion.sumaci.aws. scheduled by MalaysianUser" action
- Removed "Remote Command on uyuni-master-suse-minion.sumaci.aws. scheduled by MalaysianUser" action

Given I am authorized for the "Admin" section 2s 119ms

And I cancel all scheduled actions via API 1s 300ms

Scenario:
Cleanup: Remove role
11s 409ms 9

When I follow the left menu "Users > User List > Active" 179ms

And I follow "MalaysianUser" 417ms

And I uncheck "role_org_admin" 10s 64ms

And I click on "Update" 656ms

Then I should see "role_org_admin" as unchecked 16ms

And I should see "role_system_group_admin" as checked 18ms

And I should see "role_channel_admin" as checked 18ms

And I should see "role_activation_key_admin" as checked 19ms

And I should see "role_config_admin" as checked 19ms

Scenario:
Cleanup: Delete user
504ms 1

When I delete user "MalaysianUser" 504ms

@scope_ansible @sle_minion @bug_reported @flaky
Feature:Operate an Ansible control node in a normal minion 12m 22s 407ms 14 3 2

Scenario:
Log in as org admin user
424ms 1

Given I am authorized for the "Admin" section 424ms

Scenario:
Pre-requisite: Deploy test playbooks and inventory file
3s 884ms 1

When I deploy testing playbooks and inventory files to "sle_minion" 3s 884ms

@susemanager
Scenario:
Pre-requisite: Subscribe SUSE minions to SLE-Module-Python3-15-SP7-Pool for x86_64
< 1ms 9

Given I am on the Systems overview page of this "sle_minion" 0s

When I follow "Software" in the content area 0s

And I follow "Software Channels" in the content area 0s

And I check "SLE-Module-Python3-15-SP7-Pool for x86_64" by label 0s

And I click on "Next" 0s

And I click on "Confirm" 0s

And I wait until I see "Changing the channels has been scheduled." text 0s

And I follow "scheduled" 0s

And I wait until I see "1 system successfully completed this action" text, refreshing the page 0s

Scenario:
Enable "Ansible control node" system type
3s 404ms 5

Given I am on the Systems overview page of this "sle_minion" 1s 51ms

When I follow "Properties" in the content area 75ms

And I check "ansible_control_node" 85ms

And I click on "Update Properties" 2s 97ms

Then I wait until I see "Ansible Control Node type has been applied." text 94ms

Scenario:
Apply highstate and check that Ansible is installed
57s 338ms 5

Given I am on the Systems overview page of this "sle_minion" 1s 68ms

When I follow "States" in the content area 67ms

And I click on "Apply Highstate" 65ms

And I wait until event "Apply highstate scheduled" is completed 55s 327ms

Then "ansible" should be installed on "sle_minion" 807ms

Scenario:
The Ansible tab appears in the system overview page
1s 107ms 3

Given I am on the Systems overview page of this "sle_minion" 966ms

When I follow "Ansible" in the content area 77ms

Then I should see a "Ansible Control Node Configuration" text 63ms

Scenario:
Configure some inventory and playbooks path
1s 467ms 7

Given I am on the Systems overview page of this "sle_minion" 968ms

When I follow "Ansible" in the content area 59ms

Then I should see a "Ansible Control Node Configuration" text 61ms

And I enter "/srv/playbooks/" as "new_playbook_path_input" 165ms

And I click on "new_playbook_path_save" 56ms

And I enter "/srv/playbooks/orion_dummy/hosts" as "new_inventory_path_input" 98ms

And I click on "new_inventory_path_save" 58ms

Scenario:
Display inventories
4m 30s 74ms 6 1

Given I am on the Systems overview page of this "sle_minion" 1s 94ms

When I follow "Ansible" in the content area 61ms

And I follow "Inventories" in the content area 66ms

And I wait until I see "/srv/playbooks/orion_dummy/hosts" text 252ms

And I click on "/srv/playbooks/orion_dummy/hosts" 55ms

Then I wait until I see "myself" text, refreshing the page 4m 13s 53ms Show Error + 
                                            
 execution expired (Timeout::Error)
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/step_definitions/navigation_steps.rb:70:in `/^I wait until I see "([^"]*)" (text|regex), refreshing the page$/'
features/secondary/min_ansible_control_node.feature:63:in `I wait until I see "myself" text, refreshing the page'

15s 490ms Show Info + 
15:11:08:000 - 15:15:24:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/systems/details/ansible/inventories?sid=1000010020&
Screenshot +

Scenario:
Discover playbooks and display them
6s 521ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 50ms

When I follow "Ansible" in the content area 72ms

And I follow "Playbooks" in the content area 64ms

And I wait until I see "/srv/playbooks" text 248ms

And I click on "/srv/playbooks" 74ms

Then I wait until I see "/srv/playbooks/orion_dummy/playbook_orion_dummy.yml" text 4s 942ms

And I wait until I see "/srv/playbooks/basic_tests.yml" text 67ms

Scenario:
Run a playbook using custom inventory
48s 475ms 13

Given I am on the Systems overview page of this "sle_minion" 1s 40ms

When I follow "Ansible" in the content area 63ms

And I follow "Playbooks" in the content area 60ms

And I wait until I see "/srv/playbooks" text 245ms

And I click on "/srv/playbooks" 74ms

And I wait until I see "/srv/playbooks/orion_dummy/playbook_orion_dummy.yml" text 4s 862ms

And I click on "orion_dummy/playbook_orion_dummy.yml" 58ms

And I wait until I see "Playbook Content" text 981ms

And I select "/srv/playbooks/orion_dummy/hosts" from "inventory-path-select" 1s 130ms

And I click on "Schedule" 71ms

Then I should see a "Playbook execution has been scheduled" text 369ms

And I wait until event "Execute playbook 'playbook_orion_dummy.yml' scheduled" is completed 38s 758ms

And file "/tmp/file.txt" should exist on "sle_minion" 756ms

Scenario:
Run the basic tests playbook
44s 510ms 19

Given I am on the Systems overview page of this "sle_minion" 1s 47ms

When I follow "Ansible" in the content area 78ms

And I follow "Playbooks" in the content area 64ms

And I wait until I see "/srv/playbooks" text 155ms

And I click on "/srv/playbooks" 56ms

And I wait until I see "/srv/playbooks/basic_tests.yml" text 4s 951ms

And I click on "basic_tests.yml" 61ms

And I wait until I see "Playbook Content" text 977ms

And I click on "Schedule" 88ms

And I wait until I see "Playbook execution has been scheduled" text 461ms

And I wait for "2" seconds 2s

And I follow "scheduled" in the content area 73ms

Then I wait until I see "1 system successfully completed this action" text or "1 system failed to complete this action" text, refreshing the page 33s 484ms

When I follow "1 system" 293ms

And I wait until I see the system name of "sle_minion" 65ms

And I follow this "sle_minion" link 437ms

Then I should see a "42" text 72ms

And I should see a "101010" text 71ms

And I should see a "(code 0)" text 69ms

Scenario:
Run the basic tests playbook while editing variables and changing their values
45s 241ms 21

Given I am on the Systems overview page of this "sle_minion" 960ms

When I follow "Ansible" in the content area 72ms

And I follow "Playbooks" in the content area 65ms

And I wait until I see "/srv/playbooks" text 150ms

And I click on "/srv/playbooks" 56ms

And I wait until I see "/srv/playbooks/basic_tests.yml" text 4s 831ms

And I click on "basic_tests.yml" 60ms

And I wait until I see "Playbook Content" text 1s 61ms

And I click on "Edit variables" 104ms

And I enter data from table with value as field name 798ms
(21 + 21) * 100 p1
p2
p3
p4
p5

And I click on "Save" 94ms

And I click on "Schedule" 69ms

And I wait until I see "Playbook execution has been scheduled" text 462ms

And I wait for "2" seconds 2s

And I follow "scheduled" in the content area 72ms

Then I wait until I see "1 system successfully completed this action" text or "1 system failed to complete this action" text, refreshing the page 33s 498ms

When I follow "1 system" 288ms

And I wait until I see the system name of "sle_minion" 67ms

And I follow this "sle_minion" link 384ms

Then I should see a "4200" text 73ms

And I should see a "(code 0)" text 67ms

Scenario:
Run the basic tests playbook while editing the EMPTY variables and changing their values
45s 520ms 22

Given I am on the Systems overview page of this "sle_minion" 1s 100ms

When I follow "Ansible" in the content area 76ms

And I follow "Playbooks" in the content area 67ms

And I wait until I see "/srv/playbooks" text 244ms

And I click on "/srv/playbooks" 56ms

And I wait until I see "/srv/playbooks/basic_tests.yml" text 4s 853ms

And I click on "basic_tests.yml" 59ms

And I wait until I see "Playbook Content" text 1s 22ms

And I click on "Edit variables" 86ms

And I enter data from table with value as field name 1s 12ms
1 p1
2 p2
3 p3
4 p4
5 p5
(21 + 21) * 1000 p1_empty
(21 + 21) * 100 + (21 + 21) p2_empty

And I click on "Save" 96ms

And I click on "Schedule" 70ms

And I wait until I see "Playbook execution has been scheduled" text 296ms

And I wait for "2" seconds 2s

And I follow "scheduled" in the content area 70ms

Then I wait until I see "1 system successfully completed this action" text or "1 system failed to complete this action" text, refreshing the page 33s 385ms

When I follow "1 system" 289ms

And I wait until I see the system name of "sle_minion" 66ms

And I follow this "sle_minion" link 447ms

Then I should see a "42000" text 71ms

And I should see a "4242" text 74ms

And I should see a "(code 0)" text 71ms

Scenario:
Run the basic tests playbook while editing the NULL variable and changing its value
33s 678ms 10 11 1

Given I am on the Systems overview page of this "sle_minion" 976ms

When I follow "Ansible" in the content area 77ms

And I follow "Playbooks" in the content area 68ms

And I wait until I see "/srv/playbooks" text 154ms

And I click on "/srv/playbooks" 56ms

And I wait until I see "/srv/playbooks/basic_tests.yml" text 4s 955ms

And I click on "basic_tests.yml" 59ms

And I wait until I see "Playbook Content" text 971ms

And I click on "Edit variables" 105ms

And I enter data from table with value as field name 10s 918ms
1 p1
2 p2
3 p3
4 p4
5 p5
1e p1_empty
2e p2_empty
256 * 256 p_null
Show Error + 
                                            
 Unable to find field "p_null" that is not disabled (Capybara::ElementNotFound)
./features/step_definitions/navigation_steps.rb:269:in `/^I enter "([^"]*)" as "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:274:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:273:in `each'
./features/step_definitions/navigation_steps.rb:273:in `/^I enter data from table with value as field name$/'
features/secondary/min_ansible_control_node.feature:180:in `I enter data from table with value as field name'

And I click on "Save" 0s

And I click on "Schedule" 0s

And I wait until I see "Playbook execution has been scheduled" text 0s

And I wait for "2" seconds 0s

And I follow "scheduled" in the content area 0s

Then I wait until I see "1 system successfully completed this action" text or "1 system failed to complete this action" text, refreshing the page 0s

When I follow "1 system" 0s

And I wait until I see the system name of "sle_minion" 0s

And I follow this "sle_minion" link 0s

Then I should see a "65536" text 0s

And I should see a "(code 0)" text 0s

15s 335ms Show Info + 
15:18:56:000 - 15:19:15:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/systems/details/ansible/playbooks?sid=1000010020&
Screenshot +

Scenario:
Run the basic tests playbook on SAVE operation of YAML editor with pre-crafted strings
1m 19s 656ms 20 2 1

Given I am on the Systems overview page of this "sle_minion" 1s 40ms

When I follow "Ansible" in the content area 82ms

And I follow "Playbooks" in the content area 68ms

And I wait until I see "/srv/playbooks" text 238ms

And I click on "/srv/playbooks" 80ms

And I wait until I see "/srv/playbooks/basic_tests.yml" text 4s 883ms

And I click on "basic_tests.yml" 60ms

And I wait until I see "Playbook Content" text 959ms

And I click on "Edit variables" 107ms

And I click on "Edit YAML" 77ms

And I click on "Save" 88ms

And I click on "Schedule" 68ms

And I wait until I see "Playbook execution has been scheduled" text 292ms

And I wait for "2" seconds 2s

And I follow "scheduled" in the content area 72ms

Then I wait until I see "1 system successfully completed this action" text or "1 system failed to complete this action" text, refreshing the page 43s 432ms

When I follow "1 system" 368ms

And I wait until I see the system name of "sle_minion" 64ms

And I follow this "sle_minion" link 382ms

Then I should see a "42" text 10s 26ms Show Error + 
                                            
 Text '42' not found (ScriptError)
./features/step_definitions/navigation_steps.rb:677:in `/^I should see a "([^"]*)" text$/'
features/secondary/min_ansible_control_node.feature:221:in `I should see a "42" text'

And I should see a "101010" text 0s

And I should see a "(code 0)" text 0s

15s 261ms Show Info + 
15:19:30:000 - 15:20:36:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010020&aid=294
Screenshot +

Scenario:
Run the basic tests playbook on SAVE operation of YAML editor with safe values
45s 565ms 26

Given I am on the Systems overview page of this "sle_minion" 947ms

When I follow "Ansible" in the content area 83ms

And I follow "Playbooks" in the content area 66ms

And I wait until I see "/srv/playbooks" text 151ms

And I click on "/srv/playbooks" 62ms

And I wait until I see "/srv/playbooks/basic_tests.yml" text 4s 903ms

And I click on "basic_tests.yml" 58ms

And I wait until I see "Playbook Content" text 985ms

And I click on "Edit variables" 104ms

And I enter data from table with value as field name 831ms
abc p1
def p2
ghi p3
jkl p4
16 * 16 * 16 p5

And I click on "Edit YAML" 68ms

And I click on "Save" 94ms

And I click on "Schedule" 71ms

And I wait until I see "Playbook execution has been scheduled" text 305ms

And I wait for "2" seconds 2s

And I follow "scheduled" in the content area 67ms

Then I wait until I see "1 system successfully completed this action" text or "1 system failed to complete this action" text, refreshing the page 33s 521ms

When I follow "1 system" 287ms

And I wait until I see the system name of "sle_minion" 65ms

And I follow this "sle_minion" link 454ms

Then I should see a "abc" text 73ms

And I should see a "def" text 80ms

And I should see a "ghi" text 72ms

And I should see a "jkl" text 68ms

And I should see a "4096" text 67ms

And I should see a "(code 0)" text 68ms

Scenario:
Cleanup: Disable Ansible and remove test playbooks and inventory file
15s 416ms 7

Given I am on the Systems overview page of this "sle_minion" 954ms

When I follow "Properties" in the content area 74ms

And I uncheck "ansible_control_node" 10s 87ms

And I click on "Update Properties" 1s 653ms

Then I should see a "System properties changed" text 91ms

And I remove package "orion-dummy" from this "sle_minion" without error control 2s 137ms

And I remove "/tmp/file.txt" from "sle_minion" 418ms

@susemanager
Scenario:
Cleanup: Unsubscribe SUSE minions from SLE-Module-Python3-15-SP7-Pool for x86_64
< 1ms 9

Given I am on the Systems overview page of this "sle_minion" 0s

When I follow "Software" in the content area 0s

And I follow "Software Channels" in the content area 0s

And I uncheck "SLE-Module-Python3-15-SP7-Pool for x86_64" by label 0s

And I click on "Next" 0s

And I click on "Confirm" 0s

And I wait until I see "Changing the channels has been scheduled." text 0s

And I follow "scheduled" 0s

And I wait until I see "1 system successfully completed this action" text, refreshing the page 0s

Scenario:
Cleanup: Apply highstate to disable the minion as an "Ansible control node"
40s 120ms 4

Given I am on the Systems overview page of this "sle_minion" 945ms

When I follow "States" in the content area 74ms

And I click on "Apply Highstate" 61ms

And I wait until event "Apply highstate scheduled" is completed 39s 39ms

@sle_minion @proxy
Feature:Move a minion from a proxy to direct connection 10m 49s 687ms 13

Scenario:
Log in as org admin user
1s 620ms 1

Given I am authorized 1s 620ms

Scenario:
Delete minion system profile before bootstrap
4m 7s 224ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 763ms

When I follow "Delete System" 458ms

Then I should see a "Confirm System Profile Deletion" text 64ms

When I click on "Delete Profile" 71ms

And I wait until I see "has been deleted" text 4m 3s 742ms

And I wait until Salt client is inactive on "sle_minion" 723ms

Then "sle_minion" should not be registered 401ms

Scenario:
Bootstrap a minion
1m 55s 31ms 11

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 80ms

Then I should see a "Bootstrap Minions" text 64ms

When I enter the hostname of "sle_minion" as "hostname" 142ms

And I enter "22" as "port" 54ms

And I enter "root" as "user" 60ms

And I enter "linux" as "password" 61ms

And I select "1-SUSE-KEY-x86_64" from "activationKeys" 74ms

And I select the hostname of "proxy" from "proxies" if present 62ms

And I click on "Bootstrap" 62ms

And I wait until I see "Bootstrap process initiated." text 31s 656ms

And I wait until onboarding is completed for "sle_minion" 1m 22s 713ms

Scenario:
Check the new bootstrapped minion in System Overview page
2s 341ms 3

It took 1 seconds to contact the minion

When I follow the left menu "Salt > Keys" 134ms

Then I should see a "accepted" text 331ms

And the Salt master can reach "sle_minion" 1s 875ms

Scenario:
Check initial connection from minion to proxy
1s 300ms 4

Given I am on the Systems overview page of this "sle_minion" 1s 99ms

When I follow "Details" in the content area 72ms

And I follow "Connection" in the content area 64ms

Then I should see "proxy" short hostname 64ms

Scenario:
Check initial registration on proxy of minion
1s 313ms 4

Given I am on the Systems overview page of this "proxy" 1s 77ms

When I follow "Details" in the content area 60ms

And I follow "Proxy" in the content area 79ms

Then I should see "sle_minion" hostname 96ms

Scenario:
Change from proxy to direct connection
36s 966ms 11

Given I am on the Systems overview page of this "sle_minion" 1s 44ms

When I follow "Details" in the content area 61ms

And I follow "Connection" in the content area 59ms

And I follow "Change" in the content area 65ms

And I select "None" from "proxies" 68ms

And I click on "Change Proxy" 56ms

And I wait until I see "scheduled" text 353ms

And I follow "Events" 409ms

And I follow "History" 508ms

And I wait until I see the event "Apply states [bootstrap.set_proxy] scheduled" completed during last minute, refreshing the page 11s 449ms

And I wait until I see the event "Apply states [channels] scheduled" completed during last minute, refreshing the page 22s 890ms

Scenario:
Check direct connection
1s 216ms 4

Given I am on the Systems overview page of this "sle_minion" 1s 34ms

When I follow "Details" in the content area 61ms

And I follow "Connection" in the content area 61ms

Then I should see a "This system connects directly and not through a Proxy" text 58ms

Scenario:
Change connection back to a proxy via SSM
2m 1s 795ms 10

Given I wait for "120" seconds 2m

When I follow the left menu "Systems > System List > All" 130ms

And I click on the clear SSM button 76ms

And I check the "sle_minion" client 427ms

And I should see "1" systems selected for SSM 122ms

And I follow the left menu "Systems > System Set Manager > Overview" 475ms

And I follow "proxy server" in the content area 69ms

And I select the hostname of "proxy" from "proxies" if present 71ms

And I click on "Change Proxy" 57ms

And I wait until I see "scheduled" text 365ms

Scenario:
Check events on the minion
36s 394ms 5

Given I am on the Systems overview page of this "sle_minion" 1s 150ms

And I follow "Events" 458ms

And I follow "History" 427ms

And I wait until I see the event "Apply states [bootstrap.set_proxy] scheduled" completed during last minute, refreshing the page 11ms

And I wait until I see the event "Apply states [channels] scheduled" completed during last minute, refreshing the page 34s 345ms

Scenario:
Check registration on proxy of minion
1s 241ms 4

Given I am on the Systems overview page of this "proxy" 1s 12ms

When I follow "Details" in the content area 68ms

And I follow "Proxy" in the content area 65ms

Then I should see "sle_minion" hostname 94ms

Scenario:
Check connection from minion to proxy
1s 213ms 4

Given I am on the Systems overview page of this "sle_minion" 1s 19ms

When I follow "Details" in the content area 61ms

And I follow "Connection" in the content area 65ms

Then I should see "proxy" short hostname 66ms

Scenario:
Check events history for failures on the minion
1m 22s 27ms 2

Given I am on the Systems overview page of this "sle_minion" 1s 70ms

Then I check for failed events on history event page 1m 20s 957ms

@ssh_minion @scope_salt_ssh @proxy
Feature:Move a SSH minion from a proxy to direct connection 7m 10s 410ms 11

Scenario:
Log in as org admin user
2s 782ms 1

Given I am authorized 2s 782ms

Scenario:
Delete minion system profile before bootstrap
17s 892ms 6

Given I am on the Systems overview page of this "ssh_minion" 1s 827ms

When I follow "Delete System" 550ms

Then I should see a "Confirm System Profile Deletion" text 63ms

When I click on "Delete Profile" 61ms

And I wait until I see "has been deleted" text 14s 933ms

Then "ssh_minion" should not be registered 456ms

Scenario:
Bootstrap a minion
2m 15s 972ms 11

The hostname of ssh_minion is uyuni-master-suse-sshminion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 80ms

Then I should see a "Bootstrap Minions" text 69ms

When I check "manageWithSSH" 101ms

And I enter the hostname of "ssh_minion" as "hostname" 141ms

And I enter "root" as "user" 59ms

And I enter "linux" as "password" 62ms

And I select "1-SUSE-SSH-KEY-x86_64" from "activationKeys" 69ms

And I select the hostname of "proxy" from "proxies" if present 60ms

And I click on "Bootstrap" 60ms

And I wait at most 480 seconds until I see "Bootstrap process initiated." text 41s 77ms

And I wait until onboarding is completed for "ssh_minion" 1m 34s 189ms

Scenario:
Check initial connection from minion to proxy
1s 248ms 4

Given I am on the Systems overview page of this "ssh_minion" 1s 40ms

When I follow "Details" in the content area 72ms

And I follow "Connection" in the content area 68ms

Then I should see "proxy" short hostname 66ms

Scenario:
Check initial registration on proxy of minion
1s 291ms 4

Given I am on the Systems overview page of this "proxy" 1s 65ms

When I follow "Details" in the content area 58ms

And I follow "Proxy" in the content area 65ms

Then I should see "ssh_minion" hostname 101ms

Scenario:
Change from proxy to direct connection
36s 931ms 10

Given I am on the Systems overview page of this "ssh_minion" 1s 72ms

When I follow "Details" in the content area 59ms

And I follow "Connection" in the content area 56ms

And I follow "Change" in the content area 67ms

And I select "None" from "proxies" 70ms

And I click on "Change Proxy" 59ms

And I wait until I see "scheduled" text 354ms

And I follow "Events" 397ms

And I follow "History" 410ms

And I wait until I see the event "Apply states [channels] scheduled" completed during last minute, refreshing the page 34s 382ms

Scenario:
Check direct connection
1s 266ms 4

Given I am on the Systems overview page of this "ssh_minion" 1s 85ms

When I follow "Details" in the content area 61ms

And I follow "Connection" in the content area 59ms

Then I should see a "This system connects directly and not through a Proxy" text 60ms

Scenario:
Change connection to a proxy
2m 48s 355ms 11

Given I wait for "120" seconds 2m

Given I am on the Systems overview page of this "ssh_minion" 1s 54ms

When I follow "Details" in the content area 59ms

And I follow "Connection" in the content area 57ms

And I follow "Change" in the content area 63ms

And I select the hostname of "proxy" from "proxies" if present 94ms

And I click on "Change Proxy" 56ms

And I wait until I see "scheduled" text 350ms

And I follow "Events" 394ms

And I follow "History" 483ms

And I wait until I see the event "Apply states [channels] scheduled" completed during last minute, refreshing the page 45s 741ms

Scenario:
Check registration on proxy of minion
1s 257ms 4

Given I am on the Systems overview page of this "proxy" 1s 19ms

When I follow "Details" in the content area 62ms

And I follow "Proxy" in the content area 64ms

Then I should see "ssh_minion" hostname 111ms

Scenario:
Check connection from minion to proxy
1s 234ms 4

Given I am on the Systems overview page of this "ssh_minion" 1s 50ms

When I follow "Details" in the content area 58ms

And I follow "Connection" in the content area 61ms

Then I should see "proxy" short hostname 63ms

Scenario:
Check events history for failures on the minion
1m 2s 179ms 2

Given I am on the Systems overview page of this "ssh_minion" 1s 157ms

Then I check for failed events on history event page 1m 1s 22ms

Feature:Sanity check that all logfiles exist 6s 394ms 1

In order to be secure
As an authorized user
I want to watch different logfiles

Scenario:
All logfiles should be available
6s 394ms 9

Then I wait until file "/var/log/rhn/rhn_web_ui.log" exists on server 1s 15ms

And I wait until file "/var/log/rhn/rhn_web_api.log" exists on server 673ms

And I wait until file "/var/log/rhn/rhn_web_frontend.log" exists on server 678ms

And I wait until file "/var/log/rhn/rhn_taskomatic_daemon.log" exists on server 641ms

And I wait until file "/var/log/rhn/search/rhn_search_daemon.log" exists on server 683ms

And I wait until file "/var/log/rhn/search/rhn_search.log" exists on server 681ms

And I wait until file "/var/log/rhn/reposync.log" exists on server 642ms

And I wait until file "/var/log/salt/master" exists on server 665ms

And I wait until file "/var/log/salt/api" exists on server 711ms

@scope_cobbler
Feature:Run Cobbler Sync via WebUI 25s 167ms 6 1

Scenario:
Login as admin
2s 55ms 1

Given I am authorized for the "Admin" section 2s 55ms

Scenario:
Start Cobbler monitoring
7s 345ms 2

When I start local monitoring of Cobbler 6s 694ms

And I backup Cobbler settings file 650ms

@uyuni
Scenario:
Check that the Cobbler Settings Page exists
701ms 7

When I follow the left menu "Admin > Manager Configuration > Cobbler" 418ms

Then I should see a "Uyuni Configuration - Cobbler. " text 68ms

And I should see a "Setup your Uyuni Cobbler settings below. " text 58ms

And I should see a "Cobbler sync is used to repair or rebuild the contents /srv/tftpboot or /srv/www/cobbler when manual modification of cobbler has occurred. " text 57ms

And I should see a "For more information refer to the 'cobbler' man page. " text 59ms

And I should see a "Run Cobbler Sync" text in the content area 22ms

And I should see a "Update" button 17ms

@susemanager
Scenario:
Check that the Cobbler Settings Page exists
< 1ms 7

When I follow the left menu "Admin > Manager Configuration > Cobbler" 0s

Then I should see a "SUSE Multi-Linux Manager Configuration - Cobbler. " text 0s

And I should see a "Setup your SUSE Multi-Linux Manager Cobbler settings below. " text 0s

And I should see a "Cobbler sync is used to repair or rebuild the contents /srv/tftpboot or /srv/www/cobbler when manual modification of cobbler has occurred. " text 0s

And I should see a "For more information refer to the 'cobbler' man page. " text 0s

And I should see a "Run Cobbler Sync" text in the content area 0s

And I should see a "Update" button 0s

Scenario:
Run Cobbler Sync via button and validate UI output
510ms 3

When I follow the left menu "Admin > Manager Configuration > Cobbler" 66ms

And I click on "Update" 379ms

Then I should see a "Cobbler Sync action was successfully executed. Look at /var/log/cobbler/*.log for more information" text 64ms

Scenario:
Run Cobbler Sync via button and verify task timestamp in Last Execution Times Page
10s 871ms 4

When I follow the left menu "Admin > Manager Configuration > Cobbler" 74ms

And I click on "Update" 376ms

And I follow the left menu "Admin > Task Engine Status > Last Execution Times" 404ms

Then I should see the correct timestamp for task "Cobbler Sync:" 10s 16ms

@skip_if_github_validation
Scenario:
Check for errors in Cobbler monitoring
3s 682ms 1

Then the local logs for Cobbler should not contain errors 3s 682ms

@skip_if_github_validation @scope_cobbler
Feature:Cobbler and distribution autoinstallation 1m 17s 914ms 26

Scenario:
Start Cobbler monitoring
7s 132ms 2

When I start local monitoring of Cobbler 6s 480ms

And I backup Cobbler settings file 652ms

Scenario:
Log in as testing user
2s 431ms 2

Given I am authorized as "testing" with password "testing" 1s 754ms

And I am logged in via the Cobbler API as user "testing" with password "testing" 677ms

Scenario:
Copy cobbler profiles on the server
5s 973ms 1

When I copy autoinstall mocked files on server 5s 973ms

Scenario:
Ask cobbler to create a distribution via API
656ms 2

Given cobblerd is running 2ms

When I create "testdistro" kickstart tree via the API 653ms

Scenario:
Create dummy profile
880ms 2

Given cobblerd is running 2ms

When I create a "testprofile" profile via the API using import file for "testdistro" distribution 878ms

Scenario:
Check cobbler created distro and profile
341ms 3

When I follow the left menu "Systems > Autoinstallation > Profiles" 203ms

Then I should see a "testprofile" text 73ms

And I should see a "testdistro" text 65ms

Scenario:
Create SUSE distribution with installer updates
2s 269ms 12

When I follow the left menu "Systems > Autoinstallation > Distributions" 73ms

And I follow "Create Distribution" 309ms

And I enter "SLE-15-FAKE" as "label" 63ms

And I enter "/var/autoinstall/SLES15-SP7-x86_64/DVD1/" as "basepath" 87ms

And I select "SLE-Product-SLES15-SP7-Pool for x86_64" from "channelid" 405ms

And I select "SUSE Linux Enterprise 15" from "installtype" 56ms

And I click on "Create Autoinstallable Distribution" 763ms

And I wait until I see "Autoinstallable Distribution Created" text 74ms

Then I should see a "Autoinstallable Distributions" text 70ms

And I should see a "SLE-15-FAKE" link 11ms

When I follow "SLE-15-FAKE" 330ms

Then I should see "self_update=http://" in field identified by "kernelopts" 21ms

Scenario:
Create a distribution via the UI
1s 327ms 8

When I follow the left menu "Systems > Autoinstallation > Distributions" 69ms

And I follow "Create Distribution" 301ms

When I enter "fedora_kickstart_distro" as "label" 64ms

And I enter "/var/autoinstall/Fedora_12_i386/" as "basepath" 76ms

And I select "Fedora" from "installtype" 58ms

And I click on "Create Autoinstallable Distribution" 674ms

Then I should see a "Autoinstallable Distributions" text 71ms

And I should see a "fedora_kickstart_distro" link 11ms

Scenario:
Create a distribution via the API, without kernel options
679ms 3

When I create "fedora_kickstart_distro_api" kickstart tree via the API 592ms

When I follow the left menu "Systems > Autoinstallation > Distributions" 73ms

Then I should see a "fedora_kickstart_distro_api" link 12ms

Scenario:
Create a distribution via the API, with kernel options
1s 233ms 3

When I create a kickstart tree with kernel options via the API 1s 156ms

When I follow the left menu "Systems > Autoinstallation > Distributions" 64ms

Then I should see a "fedora_kickstart_distro_kernel_api" link 12ms

Scenario:
Update a distribution via the API
1s 60ms 6

When I update a kickstart tree via the API 567ms

When I follow the left menu "Systems > Autoinstallation > Distributions" 64ms

And I follow "fedora_kickstart_distro_api" 319ms

Then option "Generic RPM" is selected as "installtype" 69ms

And I should see "self_update=0" in field identified by "kernelopts" 19ms

And I should see "self_update=1" in field identified by "postkernelopts" 21ms

Scenario:
Create a profile via the UI
1s 463ms 10

When I follow the left menu "Systems > Autoinstallation > Profiles" 68ms

And I follow "Create Kickstart Profile" 372ms

When I enter "fedora_kickstart_profile" as "kickstartLabel" 68ms

And I click on "Next" 352ms

And I click on "Next" 338ms

And I enter "linux" as "rootPassword" 50ms

And I enter "linux" as "rootPasswordConfirm" 53ms

And I click on "Finish" 61ms

Then I should see a "Autoinstallation: fedora_kickstart_profile" text 84ms

And I should see a "Autoinstallation Details" link 11ms

Scenario:
Upload a profile via the UI
2s 363ms 8

When I follow the left menu "Systems > Autoinstallation > Profiles" 67ms

And I follow "Upload Kickstart/AutoYaST File" 361ms

When I enter "fedora_kickstart_profile_upload" as "kickstartLabel" 78ms

And I select "fedora_kickstart_distro" from "kstreeId" 43ms

And I attach the file "/example.ks" to "fileUpload" 33ms

And I click on "Create" 1s 578ms

Then I should see a "Autoinstallation: fedora_kickstart_profile_upload" text 100ms

And I should see a "Autoinstallation Details" text 100ms

Scenario:
Add an unprovisioned range to the created profile
2s 429ms 13

When I follow the left menu "Systems > Autoinstallation > Profiles" 72ms

And I follow "fedora_kickstart_profile" 724ms

And I follow "Unprovisioned Autoinstallation" 320ms

And I enter "10" as "octet1a" 48ms

And I enter "10" as "octet1b" 51ms

And I enter "0" as "octet1c" 45ms

And I enter "100" as "octet1d" 49ms

And I enter "10" as "octet2a" 52ms

And I enter "10" as "octet2b" 47ms

And I enter "0" as "octet2c" 48ms

And I enter "200" as "octet2d" 49ms

And I click on "Add IP Range" 845ms

Then I should see a "Successfully added IP Range" text 72ms

Scenario:
Add a variable to the uploaded profile
1s 972ms 7

When I follow the left menu "Systems > Autoinstallation > Profiles" 72ms

And I follow "fedora_kickstart_profile_upload" 492ms

And I follow "Variables" 281ms

And I enter "my_var=A_Test_String" as "variables" 70ms

And I click on "Update Variables" 61ms

And I follow "Autoinstallation File" 930ms

Then I should see a "A_Test_String" text 62ms

Scenario:
Add a kernel option to the created profile
1s 865ms 5

When I follow the left menu "Systems > Autoinstallation > Profiles" 69ms

And I follow "fedora_kickstart_profile" 549ms

And I enter "kernel_option=a_value" as "kernel_options" 79ms

And I click on "Update" 61ms

And I wait until file "/srv/tftpboot/pxelinux.cfg/default" contains "kernel_option=a_value" on server 1s 105ms

Scenario:
Add a kernel option to the uploaded profile
4s 90ms 5

When I follow the left menu "Systems > Autoinstallation > Profiles" 71ms

And I follow "fedora_kickstart_profile_upload" 491ms

And I enter "kernel_option2=a_value2" as "kernel_options" 68ms

And I click on "Update" 56ms

And I wait until file "/srv/tftpboot/pxelinux.cfg/default" contains "kernel_option2=a_value2" on server 3s 401ms

Scenario:
Check default snippets
1s 121ms 6

When I follow the left menu "Systems > Autoinstallation > Autoinstallation Snippets" 79ms

And I follow "Default Snippets" 300ms

And I enter "spacewalk/sles_no_signature_checks" as the filtered snippet name 101ms

And I click on the filter button 324ms

And I follow "spacewalk/sles_no_signature_checks" 300ms

Then I should see "<signature-handling>" in the textarea 15ms

Scenario:
Create a snippet
556ms 6

When I follow the left menu "Systems > Autoinstallation > Autoinstallation Snippets" 66ms

And I follow "Create Snippet" 287ms

And I enter "created_test_snippet" as "name" 65ms

And I enter "<test_element>a text string</test_element>" in the editor 4ms

And I click on "Create Snippet" 61ms

Then I should see a "created_test_snippet created successfully." text 72ms

Scenario:
Delete a snippet
1s 22ms 5

When I follow the left menu "Systems > Autoinstallation > Autoinstallation Snippets" 71ms

And I follow "created_test_snippet" 240ms

And I follow "Delete Snippet" 227ms

And I click on "Delete Snippet" 420ms

Then I should see a "created_test_snippet deleted successfully." text 61ms

Scenario:
Test for PXE environment files
4s 716ms 8

Given cobblerd is running 13ms

When I wait until file "/srv/tftpboot/pxelinux.cfg/default" exists on server 711ms

And I wait until file "/srv/tftpboot/pxelinux.cfg/default" contains "inst.ks=.*fedora_kickstart_profile:1" on server 666ms

And I wait until file "/srv/tftpboot/pxelinux.cfg/default" contains "inst.ks=.*fedora_kickstart_profile_upload:1" on server 678ms

And I wait until file "/srv/tftpboot/images/fedora_kickstart_distro:1:SUSETest/initrd.img" exists on server 685ms

And I wait until file "/srv/tftpboot/images/fedora_kickstart_distro:1:SUSETest/vmlinuz" exists on server 675ms

And I wait until file "/srv/tftpboot/menu.c32" exists on server 646ms

And I wait until file "/srv/tftpboot/pxelinux.0" exists on server 640ms

Scenario:
Trigger the creation of a cobbler system record
3s 658ms 7

When I clear the caches on the server 1s 33ms

And I am on the Systems overview page of this "sle_minion" 1s 24ms

And I follow "Provisioning" 658ms

And I click on profile "testprofile" 54ms

And I click on "Create PXE installation configuration" 56ms

Then I should see a "System record created" text 84ms

And I wait until file "/srv/tftpboot/pxelinux.cfg/01-*" contains "autoyast=" on server 746ms

Scenario:
Create a cobbler system record via API
5s 210ms 5

When I create a system record 525ms

And I wait until file "/srv/tftpboot/pxelinux.cfg/01-00-22-22-77-ee-cc" contains "inst.ks=.*testserver:1" on server 641ms

Then the cobbler report should contain "testserver.example.com" for cobbler system name "testserver:1" 1s 324ms

And the cobbler report should contain "1.1.1.1" for cobbler system name "testserver:1" 1s 334ms

And the cobbler report should contain "00:22:22:77:ee:cc" for cobbler system name "testserver:1" 1s 384ms

Scenario:
Cleanup: delete test profiles and distributions using API
14s 660ms 12

When I wait for "10" seconds 10s

When I delete profile and distribution using the API for "testdistro" kickstart tree 487ms

When I delete profile and distribution using the API for "fedora_kickstart_distro" kickstart tree 488ms

When I delete profile and distribution using the API for "fedora_kickstart_distro_api" kickstart tree 364ms

When I delete profile and distribution using the API for "fedora_kickstart_distro_kernel_api" kickstart tree 1s 99ms

When I delete profile and distribution using the API for "SLE-15-FAKE" kickstart tree 1s 801ms

When I follow the left menu "Systems > Autoinstallation > Distributions" 124ms

And I should not see a "testdistro" text 64ms

And I should not see a "fedora_kickstart_distro" text 56ms

And I should not see a "fedora_kickstart_distro_api" text 57ms

And I should not see a "fedora_kickstart_distro_kernel_api" text 56ms

And I should not see a "SLE-15-FAKE" text 59ms

@flaky
Scenario:
Check for errors in Cobbler monitoring
8s 789ms 2

When I wait for "5" seconds 5s

Then the local logs for Cobbler should not contain errors 3s 789ms

Scenario:
Logout from the Cobbler API
3ms 1

When I log out from Cobbler via the API 3ms

@scope_cobbler @skip_if_github_validation
Feature:Cobbler buildiso 1m 19s 543ms 19

Builds several ISOs with Cobbler and checks the configuration files and ISOs afterwards.

Scenario:
Start Cobbler monitoring
6s 955ms 2

When I start local monitoring of Cobbler 6s 307ms

And I backup Cobbler settings file 648ms

Scenario:
Log in as testing user in the Cobbler buildiso context
1s 66ms 2

Given I am authorized as "testing" with password "testing" 449ms

And I am logged in via the Cobbler API as user "testing" with password "testing" 616ms

Scenario:
Copy cobbler profiles on the server in the Cobbler buildiso context
5s 942ms 1

When I copy autoinstall mocked files on server 5s 942ms

Scenario:
Create a dummy distro in the Cobbler buildiso context
59ms 2

Given cobblerd is running 2ms

When I create distro "buildisodistro" 56ms

Scenario:
Create dummy profiles in the Cobbler buildiso context
263ms 4

Given distro "buildisodistro" exists 4ms

When I create profile "orchid" for distro "buildisodistro" 76ms

And I create profile "flame" for distro "buildisodistro" 77ms

And I create profile "pearl" for distro "buildisodistro" 105ms

Scenario:
Check cobbler created a distro and profiles in the Cobbler buildiso context
480ms 5

When I follow the left menu "Systems > Autoinstallation > Profiles" 191ms

Then I should see a "buildisodistro" text 73ms

And I should see a "orchid" text 73ms

And I should see a "flame" text 68ms

And I should see a "pearl" text 72ms

Scenario:
Create dummy system in the Cobbler buildiso context
1s 446ms 3

Given profile "orchid" exists 8ms

When I create system "testsystem" for profile "orchid" 50ms

And I add the Cobbler parameter "name-servers" with value "9.9.9.9" to item "system" with name "testsystem" 1s 386ms

Scenario:
Prepare the Cobbler buildiso context
3s 695ms 1

When I prepare Cobbler for the buildiso command 3s 695ms

Scenario:
Run Cobbler buildiso with all profiles and check isolinux config file in the Cobbler buildiso context
11s 831ms 4

When I run Cobbler buildiso for distro "buildisodistro" and all profiles 8s 498ms

And I check Cobbler buildiso ISO "profile_all" with xorriso 2s 36ms

And I check the Cobbler parameter "nameserver" with value "9.9.9.9" in the isolinux.cfg 643ms

And I cleanup xorriso temp files 653ms

Scenario:
Run Cobbler buildiso with selected profile in the Cobbler buildiso context
5s 158ms 3

When I run Cobbler buildiso for distro "buildisodistro" and profile "orchid" 2s 470ms

And I check Cobbler buildiso ISO "orchid" with xorriso 2s 9ms

And I cleanup xorriso temp files 678ms

Scenario:
Run Cobbler buildiso with selected profile and without dns entries in the Cobbler buildiso context
5s 768ms 3

When I run Cobbler buildiso for distro "buildisodistro" and profile "orchid" without dns entries 3s 196ms

And I check Cobbler buildiso ISO "orchid" with xorriso 1s 925ms

And I cleanup xorriso temp files 646ms

Scenario:
Run Cobbler buildiso airgapped with all profiles in the Cobbler buildiso context
14s 861ms 3

When I run Cobbler buildiso "airgapped" for distro "buildisodistro" 12s 248ms

And I check Cobbler buildiso ISO "airgapped" with xorriso 1s 960ms

And I cleanup xorriso temp files 653ms

Scenario:
Run Cobbler buildiso standalone with all profiles in the Cobbler buildiso context
15s 75ms 3

When I run Cobbler buildiso "standalone" for distro "buildisodistro" 12s 464ms

And I check Cobbler buildiso ISO "standalone" with xorriso 1s 959ms

And I cleanup xorriso temp files 651ms

Scenario:
Cleanup: delete test system in the Cobbler buildiso context
485ms 2

Given I am authorized as "testing" with password "testing" 463ms

When I remove system "testsystem" 22ms

Scenario:
Cleanup: delete test profile in the Cobbler buildiso context
1s 572ms 8

Given I am authorized as "testing" with password "testing" 984ms

And I remove profile "orchid" 130ms

And I remove profile "flame" 74ms

And I remove profile "pearl" 33ms

When I follow the left menu "Systems > Autoinstallation > Profiles" 172ms

Then I should not see a "orchid" text 60ms

And I should not see a "flame" text 58ms

And I should not see a "flame" text 57ms

Scenario:
Cleanup: delete test distro in the Cobbler buildiso context
684ms 4

Given I am authorized as "testing" with password "testing" 428ms

And I remove distro "buildisodistro" 37ms

And I follow the left menu "Systems > Autoinstallation > Profiles" 157ms

Then I should not see a "buildisodistro" text 61ms

Scenario:
Cleanup: Remove buildiso tmpdir and built ISO file in the Cobbler buildiso context
654ms 1

When I cleanup after Cobbler buildiso 654ms

@flaky
Scenario:
Check for errors in Cobbler monitoring
3s 537ms 1

Then the local logs for Cobbler should not contain errors 3s 537ms

Scenario:
Logout from the Cobbler API
3ms 1

When I log out from Cobbler via the API 3ms

@scope_cobbler @skip_if_github_validation
Feature:Edit Cobbler profiles 1m 6s 645ms 12

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 2ms

Scenario:
Copy cobbler profiles on the server
6s 910ms 2

When I copy autoinstall mocked files on server 6s 258ms

And I backup Cobbler settings file 652ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 2ms

Scenario:
Log in as testing user
10s 727ms 1

Given I am authorized as "testing" with password "testing" 10s 727ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 2ms

Scenario:
Start Cobbler monitoring
6s 619ms 1

When I start local monitoring of Cobbler 6s 619ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 3ms

Scenario:
Create a Cobbler distribution via the UI
1s 582ms 10

When I follow the left menu "Systems > Autoinstallation > Distributions" 176ms

And I follow "Create Distribution" 294ms

When I enter "isedistro_ui" as "label" 61ms

And I enter "/var/autoinstall/Fedora_12_i386/" as "basepath" 78ms

And I select "Fedora" from "installtype" 67ms

And I click on "Create Autoinstallable Distribution" 672ms

Then I should see a "Autoinstallable Distributions" text 70ms

And I should see a "isedistro_ui" link 12ms

When I follow the left menu "Systems > Autoinstallation > Distributions" 73ms

Then I should see a "isedistro_ui" text 74ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 2ms

Scenario:
Create a Cobbler profile via the UI
3s 266ms 12

When I follow the left menu "Systems > Autoinstallation > Profiles" 73ms

And I follow "Create Kickstart Profile" 346ms

When I enter "iseprofile_ui" as "kickstartLabel" 60ms

And I click on "Next" 347ms

And I click on "Next" 360ms

And I enter "linux" as "rootPassword" 51ms

And I enter "linux" as "rootPasswordConfirm" 60ms

And I click on "Finish" 1s 733ms

Then I should see a "Autoinstallation: iseprofile_ui" text 76ms

And I should see a "Autoinstallation Details" link 11ms

When I follow the left menu "Systems > Autoinstallation > Profiles" 71ms

Then I should see a "iseprofile_ui" text 74ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 5ms

Scenario:
Change profile variables using the UI
11s 746ms 7

When I follow the left menu "Systems > Autoinstallation > Profiles" 88ms

And I follow "iseprofile_ui" 613ms

And I follow "Variables" 315ms

And I enter "ise_ui_test=ISE_UI_TEST" as "variables" 79ms

And I click on "Update Variables" 60ms

And I refresh the page 10s 527ms

Then I should see a "ISE_UI_TEST" text 63ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 5ms

Scenario:
Create a Cobbler distribution via the UI in the XML-RPC context
854ms 10

When I follow the left menu "Systems > Autoinstallation > Distributions" 71ms

And I follow "Create Distribution" 313ms

When I enter "isedistro_api" as "label" 66ms

And I enter "/var/autoinstall/Fedora_12_i386/" as "basepath" 75ms

And I select "Fedora" from "installtype" 48ms

And I click on "Create Autoinstallable Distribution" 53ms

Then I should see a "Autoinstallable Distributions" text 72ms

And I should see a "isedistro_api" link 12ms

When I follow the left menu "Systems > Autoinstallation > Distributions" 69ms

Then I should see a "isedistro_api" text 71ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 5ms

Scenario:
Create a Cobbler profile via the UI in the XML-RPC context
3s 74ms 12

When I follow the left menu "Systems > Autoinstallation > Profiles" 67ms

And I follow "Create Kickstart Profile" 376ms

When I enter "iseprofile_api" as "kickstartLabel" 57ms

And I click on "Next" 53ms

And I click on "Next" 633ms

And I enter "linux" as "rootPassword" 49ms

And I enter "linux" as "rootPasswordConfirm" 50ms

And I click on "Finish" 1s 549ms

Then I should see a "Autoinstallation: iseprofile_api" text 84ms

And I should see a "Autoinstallation Details" link 8ms

When I follow the left menu "Systems > Autoinstallation > Profiles" 70ms

Then I should see a "iseprofile_api" text 72ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 8ms

Scenario:
Create a Cobbler system via the XML-RPC API
507ms 1

When I create a system record with name "isesystem_api" and kickstart label "iseprofile_api" 507ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 12ms

Scenario:
Create and modify a System profile using the XML-RPC API
1s 453ms 1

When I create and modify the kickstart system "isesystem_api" with kickstart label "iseprofile_api" and hostname "ise-system.test" via XML-RPC 1s 453ms
inst.repo http://ise.cobbler.test
self_update http://ise.cobbler.test

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 7ms

Scenario:
Cleanup: delete test profiles and distributions using API
11s 46ms 6

When I wait for "10" seconds 10s

When I delete profile and distribution using the API for "isedistro_ui" kickstart tree 435ms

When I delete profile and distribution using the API for "isedistro_api" kickstart tree 417ms

When I follow the left menu "Systems > Autoinstallation > Distributions" 67ms

And I should not see a "isedistro_ui" text 66ms

And I should not see a "isedistro_api" text 58ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 3ms

@flaky
Scenario:
Check for errors in Cobbler monitoring
8s 854ms 2

When I wait for "5" seconds 5s

Then the local logs for Cobbler should not contain errors 3s 854ms

@scope_visualization
Feature:Manage users 1m 35s 622ms 15 2

Scenario:
Log in as admin user
37s 686ms 1

Given I am authorized for the "Admin" section 37s 686ms

Scenario:
Display active users page
536ms 9

When I follow the left menu "Users > User List > Active" 212ms

Then I should see a "Active Users" text 191ms

And I should see a "Create User" link 12ms

And I should see a "User List" link in the left menu 24ms

And I should see a "Active" link in the left menu 22ms

And I should see a "Deactivated" link in the left menu 20ms

And I should see a "All" link in the left menu 31ms

And I should see a "admin" link in the table first column 10ms

And I should see a "Download CSV" link 11ms

Scenario:
Create a new user
7s 923ms 13

When I follow the left menu "Users > User List > Active" 68ms

And I follow "Create User" 278ms

And I enter "user1" as "login" 56ms

And I enter "user1" as "desiredpassword" 53ms

And I enter "user1" as "desiredpasswordConfirm" 58ms

And I select "Mr." from "prefix" 46ms

And I enter "Test" as "firstNames" 56ms

And I enter "User" as "lastName" 54ms

And I enter "galaxy-noise@localhost" as "email" 76ms

And I click on "Create Login" 6s 805ms

Then I should see a "Account user1 created, login information sent to galaxy-noise@localhost" text 185ms

And I should see a "user1" link 12ms

And I should see a "normal user" text 169ms

Scenario:
Login as the new user
1s 513ms 2

Given I am authorized as "user1" with password "user1" 1s 499ms

Then I should see a "user1" link 13ms

Scenario:
Access user details
2s 386ms 21

Given I am authorized for the "Admin" section 1s 64ms

When I follow the left menu "Users > User List > Active" 160ms

And I follow "user1" 415ms

Then I should see a "User Details" text 73ms

And I should see a "Delete User" link 13ms

And I should see a "Deactivate User" link 12ms

And I should see a "Details" link 14ms

And I should see a "System Groups" link 14ms

And I should see a "Systems" link in the content area 23ms

And I should see a "Channel Permissions" link 10ms

And I should see a "Preferences" link in the content area 20ms

And I should see a "Addresses" link 18ms

And I should see a "user1" text 72ms

And option "Mr." is selected as "prefix" 59ms

And I should see "Test" in field identified by "firstNames" 21ms

And I should see "User" in field identified by "lastName" 23ms

And I should see a "galaxy-noise@localhost" text 69ms

And I should see a "Administrative Roles" text 74ms

And I should see a "Roles:" text 69ms

And I should see a "Created:" text 78ms

And I should see a "Last Sign In:" text 76ms

@susemanager
Scenario:
Add roles
< 1ms 23

When I follow the left menu "Users > User List > Active" 0s

And I follow "user1" 0s

When the "role_satellite_admin" checkbox should be disabled 0s

And I check "role_org_admin" 0s

And I check "role_system_group_admin" 0s

And I check "role_channel_admin" 0s

And I check "role_activation_key_admin" 0s

And I check "role_config_admin" 0s

And I click on "Update" 0s

Then the "role_satellite_admin" checkbox should be disabled 0s

And I should see a "SUSE Multi-Linux Manager Administrator" text 0s

And I should see "role_org_admin" as checked 0s

And I should see a "Organization Administrator" text 0s

And I should see "role_system_group_admin" as checked 0s

And I should see a "System Group Administrator" text 0s

And I should see "role_channel_admin" as checked 0s

And I should see a "Channel Administrator" text 0s

And I should see "role_activation_key_admin" as checked 0s

And I should see a "Activation Key Administrator" text 0s

And I should see "role_config_admin" as checked 0s

And I should see a "Configuration Administrator" text 0s

And I should see "role_regular_user" as checked 0s

And I should see a "Regular User" text 0s

@uyuni
Scenario:
Add roles
22s 127ms 23

When I follow the left menu "Users > User List > Active" 66ms

And I follow "user1" 282ms

When the "role_satellite_admin" checkbox should be disabled 10s 11ms

And I check "role_org_admin" 83ms

And I check "role_system_group_admin" 75ms

And I check "role_channel_admin" 74ms

And I check "role_activation_key_admin" 73ms

And I check "role_config_admin" 75ms

And I click on "Update" 772ms

Then the "role_satellite_admin" checkbox should be disabled 10s 7ms

And I should see a "Uyuni Administrator" text 77ms

And I should see "role_org_admin" as checked 14ms

And I should see a "Organization Administrator" text 70ms

And I should see "role_system_group_admin" as checked 15ms

And I should see a "System Group Administrator" text 70ms

And I should see "role_channel_admin" as checked 15ms

And I should see a "Channel Administrator" text 70ms

And I should see "role_activation_key_admin" as checked 15ms

And I should see a "Activation Key Administrator" text 75ms

And I should see "role_config_admin" as checked 14ms

And I should see a "Configuration Administrator" text 73ms

And I should see "role_regular_user" as checked 18ms

And I should see a "Regular User" text 73ms

Scenario:
Verify user list
94ms 2

When I follow the left menu "Users > User List > Active" 69ms

Then table row for "user1" should contain "Organization Administrator" 24ms

Scenario:
Fail to deactivate organization administrator
1s 833ms 8

When I follow the left menu "Users > User List > Active" 67ms

And I follow "user1" 454ms

When I follow "Deactivate User" 355ms

Then I should see a "This action will deactivate this user. This user will no longer be able to log in or perform actions unless it is reactivated." text 52ms

When I click on "Deactivate User" 439ms

Then I should see a "You cannot deactivate another organization administrator. Please remove the 'Organization Administrator' role from this user before attempting to deactivate their account." text 77ms

When I follow "Deactivated" 331ms

Then I should see a "No deactivated users." text 55ms

Scenario:
Remove role
11s 364ms 10

When I follow the left menu "Users > User List > Active" 80ms

And I follow "user1" 449ms

When I uncheck "role_org_admin" 10s 65ms

And I click on "Update" 656ms

Then I should see "role_org_admin" as unchecked 17ms

And I should see "role_system_group_admin" as checked 17ms

And I should see "role_channel_admin" as checked 18ms

And I should see "role_activation_key_admin" as checked 19ms

And I should see "role_config_admin" as checked 19ms

And I should see "role_regular_user" as checked 18ms

Scenario:
Deactivate ordinary user
2s 387ms 13

When I follow the left menu "Users > User List > Active" 73ms

And I follow "user1" 457ms

Then I should see "role_org_admin" as unchecked 23ms

When I follow "Deactivate User" 318ms

Then I should see a "This action will deactivate this user. This user will no longer be able to log in or perform actions unless it is reactivated." text 54ms

When I click on "Deactivate User" 598ms

Then I should see a "Active Users" text 174ms

And I should not see a "user1" link 8ms

When I follow "Deactivated" 274ms

Then I should see a "Deactivated Users" text 66ms

And I should see a "user1" link 8ms

When I follow "All" 320ms

Then I should see a "user1" link 8ms

@susemanager
Scenario:
Reactivate user
< 1ms 11

When I follow the left menu "Users > User List > Active" 0s

And I follow "Deactivated" 0s

And I follow "user1" 0s

Then I should see a "Reactivate User" link 0s

When I follow "Reactivate User" 0s

Then I should see a "This action will allow this user to access SUSE Multi-Linux Manager. This user will retain all permissions, roles, and data that he or she had before being deactivated." text 0s

When I click on "Reactivate User" 0s

Then I should see a "Active Users" text 0s

And I should see a "user1" link 0s

When I follow "Deactivated" 0s

Then I should not see a "user1" link 0s

@uyuni
Scenario:
Reactivate user
1s 594ms 11

When I follow the left menu "Users > User List > Active" 66ms

And I follow "Deactivated" 245ms

And I follow "user1" 363ms

Then I should see a "Reactivate User" link 11ms

When I follow "Reactivate User" 338ms

Then I should see a "This action will allow this user to access Uyuni. This user will retain all permissions, roles, and data that he or she had before being deactivated." text 56ms

When I click on "Reactivate User" 58ms

Then I should see a "Active Users" text 178ms

And I should see a "user1" link 8ms

When I follow "Deactivated" 261ms

Then I should not see a "user1" link 5ms

Scenario:
Delete user
1s 708ms 8

When I follow the left menu "Users > User List > Active" 65ms

And I follow "user1" 451ms

When I follow "Delete User" 328ms

Then I should see a "Confirm User Deletion" text 53ms

And I should see a "This will delete this user permanently." text 48ms

When I click on "Delete User" 581ms

Then I should see a "Active Users" text 174ms

And I should not see a "user1" link 5ms

Scenario:
Display the CSV separator preference
2s 204ms 6

Given I am authorized as "testing" with password "testing" 1s 751ms

When I follow the left menu "Home > My Preferences" 68ms

Then I should see a "CSV Files" text 102ms

And I should see a "Configure a separator character to be used in downloadable CSV files:" text 98ms

And I should see a "Comma" text 91ms

And I should see a "Semicolon" text 92ms

Scenario:
Configure the CSV separator char to semicolon
1s 121ms 6

Given I am authorized as "testing" with password "testing" 428ms

When I follow the left menu "Home > My Preferences" 58ms

And I choose ";" 55ms

And I click on "Save Preferences" 455ms

Then I should see a "Preferences modified" text 103ms

And radio button "radio-semicolon" should be checked 19ms

Scenario:
Cleanup: configure the CSV separator char to comma
1s 138ms 6

Given I am authorized as "testing" with password "testing" 466ms

When I follow the left menu "Home > My Preferences" 58ms

And I choose "," 65ms

And I click on "Save Preferences" 424ms

Then I should see a "Preferences modified" text 104ms

And radio button "radio-comma" should be checked 19ms

@scope_visualization @new_issue
Feature:Web UI - Main landing page menu, texts and links 12s 894ms 43

Scenario:
Log in as admin user
1s 669ms 1

Given I am authorized for the "Admin" section 1s 669ms

Scenario:
The Home menu
253ms 7

When I follow the left menu "Home" 57ms

And I should see a "Overview" link in the left menu 32ms

Then I should see a "Overview" text 70ms

And I should see a "Notification Messages" link in the left menu 22ms

And I should see a "User Account" link in the left menu 22ms

And I should see a "My Preferences" link in the left menu 24ms

And I should see a "My Organization" link in the left menu 23ms

Scenario:
The user account submenu under the Home menu
239ms 6

When I follow the left menu "Home > User Account" 62ms

Then I should see a "My Account" text 89ms

And I should see a "My Account" link in the left menu 21ms

And I should see a "Addresses" link in the left menu 20ms

And I should see a "Change Email" link in the left menu 22ms

And I should see a "Account Deactivation" link in the left menu 22ms

Scenario:
The my orginization menu under the Home menu
210ms 5

When I follow the left menu "Home > My Organization" 64ms

Then I should see a "Organization Configuration" text 68ms

And I should see a "Configuration" link in the left menu 30ms

And I should see a "Organization Trusts" link in the left menu 24ms

And I should see a "Configuration Channels" link in the left menu 22ms

Scenario:
The Salt menu
204ms 5

When I follow the left menu "Salt" 65ms

Then I should see a "Keys" text 58ms

And I should see a "Keys" link in the left menu 24ms

And I should see a "Remote Commands" link in the left menu 36ms

And I should see a "Formula Catalog" link in the left menu 20ms

Scenario:
The content lifeycle menu
149ms 4

When I follow the left menu "Content Lifecycle" 54ms

Then I should see a "Content Lifecycle Projects" text 53ms

And I should see a "Projects" link in the left menu 21ms

And I should see a "Filters" link in the left menu 19ms

Scenario:
The images menu
198ms 6

When I follow the left menu "Images" 54ms

Then I should see a "Images" text 59ms

And I should see a "Image List" link in the left menu 22ms

And I should see a "Build" link in the left menu 20ms

And I should see a "Profiles" link in the left menu 21ms

And I should see a "Stores" link in the left menu 19ms

Scenario:
The audit menu
209ms 6

When I follow the left menu "Audit" 53ms

Then I should see a "CVE Audit" text 69ms

And I should see a "CVE Audit" link in the left menu 22ms

And I should see a "Subscription Matching" link in the left menu 21ms

And I should see a "OpenSCAP" link in the left menu 21ms

And I should see a "Confidential Computing" link in the left menu 21ms

Scenario:
The OpenSCAP submenu menu
193ms 5

When I follow the left menu "Audit > OpenSCAP" 68ms

Then I should see a "OpenSCAP Scans" text 57ms

And I should see a "All Scans" link in the left menu 23ms

And I should see a "XCCDF Diff" link in the left menu 22ms

And I should see a "Advanced Search" link in the left menu 21ms

Scenario:
The configuration menu
181ms 5

When I follow the left menu "Configuration" 55ms

Then I should see a "Configuration Overview" text 64ms

And I should see a "Overview" link in the left menu 20ms

And I should see a "Channels" link in the left menu 21ms

And I should see a "Files" link in the left menu 19ms

Scenario:
The files menu under the configuration menu
194ms 4

When I follow the left menu "Configuration > Files" 67ms

Then I should see a "Centrally-Managed Configuration Files" text 84ms

And I should see a "Centrally Managed" link in the left menu 21ms

And I should see a "Locally Managed" link in the left menu 20ms

Scenario:
The systems submenu in the configuration menu
163ms 4

When I follow the left menu "Configuration > Systems" 61ms

Then I should see a "Managed Systems" text 59ms

And I should see a "Managed" link in the left menu 22ms

And I should see a "Target" link in the left menu 19ms

Scenario:
The schedule menu
191ms 6

When I follow the left menu "Schedule" 54ms

Then I should see a "Pending Actions" text 55ms

And I should see a "Pending Actions" link in the left menu 21ms

And I should see a "Failed Actions" link in the left menu 20ms

And I should see a "Archived Actions" link in the left menu 20ms

And I should see a "Action Chains" link in the left menu 20ms

Scenario:
The users menu
371ms 8

When I follow the left menu "Users" 53ms

Then I should see a "Active Users" text 185ms

And I should see a "Users" link in the left menu 26ms

And I should see a "User List" link in the left menu 22ms

And I should see a "Active" link in the left menu 20ms

And I should see a "Deactivated" link in the left menu 20ms

And I should see a "All" link in the left menu 22ms

And I should see a "System Group Configuration" link in the left menu 20ms

Scenario:
The admin menu
299ms 10

When I follow the left menu "Admin" 54ms

Then I should see a "Setup Wizard" text 78ms

And I should see a "Setup Wizard" link in the left menu 26ms

And I should see a "Organizations" link in the left menu 22ms

And I should see a "Users" link in the left menu 17ms

And I should see a "Manager Configuration" link in the left menu 20ms

And I should see a "Hub Configuration" link in the left menu 20ms

And I should see a "Task Schedules" link in the left menu 20ms

And I should see a "Task Engine Status" link in the left menu 19ms

And I should see a "Show Tomcat Logs" link in the left menu 19ms

Scenario:
The Setup Wizard submenu of the admin menu
131ms 4

When I follow the left menu "Admin > Setup Wizard" 67ms

Then I should see a "HTTP Proxy" link in the left menu 22ms

And I should see a "Organization Credentials" link in the left menu 20ms

And I should see a "Products" link in the left menu 22ms

Scenario:
The manager configuration submenu of the admin menu
257ms 8

When I follow the left menu "Admin > Manager Configuration" 63ms

Then I should see a "Configuration - General Configuration" text 65ms

And I should see a "General" link in the left menu 20ms

And I should see a "Bootstrap Script" link in the left menu 24ms

And I should see a "Organizations" link in the left menu 18ms

And I should see a "Restart" link in the left menu 21ms

And I should see a "Cobbler" link in the left menu 21ms

And I should see a "Monitoring" link in the left menu 21ms

Scenario:
The Hub configuration submenu of the admin menu
216ms 5

When I follow the left menu "Admin > Hub Configuration" 74ms

Then I should see a "Peripherals Configuration" text 66ms

And I should see a "Peripherals Configuration" link in the left menu 30ms

And I should see a "Hub Details" link in the left menu 23ms

And I should see a "Access Tokens" link in the left menu 22ms

Scenario:
The Task Engine Status submenu of the admin menu
110ms 3

When I follow the left menu "Admin > Task Engine Status" 65ms

Then I should see a "Last Execution Times" link in the left menu 23ms

And I should see a "Runtime Status" link in the left menu 20ms

Scenario:
The menu direct link accesses the first submenu level only
449ms 6

When I follow the left menu "Patches > Patch List" 114ms

Then I should see a "Patches Relevant to Your Systems" text in the content area 99ms

And I should not see a "The following patch list represents all patches accessible by your organization." text in the content area 92ms

When I follow the left menu "Configuration > Files" 110ms

Then I should see a "Centrally-Managed Configuration Files" text in the content area 17ms

And I should not see a "Locally Managed Configuration Files" text in the content area 14ms

Scenario:
Idempotency of complete menu path and direct link
298ms 4

When I follow the left menu "Software > Manage" 115ms

Then I should see a "Software Channel Management" text in the content area 51ms

When I follow the left menu "Software > Manage > Channels" 78ms

Then I should see a "Software Channel Management" text in the content area 53ms

Scenario:
Completeness of the side navigation bar and the content frame
529ms 13

When I am on the Systems page 289ms

Then I should see a "Systems" text in the content area 26ms

And I should see a "All" link in the left menu 21ms

And I should see a "Systems" link in the left menu 23ms

And I should see a "System Groups" link in the left menu 21ms

And I should see a "System Set Manager" link in the left menu 21ms

And I should see a "Advanced Search" link in the left menu 18ms

And I should see a "Activation Keys" link in the left menu 21ms

And I should see a "Stored Profiles" link in the left menu 24ms

And I should see a "Custom System Info" link in the left menu 22ms

And I should see a "Autoinstallation" link in the left menu 21ms

And I should see a "Download CSV" link 10ms

And I should see a Sign Out link 7ms

Scenario:
Sidebar link destination for Systems
240ms 7

When I follow the left menu "Systems > System List" 63ms

Then I should see a "All" link in the left menu 19ms

And I should see a "Virtual Systems" link in the left menu 20ms

And I should see a "Duplicate Systems" link in the left menu 20ms

And I should see a "System Currency" link in the left menu 23ms

And I should see a "System Types" link in the left menu 21ms

And I should see a "Systems" text 71ms

Scenario:
Sidebar link destination for Systems => Virtual Systems
148ms 3

When I follow the left menu "Systems > System List > Virtual Systems" 72ms

Then I should see a "Virtual Systems" text 73ms

And the current path is "/rhn/manager/systems/list/virtual" 3ms

Scenario:
Sidebar link destination for Systems => Duplicate Systems
190ms 7

When I follow the left menu "Systems > System List > Duplicate Systems" 75ms

Then I should see a "Duplicate Systems" text 68ms

And the current path is "/rhn/systems/DuplicateIPList.do" 2ms

And I should see a "Duplicate IP Address" link 11ms

And I should see a "Duplicate Hostname" link 10ms

And I should see a "Duplicate IPv6 Address" link 11ms

And I should see a "Duplicate MAC Address" link 10ms

Scenario:
Sidebar link destination for Systems => System Currency
176ms 3

When I follow the left menu "Systems > System List > System Currency" 73ms

Then I should see a "System Currency Report" text 100ms

And the current path is "/rhn/systems/SystemCurrency.do" 2ms

Scenario:
Sidebar link destination for Systems => System Types
613ms 7

When I follow the left menu "Systems > System List > System Types" 73ms

Then I should see a "System Types" text 113ms

And I should see a "Management:" text 105ms

And I should see a "Salt:" text 104ms

And I should see a "Foreign:" text 106ms

And I should see a "Virtualization Host:" text 106ms

And the current path is "/rhn/systems/SystemEntitlements.do" 2ms

Scenario:
Sidebar link destination for Systems => System Groups
190ms 4

When I follow the left menu "Systems > System Groups" 62ms

Then I should see a "System Groups" text 63ms

And I should see a "Create Group" link 11ms

And I should see a "Your organization has no system groups." text 54ms

Scenario:
Sidebar link destination for Systems => System Set Manager
783ms 12

When I follow the left menu "Systems > System Set Manager > Overview" 469ms

Then I should see a "System Set Manager" text 79ms

And I should see a "Task Log" link in the left menu 23ms

And I should see a "Overview" link in the content area 20ms

And I should see a "Systems" link in the content area 16ms

And I should see a "Patches" link in the content area 20ms

And I should see a "Packages" link in the content area 26ms

And I should see a "Groups" link in the content area 31ms

And I should see a "Channels" link in the content area 34ms

And I should see a "Configuration" link in the content area 18ms

And I should see a "Provisioning" link in the content area 21ms

And I should see a "Misc" link in the content area 20ms

Scenario:
Sidebar link destination for Systems => Advanced Search
134ms 2

When I follow the left menu "Systems > Advanced Search" 63ms

Then I should see a "Advanced Search" text 70ms

Scenario:
Sidebar link destination for Systems => Activation Keys
234ms 4

When I follow the left menu "Systems > Activation Keys" 58ms

Then I should see a "Activation Keys" text 78ms

And I should see a "Create Key" link 14ms

And I should see a "The following activation keys have been created for use by your organization." text 82ms

Scenario:
Sidebar link destination for Systems => Stored Profiles
174ms 3

When I follow the left menu "Systems > Stored Profiles" 59ms

Then I should see a "Stored Profiles" text 58ms

And I should see a "No stored profiles." text 55ms

Scenario:
Sidebar link destination for Systems => Custom System Info
186ms 4

When I follow the left menu "Systems > Custom System Info" 65ms

Then I should see a "Custom System Info Keys" text 58ms

And I should see a "Create Key" link 8ms

And I should see a "No Custom Info Keys Found" text 54ms

Scenario:
Sidebar link destination for Systems => Autoinstallation
409ms 13

When I follow the left menu "Systems > Autoinstallation > Overview" 123ms

Then I should see a "Autoinstallation Overview" text 73ms

And I should see a "Profiles" link in the left menu 19ms

And I should see a "Unprovisioned" link in the left menu 55ms

And I should see a "GPG and SSL Keys" link in the left menu 27ms

And I should see a "Distributions" link in the left menu 19ms

And I should see a "File Preservation" link in the left menu 19ms

And I should see a "Autoinstallation Snippets" link in the left menu 19ms

And I should see a "Create Kickstart Profile" link 10ms

And I should see a "Upload Kickstart/AutoYaST File" link 10ms

And I should see a "View a List of Autoinstallation Profiles" link 10ms

And I should see a "Create a New Kickstart Profile" link 10ms

And I should see a "Upload a New Kickstart/AutoYaST File" link 10ms

Scenario:
Sidebar link destination for Systems => Autoinstallation => Profiles
151ms 4

When I follow the left menu "Systems > Autoinstallation > Profiles" 73ms

Then I should see a "Autoinstallation Profiles" text 63ms

And I should see a "Create Kickstart Profile" link 7ms

And I should see a "Upload Kickstart/AutoYaST File" link 7ms

Scenario:
Sidebar link destination for Systems => Autoinstallation => Unprovisioned
188ms 3

When I follow the left menu "Systems > Autoinstallation > Unprovisioned" 69ms

Then I should see a "Unprovisioned Autoinstallation By IP" text 60ms

And I should see a "No Ip Ranges Found" text 57ms

Scenario:
Sidebar link destination for Systems => Autoinstallation => GPG and SSL Keys
175ms 5

When I follow the left menu "Systems > Autoinstallation > GPG and SSL Keys" 72ms

Then I should see a "GPG Public Keys and SSL Certificates" text 69ms

And I should see a "Create Stored Key/Cert" link 11ms

And I should see a "Reference Guide" link 11ms

And I should see a "RHN-ORG-TRUSTED-SSL-CERT" link 10ms

Scenario:
Sidebar link destination for Systems => Autoinstallation => Distributions
203ms 4

When I follow the left menu "Systems > Autoinstallation > Distributions" 70ms

Then I should see a "Autoinstallable Distributions" text 62ms

And I should see a "No autoinstallable distributions available." text 58ms

And I should see a "Create Distribution" link 11ms

Scenario:
Sidebar link destination for Systems => Autoinstallation => File Preservation
148ms 4

When I follow the left menu "Systems > Autoinstallation > File Preservation" 70ms

Then I should see a "File Preservation" text 58ms

And I should see a "Reference Guide" link 8ms

And I should see a "Create File Preservation List" link 10ms

Scenario:
Sidebar link destination for Systems => Autoinstallation => Autoinstallation Snippets
266ms 7

When I follow the left menu "Systems > Autoinstallation > Autoinstallation Snippets" 71ms

Then I should see a "Autoinstallation Snippets" text 63ms

And I should see a "No autoinstallation snippets found." text 60ms

And I should see a "Create Snippet" link 11ms

And I should see a "Default Snippets" link in the content area 20ms

And I should see a "Custom Snippets" link in the content area 20ms

And I should see a "All Snippets" link in the content area 19ms

Scenario:
"Create Kickstart Profile" page Systems => Autoinstallation => Profiles => Create Kickstart Profile
427ms 3

When I follow the left menu "Systems > Autoinstallation > Profiles" 71ms

And I follow "Create Kickstart Profile" 286ms

Then I should see a "Step 1: Create Kickstart Profile" text 69ms

Scenario:
"Upload Kickstart/AutoYaST File" page Systems => Autoinstallation => Profiles => Upload Kickstart/AutoYaST File
625ms 5

When I follow the left menu "Systems > Autoinstallation > Profiles" 64ms

And I follow "Upload Kickstart/AutoYaST File" 352ms

Then I should see a "Create Autoinstallation Profile" text 71ms

And I should see a "File Contents:" text 69ms

And I should see a "Autoinstallation Details" text 68ms

Scenario:
"Create kickstart distribution" page Systems => Autoinstallation => Distributions => create new kickstart distribution
499ms 4

When I follow the left menu "Systems > Autoinstallation > Distributions" 70ms

And I follow "Create Distribution" 292ms

Then I should see a "Create Autoinstallable Distribution" text 69ms

And I should see a "Distribution Label" text 67ms

@scope_configuration_channels
Feature:Check if source packages were successfully synced 5s 861ms 3

Scenario:
Log in as org admin user
1s 808ms 1

Given I am authorized 1s 808ms

Scenario:
Check sources for noarch package
2s 164ms 6

When I follow the left menu "Software > Channel List > All" 173ms

And I follow "Show All Child Channels" 62ms

And I follow "Fake-RPM-SUSE-Channel" 563ms

And I follow "Packages" 663ms

And I follow "virgo-dummy-2.0-1.1.noarch" 632ms

Then I should see a "virgo-dummy-2.0-1.1.src.rpm" text 69ms

Scenario:
Check sources for x86_64 package
1s 888ms 6

When I follow the left menu "Software > Channel List > All" 108ms

And I follow "Show All Child Channels" 44ms

And I follow "Fake-RPM-SUSE-Channel" 574ms

And I follow "Packages" 557ms

And I follow "blackhole-dummy-1.0-1.1.x86_64" 538ms

Then I should see a "blackhole-dummy-1.0-1.1.src.rpm" text 65ms

@scope_visualization
Feature:Change the user's password 15s 558ms 4

In order to change my password
As an authorized user
I want enter a new password

Scenario:
Log in as org admin user
1s 805ms 1

Given I am authorized for the "Admin" section 1s 805ms

Scenario:
Change the password to a new password
1s 214ms 10

When I follow the left menu "Home > User Account > My Account" 136ms

And I enter "GoodPass" as "desiredpassword" 62ms

And I enter "GoodPass" as "desiredpasswordConfirm" 56ms

And I click on "Update" 60ms

Then I should see a "User information updated" text 73ms

When I sign out 307ms

And I enter "admin" as "username" 40ms

And I enter "GoodPass" as "password" 56ms

And I click on "Sign In" 54ms

Then I should be logged in 365ms

Scenario:
Revert the new password to a valid standard password
1s 458ms 10

When I follow the left menu "Home > User Account > My Account" 112ms

And I enter "admin" as "desiredpassword" 52ms

And I enter "admin" as "desiredpasswordConfirm" 48ms

And I click on "Update" 391ms

Then I should see a "User information updated" text 72ms

When I sign out 307ms

And I enter "admin" as "username" 40ms

And I enter "admin" as "password" 53ms

And I click on "Sign In" 55ms

Then I should be logged in 325ms

Scenario:
Try an invalid password
11s 81ms 10

When I follow the left menu "Home > User Account > My Account" 117ms

And I enter "A" as "desiredpassword" 45ms

And I enter "A" as "desiredpasswordConfirm" 47ms

And I click on "Update" 349ms

Then I should see a "Passwords must be at least 4 characters." text 63ms

When I sign out 309ms

And I enter "admin" as "username" 39ms

And I enter "A" as "password" 45ms

And I click on "Sign In" 52ms

Then I should not be authorized 10s 11ms

@scope_configuration_channels
Feature:Clone a channel 37s 564ms 12

Scenario:
Log in as org admin user
10s 661ms 1

Given I am authorized 10s 661ms

Scenario:
Clone a channel without patches
2s 443ms 10

When I follow the left menu "Software > Manage > Channels" 178ms

And I follow "Clone Channel" 490ms

And I select "Fake-RPM-SUSE-Channel" as the origin channel 73ms

And I choose "original" 51ms

And I click on "Clone Channel" 452ms

And I enter "Fake-Clone-RPM-SLES15SP7-Channel" as "Channel Name" 126ms

And I should see a "Create Software Channel" text 84ms

And I should see a "Original state of the channel" text 71ms

And I click on "Clone Channel" 840ms

Then I should see a "Fake-Clone-RPM-SLES15SP7-Channel" text 74ms

Scenario:
Check that this channel has no patches
1s 509ms 5

When I follow the left menu "Software > Manage > Channels" 72ms

And I follow "Fake-Clone-RPM-SLES15SP7-Channel" 570ms

And I follow "Patches" in the content area 70ms

And I follow "List/Remove Patches" 740ms

Then I should see a "There are no patches associated with this channel." text 55ms

Scenario:
Clone a channel with patches
2s 271ms 10

When I follow the left menu "Software > Manage > Channels" 65ms

And I follow "Clone Channel" 455ms

And I select "Fake-RPM-SUSE-Channel" as the origin channel 54ms

And I choose "current" 50ms

And I click on "Clone Channel" 443ms

And I enter "Fake-Clone-2-RPM-SLES15SP7-Channel" as "Channel Name" 122ms

And I should see a "Create Software Channel" text 77ms

And I should see a "Current state of the channel" text 72ms

And I click on "Clone Channel" 857ms

Then I should see a "Fake-Clone-2-RPM-SLES15SP7-Channel" text 73ms

Scenario:
Check that this channel has patches
1s 360ms 8

When I follow the left menu "Software > Manage > Channels" 72ms

And I follow "Fake-Clone-2-RPM-SLES15SP7-Channel" 561ms

And I follow "Patches" in the content area 56ms

And I follow "List/Remove Patches" 626ms

Then I should see a "CL-hoag-dummy-7890" link 11ms

And I should see a "CL-virgo-dummy-3456" link 10ms

And I should see a "CL-milkyway-dummy-2345" link 10ms

And I should see a "CL-andromeda-dummy-6789" link 11ms

Scenario:
Clone a channel with selected patches
5s 44ms 18

When I follow the left menu "Software > Manage > Channels" 86ms

And I follow "Clone Channel" 555ms

And I select "Fake-RPM-SUSE-Channel" as the origin channel 53ms

And I choose "select" 49ms

And I click on "Clone Channel" 455ms

And I enter "Fake-Clone-3-RPM-SLES15SP7-Channel" as "Channel Name" 120ms

And I should see a "Create Software Channel" text 78ms

And I should see a "Select patches" text 75ms

And I click on "Clone Channel" 996ms

And I should see a "Fake-Clone-3-RPM-SLES15SP7-Channel" text 87ms

And I should see a "Channel Fake-Clone-3-RPM-SLES15SP7-Channel cloned from channel Fake-RPM-SUSE-Channel." text 84ms

And I should see a "You may now wish to clone the patches associated with Fake-RPM-SUSE-Channel." text 81ms

And I check the row with the "hoag-dummy-7890" link 59ms

And I check the row with the "virgo-dummy-3456" link 54ms

And I click on "Clone Patches" 1s 128ms

And I click on "Confirm" 1s 58ms

Then I should see a "CL-hoag-dummy-7890" link 8ms

And I should see a "CL-virgo-dummy-3456" link 7ms

Scenario:
Check that new patches exists
1s 442ms 8

When I follow the left menu "Patches > Patch List > All" 177ms

And I enter "dummy" as the filtered synopsis 39ms

And I click on the filter button 658ms

And I select "500" from "1154021400_PAGE_SIZE_LABEL" 533ms

Then I should see a "CL-hoag-dummy-7890" link 9ms

And I should see a "CL-virgo-dummy-3456" link 8ms

And I should see a "CL-milkyway-dummy-2345" link 7ms

And I should see a "CL-andromeda-dummy-6789" link 8ms

Scenario:
Check CL-hoag-dummy-7890 patches
2s 21ms 8

When I follow the left menu "Patches > Patch List > All" 74ms

And I enter "dummy" as the filtered synopsis 77ms

And I click on the filter button 663ms

And I select "500" from "1154021400_PAGE_SIZE_LABEL" 529ms

And I follow "CL-hoag-dummy-7890" 541ms

Then I should see a "CL-hoag-dummy-7890 - Security Advisory" text 62ms

And I should see a "mcalmer" text 60ms

And I should see a "https://bugzilla.opensuse.org/show_bug.cgi?id=704608" link 11ms

Scenario:
Check CM-virgo-dummy-3456 patches
1s 800ms 8

When I follow the left menu "Patches > Patch List > All" 90ms

And I enter "dummy" as the filtered synopsis 36ms

And I click on the filter button 664ms

And I select "500" from "1154021400_PAGE_SIZE_LABEL" 450ms

And I follow "CL-virgo-dummy-3456" 423ms

Then I should see a "CL-virgo-dummy-3456 - Bug Fix Advisory" text 63ms

And I should see a "mcalmer" text 60ms

And I should see a "CVE-1999-9998" link 10ms

Scenario:
Compare channel packages
2s 133ms 9

When I follow the left menu "Software > Manage > Channels" 162ms

And I follow "Fake-Clone-2-RPM-SLES15SP7-Channel" 467ms

And I follow "Packages" in the content area 71ms

And I follow "Compare" 613ms

And I select "Fake-Clone-3-RPM-SLES15SP7-Channel" from "selected_channel" 65ms

And I click on "View Packages" 563ms

Then I should see a "andromeda-dummy" text 89ms

And I should see a "2.0-1.1" link 14ms

And I should see a "This channel only" text 86ms

Scenario:
Cleanup: remove cloned channels
6s 818ms 21

When I follow the left menu "Software > Manage > Channels" 69ms

And I follow "Fake-Clone-RPM-SLES15SP7-Channel" 576ms

And I follow "Delete Channel" 392ms

And I check "unsubscribeSystems" 78ms

And I click on "Delete Channel" 758ms

Then I should see a "Fake-Clone-RPM-SLES15SP7-Channel" text 62ms

And I should see a "has been deleted." text 59ms

Given I follow the left menu "Software > Manage > Channels" 79ms

When I follow "Fake-Clone-2-RPM-SLES15SP7-Channel" 553ms

And I follow "Delete Channel" 704ms

And I check "unsubscribeSystems" 66ms

And I click on "Delete Channel" 1s 318ms

Then I should see a "Fake-Clone-2-RPM-SLES15SP7-Channel" text 60ms

And I should see a "has been deleted." text 60ms

Given I follow the left menu "Software > Manage > Channels" 76ms

When I follow "Fake-Clone-3-RPM-SLES15SP7-Channel" 558ms

And I follow "Delete Channel" 378ms

And I check "unsubscribeSystems" 66ms

And I click on "Delete Channel" 770ms

Then I should see a "Fake-Clone-3-RPM-SLES15SP7-Channel" text 64ms

And I should see a "has been deleted." text 60ms

Scenario:
Cleanup: remove remaining systems from SSM after channel cloning tests
58ms 1

When I click on the clear SSM button 58ms

@flaky
Feature:Manipulate activation keys 14s 336ms 9 1

In order to register systems to the spacewalk server
As the testing user
I want to create and edit activation keys

Scenario:
Log in as org admin user
1s 730ms 1

Given I am authorized 1s 730ms

Scenario:
Create an activation key for i586
1s 709ms 8

When I follow the left menu "Systems > Activation Keys" 117ms

And I follow "Create Key" 263ms

And I wait until I do not see "Loading..." text 223ms

And I enter "SUSE Test Key i586" as "description" 72ms

And I enter "SUSE-TEST-i586" as "key" 69ms

And I check "virtualization_host" 84ms

And I click on "Create Activation Key" 59ms

Then I should see a "Activation key SUSE Test Key i586 has been created." text 818ms

Scenario:
Change limit of the i586 activation key
1s 552ms 7

When I follow the left menu "Systems > Activation Keys" 66ms

And I follow "SUSE Test Key i586" 329ms

And I wait until I do not see "Loading..." text 468ms

And I enter "20" as "usageLimit" 48ms

And I click on "Update Activation Key" 544ms

Then I wait until I see "Activation key SUSE Test Key i586 has been modified." text 69ms

And I should see "20" in field identified by "usageLimit" 24ms

Scenario:
Change the base channel of the i586 activation key
1s 59ms 6

When I follow the left menu "Systems > Activation Keys" 64ms

And I follow "SUSE Test Key i586" 323ms

And I wait until I do not see "Loading..." text 476ms

And I select "Fake-Base-Channel-i586" from "selectedBaseChannel" 72ms

And I click on "Update Activation Key" 53ms

Then I wait until I see "Activation key SUSE Test Key i586 has been modified." text 70ms

Scenario:
Delete the i586 activation key
1s 387ms 6

When I follow the left menu "Systems > Activation Keys" 60ms

And I follow "SUSE Test Key i586" in the content area 66ms

And I wait until I do not see "Loading..." text 467ms

And I follow "Delete Key" 238ms

And I click on "Delete Activation Key" 473ms

Then I should see a "Activation key SUSE Test Key i586 has been deleted." text 80ms

Scenario:
Create an activation key with a channel and a package list for i586
2s 154ms 12

When I follow the left menu "Systems > Activation Keys" 58ms

And I follow "Create Key" 244ms

And I wait until I do not see "Loading..." text 221ms

And I enter "SUSE Test PKG Key i586" as "description" 73ms

And I enter "SUSE-TEST-2-i586" as "key" 67ms

And I enter "20" as "usageLimit" 49ms

And I select "Fake-Base-Channel-i586" from "selectedBaseChannel" 54ms

And I click on "Create Activation Key" 824ms

And I follow "Packages" 395ms

And I enter "sed" as "packages" 48ms

And I click on "Update Activation Key" 59ms

Then I should see a "Activation key SUSE Test PKG Key i586 has been modified." text 56ms

Scenario:
Delete the i586 activation key with packages
1s 31ms 5

When I follow the left menu "Systems > Activation Keys" 61ms

And I follow "SUSE Test PKG Key i586" in the content area 67ms

And I follow "Delete Key" 307ms

And I click on "Delete Activation Key" 515ms

Then I should see a "Activation key SUSE Test PKG Key i586 has been deleted." text 79ms

@scc_credentials @susemanager
Scenario:
Create an activation key with a channel and a package list for x86_64
< 1ms 12

When I follow the left menu "Systems > Activation Keys" 0s

And I follow "Create Key" 0s

And I wait until I do not see "Loading..." text 0s

And I enter "SUSE Test PKG Key x86_64" as "description" 0s

And I enter "SUSE-TEST-x86_64" as "key" 0s

And I enter "20" as "usageLimit" 0s

And I select "SLE-Product-SLES15-SP7-Pool for x86_64" from "selectedBaseChannel" 0s

And I click on "Create Activation Key" 0s

And I follow "Packages" 0s

And I enter "sed" as "packages" 0s

And I click on "Update Activation Key" 0s

Then I should see a "Activation key SUSE Test PKG Key x86_64 has been modified." text 0s

@scc_credentials @uyuni
Scenario:
Create an activation key with a channel and a package list for x86_64
2s 689ms 12

When I follow the left menu "Systems > Activation Keys" 72ms

And I follow "Create Key" 244ms

And I wait until I do not see "Loading..." text 311ms

And I enter "SUSE Test PKG Key x86_64" as "description" 74ms

And I enter "SUSE-TEST-x86_64" as "key" 68ms

And I enter "20" as "usageLimit" 43ms

And I select "openSUSE Tumbleweed (x86_64)" from "selectedBaseChannel" 57ms

And I click on "Create Activation Key" 940ms

And I follow "Packages" 313ms

And I enter "sed" as "packages" 46ms

And I click on "Update Activation Key" 462ms

Then I should see a "Activation key SUSE Test PKG Key x86_64 has been modified." text 54ms

@scc_credentials
Scenario:
Delete the x86_64 activation key with packages
1s 22ms 5

When I follow the left menu "Systems > Activation Keys" 61ms

And I follow "SUSE Test PKG Key x86_64" in the content area 66ms

And I follow "Delete Key" 305ms

And I click on "Delete Activation Key" 510ms

Then I should see a "Activation key SUSE Test PKG Key x86_64 has been deleted." text 79ms

@scope_api
Feature:API "activationkey" namespace 3s 639ms 4

Scenario:
List all activation keys
459ms 1

Then I should get some activation keys 459ms

Scenario:
Create activation key
1s 280ms 2

When I create an activation key with id "testkey", description "Key for testing", limit of 10 and contact method "default" 847ms

Then I should get the new activation key "1-testkey" 432ms

Scenario:
Activation key details
782ms 2

Key details:
entitlements: []
usage_limit: 10
universal_default: false
description: Key description
base_channel_label: none
child_channel_labels: []
app_streams: {}
packages: []
server_group_ids: []
contact_method: default
package_names: []
disabled: false
key: 1-testkey

When I set the description of the activation key "1-testkey" to "Key description" 405ms

Then I get the description "Key description" for the activation key "1-testkey" 376ms

Scenario:
Cleanup: delete activation key
1s 117ms 1

When I delete the activation key "1-testkey" 1s 117ms

@scope_visualization
Feature:Main landing page options and preferences 54s 674ms 10 2

Scenario:
Clear browser cookies for main landing page validation
17ms 1

When I clear browser cookies 17ms

Scenario:
Access the Login page
545ms 3

Given I am not authorized 395ms

When I go to the home page 132ms

Then I should see a "Sign In" text 18ms

@uyuni
Scenario:
Access the API Documentation
10s 522ms 4

Given I am not authorized 10s 197ms

When I go to the home page 127ms

And I follow "API Documentation" 148ms

Then I should see a "API Overview" text 49ms

@susemanager
Scenario:
Access the Copyright Notice
< 1ms 10

Given I am authorized 0s

When I follow the left menu "Help" 0s

And I switch to last opened window 0s

Then I should see a "SUSE Multi-Linux Manager Guides" text 0s

When I click on the Legal button 0s

And I wait until I see "Copyright Notice" text 0s

And I follow "Copyright Notice" 0s

Then I should see a "Copyright Notice" text 0s

And I should see a "SUSE Multi-Linux Manager LICENSE AGREEMENT" text 0s

When I close the last opened window 0s

@susemanager
Scenario:
Access the EULA
< 1ms 10

Given I am authorized 0s

When I follow the left menu "Help" 0s

And I switch to last opened window 0s

Then I should see a "SUSE Multi-Linux Manager Guides" text 0s

When I click on the Legal button 0s

And I wait until I see "End User License Agreement" text 0s

And I follow "End User License Agreement" 0s

Then I should see a "End User License Agreement" text 0s

And I should see a "End User License Agreement for SUSE Software" text 0s

When I close the last opened window 0s

Scenario:
Log into Uyuni
10s 848ms 6

Given I am not authorized 10s 187ms

When I go to the home page 130ms

And I enter "testing" as "username" 56ms

And I enter "testing" as "password" 60ms

And I click on "Sign In" 60ms

Then I should be logged in 352ms

Scenario:
Log out of Uyuni
13s 157ms 3

Given I am authorized 2s 370ms

When I sign out 776ms

Then I should not be authorized 10s 10ms

Scenario:
Top level bar
11s 670ms 7

Given I am authorized for the "Admin" section 10s 623ms

When I go to the home page 948ms

And I should see a "Manage" link 16ms

And I should see a "admin" text 52ms

And I should see a "SUSE Test" link 11ms

And I should see a "Preferences" link 10ms

And I should see a Sign Out link 7ms

Scenario:
Main menu as regular user
2s 331ms 15

Given I am authorized as "testing" with password "testing" 2s 171ms

Then I should see a "Home" link 11ms

And I should see a "Systems" link 14ms

And I should see a "Salt" link 11ms

And I should see a "Images" link 11ms

And I should see a "Patches" link 12ms

And I should see a "Software" link 10ms

And I should see a "Content Lifecycle" link 10ms

And I should see a "Audit" link 10ms

And I should see a "Configuration" link 12ms

And I should see a "Schedule" link 10ms

And I should see a "Users" link 13ms

And I should not see a "Admin" link 7ms

And I should see a "Help" link 10ms

And I should see a "External Links" link 11ms

Scenario:
Log in as admin user
2s 9ms 1

Given I am authorized for the "Admin" section 2s 9ms

Scenario:
Main menu as administrator
117ms 13

Then I should see a "Home" link 10ms

And I should see a "Systems" link 10ms

And I should see a "Salt" link 8ms

And I should see a "Images" link 8ms

And I should see a "Patches" link 8ms

And I should see a "Software" link 7ms

And I should see a "Audit" link 8ms

And I should see a "Configuration" link 11ms

And I should see a "Schedule" link 9ms

And I should see a "Users" link 8ms

And I should see a "Admin" link 7ms

And I should see a "Help" link 7ms

And I should see a "External Links" link 11ms

Scenario:
Main content
3s 453ms 8

Given I am authorized 2s 52ms

Then I should see a "Tasks" text 662ms

And I should see a "Inactive Systems" text 94ms

And I should see a "Most Critical Systems" text 125ms

And I should see a "Recently Scheduled Actions" text 132ms

And I should see a "Relevant Security Patches" text 127ms

And I should see a "System Group Name" text 127ms

And I should see a "Recently Registered Systems" text 131ms

@scope_api
Feature:API "user" namespace 23s 133ms 5

Scenario:
List users
6s 789ms 2

When I call user.list_users() 6s 789ms

Then I should get at least user "admin" < 1ms

Scenario:
List roles
332ms 2

When I call user.list_roles() on user "admin" 332ms

Then I should get at least one role that matches "_admin" suffix < 1ms

Scenario:
Create user
13s 940ms 4

When I make sure "testuser" is not present 6s 787ms

And I call user.create() with login "testuser" 387ms

And I call user.list_users() 6s 766ms

Then I should get at least user "testuser" < 1ms

Scenario:
Role operations
1s 629ms 6

When I call user.add_role() on "testuser" with the role "org_admin" 370ms

And I call user.list_roles() on user "testuser" 421ms

Then I should get role "org_admin" < 1ms

When I call user.remove_role() on "testuser" with the role "org_admin" 425ms

And I call user.list_roles() on user "testuser" 412ms

Then I should not get role "org_admin" < 1ms

Scenario:
Cleanup: user tests
440ms 1

When I delete user "testuser" 440ms

@scope_salt
Feature:Endpoint to download packages 3s 902ms 7

In order to distribute software to the clients
As an authorized user
I want to download packages from the channels

Scenario:
Download package, user without token
26ms 2

Given I try to download "virgo-dummy-2.0-1.1.noarch.rpm" from channel "fake-rpm-suse-channel" 26ms

Then the download should get a 403 response < 1ms

Scenario:
Download package, user with a valid token for the org
1s 33ms 3

6c88259d95a8e56a8262511887e13b902eadb10f6e9ff126026a0928249e9b39

Given I have a valid token for organization "1" 995ms

When I try to download "virgo-dummy-2.0-1.1.noarch.rpm" from channel "fake-rpm-suse-channel" 38ms

Then the download should get no error < 1ms

Scenario:
Download package, user with an invalid token for the org
29ms 3

6e09a6d27a0d4679dea90b6ea963beda263181ba198d79d05deb525ddb711042484049cdc0271e24593a1c59ce0cc76d56ea05d4e93e9b3c4e602abcdf59bc64

Given I have an invalid token for organization "1" 1ms

When I try to download "virgo-dummy-2.0-1.1.noarch.rpm" from channel "fake-rpm-suse-channel" 28ms

Then the download should get a 403 response < 1ms

Scenario:
Download package, user with an expired valid token for the org
710ms 3

6c88259d95a8e56a8262511887e13b902eadb10f6e9ff126026a0928249e9b39

Given I have an expired valid token for organization "1" 670ms

When I try to download "virgo-dummy-2.0-1.1.noarch.rpm" from channel "fake-rpm-suse-channel" 39ms

Then the download should get a 403 response < 1ms

Scenario:
Download package, user with an non expired valid token for the org
722ms 3

6c88259d95a8e56a8262511887e13b902eadb10f6e9ff126026a0928249e9b39

Given I have a valid token expiring tomorrow for organization "1" 688ms

When I try to download "virgo-dummy-2.0-1.1.noarch.rpm" from channel "fake-rpm-suse-channel" 33ms

Then the download should get no error < 1ms

Scenario:
Download package, user with a valid token that cant be used until tomorrow for the org
692ms 3

6c88259d95a8e56a8262511887e13b902eadb10f6e9ff126026a0928249e9b39

Given I have a not yet usable valid token for organization "1" 664ms

When I try to download "virgo-dummy-2.0-1.1.noarch.rpm" from channel "fake-rpm-suse-channel" 27ms

Then the download should get a 403 response < 1ms

Scenario:
Download package, user with a valid token for the org and specific channels
688ms 3

6c88259d95a8e56a8262511887e13b902eadb10f6e9ff126026a0928249e9b39

Given I have a valid token for organization "1" and channel "foobar" 659ms

When I try to download "virgo-dummy-2.0-1.1.noarch.rpm" from channel "fake-rpm-suse-channel" 28ms

Then the download should get a 403 response < 1ms

@scope_building_container_images @no_auth_registry
Feature:Advanced content management 22s 324ms 8

Scenario:
Log in as docker user
1s 823ms 1

Given I am authorized as "docker" with password "docker" 1s 823ms

Scenario:
Create an image store as Docker admin
1s 235ms 6

When I follow the left menu "Images > Stores" 139ms

And I follow "Create" 297ms

And I enter "docker_admin" as "label" 96ms

And I enter the URI of the registry as "uri" 145ms

And I click on "create-btn" 73ms

Then I wait until table row contains a "galaxy-registry" text 482ms

@scc_credentials
Scenario:
Create a profile as Docker admin
3s 863ms 7

GITPROFILES: https://github.com/uyuni-project/uyuni.git#:testsuite/features/profiles/temporary

When I follow the left menu "Images > Profiles" 67ms

And I follow "Create" 292ms

And I enter "suse_docker_admin" as "label" 166ms

And I select "galaxy-registry" from "imageStore" 1s 133ms

And I select "1-SUSE-KEY-x86_64" from "activationKey" 1s 125ms

And I enter "Docker/serverhost" relative to profiles as "path" 1s 23ms

And I click on "create-btn" 53ms

Scenario:
Create a user without rights nor roles
10s 444ms 2

New user norole created with roles:

Given I am authorized for the "Admin" section 1s 38ms

When I create a user with name "norole" and password "norole" with roles "" 9s 405ms

Scenario:
Log in as docker user
1s 470ms 1

Given I am authorized as "docker" with password "docker" 1s 470ms

@scc_credentials
Scenario:
Cleanup: remove Docker profile
903ms 6

Given I am authorized as "docker" with password "docker" 430ms

When I follow the left menu "Images > Profiles" 103ms

And I check the row with the "suse_docker_admin" text 74ms

And I click on "Delete" 74ms

And I click on the red confirmation button 69ms

And I should see a "Image profile has been deleted." text 150ms

Scenario:
Cleanup: remove image store
493ms 5

When I follow the left menu "Images > Stores" 60ms

And I check the row with the "docker_admin" text 110ms

And I click on "Delete" 64ms

And I click on the red confirmation button 60ms

And I should see a "Image store has been deleted." text 197ms

Scenario:
Cleanup: delete no role user
2s 90ms 2

Given I am authorized for the "Admin" section 1s 110ms

When I delete user "norole" 979ms

@scope_visualization
Feature:Pick dates 17s 563ms 3

In order to execute actions at a certain date
As a authorized user
I want to be able to easily pick dates

Scenario:
Log in as admin user
6s 809ms 2

Given I am authorized 1s 715ms

And I am on the Systems overview page of this "sle_minion" 5s 93ms

Scenario:
Date picker is by default set to today
10s 206ms 3

When I follow "Remote Command" in the content area 79ms

And I open the date picker 83ms

Then the date picker title should be the current month and year 10s 44ms

Scenario:
Picking a time sets the hidden fields
547ms 8

When I follow "Details" in the content area 78ms

And I follow "Remote Command" in the content area 57ms

And I enter "ls" as "Script" 103ms

And I pick "2022-08-27" as date 105ms

And I pick "17:30" as time 122ms

Then the date field should be set to "2022-08-27" 40ms

And the time field should be set to "17:30" 36ms

And the date picker should be closed 3ms

@scope_visualization
Feature:Work with Union and Intersection buttons in the group list 24s 803ms 16

Scenario:
Log in as org admin user
1s 762ms 1

Given I am authorized 1s 762ms

Scenario:
Create a sles group
1s 48ms 6

When I follow the left menu "Systems > System Groups" 133ms

When I follow "Create Group" 287ms

And I enter "sles" as "name" 49ms

And I enter "SLES systems" as "description" 57ms

And I click on "Create Group" 453ms

Then I should see a "System group sles created." text 66ms

Scenario:
Add systems to the sles group
2s 340ms 6

When I follow the left menu "Systems > System Groups" 63ms

When I follow "sles" 299ms

And I follow "Target Systems" 592ms

And I check the "sle_minion" client 61ms

And I click on "Add Systems" 1s 227ms

Then I should see a "added to sles server group." text 96ms

@rhlike_minion
Scenario:
Create a rhlike group
951ms 6

When I follow the left menu "Systems > System Groups" 59ms

When I follow "Create Group" 288ms

And I enter "rhlike" as "name" 48ms

And I enter "Red Hat-like systems" as "description" 61ms

And I click on "Create Group" 431ms

Then I should see a "System group rhlike created." text 62ms

@rhlike_minion
Scenario:
Add systems to the rhlike group
4s 695ms 6

When I follow the left menu "Systems > System Groups" 59ms

When I follow "rhlike" 305ms

And I follow "Target Systems" 529ms

And I check the "rhlike_minion" client 2s 575ms

And I click on "Add Systems" 1s 134ms

Then I should see a "1 systems were added to rhlike server group." text 90ms

@deblike_minion
Scenario:
Create a deblike group
1s 4ms 6

When I follow the left menu "Systems > System Groups" 59ms

When I follow "Create Group" 303ms

And I enter "deblike" as "name" 47ms

And I enter "Debian-like systems" as "description" 59ms

And I click on "Create Group" 52ms

Then I should see a "System group deblike created." text 481ms

@deblike_minion
Scenario:
Add systems to the deblike group
6s 226ms 6

When I follow the left menu "Systems > System Groups" 60ms

When I follow "deblike" 315ms

And I follow "Target Systems" 455ms

And I check the "deblike_minion" client 4s 153ms

And I click on "Add Systems" 1s 146ms

Then I should see a "1 systems were added to deblike server group." text 94ms

Scenario:
Add the sles group to SSM
212ms 4

When I follow the left menu "Systems > System Groups" 62ms

When I click on "Use in SSM" in row "sles" 66ms

And I should see a "Selected Systems List" text 69ms

And I should see "sle_minion" as link 13ms

@rhlike_minion
Scenario:
Add a union of 2 groups to SSM - Red Hat-like
710ms 6

When I follow the left menu "Systems > System Groups" 57ms

When I check "sles" in the list 57ms

And I check "rhlike" in the list 56ms

And I click on "Work With Union" 513ms

And I should see "sle_minion" as link 12ms

And I should see "rhlike_minion" as link 13ms

@rhlike_minion
Scenario:
Add an intersection of 2 groups to SSM - Red Hat-like
573ms 6

When I follow the left menu "Systems > System Groups" 59ms

When I check "sles" in the list 52ms

And I check "rhlike" in the list 48ms

And I click on "Work With Intersection" 397ms

And I should not see a "sle_minion" link 8ms

And I should not see a "rhlike_minion" link 7ms

@deblike_minion
Scenario:
Add a union of 2 groups to SSM - Debian-like
676ms 6

When I follow the left menu "Systems > System Groups" 56ms

When I check "sles" in the list 51ms

And I check "deblike" in the list 61ms

And I click on "Work With Union" 482ms

And I should see "sle_minion" as link 11ms

And I should see "deblike_minion" as link 13ms

@deblike_minion
Scenario:
Add an intersection of 2 groups to SSM - Debian-like
559ms 6

When I follow the left menu "Systems > System Groups" 58ms

When I check "sles" in the list 50ms

And I check "deblike" in the list 51ms

And I click on "Work With Intersection" 387ms

And I should not see a "sle_minion" link 4ms

And I should not see a "deblike_minion" link 7ms

Scenario:
Cleanup: remove the sles group
1s 312ms 5

When I follow the left menu "Systems > System Groups" 57ms

When I follow "sles" in the content area 70ms

And I follow "Delete Group" in the content area 66ms

And I click on "Confirm Deletion" 1s 47ms

Then I should see a "deleted" text 71ms

@rhlike_minion
Scenario:
Cleanup: remove the rhlike group
1s 345ms 5

When I follow the left menu "Systems > System Groups" 65ms

When I follow "rhlike" in the content area 65ms

And I follow "Delete Group" in the content area 58ms

And I click on "Confirm Deletion" 50ms

Then I should see a "deleted" text 1s 103ms

@deblike_minion
Scenario:
Cleanup: remove the deblike group
1s 318ms 5

When I follow the left menu "Systems > System Groups" 58ms

When I follow "deblike" in the content area 65ms

And I follow "Delete Group" in the content area 57ms

And I click on "Confirm Deletion" 1s 81ms

Then I should see a "deleted" text 54ms

Scenario:
Cleanup: remove remaining systems from SSM after group union and intersection tests
63ms 1

When I click on the clear SSM button 63ms

@scope_visualization @scope_onboarding
Feature:Custom system info key-value pairs 13s 966ms 7

Scenario:
Log in as org admin user
1s 833ms 1

Given I am authorized 1s 833ms

Scenario:
Create a new key
1s 44ms 7

When I follow the left menu "Systems > Custom System Info" 115ms

And I follow "Create Key" 266ms

And I should see a "Create Custom Info Key" text 58ms

And I enter "key-label" as "label" 58ms

And I enter "key-desc" as "description" 61ms

And I click on "Create Key" 57ms

Then I should see a "Successfully added 1 custom key." text 427ms

Scenario:
Add a value to a system
3s 196ms 9

When I follow the left menu "Systems > System List > All" 131ms

And I follow this "sle_minion" link 966ms

And I follow "Custom Info" 442ms

And I follow "Create Value" 430ms

And I follow "key-label" 437ms

And I enter "key-value" as "value" 53ms

And I click on "Update Key" 648ms

Then I should see a "key-label" text 74ms

And I should see a "key-value" link 11ms

Scenario:
Edit the value
2s 843ms 9

When I follow the left menu "Systems > System List > All" 112ms

And I follow this "sle_minion" link 1s 43ms

And I follow "Custom Info" 430ms

And I follow "key-value" 442ms

And I should see a "Edit Custom Value" text 62ms

And I enter "key-value-edited" as "value" 66ms

And I click on "Update Key" 608ms

Then I should see a "key-label" text 64ms

And I should see a "key-value-edited" link 12ms

Scenario:
Edit the key description
894ms 6

When I follow the left menu "Systems > Custom System Info" 62ms

And I follow "key-label" 279ms

And I enter "key-desc-edited" as "description" 82ms

And I click on "Update Key" 399ms

Then I should see a "key-label" link 11ms

And I should see a "key-desc-edited" text 59ms

Scenario:
Delete the value
3s 36ms 8

When I follow the left menu "Systems > Custom System Info" 57ms

And I follow "key-label" 272ms

And I follow this "sle_minion" link 660ms

And I follow "Custom Info" 427ms

And I follow "key-value-edited" 506ms

And I follow "Delete Value" 421ms

And I click on "Remove Value" 629ms

Then I should see a "No custom information defined for this system." text 61ms

Scenario:
Delete the key
1s 118ms 5

When I follow the left menu "Systems > Custom System Info" 64ms

And I follow "key-label" 281ms

And I follow "Delete Key" 282ms

And I click on "Delete Key" 430ms

Then I should not see a "key-label" text 58ms

@scope_tomcat
Feature:Basic web security measures and recommendations 61ms 3

In order to be secure
As an authorized user
I want to avoid session and other attacks

Scenario:
Clear browser cookies for Basic web security measures
17ms 1

When I clear browser cookies 17ms

Scenario:
Caching should be enabled for static content
22ms 9

When I retrieve a "css" static resource 22ms

Then the response header "ETag" should not be present < 1ms

And the response header "Pragma" should not be present < 1ms

And the response header "Expires" should not be "0" < 1ms

And the response header "Set-Cookie" should not be present < 1ms

And the response header "X-Frame-Options" should contain "SAMEORIGIN" < 1ms

And the response header "X-XSS-Protection" should be "1; mode=block" < 1ms

And the response header "X-Content-Type-Options" should be "nosniff" < 1ms

And the response header "X-Permitted-Cross-Domain-Policies" should be "master-only" < 1ms

Scenario:
Obsolete and problematic headers for static content
21ms 2

Given I retrieve a "javascript" static resource 20ms

Then the response header "X-WebKit-CSP" should not be present < 1ms

@scope_salt
Feature:Salt is configured and running 6s 335ms 3

In order to operate Uyuni based on Salt
I want to use general Salt functionality and system registration

Scenario:
salt-api is properly configured
1s 13ms 4

When I get the contents of the remote file "/etc/salt/master.d/susemanager.conf" 1s 13ms

Then it should contain a "rest_cherrypy:" text < 1ms

And it should contain a "port: 9080" text < 1ms

And it should contain a "external_auth:" text < 1ms

Scenario:
salt-master and salt-api are listening
2s 3

Then salt-api should be listening on local port 9080 649ms

And salt-master should be listening on public port 4505 674ms

And salt-master should be listening on public port 4506 675ms

Scenario:
There are no top.sls files in certain folders
3s 321ms 10

When I run "ls /srv/susemanager/salt/top.sls" on "server" without error control 670ms

Then the command should fail < 1ms

When I run "ls /srv/susemanager/salt/top.sls" on "server" without error control 672ms

Then the command should fail < 1ms

When I run "ls /srv/susemanager/pillar/top.sls" on "server" without error control 653ms

Then the command should fail < 1ms

When I run "ls /usr/share/susemanager/salt/top.sls" on "server" without error control 661ms

Then the command should fail < 1ms

When I run "ls /usr/share/susemanager/pillar/top.sls" on "server" without error control 664ms

Then the command should fail < 1ms

@scope_configuration_channels
Feature:The channels page 21s 981ms 8

In Order to use the channels page and its subpages
As an authorized user
I want to see all the texts and links

Scenario:
Log in as org admin user
10s 718ms 1

Given I am authorized 10s 718ms

Scenario:
Completeness of the channels page
563ms 15

When I follow the left menu "Software > Channel List > All" 185ms

Then I should see a "Full Software Channel List" text 107ms

And I should see a "Channel List" link in the left menu 24ms

And I should see a "All" link in the left menu 24ms

And I should see a "Popular" link in the left menu 21ms

And I should see a "My Channels" link in the left menu 22ms

And I should see a "Shared" link in the left menu 21ms

And I should see a "Retired" link in the left menu 21ms

And I should see a "Package Search" link in the left menu 21ms

And I should see a "Manage" link in the left menu 23ms

And I should see a "All" link in the content area 21ms

And I should see a "Popular" link in the content area 17ms

And I should see a "My Channels" link in the content area 17ms

And I should see a "Shared" link in the content area 17ms

And I should see a "Retired" link in the content area 16ms

Scenario:
Popular channels
129ms 2

When I follow the left menu "Software > Channel List > Popular" 70ms

Then I should see a "Popular" text 58ms

Scenario:
Check packages in test channel
1s 790ms 10

When I follow the left menu "Software > Channel List > All" 70ms

And I follow "Show All Child Channels" 54ms

And I follow "Fake-RPM-SUSE-Channel" 582ms

And I follow "Packages" 561ms

Then I should see package "andromeda-dummy-2.0-1.1.noarch" 92ms

And I should see package "hoag-dummy-1.1-1.1.i586" 84ms

And I should see package "hoag-dummy-1.1-1.1.x86_64" 82ms

And I should see package "milkyway-dummy-2.0-1.1.i586" 82ms

And I should see package "milkyway-dummy-2.0-1.1.x86_64" 91ms

And I should see package "virgo-dummy-2.0-1.1.noarch" 88ms

Scenario:
Check package metadata
2s 81ms 10

When I follow the left menu "Software > Channel List > All" 65ms

And I follow "Show All Child Channels" 50ms

And I follow "Fake-RPM-SUSE-Channel" 569ms

And I follow "Packages" 573ms

And I follow "andromeda-dummy-2.0-1.1.noarch" 543ms

Then I should see a "This is the andromeda dummy package used for testing SUSE Manager" text 74ms

And I should see a "Fake-RPM-SUSE-Channel" link 11ms

And I should see a "build.opensuse.org" text 64ms

And I should see a "SHA512sum:" text 63ms

And I should see a "packages/1/199/andromeda-dummy/2.0-1.1/noarch/19940cc4a9f0d38a038a4455b0f1cf1290c4a4296b27f5a62f4aae60585ac6e2677e88c3c3127d487116ed8d9b1787379e23aafac46bc14408864926bedee693/andromeda-dummy-2.0-1.1.noarch.rpm" text 64ms

Scenario:
Check package dependencies page
2s 363ms 9

When I follow the left menu "Software > Channel List > All" 109ms

And I follow "Show All Child Channels" 48ms

And I follow "Fake-RPM-SUSE-Channel" 568ms

And I follow "Packages" 577ms

And I follow "andromeda-dummy-2.0-1.1.noarch" 537ms

And I follow "Dependencies" 365ms

Then I should see a "pam" text 50ms

And I should see a "rpmlib(PayloadIsXz) <= 5.2-1" text 51ms

And I should see a "andromeda-dummy = 2.0-1.1" text 54ms

Scenario:
Check package change log page
2s 134ms 8

When I follow the left menu "Software > Channel List > All" 103ms

And I follow "Show All Child Channels" 47ms

And I follow "Fake-RPM-SUSE-Channel" 584ms

And I follow "Packages" 567ms

And I follow "andromeda-dummy-2.0-1.1.noarch" 430ms

And I follow "Change Log" 300ms

Then I should see a "mc@suse.de" text 50ms

And I should see a "version 2.0" text 48ms

Scenario:
Check package file list page
2s 200ms 9

When I follow the left menu "Software > Channel List > All" 109ms

And I follow "Show All Child Channels" 44ms

And I follow "Fake-RPM-SUSE-Channel" 575ms

And I follow "Packages" 561ms

And I follow "andromeda-dummy-2.0-1.1.noarch" 445ms

And I follow "File List" 298ms

Then I should see a "This package contains the following files." text 56ms

And I should see a "/usr/share/doc/packages/andromeda-dummy/COPYING" text 54ms

And I should see a "sha256: 32b1062f7da84967e7019d01ab805935caa7ab7321a7ced0e30ebe75e5df1670" text 54ms

@scope_visualization
Feature:Managing channels 11s 92ms 9

In Order to distribute software to the clients
As an authorized user
I want to manage channels

Scenario:
Log in as org admin user
1s 841ms 1

Given I am authorized 1s 841ms

Scenario:
Fail when trying to add a duplicate channel
1s 523ms 10

When I follow the left menu "Software > Manage > Channels" 178ms

And I follow "Create Channel" 397ms

And I enter "Fake-Base-Channel-SUSE-like" as "Channel Name" 88ms

And I enter "fake-base-channel-suse-like" as "Channel Label" 81ms

And I select "None" from "Parent Channel" 60ms

And I select "x86_64" from "Architecture:" 50ms

And I enter "Base channel for testing" as "Channel Summary" 81ms

And I enter "No more desdcription for base channel." as "Channel Description" 92ms

And I click on "Create Channel" 413ms

Then I should see a "The channel name 'Fake-Base-Channel-SUSE-like' is already in use, please enter a different name" text 78ms

Scenario:
Fail when trying to use invalid characters in the channel label
1s 80ms 7

When I follow the left menu "Software > Manage > Channels" 73ms

And I follow "Create Channel" 377ms

And I enter "test123" as "Channel Name" 54ms

And I enter "tesT123" as "Channel Label" 56ms

And I enter "test123" as "Channel Summary" 59ms

And I click on "Create Channel" 380ms

Then I should see a "Invalid channel label, please see the format described below" text 78ms

Scenario:
Fail when trying to use invalid characters in the channel name
1s 82ms 7

When I follow the left menu "Software > Manage > Channels" 71ms

And I follow "Create Channel" 377ms

And I enter "!test123" as "Channel Name" 60ms

And I enter "test123" as "Channel Label" 56ms

And I enter "test123" as "Channel Summary" 59ms

And I click on "Create Channel" 377ms

Then I should see a "Invalid channel name, please see the format described below" text 78ms

@scc_credentials
Scenario:
Fail when trying to use reserved names for channels
789ms 7

When I follow the left menu "Software > Manage > Channels" 73ms

And I follow "Create Channel" 377ms

And I enter "openSUSE-Leap-15.6-Pool for x86_64" as "Channel Name" 85ms

And I enter "test123" as "Channel Label" 56ms

And I enter "test123" as "Channel Summary" 57ms

And I click on "Create Channel" 59ms

Then I should see a "The channel name 'openSUSE-Leap-15.6-Pool for x86_64' is reserved, please enter a different name" text 79ms

@scc_credentials
Scenario:
Fail when trying to use reserved labels for channels
774ms 7

When I follow the left menu "Software > Manage > Channels" 73ms

And I follow "Create Channel" 372ms

And I enter "test123" as "Channel Name" 56ms

And I enter "opensuse-leap-15.6-pool-x86_64" as "Channel Label" 80ms

And I enter "test123" as "Channel Summary" 55ms

And I click on "Create Channel" 59ms

Then I should see a "The channel label 'opensuse-leap-15.6-pool-x86_64' is reserved, please enter a different name" text 77ms

Scenario:
Create a channel that will be changed
807ms 7

When I follow the left menu "Software > Manage > Channels" 73ms

And I follow "Create Channel" 371ms

And I enter "aaaSLE-12-Cloud-Compute5-Pool for x86_64" as "Channel Name" 91ms

And I enter "sle-we12aaa-pool-x86_64-sap" as "Channel Label" 75ms

And I enter "test123" as "Channel Summary" 55ms

And I click on "Create Channel" 62ms

Then I should see a "Channel aaaSLE-12-Cloud-Compute5-Pool for x86_64 created." text 78ms

@scc_credentials
Scenario:
Fail when trying to change the channel name to a reserved name
1s 373ms 5

When I follow the left menu "Software > Manage > Channels" 71ms

And I follow "aaaSLE-12-Cloud-Compute5-Pool for x86_64" 568ms

And I enter "openSUSE-Leap-15.6-Pool for x86_64" as "Channel Name" 122ms

And I click on "Update Channel" 538ms

Then I should see a "The channel name 'openSUSE-Leap-15.6-Pool for x86_64' is reserved, please enter a different name" text 73ms

Scenario:
Cleanup: Delete created channel
1s 818ms 6

When I follow the left menu "Software > Manage > Channels" 73ms

And I follow "aaaSLE-12-Cloud-Compute5-Pool for x86_64" 550ms

And I follow "Delete Channel" 392ms

And I check "unsubscribeSystems" 80ms

And I click on "Delete Channel" 634ms

Then I should see a "Channel aaaSLE-12-Cloud-Compute5-Pool for x86_64 has been deleted." text 87ms

@scope_visualization
Feature:Left Menu Filter 2s 436ms 6 1

In order to verify the left menu filter works properly
As an authorized user
I want to be able to search different keywords in the menu filter

Scenario:
Log in as admin user
1s 697ms 1

Given I am authorized for the "Admin" section 1s 697ms

Scenario:
Search a word and expect the right result
112ms 2

When I enter "Admin" as the left menu search field 88ms

Then I should see a "Admin" link in the left menu 24ms

Scenario:
Search a partial word and expect the right result
111ms 2

When I enter "Formula" as the left menu search field 90ms

Then I should see a "Formula Catalog" link in the left menu 20ms

Scenario:
Search a word with a different case and expect the right result
110ms 2

When I enter "saLT" as the left menu search field 87ms

Then I should see a "Salt" link in the left menu 22ms

@susemanager
Scenario:
Search a word and expect several results
< 1ms 4

When I enter "SUSE" as the left menu search field 0s

Then I should see a "SUSE" text 0s

And I should see a "SUSE Multi-Linux Manager Server" text 0s

And I should see a "SUSE Multi-Linux Manager Proxy" text 0s

@uyuni
Scenario:
Search a word and expect several results
275ms 3

When I enter "Uyuni" as the left menu search field 88ms

Then I should see a "Uyuni Server" text 84ms

And I should see a "Uyuni Proxy" text 103ms

Scenario:
Search a non-existing word and expect no results
128ms 2

When I enter "Null" as the left menu search field 120ms

Then I should see left menu empty 7ms

@scope_api
Feature:API "channel" namespace and sub-namespaces 8s 474ms 10

Scenario:
Create a custom software channel
777ms 2

When I create the following channels: 379ms
LABEL NAME SUMMARY ARCH PARENT
foobar foobar foobar channel-x86_64

Then "foobar" should get listed with a call of listSoftwareChannels 397ms

Scenario:
Create a repository
1s 945ms 4

When I create a repo with label "foobar" and url 364ms

And I associate repo "foobar" with channel "foobar" 541ms

Then channel "foobar" should have attribute "last_modified" that is a date 521ms

And channel "foobar" should not have attribute "yumrepo_last_sync" 518ms

Scenario:
Create a custom software channel as the child of another one
1s 339ms 3

When I create the following channels: 424ms
LABEL NAME SUMMARY ARCH PARENT
foobar-child foobar-child child of foobar channel-x86_64 foobar

Then "foobar-child" should get listed with a call of listSoftwareChannels 393ms

And "foobar" should be the parent channel of "foobar-child" 520ms

Scenario:
List software channels
387ms 1

Then something should get listed with a call of listSoftwareChannels 387ms

Scenario:
Delete a child software channel
883ms 2

When I delete the software channel with label "foobar-child" 496ms

Then "foobar-child" should not get listed with a call of listSoftwareChannels 387ms

Scenario:
Delete a software channel
1s 283ms 3

When I delete the repo with label "foobar" 379ms

And I delete the software channel with label "foobar" 503ms

Then "foobar" should not get listed with a call of listSoftwareChannels 401ms

Scenario:
Check last synchronization of a synced channel
371ms 1

Then channel "fake-child-channel-i586" should have attribute "yumrepo_last_sync" that is a date 371ms

@rhlike_minion
Scenario:
Verify if a channel is modular via the API
737ms 2

When I verify channel "fake-base-channel-appstream" is modular via the API 366ms

And I verify channel "fake-rpm-suse-channel" is not modular via the API 371ms

@rhlike_minion
Scenario:
List modular channels via the API
359ms 1

When channel "Fake-Base-Channel-AppStream" is present in the modular channels listed via the API 359ms

@rhlike_minion
Scenario:
List available module streams for a given channel via the API
388ms 1

When "scorpio" module streams "2.0, 2.1" are available for channel "fake-base-channel-appstream" via the API 388ms

@scope_visualization
Feature:Patches page 11s 523ms 8

In order to use the Patches page
As a authorized user
I want to see all the texts and links

Scenario:
Log in as org admin user
1s 714ms 1

Given I am authorized 1s 714ms

Scenario:
Patches left menu
466ms 11

When I follow the left menu "Patches > Patch List > Relevant" 188ms

Then I should see a "Patches Relevant to Your Systems" text 125ms

And I should see a "Relevant" link in the left menu 22ms

And I should see a "All" link in the left menu 23ms

And I should see a "Advanced Search" link in the left menu 23ms

And I should see a "Manage Patches" link in the left menu 20ms

And I should see a "Clone Patches" link in the left menu 23ms

And I should see a "Bugfix Patches" link 10ms

And I should see a "Enhancement Patches" link 10ms

And I should see a "Security Patches" link 10ms

And I should see a Sign Out link 6ms

Scenario:
Create new bugfix patch with bnc URL
2s 637ms 18

When I follow the left menu "Patches > Manage Patches" 65ms

And I follow "Create Patch" 324ms

When I enter "Test Patch" as "synopsis" 78ms

And I enter "Test Advisory" as "advisoryName" 83ms

And I enter "Test Product" as "product" 95ms

And I enter "test@test.org" as "errataFrom" 85ms

And I enter "Test Topic" as "topic" 82ms

And I enter "Test Description" as "description" 87ms

And I enter "Test Solution" as "solution" 79ms

And I enter "620212" as "buglistId" 65ms

And I enter "Test Summary" as "buglistSummary" 78ms

And I enter "https://bugzilla.opensuse.org/show_bug.cgi?id=620212" as "buglistUrl" 193ms

And I enter "test,keywords" as "keywords" 80ms

And I enter "Test Reference" as "refersTo" 84ms

And I enter "Test Note" as "notes" 72ms

And I check test channel 66ms

And I click on "Create Patch" 937ms

Then I should see a "Patch: Test Advisory-1" text 75ms

Scenario:
Create new enhancement patch with no bnc URL
1s 708ms 17

When I follow the left menu "Patches > Manage Patches" 64ms

And I follow "Create Patch" 345ms

When I enter "Enhancement Patch" as "synopsis" 98ms

And I enter "Enhancement Advisory" as "advisoryName" 95ms

And I select "Product Enhancement Advisory" from "advisoryType" 80ms

And I enter "Enhancement Product" as "product" 100ms

And I enter "Enhancement Topic" as "topic" 89ms

And I enter "Enhancement Description" as "description" 99ms

And I enter "Enhancement Solution" as "solution" 91ms

And I enter "1234" as "buglistId" 70ms

And I enter "Enhancement Summary" as "buglistSummary" 92ms

And I enter "Enhancement,keywords" as "keywords" 99ms

And I enter "Enhancement Reference" as "refersTo" 99ms

And I enter "Enhancement Note" as "notes" 86ms

And I check test channel 56ms

And I click on "Create Patch" 59ms

Then I should see a "Patch: Enhancement Advisory-1" text 78ms

Scenario:
Delete enhancement patch
1s 269ms 5

When I follow the left menu "Patches > Manage Patches" 66ms

And I check "Enhancement Advisory" patch 61ms

And I click on "Delete Patches" 481ms

And I click on "Confirm" 552ms

Then I should see a "Successfully deleted 1 patches." text 107ms

Scenario:
Verify patch presence in web UI
1s 645ms 15

When I follow the left menu "Patches > Patch List > All" 167ms

And I follow "Bugfix Patches" in the content area 82ms

And I enter "Test Patch" as the filtered synopsis 59ms

And I click on the filter button 467ms

And I follow "Test Advisory" 361ms

Then I should see a "Test Patch" text 63ms

And I should see a "test@test.org" text 59ms

And I should see a "Test Topic" text 59ms

And I should see a "Test Description" text 64ms

And I should see a "Test Solution" text 57ms

And I should see a "Fake-Base-Channel-SUSE-like" link 11ms

And I should see a "Test Summary" link 10ms

And I should see a "keywords, test" text 60ms

And I should see a "Test Reference" text 63ms

And I should see a "Test Note" text 57ms

Scenario:
Assert that patch is now in test base channel
867ms 4

When I follow the left menu "Software > Channel List > All" 169ms

And I follow "Fake-Base-Channel-SUSE-like" 574ms

And I follow "Patches" in the content area 63ms

Then I should see a "Test Patch" text 59ms

Scenario:
Delete patch
1s 215ms 5

When I follow the left menu "Patches > Manage Patches" 102ms

And I check "Test Advisory" patch 57ms

And I click on "Delete Patches" 409ms

And I click on "Confirm" 539ms

Then I should see a "Successfully deleted 1 patches." text 106ms

@scc_credentials @scope_content_lifecycle_management
Feature:Content lifecycle 9m 51s 559ms 46 4

Scenario:
Log in as org admin user
1s 736ms 1

Given I am authorized 1s 736ms

Scenario:
Create CLM filter to remove all fonts packages
3s 93ms 10

When I follow the left menu "Content Lifecycle > Filters" 118ms

And I click on "Create Filter" 134ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 11ms

Then I should see a "Create a new filter" text 61ms

And I enter "remove fonts packages" as "filter_name" 127ms

And I select "Package (Name)" from "type" 1s 136ms

And I select "contains" from "matcher" 1s 114ms

And I enter "fonts" as "name" 73ms

And I click on "Save" in "Create a new filter" modal 260ms

Then I should see a "remove fonts packages" text 55ms

Scenario:
Create a content lifecycle project
1s 300ms 9

When I follow the left menu "Content Lifecycle > Projects" 66ms

And I follow "Create Project" 354ms

Then I should see a "Create a new Content Lifecycle Project" text 52ms

And I should see a "Project Properties" text 50ms

When I enter "clp_label" as "label" 68ms

And I enter "clp_name" as "name" 58ms

And I enter "clp_desc" as "description" 61ms

And I click on "Create" 65ms

And I wait until I see "Content Lifecycle Project - clp_name" text 523ms

Scenario:
Verify the content lifecycle project page
818ms 9

When I follow the left menu "Content Lifecycle > Projects" 58ms

Then I should see a "clp_name" text 57ms

And I should see a "clp_desc" text 64ms

When I follow "clp_name" 344ms

Then I should see a "Project Properties" text 59ms

And I should see a "Versions history" text 57ms

And I should see a "Sources" text 60ms

And I should see a "Filters" text 60ms

And I should see a "Environment Lifecycle" text 55ms

@susemanager
Scenario:
Add a source to the project
< 1ms 8

When I follow the left menu "Content Lifecycle > Projects" 0s

And I follow "clp_name" 0s

And I click on "Attach/Detach Sources" 0s

And I select "SLE-Product-SLES15-SP7-Pool for x86_64" from "selectedBaseChannel" 0s

And I exclude the recommended child channels 0s

And I click on "Save" 0s

And I wait until I see "SLE-Product-SLES15-SP7-Pool for x86_64" text 0s

Then I should see a "Version 1: (draft - not built) - Check the changes below" text 0s

@uyuni
Scenario:
Add a source to the project
2s 90ms 8

When I follow the left menu "Content Lifecycle > Projects" 59ms

And I follow "clp_name" 340ms

And I click on "Attach/Detach Sources" 75ms

And I select "openSUSE Tumbleweed (x86_64)" from "selectedBaseChannel" 1s 114ms

And I wait until I see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" text 90ms

And I click on "Save" 68ms

And I wait until I see "openSUSE Tumbleweed (x86_64)" text 280ms

Then I should see a "Version 1: (draft - not built) - Check the changes below" text 61ms

@susemanager
Scenario:
Verify added sources
< 1ms 4

When I follow the left menu "Content Lifecycle > Projects" 0s

And I follow "clp_name" 0s

Then I should see a "SLE-Product-SLES15-SP7-Updates for x86_64" text 0s

And I should see a "Build (2)" text 0s

@uyuni
Scenario:
Verify added sources
660ms 4

When I follow the left menu "Content Lifecycle > Projects" 63ms

And I follow "clp_name" 474ms

Then I should see a "openSUSE Tumbleweed (x86_64)" text 61ms

And I should see a "Build (1)" text 61ms

Scenario:
Add fonts packages filter to the project
1s 316ms 10

When I follow the left menu "Content Lifecycle > Projects" 62ms

And I follow "clp_name" 389ms

Then I should see a "Content Lifecycle Project - clp_name" text 64ms

When I click on "Attach/Detach Filters" 67ms

And I check the "remove fonts packages" CLM filter 163ms

And I click on "Save" 58ms

And I wait until I see "Deny" text 320ms

Then I should see a "remove fonts packages" text 66ms

When I follow the left menu "Content Lifecycle > Filters" 61ms

Then I should see a "clp_name" text 61ms

Scenario:
Add environments to the project
3s 792ms 25

When I follow the left menu "Content Lifecycle > Projects" 59ms

And I follow "clp_name" 427ms

Then I should see a "No environments created" text 64ms

When I click on "Add Environment" 73ms

And I enter "dev_name" as "name" 73ms

And I enter "dev_label" as "label" 73ms

And I enter "dev_desc" as "description" 68ms

And I click on "Save" 57ms

Then I wait until I see "dev_name" text 300ms

And I should see a "dev_desc" text 67ms

When I click on "Add Environment" 63ms

And I enter "prod_name" as "name" 78ms

And I enter "prod_label" as "label" 78ms

And I enter "prod_desc" as "description" 71ms

And I click on "Save" 55ms

Then I wait until I see "prod_name" text 321ms

And I should see a "prod_desc" text 78ms

When I click on "Add Environment" 64ms

And I enter "qa_name" as "name" 71ms

And I enter "qa_label" as "label" 72ms

And I enter "qa_desc" as "description" 74ms

And I select "prod_name" from "predecessorLabel" 1s 115ms

And I click on "Save" 61ms

Then I wait until I see "qa_name" text 238ms

And I should see a "qa_desc" text 81ms

@susemanager
Scenario:
Build the sources in the project
< 1ms 9

When I follow the left menu "Content Lifecycle > Projects" 0s

And I follow "clp_name" 0s

Then I should see a "not built" text in the environment "qa_name" 0s

When I click on "Build (3)" 0s

Then I should see a "Version 1 history" text 0s

When I enter "test version message 1" as "message" 0s

And I click the environment build button 0s

And I wait until I see "Version 1: test version message 1" text in the environment "dev_name" 0s

And I wait at most 600 seconds until I see "Built" text in the environment "dev_name" 0s

@uyuni
Scenario:
Build the sources in the project
6s 290ms 9

When I follow the left menu "Content Lifecycle > Projects" 59ms

And I follow "clp_name" 397ms

Then I should see a "not built" text in the environment "qa_name" 22ms

When I click on "Build (2)" 69ms

Then I should see a "Version 1 history" text 98ms

When I enter "test version message 1" as "message" 63ms

And I click the environment build button 56ms

And I wait until I see "Version 1: test version message 1" text in the environment "dev_name" 334ms

And I wait at most 600 seconds until I see "Built" text in the environment "dev_name" 5s 187ms

Scenario:
Promote the sources in the project
2m 2s 403ms 15

When I follow the left menu "Content Lifecycle > Projects" 57ms

Then I should see a "clp_name" text 58ms

And I should see a "clp_desc" text 55ms

And I should see a "dev_name > qa_name > prod_name" text 70ms

When I follow "clp_name" 388ms

Then I should see a "qa_desc" text in the environment "qa_name" 18ms

And I should see a "not built" text in the environment "qa_name" 17ms

When I click promote from Development to QA 59ms

Then I should see a "Version 1: test version message 1" text 98ms

And I click on "Promote environment" in "Promote version 1 into qa_name" modal 350ms

Then I wait at most 600 seconds until I see "Built" text in the environment "qa_name" 1m 367ms

When I click promote from QA to Production 64ms

Then I should see a "Version 1: test version message 1" text 91ms

And I click on "Promote environment" in "Promote version 1 into prod_name" modal 365ms

Then I wait at most 600 seconds until I see "Built" text in the environment "prod_name" 1m 339ms

@skip_if_github_validation
Scenario:
Add new sources and promote again
3m 733ms 27

When I follow the left menu "Content Lifecycle > Projects" 80ms

And I follow "clp_name" 407ms

Then I should see a "Build (0)" text 95ms

When I click on "Attach/Detach Sources" 77ms

And I uncheck "Vendors" 10s 971ms

And I enter "Fake-Base-Channel-SUSE-like" in the placeholder "Search a channel" 124ms

And I add the "Fake-Base-Channel-SUSE-like" channel to sources 76ms

And I click on "Save" 110ms

Then I wait until I see "Fake-Base-Channel-SUSE-like" text 517ms

And I wait until I see "Build (1)" text 86ms

And I should see a "Version 2: (draft - not built) - Check the changes below" text 86ms

When I click on "Build (1)" 69ms

Then I wait until I see "Version 2 history" text 92ms

When I enter "test version message 2" as "message" 64ms

And I click the environment build button 57ms

Then I wait until I see "Version 2: test version message 2" text in the environment "dev_name" 353ms

And I wait at most 600 seconds until I see "Built" text in the environment "dev_name" 45s 406ms

When I click promote from Development to QA 64ms

Then I should see a "Version 2: test version message 2" text 94ms

And I click on "Promote environment" in "Promote version 2 into qa_name" modal 412ms

And I wait for "1" second 1s

Then I wait at most 600 seconds until I see "Built" text in the environment "qa_name" 59s 437ms

When I click promote from QA to Production 63ms

Then I should see a "Version 2: test version message 2" text 103ms

And I click on "Promote environment" in "Promote version 2 into prod_name" modal 436ms

And I wait for "1" second 1s

Then I wait at most 600 seconds until I see "Built" text in the environment "prod_name" 59s 443ms

Scenario:
Create a CLM filter of type Package(NEVRA) that allows packages whose version and release number are lower to a defined one
13s 374ms 15

When I follow the left menu "Content Lifecycle > Filters" 82ms

And I click on "Create Filter" 74ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 11ms

Then I should see a "Create a new filter" text 71ms

When I enter "mercury" as "filter_name" 78ms

And I select "Package (NEVRA)" from "type" 1s 146ms

And I select "lower" from "matcher" 1s 116ms

And I enter "mercury" as "Package Name" 92ms

And I enter "mercury" as "Epoch" 92ms

And I enter "0.0.0" as "version" 72ms

And I enter "0.0.0" as "Release" 82ms

And I enter "x86_64" as "Architecture" 83ms

And I check radio button "Allow" 10s 68ms

And I click on "Save" in "Create a new filter" modal 240ms

Then I should see a "Filter created successfully" text 58ms

Scenario:
Create a CLM filter of type Package(NEVRA) that denys packages whose version and release number are lower to a defined one
3s 183ms 15

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 73ms

And I click on "Create Filter" 63ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 73ms

When I enter "venus" as "filter_name" 59ms

And I select "Package (NEVRA)" from "type" 1s 122ms

And I select "lower" from "matcher" 1s 98ms

And I enter "venus" as "Package Name" 73ms

And I enter "venus" as "Epoch" 76ms

And I enter "0.0.0" as "version" 67ms

And I enter "0.0.0" as "Release" 74ms

And I enter "x86_64" as "Architecture" 75ms

And I check radio button "Deny" 19ms

And I click on "Save" in "Create a new filter" modal 231ms

Then I should see a "Filter created successfully" text 66ms

Scenario:
Create CLM filter that allows packages of type Package (Provides Name)
2s 879ms 10

When I follow the left menu "Content Lifecycle > Filters" 61ms

And I click on "Create Filter" 62ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 74ms

When I enter "cereal" as "filter_name" 60ms

And I select "Package (Provides Name)" from "type" 1s 128ms

And I select "provides name" from "matcher" 1s 104ms

And I enter "cereal" as "Provides Name" 81ms

And I click on "Save" in "Create a new filter" modal 231ms

Then I should see a "Filter created successfully" text 67ms

Scenario:
Create CLM filter that denys packages of type Package (Provides Name)
2s 895ms 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 61ms

And I click on "Create Filter" 63ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 15ms

Then I should see a "Create a new filter" text 76ms

When I enter "potato" as "filter_name" 59ms

And I select "Package (Provides Name)" from "type" 1s 123ms

And I select "provides name" from "matcher" 1s 102ms

And I enter "potato" as "Provides Name" 78ms

And I check radio button "Deny" 16ms

And I click on "Save" in "Create a new filter" modal 228ms

Then I should see a "Filter created successfully" text 69ms

Scenario:
Create CLM filter of type Package (Build date) that allows packages whose date is lower than a defined one
12s 932ms 10

When I follow the left menu "Content Lifecycle > Filters" 62ms

And I click on "Create Filter" 61ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 79ms

When I enter "cherry" as "filter_name" 60ms

And I select "Package (Build date)" from "type" 1s 141ms

And I select "lower" from "matcher" 1s 110ms

And I check radio button "Allow" 10s 71ms

And I click on "Save" in "Create a new filter" modal 261ms

Then I should see a "Filter created successfully" text 76ms

Scenario:
Create CLM filter of type Package (Build date) that denys packages whose date is lower than a defined one
2s 891ms 10

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 62ms

And I click on "Create Filter" 99ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 80ms

When I enter "drummer" as "filter_name" 62ms

And I select "Package (Build date)" from "type" 1s 119ms

And I select "lower" from "matcher" 1s 102ms

And I check radio button "Deny" 16ms

And I click on "Save" in "Create a new filter" modal 263ms

Then I should see a "Filter created successfully" text 77ms

Scenario:
Create CLM filter of type Patch(Advisory Name) that allows patches that are equal to a defined one
12s 988ms 11

When I follow the left menu "Content Lifecycle > Filters" 61ms

And I click on "Create Filter" 65ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 7ms

Then I should see a "Create a new filter" text 86ms

When I enter "africa-patch" as "filter_name" 76ms

And I select "Patch (Advisory Name)" from "type" 1s 114ms

And I select "equals" from "matcher" 1s 106ms

And I enter "africa" as "Advisory name" 87ms

And I check radio button "Allow" 10s 60ms

And I click on "Save" in "Create a new filter" modal 243ms

Then I should see a "Filter created successfully" text 77ms

Scenario:
Create CLM filter of type Patch(Advisory Name) that denys patches that are equal to a defined one
2s 933ms 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 59ms

And I click on "Create Filter" 63ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 92ms

When I enter "asia-patch" as "filter_name" 73ms

And I select "Patch (Advisory Name)" from "type" 1s 116ms

And I select "equals" from "matcher" 1s 98ms

And I enter "asia" as "Advisory name" 69ms

And I check radio button "Deny" 17ms

And I click on "Save" in "Create a new filter" modal 248ms

Then I should see a "Filter created successfully" text 84ms

Scenario:
Create CLM filter of type Patch(Advisory Type) that allows Security Advisory patches that are equal to a defined one
12s 923ms 11

Warning: Radio button 'Security Advisory' is already checked

When I follow the left menu "Content Lifecycle > Filters" 58ms

And I click on "Create Filter" 66ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 90ms

When I enter "key" as "filter_name" 50ms

And I select "Patch (Advisory Type)" from "type" 1s 131ms

And I select "equals" from "matcher" 1s 98ms

And I check radio button "Security Advisory" 21ms

And I check radio button "Allow" 10s 65ms

And I click on "Save" in "Create a new filter" modal 250ms

Then I should see a "Filter created successfully" text 84ms

Scenario:
Create CLM filter of type Patch(Advisory Type) that denys Security Advisory patches that are equal to a defined one
2s 939ms 11

Warning: Radio button 'Security Advisory' is already checked
Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 57ms

And I click on "Create Filter" 67ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 9ms

Then I should see a "Create a new filter" text 94ms

When I enter "geminis-patch" as "filter_name" 83ms

And I select "Patch (Advisory Type)" from "type" 1s 121ms

And I select "equals" from "matcher" 1s 109ms

And I check radio button "Security Advisory" 18ms

And I check radio button "Deny" 16ms

And I click on "Save" in "Create a new filter" modal 274ms

Then I should see a "Filter created successfully" text 86ms

Scenario:
Create CLM filter of type Patch(Synopsis) that allows patches that that are equal to a defined one
13s 64ms 11

When I follow the left menu "Content Lifecycle > Filters" 62ms

And I click on "Create Filter" 64ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 9ms

Then I should see a "Create a new filter" text 100ms

When I enter "aries-patch" as "filter_name" 73ms

And I select "Patch (Synopsis)" from "type" 1s 128ms

And I select "equals" from "matcher" 1s 100ms

And I enter "aries" as "Synopsis" 81ms

And I check radio button "Allow" 10s 62ms

And I click on "Save" in "Create a new filter" modal 291ms

Then I should see a "Filter created successfully" text 88ms

Scenario:
Create CLM filter of type Patch(Synopsis) that denys patches that are equal to a defined one
3s 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 58ms

And I click on "Create Filter" 65ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 9ms

Then I should see a "Create a new filter" text 99ms

When I enter "andromeda-patch" as "filter_name" 86ms

And I select "Patch (Synopsis)" from "type" 1s 113ms

And I select "equals" from "matcher" 1s 111ms

And I enter "andromeda" as "Synopsis" 94ms

And I check radio button "Deny" 17ms

And I click on "Save" in "Create a new filter" modal 252ms

Then I should see a "Filter created successfully" text 91ms

Scenario:
Create CLM filter of type Patch(Keyword) that allows patches that contains Package Manager Restart Required keyword in its name
23s 36ms 11

When I follow the left menu "Content Lifecycle > Filters" 59ms

And I click on "Create Filter" 68ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 9ms

Then I should see a "Create a new filter" text 107ms

When I enter "mars-patch" as "filter_name" 72ms

And I select "Patch (Keyword)" from "type" 1s 123ms

And I select "contains" from "matcher" 1s 106ms

And I check radio button "Package Manager Restart Required" 10s 78ms

And I check radio button "Allow" 10s 59ms

And I click on "Save" in "Create a new filter" modal 254ms

Then I should see a "Filter created successfully" text 97ms

Scenario:
Create CLM filter of type Patch(Keyword) that denys patches that contains Package Manager Restart Required Keyword in its name
13s 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 61ms

And I click on "Create Filter" 67ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 101ms

When I enter "eurasia-patch" as "filter_name" 81ms

And I select "Patch (Keyword)" from "type" 1s 122ms

And I select "contains" from "matcher" 1s 112ms

And I check radio button "Package Manager Restart Required" 10s 64ms

And I check radio button "Deny" 20ms

And I click on "Save" in "Create a new filter" modal 261ms

Then I should see a "Filter created successfully" text 97ms

Scenario:
Create CLM filter of type Patch(Issue date) that allows patches whose date is greater or equal than a defined one
13s 22ms 10

When I follow the left menu "Content Lifecycle > Filters" 64ms

And I click on "Create Filter" 66ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 9ms

Then I should see a "Create a new filter" text 108ms

When I enter "milkyway-patch" as "filter_name" 86ms

And I select "Patch (Issue date)" from "type" 1s 132ms

And I select "greater or equal" from "matcher" 1s 108ms

And I check radio button "Allow" 10s 74ms

And I click on "Save" in "Create a new filter" modal 269ms

Then I should see a "Filter created successfully" text 101ms

Scenario:
Create CLM filter of type Patch(Issue date) that denys patches whose date is greater or equal than a defined one
3s 108ms 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 59ms

And I click on "Create Filter" 70ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 9ms

Then I should see a "Create a new filter" text 105ms

When I enter "venus-patch" as "filter_name" 76ms

And I select "Patch (Issue date)" from "type" 1s 123ms

And I select "greater or equal" from "matcher" 1s 113ms

When I enter "solar" as "filter_name" 139ms

And I check radio button "Deny" 17ms

And I click on "Save" in "Create a new filter" modal 285ms

Then I should see a "Filter created successfully" text 108ms

Scenario:
Create CLM filter of type Patch(Contains Package Name) that allows patches that are equal to a specific one
13s 170ms 11

When I follow the left menu "Content Lifecycle > Filters" 59ms

And I click on "Create Filter" 67ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 9ms

Then I should see a "Create a new filter" text 119ms

When I enter "Triangulum-patch" as "filter_name" 90ms

And I select "Patch (Contains Package Name)" from "type" 1s 118ms

And I select "equals" from "matcher" 1s 113ms

When I enter "Triangulum-patch" as "Package Name" 125ms

And I check radio button "Allow" 10s 70ms

And I click on "Save" in "Create a new filter" modal 291ms

Then I should see a "Filter created successfully" text 105ms

Scenario:
Create CLM filter of type Patch(Contains Package Name) that denys patches that are equal to a specific one
3s 83ms 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 63ms

And I click on "Create Filter" 69ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 119ms

When I enter "Pinwheel-patch" as "filter_name" 83ms

And I select "Patch (Contains Package Name)" from "type" 1s 117ms

And I select "equals" from "matcher" 1s 107ms

When I enter "Pinwheel-patch" as "Package Name" 109ms

And I check radio button "Deny" 16ms

And I click on "Save" in "Create a new filter" modal 279ms

Then I should see a "Filter created successfully" text 108ms

Scenario:
Create CLM filter that allows patches of type Patch(Contains Package Name) that matches to a specific one
13s 184ms 11

When I follow the left menu "Content Lifecycle > Filters" 63ms

And I click on "Create Filter" 93ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 9ms

Then I should see a "Create a new filter" text 118ms

When I enter "Sunflower-patch" as "filter_name" 86ms

And I select "Patch (Contains Package Name)" from "type" 1s 123ms

And I select "matches" from "matcher" 1s 116ms

When I enter "Sunflower-patch" as "Package Name" 115ms

And I check radio button "Allow" 10s 61ms

And I click on "Save" in "Create a new filter" modal 279ms

Then I should see a "Filter created successfully" text 116ms

Scenario:
Create CLM filter of type Patch(Contains Package Name) that denys patches that matches to a specific one
3s 154ms 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 65ms

And I click on "Create Filter" 67ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 9ms

Then I should see a "Create a new filter" text 130ms

When I enter "Whirlpool-patch" as "filter_name" 88ms

And I select "Patch (Contains Package Name)" from "type" 1s 116ms

And I select "matches" from "matcher" 1s 120ms

When I enter "Whirlpool-patch" as "Package Name" 114ms

And I check radio button "Deny" 18ms

And I click on "Save" in "Create a new filter" modal 293ms

Then I should see a "Filter created successfully" text 128ms

Scenario:
Create CLM filter of type Patch(Contains Package Provides Name) that allows patches with a specific name
13s 196ms 11

When I follow the left menu "Content Lifecycle > Filters" 65ms

And I click on "Create Filter" 70ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 9ms

Then I should see a "Create a new filter" text 138ms

When I enter "Antennae-patch" as "filter_name" 84ms

And I select "Patch (Contains Package Provides Name)" from "type" 1s 128ms

And I select "provides name" from "matcher" 1s 108ms

When I enter "Antennae-patch" as "Package Provides Name" 119ms

And I check radio button "Allow" 10s 56ms

And I click on "Save" in "Create a new filter" modal 287ms

Then I should see a "Filter created successfully" text 129ms

Scenario:
Create CLM filter of type Patch(Contains Package Provides Name) that denys patches with a specific name
3s 96ms 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 59ms

And I click on "Create Filter" 77ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 132ms

When I enter "hat-patch" as "filter_name" 68ms

And I select "Patch (Contains Package Provides Name)" from "type" 1s 115ms

And I select "provides name" from "matcher" 1s 105ms

When I enter "hat-patch" as "Package Provides Name" 92ms

And I check radio button "Deny" 16ms

And I click on "Save" in "Create a new filter" modal 299ms

Then I should see a "Filter created successfully" text 120ms

Scenario:
Create CLM filter of type Patch(Contains Package) that allows patches whose version is lower than a specific one
13s 508ms 14

When I follow the left menu "Content Lifecycle > Filters" 62ms

And I click on "Create Filter" 70ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 131ms

When I enter "Hubble-patch" as "filter_name" 78ms

And I select "Patch (Contains Package)" from "type" 1s 125ms

And I select "version lower than" from "matcher" 1s 118ms

When I enter "Hubble-patch" as "Package Name" 106ms

And I enter "Hubble-patch" as "Epoch" 109ms

And I enter "0.0.0" as "Version" 76ms

And I enter "0.0.0" as "Release" 79ms

And I check radio button "Allow" 10s 68ms

And I click on "Save" in "Create a new filter" modal 344ms

Then I should see a "Filter created successfully" text 128ms

Scenario:
Create CLM filter of type Patch(Contains Package) that denys patches whose version is lower than a specific one
3s 390ms 14

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 59ms

And I click on "Create Filter" 72ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 138ms

When I enter "galaxy-patch" as "filter_name" 77ms

And I select "Patch (Contains Package)" from "type" 1s 126ms

And I select "version lower than" from "matcher" 1s 115ms

When I enter "galaxy-patch" as "Package Name" 107ms

And I enter "galaxy-patch" as "Epoch" 103ms

And I enter "0.0.0" as "Version" 71ms

And I enter "0.0.0" as "Release" 72ms

And I check radio button "Deny" 16ms

And I click on "Save" in "Create a new filter" modal 292ms

Then I should see a "Filter created successfully" text 127ms

Scenario:
Create CLM filter of type Patch(Contains Package) that allows patches whose version is lower or equal than a specific one
13s 471ms 14

When I follow the left menu "Content Lifecycle > Filters" 64ms

And I click on "Create Filter" 71ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 9ms

Then I should see a "Create a new filter" text 147ms

When I enter "earth-patch" as "filter_name" 74ms

And I select "Patch (Contains Package)" from "type" 1s 127ms

And I select "version lower or equal" from "matcher" 1s 115ms

When I enter "earth-patch" as "Package Name" 104ms

And I enter "earth-patch" as "Epoch" 96ms

And I enter "0.0.0" as "Version" 73ms

And I enter "0.0.0" as "Release" 76ms

And I check radio button "Allow" 10s 58ms

And I click on "Save" in "Create a new filter" modal 316ms

Then I should see a "Filter created successfully" text 134ms

Scenario:
Create CLM filter of type Patch(Contains Package) that denys patches whose version is lower or equal than a specific one
3s 410ms 14

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 59ms

And I click on "Create Filter" 71ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 144ms

When I enter "moon-patch" as "filter_name" 74ms

And I select "Patch (Contains Package)" from "type" 1s 127ms

And I select "version lower or equal" from "matcher" 1s 107ms

When I enter "moon-patch" as "Package Name" 100ms

And I enter "moon-patch" as "Epoch" 93ms

And I enter "0.0.0" as "Version" 71ms

And I enter "0.0.0" as "Release" 73ms

And I check radio button "Deny" 17ms

And I click on "Save" in "Create a new filter" modal 328ms

Then I should see a "Filter created successfully" text 131ms

Scenario:
Create CLM filter to enable Ruby 2.7 module
3s 268ms 11

When I follow the left menu "Content Lifecycle > Filters" 62ms

And I click on "Create Filter" 145ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 11ms

Then I should see a "Create a new filter" text 145ms

And I enter "ruby 2.7 module" as "filter_name" 94ms

And I select "Module (Stream)" from "type" 1s 118ms

And I select "equals" from "matcher" 1s 117ms

And I enter "ruby" as "moduleName" 73ms

And I enter "2.7" as "moduleStream" 57ms

And I click on "Save" in "Create a new filter" modal 314ms

Then I should see a "Filter created successfully" text 129ms

Scenario:
Create CLM filter that allows Product Temporary Fix (All)
3s 65ms 10

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 69ms

And I click on "Create Filter" 73ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 137ms

When I enter "mars" as "filter_name" 55ms

And I select "Product Temporary Fix (All)" from "type" 1s 124ms

And I select "all" from "matcher" 1s 113ms

And I check radio button "Deny" 16ms

And I click on "Save" in "Create a new filter" modal 336ms

Then I should see a "Filter created successfully" text 130ms

Scenario:
Create CLM filter that denys Product Temporary Fix (All)
3s 95ms 10

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 64ms

And I click on "Create Filter" 70ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 145ms

When I enter "mercury-patch" as "filter_name" 87ms

And I select "Product Temporary Fix (All)" from "type" 1s 119ms

And I select "all" from "matcher" 1s 113ms

And I check radio button "Deny" 17ms

And I click on "Save" in "Create a new filter" modal 338ms

Then I should see a "Filter created successfully" text 130ms

Scenario:
Create CLM filter of type Product Temporary Fix (Number) that allows packages of a version lower than a specific one
13s 184ms 11

When I follow the left menu "Content Lifecycle > Filters" 58ms

And I click on "Create Filter" 74ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 140ms

When I enter "jupiter-patch" as "filter_name" 81ms

And I select "Product Temporary Fix (Number)" from "type" 1s 121ms

And I select "lower" from "matcher" 1s 120ms

And I enter "1" as "Number" 68ms

And I check radio button "Allow" 10s 56ms

And I click on "Save" in "Create a new filter" modal 322ms

Then I should see a "Filter created successfully" text 130ms

Scenario:
Create CLM filter of type Product Temporary Fix (Number) that denys packages of a version lower than a specific one
3s 136ms 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 58ms

And I click on "Create Filter" 68ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 139ms

When I enter "pluto-patch" as "filter_name" 75ms

And I select "Product Temporary Fix (Number)" from "type" 1s 128ms

And I select "lower" from "matcher" 1s 113ms

And I enter "2" as "Number" 60ms

And I check radio button "Deny" 16ms

And I click on "Save" in "Create a new filter" modal 335ms

Then I should see a "Filter created successfully" text 132ms

@skip_if_github_validation
Scenario:
Create CLM filter that allows packages versions that are equal to a specific Product Temporary Fix (Fixes Package Name)
13s 238ms 11

When I follow the left menu "Content Lifecycle > Filters" 65ms

And I click on "Create Filter" 71ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 141ms

When I enter "comet-patch" as "filter_name" 75ms

And I select "Product Temporary Fix (Fixes Package Name)" from "type" 1s 132ms

And I select "equals" from "matcher" 1s 106ms

And I enter "comet-patch" as "Package Name" 100ms

And I check radio button "Allow" 10s 73ms

And I click on "Save" in "Create a new filter" modal 327ms

Then I should see a "Filter created successfully" text 135ms

Scenario:
Cleanup: remove the Content Lifecycle Management project
946ms 5

When I follow the left menu "Content Lifecycle > Projects" 66ms

And I follow "clp_name" 535ms

And I click on "Delete" 90ms

And I click on "Delete" in "Delete Project" modal 99ms

Then I should not see a "clp_name" text 154ms

Scenario:
Cleanup: remove the CLM filters
4s 230ms 32

When I follow the left menu "Content Lifecycle > Filters" 56ms

And I click on "Select unused" 90ms

And I click on "Delete" 100ms

Then I should not see a "remove fonts packages" text 132ms

And I should not see a "africa-patch" text 2s 491ms

And I should not see a "andromeda-patch" text 48ms

And I should not see a "Antennae-patch" text 48ms

And I should not see a "aries-patch" text 48ms

And I should not see a "asia-patch" text 48ms

And I should not see a "cereal" text 48ms

And I should not see a "comet-patch" text 48ms

And I should not see a "cherry" text 54ms

And I should not see a "drummer" text 50ms

And I should not see a "earth-patch" text 50ms

And I should not see a "galaxy-patch" text 51ms

And I should not see a "hat-patch" text 48ms

And I should not see a "Hubble-patch" text 48ms

And I should not see a "mars" text 48ms

And I should not see a "mars-patch" text 48ms

And I should not see a "mercury" text 48ms

And I should not see a "milkyway-patch" text 56ms

And I should not see a "moon-patch" text 49ms

And I should not see a "Pinwheel-patch" text 50ms

And I should not see a "pluto-patch" text 49ms

And I should not see a "solar" text 49ms

And I should not see a "Sunflower-patch" text 50ms

And I should not see a "Triangulum-patch" text 48ms

And I should not see a "venus" text 51ms

And I should not see a "Whirlpool-patch" text 51ms

And I should not see a "remove fonts packages" text 57ms

And I should not see a "ruby 2.7 module" text 50ms

And I should not see a "key" text 52ms

@susemanager
Scenario:
Cleanup: remove the created channels
< 1ms 4

When I delete these channels with spacewalk-remove-channel: 0s
clp_label-prod_label-fake-base-channel-suse-like
clp_label-prod_label-sle-product-sles15-sp7-updates-x86_64
clp_label-qa_label-fake-base-channel-suse-like
clp_label-qa_label-sle-product-sles15-sp7-updates-x86_64
clp_label-dev_label-fake-base-channel-suse-like
clp_label-dev_label-sle-product-sles15-sp7-updates-x86_64

And I delete these channels with spacewalk-remove-channel: 0s
clp_label-prod_label-sle-product-sles15-sp7-pool-x86_64
clp_label-qa_label-sle-product-sles15-sp7-pool-x86_64
clp_label-dev_label-sle-product-sles15-sp7-pool-x86_64

And I list channels with spacewalk-remove-channel 0s

Then I shouldn't get "clp_label" 0s

@skip_if_github_validation @uyuni
Scenario:
Cleanup: remove the created channels
2s 311ms 3

When I delete these channels with spacewalk-remove-channel: 1s 340ms
clp_label-prod_label-fake-base-channel-suse-like
clp_label-prod_label-opensuse_tumbleweed-x86_64
clp_label-qa_label-fake-base-channel-suse-like
clp_label-qa_label-opensuse_tumbleweed-x86_64
clp_label-dev_label-fake-base-channel-suse-like
clp_label-dev_label-opensuse_tumbleweed-x86_64

And I list channels with spacewalk-remove-channel 971ms

Then I shouldn't get "clp_label" < 1ms

@scope_recurring_actions
Feature:Change the schedule of a task 42s 30ms 4

Scenario:
Log in as admin user
2s 44ms 1

Given I am authorized for the "Admin" section 2s 44ms

Scenario:
Change the schedule of task sandbox-cleanup-default to weekly
13s 713ms 10

When I follow the left menu "Admin > Task Schedules" 123ms

And I follow "sandbox-cleanup-default" 1s 172ms

And I check radio button "weekly" 10s 70ms

And I select "Friday" from "date_day_week" 63ms

And I click on "Update Schedule" 683ms

Then I should see a "Schedule sandbox-cleanup-default has been updated." text 86ms

When I follow the left menu "Admin > Task Schedules" 76ms

And I follow "sandbox-cleanup-default" 1s 338ms

Then I should see a "Friday" text 83ms

And radio button "weekly" should be checked 15ms

Scenario:
Change the schedule of task sandbox-cleanup-default to monthly
12s 814ms 9

When I follow the left menu "Admin > Task Schedules" 57ms

And I follow "sandbox-cleanup-default" 389ms

And I check radio button "monthly" 10s 70ms

And I select "17" from "date_day_month" 64ms

And I click on "Update Schedule" 59ms

Then I should see a "Schedule sandbox-cleanup-default has been updated." text 766ms

When I follow the left menu "Admin > Task Schedules" 60ms

And I follow "sandbox-cleanup-default" 1s 330ms

Then radio button "monthly" should be checked 16ms

Scenario:
Change the schedule of task sandbox-cleanup-default back to daily
13s 458ms 8

When I follow the left menu "Admin > Task Schedules" 60ms

And I follow "sandbox-cleanup-default" 1s 158ms

And I check radio button "daily" 10s 73ms

And I click on "Update Schedule" 678ms

Then I should see a "Schedule sandbox-cleanup-default has been updated." text 85ms

When I follow the left menu "Admin > Task Schedules" 61ms

And I follow "sandbox-cleanup-default" 1s 325ms

Then radio button "daily" should be checked 15ms

@scope_visualization
Feature:Test the notification/notification-messages feature 12s 800ms 4

Scenario:
Log in as org admin user
1s 777ms 1

Given I am authorized 1s 777ms

Scenario:
Check the unread notification counter is correct
10s 409ms 4

All notification-messages are read, I expect no notification badge

When I follow the left menu "Home > Notification Messages" 70ms

And I wait until I see "The server has collected the following notification messages." text 247ms

Then I follow "Unread Messages" 63ms

And the notification badge and the table should count the same amount of messages 10s 28ms

Scenario:
Delete notification-messages
316ms 5

There are no notification messages, nothing to do then

When I follow the left menu "Home > Notification Messages" 58ms

And I wait until I see "The server has collected the following notification messages." text 165ms

Then I follow "All Messages" 66ms

Then I check the first notification message 13ms

And I delete it via the "Delete" button 12ms

Scenario:
Flag a notification-message as read
296ms 5

There are no notification messages, nothing to do then

When I follow the left menu "Home > Notification Messages" 64ms

And I wait until I see "The server has collected the following notification messages." text 144ms

Then I follow "All Messages" 61ms

Then I check the first notification message 13ms

And I mark as read it via the "Mark as Read" button 13ms

Feature:Pay as you go 2m 12s 217ms 9

In order to use payg
As admin user
I want to list available ssh connections and add or remove them

Scenario:
Log in as admin user
1s 546ms 1

Given I am authorized for the "Admin" section 1s 546ms

Scenario:
Enter minimal information for payg ssh connection data
1s 511ms 11

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 187ms

And I click on "Add PAYG Connection" 354ms

And I enter "My Instance" as "description" 96ms

And I enter "my-host.local" as "host" 91ms

And I enter "root" as "username" 56ms

And I click on "Create" 70ms

Then I should see a "PAYG my-host.local created successfully" text 574ms

And I should see a "My Instance" text in element "Info-panel-wrapper" 19ms

And I should see a "my-host.local" text in element "Instance-panel-wrapper" 22ms

And I should see a "root" text in element "Instance-panel-wrapper" 17ms

And I should see a "Delete" button 19ms

Scenario:
Enter full information for payg ssh connection data
1m 2s 965ms 31

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 74ms

And I click on "Add PAYG Connection" 324ms

And I enter "My Full Instance" as "description" 90ms

And I enter "my-host-full.local" as "host" 101ms

And I enter "21" as "port" 51ms

And I enter "rootFull" as "username" 65ms

And I enter "passwordFull" as "password" 77ms

And I enter "keyFull" as "key" 69ms

And I enter "keyPasswordFull" as "key_password" 89ms

And I enter "my-bastion.local" as "bastion_host" 91ms

And I enter "22" as "bastion_port" 52ms

And I enter "b_rootFull" as "bastion_username" 74ms

And I enter "b_passwordFull" as "bastion_password" 86ms

And I enter "b_keyFull" as "bastion_key" 77ms

And I enter "b_keyPasswordFull" as "bastion_key_password" 94ms

And I click on "Create" 60ms

Then I should see a "PAYG my-host-full.local created successfully" text 1s 230ms

And I should see a "My Full Instance" text in element "Info-panel-wrapper" 16ms

And I should see a "my-host-full.local" text in element "Instance-panel-wrapper" 18ms

And I should see a "21" text in element "Instance-panel-wrapper" 18ms

And I should see a "rootFull" text in element "Instance-panel-wrapper" 18ms

And I should not see a "passwordFull" text in element "Instance-panel-wrapper" 10s 18ms

And I should not see a "keyFull" text in element "Instance-panel-wrapper" 10s 13ms

And I should not see a "keyPasswordFull" text in element "Instance-panel-wrapper" 10s 21ms

And I should see a "my-bastion.local" text in element "Bastion-panel-wrapper" 20ms

And I should see a "22" text in element "Bastion-panel-wrapper" 17ms

And I should see a "b_rootFull" text in element "Bastion-panel-wrapper" 17ms

And I should not see a "b_passwordFull" text in element "Bastion-panel-wrapper" 10s 31ms

And I should not see a "b_keyFull" text in element "Bastion-panel-wrapper" 10s 10ms

And I should not see a "b_keyPasswordFull" text in element "Bastion-panel-wrapper" 10s 11ms

And I should see a "Delete" button 19ms

Scenario:
Check pay-as-you-go list
261ms 5

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 93ms

Then I should see a "my-host.local" link 13ms

And I should see a "My Instance" text 72ms

And I should see a "my-host-full.local" link 11ms

And I should see a "My Full Instance" text 69ms

Scenario:
Edit connection description
907ms 7

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 70ms

And I follow "my-host-full.local" 327ms

And I click on "Edit Information" 73ms

And I enter "My new Full Instance" as "description" 122ms

And I click on "Save" in "Information" modal 223ms

Then I should see a "PAYG properties updated successfully" text 69ms

And I should see a "My new Full Instance" text in element "Info-panel-wrapper" 20ms

Scenario:
Edit instance ssh connection data
32s 79ms 15

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 68ms

And I follow "my-host-full.local" 402ms

And I click on "Edit Instance" 66ms

And I enter "221" as "port" 59ms

And I enter "NewRootFull" as "username" 125ms

And I enter "NewPasswordFull" as "password" 84ms

And I enter "newKeyFull" as "key" 81ms

And I enter "newKeyPasswordFull" as "key_password" 92ms

And I click on "Save" in "Instance SSH connection" modal 937ms

Then I should see a "PAYG properties updated successfully" text 70ms

And I should see a "221" text in element "Instance-panel-wrapper" 22ms

And I should see a "NewRootFull" text in element "Instance-panel-wrapper" 18ms

And I should not see a "NewPasswordFull" text in element "Instance-panel-wrapper" 10s 24ms

And I should not see a "newKeyFull" text in element "Instance-panel-wrapper" 10s 16ms

And I should not see a "newKeyPasswordFull" text in element "Instance-panel-wrapper" 10s 9ms

Scenario:
Edit bastion ssh connection data
31s 536ms 17

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 97ms

And I follow "my-host-full.local" 330ms

And I click on "Edit Bastion" 67ms

And I enter "my-new-bastion.local" as "bastion_host" 153ms

And I enter "222" as "bastion_port" 61ms

And I enter "b_new_rootFull" as "bastion_username" 106ms

And I enter "b_new_passwordFull" as "bastion_password" 91ms

And I enter "b_new_keyFull" as "bastion_key" 91ms

And I enter "b_new_keyPasswordFull" as "bastion_key_password" 108ms

And I click on "Save" in "Bastion SSH connection" modal 222ms

Then I should see a "PAYG properties updated successfully" text 77ms

And I should see a "my-new-bastion.local" text in element "Bastion-panel-wrapper" 23ms

And I should see a "222" text in element "Bastion-panel-wrapper" 19ms

And I should see a "b_new_rootFull" text in element "Bastion-panel-wrapper" 19ms

And I should not see a "b_new_passwordFull" text in element "Bastion-panel-wrapper" 10s 31ms

And I should not see a "b_new_keyFull" text in element "Bastion-panel-wrapper" 10s 17ms

And I should not see a "b_new_keyPasswordFull" text in element "Bastion-panel-wrapper" 10s 15ms

Scenario:
Cleanup: delete minimal information for payg ssh connection data
768ms 6

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 96ms

And I follow "my-host.local" 330ms

And I click on "Delete" 72ms

And I click on "Delete" in "Delete PAYG Connection" modal 93ms

Then I should not see a "my-host.local" link 8ms

And I should not see a "my-host.local" text 166ms

Scenario:
Cleanup: delete full information for payg ssh connection data
641ms 6

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 71ms

And I follow "my-host-full.local" 331ms

And I click on "Delete" 61ms

And I click on "Delete" in "Delete PAYG Connection" modal 87ms

Then I should not see a "my-bastion.local" link 8ms

And I should not see a "my-host.local" text 81ms

@sle_minion @scc_credentials @skip_if_github_validation @bug_reported
Feature:Push a package with unset vendor 1m 30s 994ms 1 3

In order to distribute software to the clients
As an authorized user
I want to push a package with unset vendor

Scenario:
Log in as org admin user
1s 753ms 1

Given I am authorized 1s 753ms

Scenario:
Pre-requisite: mgr-push package must be installed on the SLES minion
44s 750ms 12 1

Event Details: ---------- ID: sync_states Function: saltutil.sync_states Name: sync_states Result: true Comment: No updates to sync Started: 16:13:06.108995 Duration: 263.921 SLS: util.syncstates Changed: {} ---------- ID: mgr_absent_ca_package Function: pkg.removed Name: rhn-org-trusted-ssl-cert Result: true Comment: All specified packages are already absent Started: 16:13:11.731578 Duration: 11.196 SLS: certs Changed: {} ---------- ID: mgr_ca_cert Function: file.managed Name: /etc/pki/trust/anchors/RHN-ORG-TRUSTED-SSL-CERT Result: true Comment: File /etc/pki/trust/anchors/RHN-ORG-TRUSTED-SSL-CERT is in the correct state Started: 16:13:11.745656 Duration: 42.485 SLS: certs Changed: {} ---------- ID: update-ca-certificates Function: cmd.run Name: /usr/sbin/update-ca-certificates Result: true Comment: State was not run because none of the onchanges reqs changed Started: 16:13:11.789473 Duration: 0.006 SLS: certs Changed: {} ---------- ID: mgr_proxy_ca_cert_symlink Function: file.symlink Name: /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT Result: true Comment: onlyif condition is false Started: 16:13:11.789591 Duration: 716.163 SLS: certs Changed: {} ---------- ID: mgr_deploy_tools_uyuni_key Function: file.managed Name: /etc/pki/rpm-gpg/uyuni-tools-gpg-pubkey-0d20833e.key Result: true Comment: File /etc/pki/rpm-gpg/uyuni-tools-gpg-pubkey-0d20833e.key is in the correct state Started: 16:13:12.505959 Duration: 45.551 SLS: channels.gpg-keys Changed: {} ---------- ID: mgr_deploy_suse_addon_key Function: file.managed Name: /etc/pki/rpm-gpg/suse-addon-97a636db0bad8ecc.key Result: true Comment: File /etc/pki/rpm-gpg/suse-addon-97a636db0bad8ecc.key is in the correct state Started: 16:13:12.551645 Duration: 39.176 SLS: channels.gpg-keys Changed: {} ---------- ID: mgr_deploy_suse16_gpg_key Function: file.managed Name: /etc/pki/rpm-gpg/suse16-gpg-pubkey-09d9ea69.key Result: true Comment: File /etc/pki/rpm-gpg/suse16-gpg-pubkey-09d9ea69.key is in the correct state Started: 16:13:12.590965 Duration: 39.61 SLS: channels.gpg-keys Changed: {} ---------- ID: file_///etc/pki/rpm-gpg/uyuni-tools-gpg-pubkey-0d20833e.key Function: mgrcompat.module_run Name: pkg.add_repo_key Result: true Comment: Module function pkg.add_repo_key executed Started: 16:13:12.630738 Duration: 27.283 SLS: channels.gpg-keys Changed: ret: true ---------- ID: file_///usr/lib/rpm/gnupg/keys/gpg-pubkey-29b700a4-62b07e22.asc Function: mgrcompat.module_run Name: pkg.add_repo_key Result: true Comment: Module function pkg.add_repo_key executed Started: 16:13:12.658167 Duration: 30.298 SLS: channels.gpg-keys Changed: ret: true ---------- ID: mgrchannels_repo Function: file.managed Name: /etc/zypp/repos.d/susemanager:channels.repo Result: true Comment: File /etc/zypp/repos.d/susemanager:channels.repo is in the correct state Started: 16:13:12.688698 Duration: 153.468 SLS: channels Changed: {} ---------- ID: pkg_installed Function: pkg.installed Name: pkg_installed Result: false Comment: An error was encountered while installing package(s): Zypper command failure: Running as unit: run-p14848-i14849.scope; invocation ID: a87b314d25544790b59238e74170cb4aLoading repository data... Reading installed packages... Resolving package dependencies... Problem: 1: nothing provides 'python3-defusedxml' needed by the to be installed python3-rhnlib-5.2.3-2.1.uyuni.noarch Solution 1: do not install mgr-push-5.2.2-2.1.uyuni.noarch Solution 2: break python3-rhnlib-5.2.3-2.1.uyuni.noarch by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/c/d/?] (c): c Started: 16:13:12.842733 Duration: 2139.188 SLS: packages.pkginstall Changed: {}

Given I am on the Systems overview page of this "sle_minion" 1s 466ms

When I follow "Software" in the content area 72ms

And I wait until I see "Upgrade Packages" text 59ms

And I follow "Install" 590ms

And I wait until I see "Installable Packages" text 120ms

And I enter "mgr-push" as the filtered package name 46ms

And I click on the filter button 618ms

And I check "mgr-push" in the list 63ms

And I click on "Install Packages" 604ms

And I click on "Confirm" 744ms

Then I should see a "1 package install has been scheduled for" text 62ms

And I wait until event "Package Install/Upgrade scheduled" is completed 24s 958ms Show Error + 
                                            
 unknown error - Event failed (SystemCallError)
./features/step_definitions/navigation_steps.rb:107:in `block (2 levels) in (top (required))'
./features/support/commonlib.rb:106:in `block in repeat_until_timeout'
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/step_definitions/navigation_steps.rb:99:in `/^I wait at most (\d+) seconds until the event is completed, refreshing the page$/'
./features/step_definitions/common_steps.rb:157:in `/^I wait (\d+) seconds until the event is picked up and (\d+) seconds until the event "([^"]*)" is completed$/'
./features/step_definitions/common_steps.rb:174:in `/^I wait at most (\d+) seconds until event "([^"]*)" is completed$/'
./features/step_definitions/common_steps.rb:151:in `/^I wait until event "([^"]*)" is completed$/'
features/secondary/srv_push_package.feature:29:in `I wait until event "Package Install/Upgrade scheduled" is completed'

15s 342ms Show Info + 
16:12:58:000 - 16:13:28:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010023&aid=314
Screenshot +

Scenario:
Push a package with unset vendor through the SLES minion
17s 919ms 2 1 1

When I copy unset package file on "sle_minion" 2s 153ms

And I push package "/root/subscription-tools-1.0-0.noarch.rpm" into "fake-base-channel-suse-like" channel through "sle_minion" 411ms Show Error + 
                                            
 FAIL: mgrpush -u admin -p admin --server=uyuni-master-server.sumaci.aws --nosig -c fake-base-channel-suse-like /root/subscription-tools-1.0-0.noarch.rpm returned status code = 127.
Output:
 (ScriptError)
./features/support/remote_node.rb:169:in `run_local'
./features/support/remote_node.rb:117:in `run'
./features/step_definitions/common_steps.rb:327:in `/^I push package "([^"]*)" into "([^"]*)" channel through "([^"]*)"$/'
features/secondary/srv_push_package.feature:33:in `I push package "/root/subscription-tools-1.0-0.noarch.rpm" into "fake-base-channel-suse-like" channel through "sle_minion"'

Then I should see package "subscription-tools-1.0-0.noarch" in channel "Fake-Base-Channel-SUSE-like" 0s

15s 355ms Show Info + 
16:13:43:000 - 16:13:46:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010023&aid=314
Screenshot +

Scenario:
Check vendor of package displayed in web UI
26s 571ms 4 2 1

When I follow the left menu "Software > Channel List > All" 198ms

And I follow "Fake-Base-Channel-SUSE-like" 573ms

And I follow "Packages" 493ms

And I follow "subscription-tools-1.0-0.noarch" 10s 19ms Show Error + 
                                            
 Unable to find link "subscription-tools-1.0-0.noarch" (Capybara::ElementNotFound)
./features/support/commonlib.rb:198:in `click_link_and_wait'
./features/step_definitions/navigation_steps.rb:354:in `/^I follow "([^"]*)"$/'
features/secondary/srv_push_package.feature:40:in `I follow "subscription-tools-1.0-0.noarch"'

Then I should see a "Vendor:" text 0s

And I should see a "Not defined" text 0s

15s 287ms Show Info + 
16:14:01:000 - 16:14:13:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/ChannelPackages.do?cid=121
Screenshot +

@skip_if_github_validation @scope_reportdb @new_issue
Feature:Report database 1m 18s 497ms 9 1

In order to use reporting tools
As an authorized user
I want to access and use the report database named "ReportDB"

Scenario:
Log in as admin user
1s 682ms 1

Given I am authorized for the "Admin" section 1s 682ms

Scenario:
Populate the report database after bootstrapping minions
12s 778ms 1

When I schedule a task to update ReportDB 12s 778ms

Scenario:
Connect to the ReportDB on the server with admin user
1s 941ms 2

Then I should be able to connect to the ReportDB on the server 1s 161ms

And there should be a user allowed to create roles on the ReportDB 779ms

Scenario:
Create read-only user
2s 918ms 2

When I create a read-only user for the ReportDB 2s 69ms

Then I should see the read-only user listed on the ReportDB user accounts 848ms

Scenario:
External read-only user can connect to ReportDB and make queries
66ms 2

When I connect to the ReportDB with read-only user from external machine 65ms

Then I should be able to query the ReportDB 1ms

Scenario:
Read-only user can't make changes in the ReportDB
5ms 6

Then I should not be able to "insert" data in a ReportDB "table" as a read-only user 2ms

And I should not be able to "update" data in a ReportDB "table" as a read-only user 1ms

And I should not be able to "delete" data in a ReportDB "table" as a read-only user < 1ms

And I should not be able to "insert" data in a ReportDB "view" as a read-only user < 1ms

And I should not be able to "update" data in a ReportDB "view" as a read-only user < 1ms

And I should not be able to "delete" data in a ReportDB "view" as a read-only user < 1ms

Scenario:
ReportDB admin user can't access product database from external machine
1s 460ms 3

Given I know the ReportDB admin user credentials 1s 338ms

Then I should be able to connect to the ReportDB with the ReportDB admin user 60ms

And I should not be able to connect to product database with the ReportDB admin user 61ms

Scenario:
The systems should match between the UI and the ReportDB
10s 206ms 3

When I follow the left menu "Systems > System List > All" 192ms

And I make a list of the existing systems 10s 13ms

Then I should find the systems from the UI in the ReportDB < 1ms

@sle_minion
Scenario:
System changes should be reflected in systems, on ReportDB
27s 744ms 4

Search by hostname: uyuni-master-suse-minion
[{"last_boot"=>"2026-03-06T13:36:49Z", "name"=>"uyuni-master-suse-minion.sumaci.aws", "id"=>1000010023, "last_checkin"=>"2026-03-06T15:13:15Z"}]

Given I have a property "City" with value "Arrakeen" on "sle_minion" 8s 124ms

And I know the current synced_date for "sle_minion" 1ms

When I schedule a task to update ReportDB 19s 617ms

Then I should find the updated "City" property as "Arrakeen" on the "sle_minion", on ReportDB 1ms

Scenario:
Cleanup: delete read-only user
19s 692ms 2 1

When I delete the read-only user for the ReportDB 3s 363ms

Then I shouldn't see the read-only user listed on the ReportDB user accounts 968ms Show Error + 
                                            
 Created read-only user on the ReportDB remains listed (ScriptError)
./features/step_definitions/command_steps.rb:1424:in `/^I shouldn't see the read-only user listed on the ReportDB user accounts$/'
features/secondary/srv_reportdb.feature:57:in `I shouldn't see the read-only user listed on the ReportDB user accounts'

15s 361ms Show Info + 
16:15:40:000 - 16:15:44:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/admin/BunchDetail.do?label=mgr-update-reporting-bunch
Screenshot +

@flaky
Feature:Distribution Channel Mapping 3m 32s 644ms 12 3

Scenario:
Log in as org admin user
1s 863ms 1

Given I am authorized 1s 863ms

Scenario:
Check if Distribution Channel Mapping page exists
296ms 8

When I follow the left menu "Software > Distribution Channel Mapping" 119ms

Then I should see a "Distribution Channel Mapping" text 55ms

And I should see a "Channel List" link in the left menu 24ms

And I should see a "Package Search" link in the left menu 19ms

And I should see a "Manage" link in the left menu 23ms

And I should see a "Distribution Channel Mapping" link in the left menu 21ms

And I should see a "Create Distribution Channel Mapping" link 10ms

And I should see a "No distribution channel mappings currently exist." text in the content area 20ms

@scc_credentials @susemanager
Scenario:
Create new map for x86_64 SUSE clients
< 1ms 9

When I follow the left menu "Software > Distribution Channel Mapping" 0s

And I follow "Create Distribution Channel Mapping" 0s

Then I should see a "Create Distribution Channel Map" text 0s

When I enter "SUSE Linux Enterprise Server 15 SP 4" as "os" 0s

And I enter "15.5" as "release" 0s

And I select "x86_64" from "architecture" 0s

And I select "SLE-Product-SLES15-SP7-Pool for x86_64" from "channel_label" 0s

And I click on "Create Mapping" 0s

Then I should see a "SUSE Linux Enterprise Server 15 SP 4" link in the content area 0s

@scc_credentials @uyuni
Scenario:
Create new map for x86_64 openSUSE clients
1s 259ms 9

When I follow the left menu "Software > Distribution Channel Mapping" 61ms

And I follow "Create Distribution Channel Mapping" 320ms

Then I should see a "Create Distribution Channel Map" text 56ms

When I enter "openSUSE Tumbleweed" as "os" 72ms

And I enter "20250928" as "release" 55ms

And I select "x86_64" from "architecture" 68ms

And I select "openSUSE Tumbleweed (x86_64)" from "channel_label" 60ms

And I click on "Create Mapping" 538ms

Then I should see a "openSUSE Tumbleweed" link in the content area 26ms

@deblike_minion
Scenario:
Create new map for amd64 Ubuntu clients with test base channel
766ms 9

When I follow the left menu "Software > Distribution Channel Mapping" 66ms

And I follow "Create Distribution Channel Mapping" 354ms

Then I should see a "Create Distribution Channel Map" text 55ms

When I enter "Ubuntu 24.04" as "os" 56ms

And I enter "24.04" as "release" 47ms

And I select "AMD64 Debian" from "architecture" 54ms

And I select "Fake-Base-Channel-Debian-like" from "channel_label" 57ms

And I click on "Create Mapping" 51ms

Then I should see a "Ubuntu 24.04" link in the content area 23ms

@scc_credentials
Scenario:
Create new map for iSeries SUSE clients using test channel
1s 326ms 9

When I follow the left menu "Software > Distribution Channel Mapping" 64ms

And I follow "Create Distribution Channel Mapping" 372ms

Then I should see a "Create Distribution Channel Map" text 56ms

When I enter "SUSE Linux Enterprise Server 15 SP 4 iSeries" as "os" 89ms

And I enter "15.5" as "release" 49ms

And I select "iSeries" from "architecture" 59ms

And I select "Fake-Base-Channel-i586" from "channel_label" 57ms

And I click on "Create Mapping" 555ms

Then I should see a "SUSE Linux Enterprise Server 15 SP 4 iSeries" link in the content area 22ms

@scc_credentials @susemanager
Scenario:
Update map for x86_64 SUSE clients using test-x86_64 channel
< 1ms 11

When I follow the left menu "Software > Distribution Channel Mapping" 0s

Then I should see the text "SUSE Linux Enterprise Server 15 SP 4" in the Operating System field 0s

And I should see the text "x86_64" in the Architecture field 0s

And I should see the text "sle-product-sles15-sp7-pool-x86_64" in the Channel Label field 0s

When I follow "SUSE Linux Enterprise Server 15 SP 4" 0s

Then I should see a "Update Distribution Channel Map" text 0s

When I enter "SUSE Linux Enterprise Server 15 SP 4 modified" as "os" 0s

And I select "SLE-Product-SLES15-SP7-Pool for x86_64" from "channel_label" 0s

And I click on "Update Mapping" 0s

Then I should see the text "SUSE Linux Enterprise Server 15 SP 4 modified" in the Operating System field 0s

And I should see the text "sle-product-sles15-sp7-pool-x86_64" in the Channel Label field 0s

@scc_credentials @uyuni
Scenario:
Update map for x86_64 openSUSE clients using test-x86_64 channel
51s 294ms 11

When I follow the left menu "Software > Distribution Channel Mapping" 64ms

Then I should see the text "openSUSE Tumbleweed" in the Operating System field 10s 7ms

And I should see the text "x86_64" in the Architecture field 10s 4ms

And I should see the text "opensuse_tumbleweed-x86_64" in the Channel Label field 10s 12ms

When I follow "openSUSE Tumbleweed" 374ms

Then I should see a "Update Distribution Channel Map" text 55ms

When I enter "openSUSE Tumbleweed modified" as "os" 110ms

And I select "openSUSE Tumbleweed (x86_64)" from "channel_label" 49ms

And I click on "Update Mapping" 596ms

Then I should see the text "openSUSE Tumbleweed modified" in the Operating System field 10s 5ms

And I should see the text "opensuse_tumbleweed-x86_64" in the Channel Label field 10s 12ms

@deblike_minion
Scenario:
Update map for amd64 Ubuntu clients using test base channel
41s 162ms 8

When I follow the left menu "Software > Distribution Channel Mapping" 81ms

Then I should see the text "Ubuntu 24.04" in the Operating System field 10s 7ms

And I should see the text "AMD64 Debian" in the Architecture field 10s 14ms

And I should see the text "fake-base-channel-debian-like" in the Channel Label field 10s 10ms

When I follow "Ubuntu 24.04" 368ms

And I enter "Ubuntu 24.04 modified" as "os" 92ms

And I click on "Update Mapping" 574ms

Then I should see the text "Ubuntu 24.04 modified" in the Operating System field 10s 13ms

@scc_credentials
Scenario:
Update map for IA-32 SUSE clients using amd deb test channel
51s 195ms 10

When I follow the left menu "Software > Distribution Channel Mapping" 77ms

Then I should see the text "SUSE Linux Enterprise Server 15 SP 4 iSeries" in the Operating System field 10s 7ms

And I should see the text "iSeries" in the Architecture field 10s 14ms

And I should see the text "fake-base-channel-i586" in the Channel Label field 10s 1ms

When I follow "SUSE Linux Enterprise Server 15 SP 4 iSeries" 296ms

And I enter "SUSE Linux Enterprise Server 15 SP 4 iSeries modified" as "os" 148ms

And I select "Fake-Base-Channel-Debian-like" from "channel_label" 67ms

And I click on "Update Mapping" 556ms

Then I should see the text "SUSE Linux Enterprise Server 15 SP 4 iSeries modified" in the Operating System field 10s 13ms

And I should see the text "fake-base-channel-debian-like" in the Channel Label field 10s 11ms

@scc_credentials @susemanager
Scenario:
Cleanup: delete the map created for x68_64 SUSE clients
< 1ms 10

When I follow the left menu "Software > Distribution Channel Mapping" 0s

Then I should see the text "SUSE Linux Enterprise Server 15 SP 4 modified" in the Operating System field 0s

And I should see the text "x86_64" in the Architecture field 0s

When I follow "SUSE Linux Enterprise Server 15 SP 4 modified" 0s

Then I should see a "Update Distribution Channel Map" text 0s

And I should see a "Delete Distribution Channel" link 0s

When I follow "Delete Distribution Channel Mapping" 0s

Then I should see a "Delete Distribution Channel Map" text 0s

When I click on "Delete Mapping" 0s

Then I should not see a "SUSE Linux Enterprise Server 15 SP 4 modified" link 0s

@scc_credentials @uyuni
Scenario:
Cleanup: delete the map created for x68_64 openSUSE clients
20s 921ms 10

When I follow the left menu "Software > Distribution Channel Mapping" 95ms

Then I should see the text "openSUSE Tumbleweed modified" in the Operating System field 10s 5ms

And I should see the text "x86_64" in the Architecture field 10s 5ms

When I follow "openSUSE Tumbleweed modified" 309ms

Then I should see a "Update Distribution Channel Map" text 56ms

And I should see a "Delete Distribution Channel" link 10ms

When I follow "Delete Distribution Channel Mapping" 320ms

Then I should see a "Delete Distribution Channel Map" text 48ms

When I click on "Delete Mapping" 60ms

Then I should not see a "openSUSE Tumbleweed modified" link 9ms

@deblike_minion
Scenario:
Cleanup: delete the map created for amd64 Ubuntu clients
21s 215ms 10

When I follow the left menu "Software > Distribution Channel Mapping" 82ms

Then I should see the text "Ubuntu 24.04 modified" in the Operating System field 10s 13ms

And I should see the text "AMD64 Debian" in the Architecture field 10s 9ms

When I follow "Ubuntu 24.04 modified" 291ms

Then I should see a "Update Distribution Channel Map" text 54ms

And I should see a "Delete Distribution Channel" link 12ms

When I follow "Delete Distribution Channel Mapping" 251ms

Then I should see a "Delete Distribution Channel Map" text 48ms

When I click on "Delete Mapping" 443ms

Then I should not see a "Ubuntu 24.04 modified" link 8ms

@scc_credentials
Scenario:
Cleanup: delete the map created for i586 clients
21s 189ms 10

When I follow the left menu "Software > Distribution Channel Mapping" 76ms

Then I should see the text "SUSE Linux Enterprise Server 15 SP 4 iSeries modified" in the Operating System field 10s 4ms

And I should see the text "x86_64" in the Architecture field 10s 1ms

When I follow "SUSE Linux Enterprise Server 15 SP 4 iSeries modified" 282ms

Then I should see a "Update Distribution Channel Map" text 54ms

And I should see a "Delete Distribution Channel" link 11ms

When I follow "Delete Distribution Channel Mapping" 253ms

Then I should see a "Delete Distribution Channel Map" text 51ms

When I click on "Delete Mapping" 445ms

Then I should not see a "SUSE Linux Enterprise Server 15 SP 4 iSeries modified" link 8ms

Scenario:
Sanity check whether the page is in its default state
152ms 3

When I follow the left menu "Software > Distribution Channel Mapping" 77ms

Then I should see a "Distribution Channel Mapping" text 52ms

And I should see a "No distribution channel mappings currently exist." text in the content area 22ms

Feature:Task Engine Status 28s 175ms 4 2

Scenario:
Login as admin
1s 824ms 1

Given I am authorized for the "Admin" section 1s 824ms

@susemanager
Scenario:
Check if the Task Engine Status page exists
< 1ms 6

When I follow the left menu "Admin > Task Engine Status > Last Execution Times" 0s

Then I should see a "Task Engine Status" text 0s

And I should see a "The following is a status report for the various tasks run by the SUSE Multi-Linux Manager task engine:" text 0s

And I should see a "Runtime Status" text 0s

And I should see a "Last Execution Times" link in the left menu 0s

And I should see a "Runtime Status" link in the left menu 0s

@uyuni
Scenario:
Check if the Task Engine Status page exists
1s 146ms 6

When I follow the left menu "Admin > Task Engine Status > Last Execution Times" 840ms

Then I should see a "Task Engine Status" text 89ms

And I should see a "The following is a status report for the various tasks run by the Uyuni task engine:" text 84ms

And I should see a "Runtime Status" text 84ms

And I should see a "Last Execution Times" link in the left menu 26ms

And I should see a "Runtime Status" link in the left menu 21ms

Scenario:
Check if the Runtime Status Page exists
593ms 6

When I follow the left menu "Admin > Task Engine Status > Runtime Status" 73ms

Then I should see a "Task Engine Status" text 54ms

And I should see a "Last Execution Times" text 52ms

And I should see a "The server is running or has finished executing the following tasks during the latest 5 minutes." text 375ms

And I should see a "Last Execution Times" link in the left menu 19ms

And I should see a "Runtime Status" link in the left menu 17ms

Scenario:
Run a remote command on the server to check if it shows up on Last Execution Times page
24s 611ms 6

When I follow the left menu "Admin > Task Engine Status > Last Execution Times" 71ms

And I run "cobbler sync" on "server" 3s 182ms

And I refresh the page 11s 169ms

Then I should see a "Cobbler Sync:" text 91ms

And I should see the correct timestamp for task "Cobbler Sync:" 10s 3ms

And I should see a "FINISHED" text 92ms

@scc_credentials @susemanager
Scenario:
Resync a product to trigger a new task and check if it is visible on the Runtime Status page
< 1ms 13

When I follow the left menu "Admin > Task Engine Status > Runtime Status" 0s

And I follow the left menu "Admin > Setup Wizard > Products" 0s

And I wait until I do not see "Loading" text 0s

And I enter "SUSE Linux Enterprise Server 15 SP7 x86_64" as "product-description-filter" 0s

And I wait until I see "SUSE Linux Enterprise Server 15 SP7 x86_64" text 0s

Then I should see the "SUSE Linux Enterprise Server 15 SP7 x86_64" selected 0s

When I click on "Schedule channels product resync" 0s

And I follow the left menu "Admin > Task Engine Status > Runtime Status" 0s

And I wait until I see "repo-sync" text 0s

Then I should see the correct timestamp for task "repo-sync" 0s

And I should see a "running" text in the content area 0s

And I wait until I see "finished" text 0s

And I should see the correct timestamp for task "repo-sync" 0s

@scope_api
Feature:Systems errata API 6s 190ms 2

@ssh_minion
Scenario:
Check the relevant errata for a system
4s 730ms 1

When I retrieve the relevant errata for ssh_minion 4s 730ms

@ssh_minion @rhlike_minion @deblike_minion
Scenario:
Check the relevant errata for multiple systems
1s 459ms 1

When I retrieve the relevant errata for ssh_minion, rhlike_minion, deblike_minion 1s 459ms

@scope_salt @skip_if_github_validation @bug_reported
Feature:Health Check tool based on a supportconfig 6m 41s 59ms 2 3

A supportconfig generated from the Uyuni server
should be able to be parsed by Health Check tool.

Scenario:
A supportconfig is taken from the server
1m 44s 742ms 2

When I generate a supportconfig for the server 1m 43s 716ms

Then I obtain and extract the supportconfig from the server 1s 26ms

Scenario:
Execute Health Check tool with server supportconfig
15s 527ms 1 1 1

When I start the health check tool with supportconfig "/root/server-supportconfig/uyuni-server-supportconfig/" on "localhost" 525ms Show Error + 
                                            
 FAIL: mgr-health-check -v -s /root/server-supportconfig/uyuni-server-supportconfig/ start returned status code = 1.
Output:
┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃                                 Health Check                                 ┃
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛
[16:22:50] Checking connection with podman:                           main.py:43
           Executing: podman --version                               utils.py:37
           podman version 4.9.5                                      utils.py:61
           Supportconfig path not accessible, exitting                main.py:94
 (ScriptError)
./features/support/remote_node.rb:169:in `run_local'
./features/support/remote_node.rb:117:in `run'
./features/step_definitions/command_steps.rb:1793:in `/^I start the health check tool with supportconfig "([^"]*)" on "([^"]*)"$/'
features/secondary/srv_health_check_supportconfig.feature:17:in `I start the health check tool with supportconfig "/root/server-supportconfig/uyuni-server-supportconfig/" on "localhost"'

Then I check that the health check tool is running on "localhost" 0s

15s 1ms Show Info + 
16:22:49:000 - 16:22:50:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/admin/TaskStatus.do
Screenshot +

Scenario:
Health Check containers are healthy and running
4m 24s 930ms 1 3 1

When I wait until port "9000" is listening on "localhost" host 4m 10s Show Error + 
                                            
 execution expired (Timeout::Error)
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/support/remote_node.rb:186:in `run_until_ok'
./features/step_definitions/command_steps.rb:1570:in `/^I wait until port "([^"]*)" is listening on "([^"]*)" (host|container)$/'
features/secondary/srv_health_check_supportconfig.feature:21:in `I wait until port "9000" is listening on "localhost" host'

Then I wait until port "3100" is listening on "localhost" host 0s

And I wait until port "9081" is listening on "localhost" host 0s

And I wait until port "3000" is listening on "localhost" host 0s

14s 929ms Show Info + 
16:23:05:000 - 16:27:15:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/admin/TaskStatus.do
Screenshot +

Scenario:
Health Check containers are exposing metrics
15s 58ms 1 1

Then I check that the health check tool exposes metrics on "localhost" 186ms Show Error + 
                                            
 FAIL: curl -s localhost:9000/metrics.json | python3 -c 'import sys, json; print(json.load(sys.stdin).keys())' returned status code = 1.
Output:
 (ScriptError)
./features/support/remote_node.rb:169:in `run_local'
./features/support/remote_node.rb:117:in `run'
./features/step_definitions/command_steps.rb:1821:in `/^I check that the health check tool exposes metrics on "([^"]*)"$/'
features/secondary/srv_health_check_supportconfig.feature:27:in `I check that the health check tool exposes metrics on "localhost"'

14s 872ms Show Info + 
16:27:30:000 - 16:27:30:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/admin/TaskStatus.do
Screenshot +

Scenario:
I can stop the Health Check tool
801ms 3

When I stop health check tool on "localhost" 414ms

Then I check that the health check tool is not running on "localhost" 197ms

And I remove test supportconfig on "localhost" 189ms

@skip_if_github_validation
Feature:Password Policy Management 1m 57s 650ms 17

As an organization administrator,
I want to configure and enforce password complexity requirements,
So that user accounts comply with security policies

Scenario:
Log in as org admin user
1s 618ms 1

Given I am authorized as "admin" with password "admin" 1s 618ms

Scenario:
Navigate to Password Policy settings page
791ms 2

When I follow the left menu "Admin > Manager Configuration > Password Policy" 717ms

Then I should see a "Server Configuration - Password Policy" text 74ms

Scenario:
Configure password complexity restrictions
662ms 5

When I set the minimum password length to "5" 52ms

And I set the maximum password length to "12" 53ms

And I enable the following restrictions: 321ms
Require Digits
Require Lowercase Characters
Require Uppercase Characters
Require Special Characters
Restrict Characters Occurrences
Restrict Consecutive Characters

And I click on "Save" 58ms

And I should see a "Password Policy Changed" text 176ms

Scenario:
Verify password complexity restrictions are saved correctly
10s 401ms 2

When I refresh the page 10s 353ms

Then the following restrictions should be enabled: 47ms
Require Digits
Require Lowercase Characters
Require Uppercase Characters
Require Special Characters
Restrict Characters Occurrences
Restrict Consecutive Characters

Scenario:
Update special characters list and maximum character occurrence
359ms 4

When I set the special characters list to "$@?" 58ms

And I set the maximum allowed occurrence of any character to "3" 49ms

And I click on "Save" 52ms

And I should see a "Password Policy Changed" text 198ms

Scenario Outline:
Reject invalid passwords based on policy enforcement
8s 985ms 2

Failed to create user password_policy_user: unknown error - API failure: Passwords must be at least 5 characters.

When I create a user with name "password_policy_user" and password "aB$1" with roles "config_admin,system_group_admin,activation_key_admin,image_admin" 8s 985ms

Then the user creation should fail with error containing "Passwords must be at least 5 characters" < 1ms

Scenario Outline:
Reject invalid passwords based on policy enforcement
9s 72ms 2

Failed to create user password_policy_user: unknown error - API failure: Passwords must contain at least one upper case character.

When I create a user with name "password_policy_user" and password "ab$123" with roles "config_admin,system_group_admin,activation_key_admin,image_admin" 9s 72ms

Then the user creation should fail with error containing "Passwords must contain at least one upper case character" < 1ms

Scenario Outline:
Reject invalid passwords based on policy enforcement
9s 207ms 2

Failed to create user password_policy_user: unknown error - API failure: Passwords must contain at least one lower case character.

When I create a user with name "password_policy_user" and password "AB$123" with roles "config_admin,system_group_admin,activation_key_admin,image_admin" 9s 207ms

Then the user creation should fail with error containing "Passwords must contain at least one lower case character" < 1ms

Scenario Outline:
Reject invalid passwords based on policy enforcement
8s 979ms 2

Failed to create user password_policy_user: unknown error - API failure: Passwords must contain at least one digit.

When I create a user with name "password_policy_user" and password "aB$cde" with roles "config_admin,system_group_admin,activation_key_admin,image_admin" 8s 979ms

Then the user creation should fail with error containing "Passwords must contain at least one digit" < 1ms

Scenario Outline:
Reject invalid passwords based on policy enforcement
9s 57ms 2

Failed to create user password_policy_user: unknown error - API failure: Passwords must contain at least one special character, allowed special characters are: $@?.

When I create a user with name "password_policy_user" and password "aBc123" with roles "config_admin,system_group_admin,activation_key_admin,image_admin" 9s 57ms

Then the user creation should fail with error containing "Passwords must contain at least one special character" < 1ms

Scenario Outline:
Reject invalid passwords based on policy enforcement
9s 131ms 2

Failed to create user password_policy_user: unknown error - API failure: Passwords must contain at least one special character, allowed special characters are: $@?.

When I create a user with name "password_policy_user" and password "aB:123" with roles "config_admin,system_group_admin,activation_key_admin,image_admin" 9s 130ms

Then the user creation should fail with error containing "Passwords must contain at least one special character, allowed special characters are: $@?" < 1ms

Scenario Outline:
Reject invalid passwords based on policy enforcement
8s 969ms 2

Failed to create user password_policy_user: unknown error - API failure: **consecutive_characters_presents**

When I create a user with name "password_policy_user" and password "aaB$123" with roles "config_admin,system_group_admin,activation_key_admin,image_admin" 8s 969ms

Then the user creation should fail with error containing "consecutive_characters_presents" < 1ms

Scenario Outline:
Reject invalid passwords based on policy enforcement
9s 68ms 2

Failed to create user password_policy_user: unknown error - API failure: **consecutive_characters_presents** :: Password characters occurrences exceeded maximum allowed 3.

When I create a user with name "password_policy_user" and password "aB$a12aa3" with roles "config_admin,system_group_admin,activation_key_admin,image_admin" 9s 68ms

Then the user creation should fail with error containing "Password characters occurrences exceeded maximum allowed 3" < 1ms

Scenario Outline:
Reject invalid passwords based on policy enforcement
9s 145ms 2

Failed to create user password_policy_user: unknown error - API failure: Passwords cannot be more than 12 characters.

When I create a user with name "password_policy_user" and password "aBcdef$123456" with roles "config_admin,system_group_admin,activation_key_admin,image_admin" 9s 145ms

Then the user creation should fail with error containing "Passwords cannot be more than 12 characters" < 1ms

Scenario:
Accept valid password complying with policy
10s 907ms 2

New user password_policy_user created with roles: config_admin, system_group_admin, activation_key_admin, image_admin

When I create a user with name "password_policy_user" and password "aB$123" with roles "config_admin,system_group_admin,activation_key_admin,image_admin" 10s 907ms

Then the user creation should succeed < 1ms

Scenario:
Reset password policy to default settings
10s 844ms 5

When I follow the left menu "Admin > Manager Configuration > Password Policy" 76ms

And I click on "Reset" 60ms

And I should see a "Password Policy Reset to Default" text 289ms

And I refresh the page 10s 370ms

Then the following restrictions should be disabled: 46ms
Require Digits
Require Lowercase Characters
Require Uppercase Characters
Require Special Characters
Restrict Characters Occurrences
Restrict Consecutive Characters

Scenario:
Cleanup: Delete test user
446ms 1

When I delete user "password_policy_user" 446ms

@skip_if_github_validation @build_host @scope_building_container_images @scope_cve_audit @no_auth_registry
Feature:Build container images and CVE audit them 18m 38s 859ms 16 14

Scenario:
Log in as org admin user
1s 690ms 1

Given I am authorized 1s 690ms

Scenario:
Create a simple image profile without activation key
2s 782ms 6

GITPROFILES: https://github.com/uyuni-project/uyuni.git#:testsuite/features/profiles/temporary

When I follow the left menu "Images > Profiles" 117ms

And I follow "Create" 483ms

And I enter "suse_simple" as "label" 102ms

And I select "galaxy-registry" from "imageStore" 1s 136ms

And I enter "Docker" relative to profiles as "path" 880ms

And I click on "create-btn" 60ms

Scenario:
Create a simple real image profile without activation key
2s 815ms 6

GITPROFILES: https://github.com/uyuni-project/uyuni.git#:testsuite/features/profiles/temporary

When I follow the left menu "Images > Profiles" 61ms

And I follow "Create" 522ms

And I enter "suse_real_simple" as "label" 121ms

And I select "galaxy-registry" from "imageStore" 1s 113ms

And I enter "Docker/serverhost" relative to profiles as "path" 944ms

And I click on "create-btn" 52ms

@scc_credentials
Scenario:
Create an image profile with activation key
3s 835ms 7

GITPROFILES: https://github.com/uyuni-project/uyuni.git#:testsuite/features/profiles/temporary

When I follow the left menu "Images > Profiles" 60ms

And I follow "Create" 519ms

And I enter "suse_key" as "label" 85ms

And I select "galaxy-registry" from "imageStore" 1s 112ms

And I select "1-SUSE-KEY-x86_64" from "activationKey" 1s 115ms

And I enter "Docker" relative to profiles as "path" 885ms

And I click on "create-btn" 56ms

@scc_credentials
Scenario:
Create a simple real image profile with activation key
3s 884ms 7

GITPROFILES: https://github.com/uyuni-project/uyuni.git#:testsuite/features/profiles/temporary

When I follow the left menu "Images > Profiles" 60ms

And I follow "Create" 464ms

And I enter "suse_real_key" as "label" 101ms

And I select "galaxy-registry" from "imageStore" 1s 143ms

And I select "1-SUSE-KEY-x86_64" from "activationKey" 1s 116ms

And I enter "Docker/serverhost" relative to profiles as "path" 942ms

And I click on "create-btn" 56ms

@scc_credentials
Scenario:
Build the suse_key image with and without activation key
1m 1s 543ms 3 2 1

Event Details: ---------- ID: mgr_registries_login Function: mgrcompat.module_run Name: docker.login Result: true Comment: Module function docker.login executed Started: 16:30:34.301080 Duration: 2.078 SLS: images.docker Changed: ret: retcode: 0.0 Errors: [ ] Results: { } ---------- ID: mgr_buildimage Function: mgrcompat.module_run Name: docker.build Result: false Comment: Module function docker.build threw an exception. Exception: Build failed for https://github.com/uyuni-project/uyuni.git#:testsuite/features/profiles/temporary/docker_profiles/cloud_aws/Docker. Error(s) follow: manifest for ip-172-16-1-175.eu-central-1.compute.internal/suse/sle15:15.7 not found: manifest unknown: manifest unknown Started: 16:30:34.303482 Duration: 14036.149 SLS: images.docker Changed: {} ---------- ID: mgr_pushimage Function: mgrcompat.module_run Name: docker.push Result: false Comment: One or more requisite failed: images.docker.mgr_buildimage Started: 16:30:48.340228 Duration: 0.004 SLS: images.docker Changed: {} ---------- ID: mgr_registries_logout Function: mgrcompat.module_run Name: docker.logout Result: false Comment: One or more requisite failed: images.docker.mgr_pushimage Started: 16:30:48.340496 Duration: 0.004 SLS: images.docker Changed: {} ---------- ID: mgr_buildimage_docker_collect_logs Function: file.touch Name: /var/log/image-build315.log Result: true Comment: Updated times on file /var/log/image-build315.log Started: 16:30:48.343441 Duration: 7.219 SLS: images.docker Changed: touched: /var/log/image-build315.log ---------- ID: mgr_buildimage_docker_collect_logs Function: mgrcompat.module_run Name: cp.push Result: true Comment: Module function cp.push executed Started: 16:30:48.350786 Duration: 11.938 SLS: images.docker Changed: ret: true

Given I am on the Systems overview page of this "build_host" 3s 567ms

When I schedule the build of image "suse_key" via API calls 962ms

And I wait at most 660 seconds until event "Image Build suse_key scheduled" is completed 41s 611ms Show Error + 
                                            
 unknown error - Event failed (SystemCallError)
./features/step_definitions/navigation_steps.rb:107:in `block (2 levels) in (top (required))'
./features/support/commonlib.rb:106:in `block in repeat_until_timeout'
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/step_definitions/navigation_steps.rb:99:in `/^I wait at most (\d+) seconds until the event is completed, refreshing the page$/'
./features/step_definitions/common_steps.rb:157:in `/^I wait (\d+) seconds until the event is picked up and (\d+) seconds until the event "([^"]*)" is completed$/'
./features/step_definitions/common_steps.rb:174:in `/^I wait at most (\d+) seconds until event "([^"]*)" is completed$/'
features/secondary/buildhost_docker_build_image.feature:61:in `I wait at most 660 seconds until event "Image Build suse_key scheduled" is completed'

And I wait at most 900 seconds until image "suse_key" with version "latest" is built successfully via API 0s

And I wait at most 300 seconds until image "suse_key" with version "latest" is inspected successfully via API 0s

15s 401ms Show Info + 
16:30:28:000 - 16:31:14:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010003&aid=315
Screenshot +

Scenario:
Check the list of packages is not empty
16s 44ms 1 1

List of images: [{"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>1, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}]
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"failed", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>1, "arch"=>"x86_64", "enhancementErrata"=>0}

Then the list of packages of image "suse_key" with version "latest" is not empty 788ms Show Error + 
                                            
 the list of image packages is empty (ScriptError)
./features/step_definitions/docker_steps.rb:143:in `/^the list of packages of image "([^"]*)" with version "([^"]*)" is not empty$/'
features/secondary/buildhost_docker_build_image.feature:69:in `the list of packages of image "suse_key" with version "latest" is not empty'

15s 256ms Show Info + 
16:31:30:000 - 16:31:31:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010003&aid=315
Screenshot +

Scenario:
Build the suse_simple image with and without activation key
58s 819ms 3 2 1

Event Details: ---------- ID: mgr_registries_login Function: mgrcompat.module_run Name: docker.login Result: true Comment: Module function docker.login executed Started: 16:31:49.357515 Duration: 2.135 SLS: images.docker Changed: ret: retcode: 0.0 Errors: [ ] Results: { } ---------- ID: mgr_buildimage Function: mgrcompat.module_run Name: docker.build Result: false Comment: Module function docker.build threw an exception. Exception: Build failed for https://github.com/uyuni-project/uyuni.git#:testsuite/features/profiles/temporary/docker_profiles/cloud_aws/Docker. Error(s) follow: manifest for ip-172-16-1-175.eu-central-1.compute.internal/suse/sle15:15.7 not found: manifest unknown: manifest unknown Started: 16:31:49.360006 Duration: 13887.446 SLS: images.docker Changed: {} ---------- ID: mgr_pushimage Function: mgrcompat.module_run Name: docker.push Result: false Comment: One or more requisite failed: images.docker.mgr_buildimage Started: 16:32:03.247975 Duration: 0.005 SLS: images.docker Changed: {} ---------- ID: mgr_registries_logout Function: mgrcompat.module_run Name: docker.logout Result: false Comment: One or more requisite failed: images.docker.mgr_pushimage Started: 16:32:03.248262 Duration: 0.004 SLS: images.docker Changed: {} ---------- ID: mgr_buildimage_docker_collect_logs Function: file.touch Name: /var/log/image-build316.log Result: true Comment: Updated times on file /var/log/image-build316.log Started: 16:32:03.251124 Duration: 6.999 SLS: images.docker Changed: touched: /var/log/image-build316.log ---------- ID: mgr_buildimage_docker_collect_logs Function: mgrcompat.module_run Name: cp.push Result: true Comment: Module function cp.push executed Started: 16:32:03.258240 Duration: 11.478 SLS: images.docker Changed: ret: true

Given I am on the Systems overview page of this "build_host" 1s 100ms

When I schedule the build of image "suse_simple" via API calls 877ms

And I wait at most 660 seconds until event "Image Build suse_simple scheduled" is completed 41s 424ms Show Error + 
                                            
 unknown error - Event failed (SystemCallError)
./features/step_definitions/navigation_steps.rb:107:in `block (2 levels) in (top (required))'
./features/support/commonlib.rb:106:in `block in repeat_until_timeout'
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/step_definitions/navigation_steps.rb:99:in `/^I wait at most (\d+) seconds until the event is completed, refreshing the page$/'
./features/step_definitions/common_steps.rb:157:in `/^I wait (\d+) seconds until the event is picked up and (\d+) seconds until the event "([^"]*)" is completed$/'
./features/step_definitions/common_steps.rb:174:in `/^I wait at most (\d+) seconds until event "([^"]*)" is completed$/'
features/secondary/buildhost_docker_build_image.feature:74:in `I wait at most 660 seconds until event "Image Build suse_simple scheduled" is completed'

And I wait at most 900 seconds until image "suse_simple" with version "latest" is built successfully via API 0s

And I wait at most 300 seconds until image "suse_simple" with version "latest" is inspected successfully via API 0s

15s 416ms Show Info + 
16:31:46:000 - 16:32:29:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010003&aid=316
Screenshot +

Scenario:
Check the list of packages is not empty
16s 284ms 1 1

List of images: [{"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>1, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>2, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}]
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"failed", "external"=>false, "profileLabel"=>"suse_simple", "name"=>"suse_simple", "checksum"=>"", "files"=>[], "id"=>2, "arch"=>"x86_64", "enhancementErrata"=>0}

Then the list of packages of image "suse_simple" with version "latest" is not empty 929ms Show Error + 
                                            
 the list of image packages is empty (ScriptError)
./features/step_definitions/docker_steps.rb:143:in `/^the list of packages of image "([^"]*)" with version "([^"]*)" is not empty$/'
features/secondary/buildhost_docker_build_image.feature:80:in `the list of packages of image "suse_simple" with version "latest" is not empty'

15s 355ms Show Info + 
16:32:45:000 - 16:32:46:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010003&aid=316
Screenshot +

@scc_credentials
Scenario:
Build the suse_real_key image with and without activation key
2m 53s 959ms 4 3 1

Given I am on the Systems overview page of this "build_host" 1s 135ms

When I schedule the build of image "suse_real_key" via API calls 971ms

And I wait at most 660 seconds until event "Image Build suse_real_key scheduled" is completed 2m 34s 182ms

And I wait at most 60 seconds until all "3" container images are built correctly on the Image List page 1s 527ms Show Error + 
                                            
 unknown error - error detected while building images (SystemCallError)
./features/step_definitions/docker_steps.rb:90:in `block (2 levels) in (top (required))'
./features/support/commonlib.rb:106:in `block in repeat_until_timeout'
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/step_definitions/docker_steps.rb:87:in `/^I wait at most (\d+) seconds until all "([^"]*)" container images are built correctly on the Image List page$/'
features/secondary/buildhost_docker_build_image.feature:87:in `I wait at most 60 seconds until all "3" container images are built correctly on the Image List page'

And I wait at most 900 seconds until image "suse_real_key" with version "latest" is built successfully via API 0s

And I wait at most 300 seconds until image "suse_real_key" with version "latest" is inspected successfully via API 0s

When I wait until no Salt job is running on "build_host" 0s

16s 142ms Show Info + 
16:33:01:000 - 16:35:39:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

Scenario:
Check the list of packages is not empty
16s 756ms 1 1

List of images: [{"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>1, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>2, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_real_key", "checksum"=>"", "obsolete"=>false, "id"=>3, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>1}]
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>3, "arch"=>"x86_64", "enhancementErrata"=>0}

Then the list of packages of image "suse_real_key" with version "latest" is not empty 800ms Show Error + 
                                            
 the list of image packages is empty (ScriptError)
./features/step_definitions/docker_steps.rb:143:in `/^the list of packages of image "([^"]*)" with version "([^"]*)" is not empty$/'
features/secondary/buildhost_docker_build_image.feature:94:in `the list of packages of image "suse_real_key" with version "latest" is not empty'

15s 955ms Show Info + 
16:35:55:000 - 16:35:56:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

@scc_credentials
Scenario:
Build suse_key images with different versions
1m 59s 790ms 2 2 1

List of images: [{"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>1, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>2, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_real_key", "checksum"=>"", "obsolete"=>false, "id"=>3, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>1}, {"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>4, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0}]
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"failed", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}

When I schedule the build of image "suse_key" with version "Latest_key-activation1" via API calls 942ms

And I wait at most 900 seconds until image "suse_key" with version "Latest_key-activation1" is built successfully via API 1m 42s 951ms Show Error + 
                                            
 unknown error - image build failed. (SystemCallError)
./features/step_definitions/docker_steps.rb:55:in `block (2 levels) in (top (required))'
./features/support/commonlib.rb:106:in `block in repeat_until_timeout'
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/step_definitions/docker_steps.rb:41:in `/^I wait at most (\d+) seconds until image "([^"]*)" with version "([^"]*)" is built successfully via API$/'
features/secondary/buildhost_docker_build_image.feature:99:in `I wait at most 900 seconds until image "suse_key" with version "Latest_key-activation1" is built successfully via API'

And I wait at most 300 seconds until image "suse_key" with version "Latest_key-activation1" is inspected successfully via API 0s

When I wait until no Salt job is running on "build_host" 0s

15s 896ms Show Info + 
16:36:12:000 - 16:37:56:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

Scenario:
Check the list of packages is not empty
16s 658ms 1 1

List of images: [{"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>1, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>2, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_real_key", "checksum"=>"bae427e4b3e6073f458162b8e8b2698b2980f0913a250fd250ca55704e01249c", "obsolete"=>false, "id"=>3, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>1}, {"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>4, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0}]
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"failed", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}

Then the list of packages of image "suse_key" with version "Latest_key-activation1" is not empty 876ms Show Error + 
                                            
 the list of image packages is empty (ScriptError)
./features/step_definitions/docker_steps.rb:143:in `/^the list of packages of image "([^"]*)" with version "([^"]*)" is not empty$/'
features/secondary/buildhost_docker_build_image.feature:105:in `the list of packages of image "suse_key" with version "Latest_key-activation1" is not empty'

15s 782ms Show Info + 
16:38:12:000 - 16:38:12:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

Scenario:
Build suse_simple image with different versions
38s 853ms 2 2 1

List of images: [{"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>1, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>2, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_real_key", "checksum"=>"bae427e4b3e6073f458162b8e8b2698b2980f0913a250fd250ca55704e01249c", "obsolete"=>false, "id"=>3, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>1}, {"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>4, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>5, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0}]
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_simple", "name"=>"suse_simple", "checksum"=>"", "files"=>[], "id"=>5, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_simple", "name"=>"suse_simple", "checksum"=>"", "files"=>[], "id"=>5, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_simple", "name"=>"suse_simple", "checksum"=>"", "files"=>[], "id"=>5, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"failed", "external"=>false, "profileLabel"=>"suse_simple", "name"=>"suse_simple", "checksum"=>"", "files"=>[], "id"=>5, "arch"=>"x86_64", "enhancementErrata"=>0}

When I schedule the build of image "suse_simple" with version "Latest_simple" via API calls 834ms

And I wait at most 900 seconds until image "suse_simple" with version "Latest_simple" is built successfully via API 22s 56ms Show Error + 
                                            
 unknown error - image build failed. (SystemCallError)
./features/step_definitions/docker_steps.rb:55:in `block (2 levels) in (top (required))'
./features/support/commonlib.rb:106:in `block in repeat_until_timeout'
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/step_definitions/docker_steps.rb:41:in `/^I wait at most (\d+) seconds until image "([^"]*)" with version "([^"]*)" is built successfully via API$/'
features/secondary/buildhost_docker_build_image.feature:109:in `I wait at most 900 seconds until image "suse_simple" with version "Latest_simple" is built successfully via API'

And I wait at most 300 seconds until image "suse_simple" with version "Latest_simple" is inspected successfully via API 0s

When I wait until no Salt job is running on "build_host" 0s

15s 961ms Show Info + 
16:38:28:000 - 16:38:51:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

Scenario:
Check the list of packages is not empty
16s 787ms 1 1

List of images: [{"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>1, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>2, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_real_key", "checksum"=>"bae427e4b3e6073f458162b8e8b2698b2980f0913a250fd250ca55704e01249c", "obsolete"=>false, "id"=>3, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>1}, {"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>4, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>5, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0}]
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"failed", "external"=>false, "profileLabel"=>"suse_simple", "name"=>"suse_simple", "checksum"=>"", "files"=>[], "id"=>5, "arch"=>"x86_64", "enhancementErrata"=>0}

Then the list of packages of image "suse_simple" with version "Latest_simple" is not empty 805ms Show Error + 
                                            
 the list of image packages is empty (ScriptError)
./features/step_definitions/docker_steps.rb:143:in `/^the list of packages of image "([^"]*)" with version "([^"]*)" is not empty$/'
features/secondary/buildhost_docker_build_image.feature:115:in `the list of packages of image "suse_simple" with version "Latest_simple" is not empty'

15s 981ms Show Info + 
16:39:07:000 - 16:39:08:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

@scc_credentials
Scenario:
Delete image via API calls with key
3s 166ms 3

When I delete the image "suse_key" with version "Latest_key-activation1" via API calls 880ms

Then the image "suse_simple" with version "Latest_key-activation1" doesn't exist via API calls 405ms

When I wait until no Salt job is running on "build_host" 1s 880ms

Scenario:
Delete image via API calls without key
2s 670ms 3

When I delete the image "suse_simple" with version "Latest_simple" via API calls 748ms

Then the image "suse_simple" with version "Latest_simple" doesn't exist via API calls 365ms

When I wait until no Salt job is running on "build_host" 1s 557ms

Scenario:
Rebuild suse_simple image
38s 999ms 2 2 1

List of images: [{"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>1, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>2, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_real_key", "checksum"=>"bae427e4b3e6073f458162b8e8b2698b2980f0913a250fd250ca55704e01249c", "obsolete"=>false, "id"=>3, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>1}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>6, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0}]
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_simple", "name"=>"suse_simple", "checksum"=>"", "files"=>[], "id"=>6, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_simple", "name"=>"suse_simple", "checksum"=>"", "files"=>[], "id"=>6, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_simple", "name"=>"suse_simple", "checksum"=>"", "files"=>[], "id"=>6, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"failed", "external"=>false, "profileLabel"=>"suse_simple", "name"=>"suse_simple", "checksum"=>"", "files"=>[], "id"=>6, "arch"=>"x86_64", "enhancementErrata"=>0}

When I schedule the build of image "suse_simple" with version "Latest_simple" via API calls 843ms

And I wait at most 900 seconds until image "suse_simple" with version "Latest_simple" is built successfully via API 21s 910ms Show Error + 
                                            
 unknown error - image build failed. (SystemCallError)
./features/step_definitions/docker_steps.rb:55:in `block (2 levels) in (top (required))'
./features/support/commonlib.rb:106:in `block in repeat_until_timeout'
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/step_definitions/docker_steps.rb:41:in `/^I wait at most (\d+) seconds until image "([^"]*)" with version "([^"]*)" is built successfully via API$/'
features/secondary/buildhost_docker_build_image.feature:130:in `I wait at most 900 seconds until image "suse_simple" with version "Latest_simple" is built successfully via API'

And I wait at most 300 seconds until image "suse_simple" with version "Latest_simple" is inspected successfully via API 0s

When I wait until no Salt job is running on "build_host" 0s

16s 244ms Show Info + 
16:39:30:000 - 16:39:53:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

Scenario:
Check the list of packages is not empty
16s 673ms 1 1

List of images: [{"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>1, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>2, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_real_key", "checksum"=>"bae427e4b3e6073f458162b8e8b2698b2980f0913a250fd250ca55704e01249c", "obsolete"=>false, "id"=>3, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>1}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>6, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0}]
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"failed", "external"=>false, "profileLabel"=>"suse_simple", "name"=>"suse_simple", "checksum"=>"", "files"=>[], "id"=>6, "arch"=>"x86_64", "enhancementErrata"=>0}

Then the list of packages of image "suse_simple" with version "Latest_simple" is not empty 777ms Show Error + 
                                            
 the list of image packages is empty (ScriptError)
./features/step_definitions/docker_steps.rb:143:in `/^the list of packages of image "([^"]*)" with version "([^"]*)" is not empty$/'
features/secondary/buildhost_docker_build_image.feature:136:in `the list of packages of image "suse_simple" with version "Latest_simple" is not empty'

15s 896ms Show Info + 
16:40:09:000 - 16:40:10:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

@scc_credentials
Scenario:
Rebuild suse_key image
38s 687ms 2 2 1

List of images: [{"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>1, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>2, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_real_key", "checksum"=>"bae427e4b3e6073f458162b8e8b2698b2980f0913a250fd250ca55704e01249c", "obsolete"=>false, "id"=>3, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>1}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>6, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>7, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0}]
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>7, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>7, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>7, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"failed", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>7, "arch"=>"x86_64", "enhancementErrata"=>0}

When I schedule the build of image "suse_key" with version "Latest_key-activation1" via API calls 827ms

And I wait at most 900 seconds until image "suse_key" with version "Latest_key-activation1" is built successfully via API 22s 14ms Show Error + 
                                            
 unknown error - image build failed. (SystemCallError)
./features/step_definitions/docker_steps.rb:55:in `block (2 levels) in (top (required))'
./features/support/commonlib.rb:106:in `block in repeat_until_timeout'
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/step_definitions/docker_steps.rb:41:in `/^I wait at most (\d+) seconds until image "([^"]*)" with version "([^"]*)" is built successfully via API$/'
features/secondary/buildhost_docker_build_image.feature:141:in `I wait at most 900 seconds until image "suse_key" with version "Latest_key-activation1" is built successfully via API'

And I wait at most 300 seconds until image "suse_key" with version "Latest_key-activation1" is inspected successfully via API 0s

When I wait until no Salt job is running on "build_host" 0s

15s 845ms Show Info + 
16:40:26:000 - 16:40:48:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

Scenario:
Check the list of packages is not empty
16s 925ms 1 1

List of images: [{"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>1, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>2, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_real_key", "checksum"=>"bae427e4b3e6073f458162b8e8b2698b2980f0913a250fd250ca55704e01249c", "obsolete"=>false, "id"=>3, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>1}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>6, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>7, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0}]
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"failed", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>7, "arch"=>"x86_64", "enhancementErrata"=>0}

Then the list of packages of image "suse_key" with version "Latest_key-activation1" is not empty 792ms Show Error + 
                                            
 the list of image packages is empty (ScriptError)
./features/step_definitions/docker_steps.rb:143:in `/^the list of packages of image "([^"]*)" with version "([^"]*)" is not empty$/'
features/secondary/buildhost_docker_build_image.feature:147:in `the list of packages of image "suse_key" with version "Latest_key-activation1" is not empty'

16s 133ms Show Info + 
16:41:04:000 - 16:41:05:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

@scc_credentials
Scenario:
Build an image via the GUI
3m 43s 596ms 9

List of images: [{"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>1, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>2, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_real_key", "checksum"=>"bae427e4b3e6073f458162b8e8b2698b2980f0913a250fd250ca55704e01249c", "obsolete"=>false, "id"=>3, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>1}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>6, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>7, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_real_key", "checksum"=>"", "obsolete"=>false, "id"=>8, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>0}]
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>8, "arch"=>"x86_64", "enhancementErrata"=>0}
List of images: [{"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>1, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>2, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_real_key", "checksum"=>"bae427e4b3e6073f458162b8e8b2698b2980f0913a250fd250ca55704e01249c", "obsolete"=>false, "id"=>3, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>1}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>6, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>7, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_real_key", "checksum"=>"", "obsolete"=>false, "id"=>8, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>1}]
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>8, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>8, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>8, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>8, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>8, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>8, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>8, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>8, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>8, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>8, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>8, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>8, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>160, "type"=>"dockerfile", "inspectStatus"=>"completed", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"a301a4b68b76e28093b28fa0b2310861bfd056a0a6ee467884e1c65dcbe667d2", "files"=>[], "id"=>8, "arch"=>"x86_64", "enhancementErrata"=>0}

When I follow the left menu "Images > Build" 78ms

And I select "suse_real_key" from "profileId" 1s 133ms

And I enter "GUI_BUILT_IMAGE" as "version" 307ms

And I select the hostname of "build_host" from "buildHostId" 1s 121ms

And I click on "submit-btn" 62ms

And I wait until no Salt job is running on "build_host" 2m 29s 652ms

Then I wait until I see "GUI_BUILT_IMAGE" text 98ms

And I wait at most 900 seconds until image "suse_real_key" with version "GUI_BUILT_IMAGE" is built successfully via API 5s 858ms

And I wait at most 300 seconds until image "suse_real_key" with version "GUI_BUILT_IMAGE" is inspected successfully via API 1m 5s 283ms

@scc_credentials
Scenario:
Login as Docker image administrator and build an image
3m 35s 191ms 10

List of images: [{"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>1, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>2, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_real_key", "checksum"=>"bae427e4b3e6073f458162b8e8b2698b2980f0913a250fd250ca55704e01249c", "obsolete"=>false, "id"=>3, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>1}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>6, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>7, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_real_key", "checksum"=>"a301a4b68b76e28093b28fa0b2310861bfd056a0a6ee467884e1c65dcbe667d2", "obsolete"=>false, "id"=>8, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>1}, {"external"=>false, "name"=>"suse_real_key", "checksum"=>"", "obsolete"=>false, "id"=>9, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"GUI_DOCKERADMIN", "storeLabel"=>"galaxy-registry", "revision"=>0}]
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_DOCKERADMIN", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>9, "arch"=>"x86_64", "enhancementErrata"=>0}
List of images: [{"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>1, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>2, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_real_key", "checksum"=>"bae427e4b3e6073f458162b8e8b2698b2980f0913a250fd250ca55704e01249c", "obsolete"=>false, "id"=>3, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>1}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>6, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>7, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_real_key", "checksum"=>"a301a4b68b76e28093b28fa0b2310861bfd056a0a6ee467884e1c65dcbe667d2", "obsolete"=>false, "id"=>8, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>1}, {"external"=>false, "name"=>"suse_real_key", "checksum"=>"", "obsolete"=>false, "id"=>9, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"GUI_DOCKERADMIN", "storeLabel"=>"galaxy-registry", "revision"=>1}]
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_DOCKERADMIN", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>9, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_DOCKERADMIN", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>9, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_DOCKERADMIN", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>9, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_DOCKERADMIN", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>9, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_DOCKERADMIN", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>9, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_DOCKERADMIN", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>9, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_DOCKERADMIN", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>9, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_DOCKERADMIN", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>9, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_DOCKERADMIN", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>9, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_DOCKERADMIN", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>9, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_DOCKERADMIN", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>9, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_DOCKERADMIN", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>9, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_DOCKERADMIN", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>9, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>160, "type"=>"dockerfile", "inspectStatus"=>"completed", "version"=>"GUI_DOCKERADMIN", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"925e0a7c3c0ba00c59b7d6c7cea41e00109b583c02bffdf2f3a13a2ccfaf622c", "files"=>[], "id"=>9, "arch"=>"x86_64", "enhancementErrata"=>0}

Given I am authorized as "docker" with password "docker" 1s 384ms

When I follow the left menu "Images > Build" 135ms

And I select "suse_real_key" from "profileId" 1s 123ms

And I enter "GUI_DOCKERADMIN" as "version" 241ms

And I select the hostname of "build_host" from "buildHostId" 1s 113ms

And I click on "submit-btn" 53ms

And I wait until no Salt job is running on "build_host" 2m 17s 847ms

Then I wait until I see "GUI_DOCKERADMIN" text 99ms

And I wait at most 900 seconds until image "suse_real_key" with version "GUI_DOCKERADMIN" is built successfully via API 5s 404ms

And I wait at most 300 seconds until image "suse_real_key" with version "GUI_DOCKERADMIN" is inspected successfully via API 1m 7s 789ms

@scc_credentials
Scenario:
Audit images, searching for a known CVE number
882ms 5

When I follow the left menu "Audit > CVE Audit" 120ms

And I select "1999" from "cveIdentifierYear" 85ms

And I enter "9999" as "cveIdentifierId" 61ms

And I click on "Audit Images" 61ms

Then I should see a "No action required" text 554ms

Scenario:
Audit images, searching for an unknown CVE number
401ms 5

When I follow the left menu "Audit > CVE Audit" 66ms

And I select "2012" from "cveIdentifierYear" 60ms

And I enter "2806" as "cveIdentifierId" 57ms

And I click on "Audit Images" 53ms

Then I should see a "The specified CVE number was not found" text 162ms

@scc_credentials
Scenario:
Cleanup: delete all images with key
5s 410ms 6

Given I am authorized as "admin" with password "admin" 1s 133ms

When I delete the image "suse_key" with version "latest" via API calls 1s 351ms

And I delete the image "suse_key" with version "Latest_key-activation1" via API calls 729ms

And I delete the image "suse_real_key" with version "latest" via API calls 737ms

And I delete the image "suse_real_key" with version "GUI_BUILT_IMAGE" via API calls 724ms

And I delete the image "suse_real_key" with version "GUI_DOCKERADMIN" via API calls 734ms

Scenario:
Cleanup: delete images without key
2s 311ms 3

Given I am authorized as "admin" with password "admin" 411ms

When I delete the image "suse_simple" with version "latest" via API calls 1s 172ms

And I delete the image "suse_simple" with version "Latest_simple" via API calls 726ms

@scc_credentials
Scenario:
Cleanup: delete all profiles with key
807ms 7

When I follow the left menu "Images > Profiles" 129ms

And I check "suse_key" in the list 202ms

And I check "suse_real_key" in the list 60ms

And I click on "Delete" 79ms

And I should see a "Are you sure you want to delete selected profiles?" text 79ms

And I click on the red confirmation button 68ms

And I wait until I see "Image profiles have been deleted" text 187ms

Scenario:
Cleanup: delete all profiles without key
664ms 7

When I follow the left menu "Images > Profiles" 61ms

And I check "suse_simple" in the list 185ms

And I check "suse_real_simple" in the list 59ms

And I click on "Delete" 60ms

And I should see a "Are you sure you want to delete selected profiles?" text 71ms

And I click on the red confirmation button 60ms

And I wait until I see "Image profiles have been deleted" text 166ms

Scenario:
Cleanup: Make sure no job is left running on buildhost
1s 965ms 1

When I wait until no Salt job is running on "build_host" 1s 965ms

@skip_if_github_validation @build_host @scope_building_container_images @auth_registry
Feature:Build image with authenticated registry 1m 4s 549ms 6 2

Scenario:
Log in as docker user
1s 423ms 1

Given I am authorized as "docker" with password "docker" 1s 423ms

Scenario:
Create an authenticated image store as Docker admin
1s 166ms 7

AUTH_REGISTRY_CREDENTIALS: cucutest|cucusecret

When I follow the left menu "Images > Stores" 121ms

And I follow "Create" 331ms

And I enter "auth_registry" as "label" 99ms

And I check "useCredentials" 97ms

And I enter URI, username and password for registry 406ms

And I click on "create-btn" 57ms

Then I wait until I see "registry" text 52ms

@scc_credentials
Scenario:
Create a profile for the authenticated image store as Docker admin
4s 216ms 8

GITPROFILES: https://github.com/uyuni-project/uyuni.git#:testsuite/features/profiles/temporary

When I follow the left menu "Images > Profiles" 76ms

And I follow "Create" 229ms

And I enter "auth_registry_profile" as "label" 157ms

And I select "auth_registry" from "imageStore" 1s 126ms

And I select "1-SUSE-KEY-x86_64" from "activationKey" 1s 117ms

And I enter "Docker/authprofile" relative to profiles as "path" 979ms

And I click on "create-btn" 56ms

Then I wait until I see "auth_registry_profile" text 474ms

@scc_credentials
Scenario:
Build an image in the authenticated image store
38s 860ms 7 4 1

List of images: [{"external"=>false, "name"=>"auth_registry_profile", "checksum"=>"", "obsolete"=>false, "id"=>10, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"auth_registry", "revision"=>0}]
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"auth_registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"auth_registry_profile", "name"=>"auth_registry_profile", "checksum"=>"", "files"=>[], "id"=>10, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"auth_registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"auth_registry_profile", "name"=>"auth_registry_profile", "checksum"=>"", "files"=>[], "id"=>10, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"auth_registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"auth_registry_profile", "name"=>"auth_registry_profile", "checksum"=>"", "files"=>[], "id"=>10, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"auth_registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"failed", "external"=>false, "profileLabel"=>"auth_registry_profile", "name"=>"auth_registry_profile", "checksum"=>"", "files"=>[], "id"=>10, "arch"=>"x86_64", "enhancementErrata"=>0}

When I follow the left menu "Images > Build" 71ms

And I select "auth_registry_profile" from "profileId" 1s 137ms

And I enter "latest" as "version" 152ms

And I select the hostname of "build_host" from "buildHostId" 1s 122ms

And I click on "submit-btn" 62ms

Then I wait until I see "auth_registry_profile" text 71ms

When I wait at most 900 seconds until image "auth_registry_profile" with version "latest" is built successfully via API 21s 4ms Show Error + 
                                            
 unknown error - image build failed. (SystemCallError)
./features/step_definitions/docker_steps.rb:55:in `block (2 levels) in (top (required))'
./features/support/commonlib.rb:106:in `block in repeat_until_timeout'
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/step_definitions/docker_steps.rb:41:in `/^I wait at most (\d+) seconds until image "([^"]*)" with version "([^"]*)" is built successfully via API$/'
features/secondary/buildhost_docker_auth_registry.feature:45:in `I wait at most 900 seconds until image "auth_registry_profile" with version "latest" is built successfully via API'

And I wait at most 300 seconds until image "auth_registry_profile" with version "latest" is inspected successfully via API 0s

And I wait until no Salt job is running on "build_host" 0s

And I refresh the page 0s

Then table row for "auth_registry_profile" should contain "1" 0s

15s 237ms Show Info + 
16:49:16:000 - 16:49:40:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

Scenario:
Check the list of packages is not empty
15s 576ms 1 1

List of images: [{"external"=>false, "name"=>"auth_registry_profile", "checksum"=>"", "obsolete"=>false, "id"=>10, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"auth_registry", "revision"=>0}]
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"auth_registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"failed", "external"=>false, "profileLabel"=>"auth_registry_profile", "name"=>"auth_registry_profile", "checksum"=>"", "files"=>[], "id"=>10, "arch"=>"x86_64", "enhancementErrata"=>0}

And the list of packages of image "auth_registry_profile" with version "latest" is not empty 430ms Show Error + 
                                            
 the list of image packages is empty (ScriptError)
./features/step_definitions/docker_steps.rb:143:in `/^the list of packages of image "([^"]*)" with version "([^"]*)" is not empty$/'
features/secondary/buildhost_docker_auth_registry.feature:53:in `the list of packages of image "auth_registry_profile" with version "latest" is not empty'

15s 146ms Show Info + 
16:49:55:000 - 16:49:55:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

@scc_credentials
Scenario:
Cleanup: remove Docker profile for the authenticated image store
2s 413ms 6

When I follow the left menu "Images > Profiles" 79ms

And I check the row with the "auth_registry_profile" text 128ms

And I click on "Delete" 77ms

And I click on the red confirmation button 65ms

And I should see a "Image profile has been deleted." text 178ms

And I wait until no Salt job is running on "build_host" 1s 883ms

Scenario:
Cleanup: remove authenticated image store
458ms 5

When I follow the left menu "Images > Stores" 65ms

And I check the row with the "auth_registry" text 112ms

And I click on "Delete" 65ms

And I click on the red confirmation button 58ms

And I should see a "Image store has been deleted." text 157ms

Scenario:
Cleanup: delete registry image
433ms 1

When I delete the image "auth_registry_profile" with version "latest" via API calls 433ms

@scope_visualization
Feature:The system details of each minion and client provides an overview of the system 2m 34s 119ms 9

Scenario:
Log in as org admin user
1s 185ms 1

Given I am authorized 1s 185ms

@sle_minion
Scenario:
SLE minion hardware refresh
44s 559ms 6

Given I navigate to the Systems overview page of this "sle_minion" 2s 418ms

When I follow "Hardware" 559ms

And I click on "Schedule Hardware Refresh" 817ms

Then I should see a "You have successfully scheduled a hardware profile refresh" text 116ms

When I wait until event "Hardware List Refresh scheduled" is completed 38s 395ms

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "sle_minion" 2s 250ms

@sle_minion
Scenario:
Minion grains are displayed correctly on the details page
3s 891ms 19

I should see kernel version: 6.19.3-1-default
IPv4 address: 172.16.3.8
IPv6 address: fe80::424:e9ff:fee8:198b

Given I am on the Systems overview page of this "sle_minion" 1s 19ms

Then the hostname for "sle_minion" should be correct 95ms

And the kernel for "sle_minion" should be correct 504ms

And the OS version for "sle_minion" should be correct < 1ms

And the IPv4 address for "sle_minion" should be correct 83ms

And the IPv6 address for "sle_minion" should be correct 443ms

And the system ID for "sle_minion" should be correct 444ms

And the system name for "sle_minion" should be correct 81ms

And the uptime for "sle_minion" should be correct 421ms

And I should see a "UUID" text 78ms

And I should see a "Virtualization" text 77ms

And I should see a "Installed Products" text 91ms

And I should see a "Checked In" text 78ms

And I should see a "Registered" text 78ms

And I should see a "Contact Method" text 77ms

And I should see a "Auto Patch Update" text 80ms

And I should see a "Maintenance Schedule" text 79ms

And I should see a "Description" text 78ms

And I should see a "Location" text 78ms

@rhlike_minion
Scenario:
Red Hat-like minion hardware refresh
26s 91ms 6

Given I am on the Systems overview page of this "rhlike_minion" 995ms

When I follow "Hardware" 569ms

And I click on "Schedule Hardware Refresh" 837ms

Then I should see a "You have successfully scheduled a hardware profile refresh" text 115ms

When I wait until event "Hardware List Refresh scheduled" is completed 21s 950ms

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "rhlike_minion" 1s 622ms

@rhlike_minion
Scenario:
Red Hat-like minion grains are displayed correctly on the details page
3s 155ms 19

I should see kernel version: 4.18.0-553.el8_10.x86_64
IPv4 address: 172.16.3.10
IPv6 address: fe80::477:a4ff:feca:b21d

Given I am on the Systems overview page of this "rhlike_minion" 975ms

Then the hostname for "rhlike_minion" should be correct 89ms

And the kernel for "rhlike_minion" should be correct 263ms

And the OS version for "rhlike_minion" should be correct < 1ms

And the IPv4 address for "rhlike_minion" should be correct 81ms

And the IPv6 address for "rhlike_minion" should be correct 196ms

And the system ID for "rhlike_minion" should be correct 472ms

And the system name for "rhlike_minion" should be correct 83ms

And the uptime for "rhlike_minion" should be correct 195ms

And I should see a "UUID" text 77ms

And I should see a "Virtualization" text 85ms

And I should see a "Installed Products" text 77ms

And I should see a "Checked In" text 81ms

And I should see a "Registered" text 77ms

And I should see a "Contact Method" text 77ms

And I should see a "Auto Patch Update" text 78ms

And I should see a "Maintenance Schedule" text 78ms

And I should see a "Description" text 81ms

And I should see a "Location" text 80ms

@deblike_minion
Scenario:
Debian-like minion hardware refresh
26s 563ms 6

Given I am on the Systems overview page of this "deblike_minion" 1s 17ms

When I follow "Hardware" 647ms

And I click on "Schedule Hardware Refresh" 787ms

Then I should see a "You have successfully scheduled a hardware profile refresh" text 116ms

When I wait until event "Hardware List Refresh scheduled" is completed 21s 826ms

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "deblike_minion" 2s 168ms

@deblike_minion
Scenario:
Debian-like minion grains are displayed correctly on the details page
3s 161ms 19

I should see kernel version: 6.17.0-1007-aws
IPv4 address: 172.16.3.11
IPv6 address: fe80::499:e5ff:fe69:af7b

Given I am on the Systems overview page of this "deblike_minion" 984ms

Then the hostname for "deblike_minion" should be correct 83ms

And the kernel for "deblike_minion" should be correct 276ms

And the OS version for "deblike_minion" should be correct < 1ms

And the IPv4 address for "deblike_minion" should be correct 82ms

And the IPv6 address for "deblike_minion" should be correct 211ms

And the system ID for "deblike_minion" should be correct 450ms

And the system name for "deblike_minion" should be correct 78ms

And the uptime for "deblike_minion" should be correct 211ms

And I should see a "UUID" text 76ms

And I should see a "Virtualization" text 75ms

And I should see a "Installed Products" text 75ms

And I should see a "Checked In" text 82ms

And I should see a "Registered" text 89ms

And I should see a "Contact Method" text 75ms

And I should see a "Auto Patch Update" text 75ms

And I should see a "Maintenance Schedule" text 75ms

And I should see a "Description" text 79ms

And I should see a "Location" text 75ms

@ssh_minion
Scenario:
SSH-managed minion hardware refresh
41s 238ms 5

Given I am on the Systems overview page of this "ssh_minion" 1s 49ms

When I follow "Hardware" 566ms

And I click on "Schedule Hardware Refresh" 983ms

Then I should see a "You have successfully scheduled a hardware profile refresh" text 122ms

And I wait until event "Hardware List Refresh scheduled" is completed 38s 516ms

@ssh_minion
Scenario:
SSH-managed minion grains are displayed correctly on the details page
4s 272ms 19

I should see kernel version: 6.19.3-1-default
IPv4 address: 172.16.3.9
IPv6 address: fe80::43d:3cff:fe53:92d9

Given I am on the Systems overview page of this "ssh_minion" 1s 34ms

Then the hostname for "ssh_minion" should be correct 92ms

And the kernel for "ssh_minion" should be correct 807ms

And the OS version for "ssh_minion" should be correct < 1ms

And the IPv4 address for "ssh_minion" should be correct 97ms

And the IPv6 address for "ssh_minion" should be correct 415ms

And the system ID for "ssh_minion" should be correct 495ms

And the system name for "ssh_minion" should be correct 85ms

And the uptime for "ssh_minion" should be correct 418ms

And I should see a "UUID" text 78ms

And I should see a "Virtualization" text 79ms

And I should see a "Installed Products" text 79ms

And I should see a "Checked In" text 83ms

And I should see a "Registered" text 83ms

And I should see a "Contact Method" text 83ms

And I should see a "Auto Patch Update" text 82ms

And I should see a "Maintenance Schedule" text 84ms

And I should see a "Description" text 78ms

And I should see a "Location" text 91ms

@scope_ssm @sle_minion @scope_visualization @new_issue @flaky
Feature:Manage a group of systems and the Systems Set Manager 9m 15s 992ms 20 2 2

Scenario:
Log in as org admin user
1s 561ms 1

Given I am authorized for the "Admin" section 1s 561ms

@skip_if_github_validation
Scenario:
Pre-requisite: install dummy packages to allow patching
5s 251ms 4

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 777ms

And I refresh the metadata for "sle_minion" 862ms

And I install old package "andromeda-dummy-1.0" on this "sle_minion" 1s 843ms

And I install old package "virgo-dummy-1.0" on this "sle_minion" 1s 767ms

Scenario:
Pre-requisite: ensure that fake patches are available
1m 41s 412ms 6

When I follow the left menu "Admin > Task Schedules" 144ms

And I follow "errata-cache-default" 1s 202ms

And I follow "errata-cache-bunch" 1s 282ms

And I click on "Single Run Schedule" 1s 535ms

Then I should see a "bunch was scheduled" text 259ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 1m 36s 987ms

Scenario:
Pre-requisite: ensure that fake channels were created
607ms 7

When I follow the left menu "Patches > Patch List > Relevant" 236ms

Then I should see an update in the list 35ms

When I wait until I see "andromeda-dummy" text, refreshing the page 132ms

Then I should see a "andromeda-dummy-6789" link 11ms

When I enter "virgo-dummy" as the filtered synopsis 54ms

And I click on the filter button until page does contain "virgo-dummy-3456" text 125ms

Then I should see a "virgo-dummy-3456" link 11ms

Scenario:
Fail to create a group with only its name
859ms 5

When I follow the left menu "Systems > System Groups" 122ms

And I follow "Create Group" 282ms

And I enter "new-systems-group" as "name" 69ms

And I click on "Create Group" 60ms

Then I should see a "Both name and description are required for System Groups." text 323ms

Scenario:
Fail to create a group with only its description
521ms 5

When I follow the left menu "Systems > System Groups" 68ms

And I follow "Create Group" 282ms

And I enter "My new group" as "description" 57ms

And I click on "Create Group" 51ms

Then I should see a "Both name and description are required for System Groups." text 61ms

Scenario:
Create a group
569ms 6

When I follow the left menu "Systems > System Groups" 62ms

And I follow "Create Group" 271ms

And I enter "new-systems-group" as "name" 58ms

And I enter "My new group" as "description" 54ms

And I click on "Create Group" 53ms

Then I should see a "System group new-systems-group created." text 68ms

Scenario:
Add the SLE minion to the group and to SSM
2s 576ms 7

When I follow the left menu "Systems > System Groups" 63ms

And I follow "new-systems-group" 306ms

And I follow "Target Systems" 481ms

And I check the "sle_minion" client 62ms

And I click on "Add Systems" 1s 70ms

Then I should see a "1 systems were added to new-systems-group server group." text 93ms

When I click on "Add Selected to SSM" 499ms

Scenario:
The SLE minion is part of the new group
1s 145ms 3

Given I am on the Systems overview page of this "sle_minion" 1s

When I follow "Groups" in the content area 74ms

Then I should see a "new-systems-group" text 69ms

Scenario:
Apply a patch to systems in the system group
42s 281ms 14

When I follow the left menu "Systems > System Groups" 57ms

And I follow "new-systems-group" 252ms

And I follow first "Patches" 325ms

When I enter "virgo-dummy" as the filtered synopsis 46ms

And I click on the filter button until page does contain "virgo-dummy-3456" text 132ms

Then I should see a "virgo-dummy-3456" link 8ms

When I follow "virgo-dummy-3456" 360ms

And I follow first "Affected Systems" 298ms

And I check the "sle_minion" client 53ms

And I click on "Apply Patches" 554ms

And I click on "Confirm" 602ms

Then I should see a "Patch virgo-dummy-3456 has been scheduled for 1 system" text 144ms

And I am on the Systems overview page of this "sle_minion" 1s 98ms

And I wait until event "Patch Update: virgo-dummy-3456 - Test update for virgo-dummy scheduled by admin" is completed 38s 345ms

Scenario:
Apply a patch to systems in the SSM
42s 420ms 14

When I follow the left menu "Systems > System Set Manager > Overview" 471ms

And I follow first "Patches" 302ms

When I enter "andromeda-dummy" as the filtered synopsis 63ms

And I click on the filter button 342ms

When I wait until I see "andromeda-dummy-6789" text, refreshing the page 65ms

Then I should see a "andromeda-dummy-6789" link 11ms

When I follow "andromeda-dummy-6789" 390ms

And I follow first "Affected Systems" 308ms

And I check the "sle_minion" client 66ms

And I click on "Apply Patches" 435ms

And I click on "Confirm" 602ms

Then I should see a "Patch andromeda-dummy-6789 has been scheduled for 1 system" text 143ms

And I am on the Systems overview page of this "sle_minion" 1s 24ms

And I wait until event "Patch Update: andromeda-dummy-6789 - Test update for andromeda-dummy scheduled by admin" is completed 38s 193ms

@skip_if_github_validation
Scenario:
Delete a package from systems in the SSM
26s 219ms 5 5 1

When I follow the left menu "Systems > System Set Manager > Overview" 463ms

And I follow "Packages" 334ms

And I follow "Remove" 369ms

And I wait until I see "Package Removal" text, refreshing the page 62ms

And I enter "virgo-dummy" as the filtered package name 10s 4ms Show Error + 
                                            
 Unable to find css "input[placeholder='Filter by Package Name: ']" (Capybara::ElementNotFound)
./features/support/navigation_step_helper.rb:45:in `filter_by_package_name'
./features/step_definitions/navigation_steps.rb:944:in `/^I enter "([^"]*)" as the filtered package name$/'
features/secondary/allcli_system_group.feature:113:in `I enter "virgo-dummy" as the filtered package name'

And I click on the filter button until page does contain "virgo-dummy-2.0-1.1" text 0s

And I check "virgo-dummy-2.0-1.1" in the list 0s

And I click on "Remove Packages" 0s

And I click on "Confirm" 0s

Then I should see a "Package removals are being scheduled, it may take several minutes for this to complete." text 0s

14s 984ms Show Info + 
16:56:37:000 - 16:56:49:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/ssm/PackageRemove.do
Screenshot +

@skip_if_github_validation
Scenario:
Install a package to systems in the SSM
4m 28s 835ms 4 9 1

When I follow the left menu "Systems > System Set Manager > Overview" 72ms

And I follow "Packages" 344ms

And I follow "Install" 350ms

And I wait until I see "Fake-RPM-SUSE-Channel" text, refreshing the page 4m 13s 87ms Show Error + 
                                            
 execution expired (Timeout::Error)
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/step_definitions/navigation_steps.rb:70:in `/^I wait until I see "([^"]*)" (text|regex), refreshing the page$/'
features/secondary/allcli_system_group.feature:126:in `I wait until I see "Fake-RPM-SUSE-Channel" text, refreshing the page'

Then I should see a "Fake-RPM-SUSE-Channel" text 0s

When I follow "Fake-RPM-SUSE-Channel" 0s

Then I should see a "virgo-dummy-2.0-1.1" text 0s

And I enter "virgo-dummy" as the filtered package name 0s

And I click on the filter button until page does contain "virgo-dummy-2.0-1.1" text 0s

When I check "virgo-dummy-2.0-1.1" in the list 0s

And I click on "Install Packages" 0s

And I click on "Confirm" 0s

Then I should see a "Package installations are being scheduled, it may take several minutes for this to complete." text 0s

14s 980ms Show Info + 
16:57:04:000 - 17:01:18:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/ssm/PackageInstall.do
Screenshot +

@rhlike_minion
Scenario:
Add the Red Hat-like minion to the group in a different way
2s 474ms 8

When I follow the left menu "Systems > System Groups" 78ms

Then I should see a "System Groups" text 66ms

When I follow "new-systems-group" 304ms

And I follow "Target Systems" 556ms

Then I should see a "The following are systems that may be added to this group." text 98ms

When I check the "rhlike_minion" client 61ms

And I click on "Add Systems" 1s 217ms

Then I should see a "1 systems were added to new-systems-group server group" text 91ms

Scenario:
Add the new group to SSM
236ms 5

When I follow the left menu "Systems > System Groups" 60ms

And I click on "Use in SSM" in row "new-systems-group" 71ms

Then I should see a "Selected Systems List" text 76ms

And I should see "rhlike_minion" as link 14ms

And I should see "sle_minion" as link 13ms

@skip_if_containerized_server
Scenario:
Install the locale formula package on the server
< 1ms 1

When I manually install the "locale" formula on the server 0s

Scenario:
I synchronize all Salt dynamic modules on "sle_minion"
2s 549ms 1

When I synchronize all Salt dynamic modules on "sle_minion" 2s 549ms

Scenario:
New formula page is rendered for the system group
11s 36ms 6

When I follow the left menu "Systems > System Groups" 58ms

And I follow "new-systems-group" 300ms

And I follow "Formulas" 388ms

Then I should see a "Choose formulas:" text 59ms

And I should see a "General System Configuration" text 186ms

And the "locale" formula should be unchecked 10s 43ms

@rhlike_minion
Scenario:
Apply the highstate to the group
31s 456ms 10

When I follow the left menu "Systems > System Groups" 57ms

Then I should see a "System Groups" text 67ms

When I follow "new-systems-group" 297ms

And I follow "States" 408ms

And I click on "Apply Highstate" 78ms

Then I should see a "Applying the highstate has been scheduled." text 311ms

When I follow "scheduled" 279ms

Then I should see a "Apply states (highstate)" text 54ms

And I should see a "Action Details" text 51ms

And I wait until I see "2 systems successfully completed this action." text, refreshing the page 29s 851ms

Scenario:
Remove SLE minion from new group
2s 473ms 5

Given I am on the Systems overview page of this "sle_minion" 1s 10ms

When I follow "Groups" 392ms

And I check "new-systems-group" in the list 64ms

And I click on "Leave Groups" 942ms

Then I should see a "1 system groups removed." text 63ms

@skip_if_containerized_server
Scenario:
Cleanup: uninstall formula from the server
< 1ms 1

When I manually uninstall the "locale" formula from the server 0s

Scenario:
Cleanup: remove the new group
1s 430ms 7

When I follow the left menu "Systems > System Groups" 73ms

When I follow "new-systems-group" in the content area 70ms

And I follow "Delete Group" in the content area 69ms

And I click on "Confirm Deletion" 1s 34ms

Then I should see a "System group" text 63ms

And I should see a "new-systems-group" text 61ms

And I should see a "deleted" text 57ms

Scenario:
Cleanup: regenerate search index for later tests
5s 49ms 1

Search by hostname: uyuni-master-suse-minion
[{"last_boot"=>"2026-03-06T13:36:49Z", "name"=>"uyuni-master-suse-minion.sumaci.aws", "id"=>1000010023, "last_checkin"=>"2026-03-06T16:02:26Z"}]

When I clean the search index on the server 5s 49ms

Scenario:
Cleanup: remove dummy packages
5s 24ms 4

When I disable repository "test_repo_rpm_pool" on this "sle_minion" without error control 790ms

And I refresh the metadata for "sle_minion" 903ms

And I remove package "andromeda-dummy" from this "sle_minion" without error control 1s 590ms

And I remove package "virgo-dummy" from this "sle_minion" without error control 1s 739ms

@scope_configuration_channels
Feature:Management of configuration of all types of clients in a single channel 6m 16s 675ms 27 1

Scenario:
Log in as org admin user
2s 34ms 1

Given I am authorized 2s 34ms

Scenario:
Create a configuration channel for mixed client types
1s 478ms 7

When I follow the left menu "Configuration > Channels" 123ms

And I follow "Create Config Channel" 310ms

And I enter "Mixed Channel" as "cofName" 64ms

And I enter "mixedchannel" as "cofLabel" 57ms

And I enter "This is a configuration channel for different system types" as "cofDescription" 95ms

And I click on "Create Config Channel" 764ms

Then I should see a "Mixed Channel" text 62ms

Scenario:
Add a configuration file to the mixed configuration channel
3s 881ms 9

When I follow the left menu "Configuration > Channels" 63ms

And I follow "Mixed Channel" 525ms

And I follow "Create Configuration File or Directory" 380ms

And I enter "/etc/s-mgr/config" as "cffPath" 68ms

And I enter "COLOR=white" in the editor 5ms

And I click on "Create Configuration File" 67ms

Then I should see a "Revision 1 of /etc/s-mgr/config from channel Mixed Channel" text 778ms

And file "/srv/susemanager/salt/manager_org_1/mixedchannel/init.sls" should exist on server 1s 256ms

And file "/srv/susemanager/salt/manager_org_1/mixedchannel/etc/s-mgr/config" should exist on server 734ms

@sle_minion
Scenario:
Subscribe a Salt minion to the configuration channel
3s 374ms 8

When I am on the Systems overview page of this "sle_minion" 1s 269ms

And I follow "Configuration" in the content area 69ms

And I follow "Manage Configuration Channels" in the content area 67ms

And I follow first "Subscribe to Channels" in the content area 69ms

And I check "Mixed Channel" in the list 60ms

And I click on "Continue" 793ms

And I click on "Update Channel Rankings" 973ms

Then I should see a "Channel Subscriptions successfully changed for" text 71ms

@rhlike_minion
Scenario:
Subscribe a Red Hat-like minion to the configuration channel
2s 737ms 8

When I am on the Systems overview page of this "rhlike_minion" 1s 405ms

And I follow "Configuration" in the content area 61ms

And I follow "Manage Configuration Channels" in the content area 75ms

And I follow first "Subscribe to Channels" in the content area 62ms

And I check "Mixed Channel" in the list 56ms

And I click on "Continue" 50ms

And I click on "Update Channel Rankings" 953ms

Then I should see a "Channel Subscriptions successfully changed for" text 71ms

@deblike_minion
Scenario:
Subscribe a Debian-like minion to the configuration channel
3s 199ms 8

When I am on the Systems overview page of this "deblike_minion" 1s 256ms

And I follow "Configuration" in the content area 68ms

And I follow "Manage Configuration Channels" in the content area 64ms

And I follow first "Subscribe to Channels" in the content area 59ms

And I check "Mixed Channel" in the list 51ms

And I click on "Continue" 735ms

And I click on "Update Channel Rankings" 893ms

Then I should see a "Channel Subscriptions successfully changed for" text 71ms

@ssh_minion
Scenario:
Subscribe a SSH minion to the configuration channel
2s 678ms 8

When I am on the Systems overview page of this "ssh_minion" 1s 412ms

And I follow "Configuration" in the content area 60ms

And I follow "Manage Configuration Channels" in the content area 56ms

And I follow first "Subscribe to Channels" in the content area 58ms

And I check "Mixed Channel" in the list 50ms

And I click on "Continue" 54ms

And I click on "Update Channel Rankings" 915ms

Then I should see a "Channel Subscriptions successfully changed for" text 70ms

Scenario:
Deploy the file to all systems
2s 345ms 7

When I follow the left menu "Configuration > Channels" 115ms

And I follow "Mixed Channel" 607ms

And I follow "Deploy all configuration files to all subscribed systems" 536ms

Then I should see a "/etc/s-mgr/config" link 12ms

When I click on "Deploy Files to Selected Systems" 940ms

Then I should see a "revision-deploys are being scheduled," text 67ms

And I should see a "0 revision-deploys overridden." text 65ms

@sle_minion
Scenario:
Check that file has been created on SLE minion
3s 104ms 2

When I wait until file "/etc/s-mgr/config" exists on "sle_minion" 2s 275ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "sle_minion" 828ms

@rhlike_minion
Scenario:
Check that file has been created on Red Hat-like minion
712ms 2

When I wait until file "/etc/s-mgr/config" exists on "rhlike_minion" 313ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "rhlike_minion" 398ms

@deblike_minion
Scenario:
Check that file has been created on Debian-like minion
1s 274ms 2

When I wait until file "/etc/s-mgr/config" exists on "deblike_minion" 891ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "deblike_minion" 383ms

@ssh_minion
Scenario:
Check that file has been created on SSH minion
5s 787ms 2

When I wait until file "/etc/s-mgr/config" exists on "ssh_minion" 4s 965ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "ssh_minion" 822ms

@sle_minion
Scenario:
Apply highstate to override changed content on SLE minion
14s 938ms 3

Salt command: salt uyuni-master-suse-minion.sumaci.aws state.highstate

When I store "COLOR=blue" into file "/etc/s-mgr/config" on "sle_minion" 425ms

And I apply highstate on "sle_minion" 13s 312ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "sle_minion" 1s 200ms

@rhlike_minion
Scenario:
Apply highstate to override changed content on Red Hat-like minion
4m 25s 711ms 2 1 1

Salt command: salt uyuni-master-rhlike-minion state.highstate

When I store "COLOR=blue" into file "/etc/s-mgr/config" on "rhlike_minion" 301ms

And I apply highstate on "rhlike_minion" 4m 10s Show Error + 
                                            
 execution expired (Timeout::Error)
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/support/remote_node.rb:186:in `run_until_ok'
./features/step_definitions/salt_steps.rb:650:in `/^I apply highstate on "([^"]*)"$/'
features/secondary/allcli_config_channel.feature:112:in `I apply highstate on "rhlike_minion"'

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "rhlike_minion" 0s

15s 409ms Show Info + 
17:03:52:000 - 17:08:02:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/configuration/ChannelOverview.do?ccid=7
Screenshot +

@deblike_minion
Scenario:
Apply highstate to override changed content on Debian-like minion
7s 361ms 3

Salt command: salt uyuni-master-deblike-minion state.highstate

When I store "COLOR=blue" into file "/etc/s-mgr/config" on "deblike_minion" 854ms

And I apply highstate on "deblike_minion" 6s 119ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "deblike_minion" 387ms

@ssh_minion
Scenario:
Apply highstate to override changed content on SSH minion
29s 978ms 3

Salt command: mgr-salt-ssh uyuni-master-suse-sshminion.sumaci.aws state.highstate

When I store "COLOR=blue" into file "/etc/s-mgr/config" on "ssh_minion" 762ms

And I apply highstate on "ssh_minion" 28s 400ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "ssh_minion" 815ms

@rhlike_minion
Scenario:
Unsubscribe Red Hat-like minion and delete configuration files
1s 677ms 7

When I follow the left menu "Configuration > Channels" 79ms

And I follow "Mixed Channel" 494ms

And I follow "Systems" in the content area 66ms

And I check the "rhlike_minion" client 60ms

And I click on "Unsubscribe systems" 606ms

Then I should see a "Successfully unsubscribed 1 system(s)." text 75ms

And I destroy "/etc/s-mgr" directory on "rhlike_minion" 294ms

@deblike_minion
Scenario:
Unsubscribe Debian-like minion and delete configuration files
1s 176ms 7

When I follow the left menu "Configuration > Channels" 63ms

And I follow "Mixed Channel" 465ms

And I follow "Systems" in the content area 57ms

And I check the "deblike_minion" client 56ms

And I click on "Unsubscribe systems" 48ms

Then I should see a "Successfully unsubscribed 1 system(s)." text 69ms

And I destroy "/etc/s-mgr" directory on "deblike_minion" 415ms

@ssh_minion
Scenario:
Unsubscribe SSH minion and delete configuration files
1s 771ms 7

When I follow the left menu "Configuration > Channels" 63ms

And I follow "Mixed Channel" 479ms

And I follow "Systems" in the content area 56ms

And I check the "ssh_minion" client 54ms

And I click on "Unsubscribe systems" 559ms

Then I should see a "Successfully unsubscribed 1 system(s)." text 65ms

And I destroy "/etc/s-mgr" directory on "ssh_minion" 492ms

@sle_minion
Scenario:
Change file on Salt minion and compare
6s 435ms 13

When I am on the Systems overview page of this "sle_minion" 1s

And I store "COLOR=red" into file "/etc/s-mgr/config" on "sle_minion" 747ms

And I follow "Configuration" in the content area 69ms

And I follow "Compare Files" in the content area 64ms

And I check "/etc/s-mgr/config" in the list 57ms

And I click on "Compare Files" 650ms

And I click on "Schedule Compare" 840ms

Then I should see a "1 files scheduled for comparison." text 68ms

When I wait until event "Show differences between profiled config files and deployed config files scheduled" is completed 2s 365ms

Then I should see a "Differences exist" link 11ms

When I follow "Differences exist" 437ms

Then I should see a "+COLOR=white" text 59ms

And I should see a "-COLOR=red" text 61ms

@sle_minion
Scenario:
Check configuration channel and files via API for Salt minion
1s 142ms 3

Then channel "mixedchannel" should exist 389ms

And channel "mixedchannel" should contain file "/etc/s-mgr/config" 382ms

And "sle_minion" should be subscribed to channel "mixedchannel" 371ms

@sle_minion
Scenario:
Extend configuration channel and deploy files via API for Salt minion
4s 910ms 6

When I store "COLOR=green" into file "/etc/s-mgr/config" on "sle_minion" 402ms

And I add file "/etc/s-mgr/other" containing "NAME=Dante" to channel "mixedchannel" 472ms

And I deploy all systems registered to channel "mixedchannel" 456ms

And I wait until file "/etc/s-mgr/other" exists on "sle_minion" 1s 916ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "sle_minion" 826ms

And file "/etc/s-mgr/other" should contain "NAME=Dante" on "sle_minion" 836ms

@sle_minion
Scenario:
Unsubscribe systems via API for Salt minion
1s 145ms 2

When I unsubscribe "sle_minion" from configuration channel "mixedchannel" 780ms

Then "sle_minion" should not be subscribed to channel "mixedchannel" 364ms

@sle_minion
Scenario:
Re-add SLE Minion via SSM
3s 275ms 10

When I follow the left menu "Systems > System List > All" 132ms

And I click on the clear SSM button 71ms

And I check the "sle_minion" client 427ms

And I follow the left menu "Systems > System Set Manager > Overview" 477ms

And I follow "config channel subscriptions" in the content area 65ms

And I check "Mixed Channel" in the list 69ms

And I click on "Continue" 574ms

And I click on "Apply Subscriptions" 779ms

And I click on "Confirm" 614ms

Then I should see a "Configuration channel subscriptions changed for 1 system successfully." text 62ms

@sle_minion
Scenario:
Cleanup: remove remaining Salt minion from configuration channel
1s 392ms 6

When I follow the left menu "Configuration > Channels" 127ms

And I follow "Mixed Channel" 551ms

And I follow "Systems" in the content area 64ms

And I check the "sle_minion" client 53ms

And I click on "Unsubscribe systems" 542ms

Then I should see a "Successfully unsubscribed 1 system(s)." text 53ms

Scenario:
Cleanup: remove the mixed configuration channel
2s 338ms 5

When I follow the left menu "Configuration > Channels" 63ms

And I follow "Mixed Channel" 462ms

And I follow "Delete Channel" 279ms

And I click on "Delete Config Channel" 476ms

Then file "/srv/susemanager/salt/manager_org_1/mixedchannel/init.sls" should not exist on server 1s 56ms

@sle_minion
Scenario:
Cleanup: delete configuration files on remaining Salt minion
756ms 1

When I destroy "/etc/s-mgr" directory on "sle_minion" 756ms

Scenario:
Cleanup: remove remaining systems from SSM after tests of configuration channel on all clients
54ms 1

When I click on the clear SSM button 54ms

@scope_changing_software_channels @scc_credentials
Feature:Channel subscription via SSM 5m 20s 344ms 14 5

Scenario:
Log in as org admin user
1s 784ms 1

Given I am authorized 1s 784ms

@sle_minion @susemanager
Scenario:
Change child channels for SLES minion subscribed to a base channel
< 1ms 22

When I follow the left menu "Systems > System List > All" 0s

And I click on the clear SSM button 0s

And I check the "sle_minion" client 0s

And I should see "1" systems selected for SSM 0s

And I follow the left menu "Systems > System Set Manager > Overview" 0s

And I follow "channel memberships" in the content area 0s

Then I should see a "Base Channel" text 0s

And I should see a "Next" text 0s

When I select "Fake-Base-Channel-SUSE-like" from drop-down in table line with "SLE-Product-SLES15-SP7-Pool for x86_64" 0s

And I click on "Next" 0s

Then I should see a "Child Channels" text 0s

And I should see a "Fake-Base-Channel-SUSE-like" text 0s

And I should see a "1 system(s) to subscribe" text 0s

When I choose radio button "Subscribe" for child channel "Fake-Child-Channel-SUSE-like" 0s

And I click on "Next" 0s

Then I should see a "Channel Changes Overview" text 0s

And I should see a "1 system(s) to subscribe" text 0s

When I schedule action to 3 minutes from now 0s

And I click on "Confirm" 0s

And I remember when I scheduled an action 0s

Then I wait until I see "Channel Changes Actions" text 0s

And a table line should contain system "sle_minion", "Scheduled" 0s

@sle_minion @uyuni
Scenario:
Change child channels for openSUSE minion subscribed to a base channel
3s 22ms 22

When I follow the left menu "Systems > System List > All" 172ms

And I click on the clear SSM button 54ms

And I check the "sle_minion" client 432ms

And I should see "1" systems selected for SSM 153ms

And I follow the left menu "Systems > System Set Manager > Overview" 452ms

And I follow "channel memberships" in the content area 68ms

Then I should see a "Base Channel" text 69ms

And I should see a "Next" text 65ms

When I select "Fake-Base-Channel-SUSE-like" from drop-down in table line with "openSUSE Tumbleweed (x86_64)" 110ms

And I click on "Next" 62ms

Then I should see a "Child Channels" text 314ms

And I should see a "Fake-Base-Channel-SUSE-like" text 66ms

And I should see a "1 system(s) to subscribe" text 63ms

When I choose radio button "Subscribe" for child channel "Fake-Child-Channel-SUSE-like" 67ms

And I click on "Next" 61ms

Then I should see a "Channel Changes Overview" text 60ms

And I should see a "1 system(s) to subscribe" text 62ms

When I schedule action to 3 minutes from now 227ms

And I click on "Confirm" 54ms

And I remember when I scheduled an action < 1ms

Then I wait until I see "Channel Changes Actions" text 382ms

And a table line should contain system "sle_minion", "Scheduled" 20ms

@sle_minion @susemanager
Scenario:
Check SLES minion is still subscribed to old channels before channel change completes
< 1ms 7

Given I am on the Systems overview page of this "sle_minion" 0s

When I follow "Software" in the content area 0s

And I follow "Software Channels" in the content area 0s

And I wait until I do not see "Loading..." text 0s

Then radio button "SLE-Product-SLES15-SP7-Pool for x86_64" should be checked 0s

And I wait until I do not see "Loading..." text 0s

And I should see "SLE15-SP7-Installer-Updates for x86_64" as unchecked 0s

@sle_minion @uyuni
Scenario:
Check openSUSE minion is still subscribed to old channels before channel change completes
1s 925ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 12ms

When I follow "Software" in the content area 70ms

And I follow "Software Channels" in the content area 82ms

And I wait until I do not see "Loading..." text 72ms

Then radio button "openSUSE Tumbleweed (x86_64)" should be checked 171ms

And I wait until I do not see "Loading..." text 496ms

And I should see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" as unchecked 18ms

@sle_minion @susemanager
Scenario:
Check via API old channels are still the same on SLES minion before channel change completes
< 1ms 3

When I refresh the metadata for "sle_minion" 0s

Then channel "SLE-Product-SLES15-SP7-Pool for x86_64" should be enabled on "sle_minion" 0s

And channel "SLE15-SP7-Installer-Updates for x86_64" should be disabled on "sle_minion" 0s

@sle_minion @uyuni
Scenario:
Check via API old channels are still the same on openSUSE minion before channel change completes
2s 772ms 3

When I refresh the metadata for "sle_minion" 1s 286ms

Then channel "openSUSE Tumbleweed (x86_64)" should be enabled on "sle_minion" 755ms

And channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" should be disabled on "sle_minion" 730ms

Scenario:
Wait 3 minutes for the scheduled action to be executed
3m 1

When I wait for "180" seconds 3m

@sle_minion
Scenario:
Check channel change has completed for the SLES minion
1m 13s 877ms 3

Given I am on the Systems overview page of this "sle_minion" 1s 38ms

When I wait until event "Subscribe channels scheduled" is completed 1m 12s 775ms

Then I should see a "The client completed this action on" text 63ms

@sle_minion
Scenario:
Check the SLES minion is subscribed to the new channels
1s 909ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 41ms

When I follow "Software" in the content area 76ms

And I follow "Software Channels" in the content area 66ms

And I wait until I do not see "Loading..." text 64ms

Then radio button "Fake-Base-Channel-SUSE-like" should be checked 159ms

And I wait until I do not see "Loading..." text 483ms

And I should see "Fake-Child-Channel-SUSE-like" as checked 17ms

@sle_minion @susemanager
Scenario:
Check via API the new channels are enabled on the SLES minion
< 1ms 4

When I refresh the metadata for "sle_minion" 0s

Then "2" channels should be enabled on "sle_minion" 0s

And channel "Fake-Base-Channel-SUSE-like" should be enabled on "sle_minion" 0s

And channel "Fake-Child-Channel-SUSE-like" should be enabled on "sle_minion" 0s

@uyuni
Scenario:
Check via API the new channels are enabled on the openSUSE minion
3s 749ms 4

When I refresh the metadata for "sle_minion" 1s 588ms

Then "2" channels should be enabled on "sle_minion" 725ms

And channel "Fake-Base-Channel-SUSE-like" should be enabled on "sle_minion" 716ms

And channel "Fake-Child-Channel-SUSE-like" should be enabled on "sle_minion" 719ms

@rhlike_minion
Scenario:
System default channel can't be determined on the Red Hat-like minion
2s 719ms 20

When I follow the left menu "Systems > System List > All" 151ms

And I click on the clear SSM button 67ms

And I check the "rhlike_minion" client 410ms

Then I should see "1" systems selected for SSM 123ms

When I follow the left menu "Systems > System Set Manager > Overview" 454ms

And I follow "channel memberships" in the content area 64ms

And I select "System Default Base Channel" from drop-down in table line with "Fake-Base-Channel-RH-like" 218ms

And I click on "Next" 63ms

Then I should see a "Child Channels" text 287ms

And I should see a "Couldn't determine new base channel" text 73ms

And I should see a "1 system(s) incompatible" text 61ms

When I click on "Next" 60ms

Then I should see a "Channel Changes Overview" text 62ms

And I should see a "Couldn't determine new base channel" text 64ms

And I should see a "1 system(s) incompatible" text 72ms

When I click on "Confirm" 60ms

Then I should see a "Channel Changes Actions" text 290ms

And I should see a "Items 1 - 1 of 1" text 61ms

And a table line should contain system "rhlike_minion", "Could not determine system default channel" 21ms

And I click on the clear SSM button 49ms

@rhlike_minion
Scenario:
Cleanup: make sure the Red Hat-like minion is still unchanged
1s 380ms 4

Given I am on the Systems overview page of this "rhlike_minion" 1s 21ms

When I follow "Software" in the content area 64ms

And I follow "Software Channels" in the content area 58ms

Then radio button "Fake-Base-Channel-RH-like" should be checked 235ms

@deblike_minion
Scenario:
System default channel can't be determined on the Debian-like minion
2s 607ms 20

When I follow the left menu "Systems > System List > All" 113ms

And I click on the clear SSM button 52ms

And I check the "deblike_minion" client 434ms

Then I should see "1" systems selected for SSM 116ms

When I follow the left menu "Systems > System Set Manager > Overview" 449ms

And I follow "channel memberships" in the content area 60ms

And I select "System Default Base Channel" from drop-down in table line with "Fake-Base-Channel-Debian-like" 201ms

And I click on "Next" 52ms

Then I should see a "Child Channels" text 280ms

And I should see a "Couldn't determine new base channel" text 67ms

And I should see a "1 system(s) incompatible" text 63ms

When I click on "Next" 56ms

Then I should see a "Channel Changes Overview" text 61ms

And I should see a "Couldn't determine new base channel" text 61ms

And I should see a "1 system(s) incompatible" text 69ms

When I click on "Confirm" 51ms

Then I should see a "Channel Changes Actions" text 285ms

And I should see a "Items 1 - 1 of 1" text 61ms

And a table line should contain system "deblike_minion", "Could not determine system default channel" 17ms

And I click on the clear SSM button 50ms

@deblike_minion
Scenario:
Cleanup: make sure the Debian-like minion is still unchanged
1s 346ms 4

Given I am on the Systems overview page of this "deblike_minion" 1s

When I follow "Software" in the content area 58ms

And I follow "Software Channels" in the content area 56ms

Then radio button "Fake-Base-Channel-Debian-like" should be checked 230ms

@sle_minion @susemanager
Scenario:
Cleanup: subscribe the SLES minion back to previous channels
< 1ms 23

Given I am on the Systems overview page of this "sle_minion" 0s

When I follow "Software" in the content area 0s

And I follow "Software Channels" in the content area 0s

And I wait until I do not see "Loading..." text 0s

And I check radio button "SLE-Product-SLES15-SP7-Pool for x86_64" 0s

And I wait until I do not see "Loading..." text 0s

And I include the recommended child channels 0s

And I check "SLE-Module-DevTools15-SP7-Pool for x86_64" 0s

And I check "SLE-Module-Containers15-SP7-Pool for x86_64" 0s

And I check "Fake-RPM-SUSE-Channel" 0s

And I wait until I do not see "Loading..." text 0s

And I wait until I see "SLE15-SP7-Installer-Updates for x86_64" text 0s

And I wait until I do not see "Loading..." text 0s

And I include the recommended child channels 0s

And I check "SLE-Module-DevTools15-SP7-Pool for x86_64" 0s

And I check "Fake-RPM-SUSE-Channel" 0s

And I click on "Next" 0s

Then I should see a "Confirm Software Channel Change" text 0s

When I click on "Confirm" 0s

Then I should see a "Changing the channels has been scheduled." text 0s

When I follow "scheduled" in the content area 0s

And I wait until I see "1 system successfully completed this action." text, refreshing the page 0s

Then channel "SLE15-SP7-Installer-Updates for x86_64" should be disabled on "sle_minion" 0s

@sle_minion @uyuni
Scenario:
Cleanup: subscribe the openSUSE minion back to previous channels
43s 178ms 15

Given I am on the Systems overview page of this "sle_minion" 1s 7ms

When I follow "Software" in the content area 61ms

And I follow "Software Channels" in the content area 56ms

And I wait until I do not see "Loading..." text 65ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 10s 71ms

And I wait until I do not see "Loading..." text 512ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 76ms

And I check "Fake-RPM-SUSE-Channel" 75ms

And I click on "Next" 56ms

Then I should see a "Confirm Software Channel Change" text 65ms

When I click on "Confirm" 67ms

Then I should see a "Changing the channels has been scheduled." text 399ms

When I follow "scheduled" in the content area 74ms

And I wait until I see "1 system successfully completed this action." text, refreshing the page 29s 859ms

Then channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" should be disabled on "sle_minion" 727ms

Scenario:
Cleanup: remove remaining systems from SSM after channel subscription tests
69ms 1

When I click on the clear SSM button 69ms

@scope_changing_software_channels @scc_credentials
Feature:Channel subscription with recommended or required dependencies 46s 557ms 5 2

Scenario:
Log in as org admin user
1s 804ms 1

Given I am authorized 1s 804ms

Scenario:
Pre-requisite: remove remaining systems from SSM after software channel tests
54ms 1

When I click on the clear SSM button 54ms

@susemanager
Scenario:
Play with recommended and required child channels selection for a single system
< 1ms 15

Given I am on the Systems overview page of this "sle_minion" 0s

When I follow "Software" in the content area 0s

And I follow "Software Channels" in the content area 0s

And I wait until I do not see "Loading..." text 0s

And I check radio button "SLE-Product-SLES15-SP7-Pool for x86_64" 0s

And I wait until I do not see "Loading..." text 0s

Then I should see the child channel "SLE-Product-SLES15-SP7-Updates for x86_64" "selected" and "disabled" 0s

When I exclude the recommended child channels 0s

Then I should see the toggler "disabled" 0s

And I should see a "SLE-Module-Containers15-SP7-Pool for x86_64" text 0s

And I should see the child channel "SLE-Module-Containers15-SP7-Pool for x86_64" "unselected" 0s

When I select the child channel "SLE-Module-Containers15-SP7-Pool for x86_64" 0s

Then I should see the child channel "SLE-Module-Containers15-SP7-Pool for x86_64" "selected" 0s

When I click on the "disabled" toggler 0s

Then I should see the child channel "SLE-Module-Server-Applications15-SP7-Pool for x86_64" "selected" 0s

@uyuni
Scenario:
Play with recommended and required child channels selection for a single system
42s 710ms 10

Given I am on the Systems overview page of this "sle_minion" 1s 636ms

When I follow "Software" in the content area 71ms

And I follow "Software Channels" in the content area 64ms

And I wait for child channels to appear 211ms

And I check radio button "(none, disable service)" 10s 64ms

And I wait for child channels to appear 219ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 10s 58ms

Then I should see the child channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" "unselected" and "disabled" 10s 108ms

When I select the child channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" 10s 170ms

Then I should see the child channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" "selected" 103ms

@susemanager
Scenario:
Play with recommended and required child channels selection in SSM
< 1ms 16

When I follow the left menu "Systems > System List > All" 0s

And I check the "sle_minion" client 0s

Then I should see "1" systems selected for SSM 0s

When I follow the left menu "Systems > System Set Manager > Overview" 0s

And I follow "channel memberships" in the content area 0s

Then I should see a "Base Channel" text 0s

And I should see a "Next" text 0s

And I should see a table line with "SLE-Product-SLES15-SP7-Pool for x86_64", "1" 0s

When I select "System Default Base Channel" from drop-down in table line with "SLE-Product-SLES15-SP7-Pool for x86_64" 0s

And I click on "Next" 0s

Then I should see the toggler "disabled" 0s

And I should see a "SLE-Module-Basesystem15-SP7-Pool for x86_64" text 0s

And I should see "No change" "selected" for the "SLE-Module-Basesystem15-SP7-Pool for x86_64" channel 0s

When I click on the "disabled" toggler 0s

Then I should see "Subscribe" "selected" for the "SLE-Module-Basesystem15-SP7-Pool for x86_64" channel 0s

And I should see "No change" "unselected" for the "SLE-Module-Basesystem15-SP7-Pool for x86_64" channel 0s

@uyuni
Scenario:
Play with recommended and required child channels selection in SSM
1s 925ms 10

When I follow the left menu "Systems > System List > All" 137ms

And I check the "sle_minion" client 508ms

Then I should see "1" systems selected for SSM 120ms

When I follow the left menu "Systems > System Set Manager > Overview" 486ms

And I follow "channel memberships" in the content area 72ms

Then I should see a "Base Channel" text 64ms

And I should see a "Next" text 61ms

When I select "No Change" from drop-down in table line with "openSUSE Tumbleweed (x86_64)" 65ms

And I click on "Next" 63ms

Then I should see the toggler "disabled" 344ms

Scenario:
Cleanup: remove remaining systems from SSM after software channel tests
61ms 1

When I click on the clear SSM button 61ms

@flaky @scope_res @scope_salt @rhlike_minion
Feature:Install a patch on the Red Hat-like minion via Salt through the UI 2m 33s 579ms 9 1

Scenario:
Pre-requisite: enable test_repo_rpm_pool repository on the Red Hat-like minion
314ms 1

When I enable repository "test_repo_rpm_pool" on this "rhlike_minion" 314ms

Scenario:
Pre-requisite: install virgo-dummy-1.0 package on Red Hat-like minion
1s 651ms 1

When I install package "virgo-dummy-1.0" on this "rhlike_minion" 1s 651ms

Scenario:
Pre-requisite: remove andromeda-dummy package from Red Hat-like minion
1s 572ms 1

When I remove package "andromeda-dummy" from this "rhlike_minion" 1s 572ms

Scenario:
Pre-requisite: refresh package list and check newly installed packages on Red Hat-like minion
17s 854ms 1 2 1

When I refresh packages list via spacecmd on "rhlike_minion" 2s 470ms Show Error + 
                                            
 FAIL: mgrctl exec -i 'spacecmd -u admin -p admin system_schedulepackagerefresh uyuni-master-rhlike-minion' returned status code = 1.
Output:


** Generating system cache **
                             
 (ScriptError)
./features/support/remote_node.rb:169:in `run_local'
./features/support/remote_node.rb:117:in `run'
./features/step_definitions/command_steps.rb:1251:in `/^I refresh packages list via spacecmd on "([^"]*)"$/'
features/secondary/min_rhlike_salt_install_package_and_patch.feature:20:in `I refresh packages list via spacecmd on "rhlike_minion"'

And I wait until refresh package list on "rhlike_minion" is finished 0s

Then spacecmd should show packages "virgo-dummy-1.0" installed on "rhlike_minion" 0s

15s 383ms Show Info + 
17:16:31:000 - 17:16:34:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channel/ssm/ChannelSubscriptions.do
Screenshot +

Scenario:
Log in as org admin user
2s 108ms 1

Given I am authorized for the "Admin" section 2s 108ms

Scenario:
Pre-requisite: re-subscribe the Red Hat-like minion to a base channel
24s 558ms 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 616ms

When I follow "Software" in the content area 69ms

And I follow "Software Channels" in the content area 65ms

And I wait until I do not see "Loading..." text 66ms

And I check radio button "Fake-Base-Channel-RH-like" 212ms

And I wait until I do not see "Loading..." text 335ms

And I click on "Next" 60ms

Then I should see a "Confirm Software Channel Change" text 60ms

When I click on "Confirm" 73ms

Then I should see a "Changing the channels has been scheduled." text 298ms

And I wait until event "Subscribe channels scheduled" is completed 21s 699ms

Scenario:
Schedule errata refresh to reflect channel assignment on Red Hat-like minion
44s 288ms 10

When I follow "Software" in the content area 61ms

And I follow "List / Remove" in the content area 65ms

And I enter "virgo-dummy" as the filtered package name 137ms

And I click on the filter button until page does contain "virgo-dummy" text 11s 116ms

When I follow the left menu "Admin > Task Schedules" 125ms

And I follow "errata-cache-default" 1s 324ms

And I follow "errata-cache-bunch" 1s 267ms

And I click on "Single Run Schedule" 1s 243ms

Then I should see a "bunch was scheduled" text 265ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 28s 681ms

Scenario:
Install a patch on the Red Hat-like minion
12s 211ms 8

Given I am on the Systems overview page of this "rhlike_minion" 1s 32ms

When I follow "Software" in the content area 84ms

And I follow "Patches" in the content area 64ms

When I check "virgo-dummy-3456" in the list 65ms

And I click on "Apply Patches" 712ms

And I click on "Confirm" 669ms

Then I should see a "1 patch update has been scheduled for" text 85ms

And I wait for "virgo-dummy-2.0-1.1" to be installed on "rhlike_minion" 9s 495ms

Scenario:
Install a package on the Red Hat-like minion
23s 788ms 7

When I follow "Software" in the content area 63ms

And I follow "Install" 453ms

And I check "andromeda-dummy" in the list 58ms

And I click on "Install Packages" 622ms

And I click on "Confirm" 690ms

Then I should see a "1 package install has been scheduled for" text 66ms

And I wait until event "Package Install/Upgrade scheduled" is completed 21s 832ms

Scenario:
Cleanup: remove virgo-dummy and andromeda-dummy packages from Red Hat-like minion
25s 230ms 13

When I follow "Software" in the content area 78ms

And I follow "List / Remove" 540ms

And I enter "andromeda" as the filtered package name 143ms

And I click on the filter button 826ms

And I check "andromeda-dummy" in the list 63ms

And I enter "virgo-dummy" as the filtered package name 44ms

And I click on the filter button 126ms

And I check "virgo-dummy" in the list 56ms

And I click on "Remove Packages" 600ms

And I click on "Confirm" 685ms

Then I should see a "2 package removals have been scheduled" text 63ms

And I wait until event "Package Removal scheduled" is completed 21s 706ms

And I disable repository "test_repo_rpm_pool" on this "rhlike_minion" 294ms

@scope_monitoring @scope_res @rhlike_minion
Feature:Monitor MLM environment with Prometheus on a Red Hat-like Salt minion 1m 11s 651ms 10

In order to monitor Uyuni server
As an authorized user
I want to enable Prometheus exporters

Scenario:
Log in as org admin user
1s 713ms 1

Given I am authorized 1s 713ms

Scenario:
Apply Prometheus exporter formulas on the Red Hat-like minion
2s 547ms 7

Given I am on the Systems overview page of this "rhlike_minion" 1s 492ms

When I follow "Formulas" in the content area 73ms

Then I should see a "Choose formulas:" text 54ms

And I should see a "Monitoring" text 196ms

When I check the "prometheus-exporters" formula 78ms

And I click on "Save" 65ms

And I wait until I see "Formula saved" text 585ms

Scenario:
Configure Prometheus exporter formula on the Red Hat-like minion
2s 242ms 9

When I follow "Formulas" in the content area 66ms

And I follow "Prometheus Exporters" in the content area 273ms

And I click on "Expand All Sections" 215ms

Then I should see a "Enable and configure Prometheus exporters for managed systems." text 100ms

When I check "node" exporter 44ms

And I check "apache" exporter 84ms

And I check "postgres" exporter 95ms

And I click on "Save" 101ms

Then I should see a "Formula saved" text 1s 261ms

Scenario:
Enable tools_update_repo tools_pool_repo so the exporters packages are available
524ms 1

When I enable the repositories "tools_update_repo tools_pool_repo" on this "rhlike_minion" without error control 524ms

@skip_if_github_validation
Scenario:
Apply highstate for Prometheus exporters on the Red Hat-like minion
39s 130ms 4

When I follow "States" in the content area 70ms

And I click on "Apply Highstate" 60ms

Then I should see a "Applying the highstate has been scheduled." text 463ms

And I wait until event "Apply highstate scheduled" is completed 38s 535ms

@skip_if_github_validation
Scenario:
Wait for service
705ms 3

When I wait until "node" exporter service is active on "rhlike_minion" 313ms

And I wait until "apache" exporter service is active on "rhlike_minion" 200ms

And I wait until "postgres" exporter service is active on "rhlike_minion" 190ms

Scenario:
Visit monitoring endpoints on the Red Hat-like minion
592ms 3

When I visit "Prometheus node exporter" endpoint of this "rhlike_minion" 191ms

And I visit "Prometheus apache exporter" endpoint of this "rhlike_minion" 198ms

And I visit "Prometheus postgres exporter" endpoint of this "rhlike_minion" 202ms

Scenario:
Cleanup: undo Prometheus exporter formulas on the Red Hat-like minion
1s 343ms 4

When I follow "Formulas" in the content area 78ms

And I uncheck the "prometheus-exporters" formula 223ms

And I click on "Save" 63ms

Then I wait until I see "Formula saved" text 977ms

@skip_if_github_validation
Scenario:
Cleanup: apply highstate after test monitoring on the Red Hat-like minion
22s 551ms 4

When I follow "States" in the content area 75ms

And I click on "Apply Highstate" 73ms

Then I should see a "Applying the highstate has been scheduled." text 442ms

And I wait until event "Apply highstate scheduled" is completed 21s 961ms

Scenario:
Cleanup: Disable tools_update_repo tools_pool_repo because they are no longer needed
300ms 1

When I disable the repositories "tools_update_repo tools_pool_repo" on this "rhlike_minion" without error control 300ms

@skip_if_github_validation @scope_salt
Feature:Install a package and a patch on the SUSE SSH client via Salt through the UI 3m 57s 281ms 11

Scenario:
Pre-requisite: enable test_repo_rpm_pool repository on SSH minion
757ms 1

When I enable repository "test_repo_rpm_pool" on this "ssh_minion" 757ms

Scenario:
Pre-requisite: install virgo-dummy-1.0 package on SSH minion
2s 258ms 2

When I refresh the metadata for "ssh_minion" 976ms

And I install old package "virgo-dummy-1.0" on this "ssh_minion" without error control 1s 282ms

Scenario:
Pre-requisite: remove andromeda-dummy package from SSH minion
26s 80ms 4

When I remove package "andromeda-dummy" from this "ssh_minion" without error control 779ms

And I refresh the metadata for "ssh_minion" 818ms

And I refresh packages list via spacecmd on "ssh_minion" 2s 713ms

And I wait until refresh package list on "ssh_minion" is finished 21s 768ms

Scenario:
Pre-requisite: refresh package list and check old packages installed on SSH minion
29s 745ms 4

When I refresh packages list via spacecmd on "ssh_minion" 2s 349ms

And I wait until refresh package list on "ssh_minion" is finished 21s 468ms

Then spacecmd should show packages "virgo-dummy-1.0" installed on "ssh_minion" 2s 441ms

And I wait until package "andromeda-dummy-2.0-1.1" is removed from "ssh_minion" via spacecmd 3s 485ms

Scenario:
Log in as org admin user
1s 717ms 1

Given I am authorized for the "Admin" section 1s 717ms

Scenario:
Pre-requisite: ensure the errata cache is computed before patching Salt minion
19s 534ms 11

Given I am on the Systems overview page of this "ssh_minion" 1s 514ms

When I follow "Software" in the content area 79ms

And I follow "List / Remove" in the content area 81ms

And I enter "virgo-dummy" as the filtered package name 172ms

And I click on the filter button until page does contain "virgo-dummy" text 11s 155ms

When I follow the left menu "Admin > Task Schedules" 126ms

And I follow "errata-cache-default" 1s 328ms

And I follow "errata-cache-bunch" 1s 264ms

And I click on "Single Run Schedule" 1s 519ms

Then I should see a "bunch was scheduled" text 281ms

When I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 2s 10ms

Scenario:
Install a patch on the SSH minion
42s 885ms 12

Given I am on the Systems overview page of this "ssh_minion" 1s 32ms

When I follow "Software" in the content area 70ms

And I follow "Patches" in the content area 64ms

And I enter "virgo" as the filtered synopsis 46ms

And I click on the filter button 10s 163ms

And I check "virgo-dummy-3456" in the list 84ms

And I check "allowVendorChange" 79ms

And I click on "Apply Patches" 608ms

And I click on "Confirm" 671ms

Then I should see a "1 patch update has been scheduled for" text 72ms

When I wait for "virgo-dummy-2.0-1.1" to be installed on "ssh_minion" 28s 826ms

Then vendor change should be enabled for package actions on "ssh_minion" 1s 167ms

Scenario:
Install a package on the SSH minion
48s 319ms 12

Given I am on the Systems overview page of this "ssh_minion" 1s 105ms

When I follow "Software" in the content area 75ms

And I follow "Packages" 419ms

And I follow "Install" 553ms

And I enter "andromeda" as the filtered package name 112ms

And I click on the filter button 603ms

And I check "andromeda-dummy-2.0-1.1" in the list 56ms

And I click on "Install Packages" 582ms

And I click on "Confirm" 664ms

Then I should see a "1 package install has been scheduled" text 64ms

When I wait for "andromeda-dummy-2.0-1.1" to be installed on "ssh_minion" 43s 275ms

Then vendor change should be enabled for package actions on "ssh_minion" 808ms

Scenario:
Cleanup: disable test_repo_rpm_pool on SSH minion
471ms 1

When I disable repository "test_repo_rpm_pool" on this "ssh_minion" 471ms

Scenario:
Cleanup: remove virgo-dummy package from SSH minion
39s 434ms 4

When I remove package "virgo-dummy" from this "ssh_minion" without error control 1s 505ms

And I refresh the metadata for "ssh_minion" 990ms

And I refresh packages list via spacecmd on "ssh_minion" 2s 819ms

And I wait until refresh package list on "ssh_minion" is finished 34s 118ms

Scenario:
Cleanup: remove andromeda-dummy package from SSH minion
26s 76ms 4

When I remove package "andromeda-dummy" from this "ssh_minion" without error control 1s 219ms

And I refresh the metadata for "ssh_minion" 846ms

And I refresh packages list via spacecmd on "ssh_minion" 2s 364ms

And I wait until refresh package list on "ssh_minion" is finished 21s 646ms

@scope_ansible @scope_salt_ssh @ssh_minion
Feature:Operate an Ansible control node in SSH minion 4m 17s 426ms 12 2

Scenario:
Log in as org admin user
426ms 1

Given I am authorized for the "Admin" section 426ms

Scenario:
Pre-requisite: Deploy test playbooks and inventory file
3s 859ms 1

When I deploy testing playbooks and inventory files to "ssh_minion" 3s 859ms

@susemanager
Scenario:
Pre-requisite: Subscribe SUSE minions to SLE-Module-Python3-15-SP7-Pool for x86_64
< 1ms 9

Given I am on the Systems overview page of this "ssh_minion" 0s

When I follow "Software" in the content area 0s

And I follow "Software Channels" in the content area 0s

And I check "SLE-Module-Python3-15-SP7-Pool for x86_64" by label 0s

And I click on "Next" 0s

And I click on "Confirm" 0s

And I wait until I see "Changing the channels has been scheduled." text 0s

And I follow "scheduled" 0s

And I wait until I see "1 system successfully completed this action" text, refreshing the page 0s

Scenario:
Enable "Ansible control node" system type
2s 790ms 5

Given I am on the Systems overview page of this "ssh_minion" 1s 38ms

When I follow "Properties" in the content area 68ms

And I check "ansible_control_node" 80ms

And I click on "Update Properties" 1s 517ms

Then I wait until I see "Ansible Control Node type has been applied." text 85ms

Scenario:
Apply highstate and check that Ansible is installed
1m 13s 583ms 5

Given I am on the Systems overview page of this "ssh_minion" 1s 151ms

When I follow "States" in the content area 68ms

And I click on "Apply Highstate" 59ms

And I wait until event "Apply highstate scheduled" is completed 1m 11s 707ms

Then "ansible" should be installed on "ssh_minion" 594ms

Scenario:
The Ansible tab appears in the system overview page
1s 163ms 3

Given I am on the Systems overview page of this "ssh_minion" 1s 24ms

When I follow "Ansible" in the content area 78ms

Then I should see a "Ansible Control Node Configuration" text 61ms

Scenario:
Configure some inventory and playbooks path
1s 662ms 7

Given I am on the Systems overview page of this "ssh_minion" 1s 55ms

When I follow "Ansible" in the content area 56ms

Then I should see a "Ansible Control Node Configuration" text 59ms

And I enter "/srv/playbooks/" as "new_playbook_path_input" 253ms

And I click on "new_playbook_path_save" 81ms

And I enter "/srv/playbooks/orion_dummy/hosts" as "new_inventory_path_input" 98ms

And I click on "new_inventory_path_save" 56ms

Scenario:
Display inventories
23s 239ms 6

Given I am on the Systems overview page of this "ssh_minion" 1s 70ms

When I follow "Ansible" in the content area 58ms

And I follow "Inventories" in the content area 62ms

And I wait until I see "/srv/playbooks/orion_dummy/hosts" text 243ms

And I click on "/srv/playbooks/orion_dummy/hosts" 57ms

Then I wait until I see "myself" text 21s 746ms

Scenario:
Discover playbooks and display them
10s 723ms 6

Given I am on the Systems overview page of this "ssh_minion" 1s 23ms

When I follow "Ansible" in the content area 76ms

And I follow "Playbooks" in the content area 65ms

And I wait until I see "/srv/playbooks" text 241ms

And I click on "/srv/playbooks" 57ms

Then I wait until I see "/srv/playbooks/orion_dummy/playbook_orion_dummy.yml" text 9s 258ms

Scenario:
Run a playbook using custom inventory
56s 944ms 13

Given I am on the Systems overview page of this "ssh_minion" 976ms

When I follow "Ansible" in the content area 59ms

And I follow "Playbooks" in the content area 57ms

And I wait until I see "/srv/playbooks" text 238ms

And I click on "/srv/playbooks" 50ms

And I wait until I see "/srv/playbooks/orion_dummy/playbook_orion_dummy.yml" text 8s 913ms

And I click on "orion_dummy/playbook_orion_dummy.yml" 59ms

And I wait until I see "Playbook Content" text 5s 790ms

And I select "/srv/playbooks/orion_dummy/hosts" from "inventory-path-select" 1s 120ms

And I click on "Schedule" 66ms

Then I should see a "Playbook execution has been scheduled" text 363ms

And I wait until event "Execute playbook 'playbook_orion_dummy.yml' scheduled" is completed 38s 502ms

And file "/tmp/file.txt" should exist on "ssh_minion" 745ms

Scenario:
Cleanup: Disable Ansible and remove test playbooks and inventory file
14s 574ms 7

Given I am on the Systems overview page of this "ssh_minion" 1s 102ms

When I follow "Properties" in the content area 78ms

And I uncheck "ansible_control_node" 10s 80ms

And I click on "Update Properties" 1s 200ms

Then I should see a "System properties changed" text 88ms

And I remove package "orion-dummy" from this "ssh_minion" without error control 1s 619ms

And I remove "/tmp/file.txt" from "ssh_minion" 405ms

@susemanager
Scenario:
Cleanup: Unsubscribe SUSE minions from SLE-Module-Python3-15-SP7-Pool for x86_64
< 1ms 9

Given I am on the Systems overview page of this "ssh_minion" 0s

When I follow "Software" in the content area 0s

And I follow "Software Channels" in the content area 0s

And I uncheck "SLE-Module-Python3-15-SP7-Pool for x86_64" by label 0s

And I click on "Next" 0s

And I click on "Confirm" 0s

And I wait until I see "Changing the channels has been scheduled." text 0s

And I follow "scheduled" 0s

And I wait until I see "1 system successfully completed this action" text, refreshing the page 0s

Scenario:
Cleanup: Disable "Ansible control node" system type
12s 107ms 4

Given I am on the Systems overview page of this "ssh_minion" 1s 118ms

When I follow "Properties" in the content area 74ms

And I uncheck "ansible_control_node" 10s 30ms

And I click on "Update Properties" 883ms

Scenario:
Cleanup: Apply highstate to disable the minion as an "Ansible control node"
56s 350ms 4

Given I am on the Systems overview page of this "ssh_minion" 1s 80ms

When I follow "States" in the content area 73ms

And I click on "Apply Highstate" 70ms

And I wait until event "Apply highstate scheduled" is completed 55s 126ms

@scope_monitoring @scope_res @deblike_minion
Feature:Monitor MLM environment with Prometheus on a Debian-like Salt minion 1m 29s 862ms 10

In order to monitor Uyuni server
As an authorized user
I want to enable Prometheus exporters

Scenario:
Log in as org admin user
1s 570ms 1

Given I am authorized 1s 570ms

Scenario:
Apply Prometheus exporter formulas on the Debian-like minion
2s 714ms 7

Given I am on the Systems overview page of this "deblike_minion" 1s 666ms

When I follow "Formulas" in the content area 73ms

Then I should see a "Choose formulas:" text 58ms

And I should see a "Monitoring" text 184ms

When I check the "prometheus-exporters" formula 75ms

And I click on "Save" 64ms

And I wait until I see "Formula saved" text 591ms

Scenario:
Configure Prometheus exporter formula on the Debian-like minion
2s 166ms 9

When I follow "Formulas" in the content area 63ms

And I follow "Prometheus Exporters" in the content area 236ms

And I click on "Expand All Sections" 184ms

Then I should see a "Enable and configure Prometheus exporters for managed systems." text 113ms

When I check "node" exporter 44ms

And I check "apache" exporter 87ms

And I check "postgres" exporter 92ms

And I click on "Save" 95ms

Then I should see a "Formula saved" text 1s 248ms

Scenario:
Enable tools_update_repo tools_pool_repo so the exporters packages are available
1s 347ms 1

When I enable the repositories "tools_update_repo tools_pool_repo" on this "deblike_minion" without error control 1s 347ms

@skip_if_github_validation
Scenario:
Apply highstate for Prometheus exporters on the Debian-like minion
55s 736ms 4

When I follow "States" in the content area 69ms

And I click on "Apply Highstate" 59ms

Then I should see a "Applying the highstate has been scheduled." text 454ms

And I wait until event "Apply highstate scheduled" is completed 55s 152ms

@skip_if_github_validation
Scenario:
Wait for services
801ms 3

When I wait until "node" exporter service is active on "deblike_minion" 406ms

And I wait until "apache" exporter service is active on "deblike_minion" 197ms

And I wait until "postgres" exporter service is active on "deblike_minion" 197ms

Scenario:
Visit monitoring endpoints on the Debian-like minion
600ms 3

And I visit "Prometheus node exporter" endpoint of this "deblike_minion" 199ms

And I visit "Prometheus apache exporter" endpoint of this "deblike_minion" 199ms

And I visit "Prometheus postgres exporter" endpoint of this "deblike_minion" 200ms

Scenario:
Cleanup: undo Prometheus exporter formulas on the Debian-like minion
1s 459ms 4

When I follow "Formulas" in the content area 81ms

And I uncheck the "prometheus-exporters" formula 214ms

And I click on "Save" 65ms

Then I wait until I see "Formula saved" text 1s 97ms

@skip_if_github_validation
Scenario:
Cleanup: apply highstate after test monitoring on the Debian-like minion
22s 602ms 4

When I follow "States" in the content area 70ms

And I click on "Apply Highstate" 60ms

Then I should see a "Applying the highstate has been scheduled." text 414ms

And I wait until event "Apply highstate scheduled" is completed 22s 57ms

Scenario:
Cleanup: Disable tools_update_repo tools_pool_repo because they are no longer needed
863ms 1

When I disable the repositories "tools_update_repo tools_pool_repo" on this "deblike_minion" without error control 863ms

@deblike_minion @scope_deblike @scope_content_staging
Feature:Install a package on the Debian-like minion with staging enabled 3m 59s 581ms 7 1

Scenario:
Pre-requisite: install virgo-dummy-1.0 package, make sure orion-dummy is not present on Debian-like minion
1s 753ms 4

When I enable repository "test_repo_deb_pool" on this "deblike_minion" 409ms

And I run "apt update" on "deblike_minion" 843ms

And I remove package "orion-dummy" from this "deblike_minion" 250ms

And I install old package "virgo-dummy=1.0" on this "deblike_minion" 250ms

Scenario:
Pre-requisite: refresh package list on Debian-like minion
12s 566ms 3

When I refresh packages list via spacecmd on "deblike_minion" 2s 806ms

And I wait until refresh package list on "deblike_minion" is finished 7s 351ms

Then spacecmd should show packages "virgo-dummy-1.0" installed on "deblike_minion" 2s 409ms

Scenario:
Log in as admin user
1s 692ms 1

Given I am authorized for the "Admin" section 1s 692ms

Scenario:
Pre-requisite: ensure the errata cache is computed for Debian-like minion
13s 4ms 6

When I follow the left menu "Admin > Task Schedules" 127ms

And I follow "errata-cache-default" 1s 176ms

And I follow "errata-cache-bunch" 1s 554ms

Then I click on "Single Run Schedule" 1s 226ms

And I should see a "bunch was scheduled" text 263ms

Then I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 8s 656ms

Scenario:
Enable content staging for Debian-like minion
1s 83ms 6

When I follow the left menu "Admin > Organizations" 67ms

And I follow first "SUSE Test" 227ms

And I follow first "Configuration" 286ms

And I check "staging_content_enabled" 42ms

And I click on "Update Organization" 398ms

Then I should see a "was successfully updated." text 61ms

Scenario:
Install package in the future and check for staging on Debian-like minion
3m 1s 689ms 13

Given I am on the Systems overview page of this "deblike_minion" 1s 103ms

And I follow "Software" in the content area 70ms

And I follow "Packages" in the content area 62ms

And I follow "Install" in the content area 65ms

And I enter "orion-dummy-1.1-X" as the filtered package name 59ms

And I click on the filter button 492ms

When I check "orion-dummy-1.1-X" in the list 64ms

And I click on "Install Packages" 578ms

And I pick 3 minutes from now as schedule time 88ms

And I click on "Confirm" 671ms

Then I should see a "1 package install has been scheduled for" text 63ms

And I wait until the package "orion-dummy_1.1" has been cached on this "deblike_minion" 1m 1s 949ms

And I wait for "orion-dummy-1.1" to be installed on "deblike_minion" 1m 56s 418ms

Scenario:
Install patch in the future and check for staging on Debian-like minion
25s 304ms 3 8 1

When I follow "Software" in the content area 64ms

And I follow "Patches" in the content area 72ms

And I enter "virgo" as the filtered synopsis 10s 6ms Show Error + 
                                            
 Unable to find css "input[placeholder='Filter by Synopsis: ']" (Capybara::ElementNotFound)
./features/step_definitions/navigation_steps.rb:954:in `/^I enter "([^"]*)" as the filtered synopsis$/'
features/secondary/min_deblike_salt_install_with_staging.feature:66:in `I enter "virgo" as the filtered synopsis'

And I click on the filter button 0s

And I check "3456-1" in the list 0s

And I click on "Apply Patches" 0s

And I pick 3 minutes from now as schedule time 0s

And I click on "Confirm" 0s

Then I should see a "1 patch update has been scheduled for" text 0s

And I wait until the package "virgo-dummy_2.0" has been cached on this "deblike_minion" 0s

And I wait for "virgo-dummy-2.0" to be installed on "deblike_minion" 0s

15s 160ms Show Info + 
17:35:06:000 - 17:35:16:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/ErrataList.do?sid=1000010009&
Screenshot +

Scenario:
Cleanup: remove virgo-dummy and orion-dummy packages from Debian-like minion
2s 487ms 4

And I remove package "orion-dummy" from this "deblike_minion" 1s 4ms

And I remove package "virgo-dummy" from this "deblike_minion" 332ms

And I disable repository "test_repo_deb_pool" on this "deblike_minion" 196ms

And I run "apt update" on "deblike_minion" 954ms

@scope_deblike @scope_salt @deblike_minion
Feature:Install and upgrade package on the Debian-like minion via Salt through the UI 1m 30s 615ms 9 1 1

Scenario:
Pre-requisite: enable test_repo_deb_pool repository on the Debian-like minion
412ms 1

When I enable repository "test_repo_deb_pool" on this "deblike_minion" 412ms

Scenario:
Pre-requisite: install virgo-dummy-1.0 package on Debian-like minion
2s 741ms 2

OUT: Ign:1 http://mirror.sumaci.aws/repositories/systemsmanagement:/Uyuni:/Test-Packages:/Pool/deb InRelease Get:2 http://mirror.sumaci.aws/repositories/systemsmanagement:/Uyuni:/Test-Packages:/Pool/deb Release [1,026 B] Get:3 http://mirror.sumaci.aws/repositories/systemsmanagement:/Uyuni:/Test-Packages:/Pool/deb Release.gpg [481 B] Ign:4 https://uyuni-master-proxy.sumaci.aws:443/rhn/manager/download fake-base-channel-debian-like/ InRelease Hit:5 https://uyuni-master-proxy.sumaci.aws:443/rhn/manager/download fake-base-channel-debian-like/ Release Ign:6 https://uyuni-master-proxy.sumaci.aws:443/rhn/manager/download fake-base-channel-debian-like/ Release.gpg Get:7 http://mirror.sumaci.aws/repositories/systemsmanagement:/Uyuni:/Test-Packages:/Pool/deb Packages [785 B] Fetched 2,292 B in 0s (7,627 B/s) Reading package lists... Building dependency tree... Reading state information... 2 packages can be upgraded. Run 'apt list --upgradable' to see them. WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

When I run "apt update" on "deblike_minion" with logging 822ms

And I install old package "virgo-dummy=1.0" on this "deblike_minion" 1s 918ms

Scenario:
Pre-requisite: remove andromeda-dummy package from Debian-like minion
328ms 1

When I remove package "andromeda-dummy" from this "deblike_minion" 328ms

Scenario:
Log in as org admin user
2s 168ms 1

Given I am authorized 2s 168ms

Scenario:
Pre-requisite: refresh package list and check newly installed packages on Debian-like minion
32s 878ms 7

Given I am on the Systems overview page of this "deblike_minion" 1s 741ms

When I follow "Software" in the content area 74ms

And I click on "Update Package List" 687ms

And I follow "Events" in the content area 67ms

And I wait until I do not see "Package List Refresh scheduled" text, refreshing the page 24s 170ms

And I wait until package "virgo-dummy" is installed on "deblike_minion" via spacecmd 2s 742ms

And I wait until package "andromeda-dummy" is removed from "deblike_minion" via spacecmd 3s 394ms

Scenario:
Install a patch on the Debian-like minion
25s 479ms 3 4 1

When I follow "Software" in the content area 62ms

And I follow "Patches" in the content area 70ms

When I check "3456-1" in the list 10s 3ms Show Error + 
                                            
 Unable to find xpath "//table/tbody/tr[.//td[contains(.,'3456-1')]]//input[@type='checkbox']" (Capybara::ElementNotFound)
./features/support/navigation_step_helper.rb:32:in `toggle_checkbox_in_list'
./features/support/navigation_step_helper.rb:10:in `toggle_checkbox_in_package_list'
./features/step_definitions/navigation_steps.rb:1026:in `/^I (check|uncheck) "([^"]*)"(| last version) in the list$/'
features/secondary/min_deblike_salt_install_package_and_patch.feature:34:in `I check "3456-1" in the list'

And I click on "Apply Patches" 0s

And I click on "Confirm" 0s

Then I should see a "1 patch update has been scheduled for" text 0s

And I wait for "virgo-dummy-2.0" to be installed on "deblike_minion" 0s

15s 343ms Show Info + 
17:36:29:000 - 17:36:40:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/ErrataList.do?sid=1000010009&
Screenshot +

@susemanager
Scenario:
Install a package on the Debian-like minion
< 1ms 8

When I follow "Software" in the content area 0s

And I follow "Install" 0s

And I check "andromeda-dummy-2.0" in the list 0s

And I click on "Install Packages" 0s

And I click on "Confirm" 0s

And I should see a "1 package install has been scheduled for" text 0s

When I wait until event "Package Install/Upgrade scheduled" is completed 0s

Then Deb package "andromeda-dummy" with version "2.0" should be installed on "deblike_minion" 0s

@uyuni
Scenario:
Install a package on the Debian-like minion
24s 776ms 8

When I follow "Software" in the content area 69ms

And I follow "Install" 489ms

And I check "andromeda-dummy-2.0" in the list 61ms

And I click on "Install Packages" 633ms

And I click on "Confirm" 751ms

And I should see a "1 package install has been scheduled for" text 59ms

When I wait until event "Package Install/Upgrade scheduled" is completed 21s 847ms

Then Deb package "andromeda-dummy" with version "2.0" should be installed on "deblike_minion" 864ms

Scenario:
Cleanup: disable test_repo_deb_pool on Debian-like minion
191ms 1

When I disable repository "test_repo_deb_pool" on this "deblike_minion" 191ms

Scenario:
Cleanup: remove virgo-dummy package from Debian-like minion
321ms 1

When I remove package "virgo-dummy" from this "deblike_minion" 321ms

Scenario:
Cleanup: remove andromeda-dummy package from Debian-like minion
1s 316ms 2

OUT: Ign:1 https://uyuni-master-proxy.sumaci.aws:443/rhn/manager/download fake-base-channel-debian-like/ InRelease Hit:2 https://uyuni-master-proxy.sumaci.aws:443/rhn/manager/download fake-base-channel-debian-like/ Release Ign:3 https://uyuni-master-proxy.sumaci.aws:443/rhn/manager/download fake-base-channel-debian-like/ Release.gpg Reading package lists... Building dependency tree... Reading state information... 1 package can be upgraded. Run 'apt list --upgradable' to see it. WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

When I remove package "andromeda-dummy" from this "deblike_minion" 328ms

And I run "apt update" on "deblike_minion" with logging 988ms

@skip_if_github_validation @sle_minion @scope_onboarding
Feature:Negative tests for bootstrapping normal minions 20s 987ms 5

In order to register only valid minions
As an authorized user
I want to avoid registration with invalid input parameters

Scenario:
Log in as org admin user
1s 742ms 1

Given I am authorized 1s 742ms

Scenario:
Bootstrap should fail when minion already exists
961ms 10

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 129ms

Then I should see a "Bootstrap Minions" text 68ms

When I enter the hostname of "sle_minion" as "hostname" 137ms

And I enter "22" as "port" 59ms

And I enter "root" as "user" 59ms

And I enter "linux" as "password" 59ms

And I click on "Bootstrap" 65ms

And I wait until I see "A salt key for this host" text 260ms

Then I should not see a "GenericSaltError" text 61ms

And I should see a "seems to already exist, please check!" text 61ms

Scenario:
Bootstrap a SLES minion with wrong hostname
2s 930ms 14

When I follow the left menu "Systems > Bootstrapping" 64ms

Then I should see a "Bootstrap Minions" text 66ms

When I enter "not-existing-name" as "hostname" 82ms

And I enter "22" as "port" 48ms

And I enter "root" as "user" 51ms

And I enter "linux" as "password" 53ms

And I click on "Bootstrap" 57ms

And I wait until I see "An error has occurred during salt execution: unable to establish ssh connection." text 2s 262ms

Then I should see a "Details" button 17ms

When I click on "Details" 71ms

And I wait at most 10 seconds until I see modal containing "Error Details" text 13ms

Then I should see a "Standard Error" text 67ms

And I should see "Could not resolve hostname not-existing-name: Name or service not known" in the stderr textarea 17ms

When I close the modal dialog 55ms

Scenario:
Bootstrap a SLES minion with wrong SSH credentials
12s 379ms 14

The hostname of localhost is uyuni-master-controller.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 62ms

Then I should see a "Bootstrap Minions" text 62ms

When I enter the hostname of "localhost" as "hostname" 121ms

And I enter "22" as "port" 50ms

And I enter "FRANZ" as "user" 56ms

And I enter "KAFKA" as "password" 56ms

And I click on "Bootstrap" 56ms

And I wait until I see "An error has occurred during salt execution: unable to establish ssh connection." text 11s 703ms

Then I should see a "Details" button 13ms

When I click on "Details" 61ms

And I wait at most 10 seconds until I see modal containing "Error Details" text 8ms

Then I should see a "Standard Error" text 68ms

And I should see "Permission denied (publickey" or "Password authentication failed" in the stderr textarea 12ms

When I close the modal dialog 45ms

Scenario:
Bootstrap a SLES minion with wrong SSH port number
2s 973ms 14

The hostname of localhost is uyuni-master-controller.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 61ms

Then I should see a "Bootstrap Minions" text 62ms

When I enter the hostname of "localhost" as "hostname" 120ms

And I enter "11" as "port" 45ms

And I enter "root" as "user" 52ms

And I enter "linux" as "password" 55ms

And I click on "Bootstrap" 57ms

And I wait until I see "An error has occurred during salt execution: unable to establish ssh connection." text 2s 313ms

Then I should see a "Details" button 13ms

When I click on "Details" 59ms

And I wait at most 10 seconds until I see modal containing "Error Details" text 8ms

Then I should see a "Standard Error" text 66ms

And I should see "port 11: Connection refused" or "port 11: Network is unreachable" in the stderr textarea 12ms

When I close the modal dialog 45ms

@skip_if_github_validation @scope_formulas @bug_reported
Feature:Use salt formulas 4m 38s 464ms 20 2

In order to use simple forms to apply changes to minions
As an authorized user
I want to be able to install and use salt formulas

Scenario:
Log in as org admin user
1s 732ms 1

Given I am authorized 1s 732ms

@skip_if_containerized_server
Scenario:
Install the locale formula package on the server
< 1ms 1

When I manually install the "locale" formula on the server 0s

Scenario:
I synchronize all Salt dynamic modules on "sle_minion"
3s 260ms 1

When I synchronize all Salt dynamic modules on "sle_minion" 3s 260ms

Scenario:
The new formula appears on the server
327ms 2

When I follow the left menu "Salt > Formula Catalog" 124ms

Then I should see a "locale" text in the content area 203ms

Scenario:
Enable the formula on the minion
12s 314ms 9

Given I am on the Systems overview page of this "sle_minion" 1s 20ms

When I follow "Formulas" in the content area 75ms

Then I should see a "Choose formulas:" text 64ms

And I should see a "General System Configuration" text 281ms

And I should see a "Locale" text 82ms

When I check the "locale" formula 82ms

And I click on "Save" 65ms

And I wait until I see "Formula saved." text 618ms

Then the "locale" formula should be checked 10s 23ms

Scenario:
Parametrize the formula on the minion
1s 427ms 8

When I follow "Formulas" in the content area 63ms

And I follow first "Locale" in the content area 209ms

And I click on "Expand All Sections" 231ms

And I select "Etc/GMT-5" in timezone name field 58ms

And I select "French" in language field 47ms

And I select "French (Canada)" in keyboard layout field 44ms

And I click on "Save Formula" 61ms

Then I should see a "Formula saved" text 710ms

Scenario:
Check the pillar data after saving the formula
8s 736ms 5

When I refresh the pillar data 2s 454ms

Then the pillar data for "formulas" should be "- locale" on "sle_minion" 1s 580ms

And the pillar data for "timezone:name" should be "Etc/GMT-5" on "sle_minion" 1s 579ms

And the pillar data for "keyboard_and_language:keyboard_layout" should be "French (Canada)" on "sle_minion" 1s 559ms

And the pillar data for "keyboard_and_language:language" should be "French" on "sle_minion" 1s 562ms

@ssh_minion
Scenario:
No other minion is affected by the formula
21s 663ms 3

Then the pillar data for "formulas" should be empty on "ssh_minion" 7s 652ms

And the pillar data for "timezone" should be empty on "ssh_minion" 6s 924ms

And the pillar data for "keyboard_and_language" should be empty on "ssh_minion" 7s 87ms

Scenario:
Use the parametrized formula in test mode
40s 70ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 21ms

And I follow "States" in the content area 70ms

Then I should see the toggler "disabled" 12ms

When I click on the "disabled" toggler 45ms

And I click on "Apply Highstate" 61ms

Then I should see a "Applying the highstate has been scheduled." text 342ms

And I wait at most 300 seconds until event "Apply highstate in test-mode scheduled" is completed 38s 517ms

Scenario:
Apply the parametrized formula via the highstate
42s 357ms 9

When I enable repository "sle_update_repo" on this "sle_minion" without error control 763ms

And I follow "States" in the content area 79ms

And I click on "Apply Highstate" 66ms

Then I should see a "Applying the highstate has been scheduled." text 464ms

When I wait until event "Apply highstate scheduled" is completed 38s 552ms

Then the timezone on "sle_minion" should be "+05" 749ms

And the keymap on "sle_minion" should be "ca" 421ms

And the language on "sle_minion" should be "fr_FR.UTF-8" 818ms

And I disable repository "sle_update_repo" on this "sle_minion" without error control 441ms

Scenario:
Reset the formula on the minion
1s 245ms 5

When I follow "Formulas" in the content area 80ms

And I follow first "Locale" in the content area 165ms

And I click on "Clear values" and confirm alert box 366ms

And I click on "Save Formula" 73ms

Then I should see a "Formula saved" text 559ms

Scenario:
Check the pillar data after resetting the formula
8s 759ms 5

When I refresh the pillar data 2s 574ms

Then the pillar data for "formulas" should be "- locale" on "sle_minion" 1s 562ms

And the pillar data for "timezone:name" should be "CET" on "sle_minion" 1s 539ms

And the pillar data for "keyboard_and_language:keyboard_layout" should be "English (US)" on "sle_minion" 1s 536ms

And the pillar data for "keyboard_and_language:language" should be "English (US)" on "sle_minion" 1s 547ms

Scenario:
Apply the reset formula via the highstate
41s 204ms 7

And I follow "States" in the content area 69ms

And I click on "Apply Highstate" 94ms

Then I should see a "Applying the highstate has been scheduled." text 322ms

When I wait until event "Apply highstate scheduled" is completed 38s 713ms

Then the timezone on "sle_minion" should be "CET" 740ms

And the keymap on "sle_minion" should be "us" 411ms

And the language on "sle_minion" should be "en_US.UTF-8" 851ms

Scenario:
Disable the formula on the minion
11s 246ms 8

When I follow "Formulas" in the content area 79ms

Then I should see a "Choose formulas:" text 61ms

And I should see a "General System Configuration" text 204ms

And I should see a "Locale" text 89ms

When I uncheck the "locale" formula 74ms

And I click on "Save" 79ms

And I wait until I see "Formula saved." text 632ms

Then the "locale" formula should be unchecked 10s 24ms

Scenario:
Check the pillar data after disabling the formula
7s 30ms 4

When I refresh the pillar data 2s 366ms

Then the pillar data for "formulas" should be empty on "sle_minion" 1s 563ms

And the pillar data for "timezone" should be empty on "sle_minion" 1s 570ms

And the pillar data for "keyboard_and_language" should be empty on "sle_minion" 1s 530ms

Scenario:
Assign locale formula to minion via group formula
3s 624ms 17

When I follow the left menu "Systems > System Groups" 78ms

When I follow "Create Group" 277ms

And I enter "locale-formula-group" as "name" 76ms

And I enter "Test group with locale formula added" as "description" 76ms

And I click on "Create Group" 62ms

Then I should see a "System group locale-formula-group created." text 63ms

When I follow "Formulas" in the content area 73ms

Then I should see a "Choose formulas:" text 57ms

And I should see a "General System Configuration" text 279ms

And I should see a "Locale" text 93ms

When I check the "locale" formula 70ms

And I click on "Save" 66ms

And I wait until I see "Formula saved." text 455ms

And I follow "Target" 487ms

And I check the "sle_minion" client 62ms

And I click on "Add Systems" 1s 251ms

Then I should see a "1 systems were added to locale-formula-group server group." text 92ms

Scenario:
Check the pillar data after assigning group formula
8s 369ms 5

When I refresh the pillar data 2s 138ms

Then the pillar data for "formulas" should be "- locale" on "sle_minion" 1s 575ms

And the pillar data for "timezone:name" should be "CET" on "sle_minion" 1s 546ms

And the pillar data for "keyboard_and_language:keyboard_layout" should be "English (US)" on "sle_minion" 1s 560ms

And the pillar data for "keyboard_and_language:language" should be "English (US)" on "sle_minion" 1s 548ms

@ssh_minion
Scenario:
No other minion is affected by the group formula
21s 545ms 3

Then the pillar data for "formulas" should be empty on "ssh_minion" 7s 635ms

And the pillar data for "timezone" should be empty on "ssh_minion" 7s 17ms

And the pillar data for "keyboard_and_language" should be empty on "ssh_minion" 6s 892ms

Scenario:
Cleanup: remove "locale-formula-group" system group
1s 444ms 7

When I follow the left menu "Systems > System Groups" 63ms

And I follow "locale-formula-group" in the content area 82ms

And I follow "Delete Group" in the content area 59ms

When I click on "Confirm Deletion" 1s 69ms

Then I should see a "System group" text 55ms

And I should see a "locale-formula-group" text 58ms

And I should see a "deleted" text 54ms

Scenario:
Cleanup: reset locale values on the minion
42s 31ms 8

Given I am on the Systems overview page of this "sle_minion" 1s 76ms

And I follow "States" in the content area 69ms

And I click on "Apply Highstate" 61ms

Then I should see a "Applying the highstate has been scheduled." text 406ms

When I wait until event "Apply highstate scheduled" is completed 38s 455ms

Then the timezone on "sle_minion" should be "CET" 743ms

And the keymap on "sle_minion" should be "us" 408ms

And the language on "sle_minion" should be "en_US.UTF-8" 810ms

@skip_if_containerized_server
Scenario:
Cleanup: uninstall formula package from the server
< 1ms 1

When I manually uninstall the "locale" formula from the server 0s

Scenario:
Cleanup: remove remaining systems from SSM after formula tests
71ms 1

When I click on the clear SSM button 71ms

@flaky @scope_formulas
Feature:Use advanced features of Salt formulas 3m 28s 476ms 12

In order to use forms to apply changes to minions
As an authorized user
I want to be able to install and use Salt formulas

Scenario:
Log in as org admin user
1s 836ms 1

Given I am authorized 1s 836ms

Scenario:
Install a test formula package on the server
5s 762ms 5

When I install "form.yml" to custom formula metadata directory "testform" 3s 119ms

And I install "metadata.yml" to custom formula metadata directory "testform" 2s 370ms

When I follow the left menu "Salt > Formula Catalog" 125ms

And I enter "testform" as the filtered formula name 85ms

Then I should see a "testform" text 60ms

Scenario:
Assign test formula to minion via group formula
4s 15ms 17

When I follow the left menu "Systems > System Groups" 116ms

When I follow "Create Group" 263ms

And I enter "test-formula-group" as "name" 65ms

And I enter "Test group with testform formula added" as "description" 76ms

And I click on "Create Group" 458ms

Then I should see a "System group test-formula-group created." text 65ms

When I follow "Formulas" in the content area 71ms

Then I should see a "Choose formulas:" text 58ms

And I should see a "General System Configuration" text 189ms

And I should see a "Testform" text 87ms

When I check the "testform" formula 77ms

And I click on "Save" 64ms

And I wait until I see "Formula saved." text 465ms

And I follow "Target Systems" 525ms

And I check the "sle_minion" client 63ms

And I click on "Add Systems" 1s 274ms

Then I should see a "1 systems were added to test-formula-group server group." text 93ms

Scenario:
Verify default values
39s 691ms 25

When I refresh the pillar data 2s 91ms

Then the pillar data for "testing:str" should be "" on "sle_minion" 1s 565ms

And the pillar data for "testing:str_def" should be "defvalue" on "sle_minion" 1s 616ms

And the pillar data for "testing:str_or_null" should be "None" on "sle_minion" 1s 536ms

And the pillar data for "testing" should not contain "str_opt" on "sle_minion" 1s 578ms

And the pillar data for "testing:num" should be "" on "sle_minion" 1s 546ms

And the pillar data for "testing:num_def" should be "0" on "sle_minion" 1s 545ms

And the pillar data for "testing:num_or_null" should be "None" on "sle_minion" 1s 550ms

And the pillar data for "testing" should not contain "num_opt" on "sle_minion" 1s 547ms

And the pillar data for "testing:pw" should be "" on "sle_minion" 1s 541ms

And the pillar data for "testing:pw_or_null" should be "None" on "sle_minion" 1s 561ms

And the pillar data for "testing" should not contain "pw_opt" on "sle_minion" 1s 585ms

And the pillar data for "testing:list_of_strings" should contain "def_item1" on "sle_minion" 1s 550ms

And the pillar data for "testing:list_of_strings" should contain "def_item2" on "sle_minion" 1s 552ms

And the pillar data for "testing:dict_of_strings:name1" should be "def_value1" on "sle_minion" 1s 548ms

And the pillar data for "testing:dict_of_strings:name2" should be "def_value2" on "sle_minion" 1s 560ms

And the pillar data for "testing:list_of_dicts:0:name" should be "def_user" on "sle_minion" 1s 580ms

And the pillar data for "testing:list_of_dicts:0:password" should be "secret1" on "sle_minion" 1s 586ms

And the pillar data for "testing:list_of_dicts:0" should not contain "full_name" on "sle_minion" 1s 563ms

And the pillar data for "testing:dict_of_dicts:def_user:name" should be "root" on "sle_minion" 1s 564ms

And the pillar data for "testing:dict_of_dicts:def_user:password" should be "secret2" on "sle_minion" 1s 543ms

And the pillar data for "testing:dict_of_dicts:def_user:full_name" should be "None" on "sle_minion" 1s 590ms

And the pillar data for "testing:recursive_dict_of_dicts:def_gr1:group_name" should be "default group 1" on "sle_minion" 1s 601ms

And the pillar data for "testing:recursive_dict_of_dicts:def_gr1:entries:def_entry1:entry_name" should be "default entry 1" on "sle_minion" 1s 600ms

And the pillar data for "testing:recursive_dict_of_dicts:def_gr1:entries:def_entry1:entry_desc" should be "some text" on "sle_minion" 1s 582ms

Scenario:
Fill in and verify non-default values in group formula
20s 527ms 30

When I follow the left menu "Systems > System Groups" 62ms

When I follow "test-formula-group" in the content area 68ms

And I follow "Formulas" in the content area 73ms

And I follow first "Testform" in the content area 230ms

And I click on "Expand All Sections" 238ms

And I enter "text1" as "testing#str" 116ms

And I enter "text2" as "testing#str_def" 139ms

And I enter "text3" as "testing#str_or_null" 85ms

And I enter "text4" as "testing#str_opt" 92ms

And I enter "1" as "testing#num" 59ms

And I enter "2" as "testing#num_def" 82ms

And I enter "3" as "testing#num_or_null" 62ms

And I enter "4" as "testing#num_opt" 62ms

And I enter "pw1" as "testing#pw" 93ms

And I enter "pw2" as "testing#pw_or_null" 86ms

And I enter "pw3" as "testing#pw_opt" 83ms

And I click on "Save Formula" 102ms

Then I should see a "Formula saved" text 721ms

When I wait for "1" seconds 1s

Then the pillar data for "testing:str" should be "text1" on "sle_minion" 1s 538ms

And the pillar data for "testing:str_def" should be "text2" on "sle_minion" 1s 543ms

And the pillar data for "testing:str_or_null" should be "text3" on "sle_minion" 1s 571ms

And the pillar data for "testing:str_opt" should be "text4" on "sle_minion" 1s 565ms

And the pillar data for "testing:num" should be "1" on "sle_minion" 1s 543ms

And the pillar data for "testing:num_def" should be "2" on "sle_minion" 1s 544ms

And the pillar data for "testing:num_or_null" should be "3" on "sle_minion" 1s 542ms

And the pillar data for "testing:num_opt" should be "4" on "sle_minion" 1s 548ms

And the pillar data for "testing:pw" should be "pw1" on "sle_minion" 1s 546ms

And the pillar data for "testing:pw_or_null" should be "pw2" on "sle_minion" 1s 554ms

And the pillar data for "testing:pw_opt" should be "pw3" on "sle_minion" 1s 567ms

Scenario:
Clear values in group formula and verify the defaults again
39s 867ms 32

When I follow the left menu "Systems > System Groups" 89ms

When I follow "test-formula-group" in the content area 76ms

And I follow "Formulas" in the content area 64ms

And I follow first "Testform" in the content area 216ms

And I click on "Clear values" and confirm alert box 336ms

And I click on "Save Formula" 84ms

Then I should see a "Formula saved" text 553ms

When I wait for "1" seconds 1s

Then the pillar data for "testing:str" should be "" on "sle_minion" 1s 543ms

And the pillar data for "testing:str_def" should be "defvalue" on "sle_minion" 1s 547ms

And the pillar data for "testing:str_or_null" should be "None" on "sle_minion" 1s 556ms

And the pillar data for "testing" should not contain "str_opt" on "sle_minion" 1s 563ms

And the pillar data for "testing:num" should be "" on "sle_minion" 1s 544ms

And the pillar data for "testing:num_def" should be "0" on "sle_minion" 1s 547ms

And the pillar data for "testing:num_or_null" should be "None" on "sle_minion" 1s 570ms

And the pillar data for "testing" should not contain "num_opt" on "sle_minion" 1s 561ms

And the pillar data for "testing:pw" should be "" on "sle_minion" 1s 571ms

And the pillar data for "testing:pw_or_null" should be "None" on "sle_minion" 1s 552ms

And the pillar data for "testing" should not contain "pw_opt" on "sle_minion" 1s 565ms

And the pillar data for "testing:list_of_strings" should contain "def_item1" on "sle_minion" 1s 546ms

And the pillar data for "testing:list_of_strings" should contain "def_item2" on "sle_minion" 1s 553ms

And the pillar data for "testing:dict_of_strings:name1" should be "def_value1" on "sle_minion" 1s 549ms

And the pillar data for "testing:dict_of_strings:name2" should be "def_value2" on "sle_minion" 1s 557ms

And the pillar data for "testing:list_of_dicts:0:name" should be "def_user" on "sle_minion" 1s 580ms

And the pillar data for "testing:list_of_dicts:0:password" should be "secret1" on "sle_minion" 1s 568ms

And the pillar data for "testing:list_of_dicts:0" should not contain "full_name" on "sle_minion" 1s 552ms

And the pillar data for "testing:dict_of_dicts:def_user:name" should be "root" on "sle_minion" 1s 569ms

And the pillar data for "testing:dict_of_dicts:def_user:password" should be "secret2" on "sle_minion" 1s 541ms

And the pillar data for "testing:dict_of_dicts:def_user:full_name" should be "None" on "sle_minion" 1s 550ms

And the pillar data for "testing:recursive_dict_of_dicts:def_gr1:group_name" should be "default group 1" on "sle_minion" 1s 585ms

And the pillar data for "testing:recursive_dict_of_dicts:def_gr1:entries:def_entry1:entry_name" should be "default entry 1" on "sle_minion" 1s 589ms

And the pillar data for "testing:recursive_dict_of_dicts:def_gr1:entries:def_entry1:entry_desc" should be "some text" on "sle_minion" 1s 577ms

Scenario:
Fill in and verify mix of default and non-default values in group formula
19s 925ms 23

When I follow the left menu "Systems > System Groups" 59ms

When I follow "test-formula-group" in the content area 61ms

And I follow "Formulas" in the content area 54ms

And I follow first "Testform" in the content area 235ms

And I click on "Expand All Sections" 200ms

And I enter "text1" as "testing#str" 102ms

And I enter "1" as "testing#num" 79ms

And I enter "2" as "testing#num_def" 80ms

And I enter "pw1" as "testing#pw" 102ms

And I click on "Save Formula" 86ms

Then I should see a "Formula saved" text 717ms

When I wait for "1" seconds 1s

Then the pillar data for "testing:str" should be "text1" on "sle_minion" 1s 560ms

And the pillar data for "testing:str_def" should be "defvalue" on "sle_minion" 1s 571ms

And the pillar data for "testing:str_or_null" should be "None" on "sle_minion" 1s 534ms

And the pillar data for "testing" should not contain "str_opt" on "sle_minion" 1s 573ms

And the pillar data for "testing:num" should be "1" on "sle_minion" 1s 553ms

And the pillar data for "testing:num_def" should be "2" on "sle_minion" 1s 564ms

And the pillar data for "testing:num_or_null" should be "None" on "sle_minion" 1s 540ms

And the pillar data for "testing" should not contain "num_opt" on "sle_minion" 1s 547ms

And the pillar data for "testing:pw" should be "pw1" on "sle_minion" 1s 554ms

And the pillar data for "testing:pw_or_null" should be "None" on "sle_minion" 1s 544ms

And the pillar data for "testing" should not contain "pw_opt" on "sle_minion" 1s 598ms

Scenario:
Verify that minion form inherits the values from group form
19s 269ms 16

Given I am on the Systems overview page of this "sle_minion" 1s 132ms

When I follow "Formulas" in the content area 74ms

And I follow first "Testform" in the content area 240ms

And I click on "Save Formula" 152ms

Then I should see a "Formula saved" text 529ms

And the pillar data for "testing:str" should be "text1" on "sle_minion" 1s 561ms

And the pillar data for "testing:str_def" should be "defvalue" on "sle_minion" 1s 547ms

And the pillar data for "testing:str_or_null" should be "None" on "sle_minion" 1s 560ms

And the pillar data for "testing" should not contain "str_opt" on "sle_minion" 1s 554ms

And the pillar data for "testing:num" should be "1" on "sle_minion" 1s 554ms

And the pillar data for "testing:num_def" should be "2" on "sle_minion" 1s 547ms

And the pillar data for "testing:num_or_null" should be "None" on "sle_minion" 1s 538ms

And the pillar data for "testing" should not contain "num_opt" on "sle_minion" 1s 586ms

And the pillar data for "testing:pw" should be "pw1" on "sle_minion" 1s 559ms

And the pillar data for "testing:pw_or_null" should be "None" on "sle_minion" 1s 557ms

And the pillar data for "testing" should not contain "pw_opt" on "sle_minion" 1s 570ms

Scenario:
Fill in and verify non-default values in minion formula
20s 681ms 28

When I follow "Formulas" in the content area 60ms

And I follow first "Testform" in the content area 221ms

And I click on "Expand All Sections" 233ms

And I enter "min_text1" as "testing#str" 155ms

And I enter "min_text2" as "testing#str_def" 141ms

And I enter "min_text3" as "testing#str_or_null" 111ms

And I enter "min_text4" as "testing#str_opt" 103ms

And I enter "101" as "testing#num" 79ms

And I enter "102" as "testing#num_def" 90ms

And I enter "103" as "testing#num_or_null" 73ms

And I enter "104" as "testing#num_opt" 71ms

And I enter "min_pw1" as "testing#pw" 131ms

And I enter "min_pw2" as "testing#pw_or_null" 93ms

And I enter "min_pw3" as "testing#pw_opt" 102ms

And I click on "Save Formula" 75ms

Then I should see a "Formula saved" text 688ms

When I wait for "1" seconds 1s

Then the pillar data for "testing:str" should be "min_text1" on "sle_minion" 1s 598ms

And the pillar data for "testing:str_def" should be "min_text2" on "sle_minion" 1s 546ms

And the pillar data for "testing:str_or_null" should be "min_text3" on "sle_minion" 1s 549ms

And the pillar data for "testing:str_opt" should be "min_text4" on "sle_minion" 1s 568ms

And the pillar data for "testing:num" should be "101" on "sle_minion" 1s 565ms

And the pillar data for "testing:num_def" should be "102" on "sle_minion" 1s 543ms

And the pillar data for "testing:num_or_null" should be "103" on "sle_minion" 1s 551ms

And the pillar data for "testing:num_opt" should be "104" on "sle_minion" 1s 545ms

And the pillar data for "testing:pw" should be "min_pw1" on "sle_minion" 1s 564ms

And the pillar data for "testing:pw_or_null" should be "min_pw2" on "sle_minion" 1s 621ms

And the pillar data for "testing:pw_opt" should be "min_pw3" on "sle_minion" 1s 591ms

Scenario:
Clear values in minion formula and verify that the pillar is set to group values
19s 494ms 17

When I follow "Formulas" in the content area 88ms

And I follow first "Testform" in the content area 240ms

And I click on "Clear values" and confirm alert box 367ms

And I click on "Save Formula" 66ms

Then I should see a "Formula saved" text 561ms

When I wait for "1" seconds 1s

Then the pillar data for "testing:str" should be "text1" on "sle_minion" 1s 560ms

And the pillar data for "testing:str_def" should be "defvalue" on "sle_minion" 1s 553ms

And the pillar data for "testing:str_or_null" should be "None" on "sle_minion" 1s 556ms

And the pillar data for "testing" should not contain "str_opt" on "sle_minion" 1s 539ms

And the pillar data for "testing:num" should be "1" on "sle_minion" 1s 573ms

And the pillar data for "testing:num_def" should be "2" on "sle_minion" 1s 559ms

And the pillar data for "testing:num_or_null" should be "None" on "sle_minion" 1s 558ms

And the pillar data for "testing" should not contain "num_opt" on "sle_minion" 1s 551ms

And the pillar data for "testing:pw" should be "pw1" on "sle_minion" 1s 554ms

And the pillar data for "testing:pw_or_null" should be "None" on "sle_minion" 1s 590ms

And the pillar data for "testing" should not contain "pw_opt" on "sle_minion" 1s 570ms

Scenario:
Cleanup: remove formula from minion
11s 56ms 5

When I follow "Formulas" in the content area 60ms

And I uncheck the "testform" formula 236ms

And I click on "Save" 84ms

And I wait until I see "Formula saved." text 638ms

Then the "testform" formula should be unchecked 10s 36ms

Scenario:
Cleanup: remove "test-formula-group" system group
6s 346ms 9

When I follow the left menu "Systems > System Groups" 78ms

And I follow "test-formula-group" in the content area 69ms

And I follow "Delete Group" in the content area 70ms

When I click on "Confirm Deletion" 1s 96ms

Then I should see a "System group" text 56ms

Then I should see a "test-formula-group" text 54ms

And I should see a "deleted" text 52ms

And I wait until there is no pillar refresh salt job active 3s 295ms

Then the pillar data for "testing" should be empty on "sle_minion" 1s 572ms

@skip_if_github_validation @scope_openscap
Feature:OpenSCAP audit of Salt minion 1m 23s 429ms 5 7 5

In order to audit a Salt minion
As an authorized user
I want to run an OpenSCAP scan on it

Scenario:
Log in as admin user
3s 319ms 2

Given I am authorized for the "Admin" section 1s 830ms

And I am on the Systems overview page of this "sle_minion" 1s 489ms

@Uyuni
Scenario:
Enable required repositories
749ms 1

When I enable repository "repo-oss" on this "sle_minion" without error control 749ms

@susemanager
Scenario:
Enable required repositories
< 1ms 1

When I enable repository "os_pool_repo" on this "sle_minion" without error control 0s

Scenario:
Install the OpenSCAP packages on the SLE minion
16s 808ms 2 3 1

When I refresh the metadata for "sle_minion" 844ms

And I install OpenSCAP dependencies on "sle_minion" 671ms Show Error + 
                                            
 FAIL: zypper --non-interactive install -y openscap-utils openscap-content scap-security-guide returned status code = 104.
Output:
Loading repository data...
Reading installed packages...
'openscap-content' not found in package names. Trying capabilities.
'openscap-utils' not found in package names. Trying capabilities.
'scap-security-guide' not found in package names. Trying capabilities.
 (ScriptError)
./features/support/remote_node.rb:169:in `run_local'
./features/support/remote_node.rb:117:in `run'
./features/step_definitions/command_steps.rb:978:in `/^I install packages? "([^"]*)" on this "([^"]*)"((?: without error control)?)$/'
./features/step_definitions/command_steps.rb:956:in `/^I (install|remove) OpenSCAP dependencies (on|from) "([^"]*)"$/'
features/secondary/min_salt_openscap_audit.feature:25:in `I install OpenSCAP dependencies on "sle_minion"'

And I follow "Software" in the content area 0s

And I click on "Update Package List" 0s

And I wait until event "Package List Refresh" is completed 0s

15s 292ms Show Info + 
17:47:16:000 - 17:47:17:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/Overview.do?sid=1000010023
Screenshot +

@susemanager
Scenario:
Schedule an OpenSCAP audit job on the SLE minion
< 1ms 9

When I follow "Audit" in the content area 0s

And I follow "OpenSCAP" in the content area 0s

And I follow "Schedule" in the content area 0s

And I wait at most 30 seconds until I do not see "This system does not yet have OpenSCAP scan capability." text, refreshing the page 0s

And I enter "--profile standard" as "params" 0s

And I enter "/usr/share/xml/scap/ssg/content/ssg-sle15-ds.xml" as "path" 0s

And I click on "Schedule" 0s

Then I should see a "XCCDF scan has been scheduled" text 0s

And I wait at most 500 seconds until event "OpenSCAP xccdf scanning" is completed 0s

@uyuni
Scenario:
Schedule an OpenSCAP audit job on the SLE minion
33s 266ms 3 5 1

When I follow "Audit" in the content area 70ms

And I follow "OpenSCAP" in the content area 64ms

And I follow "Schedule" in the content area 65ms

And I wait at most 30 seconds until I do not see "This system does not yet have OpenSCAP scan capability." text, refreshing the page 33s 66ms Show Error + 
                                            
 execution expired (Timeout::Error)
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/step_definitions/navigation_steps.rb:80:in `/^I wait at most (\d+) seconds until I do not see "([^"]*)" text, refreshing the page$/'
features/secondary/min_salt_openscap_audit.feature:47:in `I wait at most 30 seconds until I do not see "This system does not yet have OpenSCAP scan capability." text, refreshing the page'

And I enter "--profile standard" as "params" 0s

And I enter "/usr/share/xml/scap/ssg/content/ssg-opensuse-ds.xml" as "path" 0s

And I click on "Schedule" 0s

Then I should see a "XCCDF scan has been scheduled" text 0s

And I wait at most 500 seconds until event "OpenSCAP xccdf scanning" is completed 0s

@susemanager
Scenario:
Check results of the audit job on the minion
< 1ms 9

When I follow "Audit" in the content area 0s

And I follow "OpenSCAP" in the content area 0s

And I follow "xccdf_org.open-scap_testresult" 0s

Then I should see a "Details of XCCDF Scan" text 0s

And I should see a "profile standard" text 0s

And I should see a "XCCDF Rule Results" text 0s

When I enter "pass" as the filtered XCCDF result type 0s

And I click on the filter button 0s

Then I should see a "xccdf_org.ssgproject.content_rule_service_httpd_disabled" link 0s

@uyuni
Scenario:
Check results of the audit job on the minion
107ms 8 1

When I follow "Audit" in the content area 107ms Show Error + 
                                            
 undefined method `map' for true (NoMethodError)
./features/support/commonlib.rb:198:in `click_link_and_wait'
./features/step_definitions/navigation_steps.rb:354:in `/^I follow "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:376:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:375:in `/^I follow "([^"]*)" in the (.+)$/'
features/secondary/min_salt_openscap_audit.feature:68:in `I follow "Audit" in the content area'

And I follow "OpenSCAP" in the content area 0s

And I follow "xccdf_org.open-scap_testresult" 0s

Then I should see a "Details of XCCDF Scan" text 0s

And I should see a "profile standard" text 0s

And I should see a "XCCDF Rule Results" text 0s

When I enter "pass" as the filtered XCCDF result type 0s

And I click on the filter button 0s

Then I should see a "xccdf_org.ssgproject.content_rule_file_permissions_etc_passwd" link 0s

@susemanager
Scenario:
Create a second, almost identical, audit job
< 1ms 9

When I follow "Audit" in the content area 0s

And I follow "OpenSCAP" in the content area 0s

And I follow "Schedule" in the content area 0s

And I wait at most 30 seconds until I do not see "This system does not yet have OpenSCAP scan capability." text, refreshing the page 0s

And I enter "--profile standard" as "params" 0s

And I enter "/usr/share/xml/scap/ssg/content/ssg-sle15-ds.xml" as "path" 0s

And I click on "Schedule" 0s

Then I should see a "XCCDF scan has been scheduled" text 0s

When I wait for the OpenSCAP audit to finish 0s

@uyuni
Scenario:
Create a second, almost identical, audit job
9ms 8 1

When I follow "Audit" in the content area 9ms Show Error + 
                                            
 undefined method `map' for true (NoMethodError)
./features/support/commonlib.rb:198:in `click_link_and_wait'
./features/step_definitions/navigation_steps.rb:354:in `/^I follow "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:376:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:375:in `/^I follow "([^"]*)" in the (.+)$/'
features/secondary/min_salt_openscap_audit.feature:92:in `I follow "Audit" in the content area'

And I follow "OpenSCAP" in the content area 0s

And I follow "Schedule" in the content area 0s

And I wait at most 30 seconds until I do not see "This system does not yet have OpenSCAP scan capability." text, refreshing the page 0s

And I enter "--profile standard" as "params" 0s

And I enter "/usr/share/xml/scap/ssg/content/ssg-opensuse-ds.xml" as "path" 0s

And I click on "Schedule" 0s

Then I should see a "XCCDF scan has been scheduled" text 0s

When I wait for the OpenSCAP audit to finish 0s

Scenario:
Compare audit results
9ms 6 1

When I follow "Audit" in the content area 9ms Show Error + 
                                            
 undefined method `map' for true (NoMethodError)
./features/support/commonlib.rb:198:in `click_link_and_wait'
./features/step_definitions/navigation_steps.rb:354:in `/^I follow "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:376:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:375:in `/^I follow "([^"]*)" in the (.+)$/'
features/secondary/min_salt_openscap_audit.feature:103:in `I follow "Audit" in the content area'

And I follow "OpenSCAP" in the content area 0s

And I follow "List Scans" in the content area 0s

And I click on "Select All" 0s

And I click on "Compare" 0s

Then I should see a "XCCDF Rule Results" text 0s

And I should see a "None" text 0s

Scenario:
Cleanup: remove audit scans retention period
402ms 5 1

The browser session could not be cleaned because there is no browser available: undefined method `first' for an instance of String

When I follow the left menu "Admin > Organizations" 402ms Show Error + 
                                            
 undefined method `map' for nil (NoMethodError)
./features/step_definitions/navigation_steps.rb:609:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:475:in `/^I am authorized for the "([^"]*)" section$/'
./features/step_definitions/navigation_steps.rb:435:in `rescue in block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:428:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:421:in `each'
./features/step_definitions/navigation_steps.rb:421:in `each_with_index'
./features/step_definitions/navigation_steps.rb:421:in `/^I follow the left menu "([^"]*)"$/'
features/secondary/min_salt_openscap_audit.feature:112:in `I follow the left menu "Admin ) Organizations"'

When I follow "SUSE Test" in the content area 0s

And I follow "Configuration" in the content area 0s

And I enter "0" as "scap_retention_period" 0s

And I click on "Update Organization" 0s

Then I should see a "Organization SUSE Test was successfully updated." text 0s

Scenario:
Cleanup: delete audit results
26s 448ms 5 3 1

Given I am on the Systems overview page of this "sle_minion" 1s 122ms

When I follow "Audit" in the content area 72ms

And I follow "OpenSCAP" in the content area 65ms

And I follow "List Scans" in the content area 64ms

And I click on "Select All" 10s 1ms Show Error + 
                                            
 Unable to find button "Select All" that is not disabled (Capybara::ElementNotFound)
./features/support/commonlib.rb:184:in `click_button_and_wait'
./features/step_definitions/navigation_steps.rb:315:in `/^I click on "([^"]*)"$/'
features/secondary/min_salt_openscap_audit.feature:124:in `I click on "Select All"'

And I click on "Remove" 0s

And I click on "Confirm" 0s

Then I should see a "2 SCAP Scan(s) deleted. 0 SCAP Scan(s) retained" text 0s

15s 121ms Show Info + 
17:48:19:000 - 17:48:32:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/audit/ListScap.do?sid=1000010023&
Screenshot +

Scenario:
Cleanup: restore audit scans retention period
781ms 6

When I follow the left menu "Admin > Organizations" 119ms

When I follow "SUSE Test" in the content area 67ms

And I follow "Configuration" in the content area 63ms

And I enter "90" as "scap_retention_period" 54ms

And I click on "Update Organization" 409ms

Then I should see a "Organization SUSE Test was successfully updated." text 66ms

Scenario:
Cleanup: remove the OpenSCAP packages from the SLE minion
1s 90ms 1

When I remove OpenSCAP dependencies from "sle_minion" 1s 90ms

@Uyuni
Scenario:
Cleanup: Disable required repositories
437ms 1

When I disable repository "repo-oss" on this "sle_minion" without error control 437ms

@susemanager
Scenario:
Cleanup: Disable required repositories
< 1ms 1

When I disable repository "os_pool_repo" on this "sle_minion" without error control 0s

@flaky @scope_salt
Feature:Coexistence with user-defined states 1m 11s 596ms 4

Scenario:
Log in as org admin user
1s 672ms 1

Given I am authorized 1s 672ms

Scenario:
Create a user-defined state
11s 808ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 482ms

When I follow "States" in the content area 71ms

And I install a user-defined state for "sle_minion" on the server 3s 888ms

And I follow "Highstate" in the content area 67ms

And I click on "Show full highstate output" 256ms

And I wait for "6" seconds 6s

Then I should see a "user_defined_state" or "running as PID" text in element "highstate" 42ms

Scenario:
Trigger highstate from API
40s 178ms 3

When I schedule a highstate for "sle_minion" via API 890ms

And I wait until event "Apply highstate scheduled" is completed 38s 570ms

Then file "/tmp/test_user_defined_state" should exist on "sle_minion" 717ms

Scenario:
Cleanup: remove user-defined state and the file it created
17s 937ms 7

When I follow "States" in the content area 80ms

And I uninstall the user-defined state from the server 1s 188ms

And I uninstall the managed file from "sle_minion" 393ms

And I follow "Highstate" in the content area 66ms

And I click on "Show full highstate output" 173ms

And I wait for "6" seconds 6s

Then I should not see a "user_defined_state" text in element "highstate" 10s 34ms

@scope_salt
Feature:Verify the minion registration 30s 373ms 5

In order to validate the completeness of minion registration
I want to see minion details and installed packages

Scenario:
Log in as org admin user
1s 801ms 1

Given I am authorized 1s 801ms

Scenario:
Check the Salt entitlement
1s 610ms 2

Given I am on the Systems overview page of this "sle_minion" 1s 521ms

Then I should see a "[Salt]" text 88ms

Scenario:
Check that installed packages are visible
902ms 3

When I follow "Software" in the content area 74ms

And I follow "List / Remove" 704ms

Then I should see a "aaa_base" text 124ms

Scenario:
Check that Hardware Refresh button works on a SLES Salt minion
25s 125ms 6

When I follow "Details" in the content area 68ms

And I follow "Hardware" in the content area 81ms

And I click on "Schedule Hardware Refresh" 797ms

Then I should see a "You have successfully scheduled a hardware profile refresh" text 112ms

When I wait until event "Hardware List Refresh scheduled" is completed 21s 938ms

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "sle_minion" 2s 127ms

Scenario:
Check that Update Properties button works
933ms 4

When I follow "Details" in the content area 75ms

And I follow "Hardware" in the content area 89ms

And I click on "Update Properties" 649ms

Then I should see a "Networking properties updated." text 118ms

@sle_minion @scope_configuration_channels
Feature:Configuration state channels 1m 30s 960ms 17

In order to configure systems through Salt
I want to be able to use the state channels

Scenario:
Log in as org admin user
1s 777ms 1

Given I am authorized 1s 777ms

Scenario:
Create a state channel
1s 687ms 12

When I follow the left menu "Configuration > Channels" 122ms

And I follow "Create State Channel" 330ms

Then I should see a "New Config State Channel" text 61ms

When I enter "My State Channel" as "cofName" 67ms

And I enter "statechannel" as "cofLabel" 57ms

And I enter "This is a state channel" as "cofDescription" 67ms

And I enter "touch /root/foobar:\n cmd.run:\n - creates: /root/foobar" in the editor 4ms

And I click on "Create Config State Channel" 726ms

Then I should see a "State Channel" text 67ms

And I should see a "Channel Properties" text 60ms

And I should see a "Channel Information" text 57ms

And I should see a "Configuration Actions" text 62ms

Scenario:
Subscribe a minion to the state channel
2s 938ms 8

When I am on the Systems overview page of this "sle_minion" 1s 4ms

And I follow "Configuration" in the content area 70ms

And I follow "Manage Configuration Channels" in the content area 66ms

And I follow first "Subscribe to Channels" in the content area 61ms

And I check "My State Channel" in the list 60ms

And I click on "Continue" 57ms

And I click on "Update Channel Rankings" 1s 540ms

Then I should see a "Channel Subscriptions successfully changed for" text 77ms

Scenario:
Salt state details
1s 277ms 7

When I follow the left menu "Configuration > Channels" 116ms

And I follow "My State Channel" 498ms

Then I should see a "1 system subscribed" text 60ms

When I follow "View/Edit 'init.sls' File" 379ms

Then I should see a "Revision 1 of /init.sls from channel My State Channel" text 75ms

And I should see a "File Contents" text 72ms

And I should see a "touch /root/foobar:" text 75ms

Scenario:
Apply the new state
24s 226ms 8

When I am on the Systems overview page of this "sle_minion" 992ms

And I follow "States" in the content area 69ms

And I follow "Configuration Channels" in the content area 62ms

Then I should see a "Execute States" button 153ms

When I click on "Execute States" 52ms

Then I should see a "Applying the config channels has been scheduled" text 254ms

When I wait until event "Apply states [custom] scheduled" is completed 21s 911ms

And I wait until file "/root/foobar" exists on "sle_minion" 728ms

Scenario:
Try to remove init.sls file
1s 989ms 7

When I follow the left menu "Configuration > Channels" 103ms

And I follow "My State Channel" 472ms

And I follow "View/Edit 'init.sls' File" 367ms

When I follow "Delete" 321ms

And I click on "Delete Configuration Revision" 572ms

Then I should see a "Cannot delete the only revision for the init.sls file" text 79ms

And I should see a "Revision 1 of /init.sls from channel My State Channel" text 73ms

Scenario:
Cleanup: remove the state channel and the file
1s 393ms 7

When I follow the left menu "Configuration > Channels" 63ms

And I follow "My State Channel" 478ms

And I follow "Delete Channel" 291ms

Then I should see a "Are you sure you want to delete this config channel?" text 52ms

When I click on "Delete Config Channel" 59ms

Then I should see a "Channel 'My State Channel' has been deleted." text 51ms

And I remove "/root/foobar" from "sle_minion" 396ms

Scenario:
Create the 1st state channel
1s 645ms 12

When I follow the left menu "Configuration > Channels" 60ms

And I follow "Create State Channel" 347ms

Then I should see a "New Config State Channel" text 52ms

When I enter "My State Channel" as "cofName" 70ms

And I enter "statechannel" as "cofLabel" 58ms

And I enter "This is a state channel" as "cofDescription" 67ms

And I enter "touch /root/statechannel:\n cmd.run:\n - creates: /root/statechannel" in the editor 4ms

And I click on "Create Config State Channel" 744ms

Then I should see a "State Channel" text 60ms

And I should see a "Channel Properties" text 58ms

And I should see a "Channel Information" text 58ms

And I should see a "Configuration Actions" text 61ms

Scenario:
Create the 2nd state channel with same name
1s 543ms 12

When I follow the left menu "Configuration > Channels" 60ms

And I follow "Create State Channel" 294ms

Then I should see a "New Config State Channel" text 54ms

When I enter "My State Channel" as "cofName" 59ms

And I enter "statechannel2" as "cofLabel" 55ms

And I enter "This is a state channel" as "cofDescription" 63ms

And I enter "touch /root/statechannel2:\n cmd.run:\n - creates: /root/statechannel2" in the editor 3ms

And I click on "Create Config State Channel" 712ms

Then I should see a "State Channel" text 62ms

And I should see a "Channel Properties" text 59ms

And I should see a "Channel Information" text 58ms

And I should see a "Configuration Actions" text 58ms

Scenario:
Create the 3rd state channel with spacecmd
9s 289ms 9

When I create channel "statechannel3" from spacecmd of type "state" 1s 557ms

And I follow the left menu "Configuration > Channels" 60ms

Then I should see a "statechannel3" text 61ms

When I update init.sls from spacecmd with content "touch /tmp/statechannel3:\n cmd.run:\n - creates: /tmp/statechannel3" for channel "statechannel3" 2s 559ms

And I get "/init.sls" file details for channel "statechannel3" via spacecmd 1s 254ms

Then I should see "Revision: 2" in the output < 1ms

When I update init.sls from spacecmd with content "touch /root/statechannel3:\n cmd.run:\n - creates: /root/statechannel3" for channel "statechannel3" and revision "100" 2s 533ms

And I get "/init.sls" file details for channel "statechannel3" via spacecmd 1s 262ms

Then I should see "Revision: 100" in the output < 1ms

Scenario:
Subscribe a minion to 1st and 2nd state channels
2s 305ms 15

When I am on the Systems overview page of this "sle_minion" 1s 67ms

And I follow "States" in the content area 71ms

And I follow "Configuration Channels" in the content area 76ms

And I click on "Search" in element "search-row" 70ms

Then I should see a "My State Channel" text 167ms

And I should see a "statechannel" text 69ms

And I should see a "statechannel2" text 68ms

When I check "statechannel-cbox" 86ms

And I check "statechannel2-cbox" 80ms

And I click on "Save Changes" 63ms

And I wait until I see "Edit Channel Ranks" text 56ms

Then I should see a "My State Channel (statechannel)" text 56ms

And I should see a "My State Channel (statechannel2)" text 58ms

When I click on "Confirm" 60ms

Then I should see a "State assignments have been saved." text 251ms

Scenario:
Apply the Configuration channel state
23s 717ms 9

When I follow "States" in the content area 57ms

And I follow "Configuration Channels" in the content area 72ms

And I click on "Search" in element "search-row" 58ms

And I wait until I see "Execute States" text 62ms

And I click on "Execute States" 61ms

Then I should see a "Applying the config channels has been scheduled" text 268ms

And I wait until event "Apply states [custom] scheduled" is completed 22s 34ms

And I wait until file "/root/statechannel" exists on "sle_minion" 702ms

And I wait until file "/root/statechannel2" exists on "sle_minion" 399ms

Scenario:
Subscribe a minion to the 3rd state channel
1s 165ms 12

When I follow "States" in the content area 62ms

And I follow "Configuration Channels" in the content area 55ms

Then I should see a "My State Channel" text 275ms

And I should see a "statechannel3" text 63ms

When I check "statechannel3-cbox" 88ms

And I click on "Save Changes" 67ms

And I wait until I see "Edit Channel Ranks" text 56ms

And I should see a "My State Channel (statechannel)" text 61ms

And I should see a "My State Channel (statechannel2)" text 57ms

And I should see a "statechannel3 (statechannel3)" text 59ms

When I click on "Confirm" 58ms

Then I should see a "State assignments have been saved." text 256ms

Scenario:
Apply the Configuration channel state with spacecmd
10s 717ms 2

When I schedule apply configchannels for "sle_minion" 2s 707ms

And I wait until file "/root/statechannel3" exists on "sle_minion" 8s 9ms

Scenario:
Cleanup: remove the 1st state channel and the deployed file
1s 528ms 7

When I follow the left menu "Configuration > Channels" 120ms

And I follow first "My State Channel" 534ms

And I follow "Delete Channel" 290ms

Then I should see a "Are you sure you want to delete this config channel?" text 52ms

When I click on "Delete Config Channel" 60ms

Then I should see a "Channel 'My State Channel' has been deleted." text 66ms

When I remove "/root/statechannel" from "sle_minion" 402ms

Scenario:
Cleanup: remove the 2nd state channel and the deployed file
1s 893ms 7

When I follow the left menu "Configuration > Channels" 66ms

And I follow first "My State Channel" 477ms

And I follow "Delete Channel" 283ms

Then I should see a "Are you sure you want to delete this config channel?" text 52ms

When I click on "Delete Config Channel" 548ms

Then I should see a "Channel 'My State Channel' has been deleted." text 70ms

When I remove "/root/statechannel2" from "sle_minion" 394ms

Scenario:
Cleanup: remove the 3rd state channel and the deployed file
1s 863ms 7

When I follow the left menu "Configuration > Channels" 63ms

And I follow first "statechannel3" 537ms

And I follow "Delete Channel" 287ms

Then I should see a "Are you sure you want to delete this config channel?" text 58ms

When I click on "Delete Config Channel" 472ms

Then I should see a "Channel 'statechannel3' has been deleted." text 49ms

When I remove "/root/statechannel3" from "sle_minion" 394ms

Feature:Configuration state channels via API 2s 361ms 3

Scenario:
Create a state channel via API
795ms 3

When I create state channel "statechannel1" via API 412ms

And I call configchannel.get_file_revision() with file "/init.sls", revision "1" and channel "statechannel1" via API 383ms

Then I should get file contents "" < 1ms

Scenario:
Create a state channel with contents via API
784ms 3

When I create state channel "statechannel2" containing "touch /root/foobar:\n cmd.run:\n - creates: /root/foobar" via API 404ms

And I call configchannel.get_file_revision() with file "/init.sls", revision "1" and channel "statechannel2" via API 380ms

Then I should get file contents "touch /root/foobar:\n cmd.run:\n - creates: /root/foobar" < 1ms

Scenario:
Cleanup: remove state channels via API
781ms 2

Then I delete channel "statechannel1" via API without error control 411ms

And I delete channel "statechannel2" via API without error control 369ms

@skip_if_github_validation @scope_salt
Feature:System package list is updated if packages are manually installed or removed 1m 16s 329ms 7

Scenario:
Pre-requisite: install milkyway-dummy-1.0 package
3s 273ms 3

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 768ms

And I refresh the metadata for "sle_minion" 847ms

And I install old package "milkyway-dummy-1.0" on this "sle_minion" without error control 1s 656ms

Scenario:
Pre-requisite: refresh package list and check installed packages on SLE minion client
10s 239ms 3

When I refresh packages list via spacecmd on "sle_minion" 2s 727ms

And I wait until refresh package list on "sle_minion" is finished 5s 18ms

Then spacecmd should show packages "milkyway-dummy-1.0" installed on "sle_minion" 2s 493ms

Scenario:
Log in as org admin user
1s 732ms 1

Given I am authorized for the "Admin" section 1s 732ms

Scenario:
Pre-requisite: ensure the errata cache is computed before package list tests
19s 511ms 11

Given I am on the Systems overview page of this "sle_minion" 1s 625ms

When I follow "Software" in the content area 71ms

And I follow "List / Remove" in the content area 63ms

And I enter "milkyway-dummy" as the filtered package name 197ms

And I click on the filter button until page does contain "milkyway-dummy-1.0" text 11s 123ms

And I follow the left menu "Admin > Task Schedules" 129ms

And I follow "errata-cache-default" 1s 164ms

And I follow "errata-cache-bunch" 1s 350ms

And I click on "Single Run Schedule" 1s 537ms

Then I should see a "bunch was scheduled" text 266ms

When I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 1s 981ms

Scenario:
Remove manually a package on a minion
24s 548ms 8

Given I am on the Systems overview page of this "sle_minion" 975ms

When I follow "Software" in the content area 73ms

And I follow "List / Remove" 742ms

And I enter "milkyway-dummy" as the filtered package name 151ms

And I click on the filter button 811ms

Then I should see a "milkyway-dummy" text 70ms

When I remove package "milkyway-dummy" from this "sle_minion" 1s 856ms

And I click on the filter button until page does not contain "milkyway-dummy" text 19s 867ms

Scenario:
Install manually a package on a minion
13s 920ms 7

When I follow "Software" in the content area 73ms

And I follow "List / Remove" 673ms

And I enter "milkyway-dummy" as the filtered package name 167ms

And I click on the filter button 797ms

Then I should not see a "milkyway-dummy" text 83ms

When I install package "milkyway-dummy" on this "sle_minion" 2s 61ms

And I click on the filter button until page does not contain "milkyway-dummy" text 10s 63ms

Scenario:
Cleanup: remove milkyway-dummy packages from SLES minion
3s 102ms 3

When I disable repository "test_repo_rpm_pool" on this "sle_minion" 776ms

And I remove package "milkyway-dummy" from this "sle_minion" without error control 1s 561ms

And I refresh the metadata for "sle_minion" 765ms

@sle_minion @scope_monitoring @skip_if_github_validation @under_debugging
Feature:Monitor MLM environment with Prometheus on a SLE Salt minion 11m 9s 518ms 6 3

In order to monitor Uyuni server
As an authorized user
I want to enable Prometheus exporters

Scenario:
Log in as org admin user
1s 616ms 1

Given I am authorized 1s 616ms

Scenario:
Apply Prometheus and Prometheus exporter formulas
2s 731ms 8

Given I am on the Systems overview page of this "sle_minion" 1s 602ms

When I follow "Formulas" in the content area 73ms

And I should see a "Choose formulas:" text 56ms

And I should see a "Monitoring" text 187ms

And I check the "prometheus" formula 77ms

And I check the "prometheus-exporters" formula 69ms

And I click on "Save" 65ms

Then I wait until I see "Formula saved" text 599ms

Scenario:
Configure Prometheus formula
1s 314ms 7

When I follow "Formulas" in the content area 62ms

And I follow "Prometheus" in the content area 237ms

And I click on "Expand All Sections" 171ms

And I enter "admin" as "Username" 117ms

And I enter "admin" as "Password" 80ms

And I click on "Save Formula" 79ms

Then I should see a "Formula saved" text 565ms

Scenario:
Configure Prometheus exporter formula
2s 215ms 9

When I follow "Formulas" in the content area 60ms

And I follow "Prometheus Exporters" in the content area 272ms

And I click on "Expand All Sections" 210ms

And I should see a "Enable and configure Prometheus exporters for managed systems." text 105ms

And I check "node" exporter 45ms

And I check "apache" exporter 84ms

And I check "postgres" exporter 90ms

And I click on "Save" 63ms

Then I should see a "Formula saved" text 1s 281ms

Scenario:
Apply highstate for Prometheus exporters
1m 30s 553ms 4 1

Event Details: Failed to apply state(s): highstate ---------- ID: sync_states Function: saltutil.sync_states Name: sync_states Result: true Comment: No updates to sync Started: 17:55:27.961564 Duration: 238.128 SLS: util.syncstates Changed: {} ---------- ID: mgr_absent_ca_package Function: pkg.removed Name: rhn-org-trusted-ssl-cert Result: true Comment: All specified packages are already absent Started: 17:55:33.225322 Duration: 11.133 SLS: certs Changed: {} ---------- ID: mgr_ca_cert Function: file.managed Name: /etc/pki/trust/anchors/RHN-ORG-TRUSTED-SSL-CERT Result: true Comment: File /etc/pki/trust/anchors/RHN-ORG-TRUSTED-SSL-CERT is in the correct state Started: 17:55:33.239354 Duration: 47.451 SLS: certs Changed: {} ---------- ID: update-ca-certificates Function: cmd.run Name: /usr/sbin/update-ca-certificates Result: true Comment: State was not run because none of the onchanges reqs changed Started: 17:55:33.288490 Duration: 0.007 SLS: certs Changed: {} ---------- ID: mgr_proxy_ca_cert_symlink Function: file.symlink Name: /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT Result: true Comment: onlyif condition is false Started: 17:55:33.288635 Duration: 636.366 SLS: certs Changed: {} ---------- ID: mgr_deploy_tools_uyuni_key Function: file.managed Name: /etc/pki/rpm-gpg/uyuni-tools-gpg-pubkey-0d20833e.key Result: true Comment: File /etc/pki/rpm-gpg/uyuni-tools-gpg-pubkey-0d20833e.key is in the correct state Started: 17:55:33.925158 Duration: 47.523 SLS: channels.gpg-keys Changed: {} ---------- ID: mgr_deploy_suse_addon_key Function: file.managed Name: /etc/pki/rpm-gpg/suse-addon-97a636db0bad8ecc.key Result: true Comment: File /etc/pki/rpm-gpg/suse-addon-97a636db0bad8ecc.key is in the correct state Started: 17:55:33.972819 Duration: 40.987 SLS: channels.gpg-keys Changed: {} ---------- ID: mgr_deploy_suse16_gpg_key Function: file.managed Name: /etc/pki/rpm-gpg/suse16-gpg-pubkey-09d9ea69.key Result: true Comment: File /etc/pki/rpm-gpg/suse16-gpg-pubkey-09d9ea69.key is in the correct state Started: 17:55:34.013965 Duration: 40.546 SLS: channels.gpg-keys Changed: {} ---------- ID: file_///etc/pki/rpm-gpg/uyuni-tools-gpg-pubkey-0d20833e.key Function: mgrcompat.module_run Name: pkg.add_repo_key Result: true Comment: Module function pkg.add_repo_key executed Started: 17:55:34.054692 Duration: 25.756 SLS: channels.gpg-keys Changed: ret: true ---------- ID: file_///usr/lib/rpm/gnupg/keys/gpg-pubkey-29b700a4-62b07e22.asc Function: mgrcompat.module_run Name: pkg.add_repo_key Result: true Comment: Module function pkg.add_repo_key executed Started: 17:55:34.080597 Duration: 25.954 SLS: channels.gpg-keys Changed: ret: true ---------- ID: mgrchannels_repo Function: file.managed Name: /etc/zypp/repos.d/susemanager:channels.repo Result: true Comment: File /etc/zypp/repos.d/susemanager:channels.repo is in the correct state Started: 17:55:34.106884 Duration: 149.832 SLS: channels Changed: {} ---------- ID: pkg_installed Function: pkg.installed Name: pkg_installed Result: true Comment: No packages to install provided Started: 17:55:34.257431 Duration: 0.763 SLS: packages.packages_09880fab54db27be7d71c29a69aa9ddd Changed: {} ---------- ID: pkg_removed Function: pkg.removed Name: pkg_removed Result: true Comment: All specified packages are already absent Started: 17:55:34.258424 Duration: 12.73 SLS: packages.packages_09880fab54db27be7d71c29a69aa9ddd Changed: {} ---------- ID: pkg_latest Function: pkg.latest Name: pkg_latest Result: true Comment: No packages to install provided Started: 17:55:34.271437 Duration: 0.614 SLS: packages.packages_09880fab54db27be7d71c29a69aa9ddd Changed: {} ---------- ID: os_not_supported Function: test.fail_without_changes Name: OS not supported! Result: false Comment: Failure! Started: 17:55:34.272133 Duration: 0.762 SLS: prometheus Changed: {} ---------- ID: exporter_exporter Function: service.dead Name: prometheus-exporter_exporter Result: true Comment: The named service prometheus-exporter_exporter is not available Started: 17:55:34.273004 Duration: 19.782 SLS: prometheus-exporters Changed: {} ---------- ID: node_exporter Function: pkg.installed Name: golang-github-prometheus-node_exporter Result: true Comment: 1 targeted package was installed/updated. Started: 17:55:34.292932 Duration: 4137.902 SLS: prometheus-exporters Changed: golang-github-prometheus-node_exporter: old: '' new: 1.10.2-2.1 system-user-prometheus: old: '' new: 1.0.0-2.2 ---------- ID: node_exporter Function: file.managed Name: /etc/sysconfig/prometheus-node_exporter Result: true Comment: File /etc/sysconfig/prometheus-node_exporter updated Started: 17:55:38.434725 Duration: 128.293 SLS: prometheus-exporters Changed: diff: "--- \n+++ \n@@ -1,11 +1,9 @@\n-## Path: Network/Monitors/Prometheus/node_exporter\n-## Description: Prometheus node exporter startup parameters\n\ -## Type: string\n-## Default: ''\n+## Path: Applications/NodeExporter\n+## Description: Prometheus exporter for machine metrics\n\ +## Type: string()\n+## Default: \"\"\n+## ServiceRestart: prometheus-node_exporter\n #\n-# Additional arguments for the node_exporter.\n\ -# Please call: /usr/bin/node_exporter --help\n-# for a full list of possible options. \n-# Note: Please keep the list on one line, of possible.\n+#\ \ Arguments for running prometheus-node_exporter\n #\n-ARGS=''\n+ARGS=--collector.systemd --web.listen-address=:9100\n" ---------- ID: node_exporter Function: service.running Name: prometheus-node_exporter Result: true Comment: Service prometheus-node_exporter has been enabled, and is running Started: 17:55:43.305898 Duration: 535.174 SLS: prometheus-exporters Changed: prometheus-node_exporter: true ---------- ID: apache_exporter Function: pkg.installed Name: golang-github-lusitaniae-apache_exporter Result: true Comment: 1 targeted package was installed/updated. Started: 17:55:43.844230 Duration: 2937.782 SLS: prometheus-exporters Changed: golang-github-lusitaniae-apache_exporter: old: '' new: 1.0.10-3.2 ---------- ID: apache_exporter Function: file.managed Name: /etc/sysconfig/prometheus-apache_exporter Result: true Comment: File /etc/sysconfig/prometheus-apache_exporter updated Started: 17:55:46.786280 Duration: 97.468 SLS: prometheus-exporters Changed: diff: New file mode: '0644' ---------- ID: apache_exporter Function: service.running Name: prometheus-apache_exporter Result: true Comment: Service prometheus-apache_exporter has been enabled, and is running Started: 17:55:51.580715 Duration: 538.043 SLS: prometheus-exporters Changed: prometheus-apache_exporter: true ---------- ID: postgres_exporter Function: pkg.installed Name: prometheus-postgres_exporter Result: true Comment: 1 targeted package was installed/updated. Started: 17:55:52.120233 Duration: 2971.077 SLS: prometheus-exporters Changed: prometheus-postgres_exporter: old: '' new: 0.10.1-5.2 ---------- ID: postgres_exporter Function: file.managed Name: /etc/systemd/system/prometheus-postgres_exporter.service.d/60-suse-salt-formula.conf Result: true Comment: File /etc/systemd/system/prometheus-postgres_exporter.service.d/60-suse-salt-formula.conf updated Started: 17:55:55.094981 Duration: 111.916 SLS: prometheus-exporters Changed: diff: New file mode: '0644' ---------- ID: postgres_exporter Function: file.managed Name: /etc/postgres_exporter/pg_passwd Result: true Comment: File /etc/postgres_exporter/pg_passwd updated Started: 17:55:55.207237 Duration: 94.552 SLS: prometheus-exporters Changed: diff: New file user: prometheus ---------- ID: postgres_exporter Function: module.run Name: service.systemctl_reload Result: true Comment: Module function service.systemctl_reload executed Started: 17:55:55.303648 Duration: 420.648 SLS: prometheus-exporters Changed: ret: true ---------- ID: postgres_exporter Function: service.running Name: prometheus-postgres_exporter Result: true Comment: Service prometheus-postgres_exporter has been enabled, and is running Started: 17:56:00.323201 Duration: 544.871 SLS: prometheus-exporters Changed: prometheus-postgres_exporter: true ---------- ID: disable_spacewalksd Function: service.dead Name: rhnsd Result: true Comment: The named service rhnsd is not available Started: 17:56:00.868240 Duration: 12.417 SLS: services.salt-minion Changed: {} ---------- ID: disable_spacewalk-update-status Function: service.dead Name: spacewalk-update-status Result: true Comment: The named service spacewalk-update-status is not available Started: 17:56:00.880797 Duration: 12.297 SLS: services.salt-minion Changed: {} ---------- ID: disable_osad Function: service.dead Name: osad Result: true Comment: The named service osad is not available Started: 17:56:00.893237 Duration: 12.365 SLS: services.salt-minion Changed: {} ---------- ID: remove_traditional_stack_all Function: pkg.removed Name: remove_traditional_stack_all Result: true Comment: All specified packages are already absent Started: 17:56:00.907221 Duration: 12.054 SLS: services.salt-minion Changed: {} ---------- ID: remove_traditional_stack Function: pkg.removed Name: remove_traditional_stack Result: true Comment: All specified packages are already absent Started: 17:56:00.919423 Duration: 258.226 SLS: services.salt-minion Changed: {} ---------- ID: /etc/sysconfig/rhn/systemid Function: file.managed Name: /etc/sysconfig/rhn/systemid Result: true Comment: File /etc/sysconfig/rhn/systemid exists with proper permissions. No changes made. Started: 17:56:01.177778 Duration: 1.548 SLS: services.salt-minion Changed: {} ---------- ID: mgr_salt_minion_inst Function: pkg.installed Name: venv-salt-minion Result: true Comment: All specified packages are already installed Started: 17:56:01.179848 Duration: 10.729 SLS: services.salt-minion Changed: {} ---------- ID: /etc/venv-salt-minion/minion.d/susemanager.conf Function: file.managed Name: /etc/venv-salt-minion/minion.d/susemanager.conf Result: true Comment: File /etc/venv-salt-minion/minion.d/susemanager.conf is in the correct state Started: 17:56:01.190809 Duration: 156.565 SLS: services.salt-minion Changed: {} ---------- ID: mgr_salt_minion_run Function: service.running Name: venv-salt-minion Result: true Comment: The service venv-salt-minion is already running Started: 17:56:01.347504 Duration: 35.487 SLS: services.salt-minion Changed: {}

When I follow "States" in the content area 69ms

And I click on "Apply Highstate" 60ms

Then I should see a "Applying the highstate has been scheduled." text 433ms

And I wait until event "Apply highstate scheduled" is completed 1m 14s 614ms Show Error + 
                                            
 unknown error - Event failed (SystemCallError)
./features/step_definitions/navigation_steps.rb:107:in `block (2 levels) in (top (required))'
./features/support/commonlib.rb:106:in `block in repeat_until_timeout'
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/step_definitions/navigation_steps.rb:99:in `/^I wait at most (\d+) seconds until the event is completed, refreshing the page$/'
./features/step_definitions/common_steps.rb:157:in `/^I wait (\d+) seconds until the event is picked up and (\d+) seconds until the event "([^"]*)" is completed$/'
./features/step_definitions/common_steps.rb:174:in `/^I wait at most (\d+) seconds until event "([^"]*)" is completed$/'
./features/step_definitions/common_steps.rb:151:in `/^I wait until event "([^"]*)" is completed$/'
features/secondary/min_monitoring.feature:52:in `I wait until event "Apply highstate scheduled" is completed'

15s 375ms Show Info + 
17:55:21:000 - 17:56:37:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010023&aid=409
Screenshot +

Scenario:
Wait for services
4m 25s 298ms 1 3 1

When I wait until "prometheus" service is active on "sle_minion" 4m 10s Show Error + 
                                            
 execution expired (Timeout::Error)
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/support/remote_node.rb:186:in `run_until_ok'
./features/step_definitions/command_steps.rb:304:in `/^I wait until "([^"]*)" service is active on "([^"]*)"$/'
features/secondary/min_monitoring.feature:55:in `I wait until "prometheus" service is active on "sle_minion"'

And I wait until "node" exporter service is active on "sle_minion" 0s

And I wait until "apache" exporter service is active on "sle_minion" 0s

And I wait until "postgres" exporter service is active on "sle_minion" 0s

15s 298ms Show Info + 
17:56:52:000 - 18:01:02:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010023&aid=409
Screenshot +

Scenario:
Visit monitoring endpoints on the minion
4m 25s 298ms 1 3 1

When I visit "Prometheus" endpoint of this "sle_minion" 4m 10s Show Error + 
                                            
 execution expired (Timeout::Error)
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/support/remote_node.rb:186:in `run_until_ok'
./features/step_definitions/navigation_steps.rb:1187:in `/^I visit "([^"]*)" endpoint of this "([^"]*)"$/'
features/secondary/min_monitoring.feature:62:in `I visit "Prometheus" endpoint of this "sle_minion"'

And I visit "Prometheus node exporter" endpoint of this "sle_minion" 0s

And I visit "Prometheus apache exporter" endpoint of this "sle_minion" 0s

And I visit "Prometheus postgres exporter" endpoint of this "sle_minion" 0s

15s 298ms Show Info + 
18:01:18:000 - 18:05:28:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010023&aid=409
Screenshot +

Scenario:
Cleanup: undo Prometheus and Prometheus exporter formulas
1s 418ms 5

When I follow "Formulas" in the content area 76ms

And I uncheck the "prometheus" formula 225ms

And I uncheck the "prometheus-exporters" formula 68ms

And I click on "Save" 63ms

Then I wait until I see "Formula saved" text 984ms

Scenario:
Cleanup: apply highstate after test monitoring
39s 71ms 4

And I follow "States" in the content area 73ms

And I click on "Apply Highstate" 62ms

Then I should see a "Applying the highstate has been scheduled." text 440ms

And I wait until event "Apply highstate scheduled" is completed 38s 494ms

@skip_if_github_validation @no_mirror
Feature:SCC user credentials in the Setup Wizard < 1ms 7

As a systems administrator
In order to manage organization's access to SUSE Customer Service
I want to create, edit, and delete its credentials

Scenario:
Log in as admin user
< 1ms 1

Given I am authorized for the "Admin" section 0s

Scenario:
Enter some invalid organization credentials
< 1ms 7

When I follow the left menu "Admin > Setup Wizard > Organization Credentials" 0s

And I ask to add new credentials 0s

And I enter "SCC user" as "edit-user" 0s

And I enter "SCC password" as "edit-password" 0s

And I click on "Save" 0s

Then I should see a "SCC user" text 0s

And the credentials for "SCC user" should be invalid 0s

Scenario:
Make the credentials primary
< 1ms 3

When I follow the left menu "Admin > Setup Wizard > Organization Credentials" 0s

And I make the credentials for "SCC user" primary 0s

Then the credentials for "SCC user" should be primary 0s

Scenario:
Check the associated subscription list
< 1ms 4

When I follow the left menu "Admin > Setup Wizard > Organization Credentials" 0s

And I view the subscription list for "SCC user" 0s

And I wait until I see "No subscriptions available" text 0s

And I click on "Close" 0s

Scenario:
Enter duplicate SCC credentials
< 1ms 14

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 "invalidname" as "edit-user" 0s

And I enter "invalidpw" as "edit-password" 0s

And I click on "Save" 0s

Then the credentials for "invalidname" should be invalid 0s

When I ask to add new credentials 0s

And I enter "invalidname" as "edit-user" 0s

And I enter "invalidpw" as "edit-password" 0s

And I click on "Save" 0s

Then I should see a "Credentials with this username already exist" text 0s

When I click on "Cancel" 0s

Then the credentials for "invalidname" should be invalid 0s

Scenario:
Edit credentials
< 1ms 11

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 edit the credentials for "invalidname" 0s

And I enter "SCC user" as "edit-user" 0s

And I enter "geekogeeko" as "edit-password" 0s

And I click on "Save" 0s

Then I should see a "Credentials with this username already exist" text 0s

When I enter "invalidgeeko" as "edit-user" 0s

And I click on "Save" 0s

Then I should see a "invalidgeeko" text 0s

And the credentials for "invalidgeeko" should be invalid 0s

Scenario:
Cleanup: delete the new organization credentials
< 1ms 9

When I follow the left menu "Admin > Setup Wizard > Organization Credentials" 0s

And I wait for the trash icon to appear for "SCC user" 0s

And I ask to delete the credentials for "SCC user" 0s

And I click on "Delete" in "Are you sure you want to delete these credentials?" modal 0s

Then I wait until I do not see "SCC user" text 0s

When I wait for the trash icon to appear for "invalidgeeko" 0s

And I ask to delete the credentials for "invalidgeeko" 0s

And I click on "Delete" in "Are you sure you want to delete these credentials?" modal 0s

Then I wait until I do not see "invalidgeeko" text 0s

@scope_cve_audit
Feature:Support for new CVE-ID syntax 7s 560ms 4

Scenario:
Log in as org admin user
1s 610ms 1

Given I am authorized 1s 610ms

Scenario:
Check perseus-dummy-7891 patches
1s 257ms 7

When I follow the left menu "Patches > Patch List > All" 193ms

And I enter "dummy" as the filtered synopsis 42ms

And I click on the filter button 490ms

And I follow "perseus-dummy-7891" 440ms

Then I should see a "perseus-dummy-7891 - Security Advisory" text 67ms

And I should see a "CVE-1999-12345" link 11ms

And I should see a "CVE-1999-99781" link 11ms

Scenario:
Check local metadata for long CVE IDs
4s 349ms 5

When I refresh the metadata for "sle_minion" 1s 85ms

Then I should have 'reference.*id="CVE-1999-12345' in the patch metadata for "sle_minion" 802ms

And I should have 'reference.*id="CVE-1999-99781' in the patch metadata for "sle_minion" 810ms

And I should have 'reference.*http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-1999-12345' in the patch metadata for "sle_minion" 815ms

And I should have 'reference.*http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-1999-99781' in the patch metadata for "sle_minion" 835ms

Scenario:
Search for CVE ID with the new format
343ms 5

When I follow the left menu "Patches > Advanced Search" 90ms

When I enter "CVE-1999-12345" as "search_string" in the content area 78ms

And I click on "Search" 74ms

Then I should see a "Advanced Search" text 77ms

And I should see a "perseus-dummy-7891" link in the content area 22ms

@scope_onboarding
Feature:Display patches 1m 19s 592ms 8

Scenario:
Log in as org admin user
1s 596ms 1

Given I am authorized for the "Admin" section 1s 596ms

Scenario:
Pre-require: enable old packages to fake a possible installation
10s 212ms 10

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 776ms

And I refresh the metadata for "sle_minion" 776ms

And I install old package "andromeda-dummy-1.0" on this "sle_minion" 1s 607ms

And I install old package "virgo-dummy-1.0" on this "sle_minion" 1s 598ms

When I follow the left menu "Admin > Task Schedules" 124ms

And I follow "errata-cache-default" 1s 184ms

And I follow "errata-cache-bunch" 288ms

And I click on "Single Run Schedule" 1s 536ms

Then I should see a "bunch was scheduled" text 269ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 2s 48ms

Scenario:
Check all patches exist
44s 322ms 8

When I follow the left menu "Patches > Patch List > Relevant" 215ms

Then I should see an update in the list 32ms

When I wait until I see "andromeda-dummy" text, refreshing the page 43s 571ms

Then I should see a "andromeda-dummy-6789" link 11ms

When I enter "virgo-dummy" as the filtered synopsis 51ms

And I click on the filter button 362ms

And I wait until I see "virgo-dummy" text 64ms

Then I should see a "virgo-dummy-3456" link 12ms

Scenario:
Check SLES release 6789 patches
816ms 6

When I follow the left menu "Patches > Patch List > Relevant" 85ms

And I follow "andromeda-dummy-6789" 522ms

Then I should see a "andromeda-dummy-6789 - Bug Fix Advisory" text 70ms

And I should see a "Test update for andromeda-dummy" text 64ms

And I should see a "Fake-RPM-SUSE-Channel" link 11ms

And I should see a "reboot_suggested" text 62ms

Scenario:
Check packages of SLES release 6789 patches
1s 346ms 6

When I follow the left menu "Patches > Patch List > Relevant" 69ms

And I follow "andromeda-dummy-6789" 499ms

And I follow "Packages" 695ms

Then I should see a "Fake-RPM-SUSE-Channel" link 8ms

And I should see a "sha512:19940cc4a9f0d38a038a4455b0f1cf1290c4a4296b27f5a62f4aae60585ac6e2677e88c3c3127d487116ed8d9b1787379e23aafac46bc14408864926bedee693" text 58ms

And I should see a "andromeda-dummy-2.0-1.1-noarch" link 15ms

Scenario:
Check relevant patches for this client
11s 546ms 8

Given I am on the Systems overview page of this "sle_minion" 1s 31ms

When I follow "Software" in the content area 73ms

And I follow "Patches" in the content area 64ms

Then I should see a "Relevant Patches" text 83ms

When I enter "dummy" as the filtered synopsis 46ms

And I click on the filter button 10s 99ms

Then I should see a "Test update for andromeda-dummy" text 73ms

And I should see a "Test update for virgo-dummy" text 73ms

Scenario:
Cleanup: regenerate search index for later tests
5s 91ms 1

Search by hostname: uyuni-master-suse-minion
[{"last_boot"=>"2026-03-06T13:36:50Z", "name"=>"uyuni-master-suse-minion.sumaci.aws", "id"=>1000010023, "last_checkin"=>"2026-03-06T17:07:34Z"}]

When I clean the search index on the server 5s 91ms

Scenario:
Cleanup: remove old packages
4s 659ms 4

When I disable repository "test_repo_rpm_pool" on this "sle_minion" without error control 760ms

And I refresh the metadata for "sle_minion" 822ms

And I remove package "andromeda-dummy" from this "sle_minion" without error control 1s 540ms

And I remove package "virgo-dummy" from this "sle_minion" without error control 1s 535ms

@sle_minion @susemanager @scope_project_lotus
Feature:Project Lotus < 1ms 12

In order to manage Program Temporary Fixes (PTFs)
As an authorized user
I want to be able to install and remove them through the WebUI

Scenario:
Log in as org admin user
< 1ms 1

Given I am authorized 0s

Scenario:
Pre-requisite: Create custom channel for PTFs
< 1ms 9

When I follow the left menu "Software > Manage > Channels" 0s

And I follow "Create Channel" 0s

And I enter "Custom Channel for SLES15SP7 PTFs" as "Channel Name" 0s

And I enter "sles15sp7-ptfs" as "Channel Label" 0s

And I select the parent channel for the "sle_minion" from "Parent Channel" 0s

And I enter "Custom channel for PTFs" as "Channel Summary" 0s

And I uncheck "gpg_check" 0s

And I click on "Create Channel" 0s

Then I should see a "Custom Channel for SLES15SP7 PTFs" text 0s

Scenario:
Pre-requisite: Create custom repository for PTFs
< 1ms 7

When I follow the left menu "Software > Manage > Repositories" 0s

And I follow "Create Repository" 0s

And I enter "sles15sp7_ptf_repo" as "label" 0s

And I enter "http://updates.suse.de/PTF/Release/A127499/SLES/15.7/x86_64/ptf/" as "url" 0s

And I uncheck "metadataSigned" 0s

And I click on "Create Repository" 0s

Then I should see a "Repository created successfully" text 0s

Scenario:
Pre-requisite: Add PTF repository to custom channel
< 1ms 6

When I follow the left menu "Software > Manage > Channels" 0s

And I follow "Custom Channel for SLES15SP7 PTFs" 0s

And I follow "Repositories" in the content area 0s

And I select the "sles15sp7_ptf_repo" repo 0s

And I click on "Save Repositories" 0s

Then I should see a "repository information was successfully updated" text 0s

Scenario:
Pre-requisite: Sync PTF repository
< 1ms 6

When I follow the left menu "Software > Manage > Channels" 0s

And I follow "Custom Channel for SLES15SP7 PTFs" 0s

And I follow "Repositories" in the content area 0s

And I follow "Sync" 0s

Then I should see a "Repository sync is running" text 0s

When I wait until the channel "sles15sp7-ptfs" has been synced 0s

Scenario:
Pre-requisite: Add custom channel to minion
< 1ms 16

Given I am on the Systems overview page of this "sle_minion" 0s

When I follow "Software" in the content area 0s

And I follow "Software Channels" in the content area 0s

And I wait until I do not see "Loading..." text 0s

And I check radio button "SLE-Product-SLES15-SP7-Pool for x86_64" 0s

And I wait until I do not see "Loading..." text 0s

Then radio button "SLE-Product-SLES15-SP7-Pool for x86_64" should be checked 0s

And I wait until I do not see "Loading..." text 0s

And I check "Custom Channel for SLES15SP7 PTFs" 0s

And I click on "Next" 0s

Then I should see a "Confirm Software Channel Change" text 0s

And I click on "Confirm" 0s

Then I should see a "Changing the channels has been scheduled." text 0s

When I follow "scheduled" in the content area 0s

And I wait until I see "1 system successfully completed this action." text, refreshing the page 0s

Then channel "Custom Channel for SLES15SP7 PTFs" should be enabled on "sle_minion" 0s

Scenario:
Install PTF through PTFs tab
< 1ms 9

Given I am on the Systems overview page of this "sle_minion" 0s

When I follow "Software" in the content area 0s

And I follow "PTFs" in the content area 0s

And I follow "Install" in the content area 0s

And I check "ptf-30961-3-0" in the list 0s

And I click on "Install PTFs" 0s

And I click on "Confirm" 0s

Then I should see a "The action has been scheduled" text 0s

And I wait until event "Package Install/Upgrade scheduled" is completed 0s

Scenario:
Remove PTF through PTFs tab
< 1ms 9

Given I am on the Systems overview page of this "sle_minion" 0s

When I follow "Software" in the content area 0s

And I follow "PTFs" in the content area 0s

And I follow "List / Remove" in the content area 0s

And I check "ptf-30961-3-0" in the list 0s

And I click on "Remove PTFs" 0s

And I click on "Confirm" 0s

Then I should see a "The action has been scheduled" text 0s

And I wait until event "Package Removal scheduled" is completed 0s

Scenario:
Install PTF through Packages tab
< 1ms 11

Given I am on the Systems overview page of this "sle_minion" 0s

When I follow "Software" in the content area 0s

And I follow "Packages" in the content area 0s

And I follow "Install" in the content area 0s

And I enter "ptf-30961-3-0" as the filtered package name 0s

And I click on the filter button 0s

And I check "ptf-30961-3-0" in the list 0s

And I click on "Install Packages" 0s

And I click on "Confirm" 0s

Then I should see a "1 package install has been scheduled for" text 0s

And I wait until event "Package Install/Upgrade scheduled" is completed 0s

Scenario:
Remove PTF through Packages tab
< 1ms 11

Given I am on the Systems overview page of this "sle_minion" 0s

When I follow "Software" in the content area 0s

And I follow "Packages" in the content area 0s

And I follow "List / Remove" in the content area 0s

And I enter "ptf-30961-3-0" as the filtered package name 0s

And I click on the filter button 0s

And I check "ptf-30961-3-0" in the list 0s

And I click on "Remove Packages" 0s

And I click on "Confirm" 0s

Then I should see a "1 package removal has been scheduled for" text 0s

And I wait until event "Package Removal scheduled" is completed 0s

Scenario:
Cleanup: Delete custom channel for PTFs
< 1ms 6

When I follow the left menu "Software > Manage > Channels" 0s

And I follow "Custom Channel for SLES15SP7 PTFs" 0s

And I follow "Delete Channel" 0s

And I check "unsubscribeSystems" 0s

And I click on "Delete Channel" 0s

Then I should see a "Channel Custom Channel for SLES15SP7 PTFs has been deleted" text 0s

Scenario:
Cleanup: Remove custom repository for PTFs
< 1ms 5

When I follow the left menu "Software > Manage > Repositories" 0s

And I follow "sles15sp7_ptf_repo" 0s

And I follow "Delete Repository" 0s

And I click on "Delete Repository" 0s

Then I should see a "Repository deleted successfully" text 0s

@skip_if_github_validation @skip_if_cloud @skip_if_containerized_server
Feature:Reconfigure the server's hostname < 1ms 20

As admin user
In order to change the server's hostname
I want to use the tool spacewalk-hostname-rename.

Scenario:
Log in as admin user
< 1ms 1

Given I am authorized for the "Admin" section 0s

Scenario:
Change hostname and reboot server
< 1ms 3

When I change the server's short hostname from hosts and hostname files 0s

And I reboot the server through SSH 0s

And I run spacewalk-hostname-rename command on the server 0s

@proxy
Scenario:
Copy the new server keys and configure the proxy
< 1ms 7

When I copy server's keys to the proxy 0s

And I configure the proxy 0s

Then I should see "proxy" via spacecmd 0s

When I restart the "venv-salt-minion" service on "proxy" 0s

Then service "venv-salt-minion" is active on "proxy" 0s

When I restart the "salt-broker" service on "proxy" 0s

Then service "salt-broker" is active on "proxy" 0s

@proxy
Scenario:
Apply high state on the proxy to populate new server CA
< 1ms 1

When I apply highstate on "proxy" 0s

@sle_minion
Scenario:
Apply high state on the SUSE Minion to populate new server CA
< 1ms 1

When I apply highstate on "sle_minion" 0s

@ssh_minion
Scenario:
Apply high state on the SUSE SSH Minion to populate new server CA
< 1ms 1

When I apply highstate on "ssh_minion" 0s

@rhlike_minion
Scenario:
Apply high state on the Red Hat-like Minion to populate new server CA
< 1ms 1

When I apply highstate on "rhlike_minion" 0s

@deblike_minion
Scenario:
Apply high state on the Debian-like Minion to populate new server CA
< 1ms 1

When I apply highstate on "deblike_minion" 0s

@build_host
Scenario:
Apply high state on the build host to populate new server CA
< 1ms 1

When I apply highstate on "build_host" 0s

Scenario:
Check all new server certificates on the minions
< 1ms 1

When I check all certificates after renaming the server hostname 0s

Scenario:
Do some minimal smoke test on the renamed server
< 1ms 10

Given I am on the Systems overview page of this "sle_minion" 0s

When I follow "Details" in the content area 0s

And I follow "Remote Command" in the content area 0s

And I enter as remote command this script in #!/bin/bash date 0s

And I click on "Schedule" 0s

And I follow "Events" in the content area 0s

And I follow "Pending" in the content area 0s

And I wait at most 180 seconds until I do not see "Remote Command on" text, refreshing the page 0s

And I follow "History" in the content area 0s

And I wait until I see the event "Remote Command on" completed during last minute, refreshing the page 0s

Scenario:
Change hostname back and reboot server
< 1ms 2

When I change back the server's hostname 0s

And I run spacewalk-hostname-rename command on the server 0s

@proxy
Scenario:
Copy the new server keys and configure the proxy
< 1ms 7

When I copy server's keys to the proxy 0s

And I configure the proxy 0s

Then I should see "proxy" via spacecmd 0s

When I restart the "venv-salt-minion" service on "proxy" 0s

Then service "venv-salt-minion" is active on "proxy" 0s

When I restart the "salt-broker" service on "proxy" 0s

Then service "salt-broker" is active on "proxy" 0s

@proxy
Scenario:
Apply high state on the proxy to populate new server CA
< 1ms 1

When I apply highstate on "proxy" 0s

@sle_minion
Scenario:
Apply high state on the SUSE Minion to populate new server CA
< 1ms 1

When I apply highstate on "sle_minion" 0s

@ssh_minion
Scenario:
Apply high state on the SUSE SSH Minion to populate new server CA
< 1ms 1

When I apply highstate on "ssh_minion" 0s

@rhlike_minion
Scenario:
Apply high state on the Red Hat-like Minion to populate new server CA
< 1ms 1

When I apply highstate on "rhlike_minion" 0s

@deblike_minion
Scenario:
Apply high state on the Debian-like Minion to populate new server CA
< 1ms 1

When I apply highstate on "deblike_minion" 0s

@build_host
Scenario:
Apply high state on the build host to populate new server CA
< 1ms 1

When I apply highstate on "build_host" 0s

Scenario:
Check all new server certificates on the minions
< 1ms 1

When I check all certificates after renaming the server hostname 0s

@transactional_server
Feature:SELinux debugging < 1ms 1

In order for the server to behave correctly after a reboot
I want to be sure that there is no wrong SELinux label

Scenario:
No previous operation has created wrong SELinux label
< 1ms 1

Then files on container volumes should all have the proper SELinux label 0s

@new_issue
Feature:Debug the server after the testsuite has run 42s 812ms 4 1

Scenario:
Call spacewalk-debug on server
35s 333ms 1

When I execute spacewalk-debug on the server 35s 333ms

Scenario:
Check the tomcat logs on server
857ms 1

Then the tomcat logs should not contain errors 857ms

Scenario:
Check salt event log for failures on server
5s 45ms 1

Then the salt event log on server should contain no failures 5s 45ms Show Error + 
                                            
 
Found 24 failures in salt event log:

# Failure 2 , _stamp: 2026-03-06T14:19:45.294676 {
    "__id__": "run_ansible_playbook",
    "__run_num__": 0,
    "__sls__": "ansible.runplaybook",
    "changes": {
        "ret": {
            "pid": 11059,
            "retcode": 2,
            "stderr": "usage: ansible-playbook [-h] [--version] [-v] [--private-key PRIVATE_KEY_FILE]\n                        [-u REMOTE_USER] [-c CONNECTION] [-T TIMEOUT]\n                        [--ssh-common-args SSH_COMMON_ARGS]\n                        [--sftp-extra-args SFTP_EXTRA_ARGS]\n                        [--scp-extra-args SCP_EXTRA_ARGS]\n                        [--ssh-extra-args SSH_EXTRA_ARGS] [-k |\n                        --connection-password-file CONNECTION_PASSWORD_FILE]\n                        [--force-handlers] [-b]\n                        [--become-method BECOME_METHOD]\n                        [--become-user BECOME_USER] [-K |\n                        --become-password-file BECOME_PASSWORD_FILE] [-t TAGS]\n                        [--skip-tags SKIP_TAGS] [-C] [-D] [-i INVENTORY]\n                        [--list-hosts] [-l SUBSET] [--flush-cache]\n                        [-e EXTRA_VARS] [--vault-id VAULT_IDS] [-J |\n                        --vault-password-file VAULT_PASSWORD_FILES] [-f FORKS]\n                        [-M MODULE_PATH] [--syntax-check] [--list-tasks]\n                        [--list-tags] [--step] [--start-at-task START_AT_TASK]\n                        playbook [playbook ...]\nansible-playbook: error: unrecognized arguments: worry about a thing, p2: Cause every little thing gonna be alright\", \"p3\": \"Singing, \\\\\\\"Dont worry about a thing\\\", p4: Cause every little thing gonna be alright\", \"p5\": \"2 * 50505\", \"p1_empty\": \"\", \"p2_empty\": \"\", \"p_null\": null}\n \nusage: ansible-playbook [-h] [--version] [-v] [--private-key PRIVATE_KEY_FILE]\n                        [-u REMOTE_USER] [-c CONNECTION] [-T TIMEOUT]\n                        [--ssh-common-args SSH_COMMON_ARGS]\n                        [--sftp-extra-args SFTP_EXTRA_ARGS]\n                        [--scp-extra-args SCP_EXTRA_ARGS]\n                        [--ssh-extra-args SSH_EXTRA_ARGS] [-k |\n                        --connection-password-file CONNECTION_PASSWORD_FILE]\n                        [--force-handlers] [-b]\n                        [--become-method BECOME_METHOD]\n                        [--become-user BECOME_USER] [-K |\n                        --become-password-file BECOME_PASSWORD_FILE] [-t TAGS]\n                        [--skip-tags SKIP_TAGS] [-C] [-D] [-i INVENTORY]\n                        [--list-hosts] [-l SUBSET] [--flush-cache]\n                        [-e EXTRA_VARS] [--vault-id VAULT_IDS] [-J |\n                        --vault-password-file VAULT_PASSWORD_FILES] [-f FORKS]\n                        [-M MODULE_PATH] [--syntax-check] [--list-tasks]\n                        [--list-tags] [--step] [--start-at-task START_AT_TASK]\n                        playbook [playbook ...]\n\nRuns Ansible playbooks, executing the defined tasks on the targeted hosts.\n\npositional arguments:\n  playbook              Playbook(s)\n\noptions:\n  --become-password-file, --become-pass-file BECOME_PASSWORD_FILE\n                        Become password file\n  --connection-password-file, --conn-pass-file CONNECTION_PASSWORD_FILE\n                        Connection password file\n  --flush-cache         clear the fact cache for every host in inventory\n  --force-handlers      run handlers even if a task fails\n  --list-hosts          outputs a list of matching hosts; does not execute\n                        anything else\n  --list-tags           list all available tags\n  --list-tasks          list all tasks that would be executed\n  --skip-tags SKIP_TAGS\n                        only run plays and tasks whose tags do not match these\n                        values. This argument may be specified multiple times.\n  --start-at-task START_AT_TASK\n                        start the playbook at the task matching this name\n  --step                one-step-at-a-time: confirm each task before running\n  --syntax-check        perform a syntax check on the playbook, but do not\n                        execute it\n  --vault-id VAULT_IDS  the vault identity to use. This argument may be\n                        specified multiple times.\n  --vault-password-file, --vault-pass-file VAULT_PASSWORD_FILES\n                        vault password file\n  --version             show program's version number, config file location,\n                        configured module search path, module location,\n                        executable location and exit\n  -C, --check           don't make any changes; instead, try to predict some\n                        of the changes that may occur\n  -D, --diff            when changing (small) files and templates, show the\n                        differences in those files; works great with --check\n  -J, --ask-vault-password, --ask-vault-pass\n                        ask for vault password\n  -K, --ask-become-pass\n                        ask for privilege escalation password\n  -M, --module-path MODULE_PATH\n                        prepend colon-separated path(s) to module library\n                        (default={{ ANSIBLE_HOME ~\n                        \"/plugins/modules:/usr/share/ansible/plugins/modules\"\n                        }}). This argument may be specified multiple times.\n  -e, --extra-vars EXTRA_VARS\n                        set additional variables as key=value or YAML/JSON, if\n                        filename prepend with @. This argument may be\n                        specified multiple times.\n  -f, --forks FORKS     specify number of parallel processes to use\n                        (default=5)\n  -h, --help            show this help message and exit\n  -i, --inventory, --inventory-file INVENTORY\n                        specify inventory host path or comma separated host\n                        list. This argument may be specified multiple times.\n  -k, --ask-pass        ask for connection password\n  -l, --limit SUBSET    further limit selected hosts to an additional pattern\n  -t, --tags TAGS       only run plays and tasks tagged with these values.\n                        This argument may be specified multiple times.\n  -v, --verbose         Causes Ansible to print more debug messages. Adding\n                        multiple -v will increase the verbosity, the builtin\n                        plugins currently evaluate up to -vvvvvv. A reasonable\n                        level to start is -vvv, connection debugging might\n                        require -vvvv. This argument may be specified multiple\n                        times.\n\nConnection Options:\n  control as whom and how to connect to hosts\n\n  --private-key, --key-file PRIVATE_KEY_FILE\n                        use this file to authenticate the connection\n  --scp-extra-args SCP_EXTRA_ARGS\n                        specify extra arguments to pass to scp only (e.g. -l)\n  --sftp-extra-args SFTP_EXTRA_ARGS\n                        specify extra arguments to pass to sftp only (e.g. -f,\n                        -l)\n  --ssh-common-args SSH_COMMON_ARGS\n                        specify common arguments to pass to sftp/scp/ssh (e.g.\n                        ProxyCommand)\n  --ssh-extra-args SSH_EXTRA_ARGS\n                        specify extra arguments to pass to ssh only (e.g. -R)\n  -T, --timeout TIMEOUT\n                        override the connection timeout in seconds (default\n                        depends on connection)\n  -c, --connection CONNECTION\n                        connection type to use (default=ssh)\n  -u, --user REMOTE_USER\n                        connect as this user (default=None)\n\nPrivilege Escalation Options:\n  control how and which user you become as on target hosts\n\n  --become-method BECOME_METHOD\n                        privilege escalation method to use (default=sudo), use\n                        `ansible-doc -t become -l` to list valid choices.\n  --become-user BECOME_USER\n                        run operations as this user (default=root)\n  -b, --become          run operations with become (does not imply password\n                        prompting)",
            "stdout": ""
        }
    },
    "comment": "Module function ansible.playbooks executed",
    "duration": 4662.758,
    "name": "ansible.playbooks",
    "result": false,
    "start_time": "15:19:40.621404"
}

# Failure 3 , _stamp: 2026-03-06T15:13:14.992511 {
    "__id__": "pkg_installed",
    "__run_num__": 11,
    "__sls__": "packages.pkginstall",
    "changes": {},
    "comment": "An error was encountered while installing package(s): Zypper command failure: Running as unit: run-p14848-i14849.scope; invocation ID: a87b314d25544790b59238e74170cb4aLoading repository data...\nReading installed packages...\nResolving package dependencies...\n\nProblem: 1: nothing provides 'python3-defusedxml' needed by the to be installed python3-rhnlib-5.2.3-2.1.uyuni.noarch\n Solution 1: do not install mgr-push-5.2.2-2.1.uyuni.noarch\n Solution 2: break python3-rhnlib-5.2.3-2.1.uyuni.noarch by ignoring some of its dependencies\n\nChoose from above solutions by number or cancel [1/2/c/d/?] (c): c",
    "duration": 2139.188,
    "name": "pkg_installed",
    "result": false,
    "start_time": "16:13:12.842733"
}

# Failure 4 , _stamp: 2026-03-06T15:30:48.372454 {
    "__id__": "mgr_buildimage",
    "__run_num__": 1,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "Module function docker.build threw an exception. Exception: Build failed for https://github.com/uyuni-project/uyuni.git#:testsuite/features/profiles/temporary/docker_profiles/cloud_aws/Docker. Error(s) follow:\n\nmanifest for ip-172-16-1-175.eu-central-1.compute.internal/suse/sle15:15.7 not found: manifest unknown: manifest unknown",
    "duration": 14036.149,
    "name": "docker.build",
    "result": false,
    "start_time": "16:30:34.303482"
}

# Failure 5 , _stamp: 2026-03-06T15:30:48.372454 {
    "__id__": "mgr_pushimage",
    "__run_num__": 2,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "One or more requisite failed: images.docker.mgr_buildimage",
    "duration": 0.004,
    "name": "docker.push",
    "result": false,
    "start_time": "16:30:48.340228"
}

# Failure 6 , _stamp: 2026-03-06T15:30:48.372454 {
    "__id__": "mgr_registries_logout",
    "__run_num__": 3,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "One or more requisite failed: images.docker.mgr_pushimage",
    "duration": 0.004,
    "name": "docker.logout",
    "result": false,
    "start_time": "16:30:48.340496"
}

# Failure 7 , _stamp: 2026-03-06T15:32:03.278694 {
    "__id__": "mgr_buildimage",
    "__run_num__": 1,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "Module function docker.build threw an exception. Exception: Build failed for https://github.com/uyuni-project/uyuni.git#:testsuite/features/profiles/temporary/docker_profiles/cloud_aws/Docker. Error(s) follow:\n\nmanifest for ip-172-16-1-175.eu-central-1.compute.internal/suse/sle15:15.7 not found: manifest unknown: manifest unknown",
    "duration": 13887.446,
    "name": "docker.build",
    "result": false,
    "start_time": "16:31:49.360006"
}

# Failure 8 , _stamp: 2026-03-06T15:32:03.278694 {
    "__id__": "mgr_pushimage",
    "__run_num__": 2,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "One or more requisite failed: images.docker.mgr_buildimage",
    "duration": 0.005,
    "name": "docker.push",
    "result": false,
    "start_time": "16:32:03.247975"
}

# Failure 9 , _stamp: 2026-03-06T15:32:03.278694 {
    "__id__": "mgr_registries_logout",
    "__run_num__": 3,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "One or more requisite failed: images.docker.mgr_pushimage",
    "duration": 0.004,
    "name": "docker.logout",
    "result": false,
    "start_time": "16:32:03.248262"
}

# Failure 10 , _stamp: 2026-03-06T15:37:47.089958 {
    "__id__": "mgr_buildimage",
    "__run_num__": 1,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "Module function docker.build threw an exception. Exception: Build failed for https://github.com/uyuni-project/uyuni.git#:testsuite/features/profiles/temporary/docker_profiles/cloud_aws/Docker. Error(s) follow:\n\nmanifest for ip-172-16-1-175.eu-central-1.compute.internal/suse/sle15:15.7 not found: manifest unknown: manifest unknown",
    "duration": 13710.384,
    "name": "docker.build",
    "result": false,
    "start_time": "16:37:33.345414"
}

# Failure 11 , _stamp: 2026-03-06T15:37:47.089958 {
    "__id__": "mgr_pushimage",
    "__run_num__": 2,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "One or more requisite failed: images.docker.mgr_buildimage",
    "duration": 0.005,
    "name": "docker.push",
    "result": false,
    "start_time": "16:37:47.056307"
}

# Failure 12 , _stamp: 2026-03-06T15:37:47.089958 {
    "__id__": "mgr_registries_logout",
    "__run_num__": 3,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "One or more requisite failed: images.docker.mgr_pushimage",
    "duration": 0.004,
    "name": "docker.logout",
    "result": false,
    "start_time": "16:37:47.056575"
}

# Failure 13 , _stamp: 2026-03-06T15:38:44.246653 {
    "__id__": "mgr_buildimage",
    "__run_num__": 1,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "Module function docker.build threw an exception. Exception: Build failed for https://github.com/uyuni-project/uyuni.git#:testsuite/features/profiles/temporary/docker_profiles/cloud_aws/Docker. Error(s) follow:\n\nmanifest for ip-172-16-1-175.eu-central-1.compute.internal/suse/sle15:15.7 not found: manifest unknown: manifest unknown",
    "duration": 13644.973,
    "name": "docker.build",
    "result": false,
    "start_time": "16:38:30.571077"
}

# Failure 14 , _stamp: 2026-03-06T15:38:44.246653 {
    "__id__": "mgr_pushimage",
    "__run_num__": 2,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "One or more requisite failed: images.docker.mgr_buildimage",
    "duration": 0.005,
    "name": "docker.push",
    "result": false,
    "start_time": "16:38:44.216545"
}

# Failure 15 , _stamp: 2026-03-06T15:38:44.246653 {
    "__id__": "mgr_registries_logout",
    "__run_num__": 3,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "One or more requisite failed: images.docker.mgr_pushimage",
    "duration": 0.004,
    "name": "docker.logout",
    "result": false,
    "start_time": "16:38:44.216811"
}

# Failure 16 , _stamp: 2026-03-06T15:39:45.857123 {
    "__id__": "mgr_buildimage",
    "__run_num__": 1,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "Module function docker.build threw an exception. Exception: Build failed for https://github.com/uyuni-project/uyuni.git#:testsuite/features/profiles/temporary/docker_profiles/cloud_aws/Docker. Error(s) follow:\n\nmanifest for ip-172-16-1-175.eu-central-1.compute.internal/suse/sle15:15.7 not found: manifest unknown: manifest unknown",
    "duration": 13589.565,
    "name": "docker.build",
    "result": false,
    "start_time": "16:39:32.237007"
}

# Failure 17 , _stamp: 2026-03-06T15:39:45.857123 {
    "__id__": "mgr_pushimage",
    "__run_num__": 2,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "One or more requisite failed: images.docker.mgr_buildimage",
    "duration": 0.005,
    "name": "docker.push",
    "result": false,
    "start_time": "16:39:45.827019"
}

# Failure 18 , _stamp: 2026-03-06T15:39:45.857123 {
    "__id__": "mgr_registries_logout",
    "__run_num__": 3,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "One or more requisite failed: images.docker.mgr_pushimage",
    "duration": 0.004,
    "name": "docker.logout",
    "result": false,
    "start_time": "16:39:45.827288"
}

# Failure 19 , _stamp: 2026-03-06T15:40:41.685194 {
    "__id__": "mgr_buildimage",
    "__run_num__": 1,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "Module function docker.build threw an exception. Exception: Build failed for https://github.com/uyuni-project/uyuni.git#:testsuite/features/profiles/temporary/docker_profiles/cloud_aws/Docker. Error(s) follow:\n\nmanifest for ip-172-16-1-175.eu-central-1.compute.internal/suse/sle15:15.7 not found: manifest unknown: manifest unknown",
    "duration": 13656.442,
    "name": "docker.build",
    "result": false,
    "start_time": "16:40:27.989461"
}

# Failure 20 , _stamp: 2026-03-06T15:40:41.685194 {
    "__id__": "mgr_pushimage",
    "__run_num__": 2,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "One or more requisite failed: images.docker.mgr_buildimage",
    "duration": 0.005,
    "name": "docker.push",
    "result": false,
    "start_time": "16:40:41.646360"
}

# Failure 21 , _stamp: 2026-03-06T15:40:41.685194 {
    "__id__": "mgr_registries_logout",
    "__run_num__": 3,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "One or more requisite failed: images.docker.mgr_pushimage",
    "duration": 0.004,
    "name": "docker.logout",
    "result": false,
    "start_time": "16:40:41.646635"
}

# Failure 22 , _stamp: 2026-03-06T15:49:34.295222 {
    "__id__": "mgr_buildimage",
    "__run_num__": 1,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "Module function docker.build threw an exception. Exception: Build failed for https://github.com/uyuni-project/uyuni.git#:testsuite/features/profiles/temporary/docker_profiles/cloud_aws/Docker/authprofile. Error(s) follow:\n\nHead \"https://ip-172-16-1-175.eu-central-1.compute.internal:5000/v2/cucutest/systemsmanagement/uyuni/master/docker/containers/uyuni-master-testsuite/manifests/latest\": no basic auth credentials",
    "duration": 13896.049,
    "name": "docker.build",
    "result": false,
    "start_time": "16:49:20.363814"
}

# Failure 23 , _stamp: 2026-03-06T15:49:34.295222 {
    "__id__": "mgr_pushimage",
    "__run_num__": 2,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "One or more requisite failed: images.docker.mgr_buildimage",
    "duration": 0.005,
    "name": "docker.push",
    "result": false,
    "start_time": "16:49:34.260353"
}

# Failure 24 , _stamp: 2026-03-06T15:49:34.295222 {
    "__id__": "mgr_registries_logout",
    "__run_num__": 3,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "One or more requisite failed: images.docker.mgr_pushimage",
    "duration": 0.004,
    "name": "docker.logout",
    "result": false,
    "start_time": "16:49:34.260626"
}

# Failure 25 , _stamp: 2026-03-06T16:56:01.392261 {
    "__id__": "os_not_supported",
    "__run_num__": 14,
    "__sls__": "prometheus",
    "changes": {},
    "comment": "Failure!",
    "duration": 0.762,
    "name": "OS not supported!",
    "result": false,
    "start_time": "17:55:34.272133"
}

 (ScriptError)
./features/step_definitions/salt_steps.rb:526:in `/^the salt event log on server should contain no failures$/'
features/finishing/srv_debug.feature:15:in `the salt event log on server should contain no failures'

Scenario:
Check the taskomatic logs on server
887ms 1

Then the taskomatic logs should not contain errors 887ms

Scenario:
Check for out of memory errors
689ms 1

Then the log messages should not contain out of memory errors 689ms

Feature:Debug the clients after the testsuite has run 2m 42s 764ms 1

Scenario:
Extract the logs from all our clients
2m 42s 764ms 1

When I extract the log files from all our active nodes 2m 42s 764ms

@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