All Scenarios

1525

Passed Scenarios

1258

Failed Scenarios

49

Skipped Scenarios

218

Execution Time: 428m 4s 430ms

Expand All | Collapse All

Metadata

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

Feature:Sanity checks 43s 405ms 10 2

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

Scenario:
The server is healthy
11s 859ms 19

Then "server" should have a FQDN 387ms

And reverse resolution should work for "server" 630ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

And reverse resolution should work for "proxy" 276ms

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

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

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

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

And reverse resolution should work for "sle_minion" 408ms

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

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

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

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

And reverse resolution should work for "build_host" 214ms

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

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

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

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

And reverse resolution should work for "ssh_minion" 410ms

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

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

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

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

And reverse resolution should work for "rhlike_minion" 200ms

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

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

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

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

And reverse resolution should work for "deblike_minion" 213ms

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

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

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

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

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

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

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

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

Feature:Very first settings 50s 403ms 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
923ms 1

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

Scenario:
Log in as admin user
40s 58ms 1

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

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

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

Scenario:
Create testing username
1s 476ms 12

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

And I follow "Create User" 707ms

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

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

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

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

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

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

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

And I click on "Create Login" 65ms

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

And I should see a "testing" link 12ms

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

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

And I follow "testing" 699ms

And I check "role_org_admin" 87ms

And I check "role_system_group_admin" 77ms

And I check "role_channel_admin" 78ms

And I check "role_activation_key_admin" 77ms

And I check "role_config_admin" 77ms

And I click on "Update" 1s 177ms

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

And I should see a "testing" text 70ms

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

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

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

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 784ms 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 505ms 5

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

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

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

And I click on "Save Preferences" 680ms

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

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

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

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

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

And I click on "Save Preferences" 723ms

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

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

Scenario:
Create a Kiwi user with image administrators rights
6s 483ms 2

New user kiwikiwi created with roles: image_admin

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

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

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

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

New user docker created with roles: image_admin

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

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

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

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

And I follow "Create" 609ms

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

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

And I click on "create-btn" 129ms

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

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

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

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

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

Scenario:
Disable scheduled reposyncs
4s 681ms 5

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

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

And I choose "disabled" 69ms

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

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

Scenario:
Disable scheduled Cobbler syncs
4s 585ms 5

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

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

And I choose "disabled" 47ms

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

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

@scc_credentials
Feature:List available channels and enable them 1m 39s 745ms 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 918ms 5

When I refresh SCC 31s 638ms

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

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

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

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

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

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

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

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

When I remove the mgr-sync cache file 727ms

And I execute mgr-sync refresh 1m 776ms

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

Feature:Synchronize products in the products page of the Setup Wizard 52m 30s 494ms 9 9

@scc_credentials
Scenario:
Refresh SCC
28s 478ms 1

When I refresh SCC 28s 478ms

@scc_credentials
Scenario:
Let the products page appear
1s 895ms 6

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

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

And I wait until I see "Product Description" text 918ms

Then I should see a "Arch" text 116ms

And I should see a "Channels" text 116ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@scc_credentials @uyuni @build_host
Scenario:
Synchronize SLES 15 SP7 product with recommended sub-products for Retail feature
46m 14s 985ms 20

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

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 57ms

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

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

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

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

And I wait until all synchronized channels for "sles15-sp7" have finished 45m 51s 706ms

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

SUCCESS: Channel opensuse_tumbleweed-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel opensuse_tumbleweed-x86_64 synchronization took 89 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 89 seconds.
SUCCESS: Channel opensuse_tumbleweed-uyuni-client-devel-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel opensuse_tumbleweed-uyuni-client-devel-x86_64 synchronization took 10 seconds.
SUCCESS: Channel uyuni-proxy-devel-tumbleweed-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel uyuni-proxy-devel-tumbleweed-x86_64 synchronization took 7 seconds.
SUCCESS: Channel sle-product-sles15-sp7-pool-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-product-sles15-sp7-pool-x86_64 synchronization took 7 seconds.
SUCCESS: Channel sle-product-sles15-sp7-updates-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-product-sles15-sp7-updates-x86_64 synchronization took 3 seconds.
SUCCESS: Channel sle15-sp7-installer-updates-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle15-sp7-installer-updates-x86_64 synchronization took 4 seconds.
SUCCESS: Channel sle-module-basesystem15-sp7-pool-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-module-basesystem15-sp7-pool-x86_64 synchronization took 331 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 897 seconds.
SUCCESS: Channel sle-module-python3-15-sp7-pool-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-module-python3-15-sp7-pool-x86_64 synchronization took 41 seconds.
SUCCESS: Channel sle-module-python3-15-sp7-updates-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-module-python3-15-sp7-updates-x86_64 synchronization took 42 seconds.
SUCCESS: Channel sle-module-server-applications15-sp7-pool-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-module-server-applications15-sp7-pool-x86_64 synchronization took 55 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 81 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 341 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 53 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 570 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 29 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 24 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 176 seconds.

When I wait until all synchronized channels have solved their dependencies 1m 38s 455ms

Then all channels have been synced without errors < 1ms

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

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

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

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

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

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

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

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

@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 869ms 11 1

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

Scenario:
Log in as admin user
489ms 1

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

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

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

And I follow "Create Channel" 316ms

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

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

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

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

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

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

And I click on "Create Channel" 600ms

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

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

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

And I follow "Create Channel" 320ms

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

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

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

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

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

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

And I click on "Create Channel" 55ms

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

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

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

And I follow "Create Channel" 305ms

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

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

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

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

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

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

And I click on "Create Channel" 542ms

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

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

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

And I follow "Create Channel" 252ms

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

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

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

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

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

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

And I click on "Create Channel" 545ms

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

Scenario:
Add a fake child channel into the fake base channel i586
967ms 10

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

And I follow "Create Channel" 338ms

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

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

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

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

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

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

And I click on "Create Channel" 54ms

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

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

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

And I follow "Create Channel" 323ms

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

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

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

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

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

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

And I click on "Create Channel" 559ms

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

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

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

And I follow "Create Channel" 324ms

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

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

And I click on "Create Channel" 585ms

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

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

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

And I follow "Create Channel" 328ms

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

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

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

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

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

And I uncheck "gpg_check" 10s 72ms

And I click on "Create Channel" 701ms

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

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

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

And I follow "Create Channel" 333ms

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

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

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

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

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

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

And I click on "Create Channel" 53ms

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

@rhlike_minion
Scenario:
Add a fake AppStream base channel
985ms 10

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

And I follow "Create Channel" 357ms

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

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

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

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

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

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

And I click on "Create Channel" 55ms

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

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

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

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

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

And I follow "Create Repository" 350ms

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

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

And I click on "Create Repository" 439ms

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

And I should see "metadataSigned" as checked 20ms

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

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

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

And I uncheck "metadataSigned" 10s 72ms

And I click on "Update Repository" 438ms

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

And I should see "metadataSigned" as unchecked 15ms

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

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

And I follow "Create Repository" 295ms

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

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

And I click on "Create Repository" 401ms

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

And I should see "metadataSigned" as checked 15ms

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

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

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

And I uncheck "metadataSigned" 10s 77ms

And I click on "Update Repository" 448ms

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

And I should see "metadataSigned" as unchecked 15ms

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

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

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

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

And I click on "Update Channel" 556ms

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

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

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

And I click on "Save Repositories" 579ms

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

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

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

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

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

And I click on "Update Channel" 577ms

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

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

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

And I click on "Save Repositories" 963ms

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

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

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

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

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

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

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

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

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

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 135ms 9

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

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

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

And I click on "Update Channel" 56ms

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

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

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

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

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

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

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

And I follow "Create Repository" 309ms

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

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

And I uncheck "metadataSigned" 10s 70ms

And I click on "Create Repository" 447ms

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

Scenario:
Add the repository to the i586 channel
2s 9ms 9

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

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

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

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

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

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

And I click on "Save Repositories" 574ms

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

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

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

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

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

And I click on "Save Repositories" 874ms

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

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

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

And I follow "Create Repository" 316ms

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

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

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

And I click on "Create Repository" 58ms

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

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

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

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

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

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

And I click on "Save Repositories" 907ms

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

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

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

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

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

And I click on "Update Channel" 0s

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

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

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

And I click on "Save Repositories" 0s

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

@skip_if_github_validation
Feature:Create custom channels with development repositories 28s 656ms 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
479ms 1

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

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

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

And I follow "Create Channel" 290ms

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

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

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

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

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

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

And I click on "Create Channel" 621ms

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

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

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

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

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

And I follow "Create Channel" 366ms

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

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

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

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

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

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

And I click on "Create Channel" 54ms

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

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

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

@deblike_minion
Scenario:
Create a custom channel for Debian-like minions
915ms 10

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

And I follow "Create Channel" 265ms

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

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

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

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

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

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

And I click on "Create Channel" 54ms

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 180ms 1

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

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

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

And I follow "Create Channel" 294ms

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

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

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

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

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

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

And I click on "Create Channel" 54ms

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

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

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

Feature:Synchronize fake channels 1m 49s 390ms 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 795ms 2

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

And I enable source package syncing 1s 369ms

@sle_minion
Scenario:
Synchronize Fake-RPM-SUSE-Channel channel
4s 681ms 9

DEBUG: Found channel 'fake-rpm-suse-channel' at line 169. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for fake-rpm-suse-channel at line 173.
SUCCESS: fake-rpm-suse-channel is fully synchronized.

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

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

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

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

And I follow "Sync" 513ms

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

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

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

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

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

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

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

@skip_if_github_validation
Scenario:
Synchronize Fake-Child-Channel-i586 channel
15s 733ms 9

DEBUG: Found channel 'fake-child-channel-i586' at line 225. 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 225. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for fake-child-channel-i586 at line 229.
SUCCESS: fake-child-channel-i586 is fully synchronized.

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

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

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

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

And I follow "Sync" 331ms

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

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

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

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

Scenario:
Synchronize Test-Child-Channel-x86_64 channel
15s 840ms 9

DEBUG: Found channel 'test-child-channel-x86_64' at line 233. 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 233. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for test-child-channel-x86_64 at line 237.
SUCCESS: test-child-channel-x86_64 is fully synchronized.

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

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

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

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

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

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

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

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

@sle_minion
Scenario:
Synchronize Fake-Child-Channel-SUSE-like channel
15s 790ms 9

DEBUG: Found channel 'fake-child-channel-suse-like' at line 241. 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 241. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for fake-child-channel-suse-like at line 245.
SUCCESS: fake-child-channel-suse-like is fully synchronized.

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

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

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

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

And I follow "Sync" 327ms

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

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

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

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

DEBUG: Found channel 'fake-base-channel-debian-like' at line 249. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for fake-base-channel-debian-like at line 253.
SUCCESS: fake-base-channel-debian-like is fully synchronized.

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

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

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

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

And I follow "Sync" 329ms

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

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

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

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

@rhlike_minion
Scenario:
Synchronize Fake-Base-Channel-RH-like channel
16s 728ms 9

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

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

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

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

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

And I follow "Sync" 1s 300ms

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

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

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

@rhlike_minion
Scenario:
Synchronize Fake-Base-Channel-AppStream channel
15s 838ms 9

DEBUG: Found channel 'fake-base-channel-appstream' at line 265. 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 265. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for fake-base-channel-appstream at line 269.
SUCCESS: fake-base-channel-appstream is fully synchronized.

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

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

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

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

And I follow "Sync" 347ms

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

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

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

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

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

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

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

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

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

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

Scenario:
Refresh the channel's repository data
6s 147ms 6

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

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

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

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

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

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

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

Then I disable source package syncing 1s 65ms

@skip_if_github_validation
Feature:Synchronize development channels 1m 26s 848ms 4

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

@sle_minion
Scenario:
Synchronize Devel-SUSE-Channel channel
16s 56ms 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 467ms

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

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

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

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

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

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

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

@deblike_minion
Scenario:
Synchronize Devel-Debian-like-Channel channel
15s 941ms 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 466ms

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

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

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

And I follow "Sync" 333ms

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

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

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

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

@rhlike_minion
Scenario:
Synchronize Devel-RH-like-Channel channel
38s 815ms 9

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

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

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

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

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

And I follow "Sync" 427ms

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

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

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

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

@build_host @uyuni
Scenario:
Synchronize Devel-Build-Host-Channel channel
16s 35ms 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 437ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Feature:Update activation keys 19s 833ms 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
429ms 1

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 492ms

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

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

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

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

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

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

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

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

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

And I click on "Update Activation Key" 0s

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 458ms

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

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

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

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

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

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

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

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

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

And I click on "Update Activation Key" 0s

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 58ms

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

@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
2s 892ms 20

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

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

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

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

And I wait for child channels to appear 514ms

And I include the recommended child channels 177ms

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

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 449ms

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

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

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

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

And I wait for child channels to appear 853ms

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

And I wait for child channels to appear 302ms

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

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

And I click on "Update Activation Key" 462ms

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

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

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

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

And I wait for child channels to appear 850ms

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

And I wait for child channels to appear 300ms

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

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

And I click on "Update Activation Key" 466ms

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

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

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

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

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

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

And I wait for child channels to appear 508ms

And I include the recommended child channels 160ms

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 470ms

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

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

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

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

And I wait for child channels to appear 725ms

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

And I click on "Update Activation Key" 450ms

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

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

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

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

And I wait for child channels to appear 740ms

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

And I click on "Update Activation Key" 440ms

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

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

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

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

And I wait for child channels to appear 568ms

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

And I click on "Update Activation Key" 426ms

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

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

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

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

@proxy
Scenario:
Create the bootstrap repository for Proxy
2s 39ms 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 39ms

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

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

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

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

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

Scenario:
Bootstrap the proxy host as a salt minion
36s 389ms 9

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 62ms

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

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

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

Scenario:
Generate containerized proxy configuration
10s 933ms 2

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

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

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 914ms 1

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

Scenario:
Wait until containerized proxy service is active
4s 88ms 10

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

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

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

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

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

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

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

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

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

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

Scenario:
The containerized proxy should be registered automatically
669ms 2

When I follow the left menu "Systems" 62ms

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

Scenario:
Check if Monitoring can be enabled on the containerized proxy
11s 85ms 3

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

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

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

@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 6s 405ms 7

Scenario:
Log in as admin user
38s 64ms 1

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

Scenario:
Bootstrap a Debian-like minion
2m 6s 701ms 14

The hostname of deblike_minion is uyuni-master-deblike-minion
* Mon Feb 16 2026 Victor Zhestkov
- Fix the typo causing buiding EL9 bundle without binary dependencies
* Mon Feb 2 2026 Michael Calmer
- Rebuild because of maintenance release
* Mon Jan 19 2026 Marek Czernek
- Make syntax in httputil_test compatible with Python 3.6
- Fix KeyError in postgres module with PostgreSQL 17 (bsc#1254325)
- Added:
* fix-tornado-s-httputil_test-syntax-for-python-3.6.patch
* backport-add-maintain-m-privilege-to-postgres-module.patch
* Wed Jan 14 2026 Marek Czernek
- Use internal deb classes instead of external aptsource lib
* Drop dependency on saltbundlepy-apt
- Speed up wheel key.finger call (bsc#1240532)
- Backport security patches for Salt vendored tornado:

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 145ms

And I wait until I see "Bootstrap process initiated." text 36s 498ms

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

And I wait until I see the name of "deblike_minion", refreshing the page 45s 472ms

And I wait until onboarding is completed for "deblike_minion" 34s 792ms

And I query latest Salt changes on Debian-like system "deblike_minion" 925ms

@proxy
Scenario:
Check connection from the Debian-like minion to proxy
1s 570ms 4

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

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

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

Then I should see "proxy" short hostname 97ms

@proxy
Scenario:
Check registration on proxy of the Debian-like minion
2s 52ms 4

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

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

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

Then I should see "deblike_minion" hostname 287ms

Scenario:
Subscribe the Debian-like minion to a base channel
25s 101ms 11

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

Given I am on the Systems overview page of this "deblike_minion" 2s 312ms

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

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

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

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

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

And I click on "Next" 77ms

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

When I click on "Confirm" 85ms

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

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

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

* Mon Feb 16 2026 Victor Zhestkov
- Fix the typo causing buiding EL9 bundle without binary dependencies
* Mon Feb 2 2026 Michael Calmer
- Rebuild because of maintenance release
* Mon Jan 19 2026 Marek Czernek
- Make syntax in httputil_test compatible with Python 3.6
- Fix KeyError in postgres module with PostgreSQL 17 (bsc#1254325)
- Added:
* fix-tornado-s-httputil_test-syntax-for-python-3.6.patch
* backport-add-maintain-m-privilege-to-postgres-module.patch
* Wed Jan 14 2026 Marek Czernek
- Use internal deb classes instead of external aptsource lib
* Drop dependency on saltbundlepy-apt
- Speed up wheel key.finger call (bsc#1240532)
- Backport security patches for Salt vendored tornado:

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

Scenario:
Check events history for failures on Debian-like minion
52s 476ms 2

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

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

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

Scenario:
Log in as admin user
38s 221ms 1

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

Scenario:
Bootstrap a Red Hat-like minion
2m 3s 396ms 13

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

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 74ms

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

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

And I wait until I see the name of "rhlike_minion", refreshing the page 46s 438ms

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

@proxy
Scenario:
Check connection from Red Hat-like minion to proxy
1s 623ms 4

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

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

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

Then I should see "proxy" short hostname 77ms

@proxy
Scenario:
Check registration on proxy of Red Hat-like minion
2s 22ms 4

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

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

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

Then I should see "rhlike_minion" hostname 139ms

Scenario:
Subscribe the Red Hat-like minion to a base channel
25s 172ms 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 536ms

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

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

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

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

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

And I click on "Next" 103ms

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

When I click on "Confirm" 95ms

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

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

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

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

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

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

* Wed Jan 14 2026 Marek Czernek
- Use internal deb classes instead of external aptsource lib

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

Scenario:
Check events history for failures on Red Hat-like minion
52s 833ms 2

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

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

@build_host
Feature:Bootstrap a build host via the GUI 6m 3s 377ms 9

Scenario:
Clean up sumaform leftovers on build host
8s 51ms 1

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

Scenario:
Log in as admin user
38s 280ms 1

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

Scenario:
Bootstrap a build host
47s 117ms 10

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

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 119ms

And I wait until I see "Bootstrap process initiated." text 42s 569ms

Scenario:
Check the new bootstrapped build host in System Overview page
3m 3s 653ms 6

It took 2 seconds to contact the minion

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

Then I should see a "accepted" text 703ms

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

And I wait at most 500 seconds until I see the name of "build_host", refreshing the page 28s 817ms

And I wait at most 500 seconds until onboarding is completed for "build_host" 2m 31s 646ms

Then the Salt master can reach "build_host" 1s 890ms

@proxy
Scenario:
Check connection from build host to proxy
1s 278ms 4

Given I am on the Systems overview page of this "build_host" 1s 62ms

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

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

Then I should see "proxy" short hostname 66ms

@proxy
Scenario:
Check registration on build host of minion
1s 204ms 4

Given I am on the Systems overview page of this "proxy" 975ms

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

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

Then I should see "build_host" hostname 99ms

Scenario:
Detect latest Salt changes on the SLES build host
517ms 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" 517ms

Scenario:
Check that the build host is a build host
1s 264ms 3

Given I am on the Systems overview page of this "build_host" 1s 67ms

Then I should see a "[Container Build Host]" text 96ms

Then I should see a "[OS Image Build Host]" text 100ms

Scenario:
Check events history for failures on SLES build host
1m 22s 9ms 2

Given I am on the Systems overview page of this "build_host" 1s 66ms

Then I check for failed events on history event page 1m 20s 942ms

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

Scenario:
Clean up sumaform leftovers on SLES minion
9s 698ms 1

When I perform a full salt minion cleanup on "sle_minion" 9s 698ms

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

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

Scenario:
Bootstrap a SLES minion
43s 164ms 11

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

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

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

When I enter the hostname of "sle_minion" as "hostname" 245ms

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

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

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

And I select "1-SUSE-KEY-x86_64" from "activationKeys" 137ms

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

And I click on "Bootstrap" 122ms

And I wait until I see "Bootstrap process initiated." text 38s 506ms

And I report the bootstrap duration for "sle_minion" < 1ms

Scenario:
Check the new bootstrapped minion in System List page
1m 25s 815ms 8

It took 3 seconds to contact the minion

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

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

Then I should see a "accepted" text 732ms

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

And I wait until I see the name of "sle_minion", refreshing the page 31s 862ms

And I wait until onboarding is completed for "sle_minion" 49s 597ms

Then the Salt master can reach "sle_minion" 2s 925ms

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
1s 982ms 4

Given I am on the Systems overview page of this "sle_minion" 1s 572ms

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

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

Then I should see "proxy" short hostname 162ms

@proxy
Scenario:
Check registration on proxy of minion
2s 6ms 4

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

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

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

Then I should see "sle_minion" hostname 171ms

@ssh_minion
Feature:Bootstrap a Salt host managed via salt-ssh 3m 31s 8ms 5 2

Scenario:
Clean up sumaform leftovers on SLES SSH minion
9s 890ms 1

When I perform a full salt minion cleanup on "ssh_minion" 9s 890ms

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

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

Scenario:
Bootstrap a SLES SSH minion
2m 38s 796ms 11

The hostname of ssh_minion is uyuni-master-suse-sshminion.sumaci.aws

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

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

When I check "manageWithSSH" 160ms

And I enter the hostname of "ssh_minion" as "hostname" 257ms

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

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

And I click on "Bootstrap" 159ms

And I wait until I see "Bootstrap process initiated." text 54s 759ms

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

And I wait until I see the name of "ssh_minion", refreshing the page 17s 867ms

And I wait until onboarding is completed for "ssh_minion" 1m 21s 218ms

@susemanager
Scenario:
Use correct kernel image on the SSH minion
< 1ms 2

When I remove package "kernel-default-base" from this "ssh_minion" 0s

And I install package "kernel-default" on this "ssh_minion" 0s

@susemanager
Scenario:
Reboot the SSH minion to use the new kernel
< 1ms 1

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

@proxy
Scenario:
Check connection from SSH minion to proxy
1s 506ms 4

Given I am on the Systems overview page of this "ssh_minion" 1s 176ms

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

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

Then I should see "proxy" short hostname 118ms

@proxy
Scenario:
Check registration on proxy of SSH minion
1s 618ms 4

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

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

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

Then I should see "ssh_minion" hostname 157ms

@scope_visualization
Feature:Secure connection 209ms 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 79ms

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

When I connect to the server securely while using incorrect certificate as a CA certificate file 36ms

Then the secure connection should fail due to unverified certificate signature < 1ms

Feature:List available products 2s 663ms 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 663ms 1 1

When I execute mgr-sync "list products" with user "admin" and password "admin" 2s 663ms

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 47s 222ms 12

Scenario:
Fake an IPMI host
8s 691ms 1

When the server starts mocking an IPMI host 8s 691ms

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

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

Scenario:
Start Cobbler monitoring
6s 635ms 1

When I start local monitoring of Cobbler 6s 635ms

Scenario:
Check the power management page
5s 410ms 6

Given I am on the Systems overview page of this "sle_minion" 5s 63ms

When I follow "Provisioning" in the content area 87ms

And I follow "Power Management" in the content area 88ms

Then I should see a "Power Management Settings" text 77ms

And I should see a "IPMI" text 65ms

And I should see a "Save" button 27ms

Scenario:
Save power management values
6s 567ms 9

When I enter "fakeipmi" as "powerAddress" 58ms

And I enter "ipmiusr" as "powerUsername" 60ms

And I enter "test" as "powerPassword" 57ms

And I click on "Save" 586ms

Then I should see a "Power settings saved" text 77ms

And the cobbler report should contain "Power Management Address : fakeipmi" for "sle_minion" 1s 732ms

And the cobbler report should contain "Power Management Username : ipmiusr" for "sle_minion" 1s 311ms

And the cobbler report should contain "Power Management Password : test" for "sle_minion" 1s 351ms

And the cobbler report should contain "Power Management Type : ipmilan" for "sle_minion" 1s 330ms

Scenario:
Test IPMI functions
21s 858ms 18

When I follow "Provisioning" in the content area 65ms

And I follow "Power Management" in the content area 61ms

And I click on "Power On" 2s 855ms

And I click on "Get status" 745ms

Then I should see the power is "On" 25ms

When I click on "Power Off" 2s 789ms

Then I should see a "system has been powered off" text 72ms

And I should see the power is "Unknown" 22ms

When I click on "Get status" 650ms

Then I should see the power is "Off" 21ms

When I click on "Power On" 2s 798ms

Then I should see a "system has been powered on" text 72ms

When I click on "Get status" 678ms

Then I should see the power is "On" 20ms

When I click on "Reboot" 10s 112ms

Then I should see a "system has been rebooted" text 75ms

When I click on "Get status" 769ms

Then I should see the power is "On" 22ms

Scenario:
Check power management SSM configuration
8s 134ms 21

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

And I click on the clear SSM button 117ms

And I check the "sle_minion" client 446ms

And I follow the left menu "Systems > System Set Manager > Overview" 522ms

And I follow "Configure power management" in the content area 69ms

Then I should see "sle_minion" as link 29ms

And I should see a "Change Power Management Configuration" text 76ms

And I should see a "Type" text 74ms

And I should see a "Network address" text 78ms

And I should see a "Username" text 76ms

And I should see a "Password" text 75ms

And I should see a "System identifier" text 74ms

And I should see a "Update" button 17ms

When I enter "testing" as "powerUsername" 49ms

And I enter "qwertz" as "powerPassword" 52ms

And I click on "Update" 61ms

Then I should see a "Configuration successfully saved for 1 system(s)" text 466ms

And the cobbler report should contain "Power Management Username : testing" for "sle_minion" 1s 686ms

And the cobbler report should contain "Power Management Password : qwertz" for "sle_minion" 1s 332ms

And the cobbler report should contain "Power Management Address : fakeipmi" for "sle_minion" 1s 318ms

And the cobbler report should contain "Power Management Type : ipmilan" for "sle_minion" 1s 334ms

Scenario:
Check power management SSM operation
237ms 6

And I follow the left menu "Systems > System Set Manager > Overview" 90ms

When I follow "power management operations" in the content area 76ms

Then I should see "sle_minion" as link 17ms

And I should see a "Power On" button 17ms

And I should see a "Power Off" button 17ms

And I should see a "Reboot" button 18ms

Scenario:
Cleanup: reset IPMI values
6s 800ms 8

Given I want to operate on this "sle_minion" 393ms

When I set power management value "" for "powerAddress" 364ms

And I set power management value "" for "powerUsername" 356ms

And I set power management value "" for "powerPassword" 361ms

Then the cobbler report should contain "Power Management Address :" for "sle_minion" 1s 314ms

And the cobbler report should contain "Power Management Username :" for "sle_minion" 1s 378ms

And the cobbler report should contain "Power Management Password :" for "sle_minion" 1s 319ms

And the cobbler report should contain "Power Management Type : ipmilan" for "sle_minion" 1s 312ms

Scenario:
Cleanup: tear down the IPMI host
481ms 1

When the server stops mocking an IPMI host 481ms

Scenario:
Cleanup: remove remaining systems from SSM after power management tests
58ms 1

When I click on the clear SSM button 58ms

Scenario:
Check for errors in Cobbler monitoring
4s 787ms 1

Then the local logs for Cobbler should not contain errors 4s 787ms

@skip_if_github_validation @scope_api @sle_minion
Feature:IPMI Power management API 30s 485ms 6

Scenario:
Setup an IPMI host for API test
1s 13ms 2

When the server starts mocking an IPMI host 656ms

And I want to operate on this "sle_minion" 357ms

Scenario:
Check the power management settings for API test
376ms 2

When I fetch power management values 376ms

Then power management results should have "ipmilan" for "powerType" < 1ms

Scenario:
Save power management values for API test
6s 988ms 8

When I set power management value "fakeipmi" for "powerAddress" 379ms

And I set power management value "ipmiusr" for "powerUsername" 385ms

And I set power management value "test" for "powerPassword" 390ms

And I set power management value "ipmilan" for "powerType" 365ms

Then the cobbler report should contain "Power Management Address : fakeipmi" for "sle_minion" 1s 353ms

And the cobbler report should contain "Power Management Username : ipmiusr" for "sle_minion" 1s 352ms

And the cobbler report should contain "Power Management Password : test" for "sle_minion" 1s 358ms

And the cobbler report should contain "Power Management Type : ipmilan" for "sle_minion" 1s 402ms

Scenario:
Test IPMI functions for API test
14s 777ms 6

When I turn power on 2s 707ms

Then the power status is "on" 546ms

When I turn power off 2s 659ms

Then the power status is "off" 534ms

When I do power management reboot 7s 806ms

Then the power status is "on" 522ms

Scenario:
Cleanup: reset IPMI values for API test
6s 852ms 7

When I set power management value "" for "powerAddress" 374ms

And I set power management value "" for "powerUsername" 385ms

And I set power management value "" for "powerPassword" 372ms

Then the cobbler report should contain "Power Management Address :" for "sle_minion" 1s 666ms

And the cobbler report should contain "Power Management Username :" for "sle_minion" 1s 356ms

And the cobbler report should contain "Power Management Password :" for "sle_minion" 1s 313ms

And the cobbler report should contain "Power Management Type : ipmilan" for "sle_minion" 1s 382ms

Scenario:
Cleanup: tear down the IPMI host for API test
477ms 1

When the server stops mocking an IPMI host 477ms

@skip_if_github_validation @scope_power_management @scope_cobbler @sle_minion
Feature:Redfish Power management 51s 423ms 11

Scenario:
Setup a Redfish host
7s 314ms 1

When the controller starts mocking a Redfish host 7s 314ms

Scenario:
Log in as admin user
446ms 1

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

Scenario:
Start Cobbler monitoring
6s 468ms 1

When I start local monitoring of Cobbler 6s 468ms

Scenario:
Save power management values for Redfish
7s 160ms 13

Given I am on the Systems overview page of this "sle_minion" 1s 217ms

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

And I follow "Power Management" in the content area 67ms

And I enter the controller hostname as the redfish server address 101ms

And I enter "ipmiusr" as "powerUsername" 56ms

And I enter "test" as "powerPassword" 50ms

And I select "Redfish" from "powerType" 81ms

And I click on "Save" 63ms

Then I should see a "Power settings saved" text 80ms

And the cobbler report should contain ":8443" for "sle_minion" 1s 381ms

And the cobbler report should contain "Power Management Username : ipmiusr" for "sle_minion" 1s 327ms

And the cobbler report should contain "Power Management Password : test" for "sle_minion" 1s 323ms

And the cobbler report should contain "Power Management Type : redfish" for "sle_minion" 1s 340ms

Scenario:
Test Redfish functions
11s 94ms 18

When I follow "Provisioning" in the content area 69ms

And I follow "Power Management" in the content area 61ms

And I click on "Power On" 813ms

And I click on "Get status" 931ms

Then I should see the power is "On" 24ms

When I click on "Power Off" 58ms

Then I should see a "system has been powered off" text 79ms

And I should see the power is "Unknown" 23ms

When I click on "Get status" 53ms

Then I should see the power is "Off" 22ms

When I click on "Power On" 880ms

Then I should see a "system has been powered on" text 72ms

When I click on "Get status" 792ms

Then I should see the power is "On" 22ms

When I click on "Reboot" 6s 299ms

Then I should see a "system has been rebooted" text 78ms

When I click on "Get status" 787ms

Then I should see the power is "On" 21ms

Scenario:
Check power management SSM configuration for Redfish
7s 952ms 21

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

And I click on the clear SSM button 53ms

And I check the "sle_minion" client 424ms

And I follow the left menu "Systems > System Set Manager > Overview" 431ms

And I follow "Configure power management" in the content area 74ms

Then I should see "sle_minion" as link 15ms

And I should see a "Change Power Management Configuration" text 82ms

And I should see a "Type" text 75ms

And I should see a "Network address" text 78ms

And I should see a "Username" text 75ms

And I should see a "Password" text 75ms

And I should see a "System identifier" text 77ms

And I should see a "Update" button 14ms

When I enter "testing" as "powerUsername" 50ms

And I enter "qwertz" as "powerPassword" 53ms

And I click on "Update" 413ms

Then I should see a "Configuration successfully saved for 1 system(s)" text 79ms

And the cobbler report should contain "Power Management Username : testing" for "sle_minion" 1s 723ms

And the cobbler report should contain "Power Management Password : qwertz" for "sle_minion" 1s 334ms

And the cobbler report should contain ":8443" for "sle_minion" 1s 334ms

And the cobbler report should contain "Power Management Type : redfish" for "sle_minion" 1s 346ms

Scenario:
Check power management SSM operation for Redfish
202ms 6

And I follow the left menu "Systems > System Set Manager > Overview" 74ms

When I follow "power management operations" in the content area 57ms

Then I should see "sle_minion" as link 27ms

And I should see a "Power On" button 14ms

And I should see a "Power Off" button 14ms

And I should see a "Reboot" button 13ms

Scenario:
Cleanup: reset Redfish values
7s 296ms 9

Given I want to operate on this "sle_minion" 399ms

When I set power management value "" for "powerAddress" 383ms

And I set power management value "" for "powerUsername" 455ms

And I set power management value "" for "powerPassword" 412ms

And I set power management value "ipmilan" for "powerType" 384ms

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

And the cobbler report should contain "Power Management Password :" for "sle_minion" 1s 304ms

And the cobbler report should contain "Power Management Type : ipmilan" for "sle_minion" 1s 316ms

Scenario:
Cleanup: tear down the Redfish host
49ms 1

When the controller stops mocking a Redfish host 49ms

Scenario:
Cleanup: remove remaining systems from SSM after Redfish power management tests
66ms 1

When I click on the clear SSM button 66ms

Scenario:
Check for errors in Cobbler monitoring
3s 372ms 1

Then the local logs for Cobbler should not contain errors 3s 372ms

@scope_configuration_channels
Feature:Delete channels with child or clone is not allowed 16s 699ms 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 839ms 1

Given I am authorized 1s 839ms

Scenario:
Clone the first channel before deletion from UI test
2s 5ms 8

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

And I follow "Clone Channel" 382ms

And I select "Fake-Base-Channel-SUSE-like" as the origin channel 102ms

And I click on "Clone Channel" 407ms

Then I should see a "Create Software Channel" text 77ms

And I should see a "Current state of the channel" text 78ms

When I click on "Clone Channel" 691ms

Then I should see a "Clone of Fake-Base-Channel-SUSE-like" text 77ms

Scenario:
Clone the second channel using first channel as base
1s 845ms 8

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

And I follow "Clone Channel" 375ms

And I select "Clone of Fake-Base-Channel-SUSE-like" as the origin channel 45ms

And I click on "Clone Channel" 457ms

Then I should see a "Create Software Channel" text 76ms

And I should see a "Current state of the channel" text 74ms

When I click on "Clone Channel" 663ms

Then I should see a "Clone of Clone of Fake-Base-Channel-SUSE-like" text 77ms

Scenario:
Try to delete channel with clone
1s 402ms 7

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

And I follow "Clone of Fake-Base-Channel-SUSE-like" 487ms

And I follow "Delete Channel" 571ms

And I check "unsubscribeSystems" 83ms

And I click on "Delete Channel" 59ms

Then I should see a "Clone of Fake-Base-Channel-SUSE-like" text 64ms

And I should see a "Unable to delete channel" text 60ms

Scenario:
Delete channel without clones neither children
1s 853ms 7

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

And I follow "Clone of Clone of Fake-Base-Channel-SUSE-like" 493ms

And I follow "Delete Channel" 410ms

And I check "unsubscribeSystems" 81ms

And I click on "Delete Channel" 607ms

Then I should see a "Clone of Clone of Fake-Base-Channel-SUSE-like" text 95ms

And I should see a "has been deleted" text 90ms

Scenario:
Clone a child channel to the clone of x86_64 test channel
2s 372ms 9

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

And I follow "Clone Channel" 370ms

And I select "Fake-RPM-SUSE-Channel" as the origin channel 70ms

And I click on "Clone Channel" 391ms

Then I should see a "Create Software Channel" text 77ms

And I should see a "Current state of the channel" text 74ms

When I select "Clone of Fake-Base-Channel-SUSE-like" from "Parent Channel" 72ms

And I click on "Clone Channel" 1s 157ms

Then I should see a "Clone of Fake-RPM-SUSE-Channel" text 78ms

Scenario:
Try delete channel with child
1s 619ms 8

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

And I follow "Clone of Fake-Base-Channel-SUSE-like" 476ms

And I follow "Delete Channel" 393ms

And I check "unsubscribeSystems" 68ms

And I click on "Delete Channel" 419ms

Then I should see a "Clone of Fake-Base-Channel-SUSE-like" text 61ms

And I should see a "channel has child channels associated" text 59ms

And I should see a "must delete those channels first before deleting the parent." text 65ms

Scenario:
Cleanup: remove cloned child channel
1s 901ms 7

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

And I follow "Clone of Fake-RPM-SUSE-Channel" 401ms

And I follow "Delete Channel" 482ms

And I check "unsubscribeSystems" 70ms

And I click on "Delete Channel" 741ms

Then I should see a "Clone of Fake-RPM-SUSE-Channel" text 64ms

And I should see a "has been deleted." text 60ms

Scenario:
Cleanup: remove cloned parent channel
1s 859ms 7

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

And I follow "Clone of Fake-Base-Channel-SUSE-like" 468ms

And I follow "Delete Channel" 313ms

And I check "unsubscribeSystems" 71ms

And I click on "Delete Channel" 740ms

Then I should see a "Clone of Fake-Base-Channel-SUSE-like" text 93ms

And I should see a "has been deleted." text 85ms

@scope_configuration_channels
Feature:Deleting channels with children or clones is not allowed 9s 986ms 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 957ms 1

Given I am authorized 1s 957ms

Scenario:
Clone the first channel before deletion from tool test
1s 977ms 8

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

And I follow "Clone Channel" 392ms

And I select "Fake-RPM-SUSE-Channel" as the origin channel 56ms

And I click on "Clone Channel" 383ms

Then I should see a "Create Software Channel" text 80ms

And I should see a "Current state of the channel" text 78ms

When I click on "Clone Channel" 729ms

Then I should see a "Clone of Fake-RPM-SUSE-Channel" text 74ms

Scenario:
Clone a second channel using first channel as base
1s 831ms 8

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

And I follow "Clone Channel" 365ms

And I select "Clone of Fake-RPM-SUSE-Channel" as the origin channel 69ms

And I click on "Clone Channel" 402ms

Then I should see a "Create Software Channel" text 80ms

And I should see a "Current state of the channel" text 76ms

When I click on "Clone Channel" 685ms

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

Scenario:
Verify if both clone channels exists
1s 314ms 3

When I list channels with spacewalk-remove-channel 1s 314ms

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
963ms 5

When I delete these channels with spacewalk-remove-channel: 963ms
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 942ms 4

When I delete these channels with spacewalk-remove-channel: 998ms
clone-fake-rpm-suse-channel
clone-clone-fake-rpm-suse-channel

And I list channels with spacewalk-remove-channel 943ms

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 55s 997ms 14 1

Scenario:
Log in as org admin user
1s 854ms 1

Given I am authorized 1s 854ms

Scenario:
Create a single calendar
4s 899ms 9

URL: https://uyuni-master-server.sumaci.aws/pub/maintenance-windows-exchange.ics

When I follow the left menu "Schedule > Maintenance Windows > Calendars" 965ms

And I wait for "1" second 1s

Then I should see a "No calendars created" text 55ms

When I click on "Create" in element "maintenance-windows" 83ms

Then I should see a "Calendar Name" text 56ms

When I enter "singlecalendar" as "name" 82ms

And I add "maintenance-windows-exchange.ics" calendar file as url 2s 332ms

And I click on "Create Calendar" 62ms

Then I should see a "Calendar successfully created" text 261ms

Scenario:
Create a multi calendar
3s 576ms 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" 95ms

And I wait for "1" second 1s

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

When I click on "Create" in element "maintenance-windows" 66ms

Then I should see a "Calendar Name" text 53ms

When I enter "multicalendar" as "name" 69ms

And I add "maintenance-windows-multi-exchange-1.ics" calendar file as url 1s 895ms

And I click on "Create Calendar" 71ms

Then I should see a "Calendar successfully created" text 265ms

Scenario:
Create a single schedule
2s 859ms 11

When I follow the left menu "Schedule > Maintenance Windows > Schedules" 88ms

And I wait for "1" second 1s

Then I should see a "No schedules created" text 57ms

When I click on "Create" in element "maintenance-windows" 66ms

Then I should see a "Schedule Name" text 54ms

When I enter "singleschedule" as "name" 73ms

And I choose "SINGLE" 60ms

And I click on "Add Calendar" 73ms

And I select "singlecalendar" from "calendarSelect" 1s 140ms

And I click on "Create Schedule" 65ms

Then I should see a "Schedule successfully created" text 180ms

Scenario:
Create a multi schedule
2s 840ms 11

When I follow the left menu "Schedule > Maintenance Windows > Schedules" 90ms

And I wait for "1" second 1s

Then I should see a "Items 1 - 1 of 1" text 62ms

When I click on "Create" in element "maintenance-windows" 65ms

Then I should see a "Schedule Name" text 56ms

When I enter "SAP Maintenance Window" as "name" 88ms

And I choose "MULTI" 63ms

And I click on "Add Calendar" 61ms

And I select "multicalendar" from "calendarSelect" 1s 112ms

And I click on "Create Schedule" 54ms

Then I should see a "Schedule successfully created" text 184ms

Scenario:
Create another multi schedule
2s 749ms 10

When I follow the left menu "Schedule > Maintenance Windows > Schedules" 88ms

And I wait for "1" second 1s

Then I should see a "Items 1 - 2 of 2" text 66ms

When I click on "Create" 62ms

And I enter "Core Server Window" as "name" 77ms

And I choose "MULTI" 51ms

And I click on "Add Calendar" 60ms

And I select "multicalendar" from "calendarSelect" 1s 105ms

And I click on "Create Schedule" 55ms

Then I should see a "Schedule successfully created" text 182ms

Scenario:
Assign a single system to the single schedule
2s 290ms 5

Given I am on the Systems overview page of this "sle_minion" 1s 33ms

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

And I select "singleschedule" from "maintenance-schedule" 71ms

And I click on "Update Properties" 1s 19ms

Then I should see a "System properties changed" text 87ms

Scenario:
Assign systems to the multi schedule using SSM
4s 386ms 10

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

And I click on the clear SSM button 63ms

And I check the "rhlike_minion" client 2s 36ms

And I follow the left menu "Systems > System Set Manager > Overview" 521ms

And I follow "Assign" in the content area 77ms

And I select "SAP Maintenance Window" from "scheduleId" 1s 132ms

And I check "cancelActions" 89ms

And I click on "Assign All" 71ms

And I click on "Confirm" 71ms

Then I should see a "Maintenance schedule has been assigned" text 176ms

@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
19s 194ms 3

When I remove package "virgo-dummy" from this "rhlike_minion" without error control 1s 474ms

And I refresh packages list via spacecmd on "rhlike_minion" 3s 569ms

And I wait until refresh package list on "rhlike_minion" is finished 14s 150ms

Scenario:
Schedule package installation action
4s 443ms 10

Given I am on the Systems overview page of this "rhlike_minion" 986ms

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

And I follow "Install" 588ms

And I enter "virgo-dummy" as the filtered package name 56ms

And I click on the filter button 631ms

And I check "virgo-dummy" in the list 58ms

And I click on "Install Packages" 1s 95ms

And I select the next maintenance window 41ms

And I click on "Confirm" 852ms

Then I should see a "1 package install has been scheduled for" text 61ms

Scenario:
Detach systems from schedules
2s 510ms 8

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

And I click on the clear SSM button 52ms

And I check the "sle_minion" client 435ms

And I follow the left menu "Systems > System Set Manager > Overview" 488ms

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

And I select "None - clear schedule" from "scheduleId" 1s 112ms

And I click on "Clear All" 66ms

Then I should see a "Maintenance schedule has been cleared" text 176ms

Scenario:
Cleanup: cancel all scheduled actions
1s 270ms 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 270ms

Scenario:
Delete maintenance schedules
2s 9ms 13

When I follow the left menu "Schedule > Maintenance Windows > Schedules" 506ms

And I click the "Core Server Window" item delete button 254ms

Then I should see a "Delete maintenance schedule" text 68ms

When I click on the red confirmation button 69ms

And I wait until I see "Schedule 'Core Server Window' has been deleted." text 188ms

And I click the "SAP Maintenance Window" item delete button 144ms

Then I should see a "Delete maintenance schedule" text 63ms

When I click on the red confirmation button 60ms

And I wait until I see "Schedule 'SAP Maintenance Window' has been deleted." text 181ms

And I click the "singleschedule" item delete button 159ms

Then I should see a "Delete maintenance schedule" text 66ms

When I click on the red confirmation button 60ms

And I wait until I see "singleschedule' has been deleted." text 184ms

Scenario:
Delete maintenance calendars
1s 112ms 9

When I follow the left menu "Schedule > Maintenance Windows > Calendars" 89ms

And I click the "singlecalendar" item delete button 235ms

Then I should see a "Delete maintenance calendar" text 73ms

When I click on the red confirmation button 66ms

And I wait until I see "Calendar 'singlecalendar' has been deleted." text 185ms

And I click the "multicalendar" item delete button 157ms

Then I should see a "Delete maintenance calendar" text 62ms

When I click on the red confirmation button 60ms

And I wait until I see "Calendar 'multicalendar' has been deleted." text 180ms

@flaky @scope_visualization @scope_salt
Feature:Create organizations, users, groups, and activation keys using Salt states 38s 319ms 13 2

Scenario:
Log in as org admin user
1s 748ms 1

Given I am authorized 1s 748ms

@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
12s 742ms 1

When I apply "setup_users_configuration" local salt state on "server" 12s 742ms

Scenario:
Organization my_org was correctly created
2s 507ms 5

Given I am authorized as "my_org_user" with password "my_org_user" 2s 291ms

When I follow the left menu "Home > My Organization" 77ms

Then I should see a "my_org" text in the content area 29ms

When I follow the left menu "Home > My Organization > Organization Trusts" 84ms

Then I should see a "my_org2" text in the content area 23ms

Scenario:
Organization my_org2 was correctly created
1s 972ms 5

Given I am authorized as "my_org_user2" with password "my_org_user2" 1s 789ms

When I follow the left menu "Home > My Organization" 61ms

Then I should see a "my_org2" text in the content area 23ms

When I follow the left menu "Home > My Organization > Organization Trusts" 73ms

Then I should see a "my_org" text in the content area 23ms

Scenario:
Group was correctly created
2s 373ms 5

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

When I follow the left menu "Systems > System Groups" 123ms

When I follow "minions_group" 411ms

Then I should see a "minions_group" text 65ms

And I should see a "System Group Status" text 67ms

Scenario:
User was correctly created
2s 166ms 5

Given I am authorized as "user2" with password "user2" 1s 558ms

When I follow the left menu "Systems > System Groups" 113ms

And I follow "minions_group" 374ms

Then I should see a "minions_group" text 62ms

And I should see a "System Group Status" text 57ms

Scenario:
User channels permissions were assigned
3s 361ms 5

Given I am authorized as "user2" with password "user2" 355ms

When I follow the left menu "Software > Channel List > All" 213ms

And I follow "Show All Child Channels" 79ms

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

And I follow "Managers" 2s 307ms

Scenario:
User Roles were assigned
2s 150ms 9

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

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

And I follow "user2" 426ms

Then I should see a "User Details" text 76ms

And I should see "role_activation_key_admin" as checked 22ms

And I should see "role_image_admin" as unchecked 19ms

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

Scenario:
Activation Key was correctly created
524ms 6

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

And I follow "My Activation Key created via Salt" 265ms

Then I should see "10" in field identified by "usageLimit" 26ms

And I should see "virtualization_host" as checked 21ms

And I should see a "Push via SSH" text 74ms

And I should see "enable-config-auto-deploy" as checked 21ms

Scenario:
Cleanup: apply configuration teardown salt state to server
8s 64ms 1

When I apply "teardown_users_configuration" local salt state on "server" 8s 64ms

@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
253ms 3

When I follow the left menu "Admin > Organizations" 126ms

Then I should not see a "my_org" text 65ms

And I should not see a "my_org2" text 61ms

Scenario:
Cleanup: user was successfully removed
264ms 2

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

Then I should not see a "user2" text 94ms

Scenario:
Cleanup: activation key was successfully removed
191ms 2

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

Then I should not see a "My Activation Key created via Salt" text 79ms

@flaky
Feature:Export and import software channels with new ISS implementation 46s 579ms 10

Distribute software between servers
Run export and import with ISS v2

Scenario:
Install inter server sync package
3s 141ms 2

When I install packages "inter-server-sync" on this "server" 2s 463ms

Then "inter-server-sync" should be installed on "server" 678ms

Scenario:
Log in as org admin user
1s 865ms 1

Given I am authorized 1s 865ms

Scenario:
Clone a channel with patches
2s 306ms 9

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

And I follow "Clone Channel" 457ms

And I select "Fake-RPM-SUSE-Channel" as the origin channel 77ms

And I choose "current" 53ms

And I click on "Clone Channel" 440ms

And I should see a "Create Software Channel" text 76ms

And I should see a "Current state of the channel" text 75ms

And I click on "Clone Channel" 857ms

Then I should see a "Clone of Fake-RPM-SUSE-Channel" text 77ms

Scenario:
Check that this channel has patches
1s 377ms 8

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

And I follow "Clone of Fake-RPM-SUSE-Channel" 486ms

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

And I follow "List/Remove Patches" 692ms

Then I should see a "CL-hoag-dummy-7890" link 12ms

And I should see a "CL-virgo-dummy-3456" link 11ms

And I should see a "CL-milkyway-dummy-2345" link 11ms

And I should see a "CL-andromeda-dummy-6789" link 12ms

Scenario:
Export data with ISS v2
18s 617ms 3

When I ensure folder "/tmp/export_iss_v2" doesn't exist on "server" 786ms

When I export software channels "clone-fake-rpm-suse-channel" with ISS v2 to "/tmp/export_iss_v2" 17s 160ms

Then "/tmp/export_iss_v2" folder on server is ISS v2 export directory 669ms

Scenario:
Cleanup: remove cloned channels
1s 812ms 6

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

And I follow "Clone of Fake-RPM-SUSE-Channel" 480ms

And I follow "Delete Channel" 403ms

And I check "unsubscribeSystems" 82ms

And I click on "Delete Channel" 709ms

Then I should see a "Clone of Fake-RPM-SUSE-Channel" text 61ms

Scenario:
Import data with ISS v2
13s 148ms 1

When I import data with ISS v2 from "/tmp/export_iss_v2" 13s 148ms

Scenario:
Check that this channel was imported and has patches
1s 105ms 8

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

And I follow "Clone of Fake-RPM-SUSE-Channel" 481ms

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

And I follow "List/Remove Patches" 449ms

Then I should see a "CL-hoag-dummy-7890" link 8ms

And I should see a "CL-virgo-dummy-3456" link 8ms

And I should see a "CL-milkyway-dummy-2345" link 8ms

And I should see a "CL-andromeda-dummy-6789" link 7ms

Scenario:
Cleanup: remove imported channel
1s 772ms 6

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

When I follow "Clone of Fake-RPM-SUSE-Channel" 461ms

And I follow "Delete Channel" 395ms

And I check "unsubscribeSystems" 69ms

And I click on "Delete Channel" 708ms

Then I should see a "Clone of Fake-RPM-SUSE-Channel" text 66ms

Scenario:
Cleanup: remove ISS v2 export folder
1s 432ms 1

When I ensure folder "/tmp/export_iss_v2" doesn't exist on "server" 1s 432ms

Feature:Export and import configuration channels with new ISS implementation 22s 886ms 10

Distribute configuration between servers
Run export and import with ISS v2

Scenario:
Install inter server sync package
1s 527ms 2

When I install packages "inter-server-sync" on this "server" 870ms

Then "inter-server-sync" should be installed on "server" 656ms

Scenario:
Log in as org admin user
2s 14ms 1

Given I am authorized 2s 14ms

Scenario:
Create a configuration channel
720ms 7

When I follow the left menu "Configuration > Channels" 121ms

And I follow "Create Config Channel" 253ms

And I enter "Test Config Channel" as "cofName" 72ms

And I enter "testconfigchannel" as "cofLabel" 66ms

And I enter "This is a test configuration channel" as "cofDescription" 77ms

And I click on "Create Config Channel" 67ms

Then I should see a "Test Config Channel" text 62ms

Scenario:
Add a configuration file to the test configuration channel
2s 573ms 9

When I follow the left menu "Configuration > Channels" 66ms

And I follow "Test Config Channel" 403ms

And I follow "Create Configuration File or Directory" 383ms

And I enter "/etc/s-mgr/config" as "cffPath" 69ms

And I enter "COLOR=white" in the editor 8ms

And I click on "Create Configuration File" 66ms

Then I should see a "Revision 1 of /etc/s-mgr/config from channel Test Config Channel" text 94ms

And file "/srv/susemanager/salt/manager_org_1/testconfigchannel/init.sls" should exist on server 787ms

And file "/srv/susemanager/salt/manager_org_1/testconfigchannel/etc/s-mgr/config" should exist on server 694ms

Scenario:
Export data with ISS v2
7s 48ms 3

When I ensure folder "/tmp/export_iss_v2" doesn't exist on "server" 670ms

When I export config channels "testconfigchannel" with ISS v2 to "/tmp/export_iss_v2" 5s 708ms

Then "/tmp/export_iss_v2" folder on server is ISS v2 export directory 669ms

Scenario:
Cleanup: remove the test configuration channel
1s 814ms 6

When I follow the left menu "Configuration > Channels" 64ms

And I follow "Test Config Channel" 469ms

And I follow "Delete Channel" 408ms

And I click on "Delete Config Channel" 58ms

Then file "/srv/susemanager/salt/manager_org_1/testconfigchannel/init.sls" should not exist on server 805ms

And I should not see a "Test Config Channel" link 8ms

Scenario:
Import data with ISS v2
2s 669ms 1

When I import data with ISS v2 from "/tmp/export_iss_v2" 2s 669ms

Scenario:
Check that the config channel was imported
1s 495ms 4

When I follow the left menu "Configuration > Channels" 62ms

Then I should see a "Test Config Channel" link 9ms

And file "/srv/susemanager/salt/manager_org_1/testconfigchannel/init.sls" should exist on server 760ms

And file "/srv/susemanager/salt/manager_org_1/testconfigchannel/etc/s-mgr/config" should exist on server 664ms

Scenario:
Cleanup: remove the test configuration channel
1s 674ms 6

When I follow the left menu "Configuration > Channels" 58ms

And I follow "Test Config Channel" 425ms

And I follow "Delete Channel" 272ms

And I click on "Delete Config Channel" 53ms

Then file "/srv/susemanager/salt/manager_org_1/testconfigchannel/init.sls" should not exist on server 858ms

And I should not see a "Test Config Channel" link 5ms

Scenario:
Cleanup: remove ISS v2 export folder
1s 346ms 1

When I ensure folder "/tmp/export_iss_v2" doesn't exist on "server" 1s 346ms

@skip_if_github_validation @sle_minion @scope_salt @new_issue @flaky
Feature:Salt master integration with Git pillar 56s 256ms 6

Scenario:
Pre-requisite: Enabling repositories for installing git-core
1s 622ms 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 829ms

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

Scenario:
Preparing Git pillar configuration for Salt master
19s 667ms 3

When I setup a git_pillar environment on the Salt master 5s 923ms

And I wait until Salt master can reach "sle_minion" 13s 30ms

Then file "/etc/salt/master.d/zz-testing-gitpillar.conf" should exist on server 714ms

Scenario:
Check for the expected pillar data after enabling Git pillar
11s 105ms 5

When I refresh the pillar data 2s 264ms

And I wait until there is no pillar refresh salt job active 2s 888ms

Then the pillar data for "org_id" should be "1" on "sle_minion" 1s 555ms

And the pillar data for "git_pillar_foobar" should be "12345" on "sle_minion" 1s 546ms

And the pillar data for "git_pillar_foobar" should be "12345" on the Salt master 2s 849ms

Scenario:
Cleanup: Remove Git pillar configuration for Salt master
14s 625ms 3

When I clean up the git_pillar environment on the Salt master 910ms

And I wait until Salt master can reach "sle_minion" 13s 20ms

Then file "/etc/salt/master.d/zz-testing-gitpillar.conf" should not exist on server 694ms

Scenario:
Cleanup: Check for the expected pillar data after disabling Git pillar
7s 937ms 4

When I refresh the pillar data 2s 127ms

Then the pillar data for "git_pillar_foobar" should be empty on "sle_minion" 1s 546ms

And the pillar data for "org_id" should be "1" on "sle_minion" 1s 542ms

And the pillar data for "git_pillar_foobar" should be empty on the Salt master 2s 720ms

Scenario:
Pre-Cleanup: Disabling repositories for uninstalling git-core
1s 297ms 2

When I remove repository "SLE-Module-Basesystem15-SP7-Updates" on "server" without error control 646ms

And I remove repository "SLE-Module-Basesystem15-SP7-Pool" on "server" without error control 650ms

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

Scenario:
Log in as org admin user
1s 807ms 1

Given I am authorized 1s 807ms

@ssh_minion
Scenario:
Reboot the SSH-managed SLES minion
3m 56s 31ms 6

Given I am on the Systems overview page of this "ssh_minion" 4s 983ms

When I follow first "Schedule System Reboot" 575ms

Then I should see a "System Reboot Confirmation" text 75ms

And I should see a "Reboot system" button 18ms

When I click on "Reboot system" 940ms

Then I wait and check that "ssh_minion" has rebooted 3m 49s 436ms

Scenario:
Schedule a reboot on a SLES Salt minion
4m 16s 42ms 8

2026-03-04 20:59:53 +0100 Still waiting for action to complete...

Given I am on the Systems overview page of this "sle_minion" 995ms

When I follow first "Schedule System Reboot" 489ms

Then I should see a "System Reboot Confirmation" text 69ms

And I should see a "Reboot system" button 15ms

And I click on "Reboot system" 864ms

Then I should see a "Reboot scheduled for system" text 92ms

When I wait at most 600 seconds until event "System reboot scheduled" is completed 4m 13s 457ms

And I should see a "Reboot completed." text 58ms

@rhlike_minion
Scenario:
Reboot the Red Hat-like minion and wait until reboot is completed
3m 59s 381ms 8

2026-03-04 21:04:09 +0100 Still waiting for action to complete...

Given I am on the Systems overview page of this "rhlike_minion" 976ms

When I follow first "Schedule System Reboot" 583ms

Then I should see a "System Reboot Confirmation" text 66ms

And I should see a "Reboot system" button 19ms

When I click on "Reboot system" 935ms

Then I should see a "Reboot scheduled for system" text 82ms

When I wait at most 600 seconds until event "System reboot scheduled" is completed 3m 56s 657ms

Then I should see a "Reboot completed." text 59ms

@deblike_minion
Scenario:
Reboot the Debian-like minion and wait until reboot is completed
3m 47s 108ms 8

2026-03-04 21:08:13 +0100 Still waiting for action to complete...

Given I am on the Systems overview page of this "deblike_minion" 5s 242ms

When I follow first "Schedule System Reboot" 577ms

Then I should see a "System Reboot Confirmation" text 73ms

And I should see a "Reboot system" button 18ms

When I click on "Reboot system" 860ms

Then I should see a "Reboot scheduled for system" text 91ms

When I wait at most 600 seconds until event "System reboot scheduled" is completed 3m 40s 182ms

Then I should see a "Reboot completed." text 61ms

@skip_if_github_validation @sle_minion @scope_cve_audit
Feature:CVE Audit on SLE Salt Minions 2m 6s 840ms 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 292ms 1

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

Scenario:
Pre-requisite: downgrade milkyway-dummy to lower version
42s 756ms 9

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 949ms

And I install old package "milkyway-dummy-1.0" on this "sle_minion" 1s 451ms

And I refresh the metadata for "sle_minion" 879ms

And I follow the left menu "Admin > Task Schedules" 146ms

And I follow "errata-cache-default" 1s 210ms

And I follow "errata-cache-bunch" 1s 214ms

And I click on "Single Run Schedule" 1s 524ms

Then I should see a "bunch was scheduled" text 271ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 35s 108ms

Scenario:
Schedule channel data refresh
4s 261ms 6

When I follow the left menu "Admin > Task Schedules" 90ms

And I follow "cve-server-channels-default" 1s 341ms

And I follow "cve-server-channels-bunch" 1s 146ms

And I click on "Single Run Schedule" 337ms

Then I should see a "bunch was scheduled" text 60ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 1s 285ms

Scenario:
Display CVE audit page
225ms 3

When I follow the left menu "Audit > CVE Audit" 130ms

Then I should see a "CVE Audit" link in the left menu 25ms

And I should see a "CVE Audit" text 69ms

Scenario:
Search for a known CVE number
21s 535ms 14

When I follow the left menu "Audit > CVE Audit" 63ms

And I select "1999" from "cveIdentifierYear" 74ms

And I enter "9999" as "cveIdentifierId" 74ms

And I click on "Audit Servers" 64ms

Then I should see "sle_minion" as link 837ms

And I should see a "Affected, at least one patch available in an assigned channel" text 89ms

And I should see a "Install a new patch on this system" link 12ms

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 17ms

And I should see a "extra CVE data update" link 16ms

Then I follow "Install a new patch on this system" on "sle_minion" row 20s 86ms

And I should see a "Relevant Patches" text 83ms

Scenario:
Search for an unknown CVE number
473ms 5

When I follow the left menu "Audit > CVE Audit" 113ms

And I select "2012" from "cveIdentifierYear" 58ms

And I enter "2806" as "cveIdentifierId" 59ms

And I click on "Audit Servers" 54ms

Then I should see a "The specified CVE number was not found" text 187ms

Scenario:
Select a system for the System Set Manager
1s 989ms 11

And I click on the clear SSM button 65ms

And I follow the left menu "Audit > CVE Audit" 60ms

And I select "1999" from "cveIdentifierYear" 49ms

And I enter "9999" as "cveIdentifierId" 58ms

And I click on "Audit Servers" 52ms

Then I should see a "Affected, at least one patch available in an assigned channel" text 71ms

When I check the "sle_minion" client 731ms

Then I should see a "system selected" text 215ms

When I follow the left menu "Systems > System List > All" 187ms

Then I should see "sle_minion" as link 444ms

And I click on the clear SSM button 52ms

Scenario:
List systems by patch status via API before patch
7s 196ms 12

Result list: [{"errata_advisories"=>[], "system_id"=>1000010003, "channel_labels"=>[], "patch_status"=>"NOT_AFFECTED"}, {"errata_advisories"=>[], "system_id"=>1000010001, "channel_labels"=>[], "patch_status"=>"NOT_AFFECTED"}, {"errata_advisories"=>[], "system_id"=>1000010004, "channel_labels"=>[], "patch_status"=>"NOT_AFFECTED"}, {"errata_advisories"=>[], "system_id"=>1000010000, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}, {"errata_advisories"=>[], "system_id"=>1000010005, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}, {"errata_advisories"=>[], "system_id"=>1000010002, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}]
Result list: [{"errata_advisories"=>["milkyway-dummy-2345"], "system_id"=>1000010003, "channel_labels"=>["fake-rpm-suse-channel"], "patch_status"=>"AFFECTED_FULL_PATCH_APPLICABLE"}, {"errata_advisories"=>["milkyway-dummy-2345"], "system_id"=>1000010001, "channel_labels"=>["fake-base-channel-rh-like"], "patch_status"=>"AFFECTED_FULL_PATCH_APPLICABLE"}, {"errata_advisories"=>[], "system_id"=>1000010004, "channel_labels"=>[], "patch_status"=>"NOT_AFFECTED"}, {"errata_advisories"=>[], "system_id"=>1000010000, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}, {"errata_advisories"=>[], "system_id"=>1000010005, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}, {"errata_advisories"=>[], "system_id"=>1000010002, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}]
result: {"errata_advisories"=>["milkyway-dummy-2345"], "system_id"=>1000010003, "channel_labels"=>["fake-rpm-suse-channel"], "patch_status"=>"AFFECTED_FULL_PATCH_APPLICABLE"}

When I follow the left menu "Admin > Task Schedules" 130ms

And I follow "cve-server-channels-default" 1s 339ms

And I follow "cve-server-channels-bunch" 1s 160ms

And I click on "Single Run Schedule" 365ms

Then I should see a "bunch was scheduled" text 66ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 1s 265ms

When I call audit.list_systems_by_patch_status() with CVE identifier "CVE-1999-9979" 1s 111ms

Then I should get status "NOT_AFFECTED" for "sle_minion" 372ms

When I call audit.list_systems_by_patch_status() with CVE identifier "CVE-1999-9999" 1s 20ms

Then I should get status "AFFECTED_FULL_PATCH_APPLICABLE" for "sle_minion" 365ms

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
42s 582ms 10

Given I am on the Systems overview page of this "sle_minion" 1s 151ms

When I follow "Software" in the content area 74ms

And I follow "Patches" in the content area 67ms

And I enter "milkyway" as the filtered synopsis 48ms

And I click on the filter button 622ms

And I check "milkyway-dummy-2345" in the list 59ms

And I click on "Apply Patches" 691ms

And I click on "Confirm" 853ms

Then I should see a "patch update has been scheduled" text 107ms

And I wait until event "Patch Update: milkyway-dummy-2345" is completed 38s 906ms

Scenario:
List systems by patch status via API after patch
1s 277ms 2

Result list: [{"errata_advisories"=>["milkyway-dummy-2345"], "system_id"=>1000010001, "channel_labels"=>["fake-base-channel-rh-like"], "patch_status"=>"AFFECTED_FULL_PATCH_APPLICABLE"}, {"errata_advisories"=>[], "system_id"=>1000010004, "channel_labels"=>[], "patch_status"=>"NOT_AFFECTED"}, {"errata_advisories"=>[], "system_id"=>1000010003, "channel_labels"=>[], "patch_status"=>"PATCHED"}, {"errata_advisories"=>[], "system_id"=>1000010000, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}, {"errata_advisories"=>[], "system_id"=>1000010005, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}, {"errata_advisories"=>[], "system_id"=>1000010002, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}]

And I call audit.list_systems_by_patch_status() with CVE identifier "CVE-1999-9999" 936ms

Then I should get status "PATCHED" for "sle_minion" 341ms

Scenario:
Cleanup: remove installed packages
2s 175ms 2

When I disable repository "test_repo_rpm_pool" on this "sle_minion" without error control 762ms

And I remove package "milkyway-dummy" from this "sle_minion" without error control 1s 413ms

Scenario:
Cleanup: remove remaining systems from SSM after CVE audit tests
72ms 1

When I click on the clear SSM button 72ms

@scope_openscap @scope_res @rhlike_minion
Feature:OpenSCAP audit of Red Hat-like Salt minion 3m 47s 239ms 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
527ms 1

Given I am authorized for the "Admin" section 527ms

@skip_if_github_validation
Scenario:
Enable repositories for openSCAP on the Red Hat-like minion
31s 69ms 2

When I enable the repositories "Rocky-BaseOS Rocky-AppStream" on this "rhlike_minion" 424ms

And I refresh the metadata for "rhlike_minion" 30s 645ms

@skip_if_github_validation
Scenario:
Install the OpenSCAP packages on the Red Hat-like minion
1m 27s 859ms 5

Given I am on the Systems overview page of this "rhlike_minion" 995ms

And I install OpenSCAP dependencies on "rhlike_minion" 46s 678ms

And I follow "Software" in the content area 79ms

And I click on "Update Package List" 1s 644ms

And I wait until event "Package List Refresh" is completed 38s 460ms

Scenario:
Schedule an OpenSCAP audit job on the Red Hat-like minion
1m 13s 688ms 10

Given I am on the Systems overview page of this "rhlike_minion" 947ms

When I follow "Audit" in the content area 81ms

And I follow "OpenSCAP" in the content area 66ms

And I follow "Schedule" in the content area 66ms

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 71ms

And I enter "--profile xccdf_org.ssgproject.content_profile_anssi_bp28_intermediary" as "params" 132ms

And I enter "/usr/share/xml/scap/ssg/content/ssg-rhel8-ds.xml" as "path" 93ms

And I click on "Schedule" 726ms

Then I should see a "XCCDF scan has been scheduled" text 74ms

And I wait at most 500 seconds until event "OpenSCAP xccdf scanning" is completed 1m 11s 427ms

Scenario:
Check the results of the OpenSCAP scan on the Red Hat-like minion
2s 920ms 7

Given I am on the Systems overview page of this "rhlike_minion" 979ms

When I follow "Audit" in the content area 82ms

And I follow "OpenSCAP" in the content area 88ms

And I follow "xccdf_org.open-scap_testresult" 1s 137ms

Then I should see a "Details of XCCDF Scan" text 222ms

And I should see a "RHEL-8" text 206ms

And I should see a "XCCDF Rule Results" text 202ms

Scenario:
Cleanup: remove audit scans retention period from Red Hat-like minion
915ms 6

When I follow the left menu "Admin > Organizations" 140ms

When I follow "SUSE Test" in the content area 76ms

And I follow "Configuration" in the content area 67ms

And I enter "0" as "scap_retention_period" 60ms

And I click on "Update Organization" 503ms

Then I should see a "Organization SUSE Test was successfully updated." text 65ms

Scenario:
Cleanup: delete audit results from Red Hat-like minion
3s 622ms 8

Given I am on the Systems overview page of this "rhlike_minion" 1s 74ms

When I follow "Audit" in the content area 66ms

And I follow "OpenSCAP" in the content area 60ms

And I follow "List Scans" in the content area 65ms

And I click on "Select All" 501ms

And I click on "Remove" 588ms

And I click on "Confirm" 1s 199ms

Then I should see a " SCAP Scan(s) deleted. 0 SCAP Scan(s) retained" text 66ms

Scenario:
Cleanup: restore audit scans retention period on Red Hat-like minion
405ms 6

When I follow the left menu "Admin > Organizations" 105ms

When I follow "SUSE Test" in the content area 61ms

And I follow "Configuration" in the content area 61ms

And I enter "90" as "scap_retention_period" 45ms

And I click on "Update Organization" 57ms

Then I should see a "Organization SUSE Test was successfully updated." text 73ms

@skip_if_github_validation
Scenario:
Cleanup: remove the OpenSCAP packages from the Red Hat-like minion
5s 267ms 2

When I remove OpenSCAP dependencies from "rhlike_minion" 5s 75ms

And I disable repository "Rocky-BaseOS" on this "rhlike_minion" 191ms

@skip_if_github_validation
Scenario:
Cleanup: restore the base channel for the Red Hat-like minion
20s 965ms 11

Warning: Radio button 'Fake-Base-Channel-RH-like' is already checked

Given I am on the Systems overview page of this "rhlike_minion" 956ms

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 71ms

And I check radio button "Fake-Base-Channel-RH-like" 136ms

And I wait until I do not see "Loading..." text 336ms

And I click on "Next" 63ms

Then I should see a "Confirm Software Channel Change" text 61ms

When I click on "Confirm" 70ms

Then I should see a "Changing the channels has been scheduled." text 304ms

And I wait until event "Subscribe channels scheduled" is completed 18s 819ms

@skip_if_github_validation @scope_res @rhlike_minion @new_issue
Feature:Remote command on the Red Hat-like Salt minion 28s 818ms 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
1s 848ms 1

Given I am authorized 1s 848ms

Scenario:
Run a remote command on the Red Hat-like minion
26s 969ms 11

When I follow the left menu "Salt > Remote Commands" 132ms

Then I should see a "Remote Commands" text in the content area 21ms

When I enter command "cat /etc/os-release" 89ms

And I enter target "rhlike_minion" 110ms

And I click on preview 11s 347ms

And I click on run 50ms

Then I should see "rhlike_minion" hostname 53ms

When I wait for "15" seconds 15s

And I expand the results for "rhlike_minion" 54ms

Then I should see a "rhel centos fedora" text 55ms

And I should see a "ROCKY_SUPPORT_PRODUCT" text 54ms

@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 57s 41ms 12

Scenario:
Log in as org admin user
1s 901ms 1

Given I am authorized 1s 901ms

Scenario:
Delete the Red Hat-like minion before SSH minion tests
4m 7s 366ms 7

When I am on the Systems overview page of this "rhlike_minion" 1s 922ms

And I follow "Delete System" 495ms

Then I should see a "Confirm System Profile Deletion" text 62ms

When I click on "Delete Profile" 67ms

And I wait until I see "has been deleted" text 4m 4s 68ms

And I wait until Salt client is inactive on "rhlike_minion" 330ms

Then "rhlike_minion" should not be registered 420ms

Scenario:
Bootstrap a SSH-managed Red Hat-like minion
2m 38s 700ms 11

The hostname of rhlike_minion is uyuni-master-rhlike-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 84ms

Then I should see a "Bootstrap Minions" text 71ms

When I check "manageWithSSH" 107ms

And I enter the hostname of "rhlike_minion" as "hostname" 151ms

And I enter "linux" as "password" 65ms

And I select the hostname of "proxy" from "proxies" if present 2s 832ms

And I click on "Bootstrap" 66ms

And I wait at most 480 seconds until I see "Bootstrap process initiated." text 52s 75ms

And I follow the left menu "Systems > System List > All" 160ms

And I wait until I see the name of "rhlike_minion", refreshing the page 57s 902ms

And I wait until onboarding is completed for "rhlike_minion" 45s 184ms

@proxy
Scenario:
Check connection from SSH-managed Red Hat-like minion to proxy
1s 298ms 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 65ms

Then I should see "proxy" short hostname 72ms

@proxy
Scenario:
Check registration on proxy of SSH-managed Red Hat-like minion
1s 297ms 4

Given I am on the Systems overview page of this "proxy" 1s 64ms

When I follow "Details" in the content area 65ms

And I follow "Proxy" in the content area 73ms

Then I should see "rhlike_minion" hostname 93ms

Scenario:
Subscribe the SSH-managed Red Hat-like minion to a base channel
51s 374ms 11

Given I am on the Systems overview page of this "rhlike_minion" 1s 34ms

When I follow "Software" in the content area 71ms

And I follow "Software Channels" in the content area 93ms

And I wait until I do not see "Loading..." text 64ms

And I check radio button "Fake-Base-Channel-RH-like" 10s 84ms

And I wait until I do not see "Loading..." text 413ms

And I click on "Next" 68ms

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 284ms

And I wait until event "Subscribe channels scheduled" is completed 39s 110ms

Scenario:
Check events history for failures on SSH-managed Red Hat-like minion
1m 2s 581ms 2

Given I am on the Systems overview page of this "rhlike_minion" 1s 415ms

Then I check for failed events on history event page 1m 1s 165ms

Scenario:
Run a remote command on the SSH-managed Red Hat-like minion
29s 819ms 11

When I follow the left menu "Salt > Remote Commands" 138ms

Then I should see a "Remote Commands" text in the content area 21ms

When I enter command "cat /etc/os-release" 100ms

And I enter target "rhlike_minion" 112ms

And I click on preview 14s 176ms

And I click on run 51ms

Then I should see "rhlike_minion" hostname 57ms

When I wait for "15" seconds 15s

And I expand the results for "rhlike_minion" 52ms

Then I should see a "rhel centos fedora" text 54ms

And I should see a "ROCKY_SUPPORT_PRODUCT" text 52ms

Scenario:
Check events history for failures on SSH-managed Red Hat-like minion
1m 12s 302ms 2

Given I am on the Systems overview page of this "rhlike_minion" 1s 94ms

Then I check for failed events on history event page 1m 11s 208ms

Scenario:
Cleanup: delete the SSH-managed Red Hat-like minion
14s 239ms 6

When I am on the Systems overview page of this "rhlike_minion" 1s 166ms

And I follow "Delete System" 473ms

Then I should see a "Confirm System Profile Deletion" text 62ms

When I click on "Delete Profile" 65ms

And I wait until I see "has been deleted" text 12s 13ms

Then "rhlike_minion" should not be registered 457ms

Scenario:
Cleanup: bootstrap a Red Hat-like minion after SSH minion tests
1m 45s 14ms 12

The hostname of rhlike_minion is uyuni-master-rhlike-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 86ms

Then I should see a "Bootstrap Minions" text 65ms

When I enter the hostname of "rhlike_minion" as "hostname" 152ms

And I enter "22" as "port" 55ms

And I enter "root" as "user" 66ms

And I enter "linux" as "password" 66ms

And I select the hostname of "proxy" from "proxies" if present 81ms

And I click on "Bootstrap" 66ms

And I wait at most 480 seconds until I see "Bootstrap process initiated." text 20s 967ms

And I follow the left menu "Systems > System List > All" 152ms

And I wait until I see the name of "rhlike_minion", refreshing the page 57s 903ms

And I wait until onboarding is completed for "rhlike_minion" 25s 349ms

Scenario:
Cleanup: re-subscribe the Red Hat-like minion to a base channel
31s 144ms 11

Given I am on the Systems overview page of this "rhlike_minion" 1s 75ms

When I follow "Software" in the content area 79ms

And I follow "Software Channels" in the content area 67ms

And I wait until I do not see "Loading..." text 70ms

And I check radio button "Fake-Base-Channel-RH-like" 10s 85ms

And I wait until I do not see "Loading..." text 413ms

And I click on "Next" 66ms

Then I should see a "Confirm Software Channel Change" text 57ms

When I click on "Confirm" 78ms

Then I should see a "Changing the channels has been scheduled." text 303ms

And I wait until event "Subscribe channels scheduled" is completed 18s 848ms

@skip_if_github_validation @scope_deblike @deblike_minion
Feature:Remote command on Debian-like Salt minion 15s 368ms 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
2s 177ms 1

Given I am authorized 2s 177ms

Scenario:
Run a remote command on the Debian-like minion
13s 190ms 10

When I follow the left menu "Salt > Remote Commands" 131ms

Then I should see a "Remote Commands" text in the content area 22ms

When I enter command "cat /etc/os-release" 93ms

And I enter target "deblike_minion" 97ms

And I click on preview 11s 635ms

And I click on run 50ms

Then I should see "deblike_minion" hostname 57ms

When I wait until I see "show response" text 991ms

And I expand the results for "deblike_minion" 55ms

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 16s 508ms 12

Scenario:
Log in as org admin user
1s 937ms 1

Given I am authorized 1s 937ms

Scenario:
Delete the Debian-like minion
4m 7s 969ms 7

When I am on the Systems overview page of this "deblike_minion" 1s 892ms

And I follow "Delete System" 563ms

Then I should see a "Confirm System Profile Deletion" text 61ms

When I click on "Delete Profile" 82ms

And I wait until I see "has been deleted" text 4m 3s 646ms

And I wait until Salt client is inactive on "deblike_minion" 1s 335ms

Then "deblike_minion" should not be registered 388ms

Scenario:
Bootstrap a SSH-managed Debian-like minion
2m 3s 537ms 11

The hostname of deblike_minion is uyuni-master-deblike-minion

When I follow the left menu "Systems > Bootstrapping" 86ms

Then I should see a "Bootstrap Minions" text 63ms

When I check "manageWithSSH" 94ms

And I enter the hostname of "deblike_minion" as "hostname" 128ms

And I enter "linux" as "password" 68ms

And I select the hostname of "proxy" from "proxies" if present 78ms

And I click on "Bootstrap" 67ms

And I wait at most 480 seconds until I see "Bootstrap process initiated." text 39s 495ms

And I follow the left menu "Systems > System List > All" 155ms

And I wait until I see the name of "deblike_minion", refreshing the page 30s 871ms

And I wait until onboarding is completed for "deblike_minion" 52s 429ms

@proxy
Scenario:
Check connection from SSH-managed Debian-like minion to proxy
1s 396ms 4

Given I am on the Systems overview page of this "deblike_minion" 1s 186ms

When I follow "Details" in the content area 75ms

And I follow "Connection" in the content area 70ms

Then I should see "proxy" short hostname 64ms

@proxy
Scenario:
Check registration on proxy of SSH-managed Debian-like minion
1s 294ms 4

Given I am on the Systems overview page of this "proxy" 1s 63ms

When I follow "Details" in the content area 65ms

And I follow "Proxy" in the content area 70ms

Then I should see "deblike_minion" hostname 95ms

Scenario:
Subscribe the SSH-managed Debian-like minion to a base channel
51s 80ms 11

Given I am on the Systems overview page of this "deblike_minion" 1s 213ms

When I follow "Software" in the content area 73ms

And I follow "Software Channels" in the content area 68ms

And I wait until I do not see "Loading..." text 63ms

And I check radio button "Fake-Base-Channel-Debian-like" 10s 77ms

And I wait until I do not see "Loading..." text 397ms

And I click on "Next" 70ms

Then I should see a "Confirm Software Channel Change" text 58ms

When I click on "Confirm" 84ms

Then I should see a "Changing the channels has been scheduled." text 274ms

And I wait until event "Subscribe channels scheduled" is completed 38s 699ms

Scenario:
Check events history for failures on SSH-managed Debian-like minion
1m 2s 308ms 2

Given I am on the Systems overview page of this "deblike_minion" 1s 293ms

Then I check for failed events on history event page 1m 1s 14ms

Scenario:
Run a remote command on the SSH-managed Debian-like minion
20s 315ms 10

When I follow the left menu "Salt > Remote Commands" 146ms

Then I should see a "Remote Commands" text in the content area 25ms

When I enter command "cat /etc/os-release" 104ms

And I enter target "deblike_minion" 96ms

And I click on preview 14s 999ms

And I click on run 49ms

Then I should see "deblike_minion" hostname 63ms

When I wait until I see "show response" text 4s 722ms

And I expand the results for "deblike_minion" 52ms

Then I should see a "ID=ubuntu" text 56ms

Scenario:
Check events history for failures on SSH-managed Debian-like minion
1m 12s 265ms 2

Given I am on the Systems overview page of this "deblike_minion" 1s 208ms

Then I check for failed events on history event page 1m 11s 56ms

Scenario:
Cleanup: delete the SSH-managed Debian-like minion
15s 161ms 6

When I am on the Systems overview page of this "deblike_minion" 1s 237ms

And I follow "Delete System" 465ms

Then I should see a "Confirm System Profile Deletion" text 65ms

When I click on "Delete Profile" 82ms

And I wait until I see "has been deleted" text 12s 836ms

Then "deblike_minion" should not be registered 474ms

Scenario:
Cleanup: bootstrap a Debian-like minion
1m 48s 209ms 12

The hostname of deblike_minion is uyuni-master-deblike-minion

When I follow the left menu "Systems > Bootstrapping" 84ms

Then I should see a "Bootstrap Minions" text 75ms

When I enter the hostname of "deblike_minion" as "hostname" 130ms

And I enter "22" as "port" 54ms

And I enter "root" as "user" 61ms

And I enter "linux" as "password" 64ms

And I select the hostname of "proxy" from "proxies" if present 83ms

And I click on "Bootstrap" 66ms

And I wait at most 480 seconds until I see "Bootstrap process initiated." text 24s 212ms

And I follow the left menu "Systems > System List > All" 153ms

And I wait until I see the name of "deblike_minion", refreshing the page 57s 874ms

And I wait until onboarding is completed for "deblike_minion" 25s 348ms

Scenario:
Cleanup: re-subscribe the Debian-like minion to a base channel
31s 29ms 11

Given I am on the Systems overview page of this "deblike_minion" 1s 18ms

When I follow "Software" in the content area 78ms

And I follow "Software Channels" in the content area 67ms

And I wait until I do not see "Loading..." text 61ms

And I check radio button "Fake-Base-Channel-Debian-like" 10s 90ms

And I wait until I do not see "Loading..." text 387ms

And I click on "Next" 67ms

Then I should see a "Confirm Software Channel Change" text 58ms

When I click on "Confirm" 78ms

Then I should see a "Changing the channels has been scheduled." text 271ms

And I wait until event "Subscribe channels scheduled" is completed 18s 848ms

@scope_salt_ssh @scope_onboarding @ssh_minion @skip_if_github_validation
Feature:Register a salt-ssh system via API 4m 14s 784ms 11 1

Scenario:
Log in as org admin user
2s 86ms 1

Given I am authorized 2s 86ms

Scenario:
Delete SSH minion system profile before API bootstrap test
16s 983ms 6

Given I am on the Systems overview page of this "ssh_minion" 1s 680ms

When I follow "Delete System" 450ms

Then I should see a "Confirm System Profile Deletion" text 65ms

When I click on "Delete Profile" 66ms

And I wait until I see "has been deleted" text 14s 264ms

Then "ssh_minion" should not be registered 456ms

@proxy
Scenario:
Block direct access from server to sshminion to test proxy as jumphost
830ms 1

Given I block connections from "server" on "ssh_minion" 830ms

Scenario:
Bootstrap a SLES SSH minion via API
42s 399ms 1

When I call system.bootstrap() on host "ssh_minion" and salt-ssh "enabled" 42s 399ms

Scenario:
Check new API bootstrapped salt-ssh system in System Overview page
1m 42s 620ms 3

When I follow the left menu "Systems > System List > All" 102ms

And I wait until I see the name of "ssh_minion", refreshing the page 57s 816ms

And I wait until onboarding is completed for "ssh_minion" 44s 701ms

Scenario:
Check contact method of this Salt SSH system
1s 168ms 2

Given I am on the Systems overview page of this "ssh_minion" 1s 84ms

Then I should see a "Push via SSH" text 83ms

@proxy
Scenario:
Check registration on proxy of SSH minion bootstrapped via API
1s 365ms 4

Given I am on the Systems overview page of this "proxy" 1s 117ms

When I follow "Details" in the content area 79ms

And I follow "Proxy" in the content area 71ms

Then I should see "ssh_minion" hostname 97ms

Scenario:
Check spacecmd system ID of SSH minion bootstrapped via API
3s 765ms 2

Given I am on the Systems overview page of this "ssh_minion" 1s 73ms

Then I run spacecmd listeventhistory for "ssh_minion" 2s 691ms

Scenario:
Check events history for failures on SSH minion after API bootstrap
42s 25ms 2

Given I am on the Systems overview page of this "ssh_minion" 1s 48ms

Then I check for failed events on history event page 40s 976ms

@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 837ms 13

Warning: Radio button 'openSUSE Tumbleweed (x86_64)' is already checked

Given I am on the Systems overview page of this "ssh_minion" 1s 65ms

When I follow "Software" in the content area 71ms

And I follow "Software Channels" in the content area 71ms

And I wait until I do not see "Loading..." text 67ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 166ms

And I wait until I do not see "Loading..." text 421ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 41ms

And I check "Fake-RPM-SUSE-Channel" 42ms

And I click on "Next" 67ms

Then I should see a "Confirm Software Channel Change" text 62ms

When I click on "Confirm" 79ms

Then I should see a "Changing the channels has been scheduled." text 308ms

And I wait until event "Subscribe channels scheduled" is completed 38s 372ms

@proxy
Scenario:
Cleanup and flush the firewall rules
702ms 1

When I flush firewall on "ssh_minion" 702ms

@skip_if_github_validation @scope_onboarding
Feature:Bootstrap a Salt minion via the GUI using SSH key 7m 9ms 7 1

Scenario:
Log in as org admin user
1s 877ms 1

Given I am authorized 1s 877ms

Scenario:
Delete SLES minion system profile before bootstrap with SSH key test
4m 7s 508ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 636ms

When I follow "Delete System" 470ms

Then I should see a "Confirm System Profile Deletion" text 61ms

When I click on "Delete Profile" 65ms

And I wait until I see "has been deleted" text 4m 4s 143ms

And I wait until Salt client is inactive on "sle_minion" 727ms

Then "sle_minion" should not be registered 404ms

Scenario:
Prepare the minion for SSH key authentication
1s 254ms 2

When I backup the SSH authorized_keys file of host "sle_minion" 403ms

And I add pre-generated SSH public key to authorized_keys of host "sle_minion" 850ms

Scenario:
Bootstrap a SLES minion using SSH key with wrong passphrase
39s 215ms 14 1 1

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 86ms

Then I should see a "Bootstrap Minions" text 66ms

When I enter the hostname of "sle_minion" as "hostname" 146ms

And I enter "22" as "port" 53ms

And I enter "root" as "user" 59ms

And I check radio button "SSH Private Key" 10s 76ms

And I attach the file "ssh_keypair/id_rsa_bootstrap-passphrase_linux" to "privKeyFile" 41ms

And I enter "you-shall-not-pass" as "privKeyPwd" 94ms

And I click on "Bootstrap" 63ms

And I wait until I see "An error has occurred during salt execution: unable to establish ssh connection." text 8s 315ms

Then I should see a "Details" button 18ms

When I click on "Details" 74ms

And I wait at most 10 seconds until I see modal containing "Error Details" text 12ms

Then I should see a "Standard Error" text 66ms

And I should see "Permission denied, no authentication information" or "Permission denied (publickey,password,keyboard-interactive)" in the stderr textarea 20s 39ms 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
42s 675ms 11

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 83ms

Then I should see a "Bootstrap Minions" text 65ms

When I enter the hostname of "sle_minion" as "hostname" 142ms

And I enter "22" as "port" 54ms

And I enter "root" as "user" 58ms

And I check radio button "SSH Private Key" 10s 75ms

And I attach the file "ssh_keypair/id_rsa_bootstrap-passphrase_linux" to "privKeyFile" 60ms

And I enter "linux" as "privKeyPwd" 64ms

And I select the hostname of "proxy" from "proxies" if present 75ms

And I click on "Bootstrap" 69ms

And I wait at most 480 seconds until I see "Bootstrap process initiated." text 31s 926ms

Scenario:
Check new minion bootstrapped with SSH key in System Overview page
1m 25s 289ms 6

It took 2 seconds to contact the minion

When I follow the left menu "Salt > Keys" 138ms

Then I should see a "accepted" text 341ms

When I am on the Systems page 250ms

And I wait until I see the name of "sle_minion", refreshing the page 30s 868ms

And I wait until onboarding is completed for "sle_minion" 51s 805ms

Then the Salt master can reach "sle_minion" 1s 885ms

Scenario:
Also check contact method of this minion
1s 90ms 2

Given I am on the Systems overview page of this "sle_minion" 1s 4ms

Then I should see a "Default" text 85ms

Scenario:
Cleanup: restore authorized keys
1s 98ms 1

When I restore the SSH authorized_keys file of host "sle_minion" 1s 98ms

@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 11m 22s 381ms 9 1

Scenario:
Log in as org admin user
1s 655ms 1

Given I am authorized 1s 655ms

Scenario:
Pre-requisite: remove package before ssh tunnel test
1s 737ms 1

When I remove package "milkyway-dummy" from this "ssh_minion" without error control 1s 737ms

Scenario:
Delete the Salt minion for SSH tunnel bootstrap
16s 106ms 6

Given I am on the Systems overview page of this "ssh_minion" 1s 82ms

When I follow "Delete System" 486ms

Then I should see a "Confirm System Profile Deletion" text 60ms

When I click on "Delete Profile" 65ms

And I wait until I see "has been deleted" text 13s 855ms

Then "ssh_minion" should not be registered 555ms

Scenario:
Register this minion for push via SSH tunnel
2m 23s 132ms 12

The hostname of ssh_minion is uyuni-master-suse-sshminion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 84ms

Then I should see a "Bootstrap Minions" text 65ms

And I enter the hostname of "ssh_minion" as "hostname" 158ms

And I enter "22" as "port" 69ms

And I enter "root" as "user" 66ms

And I enter "linux" as "password" 65ms

And I select "1-SUSE-SSH-TUNNEL-KEY-x86_64" from "activationKeys" 77ms

And I select the hostname of "proxy" from "proxies" if present 66ms

And I check "manageWithSSH" 87ms

And I click on "Bootstrap" 64ms

And I wait at most 480 seconds until I see "Bootstrap process initiated." text 40s 346ms

And I wait until onboarding is completed for "ssh_minion" 1m 41s 979ms

Scenario:
The contact method is SSH tunnel on this minion
1s 198ms 2

Given I am on the Systems overview page of this "ssh_minion" 1s 115ms

Then I should see a "Push via SSH tunnel" text 83ms

Scenario:
Install a package from this SSH tunnel minion
58s 697ms 11

Given I am on the Systems overview page of this "ssh_minion" 1s 80ms

When I follow "Software" in the content area 80ms

And I follow "Install" 512ms

And I enter "milkyway-dummy" as the filtered package name 65ms

And I click on the filter button 626ms

And I wait until I see "milkyway-dummy" text 70ms

And I check row with "milkyway-dummy" and arch of "ssh_minion" 65ms

And I click on "Install Packages" 590ms

And I click on "Confirm" 731ms

Then I should see a "1 package install has been scheduled for" text 61ms

Then I wait until event "Package Install/Upgrade scheduled" is completed 54s 812ms

@flaky
Scenario:
Remove a package from this SSH tunnel minion
4m 28s 591ms 6 5 1

Given I am on the Systems overview page of this "ssh_minion" 1s

And I follow "Software" in the content area 85ms

And I follow "List / Remove" 724ms

And I enter "milkyway-dummy" as the filtered package name 64ms

And I click on the filter button 947ms

And I wait until I see "milkyway-dummy" text 4m 10s 41ms Show Error + 
                                            
 Text 'milkyway-dummy' not found (ScriptError)
./features/step_definitions/navigation_steps.rb:40:in `/^I wait until I see "([^"]*)" text$/'
features/secondary/minssh_tunnel.feature:66:in `I wait until I see "milkyway-dummy" text'

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 727ms Show Info + 
21:58:10:000 - 22:02:23: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
28s 602ms 11

The hostname of ssh_minion is uyuni-master-suse-sshminion.sumaci.aws

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 "echo 'My remote command output'" 105ms

And I enter the hostname of "ssh_minion" as "target" 112ms

And I click on preview 18s 797ms

Then I should see a "Target systems (1)" text 54ms

When I wait until I do not see "pending" text 48ms

And I click on run 47ms

And I wait until I see "show response" text 9s 202ms

And I expand the results for "ssh_minion" 50ms

Then I should see "My remote command output" in the command output for "ssh_minion" 31ms

Scenario:
Cleanup: delete the SSH tunnel minion
22s 330ms 6

Given I am on the Systems overview page of this "ssh_minion" 1s 201ms

When I follow "Delete System" 529ms

Then I should see a "Confirm System Profile Deletion" text 61ms

When I click on "Delete Profile" 65ms

And I wait until I see "has been deleted" text 20s 12ms

Then "ssh_minion" should not be registered 459ms

Scenario:
Cleanup: register a SSH minion after SSH tunnel tests
2m 20s 329ms 4

When I call system.bootstrap() on host "ssh_minion" and salt-ssh "enabled" 40s 878ms

And I follow the left menu "Systems > System List > All" 97ms

And I wait until I see the name of "ssh_minion", refreshing the page 1m 11s 361ms

And I wait until onboarding is completed for "ssh_minion" 27s 990ms

@skip_if_github_validation @scope_onboarding
Feature:Bootstrap a Salt minion via the GUI with an activation key 7m 15s 24ms 14 2

Scenario:
Log in as org admin user
1s 971ms 1

Given I am authorized 1s 971ms

Scenario:
Delete SLES minion system profile
4m 7s 186ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 642ms

When I follow "Delete System" 469ms

Then I should see a "Confirm System Profile Deletion" text 64ms

When I click on "Delete Profile" 72ms

And I wait until I see "has been deleted" text 4m 3s 743ms

And I wait until Salt client is inactive on "sle_minion" 745ms

Then "sle_minion" should not be registered 448ms

Scenario:
Create a configuration channel for the activation key
1s 333ms 7

When I follow the left menu "Configuration > Channels" 136ms

And I follow "Create Config Channel" 253ms

And I enter "Key Channel" as "cofName" 70ms

And I enter "keychannel" as "cofLabel" 58ms

And I enter "This is a configuration channel for the activation key" as "cofDescription" 96ms

And I click on "Create Config Channel" 69ms

Then I should see a "Key Channel" text 648ms

Scenario:
Add a configuration file to the key configuration channel
1s 583ms 6

When I follow the left menu "Configuration > Channels" 67ms

And I follow "Key Channel" 420ms

And I follow "Create Configuration File or Directory" 382ms

And I enter "/etc/euler.conf" as "cffPath" 66ms

And I enter "e^i.pi=-1" in the editor 4ms

And I click on "Create Configuration File" 643ms

@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 675ms 19

When I follow the left menu "Systems > Activation Keys" 125ms

And I follow "Create Key" 345ms

And I wait for child channels to appear 1s 342ms

And I enter "Minion testing" as "description" 92ms

And I enter "MINION-TEST" as "key" 94ms

And I enter "20" as "usageLimit" 77ms

And I select "openSUSE Tumbleweed (x86_64)" from "selectedBaseChannel" 100ms

And I wait for child channels to appear 376ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 85ms

And I check "Fake-RPM-SUSE-Channel" 79ms

And I click on "Create Activation Key" 747ms

And I follow "Configuration" in the content area 74ms

And I follow first "Subscribe to Channels" in the content area 67ms

And I check "Key Channel" in the list 58ms

And I click on "Continue" 502ms

And I follow "Packages" 315ms

And I enter "orion-dummy perseus-dummy" as "packages" 69ms

And I click on "Update Activation Key" 63ms

Then I should see a "Activation key Minion testing has been modified" text 57ms

Scenario:
Bootstrap a SLES minion with an activation key
1m 47s 628ms 13

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 74ms

Then I should see a "Bootstrap Minions" text 64ms

When I enter the hostname of "sle_minion" as "hostname" 139ms

And I enter "22" as "port" 55ms

And I enter "root" as "user" 59ms

And I enter "linux" as "password" 62ms

And I select "1-MINION-TEST" from "activationKeys" 63ms

And I select the hostname of "proxy" from "proxies" if present 66ms

And I click on "Bootstrap" 62ms

And I wait until I see "Bootstrap process initiated." text 23s 955ms

And I follow the left menu "Systems > System List > All" 149ms

And I wait until I see the name of "sle_minion", refreshing the page 30s 761ms

And I wait until onboarding is completed for "sle_minion" 52s 113ms

Scenario:
Verify that minion bootstrapped with Salt key and packages
4s 331ms 5

It took 2 seconds to contact the minion

When I follow the left menu "Salt > Keys" 126ms

Then I should see a "accepted" text 342ms

And the Salt master can reach "sle_minion" 1s 902ms

When I wait for "orion-dummy" to be installed on "sle_minion" 1s 139ms

And I wait for "perseus-dummy" to be installed on "sle_minion" 820ms

Scenario:
Check system ID of bootstrapped minion
3s 410ms 2

Given I am on the Systems overview page of this "sle_minion" 1s 4ms

Then I run spacecmd listeventhistory for "sle_minion" 2s 405ms

@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
789ms 2

Given I am on the Systems page 245ms

Then I should see a "openSUSE Tumbleweed (x86_64)" text 544ms

Scenario:
Verify that minion bootstrapped with configuration channel
1s 332ms 6

Given I am on the Systems overview page of this "sle_minion" 980ms

When I follow "Configuration" in the content area 77ms

Then I should see a "1 configuration channel" text 66ms

When I follow "View Files" in the content area 67ms

Then I should see a "/etc/euler.conf" text 70ms

And I should see a "Key Channel" text 69ms

Scenario:
Cleanup: remove the package states
5s 980ms 12

Given I am on the Systems overview page of this "sle_minion" 1s 16ms

When I follow "States" in the content area 69ms

And I follow "Packages" 463ms

Then I should see a "Package States" text 62ms

When I change the state of "orion-dummy" to "Unmanaged" and "" 126ms

And I change the state of "perseus-dummy" to "Unmanaged" and "" 43ms

Then I should see a "2 Changes" text 66ms

When I click save 51ms

Then I wait until I see "Package states have been saved." text 271ms

And I click apply 50ms

And I remove package "orion-dummy" from this "sle_minion" 1s 696ms

And I remove package "perseus-dummy" from this "sle_minion" 2s 62ms

Scenario:
Cleanup: remove the key configuration channel
1s 431ms 4

When I follow the left menu "Configuration > Channels" 120ms

And I follow "Key Channel" 492ms

And I follow "Delete Channel" 307ms

And I click on "Delete Config Channel" 511ms

Scenario:
Cleanup: delete the activation key
1s 208ms 5

When I follow the left menu "Systems > Activation Keys" 126ms

And I follow "Minion testing" in the content area 71ms

And I follow "Delete Key" 395ms

And I click on "Delete Activation Key" 536ms

Then I should see a "Activation key Minion testing has been deleted." text 78ms

Scenario:
Check events history for failures on SLES minion with activation key
52s 160ms 2

Given I am on the Systems overview page of this "sle_minion" 1s 47ms

Then I check for failed events on history event page 51s 112ms

@skip_if_github_validation @scope_onboarding
Feature:Register a Salt minion via API 7m 21s 14ms 11 1

Scenario:
Log in as org admin user
2s 118ms 1

Given I am authorized 2s 118ms

Scenario:
Delete SLES minion system profile before API bootstrap test
4m 7s 11ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 524ms

When I follow "Delete System" 465ms

Then I should see a "Confirm System Profile Deletion" text 65ms

When I click on "Delete Profile" 83ms

And I wait until I see "has been deleted" text 4m 3s 735ms

And I wait until Salt client is inactive on "sle_minion" 747ms

Then "sle_minion" should not be registered 389ms

Scenario:
Bootstrap a SLES minion via API
22s 905ms 1

When I call system.bootstrap() on host "sle_minion" and salt-ssh "disabled" 22s 905ms

Scenario:
Check new minion bootstrapped via API in System Overview page
1m 22s 643ms 6

It took 2 seconds to contact the minion

When I follow the left menu "Salt > Keys" 141ms

Then I should see a "accepted" text 358ms

When I follow the left menu "Systems > System List > All" 194ms

And I wait until I see the name of "sle_minion", refreshing the page 1m 11s 449ms

And I wait until onboarding is completed for "sle_minion" 8s 622ms

Then the Salt master can reach "sle_minion" 1s 876ms

Scenario:
Check contact method of this minion
1s 176ms 2

Given I am on the Systems overview page of this "sle_minion" 1s 85ms

Then I should see a "Default" text 90ms

@proxy
Scenario:
Check registration on proxy of minion bootstrapped via API
1s 313ms 4

Given I am on the Systems overview page of this "proxy" 1s 73ms

When I follow "Details" in the content area 73ms

And I follow "Proxy" in the content area 70ms

Then I should see "sle_minion" hostname 95ms

Scenario:
Check spacecmd system ID of minion bootstrapped via API
3s 464ms 2

Given I am on the Systems overview page of this "sle_minion" 1s 58ms

Then I run spacecmd listeventhistory for "sle_minion" 2s 406ms

@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
24s 332ms 13

Warning: Radio button 'openSUSE Tumbleweed (x86_64)' is already checked

Given I am on the Systems overview page of this "sle_minion" 1s 39ms

When I follow "Software" in the content area 71ms

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 "openSUSE Tumbleweed (x86_64)" 243ms

And I wait until I do not see "Loading..." text 342ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 41ms

And I check "Fake-RPM-SUSE-Channel" 38ms

And I click on "Next" 64ms

Then I should see a "Confirm Software Channel Change" text 64ms

When I click on "Confirm" 77ms

Then I should see a "Changing the channels has been scheduled." text 416ms

And I wait until event "Subscribe channels scheduled" is completed 21s 796ms

Scenario:
Check events history for failures on SLES minion after API bootstrap
52s 54ms 2

Given I am on the Systems overview page of this "sle_minion" 1s 43ms

Then I check for failed events on history event page 51s 11ms

Scenario:
Bootstrap via API a non-existing system
3s 199ms 1

When I call system.bootstrap() on unknown host, I should get an API fault 3s 199ms

Scenario:
Bootstrap a salt-ssh system with activation key and default contact method
795ms 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 795ms

@skip_if_github_validation @sle_minion @scope_onboarding
Feature:Bootstrapping with reactivation key 7m 52s 798ms 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 83ms 1

Given I am authorized 2s 83ms

Scenario:
Generate a re-activation key
3s 202ms 4

Given I am on the Systems overview page of this "sle_minion" 1s 826ms

When I follow "Reactivation" 557ms

And I click on "Generate New Key" 754ms

Then I should see a "Key:" text 63ms

Scenario:
Bootstrap should fail when minion already exists
920ms 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 71ms

When I enter the hostname of "sle_minion" as "hostname" 140ms

And I enter "22" as "port" 54ms

And I enter "root" as "user" 57ms

And I enter "linux" as "password" 57ms

And I click on "Bootstrap" 66ms

And I wait until I see "A salt key for this host" text 267ms

Then I should not see a "GenericSaltError" text 62ms

And I should see a "seems to already exist, please check!" text 64ms

Scenario:
Bootstrap should fail when system already exists in the server
2s 968ms 11

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

Given I delete "sle_minion" key in the Salt master 2s 85ms

When I follow the left menu "Systems > Bootstrapping" 64ms

Then I should see a "Bootstrap Minions" text 65ms

When I enter the hostname of "sle_minion" as "hostname" 131ms

And I enter "22" as "port" 47ms

And I enter "root" as "user" 54ms

And I enter "linux" as "password" 57ms

And I click on "Bootstrap" 60ms

And I wait until I see "seems to already exist, please check!" text 277ms

Then I should not see a "GenericSaltError" text 61ms

And I should see a "with minion id" text 62ms

Scenario:
Bootstrap a SLES minion with reactivation key
1m 48s 757ms 13

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws
Reactivation Key: re-1-ae8bc96d492c4015bb05474e8892f183

When I follow the left menu "Systems > Bootstrapping" 63ms

Then I should see a "Bootstrap Minions" text 68ms

When I enter the hostname of "sle_minion" as "hostname" 122ms

And I enter "22" as "port" 48ms

And I enter "root" as "user" 54ms

And I enter "linux" as "password" 57ms

And I enter the reactivation key of "sle_minion" 1s 79ms

And I select "1-SUSE-KEY-x86_64" from "activationKeys" 76ms

And I click on "Bootstrap" 59ms

And I wait until I see "Bootstrap process initiated." text 27s 349ms

And I follow the left menu "Systems > System List > All" 144ms

And I wait until I see the name of "sle_minion", refreshing the page 624ms

And I wait until onboarding is completed for "sle_minion" 1m 19s 7ms

Scenario:
Check the events history for the reactivation
3s 382ms 5

Given I am on the Systems overview page of this "sle_minion" 995ms

When I follow "Events" in the content area 78ms

And I follow "History" in the content area 63ms

And I wait until I see "Server reactivated as Salt minion" text, refreshing the page 84ms

And I wait until event "Apply states [certs, channels, packages, services.salt-minion] scheduled" is completed 2s 160ms

Scenario:
Cleanup: delete SLES minion after reactivation tests
4m 5s 577ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 18ms

When I follow "Delete System" 462ms

Then I should see a "Confirm System Profile Deletion" text 59ms

When I click on "Delete Profile" 89ms

And I wait until I see "has been deleted" text 4m 2s 835ms

And I wait until Salt client is inactive on "sle_minion" 751ms

Then "sle_minion" should not be registered 360ms

Scenario:
Cleanup: bootstrap a SLES minion after reactivation tests
1m 45s 906ms 13

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 84ms

Then I should see a "Bootstrap Minions" text 76ms

When I enter the hostname of "sle_minion" as "hostname" 150ms

And I enter "22" as "port" 60ms

And I enter "root" as "user" 63ms

And I enter "linux" as "password" 64ms

And I select "1-SUSE-KEY-x86_64" from "activationKeys" 74ms

And I select the hostname of "proxy" from "proxies" if present 67ms

And I click on "Bootstrap" 67ms

And I wait until I see "Bootstrap process initiated." text 22s 362ms

And I follow the left menu "Systems > System List > All" 149ms

And I wait until I see the name of "sle_minion", refreshing the page 44s 384ms

And I wait until onboarding is completed for "sle_minion" 38s 301ms

@skip_if_github_validation @sle_minion @scope_salt
Feature:Management of minion keys 8m 21s 901ms 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 270ms 1

Given I am authorized 2s 270ms

Scenario:
Delete SLES minion system profile before exploring the onboarding page
4m 7s 17ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 718ms

When I follow "Delete System" 478ms

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 3s 585ms

And I wait until Salt client is inactive on "sle_minion" 740ms

Then "sle_minion" should not be registered 367ms

Scenario:
Completeness of the onboarding page
159ms 2

When I follow the left menu "Salt > Keys" 134ms

Then I should see a "Keys" text in the content area 24ms

Scenario:
Minion is visible in the Pending section
15s 93ms 8

When I configure salt minion on "sle_minion" 399ms

And I restart salt-minion on "sle_minion" 631ms

And I wait at most 10 seconds until Salt master sees "sle_minion" as "unaccepted" 1s 798ms

And I follow the left menu "Salt > Keys" 61ms

And I refresh page until I see "sle_minion" hostname as text 10s 166ms

Then I should see a "Fingerprint" text 71ms

And I see "sle_minion" fingerprint 1s 899ms

And I should see a "pending" text 64ms

Scenario:
Reject and delete the pending key
18s 908ms 7

And I follow the left menu "Salt > Keys" 77ms

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 906ms

Then I should see a "rejected" text 64ms

When I stop salt-minion on "sle_minion" 3s 10ms

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 535ms

Scenario:
Accepted minion shows up as a registered system
1m 38s 27ms 9

When I start salt-minion on "sle_minion" 995ms

And I wait at most 10 seconds until Salt master sees "sle_minion" as "unaccepted" 1s 794ms

Then "sle_minion" should not be registered 408ms

When I follow the left menu "Salt > Keys" 62ms

Then I should see a "pending" text 403ms

When I accept "sle_minion" key 50ms

And I wait at most 10 seconds until Salt master sees "sle_minion" as "accepted" 1s 568ms

And I wait until onboarding is completed for "sle_minion" 1m 32s 346ms

Then "sle_minion" should be registered 397ms

Scenario:
The minion communicates with the Salt master
3s 404ms 3

It took 1 seconds to contact the minion

Then the Salt master can reach "sle_minion" 1s 863ms

When I get OS information of "sle_minion" from the Master 1s 540ms

Then it should contain the OS of "sle_minion" < 1ms

Scenario:
Delete profile of unreacheable minion
15s 175ms 9

Given I am on the Systems overview page of this "sle_minion" 1s 72ms

When I stop salt-minion on "sle_minion" 3s 157ms

And I follow "Delete System" 448ms

Then I should see a "Confirm System Profile Deletion" text 61ms

When I click on "Delete Profile" 63ms

Then I wait until I see "Cleanup timed out. Please check if the machine is reachable." text 7s 705ms

When I click on "Delete Profile Without Cleanup" in "An error occurred during cleanup" modal 2s 35ms

And I wait until I see "has been deleted" text 68ms

Then "sle_minion" should not be registered 562ms

Scenario:
Cleanup: bootstrap again the minion
1m 41s 844ms 11

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 75ms

Then I should see a "Bootstrap Minions" text 72ms

When I enter the hostname of "sle_minion" as "hostname" 139ms

And I enter "22" as "port" 52ms

And I enter "root" as "user" 59ms

And I enter "linux" as "password" 62ms

And I select "1-SUSE-KEY-x86_64" from "activationKeys" 72ms

And I select the hostname of "proxy" from "proxies" if present 57ms

And I click on "Bootstrap" 60ms

And I wait until I see "Bootstrap process initiated." text 22s 249ms

And I wait until onboarding is completed for "sle_minion" 1m 18s 942ms

@skip_if_github_validation @scope_salt
Feature:Install a package and a patch on the SUSE client via Salt through the UI 1m 51s 20ms 11

Scenario:
Pre-requisite: enable test_repo_rpm_pool repository on SLE minion
762ms 1

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 762ms

Scenario:
Pre-requisite: install virgo-dummy-1.0 package on SLE minion
1s 849ms 2

When I refresh the metadata for "sle_minion" 1s 10ms

And I install old package "virgo-dummy-1.0" on this "sle_minion" without error control 838ms

Scenario:
Pre-requisite: remove andromeda-dummy package from SLE minion
12s 552ms 4

When I remove package "andromeda-dummy" from this "sle_minion" without error control 1s 443ms

And I refresh the metadata for "sle_minion" 820ms

And I refresh packages list via spacecmd on "sle_minion" 2s 990ms

And I wait until refresh package list on "sle_minion" is finished 7s 297ms

Scenario:
Pre-requisite: refresh package list and check old packages installed on SLE minion
15s 668ms 4

When I refresh packages list via spacecmd on "sle_minion" 2s 378ms

And I wait until refresh package list on "sle_minion" is finished 7s 272ms

Then spacecmd should show packages "virgo-dummy-1.0" installed on "sle_minion" 2s 480ms

And I wait until package "andromeda-dummy-2.0-1.1" is removed from "sle_minion" via spacecmd 3s 536ms

Scenario:
Log in as org admin user
2s 184ms 1

Given I am authorized for the "Admin" section 2s 184ms

Scenario:
Pre-requisite: ensure the errata cache is computed before patching Salt minion
18s 505ms 11

Given I am on the Systems overview page of this "sle_minion" 1s 592ms

When I follow "Software" in the content area 74ms

And I follow "List / Remove" in the content area 70ms

And I enter "virgo-dummy" as the filtered package name 157ms

And I click on the filter button until page does contain "virgo-dummy" text 10s 988ms

When I follow the left menu "Admin > Task Schedules" 124ms

And I follow "errata-cache-default" 376ms

And I follow "errata-cache-bunch" 1s 405ms

And I click on "Single Run Schedule" 1s 241ms

Then I should see a "bunch was scheduled" text 270ms

When I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 2s 204ms

Scenario:
Install a patch on the SLE minion
22s 523ms 12

Given I am on the Systems overview page of this "sle_minion" 1s 15ms

When I follow "Software" in the content area 72ms

And I follow "Patches" in the content area 68ms

And I enter "virgo" as the filtered synopsis 47ms

And I click on the filter button 10s 109ms

And I check "virgo-dummy-3456" in the list 62ms

And I check "allowVendorChange" 79ms

And I click on "Apply Patches" 590ms

And I click on "Confirm" 659ms

Then I should see a "1 patch update has been scheduled for" text 71ms

When I wait for "virgo-dummy-2.0-1.1" to be installed on "sle_minion" 8s 704ms

Then vendor change should be enabled for package actions on "sle_minion" 1s 41ms

Scenario:
Install a package on the SLE minion
13s 580ms 12

Given I am on the Systems overview page of this "sle_minion" 969ms

When I follow "Software" in the content area 61ms

And I follow "Packages" 454ms

And I follow "Install" 547ms

And I enter "andromeda" as the filtered package name 108ms

And I click on the filter button 708ms

And I check "andromeda-dummy-2.0-1.1" in the list 56ms

And I click on "Install Packages" 606ms

And I click on "Confirm" 663ms

Then I should see a "1 package install has been scheduled" text 62ms

When I wait for "andromeda-dummy-2.0-1.1" to be installed on "sle_minion" 8s 531ms

Then vendor change should be enabled for package actions on "sle_minion" 811ms

Scenario:
Cleanup: disable test_repo_rpm_pool on SLE minion
433ms 1

When I disable repository "test_repo_rpm_pool" on this "sle_minion" 433ms

Scenario:
Cleanup: remove virgo-dummy package from SLE minion
13s 196ms 4

When I remove package "virgo-dummy" from this "sle_minion" without error control 1s 420ms

And I refresh the metadata for "sle_minion" 820ms

And I refresh packages list via spacecmd on "sle_minion" 3s 681ms

And I wait until refresh package list on "sle_minion" is finished 7s 272ms

Scenario:
Cleanup: remove andromeda-dummy package from SLE minion
9s 763ms 4

When I remove package "andromeda-dummy" from this "sle_minion" without error control 1s 735ms

And I refresh the metadata for "sle_minion" 811ms

And I refresh packages list via spacecmd on "sle_minion" 2s 368ms

And I wait until refresh package list on "sle_minion" is finished 4s 848ms

@skip_if_github_validation @sle_minion @scope_content_staging
Feature:Install a package on the SLES minion with staging enabled 6m 28s 51ms 8

Scenario:
Pre-requisite: install virgo-dummy-1.0 package, make sure orion-dummy is not present
3s 258ms 3

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 786ms

And I remove package "orion-dummy" from this "sle_minion" without error control 795ms

And I install package "virgo-dummy-1.0" on this "sle_minion" 1s 676ms

Scenario:
Pre-requisite: refresh package list
14s 766ms 3

When I refresh packages list via spacecmd on "sle_minion" 2s 725ms

And I wait until refresh package list on "sle_minion" is finished 9s 635ms

Then spacecmd should show packages "virgo-dummy-1.0" installed on "sle_minion" 2s 405ms

Scenario:
Log in as admin user
449ms 1

Given I am authorized for the "Admin" section 449ms

Scenario:
Pre-requisite: ensure the errata cache is computed before staging tests
6s 508ms 6

When I follow the left menu "Admin > Task Schedules" 129ms

And I follow "errata-cache-default" 1s 224ms

And I follow "errata-cache-bunch" 1s 299ms

Then I click on "Single Run Schedule" 1s 265ms

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 319ms

Scenario:
Enable content staging
815ms 6

When I follow the left menu "Admin > Organizations" 71ms

And I follow first "SUSE Test" 226ms

And I follow first "Configuration" 292ms

And I check "staging_content_enabled" 98ms

And I click on "Update Organization" 58ms

Then I should see a "was successfully updated." text 68ms

Scenario:
Install package in the future and check for staging
2m 57s 917ms 13

Given I am on the Systems overview page of this "sle_minion" 1s 93ms

When I follow "Software" in the content area 75ms

And I follow "Packages" in the content area 86ms

And I follow "Install" in the content area 71ms

And I enter "orion-dummy-1.1-1.1" as the filtered package name 218ms

And I click on the filter button 720ms

And I check row with "orion-dummy-1.1-1.1" and arch of "sle_minion" 62ms

And I click on "Install Packages" 685ms

And I pick 3 minutes from now as schedule time 91ms

And I click on "Confirm" 1s 100ms

Then I should see a "1 package install has been scheduled for" text 64ms

And I wait until the package "orion-dummy-1.1-1.1" has been cached on this "sle_minion" 1m 40s 31ms

And I wait for "orion-dummy-1.1-1.1" to be installed on "sle_minion" 1m 13s 615ms

Scenario:
Install patch in the future and check for staging
3m 411ms 11

When I follow "Software" in the content area 63ms

And I follow "Patches" in the content area 65ms

And I enter "virgo" as the filtered synopsis 38ms

And I click on the filter button 10s 118ms

And I check "virgo-dummy-3456" in the list 68ms

And I click on "Apply Patches" 611ms

And I pick 3 minutes from now as schedule time 90ms

And I click on "Confirm" 1s 12ms

Then I should see a "1 patch update has been scheduled for" text 73ms

And I wait until the package "virgo-dummy-2.0-1.1.noarch" has been cached on this "sle_minion" 34s 754ms

And I wait for "virgo-dummy-2.0-1.1" to be installed on "sle_minion" 2m 13s 515ms

Scenario:
Cleanup: remove virgo-dummy package from SLES minion
3s 923ms 11

When I follow "Software" in the content area 86ms

And I follow "List / Remove" 710ms

And I enter "orion-dummy" as the filtered package name 168ms

And I click on the filter button 856ms

And I check row with "orion-dummy" and arch of "sle_minion" 64ms

And I enter "virgo-dummy" as the filtered package name 42ms

And I click on the filter button 123ms

And I check "virgo-dummy" in the list 57ms

And I click on "Remove Packages" 594ms

And I click on "Confirm" 673ms

And I disable repository "test_repo_rpm_pool" on this "sle_minion" 544ms

@skip_if_github_validation @scope_salt
Feature:Salt package states 2m 9s 122ms 15

Scenario:
Pre-requisite: install old packages on SLES minion
15s 918ms 6

Salt command: salt uyuni-master-suse-minion.sumaci.aws state.highstate

When I apply highstate on "sle_minion" 8s 559ms

And I enable repository "test_repo_rpm_pool" on this "sle_minion" 747ms

And I refresh the metadata for "sle_minion" 819ms

And I install old package "milkyway-dummy-1.0" on this "sle_minion" without error control 1s 892ms

And I install old package "virgo-dummy-1.0" on this "sle_minion" without error control 2s 249ms

And I install old package "andromeda-dummy-1.0" on this "sle_minion" without error control 1s 650ms

Scenario:
Pre-requisite: refresh package list and check installed packages on SLE minion
14s 374ms 3

When I refresh packages list via spacecmd on "sle_minion" 2s 386ms

And I wait until refresh package list on "sle_minion" is finished 9s 574ms

Then spacecmd should show packages "milkyway-dummy-1.0 virgo-dummy-1.0 andromeda-dummy-1.0" installed on "sle_minion" 2s 413ms

Scenario:
Log in as admin user
915ms 1

Given I am authorized for the "Admin" section 915ms

Scenario:
Pre-requisite: ensure the errata cache is computed before software states tests
8s 629ms 11

Given I am on the Systems overview page of this "sle_minion" 1s 534ms

When I follow "Software" in the content area 69ms

And I follow "List / Remove" in the content area 67ms

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 277ms

When I follow the left menu "Admin > Task Schedules" 145ms

And I follow "errata-cache-default" 1s 180ms

And I follow "errata-cache-bunch" 1s 383ms

Then I click on "Single Run Schedule" 1s 231ms

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 278ms

Scenario:
Accepted minion has a base channel
1s 253ms 4

Given I am on the Systems overview page of this "sle_minion" 1s 20ms

When I follow "Software" in the content area 74ms

And I follow "Software Channels" in the content area 82ms

Then the system should have a base channel set 76ms

Scenario:
Remove a package through the UI
9s 501ms 13

When I follow "States" in the content area 65ms

And I follow "Packages" 471ms

And I follow "Search" 66ms

And I should see a "Package States" text 70ms

And I list packages with "dummy" 1s 158ms

And I wait until I see "milkyway-dummy" text 435ms

Then "milkyway-dummy" should be installed on "sle_minion" 725ms

And I change the state of "milkyway-dummy" to "Removed" and "" 58ms

Then I should see a "1 Change" text 85ms

And I click save 50ms

Then I wait until I see "Package states have been saved." text 327ms

And I click apply 46ms

And I wait for "milkyway-dummy" to be uninstalled on "sle_minion" 5s 941ms

Scenario:
Install a package through the UI
12s 247ms 13

When I follow "States" in the content area 60ms

And I follow "Packages" 460ms

And I follow "Search" 55ms

And I should see a "Package States" text 68ms

And I list packages with "dummy" 1s 143ms

And I wait until I see "milkyway-dummy" text 456ms

Then "milkyway-dummy" should not be installed on "sle_minion" 585ms

And I change the state of "milkyway-dummy" to "Installed" and "" 44ms

Then I should see a "1 Change" text 89ms

And I click save 43ms

Then I wait until I see "Package states have been saved." text 333ms

And I click apply 40ms

And I wait for "milkyway-dummy" to be installed on "sle_minion" 8s 865ms

Scenario:
Install an already installed package through the UI
4s 592ms 13

When I follow "States" in the content area 66ms

And I follow "Packages" 408ms

And I follow "Search" 55ms

And I should see a "Package States" text 72ms

And I list packages with "dummy" 1s 143ms

And I wait until I see "virgo-dummy" text 472ms

Then "virgo-dummy-1.0" should be installed on "sle_minion" 887ms

And I change the state of "virgo-dummy" to "Installed" and "Any" 107ms

Then I should see a "1 Change" text 92ms

And I click save 63ms

Then I wait until I see "Package states have been saved." text 217ms

And I click apply 51ms

And I wait for "virgo-dummy-1.0" to be installed on "sle_minion" 953ms

Scenario:
Upgrade a package through the UI
17s 365ms 13

When I follow "States" in the content area 75ms

And I follow "Packages" 563ms

And I follow "Search" 65ms

And I should see a "Package States" text 67ms

And I list packages with "dummy" 1s 145ms

And I wait until I see "andromeda-dummy" text 472ms

Then "andromeda-dummy-1.0" should be installed on "sle_minion" 496ms

And I change the state of "andromeda-dummy" to "Installed" and "Latest" 84ms

Then I should see a "1 Change" text 102ms

And I click save 50ms

Then I wait until I see "Package states have been saved." text 359ms

And I click apply 47ms

And I wait for "andromeda-dummy-2.0-1.1" to be installed on "sle_minion" 13s 834ms

Scenario:
Verify the package states
970ms 6

When I follow "States" in the content area 75ms

And I follow "Packages" 483ms

And I should see a "Package States" text 67ms

And I should see a "milkyway-dummy" text 186ms

And I should see a "andromeda-dummy" text 73ms

And I should see a "virgo-dummy" text 83ms

Scenario:
Use Salt presence mechanism on an active minion
16s 499ms 5

When I follow "States" in the content area 63ms

And I follow "Highstate" in the content area 64ms

And I click on "Show full highstate output" 291ms

And I wait for "6" seconds 6s

And I should see a "pkg_removed" or "running as PID" text in element "highstate" 10s 79ms

Scenario:
Use Salt presence mechanism on an unreachable minion
16s 650ms 6

When I follow "States" in the content area 95ms

And I run "pkill salt-minion" on "sle_minion" without error control 721ms

And I run "pkill python.original" on "sle_minion" without error control 404ms

And I follow "Highstate" in the content area 68ms

And I click on "Show full highstate output" 222ms

And I wait until I see "No reply from minion" text 15s 138ms

Scenario:
Cleanup: restart the salt service on SLES minion
939ms 1

When I restart salt-minion on "sle_minion" 939ms

Scenario:
Cleanup: set the package states as unmanaged
3s 646ms 11

Given I am on the Systems overview page of this "sle_minion" 981ms

When I follow "States" in the content area 81ms

And I follow "Packages" 440ms

And I follow "Search" 68ms

And I should see a "Package States" text 71ms

And I list packages with "dummy" 1s 155ms

And I wait until I see "andromeda-dummy" text 463ms

And I change the state of "virgo-dummy" to "Unmanaged" and "" 65ms

And I change the state of "andromeda-dummy" to "Unmanaged" and "" 50ms

And I click save 54ms

Then I wait until I see "Package states have been saved." text 215ms

Scenario:
Cleanup: remove old packages from SLES minion
5s 619ms 5

When I disable repository "test_repo_rpm_pool" on this "sle_minion" 437ms

And I remove package "milkyway-dummy" from this "sle_minion" without error control 1s 407ms

And I remove package "virgo-dummy" from this "sle_minion" without error control 1s 434ms

And I remove package "andromeda-dummy" from this "sle_minion" without error control 1s 460ms

And I refresh the metadata for "sle_minion" 878ms

@skip_if_github_validation @sle_minion @scope_salt
Feature:Verify that Salt mgrcompat state works when the new module.run syntax is enabled 16m 50s 927ms 9 1

Scenario:
Log in as org admin user
1s 731ms 1

Given I am authorized 1s 731ms

Scenario:
Remove mgrcompat module from minion synced modules and schedule Hardware Refresh
27s 188ms 8

Given I remove "minion/extmods/states/mgrcompat.py" from salt cache on "sle_minion" 720ms

And I remove "minion/extmods/states/__pycache__/mgrcompat*" from salt cache on "sle_minion" 396ms

And I am on the Systems overview page of this "sle_minion" 1s 104ms

When I follow "Hardware" 588ms

And I click on "Schedule Hardware Refresh" 61ms

Then I should see a "You have successfully scheduled a hardware profile refresh" text 123ms

When I wait until event "Hardware List Refresh scheduled" is completed 22s 81ms

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "sle_minion" 2s 111ms

Scenario:
Remove saltutil grain and mgrcompat module from minion and schedule Hardware Refresh
29s 903ms 10

Given I remove "minion/extmods/states/mgrcompat.py" from salt cache on "sle_minion" 391ms

And I remove "minion/extmods/states/__pycache__/mgrcompat*" from salt cache on "sle_minion" 393ms

And I store "grains: {__suse_reserved_saltutil_states_support: False}" into file "custom_grains.conf" in salt minion config directory on "sle_minion" 405ms

And I refresh salt-minion grains on "sle_minion" 1s 822ms

And I am on the Systems overview page of this "sle_minion" 1s 35ms

When I follow "Hardware" 572ms

And I click on "Schedule Hardware Refresh" 781ms

Then I should see a "You have successfully scheduled a hardware profile refresh" text 119ms

When I wait until event "Hardware List Refresh scheduled" is completed 22s 286ms

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "sle_minion" 2s 95ms

Scenario:
Delete SLES minion system profile before mgrcompat test
4m 6s 546ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 9ms

When I follow "Delete System" 479ms

Then I should see a "Confirm System Profile Deletion" text 62ms

When I click on "Delete Profile" 67ms

And I wait until I see "has been deleted" text 4m 3s 831ms

And I wait until Salt client is inactive on "sle_minion" 722ms

Then "sle_minion" should not be registered 373ms

Scenario:
Enable new module.run syntax on the minion and perform registration
1m 45s 704ms 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" 399ms

When I follow the left menu "Systems > Bootstrapping" 79ms

Then I should see a "Bootstrap Minions" text 61ms

When I enter the hostname of "sle_minion" as "hostname" 143ms

And I enter "22" as "port" 54ms

And I enter "root" as "user" 59ms

And I enter "linux" as "password" 63ms

And I select the hostname of "proxy" from "proxies" if present 75ms

And I click on "Bootstrap" 61ms

And I wait until I see "Bootstrap process initiated." text 22s 454ms

And I wait until onboarding is completed for "sle_minion" 1m 22s 250ms

Scenario:
Check if onboarding for the minion with the new module.run syntax was successful
9s 197ms 3

When I follow the left menu "Systems > System List > All" 157ms

And I wait until I see the name of "sle_minion", refreshing the page 708ms

And I wait until onboarding is completed for "sle_minion" 8s 332ms

Scenario:
Check that installed packages are visible with the new module.run syntax
2s 46ms 4

Given I am on the Systems overview page of this "sle_minion" 1s 63ms

When I follow "Software" in the content area 72ms

And I follow "List / Remove" 789ms

Then I should see a "aaa_base" text 121ms

Scenario:
Check that Hardware Refresh button works on a SLE minion with new module.run syntax
26s 434ms 6

Given I am on the Systems overview page of this "sle_minion" 1s 33ms

And I follow "Hardware" 537ms

And I click on "Schedule Hardware Refresh" 843ms

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 822ms

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "sle_minion" 2s 86ms

Scenario:
Cleanup: Delete profile of the minion and disable new module.run syntax
4m 8s 662ms 9

Given I am on the Systems overview page of this "sle_minion" 990ms

And I remove "custom_modulerun.conf" from salt minion config directory on "sle_minion" 385ms

And I remove "custom_grains.conf" from salt minion config directory on "sle_minion" 396ms

When I follow "Delete System" 450ms

Then I should see a "Confirm System Profile Deletion" text 61ms

When I click on "Delete Profile" 62ms

And I wait until I see "has been deleted" text 4m 5s 147ms

And I wait until Salt client is inactive on "sle_minion" 731ms

Then "sle_minion" should not be registered 437ms

Scenario:
Cleanup: bootstrap again the minion after mgrcompat tests
5m 13s 510ms 11 1

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 79ms

When I enter the hostname of "sle_minion" as "hostname" 144ms

And I enter "22" as "port" 55ms

And I enter "root" as "user" 58ms

And I enter "linux" as "password" 62ms

And I select "1-SUSE-KEY-x86_64" from "activationKeys" 73ms

And I select the hostname of "proxy" from "proxies" if present 63ms

And I click on "Bootstrap" 62ms

And I wait until I see "Bootstrap process initiated." text 23s 126ms

And I wait until onboarding is completed for "sle_minion" 4m 33s 879ms 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/min_salt_mgrcompat_state.feature:108:in `I wait until onboarding is completed for "sle_minion"'

15s 818ms Show Info + 
23:00:28:000 - 23:05:26:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/History.do?sid=1000010020&
Screenshot +

@skip_if_github_validation @sle_minion @scope_salt @flaky
Feature:Lock packages on SLES salt minion 3m 58s 986ms 8 2

Scenario:
Log in as org admin user
2s 226ms 1

Given I am authorized 2s 226ms

Scenario:
Pre-requisite: install packages needed for locking test
17s 84ms 1 2 1

When I install package "orion-dummy" on this "sle_minion" 982ms Show Error + 
                                            
 FAIL: zypper --non-interactive install -y orion-dummy returned status code = 104.
Output:
Loading repository data...
Reading installed packages...
'orion-dummy' 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/secondary/min_salt_lock_packages.feature:19:in `I install package "orion-dummy" on this "sle_minion"'

And I install package "milkyway-dummy" on this "sle_minion" 0s

And I remove package "hoag-dummy" from this "sle_minion" without error control 0s

16s 102ms Show Info + 
23:05:56:000 - 23:05:57:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/YourRhn.do
Screenshot +

Scenario:
Lock a package on the client
39s 800ms 10 3 1

Given I am on the Systems overview page of this "sle_minion" 1s 183ms

When I follow "Software" in the content area 76ms

And I follow "Lock / Unlock" 719ms

And I enter "hoag-dummy-1.1-1.1" as the filtered package name 56ms

And I click on the filter button 774ms

And I check row with "hoag-dummy-1.1-1.1" and arch of "sle_minion" 62ms

And I click on "Lock" 748ms

Then I should see a "Packages has been requested for being locked." text 76ms

When I wait until event "Lock packages scheduled" is completed 19s 17ms

Then "hoag-dummy-1.1-1.1" is locked on "sle_minion" 941ms Show Error + 
                                            
 FAIL: zypper locks  --solvables | grep hoag-dummy-1.1-1.1 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/lock_packages_on_client.rb:10:in `/^"(.*?)" is (locked|unlocked) on "(.*?)"$/'
features/secondary/min_salt_lock_packages.feature:33:in `"hoag-dummy-1.1-1.1" is locked on "sle_minion"'

When I follow "Software" in the content area 0s

And I follow "Lock / Unlock" 0s

Then package "hoag-dummy-1.1-1.1" is reported as locked 0s

16s 141ms Show Info + 
23:06:13:000 - 23:06:37:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010020&aid=169
Screenshot +

Scenario:
Attempt to install a locked package on the client
29s 185ms 17

Given I am on the Systems overview page of this "sle_minion" 1s 352ms

When I follow "Software" in the content area 73ms

And I follow "Lock / Unlock" 562ms

And package "hoag-dummy-1.1-1.1" is reported as locked 32ms

And I follow "Install" 719ms

And I enter "hoag-dummy-1.1-1.1" as the filtered package name 57ms

And I click on the filter button 596ms

And I check row with "hoag-dummy-1.1-1.1" and arch of "sle_minion" 87ms

And I click on "Install Packages" 657ms

And I click on "Confirm" 896ms

Then I should see a "1 package install has been scheduled for" text 64ms

When I follow "Events" 478ms

And I follow "History" 484ms

And I wait until I see the event "Package Install/Upgrade scheduled" completed during last minute, refreshing the page 22s 969ms

And I follow the event "Package Install/Upgrade scheduled" completed during last minute 60ms

Then the package scheduled is "hoag-dummy-1.1-1.1" 20ms

And the action status is "Failed" 71ms

Scenario:
Unlock a package on the client
35s 114ms 16

Given I am on the Systems overview page of this "sle_minion" 1s 233ms

When I follow "Software" in the content area 75ms

And I follow "Lock / Unlock" 717ms

And package "hoag-dummy-1.1-1.1" is reported as locked 27ms

And I enter "hoag-dummy-1.1-1.1" as the filtered package name 60ms

And I click on the filter button 611ms

And I check row with "hoag-dummy-1.1-1.1" and arch of "sle_minion" 21ms

And I click on "Unlock" 689ms

Then I should see a "Packages has been requested for being unlocked." text 78ms

When I wait until event "Lock packages scheduled" is completed 19s 50ms

Then "hoag-dummy-1.1-1.1" is unlocked on "sle_minion" 988ms

When I follow "Software" in the content area 69ms

And I follow "Lock / Unlock" 661ms

And I enter "hoag-dummy-1.1-1.1" as the filtered package name 66ms

And I click on the filter button 734ms

Then package "hoag-dummy-1.1-1.1" is reported as unlocked 10s 25ms

Scenario:
Schedule a package lock
3s 345ms 9

Given I am on the Systems overview page of this "sle_minion" 1s 112ms

When I follow "Software" in the content area 62ms

And I follow "Lock / Unlock" 505ms

And I enter "hoag-dummy-1.1-1.1" as the filtered package name 58ms

And I click on the filter button 752ms

And I check row with "hoag-dummy-1.1-1.1" and arch of "sle_minion" 68ms

And I click on "Lock" 698ms

Then I should see a "Packages has been requested for being locked." text 75ms

And package "hoag-dummy-1.1-1.1" is reported as pending to be locked 11ms

Scenario:
Schedule another package lock
25s 214ms 16

Given I am on the Systems overview page of this "sle_minion" 1s 210ms

When I follow "Software" in the content area 62ms

And I follow "Lock / Unlock" 856ms

And I enter "milkyway-dummy-2.0-1.1" as the filtered package name 62ms

And I click on the filter button 759ms

When I check row with "milkyway-dummy-2.0-1.1" and arch of "sle_minion" 60ms

And I click on "Lock" 665ms

Then I should see a "Packages has been requested for being locked." text 93ms

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 19s 6ms

Then "hoag-dummy-1.1-1.1" is locked on "sle_minion" 987ms

And "milkyway-dummy-2.0-1.1" is locked on "sle_minion" 656ms

When I follow "Software" in the content area 69ms

And I follow "Lock / Unlock" 652ms

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 31ms

Scenario:
Mix package locks and unlock events
39s 302ms 32

Given I am on the Systems overview page of this "sle_minion" 1s 134ms

When I follow "Software" in the content area 60ms

And I follow "Lock / Unlock" 579ms

And package "hoag-dummy-1.1-1.1" is reported as locked 26ms

And package "milkyway-dummy-2.0-1.1" is reported as locked 31ms

And I enter "orion-dummy-1.1-1.1" as the filtered package name 64ms

And I click on the filter button 760ms

When I check row with "orion-dummy-1.1-1.1" and arch of "sle_minion" 64ms

And I click on "Lock" 749ms

Then I should see a "Packages has been requested for being locked." text 90ms

And package "orion-dummy-1.1-1.1" is reported as pending to be locked 11ms

When I follow "Lock / Unlock" 666ms

And I enter "hoag-dummy-1.1-1.1" as the filtered package name 55ms

And I click on the filter button 898ms

And I uncheck row with "hoag-dummy-1.1-1.1" and arch of "sle_minion" 61ms

And I enter "milkyway-dummy-2.0-1.1" as the filtered package name 55ms

And I click on the filter button 130ms

And I check row with "milkyway-dummy-2.0-1.1" and arch of "sle_minion" 23ms

And I click on "Unlock" 755ms

Then I should see a "Packages has been requested for being unlocked." text 77ms

And package "milkyway-dummy-2.0-1.1" is reported as pending to be unlocked 10ms

When I wait until event "Lock packages scheduled" is completed 19s 75ms

Then "hoag-dummy-1.1-1.1" is locked on "sle_minion" 967ms

And "milkyway-dummy-2.0-1.1" is unlocked on "sle_minion" 661ms

And "orion-dummy-1.1-1.1" is locked on "sle_minion" 662ms

When I follow "Software" in the content area 70ms

And I follow "Lock / Unlock" 633ms

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 33ms

And I enter "milkyway-dummy-2.0-1.1" as the filtered package name 58ms

And I click on the filter button 781ms

And package "milkyway-dummy-2.0-1.1" is reported as unlocked 10s 21ms

Scenario:
Mix package locks and unlock events part 2
45s 859ms 18

Given I am on the Systems overview page of this "sle_minion" 1s 205ms

And I follow "Software" in the content area 61ms

And I follow "Lock / Unlock" 649ms

When I click on "Select All" 590ms

And I click on "Unlock" 959ms

Then I should see a "Packages has been requested for being unlocked." text 111ms

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 19s 26ms

Then "hoag-dummy-1.1-1.1" is unlocked on "sle_minion" 995ms

And "orion-dummy-1.1-1.1" is unlocked on "sle_minion" 661ms

When I follow "Software" in the content area 71ms

And I follow "Lock / Unlock" 569ms

And I enter "hoag-dummy-1.1-1.1" as the filtered package name 68ms

And I click on the filter button 629ms

Then package "hoag-dummy-1.1-1.1" is reported as unlocked 10s 13ms

And I enter "orion-dummy-1.1-1.1" as the filtered package name 53ms

And I click on the filter button 139ms

And package "orion-dummy-1.1-1.1" is reported as unlocked 10s 14ms

Scenario:
Cleanup: remove packages after testing locks
1s 852ms 2

Then I remove package "orion-dummy" from this "sle_minion" 1s 85ms

And I remove package "milkyway-dummy" from this "sle_minion" 767ms

@scope_onboarding
Feature:Empty minion profile operations 1m 11s 194ms 8

Scenario:
Log in as org admin user
2s 108ms 1

Given I am authorized 2s 108ms

Scenario:
Create an empty minion profile with HW address via API
1s 426ms 1

When I call system.create_system_profile() with name "empty-profile" and HW address "00:11:22:33:44:55" 1s 426ms

Scenario:
Create an empty minion profile with hostname via API
696ms 1

When I call system.create_system_profile() with name "empty-profile-hostname" and hostname "min-retail.mgr.suse.de" 696ms

Scenario:
Check the created empty minion profiles in Unprovisioned Systems page
443ms 4

And I follow the left menu "System > System List > Unprovisioned Systems" 202ms

And I wait until I see "empty-profile" text, refreshing the page 88ms

And I wait until I see "00:11:22:33:44:55" text 76ms

And I wait until I see "empty-profile-hostname" text 75ms

Scenario:
Check the empty profiles has the hostname set
1s 80ms 3

And I follow the left menu "System > System List > Unprovisioned Systems" 69ms

And I follow "empty-profile-hostname" 940ms

Then I wait until I see "min-retail.mgr.suse.de" text, refreshing the page 69ms

Scenario:
Check the empty minion profiles visible via API
515ms 3

When I call system.list_empty_system_profiles() 515ms

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
1m 629ms 7

When I follow the left menu "Systems > System List" 67ms

And I wait until I see the "empty-profile" system, refreshing the page 58s 24ms

And I follow "empty-profile" 888ms

And I follow "Delete System" 568ms

Then I should see a "Confirm System Profile Deletion" text 59ms

When I click on "Delete Profile" 81ms

And I wait until I see "has been deleted" text 939ms

Scenario:
Cleanup: Delete second empty minion profiles
4s 295ms 7

When I follow the left menu "Systems > System List" 76ms

And I wait until I see the "empty-profile-hostname" system, refreshing the page 705ms

And I follow "empty-profile-hostname" 629ms

And I follow "Delete System" 494ms

Then I should see a "Confirm System Profile Deletion" text 60ms

When I click on "Delete Profile" 55ms

And I wait until I see "has been deleted" text 2s 273ms

@scope_onboarding @custom_download_endpoint
Feature:Repos file generation based on custom pillar data 1m 15s 948ms 9 3

Scenario:
Log in as org admin user
2s 140ms 1

Given I am authorized 2s 140ms

@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 776ms 11

Warning: Radio button 'openSUSE Tumbleweed (x86_64)' is already checked

Given I am on the Systems overview page of this "sle_minion" 1s 751ms

When I follow "Software" in the content area 72ms

And I follow "Software Channels" in the content area 84ms

And I wait until I do not see "Loading..." text 69ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 210ms

And I click on "Next" 405ms

Then I should see a "Confirm Software Channel Change" text 65ms

When I click on "Confirm" 74ms

Then I should see a "Changing the channels has been scheduled." text 413ms

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 16s 554ms

Scenario:
Check the default RPM download point values
2s 294ms 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 197ms

Then the susemanager repo file should exist on the "sle_minion" 705ms

And the repo file should contain the normal download endpoint on the "sle_minion" 391ms

Scenario:
Set the custom RPM download point
7s 426ms 5

Given I am on the Systems overview page of this "sle_minion" 1s 163ms

When I install a salt pillar top file for "pkg_endpoint" with target "*" on the server 2s 409ms

And I wait for "1" seconds 1s

And I install the package download endpoint pillar file on the server 704ms

And I refresh the pillar data 2s 147ms

@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
17s 999ms 10

Warning: Radio button 'openSUSE Tumbleweed (x86_64)' is already checked

When I follow "Software" in the content area 62ms

And I follow "Software Channels" in the content area 60ms

And I wait until I do not see "Loading..." text 70ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 218ms

And I click on "Next" 438ms

Then I should see a "Confirm Software Channel Change" text 63ms

When I click on "Confirm" 76ms

Then I should see a "Changing the channels has been scheduled." text 421ms

When I follow "scheduled" in the content area 76ms

And I wait until I see "1 system successfully completed this action." text, refreshing the page 16s 510ms

Scenario:
Check the channel.repo file to see the custom RPM download point
2s 240ms 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 121ms

Then the susemanager repo file should exist on the "sle_minion" 721ms

And the repo file should contain the custom download endpoint on the "sle_minion" 397ms

Scenario:
Cleanup: remove the custom RPM download point
5s 48ms 3

When I delete the package download endpoint pillar file from the server 1s 42ms

And I install a salt pillar top file for "disable_local_repos_off, salt_bundle_config" with target "*" on the server 1s 888ms

And I refresh the pillar data 2s 118ms

@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 904ms 12

Warning: Radio button 'openSUSE Tumbleweed (x86_64)' is already checked

When I follow "Software" in the content area 81ms

And I follow "Software Channels" in the content area 76ms

And I wait until I do not see "Loading..." text 66ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 180ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 315ms

And I check "Fake-RPM-SUSE-Channel" 40ms

And I click on "Next" 63ms

Then I should see a "Confirm Software Channel Change" text 66ms

When I click on "Confirm" 84ms

Then I should see a "Changing the channels has been scheduled." text 407ms

When I follow "scheduled" in the content area 75ms

And I wait until I see "1 system successfully completed this action." text, refreshing the page 16s 446ms

Scenario:
Cleanup: recheck the default RPM download point values
1s 117ms 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" 722ms

And the repo file should contain the normal download endpoint on the "sle_minion" 395ms

@skip_if_github_validation @sle_minion @scope_action_chains @flaky
Feature:Action chains on Salt minions 8m 57s 525ms 33

Scenario:
Log in as admin user
1s 903ms 1

Given I am authorized for the "Admin" section 1s 903ms

Scenario:
Pre-requisite: downgrade repositories to lower version on Salt minion
6s 399ms 6

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 758ms

And I remove package "andromeda-dummy" from this "sle_minion" without error control 777ms

And I remove package "virgo-dummy" from this "sle_minion" without error control 775ms

And I install package "milkyway-dummy" on this "sle_minion" without error control 1s 577ms

And I install old package "andromeda-dummy-1.0" on this "sle_minion" 1s 572ms

And I refresh the metadata for "sle_minion" 937ms

Scenario:
Pre-requisite: refresh package list and check installed packages after downgrade on SLE minion
14s 13ms 3

When I refresh packages list via spacecmd on "sle_minion" 3s 144ms

And I wait until refresh package list on "sle_minion" is finished 8s 129ms

Then spacecmd should show packages "milkyway-dummy andromeda-dummy-1.0" installed on "sle_minion" 2s 738ms

Scenario:
Pre-requisite: wait until downgrade is finished on SLE minion
1s 763ms 5

Given I am on the Systems overview page of this "sle_minion" 1s 124ms

When I follow "Software" in the content area 73ms

And I follow "List / Remove" in the content area 70ms

And I enter "andromeda-dummy" as the filtered package name 214ms

And I click on the filter button until page does contain "andromeda-dummy-1.0" text 280ms

Scenario:
Pre-requisite: ensure the errata cache is computed before testing on Salt minion
19s 972ms 6

When I follow the left menu "Admin > Task Schedules" 163ms

And I follow "errata-cache-default" 1s 331ms

And I follow "errata-cache-bunch" 1s 634ms

And I click on "Single Run Schedule" 1s 202ms

Then I should see a "bunch was scheduled" text 278ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 15s 362ms

Scenario:
Create a custom action chain for the Salt minion
603ms 3

When I create an action chain with label "salt_minion_action_chain" via API 398ms

And I follow the left menu "Schedule > Action Chains" 143ms

Then I should see a "salt_minion_action_chain" text 62ms

Scenario:
Add a patch installation to the action chain on Salt minion
23s 162ms 10

Given I am on the Systems overview page of this "sle_minion" 1s 217ms

When I follow "Software" in the content area 72ms

And I follow "Patches" in the content area 66ms

And I enter "andromeda" as the filtered synopsis 54ms

And I click on the filter button 10s 128ms

And I check "andromeda-dummy-6789" in the list 69ms

And I click on "Apply Patches" 632ms

And I check radio button "schedule-by-action-chain" 10s 72ms

And I click on "Confirm" 773ms

Then I should see a "Action has been successfully added to the Action Chain" text 75ms

Scenario:
Add a package removal to the action chain on Salt minion
13s 973ms 10

Given I am on the Systems overview page of this "sle_minion" 1s 384ms

When I follow "Software" in the content area 80ms

And I follow "List / Remove" in the content area 66ms

And I enter "milkyway-dummy" as the filtered package name 215ms

And I click on the filter button 833ms

And I check row with "milkyway-dummy" and arch of "sle_minion" 60ms

And I click on "Remove Packages" 598ms

And I check radio button "schedule-by-action-chain" 10s 72ms

And I click on "Confirm" 597ms

Then I should see a "Action has been successfully added to the Action Chain" text 64ms

Scenario:
Add a package installation to an action chain on Salt minion
12s 352ms 9

When I follow "Software" in the content area 67ms

And I follow "Install New Packages" in the content area 64ms

And I enter "virgo-dummy" as the filtered package name 152ms

And I click on the filter button 696ms

And I check "virgo-dummy" in the list 54ms

And I click on "Install Packages" 601ms

And I check radio button "schedule-by-action-chain" 10s 53ms

And I click on "Confirm" 597ms

Then I should see a "Action has been successfully added to the Action Chain" text 64ms

Scenario:
Create a configuration channel for testing action chain on Salt minion
784ms 7

When I follow the left menu "Configuration > Channels" 123ms

And I follow "Create Config Channel" 325ms

And I enter "Action Chain Channel" as "cofName" 70ms

And I enter "actionchainchannel" as "cofLabel" 66ms

And I enter "This is a test channel" as "cofDescription" 68ms

And I click on "Create Config Channel" 66ms

Then I should see a "Action Chain Channel" text 63ms

Scenario:
Add a configuration file to configuration channel for testing action chain on Salt minion
2s 25ms 8

When I follow the left menu "Configuration > Channels" 65ms

And I follow "Action Chain Channel" 390ms

And I follow "Create Configuration File or Directory" 393ms

And I enter "/etc/action-chain.cnf" as "cffPath" 78ms

And I enter "Testchain=YES_PLEASE" in the editor 5ms

And I click on "Create Configuration File" 977ms

Then I should see a "Revision 1 of /etc/action-chain.cnf from channel Action Chain Channel" text 96ms

And I should see a "Update Configuration File" button 18ms

Scenario:
Download the configuration file from configuration channel
2s 261ms 7

When I follow the left menu "Configuration > Channels" 61ms

And I follow "Action Chain Channel" 503ms

And I follow "List/Remove Files" 465ms

And I follow "/etc/action-chain.cnf" 498ms

And I follow "Download File" 234ms

And I wait until file "/tmp/downloads/action-chain.cnf" exists on "localhost" 168ms

Then file "/tmp/downloads/action-chain.cnf" should contain "Testchain=YES_PLEASE" on "localhost" 329ms

Scenario:
Subscribe system to configuration channel for testing action chain on Salt minion
3s 52ms 8

Given I am on the Systems overview page of this "sle_minion" 1s 117ms

When I follow "Configuration" in the content area 74ms

And I follow "Manage Configuration Channels" in the content area 74ms

And I follow first "Subscribe to Channels" in the content area 71ms

And I check "Action Chain Channel" in the list 60ms

And I click on "Continue" 678ms

And I click on "Update Channel Rankings" 895ms

Then I should see a "Channel Subscriptions successfully changed for" text 80ms

Scenario:
Add a configuration file deployment to the action chain on Salt minion
13s 119ms 9

When I follow the left menu "Configuration > Channels" 113ms

And I follow "Action Chain Channel" 509ms

And I follow "Deploy Files" in the content area 68ms

And I click on "Deploy All Files" 677ms

And I check the "sle_minion" client 58ms

And I click on "Confirm & Deploy to Selected Systems" 780ms

And I check radio button "schedule-by-action-chain" 10s 61ms

And I click on "Deploy Files to Selected Systems" 781ms

Then I should see a "Action has been successfully added to the Action Chain" text 68ms

Scenario:
Add apply highstate to action chain on Salt minion
11s 338ms 4

Given I am on the Systems overview page of this "sle_minion" 1s 116ms

When I follow "States" in the content area 74ms

And I check radio button "schedule-by-action-chain" 10s 81ms

And I click on "Apply Highstate" 67ms

Scenario:
Add a reboot action to the action chain on Salt minion
12s 805ms 5

Given I am on the Systems overview page of this "sle_minion" 1s 61ms

When I follow first "Schedule System Reboot" 579ms

And I check radio button "schedule-by-action-chain" 10s 77ms

And I click on "Reboot system" 998ms

Then I should see a "Action has been successfully added to the Action Chain" text 88ms

Scenario:
Add a remote command to the action chain on Salt minion
11s 54ms 6

When I follow "Details" in the content area 77ms

And I follow "Remote Command" in the content area 72ms

And I enter as remote command this script in #!/bin/bash touch /tmp/action_chain_one_system_done 69ms

And I check radio button "schedule-by-action-chain" 10s 64ms

And I click on "Schedule" 688ms

Then I should see a "Action has been successfully added to the Action Chain" text 81ms

Scenario:
Verify the action chain list on Salt minion
1s 890ms 10

When I follow "Schedule" 428ms

And I follow "Action Chains" 293ms

And I follow "salt_minion_action_chain" 579ms

Then I should see a "1. Apply patch(es) andromeda-dummy-6789 on 1 system" text 94ms

And I should see a "2. Remove milkyway-dummy from 1 system" text 84ms

And I should see a "3. Install or update virgo-dummy on 1 system" text 81ms

And I should see a text like "4. Deploy.*/etc/action-chain.cnf.*to 1 system" 87ms

And I should see a "5. Apply Highstate" text 81ms

And I should see a "6. Reboot 1 system" text 79ms

And I should see a "7. Run a remote command on 1 system" text 79ms

Scenario:
Check that a different user cannot see the action chain for Salt minion
3s 143ms 4

Given I am authorized as "testing" with password "testing" 2s 7ms

When I follow "Schedule" 878ms

And I follow "Action Chains" 249ms

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 28s 474ms 9

Given I am authorized for the "Admin" section 1s 871ms

When I am on the Systems overview page of this "sle_minion" 1s 687ms

And I follow "Schedule" 371ms

And I follow "Action Chains" 263ms

And I follow "salt_minion_action_chain" 325ms

And I click on "Save and Schedule" 61ms

Then I should see a "Action Chain salt_minion_action_chain has been scheduled for execution." text 833ms

When I wait for "virgo-dummy" to be installed on "sle_minion" 24s 484ms

And I wait at most 300 seconds until file "/tmp/action_chain_one_system_done" exists on "sle_minion" 3m 58s 575ms

Scenario:
Create a custom action chain for the Salt minion
583ms 3

When I create an action chain with label "salt_minion_action_chain_to_delete" via API 440ms

And I follow the left menu "Schedule > Action Chains" 74ms

Then I should see a "salt_minion_action_chain_to_delete" text 69ms

Scenario:
Add a remote command to the action chain on Salt minion
12s 810ms 6

Given I am on the Systems overview page of this "sle_minion" 1s 342ms

When I follow "Remote Command" 586ms

And I enter as remote command this script in #!/bin/bash uptime 52ms

And I check radio button "schedule-by-action-chain" 10s 76ms

And I click on "Schedule" 664ms

Then I should see a "Action has been successfully added to the Action Chain" text 86ms

Scenario:
Delete the action chain for Salt minion
1s 492ms 5

When I follow "Schedule" 347ms

And I follow "Action Chains" 292ms

And I follow "salt_minion_action_chain_to_delete" 300ms

And I follow "Delete Action Chains" in the content area 81ms

And I click on "Delete" 470ms

Scenario:
Downgrade again repositories to lower version on Salt minion
7s 32ms 4

When I remove package "andromeda-dummy" from this "sle_minion" without error control 2s 291ms

And I remove package "virgo-dummy" from this "sle_minion" without error control 1s 422ms

And I install package "milkyway-dummy" on this "sle_minion" without error control 1s 631ms

And I install old package "andromeda-dummy-1.0" on this "sle_minion" 1s 687ms

Scenario:
Refresh package list and check installed packages after second downgrade on SLE minion
12s 558ms 3

When I refresh packages list via spacecmd on "sle_minion" 3s 770ms

And I wait until refresh package list on "sle_minion" is finished 5s 841ms

Then spacecmd should show packages "milkyway-dummy andromeda-dummy-1.0" installed on "sle_minion" 2s 946ms

Scenario:
Ensure again the errata cache is computed before testing on Salt minion
52s 801ms 6

When I follow the left menu "Admin > Task Schedules" 126ms

And I follow "errata-cache-default" 1s 364ms

And I follow "errata-cache-bunch" 1s 242ms

And I click on "Single Run Schedule" 1s 535ms

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 48s 258ms

Scenario:
Add operations to the action chain via API for Salt minions
7s 659ms 11

Running actions:
- System reboot
- Package Removal
- Package Install/Upgrade
- Run an arbitrary script
- Package Install/Upgrade
- Removed "System reboot" action
- Removed "Package Removal" action
- Removed "Package Install/Upgrade" action
- Removed "Run an arbitrary script" action
- Removed "Package Install/Upgrade" action

Given I want to operate on this "sle_minion" 415ms

When I create an action chain with label "salt_minion_api_chain" via API 396ms

And I add a package install to the action chain via API 884ms

And I add a package removal to the action chain via API 871ms

And I add a package upgrade to the action chain via API 939ms

And I add the script "exit 1;" to the action chain via API 409ms

And I add a system reboot to the action chain via API 406ms

Then I should be able to see all these actions in the action chain via API 364ms

When I remove each action within the chain via API 2s 216ms

Then the current action chain should be empty 363ms

And I delete the action chain via API 390ms

Scenario:
Run an action chain via API on Salt minion
8s 848ms 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" 373ms

When I create an action chain with label "salt_minion_multiple_scripts" via API 384ms

And I add the script "echo -n 1 >> /tmp/action_chain.log" to the action chain via API 434ms

And I add the script "echo -n 2 >> /tmp/action_chain.log" to the action chain via API 452ms

And I add the script "echo -n 3 >> /tmp/action_chain.log" to the action chain via API 414ms

And I add the script "touch /tmp/action_chain_done" to the action chain via API 387ms

Then I should be able to see all these actions in the action chain via API 370ms

When I schedule the action chain via API 507ms

And I wait until there are no more action chains listed via API 426ms

And I wait until file "/tmp/action_chain_done" exists on "sle_minion" 3s 919ms

Then file "/tmp/action_chain.log" should contain "123" on "sle_minion" 792ms

When I wait until there are no more scheduled actions listed via API 385ms

Scenario:
Cleanup: remove Salt minion from configuration channel
1s 528ms 6

When I follow the left menu "Configuration > Channels" 153ms

And I follow "Action Chain Channel" 512ms

And I follow "Systems" in the content area 70ms

And I check the "sle_minion" client 69ms

And I click on "Unsubscribe systems" 658ms

Then I should see a "Successfully unsubscribed 1 system(s)." text 63ms

Scenario:
Cleanup: remove configuration channel for Salt minion
1s 336ms 4

When I follow the left menu "Configuration > Channels" 64ms

And I follow "Action Chain Channel" 418ms

And I follow "Delete Channel" 295ms

And I click on "Delete Config Channel" 557ms

Scenario:
Cleanup: remove packages and repository used in action chain for Salt minion
4s 545ms 4

When I remove package "andromeda-dummy" from this "sle_minion" without error control 1s 396ms

And I remove package "virgo-dummy" from this "sle_minion" without error control 775ms

And I remove package "milkyway-dummy" from this "sle_minion" without error control 1s 697ms

And I disable repository "test_repo_rpm_pool" on this "sle_minion" without error control 675ms

Scenario:
Cleanup: remove temporary files for testing action chains on Salt minion
2s 69ms 4

When I run "rm -f /tmp/action_chain.log" on "sle_minion" without error control 695ms

And I run "rm -f /tmp/action_chain_done" on "sle_minion" without error control 505ms

And I run "rm -f /etc/action-chain.cnf" on "sle_minion" without error control 473ms

And I run "rm -f /tmp/action_chain_one_system_done" on "sle_minion" without error control 394ms

Scenario:
Cleanup: remove downloaded files
164ms 1

When I run "rm -f /tmp/downloads/action-chain.cnf" on "localhost" without error control 164ms

@skip_if_github_validation @ssh_minion @scope_action_chains @scope_salt_ssh
Feature:Salt SSH action chain 10m 49s 715ms 30

Scenario:
Log in as org admin user
482ms 1

Given I am authorized for the "Admin" section 482ms

Scenario:
Pre-requisite: downgrade repositories to lower version on SSH minion
6s 488ms 6

When I enable repository "test_repo_rpm_pool" on this "ssh_minion" 777ms

And I remove package "andromeda-dummy" from this "ssh_minion" without error control 1s 211ms

And I remove package "virgo-dummy" from this "ssh_minion" without error control 1s 195ms

And I install package "milkyway-dummy" on this "ssh_minion" without error control 1s 220ms

And I install old package "andromeda-dummy-1.0" on this "ssh_minion" 1s 256ms

And I refresh the metadata for "ssh_minion" 827ms

Scenario:
Pre-requisite: refresh package list and check newly installed packages on SSH minion
28s 886ms 3

When I refresh packages list via spacecmd on "ssh_minion" 3s 621ms

And I wait until refresh package list on "ssh_minion" is finished 22s 8ms

Then spacecmd should show packages "milkyway-dummy andromeda-dummy-1.0" installed on "ssh_minion" 3s 256ms

Scenario:
Pre-requisite: wait until downgrade is finished on SSH minion
1s 922ms 5

Given I am on the Systems overview page of this "ssh_minion" 1s 310ms

When I follow "Software" in the content area 70ms

And I follow "List / Remove" in the content area 66ms

And I enter "andromeda-dummy" as the filtered package name 200ms

And I click on the filter button until page does contain "andromeda-dummy-1.0" text 274ms

Scenario:
Pre-requisite: ensure the errata cache is computed before testing on SSH minion
42s 983ms 6

When I follow the left menu "Admin > Task Schedules" 148ms

And I follow "errata-cache-default" 1s 334ms

And I follow "errata-cache-bunch" 1s 288ms

And I click on "Single Run Schedule" 1s 510ms

Then I should see a "bunch was scheduled" text 267ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 38s 434ms

Scenario:
Create a custom action chain for the SSH minion
626ms 3

When I create an action chain with label "minssh_action_chain" via API 382ms

And I follow the left menu "Schedule > Action Chains" 161ms

Then I wait until I see "minssh_action_chain" text 82ms

Scenario:
Add a patch installation to the action chain on SSH minion
22s 795ms 10

Given I am on the Systems overview page of this "ssh_minion" 1s 34ms

When I follow "Software" in the content area 73ms

And I follow "Patches" in the content area 66ms

And I enter "andromeda" as the filtered synopsis 53ms

And I click on the filter button 10s 118ms

And I check "andromeda-dummy-6789" in the list 62ms

And I click on "Apply Patches" 635ms

And I check radio button "schedule-by-action-chain" 10s 62ms

And I click on "Confirm" 595ms

Then I should see a "Action has been successfully added to the Action Chain" text 93ms

Scenario:
Add a package removal to the action chain on SSH minion
12s 596ms 9

When I follow "Software" in the content area 74ms

And I follow "List / Remove" in the content area 69ms

And I enter "milkyway-dummy" as the filtered package name 235ms

And I click on the filter button 835ms

And I check row with "milkyway-dummy" and arch of "ssh_minion" 62ms

And I click on "Remove Packages" 574ms

And I check radio button "schedule-by-action-chain" 10s 71ms

And I click on "Confirm" 597ms

Then I should see a "Action has been successfully added to the Action Chain" text 75ms

Scenario:
Add a package installation to an action chain on SSH minion
12s 226ms 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 120ms

And I click on the filter button 638ms

And I check "virgo-dummy" in the list 55ms

And I click on "Install Packages" 572ms

And I check radio button "schedule-by-action-chain" 10s 52ms

And I click on "Confirm" 580ms

Then I should see a "Action has been successfully added to the Action Chain" text 72ms

Scenario:
Create a configuration channel for testing action chain on SSH minion
711ms 7

When I follow the left menu "Configuration > Channels" 120ms

And I follow "Create Config Channel" 263ms

And I enter "Action Chain Channel" as "cofName" 69ms

And I enter "actionchainchannel" as "cofLabel" 65ms

And I enter "This is a test channel" as "cofDescription" 68ms

And I click on "Create Config Channel" 63ms

Then I should see a "Action Chain Channel" text 61ms

Scenario:
Add a configuration file to configuration channel for testing action chain on SSH minion
1s 100ms 8

When I follow the left menu "Configuration > Channels" 66ms

And I follow "Action Chain Channel" 441ms

And I follow "Create Configuration File or Directory" 334ms

And I enter "/etc/action-chain.cnf" as "cffPath" 72ms

And I enter "Testchain=YES_PLEASE" in the editor 5ms

And I click on "Create Configuration File" 67ms

Then I should see a "Revision 1 of /etc/action-chain.cnf from channel Action Chain Channel" text 94ms

And I should see a "Update Configuration File" button 19ms

Scenario:
Subscribe system to configuration channel for testing action chain on SSH minion
2s 880ms 8

Given I am on the Systems overview page of this "ssh_minion" 1s 77ms

When I follow "Configuration" in the content area 75ms

And I follow "Manage Configuration Channels" in the content area 68ms

And I follow first "Subscribe to Channels" in the content area 66ms

And I check "Action Chain Channel" in the list 57ms

And I click on "Continue" 636ms

And I click on "Update Channel Rankings" 822ms

Then I should see a "Channel Subscriptions successfully changed for" text 77ms

Scenario:
Add a configuration file deployment to the action chain on SSH minion
12s 909ms 9

When I follow the left menu "Configuration > Channels" 111ms

And I follow "Action Chain Channel" 500ms

And I follow "Deploy Files" in the content area 66ms

And I click on "Deploy All Files" 640ms

And I check the "ssh_minion" client 65ms

And I click on "Confirm & Deploy to Selected Systems" 686ms

And I check radio button "schedule-by-action-chain" 10s 65ms

And I click on "Deploy Files to Selected Systems" 692ms

Then I should see a "Action has been successfully added to the Action Chain" text 82ms

Scenario:
Add apply highstate to action chain on SSH minion
11s 185ms 4

Given I am on the Systems overview page of this "ssh_minion" 989ms

When I follow "States" in the content area 71ms

And I check radio button "schedule-by-action-chain" 10s 65ms

And I click on "Apply Highstate" 59ms

Scenario:
Add a reboot action to the action chain on SSH minion
12s 527ms 5

Given I am on the Systems overview page of this "ssh_minion" 1s 32ms

When I follow first "Schedule System Reboot" 483ms

And I check radio button "schedule-by-action-chain" 10s 76ms

And I click on "Reboot system" 843ms

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 SSH minion
10s 877ms 6

When I follow "Details" in the content area 75ms

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 69ms

And I check radio button "schedule-by-action-chain" 10s 67ms

And I click on "Schedule" 516ms

Then I should see a "Action has been successfully added to the Action Chain" text 81ms

Scenario:
Verify the action chain list on SSH minion
1s 35ms 9

When I follow the left menu "Schedule > Action Chains" 132ms

And I follow "minssh_action_chain" 327ms

Then I should see a "1. Apply patch(es) andromeda-dummy-6789 on 1 system" text 80ms

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 91ms

And I should see a text like "4. Deploy.*/etc/action-chain.cnf.*to 1 system" 77ms

And I should see a "5. Apply Highstate" text 78ms

And I should see a "6. Reboot 1 system" text 80ms

And I should see a "7. Run a remote command on 1 system" text 81ms

Scenario:
Check that a different user cannot see the action chain for SSH minion
1s 822ms 3

Given I am authorized as "testing" with password "testing" 1s 706ms

When I follow the left menu "Schedule > Action Chains" 108ms

Then I should not see a "minssh_action_chain" link 7ms

Scenario:
Execute the action chain from the web UI on SSH minion
3s 7ms 6

Given I am authorized for the "Admin" section 1s 649ms

When I follow the left menu "Schedule > Action Chains" 104ms

And I wait until I see "minssh_action_chain" text 70ms

And I follow "minssh_action_chain" 309ms

Then I click on "Save and Schedule" 58ms

And I should see a "Action Chain minssh_action_chain has been scheduled for execution." text 814ms

Scenario:
Verify that the action chain was executed successfully
5m 24s 368ms 2

When I wait for "virgo-dummy" to be installed on "ssh_minion" 46s 98ms

And I wait at most 300 seconds until file "/tmp/action_chain_one_system_done" exists on "ssh_minion" 4m 38s 270ms

Scenario:
Create a custom action chain for the SSH minion
489ms 3

When I create an action chain with label "minssh_action_chain_to_delete" via API 359ms

And I follow the left menu "Schedule > Action Chains" 66ms

Then I should see a "minssh_action_chain_to_delete" text 63ms

Scenario:
Add a remote command to the action chain on SSH minion
12s 513ms 6

Given I am on the Systems overview page of this "ssh_minion" 1s 56ms

When I follow "Remote Command" 678ms

And I enter as remote command this script in #!/bin/bash uptime 56ms

And I check radio button "schedule-by-action-chain" 10s 67ms

And I click on "Schedule" 57ms

Then I should see a "Action has been successfully added to the Action Chain" text 596ms

Scenario:
Delete the action chain for SSH minion
549ms 4

When I follow the left menu "Schedule > Action Chains" 130ms

And I follow "minssh_action_chain_to_delete" 285ms

And I follow "Delete Action Chains" in the content area 75ms

Then I click on "Delete" 57ms

Scenario:
Cleanup: roll back action chain effects on SSH minion
1m 22s 696ms 21

Given I am on the Systems overview page of this "ssh_minion" 1s 207ms

When I run "rm /tmp/action_chain_done" on "ssh_minion" without error control 406ms

And I enable repository "test_repo_rpm_pool" on this "ssh_minion" 499ms

And I remove package "andromeda-dummy" from this "ssh_minion" without error control 1s 663ms

And I remove package "virgo-dummy" from this "ssh_minion" without error control 1s 209ms

And I install package "milkyway-dummy" on this "ssh_minion" without error control 1s 391ms

And I install old package "andromeda-dummy-1.0" on this "ssh_minion" 1s 251ms

And I follow "Software" in the content area 71ms

And I click on "Update Package List" 599ms

And I follow "Events" in the content area 69ms

And I wait until I do not see "Package List Refresh scheduled" text, refreshing the page 24s 147ms

And I follow "Software" in the content area 80ms

And I follow "List / Remove" in the content area 68ms

And I enter "andromeda-dummy" as the filtered package name 264ms

And I click on the filter button until page does contain "andromeda-dummy-1.0" text 277ms

When I follow the left menu "Admin > Task Schedules" 154ms

And I follow "errata-cache-default" 1s 284ms

And I follow "errata-cache-bunch" 1s 266ms

And I click on "Single Run Schedule" 1s 526ms

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 44s 991ms

Scenario:
Add operations to the action chain via API for SSH minions
6s 139ms 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" 346ms

When I create an action chain with label "minssh_api_chain" via API 339ms

And I add a package install to the action chain via API 799ms

And I add a package removal to the action chain via API 753ms

And I add a package upgrade to the action chain via API 822ms

And I add the script "exit 1;" to the action chain via API 361ms

Then I should be able to see all these actions in the action chain via API 326ms

When I remove each action within the chain via API 1s 679ms

Then the current action chain should be empty 354ms

And I delete the action chain via API 357ms

Scenario:
Run an action chain via API on SSH minion
28s 568ms 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" 363ms

When I create an action chain with label "minssh_multiple_scripts" via API 340ms

And I add the script "echo -n 1 >> /tmp/action_chain.log" to the action chain via API 361ms

And I add the script "echo -n 2 >> /tmp/action_chain.log" to the action chain via API 368ms

And I add the script "echo -n 3 >> /tmp/action_chain.log" to the action chain via API 361ms

And I add the script "touch /tmp/action_chain_done" to the action chain via API 353ms

Then I should be able to see all these actions in the action chain via API 338ms

When I schedule the action chain via API 418ms

Then I wait until there are no more action chains listed via API 369ms

When I wait until file "/tmp/action_chain_done" exists on "ssh_minion" 24s 155ms

Then file "/tmp/action_chain.log" should contain "123" on "ssh_minion" 801ms

When I wait until there are no more scheduled actions listed via API 336ms

Scenario:
Cleanup: remove SSH minion from configuration channel
875ms 6

When I follow the left menu "Configuration > Channels" 164ms

And I follow "Action Chain Channel" 437ms

And I follow "Systems" in the content area 83ms

And I check the "ssh_minion" client 68ms

And I click on "Unsubscribe systems" 57ms

Then I should see a "Successfully unsubscribed 1 system(s)." text 64ms

Scenario:
Cleanup: remove configuration channel for SSH minion
1s 265ms 4

When I follow the left menu "Configuration > Channels" 65ms

And I follow "Action Chain Channel" 417ms

And I follow "Delete Channel" 298ms

And I click on "Delete Config Channel" 483ms

Scenario:
Cleanup: remove packages and repository used in action chain for SSH minion
3s 601ms 4

When I remove package "andromeda-dummy" from this "ssh_minion" without error control 1s 200ms

And I remove package "virgo-dummy" from this "ssh_minion" without error control 775ms

And I remove package "milkyway-dummy" from this "ssh_minion" without error control 1s 191ms

And I disable repository "test_repo_rpm_pool" on this "ssh_minion" without error control 434ms

Scenario:
Cleanup: remove temporary files for testing action chains on SSH minion
1s 579ms 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 396ms

And I run "rm -f /etc/action-chain.cnf" on "ssh_minion" without error control 392ms

And I run "rm -f /tmp/action_chain_one_system_done" on "ssh_minion" without error control 396ms

@skip_if_github_validation @ssh_minion @sle_minion @scope_action_chains
Feature:Action chains on several systems at once 2m 20s 799ms 12

Scenario:
Log in as admin user
429ms 1

Given I am authorized for the "Admin" section 429ms

Scenario:
Pre-requisite: downgrade packages before action chain test on several systems
8s 331ms 8

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 758ms

And I enable repository "test_repo_rpm_pool" on this "ssh_minion" 757ms

And I remove package "andromeda-dummy" from this "ssh_minion" without error control 790ms

And I remove package "andromeda-dummy" from this "sle_minion" without error control 768ms

And I install package "andromeda-dummy-1.0" on this "sle_minion" 1s 848ms

And I install package "andromeda-dummy-1.0" on this "ssh_minion" 1s 323ms

And I refresh the metadata for "sle_minion" 1s 208ms

And I refresh the metadata for "ssh_minion" 874ms

Scenario:
Pre-requisite: refresh package list and check installed packages before action chain test on several systems
36s 86ms 6

When I refresh packages list via spacecmd on "sle_minion" 2s 720ms

And I wait until refresh package list on "sle_minion" is finished 4s 849ms

Then spacecmd should show packages "andromeda-dummy-1.0" installed on "sle_minion" 2s 399ms

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 336ms

Then spacecmd should show packages "andromeda-dummy-1.0" installed on "ssh_minion" 2s 431ms

Scenario:
Pre-requisite: wait until downgrade is finished before action chain test on several systems
1s 613ms 5

Given I am on the Systems overview page of this "sle_minion" 1s 11ms

When I follow "Software" in the content area 69ms

And I follow "List / Remove" in the content area 70ms

And I enter "andromeda-dummy" as the filtered package name 186ms

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
26s 345ms 13

When I follow the left menu "Admin > Task Schedules" 143ms

And I follow "errata-cache-default" 1s 217ms

And I follow "errata-cache-bunch" 1s 246ms

And I click on "Single Run Schedule" 420ms

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 15s 455ms

Given I am on the Systems overview page of this "ssh_minion" 1s 55ms

When I follow the left menu "Admin > Task Schedules" 139ms

And I follow "errata-cache-default" 1s 296ms

And I follow "errata-cache-bunch" 1s 297ms

And I click on "Single Run Schedule" 1s 539ms

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 1s 994ms

Scenario:
Create a custom action chain for two systems
551ms 3

When I create an action chain with label "two_systems_action_chain" via API 331ms

And I follow the left menu "Schedule > Action Chains" 137ms

Then I should see a "two_systems_action_chain" text 82ms

Scenario:
Add an action chain using system set manager for SSH minion and SLE minion
24s 24ms 22

When I follow the left menu "Systems > System List > All" 178ms

And I check the "sle_minion" client 489ms

And I check the "ssh_minion" client 62ms

And I follow the left menu "Systems > System Set Manager > Overview" 451ms

And I follow "Install" in the content area 70ms

And I follow "Fake-RPM-SUSE-Channel" in the content area 69ms

And I enter "andromeda-dummy" as the filtered package name 59ms

And I click on the filter button 403ms

And I check "andromeda-dummy" in the list 55ms

And I click on "Install Packages" 333ms

Then I should see "sle_minion" hostname 74ms

And I should see "ssh_minion" hostname 71ms

When I check radio button "schedule-by-action-chain" 10s 70ms

And I click on "Confirm" 469ms

Then I should see a "Package installations are being scheduled" text 61ms

When I follow the left menu "Systems > System Set Manager > Overview" 71ms

And I follow "remote commands" in the content area 69ms

And I enter as remote command this script in #!/bin/bash touch /tmp/action_chain_done 66ms

And I check radio button "schedule-by-action-chain" 10s 62ms

And I click on "Schedule" 646ms

Then I should see "sle_minion" hostname 91ms

And I should see "ssh_minion" hostname 94ms

Scenario:
Verify action chain for two systems
2s 626ms 8

Given I am on the Systems overview page of this "sle_minion" 973ms

When I follow "Schedule" 271ms

And I follow "Action Chains" 266ms

And I follow "two_systems_action_chain" 296ms

And I should see a "1. Install or update andromeda-dummy on 2 systems" text 71ms

And I should see a "2. Run a remote command on 2 systems" text 67ms

And I click on "Save and Schedule" 69ms

Then I should see a "Action Chain two_systems_action_chain has been scheduled for execution." text 609ms

Scenario:
Verify that the action chain from the system set manager was executed successfully
35s 999ms 4

When I wait until file "/tmp/action_chain_done" exists on "ssh_minion" 34s 469ms

And I wait until file "/tmp/action_chain_done" exists on "sle_minion" 720ms

Then "andromeda-dummy" should be installed on "ssh_minion" 404ms

And "andromeda-dummy" should be installed on "sle_minion" 405ms

Scenario:
Cleanup: remove package and repository used in action chain for several systems
3s 921ms 4

When I remove package "andromeda-dummy" from this "sle_minion" without error control 1s 433ms

And I remove package "andromeda-dummy" from this "ssh_minion" without error control 1s 441ms

And I disable repository "test_repo_rpm_pool" on this "sle_minion" without error control 442ms

And I disable repository "test_repo_rpm_pool" on this "ssh_minion" without error control 603ms

Scenario:
Cleanup: remove temporary files for testing action chains on several systems
798ms 2

When I run "rm /tmp/action_chain_done" on "sle_minion" without error control 401ms

And I run "rm /tmp/action_chain_done" on "ssh_minion" without error control 396ms

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 48s 533ms 31 1

Scenario:
Log in as admin user
467ms 1

Given I am authorized for the "Admin" section 467ms

Scenario:
Create an IP forwarding config state channel
1s 576ms 10

When I follow the left menu "Configuration > Channels" 125ms

And I follow "Create State Channel" 286ms

And I wait until I see "New Config State Channel" text 59ms

And I enter "My State Channel for Recurring Actions" as "cofName" 98ms

And I enter "statechannel-recurring" as "cofLabel" 70ms

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" 698ms

Then I wait until I see "Channel Properties" text 72ms

And I wait until I see "My State Channel for Recurring Actions" text 64ms

Scenario:
Enable IP forwarding through a custom state recurring action
35s 238ms 21

Execution time: 23:37

When I am on the "Recurring Actions" page of this "sle_minion" 1s 61ms

Then I should see a "No schedules created. Use Create to add a schedule" text 65ms

When I click on "Create" 93ms

And I wait until I see "Action Type" text 89ms

And I enter "IP forwarding custom state recurring action" as "scheduleName" 275ms

And I select "Custom state" from "actionTypeDescription" 1s 141ms

And I wait until I see "Configure states to execute" text 103ms

And I check radio button "schedule-daily" 10s 77ms

And I enter 1 minutes from now as "time-daily_time" 101ms

And I check "statechannel-recurring-cbox" 90ms

And I click on "Save Changes" 66ms

And I wait until I see "Edit State Ranks" text 93ms

And I click on "Confirm" 79ms

And I click on "Create Schedule" 68ms

Then I wait until I see "Schedule successfully created" text 435ms

And I should see a "IP forwarding custom state recurring action" text 171ms

And I should see a "Minion" text 67ms

When I follow "Events" 414ms

And I follow "History" 449ms

Then I wait at most 420 seconds until event "Apply recurring states [manager_org_1.statechannel-recurring] schedule" is completed 19s 166ms

And file "/proc/sys/net/ipv4/conf/all/forwarding" should contain "1" on "sle_minion" 1s 123ms

Scenario:
Edit the IP forwarding custom state recurring action
1m 601ms 19

Execution time: 23:38

When I am on the "Recurring Actions" page of this "sle_minion" 1s 44ms

Then I should see a "IP forwarding custom state recurring action" text 275ms

When I click the "IP forwarding custom state recurring action" item edit button 67ms

And I wait until I see "Update Schedule" text 322ms

And I enter "custom_state_schedule_name_changed" as "scheduleName" 566ms

And I enter 1 minutes from now as "time-daily_time" 97ms

And I uncheck "statechannel-recurring-cbox" 10s 95ms

And I check "Sync States-cbox" 82ms

And I click on "Save Changes" 67ms

And I wait until I see "Edit State Ranks" text 96ms

And I click on "Confirm" 78ms

And I click on "Update Schedule" 65ms

Then I wait until I see "Schedule successfully updated" text 616ms

And I should see a "custom_state_schedule_name_changed" text 167ms

And I should see a "Minion" text 74ms

When I follow "Events" 400ms

And I follow "History" 459ms

Then I wait at most 420 seconds until event "Apply recurring states [util.syncstates] scheduled" is completed 45s 959ms

And I wait until I see "SLS: util.syncstates" text 64ms

@skip_if_github_validation
Scenario:
Cleanup: Disable IP forwarding
14s 420ms 9

When I follow the left menu "Salt > Remote Commands" 126ms

Then I should see a "Remote Commands" text in the content area 25ms

When I enter command "echo 0 > /proc/sys/net/ipv4/conf/all/forwarding" 136ms

And I enter target "sle_minion" 108ms

And I click on preview 11s 811ms

And I click on run 48ms

Then I should see "sle_minion" hostname 63ms

And I wait until I see "show response" text 998ms

And file "/proc/sys/net/ipv4/conf/all/forwarding" should contain "0" on "sle_minion" 1s 101ms

Scenario:
Cleanup: Delete the minion Custom state Recurring Action
1s 771ms 6

When I am on the "Recurring Actions" page of this "sle_minion" 1s 81ms

Then I should see a "custom_state_schedule_name_changed" text 281ms

When I click the "custom_state_schedule_name_changed" item delete button 75ms

And I wait until I see "Delete Recurring Action Schedule" text 72ms

And I click on the red confirmation button 66ms

Then I wait until I see "Schedule 'custom_state_schedule_name_changed' has been deleted." text 194ms

Scenario:
Create a minion Highstate Recurring Action
48s 455ms 16

Execution time: 23:39

When I am on the "Recurring Actions" page of this "sle_minion" 983ms

Then I should see a "No schedules created. Use Create to add a schedule" text 63ms

When I click on "Create" 110ms

And I wait until I see "Schedule Name" text 89ms

And I enter "Minion Highstate Recurring Action" as "scheduleName" 245ms

And I select "Highstate" from "actionTypeDescription" 1s 126ms

And I check radio button "schedule-daily" 10s 89ms

And I enter 1 minutes from now as "time-daily_time" 94ms

And I click on the "disabled" toggler 52ms

And I click on "Create Schedule" 59ms

Then I wait until I see "Schedule successfully created" text 218ms

And I should see a "Minion Highstate Recurring Action" text 169ms

And I should see a "Minion" text 65ms

When I follow "Events" 353ms

And I follow "History" 385ms

And I wait until I see the event "Apply highstate in test-mode scheduled" completed during last minute, refreshing the page 34s 348ms

Scenario:
Edit the minion Highstate Recurring Action
14s 151ms 13

When I am on the "Recurring Actions" page of this "sle_minion" 1s 56ms

Then I should see a "Minion Highstate Recurring Action" text 266ms

When I click the "Minion Highstate Recurring Action" item edit button 67ms

And I wait until I see "Update Schedule" text 211ms

And I enter "schedule_name_minion" as "scheduleName" 359ms

And I check radio button "schedule-weekly" 10s 92ms

And I select "Wednesday" from "date_weekly" 1s 125ms

And I enter "01:35" as "time-weekly_time" 99ms

And I click on "Update Schedule" 63ms

Then I wait until I see "Schedule successfully updated" text 495ms

And I should see a "schedule_name_minion" text 171ms

And I should see a "Minion" text 66ms

And I should see a "0 35 1 ? * 4" text 73ms

Scenario:
View the minion Highstate Recurring Action details
1s 924ms 6

When I am on the "Recurring Actions" page of this "sle_minion" 1s 191ms

Then I should see a "schedule_name_minion" text 264ms

When I click the "schedule_name_minion" item details button 64ms

Then I should see a "Every Wednesday at 01:35" text 276ms

When I click on "Back" 67ms

Then I should see a "Schedules" text 60ms

Scenario:
Create a System group for testing
3s 854ms 11

When I follow the left menu "Systems > System Groups" 99ms

And I follow "Create Group" 272ms

And I enter "Recurring-Action-test-group" as "name" 72ms

And I enter "This is for testing" as "description" 63ms

And I click on "Create Group" 432ms

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 65ms

And I follow first "Join" 428ms

And I check the first row in the list 75ms

And I click on "Join Groups" 1s 204ms

Then I wait until I see "1 system groups added" text 72ms

Scenario:
Pre-requisite: subscribe system to Fake Channel
45s 429ms 12

Given I am on the Systems overview page of this "sle_minion" 992ms

When I follow "Software" in the content area 73ms

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 "Fake-Base-Channel-SUSE-like" 10s 86ms

And I wait until I do not see "Loading..." text 543ms

And I check "Fake-Child-Channel-SUSE-like" 80ms

And I click on "Next" 65ms

Then I should see a "Confirm Software Channel Change" text 62ms

When I click on "Confirm" 78ms

Then I should see a "Changing the channels has been scheduled." text 290ms

And I wait until event "Subscribe channels scheduled" is completed 33s 20ms

@skip_if_github_validation
Scenario:
Pre-requisite: downgrade milkyway-dummy to lower version
1m 29s 444ms 9

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 757ms

And I install old package "milkyway-dummy-1.0" on this "sle_minion" 2s 128ms

And I refresh the metadata for "sle_minion" 723ms

And I follow the left menu "Admin > Task Schedules" 141ms

And I follow "errata-cache-default" 1s 246ms

And I follow "errata-cache-bunch" 1s 324ms

And I click on "Single Run Schedule" 1s 526ms

Then I should see a "bunch was scheduled" text 271ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 1m 21s 324ms

Scenario:
Pre-requisite: check that there are updates available
1s 22ms 2

Given I am on the Systems overview page of this "sle_minion" 929ms

And I wait until I see "Software Updates Available" text, refreshing the page 92ms

Scenario:
Create a recurring action to apply "uptodate" state to a system group
1m 24s 597ms 24

Execution time: 23:43

When I follow the left menu "Systems > System Groups" 81ms

And I follow "Recurring-Action-test-group" 246ms

And I follow "Recurring Actions" in the content area 75ms

Then I should see a "No schedules created. Use Create to add a schedule" text 63ms

When I click on "Create" 102ms

And I wait until I see "Schedule Name" text 89ms

And I enter "Recurring action to keep Recurring-Action-test-group uptodate" as "scheduleName" 372ms

And I select "Custom state" from "actionTypeDescription" 1s 134ms

And I wait until I see "Configure states to execute" text 105ms

And I check radio button "schedule-daily" 10s 94ms

And I enter 1 minutes from now as "time-daily_time" 101ms

And I check "Update System-cbox" 94ms

And I click on "Save Changes" 69ms

And I wait until I see "Edit State Ranks" text 96ms

And I click on "Confirm" 82ms

And I click on "Create Schedule" 66ms

Then I wait until I see "Schedule successfully created" text 291ms

And I should see a "Recurring action to keep Recurring-Action-test-group uptodate" text 77ms

And I should see a "Group" text 71ms

When I am on the "Events" page of this "sle_minion" 1s 72ms

And I follow "History" 472ms

Then I wait until I see the event "Apply recurring states [uptodate] scheduled" completed during last minute, refreshing the page 1m 8s 692ms

When I am on the Systems overview page of this "sle_minion" 953ms

Then I wait at most 500 seconds until I do not see "System is up to date" text, refreshing the page 91ms

@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 85ms 14

Given I am on the Systems overview page of this "sle_minion" 976ms

When I follow "Software" in the content area 69ms

And I disable repository "test_repo_rpm_pool" on this "sle_minion" without error control 763ms

And I follow "Software Channels" in the content area 65ms

And I wait until I do not see "Loading..." text 72ms

And I check default base channel radio button of this "sle_minion" 447ms

And I wait for child channels to appear 707ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 92ms

And I check "Fake-RPM-SUSE-Channel" 75ms

And I click on "Next" 63ms

Then I should see a "Confirm Software Channel Change" text 67ms

When I click on "Confirm" 73ms

Then I should see a "Changing the channels has been scheduled." text 297ms

And I wait until event "Subscribe channels scheduled" is completed 19s 313ms

Scenario:
Edit the group Recurring Action
12s 387ms 14

When I follow the left menu "Systems > System Groups" 73ms

And I follow "Recurring-Action-test-group" 311ms

And I follow "Recurring Actions" in the content area 80ms

Then I should see a "Recurring action to keep Recurring-Action-test-group uptodate" text 184ms

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 216ms

And I enter "schedule_name_group" as "scheduleName" 620ms

And I check radio button "schedule-hourly" 10s 76ms

And I enter "35" as "minutes" 89ms

And I click on "Update Schedule" 70ms

Then I wait until I see "Schedule successfully updated" text 280ms

And I should see a "schedule_name_group" text 175ms

And I should see a "Group" text 74ms

And I should see a "0 35 * ? * *" text 70ms

Scenario:
View the group recurring actions details
1s 234ms 10

When I follow the left menu "Systems > System Groups" 74ms

And I follow "Recurring-Action-test-group" 345ms

And I follow "Recurring Actions" in the content area 68ms

Then I should see a "schedule_name" text 277ms

When I click the "schedule_name" item details button 67ms

Then I should see a "Every hour at minute 35" text 171ms

And I should see a "Recurring-Action-test-group" link 13ms

And I should see a "Update System" text 84ms

When I click on "Back" 70ms

Then I should see a "Schedules" text 61ms

Scenario:
Create a yourorg Recurring Action
1m 11s 784ms 21

Execution time: 23:45

When I follow the left menu "Home > My Organization > Recurring Actions" 189ms

Then I should see a "No schedules created. Use Create to add a schedule" text 60ms

When I click on "Create" 85ms

And I wait until I see "Schedule Name" text 94ms

And I enter "schedule_name" as "scheduleName" 143ms

And I select "Custom state" from "actionTypeDescription" 1s 133ms

And I wait until I see "Configure states to execute" text 100ms

And I check radio button "schedule-daily" 10s 85ms

And I enter 1 minutes from now as "time-daily_time" 99ms

And I click on the "disabled" toggler 54ms

And I check "Package Profile Update-cbox" 87ms

And I click on "Save Changes" 67ms

And I wait until I see "Edit State Ranks" text 92ms

And I click on "Confirm" 76ms

And I click on "Create Schedule" 64ms

Then I wait until I see "Schedule successfully created" text 297ms

And I should see a "schedule_name" text 63ms

And I should see a "Organization" text 63ms

When I am on the "Events" page of this "sle_minion" 1s 94ms

And I follow "History" 466ms

Then I wait until I see the event "Apply recurring states [packages.profileupdate] scheduled" completed during last minute, refreshing the page 57s 363ms

Scenario:
Edit the yourorg Recurring Action
13s 128ms 13

When I follow the left menu "Home > My Organization > Recurring Actions" 215ms

Then I should see a "schedule_name" text 263ms

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" 285ms

And I check radio button "schedule-monthly" 10s 83ms

And I select "7" from "date_monthly" 1s 155ms

And I enter "05:17" as "time-monthly_time" 109ms

And I click on "Update Schedule" 67ms

Then I wait until I see "Schedule successfully updated" text 281ms

And I should see a "schedule_name_edit" text 162ms

And I should see a "Organization" text 63ms

And I should see a "0 17 5 7 * ?" text 63ms

Scenario:
View the yourorg recurring actions details
760ms 7

When I follow the left menu "Home > My Organization > Recurring Actions" 87ms

Then I should see a "schedule_name" text 252ms

When I click the "schedule_name" item details button 67ms

Then I should see a "Every 7th of the month at 05:17" text 168ms

And I should see a "Package Profile Update" text 66ms

When I click on "Back" 63ms

Then I should see a "Schedules" text 55ms

Scenario:
Cleanup: Delete the yourorg Recurring Action
1s 699ms 7

When I follow the left menu "Home > My Organization > Recurring Actions" 80ms

Then I should see a "schedule_name_edit" text 258ms

When I click the "schedule_name" item delete button 78ms

And I wait until I see "Delete Recurring Action Schedule" text 66ms

And I click on the red confirmation button 69ms

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 162ms

Scenario:
Create an admin org Recurring Action
37s 520ms 23

Execution time: 23:46

When I follow the left menu "Admin > Organizations" 119ms

And I follow "SUSE Test" in the content area 72ms

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 61ms

When I click on "Create" 85ms

And I wait until I see "Schedule Name" text 89ms

And I select "Custom state" from "actionTypeDescription" 1s 127ms

And I wait until I see "Configure states to execute" text 98ms

And I enter "schedule_name" as "scheduleName" 130ms

And I check radio button "schedule-daily" 10s 72ms

And I enter 1 minutes from now as "time-daily_time" 100ms

And I click on the "disabled" toggler 56ms

And I check "Hardware Profile Update-cbox" 90ms

And I click on "Save Changes" 66ms

And I wait until I see "Edit State Ranks" text 92ms

And I click on "Confirm" 101ms

And I click on "Create Schedule" 65ms

Then I wait until I see "Schedule successfully created" text 250ms

And I should see a "schedule_name" text 73ms

And I should see a "Organization" text 70ms

When I am on the "Events" page of this "sle_minion" 1s 36ms

And I follow "History" 639ms

Then I wait until I see the event "Apply recurring states [hardware.profileupdate] scheduled" completed during last minute, refreshing the page 22s 952ms

Scenario:
Edit the admin org Recurring Action
12s 12ms 14

When I follow the left menu "Admin > Organizations" 133ms

And I follow "SUSE Test" in the content area 69ms

And I follow "Recurring Actions" in the content area 67ms

Then I should see a "schedule_name" text 192ms

When I click the "schedule_name" item edit button 67ms

And I wait until I see "Update Schedule" text 213ms

And I enter "schedule_name_org" as "scheduleName" 289ms

And I check radio button "schedule-cron" 10s 90ms

And I enter "0 0 15 3 * ?" as "cron" 199ms

And I click on "Update Schedule" 65ms

Then I wait until I see "Schedule successfully updated" text 424ms

And I should see a "schedule_name_org" text 65ms

And I should see a "Organization" text 68ms

And I should see a "0 0 15 3 * ?" text 65ms

Scenario:
View the admin org recurring actions details
817ms 8

When I follow the left menu "Admin > Organizations" 72ms

And I follow "SUSE Test" in the content area 61ms

And I follow "Recurring Actions" in the content area 66ms

Then I should see a "schedule_name" text 260ms

When I click the "schedule_name" item details button 63ms

Then I should see a "Every 3rd of the month at 15:00" text 162ms

When I click on "Back" 70ms

Then I should see a "Schedules" text 61ms

Scenario:
View all types of recurring actions in the list of all actions
975ms 8

When I follow the left menu "Schedule > Recurring Actions" 127ms

Then I should not see a "Create" text 56ms

And I should see a "schedule_name_minion" text 434ms

And I should see a "Minion" text 69ms

And I should see a "schedule_name_group" text 69ms

And I should see a "Group" text 74ms

And I should see a "schedule_name_org" text 72ms

And I should see a "Organization" text 69ms

Scenario:
View details in list of all actions
1s 334ms 6

When I follow the left menu "Schedule > Recurring Actions" 57ms

And I click the "schedule_name_minion" item details button 443ms

Then I should see a "Every Wednesday at 01:35" text 232ms

And I should not see a "Schedules" text in the content area 29ms

When I click on "Back" 59ms

Then I should see a "schedule_name_group" text 511ms

Scenario:
Cleanup: Delete the admin org Recurring Action
980ms 8

When I follow the left menu "Admin > Organizations" 108ms

And I follow "SUSE Test" in the content area 61ms

And I follow "Recurring Actions" in the content area 58ms

Then I should see a "schedule_name_org" text 250ms

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 64ms

Then I wait until I see "Schedule 'schedule_name_org' has been deleted." text 292ms

Scenario:
Cleanup: Delete the group Recurring Action
1s 742ms 9

When I follow the left menu "Systems > System Groups" 115ms

And I follow "Recurring-Action-test-group" 334ms

And I follow "Recurring Actions" in the content area 59ms

Then I should see a "schedule_name_group" text 269ms

When I click the "schedule_name_group" item delete button 64ms

And I wait until I see "Delete Recurring Action Schedule" text 69ms

And I click on the red confirmation button 59ms

Then I wait until I see "Schedule 'schedule_name_group' has been deleted." text 709ms

And I should see a "No schedules created. Use Create to add a schedule" text 60ms

Scenario:
Cleanup: Delete the minion Highstate Recurring Action
2s 822ms 7

When I am on the "Recurring Actions" page of this "sle_minion" 1s 96ms

Then I should see a "schedule_name_minion" text 265ms

When I click the "schedule_name_minion" item delete button 64ms

And I wait until I see "Delete Recurring Action Schedule" text 72ms

And I click on the red confirmation button 51ms

Then I wait until I see "Schedule 'schedule_name_minion' has been deleted." text 1s 105ms

And I should see a "No schedules created. Use Create to add a schedule" text 166ms

Scenario:
Cleanup: Delete the system group created for group recurring action tests
1s 750ms 5

When I follow the left menu "Systems > System Groups" 60ms

And I follow "Recurring-Action-test-group" 309ms

And I follow "Delete Group" 312ms

And I click on "Confirm Deletion" 1s 7ms

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 541ms 5

When I follow the left menu "Configuration > Channels" 121ms

And I follow "My State Channel for Recurring Actions" 494ms

And I follow "Delete Channel" 309ms

And I click on "Delete Config Channel" 562ms

Then I should see a "Channel 'My State Channel for Recurring Actions' has been deleted" text 53ms

@skip_if_github_validation @scc_credentials @scope_changing_software_channels @sle_minion
Feature:Assign child channel to a system 1m 25s 730ms 8 6

Scenario:
Log in as org admin user
1s 969ms 1

Given I am authorized 1s 969ms

@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 207ms 15

Warning: Radio button 'openSUSE Tumbleweed (x86_64)' is already checked

Given I am on the Systems overview page of this "sle_minion" 1s 641ms

When I follow "Software" in the content area 69ms

And I follow "Software Channels" in the content area 68ms

And I wait until I do not see "Loading..." text 65ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 161ms

Then radio button "openSUSE Tumbleweed (x86_64)" should be checked 15ms

When I wait until I do not see "Loading..." text 413ms

And I uncheck "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" by label 37ms

Then I should see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" as unchecked 15ms

When I uncheck "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" by label 79ms

Then I should see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" as unchecked 15ms

When I click on "Next" 67ms

Then I should see a "Confirm Software Channel Change" text 67ms

When I click on "Confirm" 76ms

Then I should see a "Changing the channels has been scheduled." text 413ms

@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 85ms 3

When I refresh the metadata for "sle_minion" 7s 462ms

Then channel "openSUSE Tumbleweed (x86_64)" should be enabled on "sle_minion" 817ms

And channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" should be disabled on "sle_minion" 804ms

@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
31s 982ms 14

When I follow "Software" in the content area 62ms

And I follow "Software Channels" in the content area 59ms

And I wait until I do not see "Loading..." text 65ms

Then radio button "openSUSE Tumbleweed (x86_64)" should be checked 125ms

When I wait until I do not see "Loading..." text 503ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" by label 69ms

Then I should see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" as checked 14ms

When I click on "Next" 53ms

Then I should see a "Confirm Software Channel Change" text 63ms

When I click on "Confirm" 81ms

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 29s 789ms

Then channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" should be enabled on "sle_minion" 708ms

Scenario:
Check channel change has completed for the system
3s 433ms 3

Given I am on the Systems overview page of this "sle_minion" 994ms

When I wait until event "Subscribe channels scheduled" is completed 2s 376ms

Then I should see a "The client completed this action on" text 62ms

@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
853ms 6

When I follow "Software" in the content area 70ms

And I follow "Software Channels" in the content area 64ms

And I wait until I do not see "Loading..." text 63ms

Then radio button "openSUSE Tumbleweed (x86_64)" should be checked 209ms

And I wait until I do not see "Loading..." text 426ms

And I should see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" as checked 18ms

@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
2s 879ms 3

When I refresh the metadata for "sle_minion" 1s 326ms

Then channel "openSUSE Tumbleweed (x86_64)" should be enabled on "sle_minion" 771ms

And channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" should be enabled on "sle_minion" 781ms

@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 318ms 18

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 65ms

Then radio button "openSUSE Tumbleweed (x86_64)" should be checked 153ms

And I wait until I do not see "Loading..." text 400ms

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 77ms

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 73ms

Then I should see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" as checked 14ms

When I check "Fake-RPM-SUSE-Channel" 38ms

And I click on "Next" 61ms

Then I should see a "Confirm Software Channel Change" text 65ms

When I click on "Confirm" 88ms

And I wait until I see "Changing the channels has been scheduled." text 292ms

And I follow "scheduled" in the content area 78ms

And I wait until I see "1 system successfully completed this action." text, refreshing the page 29s 994ms

Then channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" should be disabled on "sle_minion" 708ms

@scope_retracted_patches
Feature:Retracted patches 2m 8s 164ms 12

Scenario:
Log in as org admin user
1s 800ms 1

Given I am authorized 1s 800ms

Scenario:
Installed retracted package should show icon in the system packages list
37s 386ms 12

When I install package "rute-dummy=2.1-1.1" on this "sle_minion" 2s 207ms

And I refresh packages list via spacecmd on "sle_minion" 2s 749ms

And I wait until refresh package list on "sle_minion" is finished 9s 990ms

And I am on the "Software" page of this "sle_minion" 1s 125ms

And I follow "Packages" 473ms

And I follow "List / Remove" 717ms

And I enter "rute-dummy" as the filtered package name 51ms

And I click on the filter button until page does contain "rute-dummy" text 11s 10ms

Then the table row for "rute-dummy-2.1-1.1" should contain "retracted" icon 21ms

When I remove package "rute-dummy" from this "sle_minion" 1s 751ms

And I refresh packages list via spacecmd on "sle_minion" 3s 765ms

And I wait until package "rute-dummy" is removed from "sle_minion" via spacecmd 3s 523ms

Scenario:
Retracted package should not be available for installation
13s 77ms 7

When I am on the "Software" page of this "sle_minion" 1s 77ms

And I follow "Packages" 486ms

And I follow "Install" 511ms

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 809ms

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 68ms

Scenario:
Retracted package should not be available for upgrade
27s 399ms 10

When I install old package "rute-dummy=2.0-1.2" on this "sle_minion" 1s 916ms

And I refresh packages list via spacecmd on "sle_minion" 2s 806ms

And I wait until refresh package list on "sle_minion" is finished 10s 42ms

And I am on the "Software" page of this "sle_minion" 1s 189ms

And I follow "Packages" 493ms

And I follow "Upgrade" 570ms

Then I should not see a "rute-dummy-2.1-1.1" text 119ms

When I remove package "rute-dummy" from this "sle_minion" 1s 726ms

And I refresh packages list via spacecmd on "sle_minion" 2s 579ms

And I wait until package "rute-dummy" is removed from "sle_minion" via spacecmd 5s 954ms

Scenario:
Retracted patch should not affect any system
24s 438ms 13

When I install package "rute-dummy=2.0-1.2" on this "sle_minion" 1s 542ms

And I refresh packages list via spacecmd on "sle_minion" 2s 466ms

And I wait until refresh package list on "sle_minion" is finished 7s 523ms

And I follow the left menu "Software > Channel List > All" 201ms

And I follow "Show All Child Channels" 64ms

And I follow "Fake-RPM-SUSE-Channel" 731ms

And I follow "Patches" in the content area 65ms

And I follow "rute-dummy-0817" 430ms

And I follow "Affected Systems" 288ms

Then I should see a "No systems." text 54ms

When I remove package "rute-dummy" from this "sle_minion" 1s 742ms

And I refresh packages list via spacecmd on "sle_minion" 3s 127ms

And I wait until package "rute-dummy" is removed from "sle_minion" via spacecmd 6s 199ms

Scenario:
Target systems for stable packages should not be empty
2s 214ms 7

When I follow the left menu "Software > Channel List > All" 171ms

And I follow "Show All Child Channels" 46ms

And I follow "Fake-RPM-SUSE-Channel" 586ms

And I follow "Packages" in the content area 67ms

And I follow "rute-dummy-2.0-1.2.x86_64" 666ms

And I follow "Target Systems" 538ms

And I refresh page until I see "sle_minion" hostname as text 137ms

Scenario:
Target systems for retracted packages should be empty
11s 741ms 7

When I follow the left menu "Software > Channel List > All" 151ms

And I follow "Show All Child Channels" 60ms

And I follow "Fake-RPM-SUSE-Channel" 591ms

And I follow "Packages" in the content area 67ms

And I follow "rute-dummy-2.1-1.1.x86_64" 561ms

And I follow "Target Systems" 308ms

Then I should not see "sle_minion" hostname 10s

Scenario:
Retracted packages in the patch detail
5s 43ms 15

When I follow the left menu "Patches > Patch List > All" 186ms

And I enter "dummy" as the filtered synopsis 50ms

And I click on the filter button 653ms

And I follow "rute-dummy-0815" 442ms

Then I should see a "Status: Retracted" text 64ms

When I go back 607ms

And I enter "dummy" as the filtered synopsis 39ms

And I click on the filter button 669ms

And I follow "rute-dummy-0816" 438ms

Then I should see a "Status: Stable" text 67ms

When I go back 599ms

And I enter "dummy" as the filtered synopsis 36ms

And I click on the filter button 661ms

And I follow "rute-dummy-0817" 461ms

Then I should see a "Status: Retracted" text 65ms

Scenario:
Retracted packages in the patches list
828ms 6

When I follow the left menu "Patches > Patch List > All" 89ms

And I enter "dummy" as the filtered synopsis 39ms

And I click on the filter button 644ms

Then the table row for "rute-dummy-0815" should contain "retracted" icon 21ms

And the table row for "rute-dummy-0816" should not contain "retracted" icon 15ms

And the table row for "rute-dummy-0817" should contain "retracted" icon 18ms

Scenario:
Retracted patches in the channel patches list
935ms 7

When I follow the left menu "Software > Channel List > All" 180ms

And I follow "Show All Child Channels" 60ms

And I follow "Fake-RPM-SUSE-Channel" 581ms

And I follow "Patches" in the content area 70ms

Then the table row for "rute-dummy-0815" should contain "retracted" icon 16ms

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 14ms

Scenario:
Retracted packages in the channel packages list
843ms 7

When I follow the left menu "Software > Channel List > All" 70ms

And I follow "Show All Child Channels" 51ms

And I follow "Fake-RPM-SUSE-Channel" 594ms

And I follow "Packages" in the content area 71ms

Then the table row for "rute-dummy-2.0-1.1.x86_64" should contain "retracted" icon 19ms

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 21ms

Scenario:
SSM: Retracted package should not be available for installation
2s 454ms 10

When I follow the left menu "Systems > System List > All" 179ms

And I click on the clear SSM button 62ms

And I check the "sle_minion" client 436ms

And I follow the left menu "Systems > System Set Manager > Overview" 560ms

And I follow "Packages" in the content area 58ms

And I follow "Install" 484ms

And I follow "Fake-RPM-SUSE-Channel" 450ms

Then I should see a "rute-dummy-2.0-1.2" text 89ms

And I should not see a "rute-dummy-2.1-1.1" text 84ms

And I click on the clear SSM button 49ms

@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 1m 1s 812ms 11

Scenario:
Log in as admin user
1s 751ms 1

Given I am authorized for the "Admin" section 1s 751ms

Scenario:
Create a new user in a timezone different than server's timezone
1s 25ms 11

When I follow the left menu "Users > User List > Active" 184ms

And I follow "Create User" 270ms

And I enter "MalaysianUser" as "login" 67ms

And I enter "MalaysianUser" as "desiredpassword" 64ms

And I enter "MalaysianUser" as "desiredpasswordConfirm" 68ms

And I select "Mr." from "prefix" 49ms

And I enter "Test" as "firstNames" 59ms

And I enter "User" as "lastName" 56ms

And I enter "galaxy-noise@localhost" as "email" 74ms

And I select "(GMT+0800) Malaysia" from "timezone" 65ms

And I click on "Create Login" 65ms

Scenario:
Add roles for the Malaysian user
18s 619ms 9

When I follow the left menu "Users > User List > Active" 7s 15ms

And I follow "MalaysianUser" 279ms

And the "role_satellite_admin" checkbox should be disabled 10s 3ms

And I check "role_org_admin" 77ms

And I check "role_system_group_admin" 76ms

And I check "role_channel_admin" 76ms

And I check "role_activation_key_admin" 75ms

And I check "role_config_admin" 76ms

And I click on "Update" 938ms

Scenario:
Login as the new Malaysian user
1s 739ms 2

Given I am authorized as "MalaysianUser" with password "MalaysianUser" 1s 728ms

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 628ms 10

Given I am on the Systems overview page of this "sle_minion" 1s 557ms

When I follow "Remote Command" in the content area 69ms

And I enter as remote command this script in #!/bin/bash ls 50ms

And I click on "Schedule" 61ms

And I follow "Events" in the content area 608ms

And I follow "Pending" in the content area 73ms

And I wait at most 180 seconds until I do not see "Remote Command on" text, refreshing the page 16s 586ms

And I follow "History" in the content area 66ms

And I follow first "scheduled by MalaysianUser" 491ms

Then I should see a "MYT" text 62ms

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 8ms

Scenario:
Schedule a remote script in the future and see the correct timezone as a pop up
2s 550ms 6

Given I am on the Systems overview page of this "sle_minion" 1s 704ms

When I follow "Remote Command" in the content area 63ms

And I enter as remote command this script in #!/bin/bash ls 47ms

And I enter "00:00" as "date_timepicker_widget_input" 72ms

And I click on "Schedule" 53ms

Then I should see a "00:00:00 MYT" text 609ms

Scenario:
Login as the new Malaysian user if the previous scenario failed
475ms 2

Given I am authorized as "MalaysianUser" with password "MalaysianUser" 467ms

Then I should see a "MalaysianUser" link 8ms

Scenario:
Cleanup: Log in as admin user again and remove scheduled actions
3s 501ms 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 61ms

And I cancel all scheduled actions via API 1s 439ms

Scenario:
Cleanup: Remove role
11s 503ms 9

When I follow the left menu "Users > User List > Active" 212ms

And I follow "MalaysianUser" 411ms

And I uncheck "role_org_admin" 10s 105ms

And I click on "Update" 680ms

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 19ms

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
507ms 1

When I delete user "MalaysianUser" 507ms

@scope_ansible @sle_minion @new_issue @under_debugging
Feature:Operate an Ansible control node in a normal minion 12m 5s 41ms 14 3 2

Scenario:
Log in as org admin user
442ms 1

Given I am authorized for the "Admin" section 442ms

Scenario:
Pre-requisite: Deploy test playbooks and inventory file
3s 749ms 1

When I deploy testing playbooks and inventory files to "sle_minion" 3s 749ms

@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 417ms 5

Given I am on the Systems overview page of this "sle_minion" 988ms

When I follow "Properties" in the content area 77ms

And I check "ansible_control_node" 87ms

And I click on "Update Properties" 2s 165ms

Then I wait until I see "Ansible Control Node type has been applied." text 98ms

Scenario:
Apply highstate and check that Ansible is installed
57s 613ms 5

Given I am on the Systems overview page of this "sle_minion" 1s 25ms

When I follow "States" in the content area 70ms

And I click on "Apply Highstate" 60ms

And I wait until event "Apply highstate scheduled" is completed 55s 667ms

Then "ansible" should be installed on "sle_minion" 789ms

Scenario:
The Ansible tab appears in the system overview page
1s 78ms 3

Given I am on the Systems overview page of this "sle_minion" 938ms

When I follow "Ansible" in the content area 77ms

Then I should see a "Ansible Control Node Configuration" text 61ms

Scenario:
Configure some inventory and playbooks path
1s 530ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 48ms

When I follow "Ansible" in the content area 63ms

Then I should see a "Ansible Control Node Configuration" text 61ms

And I enter "/srv/playbooks/" as "new_playbook_path_input" 134ms

And I click on "new_playbook_path_save" 58ms

And I enter "/srv/playbooks/orion_dummy/hosts" as "new_inventory_path_input" 99ms

And I click on "new_inventory_path_save" 65ms

Scenario:
Display inventories
4m 29s 830ms 6 1

Given I am on the Systems overview page of this "sle_minion" 1s 89ms

When I follow "Ansible" in the content area 63ms

And I follow "Inventories" in the content area 72ms

And I wait until I see "/srv/playbooks/orion_dummy/hosts" text 248ms

And I click on "/srv/playbooks/orion_dummy/hosts" 57ms

Then I wait until I see "myself" text, refreshing the page 4m 13s 25ms 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 273ms Show Info + 
23:53:58:000 - 23:58:14: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 157ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 20ms

When I follow "Ansible" in the content area 79ms

And I follow "Playbooks" in the content area 69ms

And I wait until I see "/srv/playbooks" text 240ms

And I click on "/srv/playbooks" 63ms

Then I wait until I see "/srv/playbooks/orion_dummy/playbook_orion_dummy.yml" text 4s 619ms

And I wait until I see "/srv/playbooks/basic_tests.yml" text 63ms

Scenario:
Run a playbook using custom inventory
31s 918ms 13

Given I am on the Systems overview page of this "sle_minion" 1s 27ms

When I follow "Ansible" in the content area 62ms

And I follow "Playbooks" in the content area 58ms

And I wait until I see "/srv/playbooks" text 249ms

And I click on "/srv/playbooks" 51ms

And I wait until I see "/srv/playbooks/orion_dummy/playbook_orion_dummy.yml" text 4s 697ms

And I click on "orion_dummy/playbook_orion_dummy.yml" 60ms

And I wait until I see "Playbook Content" text 939ms

And I select "/srv/playbooks/orion_dummy/hosts" from "inventory-path-select" 1s 124ms

And I click on "Schedule" 71ms

Then I should see a "Playbook execution has been scheduled" text 374ms

And I wait until event "Execute playbook 'playbook_orion_dummy.yml' scheduled" is completed 22s 485ms

And file "/tmp/file.txt" should exist on "sle_minion" 715ms

Scenario:
Run the basic tests playbook
44s 80ms 19

Given I am on the Systems overview page of this "sle_minion" 953ms

When I follow "Ansible" in the content area 78ms

And I follow "Playbooks" in the content area 63ms

And I wait until I see "/srv/playbooks" text 152ms

And I click on "/srv/playbooks" 57ms

And I wait until I see "/srv/playbooks/basic_tests.yml" text 4s 582ms

And I click on "basic_tests.yml" 60ms

And I wait until I see "Playbook Content" text 1s 14ms

And I click on "Schedule" 65ms

And I wait until I see "Playbook execution has been scheduled" text 457ms

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 469ms

When I follow "1 system" 314ms

And I wait until I see the system name of "sle_minion" 67ms

And I follow this "sle_minion" link 452ms

Then I should see a "42" text 75ms

And I should see a "101010" text 73ms

And I should see a "(code 0)" text 69ms

Scenario:
Run the basic tests playbook while editing variables and changing their values
45s 660ms 21

Given I am on the Systems overview page of this "sle_minion" 976ms

When I follow "Ansible" in the content area 74ms

And I follow "Playbooks" in the content area 66ms

And I wait until I see "/srv/playbooks" text 250ms

And I click on "/srv/playbooks" 57ms

And I wait until I see "/srv/playbooks/basic_tests.yml" text 4s 662ms

And I click on "basic_tests.yml" 63ms

And I wait until I see "Playbook Content" text 1s 200ms

And I click on "Edit variables" 102ms

And I enter data from table with value as field name 844ms
(21 + 21) * 100 p1
p2
p3
p4
p5

And I click on "Save" 97ms

And I click on "Schedule" 70ms

And I wait until I see "Playbook execution has been scheduled" text 626ms

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 470ms

When I follow "1 system" 296ms

And I wait until I see the system name of "sle_minion" 66ms

And I follow this "sle_minion" link 512ms

Then I should see a "4200" text 76ms

And I should see a "(code 0)" text 70ms

Scenario:
Run the basic tests playbook while editing the EMPTY variables and changing their values
45s 686ms 22

Given I am on the Systems overview page of this "sle_minion" 1s 176ms

When I follow "Ansible" in the content area 90ms

And I follow "Playbooks" in the content area 68ms

And I wait until I see "/srv/playbooks" text 244ms

And I click on "/srv/playbooks" 60ms

And I wait until I see "/srv/playbooks/basic_tests.yml" text 4s 639ms

And I click on "basic_tests.yml" 63ms

And I wait until I see "Playbook Content" text 970ms

And I click on "Edit variables" 87ms

And I enter data from table with value as field name 1s 62ms
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" 97ms

And I click on "Schedule" 72ms

And I wait until I see "Playbook execution has been scheduled" text 457ms

And I wait for "2" seconds 2s

And I follow "scheduled" in the content area 105ms

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 511ms

When I follow "1 system" 299ms

And I wait until I see the system name of "sle_minion" 68ms

And I follow this "sle_minion" link 387ms

Then I should see a "42000" text 78ms

And I should see a "4242" text 75ms

And I should see a "(code 0)" text 68ms

Scenario:
Run the basic tests playbook while editing the NULL variable and changing its value
33s 658ms 10 11 1

Given I am on the Systems overview page of this "sle_minion" 985ms

When I follow "Ansible" in the content area 76ms

And I follow "Playbooks" in the content area 68ms

And I wait until I see "/srv/playbooks" text 253ms

And I click on "/srv/playbooks" 59ms

And I wait until I see "/srv/playbooks/basic_tests.yml" text 4s 673ms

And I click on "basic_tests.yml" 62ms

And I wait until I see "Playbook Content" text 993ms

And I click on "Edit variables" 100ms

And I enter data from table with value as field name 10s 940ms
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 444ms Show Info + 
00:01:28:000 - 00:01:48: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 327ms 20 2 1

Given I am on the Systems overview page of this "sle_minion" 936ms

When I follow "Ansible" in the content area 76ms

And I follow "Playbooks" in the content area 63ms

And I wait until I see "/srv/playbooks" text 245ms

And I click on "/srv/playbooks" 56ms

And I wait until I see "/srv/playbooks/basic_tests.yml" text 4s 558ms

And I click on "basic_tests.yml" 60ms

And I wait until I see "Playbook Content" text 986ms

And I click on "Edit variables" 89ms

And I click on "Edit YAML" 65ms

And I click on "Save" 96ms

And I click on "Schedule" 69ms

And I wait until I see "Playbook execution has been scheduled" text 304ms

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 43s 466ms

When I follow "1 system" 299ms

And I wait until I see the system name of "sle_minion" 74ms

And I follow this "sle_minion" link 369ms

Then I should see a "42" text 10s 20ms 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 414ms Show Info + 
00:02:03:000 - 00:03:08:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010020&aid=290
Screenshot +

Scenario:
Run the basic tests playbook on SAVE operation of YAML editor with safe values
45s 383ms 26

Given I am on the Systems overview page of this "sle_minion" 999ms

When I follow "Ansible" in the content area 80ms

And I follow "Playbooks" in the content area 66ms

And I wait until I see "/srv/playbooks" text 246ms

And I click on "/srv/playbooks" 57ms

And I wait until I see "/srv/playbooks/basic_tests.yml" text 4s 577ms

And I click on "basic_tests.yml" 62ms

And I wait until I see "Playbook Content" text 1s 5ms

And I click on "Edit variables" 88ms

And I enter data from table with value as field name 840ms
abc p1
def p2
ghi p3
jkl p4
16 * 16 * 16 p5

And I click on "Edit YAML" 70ms

And I click on "Save" 96ms

And I click on "Schedule" 74ms

And I wait until I see "Playbook execution has been scheduled" text 324ms

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 504ms

When I follow "1 system" 283ms

And I wait until I see the system name of "sle_minion" 65ms

And I follow this "sle_minion" link 441ms

Then I should see a "abc" text 82ms

And I should see a "def" text 67ms

And I should see a "ghi" text 67ms

And I should see a "jkl" text 66ms

And I should see a "4096" text 68ms

And I should see a "(code 0)" text 73ms

Scenario:
Cleanup: Disable Ansible and remove test playbooks and inventory file
15s 262ms 7

Given I am on the Systems overview page of this "sle_minion" 990ms

When I follow "Properties" in the content area 76ms

And I uncheck "ansible_control_node" 10s 69ms

And I click on "Update Properties" 1s 746ms

Then I should see a "System properties changed" text 84ms

And I remove package "orion-dummy" from this "sle_minion" without error control 1s 899ms

And I remove "/tmp/file.txt" from "sle_minion" 395ms

@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 241ms 4

Given I am on the Systems overview page of this "sle_minion" 977ms

When I follow "States" in the content area 69ms

And I click on "Apply Highstate" 60ms

And I wait until event "Apply highstate scheduled" is completed 39s 134ms

@sle_minion @proxy
Feature:Move a minion from a proxy to direct connection 10m 58s 466ms 13

Scenario:
Log in as org admin user
1s 700ms 1

Given I am authorized 1s 700ms

Scenario:
Delete minion system profile before bootstrap
4m 6s 974ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 661ms

When I follow "Delete System" 472ms

Then I should see a "Confirm System Profile Deletion" text 65ms

When I click on "Delete Profile" 79ms

And I wait until I see "has been deleted" text 4m 3s 570ms

And I wait until Salt client is inactive on "sle_minion" 747ms

Then "sle_minion" should not be registered 378ms

Scenario:
Bootstrap a minion
2m 3s 706ms 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 71ms

When I enter the hostname of "sle_minion" as "hostname" 154ms

And I enter "22" as "port" 55ms

And I enter "root" as "user" 57ms

And I enter "linux" as "password" 63ms

And I select "1-SUSE-KEY-x86_64" from "activationKeys" 73ms

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 29s 589ms

And I wait until onboarding is completed for "sle_minion" 1m 33s 429ms

Scenario:
Check the new bootstrapped minion in System Overview page
2s 355ms 3

It took 2 seconds to contact the minion

When I follow the left menu "Salt > Keys" 122ms

Then I should see a "accepted" text 334ms

And the Salt master can reach "sle_minion" 1s 898ms

Scenario:
Check initial connection from minion to proxy
1s 306ms 4

Given I am on the Systems overview page of this "sle_minion" 1s 101ms

When I follow "Details" in the content area 71ms

And I follow "Connection" in the content area 66ms

Then I should see "proxy" short hostname 67ms

Scenario:
Check initial registration on proxy of minion
1s 349ms 4

Given I am on the Systems overview page of this "proxy" 1s 126ms

When I follow "Details" in the content area 63ms

And I follow "Proxy" in the content area 66ms

Then I should see "sle_minion" hostname 92ms

Scenario:
Change from proxy to direct connection
37s 54ms 11

Given I am on the Systems overview page of this "sle_minion" 1s 175ms

When I follow "Details" in the content area 65ms

And I follow "Connection" in the content area 58ms

And I follow "Change" in the content area 64ms

And I select "None" from "proxies" 68ms

And I click on "Change Proxy" 58ms

And I wait until I see "scheduled" text 353ms

And I follow "Events" 415ms

And I follow "History" 422ms

And I wait until I see the event "Apply states [bootstrap.set_proxy] scheduled" completed during last minute, refreshing the page 11s 452ms

And I wait until I see the event "Apply states [channels] scheduled" completed during last minute, refreshing the page 22s 920ms

Scenario:
Check direct connection
1s 187ms 4

Given I am on the Systems overview page of this "sle_minion" 999ms

When I follow "Details" in the content area 65ms

And I follow "Connection" in the content area 62ms

Then I should see a "This system connects directly and not through a Proxy" text 60ms

Scenario:
Change connection back to a proxy via SSM
2m 1s 819ms 10

Given I wait for "120" seconds 2m

When I follow the left menu "Systems > System List > All" 138ms

And I click on the clear SSM button 67ms

And I check the "sle_minion" client 446ms

And I should see "1" systems selected for SSM 122ms

And I follow the left menu "Systems > System Set Manager > Overview" 547ms

And I follow "proxy server" in the content area 74ms

And I select the hostname of "proxy" from "proxies" if present 72ms

And I click on "Change Proxy" 60ms

And I wait until I see "scheduled" text 288ms

Scenario:
Check events on the minion
36s 385ms 5

Given I am on the Systems overview page of this "sle_minion" 1s 128ms

And I follow "Events" 460ms

And I follow "History" 418ms

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 367ms

Scenario:
Check registration on proxy of minion
1s 294ms 4

Given I am on the Systems overview page of this "proxy" 1s 38ms

When I follow "Details" in the content area 68ms

And I follow "Proxy" in the content area 67ms

Then I should see "sle_minion" hostname 119ms

Scenario:
Check connection from minion to proxy
1s 318ms 4

Given I am on the Systems overview page of this "sle_minion" 1s 121ms

When I follow "Details" in the content area 63ms

And I follow "Connection" in the content area 66ms

Then I should see "proxy" short hostname 67ms

Scenario:
Check events history for failures on the minion
1m 22s 14ms 2

Given I am on the Systems overview page of this "sle_minion" 1s 90ms

Then I check for failed events on history event page 1m 20s 924ms

@ssh_minion @scope_salt_ssh @proxy
Feature:Move a SSH minion from a proxy to direct connection 6m 47s 289ms 11

Scenario:
Log in as org admin user
2s 131ms 1

Given I am authorized 2s 131ms

Scenario:
Delete minion system profile before bootstrap
17s 641ms 6

Given I am on the Systems overview page of this "ssh_minion" 1s 870ms

When I follow "Delete System" 477ms

Then I should see a "Confirm System Profile Deletion" text 61ms

When I click on "Delete Profile" 63ms

And I wait until I see "has been deleted" text 14s 700ms

Then "ssh_minion" should not be registered 468ms

Scenario:
Bootstrap a minion
2m 4s 911ms 11

The hostname of ssh_minion is uyuni-master-suse-sshminion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 75ms

Then I should see a "Bootstrap Minions" text 83ms

When I check "manageWithSSH" 89ms

And I enter the hostname of "ssh_minion" as "hostname" 145ms

And I enter "root" as "user" 58ms

And I enter "linux" as "password" 64ms

And I select "1-SUSE-SSH-KEY-x86_64" from "activationKeys" 73ms

And I select the hostname of "proxy" from "proxies" if present 64ms

And I click on "Bootstrap" 63ms

And I wait at most 480 seconds until I see "Bootstrap process initiated." text 40s 744ms

And I wait until onboarding is completed for "ssh_minion" 1m 23s 447ms

Scenario:
Check initial connection from minion to proxy
1s 322ms 4

Given I am on the Systems overview page of this "ssh_minion" 1s 111ms

When I follow "Details" in the content area 79ms

And I follow "Connection" in the content area 68ms

Then I should see "proxy" short hostname 62ms

Scenario:
Check initial registration on proxy of minion
1s 284ms 4

Given I am on the Systems overview page of this "proxy" 1s 45ms

When I follow "Details" in the content area 61ms

And I follow "Proxy" in the content area 69ms

Then I should see "ssh_minion" hostname 106ms

Scenario:
Change from proxy to direct connection
36s 953ms 10

Given I am on the Systems overview page of this "ssh_minion" 1s 88ms

When I follow "Details" in the content area 62ms

And I follow "Connection" in the content area 63ms

And I follow "Change" in the content area 64ms

And I select "None" from "proxies" 73ms

And I click on "Change Proxy" 59ms

And I wait until I see "scheduled" text 367ms

And I follow "Events" 390ms

And I follow "History" 413ms

And I wait until I see the event "Apply states [channels] scheduled" completed during last minute, refreshing the page 34s 370ms

Scenario:
Check direct connection
1s 289ms 4

Given I am on the Systems overview page of this "ssh_minion" 1s 103ms

When I follow "Details" in the content area 60ms

And I follow "Connection" in the content area 66ms

Then I should see a "This system connects directly and not through a Proxy" text 59ms

Scenario:
Change connection to a proxy
2m 37s 7ms 11

Given I wait for "120" seconds 2m

Given I am on the Systems overview page of this "ssh_minion" 1s 30ms

When I follow "Details" in the content area 63ms

And I follow "Connection" in the content area 59ms

And I follow "Change" in the content area 66ms

And I select the hostname of "proxy" from "proxies" if present 72ms

And I click on "Change Proxy" 79ms

And I wait until I see "scheduled" text 346ms

And I follow "Events" 390ms

And I follow "History" 509ms

And I wait until I see the event "Apply states [channels] scheduled" completed during last minute, refreshing the page 34s 388ms

Scenario:
Check registration on proxy of minion
1s 290ms 4

Given I am on the Systems overview page of this "proxy" 1s 60ms

When I follow "Details" in the content area 63ms

And I follow "Proxy" in the content area 72ms

Then I should see "ssh_minion" hostname 93ms

Scenario:
Check connection from minion to proxy
1s 283ms 4

Given I am on the Systems overview page of this "ssh_minion" 1s 97ms

When I follow "Details" in the content area 62ms

And I follow "Connection" in the content area 59ms

Then I should see "proxy" short hostname 63ms

Scenario:
Check events history for failures on the minion
1m 2s 173ms 2

Given I am on the Systems overview page of this "ssh_minion" 1s 135ms

Then I check for failed events on history event page 1m 1s 38ms

Feature:Sanity check that all logfiles exist 6s 300ms 1

In order to be secure
As an authorized user
I want to watch different logfiles

Scenario:
All logfiles should be available
6s 300ms 9

Then I wait until file "/var/log/rhn/rhn_web_ui.log" exists on server 995ms

And I wait until file "/var/log/rhn/rhn_web_api.log" exists on server 656ms

And I wait until file "/var/log/rhn/rhn_web_frontend.log" exists on server 683ms

And I wait until file "/var/log/rhn/rhn_taskomatic_daemon.log" exists on server 651ms

And I wait until file "/var/log/rhn/search/rhn_search_daemon.log" exists on server 689ms

And I wait until file "/var/log/rhn/search/rhn_search.log" exists on server 662ms

And I wait until file "/var/log/rhn/reposync.log" exists on server 663ms

And I wait until file "/var/log/salt/master" exists on server 653ms

And I wait until file "/var/log/salt/api" exists on server 642ms

@scope_cobbler
Feature:Run Cobbler Sync via WebUI 25s 163ms 6 1

Scenario:
Login as admin
2s 167ms 1

Given I am authorized for the "Admin" section 2s 167ms

Scenario:
Start Cobbler monitoring
7s 242ms 2

When I start local monitoring of Cobbler 6s 583ms

And I backup Cobbler settings file 659ms

@uyuni
Scenario:
Check that the Cobbler Settings Page exists
723ms 7

When I follow the left menu "Admin > Manager Configuration > Cobbler" 433ms

Then I should see a "Uyuni Configuration - Cobbler. " text 66ms

And I should see a "Setup your Uyuni Cobbler settings below. " text 62ms

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 60ms

And I should see a "For more information refer to the 'cobbler' man page. " text 62ms

And I should see a "Run Cobbler Sync" text in the content area 21ms

And I should see a "Update" button 16ms

@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
499ms 3

When I follow the left menu "Admin > Manager Configuration > Cobbler" 67ms

And I click on "Update" 60ms

Then I should see a "Cobbler Sync action was successfully executed. Look at /var/log/cobbler/*.log for more information" text 370ms

Scenario:
Run Cobbler Sync via button and verify task timestamp in Last Execution Times Page
10s 779ms 4

When I follow the left menu "Admin > Manager Configuration > Cobbler" 77ms

And I click on "Update" 326ms

And I follow the left menu "Admin > Task Engine Status > Last Execution Times" 361ms

Then I should see the correct timestamp for task "Cobbler Sync:" 10s 12ms

@skip_if_github_validation
Scenario:
Check for errors in Cobbler monitoring
3s 751ms 1

Then the local logs for Cobbler should not contain errors 3s 751ms

@skip_if_github_validation @scope_cobbler
Feature:Cobbler and distribution autoinstallation 1m 22s 569ms 26

Scenario:
Start Cobbler monitoring
6s 909ms 2

When I start local monitoring of Cobbler 6s 252ms

And I backup Cobbler settings file 656ms

Scenario:
Log in as testing user
2s 480ms 2

Given I am authorized as "testing" with password "testing" 1s 742ms

And I am logged in via the Cobbler API as user "testing" with password "testing" 738ms

Scenario:
Copy cobbler profiles on the server
5s 999ms 1

When I copy autoinstall mocked files on server 5s 999ms

Scenario:
Ask cobbler to create a distribution via API
703ms 2

Given cobblerd is running 2ms

When I create "testdistro" kickstart tree via the API 700ms

Scenario:
Create dummy profile
1s 479ms 2

Given cobblerd is running 2ms

When I create a "testprofile" profile via the API using import file for "testdistro" distribution 1s 476ms

Scenario:
Check cobbler created distro and profile
352ms 3

When I follow the left menu "Systems > Autoinstallation > Profiles" 207ms

Then I should see a "testprofile" text 82ms

And I should see a "testdistro" text 63ms

Scenario:
Create SUSE distribution with installer updates
2s 292ms 12

When I follow the left menu "Systems > Autoinstallation > Distributions" 78ms

And I follow "Create Distribution" 318ms

And I enter "SLE-15-FAKE" as "label" 63ms

And I enter "/var/autoinstall/SLES15-SP7-x86_64/DVD1/" as "basepath" 91ms

And I select "SLE-Product-SLES15-SP7-Pool for x86_64" from "channelid" 364ms

And I select "SUSE Linux Enterprise 15" from "installtype" 60ms

And I click on "Create Autoinstallable Distribution" 803ms

And I wait until I see "Autoinstallable Distribution Created" text 73ms

Then I should see a "Autoinstallable Distributions" text 70ms

And I should see a "SLE-15-FAKE" link 12ms

When I follow "SLE-15-FAKE" 332ms

Then I should see "self_update=http://" in field identified by "kernelopts" 23ms

Scenario:
Create a distribution via the UI
1s 377ms 8

When I follow the left menu "Systems > Autoinstallation > Distributions" 96ms

And I follow "Create Distribution" 303ms

When I enter "fedora_kickstart_distro" as "label" 68ms

And I enter "/var/autoinstall/Fedora_12_i386/" as "basepath" 77ms

And I select "Fedora" from "installtype" 56ms

And I click on "Create Autoinstallable Distribution" 690ms

Then I should see a "Autoinstallable Distributions" text 72ms

And I should see a "fedora_kickstart_distro" link 12ms

Scenario:
Create a distribution via the API, without kernel options
692ms 3

When I create "fedora_kickstart_distro_api" kickstart tree via the API 602ms

When I follow the left menu "Systems > Autoinstallation > Distributions" 77ms

Then I should see a "fedora_kickstart_distro_api" link 12ms

Scenario:
Create a distribution via the API, with kernel options
1s 268ms 3

When I create a kickstart tree with kernel options via the API 1s 186ms

When I follow the left menu "Systems > Autoinstallation > Distributions" 68ms

Then I should see a "fedora_kickstart_distro_kernel_api" link 12ms

Scenario:
Update a distribution via the API
1s 139ms 6

When I update a kickstart tree via the API 614ms

When I follow the left menu "Systems > Autoinstallation > Distributions" 70ms

And I follow "fedora_kickstart_distro_api" 329ms

Then option "Generic RPM" is selected as "installtype" 78ms

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" 26ms

Scenario:
Create a profile via the UI
3s 369ms 10

When I follow the left menu "Systems > Autoinstallation > Profiles" 72ms

And I follow "Create Kickstart Profile" 382ms

When I enter "fedora_kickstart_profile" as "kickstartLabel" 70ms

And I click on "Next" 341ms

And I click on "Next" 393ms

And I enter "linux" as "rootPassword" 51ms

And I enter "linux" as "rootPasswordConfirm" 56ms

And I click on "Finish" 59ms

Then I should see a "Autoinstallation: fedora_kickstart_profile" text 1s 927ms

And I should see a "Autoinstallation Details" link 12ms

Scenario:
Upload a profile via the UI
2s 386ms 8

When I follow the left menu "Systems > Autoinstallation > Profiles" 71ms

And I follow "Upload Kickstart/AutoYaST File" 340ms

When I enter "fedora_kickstart_profile_upload" as "kickstartLabel" 77ms

And I select "fedora_kickstart_distro" from "kstreeId" 47ms

And I attach the file "/example.ks" to "fileUpload" 37ms

And I click on "Create" 1s 622ms

Then I should see a "Autoinstallation: fedora_kickstart_profile_upload" text 96ms

And I should see a "Autoinstallation Details" text 93ms

Scenario:
Add an unprovisioned range to the created profile
2s 357ms 13

When I follow the left menu "Systems > Autoinstallation > Profiles" 75ms

And I follow "fedora_kickstart_profile" 661ms

And I follow "Unprovisioned Autoinstallation" 323ms

And I enter "10" as "octet1a" 50ms

And I enter "10" as "octet1b" 54ms

And I enter "0" as "octet1c" 49ms

And I enter "100" as "octet1d" 53ms

And I enter "10" as "octet2a" 49ms

And I enter "10" as "octet2b" 52ms

And I enter "0" as "octet2c" 49ms

And I enter "200" as "octet2d" 53ms

And I click on "Add IP Range" 63ms

Then I should see a "Successfully added IP Range" text 821ms

Scenario:
Add a variable to the uploaded profile
1s 995ms 7

When I follow the left menu "Systems > Autoinstallation > Profiles" 74ms

And I follow "fedora_kickstart_profile_upload" 486ms

And I follow "Variables" 359ms

And I enter "my_var=A_Test_String" as "variables" 71ms

And I click on "Update Variables" 62ms

And I follow "Autoinstallation File" 857ms

Then I should see a "A_Test_String" text 81ms

Scenario:
Add a kernel option to the created profile
2s 28ms 5

When I follow the left menu "Systems > Autoinstallation > Profiles" 69ms

And I follow "fedora_kickstart_profile" 625ms

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 191ms

Scenario:
Add a kernel option to the uploaded profile
5s 277ms 5

When I follow the left menu "Systems > Autoinstallation > Profiles" 73ms

And I follow "fedora_kickstart_profile_upload" 592ms

And I enter "kernel_option2=a_value2" as "kernel_options" 68ms

And I click on "Update" 1s 134ms

And I wait until file "/srv/tftpboot/pxelinux.cfg/default" contains "kernel_option2=a_value2" on server 3s 408ms

Scenario:
Check default snippets
1s 113ms 6

When I follow the left menu "Systems > Autoinstallation > Autoinstallation Snippets" 80ms

And I follow "Default Snippets" 310ms

And I enter "spacewalk/sles_no_signature_checks" as the filtered snippet name 94ms

And I click on the filter button 302ms

And I follow "spacewalk/sles_no_signature_checks" 309ms

Then I should see "<signature-handling>" in the textarea 15ms

Scenario:
Create a snippet
974ms 6

When I follow the left menu "Systems > Autoinstallation > Autoinstallation Snippets" 69ms

And I follow "Create Snippet" 292ms

And I enter "created_test_snippet" as "name" 68ms

And I enter "<test_element>a text string</test_element>" in the editor 4ms

And I click on "Create Snippet" 463ms

Then I should see a "created_test_snippet created successfully." text 76ms

Scenario:
Delete a snippet
1s 127ms 5

When I follow the left menu "Systems > Autoinstallation > Autoinstallation Snippets" 73ms

And I follow "created_test_snippet" 321ms

And I follow "Delete Snippet" 251ms

And I click on "Delete Snippet" 420ms

Then I should see a "created_test_snippet deleted successfully." text 60ms

Scenario:
Test for PXE environment files
4s 747ms 8

Given cobblerd is running 18ms

When I wait until file "/srv/tftpboot/pxelinux.cfg/default" exists on server 718ms

And I wait until file "/srv/tftpboot/pxelinux.cfg/default" contains "inst.ks=.*fedora_kickstart_profile:1" on server 672ms

And I wait until file "/srv/tftpboot/pxelinux.cfg/default" contains "inst.ks=.*fedora_kickstart_profile_upload:1" on server 677ms

And I wait until file "/srv/tftpboot/images/fedora_kickstart_distro:1:SUSETest/initrd.img" exists on server 688ms

And I wait until file "/srv/tftpboot/images/fedora_kickstart_distro:1:SUSETest/vmlinuz" exists on server 654ms

And I wait until file "/srv/tftpboot/menu.c32" exists on server 641ms

And I wait until file "/srv/tftpboot/pxelinux.0" exists on server 675ms

Scenario:
Trigger the creation of a cobbler system record
3s 694ms 7

When I clear the caches on the server 1s 29ms

And I am on the Systems overview page of this "sle_minion" 1s 44ms

And I follow "Provisioning" 647ms

And I click on profile "testprofile" 56ms

And I click on "Create PXE installation configuration" 84ms

Then I should see a "System record created" text 84ms

And I wait until file "/srv/tftpboot/pxelinux.cfg/01-*" contains "autoyast=" on server 747ms

Scenario:
Create a cobbler system record via API
5s 230ms 5

When I create a system record 530ms

And I wait until file "/srv/tftpboot/pxelinux.cfg/01-00-22-22-77-ee-cc" contains "inst.ks=.*testserver:1" on server 647ms

Then the cobbler report should contain "testserver.example.com" for cobbler system name "testserver:1" 1s 343ms

And the cobbler report should contain "1.1.1.1" for cobbler system name "testserver:1" 1s 357ms

And the cobbler report should contain "00:22:22:77:ee:cc" for cobbler system name "testserver:1" 1s 351ms

Scenario:
Cleanup: delete test profiles and distributions using API
14s 719ms 12

When I wait for "10" seconds 10s

When I delete profile and distribution using the API for "testdistro" kickstart tree 506ms

When I delete profile and distribution using the API for "fedora_kickstart_distro" kickstart tree 534ms

When I delete profile and distribution using the API for "fedora_kickstart_distro_api" kickstart tree 392ms

When I delete profile and distribution using the API for "fedora_kickstart_distro_kernel_api" kickstart tree 1s 45ms

When I delete profile and distribution using the API for "SLE-15-FAKE" kickstart tree 1s 800ms

When I follow the left menu "Systems > Autoinstallation > Distributions" 129ms

And I should not see a "testdistro" text 69ms

And I should not see a "fedora_kickstart_distro" text 57ms

And I should not see a "fedora_kickstart_distro_api" text 59ms

And I should not see a "fedora_kickstart_distro_kernel_api" text 56ms

And I should not see a "SLE-15-FAKE" text 67ms

@flaky
Scenario:
Check for errors in Cobbler monitoring
8s 848ms 2

When I wait for "5" seconds 5s

Then the local logs for Cobbler should not contain errors 3s 848ms

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 21s 440ms 19

Builds several ISOs with Cobbler and checks the configuration files and ISOs afterwards.

Scenario:
Start Cobbler monitoring
7s 13ms 2

When I start local monitoring of Cobbler 6s 339ms

And I backup Cobbler settings file 674ms

Scenario:
Log in as testing user in the Cobbler buildiso context
1s 223ms 2

Given I am authorized as "testing" with password "testing" 469ms

And I am logged in via the Cobbler API as user "testing" with password "testing" 753ms

Scenario:
Copy cobbler profiles on the server in the Cobbler buildiso context
6s 201ms 1

When I copy autoinstall mocked files on server 6s 201ms

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
257ms 4

Given distro "buildisodistro" exists 4ms

When I create profile "orchid" for distro "buildisodistro" 75ms

And I create profile "flame" for distro "buildisodistro" 76ms

And I create profile "pearl" for distro "buildisodistro" 100ms

Scenario:
Check cobbler created a distro and profiles in the Cobbler buildiso context
481ms 5

When I follow the left menu "Systems > Autoinstallation > Profiles" 199ms

Then I should see a "buildisodistro" text 72ms

And I should see a "orchid" text 68ms

And I should see a "flame" text 72ms

And I should see a "pearl" text 68ms

Scenario:
Create dummy system in the Cobbler buildiso context
1s 468ms 3

Given profile "orchid" exists 9ms

When I create system "testsystem" for profile "orchid" 51ms

And I add the Cobbler parameter "name-servers" with value "9.9.9.9" to item "system" with name "testsystem" 1s 406ms

Scenario:
Prepare the Cobbler buildiso context
3s 742ms 1

When I prepare Cobbler for the buildiso command 3s 742ms

Scenario:
Run Cobbler buildiso with all profiles and check isolinux config file in the Cobbler buildiso context
12s 225ms 4

When I run Cobbler buildiso for distro "buildisodistro" and all profiles 8s 850ms

And I check Cobbler buildiso ISO "profile_all" with xorriso 2s 29ms

And I check the Cobbler parameter "nameserver" with value "9.9.9.9" in the isolinux.cfg 666ms

And I cleanup xorriso temp files 679ms

Scenario:
Run Cobbler buildiso with selected profile in the Cobbler buildiso context
5s 268ms 3

When I run Cobbler buildiso for distro "buildisodistro" and profile "orchid" 2s 504ms

And I check Cobbler buildiso ISO "orchid" with xorriso 2s 54ms

And I cleanup xorriso temp files 709ms

Scenario:
Run Cobbler buildiso with selected profile and without dns entries in the Cobbler buildiso context
5s 894ms 3

When I run Cobbler buildiso for distro "buildisodistro" and profile "orchid" without dns entries 3s 189ms

And I check Cobbler buildiso ISO "orchid" with xorriso 2s 38ms

And I cleanup xorriso temp files 666ms

Scenario:
Run Cobbler buildiso airgapped with all profiles in the Cobbler buildiso context
15s 392ms 3

When I run Cobbler buildiso "airgapped" for distro "buildisodistro" 12s 639ms

And I check Cobbler buildiso ISO "airgapped" with xorriso 2s 64ms

And I cleanup xorriso temp files 688ms

Scenario:
Run Cobbler buildiso standalone with all profiles in the Cobbler buildiso context
15s 302ms 3

When I run Cobbler buildiso "standalone" for distro "buildisodistro" 12s 614ms

And I check Cobbler buildiso ISO "standalone" with xorriso 2s 12ms

And I cleanup xorriso temp files 675ms

Scenario:
Cleanup: delete test system in the Cobbler buildiso context
506ms 2

Given I am authorized as "testing" with password "testing" 482ms

When I remove system "testsystem" 24ms

Scenario:
Cleanup: delete test profile in the Cobbler buildiso context
1s 470ms 8

Given I am authorized as "testing" with password "testing" 918ms

And I remove profile "orchid" 113ms

And I remove profile "flame" 63ms

And I remove profile "pearl" 22ms

When I follow the left menu "Systems > Autoinstallation > Profiles" 172ms

Then I should not see a "orchid" text 61ms

And I should not see a "flame" text 58ms

And I should not see a "flame" text 60ms

Scenario:
Cleanup: delete test distro in the Cobbler buildiso context
707ms 4

Given I am authorized as "testing" with password "testing" 461ms

And I remove distro "buildisodistro" 16ms

And I follow the left menu "Systems > Autoinstallation > Profiles" 166ms

Then I should not see a "buildisodistro" text 63ms

Scenario:
Cleanup: Remove buildiso tmpdir and built ISO file in the Cobbler buildiso context
676ms 1

When I cleanup after Cobbler buildiso 676ms

@flaky
Scenario:
Check for errors in Cobbler monitoring
3s 545ms 1

Then the local logs for Cobbler should not contain errors 3s 545ms

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 7s 509ms 12

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 2ms

Scenario:
Copy cobbler profiles on the server
7s 172ms 2

When I copy autoinstall mocked files on server 6s 495ms

And I backup Cobbler settings file 676ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 2ms

Scenario:
Log in as testing user
10s 770ms 1

Given I am authorized as "testing" with password "testing" 10s 770ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 6ms

Scenario:
Start Cobbler monitoring
6s 605ms 1

When I start local monitoring of Cobbler 6s 605ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 3ms

Scenario:
Create a Cobbler distribution via the UI
970ms 10

When I follow the left menu "Systems > Autoinstallation > Distributions" 177ms

And I follow "Create Distribution" 285ms

When I enter "isedistro_ui" as "label" 63ms

And I enter "/var/autoinstall/Fedora_12_i386/" as "basepath" 79ms

And I select "Fedora" from "installtype" 69ms

And I click on "Create Autoinstallable Distribution" 59ms

Then I should see a "Autoinstallable Distributions" text 73ms

And I should see a "isedistro_ui" link 12ms

When I follow the left menu "Systems > Autoinstallation > Distributions" 78ms

Then I should see a "isedistro_ui" text 71ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 3ms

Scenario:
Create a Cobbler profile via the UI
3s 368ms 12

When I follow the left menu "Systems > Autoinstallation > Profiles" 71ms

And I follow "Create Kickstart Profile" 350ms

When I enter "iseprofile_ui" as "kickstartLabel" 59ms

And I click on "Next" 345ms

And I click on "Next" 379ms

And I enter "linux" as "rootPassword" 52ms

And I enter "linux" as "rootPasswordConfirm" 56ms

And I click on "Finish" 1s 827ms

Then I should see a "Autoinstallation: iseprofile_ui" text 75ms

And I should see a "Autoinstallation Details" link 12ms

When I follow the left menu "Systems > Autoinstallation > Profiles" 70ms

Then I should see a "iseprofile_ui" text 66ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 6ms

Scenario:
Change profile variables using the UI
11s 938ms 7

When I follow the left menu "Systems > Autoinstallation > Profiles" 66ms

And I follow "iseprofile_ui" 523ms

And I follow "Variables" 308ms

And I enter "ise_ui_test=ISE_UI_TEST" as "variables" 76ms

And I click on "Update Variables" 408ms

And I refresh the page 10s 492ms

Then I should see a "ISE_UI_TEST" text 62ms

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
1s 561ms 10

When I follow the left menu "Systems > Autoinstallation > Distributions" 71ms

And I follow "Create Distribution" 318ms

When I enter "isedistro_api" as "label" 57ms

And I enter "/var/autoinstall/Fedora_12_i386/" as "basepath" 78ms

And I select "Fedora" from "installtype" 51ms

And I click on "Create Autoinstallable Distribution" 758ms

Then I should see a "Autoinstallable Distributions" text 73ms

And I should see a "isedistro_api" link 12ms

When I follow the left menu "Systems > Autoinstallation > Distributions" 68ms

Then I should see a "isedistro_api" text 70ms

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
2s 859ms 12

When I follow the left menu "Systems > Autoinstallation > Profiles" 68ms

And I follow "Create Kickstart Profile" 371ms

When I enter "iseprofile_api" as "kickstartLabel" 57ms

And I click on "Next" 53ms

And I click on "Next" 366ms

And I enter "linux" as "rootPassword" 47ms

And I enter "linux" as "rootPasswordConfirm" 53ms

And I click on "Finish" 1s 594ms

Then I should see a "Autoinstallation: iseprofile_api" text 81ms

And I should see a "Autoinstallation Details" link 8ms

When I follow the left menu "Systems > Autoinstallation > Profiles" 71ms

Then I should see a "iseprofile_api" text 83ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 7ms

Scenario:
Create a Cobbler system via the XML-RPC API
531ms 1

When I create a system record with name "isesystem_api" and kickstart label "iseprofile_api" 531ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 7ms

Scenario:
Create and modify a System profile using the XML-RPC API
1s 606ms 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 606ms
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 83ms 6

When I wait for "10" seconds 10s

When I delete profile and distribution using the API for "isedistro_ui" kickstart tree 460ms

When I delete profile and distribution using the API for "isedistro_api" kickstart tree 428ms

When I follow the left menu "Systems > Autoinstallation > Distributions" 71ms

And I should not see a "isedistro_ui" text 64ms

And I should not see a "isedistro_api" text 58ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 2ms

@flaky
Scenario:
Check for errors in Cobbler monitoring
9s 40ms 2

When I wait for "5" seconds 5s

Then the local logs for Cobbler should not contain errors 4s 40ms

@scope_visualization
Feature:Manage users 1m 36s 966ms 15 2

Scenario:
Log in as admin user
37s 862ms 1

Given I am authorized for the "Admin" section 37s 862ms

Scenario:
Display active users page
553ms 9

When I follow the left menu "Users > User List > Active" 214ms

Then I should see a "Active Users" text 186ms

And I should see a "Create User" link 11ms

And I should see a "User List" link in the left menu 24ms

And I should see a "Active" link in the left menu 25ms

And I should see a "Deactivated" link in the left menu 22ms

And I should see a "All" link in the left menu 46ms

And I should see a "admin" link in the table first column 10ms

And I should see a "Download CSV" link 10ms

Scenario:
Create a new user
7s 471ms 13

When I follow the left menu "Users > User List > Active" 75ms

And I follow "Create User" 285ms

And I enter "user1" as "login" 58ms

And I enter "user1" as "desiredpassword" 56ms

And I enter "user1" as "desiredpasswordConfirm" 59ms

And I select "Mr." from "prefix" 47ms

And I enter "Test" as "firstNames" 56ms

And I enter "User" as "lastName" 56ms

And I enter "galaxy-noise@localhost" as "email" 78ms

And I click on "Create Login" 6s 322ms

Then I should see a "Account user1 created, login information sent to galaxy-noise@localhost" text 188ms

And I should see a "user1" link 12ms

And I should see a "normal user" text 174ms

Scenario:
Login as the new user
1s 596ms 2

Given I am authorized as "user1" with password "user1" 1s 586ms

Then I should see a "user1" link 9ms

Scenario:
Access user details
2s 548ms 21

Given I am authorized for the "Admin" section 1s 125ms

When I follow the left menu "Users > User List > Active" 157ms

And I follow "user1" 502ms

Then I should see a "User Details" text 76ms

And I should see a "Delete User" link 12ms

And I should see a "Deactivate User" link 11ms

And I should see a "Details" link 14ms

And I should see a "System Groups" link 15ms

And I should see a "Systems" link in the content area 25ms

And I should see a "Channel Permissions" link 12ms

And I should see a "Preferences" link in the content area 25ms

And I should see a "Addresses" link 14ms

And I should see a "user1" text 72ms

And option "Mr." is selected as "prefix" 61ms

And I should see "Test" in field identified by "firstNames" 24ms

And I should see "User" in field identified by "lastName" 22ms

And I should see a "galaxy-noise@localhost" text 71ms

And I should see a "Administrative Roles" text 75ms

And I should see a "Roles:" text 77ms

And I should see a "Created:" text 76ms

And I should see a "Last Sign In:" text 72ms

@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 673ms 23

When I follow the left menu "Users > User List > Active" 71ms

And I follow "user1" 466ms

When the "role_satellite_admin" checkbox should be disabled 10s 11ms

And I check "role_org_admin" 80ms

And I check "role_system_group_admin" 75ms

And I check "role_channel_admin" 75ms

And I check "role_activation_key_admin" 75ms

And I check "role_config_admin" 75ms

And I click on "Update" 1s 122ms

Then the "role_satellite_admin" checkbox should be disabled 10s

And I should see a "Uyuni Administrator" text 79ms

And I should see "role_org_admin" as checked 16ms

And I should see a "Organization Administrator" text 71ms

And I should see "role_system_group_admin" as checked 15ms

And I should see a "System Group Administrator" text 74ms

And I should see "role_channel_admin" as checked 15ms

And I should see a "Channel Administrator" text 74ms

And I should see "role_activation_key_admin" as checked 15ms

And I should see a "Activation Key Administrator" text 79ms

And I should see "role_config_admin" as checked 15ms

And I should see a "Configuration Administrator" text 70ms

And I should see "role_regular_user" as checked 18ms

And I should see a "Regular User" text 74ms

Scenario:
Verify user list
96ms 2

When I follow the left menu "Users > User List > Active" 72ms

Then table row for "user1" should contain "Organization Administrator" 23ms

Scenario:
Fail to deactivate organization administrator
1s 973ms 8

When I follow the left menu "Users > User List > Active" 66ms

And I follow "user1" 469ms

When I follow "Deactivate User" 422ms

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 50ms

When I click on "Deactivate User" 485ms

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 79ms

When I follow "Deactivated" 337ms

Then I should see a "No deactivated users." text 61ms

Scenario:
Remove role
11s 389ms 10

When I follow the left menu "Users > User List > Active" 92ms

And I follow "user1" 459ms

When I uncheck "role_org_admin" 10s 55ms

And I click on "Update" 686ms

Then I should see "role_org_admin" as unchecked 16ms

And I should see "role_system_group_admin" as checked 15ms

And I should see "role_channel_admin" as checked 15ms

And I should see "role_activation_key_admin" as checked 15ms

And I should see "role_config_admin" as checked 16ms

And I should see "role_regular_user" as checked 16ms

Scenario:
Deactivate ordinary user
2s 493ms 13

When I follow the left menu "Users > User List > Active" 77ms

And I follow "user1" 488ms

Then I should see "role_org_admin" as unchecked 38ms

When I follow "Deactivate User" 331ms

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 51ms

When I click on "Deactivate User" 631ms

Then I should see a "Active Users" text 178ms

And I should not see a "user1" link 8ms

When I follow "Deactivated" 276ms

Then I should see a "Deactivated Users" text 66ms

And I should see a "user1" link 8ms

When I follow "All" 324ms

Then I should see a "user1" link 9ms

@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 721ms 11

When I follow the left menu "Users > User List > Active" 71ms

And I follow "Deactivated" 258ms

And I follow "user1" 374ms

Then I should see a "Reactivate User" link 11ms

When I follow "Reactivate User" 414ms

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 62ms

When I click on "Reactivate User" 62ms

Then I should see a "Active Users" text 182ms

And I should see a "user1" link 8ms

When I follow "Deactivated" 270ms

Then I should not see a "user1" link 4ms

Scenario:
Delete user
1s 761ms 8

When I follow the left menu "Users > User List > Active" 66ms

And I follow "user1" 470ms

When I follow "Delete User" 332ms

Then I should see a "Confirm User Deletion" text 52ms

And I should see a "This will delete this user permanently." text 50ms

When I click on "Delete User" 605ms

Then I should see a "Active Users" text 177ms

And I should not see a "user1" link 6ms

Scenario:
Display the CSV separator preference
2s 373ms 6

Given I am authorized as "testing" with password "testing" 1s 886ms

When I follow the left menu "Home > My Preferences" 70ms

Then I should see a "CSV Files" text 114ms

And I should see a "Configure a separator character to be used in downloadable CSV files:" text 116ms

And I should see a "Comma" text 92ms

And I should see a "Semicolon" text 93ms

Scenario:
Configure the CSV separator char to semicolon
1s 193ms 6

Given I am authorized as "testing" with password "testing" 476ms

When I follow the left menu "Home > My Preferences" 64ms

And I choose ";" 57ms

And I click on "Save Preferences" 473ms

Then I should see a "Preferences modified" text 100ms

And radio button "radio-semicolon" should be checked 20ms

Scenario:
Cleanup: configure the CSV separator char to comma
1s 259ms 6

Given I am authorized as "testing" with password "testing" 510ms

When I follow the left menu "Home > My Preferences" 60ms

And I choose "," 79ms

And I click on "Save Preferences" 491ms

Then I should see a "Preferences modified" text 98ms

And radio button "radio-comma" should be checked 20ms

@scope_visualization @new_issue
Feature:Web UI - Main landing page menu, texts and links 13s 11ms 43

Scenario:
Log in as admin user
1s 653ms 1

Given I am authorized for the "Admin" section 1s 653ms

Scenario:
The Home menu
234ms 7

When I follow the left menu "Home" 56ms

And I should see a "Overview" link in the left menu 31ms

Then I should see a "Overview" text 51ms

And I should see a "Notification Messages" link in the left menu 23ms

And I should see a "User Account" link in the left menu 23ms

And I should see a "My Preferences" link in the left menu 25ms

And I should see a "My Organization" link in the left menu 22ms

Scenario:
The user account submenu under the Home menu
239ms 6

When I follow the left menu "Home > User Account" 72ms

Then I should see a "My Account" text 72ms

And I should see a "My Account" link in the left menu 25ms

And I should see a "Addresses" link in the left menu 21ms

And I should see a "Change Email" link in the left menu 25ms

And I should see a "Account Deactivation" link in the left menu 22ms

Scenario:
The my orginization menu under the Home menu
198ms 5

When I follow the left menu "Home > My Organization" 64ms

Then I should see a "Organization Configuration" text 65ms

And I should see a "Configuration" link in the left menu 27ms

And I should see a "Organization Trusts" link in the left menu 21ms

And I should see a "Configuration Channels" link in the left menu 20ms

Scenario:
The Salt menu
182ms 5

When I follow the left menu "Salt" 55ms

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 21ms

And I should see a "Formula Catalog" link in the left menu 22ms

Scenario:
The content lifeycle menu
172ms 4

When I follow the left menu "Content Lifecycle" 74ms

Then I should see a "Content Lifecycle Projects" text 54ms

And I should see a "Projects" link in the left menu 21ms

And I should see a "Filters" link in the left menu 21ms

Scenario:
The images menu
216ms 6

When I follow the left menu "Images" 56ms

Then I should see a "Images" text 71ms

And I should see a "Image List" link in the left menu 22ms

And I should see a "Build" link in the left menu 21ms

And I should see a "Profiles" link in the left menu 24ms

And I should see a "Stores" link in the left menu 20ms

Scenario:
The audit menu
218ms 6

When I follow the left menu "Audit" 56ms

Then I should see a "CVE Audit" text 74ms

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 22ms

And I should see a "Confidential Computing" link in the left menu 21ms

Scenario:
The OpenSCAP submenu menu
203ms 5

When I follow the left menu "Audit > OpenSCAP" 69ms

Then I should see a "OpenSCAP Scans" text 61ms

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 25ms

And I should see a "Advanced Search" link in the left menu 23ms

Scenario:
The configuration menu
180ms 5

When I follow the left menu "Configuration" 52ms

Then I should see a "Configuration Overview" text 65ms

And I should see a "Overview" link in the left menu 20ms

And I should see a "Channels" link in the left menu 22ms

And I should see a "Files" link in the left menu 20ms

Scenario:
The files menu under the configuration menu
168ms 4

When I follow the left menu "Configuration > Files" 70ms

Then I should see a "Centrally-Managed Configuration Files" text 52ms

And I should see a "Centrally Managed" link in the left menu 23ms

And I should see a "Locally Managed" link in the left menu 21ms

Scenario:
The systems submenu in the configuration menu
162ms 4

When I follow the left menu "Configuration > Systems" 64ms

Then I should see a "Managed Systems" text 54ms

And I should see a "Managed" link in the left menu 22ms

And I should see a "Target" link in the left menu 21ms

Scenario:
The schedule menu
210ms 6

When I follow the left menu "Schedule" 57ms

Then I should see a "Pending Actions" text 61ms

And I should see a "Pending Actions" link in the left menu 24ms

And I should see a "Failed Actions" link in the left menu 21ms

And I should see a "Archived Actions" link in the left menu 22ms

And I should see a "Action Chains" link in the left menu 22ms

Scenario:
The users menu
373ms 8

When I follow the left menu "Users" 54ms

Then I should see a "Active Users" text 185ms

And I should see a "Users" link in the left menu 22ms

And I should see a "User List" link in the left menu 23ms

And I should see a "Active" link in the left menu 22ms

And I should see a "Deactivated" link in the left menu 21ms

And I should see a "All" link in the left menu 23ms

And I should see a "System Group Configuration" link in the left menu 21ms

Scenario:
The admin menu
323ms 10

When I follow the left menu "Admin" 59ms

Then I should see a "Setup Wizard" text 98ms

And I should see a "Setup Wizard" link in the left menu 21ms

And I should see a "Organizations" link in the left menu 22ms

And I should see a "Users" link in the left menu 18ms

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 21ms

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 20ms

And I should see a "Show Tomcat Logs" link in the left menu 19ms

Scenario:
The Setup Wizard submenu of the admin menu
136ms 4

When I follow the left menu "Admin > Setup Wizard" 67ms

Then I should see a "HTTP Proxy" link in the left menu 25ms

And I should see a "Organization Credentials" link in the left menu 22ms

And I should see a "Products" link in the left menu 20ms

Scenario:
The manager configuration submenu of the admin menu
263ms 8

When I follow the left menu "Admin > Manager Configuration" 65ms

Then I should see a "Configuration - General Configuration" text 72ms

And I should see a "General" link in the left menu 21ms

And I should see a "Bootstrap Script" link in the left menu 19ms

And I should see a "Organizations" link in the left menu 16ms

And I should see a "Restart" link in the left menu 24ms

And I should see a "Cobbler" link in the left menu 22ms

And I should see a "Monitoring" link in the left menu 20ms

Scenario:
The Hub configuration submenu of the admin menu
188ms 5

When I follow the left menu "Admin > Hub Configuration" 63ms

Then I should see a "Peripherals Configuration" text 58ms

And I should see a "Peripherals Configuration" link in the left menu 24ms

And I should see a "Hub Details" link in the left menu 20ms

And I should see a "Access Tokens" link in the left menu 20ms

Scenario:
The Task Engine Status submenu of the admin menu
112ms 3

When I follow the left menu "Admin > Task Engine Status" 68ms

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 21ms

Scenario:
The menu direct link accesses the first submenu level only
446ms 6

When I follow the left menu "Patches > Patch List" 123ms

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 84ms

When I follow the left menu "Configuration > Files" 106ms

Then I should see a "Centrally-Managed Configuration Files" text in the content area 16ms

And I should not see a "Locally Managed Configuration Files" text in the content area 15ms

Scenario:
Idempotency of complete menu path and direct link
308ms 4

When I follow the left menu "Software > Manage" 117ms

Then I should see a "Software Channel Management" text in the content area 55ms

When I follow the left menu "Software > Manage > Channels" 82ms

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
568ms 13

When I am on the Systems page 325ms

Then I should see a "Systems" text in the content area 27ms

And I should see a "All" link in the left menu 19ms

And I should see a "Systems" link in the left menu 27ms

And I should see a "System Groups" link in the left menu 22ms

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 21ms

And I should see a "Custom System Info" link in the left menu 21ms

And I should see a "Autoinstallation" link in the left menu 20ms

And I should see a "Download CSV" link 10ms

And I should see a Sign Out link 10ms

Scenario:
Sidebar link destination for Systems
237ms 7

When I follow the left menu "Systems > System List" 63ms

Then I should see a "All" link in the left menu 20ms

And I should see a "Virtual Systems" link in the left menu 22ms

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 21ms

And I should see a "System Types" link in the left menu 21ms

And I should see a "Systems" text 68ms

Scenario:
Sidebar link destination for Systems => Virtual Systems
149ms 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
197ms 7

When I follow the left menu "Systems > System List > Duplicate Systems" 76ms

Then I should see a "Duplicate Systems" text 74ms

And the current path is "/rhn/systems/DuplicateIPList.do" 2ms

And I should see a "Duplicate IP Address" link 12ms

And I should see a "Duplicate Hostname" link 11ms

And I should see a "Duplicate IPv6 Address" link 10ms

And I should see a "Duplicate MAC Address" link 10ms

Scenario:
Sidebar link destination for Systems => System Currency
175ms 3

When I follow the left menu "Systems > System List > System Currency" 73ms

Then I should see a "System Currency Report" text 99ms

And the current path is "/rhn/systems/SystemCurrency.do" 2ms

Scenario:
Sidebar link destination for Systems => System Types
623ms 7

When I follow the left menu "Systems > System List > System Types" 75ms

Then I should see a "System Types" text 112ms

And I should see a "Management:" text 103ms

And I should see a "Salt:" text 108ms

And I should see a "Foreign:" text 113ms

And I should see a "Virtualization Host:" text 108ms

And the current path is "/rhn/systems/SystemEntitlements.do" 2ms

Scenario:
Sidebar link destination for Systems => System Groups
197ms 4

When I follow the left menu "Systems > System Groups" 64ms

Then I should see a "System Groups" text 64ms

And I should see a "Create Group" link 12ms

And I should see a "Your organization has no system groups." text 55ms

Scenario:
Sidebar link destination for Systems => System Set Manager
788ms 12

When I follow the left menu "Systems > System Set Manager > Overview" 467ms

Then I should see a "System Set Manager" text 80ms

And I should see a "Task Log" link in the left menu 37ms

And I should see a "Overview" link in the content area 38ms

And I should see a "Systems" link in the content area 23ms

And I should see a "Patches" link in the content area 21ms

And I should see a "Packages" link in the content area 20ms

And I should see a "Groups" link in the content area 20ms

And I should see a "Channels" link in the content area 17ms

And I should see a "Configuration" link in the content area 20ms

And I should see a "Provisioning" link in the content area 19ms

And I should see a "Misc" link in the content area 19ms

Scenario:
Sidebar link destination for Systems => Advanced Search
135ms 2

When I follow the left menu "Systems > Advanced Search" 64ms

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" 65ms

Then I should see a "Activation Keys" text 79ms

And I should see a "Create Key" link 11ms

And I should see a "The following activation keys have been created for use by your organization." text 77ms

Scenario:
Sidebar link destination for Systems => Stored Profiles
176ms 3

When I follow the left menu "Systems > Stored Profiles" 61ms

Then I should see a "Stored Profiles" text 59ms

And I should see a "No stored profiles." text 55ms

Scenario:
Sidebar link destination for Systems => Custom System Info
206ms 4

When I follow the left menu "Systems > Custom System Info" 65ms

Then I should see a "Custom System Info Keys" text 76ms

And I should see a "Create Key" link 7ms

And I should see a "No Custom Info Keys Found" text 56ms

Scenario:
Sidebar link destination for Systems => Autoinstallation
384ms 13

When I follow the left menu "Systems > Autoinstallation > Overview" 122ms

Then I should see a "Autoinstallation Overview" text 76ms

And I should see a "Profiles" link in the left menu 19ms

And I should see a "Unprovisioned" link in the left menu 23ms

And I should see a "GPG and SSL Keys" link in the left menu 22ms

And I should see a "Distributions" link in the left menu 23ms

And I should see a "File Preservation" link in the left menu 20ms

And I should see a "Autoinstallation Snippets" link in the left menu 20ms

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 14ms

Scenario:
Sidebar link destination for Systems => Autoinstallation => Profiles
153ms 4

When I follow the left menu "Systems > Autoinstallation > Profiles" 74ms

Then I should see a "Autoinstallation Profiles" text 63ms

And I should see a "Create Kickstart Profile" link 8ms

And I should see a "Upload Kickstart/AutoYaST File" link 7ms

Scenario:
Sidebar link destination for Systems => Autoinstallation => Unprovisioned
194ms 3

When I follow the left menu "Systems > Autoinstallation > Unprovisioned" 72ms

Then I should see a "Unprovisioned Autoinstallation By IP" text 62ms

And I should see a "No Ip Ranges Found" text 58ms

Scenario:
Sidebar link destination for Systems => Autoinstallation => GPG and SSL Keys
177ms 5

When I follow the left menu "Systems > Autoinstallation > GPG and SSL Keys" 71ms

Then I should see a "GPG Public Keys and SSL Certificates" text 72ms

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
210ms 4

When I follow the left menu "Systems > Autoinstallation > Distributions" 72ms

Then I should see a "Autoinstallable Distributions" text 63ms

And I should see a "No autoinstallable distributions available." text 62ms

And I should see a "Create Distribution" link 12ms

Scenario:
Sidebar link destination for Systems => Autoinstallation => File Preservation
151ms 4

When I follow the left menu "Systems > Autoinstallation > File Preservation" 71ms

Then I should see a "File Preservation" text 59ms

And I should see a "Reference Guide" link 8ms

And I should see a "Create File Preservation List" link 11ms

Scenario:
Sidebar link destination for Systems => Autoinstallation => Autoinstallation Snippets
274ms 7

When I follow the left menu "Systems > Autoinstallation > Autoinstallation Snippets" 74ms

Then I should see a "Autoinstallation Snippets" text 64ms

And I should see a "No autoinstallation snippets found." text 59ms

And I should see a "Create Snippet" link 11ms

And I should see a "Default Snippets" link in the content area 22ms

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 20ms

Scenario:
"Create Kickstart Profile" page Systems => Autoinstallation => Profiles => Create Kickstart Profile
436ms 3

When I follow the left menu "Systems > Autoinstallation > Profiles" 74ms

And I follow "Create Kickstart Profile" 293ms

Then I should see a "Step 1: Create Kickstart Profile" text 67ms

Scenario:
"Upload Kickstart/AutoYaST File" page Systems => Autoinstallation => Profiles => Upload Kickstart/AutoYaST File
634ms 5

When I follow the left menu "Systems > Autoinstallation > Profiles" 66ms

And I follow "Upload Kickstart/AutoYaST File" 359ms

Then I should see a "Create Autoinstallation Profile" text 67ms

And I should see a "File Contents:" text 70ms

And I should see a "Autoinstallation Details" text 69ms

Scenario:
"Create kickstart distribution" page Systems => Autoinstallation => Distributions => create new kickstart distribution
507ms 4

When I follow the left menu "Systems > Autoinstallation > Distributions" 69ms

And I follow "Create Distribution" 299ms

Then I should see a "Create Autoinstallable Distribution" text 69ms

And I should see a "Distribution Label" text 68ms

@scope_configuration_channels
Feature:Check if source packages were successfully synced 5s 671ms 3

Scenario:
Log in as org admin user
1s 849ms 1

Given I am authorized 1s 849ms

Scenario:
Check sources for noarch package
1s 944ms 6

When I follow the left menu "Software > Channel List > All" 176ms

And I follow "Show All Child Channels" 66ms

And I follow "Fake-RPM-SUSE-Channel" 578ms

And I follow "Packages" 506ms

And I follow "virgo-dummy-2.0-1.1.noarch" 547ms

Then I should see a "virgo-dummy-2.0-1.1.src.rpm" text 69ms

Scenario:
Check sources for x86_64 package
1s 877ms 6

When I follow the left menu "Software > Channel List > All" 116ms

And I follow "Show All Child Channels" 47ms

And I follow "Fake-RPM-SUSE-Channel" 572ms

And I follow "Packages" 495ms

And I follow "blackhole-dummy-1.0-1.1.x86_64" 577ms

Then I should see a "blackhole-dummy-1.0-1.1.src.rpm" text 67ms

@scope_visualization
Feature:Change the user's password 15s 508ms 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 611ms 1

Given I am authorized for the "Admin" section 1s 611ms

Scenario:
Change the password to a new password
1s 572ms 10

When I follow the left menu "Home > User Account > My Account" 131ms

And I enter "GoodPass" as "desiredpassword" 59ms

And I enter "GoodPass" as "desiredpasswordConfirm" 61ms

And I click on "Update" 422ms

Then I should see a "User information updated" text 71ms

When I sign out 323ms

And I enter "admin" as "username" 40ms

And I enter "GoodPass" as "password" 56ms

And I click on "Sign In" 53ms

Then I should be logged in 351ms

Scenario:
Revert the new password to a valid standard password
1s 513ms 10

When I follow the left menu "Home > User Account > My Account" 116ms

And I enter "admin" as "desiredpassword" 72ms

And I enter "admin" as "desiredpasswordConfirm" 48ms

And I click on "Update" 394ms

Then I should see a "User information updated" text 69ms

When I sign out 322ms

And I enter "admin" as "username" 40ms

And I enter "admin" as "password" 51ms

And I click on "Sign In" 56ms

Then I should be logged in 340ms

Scenario:
Try an invalid password
10s 811ms 10

When I follow the left menu "Home > User Account > My Account" 117ms

And I enter "A" as "desiredpassword" 47ms

And I enter "A" as "desiredpasswordConfirm" 45ms

And I click on "Update" 53ms

Then I should see a "Passwords must be at least 4 characters." text 69ms

When I sign out 320ms

And I enter "admin" as "username" 40ms

And I enter "A" as "password" 48ms

And I click on "Sign In" 53ms

Then I should not be authorized 10s 13ms

@scope_configuration_channels
Feature:Clone a channel 38s 313ms 12

Scenario:
Log in as org admin user
10s 786ms 1

Given I am authorized 10s 786ms

Scenario:
Clone a channel without patches
2s 494ms 10

When I follow the left menu "Software > Manage > Channels" 188ms

And I follow "Clone Channel" 484ms

And I select "Fake-RPM-SUSE-Channel" as the origin channel 76ms

And I choose "original" 55ms

And I click on "Clone Channel" 460ms

And I enter "Fake-Clone-RPM-SLES15SP7-Channel" as "Channel Name" 135ms

And I should see a "Create Software Channel" text 84ms

And I should see a "Original state of the channel" text 78ms

And I click on "Clone Channel" 852ms

Then I should see a "Fake-Clone-RPM-SLES15SP7-Channel" text 78ms

Scenario:
Check that this channel has no patches
1s 439ms 5

When I follow the left menu "Software > Manage > Channels" 77ms

And I follow "Fake-Clone-RPM-SLES15SP7-Channel" 569ms

And I follow "Patches" in the content area 69ms

And I follow "List/Remove Patches" 667ms

Then I should see a "There are no patches associated with this channel." text 55ms

Scenario:
Clone a channel with patches
2s 435ms 10

When I follow the left menu "Software > Manage > Channels" 68ms

And I follow "Clone Channel" 561ms

And I select "Fake-RPM-SUSE-Channel" as the origin channel 53ms

And I choose "current" 52ms

And I click on "Clone Channel" 450ms

And I enter "Fake-Clone-2-RPM-SLES15SP7-Channel" as "Channel Name" 125ms

And I should see a "Create Software Channel" text 80ms

And I should see a "Current state of the channel" text 71ms

And I click on "Clone Channel" 891ms

Then I should see a "Fake-Clone-2-RPM-SLES15SP7-Channel" text 78ms

Scenario:
Check that this channel has patches
1s 375ms 8

When I follow the left menu "Software > Manage > Channels" 71ms

And I follow "Fake-Clone-2-RPM-SLES15SP7-Channel" 585ms

And I follow "Patches" in the content area 60ms

And I follow "List/Remove Patches" 613ms

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 12ms

Scenario:
Clone a channel with selected patches
4s 819ms 18

When I follow the left menu "Software > Manage > Channels" 67ms

And I follow "Clone Channel" 541ms

And I select "Fake-RPM-SUSE-Channel" as the origin channel 57ms

And I choose "select" 50ms

And I click on "Clone Channel" 464ms

And I enter "Fake-Clone-3-RPM-SLES15SP7-Channel" as "Channel Name" 120ms

And I should see a "Create Software Channel" text 80ms

And I should see a "Select patches" text 82ms

And I click on "Clone Channel" 944ms

And I should see a "Fake-Clone-3-RPM-SLES15SP7-Channel" text 86ms

And I should see a "Channel Fake-Clone-3-RPM-SLES15SP7-Channel cloned from channel Fake-RPM-SUSE-Channel." text 83ms

And I should see a "You may now wish to clone the patches associated with Fake-RPM-SUSE-Channel." text 96ms

And I check the row with the "hoag-dummy-7890" link 62ms

And I check the row with the "virgo-dummy-3456" link 57ms

And I click on "Clone Patches" 947ms

And I click on "Confirm" 1s 58ms

Then I should see a "CL-hoag-dummy-7890" link 10ms

And I should see a "CL-virgo-dummy-3456" link 8ms

Scenario:
Check that new patches exists
1s 559ms 8

When I follow the left menu "Patches > Patch List > All" 178ms

And I enter "dummy" as the filtered synopsis 50ms

And I click on the filter button 688ms

And I select "500" from "1154021400_PAGE_SIZE_LABEL" 600ms

Then I should see a "CL-hoag-dummy-7890" link 13ms

And I should see a "CL-virgo-dummy-3456" link 8ms

And I should see a "CL-milkyway-dummy-2345" link 9ms

And I should see a "CL-andromeda-dummy-6789" link 9ms

Scenario:
Check CL-hoag-dummy-7890 patches
2s 69ms 8

When I follow the left menu "Patches > Patch List > All" 73ms

And I enter "dummy" as the filtered synopsis 36ms

And I click on the filter button 684ms

And I select "500" from "1154021400_PAGE_SIZE_LABEL" 585ms

And I follow "CL-hoag-dummy-7890" 545ms

Then I should see a "CL-hoag-dummy-7890 - Security Advisory" text 74ms

And I should see a "mcalmer" text 59ms

And I should see a "https://bugzilla.opensuse.org/show_bug.cgi?id=704608" link 11ms

Scenario:
Check CM-virgo-dummy-3456 patches
2s 51ms 8

When I follow the left menu "Patches > Patch List > All" 70ms

And I enter "dummy" as the filtered synopsis 45ms

And I click on the filter button 653ms

And I select "500" from "1154021400_PAGE_SIZE_LABEL" 606ms

And I follow "CL-virgo-dummy-3456" 539ms

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 11ms

Scenario:
Compare channel packages
2s 243ms 9

When I follow the left menu "Software > Manage > Channels" 199ms

And I follow "Fake-Clone-2-RPM-SLES15SP7-Channel" 570ms

And I follow "Packages" in the content area 69ms

And I follow "Compare" 558ms

And I select "Fake-Clone-3-RPM-SLES15SP7-Channel" from "selected_channel" 64ms

And I click on "View Packages" 566ms

Then I should see a "andromeda-dummy" text 91ms

And I should see a "2.0-1.1" link 33ms

And I should see a "This channel only" text 89ms

Scenario:
Cleanup: remove cloned channels
6s 966ms 21

When I follow the left menu "Software > Manage > Channels" 72ms

And I follow "Fake-Clone-RPM-SLES15SP7-Channel" 560ms

And I follow "Delete Channel" 403ms

And I check "unsubscribeSystems" 79ms

And I click on "Delete Channel" 780ms

Then I should see a "Fake-Clone-RPM-SLES15SP7-Channel" text 63ms

And I should see a "has been deleted." text 60ms

Given I follow the left menu "Software > Manage > Channels" 81ms

When I follow "Fake-Clone-2-RPM-SLES15SP7-Channel" 578ms

And I follow "Delete Channel" 393ms

And I check "unsubscribeSystems" 66ms

And I click on "Delete Channel" 736ms

Then I should see a "Fake-Clone-2-RPM-SLES15SP7-Channel" text 63ms

And I should see a "has been deleted." text 58ms

Given I follow the left menu "Software > Manage > Channels" 76ms

When I follow "Fake-Clone-3-RPM-SLES15SP7-Channel" 561ms

And I follow "Delete Channel" 465ms

And I check "unsubscribeSystems" 68ms

And I click on "Delete Channel" 1s 677ms

Then I should see a "Fake-Clone-3-RPM-SLES15SP7-Channel" text 61ms

And I should see a "has been deleted." text 59ms

Scenario:
Cleanup: remove remaining systems from SSM after channel cloning tests
70ms 1

When I click on the clear SSM button 70ms

@flaky
Feature:Manipulate activation keys 14s 29ms 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 797ms 1

Given I am authorized 1s 797ms

Scenario:
Create an activation key for i586
1s 54ms 8

When I follow the left menu "Systems > Activation Keys" 121ms

And I follow "Create Key" 263ms

And I wait until I do not see "Loading..." text 300ms

And I enter "SUSE Test Key i586" as "description" 76ms

And I enter "SUSE-TEST-i586" as "key" 72ms

And I check "virtualization_host" 82ms

And I click on "Create Activation Key" 61ms

Then I should see a "Activation key SUSE Test Key i586 has been created." text 74ms

Scenario:
Change limit of the i586 activation key
1s 492ms 7

When I follow the left menu "Systems > Activation Keys" 68ms

And I follow "SUSE Test Key i586" 338ms

And I wait until I do not see "Loading..." text 391ms

And I enter "20" as "usageLimit" 52ms

And I click on "Update Activation Key" 541ms

Then I wait until I see "Activation key SUSE Test Key i586 has been modified." text 73ms

And I should see "20" in field identified by "usageLimit" 25ms

Scenario:
Change the base channel of the i586 activation key
1s 596ms 6

When I follow the left menu "Systems > Activation Keys" 63ms

And I follow "SUSE Test Key i586" 325ms

And I wait until I do not see "Loading..." text 405ms

And I select "Fake-Base-Channel-i586" from "selectedBaseChannel" 79ms

And I click on "Update Activation Key" 650ms

Then I wait until I see "Activation key SUSE Test Key i586 has been modified." text 72ms

Scenario:
Delete the i586 activation key
1s 400ms 6

When I follow the left menu "Systems > Activation Keys" 64ms

And I follow "SUSE Test Key i586" in the content area 65ms

And I wait until I do not see "Loading..." text 385ms

And I follow "Delete Key" 305ms

And I click on "Delete Activation Key" 494ms

Then I should see a "Activation key SUSE Test Key i586 has been deleted." text 84ms

Scenario:
Create an activation key with a channel and a package list for i586
1s 836ms 12

When I follow the left menu "Systems > Activation Keys" 59ms

And I follow "Create Key" 322ms

And I wait until I do not see "Loading..." text 215ms

And I enter "SUSE Test PKG Key i586" as "description" 72ms

And I enter "SUSE-TEST-2-i586" as "key" 68ms

And I enter "20" as "usageLimit" 50ms

And I select "Fake-Base-Channel-i586" from "selectedBaseChannel" 53ms

And I click on "Create Activation Key" 56ms

And I follow "Packages" 321ms

And I enter "sed" as "packages" 50ms

And I click on "Update Activation Key" 509ms

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 162ms 5

When I follow the left menu "Systems > Activation Keys" 63ms

And I follow "SUSE Test PKG Key i586" in the content area 69ms

And I follow "Delete Key" 299ms

And I click on "Delete Activation Key" 644ms

Then I should see a "Activation key SUSE Test PKG Key i586 has been deleted." text 85ms

@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 587ms 12

When I follow the left menu "Systems > Activation Keys" 59ms

And I follow "Create Key" 336ms

And I wait until I do not see "Loading..." text 141ms

And I enter "SUSE Test PKG Key x86_64" as "description" 76ms

And I enter "SUSE-TEST-x86_64" as "key" 69ms

And I enter "20" as "usageLimit" 53ms

And I select "openSUSE Tumbleweed (x86_64)" from "selectedBaseChannel" 64ms

And I click on "Create Activation Key" 856ms

And I follow "Packages" 320ms

And I enter "sed" as "packages" 46ms

And I click on "Update Activation Key" 507ms

Then I should see a "Activation key SUSE Test PKG Key x86_64 has been modified." text 56ms

@scc_credentials
Scenario:
Delete the x86_64 activation key with packages
1s 101ms 5

When I follow the left menu "Systems > Activation Keys" 68ms

And I follow "SUSE Test PKG Key x86_64" in the content area 68ms

And I follow "Delete Key" 305ms

And I click on "Delete Activation Key" 47ms

Then I should see a "Activation key SUSE Test PKG Key x86_64 has been deleted." text 612ms

@scope_api
Feature:API "activationkey" namespace 3s 433ms 4

Scenario:
List all activation keys
399ms 1

Then I should get some activation keys 399ms

Scenario:
Create activation key
1s 191ms 2

When I create an activation key with id "testkey", description "Key for testing", limit of 10 and contact method "default" 802ms

Then I should get the new activation key "1-testkey" 388ms

Scenario:
Activation key details
739ms 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" 377ms

Then I get the description "Key description" for the activation key "1-testkey" 362ms

Scenario:
Cleanup: delete activation key
1s 103ms 1

When I delete the activation key "1-testkey" 1s 103ms

@scope_visualization
Feature:Main landing page options and preferences 54s 526ms 10 2

Scenario:
Clear browser cookies for main landing page validation
16ms 1

When I clear browser cookies 16ms

Scenario:
Access the Login page
553ms 3

Given I am not authorized 398ms

When I go to the home page 135ms

Then I should see a "Sign In" text 19ms

@uyuni
Scenario:
Access the API Documentation
10s 548ms 4

Given I am not authorized 10s 206ms

When I go to the home page 130ms

And I follow "API Documentation" 165ms

Then I should see a "API Overview" text 45ms

@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 877ms 6

Given I am not authorized 10s 189ms

When I go to the home page 136ms

And I enter "testing" as "username" 53ms

And I enter "testing" as "password" 59ms

And I click on "Sign In" 60ms

Then I should be logged in 378ms

Scenario:
Log out of Uyuni
13s 111ms 3

Given I am authorized 2s 431ms

When I sign out 669ms

Then I should not be authorized 10s 11ms

Scenario:
Top level bar
11s 637ms 7

Given I am authorized for the "Admin" section 10s 645ms

When I go to the home page 896ms

And I should see a "Manage" link 16ms

And I should see a "admin" text 50ms

And I should see a "SUSE Test" link 10ms

And I should see a "Preferences" link 10ms

And I should see a Sign Out link 6ms

Scenario:
Main menu as regular user
2s 322ms 15

Given I am authorized as "testing" with password "testing" 2s 152ms

Then I should see a "Home" link 12ms

And I should see a "Systems" link 13ms

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 12ms

And I should see a "Audit" link 11ms

And I should see a "Configuration" link 18ms

And I should see a "Schedule" link 11ms

And I should see a "Users" link 11ms

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 12ms

Scenario:
Log in as admin user
2s 49ms 1

Given I am authorized for the "Admin" section 2s 49ms

Scenario:
Main menu as administrator
114ms 13

Then I should see a "Home" link 9ms

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 9ms

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 8ms

And I should see a "Users" link 7ms

And I should see a "Admin" link 8ms

And I should see a "Help" link 7ms

And I should see a "External Links" link 9ms

Scenario:
Main content
3s 294ms 8

Given I am authorized 1s 947ms

Then I should see a "Tasks" text 580ms

And I should see a "Inactive Systems" text 94ms

And I should see a "Most Critical Systems" text 140ms

And I should see a "Recently Scheduled Actions" text 137ms

And I should see a "Relevant Security Patches" text 125ms

And I should see a "System Group Name" text 144ms

And I should see a "Recently Registered Systems" text 124ms

@scope_api
Feature:API "user" namespace 24s 260ms 5

Scenario:
List users
6s 670ms 2

When I call user.list_users() 6s 670ms

Then I should get at least user "admin" < 1ms

Scenario:
List roles
363ms 2

When I call user.list_roles() on user "admin" 363ms

Then I should get at least one role that matches "_admin" suffix < 1ms

Scenario:
Create user
15s 185ms 4

When I make sure "testuser" is not present 6s 968ms

And I call user.create() with login "testuser" 1s 354ms

And I call user.list_users() 6s 862ms

Then I should get at least user "testuser" < 1ms

Scenario:
Role operations
1s 616ms 6

When I call user.add_role() on "testuser" with the role "org_admin" 362ms

And I call user.list_roles() on user "testuser" 411ms

Then I should get role "org_admin" < 1ms

When I call user.remove_role() on "testuser" with the role "org_admin" 435ms

And I call user.list_roles() on user "testuser" 406ms

Then I should not get role "org_admin" < 1ms

Scenario:
Cleanup: user tests
425ms 1

When I delete user "testuser" 425ms

@scope_salt
Feature:Endpoint to download packages 3s 908ms 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 46ms 3

2ff6b6ae29257efeda81d28d4513e39344c7eabe101c68984349f3844f583512

Given I have a valid token for organization "1" 1s 9ms

When I try to download "virgo-dummy-2.0-1.1.noarch.rpm" from channel "fake-rpm-suse-channel" 37ms

Then the download should get no error < 1ms

Scenario:
Download package, user with an invalid token for the org
28ms 3

1eb71dff835b0ac4d5b30b37667bdea37b05db9af1d64a3f7f3ae4ea014a1f319130d2aaca218d9fae599191e5702a04c8474b832a021055671d0b4d11e8be41

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
694ms 3

2ff6b6ae29257efeda81d28d4513e39344c7eabe101c68984349f3844f583512

Given I have an expired valid token for organization "1" 666ms

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 an non expired valid token for the org
699ms 3

2ff6b6ae29257efeda81d28d4513e39344c7eabe101c68984349f3844f583512

Given I have a valid token expiring tomorrow for organization "1" 666ms

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
703ms 3

2ff6b6ae29257efeda81d28d4513e39344c7eabe101c68984349f3844f583512

Given I have a not yet usable valid token for organization "1" 674ms

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 a valid token for the org and specific channels
709ms 3

2ff6b6ae29257efeda81d28d4513e39344c7eabe101c68984349f3844f583512

Given I have a valid token for organization "1" and channel "foobar" 681ms

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

@scope_building_container_images @no_auth_registry
Feature:Advanced content management 21s 867ms 8

Scenario:
Log in as docker user
1s 612ms 1

Given I am authorized as "docker" with password "docker" 1s 612ms

Scenario:
Create an image store as Docker admin
1s 219ms 6

When I follow the left menu "Images > Stores" 145ms

And I follow "Create" 281ms

And I enter "docker_admin" as "label" 94ms

And I enter the URI of the registry as "uri" 147ms

And I click on "create-btn" 63ms

Then I wait until table row contains a "galaxy-registry" text 487ms

@scc_credentials
Scenario:
Create a profile as Docker admin
3s 945ms 7

GITPROFILES: https://github.com/uyuni-project/uyuni.git#:testsuite/features/profiles/temporary

When I follow the left menu "Images > Profiles" 70ms

And I follow "Create" 382ms

And I enter "suse_docker_admin" as "label" 127ms

And I select "galaxy-registry" from "imageStore" 1s 123ms

And I select "1-SUSE-KEY-x86_64" from "activationKey" 1s 138ms

And I enter "Docker/serverhost" relative to profiles as "path" 1s 46ms

And I click on "create-btn" 55ms

Scenario:
Create a user without rights nor roles
9s 925ms 2

New user norole created with roles:

Given I am authorized for the "Admin" section 1s 29ms

When I create a user with name "norole" and password "norole" with roles "" 8s 895ms

Scenario:
Log in as docker user
1s 522ms 1

Given I am authorized as "docker" with password "docker" 1s 522ms

@scc_credentials
Scenario:
Cleanup: remove Docker profile
1s 155ms 6

Given I am authorized as "docker" with password "docker" 621ms

When I follow the left menu "Images > Profiles" 108ms

And I check the row with the "suse_docker_admin" text 126ms

And I click on "Delete" 75ms

And I click on the red confirmation button 67ms

And I should see a "Image profile has been deleted." text 157ms

Scenario:
Cleanup: remove image store
489ms 5

When I follow the left menu "Images > Stores" 58ms

And I check the row with the "docker_admin" text 158ms

And I click on "Delete" 56ms

And I click on the red confirmation button 59ms

And I should see a "Image store has been deleted." text 156ms

Scenario:
Cleanup: delete no role user
1s 998ms 2

Given I am authorized for the "Admin" section 1s 171ms

When I delete user "norole" 827ms

@scope_visualization
Feature:Pick dates 17s 548ms 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 734ms 2

Given I am authorized 1s 641ms

And I am on the Systems overview page of this "sle_minion" 5s 92ms

Scenario:
Date picker is by default set to today
10s 204ms 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 40ms

Scenario:
Picking a time sets the hidden fields
609ms 8

When I follow "Details" in the content area 95ms

And I follow "Remote Command" in the content area 66ms

And I enter "ls" as "Script" 121ms

And I pick "2022-08-27" as date 120ms

And I pick "17:30" as time 129ms

Then the date field should be set to "2022-08-27" 36ms

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 357ms 16

Scenario:
Log in as org admin user
1s 688ms 1

Given I am authorized 1s 688ms

Scenario:
Create a sles group
1s 16ms 6

When I follow the left menu "Systems > System Groups" 130ms

When I follow "Create Group" 268ms

And I enter "sles" as "name" 49ms

And I enter "SLES systems" as "description" 59ms

And I click on "Create Group" 441ms

Then I should see a "System group sles created." text 66ms

Scenario:
Add systems to the sles group
2s 388ms 6

When I follow the left menu "Systems > System Groups" 66ms

When I follow "sles" 365ms

And I follow "Target Systems" 560ms

And I check the "sle_minion" client 63ms

And I click on "Add Systems" 1s 239ms

Then I should see a "added to sles server group." text 92ms

@rhlike_minion
Scenario:
Create a rhlike group
570ms 6

When I follow the left menu "Systems > System Groups" 59ms

When I follow "Create Group" 283ms

And I enter "rhlike" as "name" 47ms

And I enter "Red Hat-like systems" as "description" 61ms

And I click on "Create Group" 55ms

Then I should see a "System group rhlike created." text 63ms

@rhlike_minion
Scenario:
Add systems to the rhlike group
4s 29ms 6

When I follow the left menu "Systems > System Groups" 61ms

When I follow "rhlike" 327ms

And I follow "Target Systems" 509ms

And I check the "rhlike_minion" client 1s 897ms

And I click on "Add Systems" 1s 140ms

Then I should see a "1 systems were added to rhlike server group." text 92ms

@deblike_minion
Scenario:
Create a deblike group
976ms 6

When I follow the left menu "Systems > System Groups" 61ms

When I follow "Create Group" 297ms

And I enter "deblike" as "name" 49ms

And I enter "Debian-like systems" as "description" 59ms

And I click on "Create Group" 445ms

Then I should see a "System group deblike created." text 62ms

@deblike_minion
Scenario:
Add systems to the deblike group
6s 740ms 6

When I follow the left menu "Systems > System Groups" 61ms

When I follow "deblike" 322ms

And I follow "Target Systems" 476ms

And I check the "deblike_minion" client 4s 549ms

And I click on "Add Systems" 1s 239ms

Then I should see a "1 systems were added to deblike server group." text 90ms

Scenario:
Add the sles group to SSM
217ms 4

When I follow the left menu "Systems > System Groups" 61ms

When I click on "Use in SSM" in row "sles" 67ms

And I should see a "Selected Systems List" text 73ms

And I should see "sle_minion" as link 14ms

@rhlike_minion
Scenario:
Add a union of 2 groups to SSM - Red Hat-like
695ms 6

When I follow the left menu "Systems > System Groups" 56ms

When I check "sles" in the list 55ms

And I check "rhlike" in the list 56ms

And I click on "Work With Union" 503ms

And I should see "sle_minion" as link 10ms

And I should see "rhlike_minion" as link 12ms

@rhlike_minion
Scenario:
Add an intersection of 2 groups to SSM - Red Hat-like
577ms 6

When I follow the left menu "Systems > System Groups" 59ms

When I check "sles" in the list 50ms

And I check "rhlike" in the list 50ms

And I click on "Work With Intersection" 400ms

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
662ms 6

When I follow the left menu "Systems > System Groups" 58ms

When I check "sles" in the list 51ms

And I check "deblike" in the list 54ms

And I click on "Work With Union" 473ms

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 51ms

And I check "deblike" in the list 50ms

And I click on "Work With Intersection" 386ms

And I should not see a "sle_minion" link 5ms

And I should not see a "deblike_minion" link 7ms

Scenario:
Cleanup: remove the sles group
1s 341ms 5

When I follow the left menu "Systems > System Groups" 57ms

When I follow "sles" in the content area 75ms

And I follow "Delete Group" in the content area 63ms

And I click on "Confirm Deletion" 1s 71ms

Then I should see a "deleted" text 73ms

@rhlike_minion
Scenario:
Cleanup: remove the rhlike group
1s 471ms 5

When I follow the left menu "Systems > System Groups" 66ms

When I follow "rhlike" in the content area 66ms

And I follow "Delete Group" in the content area 88ms

And I click on "Confirm Deletion" 1s 184ms

Then I should see a "deleted" text 65ms

@deblike_minion
Scenario:
Cleanup: remove the deblike group
1s 355ms 5

When I follow the left menu "Systems > System Groups" 67ms

When I follow "deblike" in the content area 62ms

And I follow "Delete Group" in the content area 77ms

And I click on "Confirm Deletion" 1s 91ms

Then I should see a "deleted" text 55ms

Scenario:
Cleanup: remove remaining systems from SSM after group union and intersection tests
66ms 1

When I click on the clear SSM button 66ms

@scope_visualization @scope_onboarding
Feature:Custom system info key-value pairs 14s 393ms 7

Scenario:
Log in as org admin user
1s 694ms 1

Given I am authorized 1s 694ms

Scenario:
Create a new key
1s 87ms 7

When I follow the left menu "Systems > Custom System Info" 126ms

And I follow "Create Key" 279ms

And I should see a "Create Custom Info Key" text 55ms

And I enter "key-label" as "label" 59ms

And I enter "key-desc" as "description" 60ms

And I click on "Create Key" 58ms

Then I should see a "Successfully added 1 custom key." text 445ms

Scenario:
Add a value to a system
3s 471ms 9

When I follow the left menu "Systems > System List > All" 136ms

And I follow this "sle_minion" link 1s 134ms

And I follow "Custom Info" 448ms

And I follow "Create Value" 444ms

And I follow "key-label" 526ms

And I enter "key-value" as "value" 55ms

And I click on "Update Key" 643ms

Then I should see a "key-label" text 71ms

And I should see a "key-value" link 11ms

Scenario:
Edit the value
3s 11ms 9

When I follow the left menu "Systems > System List > All" 117ms

And I follow this "sle_minion" link 1s 132ms

And I follow "Custom Info" 444ms

And I follow "key-value" 451ms

And I should see a "Edit Custom Value" text 65ms

And I enter "key-value-edited" as "value" 67ms

And I click on "Update Key" 647ms

Then I should see a "key-label" text 71ms

And I should see a "key-value-edited" link 12ms

Scenario:
Edit the key description
933ms 6

When I follow the left menu "Systems > Custom System Info" 65ms

And I follow "key-label" 280ms

And I enter "key-desc-edited" as "description" 93ms

And I click on "Update Key" 423ms

Then I should see a "key-label" link 12ms

And I should see a "key-desc-edited" text 58ms

Scenario:
Delete the value
3s 62ms 8

When I follow the left menu "Systems > Custom System Info" 61ms

And I follow "key-label" 271ms

And I follow this "sle_minion" link 743ms

And I follow "Custom Info" 434ms

And I follow "key-value-edited" 443ms

And I follow "Delete Value" 433ms

And I click on "Remove Value" 610ms

Then I should see a "No custom information defined for this system." text 64ms

Scenario:
Delete the key
1s 132ms 5

When I follow the left menu "Systems > Custom System Info" 62ms

And I follow "key-label" 269ms

And I follow "Delete Key" 306ms

And I click on "Delete Key" 434ms

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
16ms 1

When I clear browser cookies 16ms

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
22ms 2

Given I retrieve a "javascript" static resource 22ms

Then the response header "X-WebKit-CSP" should not be present < 1ms

@scope_salt
Feature:Salt is configured and running 6s 369ms 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 8ms 4

When I get the contents of the remote file "/etc/salt/master.d/susemanager.conf" 1s 8ms

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 27ms 3

Then salt-api should be listening on local port 9080 675ms

And salt-master should be listening on public port 4505 674ms

And salt-master should be listening on public port 4506 677ms

Scenario:
There are no top.sls files in certain folders
3s 332ms 10

When I run "ls /srv/susemanager/salt/top.sls" on "server" without error control 675ms

Then the command should fail < 1ms

When I run "ls /srv/susemanager/salt/top.sls" on "server" without error control 663ms

Then the command should fail < 1ms

When I run "ls /srv/susemanager/pillar/top.sls" on "server" without error control 657ms

Then the command should fail < 1ms

When I run "ls /usr/share/susemanager/salt/top.sls" on "server" without error control 659ms

Then the command should fail < 1ms

When I run "ls /usr/share/susemanager/pillar/top.sls" on "server" without error control 676ms

Then the command should fail < 1ms

@scope_configuration_channels
Feature:The channels page 22s 813ms 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
574ms 15

When I follow the left menu "Software > Channel List > All" 186ms

Then I should see a "Full Software Channel List" text 113ms

And I should see a "Channel List" link in the left menu 25ms

And I should see a "All" link in the left menu 23ms

And I should see a "Popular" link in the left menu 21ms

And I should see a "My Channels" link in the left menu 20ms

And I should see a "Shared" link in the left menu 25ms

And I should see a "Retired" link in the left menu 20ms

And I should see a "Package Search" link in the left menu 20ms

And I should see a "Manage" link in the left menu 23ms

And I should see a "All" link in the content area 22ms

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 18ms

And I should see a "Retired" link in the content area 17ms

Scenario:
Popular channels
138ms 2

When I follow the left menu "Software > Channel List > Popular" 74ms

Then I should see a "Popular" text 63ms

Scenario:
Check packages in test channel
1s 984ms 10

When I follow the left menu "Software > Channel List > All" 70ms

And I follow "Show All Child Channels" 55ms

And I follow "Fake-RPM-SUSE-Channel" 770ms

And I follow "Packages" 573ms

Then I should see package "andromeda-dummy-2.0-1.1.noarch" 86ms

And I should see package "hoag-dummy-1.1-1.1.i586" 89ms

And I should see package "hoag-dummy-1.1-1.1.x86_64" 83ms

And I should see package "milkyway-dummy-2.0-1.1.i586" 83ms

And I should see package "milkyway-dummy-2.0-1.1.x86_64" 87ms

And I should see package "virgo-dummy-2.0-1.1.noarch" 83ms

Scenario:
Check package metadata
2s 100ms 10

When I follow the left menu "Software > Channel List > All" 67ms

And I follow "Show All Child Channels" 45ms

And I follow "Fake-RPM-SUSE-Channel" 592ms

And I follow "Packages" 577ms

And I follow "andromeda-dummy-2.0-1.1.noarch" 546ms

Then I should see a "This is the andromeda dummy package used for testing SUSE Manager" text 66ms

And I should see a "Fake-RPM-SUSE-Channel" link 11ms

And I should see a "build.opensuse.org" text 63ms

And I should see a "SHA512sum:" text 64ms

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 66ms

Scenario:
Check package dependencies page
2s 469ms 9

When I follow the left menu "Software > Channel List > All" 116ms

And I follow "Show All Child Channels" 47ms

And I follow "Fake-RPM-SUSE-Channel" 655ms

And I follow "Packages" 576ms

And I follow "andromeda-dummy-2.0-1.1.noarch" 544ms

And I follow "Dependencies" 375ms

Then I should see a "pam" text 51ms

And I should see a "rpmlib(PayloadIsXz) <= 5.2-1" text 50ms

And I should see a "andromeda-dummy = 2.0-1.1" text 50ms

Scenario:
Check package change log page
2s 370ms 8

When I follow the left menu "Software > Channel List > All" 106ms

And I follow "Show All Child Channels" 47ms

And I follow "Fake-RPM-SUSE-Channel" 748ms

And I follow "Packages" 567ms

And I follow "andromeda-dummy-2.0-1.1.noarch" 438ms

And I follow "Change Log" 367ms

Then I should see a "mc@suse.de" text 47ms

And I should see a "version 2.0" text 46ms

Scenario:
Check package file list page
2s 455ms 9

When I follow the left menu "Software > Channel List > All" 107ms

And I follow "Show All Child Channels" 44ms

And I follow "Fake-RPM-SUSE-Channel" 656ms

And I follow "Packages" 570ms

And I follow "andromeda-dummy-2.0-1.1.noarch" 539ms

And I follow "File List" 370ms

Then I should see a "This package contains the following files." text 58ms

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 12s 392ms 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 637ms 1

Given I am authorized 1s 637ms

Scenario:
Fail when trying to add a duplicate channel
1s 513ms 10

When I follow the left menu "Software > Manage > Channels" 184ms

And I follow "Create Channel" 372ms

And I enter "Fake-Base-Channel-SUSE-like" as "Channel Name" 99ms

And I enter "fake-base-channel-suse-like" as "Channel Label" 83ms

And I select "None" from "Parent Channel" 60ms

And I select "x86_64" from "Architecture:" 48ms

And I enter "Base channel for testing" as "Channel Summary" 84ms

And I enter "No more desdcription for base channel." as "Channel Description" 93ms

And I click on "Create Channel" 407ms

Then I should see a "The channel name 'Fake-Base-Channel-SUSE-like' is already in use, please enter a different name" text 77ms

Scenario:
Fail when trying to use invalid characters in the channel label
1s 128ms 7

When I follow the left menu "Software > Manage > Channels" 74ms

And I follow "Create Channel" 371ms

And I enter "test123" as "Channel Name" 80ms

And I enter "tesT123" as "Channel Label" 57ms

And I enter "test123" as "Channel Summary" 58ms

And I click on "Create Channel" 410ms

Then I should see a "Invalid channel label, please see the format described below" text 76ms

Scenario:
Fail when trying to use invalid characters in the channel name
1s 78ms 7

When I follow the left menu "Software > Manage > Channels" 78ms

And I follow "Create Channel" 357ms

And I enter "!test123" as "Channel Name" 57ms

And I enter "test123" as "Channel Label" 56ms

And I enter "test123" as "Channel Summary" 59ms

And I click on "Create Channel" 390ms

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
1s 128ms 7

When I follow the left menu "Software > Manage > Channels" 71ms

And I follow "Create Channel" 376ms

And I enter "openSUSE-Leap-15.6-Pool for x86_64" as "Channel Name" 85ms

And I enter "test123" as "Channel Label" 55ms

And I enter "test123" as "Channel Summary" 55ms

And I click on "Create Channel" 406ms

Then I should see a "The channel name 'openSUSE-Leap-15.6-Pool for x86_64' is reserved, please enter a different name" text 76ms

@scc_credentials
Scenario:
Fail when trying to use reserved labels for channels
1s 119ms 7

When I follow the left menu "Software > Manage > Channels" 74ms

And I follow "Create Channel" 377ms

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" 57ms

And I click on "Create Channel" 395ms

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
1s 485ms 7

When I follow the left menu "Software > Manage > Channels" 72ms

And I follow "Create Channel" 373ms

And I enter "aaaSLE-12-Cloud-Compute5-Pool for x86_64" as "Channel Name" 92ms

And I enter "sle-we12aaa-pool-x86_64-sap" as "Channel Label" 77ms

And I enter "test123" as "Channel Summary" 55ms

And I click on "Create Channel" 732ms

Then I should see a "Channel aaaSLE-12-Cloud-Compute5-Pool for x86_64 created." text 80ms

@scc_credentials
Scenario:
Fail when trying to change the channel name to a reserved name
1s 408ms 5

When I follow the left menu "Software > Manage > Channels" 72ms

And I follow "aaaSLE-12-Cloud-Compute5-Pool for x86_64" 572ms

And I enter "openSUSE-Leap-15.6-Pool for x86_64" as "Channel Name" 122ms

And I click on "Update Channel" 567ms

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 892ms 6

When I follow the left menu "Software > Manage > Channels" 71ms

And I follow "aaaSLE-12-Cloud-Compute5-Pool for x86_64" 548ms

And I follow "Delete Channel" 484ms

And I check "unsubscribeSystems" 80ms

And I click on "Delete Channel" 621ms

Then I should see a "Channel aaaSLE-12-Cloud-Compute5-Pool for x86_64 has been deleted." text 86ms

@scope_visualization
Feature:Left Menu Filter 2s 590ms 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 798ms 1

Given I am authorized for the "Admin" section 1s 798ms

Scenario:
Search a word and expect the right result
113ms 2

When I enter "Admin" as the left menu search field 88ms

Then I should see a "Admin" link in the left menu 25ms

Scenario:
Search a partial word and expect the right result
125ms 2

When I enter "Formula" as the left menu search field 99ms

Then I should see a "Formula Catalog" link in the left menu 26ms

Scenario:
Search a word with a different case and expect the right result
114ms 2

When I enter "saLT" as the left menu search field 91ms

Then I should see a "Salt" link in the left menu 23ms

@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
308ms 3

When I enter "Uyuni" as the left menu search field 100ms

Then I should see a "Uyuni Server" text 82ms

And I should see a "Uyuni Proxy" text 125ms

Scenario:
Search a non-existing word and expect no results
130ms 2

When I enter "Null" as the left menu search field 121ms

Then I should see left menu empty 8ms

@scope_api
Feature:API "channel" namespace and sub-namespaces 10s 140ms 10

Scenario:
Create a custom software channel
818ms 2

When I create the following channels: 396ms
LABEL NAME SUMMARY ARCH PARENT
foobar foobar foobar channel-x86_64

Then "foobar" should get listed with a call of listSoftwareChannels 421ms

Scenario:
Create a repository
2s 293ms 4

When I create a repo with label "foobar" and url 373ms

And I associate repo "foobar" with channel "foobar" 660ms

Then channel "foobar" should have attribute "last_modified" that is a date 645ms

And channel "foobar" should not have attribute "yumrepo_last_sync" 613ms

Scenario:
Create a custom software channel as the child of another one
1s 516ms 3

When I create the following channels: 444ms
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 433ms

And "foobar" should be the parent channel of "foobar-child" 638ms

Scenario:
List software channels
412ms 1

Then something should get listed with a call of listSoftwareChannels 412ms

Scenario:
Delete a child software channel
901ms 2

When I delete the software channel with label "foobar-child" 497ms

Then "foobar-child" should not get listed with a call of listSoftwareChannels 403ms

Scenario:
Delete a software channel
2s 233ms 3

When I delete the repo with label "foobar" 364ms

And I delete the software channel with label "foobar" 1s 455ms

Then "foobar" should not get listed with a call of listSoftwareChannels 413ms

Scenario:
Check last synchronization of a synced channel
416ms 1

Then channel "fake-child-channel-i586" should have attribute "yumrepo_last_sync" that is a date 416ms

@rhlike_minion
Scenario:
Verify if a channel is modular via the API
767ms 2

When I verify channel "fake-base-channel-appstream" is modular via the API 375ms

And I verify channel "fake-rpm-suse-channel" is not modular via the API 392ms

@rhlike_minion
Scenario:
List modular channels via the API
375ms 1

When channel "Fake-Base-Channel-AppStream" is present in the modular channels listed via the API 375ms

@rhlike_minion
Scenario:
List available module streams for a given channel via the API
403ms 1

When "scorpio" module streams "2.0, 2.1" are available for channel "fake-base-channel-appstream" via the API 403ms

@scope_visualization
Feature:Patches page 12s 63ms 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 725ms 1

Given I am authorized 1s 725ms

Scenario:
Patches left menu
502ms 11

When I follow the left menu "Patches > Patch List > Relevant" 196ms

Then I should see a "Patches Relevant to Your Systems" text 120ms

And I should see a "Relevant" link in the left menu 28ms

And I should see a "All" link in the left menu 28ms

And I should see a "Advanced Search" link in the left menu 31ms

And I should see a "Manage Patches" link in the left menu 29ms

And I should see a "Clone Patches" link in the left menu 24ms

And I should see a "Bugfix Patches" link 12ms

And I should see a "Enhancement Patches" link 11ms

And I should see a "Security Patches" link 12ms

And I should see a Sign Out link 7ms

Scenario:
Create new bugfix patch with bnc URL
2s 757ms 18

When I follow the left menu "Patches > Manage Patches" 67ms

And I follow "Create Patch" 335ms

When I enter "Test Patch" as "synopsis" 85ms

And I enter "Test Advisory" as "advisoryName" 96ms

And I enter "Test Product" as "product" 85ms

And I enter "test@test.org" as "errataFrom" 87ms

And I enter "Test Topic" as "topic" 78ms

And I enter "Test Description" as "description" 87ms

And I enter "Test Solution" as "solution" 81ms

And I enter "620212" as "buglistId" 69ms

And I enter "Test Summary" as "buglistSummary" 82ms

And I enter "https://bugzilla.opensuse.org/show_bug.cgi?id=620212" as "buglistUrl" 182ms

And I enter "test,keywords" as "keywords" 81ms

And I enter "Test Reference" as "refersTo" 82ms

And I enter "Test Note" as "notes" 74ms

And I check test channel 65ms

And I click on "Create Patch" 1s 35ms

Then I should see a "Patch: Test Advisory-1" text 78ms

Scenario:
Create new enhancement patch with no bnc URL
1s 619ms 17

When I follow the left menu "Patches > Manage Patches" 63ms

And I follow "Create Patch" 315ms

When I enter "Enhancement Patch" as "synopsis" 87ms

And I enter "Enhancement Advisory" as "advisoryName" 94ms

And I select "Product Enhancement Advisory" from "advisoryType" 72ms

And I enter "Enhancement Product" as "product" 97ms

And I enter "Enhancement Topic" as "topic" 93ms

And I enter "Enhancement Description" as "description" 97ms

And I enter "Enhancement Solution" as "solution" 90ms

And I enter "1234" as "buglistId" 58ms

And I enter "Enhancement Summary" as "buglistSummary" 90ms

And I enter "Enhancement,keywords" as "keywords" 95ms

And I enter "Enhancement Reference" as "refersTo" 92ms

And I enter "Enhancement Note" as "notes" 83ms

And I check test channel 56ms

And I click on "Create Patch" 56ms

Then I should see a "Patch: Enhancement Advisory-1" text 75ms

Scenario:
Delete enhancement patch
1s 424ms 5

When I follow the left menu "Patches > Manage Patches" 62ms

And I check "Enhancement Advisory" patch 58ms

And I click on "Delete Patches" 576ms

And I click on "Confirm" 613ms

Then I should see a "Successfully deleted 1 patches." text 113ms

Scenario:
Verify patch presence in web UI
1s 695ms 15

When I follow the left menu "Patches > Patch List > All" 156ms

And I follow "Bugfix Patches" in the content area 73ms

And I enter "Test Patch" as the filtered synopsis 51ms

And I click on the filter button 477ms

And I follow "Test Advisory" 431ms

Then I should see a "Test Patch" text 62ms

And I should see a "test@test.org" text 60ms

And I should see a "Test Topic" text 58ms

And I should see a "Test Description" text 63ms

And I should see a "Test Solution" text 58ms

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 59ms

And I should see a "Test Note" text 59ms

Scenario:
Assert that patch is now in test base channel
953ms 4

When I follow the left menu "Software > Channel List > All" 174ms

And I follow "Fake-Base-Channel-SUSE-like" 650ms

And I follow "Patches" in the content area 66ms

Then I should see a "Test Patch" text 61ms

Scenario:
Delete patch
1s 385ms 5

When I follow the left menu "Patches > Manage Patches" 104ms

And I check "Test Advisory" patch 56ms

And I click on "Delete Patches" 518ms

And I click on "Confirm" 598ms

Then I should see a "Successfully deleted 1 patches." text 106ms

@scc_credentials @scope_content_lifecycle_management
Feature:Content lifecycle 10m 18s 878ms 46 4

Scenario:
Log in as org admin user
1s 813ms 1

Given I am authorized 1s 813ms

Scenario:
Create CLM filter to remove all fonts packages
3s 142ms 10

When I follow the left menu "Content Lifecycle > Filters" 120ms

And I click on "Create Filter" 142ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 12ms

Then I should see a "Create a new filter" text 61ms

And I enter "remove fonts packages" as "filter_name" 130ms

And I select "Package (Name)" from "type" 1s 135ms

And I select "contains" from "matcher" 1s 110ms

And I enter "fonts" as "name" 78ms

And I click on "Save" in "Create a new filter" modal 292ms

Then I should see a "remove fonts packages" text 59ms

Scenario:
Create a content lifecycle project
1s 414ms 9

When I follow the left menu "Content Lifecycle > Projects" 66ms

And I follow "Create Project" 364ms

Then I should see a "Create a new Content Lifecycle Project" text 54ms

And I should see a "Project Properties" text 51ms

When I enter "clp_label" as "label" 68ms

And I enter "clp_name" as "name" 64ms

And I enter "clp_desc" as "description" 63ms

And I click on "Create" 66ms

And I wait until I see "Content Lifecycle Project - clp_name" text 615ms

Scenario:
Verify the content lifecycle project page
888ms 9

When I follow the left menu "Content Lifecycle > Projects" 63ms

Then I should see a "clp_name" text 56ms

And I should see a "clp_desc" text 53ms

When I follow "clp_name" 403ms

Then I should see a "Project Properties" text 63ms

And I should see a "Versions history" text 64ms

And I should see a "Sources" text 60ms

And I should see a "Filters" text 63ms

And I should see a "Environment Lifecycle" text 60ms

@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 172ms 8

When I follow the left menu "Content Lifecycle > Projects" 61ms

And I follow "clp_name" 395ms

And I click on "Attach/Detach Sources" 77ms

And I select "openSUSE Tumbleweed (x86_64)" from "selectedBaseChannel" 1s 120ms

And I wait until I see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" text 94ms

And I click on "Save" 63ms

And I wait until I see "openSUSE Tumbleweed (x86_64)" text 299ms

Then I should see a "Version 1: (draft - not built) - Check the changes below" text 60ms

@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
573ms 4

When I follow the left menu "Content Lifecycle > Projects" 59ms

And I follow "clp_name" 380ms

Then I should see a "openSUSE Tumbleweed (x86_64)" text 64ms

And I should see a "Build (1)" text 68ms

Scenario:
Add fonts packages filter to the project
1s 313ms 10

When I follow the left menu "Content Lifecycle > Projects" 58ms

And I follow "clp_name" 390ms

Then I should see a "Content Lifecycle Project - clp_name" text 67ms

When I click on "Attach/Detach Filters" 69ms

And I check the "remove fonts packages" CLM filter 192ms

And I click on "Save" 53ms

And I wait until I see "Deny" text 295ms

Then I should see a "remove fonts packages" text 67ms

When I follow the left menu "Content Lifecycle > Filters" 57ms

Then I should see a "clp_name" text 60ms

Scenario:
Add environments to the project
3s 942ms 25

When I follow the left menu "Content Lifecycle > Projects" 61ms

And I follow "clp_name" 405ms

Then I should see a "No environments created" text 73ms

When I click on "Add Environment" 73ms

And I enter "dev_name" as "name" 79ms

And I enter "dev_label" as "label" 97ms

And I enter "dev_desc" as "description" 68ms

And I click on "Save" 58ms

Then I wait until I see "dev_name" text 304ms

And I should see a "dev_desc" text 70ms

When I click on "Add Environment" 64ms

And I enter "prod_name" as "name" 78ms

And I enter "prod_label" as "label" 78ms

And I enter "prod_desc" as "description" 70ms

And I click on "Save" 53ms

Then I wait until I see "prod_name" text 321ms

And I should see a "prod_desc" text 75ms

When I click on "Add Environment" 65ms

And I enter "qa_name" as "name" 75ms

And I enter "qa_label" as "label" 73ms

And I enter "qa_desc" as "description" 72ms

And I select "prod_name" from "predecessorLabel" 1s 121ms

And I click on "Save" 61ms

Then I wait until I see "qa_name" text 354ms

And I should see a "qa_desc" text 82ms

@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
36s 516ms 9

When I follow the left menu "Content Lifecycle > Projects" 60ms

And I follow "clp_name" 462ms

Then I should see a "not built" text in the environment "qa_name" 22ms

When I click on "Build (2)" 66ms

Then I should see a "Version 1 history" text 91ms

When I enter "test version message 1" as "message" 64ms

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" 325ms

And I wait at most 600 seconds until I see "Built" text in the environment "dev_name" 35s 366ms

Scenario:
Promote the sources in the project
1m 57s 432ms 15

When I follow the left menu "Content Lifecycle > Projects" 63ms

Then I should see a "clp_name" text 59ms

And I should see a "clp_desc" text 56ms

And I should see a "dev_name > qa_name > prod_name" text 55ms

When I follow "clp_name" 422ms

Then I should see a "qa_desc" text in the environment "qa_name" 20ms

And I should see a "not built" text in the environment "qa_name" 18ms

When I click promote from Development to QA 62ms

Then I should see a "Version 1: test version message 1" text 92ms

And I click on "Promote environment" in "Promote version 1 into qa_name" modal 337ms

Then I wait at most 600 seconds until I see "Built" text in the environment "qa_name" 55s 366ms

When I click promote from QA to Production 66ms

Then I should see a "Version 1: test version message 1" text 102ms

And I click on "Promote environment" in "Promote version 1 into prod_name" modal 321ms

Then I wait at most 600 seconds until I see "Built" text in the environment "prod_name" 1m 385ms

@skip_if_github_validation
Scenario:
Add new sources and promote again
3m 847ms 27

When I follow the left menu "Content Lifecycle > Projects" 83ms

And I follow "clp_name" 413ms

Then I should see a "Build (0)" text 105ms

When I click on "Attach/Detach Sources" 97ms

And I uncheck "Vendors" 10s 950ms

And I enter "Fake-Base-Channel-SUSE-like" in the placeholder "Search a channel" 126ms

And I add the "Fake-Base-Channel-SUSE-like" channel to sources 76ms

And I click on "Save" 70ms

Then I wait until I see "Fake-Base-Channel-SUSE-like" text 515ms

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 96ms

When I click on "Build (1)" 67ms

Then I wait until I see "Version 2 history" text 98ms

When I enter "test version message 2" as "message" 70ms

And I click the environment build button 56ms

Then I wait until I see "Version 2: test version message 2" text in the environment "dev_name" 385ms

And I wait at most 600 seconds until I see "Built" text in the environment "dev_name" 45s 429ms

When I click promote from Development to QA 64ms

Then I should see a "Version 2: test version message 2" text 105ms

And I click on "Promote environment" in "Promote version 2 into qa_name" modal 435ms

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 459ms

When I click promote from QA to Production 62ms

Then I should see a "Version 2: test version message 2" text 102ms

And I click on "Promote environment" in "Promote version 2 into prod_name" modal 446ms

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 439ms

Scenario:
Create a CLM filter of type Package(NEVRA) that allows packages whose version and release number are lower to a defined one
13s 395ms 15

When I follow the left menu "Content Lifecycle > Filters" 83ms

And I click on "Create Filter" 73ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 12ms

Then I should see a "Create a new filter" text 67ms

When I enter "mercury" as "filter_name" 77ms

And I select "Package (NEVRA)" from "type" 1s 134ms

And I select "lower" from "matcher" 1s 122ms

And I enter "mercury" as "Package Name" 92ms

And I enter "mercury" as "Epoch" 91ms

And I enter "0.0.0" as "version" 73ms

And I enter "0.0.0" as "Release" 83ms

And I enter "x86_64" as "Architecture" 90ms

And I check radio button "Allow" 10s 88ms

And I click on "Save" in "Create a new filter" modal 246ms

Then I should see a "Filter created successfully" text 59ms

Scenario:
Create a CLM filter of type Package(NEVRA) that denys packages whose version and release number are lower to a defined one
3s 226ms 15

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 59ms

And I click on "Create Filter" 91ms

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" 57ms

And I select "Package (NEVRA)" from "type" 1s 120ms

And I select "lower" from "matcher" 1s 103ms

And I enter "venus" as "Package Name" 74ms

And I enter "venus" as "Epoch" 73ms

And I enter "0.0.0" as "version" 66ms

And I enter "0.0.0" as "Release" 73ms

And I enter "x86_64" as "Architecture" 79ms

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 62ms

Scenario:
Create CLM filter that allows packages of type Package (Provides Name)
2s 906ms 10

When I follow the left menu "Content Lifecycle > Filters" 62ms

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 71ms

When I enter "cereal" as "filter_name" 59ms

And I select "Package (Provides Name)" from "type" 1s 120ms

And I select "provides name" from "matcher" 1s 103ms

And I enter "cereal" as "Provides Name" 82ms

And I click on "Save" in "Create a new filter" modal 270ms

Then I should see a "Filter created successfully" text 65ms

Scenario:
Create CLM filter that denys packages of type Package (Provides Name)
2s 899ms 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 56ms

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 76ms

When I enter "potato" as "filter_name" 60ms

And I select "Package (Provides Name)" from "type" 1s 122ms

And I select "provides name" from "matcher" 1s 111ms

And I enter "potato" as "Provides Name" 77ms

And I check radio button "Deny" 19ms

And I click on "Save" in "Create a new filter" modal 233ms

Then I should see a "Filter created successfully" text 68ms

Scenario:
Create CLM filter of type Package (Build date) that allows packages whose date is lower than a defined one
12s 933ms 10

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 8ms

Then I should see a "Create a new filter" text 79ms

When I enter "cherry" as "filter_name" 61ms

And I select "Package (Build date)" from "type" 1s 129ms

And I select "lower" from "matcher" 1s 139ms

And I check radio button "Allow" 10s 64ms

And I click on "Save" in "Create a new filter" modal 253ms

Then I should see a "Filter created successfully" text 70ms

Scenario:
Create CLM filter of type Package (Build date) that denys packages whose date is lower than a defined one
2s 859ms 10

Warning: Radio button 'Deny' 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 9ms

Then I should see a "Create a new filter" text 77ms

When I enter "drummer" as "filter_name" 63ms

And I select "Package (Build date)" from "type" 1s 120ms

And I select "lower" from "matcher" 1s 111ms

And I check radio button "Deny" 17ms

And I click on "Save" in "Create a new filter" modal 256ms

Then I should see a "Filter created successfully" text 78ms

Scenario:
Create CLM filter of type Patch(Advisory Name) that allows patches that are equal to a defined one
13s 17ms 11

When I follow the left menu "Content Lifecycle > Filters" 60ms

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 84ms

When I enter "africa-patch" as "filter_name" 78ms

And I select "Patch (Advisory Name)" from "type" 1s 121ms

And I select "equals" from "matcher" 1s 106ms

And I enter "africa" as "Advisory name" 83ms

And I check radio button "Allow" 10s 65ms

And I click on "Save" in "Create a new filter" modal 259ms

Then I should see a "Filter created successfully" text 78ms

Scenario:
Create CLM filter of type Patch(Advisory Name) that denys patches that are equal to a defined one
2s 969ms 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 73ms

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 88ms

When I enter "asia-patch" as "filter_name" 74ms

And I select "Patch (Advisory Name)" from "type" 1s 119ms

And I select "equals" from "matcher" 1s 107ms

And I enter "asia" as "Advisory name" 78ms

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 82ms

Scenario:
Create CLM filter of type Patch(Advisory Type) that allows Security Advisory patches that are equal to a defined one
12s 951ms 11

Warning: Radio button 'Security Advisory' is already checked

When I follow the left menu "Content Lifecycle > Filters" 64ms

And I click on "Create Filter" 67ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 10ms

Then I should see a "Create a new filter" text 93ms

When I enter "key" as "filter_name" 55ms

And I select "Patch (Advisory Type)" from "type" 1s 132ms

And I select "equals" from "matcher" 1s 112ms

And I check radio button "Security Advisory" 20ms

And I check radio button "Allow" 10s 66ms

And I click on "Save" in "Create a new filter" modal 243ms

Then I should see a "Filter created successfully" text 83ms

Scenario:
Create CLM filter of type Patch(Advisory Type) that denys Security Advisory patches that are equal to a defined one
2s 938ms 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" 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 8ms

Then I should see a "Create a new filter" text 96ms

When I enter "geminis-patch" as "filter_name" 82ms

And I select "Patch (Advisory Type)" from "type" 1s 129ms

And I select "equals" from "matcher" 1s 117ms

And I check radio button "Security Advisory" 17ms

And I check radio button "Deny" 17ms

And I click on "Save" in "Create a new filter" modal 253ms

Then I should see a "Filter created successfully" text 91ms

Scenario:
Create CLM filter of type Patch(Synopsis) that allows patches that that are equal to a defined one
13s 73ms 11

When I follow the left menu "Content Lifecycle > Filters" 64ms

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 99ms

When I enter "aries-patch" as "filter_name" 75ms

And I select "Patch (Synopsis)" from "type" 1s 126ms

And I select "equals" from "matcher" 1s 114ms

And I enter "aries" as "Synopsis" 82ms

And I check radio button "Allow" 10s 82ms

And I click on "Save" in "Create a new filter" modal 256ms

Then I should see a "Filter created successfully" text 95ms

Scenario:
Create CLM filter of type Patch(Synopsis) that denys patches that are equal to a defined one
3s 1ms 11

Warning: Radio button 'Deny' 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 9ms

Then I should see a "Create a new filter" text 100ms

When I enter "andromeda-patch" as "filter_name" 88ms

And I select "Patch (Synopsis)" from "type" 1s 114ms

And I select "equals" from "matcher" 1s 105ms

And I enter "andromeda" as "Synopsis" 91ms

And I check radio button "Deny" 17ms

And I click on "Save" in "Create a new filter" modal 251ms

Then I should see a "Filter created successfully" text 96ms

Scenario:
Create CLM filter of type Patch(Keyword) that allows patches that contains Package Manager Restart Required keyword in its name
23s 72ms 11

When I follow the left menu "Content Lifecycle > Filters" 57ms

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 98ms

When I enter "mars-patch" as "filter_name" 73ms

And I select "Patch (Keyword)" from "type" 1s 131ms

And I select "contains" from "matcher" 1s 115ms

And I check radio button "Package Manager Restart Required" 10s 82ms

And I check radio button "Allow" 10s 76ms

And I click on "Save" in "Create a new filter" modal 264ms

Then I should see a "Filter created successfully" text 95ms

Scenario:
Create CLM filter of type Patch(Keyword) that denys patches that contains Package Manager Restart Required Keyword in its name
13s 17ms 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 56ms

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 100ms

When I enter "eurasia-patch" as "filter_name" 83ms

And I select "Patch (Keyword)" from "type" 1s 121ms

And I select "contains" from "matcher" 1s 105ms

And I check radio button "Package Manager Restart Required" 10s 78ms

And I check radio button "Deny" 19ms

And I click on "Save" in "Create a new filter" modal 277ms

Then I should see a "Filter created successfully" text 98ms

Scenario:
Create CLM filter of type Patch(Issue date) that allows patches whose date is greater or equal than a defined one
13s 37ms 10

When I follow the left menu "Content Lifecycle > Filters" 59ms

And I click on "Create Filter" 65ms

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 105ms

When I enter "milkyway-patch" as "filter_name" 86ms

And I select "Patch (Issue date)" from "type" 1s 134ms

And I select "greater or equal" from "matcher" 1s 110ms

And I check radio button "Allow" 10s 73ms

And I click on "Save" in "Create a new filter" modal 290ms

Then I should see a "Filter created successfully" text 102ms

Scenario:
Create CLM filter of type Patch(Issue date) that denys patches whose date is greater or equal than a defined one
3s 126ms 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 111ms

When I enter "venus-patch" as "filter_name" 82ms

And I select "Patch (Issue date)" from "type" 1s 129ms

And I select "greater or equal" from "matcher" 1s 113ms

When I enter "solar" as "filter_name" 139ms

And I check radio button "Deny" 16ms

And I click on "Save" in "Create a new filter" modal 282ms

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 181ms 11

When I follow the left menu "Content Lifecycle > Filters" 64ms

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 112ms

When I enter "Triangulum-patch" as "filter_name" 89ms

And I select "Patch (Contains Package Name)" from "type" 1s 131ms

And I select "equals" from "matcher" 1s 116ms

When I enter "Triangulum-patch" as "Package Name" 126ms

And I check radio button "Allow" 10s 70ms

And I click on "Save" in "Create a new filter" modal 285ms

Then I should see a "Filter created successfully" text 106ms

Scenario:
Create CLM filter of type Patch(Contains Package Name) that denys patches that are equal to a specific one
3s 102ms 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 63ms

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 122ms

When I enter "Pinwheel-patch" as "filter_name" 85ms

And I select "Patch (Contains Package Name)" from "type" 1s 124ms

And I select "equals" from "matcher" 1s 104ms

When I enter "Pinwheel-patch" as "Package Name" 111ms

And I check radio button "Deny" 17ms

And I click on "Save" in "Create a new filter" modal 280ms

Then I should see a "Filter created successfully" text 115ms

Scenario:
Create CLM filter that allows patches of type Patch(Contains Package Name) that matches to a specific one
13s 190ms 11

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 118ms

When I enter "Sunflower-patch" as "filter_name" 93ms

And I select "Patch (Contains Package Name)" from "type" 1s 123ms

And I select "matches" from "matcher" 1s 110ms

When I enter "Sunflower-patch" as "Package Name" 117ms

And I check radio button "Allow" 10s 59ms

And I click on "Save" in "Create a new filter" modal 312ms

Then I should see a "Filter created successfully" text 118ms

Scenario:
Create CLM filter of type Patch(Contains Package Name) that denys patches that matches to a specific one
3s 214ms 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 63ms

And I click on "Create Filter" 129ms

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 122ms

When I enter "Whirlpool-patch" as "filter_name" 92ms

And I select "Patch (Contains Package Name)" from "type" 1s 127ms

And I select "matches" from "matcher" 1s 104ms

When I enter "Whirlpool-patch" as "Package Name" 119ms

And I check radio button "Deny" 17ms

And I click on "Save" in "Create a new filter" modal 310ms

Then I should see a "Filter created successfully" text 117ms

Scenario:
Create CLM filter of type Patch(Contains Package Provides Name) that allows patches with a specific name
13s 237ms 11

When I follow the left menu "Content Lifecycle > Filters" 64ms

And I click on "Create Filter" 69ms

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 126ms

When I enter "Antennae-patch" as "filter_name" 86ms

And I select "Patch (Contains Package Provides Name)" from "type" 1s 126ms

And I select "provides name" from "matcher" 1s 114ms

When I enter "Antennae-patch" as "Package Provides Name" 120ms

And I check radio button "Allow" 10s 70ms

And I click on "Save" in "Create a new filter" modal 329ms

Then I should see a "Filter created successfully" text 120ms

Scenario:
Create CLM filter of type Patch(Contains Package Provides Name) that denys patches with a specific name
3s 170ms 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 67ms

And I click on "Create Filter" 101ms

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 "hat-patch" as "filter_name" 69ms

And I select "Patch (Contains Package Provides Name)" from "type" 1s 131ms

And I select "provides name" from "matcher" 1s 110ms

When I enter "hat-patch" as "Package Provides Name" 93ms

And I check radio button "Deny" 16ms

And I click on "Save" in "Create a new filter" modal 316ms

Then I should see a "Filter created successfully" text 122ms

Scenario:
Create CLM filter of type Patch(Contains Package) that allows patches whose version is lower than a specific one
13s 602ms 14

When I follow the left menu "Content Lifecycle > Filters" 63ms

And I click on "Create Filter" 95ms

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 133ms

When I enter "Hubble-patch" as "filter_name" 137ms

And I select "Patch (Contains Package)" from "type" 1s 128ms

And I select "version lower than" from "matcher" 1s 118ms

When I enter "Hubble-patch" as "Package Name" 109ms

And I enter "Hubble-patch" as "Epoch" 110ms

And I enter "0.0.0" as "Version" 79ms

And I enter "0.0.0" as "Release" 84ms

And I check radio button "Allow" 10s 78ms

And I click on "Save" in "Create a new filter" modal 329ms

Then I should see a "Filter created successfully" text 124ms

Scenario:
Create CLM filter of type Patch(Contains Package) that denys patches whose version is lower than a specific one
3s 428ms 14

Warning: Radio button 'Deny' is already checked

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 8ms

Then I should see a "Create a new filter" text 134ms

When I enter "galaxy-patch" as "filter_name" 79ms

And I select "Patch (Contains Package)" from "type" 1s 129ms

And I select "version lower than" from "matcher" 1s 118ms

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" 70ms

And I enter "0.0.0" as "Release" 77ms

And I check radio button "Deny" 16ms

And I click on "Save" in "Create a new filter" modal 325ms

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 527ms 14

When I follow the left menu "Content Lifecycle > Filters" 63ms

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 137ms

When I enter "earth-patch" as "filter_name" 75ms

And I select "Patch (Contains Package)" from "type" 1s 126ms

And I select "version lower or equal" from "matcher" 1s 124ms

When I enter "earth-patch" as "Package Name" 101ms

And I enter "earth-patch" as "Epoch" 97ms

And I enter "0.0.0" as "Version" 72ms

And I enter "0.0.0" as "Release" 77ms

And I check radio button "Allow" 10s 78ms

And I click on "Save" in "Create a new filter" modal 363ms

Then I should see a "Filter created successfully" text 129ms

Scenario:
Create CLM filter of type Patch(Contains Package) that denys patches whose version is lower or equal than a specific one
3s 444ms 14

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 60ms

And I click on "Create Filter" 73ms

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 146ms

When I enter "moon-patch" as "filter_name" 74ms

And I select "Patch (Contains Package)" from "type" 1s 121ms

And I select "version lower or equal" from "matcher" 1s 110ms

When I enter "moon-patch" as "Package Name" 106ms

And I enter "moon-patch" as "Epoch" 95ms

And I enter "0.0.0" as "Version" 71ms

And I enter "0.0.0" as "Release" 74ms

And I check radio button "Deny" 17ms

And I click on "Save" in "Create a new filter" modal 353ms

Then I should see a "Filter created successfully" text 130ms

Scenario:
Create CLM filter to enable Ruby 2.7 module
3s 288ms 11

When I follow the left menu "Content Lifecycle > Filters" 66ms

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 145ms

And I enter "ruby 2.7 module" as "filter_name" 87ms

And I select "Module (Stream)" from "type" 1s 122ms

And I select "equals" from "matcher" 1s 131ms

And I enter "ruby" as "moduleName" 85ms

And I enter "2.7" as "moduleStream" 63ms

And I click on "Save" in "Create a new filter" modal 366ms

Then I should see a "Filter created successfully" text 139ms

Scenario:
Create CLM filter that allows Product Temporary Fix (All)
3s 118ms 10

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 68ms

And I click on "Create Filter" 83ms

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 145ms

When I enter "mars" as "filter_name" 57ms

And I select "Product Temporary Fix (All)" from "type" 1s 131ms

And I select "all" from "matcher" 1s 106ms

And I check radio button "Deny" 18ms

And I click on "Save" in "Create a new filter" modal 360ms

Then I should see a "Filter created successfully" text 137ms

Scenario:
Create CLM filter that denys Product Temporary Fix (All)
3s 133ms 10

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 62ms

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 145ms

When I enter "mercury-patch" as "filter_name" 87ms

And I select "Product Temporary Fix (All)" from "type" 1s 130ms

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 359ms

Then I should see a "Filter created successfully" text 131ms

Scenario:
Create CLM filter of type Product Temporary Fix (Number) that allows packages of a version lower than a specific one
13s 288ms 11

When I follow the left menu "Content Lifecycle > Filters" 64ms

And I click on "Create Filter" 164ms

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 "jupiter-patch" as "filter_name" 84ms

And I select "Product Temporary Fix (Number)" from "type" 1s 128ms

And I select "lower" from "matcher" 1s 116ms

And I enter "1" as "Number" 69ms

And I check radio button "Allow" 10s 62ms

And I click on "Save" in "Create a new filter" modal 319ms

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 146ms 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 60ms

And I click on "Create Filter" 73ms

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 141ms

When I enter "pluto-patch" as "filter_name" 76ms

And I select "Product Temporary Fix (Number)" from "type" 1s 121ms

And I select "lower" from "matcher" 1s 108ms

And I enter "2" as "Number" 65ms

And I check radio button "Deny" 17ms

And I click on "Save" in "Create a new filter" modal 341ms

Then I should see a "Filter created successfully" text 130ms

@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 253ms 11

When I follow the left menu "Content Lifecycle > Filters" 65ms

And I click on "Create Filter" 72ms

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 140ms

When I enter "comet-patch" as "filter_name" 83ms

And I select "Product Temporary Fix (Fixes Package Name)" from "type" 1s 125ms

And I select "equals" from "matcher" 1s 124ms

And I enter "comet-patch" as "Package Name" 105ms

And I check radio button "Allow" 10s 68ms

And I click on "Save" in "Create a new filter" modal 323ms

Then I should see a "Filter created successfully" text 134ms

Scenario:
Cleanup: remove the Content Lifecycle Management project
1s 212ms 5

When I follow the left menu "Content Lifecycle > Projects" 63ms

And I follow "clp_name" 719ms

And I click on "Delete" 81ms

And I click on "Delete" in "Delete Project" modal 98ms

Then I should not see a "clp_name" text 250ms

Scenario:
Cleanup: remove the CLM filters
4s 415ms 32

When I follow the left menu "Content Lifecycle > Filters" 57ms

And I click on "Select unused" 129ms

And I click on "Delete" 105ms

Then I should not see a "remove fonts packages" text 142ms

And I should not see a "africa-patch" text 2s 632ms

And I should not see a "andromeda-patch" text 50ms

And I should not see a "Antennae-patch" text 48ms

And I should not see a "aries-patch" text 50ms

And I should not see a "asia-patch" text 52ms

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 48ms

And I should not see a "drummer" text 48ms

And I should not see a "earth-patch" text 48ms

And I should not see a "galaxy-patch" text 48ms

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 54ms

And I should not see a "mars-patch" text 49ms

And I should not see a "mercury" text 49ms

And I should not see a "milkyway-patch" text 50ms

And I should not see a "moon-patch" text 49ms

And I should not see a "Pinwheel-patch" text 49ms

And I should not see a "pluto-patch" text 49ms

And I should not see a "solar" text 48ms

And I should not see a "Sunflower-patch" text 49ms

And I should not see a "Triangulum-patch" text 55ms

And I should not see a "venus" text 49ms

And I should not see a "Whirlpool-patch" text 51ms

And I should not see a "remove fonts packages" text 49ms

And I should not see a "ruby 2.7 module" text 50ms

And I should not see a "key" text 51ms

@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 439ms 3

When I delete these channels with spacewalk-remove-channel: 1s 446ms
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 992ms

Then I shouldn't get "clp_label" < 1ms

@scope_recurring_actions
Feature:Change the schedule of a task 40s 295ms 4

Scenario:
Log in as admin user
1s 951ms 1

Given I am authorized for the "Admin" section 1s 951ms

Scenario:
Change the schedule of task sandbox-cleanup-default to weekly
13s 700ms 10

When I follow the left menu "Admin > Task Schedules" 122ms

And I follow "sandbox-cleanup-default" 1s 200ms

And I check radio button "weekly" 10s 64ms

And I select "Friday" from "date_day_week" 63ms

And I click on "Update Schedule" 679ms

Then I should see a "Schedule sandbox-cleanup-default has been updated." text 85ms

When I follow the left menu "Admin > Task Schedules" 65ms

And I follow "sandbox-cleanup-default" 1s 322ms

Then I should see a "Friday" text 80ms

And radio button "weekly" should be checked 15ms

Scenario:
Change the schedule of task sandbox-cleanup-default to monthly
11s 888ms 9

When I follow the left menu "Admin > Task Schedules" 58ms

And I follow "sandbox-cleanup-default" 388ms

And I check radio button "monthly" 10s 76ms

And I select "17" from "date_day_month" 63ms

And I click on "Update Schedule" 751ms

Then I should see a "Schedule sandbox-cleanup-default has been updated." text 85ms

When I follow the left menu "Admin > Task Schedules" 62ms

And I follow "sandbox-cleanup-default" 387ms

Then radio button "monthly" should be checked 15ms

Scenario:
Change the schedule of task sandbox-cleanup-default back to daily
12s 756ms 8

When I follow the left menu "Admin > Task Schedules" 58ms

And I follow "sandbox-cleanup-default" 1s 308ms

And I check radio button "daily" 10s 78ms

And I click on "Update Schedule" 746ms

Then I should see a "Schedule sandbox-cleanup-default has been updated." text 88ms

When I follow the left menu "Admin > Task Schedules" 61ms

And I follow "sandbox-cleanup-default" 399ms

Then radio button "daily" should be checked 15ms

@scope_visualization
Feature:Test the notification/notification-messages feature 12s 872ms 4

Scenario:
Log in as org admin user
1s 686ms 1

Given I am authorized 1s 686ms

Scenario:
Check the unread notification counter is correct
10s 403ms 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 251ms

Then I follow "Unread Messages" 61ms

And the notification badge and the table should count the same amount of messages 10s 20ms

Scenario:
Delete notification-messages
392ms 5

There are no notification messages, nothing to do then

When I follow the left menu "Home > Notification Messages" 59ms

And I wait until I see "The server has collected the following notification messages." text 237ms

Then I follow "All Messages" 68ms

Then I check the first notification message 13ms

And I delete it via the "Delete" button 12ms

Scenario:
Flag a notification-message as read
390ms 5

There are no notification messages, nothing to do then

When I follow the left menu "Home > Notification Messages" 66ms

And I wait until I see "The server has collected the following notification messages." text 238ms

Then I follow "All Messages" 59ms

Then I check the first notification message 12ms

And I mark as read it via the "Mark as Read" button 12ms

Feature:Pay as you go 2m 12s 435ms 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 696ms 1

Given I am authorized for the "Admin" section 1s 696ms

Scenario:
Enter minimal information for payg ssh connection data
1s 618ms 11

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 202ms

And I click on "Add PAYG Connection" 350ms

And I enter "My Instance" as "description" 93ms

And I enter "my-host.local" as "host" 88ms

And I enter "root" as "username" 56ms

And I click on "Create" 62ms

Then I should see a "PAYG my-host.local created successfully" text 684ms

And I should see a "My Instance" text in element "Info-panel-wrapper" 20ms

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 839ms 31

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 71ms

And I click on "Add PAYG Connection" 396ms

And I enter "My Full Instance" as "description" 93ms

And I enter "my-host-full.local" as "host" 96ms

And I enter "21" as "port" 50ms

And I enter "rootFull" as "username" 67ms

And I enter "passwordFull" as "password" 74ms

And I enter "keyFull" as "key" 69ms

And I enter "keyPasswordFull" as "key_password" 89ms

And I enter "my-bastion.local" as "bastion_host" 92ms

And I enter "22" as "bastion_port" 52ms

And I enter "b_rootFull" as "bastion_username" 75ms

And I enter "b_passwordFull" as "bastion_password" 86ms

And I enter "b_keyFull" as "bastion_key" 80ms

And I enter "b_keyPasswordFull" as "bastion_key_password" 95ms

And I click on "Create" 61ms

Then I should see a "PAYG my-host-full.local created successfully" text 974ms

And I should see a "My Full Instance" text in element "Info-panel-wrapper" 22ms

And I should see a "my-host-full.local" text in element "Instance-panel-wrapper" 19ms

And I should see a "21" text in element "Instance-panel-wrapper" 19ms

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 16ms

And I should not see a "keyFull" text in element "Instance-panel-wrapper" 10s 21ms

And I should not see a "keyPasswordFull" text in element "Instance-panel-wrapper" 10s 29ms

And I should see a "my-bastion.local" text in element "Bastion-panel-wrapper" 21ms

And I should see a "22" text in element "Bastion-panel-wrapper" 18ms

And I should see a "b_rootFull" text in element "Bastion-panel-wrapper" 18ms

And I should not see a "b_passwordFull" text in element "Bastion-panel-wrapper" 10s 34ms

And I should not see a "b_keyFull" text in element "Bastion-panel-wrapper" 10s 31ms

And I should not see a "b_keyPasswordFull" text in element "Bastion-panel-wrapper" 10s 13ms

And I should see a "Delete" button 24ms

Scenario:
Check pay-as-you-go list
286ms 5

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 111ms

Then I should see a "my-host.local" link 14ms

And I should see a "My Instance" text 73ms

And I should see a "my-host-full.local" link 19ms

And I should see a "My Full Instance" text 67ms

Scenario:
Edit connection description
923ms 7

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 67ms

And I follow "my-host-full.local" 343ms

And I click on "Edit Information" 68ms

And I enter "My new Full Instance" as "description" 129ms

And I click on "Save" in "Information" modal 224ms

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
31s 974ms 15

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 68ms

And I follow "my-host-full.local" 443ms

And I click on "Edit Instance" 66ms

And I enter "221" as "port" 62ms

And I enter "NewRootFull" as "username" 99ms

And I enter "NewPasswordFull" as "password" 86ms

And I enter "newKeyFull" as "key" 83ms

And I enter "newKeyPasswordFull" as "key_password" 93ms

And I click on "Save" in "Instance SSH connection" modal 797ms

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" 19ms

And I should not see a "NewPasswordFull" text in element "Instance-panel-wrapper" 10s 17ms

And I should not see a "newKeyFull" text in element "Instance-panel-wrapper" 10s 27ms

And I should not see a "newKeyPasswordFull" text in element "Instance-panel-wrapper" 10s 15ms

Scenario:
Edit bastion ssh connection data
31s 608ms 17

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 95ms

And I follow "my-host-full.local" 387ms

And I click on "Edit Bastion" 67ms

And I enter "my-new-bastion.local" as "bastion_host" 151ms

And I enter "222" as "bastion_port" 58ms

And I enter "b_new_rootFull" as "bastion_username" 103ms

And I enter "b_new_passwordFull" as "bastion_password" 92ms

And I enter "b_new_keyFull" as "bastion_key" 90ms

And I enter "b_new_keyPasswordFull" as "bastion_key_password" 121ms

And I click on "Save" in "Bastion SSH connection" modal 225ms

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" 22ms

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 7ms

And I should not see a "b_new_keyFull" text in element "Bastion-panel-wrapper" 10s 30ms

And I should not see a "b_new_keyPasswordFull" text in element "Bastion-panel-wrapper" 10s 38ms

Scenario:
Cleanup: delete minimal information for payg ssh connection data
853ms 6

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 93ms

And I follow "my-host.local" 332ms

And I click on "Delete" 75ms

And I click on "Delete" in "Delete PAYG Connection" modal 123ms

Then I should not see a "my-host.local" link 8ms

And I should not see a "my-host.local" text 220ms

Scenario:
Cleanup: delete full information for payg ssh connection data
634ms 6

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 71ms

And I follow "my-host-full.local" 332ms

And I click on "Delete" 60ms

And I click on "Delete" in "Delete PAYG Connection" modal 86ms

Then I should not see a "my-bastion.local" link 8ms

And I should not see a "my-host.local" text 74ms

@sle_minion @scc_credentials @skip_if_github_validation @bug_reported
Feature:Push a package with unset vendor 1m 31s 170ms 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 771ms 1

Given I am authorized 1s 771ms

Scenario:
Pre-requisite: mgr-push package must be installed on the SLES minion
44s 966ms 12 1

Event Details: ---------- ID: sync_states Function: saltutil.sync_states Name: sync_states Result: true Comment: No updates to sync Started: 00:56:05.828857 Duration: 228.956 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: 00:56:10.938138 Duration: 11.016 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: 00:56:10.952115 Duration: 38.478 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: 00:56:10.991833 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: 00:56:10.991985 Duration: 670.236 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: 00:56:11.662381 Duration: 38.723 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: 00:56:11.701231 Duration: 37.016 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: 00:56:11.738392 Duration: 43.596 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: 00:56:11.782138 Duration: 25.335 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: 00:56:11.807615 Duration: 26.796 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: 00:56:11.834644 Duration: 143.154 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-p14818-i14819.scope; invocation ID: de47c2f248564401880d1cb98a6b36f7Loading 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: 00:56:11.978370 Duration: 1920.115 SLS: packages.pkginstall Changed: {}

Given I am on the Systems overview page of this "sle_minion" 1s 575ms

When I follow "Software" in the content area 73ms

And I wait until I see "Upgrade Packages" text 59ms

And I follow "Install" 513ms

And I wait until I see "Installable Packages" text 122ms

And I enter "mgr-push" as the filtered package name 47ms

And I click on the filter button 627ms

And I check "mgr-push" in the list 67ms

And I click on "Install Packages" 622ms

And I click on "Confirm" 773ms

Then I should see a "1 package install has been scheduled for" text 61ms

And I wait until event "Package Install/Upgrade scheduled" is completed 24s 961ms 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 461ms Show Info + 
00:55:59:000 - 00:56:29:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010023&aid=310
Screenshot +

Scenario:
Push a package with unset vendor through the SLES minion
17s 972ms 2 1 1

When I copy unset package file on "sle_minion" 2s 34ms

And I push package "/root/subscription-tools-1.0-0.noarch.rpm" into "fake-base-channel-suse-like" channel through "sle_minion" 395ms 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 543ms Show Info + 
00:56:44:000 - 00:56:46:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010023&aid=310
Screenshot +

Scenario:
Check vendor of package displayed in web UI
26s 459ms 4 2 1

When I follow the left menu "Software > Channel List > All" 203ms

And I follow "Fake-Base-Channel-SUSE-like" 571ms

And I follow "Packages" 505ms

And I follow "subscription-tools-1.0-0.noarch" 10s 8ms 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 171ms Show Info + 
00:57:02:000 - 00:57:14: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 17s 907ms 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 740ms 1

Given I am authorized for the "Admin" section 1s 740ms

Scenario:
Populate the report database after bootstrapping minions
13s 224ms 1

When I schedule a task to update ReportDB 13s 224ms

Scenario:
Connect to the ReportDB on the server with admin user
1s 995ms 2

Then I should be able to connect to the ReportDB on the server 1s 207ms

And there should be a user allowed to create roles on the ReportDB 787ms

Scenario:
Create read-only user
2s 944ms 2

When I create a read-only user for the ReportDB 2s 160ms

Then I should see the read-only user listed on the ReportDB user accounts 783ms

Scenario:
External read-only user can connect to ReportDB and make queries
67ms 2

When I connect to the ReportDB with read-only user from external machine 65ms

Then I should be able to query the ReportDB 2ms

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 445ms 3

Given I know the ReportDB admin user credentials 1s 319ms

Then I should be able to connect to the ReportDB with the ReportDB admin user 62ms

And I should not be able to connect to product database with the ReportDB admin user 63ms

Scenario:
The systems should match between the UI and the ReportDB
10s 211ms 3

When I follow the left menu "Systems > System List > All" 199ms

And I make a list of the existing systems 10s 10ms

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
26s 288ms 4

Search by hostname: uyuni-master-suse-minion
[{"last_boot"=>"2026-03-04T22:19:57Z", "name"=>"uyuni-master-suse-minion.sumaci.aws", "id"=>1000010023, "last_checkin"=>"2026-03-04T23:56:14Z"}]

Given I have a property "City" with value "Arrakeen" on "sle_minion" 7s 609ms

And I know the current synced_date for "sle_minion" 2ms

When I schedule a task to update ReportDB 18s 675ms

Then I should find the updated "City" property as "Arrakeen" on the "sle_minion", on ReportDB < 1ms

Scenario:
Cleanup: delete read-only user
19s 983ms 2 1

When I delete the read-only user for the ReportDB 3s 511ms

Then I shouldn't see the read-only user listed on the ReportDB user accounts 974ms 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 498ms Show Info + 
00:58:40:000 - 00:58:45: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 747ms 12 3

Scenario:
Log in as org admin user
1s 935ms 1

Given I am authorized 1s 935ms

Scenario:
Check if Distribution Channel Mapping page exists
301ms 8

When I follow the left menu "Software > Distribution Channel Mapping" 122ms

Then I should see a "Distribution Channel Mapping" text 54ms

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 21ms

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 22ms

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 21ms

@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 349ms 9

When I follow the left menu "Software > Distribution Channel Mapping" 61ms

And I follow "Create Distribution Channel Mapping" 387ms

Then I should see a "Create Distribution Channel Map" text 59ms

When I enter "openSUSE Tumbleweed" as "os" 73ms

And I enter "20250928" as "release" 57ms

And I select "x86_64" from "architecture" 70ms

And I select "openSUSE Tumbleweed (x86_64)" from "channel_label" 60ms

And I click on "Create Mapping" 552ms

Then I should see a "openSUSE Tumbleweed" link in the content area 25ms

@deblike_minion
Scenario:
Create new map for amd64 Ubuntu clients with test base channel
1s 282ms 9

When I follow the left menu "Software > Distribution Channel Mapping" 62ms

And I follow "Create Distribution Channel Mapping" 341ms

Then I should see a "Create Distribution Channel Map" text 58ms

When I enter "Ubuntu 24.04" as "os" 57ms

And I enter "24.04" as "release" 49ms

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" 576ms

Then I should see a "Ubuntu 24.04" link in the content area 22ms

@scc_credentials
Scenario:
Create new map for iSeries SUSE clients using test channel
1s 297ms 9

When I follow the left menu "Software > Distribution Channel Mapping" 64ms

And I follow "Create Distribution Channel Mapping" 349ms

Then I should see a "Create Distribution Channel Map" text 65ms

When I enter "SUSE Linux Enterprise Server 15 SP 4 iSeries" as "os" 91ms

And I enter "15.5" as "release" 46ms

And I select "iSeries" from "architecture" 58ms

And I select "Fake-Base-Channel-i586" from "channel_label" 56ms

And I click on "Create Mapping" 541ms

Then I should see a "SUSE Linux Enterprise Server 15 SP 4 iSeries" link in the content area 23ms

@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 273ms 11

When I follow the left menu "Software > Distribution Channel Mapping" 67ms

Then I should see the text "openSUSE Tumbleweed" in the Operating System field 10s 10ms

And I should see the text "x86_64" in the Architecture field 10s 3ms

And I should see the text "opensuse_tumbleweed-x86_64" in the Channel Label field 10s 1ms

When I follow "openSUSE Tumbleweed" 389ms

Then I should see a "Update Distribution Channel Map" text 53ms

When I enter "openSUSE Tumbleweed modified" as "os" 103ms

And I select "openSUSE Tumbleweed (x86_64)" from "channel_label" 49ms

And I click on "Update Mapping" 576ms

Then I should see the text "openSUSE Tumbleweed modified" in the Operating System field 10s 12ms

And I should see the text "opensuse_tumbleweed-x86_64" in the Channel Label field 10s 4ms

@deblike_minion
Scenario:
Update map for amd64 Ubuntu clients using test base channel
40s 640ms 8

When I follow the left menu "Software > Distribution Channel Mapping" 85ms

Then I should see the text "Ubuntu 24.04" in the Operating System field 10s 8ms

And I should see the text "AMD64 Debian" in the Architecture field 10s 6ms

And I should see the text "fake-base-channel-debian-like" in the Channel Label field 10s 9ms

When I follow "Ubuntu 24.04" 363ms

And I enter "Ubuntu 24.04 modified" as "os" 90ms

And I click on "Update Mapping" 65ms

Then I should see the text "Ubuntu 24.04 modified" in the Operating System field 10s 11ms

@scc_credentials
Scenario:
Update map for IA-32 SUSE clients using amd deb test channel
50s 689ms 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 1ms

And I should see the text "iSeries" in the Architecture field 10s 3ms

And I should see the text "fake-base-channel-i586" in the Channel Label field 10s 10ms

When I follow "SUSE Linux Enterprise Server 15 SP 4 iSeries" 302ms

And I enter "SUSE Linux Enterprise Server 15 SP 4 iSeries modified" as "os" 147ms

And I select "Fake-Base-Channel-Debian-like" from "channel_label" 67ms

And I click on "Update Mapping" 64ms

Then I should see the text "SUSE Linux Enterprise Server 15 SP 4 iSeries modified" in the Operating System field 10s

And I should see the text "fake-base-channel-debian-like" in the Channel Label field 10s 13ms

@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
21s 303ms 10

When I follow the left menu "Software > Distribution Channel Mapping" 96ms

Then I should see the text "openSUSE Tumbleweed modified" in the Operating System field 10s 7ms

And I should see the text "x86_64" in the Architecture field 10s 7ms

When I follow "openSUSE Tumbleweed modified" 294ms

Then I should see a "Update Distribution Channel Map" text 63ms

And I should see a "Delete Distribution Channel" link 11ms

When I follow "Delete Distribution Channel Mapping" 313ms

Then I should see a "Delete Distribution Channel Map" text 46ms

When I click on "Delete Mapping" 452ms

Then I should not see a "openSUSE Tumbleweed modified" link 8ms

@deblike_minion
Scenario:
Cleanup: delete the map created for amd64 Ubuntu clients
21s 240ms 10

When I follow the left menu "Software > Distribution Channel Mapping" 77ms

Then I should see the text "Ubuntu 24.04 modified" in the Operating System field 10s 6ms

And I should see the text "AMD64 Debian" in the Architecture field 10s 3ms

When I follow "Ubuntu 24.04 modified" 291ms

Then I should see a "Update Distribution Channel Map" text 55ms

And I should see a "Delete Distribution Channel" link 11ms

When I follow "Delete Distribution Channel Mapping" 261ms

Then I should see a "Delete Distribution Channel Map" text 50ms

When I click on "Delete Mapping" 473ms

Then I should not see a "Ubuntu 24.04 modified" link 8ms

@scc_credentials
Scenario:
Cleanup: delete the map created for i586 clients
21s 282ms 10

When I follow the left menu "Software > Distribution Channel Mapping" 82ms

Then I should see the text "SUSE Linux Enterprise Server 15 SP 4 iSeries modified" in the Operating System field 10s 6ms

And I should see the text "x86_64" in the Architecture field 10s 7ms

When I follow "SUSE Linux Enterprise Server 15 SP 4 iSeries modified" 348ms

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" 256ms

Then I should see a "Delete Distribution Channel Map" text 51ms

When I click on "Delete Mapping" 455ms

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
150ms 3

When I follow the left menu "Software > Distribution Channel Mapping" 78ms

Then I should see a "Distribution Channel Mapping" text 50ms

And I should see a "No distribution channel mappings currently exist." text in the content area 21ms

Feature:Task Engine Status 28s 133ms 4 2

Scenario:
Login as admin
1s 719ms 1

Given I am authorized for the "Admin" section 1s 719ms

@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 152ms 6

When I follow the left menu "Admin > Task Engine Status > Last Execution Times" 801ms

Then I should see a "Task Engine Status" text 102ms

And I should see a "The following is a status report for the various tasks run by the Uyuni task engine:" text 99ms

And I should see a "Runtime Status" text 101ms

And I should see a "Last Execution Times" link in the left menu 25ms

And I should see a "Runtime Status" link in the left menu 21ms

Scenario:
Check if the Runtime Status Page exists
610ms 6

When I follow the left menu "Admin > Task Engine Status > Runtime Status" 74ms

Then I should see a "Task Engine Status" text 57ms

And I should see a "Last Execution Times" text 54ms

And I should see a "The server is running or has finished executing the following tasks during the latest 5 minutes." text 386ms

And I should see a "Last Execution Times" link in the left menu 18ms

And I should see a "Runtime Status" link in the left menu 19ms

Scenario:
Run a remote command on the server to check if it shows up on Last Execution Times page
24s 650ms 6

When I follow the left menu "Admin > Task Engine Status > Last Execution Times" 71ms

And I run "cobbler sync" on "server" 3s 274ms

And I refresh the page 11s 79ms

Then I should see a "Cobbler Sync:" text 103ms

And I should see the correct timestamp for task "Cobbler Sync:" 10s 11ms

And I should see a "FINISHED" text 110ms

@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 252ms 2

@ssh_minion
Scenario:
Check the relevant errata for a system
4s 743ms 1

When I retrieve the relevant errata for ssh_minion 4s 743ms

@ssh_minion @rhlike_minion @deblike_minion
Scenario:
Check the relevant errata for multiple systems
1s 508ms 1

When I retrieve the relevant errata for ssh_minion, rhlike_minion, deblike_minion 1s 508ms

@scope_salt @skip_if_github_validation @bug_reported
Feature:Health Check tool based on a supportconfig 6m 42s 841ms 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 46s 149ms 2

When I generate a supportconfig for the server 1m 45s 116ms

Then I obtain and extract the supportconfig from the server 1s 33ms

Scenario:
Execute Health Check tool with server supportconfig
15s 681ms 1 1 1

When I start the health check tool with supportconfig "/root/server-supportconfig/uyuni-server-supportconfig/" on "localhost" 494ms Show Error + 
                                            
 FAIL: mgr-health-check -v -s /root/server-supportconfig/uyuni-server-supportconfig/ start returned status code = 1.
Output:
┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃                                 Health Check                                 ┃
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛
[01:05:53] 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 187ms Show Info + 
01:05:53:000 - 01:05:53:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/admin/TaskStatus.do
Screenshot +

Scenario:
Health Check containers are healthy and running
4m 25s 30ms 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

15s 29ms Show Info + 
01:06:08:000 - 01:10:18:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/admin/TaskStatus.do
Screenshot +

Scenario:
Health Check containers are exposing metrics
15s 161ms 1 1

Then I check that the health check tool exposes metrics on "localhost" 178ms 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 983ms Show Info + 
01:10:33:000 - 01:10:34:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/admin/TaskStatus.do
Screenshot +

Scenario:
I can stop the Health Check tool
819ms 3

When I stop health check tool on "localhost" 470ms

Then I check that the health check tool is not running on "localhost" 170ms

And I remove test supportconfig on "localhost" 178ms

@skip_if_github_validation
Feature:Password Policy Management 1m 59s 351ms 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 608ms 1

Given I am authorized as "admin" with password "admin" 1s 608ms

Scenario:
Navigate to Password Policy settings page
759ms 2

When I follow the left menu "Admin > Manager Configuration > Password Policy" 682ms

Then I should see a "Server Configuration - Password Policy" text 76ms

Scenario:
Configure password complexity restrictions
781ms 5

When I set the minimum password length to "5" 57ms

And I set the maximum password length to "12" 53ms

And I enable the following restrictions: 327ms
Require Digits
Require Lowercase Characters
Require Uppercase Characters
Require Special Characters
Restrict Characters Occurrences
Restrict Consecutive Characters

And I click on "Save" 56ms

And I should see a "Password Policy Changed" text 287ms

Scenario:
Verify password complexity restrictions are saved correctly
10s 413ms 2

When I refresh the page 10s 362ms

Then the following restrictions should be enabled: 50ms
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
339ms 4

When I set the special characters list to "$@?" 57ms

And I set the maximum allowed occurrence of any character to "3" 47ms

And I click on "Save" 53ms

And I should see a "Password Policy Changed" text 181ms

Scenario Outline:
Reject invalid passwords based on policy enforcement
9s 109ms 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" 9s 109ms

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 378ms 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 378ms

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 231ms 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 231ms

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
9s 42ms 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" 9s 42ms

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 81ms 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 81ms

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 69ms 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 69ms

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
9s 157ms 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" 9s 157ms

Then the user creation should fail with error containing "consecutive_characters_presents" < 1ms

Scenario Outline:
Reject invalid passwords based on policy enforcement
9s 72ms 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 72ms

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 301ms 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 301ms

Then the user creation should fail with error containing "Passwords cannot be more than 12 characters" < 1ms

Scenario:
Accept valid password complying with policy
11s 738ms 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" 11s 738ms

Then the user creation should succeed < 1ms

Scenario:
Reset password policy to default settings
10s 835ms 5

When I follow the left menu "Admin > Manager Configuration > Password Policy" 74ms

And I click on "Reset" 58ms

And I should see a "Password Policy Reset to Default" text 287ms

And I refresh the page 10s 368ms

Then the following restrictions should be disabled: 47ms
Require Digits
Require Lowercase Characters
Require Uppercase Characters
Require Special Characters
Restrict Characters Occurrences
Restrict Consecutive Characters

Scenario:
Cleanup: Delete test user
430ms 1

When I delete user "password_policy_user" 430ms

@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 42s 158ms 16 14

Scenario:
Log in as org admin user
1s 718ms 1

Given I am authorized 1s 718ms

Scenario:
Create a simple image profile without activation key
2s 840ms 6

GITPROFILES: https://github.com/uyuni-project/uyuni.git#:testsuite/features/profiles/temporary

When I follow the left menu "Images > Profiles" 123ms

And I follow "Create" 525ms

And I enter "suse_simple" as "label" 107ms

And I select "galaxy-registry" from "imageStore" 1s 138ms

And I enter "Docker" relative to profiles as "path" 878ms

And I click on "create-btn" 65ms

Scenario:
Create a simple real image profile without activation key
2s 911ms 6

GITPROFILES: https://github.com/uyuni-project/uyuni.git#:testsuite/features/profiles/temporary

When I follow the left menu "Images > Profiles" 63ms

And I follow "Create" 614ms

And I enter "suse_real_simple" as "label" 134ms

And I select "galaxy-registry" from "imageStore" 1s 116ms

And I enter "Docker/serverhost" relative to profiles as "path" 929ms

And I click on "create-btn" 52ms

@scc_credentials
Scenario:
Create an image profile with activation key
3s 820ms 7

GITPROFILES: https://github.com/uyuni-project/uyuni.git#:testsuite/features/profiles/temporary

When I follow the left menu "Images > Profiles" 62ms

And I follow "Create" 455ms

And I enter "suse_key" as "label" 83ms

And I select "galaxy-registry" from "imageStore" 1s 134ms

And I select "1-SUSE-KEY-x86_64" from "activationKey" 1s 124ms

And I enter "Docker" relative to profiles as "path" 904ms

And I click on "create-btn" 55ms

@scc_credentials
Scenario:
Create a simple real image profile with activation key
4s 38ms 7

GITPROFILES: https://github.com/uyuni-project/uyuni.git#:testsuite/features/profiles/temporary

When I follow the left menu "Images > Profiles" 62ms

And I follow "Create" 594ms

And I enter "suse_real_key" as "label" 117ms

And I select "galaxy-registry" from "imageStore" 1s 135ms

And I select "1-SUSE-KEY-x86_64" from "activationKey" 1s 108ms

And I enter "Docker/serverhost" relative to profiles as "path" 955ms

And I click on "create-btn" 64ms

@scc_credentials
Scenario:
Build the suse_key image with and without activation key
1m 1s 614ms 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: 01:13:40.499393 Duration: 2.224 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: 01:13:40.501935 Duration: 13930.728 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: 01:13:54.433106 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: 01:13:54.433375 Duration: 0.004 SLS: images.docker Changed: {} ---------- ID: mgr_buildimage_docker_collect_logs Function: file.touch Name: /var/log/image-build311.log Result: true Comment: Updated times on file /var/log/image-build311.log Started: 01:13:54.436078 Duration: 6.951 SLS: images.docker Changed: touched: /var/log/image-build311.log ---------- ID: mgr_buildimage_docker_collect_logs Function: mgrcompat.module_run Name: cp.push Result: true Comment: Module function cp.push executed Started: 01:13:54.443149 Duration: 9.173 SLS: images.docker Changed: ret: true

Given I am on the Systems overview page of this "build_host" 3s 639ms

When I schedule the build of image "suse_key" via API calls 1s 48ms

And I wait at most 660 seconds until event "Image Build suse_key scheduled" is completed 41s 626ms 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 300ms Show Info + 
01:13:34:000 - 01:14:20:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010004&aid=311
Screenshot +

Scenario:
Check the list of packages is not empty
16s 24ms 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"=>1000010004, "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 763ms 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 261ms Show Info + 
01:14:36:000 - 01:14:37:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010004&aid=311
Screenshot +

Scenario:
Build the suse_simple image with and without activation key
58s 793ms 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: 01:14:55.472039 Duration: 2.077 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: 01:14:55.474434 Duration: 14159.305 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: 01:15:09.634200 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: 01:15:09.634471 Duration: 0.004 SLS: images.docker Changed: {} ---------- ID: mgr_buildimage_docker_collect_logs Function: file.touch Name: /var/log/image-build312.log Result: true Comment: Updated times on file /var/log/image-build312.log Started: 01:15:09.637445 Duration: 7.82 SLS: images.docker Changed: touched: /var/log/image-build312.log ---------- ID: mgr_buildimage_docker_collect_logs Function: mgrcompat.module_run Name: cp.push Result: true Comment: Module function cp.push executed Started: 01:15:09.645392 Duration: 9.065 SLS: images.docker Changed: ret: true

Given I am on the Systems overview page of this "build_host" 1s 177ms

When I schedule the build of image "suse_simple" via API calls 882ms

And I wait at most 660 seconds until event "Image Build suse_simple scheduled" is completed 41s 514ms 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 218ms Show Info + 
01:14:52:000 - 01:15:35:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010004&aid=312
Screenshot +

Scenario:
Check the list of packages is not empty
16s 30ms 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"=>1000010004, "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 835ms 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 194ms Show Info + 
01:15:51:000 - 01:15:52:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010004&aid=312
Screenshot +

@scc_credentials
Scenario:
Build the suse_real_key image with and without activation key
2m 53s 989ms 4 3 1

Given I am on the Systems overview page of this "build_host" 1s 209ms

When I schedule the build of image "suse_real_key" via API calls 904ms

And I wait at most 660 seconds until event "Image Build suse_real_key scheduled" is completed 2m 34s 322ms

And I wait at most 60 seconds until all "3" container images are built correctly on the Image List page 1s 544ms 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 8ms Show Info + 
01:16:07:000 - 01:18:45:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

Scenario:
Check the list of packages is not empty
16s 954ms 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"=>1000010004, "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 822ms 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'

16s 131ms Show Info + 
01:19:01:000 - 01:19:02: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 508ms 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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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 803ms

And I wait at most 900 seconds until image "suse_key" with version "Latest_key-activation1" is built successfully via API 1m 42s 710ms 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 994ms Show Info + 
01:19:18:000 - 01:21:01:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

Scenario:
Check the list of packages is not empty
16s 748ms 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"=>"eb0baf939d00bf154906af24e5166d6fffcb3a9aa9e5854742254405204fd911", "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"=>1000010004, "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 748ms 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 999ms Show Info + 
01:21:17:000 - 01:21:18:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

Scenario:
Build suse_simple image with different versions
38s 764ms 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"=>"eb0baf939d00bf154906af24e5166d6fffcb3a9aa9e5854742254405204fd911", "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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 804ms

And I wait at most 900 seconds until image "suse_simple" with version "Latest_simple" is built successfully via API 21s 993ms 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 967ms Show Info + 
01:21:34:000 - 01:21:57:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

Scenario:
Check the list of packages is not empty
16s 763ms 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"=>"eb0baf939d00bf154906af24e5166d6fffcb3a9aa9e5854742254405204fd911", "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"=>1000010004, "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 752ms 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'

16s 11ms Show Info + 
01:22:13:000 - 01:22:14: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 392ms 3

When I delete the image "suse_key" with version "Latest_key-activation1" via API calls 946ms

Then the image "suse_simple" with version "Latest_key-activation1" doesn't exist via API calls 527ms

When I wait until no Salt job is running on "build_host" 1s 918ms

Scenario:
Delete image via API calls without key
2s 737ms 3

When I delete the image "suse_simple" with version "Latest_simple" via API calls 772ms

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 599ms

Scenario:
Rebuild suse_simple image
38s 715ms 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"=>"eb0baf939d00bf154906af24e5166d6fffcb3a9aa9e5854742254405204fd911", "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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 816ms

And I wait at most 900 seconds until image "suse_simple" with version "Latest_simple" is built successfully via API 21s 982ms 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

15s 916ms Show Info + 
01:22:36:000 - 01:22:59:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

Scenario:
Check the list of packages is not empty
16s 793ms 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"=>"eb0baf939d00bf154906af24e5166d6fffcb3a9aa9e5854742254405204fd911", "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"=>1000010004, "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 869ms 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 924ms Show Info + 
01:23:15:000 - 01:23:15:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

@scc_credentials
Scenario:
Rebuild suse_key image
39s 228ms 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"=>"eb0baf939d00bf154906af24e5166d6fffcb3a9aa9e5854742254405204fd911", "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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 835ms

And I wait at most 900 seconds until image "suse_key" with version "Latest_key-activation1" is built successfully via API 22s 52ms 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

16s 340ms Show Info + 
01:23:31:000 - 01:23:54:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

Scenario:
Check the list of packages is not empty
16s 670ms 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"=>"eb0baf939d00bf154906af24e5166d6fffcb3a9aa9e5854742254405204fd911", "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"=>1000010004, "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 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:147:in `the list of packages of image "suse_key" with version "Latest_key-activation1" is not empty'

15s 870ms Show Info + 
01:24:11:000 - 01:24:11:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

@scc_credentials
Scenario:
Build an image via the GUI
3m 40s 839ms 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"=>"eb0baf939d00bf154906af24e5166d6fffcb3a9aa9e5854742254405204fd911", "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"=>1000010004, "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"=>"eb0baf939d00bf154906af24e5166d6fffcb3a9aa9e5854742254405204fd911", "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>"33a510478d1cc6ee64580d8e7da4f7477c9fd571f32d89bc2202ff1f713c064d", "files"=>[], "id"=>8, "arch"=>"x86_64", "enhancementErrata"=>0}

When I follow the left menu "Images > Build" 80ms

And I select "suse_real_key" from "profileId" 1s 139ms

And I enter "GUI_BUILT_IMAGE" as "version" 317ms

And I select the hostname of "build_host" from "buildHostId" 1s 125ms

And I click on "submit-btn" 60ms

And I wait until no Salt job is running on "build_host" 2m 21s 799ms

Then I wait until I see "GUI_BUILT_IMAGE" text 95ms

And I wait at most 900 seconds until image "suse_real_key" with version "GUI_BUILT_IMAGE" is built successfully via API 5s 789ms

And I wait at most 300 seconds until image "suse_real_key" with version "GUI_BUILT_IMAGE" is inspected successfully via API 1m 10s 432ms

@scc_credentials
Scenario:
Login as Docker image administrator and build an image
3m 40s 417ms 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"=>"eb0baf939d00bf154906af24e5166d6fffcb3a9aa9e5854742254405204fd911", "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"=>"33a510478d1cc6ee64580d8e7da4f7477c9fd571f32d89bc2202ff1f713c064d", "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"=>1000010004, "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"=>"eb0baf939d00bf154906af24e5166d6fffcb3a9aa9e5854742254405204fd911", "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"=>"33a510478d1cc6ee64580d8e7da4f7477c9fd571f32d89bc2202ff1f713c064d", "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>"b0d9abb0e78c11931c1d37c0808153c42012c9305c41f7271cf3d3c95e0e8c2b", "files"=>[], "id"=>9, "arch"=>"x86_64", "enhancementErrata"=>0}

Given I am authorized as "docker" with password "docker" 1s 498ms

When I follow the left menu "Images > Build" 130ms

And I select "suse_real_key" from "profileId" 1s 118ms

And I enter "GUI_DOCKERADMIN" as "version" 236ms

And I select the hostname of "build_host" from "buildHostId" 1s 102ms

And I click on "submit-btn" 53ms

And I wait until no Salt job is running on "build_host" 2m 17s 656ms

Then I wait until I see "GUI_DOCKERADMIN" text 96ms

And I wait at most 900 seconds until image "suse_real_key" with version "GUI_DOCKERADMIN" is built successfully via API 5s 418ms

And I wait at most 300 seconds until image "suse_real_key" with version "GUI_DOCKERADMIN" is inspected successfully via API 1m 13s 106ms

@scc_credentials
Scenario:
Audit images, searching for a known CVE number
894ms 5

When I follow the left menu "Audit > CVE Audit" 119ms

And I select "1999" from "cveIdentifierYear" 100ms

And I enter "9999" as "cveIdentifierId" 63ms

And I click on "Audit Images" 60ms

Then I should see a "No action required" text 551ms

Scenario:
Audit images, searching for an unknown CVE number
400ms 5

When I follow the left menu "Audit > CVE Audit" 65ms

And I select "2012" from "cveIdentifierYear" 59ms

And I enter "2806" as "cveIdentifierId" 57ms

And I click on "Audit Images" 52ms

Then I should see a "The specified CVE number was not found" text 165ms

@scc_credentials
Scenario:
Cleanup: delete all images with key
5s 565ms 6

Given I am authorized as "admin" with password "admin" 1s 160ms

When I delete the image "suse_key" with version "latest" via API calls 1s 450ms

And I delete the image "suse_key" with version "Latest_key-activation1" via API calls 773ms

And I delete the image "suse_real_key" with version "latest" via API calls 749ms

And I delete the image "suse_real_key" with version "GUI_BUILT_IMAGE" via API calls 715ms

And I delete the image "suse_real_key" with version "GUI_DOCKERADMIN" via API calls 716ms

Scenario:
Cleanup: delete images without key
2s 440ms 3

Given I am authorized as "admin" with password "admin" 403ms

When I delete the image "suse_simple" with version "latest" via API calls 1s 336ms

And I delete the image "suse_simple" with version "Latest_simple" via API calls 700ms

@scc_credentials
Scenario:
Cleanup: delete all profiles with key
891ms 7

When I follow the left menu "Images > Profiles" 129ms

And I check "suse_key" in the list 301ms

And I check "suse_real_key" in the list 59ms

And I click on "Delete" 79ms

And I should see a "Are you sure you want to delete selected profiles?" text 73ms

And I click on the red confirmation button 69ms

And I wait until I see "Image profiles have been deleted" text 178ms

Scenario:
Cleanup: delete all profiles without key
694ms 7

When I follow the left menu "Images > Profiles" 63ms

And I check "suse_simple" in the list 193ms

And I check "suse_real_simple" in the list 60ms

And I click on "Delete" 62ms

And I should see a "Are you sure you want to delete selected profiles?" text 68ms

And I click on the red confirmation button 64ms

And I wait until I see "Image profiles have been deleted" text 181ms

Scenario:
Cleanup: Make sure no job is left running on buildhost
1s 956ms 1

When I wait until no Salt job is running on "build_host" 1s 956ms

@skip_if_github_validation @build_host @scope_building_container_images @auth_registry
Feature:Build image with authenticated registry 1m 4s 944ms 6 2

Scenario:
Log in as docker user
1s 484ms 1

Given I am authorized as "docker" with password "docker" 1s 484ms

Scenario:
Create an authenticated image store as Docker admin
1s 200ms 7

AUTH_REGISTRY_CREDENTIALS: cucutest|cucusecret

When I follow the left menu "Images > Stores" 141ms

And I follow "Create" 362ms

And I enter "auth_registry" as "label" 92ms

And I check "useCredentials" 91ms

And I enter URI, username and password for registry 403ms

And I click on "create-btn" 58ms

Then I wait until I see "registry" text 50ms

@scc_credentials
Scenario:
Create a profile for the authenticated image store as Docker admin
4s 319ms 8

GITPROFILES: https://github.com/uyuni-project/uyuni.git#:testsuite/features/profiles/temporary

When I follow the left menu "Images > Profiles" 79ms

And I follow "Create" 340ms

And I enter "auth_registry_profile" as "label" 189ms

And I select "auth_registry" from "imageStore" 1s 125ms

And I select "1-SUSE-KEY-x86_64" from "activationKey" 1s 121ms

And I enter "Docker/authprofile" relative to profiles as "path" 1s 6ms

And I click on "create-btn" 54ms

Then I wait until I see "auth_registry_profile" text 401ms

@scc_credentials
Scenario:
Build an image in the authenticated image store
39s 70ms 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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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"=>1000010004, "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" 66ms

And I select "auth_registry_profile" from "profileId" 1s 136ms

And I enter "latest" as "version" 152ms

And I select the hostname of "build_host" from "buildHostId" 1s 119ms

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 168ms 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 294ms Show Info + 
01:32:23:000 - 01:32:47:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

Scenario:
Check the list of packages is not empty
15s 566ms 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"=>1000010004, "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 383ms 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 182ms Show Info + 
01:33:02:000 - 01:33:03: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 455ms 6

When I follow the left menu "Images > Profiles" 80ms

And I check the row with the "auth_registry_profile" text 68ms

And I click on "Delete" 80ms

And I click on the red confirmation button 66ms

And I should see a "Image profile has been deleted." text 175ms

And I wait until no Salt job is running on "build_host" 1s 983ms

Scenario:
Cleanup: remove authenticated image store
476ms 5

When I follow the left menu "Images > Stores" 65ms

And I check the row with the "auth_registry" text 129ms

And I click on "Delete" 67ms

And I click on the red confirmation button 57ms

And I should see a "Image store has been deleted." text 157ms

Scenario:
Cleanup: delete registry image
370ms 1

When I delete the image "auth_registry_profile" with version "latest" via API calls 370ms

@scope_visualization
Feature:The system details of each minion and client provides an overview of the system 2m 18s 398ms 9

Scenario:
Log in as org admin user
1s 175ms 1

Given I am authorized 1s 175ms

@sle_minion
Scenario:
SLE minion hardware refresh
28s 208ms 6

Given I navigate to the Systems overview page of this "sle_minion" 2s 547ms

When I follow "Hardware" 562ms

And I click on "Schedule Hardware Refresh" 834ms

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 950ms

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "sle_minion" 2s 201ms

@sle_minion
Scenario:
Minion grains are displayed correctly on the details page
3s 830ms 19

I should see kernel version: 6.19.3-1-default
IPv4 address: 172.16.3.8
IPv6 address: fe80::45f:9fff:fe3f:6587

Given I am on the Systems overview page of this "sle_minion" 1s 41ms

Then the hostname for "sle_minion" should be correct 90ms

And the kernel for "sle_minion" should be correct 485ms

And the OS version for "sle_minion" should be correct < 1ms

And the IPv4 address for "sle_minion" should be correct 82ms

And the IPv6 address for "sle_minion" should be correct 414ms

And the system ID for "sle_minion" should be correct 446ms

And the system name for "sle_minion" should be correct 80ms

And the uptime for "sle_minion" should be correct 410ms

And I should see a "UUID" text 77ms

And I should see a "Virtualization" text 78ms

And I should see a "Installed Products" text 76ms

And I should see a "Checked In" text 77ms

And I should see a "Registered" text 79ms

And I should see a "Contact Method" text 77ms

And I should see a "Auto Patch Update" text 76ms

And I should see a "Maintenance Schedule" text 77ms

And I should see a "Description" text 78ms

And I should see a "Location" text 77ms

@rhlike_minion
Scenario:
Red Hat-like minion hardware refresh
26s 477ms 6

Given I am on the Systems overview page of this "rhlike_minion" 1s 34ms

When I follow "Hardware" 795ms

And I click on "Schedule Hardware Refresh" 801ms

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 946ms

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "rhlike_minion" 1s 786ms

@rhlike_minion
Scenario:
Red Hat-like minion grains are displayed correctly on the details page
3s 330ms 19

I should see kernel version: 4.18.0-553.el8_10.x86_64
IPv4 address: 172.16.3.10
IPv6 address: fe80::43d:9aff:fed8:2d3d

Given I am on the Systems overview page of this "rhlike_minion" 1s 191ms

Then the hostname for "rhlike_minion" should be correct 91ms

And the kernel for "rhlike_minion" should be correct 277ms

And the OS version for "rhlike_minion" should be correct < 1ms

And the IPv4 address for "rhlike_minion" should be correct 78ms

And the IPv6 address for "rhlike_minion" should be correct 206ms

And the system ID for "rhlike_minion" should be correct 430ms

And the system name for "rhlike_minion" should be correct 92ms

And the uptime for "rhlike_minion" should be correct 197ms

And I should see a "UUID" text 74ms

And I should see a "Virtualization" text 75ms

And I should see a "Installed Products" text 76ms

And I should see a "Checked In" text 74ms

And I should see a "Registered" text 78ms

And I should see a "Contact Method" text 74ms

And I should see a "Auto Patch Update" text 76ms

And I should see a "Maintenance Schedule" text 76ms

And I should see a "Description" text 76ms

And I should see a "Location" text 80ms

@deblike_minion
Scenario:
Debian-like minion hardware refresh
26s 867ms 6

Given I am on the Systems overview page of this "deblike_minion" 1s 13ms

When I follow "Hardware" 672ms

And I click on "Schedule Hardware Refresh" 845ms

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 931ms

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "deblike_minion" 2s 291ms

@deblike_minion
Scenario:
Debian-like minion grains are displayed correctly on the details page
3s 265ms 19

I should see kernel version: 6.17.0-1007-aws
IPv4 address: 172.16.3.11
IPv6 address: fe80::403:62ff:fe02:b261

Given I am on the Systems overview page of this "deblike_minion" 1s 47ms

Then the hostname for "deblike_minion" should be correct 90ms

And the kernel for "deblike_minion" should be correct 286ms

And the OS version for "deblike_minion" should be correct < 1ms

And the IPv4 address for "deblike_minion" should be correct 79ms

And the IPv6 address for "deblike_minion" should be correct 214ms

And the system ID for "deblike_minion" should be correct 469ms

And the system name for "deblike_minion" should be correct 80ms

And the uptime for "deblike_minion" should be correct 218ms

And I should see a "UUID" text 75ms

And I should see a "Virtualization" text 84ms

And I should see a "Installed Products" text 76ms

And I should see a "Checked In" text 76ms

And I should see a "Registered" text 76ms

And I should see a "Contact Method" text 76ms

And I should see a "Auto Patch Update" text 77ms

And I should see a "Maintenance Schedule" text 77ms

And I should see a "Description" text 78ms

And I should see a "Location" text 77ms

@ssh_minion
Scenario:
SSH-managed minion hardware refresh
41s 88ms 5

Given I am on the Systems overview page of this "ssh_minion" 1s 26ms

When I follow "Hardware" 690ms

And I click on "Schedule Hardware Refresh" 898ms

Then I should see a "You have successfully scheduled a hardware profile refresh" text 117ms

And I wait until event "Hardware List Refresh scheduled" is completed 38s 356ms

@ssh_minion
Scenario:
SSH-managed minion grains are displayed correctly on the details page
4s 153ms 19

I should see kernel version: 6.19.3-1-default
IPv4 address: 172.16.3.9
IPv6 address: fe80::428:58ff:fe28:71fb

Given I am on the Systems overview page of this "ssh_minion" 1s 32ms

Then the hostname for "ssh_minion" should be correct 85ms

And the kernel for "ssh_minion" should be correct 797ms

And the OS version for "ssh_minion" should be correct < 1ms

And the IPv4 address for "ssh_minion" should be correct 81ms

And the IPv6 address for "ssh_minion" should be correct 415ms

And the system ID for "ssh_minion" should be correct 436ms

And the system name for "ssh_minion" should be correct 80ms

And the uptime for "ssh_minion" should be correct 414ms

And I should see a "UUID" text 90ms

And I should see a "Virtualization" text 78ms

And I should see a "Installed Products" text 78ms

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 79ms

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 89ms

And I should see a "Location" text 77ms

@scope_ssm @sle_minion @scope_visualization @new_issue @flaky
Feature:Manage a group of systems and the Systems Set Manager 8m 21s 661ms 20 2 2

Scenario:
Log in as org admin user
1s 642ms 1

Given I am authorized for the "Admin" section 1s 642ms

@skip_if_github_validation
Scenario:
Pre-requisite: install dummy packages to allow patching
4s 941ms 4

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 756ms

And I refresh the metadata for "sle_minion" 816ms

And I install old package "andromeda-dummy-1.0" on this "sle_minion" 1s 685ms

And I install old package "virgo-dummy-1.0" on this "sle_minion" 1s 683ms

Scenario:
Pre-requisite: ensure that fake patches are available
5s 900ms 6

When I follow the left menu "Admin > Task Schedules" 144ms

And I follow "errata-cache-default" 1s 199ms

And I follow "errata-cache-bunch" 573ms

And I click on "Single Run Schedule" 1s 512ms

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 201ms

Scenario:
Pre-requisite: ensure that fake channels were created
41s 355ms 7

When I follow the left menu "Patches > Patch List > Relevant" 233ms

Then I should see an update in the list 34ms

When I wait until I see "andromeda-dummy" text, refreshing the page 121ms

Then I should see a "andromeda-dummy-6789" link 11ms

When I enter "virgo-dummy" as the filtered synopsis 50ms

And I click on the filter button until page does contain "virgo-dummy-3456" text 40s 890ms

Then I should see a "virgo-dummy-3456" link 13ms

Scenario:
Fail to create a group with only its name
876ms 5

When I follow the left menu "Systems > System Groups" 150ms

And I follow "Create Group" 272ms

And I enter "new-systems-group" as "name" 74ms

And I click on "Create Group" 321ms

Then I should see a "Both name and description are required for System Groups." text 57ms

Scenario:
Fail to create a group with only its description
772ms 5

When I follow the left menu "Systems > System Groups" 66ms

And I follow "Create Group" 302ms

And I enter "My new group" as "description" 60ms

And I click on "Create Group" 284ms

Then I should see a "Both name and description are required for System Groups." text 58ms

Scenario:
Create a group
933ms 6

When I follow the left menu "Systems > System Groups" 63ms

And I follow "Create Group" 278ms

And I enter "new-systems-group" as "name" 61ms

And I enter "My new group" as "description" 52ms

And I click on "Create Group" 411ms

Then I should see a "System group new-systems-group created." text 66ms

Scenario:
Add the SLE minion to the group and to SSM
2s 682ms 7

When I follow the left menu "Systems > System Groups" 63ms

And I follow "new-systems-group" 302ms

And I follow "Target Systems" 490ms

And I check the "sle_minion" client 64ms

And I click on "Add Systems" 1s 167ms

Then I should see a "1 systems were added to new-systems-group server group." text 99ms

When I click on "Add Selected to SSM" 494ms

Scenario:
The SLE minion is part of the new group
1s 284ms 3

Given I am on the Systems overview page of this "sle_minion" 1s 136ms

When I follow "Groups" in the content area 78ms

Then I should see a "new-systems-group" text 69ms

Scenario:
Apply a patch to systems in the system group
42s 339ms 14

When I follow the left menu "Systems > System Groups" 82ms

And I follow "new-systems-group" 293ms

And I follow first "Patches" 325ms

When I enter "virgo-dummy" as the filtered synopsis 48ms

And I click on the filter button until page does contain "virgo-dummy-3456" text 121ms

Then I should see a "virgo-dummy-3456" link 8ms

When I follow "virgo-dummy-3456" 428ms

And I follow first "Affected Systems" 301ms

And I check the "sle_minion" client 52ms

And I click on "Apply Patches" 509ms

And I click on "Confirm" 540ms

Then I should see a "Patch virgo-dummy-3456 has been scheduled for 1 system" text 127ms

And I am on the Systems overview page of this "sle_minion" 1s 78ms

And I wait until event "Patch Update: virgo-dummy-3456 - Test update for virgo-dummy scheduled by admin" is completed 38s 419ms

Scenario:
Apply a patch to systems in the SSM
42s 457ms 14

When I follow the left menu "Systems > System Set Manager > Overview" 468ms

And I follow first "Patches" 282ms

When I enter "andromeda-dummy" as the filtered synopsis 61ms

And I click on the filter button 316ms

When I wait until I see "andromeda-dummy-6789" text, refreshing the page 61ms

Then I should see a "andromeda-dummy-6789" link 11ms

When I follow "andromeda-dummy-6789" 367ms

And I follow first "Affected Systems" 300ms

And I check the "sle_minion" client 60ms

And I click on "Apply Patches" 577ms

And I click on "Confirm" 59ms

Then I should see a "Patch andromeda-dummy-6789 has been scheduled for 1 system" text 611ms

And I am on the Systems overview page of this "sle_minion" 1s 95ms

And I wait until event "Patch Update: andromeda-dummy-6789 - Test update for andromeda-dummy scheduled by admin" is completed 38s 180ms

@skip_if_github_validation
Scenario:
Delete a package from systems in the SSM
26s 203ms 5 5 1

When I follow the left menu "Systems > System Set Manager > Overview" 471ms

And I follow "Packages" 351ms

And I follow "Remove" 346ms

And I wait until I see "Package Removal" text, refreshing the page 62ms

And I enter "virgo-dummy" as the filtered package name 10s 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 970ms Show Info + 
01:38:35:000 - 01:38:47: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 890ms 4 9 1

When I follow the left menu "Systems > System Set Manager > Overview" 74ms

And I follow "Packages" 335ms

And I follow "Install" 385ms

And I wait until I see "Fake-RPM-SUSE-Channel" text, refreshing the page 4m 13s 63ms 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

15s 31ms Show Info + 
01:39:02:000 - 01:43:16: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 447ms 8

When I follow the left menu "Systems > System Groups" 79ms

Then I should see a "System Groups" text 73ms

When I follow "new-systems-group" 304ms

And I follow "Target Systems" 481ms

Then I should see a "The following are systems that may be added to this group." text 94ms

When I check the "rhlike_minion" client 64ms

And I click on "Add Systems" 1s 255ms

Then I should see a "1 systems were added to new-systems-group server group" text 95ms

Scenario:
Add the new group to SSM
241ms 5

When I follow the left menu "Systems > System Groups" 62ms

And I click on "Use in SSM" in row "new-systems-group" 71ms

Then I should see a "Selected Systems List" text 78ms

And I should see "rhlike_minion" as link 14ms

And I should see "sle_minion" as link 14ms

@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 497ms 1

When I synchronize all Salt dynamic modules on "sle_minion" 2s 497ms

Scenario:
New formula page is rendered for the system group
11s 29ms 6

When I follow the left menu "Systems > System Groups" 58ms

And I follow "new-systems-group" 305ms

And I follow "Formulas" 381ms

Then I should see a "Choose formulas:" text 60ms

And I should see a "General System Configuration" text 192ms

And the "locale" formula should be unchecked 10s 30ms

@rhlike_minion
Scenario:
Apply the highstate to the group
31s 341ms 10

When I follow the left menu "Systems > System Groups" 60ms

Then I should see a "System Groups" text 68ms

When I follow "new-systems-group" 303ms

And I follow "States" 418ms

And I click on "Apply Highstate" 61ms

Then I should see a "Applying the highstate has been scheduled." text 337ms

When I follow "scheduled" 275ms

Then I should see a "Apply states (highstate)" text 56ms

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 707ms

Scenario:
Remove SLE minion from new group
2s 552ms 5

Given I am on the Systems overview page of this "sle_minion" 964ms

When I follow "Groups" 488ms

And I check "new-systems-group" in the list 67ms

And I click on "Leave Groups" 967ms

Then I should see a "1 system groups removed." text 64ms

@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 434ms 7

When I follow the left menu "Systems > System Groups" 74ms

When I follow "new-systems-group" in the content area 72ms

And I follow "Delete Group" in the content area 67ms

And I click on "Confirm Deletion" 1s 38ms

Then I should see a "System group" text 59ms

And I should see a "new-systems-group" text 59ms

And I should see a "deleted" text 61ms

Scenario:
Cleanup: regenerate search index for later tests
5s 87ms 1

Search by hostname: uyuni-master-suse-minion
[{"last_boot"=>"2026-03-04T22:19:57Z", "name"=>"uyuni-master-suse-minion.sumaci.aws", "id"=>1000010023, "last_checkin"=>"2026-03-05T00:44:24Z"}]

When I clean the search index on the server 5s 87ms

Scenario:
Cleanup: remove dummy packages
4s 749ms 4

When I disable repository "test_repo_rpm_pool" on this "sle_minion" without error control 775ms

And I refresh the metadata for "sle_minion" 925ms

And I remove package "andromeda-dummy" from this "sle_minion" without error control 1s 500ms

And I remove package "virgo-dummy" from this "sle_minion" without error control 1s 547ms

@scope_configuration_channels
Feature:Management of configuration of all types of clients in a single channel 6m 20s 231ms 27 1

Scenario:
Log in as org admin user
2s 23ms 1

Given I am authorized 2s 23ms

Scenario:
Create a configuration channel for mixed client types
1s 523ms 7

When I follow the left menu "Configuration > Channels" 123ms

And I follow "Create Config Channel" 373ms

And I enter "Mixed Channel" as "cofName" 62ms

And I enter "mixedchannel" as "cofLabel" 58ms

And I enter "This is a configuration channel for different system types" as "cofDescription" 94ms

And I click on "Create Config Channel" 745ms

Then I should see a "Mixed Channel" text 65ms

Scenario:
Add a configuration file to the mixed configuration channel
3s 922ms 9

When I follow the left menu "Configuration > Channels" 63ms

And I follow "Mixed Channel" 463ms

And I follow "Create Configuration File or Directory" 447ms

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" 65ms

Then I should see a "Revision 1 of /etc/s-mgr/config from channel Mixed Channel" text 776ms

And file "/srv/susemanager/salt/manager_org_1/mixedchannel/init.sls" should exist on server 1s 219ms

And file "/srv/susemanager/salt/manager_org_1/mixedchannel/etc/s-mgr/config" should exist on server 811ms

@sle_minion
Scenario:
Subscribe a Salt minion to the configuration channel
3s 411ms 8

When I am on the Systems overview page of this "sle_minion" 1s 292ms

And I follow "Configuration" in the content area 71ms

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" 827ms

And I click on "Update Channel Rankings" 951ms

Then I should see a "Channel Subscriptions successfully changed for" text 70ms

@rhlike_minion
Scenario:
Subscribe a Red Hat-like minion to the configuration channel
3s 660ms 8

When I am on the Systems overview page of this "rhlike_minion" 1s 434ms

And I follow "Configuration" in the content area 62ms

And I follow "Manage Configuration Channels" in the content area 58ms

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" 860ms

And I click on "Update Channel Rankings" 1s 61ms

Then I should see a "Channel Subscriptions successfully changed for" text 74ms

@deblike_minion
Scenario:
Subscribe a Debian-like minion to the configuration channel
3s 145ms 8

When I am on the Systems overview page of this "deblike_minion" 1s 226ms

And I follow "Configuration" in the content area 61ms

And I follow "Manage Configuration Channels" in the content area 58ms

And I follow first "Subscribe to Channels" in the content area 60ms

And I check "Mixed Channel" in the list 51ms

And I click on "Continue" 51ms

And I click on "Update Channel Rankings" 1s 561ms

Then I should see a "Channel Subscriptions successfully changed for" text 74ms

@ssh_minion
Scenario:
Subscribe a SSH minion to the configuration channel
2s 481ms 8

When I am on the Systems overview page of this "ssh_minion" 1s 188ms

And I follow "Configuration" in the content area 61ms

And I follow "Manage Configuration Channels" in the content area 60ms

And I follow first "Subscribe to Channels" in the content area 65ms

And I check "Mixed Channel" in the list 52ms

And I click on "Continue" 52ms

And I click on "Update Channel Rankings" 925ms

Then I should see a "Channel Subscriptions successfully changed for" text 76ms

Scenario:
Deploy the file to all systems
2s 144ms 7

When I follow the left menu "Configuration > Channels" 117ms

And I follow "Mixed Channel" 485ms

And I follow "Deploy all configuration files to all subscribed systems" 535ms

Then I should see a "/etc/s-mgr/config" link 13ms

When I click on "Deploy Files to Selected Systems" 865ms

Then I should see a "revision-deploys are being scheduled," text 63ms

And I should see a "0 revision-deploys overridden." text 62ms

@sle_minion
Scenario:
Check that file has been created on SLE minion
3s 48ms 2

When I wait until file "/etc/s-mgr/config" exists on "sle_minion" 2s 247ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "sle_minion" 801ms

@rhlike_minion
Scenario:
Check that file has been created on Red Hat-like minion
722ms 2

When I wait until file "/etc/s-mgr/config" exists on "rhlike_minion" 326ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "rhlike_minion" 396ms

@deblike_minion
Scenario:
Check that file has been created on Debian-like minion
1s 336ms 2

When I wait until file "/etc/s-mgr/config" exists on "deblike_minion" 936ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "deblike_minion" 400ms

@ssh_minion
Scenario:
Check that file has been created on SSH minion
5s 710ms 2

When I wait until file "/etc/s-mgr/config" exists on "ssh_minion" 4s 900ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "ssh_minion" 810ms

@sle_minion
Scenario:
Apply highstate to override changed content on SLE minion
14s 574ms 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" 415ms

And I apply highstate on "sle_minion" 13s 16ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "sle_minion" 1s 141ms

@rhlike_minion
Scenario:
Apply highstate to override changed content on Red Hat-like minion
4m 26s 692ms 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" 297ms

And I apply highstate on "rhlike_minion" 4m 10s 791ms 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 603ms Show Info + 
01:45:48:000 - 01:49:59: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 844ms 3

Salt command: salt uyuni-master-deblike-minion state.highstate

When I store "COLOR=blue" into file "/etc/s-mgr/config" on "deblike_minion" 908ms

And I apply highstate on "deblike_minion" 6s 524ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "deblike_minion" 411ms

@ssh_minion
Scenario:
Apply highstate to override changed content on SSH minion
29s 645ms 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" 739ms

And I apply highstate on "ssh_minion" 28s 100ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "ssh_minion" 806ms

@rhlike_minion
Scenario:
Unsubscribe Red Hat-like minion and delete configuration files
1s 879ms 7

When I follow the left menu "Configuration > Channels" 79ms

And I follow "Mixed Channel" 559ms

And I follow "Systems" in the content area 69ms

And I check the "rhlike_minion" client 61ms

And I click on "Unsubscribe systems" 725ms

Then I should see a "Successfully unsubscribed 1 system(s)." text 81ms

And I destroy "/etc/s-mgr" directory on "rhlike_minion" 301ms

@deblike_minion
Scenario:
Unsubscribe Debian-like minion and delete configuration files
2s 15ms 7

When I follow the left menu "Configuration > Channels" 65ms

And I follow "Mixed Channel" 619ms

And I follow "Systems" in the content area 59ms

And I check the "deblike_minion" client 59ms

And I click on "Unsubscribe systems" 728ms

Then I should see a "Successfully unsubscribed 1 system(s)." text 69ms

And I destroy "/etc/s-mgr" directory on "deblike_minion" 412ms

@ssh_minion
Scenario:
Unsubscribe SSH minion and delete configuration files
1s 846ms 7

When I follow the left menu "Configuration > Channels" 64ms

And I follow "Mixed Channel" 540ms

And I follow "Systems" in the content area 56ms

And I check the "ssh_minion" client 58ms

And I click on "Unsubscribe systems" 661ms

Then I should see a "Successfully unsubscribed 1 system(s)." text 65ms

And I destroy "/etc/s-mgr" directory on "ssh_minion" 400ms

@sle_minion
Scenario:
Change file on Salt minion and compare
7s 355ms 13

When I am on the Systems overview page of this "sle_minion" 1s 207ms

And I store "COLOR=red" into file "/etc/s-mgr/config" on "sle_minion" 708ms

And I follow "Configuration" in the content area 73ms

And I follow "Compare Files" in the content area 67ms

And I check "/etc/s-mgr/config" in the list 56ms

And I click on "Compare Files" 832ms

And I click on "Schedule Compare" 1s 18ms

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 684ms

Then I should see a "Differences exist" link 11ms

When I follow "Differences exist" 503ms

Then I should see a "+COLOR=white" text 64ms

And I should see a "-COLOR=red" text 59ms

@sle_minion
Scenario:
Check configuration channel and files via API for Salt minion
1s 136ms 3

Then channel "mixedchannel" should exist 380ms

And channel "mixedchannel" should contain file "/etc/s-mgr/config" 381ms

And "sle_minion" should be subscribed to channel "mixedchannel" 374ms

@sle_minion
Scenario:
Extend configuration channel and deploy files via API for Salt minion
4s 846ms 6

When I store "COLOR=green" into file "/etc/s-mgr/config" on "sle_minion" 394ms

And I add file "/etc/s-mgr/other" containing "NAME=Dante" to channel "mixedchannel" 482ms

And I deploy all systems registered to channel "mixedchannel" 489ms

And I wait until file "/etc/s-mgr/other" exists on "sle_minion" 1s 878ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "sle_minion" 801ms

And file "/etc/s-mgr/other" should contain "NAME=Dante" on "sle_minion" 799ms

@sle_minion
Scenario:
Unsubscribe systems via API for Salt minion
1s 273ms 2

When I unsubscribe "sle_minion" from configuration channel "mixedchannel" 861ms

Then "sle_minion" should not be subscribed to channel "mixedchannel" 411ms

@sle_minion
Scenario:
Re-add SLE Minion via SSM
3s 418ms 10

When I follow the left menu "Systems > System List > All" 132ms

And I click on the clear SSM button 64ms

And I check the "sle_minion" client 471ms

And I follow the left menu "Systems > System Set Manager > Overview" 508ms

And I follow "config channel subscriptions" in the content area 80ms

And I check "Mixed Channel" in the list 56ms

And I click on "Continue" 57ms

And I click on "Apply Subscriptions" 1s 309ms

And I click on "Confirm" 677ms

Then I should see a "Configuration channel subscriptions changed for 1 system successfully." text 60ms

@sle_minion
Scenario:
Cleanup: remove remaining Salt minion from configuration channel
1s 380ms 6

When I follow the left menu "Configuration > Channels" 125ms

And I follow "Mixed Channel" 501ms

And I follow "Systems" in the content area 67ms

And I check the "sle_minion" client 61ms

And I click on "Unsubscribe systems" 572ms

Then I should see a "Successfully unsubscribed 1 system(s)." text 52ms

Scenario:
Cleanup: remove the mixed configuration channel
2s 418ms 5

When I follow the left menu "Configuration > Channels" 65ms

And I follow "Mixed Channel" 485ms

And I follow "Delete Channel" 287ms

And I click on "Delete Config Channel" 481ms

Then file "/srv/susemanager/salt/manager_org_1/mixedchannel/init.sls" should not exist on server 1s 99ms

@sle_minion
Scenario:
Cleanup: delete configuration files on remaining Salt minion
716ms 1

When I destroy "/etc/s-mgr" directory on "sle_minion" 716ms

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 968ms 14 5

Scenario:
Log in as org admin user
1s 614ms 1

Given I am authorized 1s 614ms

@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 257ms 22

When I follow the left menu "Systems > System List > All" 191ms

And I click on the clear SSM button 56ms

And I check the "sle_minion" client 451ms

And I should see "1" systems selected for SSM 149ms

And I follow the left menu "Systems > System Set Manager > Overview" 476ms

And I follow "channel memberships" in the content area 66ms

Then I should see a "Base Channel" text 70ms

And I should see a "Next" text 68ms

When I select "Fake-Base-Channel-SUSE-like" from drop-down in table line with "openSUSE Tumbleweed (x86_64)" 133ms

And I click on "Next" 60ms

Then I should see a "Child Channels" text 402ms

And I should see a "Fake-Base-Channel-SUSE-like" text 68ms

And I should see a "1 system(s) to subscribe" text 74ms

When I choose radio button "Subscribe" for child channel "Fake-Child-Channel-SUSE-like" 70ms

And I click on "Next" 60ms

Then I should see a "Channel Changes Overview" text 65ms

And I should see a "1 system(s) to subscribe" text 62ms

When I schedule action to 3 minutes from now 235ms

And I click on "Confirm" 60ms

And I remember when I scheduled an action < 1ms

Then I wait until I see "Channel Changes Actions" text 409ms

And a table line should contain system "sle_minion", "Scheduled" 21ms

@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 939ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 62ms

When I follow "Software" in the content area 70ms

And I follow "Software Channels" in the content area 66ms

And I wait until I do not see "Loading..." text 64ms

Then radio button "openSUSE Tumbleweed (x86_64)" should be checked 162ms

And I wait until I do not see "Loading..." text 494ms

And I should see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" as unchecked 19ms

@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 736ms 3

When I refresh the metadata for "sle_minion" 1s 253ms

Then channel "openSUSE Tumbleweed (x86_64)" should be enabled on "sle_minion" 728ms

And channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" should be disabled on "sle_minion" 754ms

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 14s 68ms 3

Given I am on the Systems overview page of this "sle_minion" 1s 29ms

When I wait until event "Subscribe channels scheduled" is completed 1m 12s 973ms

Then I should see a "The client completed this action on" text 64ms

@sle_minion
Scenario:
Check the SLES minion is subscribed to the new channels
1s 938ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 126ms

When I follow "Software" in the content area 76ms

And I follow "Software Channels" in the content area 65ms

And I wait until I do not see "Loading..." text 63ms

Then radio button "Fake-Base-Channel-SUSE-like" should be checked 174ms

And I wait until I do not see "Loading..." text 412ms

And I should see "Fake-Child-Channel-SUSE-like" as checked 18ms

@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 900ms 4

When I refresh the metadata for "sle_minion" 1s 537ms

Then "2" channels should be enabled on "sle_minion" 802ms

And channel "Fake-Base-Channel-SUSE-like" should be enabled on "sle_minion" 789ms

And channel "Fake-Child-Channel-SUSE-like" should be enabled on "sle_minion" 771ms

@rhlike_minion
Scenario:
System default channel can't be determined on the Red Hat-like minion
2s 752ms 20

When I follow the left menu "Systems > System List > All" 131ms

And I click on the clear SSM button 52ms

And I check the "rhlike_minion" client 443ms

Then I should see "1" systems selected for SSM 118ms

When I follow the left menu "Systems > System Set Manager > Overview" 486ms

And I follow "channel memberships" in the content area 67ms

And I select "System Default Base Channel" from drop-down in table line with "Fake-Base-Channel-RH-like" 244ms

And I click on "Next" 59ms

Then I should see a "Child Channels" text 286ms

And I should see a "Couldn't determine new base channel" text 60ms

And I should see a "1 system(s) incompatible" text 60ms

When I click on "Next" 59ms

Then I should see a "Channel Changes Overview" text 60ms

And I should see a "Couldn't determine new base channel" text 63ms

And I should see a "1 system(s) incompatible" text 68ms

When I click on "Confirm" 58ms

Then I should see a "Channel Changes Actions" text 281ms

And I should see a "Items 1 - 1 of 1" text 79ms

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 466ms 4

Given I am on the Systems overview page of this "rhlike_minion" 1s 42ms

When I follow "Software" in the content area 66ms

And I follow "Software Channels" in the content area 77ms

Then radio button "Fake-Base-Channel-RH-like" should be checked 280ms

@deblike_minion
Scenario:
System default channel can't be determined on the Debian-like minion
2s 622ms 20

When I follow the left menu "Systems > System List > All" 114ms

And I click on the clear SSM button 47ms

And I check the "deblike_minion" client 444ms

Then I should see "1" systems selected for SSM 114ms

When I follow the left menu "Systems > System Set Manager > Overview" 452ms

And I follow "channel memberships" in the content area 62ms

And I select "System Default Base Channel" from drop-down in table line with "Fake-Base-Channel-Debian-like" 198ms

And I click on "Next" 56ms

Then I should see a "Child Channels" text 280ms

And I should see a "Couldn't determine new base channel" text 64ms

And I should see a "1 system(s) incompatible" text 60ms

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 70ms

And I should see a "1 system(s) incompatible" text 71ms

When I click on "Confirm" 52ms

Then I should see a "Channel Changes Actions" text 284ms

And I should see a "Items 1 - 1 of 1" text 64ms

And a table line should contain system "deblike_minion", "Could not determine system default channel" 17ms

And I click on the clear SSM button 48ms

@deblike_minion
Scenario:
Cleanup: make sure the Debian-like minion is still unchanged
1s 416ms 4

Given I am on the Systems overview page of this "deblike_minion" 1s 64ms

When I follow "Software" in the content area 57ms

And I follow "Software Channels" in the content area 57ms

Then radio button "Fake-Base-Channel-Debian-like" should be checked 236ms

@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 191ms 15

Given I am on the Systems overview page of this "sle_minion" 1s 61ms

When I follow "Software" in the content area 61ms

And I follow "Software Channels" in the content area 55ms

And I wait until I do not see "Loading..." text 63ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 10s 84ms

And I wait until I do not see "Loading..." text 507ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 78ms

And I check "Fake-RPM-SUSE-Channel" 79ms

And I click on "Next" 53ms

Then I should see a "Confirm Software Channel Change" text 61ms

When I click on "Confirm" 68ms

Then I should see a "Changing the channels has been scheduled." text 400ms

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 793ms

Then channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" should be disabled on "sle_minion" 744ms

Scenario:
Cleanup: remove remaining systems from SSM after channel subscription tests
64ms 1

When I click on the clear SSM button 64ms

@scope_changing_software_channels @scc_credentials
Feature:Channel subscription with recommended or required dependencies 46s 718ms 5 2

Scenario:
Log in as org admin user
1s 818ms 1

Given I am authorized 1s 818ms

Scenario:
Pre-requisite: remove remaining systems from SSM after software channel tests
55ms 1

When I click on the clear SSM button 55ms

@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 774ms 10

Given I am on the Systems overview page of this "sle_minion" 1s 686ms

When I follow "Software" in the content area 73ms

And I follow "Software Channels" in the content area 67ms

And I wait for child channels to appear 212ms

And I check radio button "(none, disable service)" 10s 63ms

And I wait for child channels to appear 223ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 10s 75ms

Then I should see the child channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" "unselected" and "disabled" 10s 109ms

When I select the child channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" 10s 160ms

Then I should see the child channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" "selected" 102ms

@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
2s 9ms 10

When I follow the left menu "Systems > System List > All" 139ms

And I check the "sle_minion" client 493ms

Then I should see "1" systems selected for SSM 141ms

When I follow the left menu "Systems > System Set Manager > Overview" 477ms

And I follow "channel memberships" in the content area 88ms

Then I should see a "Base Channel" text 64ms

And I should see a "Next" text 59ms

When I select "No Change" from drop-down in table line with "openSUSE Tumbleweed (x86_64)" 112ms

And I click on "Next" 57ms

Then I should see the toggler "disabled" 373ms

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 37s 444ms 9 1

Scenario:
Pre-requisite: enable test_repo_rpm_pool repository on the Red Hat-like minion
294ms 1

When I enable repository "test_repo_rpm_pool" on this "rhlike_minion" 294ms

Scenario:
Pre-requisite: install virgo-dummy-1.0 package on Red Hat-like minion
1s 601ms 1

When I install package "virgo-dummy-1.0" on this "rhlike_minion" 1s 601ms

Scenario:
Pre-requisite: remove andromeda-dummy package from Red Hat-like minion
1s 586ms 1

When I remove package "andromeda-dummy" from this "rhlike_minion" 1s 586ms

Scenario:
Pre-requisite: refresh package list and check newly installed packages on Red Hat-like minion
18s 199ms 1 2 1

When I refresh packages list via spacecmd on "rhlike_minion" 2s 616ms 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 582ms Show Info + 
01:58:31:000 - 01:58:33:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channel/ssm/ChannelSubscriptions.do
Screenshot +

Scenario:
Log in as org admin user
1s 487ms 1

Given I am authorized for the "Admin" section 1s 487ms

Scenario:
Pre-requisite: re-subscribe the Red Hat-like minion to a base channel
21s 576ms 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 476ms

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 66ms

And I check radio button "Fake-Base-Channel-RH-like" 157ms

And I wait until I do not see "Loading..." text 409ms

And I click on "Next" 61ms

Then I should see a "Confirm Software Channel Change" text 63ms

When I click on "Confirm" 80ms

Then I should see a "Changing the channels has been scheduled." text 296ms

And I wait until event "Subscribe channels scheduled" is completed 18s 827ms

Scenario:
Schedule errata refresh to reflect channel assignment on Red Hat-like minion
47s 591ms 10

When I follow "Software" in the content area 62ms

And I follow "List / Remove" in the content area 65ms

And I enter "virgo-dummy" as the filtered package name 133ms

And I click on the filter button until page does contain "virgo-dummy" text 11s 180ms

When I follow the left menu "Admin > Task Schedules" 120ms

And I follow "errata-cache-default" 1s 173ms

And I follow "errata-cache-bunch" 1s 279ms

And I click on "Single Run Schedule" 1s 525ms

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 781ms

Scenario:
Install a patch on the Red Hat-like minion
15s 53ms 8

Given I am on the Systems overview page of this "rhlike_minion" 1s 36ms

When I follow "Software" in the content area 88ms

And I follow "Patches" in the content area 82ms

When I check "virgo-dummy-3456" in the list 65ms

And I click on "Apply Patches" 715ms

And I click on "Confirm" 771ms

Then I should see a "1 patch update has been scheduled for" text 86ms

And I wait for "virgo-dummy-2.0-1.1" to be installed on "rhlike_minion" 12s 207ms

Scenario:
Install a package on the Red Hat-like minion
24s 214ms 7

When I follow "Software" in the content area 64ms

And I follow "Install" 528ms

And I check "andromeda-dummy" in the list 64ms

And I click on "Install Packages" 744ms

And I click on "Confirm" 774ms

Then I should see a "1 package install has been scheduled for" text 68ms

And I wait until event "Package Install/Upgrade scheduled" is completed 21s 969ms

Scenario:
Cleanup: remove virgo-dummy and andromeda-dummy packages from Red Hat-like minion
25s 839ms 13

When I follow "Software" in the content area 81ms

And I follow "List / Remove" 699ms

And I enter "andromeda" as the filtered package name 142ms

And I click on the filter button 805ms

And I check "andromeda-dummy" in the list 60ms

And I enter "virgo-dummy" as the filtered package name 42ms

And I click on the filter button 124ms

And I check "virgo-dummy" in the list 56ms

And I click on "Remove Packages" 682ms

And I click on "Confirm" 760ms

Then I should see a "2 package removals have been scheduled" text 63ms

And I wait until event "Package Removal scheduled" is completed 22s 5ms

And I disable repository "test_repo_rpm_pool" on this "rhlike_minion" 313ms

@scope_monitoring @scope_res @rhlike_minion
Feature:Monitor MLM environment with Prometheus on a Red Hat-like Salt minion 1m 12s 125ms 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 771ms 7

Given I am on the Systems overview page of this "rhlike_minion" 1s 711ms

When I follow "Formulas" in the content area 76ms

Then I should see a "Choose formulas:" text 61ms

And I should see a "Monitoring" text 182ms

When I check the "prometheus-exporters" formula 76ms

And I click on "Save" 67ms

And I wait until I see "Formula saved" text 595ms

Scenario:
Configure Prometheus exporter formula on the Red Hat-like minion
2s 216ms 9

When I follow "Formulas" in the content area 67ms

And I follow "Prometheus Exporters" in the content area 211ms

And I click on "Expand All Sections" 264ms

Then I should see a "Enable and configure Prometheus exporters for managed systems." text 104ms

When I check "node" exporter 44ms

And I check "apache" exporter 114ms

And I check "postgres" exporter 89ms

And I click on "Save" 69ms

Then I should see a "Formula saved" text 1s 250ms

Scenario:
Enable tools_update_repo tools_pool_repo so the exporters packages are available
530ms 1

When I enable the repositories "tools_update_repo tools_pool_repo" on this "rhlike_minion" without error control 530ms

@skip_if_github_validation
Scenario:
Apply highstate for Prometheus exporters on the Red Hat-like minion
39s 217ms 4

When I follow "States" in the content area 72ms

And I click on "Apply Highstate" 61ms

Then I should see a "Applying the highstate has been scheduled." text 444ms

And I wait until event "Apply highstate scheduled" is completed 38s 638ms

@skip_if_github_validation
Scenario:
Wait for service
723ms 3

When I wait until "node" exporter service is active on "rhlike_minion" 327ms

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" 195ms

Scenario:
Visit monitoring endpoints on the Red Hat-like minion
599ms 3

When I visit "Prometheus node exporter" endpoint of this "rhlike_minion" 195ms

And I visit "Prometheus apache exporter" endpoint of this "rhlike_minion" 196ms

And I visit "Prometheus postgres exporter" endpoint of this "rhlike_minion" 207ms

Scenario:
Cleanup: undo Prometheus exporter formulas on the Red Hat-like minion
1s 370ms 4

When I follow "Formulas" in the content area 80ms

And I uncheck the "prometheus-exporters" formula 225ms

And I click on "Save" 64ms

Then I wait until I see "Formula saved" text 1s

@skip_if_github_validation
Scenario:
Cleanup: apply highstate after test monitoring on the Red Hat-like minion
22s 680ms 4

When I follow "States" in the content area 81ms

And I click on "Apply Highstate" 63ms

Then I should see a "Applying the highstate has been scheduled." text 429ms

And I wait until event "Apply highstate scheduled" is completed 22s 105ms

Scenario:
Cleanup: Disable tools_update_repo tools_pool_repo because they are no longer needed
302ms 1

When I disable the repositories "tools_update_repo tools_pool_repo" on this "rhlike_minion" without error control 302ms

@skip_if_github_validation @scope_salt
Feature:Install a package and a patch on the SUSE SSH client via Salt through the UI 3m 56s 307ms 11

Scenario:
Pre-requisite: enable test_repo_rpm_pool repository on SSH minion
780ms 1

When I enable repository "test_repo_rpm_pool" on this "ssh_minion" 780ms

Scenario:
Pre-requisite: install virgo-dummy-1.0 package on SSH minion
2s 188ms 2

When I refresh the metadata for "ssh_minion" 942ms

And I install old package "virgo-dummy-1.0" on this "ssh_minion" without error control 1s 245ms

Scenario:
Pre-requisite: remove andromeda-dummy package from SSH minion
26s 51ms 4

When I remove package "andromeda-dummy" from this "ssh_minion" without error control 779ms

And I refresh the metadata for "ssh_minion" 815ms

And I refresh packages list via spacecmd on "ssh_minion" 2s 828ms

And I wait until refresh package list on "ssh_minion" is finished 21s 627ms

Scenario:
Pre-requisite: refresh package list and check old packages installed on SSH minion
29s 872ms 4

When I refresh packages list via spacecmd on "ssh_minion" 2s 443ms

And I wait until refresh package list on "ssh_minion" is finished 21s 548ms

Then spacecmd should show packages "virgo-dummy-1.0" installed on "ssh_minion" 2s 436ms

And I wait until package "andromeda-dummy-2.0-1.1" is removed from "ssh_minion" via spacecmd 3s 443ms

Scenario:
Log in as org admin user
1s 696ms 1

Given I am authorized for the "Admin" section 1s 696ms

Scenario:
Pre-requisite: ensure the errata cache is computed before patching Salt minion
18s 428ms 11

Given I am on the Systems overview page of this "ssh_minion" 1s 538ms

When I follow "Software" in the content area 72ms

And I follow "List / Remove" in the content area 64ms

And I enter "virgo-dummy" as the filtered package name 174ms

And I click on the filter button until page does contain "virgo-dummy" text 10s 895ms

When I follow the left menu "Admin > Task Schedules" 122ms

And I follow "errata-cache-default" 413ms

And I follow "errata-cache-bunch" 1s 271ms

And I click on "Single Run Schedule" 1s 530ms

Then I should see a "bunch was scheduled" text 262ms

When I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 2s 82ms

Scenario:
Install a patch on the SSH minion
42s 554ms 12

Given I am on the Systems overview page of this "ssh_minion" 1s 64ms

When I follow "Software" in the content area 73ms

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 150ms

And I check "virgo-dummy-3456" in the list 59ms

And I check "allowVendorChange" 75ms

And I click on "Apply Patches" 620ms

And I click on "Confirm" 675ms

Then I should see a "1 patch update has been scheduled for" text 71ms

When I wait for "virgo-dummy-2.0-1.1" to be installed on "ssh_minion" 28s 822ms

Then vendor change should be enabled for package actions on "ssh_minion" 829ms

Scenario:
Install a package on the SSH minion
46s 588ms 12

Given I am on the Systems overview page of this "ssh_minion" 1s 111ms

When I follow "Software" in the content area 77ms

And I follow "Packages" 514ms

And I follow "Install" 538ms

And I enter "andromeda" as the filtered package name 112ms

And I click on the filter button 599ms

And I check "andromeda-dummy-2.0-1.1" in the list 55ms

And I click on "Install Packages" 668ms

And I click on "Confirm" 783ms

Then I should see a "1 package install has been scheduled" text 61ms

When I wait for "andromeda-dummy-2.0-1.1" to be installed on "ssh_minion" 40s 955ms

Then vendor change should be enabled for package actions on "ssh_minion" 1s 108ms

Scenario:
Cleanup: disable test_repo_rpm_pool on SSH minion
435ms 1

When I disable repository "test_repo_rpm_pool" on this "ssh_minion" 435ms

Scenario:
Cleanup: remove virgo-dummy package from SSH minion
41s 475ms 4

When I remove package "virgo-dummy" from this "ssh_minion" without error control 1s 295ms

And I refresh the metadata for "ssh_minion" 929ms

And I refresh packages list via spacecmd on "ssh_minion" 2s 830ms

And I wait until refresh package list on "ssh_minion" is finished 36s 420ms

Scenario:
Cleanup: remove andromeda-dummy package from SSH minion
26s 236ms 4

When I remove package "andromeda-dummy" from this "ssh_minion" without error control 1s 226ms

And I refresh the metadata for "ssh_minion" 838ms

And I refresh packages list via spacecmd on "ssh_minion" 2s 369ms

And I wait until refresh package list on "ssh_minion" is finished 21s 801ms

@scope_ansible @scope_salt_ssh @ssh_minion
Feature:Operate an Ansible control node in SSH minion 4m 14s 936ms 12 2

Scenario:
Log in as org admin user
421ms 1

Given I am authorized for the "Admin" section 421ms

Scenario:
Pre-requisite: Deploy test playbooks and inventory file
3s 814ms 1

When I deploy testing playbooks and inventory files to "ssh_minion" 3s 814ms

@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
3s 16ms 5

Given I am on the Systems overview page of this "ssh_minion" 1s 206ms

When I follow "Properties" in the content area 69ms

And I check "ansible_control_node" 82ms

And I click on "Update Properties" 1s 570ms

Then I wait until I see "Ansible Control Node type has been applied." text 86ms

Scenario:
Apply highstate and check that Ansible is installed
1m 13s 477ms 5

Given I am on the Systems overview page of this "ssh_minion" 1s 194ms

When I follow "States" in the content area 67ms

And I click on "Apply Highstate" 58ms

And I wait until event "Apply highstate scheduled" is completed 1m 11s 688ms

Then "ansible" should be installed on "ssh_minion" 467ms

Scenario:
The Ansible tab appears in the system overview page
1s 226ms 3

Given I am on the Systems overview page of this "ssh_minion" 1s 88ms

When I follow "Ansible" in the content area 78ms

Then I should see a "Ansible Control Node Configuration" text 60ms

Scenario:
Configure some inventory and playbooks path
1s 587ms 7

Given I am on the Systems overview page of this "ssh_minion" 1s 103ms

When I follow "Ansible" in the content area 59ms

Then I should see a "Ansible Control Node Configuration" text 66ms

And I enter "/srv/playbooks/" as "new_playbook_path_input" 139ms

And I click on "new_playbook_path_save" 59ms

And I enter "/srv/playbooks/orion_dummy/hosts" as "new_inventory_path_input" 99ms

And I click on "new_inventory_path_save" 59ms

Scenario:
Display inventories
20s 508ms 6

Given I am on the Systems overview page of this "ssh_minion" 1s 242ms

When I follow "Ansible" in the content area 60ms

And I follow "Inventories" in the content area 62ms

And I wait until I see "/srv/playbooks/orion_dummy/hosts" text 244ms

And I click on "/srv/playbooks/orion_dummy/hosts" 57ms

Then I wait until I see "myself" text 18s 840ms

Scenario:
Discover playbooks and display them
10s 230ms 6

Given I am on the Systems overview page of this "ssh_minion" 1s 115ms

When I follow "Ansible" in the content area 79ms

And I follow "Playbooks" in the content area 61ms

And I wait until I see "/srv/playbooks" text 246ms

And I click on "/srv/playbooks" 59ms

Then I wait until I see "/srv/playbooks/orion_dummy/playbook_orion_dummy.yml" text 8s 667ms

Scenario:
Run a playbook using custom inventory
56s 510ms 13

Given I am on the Systems overview page of this "ssh_minion" 1s 59ms

When I follow "Ansible" in the content area 61ms

And I follow "Playbooks" in the content area 58ms

And I wait until I see "/srv/playbooks" text 241ms

And I click on "/srv/playbooks" 51ms

And I wait until I see "/srv/playbooks/orion_dummy/playbook_orion_dummy.yml" text 8s 582ms

And I click on "orion_dummy/playbook_orion_dummy.yml" 60ms

And I wait until I see "Playbook Content" text 5s 576ms

And I select "/srv/playbooks/orion_dummy/hosts" from "inventory-path-select" 1s 123ms

And I click on "Schedule" 61ms

Then I should see a "Playbook execution has been scheduled" text 362ms

And I wait until event "Execute playbook 'playbook_orion_dummy.yml' scheduled" is completed 38s 510ms

And file "/tmp/file.txt" should exist on "ssh_minion" 759ms

Scenario:
Cleanup: Disable Ansible and remove test playbooks and inventory file
14s 829ms 7

Given I am on the Systems overview page of this "ssh_minion" 1s 76ms

When I follow "Properties" in the content area 80ms

And I uncheck "ansible_control_node" 10s 96ms

And I click on "Update Properties" 1s 444ms

Then I should see a "System properties changed" text 91ms

And I remove package "orion-dummy" from this "ssh_minion" without error control 1s 636ms

And I remove "/tmp/file.txt" from "ssh_minion" 402ms

@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 410ms 4

Given I am on the Systems overview page of this "ssh_minion" 1s 171ms

When I follow "Properties" in the content area 80ms

And I uncheck "ansible_control_node" 10s 49ms

And I click on "Update Properties" 1s 108ms

Scenario:
Cleanup: Apply highstate to disable the minion as an "Ansible control node"
56s 903ms 4

Given I am on the Systems overview page of this "ssh_minion" 1s 230ms

When I follow "States" in the content area 75ms

And I click on "Apply Highstate" 65ms

And I wait until event "Apply highstate scheduled" is completed 55s 531ms

@scope_monitoring @scope_res @deblike_minion
Feature:Monitor MLM environment with Prometheus on a Debian-like Salt minion 1m 30s 278ms 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 746ms 1

Given I am authorized 1s 746ms

Scenario:
Apply Prometheus exporter formulas on the Debian-like minion
2s 717ms 7

Given I am on the Systems overview page of this "deblike_minion" 1s 679ms

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 183ms

When I check the "prometheus-exporters" formula 75ms

And I click on "Save" 63ms

And I wait until I see "Formula saved" text 583ms

Scenario:
Configure Prometheus exporter formula on the Debian-like minion
2s 210ms 9

When I follow "Formulas" in the content area 63ms

And I follow "Prometheus Exporters" in the content area 246ms

And I click on "Expand All Sections" 246ms

Then I should see a "Enable and configure Prometheus exporters for managed systems." text 106ms

When I check "node" exporter 46ms

And I check "apache" exporter 85ms

And I check "postgres" exporter 89ms

And I click on "Save" 67ms

Then I should see a "Formula saved" text 1s 258ms

Scenario:
Enable tools_update_repo tools_pool_repo so the exporters packages are available
1s 299ms 1

When I enable the repositories "tools_update_repo tools_pool_repo" on this "deblike_minion" without error control 1s 299ms

@skip_if_github_validation
Scenario:
Apply highstate for Prometheus exporters on the Debian-like minion
55s 899ms 4

When I follow "States" in the content area 70ms

And I click on "Apply Highstate" 58ms

Then I should see a "Applying the highstate has been scheduled." text 437ms

And I wait until event "Apply highstate scheduled" is completed 55s 332ms

@skip_if_github_validation
Scenario:
Wait for services
867ms 3

When I wait until "node" exporter service is active on "deblike_minion" 432ms

And I wait until "apache" exporter service is active on "deblike_minion" 222ms

And I wait until "postgres" exporter service is active on "deblike_minion" 213ms

Scenario:
Visit monitoring endpoints on the Debian-like minion
610ms 3

And I visit "Prometheus node exporter" endpoint of this "deblike_minion" 201ms

And I visit "Prometheus apache exporter" endpoint of this "deblike_minion" 201ms

And I visit "Prometheus postgres exporter" endpoint of this "deblike_minion" 206ms

Scenario:
Cleanup: undo Prometheus exporter formulas on the Debian-like minion
1s 366ms 4

When I follow "Formulas" in the content area 78ms

And I uncheck the "prometheus-exporters" formula 246ms

And I click on "Save" 63ms

Then I wait until I see "Formula saved" text 978ms

@skip_if_github_validation
Scenario:
Cleanup: apply highstate after test monitoring on the Debian-like minion
22s 656ms 4

When I follow "States" in the content area 68ms

And I click on "Apply Highstate" 59ms

Then I should see a "Applying the highstate has been scheduled." text 457ms

And I wait until event "Apply highstate scheduled" is completed 22s 71ms

Scenario:
Cleanup: Disable tools_update_repo tools_pool_repo because they are no longer needed
903ms 1

When I disable the repositories "tools_update_repo tools_pool_repo" on this "deblike_minion" without error control 903ms

@deblike_minion @scope_deblike @scope_content_staging
Feature:Install a package on the Debian-like minion with staging enabled 3m 59s 255ms 7 1

Scenario:
Pre-requisite: install virgo-dummy-1.0 package, make sure orion-dummy is not present on Debian-like minion
1s 849ms 4

When I enable repository "test_repo_deb_pool" on this "deblike_minion" 437ms

And I run "apt update" on "deblike_minion" 901ms

And I remove package "orion-dummy" from this "deblike_minion" 264ms

And I install old package "virgo-dummy=1.0" on this "deblike_minion" 247ms

Scenario:
Pre-requisite: refresh package list on Debian-like minion
12s 750ms 3

When I refresh packages list via spacecmd on "deblike_minion" 2s 751ms

And I wait until refresh package list on "deblike_minion" is finished 7s 487ms

Then spacecmd should show packages "virgo-dummy-1.0" installed on "deblike_minion" 2s 511ms

Scenario:
Log in as admin user
1s 731ms 1

Given I am authorized for the "Admin" section 1s 731ms

Scenario:
Pre-requisite: ensure the errata cache is computed for Debian-like minion
13s 104ms 6

When I follow the left menu "Admin > Task Schedules" 123ms

And I follow "errata-cache-default" 1s 343ms

And I follow "errata-cache-bunch" 1s 264ms

Then I click on "Single Run Schedule" 1s 557ms

And I should see a "bunch was scheduled" text 269ms

Then I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 8s 546ms

Scenario:
Enable content staging for Debian-like minion
1s 203ms 6

When I follow the left menu "Admin > Organizations" 74ms

And I follow first "SUSE Test" 323ms

And I follow first "Configuration" 282ms

And I check "staging_content_enabled" 44ms

And I click on "Update Organization" 415ms

Then I should see a "was successfully updated." text 63ms

Scenario:
Install package in the future and check for staging on Debian-like minion
3m 555ms 13

Given I am on the Systems overview page of this "deblike_minion" 1s 58ms

And I follow "Software" in the content area 72ms

And I follow "Packages" in the content area 71ms

And I follow "Install" in the content area 67ms

And I enter "orion-dummy-1.1-X" as the filtered package name 60ms

And I click on the filter button 498ms

When I check "orion-dummy-1.1-X" in the list 61ms

And I click on "Install Packages" 589ms

And I pick 3 minutes from now as schedule time 88ms

And I click on "Confirm" 769ms

Then I should see a "1 package install has been scheduled for" text 64ms

And I wait until the package "orion-dummy_1.1" has been cached on this "deblike_minion" 33s 487ms

And I wait for "orion-dummy-1.1" to be installed on "deblike_minion" 2m 23s 663ms

Scenario:
Install patch in the future and check for staging on Debian-like minion
25s 334ms 3 8 1

When I follow "Software" in the content area 64ms

And I follow "Patches" in the content area 66ms

And I enter "virgo" as the filtered synopsis 10s 13ms 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 190ms Show Info + 
02:17:06:000 - 02:17:17: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 726ms 4

And I remove package "orion-dummy" from this "deblike_minion" 1s 88ms

And I remove package "virgo-dummy" from this "deblike_minion" 340ms

And I disable repository "test_repo_deb_pool" on this "deblike_minion" 210ms

And I run "apt update" on "deblike_minion" 1s 87ms

@scope_deblike @scope_salt @deblike_minion
Feature:Install and upgrade package on the Debian-like minion via Salt through the UI 1m 31s 231ms 9 1 1

Scenario:
Pre-requisite: enable test_repo_deb_pool repository on the Debian-like minion
442ms 1

When I enable repository "test_repo_deb_pool" on this "deblike_minion" 442ms

Scenario:
Pre-requisite: install virgo-dummy-1.0 package on Debian-like minion
2s 933ms 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,517 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 900ms

And I install old package "virgo-dummy=1.0" on this "deblike_minion" 2s 33ms

Scenario:
Pre-requisite: remove andromeda-dummy package from Debian-like minion
373ms 1

When I remove package "andromeda-dummy" from this "deblike_minion" 373ms

Scenario:
Log in as org admin user
1s 802ms 1

Given I am authorized 1s 802ms

Scenario:
Pre-requisite: refresh package list and check newly installed packages on Debian-like minion
33s 114ms 7

Given I am on the Systems overview page of this "deblike_minion" 2s 21ms

When I follow "Software" in the content area 77ms

And I click on "Update Package List" 605ms

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 196ms

And I wait until package "virgo-dummy" is installed on "deblike_minion" via spacecmd 2s 762ms

And I wait until package "andromeda-dummy" is removed from "deblike_minion" via spacecmd 3s 383ms

Scenario:
Install a patch on the Debian-like minion
25s 290ms 3 4 1

When I follow "Software" in the content area 63ms

And I follow "Patches" in the content area 64ms

When I check "3456-1" in the list 10s 9ms 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 153ms Show Info + 
02:18:30:000 - 02:18:41: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
25s 264ms 8

When I follow "Software" in the content area 63ms

And I follow "Install" 579ms

And I check "andromeda-dummy-2.0" in the list 64ms

And I click on "Install Packages" 743ms

And I click on "Confirm" 805ms

And I should see a "1 package install has been scheduled for" text 61ms

When I wait until event "Package Install/Upgrade scheduled" is completed 22s 4ms

Then Deb package "andromeda-dummy" with version "2.0" should be installed on "deblike_minion" 941ms

Scenario:
Cleanup: disable test_repo_deb_pool on Debian-like minion
207ms 1

When I disable repository "test_repo_deb_pool" on this "deblike_minion" 207ms

Scenario:
Cleanup: remove virgo-dummy package from Debian-like minion
369ms 1

When I remove package "virgo-dummy" from this "deblike_minion" 369ms

Scenario:
Cleanup: remove andromeda-dummy package from Debian-like minion
1s 433ms 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" 362ms

And I run "apt update" on "deblike_minion" with logging 1s 70ms

@skip_if_github_validation @sle_minion @scope_onboarding
Feature:Negative tests for bootstrapping normal minions 20s 486ms 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 747ms 1

Given I am authorized 1s 747ms

Scenario:
Bootstrap should fail when minion already exists
946ms 10

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 124ms

Then I should see a "Bootstrap Minions" text 65ms

When I enter the hostname of "sle_minion" as "hostname" 138ms

And I enter "22" as "port" 54ms

And I enter "root" as "user" 60ms

And I enter "linux" as "password" 57ms

And I click on "Bootstrap" 67ms

And I wait until I see "A salt key for this host" text 259ms

Then I should not see a "GenericSaltError" text 59ms

And I should see a "seems to already exist, please check!" text 59ms

Scenario:
Bootstrap a SLES minion with wrong hostname
3s 71ms 14

When I follow the left menu "Systems > Bootstrapping" 63ms

Then I should see a "Bootstrap Minions" text 64ms

When I enter "not-existing-name" as "hostname" 82ms

And I enter "22" as "port" 46ms

And I enter "root" as "user" 50ms

And I enter "linux" 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 2s 408ms

Then I should see a "Details" button 17ms

When I click on "Details" 75ms

And I wait at most 10 seconds until I see modal containing "Error Details" text 11ms

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 16ms

When I close the modal dialog 54ms

Scenario:
Bootstrap a SLES minion with wrong SSH credentials
11s 799ms 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 63ms

When I enter the hostname of "localhost" as "hostname" 125ms

And I enter "22" as "port" 48ms

And I enter "FRANZ" as "user" 55ms

And I enter "KAFKA" as "password" 57ms

And I click on "Bootstrap" 55ms

And I wait until I see "An error has occurred during salt execution: unable to establish ssh connection." text 11s 122ms

Then I should see a "Details" button 14ms

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 67ms

And I should see "Permission denied (publickey" or "Password authentication failed" in the stderr textarea 13ms

When I close the modal dialog 45ms

Scenario:
Bootstrap a SLES minion with wrong SSH port number
2s 921ms 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" 126ms

And I enter "11" as "port" 49ms

And I enter "root" as "user" 51ms

And I enter "linux" as "password" 55ms

And I click on "Bootstrap" 55ms

And I wait until I see "An error has occurred during salt execution: unable to establish ssh connection." text 2s 242ms

Then I should see a "Details" button 15ms

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 67ms

And I should see "port 11: Connection refused" or "port 11: Network is unreachable" in the stderr textarea 13ms

When I close the modal dialog 49ms

@skip_if_github_validation @scope_formulas @bug_reported
Feature:Use salt formulas 4m 25s 533ms 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 761ms 1

Given I am authorized 1s 761ms

@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 416ms 1

When I synchronize all Salt dynamic modules on "sle_minion" 3s 416ms

Scenario:
The new formula appears on the server
356ms 2

When I follow the left menu "Salt > Formula Catalog" 129ms

Then I should see a "locale" text in the content area 226ms

Scenario:
Enable the formula on the minion
12s 528ms 9

Given I am on the Systems overview page of this "sle_minion" 1s 205ms

When I follow "Formulas" in the content area 72ms

Then I should see a "Choose formulas:" text 63ms

And I should see a "General System Configuration" text 190ms

And I should see a "Locale" text 90ms

When I check the "locale" formula 77ms

And I click on "Save" 64ms

And I wait until I see "Formula saved." text 721ms

Then the "locale" formula should be checked 10s 43ms

Scenario:
Parametrize the formula on the minion
1s 416ms 8

When I follow "Formulas" in the content area 63ms

And I follow first "Locale" in the content area 214ms

And I click on "Expand All Sections" 226ms

And I select "Etc/GMT-5" in timezone name field 61ms

And I select "French" in language field 43ms

And I select "French (Canada)" in keyboard layout field 43ms

And I click on "Save Formula" 61ms

Then I should see a "Formula saved" text 702ms

Scenario:
Check the pillar data after saving the formula
9s 700ms 5

When I refresh the pillar data 2s 699ms

Then the pillar data for "formulas" should be "- locale" on "sle_minion" 1s 762ms

And the pillar data for "timezone:name" should be "Etc/GMT-5" on "sle_minion" 1s 729ms

And the pillar data for "keyboard_and_language:keyboard_layout" should be "French (Canada)" on "sle_minion" 1s 733ms

And the pillar data for "keyboard_and_language:language" should be "French" on "sle_minion" 1s 774ms

@ssh_minion
Scenario:
No other minion is affected by the formula
22s 295ms 3

Then the pillar data for "formulas" should be empty on "ssh_minion" 7s 989ms

And the pillar data for "timezone" should be empty on "ssh_minion" 7s 163ms

And the pillar data for "keyboard_and_language" should be empty on "ssh_minion" 7s 141ms

Scenario:
Use the parametrized formula in test mode
40s 620ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 252ms

And I follow "States" in the content area 75ms

Then I should see the toggler "disabled" 13ms

When I click on the "disabled" toggler 45ms

And I click on "Apply Highstate" 60ms

Then I should see a "Applying the highstate has been scheduled." text 323ms

And I wait at most 300 seconds until event "Apply highstate in test-mode scheduled" is completed 38s 851ms

Scenario:
Apply the parametrized formula via the highstate
42s 347ms 9

When I enable repository "sle_update_repo" on this "sle_minion" without error control 762ms

And I follow "States" in the content area 78ms

And I click on "Apply Highstate" 62ms

Then I should see a "Applying the highstate has been scheduled." text 434ms

When I wait until event "Apply highstate scheduled" is completed 38s 655ms

Then the timezone on "sle_minion" should be "+05" 728ms

And the keymap on "sle_minion" should be "ca" 402ms

And the language on "sle_minion" should be "fr_FR.UTF-8" 787ms

And I disable repository "sle_update_repo" on this "sle_minion" without error control 435ms

Scenario:
Reset the formula on the minion
1s 297ms 5

When I follow "Formulas" in the content area 79ms

And I follow first "Locale" in the content area 241ms

And I click on "Clear values" and confirm alert box 340ms

And I click on "Save Formula" 69ms

Then I should see a "Formula saved" text 566ms

Scenario:
Check the pillar data after resetting the formula
9s 74ms 5

When I refresh the pillar data 2s 573ms

Then the pillar data for "formulas" should be "- locale" on "sle_minion" 1s 649ms

And the pillar data for "timezone:name" should be "CET" on "sle_minion" 1s 648ms

And the pillar data for "keyboard_and_language:keyboard_layout" should be "English (US)" on "sle_minion" 1s 615ms

And the pillar data for "keyboard_and_language:language" should be "English (US)" on "sle_minion" 1s 587ms

Scenario:
Apply the reset formula via the highstate
41s 119ms 7

And 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 435ms

When I wait until event "Apply highstate scheduled" is completed 38s 655ms

Then the timezone on "sle_minion" should be "CET" 715ms

And the keymap on "sle_minion" should be "us" 389ms

And the language on "sle_minion" should be "en_US.UTF-8" 795ms

Scenario:
Disable the formula on the minion
11s 218ms 8

When I follow "Formulas" in the content area 80ms

Then I should see a "Choose formulas:" text 59ms

And I should see a "General System Configuration" text 190ms

And I should see a "Locale" text 86ms

When I uncheck the "locale" formula 75ms

And I click on "Save" 78ms

And I wait until I see "Formula saved." text 615ms

Then the "locale" formula should be unchecked 10s 31ms

Scenario:
Check the pillar data after disabling the formula
7s 326ms 4

When I refresh the pillar data 2s 498ms

Then the pillar data for "formulas" should be empty on "sle_minion" 1s 625ms

And the pillar data for "timezone" should be empty on "sle_minion" 1s 626ms

And the pillar data for "keyboard_and_language" should be empty on "sle_minion" 1s 576ms

Scenario:
Assign locale formula to minion via group formula
3s 996ms 17

When I follow the left menu "Systems > System Groups" 82ms

When I follow "Create Group" 283ms

And I enter "locale-formula-group" as "name" 76ms

And I enter "Test group with locale formula added" as "description" 77ms

And I click on "Create Group" 488ms

Then I should see a "System group locale-formula-group created." text 68ms

When I follow "Formulas" in the content area 75ms

Then I should see a "Choose formulas:" text 59ms

And I should see a "General System Configuration" text 187ms

And I should see a "Locale" text 85ms

When I check the "locale" formula 74ms

And I click on "Save" 94ms

And I wait until I see "Formula saved." text 460ms

And I follow "Target" 475ms

And I check the "sle_minion" client 64ms

And I click on "Add Systems" 1s 248ms

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 670ms 5

When I refresh the pillar data 2s 143ms

Then the pillar data for "formulas" should be "- locale" on "sle_minion" 1s 616ms

And the pillar data for "timezone:name" should be "CET" on "sle_minion" 1s 633ms

And the pillar data for "keyboard_and_language:keyboard_layout" should be "English (US)" on "sle_minion" 1s 682ms

And the pillar data for "keyboard_and_language:language" should be "English (US)" on "sle_minion" 1s 594ms

@ssh_minion
Scenario:
No other minion is affected by the group formula
21s 186ms 3

Then the pillar data for "formulas" should be empty on "ssh_minion" 7s 323ms

And the pillar data for "timezone" should be empty on "ssh_minion" 6s 947ms

And the pillar data for "keyboard_and_language" should be empty on "ssh_minion" 6s 916ms

Scenario:
Cleanup: remove "locale-formula-group" system group
1s 483ms 7

When I follow the left menu "Systems > System Groups" 65ms

And I follow "locale-formula-group" in the content area 81ms

And I follow "Delete Group" in the content area 63ms

When I click on "Confirm Deletion" 1s 102ms

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 55ms

Scenario:
Cleanup: reset locale values on the minion
25s 648ms 8

Given I am on the Systems overview page of this "sle_minion" 1s 114ms

And I follow "States" in the content area 70ms

And I click on "Apply Highstate" 109ms

Then I should see a "Applying the highstate has been scheduled." text 431ms

When I wait until event "Apply highstate scheduled" is completed 22s 29ms

Then the timezone on "sle_minion" should be "CET" 705ms

And the keymap on "sle_minion" should be "us" 399ms

And the language on "sle_minion" should be "en_US.UTF-8" 786ms

@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
67ms 1

When I click on the clear SSM button 67ms

@flaky @scope_formulas
Feature:Use advanced features of Salt formulas 3m 32s 730ms 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 678ms 1

Given I am authorized 1s 678ms

Scenario:
Install a test formula package on the server
5s 955ms 5

When I install "form.yml" to custom formula metadata directory "testform" 3s 188ms

And I install "metadata.yml" to custom formula metadata directory "testform" 2s 497ms

When I follow the left menu "Salt > Formula Catalog" 135ms

And I enter "testform" as the filtered formula name 72ms

Then I should see a "testform" text 61ms

Scenario:
Assign test formula to minion via group formula
3s 976ms 17

When I follow the left menu "Systems > System Groups" 117ms

When I follow "Create Group" 256ms

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 71ms

When I follow "Formulas" in the content area 70ms

Then I should see a "Choose formulas:" text 57ms

And I should see a "General System Configuration" text 176ms

And I should see a "Testform" text 89ms

When I check the "testform" formula 76ms

And I click on "Save" 66ms

And I wait until I see "Formula saved." text 474ms

And I follow "Target Systems" 478ms

And I check the "sle_minion" client 60ms

And I click on "Add Systems" 1s 285ms

Then I should see a "1 systems were added to test-formula-group server group." text 92ms

Scenario:
Verify default values
40s 618ms 25

When I refresh the pillar data 2s 152ms

Then the pillar data for "testing:str" should be "" on "sle_minion" 1s 585ms

And the pillar data for "testing:str_def" should be "defvalue" on "sle_minion" 1s 611ms

And the pillar data for "testing:str_or_null" should be "None" on "sle_minion" 1s 593ms

And the pillar data for "testing" should not contain "str_opt" on "sle_minion" 1s 593ms

And the pillar data for "testing:num" should be "" on "sle_minion" 1s 605ms

And the pillar data for "testing:num_def" should be "0" on "sle_minion" 1s 580ms

And the pillar data for "testing:num_or_null" should be "None" on "sle_minion" 1s 583ms

And the pillar data for "testing" should not contain "num_opt" on "sle_minion" 1s 595ms

And the pillar data for "testing:pw" should be "" on "sle_minion" 1s 614ms

And the pillar data for "testing:pw_or_null" should be "None" on "sle_minion" 1s 601ms

And the pillar data for "testing" should not contain "pw_opt" on "sle_minion" 1s 609ms

And the pillar data for "testing:list_of_strings" should contain "def_item1" on "sle_minion" 1s 595ms

And the pillar data for "testing:list_of_strings" should contain "def_item2" on "sle_minion" 1s 629ms

And the pillar data for "testing:dict_of_strings:name1" should be "def_value1" on "sle_minion" 1s 657ms

And the pillar data for "testing:dict_of_strings:name2" should be "def_value2" on "sle_minion" 1s 622ms

And the pillar data for "testing:list_of_dicts:0:name" should be "def_user" on "sle_minion" 1s 600ms

And the pillar data for "testing:list_of_dicts:0:password" should be "secret1" on "sle_minion" 1s 592ms

And the pillar data for "testing:list_of_dicts:0" should not contain "full_name" on "sle_minion" 1s 589ms

And the pillar data for "testing:dict_of_dicts:def_user:name" should be "root" on "sle_minion" 1s 606ms

And the pillar data for "testing:dict_of_dicts:def_user:password" should be "secret2" on "sle_minion" 1s 593ms

And the pillar data for "testing:dict_of_dicts:def_user:full_name" should be "None" on "sle_minion" 1s 584ms

And the pillar data for "testing:recursive_dict_of_dicts:def_gr1:group_name" should be "default group 1" on "sle_minion" 1s 605ms

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 588ms

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 628ms

Scenario:
Fill in and verify non-default values in group formula
21s 124ms 30

When I follow the left menu "Systems > System Groups" 62ms

When I follow "test-formula-group" in the content area 71ms

And I follow "Formulas" in the content area 77ms

And I follow first "Testform" in the content area 238ms

And I click on "Expand All Sections" 159ms

And I enter "text1" as "testing#str" 127ms

And I enter "text2" as "testing#str_def" 130ms

And I enter "text3" as "testing#str_or_null" 85ms

And I enter "text4" as "testing#str_opt" 100ms

And I enter "1" as "testing#num" 62ms

And I enter "2" as "testing#num_def" 80ms

And I enter "3" as "testing#num_or_null" 70ms

And I enter "4" as "testing#num_opt" 63ms

And I enter "pw1" as "testing#pw" 100ms

And I enter "pw2" as "testing#pw_or_null" 99ms

And I enter "pw3" as "testing#pw_opt" 81ms

And I click on "Save Formula" 111ms

Then I should see a "Formula saved" text 715ms

When I wait for "1" seconds 1s

Then the pillar data for "testing:str" should be "text1" on "sle_minion" 1s 708ms

And the pillar data for "testing:str_def" should be "text2" on "sle_minion" 1s 606ms

And the pillar data for "testing:str_or_null" should be "text3" on "sle_minion" 1s 592ms

And the pillar data for "testing:str_opt" should be "text4" on "sle_minion" 1s 616ms

And the pillar data for "testing:num" should be "1" on "sle_minion" 1s 594ms

And the pillar data for "testing:num_def" should be "2" on "sle_minion" 1s 606ms

And the pillar data for "testing:num_or_null" should be "3" on "sle_minion" 1s 588ms

And the pillar data for "testing:num_opt" should be "4" on "sle_minion" 1s 597ms

And the pillar data for "testing:pw" should be "pw1" on "sle_minion" 1s 594ms

And the pillar data for "testing:pw_or_null" should be "pw2" on "sle_minion" 1s 598ms

And the pillar data for "testing:pw_opt" should be "pw3" on "sle_minion" 1s 578ms

Scenario:
Clear values in group formula and verify the defaults again
40s 866ms 32

When I follow the left menu "Systems > System Groups" 88ms

When I follow "test-formula-group" in the content area 68ms

And I follow "Formulas" in the content area 64ms

And I follow first "Testform" in the content area 239ms

And I click on "Clear values" and confirm alert box 377ms

And I click on "Save Formula" 66ms

Then I should see a "Formula saved" text 554ms

When I wait for "1" seconds 1s

Then the pillar data for "testing:str" should be "" on "sle_minion" 1s 603ms

And the pillar data for "testing:str_def" should be "defvalue" on "sle_minion" 1s 583ms

And the pillar data for "testing:str_or_null" should be "None" on "sle_minion" 1s 585ms

And the pillar data for "testing" should not contain "str_opt" on "sle_minion" 1s 609ms

And the pillar data for "testing:num" should be "" on "sle_minion" 1s 592ms

And the pillar data for "testing:num_def" should be "0" on "sle_minion" 1s 598ms

And the pillar data for "testing:num_or_null" should be "None" on "sle_minion" 1s 591ms

And the pillar data for "testing" should not contain "num_opt" on "sle_minion" 1s 607ms

And the pillar data for "testing:pw" should be "" on "sle_minion" 1s 612ms

And the pillar data for "testing:pw_or_null" should be "None" on "sle_minion" 1s 607ms

And the pillar data for "testing" should not contain "pw_opt" on "sle_minion" 1s 623ms

And the pillar data for "testing:list_of_strings" should contain "def_item1" on "sle_minion" 1s 594ms

And the pillar data for "testing:list_of_strings" should contain "def_item2" on "sle_minion" 1s 596ms

And the pillar data for "testing:dict_of_strings:name1" should be "def_value1" on "sle_minion" 1s 604ms

And the pillar data for "testing:dict_of_strings:name2" should be "def_value2" on "sle_minion" 1s 600ms

And the pillar data for "testing:list_of_dicts:0:name" should be "def_user" on "sle_minion" 1s 573ms

And the pillar data for "testing:list_of_dicts:0:password" should be "secret1" on "sle_minion" 1s 595ms

And the pillar data for "testing:list_of_dicts:0" should not contain "full_name" on "sle_minion" 1s 599ms

And the pillar data for "testing:dict_of_dicts:def_user:name" should be "root" on "sle_minion" 1s 609ms

And the pillar data for "testing:dict_of_dicts:def_user:password" should be "secret2" on "sle_minion" 1s 589ms

And the pillar data for "testing:dict_of_dicts:def_user:full_name" should be "None" on "sle_minion" 1s 638ms

And the pillar data for "testing:recursive_dict_of_dicts:def_gr1:group_name" should be "default group 1" on "sle_minion" 1s 607ms

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 601ms

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 581ms

Scenario:
Fill in and verify mix of default and non-default values in group formula
20s 478ms 23

When I follow the left menu "Systems > System Groups" 62ms

When I follow "test-formula-group" in the content area 60ms

And I follow "Formulas" in the content area 57ms

And I follow first "Testform" in the content area 233ms

And I click on "Expand All Sections" 244ms

And I enter "text1" as "testing#str" 122ms

And I enter "1" as "testing#num" 60ms

And I enter "2" as "testing#num_def" 94ms

And I enter "pw1" as "testing#pw" 86ms

And I click on "Save Formula" 93ms

Then I should see a "Formula saved" text 731ms

When I wait for "1" seconds 1s

Then the pillar data for "testing:str" should be "text1" on "sle_minion" 1s 610ms

And the pillar data for "testing:str_def" should be "defvalue" on "sle_minion" 1s 620ms

And the pillar data for "testing:str_or_null" should be "None" on "sle_minion" 1s 605ms

And the pillar data for "testing" should not contain "str_opt" on "sle_minion" 1s 599ms

And the pillar data for "testing:num" should be "1" on "sle_minion" 1s 598ms

And the pillar data for "testing:num_def" should be "2" on "sle_minion" 1s 600ms

And the pillar data for "testing:num_or_null" should be "None" on "sle_minion" 1s 592ms

And the pillar data for "testing" should not contain "num_opt" on "sle_minion" 1s 624ms

And the pillar data for "testing:pw" should be "pw1" on "sle_minion" 1s 597ms

And the pillar data for "testing:pw_or_null" should be "None" on "sle_minion" 1s 591ms

And the pillar data for "testing" should not contain "pw_opt" on "sle_minion" 1s 588ms

Scenario:
Verify that minion form inherits the values from group form
19s 735ms 16

Given I am on the Systems overview page of this "sle_minion" 1s 52ms

When I follow "Formulas" in the content area 79ms

And I follow first "Testform" in the content area 216ms

And I click on "Save Formula" 204ms

Then I should see a "Formula saved" text 531ms

And the pillar data for "testing:str" should be "text1" on "sle_minion" 1s 632ms

And the pillar data for "testing:str_def" should be "defvalue" on "sle_minion" 1s 598ms

And the pillar data for "testing:str_or_null" should be "None" on "sle_minion" 1s 593ms

And the pillar data for "testing" should not contain "str_opt" on "sle_minion" 1s 599ms

And the pillar data for "testing:num" should be "1" on "sle_minion" 1s 602ms

And the pillar data for "testing:num_def" should be "2" on "sle_minion" 1s 579ms

And the pillar data for "testing:num_or_null" should be "None" on "sle_minion" 1s 603ms

And the pillar data for "testing" should not contain "num_opt" on "sle_minion" 1s 627ms

And the pillar data for "testing:pw" should be "pw1" on "sle_minion" 1s 621ms

And the pillar data for "testing:pw_or_null" should be "None" on "sle_minion" 1s 596ms

And the pillar data for "testing" should not contain "pw_opt" on "sle_minion" 1s 595ms

Scenario:
Fill in and verify non-default values in minion formula
20s 885ms 28

When I follow "Formulas" in the content area 62ms

And I follow first "Testform" in the content area 179ms

And I click on "Expand All Sections" 147ms

And I enter "min_text1" as "testing#str" 164ms

And I enter "min_text2" as "testing#str_def" 143ms

And I enter "min_text3" as "testing#str_or_null" 103ms

And I enter "min_text4" as "testing#str_opt" 106ms

And I enter "101" as "testing#num" 76ms

And I enter "102" as "testing#num_def" 82ms

And I enter "103" as "testing#num_or_null" 71ms

And I enter "104" as "testing#num_opt" 70ms

And I enter "min_pw1" as "testing#pw" 135ms

And I enter "min_pw2" as "testing#pw_or_null" 90ms

And I enter "min_pw3" as "testing#pw_opt" 98ms

And I click on "Save Formula" 73ms

Then I should see a "Formula saved" text 685ms

When I wait for "1" seconds 1s

Then the pillar data for "testing:str" should be "min_text1" on "sle_minion" 1s 613ms

And the pillar data for "testing:str_def" should be "min_text2" on "sle_minion" 1s 605ms

And the pillar data for "testing:str_or_null" should be "min_text3" on "sle_minion" 1s 600ms

And the pillar data for "testing:str_opt" should be "min_text4" on "sle_minion" 1s 594ms

And the pillar data for "testing:num" should be "101" on "sle_minion" 1s 595ms

And the pillar data for "testing:num_def" should be "102" on "sle_minion" 1s 586ms

And the pillar data for "testing:num_or_null" should be "103" on "sle_minion" 1s 611ms

And the pillar data for "testing:num_opt" should be "104" on "sle_minion" 1s 597ms

And the pillar data for "testing:pw" should be "min_pw1" on "sle_minion" 1s 600ms

And the pillar data for "testing:pw_or_null" should be "min_pw2" on "sle_minion" 1s 593ms

And the pillar data for "testing:pw_opt" should be "min_pw3" on "sle_minion" 1s 594ms

Scenario:
Clear values in minion formula and verify that the pillar is set to group values
19s 946ms 17

When I follow "Formulas" in the content area 78ms

And I follow first "Testform" in the content area 220ms

And I click on "Clear values" and confirm alert box 369ms

And I click on "Save Formula" 63ms

Then I should see a "Formula saved" text 651ms

When I wait for "1" seconds 1s

Then the pillar data for "testing:str" should be "text1" on "sle_minion" 1s 614ms

And the pillar data for "testing:str_def" should be "defvalue" on "sle_minion" 1s 594ms

And the pillar data for "testing:str_or_null" should be "None" on "sle_minion" 1s 585ms

And the pillar data for "testing" should not contain "str_opt" on "sle_minion" 1s 597ms

And the pillar data for "testing:num" should be "1" on "sle_minion" 1s 587ms

And the pillar data for "testing:num_def" should be "2" on "sle_minion" 1s 592ms

And the pillar data for "testing:num_or_null" should be "None" on "sle_minion" 1s 606ms

And the pillar data for "testing" should not contain "num_opt" on "sle_minion" 1s 601ms

And the pillar data for "testing:pw" should be "pw1" on "sle_minion" 1s 590ms

And the pillar data for "testing:pw_or_null" should be "None" on "sle_minion" 1s 610ms

And the pillar data for "testing" should not contain "pw_opt" on "sle_minion" 1s 579ms

Scenario:
Cleanup: remove formula from minion
11s 2ms 5

When I follow "Formulas" in the content area 62ms

And I uncheck the "testform" formula 208ms

And I click on "Save" 64ms

And I wait until I see "Formula saved." text 641ms

Then the "testform" formula should be unchecked 10s 26ms

Scenario:
Cleanup: remove "test-formula-group" system group
6s 462ms 9

When I follow the left menu "Systems > System Groups" 76ms

And I follow "test-formula-group" in the content area 70ms

And I follow "Delete Group" in the content area 70ms

When I click on "Confirm Deletion" 1s 138ms

Then I should see a "System group" text 61ms

Then I should see a "test-formula-group" text 57ms

And I should see a "deleted" text 55ms

And I wait until there is no pillar refresh salt job active 3s 355ms

Then the pillar data for "testing" should be empty on "sle_minion" 1s 576ms

@skip_if_github_validation @scope_openscap
Feature:OpenSCAP audit of Salt minion 1m 23s 744ms 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 538ms 2

Given I am authorized for the "Admin" section 1s 738ms

And I am on the Systems overview page of this "sle_minion" 1s 799ms

@Uyuni
Scenario:
Enable required repositories
754ms 1

When I enable repository "repo-oss" on this "sle_minion" without error control 754ms

@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 995ms 2 3 1

When I refresh the metadata for "sle_minion" 848ms

And I install OpenSCAP dependencies on "sle_minion" 675ms 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 471ms Show Info + 
02:29:08:000 - 02:29:09: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 240ms 3 5 1

When I follow "Audit" in the content area 68ms

And I follow "OpenSCAP" in the content area 66ms

And I follow "Schedule" in the content area 64ms

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 40ms 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
109ms 8 1

When I follow "Audit" in the content area 109ms 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
10ms 6 1

When I follow "Audit" in the content area 10ms 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
430ms 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" 430ms 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 653ms 5 3 1

Given I am on the Systems overview page of this "sle_minion" 1s 78ms

When I follow "Audit" in the content area 77ms

And I follow "OpenSCAP" in the content area 67ms

And I follow "List Scans" in the content area 65ms

And I click on "Select All" 10s 8ms 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 354ms Show Info + 
02:30:11:000 - 02:30:24: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
469ms 6

When I follow the left menu "Admin > Organizations" 127ms

When I follow "SUSE Test" in the content area 80ms

And I follow "Configuration" in the content area 65ms

And I enter "90" as "scap_retention_period" 66ms

And I click on "Update Organization" 61ms

Then I should see a "Organization SUSE Test was successfully updated." text 67ms

Scenario:
Cleanup: remove the OpenSCAP packages from the SLE minion
1s 103ms 1

When I remove OpenSCAP dependencies from "sle_minion" 1s 103ms

@Uyuni
Scenario:
Cleanup: Disable required repositories
430ms 1

When I disable repository "repo-oss" on this "sle_minion" without error control 430ms

@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 56s 282ms 4

Scenario:
Log in as org admin user
1s 754ms 1

Given I am authorized 1s 754ms

Scenario:
Create a user-defined state
12s 457ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 802ms

When I follow "States" in the content area 72ms

And I install a user-defined state for "sle_minion" on the server 4s 198ms

And I follow "Highstate" in the content area 68ms

And I click on "Show full highstate output" 274ms

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
24s 37ms 3

When I schedule a highstate for "sle_minion" via API 951ms

And I wait until event "Apply highstate scheduled" is completed 22s 375ms

Then file "/tmp/test_user_defined_state" should exist on "sle_minion" 711ms

Scenario:
Cleanup: remove user-defined state and the file it created
18s 33ms 7

When I follow "States" in the content area 77ms

And I uninstall the user-defined state from the server 1s 190ms

And I uninstall the managed file from "sle_minion" 391ms

And I follow "Highstate" in the content area 83ms

And I click on "Show full highstate output" 236ms

And I wait for "6" seconds 6s

Then I should not see a "user_defined_state" text in element "highstate" 10s 53ms

@scope_salt
Feature:Verify the minion registration 30s 744ms 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 894ms 1

Given I am authorized 1s 894ms

Scenario:
Check the Salt entitlement
1s 687ms 2

Given I am on the Systems overview page of this "sle_minion" 1s 595ms

Then I should see a "[Salt]" text 91ms

Scenario:
Check that installed packages are visible
910ms 3

When I follow "Software" in the content area 73ms

And I follow "List / Remove" 714ms

Then I should see a "aaa_base" text 122ms

Scenario:
Check that Hardware Refresh button works on a SLES Salt minion
25s 336ms 6

When I follow "Details" in the content area 69ms

And I follow "Hardware" in the content area 90ms

And I click on "Schedule Hardware Refresh" 842ms

Then I should see a "You have successfully scheduled a hardware profile refresh" text 113ms

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 133ms

Scenario:
Check that Update Properties button works
915ms 4

When I follow "Details" in the content area 67ms

And I follow "Hardware" in the content area 67ms

And I click on "Update Properties" 671ms

Then I should see a "Networking properties updated." text 109ms

@sle_minion @scope_configuration_channels
Feature:Configuration state channels 1m 31s 761ms 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 816ms 1

Given I am authorized 1s 816ms

Scenario:
Create a state channel
1s 731ms 12

When I follow the left menu "Configuration > Channels" 122ms

And I follow "Create State Channel" 331ms

Then I should see a "New Config State Channel" text 56ms

When I enter "My State Channel" as "cofName" 68ms

And I enter "statechannel" as "cofLabel" 60ms

And I enter "This is a state channel" as "cofDescription" 68ms

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" 767ms

Then I should see a "State Channel" text 61ms

And I should see a "Channel Properties" text 60ms

And I should see a "Channel Information" text 64ms

And I should see a "Configuration Actions" text 63ms

Scenario:
Subscribe a minion to the state channel
2s 809ms 8

When I am on the Systems overview page of this "sle_minion" 1s 11ms

And I follow "Configuration" in the content area 68ms

And I follow "Manage Configuration Channels" in the content area 66ms

And I follow first "Subscribe to Channels" in the content area 62ms

And I check "My State Channel" in the list 62ms

And I click on "Continue" 674ms

And I click on "Update Channel Rankings" 793ms

Then I should see a "Channel Subscriptions successfully changed for" text 69ms

Scenario:
Salt state details
1s 279ms 7

When I follow the left menu "Configuration > Channels" 110ms

And I follow "My State Channel" 468ms

Then I should see a "1 system subscribed" text 71ms

When I follow "View/Edit 'init.sls' File" 399ms

Then I should see a "Revision 1 of /init.sls from channel My State Channel" text 77ms

And I should see a "File Contents" text 76ms

And I should see a "touch /root/foobar:" text 75ms

Scenario:
Apply the new state
24s 595ms 8

When I am on the Systems overview page of this "sle_minion" 1s 30ms

And I follow "States" in the content area 66ms

And I follow "Configuration Channels" in the content area 60ms

Then I should see a "Execute States" button 235ms

When I click on "Execute States" 53ms

Then I should see a "Applying the config channels has been scheduled" text 256ms

When I wait until event "Apply states [custom] scheduled" is completed 22s 162ms

And I wait until file "/root/foobar" exists on "sle_minion" 730ms

Scenario:
Try to remove init.sls file
2s 25ms 7

When I follow the left menu "Configuration > Channels" 103ms

And I follow "My State Channel" 475ms

And I follow "View/Edit 'init.sls' File" 378ms

When I follow "Delete" 327ms

And I click on "Delete Configuration Revision" 585ms

Then I should see a "Cannot delete the only revision for the init.sls file" text 81ms

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 536ms 7

When I follow the left menu "Configuration > Channels" 68ms

And I follow "My State Channel" 557ms

And I follow "Delete Channel" 357ms

Then I should see a "Are you sure you want to delete this config channel?" text 50ms

When I click on "Delete Config Channel" 59ms

Then I should see a "Channel 'My State Channel' has been deleted." text 50ms

And I remove "/root/foobar" from "sle_minion" 393ms

Scenario:
Create the 1st state channel
1s 565ms 12

When I follow the left menu "Configuration > Channels" 64ms

And I follow "Create State Channel" 254ms

Then I should see a "New Config State Channel" text 53ms

When I enter "My State Channel" as "cofName" 70ms

And I enter "statechannel" as "cofLabel" 57ms

And I enter "This is a state channel" as "cofDescription" 69ms

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" 66ms

Then I should see a "State Channel" text 744ms

And I should see a "Channel Properties" text 60ms

And I should see a "Channel Information" text 59ms

And I should see a "Configuration Actions" text 59ms

Scenario:
Create the 2nd state channel with same name
1s 537ms 12

When I follow the left menu "Configuration > Channels" 63ms

And I follow "Create State Channel" 272ms

Then I should see a "New Config State Channel" text 54ms

When I enter "My State Channel" as "cofName" 60ms

And I enter "statechannel2" as "cofLabel" 57ms

And I enter "This is a state channel" as "cofDescription" 64ms

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" 727ms

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 57ms

Scenario:
Create the 3rd state channel with spacecmd
9s 469ms 9

When I create channel "statechannel3" from spacecmd of type "state" 1s 559ms

And I follow the left menu "Configuration > Channels" 61ms

Then I should see a "statechannel3" text 62ms

When I update init.sls from spacecmd with content "touch /tmp/statechannel3:\n cmd.run:\n - creates: /tmp/statechannel3" for channel "statechannel3" 2s 634ms

And I get "/init.sls" file details for channel "statechannel3" via spacecmd 1s 268ms

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 582ms

And I get "/init.sls" file details for channel "statechannel3" via spacecmd 1s 299ms

Then I should see "Revision: 100" in the output < 1ms

Scenario:
Subscribe a minion to 1st and 2nd state channels
2s 278ms 15

When I am on the Systems overview page of this "sle_minion" 1s 22ms

And I follow "States" in the content area 74ms

And I follow "Configuration Channels" in the content area 65ms

And I click on "Search" in element "search-row" 71ms

Then I should see a "My State Channel" text 172ms

And I should see a "statechannel" text 69ms

And I should see a "statechannel2" text 68ms

When I check "statechannel-cbox" 87ms

And I check "statechannel2-cbox" 83ms

And I click on "Save Changes" 65ms

And I wait until I see "Edit Channel Ranks" text 61ms

Then I should see a "My State Channel (statechannel)" text 60ms

And I should see a "My State Channel (statechannel2)" text 56ms

When I click on "Confirm" 59ms

Then I should see a "State assignments have been saved." text 260ms

Scenario:
Apply the Configuration channel state
23s 589ms 9

When I follow "States" in the content area 58ms

And I follow "Configuration Channels" in the content area 64ms

And I click on "Search" in element "search-row" 60ms

And I wait until I see "Execute States" text 63ms

And I click on "Execute States" 60ms

Then I should see a "Applying the config channels has been scheduled" text 274ms

And I wait until event "Apply states [custom] scheduled" is completed 21s 877ms

And I wait until file "/root/statechannel" exists on "sle_minion" 738ms

And I wait until file "/root/statechannel2" exists on "sle_minion" 391ms

Scenario:
Subscribe a minion to the 3rd state channel
1s 55ms 12

When I follow "States" in the content area 61ms

And I follow "Configuration Channels" in the content area 55ms

Then I should see a "My State Channel" text 161ms

And I should see a "statechannel3" text 68ms

When I check "statechannel3-cbox" 85ms

And I click on "Save Changes" 69ms

And I wait until I see "Edit Channel Ranks" text 58ms

And I should see a "My State Channel (statechannel)" text 58ms

And I should see a "My State Channel (statechannel2)" text 59ms

And I should see a "statechannel3 (statechannel3)" text 56ms

When I click on "Confirm" 58ms

Then I should see a "State assignments have been saved." text 262ms

Scenario:
Apply the Configuration channel state with spacecmd
10s 878ms 2

When I schedule apply configchannels for "sle_minion" 2s 888ms

And I wait until file "/root/statechannel3" exists on "sle_minion" 7s 990ms

Scenario:
Cleanup: remove the 1st state channel and the deployed file
2s 35ms 7

When I follow the left menu "Configuration > Channels" 122ms

And I follow first "My State Channel" 528ms

And I follow "Delete Channel" 361ms

Then I should see a "Are you sure you want to delete this config channel?" text 49ms

When I click on "Delete Config Channel" 517ms

Then I should see a "Channel 'My State Channel' has been deleted." text 66ms

When I remove "/root/statechannel" from "sle_minion" 389ms

Scenario:
Cleanup: remove the 2nd state channel and the deployed file
1s 995ms 7

When I follow the left menu "Configuration > Channels" 64ms

And I follow first "My State Channel" 557ms

And I follow "Delete Channel" 356ms

Then I should see a "Are you sure you want to delete this config channel?" text 54ms

When I click on "Delete Config Channel" 505ms

Then I should see a "Channel 'My State Channel' has been deleted." text 60ms

When I remove "/root/statechannel2" from "sle_minion" 395ms

Scenario:
Cleanup: remove the 3rd state channel and the deployed file
1s 559ms 7

When I follow the left menu "Configuration > Channels" 61ms

And I follow first "statechannel3" 605ms

And I follow "Delete Channel" 343ms

Then I should see a "Are you sure you want to delete this config channel?" text 52ms

When I click on "Delete Config Channel" 53ms

Then I should see a "Channel 'statechannel3' has been deleted." text 50ms

When I remove "/root/statechannel3" from "sle_minion" 392ms

Feature:Configuration state channels via API 2s 412ms 3

Scenario:
Create a state channel via API
852ms 3

When I create state channel "statechannel1" via API 457ms

And I call configchannel.get_file_revision() with file "/init.sls", revision "1" and channel "statechannel1" via API 395ms

Then I should get file contents "" < 1ms

Scenario:
Create a state channel with contents via API
787ms 3

When I create state channel "statechannel2" containing "touch /root/foobar:\n cmd.run:\n - creates: /root/foobar" via API 410ms

And I call configchannel.get_file_revision() with file "/init.sls", revision "1" and channel "statechannel2" via API 376ms

Then I should get file contents "touch /root/foobar:\n cmd.run:\n - creates: /root/foobar" < 1ms

Scenario:
Cleanup: remove state channels via API
773ms 2

Then I delete channel "statechannel1" via API without error control 382ms

And I delete channel "statechannel2" via API without error control 390ms

@skip_if_github_validation @scope_salt
Feature:System package list is updated if packages are manually installed or removed 1m 25s 726ms 7

Scenario:
Pre-requisite: install milkyway-dummy-1.0 package
3s 255ms 3

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 784ms

And I refresh the metadata for "sle_minion" 849ms

And I install old package "milkyway-dummy-1.0" on this "sle_minion" without error control 1s 621ms

Scenario:
Pre-requisite: refresh package list and check installed packages on SLE minion client
12s 934ms 3

When I refresh packages list via spacecmd on "sle_minion" 2s 992ms

And I wait until refresh package list on "sle_minion" is finished 7s 409ms

Then spacecmd should show packages "milkyway-dummy-1.0" installed on "sle_minion" 2s 532ms

Scenario:
Log in as org admin user
1s 830ms 1

Given I am authorized for the "Admin" section 1s 830ms

Scenario:
Pre-requisite: ensure the errata cache is computed before package list tests
26s 52ms 11

Given I am on the Systems overview page of this "sle_minion" 1s 555ms

When I follow "Software" in the content area 71ms

And I follow "List / Remove" in the content area 72ms

And I enter "milkyway-dummy" as the filtered package name 193ms

And I click on the filter button until page does contain "milkyway-dummy-1.0" text 11s 161ms

And I follow the left menu "Admin > Task Schedules" 124ms

And I follow "errata-cache-default" 1s 161ms

And I follow "errata-cache-bunch" 1s 264ms

And I click on "Single Run Schedule" 1s 518ms

Then I should see a "bunch was scheduled" text 289ms

When I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 8s 637ms

Scenario:
Remove manually a package on a minion
24s 685ms 8

Given I am on the Systems overview page of this "sle_minion" 1s 23ms

When I follow "Software" in the content area 76ms

And I follow "List / Remove" 742ms

And I enter "milkyway-dummy" as the filtered package name 153ms

And I click on the filter button 843ms

Then I should see a "milkyway-dummy" text 71ms

When I remove package "milkyway-dummy" from this "sle_minion" 1s 844ms

And I click on the filter button until page does not contain "milkyway-dummy" text 19s 930ms

Scenario:
Install manually a package on a minion
13s 899ms 7

When I follow "Software" in the content area 75ms

And I follow "List / Remove" 761ms

And I enter "milkyway-dummy" as the filtered package name 168ms

And I click on the filter button 794ms

Then I should not see a "milkyway-dummy" text 65ms

When I install package "milkyway-dummy" on this "sle_minion" 1s 999ms

And I click on the filter button until page does not contain "milkyway-dummy" text 10s 35ms

Scenario:
Cleanup: remove milkyway-dummy packages from SLES minion
3s 69ms 3

When I disable repository "test_repo_rpm_pool" on this "sle_minion" 777ms

And I remove package "milkyway-dummy" from this "sle_minion" without error control 1s 524ms

And I refresh the metadata for "sle_minion" 766ms

@sle_minion @scope_monitoring @skip_if_github_validation @under_debugging
Feature:Monitor MLM environment with Prometheus on a SLE Salt minion 10m 54s 457ms 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 748ms 1

Given I am authorized 1s 748ms

Scenario:
Apply Prometheus and Prometheus exporter formulas
2s 819ms 8

Given I am on the Systems overview page of this "sle_minion" 1s 601ms

When I follow "Formulas" in the content area 74ms

And I should see a "Choose formulas:" text 56ms

And I should see a "Monitoring" text 280ms

And I check the "prometheus" formula 77ms

And I check the "prometheus-exporters" formula 71ms

And I click on "Save" 64ms

Then I wait until I see "Formula saved" text 592ms

Scenario:
Configure Prometheus formula
1s 601ms 7

When I follow "Formulas" in the content area 75ms

And I follow "Prometheus" in the content area 214ms

And I click on "Expand All Sections" 327ms

And I enter "admin" as "Username" 117ms

And I enter "admin" as "Password" 86ms

And I click on "Save Formula" 77ms

Then I should see a "Formula saved" text 703ms

Scenario:
Configure Prometheus exporter formula
2s 112ms 9

When I follow "Formulas" in the content area 66ms

And I follow "Prometheus Exporters" in the content area 231ms

And I click on "Expand All Sections" 143ms

And I should see a "Enable and configure Prometheus exporters for managed systems." text 108ms

And I check "node" exporter 45ms

And I check "apache" exporter 87ms

And I check "postgres" exporter 89ms

And I click on "Save" 65ms

Then I should see a "Formula saved" text 1s 275ms

Scenario:
Apply highstate for Prometheus exporters
1m 31s 283ms 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: 02:37:17.702884 Duration: 229.504 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: 02:37:22.999709 Duration: 12.34 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: 02:37:23.014842 Duration: 39.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: 02:37:23.055749 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: 02:37:23.055859 Duration: 619.748 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: 02:37:23.675772 Duration: 40.995 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: 02:37:23.716948 Duration: 42.808 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: 02:37:23.759980 Duration: 40.644 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: 02:37:23.800786 Duration: 26.322 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: 02:37:23.827250 Duration: 27.542 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: 02:37:23.855118 Duration: 142.186 SLS: channels Changed: {} ---------- ID: pkg_installed Function: pkg.installed Name: pkg_installed Result: true Comment: No packages to install provided Started: 02:37:23.997957 Duration: 0.751 SLS: packages.packages_afafa3c7f0cd0feb2c7ecdc969a875ff Changed: {} ---------- ID: pkg_removed Function: pkg.removed Name: pkg_removed Result: true Comment: All specified packages are already absent Started: 02:37:23.998920 Duration: 10.82 SLS: packages.packages_afafa3c7f0cd0feb2c7ecdc969a875ff Changed: {} ---------- ID: pkg_latest Function: pkg.latest Name: pkg_latest Result: true Comment: No packages to install provided Started: 02:37:24.010020 Duration: 0.592 SLS: packages.packages_afafa3c7f0cd0feb2c7ecdc969a875ff Changed: {} ---------- ID: os_not_supported Function: test.fail_without_changes Name: OS not supported! Result: false Comment: Failure! Started: 02:37:24.010694 Duration: 0.752 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: 02:37:24.011551 Duration: 19.395 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: 02:37:24.031145 Duration: 4185.293 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: 02:37:28.220003 Duration: 126.634 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: 02:37:33.126660 Duration: 534.655 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: 02:37:33.669436 Duration: 2957.156 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: 02:37:36.631141 Duration: 91.275 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: 02:37:41.551675 Duration: 556.425 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: 02:37:42.109610 Duration: 2921.221 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: 02:37:45.034928 Duration: 109.164 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: 02:37:45.144409 Duration: 195.085 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: 02:37:45.341344 Duration: 380.586 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: 02:37:50.399118 Duration: 543.966 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: 02:37:50.943275 Duration: 12.609 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: 02:37:50.956080 Duration: 14.218 SLS: services.salt-minion Changed: {} ---------- ID: disable_osad Function: service.dead Name: osad Result: true Comment: The named service osad is not available Started: 02:37:50.970432 Duration: 14.739 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: 02:37:50.986954 Duration: 11.357 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: 02:37:50.998439 Duration: 257.14 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: 02:37:51.255704 Duration: 1.546 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: 02:37:51.257739 Duration: 10.851 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: 02:37:51.268824 Duration: 155.323 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: 02:37:51.424276 Duration: 36.406 SLS: services.salt-minion Changed: {}

When I follow "States" in the content area 72ms

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 1m 15s 78ms 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 618ms Show Info + 
02:37:11:000 - 02:38:27:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010023&aid=404
Screenshot +

Scenario:
Wait for services
4m 25s 225ms 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 225ms Show Info + 
02:38:43:000 - 02:42:53:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010023&aid=404
Screenshot +

Scenario:
Visit monitoring endpoints on the minion
4m 25s 306ms 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 305ms Show Info + 
02:43:08:000 - 02:47:18:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010023&aid=404
Screenshot +

Scenario:
Cleanup: undo Prometheus and Prometheus exporter formulas
1s 476ms 5

When I follow "Formulas" in the content area 77ms

And I uncheck the "prometheus" formula 275ms

And I uncheck the "prometheus-exporters" formula 68ms

And I click on "Save" 62ms

Then I wait until I see "Formula saved" text 992ms

Scenario:
Cleanup: apply highstate after test monitoring
22s 882ms 4

And I follow "States" in the content area 72ms

And I click on "Apply Highstate" 63ms

Then I should see a "Applying the highstate has been scheduled." text 563ms

And I wait until event "Apply highstate scheduled" is completed 22s 183ms

@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 8s 382ms 4

Scenario:
Log in as org admin user
1s 769ms 1

Given I am authorized 1s 769ms

Scenario:
Check perseus-dummy-7891 patches
1s 413ms 7

When I follow the left menu "Patches > Patch List > All" 200ms

And I enter "dummy" as the filtered synopsis 40ms

And I click on the filter button 646ms

And I follow "perseus-dummy-7891" 435ms

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 346ms 5

When I refresh the metadata for "sle_minion" 1s 127ms

Then I should have 'reference.*id="CVE-1999-12345' in the patch metadata for "sle_minion" 811ms

And I should have 'reference.*id="CVE-1999-99781' in the patch metadata for "sle_minion" 800ms

And I should have 'reference.*http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-1999-12345' in the patch metadata for "sle_minion" 808ms

And I should have 'reference.*http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-1999-99781' in the patch metadata for "sle_minion" 799ms

Scenario:
Search for CVE ID with the new format
852ms 5

When I follow the left menu "Patches > Advanced Search" 64ms

When I enter "CVE-1999-12345" as "search_string" in the content area 80ms

And I click on "Search" 607ms

Then I should see a "Advanced Search" text 76ms

And I should see a "perseus-dummy-7891" link in the content area 23ms

@scope_onboarding
Feature:Display patches 1m 48s 308ms 8

Scenario:
Log in as org admin user
1s 607ms 1

Given I am authorized for the "Admin" section 1s 607ms

Scenario:
Pre-require: enable old packages to fake a possible installation
11s 122ms 10

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 737ms

And I refresh the metadata for "sle_minion" 768ms

And I install old package "andromeda-dummy-1.0" on this "sle_minion" 1s 589ms

And I install old package "virgo-dummy-1.0" on this "sle_minion" 1s 608ms

When I follow the left menu "Admin > Task Schedules" 126ms

And I follow "errata-cache-default" 1s 176ms

And I follow "errata-cache-bunch" 1s 263ms

And I click on "Single Run Schedule" 1s 515ms

Then I should see a "bunch was scheduled" text 267ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 2s 70ms

Scenario:
Check all patches exist
1m 11s 308ms 8

When I follow the left menu "Patches > Patch List > Relevant" 217ms

Then I should see an update in the list 30ms

When I wait until I see "andromeda-dummy" text, refreshing the page 1m 10s 587ms

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 331ms

And I wait until I see "virgo-dummy" text 65ms

Then I should see a "virgo-dummy-3456" link 12ms

Scenario:
Check SLES release 6789 patches
790ms 6

When I follow the left menu "Patches > Patch List > Relevant" 89ms

And I follow "andromeda-dummy-6789" 488ms

Then I should see a "andromeda-dummy-6789 - Bug Fix Advisory" text 68ms

And I should see a "Test update for andromeda-dummy" text 66ms

And I should see a "Fake-RPM-SUSE-Channel" link 11ms

And I should see a "reboot_suggested" text 65ms

Scenario:
Check packages of SLES release 6789 patches
1s 439ms 6

When I follow the left menu "Patches > Patch List > Relevant" 68ms

And I follow "andromeda-dummy-6789" 471ms

And I follow "Packages" 822ms

Then I should see a "Fake-RPM-SUSE-Channel" link 8ms

And I should see a "sha512:19940cc4a9f0d38a038a4455b0f1cf1290c4a4296b27f5a62f4aae60585ac6e2677e88c3c3127d487116ed8d9b1787379e23aafac46bc14408864926bedee693" text 53ms

And I should see a "andromeda-dummy-2.0-1.1-noarch" link 14ms

Scenario:
Check relevant patches for this client
11s 697ms 8

Given I am on the Systems overview page of this "sle_minion" 1s 202ms

When I follow "Software" in the content area 75ms

And I follow "Patches" in the content area 66ms

Then I should see a "Relevant Patches" text 84ms

When I enter "dummy" as the filtered synopsis 37ms

And I click on the filter button 10s 75ms

Then I should see a "Test update for andromeda-dummy" text 80ms

And I should see a "Test update for virgo-dummy" text 77ms

Scenario:
Cleanup: regenerate search index for later tests
5s 671ms 1

Search by hostname: uyuni-master-suse-minion
[{"last_boot"=>"2026-03-04T22:19:58Z", "name"=>"uyuni-master-suse-minion.sumaci.aws", "id"=>1000010023, "last_checkin"=>"2026-03-05T01:49:10Z"}]

When I clean the search index on the server 5s 671ms

Scenario:
Cleanup: remove old packages
4s 670ms 4

When I disable repository "test_repo_rpm_pool" on this "sle_minion" without error control 763ms

And I refresh the metadata for "sle_minion" 898ms

And I remove package "andromeda-dummy" from this "sle_minion" without error control 1s 511ms

And I remove package "virgo-dummy" from this "sle_minion" without error control 1s 497ms

@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 41s 460ms 4 1

Scenario:
Call spacewalk-debug on server
34s 137ms 1

When I execute spacewalk-debug on the server 34s 137ms

Scenario:
Check the tomcat logs on server
813ms 1

Then the tomcat logs should not contain errors 813ms

Scenario:
Check salt event log for failures on server
4s 907ms 1

Then the salt event log on server should contain no failures 4s 907ms Show Error + 
                                            
 
Found 24 failures in salt event log:

# Failure 2 , _stamp: 2026-03-04T23:02:17.463140 {
    "__id__": "run_ansible_playbook",
    "__run_num__": 0,
    "__sls__": "ansible.runplaybook",
    "changes": {
        "ret": {
            "pid": 10995,
            "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": 4497.269,
    "name": "ansible.playbooks",
    "result": false,
    "start_time": "00:02:12.955013"
}

# Failure 3 , _stamp: 2026-03-04T23:56:13.907184 {
    "__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-p14818-i14819.scope; invocation ID: de47c2f248564401880d1cb98a6b36f7Loading 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": 1920.115,
    "name": "pkg_installed",
    "result": false,
    "start_time": "00:56:11.978370"
}

# Failure 4 , _stamp: 2026-03-05T00:13:54.460239 {
    "__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": 13930.728,
    "name": "docker.build",
    "result": false,
    "start_time": "01:13:40.501935"
}

# Failure 5 , _stamp: 2026-03-05T00:13:54.460239 {
    "__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": "01:13:54.433106"
}

# Failure 6 , _stamp: 2026-03-05T00:13:54.460239 {
    "__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": "01:13:54.433375"
}

# Failure 7 , _stamp: 2026-03-05T00:15:09.662267 {
    "__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": 14159.305,
    "name": "docker.build",
    "result": false,
    "start_time": "01:14:55.474434"
}

# Failure 8 , _stamp: 2026-03-05T00:15:09.662267 {
    "__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": "01:15:09.634200"
}

# Failure 9 , _stamp: 2026-03-05T00:15:09.662267 {
    "__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": "01:15:09.634471"
}

# Failure 10 , _stamp: 2026-03-05T00:20:52.651760 {
    "__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": 13297.557,
    "name": "docker.build",
    "result": false,
    "start_time": "01:20:39.320302"
}

# Failure 11 , _stamp: 2026-03-05T00:20:52.651760 {
    "__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": "01:20:52.618308"
}

# Failure 12 , _stamp: 2026-03-05T00:20:52.651760 {
    "__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": "01:20:52.618579"
}

# Failure 13 , _stamp: 2026-03-05T00:21:50.485844 {
    "__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": 14027.859,
    "name": "docker.build",
    "result": false,
    "start_time": "01:21:36.427520"
}

# Failure 14 , _stamp: 2026-03-05T00:21:50.485844 {
    "__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": "01:21:50.455957"
}

# Failure 15 , _stamp: 2026-03-05T00:21:50.485844 {
    "__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": "01:21:50.456234"
}

# Failure 16 , _stamp: 2026-03-05T00:22:51.534296 {
    "__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": 13378.249,
    "name": "docker.build",
    "result": false,
    "start_time": "01:22:38.127366"
}

# Failure 17 , _stamp: 2026-03-05T00:22:51.534296 {
    "__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": "01:22:51.506058"
}

# Failure 18 , _stamp: 2026-03-05T00:22:51.534296 {
    "__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": "01:22:51.506325"
}

# Failure 19 , _stamp: 2026-03-05T00:23:47.890371 {
    "__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": 14122.333,
    "name": "docker.build",
    "result": false,
    "start_time": "01:23:33.740343"
}

# Failure 20 , _stamp: 2026-03-05T00:23:47.890371 {
    "__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": "01:23:47.863160"
}

# Failure 21 , _stamp: 2026-03-05T00:23:47.890371 {
    "__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": "01:23:47.863447"
}

# Failure 22 , _stamp: 2026-03-05T00:32:41.324327 {
    "__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": 13503.741,
    "name": "docker.build",
    "result": false,
    "start_time": "01:32:27.790094"
}

# Failure 23 , _stamp: 2026-03-05T00:32:41.324327 {
    "__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": "01:32:41.294298"
}

# Failure 24 , _stamp: 2026-03-05T00:32:41.324327 {
    "__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": "01:32:41.294572"
}

# Failure 25 , _stamp: 2026-03-05T01:37:51.468737 {
    "__id__": "os_not_supported",
    "__run_num__": 14,
    "__sls__": "prometheus",
    "changes": {},
    "comment": "Failure!",
    "duration": 0.752,
    "name": "OS not supported!",
    "result": false,
    "start_time": "02:37:24.010694"
}

 (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
884ms 1

Then the taskomatic logs should not contain errors 884ms

Scenario:
Check for out of memory errors
717ms 1

Then the log messages should not contain out of memory errors 717ms

Feature:Debug the clients after the testsuite has run 2m 30s 828ms 1

Scenario:
Extract the logs from all our clients
2m 30s 828ms 1

When I extract the log files from all our active nodes 2m 30s 828ms

@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