All Scenarios

1527

Passed Scenarios

1249

Failed Scenarios

51

Skipped Scenarios

227

Execution Time: 461m 9s 4ms

Expand All | Collapse All

Metadata

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

Feature:Sanity checks 1m 24s 692ms 10 2

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

Scenario:
The server is healthy
29s 89ms 11

Then "server" should have a FQDN 435ms

And reverse resolution should work for "server" 4s 521ms

And the clock from "server" should be exact 2s 538ms

And service "apache2" is active on "server" 2s 465ms

And service "cobblerd" is active on "server" 2s 483ms

And service "rhn-search" is active on "server" 2s 512ms

And service "salt-api" is active on "server" 2s 536ms

And service "salt-master" is active on "server" 4s 62ms

And service "taskomatic" is active on "server" 2s 452ms

And socket "tftp" is active on "server" 2s 469ms

And service "tomcat" is active on "server" 2s 611ms

@proxy
Scenario:
The proxy is healthy
8s 101ms 4

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

And reverse resolution should work for "proxy" 277ms

And "proxy" should communicate with the server using public interface 4s 607ms

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

@sle_minion
Scenario:
The minion is healthy
8s 166ms 4

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

And reverse resolution should work for "sle_minion" 427ms

And "sle_minion" should communicate with the server using public interface 2s 883ms

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

@build_host
Scenario:
The build host is healthy
6s 630ms 4

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

And reverse resolution should work for "build_host" 217ms

And "build_host" should communicate with the server using public interface 3s 786ms

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

@ssh_minion
Scenario:
The SSH minion is healthy
8s 114ms 4

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

And reverse resolution should work for "ssh_minion" 405ms

And "ssh_minion" should communicate with the server using public interface 2s 958ms

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

@rhlike_minion
Scenario:
The Red Hat-like minion is healthy
7s 145ms 4

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

And reverse resolution should work for "rhlike_minion" 194ms

And "rhlike_minion" should communicate with the server using public interface 4s 669ms

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

@deblike_minion
Scenario:
The Debian-like minion is healthy
7s 924ms 4

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

And reverse resolution should work for "deblike_minion" 243ms

And "deblike_minion" should communicate with the server using public interface 2s 730ms

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

@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
2s 530ms 1

Then it should be possible to reach the authenticated registry 2s 530ms

@no_auth_registry
Scenario:
The registry without authentication is healthy
4s 493ms 1

Then it should be possible to reach the not authenticated registry 4s 493ms

@custom_download_endpoint
Scenario:
The custom download endpoint is working
2s 497ms 1

Then it should be possible to use the custom download endpoint 2s 497ms

Feature:Very first settings 58s 171ms 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
2s 499ms 1

When I run "rm -Rf /srv/salt/*" on "server" 2s 499ms

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

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

Scenario:
Wait for refresh of list of products to finish
7s 534ms 1

When I wait until mgr-sync refresh is finished 7s 534ms

Scenario:
Create testing username
3s 714ms 12

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

And I follow "Create User" 662ms

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

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

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

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

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

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

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

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

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

And I should see a "testing" link 11ms

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

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

And I follow "testing" 462ms

And I check "role_org_admin" 88ms

And I check "role_system_group_admin" 81ms

And I check "role_channel_admin" 81ms

And I check "role_activation_key_admin" 81ms

And I check "role_config_admin" 81ms

And I click on "Update" 1s 68ms

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

And I should see a "testing" text 75ms

@server_http_proxy
Scenario:
Setup HTTP proxy
< 1ms 9

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

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

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

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

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

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

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

And I click on "Save and Verify" 0s

Then HTTP proxy verification should have succeeded 0s

Scenario:
Detect latest Salt changes on the server
2s 479ms 1

* Tue Apr 14 2026 Marek Czernek
- Fix testsuite failures
- Added:
* fix-test-failures-754.patch

* Tue Mar 17 2026 Victor Zhestkov
- Backport security patch for Salt vendored tornado (bsc#1259554):
* CVE-2026-31958: Add limits on multipart form data parsing
- Added:
* backport-of-the-cve-2026-31958-fix-bsc-1259554.patch

* Fri Mar 13 2026 Victor Zhestkov
- Add x86_64_v2 as a possible rpm package architecture
- Make users with backslash working for salt-ssh (bsc#1254629)
- Fix ansible.playbooks extra-vars quoting (bsc#1257831)

When I query latest Salt changes on "server" 2s 479ms

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

When I turn off disable_local_repos for all clients 8s 223ms

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

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

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

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

And I ask to add new credentials 0s

And I enter the SCC credentials 0s

And I click on "Save" 0s

And I wait until the SCC credentials are valid 0s

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

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

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

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

And I click on "Save Preferences" 692ms

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

Scenario:
Change page size to 100 per page in testing user
4s 316ms 5

Given I am authorized as "testing" with password "testing" 4s 49ms

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

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

And I click on "Save Preferences" 54ms

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

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

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

New user kiwikiwi created with roles: image_admin

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

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

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

Scenario:
Create a Docker user with image administrators rights
4s 350ms 2

New user docker created with roles: image_admin

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

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

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

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

And I follow "Create" 548ms

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

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

And I click on "create-btn" 79ms

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

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

Feature:Do not let Taskomatic tasks interfere with our CI tests 28s 957ms 3

Scenario:
Log in as admin user
19s 825ms 1

Given I am authorized for the "Admin" section 19s 825ms

Scenario:
Disable scheduled reposyncs
4s 754ms 5

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

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

And I choose "disabled" 68ms

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

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

Scenario:
Disable scheduled Cobbler syncs
4s 377ms 5

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

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

And I choose "disabled" 46ms

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

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

@scc_credentials
Feature:List available channels and enable them 2m 1s 736ms 5 1

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

Scenario:
List available channels
45s 219ms 5

When I refresh SCC 36s 665ms

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

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
3s 264ms 4

When I execute mgr-sync "list channels -e --no-optional" 3s 264ms

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
3s 356ms 2

When I execute mgr-sync "list products" 3s 356ms

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
4s 781ms 4

When I execute mgr-sync "list products --expand --filter x86_64" 4s 781ms

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 5s 114ms 3

When I remove the mgr-sync cache file 2s 535ms

And I execute mgr-sync refresh 1m 2s 578ms

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

Feature:Synchronize products in the products page of the Setup Wizard 64m 50s 621ms 9 9

@scc_credentials
Scenario:
Refresh SCC
33s 506ms 1

When I refresh SCC 33s 506ms

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

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

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

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

Then I should see a "Arch" text 136ms

And I should see a "Channels" text 124ms

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

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

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

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

And I wait until I do not see "Loading" text 1s 23ms

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

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

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

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

@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
3m 39s 404ms 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: 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" 11s 654ms

And I kill running spacewalk-repo-sync for "opensuse_tumbleweed-x86_64" channel 7s 19ms

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

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

When I wait until all synchronized channels for "tumbleweed" have finished 45s 230ms

@containerized_server @proxy @uyuni
Scenario:
Add Uyuni Proxy product for Tumbleweed, including Uyuni Client Tools
46s 481ms 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" 28s 843ms

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

@scc_credentials @uyuni @build_host
Scenario:
Synchronize SLES 15 SP7 product with recommended sub-products for Retail feature
54m 6s 445ms 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: 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: Sync for sle15-sp7-installer-updates-x86_64 still in progress (no completion message found).
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 '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 / 64m 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 / 64m waiting for product 'sles15-sp7' synchronization
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
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 / 64m 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 / 64m 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 / 64m 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 / 64m 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 / 64m 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: Found 'Sync of channel completed.' for sle-module-basesystem15-sp7-updates-x86_64 at line 77.
SUCCESS: sle-module-basesystem15-sp7-updates-x86_64 is fully synchronized.
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sles15-sp7-devel-uyuni-client-x86_64' at line 81. Checking for completion...
DEBUG: Sync for sles15-sp7-devel-uyuni-client-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sles15-sp7-devel-uyuni-client-x86_64' at line 81. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sles15-sp7-devel-uyuni-client-x86_64 at line 85.
SUCCESS: sles15-sp7-devel-uyuni-client-x86_64 is fully synchronized.
8m / 64m waiting for product 'sles15-sp7' synchronization
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-server-applications15-sp7-updates-x86_64' at line 89. Checking for completion...
DEBUG: Sync for sle-module-server-applications15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-server-applications15-sp7-updates-x86_64' at line 89. Checking for completion...
DEBUG: Sync for sle-module-server-applications15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-server-applications15-sp7-updates-x86_64' at line 89. Checking for completion...
DEBUG: Sync for sle-module-server-applications15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-server-applications15-sp7-updates-x86_64' at line 89. Checking for completion...
DEBUG: Sync for sle-module-server-applications15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-server-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-server-applications15-sp7-updates-x86_64' at line 89. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-server-applications15-sp7-updates-x86_64 at line 93.
SUCCESS: sle-module-server-applications15-sp7-updates-x86_64 is fully synchronized.
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-server-applications15-sp7-pool-x86_64' at line 97. Checking for completion...
DEBUG: Sync for sle-module-server-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
9m / 64m 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 97. Checking for completion...
DEBUG: Sync for sle-module-server-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-python3-15-sp7-updates-x86_64' at line 105. Checking for completion...
DEBUG: Sync for sle-module-python3-15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-server-applications15-sp7-pool-x86_64' at line 97. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-server-applications15-sp7-pool-x86_64 at line 101.
SUCCESS: sle-module-server-applications15-sp7-pool-x86_64 is fully synchronized.
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-python3-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-python3-15-sp7-updates-x86_64' at line 105. Checking for completion...
DEBUG: Sync for sle-module-python3-15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-python3-15-sp7-pool-x86_64' at line 113. Checking for completion...
DEBUG: Sync for sle-module-python3-15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-python3-15-sp7-updates-x86_64' at line 105. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-python3-15-sp7-updates-x86_64 at line 109.
SUCCESS: sle-module-python3-15-sp7-updates-x86_64 is fully synchronized.
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-python3-15-sp7-pool-x86_64' at line 113. Checking for completion...
DEBUG: Sync for sle-module-python3-15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-python3-15-sp7-pool-x86_64' at line 113. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-python3-15-sp7-pool-x86_64 at line 117.
SUCCESS: sle-module-python3-15-sp7-pool-x86_64 is fully synchronized.
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-updates-x86_64' not found in reposync.log
10m / 64m waiting for product 'sles15-sp7' synchronization
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-systems-management-15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-systems-management-15-sp7-updates-x86_64' at line 121. Checking for completion...
DEBUG: Sync for sle-module-systems-management-15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-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 129. Checking for completion...
DEBUG: Sync for sle-module-systems-management-15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-systems-management-15-sp7-updates-x86_64' at line 121. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-systems-management-15-sp7-updates-x86_64 at line 125.
SUCCESS: sle-module-systems-management-15-sp7-updates-x86_64 is fully synchronized.
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-systems-management-15-sp7-pool-x86_64' at line 129. 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-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-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 129. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-systems-management-15-sp7-pool-x86_64 at line 133.
SUCCESS: sle-module-systems-management-15-sp7-pool-x86_64 is fully synchronized.
DEBUG: Channel 'sle-module-desktop-applications15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
11m / 64m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
12m / 64m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
13m / 64m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-desktop-applications15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
14m / 64m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-pool-x86_64' at line 137. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-desktop-applications15-sp7-pool-x86_64 at line 141.
SUCCESS: sle-module-desktop-applications15-sp7-pool-x86_64 is fully synchronized.
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-updates-x86_64' at line 145. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-updates-x86_64' at line 145. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-updates-x86_64' at line 145. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-updates-x86_64' at line 145. Checking for completion...
DEBUG: Sync for sle-module-desktop-applications15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-desktop-applications15-sp7-updates-x86_64' at line 145. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-desktop-applications15-sp7-updates-x86_64 at line 149.
SUCCESS: sle-module-desktop-applications15-sp7-updates-x86_64 is fully synchronized.
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Channel 'sle-module-devtools15-sp7-pool-x86_64' not found in reposync.log
15m / 64m waiting for product 'sles15-sp7' synchronization
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 153. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 153. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 153. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 153. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 153. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 153. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-pool-x86_64 still in progress (no completion message found).
16m / 64m waiting for product 'sles15-sp7' synchronization
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 153. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 153. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 153. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 153. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 153. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 153. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-pool-x86_64 still in progress (no completion message found).
17m / 64m waiting for product 'sles15-sp7' synchronization
DEBUG: Channel 'sle-module-devtools15-sp7-updates-x86_64' not found in reposync.log
DEBUG: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 153. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-pool-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-pool-x86_64' at line 153. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-devtools15-sp7-pool-x86_64 at line 157.
SUCCESS: sle-module-devtools15-sp7-pool-x86_64 is fully synchronized.
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
18m / 64m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
19m / 64m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
20m / 64m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
21m / 64m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
22m / 64m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
23m / 64m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
24m / 64m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
25m / 64m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
26m / 64m waiting for product 'sles15-sp7' synchronization
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Sync for sle-module-devtools15-sp7-updates-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'sle-module-devtools15-sp7-updates-x86_64' at line 161. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for sle-module-devtools15-sp7-updates-x86_64 at line 165.
SUCCESS: sle-module-devtools15-sp7-updates-x86_64 is fully synchronized.

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 57ms

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

Then the SLE15 SP7 product should be added 6s 829ms

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

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

And I wait until all synchronized channels for "sles15-sp7" have finished 53m 35s 255ms

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

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.2" as the filtered product description 0s

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

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

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

And I select "SUSE Multi-Linux Manager Client Tools for SLE 16 x86_64" as a product 0s

And I should see the "SUSE Multi-Linux Manager Client Tools for SLE 16 x86_64" selected 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.2 x86_64" product has been added 0s

And I wait until all synchronized channels for "sl-micro-6.2" 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" as a product 0s

Then I should see the "SUSE Linux Enterprise Server 15 SP7" 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" 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.2 with SL Micro 6.2 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.2" as the filtered product description 0s

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

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

And I select "SUSE Multi-Linux Manager Proxy Extension 5.2 x86_64 (BETA)" as a product 0s

Then I should see the "SUSE Multi-Linux Manager Proxy Extension 5.2 x86_64 (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 Multi-Linux Manager Proxy Extension 5.2 x86_64 (BETA)" product has been added 0s

And I wait until all synchronized channels for "suse-multi-linux-manager-proxy-52" 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.2 with SL Micro 6.2 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.2" as the filtered product description 0s

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

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

And I select "SUSE Multi-Linux Manager Retail Branch Server Extension 5.2 x86_64 (BETA)" as a product 0s

Then I should see the "SUSE Multi-Linux Manager Retail Branch Server Extension 5.2 x86_64 (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 Multi-Linux Manager Retail Branch Server Extension 5.2 x86_64 (BETA)" product has been added 0s

And I wait until all synchronized channels for "suse-multi-linux-manager-retail-branch-server-52" 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
4m 55s 968ms 2

SUCCESS: Channel opensuse_tumbleweed-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel opensuse_tumbleweed-x86_64 synchronization took 131 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 14 seconds.
SUCCESS: Channel opensuse_tumbleweed-uyuni-client-devel-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel opensuse_tumbleweed-uyuni-client-devel-x86_64 synchronization took 11 seconds.
SUCCESS: Channel opensuse_tumbleweed-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel opensuse_tumbleweed-x86_64 synchronization took 131 seconds.
SUCCESS: Channel opensuse_tumbleweed-uyuni-client-devel-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel opensuse_tumbleweed-uyuni-client-devel-x86_64 synchronization took 11 seconds.
SUCCESS: Channel uyuni-proxy-devel-tumbleweed-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel uyuni-proxy-devel-tumbleweed-x86_64 synchronization took 8 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 9 seconds.
SUCCESS: Channel sle-product-sles15-sp7-updates-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-product-sles15-sp7-updates-x86_64 synchronization took 4 seconds.
SUCCESS: Channel sle15-sp7-installer-updates-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle15-sp7-installer-updates-x86_64 synchronization took 5 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 341 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 1105 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 50 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 47 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 56 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 116 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 314 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 74 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 694 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 180 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 33 seconds.
SUCCESS: Channel sle-module-systems-management-15-sp7-updates-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sle-module-systems-management-15-sp7-updates-x86_64 synchronization took 30 seconds.
SUCCESS: Channel sles15-sp7-devel-uyuni-client-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel sles15-sp7-devel-uyuni-client-x86_64 synchronization took 22 seconds.

When I wait until all synchronized channels have solved their dependencies 4m 55s 968ms

Then all channels have been synced without errors < 1ms

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

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

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

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

And I wait until I do not see "Loading" text 1s 31ms

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

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

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

@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 24s 625ms 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
515ms 1

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

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

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

And I follow "Create Channel" 322ms

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

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

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

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

And I enter "Base channel 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" 622ms

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

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

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

And I follow "Create Channel" 333ms

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

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

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

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

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

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

And I click on "Create Channel" 56ms

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

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

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

And I follow "Create Channel" 334ms

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

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

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

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

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

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

And I click on "Create Channel" 609ms

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

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

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

And I follow "Create Channel" 334ms

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

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

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

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

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

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

And I click on "Create Channel" 547ms

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

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

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

And I follow "Create Channel" 356ms

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

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

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

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

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

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

And I click on "Create Channel" 624ms

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

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

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

And I follow "Create Channel" 432ms

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

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

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

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

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

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

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

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

And I follow "Create Channel" 363ms

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

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

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

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

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

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

And I click on "Create Channel" 59ms

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

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

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

And I follow "Create Channel" 267ms

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

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

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

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

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

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

And I uncheck "gpg_check" 10s 90ms

And I click on "Create Channel" 550ms

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

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

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

And I follow "Create Channel" 355ms

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

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

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

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

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

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

And I click on "Create Channel" 58ms

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

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

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

And I follow "Create Channel" 364ms

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

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

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

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

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

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

And I click on "Create Channel" 573ms

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

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

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

Scenario:
Create a fake repository for distributions using RPM
833ms 7

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

And I follow "Create Repository" 331ms

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

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

And I click on "Create Repository" 67ms

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

And I should see "metadataSigned" as checked 21ms

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

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

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

And I uncheck "metadataSigned" 10s 79ms

And I click on "Update Repository" 453ms

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

And I should see "metadataSigned" as unchecked 17ms

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

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

And I follow "Create Repository" 343ms

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

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

And I click on "Create Repository" 320ms

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

And I should see "metadataSigned" as checked 17ms

@rhlike_minion
Scenario:
Disable metadata check for the fake AppStream repository
11s 239ms 6

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

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

And I uncheck "metadataSigned" 10s 75ms

And I click on "Update Repository" 759ms

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

And I should see "metadataSigned" as unchecked 17ms

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

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

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

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

And I click on "Update Channel" 644ms

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

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

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

And I click on "Save Repositories" 601ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

And I click on "Update Channel" 60ms

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

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

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

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

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

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

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

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

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

And I click on "Update Channel" 64ms

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

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

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

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

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

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

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

And I follow "Create Repository" 325ms

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

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

And I uncheck "metadataSigned" 10s 80ms

And I click on "Create Repository" 431ms

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

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

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

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

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

And I click on "Update Channel" 69ms

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

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

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

And I click on "Save Repositories" 620ms

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

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

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

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

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

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

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

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

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

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

And I follow "Create Repository" 730ms

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

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

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

And I click on "Create Repository" 531ms

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

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

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

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

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

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

And I click on "Save Repositories" 595ms

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

@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 33s 262ms 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
543ms 1

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

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

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

And I follow "Create Channel" 378ms

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

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

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

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

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

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

And I click on "Create Channel" 70ms

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

@sle_minion
Scenario:
Create custom repositories inside the SUSE custom channel
7s 583ms 1

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

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

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

And I follow "Create Channel" 569ms

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

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

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

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

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

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

And I click on "Create Channel" 58ms

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

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

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

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

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

And I follow "Create Channel" 680ms

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

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

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

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

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

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

And I click on "Create Channel" 803ms

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

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

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

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

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

And I follow "Create Channel" 404ms

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

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

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

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

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

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

And I click on "Create Channel" 588ms

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

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

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

Feature:Synchronize fake channels 2m 25s 632ms 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
4s 325ms 2

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

And I enable source package syncing 3s 634ms

@sle_minion
Scenario:
Synchronize Fake-RPM-SUSE-Channel channel
16s 129ms 9

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

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

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

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

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

And I follow "Sync" 532ms

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

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

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

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

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

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

@skip_if_github_validation
Scenario:
Synchronize Fake-Child-Channel-i586 channel
19s 376ms 9

DEBUG: Found channel 'fake-child-channel-i586' at line 233. Checking for completion...
DEBUG: Sync for fake-child-channel-i586 still in progress (no completion message found).
DEBUG: Found channel 'fake-child-channel-i586' at line 233. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for fake-child-channel-i586 at line 237.
SUCCESS: fake-child-channel-i586 is fully synchronized.

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

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

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

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

And I follow "Sync" 359ms

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

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

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

Scenario:
Synchronize Test-Child-Channel-x86_64 channel
16s 546ms 9

DEBUG: Found channel 'test-child-channel-x86_64' at line 241. Checking for completion...
DEBUG: Sync for test-child-channel-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'test-child-channel-x86_64' at line 241. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for test-child-channel-x86_64 at line 245.
SUCCESS: test-child-channel-x86_64 is fully synchronized.

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

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

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

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

And I follow "Sync" 442ms

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

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

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

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

DEBUG: Found channel 'fake-child-channel-suse-like' at line 249. Checking for completion...
DEBUG: Sync for fake-child-channel-suse-like still in progress (no completion message found).
DEBUG: Found channel 'fake-child-channel-suse-like' at line 249. Checking for completion...
DEBUG: Found 'Sync of channel completed.' for fake-child-channel-suse-like at line 253.
SUCCESS: fake-child-channel-suse-like is fully synchronized.

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

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

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

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

And I follow "Sync" 348ms

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

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

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

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

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

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

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

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

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

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

And I follow "Sync" 355ms

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

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

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

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

@rhlike_minion
Scenario:
Synchronize Fake-Base-Channel-RH-like channel
15s 815ms 9

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

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

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

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

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

And I follow "Sync" 355ms

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

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

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

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

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

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

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

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

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

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

And I follow "Sync" 356ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Scenario:
Cleanup disable source package syncing
2s 891ms 1

Then I disable source package syncing 2s 891ms

@skip_if_github_validation
Feature:Synchronize development channels 1m 30s 763ms 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
17s 13ms 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 446ms

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

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

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

And I follow "Sync" 267ms

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

And I click on "Sync Now" 2s 928ms

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

@deblike_minion
Scenario:
Synchronize Devel-Debian-like-Channel channel
17s 181ms 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 544ms

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

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

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

And I follow "Sync" 349ms

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

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

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

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

@rhlike_minion
Scenario:
Synchronize Devel-RH-like-Channel channel
39s 638ms 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 708ms

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

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

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

And I follow "Sync" 342ms

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

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

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

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

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

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

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

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

And I follow "Sync" 364ms

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

And I click on "Sync Now" 2s 712ms

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

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

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

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

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

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

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

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

@deblike_minion
Scenario:
Create an activation key for Debian-like minion
1s 602ms 2

When I create an activation key with id "DEBLIKE-KEY", description "Debian-like Test Key", base channel "fake-base-channel-debian-like", limit of 20 and contact method "default" 1s 112ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 560ms

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

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

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

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

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

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

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

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

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

And I click on "Update Activation Key" 0s

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 1s 459ms

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

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

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

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

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

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

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

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

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

And I click on "Update Activation Key" 0s

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 496ms

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 "Multi-Linux-ManagerTools-SLE-16 for x86_64 6.2" has been checked 0s

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

And I check "SUSE-Multi-Linux-Manager-Retail-Branch-Server-5.2 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 959ms 20

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

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

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

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

And I wait for child channels to appear 452ms

And I include the recommended child channels 175ms

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

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

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 585ms

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

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

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

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

And I wait for child channels to appear 792ms

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

And I wait for child channels to appear 325ms

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

And I click on "Update Activation Key" 460ms

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

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

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

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

And I wait for child channels to appear 909ms

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

And I wait for child channels to appear 319ms

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

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

And I click on "Update Activation Key" 575ms

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

@scc_credentials @build_host
Scenario:
Update terminal key with synced base product
3s 847ms 16

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

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

And I wait for child channels to appear 2s 78ms

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

And I wait for child channels to appear 554ms

And I include the recommended child channels 169ms

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 582ms

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

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

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

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

And I wait for child channels to appear 764ms

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

And I click on "Update Activation Key" 438ms

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

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

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

And I wait for child channels to appear 761ms

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

And I click on "Update Activation Key" 428ms

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

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

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

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

And I wait for child channels to appear 688ms

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

And I click on "Update Activation Key" 445ms

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

Feature:Create bootstrap repositories 27s 304ms 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
7s 454ms 1

When I create the bootstrap repositories including custom channels 7s 454ms

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

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

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

@containerized_server @scope_containerized_proxy @proxy
Feature:Setup containerized proxy 3m 41s 480ms 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 678ms 1

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

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

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

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

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 63ms

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

@skip_if_cloud @transactional_server
Scenario:
Reboot the proxy host
< 1ms 1

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

Scenario:
Wait until the proxy host appears
1m 23s 589ms 1

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

Scenario:
Generate containerized proxy configuration
13s 986ms 2

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

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

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
19s 705ms 1

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

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

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

And I wait until "uyuni-proxy-httpd" service is active on "proxy" 5s 169ms

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

And I wait until "uyuni-proxy-squid" service is active on "proxy" 2s 749ms

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

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

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

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

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

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

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

When I follow the left menu "Systems" 65ms

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

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

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

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

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

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

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

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

Scenario:
Bootstrap a Debian-like minion
2m 24s 68ms 14

The hostname of deblike_minion is uyuni-master-deblike-minion
* Tue Apr 14 2026 Marek Czernek
- Fix testsuite failures
- Added:
* fix-test-failures-754.patch
* Tue Mar 17 2026 Victor Zhestkov
- Backport security patch for Salt vendored tornado (bsc#1259554):
* CVE-2026-31958: Add limits on multipart form data parsing
- Added:
* backport-of-the-cve-2026-31958-fix-bsc-1259554.patch
* Fri Mar 13 2026 Victor Zhestkov
- Add x86_64_v2 as a possible rpm package architecture
- Make users with backslash working for salt-ssh (bsc#1254629)
- Fix ansible.playbooks extra-vars quoting (bsc#1257831)
- Fix virtualenv call in test helper to use proper python version
- Added:

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 120ms

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

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

And I wait until I see the name of "deblike_minion", refreshing the page 31s 753ms

And I wait until onboarding is completed for "deblike_minion" 59s 467ms

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

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

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

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

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

Then I should see "proxy" short hostname 128ms

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

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

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

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

Then I should see "deblike_minion" hostname 228ms

Scenario:
Subscribe the Debian-like minion to a base channel
28s 569ms 11

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

Given I am on the Systems overview page of this "deblike_minion" 3s 99ms

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

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

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

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

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

And I click on "Next" 99ms

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

When I click on "Confirm" 115ms

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

And I wait until event "Subscribe channels scheduled by admin" is completed 23s 341ms

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

* Tue Apr 14 2026 Marek Czernek
- Fix testsuite failures
- Added:
* fix-test-failures-754.patch
* Tue Mar 17 2026 Victor Zhestkov
- Backport security patch for Salt vendored tornado (bsc#1259554):
* CVE-2026-31958: Add limits on multipart form data parsing
- Added:
* backport-of-the-cve-2026-31958-fix-bsc-1259554.patch
* Fri Mar 13 2026 Victor Zhestkov
- Add x86_64_v2 as a possible rpm package architecture
- Make users with backslash working for salt-ssh (bsc#1254629)
- Fix ansible.playbooks extra-vars quoting (bsc#1257831)
- Fix virtualenv call in test helper to use proper python version
- Added:

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

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

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

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

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

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

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

Scenario:
Bootstrap a Red Hat-like minion
2m 15s 711ms 13

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

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 147ms

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

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

And I wait until I see the name of "rhlike_minion", refreshing the page 32s 165ms

And I wait until onboarding is completed for "rhlike_minion" 1m 2s 913ms

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

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

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

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

Then I should see "proxy" short hostname 88ms

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

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

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

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

Then I should see "rhlike_minion" hostname 199ms

Scenario:
Subscribe the Red Hat-like minion to a base channel
29s 446ms 11

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

Given I am on the Systems overview page of this "rhlike_minion" 4s 712ms

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

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

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

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

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

And I click on "Next" 100ms

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

When I click on "Confirm" 132ms

Then I should see a "Changing the channels has been scheduled." text 1s 203ms

And I wait until event "Subscribe channels scheduled by admin" is completed 21s 310ms

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

* Tue Apr 14 2026 Marek Czernek
- Fix testsuite failures
- Added:
* fix-test-failures-754.patch

* Tue Mar 17 2026 Victor Zhestkov
- Backport security patch for Salt vendored tornado (bsc#1259554):
* CVE-2026-31958: Add limits on multipart form data parsing
- Added:
* backport-of-the-cve-2026-31958-fix-bsc-1259554.patch

* Fri Mar 13 2026 Victor Zhestkov
- Add x86_64_v2 as a possible rpm package architecture
- Make users with backslash working for salt-ssh (bsc#1254629)
- Fix ansible.playbooks extra-vars quoting (bsc#1257831)

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

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

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

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

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

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

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

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

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

Scenario:
Bootstrap a build host
49s 973ms 10

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

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

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

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

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

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

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

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

And I select the hostname of "proxy" from "proxies" if present 2s 695ms

And I click on "Bootstrap" 116ms

And I wait until I see "Bootstrap process initiated." text 46s 70ms

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

It took 4 seconds to contact the minion

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

Then I should see a "accepted" text 695ms

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

And I wait at most 500 seconds until I see the name of "build_host", refreshing the page 1m 25s 420ms

And I wait at most 500 seconds until onboarding is completed for "build_host" 1m 47s 349ms

Then the Salt master can reach "build_host" 3s 823ms

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

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

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

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

Then I should see "proxy" short hostname 71ms

@proxy
Scenario:
Check registration on build host of minion
1s 172ms 4

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

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

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

Then I should see "build_host" hostname 97ms

Scenario:
Detect latest Salt changes on the SLES build host
566ms 1

* Tue Apr 14 2026 marek.czernek@suse.com
- Fix testsuite failures
- Added:
* fix-test-failures-754.patch

* Tue Mar 17 2026 vzhestkov@suse.com
- Backport security patch for Salt vendored tornado (bsc#1259554):
* CVE-2026-31958: Add limits on multipart form data parsing
- Added:
* backport-of-the-cve-2026-31958-fix-bsc-1259554.patch

* Fri Mar 13 2026 vzhestkov@suse.com
- Add x86_64_v2 as a possible rpm package architecture
- Make users with backslash working for salt-ssh (bsc#1254629)
- Fix ansible.playbooks extra-vars quoting (bsc#1257831)

When I query latest Salt changes on "build_host" 566ms

Scenario:
Check that the build host is a build host
1s 474ms 3

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

Then I should see a "[Container Build Host]" text 96ms

Then I should see a "[OS Image Build Host]" text 91ms

Scenario:
Check events history for failures on SLES build host
1m 22s 42ms 2

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

Then I check for failed events on history event page 1m 20s 930ms

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

Scenario:
Clean up sumaform leftovers on SLES minion
10s 138ms 1

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

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

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

Scenario:
Bootstrap a SLES minion
45s 929ms 11

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

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

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

When I enter the hostname of "sle_minion" as "hostname" 247ms

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

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

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

And I select "1-SUSE-KEY-x86_64" from "activationKeys" 122ms

And I select the hostname of "proxy" from "proxies" if present 2s 819ms

And I click on "Bootstrap" 147ms

And I wait until I see "Bootstrap process initiated." text 41s 824ms

And I report the bootstrap duration for "sle_minion" < 1ms

Scenario:
Check the new bootstrapped minion in System List page
1m 28s 356ms 8

It took 6 seconds to contact the minion

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

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

Then I should see a "accepted" text 130ms

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

And I wait until I see the name of "sle_minion", refreshing the page 18s 428ms

And I wait until onboarding is completed for "sle_minion" 1m 2s 732ms

Then the Salt master can reach "sle_minion" 5s 881ms

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
4s 300ms 4

Given I am on the Systems overview page of this "sle_minion" 3s 771ms

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

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

Then I should see "proxy" short hostname 248ms

@proxy
Scenario:
Check registration on proxy of minion
4s 421ms 4

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

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

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

Then I should see "sle_minion" hostname 269ms

@ssh_minion
Feature:Bootstrap a Salt host managed via salt-ssh 3m 40s 184ms 5 2

Scenario:
Clean up sumaform leftovers on SLES SSH minion
10s 495ms 1

When I perform a full salt minion cleanup on "ssh_minion" 10s 495ms

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

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

Scenario:
Bootstrap a SLES SSH minion
2m 47s 820ms 11

The hostname of ssh_minion is uyuni-master-suse-sshminion.sumaci.aws

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

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

When I check "manageWithSSH" 231ms

And I enter the hostname of "ssh_minion" as "hostname" 376ms

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

And I select the hostname of "proxy" from "proxies" if present 2s 825ms

And I click on "Bootstrap" 140ms

And I wait until I see "Bootstrap process initiated." text 1m 3s 788ms

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

And I wait until I see the name of "ssh_minion", refreshing the page 59s 502ms

And I wait until onboarding is completed for "ssh_minion" 40s 109ms

@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 270ms 4

Given I am on the Systems overview page of this "ssh_minion" 995ms

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

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

Then I should see "proxy" short hostname 94ms

@proxy
Scenario:
Check registration on proxy of SSH minion
1s 608ms 4

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

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

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

Then I should see "ssh_minion" hostname 143ms

@scope_visualization
Feature:Secure connection 315ms 4

Scenario:
Connecting to the server insecurely
2ms 2

Error: 302 302

When I connect to the server insecurely 1ms

Then the connection should redirect to the secured channel < 1ms

Scenario:
Connecting to the server securely
92ms 3

When I connect to the server securely 92ms

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

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

When I connect to the server securely while using incorrect certificate as a CA certificate file 138ms

Then the secure connection should fail due to unverified certificate signature < 1ms

Feature:List available products 6s 531ms 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
6s 531ms 1 1

When I execute mgr-sync "list products" with user "admin" and password "admin" 6s 531ms

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/tomcat/conf.d/tomcat_jmx.conf" should not exist on server 0s

And file "/etc/rhn/taskomatic.conf.d/taskomatic_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/tomcat/conf.d/tomcat_jmx.conf" should contain "jmx_prometheus_javaagent.jar=5556" on server 0s

And file "/etc/rhn/taskomatic.conf.d/taskomatic_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 2m 27s 703ms 12

Scenario:
Fake an IPMI host
12s 266ms 1

When the server starts mocking an IPMI host 12s 266ms

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

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

Scenario:
Start Cobbler monitoring
12s 322ms 1

When I start local monitoring of Cobbler 12s 322ms

Scenario:
Check the power management page
5s 429ms 6

Given I am on the Systems overview page of this "sle_minion" 5s 107ms

When I follow "Provisioning" in the content area 84ms

And I follow "Power Management" in the content area 68ms

Then I should see a "Power Management Settings" text 76ms

And I should see a "IPMI" text 65ms

And I should see a "Save" button 26ms

Scenario:
Save power management values
15s 533ms 9

When I enter "fakeipmi" as "powerAddress" 65ms

And I enter "ipmiusr" as "powerUsername" 60ms

And I enter "test" as "powerPassword" 56ms

And I click on "Save" 579ms

Then I should see a "Power settings saved" text 69ms

And the cobbler report should contain "Power Management Address : fakeipmi" for "sle_minion" 3s 654ms

And the cobbler report should contain "Power Management Username : ipmiusr" for "sle_minion" 3s 193ms

And the cobbler report should contain "Power Management Password : test" for "sle_minion" 4s 519ms

And the cobbler report should contain "Power Management Type : ipmilan" for "sle_minion" 3s 334ms

Scenario:
Test IPMI functions
22s 406ms 18

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

And I follow "Power Management" in the content area 59ms

And I click on "Power On" 2s 825ms

And I click on "Get status" 726ms

Then I should see the power is "On" 22ms

When I click on "Power Off" 2s 826ms

Then I should see a "system has been powered off" text 74ms

And I should see the power is "Unknown" 23ms

When I click on "Get status" 618ms

Then I should see the power is "Off" 20ms

When I click on "Power On" 2s 831ms

Then I should see a "system has been powered on" text 69ms

When I click on "Get status" 1s 131ms

Then I should see the power is "On" 20ms

When I click on "Reboot" 10s 336ms

Then I should see a "system has been rebooted" text 72ms

When I click on "Get status" 666ms

Then I should see the power is "On" 19ms

Scenario:
Check power management SSM configuration
15s 763ms 21

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

And I click on the clear SSM button 108ms

And I check the "sle_minion" client 445ms

And I follow the left menu "Systems > System Set Manager > Overview" 511ms

And I follow "Configure power management" in the content area 67ms

Then I should see "sle_minion" as link 15ms

And I should see a "Change Power Management Configuration" text 80ms

And I should see a "Type" text 72ms

And I should see a "Network address" text 72ms

And I should see a "Username" text 73ms

And I should see a "Password" text 74ms

And I should see a "System identifier" text 72ms

And I should see a "Update" button 17ms

When I enter "testing" as "powerUsername" 50ms

And I enter "qwertz" as "powerPassword" 51ms

And I click on "Update" 438ms

Then I should see a "Configuration successfully saved for 1 system(s)" text 80ms

And the cobbler report should contain "Power Management Username : testing" for "sle_minion" 3s 701ms

And the cobbler report should contain "Power Management Password : qwertz" for "sle_minion" 3s 163ms

And the cobbler report should contain "Power Management Address : fakeipmi" for "sle_minion" 3s 217ms

And the cobbler report should contain "Power Management Type : ipmilan" for "sle_minion" 3s 289ms

Scenario:
Check power management SSM operation
202ms 6

And I follow the left menu "Systems > System Set Manager > Overview" 72ms

When I follow "power management operations" in the content area 68ms

Then I should see "sle_minion" as link 11ms

And I should see a "Power On" button 16ms

And I should see a "Power Off" button 17ms

And I should see a "Reboot" button 16ms

Scenario:
Cleanup: reset IPMI values
16s 398ms 8

Given I want to operate on this "sle_minion" 466ms

When I set power management value "" for "powerAddress" 434ms

And I set power management value "" for "powerUsername" 441ms

And I set power management value "" for "powerPassword" 413ms

Then the cobbler report should contain "Power Management Address :" for "sle_minion" 3s 271ms

And the cobbler report should contain "Power Management Username :" for "sle_minion" 3s 182ms

And the cobbler report should contain "Power Management Password :" for "sle_minion" 3s 327ms

And the cobbler report should contain "Power Management Type : ipmilan" for "sle_minion" 4s 860ms

Scenario:
Cleanup: tear down the IPMI host
478ms 1

When the server stops mocking an IPMI host 478ms

Scenario:
Cleanup: remove remaining systems from SSM after power management tests
55ms 1

When I click on the clear SSM button 55ms

Scenario:
Check for errors in Cobbler monitoring
8s 621ms 1

Then the local logs for Cobbler should not contain errors 8s 621ms

@skip_if_github_validation @scope_api @sle_minion
Feature:IPMI Power management API 51s 251ms 6

Scenario:
Setup an IPMI host for API test
3s 75ms 2

When the server starts mocking an IPMI host 2s 674ms

And I want to operate on this "sle_minion" 401ms

Scenario:
Check the power management settings for API test
761ms 2

When I fetch power management values 761ms

Then power management results should have "ipmilan" for "powerType" < 1ms

Scenario:
Save power management values for API test
16s 514ms 8

When I set power management value "fakeipmi" for "powerAddress" 658ms

And I set power management value "ipmiusr" for "powerUsername" 402ms

And I set power management value "test" for "powerPassword" 386ms

And I set power management value "ipmilan" for "powerType" 375ms

Then the cobbler report should contain "Power Management Address : fakeipmi" for "sle_minion" 3s 168ms

And the cobbler report should contain "Power Management Username : ipmiusr" for "sle_minion" 3s 231ms

And the cobbler report should contain "Power Management Password : test" for "sle_minion" 5s 16ms

And the cobbler report should contain "Power Management Type : ipmilan" for "sle_minion" 3s 275ms

Scenario:
Test IPMI functions for API test
14s 696ms 6

When I turn power on 2s 650ms

Then the power status is "on" 518ms

When I turn power off 2s 631ms

Then the power status is "off" 528ms

When I do power management reboot 7s 840ms

Then the power status is "on" 527ms

Scenario:
Cleanup: reset IPMI values for API test
15s 734ms 7

When I set power management value "" for "powerAddress" 380ms

And I set power management value "" for "powerUsername" 383ms

And I set power management value "" for "powerPassword" 398ms

Then the cobbler report should contain "Power Management Address :" for "sle_minion" 3s 537ms

And the cobbler report should contain "Power Management Username :" for "sle_minion" 3s 226ms

And the cobbler report should contain "Power Management Password :" for "sle_minion" 4s 491ms

And the cobbler report should contain "Power Management Type : ipmilan" for "sle_minion" 3s 317ms

Scenario:
Cleanup: tear down the IPMI host for API test
469ms 1

When the server stops mocking an IPMI host 469ms

@skip_if_github_validation @scope_power_management @scope_cobbler @sle_minion
Feature:Redfish Power management 1m 42s 24ms 11

Scenario:
Setup a Redfish host
14s 702ms 1

When the controller starts mocking a Redfish host 14s 702ms

Scenario:
Log in as admin user
433ms 1

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

Scenario:
Start Cobbler monitoring
13s 850ms 1

When I start local monitoring of Cobbler 13s 850ms

Scenario:
Save power management values for Redfish
16s 400ms 13

Given I am on the Systems overview page of this "sle_minion" 941ms

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

And I follow "Power Management" in the content area 71ms

And I enter the controller hostname as the redfish server address 104ms

And I enter "ipmiusr" as "powerUsername" 52ms

And I enter "test" as "powerPassword" 50ms

And I select "Redfish" from "powerType" 76ms

And I click on "Save" 63ms

Then I should see a "Power settings saved" text 461ms

And the cobbler report should contain ":8443" for "sle_minion" 3s 252ms

And the cobbler report should contain "Power Management Username : ipmiusr" for "sle_minion" 4s 893ms

And the cobbler report should contain "Power Management Password : test" for "sle_minion" 3s 181ms

And the cobbler report should contain "Power Management Type : redfish" for "sle_minion" 3s 179ms

Scenario:
Test Redfish functions
13s 665ms 18

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

And I follow "Power Management" in the content area 59ms

And I click on "Power On" 949ms

And I click on "Get status" 895ms

Then I should see the power is "On" 23ms

When I click on "Power Off" 883ms

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

Then I should see the power is "Off" 19ms

When I click on "Power On" 1s 139ms

Then I should see a "system has been powered on" text 76ms

When I click on "Get status" 1s 11ms

Then I should see the power is "On" 20ms

When I click on "Reboot" 6s 491ms

Then I should see a "system has been rebooted" text 69ms

When I click on "Get status" 925ms

Then I should see the power is "On" 19ms

Scenario:
Check power management SSM configuration for Redfish
17s 1ms 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 413ms

And I follow the left menu "Systems > System Set Manager > Overview" 488ms

And I follow "Configure power management" in the content area 64ms

Then I should see "sle_minion" as link 15ms

And I should see a "Change Power Management Configuration" text 78ms

And I should see a "Type" text 75ms

And I should see a "Network address" text 83ms

And I should see a "Username" text 79ms

And I should see a "Password" text 80ms

And I should see a "System identifier" text 77ms

And I should see a "Update" button 18ms

When I enter "testing" as "powerUsername" 50ms

And I enter "qwertz" as "powerPassword" 50ms

And I click on "Update" 59ms

Then I should see a "Configuration successfully saved for 1 system(s)" text 474ms

And the cobbler report should contain "Power Management Username : testing" for "sle_minion" 4s 855ms

And the cobbler report should contain "Power Management Password : qwertz" for "sle_minion" 3s 261ms

And the cobbler report should contain ":8443" for "sle_minion" 3s 336ms

And the cobbler report should contain "Power Management Type : redfish" for "sle_minion" 3s 242ms

Scenario:
Check power management SSM operation for Redfish
204ms 6

And I follow the left menu "Systems > System Set Manager > Overview" 76ms

When I follow "power management operations" in the content area 64ms

Then I should see "sle_minion" as link 11ms

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

Scenario:
Cleanup: reset Redfish values
16s 908ms 9

Given I want to operate on this "sle_minion" 362ms

When I set power management value "" for "powerAddress" 366ms

And I set power management value "" for "powerUsername" 374ms

And I set power management value "" for "powerPassword" 368ms

And I set power management value "ipmilan" for "powerType" 368ms

Then the cobbler report should contain "Power Management Address :" for "sle_minion" 5s 457ms

And the cobbler report should contain "Power Management Username :" for "sle_minion" 3s 167ms

And the cobbler report should contain "Power Management Password :" for "sle_minion" 3s 194ms

And the cobbler report should contain "Power Management Type : ipmilan" for "sle_minion" 3s 248ms

Scenario:
Cleanup: tear down the Redfish host
46ms 1

When the controller stops mocking a Redfish host 46ms

Scenario:
Cleanup: remove remaining systems from SSM after Redfish power management tests
52ms 1

When I click on the clear SSM button 52ms

Scenario:
Check for errors in Cobbler monitoring
8s 759ms 1

Then the local logs for Cobbler should not contain errors 8s 759ms

@scope_configuration_channels
Feature:Delete channels with child or clone is not allowed 17s 677ms 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
2s 723ms 1

Given I am authorized 2s 723ms

Scenario:
Clone the first channel before deletion from UI test
2s 41ms 8

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

And I follow "Clone Channel" 457ms

And I select "Fake-Base-Channel-SUSE-like" as the origin channel 66ms

And I click on "Clone Channel" 423ms

Then I should see a "Create Software Channel" text 78ms

And I should see a "Current state of the channel" text 73ms

When I click on "Clone Channel" 675ms

Then I should see a "Clone of Fake-Base-Channel-SUSE-like" text 78ms

Scenario:
Clone the second channel using first channel as base
1s 403ms 8

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

And I follow "Clone Channel" 355ms

And I select "Clone of Fake-Base-Channel-SUSE-like" as the origin channel 46ms

And I click on "Clone Channel" 52ms

Then I should see a "Create Software Channel" text 85ms

And I should see a "Current state of the channel" text 75ms

When I click on "Clone Channel" 634ms

Then I should see a "Clone of Clone of Fake-Base-Channel-SUSE-like" text 79ms

Scenario:
Try to delete channel with clone
1s 517ms 7

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

And I follow "Clone of Fake-Base-Channel-SUSE-like" 387ms

And I follow "Delete Channel" 403ms

And I check "unsubscribeSystems" 81ms

And I click on "Delete Channel" 447ms

Then I should see a "Clone of Fake-Base-Channel-SUSE-like" text 61ms

And I should see a "Unable to delete channel" text 60ms

Scenario:
Delete channel without clones neither children
1s 666ms 7

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

And I follow "Clone of Clone of Fake-Base-Channel-SUSE-like" 472ms

And I follow "Delete Channel" 327ms

And I check "unsubscribeSystems" 68ms

And I click on "Delete Channel" 536ms

Then I should see a "Clone of Clone of Fake-Base-Channel-SUSE-like" text 97ms

And I should see a "has been deleted" text 90ms

Scenario:
Clone a child channel to the clone of x86_64 test channel
2s 50ms 9

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

And I follow "Clone Channel" 368ms

And I select "Fake-RPM-SUSE-Channel" as the origin channel 67ms

And I click on "Clone Channel" 53ms

Then I should see a "Create Software Channel" text 79ms

And I should see a "Current state of the channel" text 81ms

When I select "Clone of Fake-Base-Channel-SUSE-like" from "Parent Channel" 63ms

And I click on "Clone Channel" 1s 185ms

Then I should see a "Clone of Fake-RPM-SUSE-Channel" text 73ms

Scenario:
Try delete channel with child
1s 453ms 8

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

And I follow "Clone of Fake-Base-Channel-SUSE-like" 367ms

And I follow "Delete Channel" 337ms

And I check "unsubscribeSystems" 70ms

And I click on "Delete Channel" 414ms

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

And I should see a "must delete those channels first before deleting the parent." text 64ms

Scenario:
Cleanup: remove cloned child channel
2s 178ms 7

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

And I follow "Clone of Fake-RPM-SUSE-Channel" 381ms

And I follow "Delete Channel" 556ms

And I check "unsubscribeSystems" 69ms

And I click on "Delete Channel" 970ms

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

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

And I follow "Clone of Fake-Base-Channel-SUSE-like" 670ms

And I follow "Delete Channel" 316ms

And I check "unsubscribeSystems" 66ms

And I click on "Delete Channel" 1s 328ms

Then I should see a "Clone of Fake-Base-Channel-SUSE-like" text 86ms

And I should see a "has been deleted." text 90ms

@scope_configuration_channels
Feature:Deleting channels with children or clones is not allowed 18s 44ms 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 891ms 1

Given I am authorized 1s 891ms

Scenario:
Clone the first channel before deletion from tool test
2s 224ms 8

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

And I follow "Clone Channel" 390ms

And I select "Fake-RPM-SUSE-Channel" as the origin channel 56ms

And I click on "Clone Channel" 388ms

Then I should see a "Create Software Channel" text 81ms

And I should see a "Current state of the channel" text 74ms

When I click on "Clone Channel" 962ms

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

Scenario:
Clone a second channel using first channel as base
1s 999ms 8

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

And I follow "Clone Channel" 445ms

And I select "Clone of Fake-RPM-SUSE-Channel" as the origin channel 64ms

And I click on "Clone Channel" 416ms

Then I should see a "Create Software Channel" text 77ms

And I should see a "Current state of the channel" text 74ms

When I click on "Clone Channel" 760ms

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

Scenario:
Verify if both clone channels exists
3s 308ms 3

When I list channels with spacewalk-remove-channel 3s 308ms

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

When I delete these channels with spacewalk-remove-channel: 2s 828ms
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
5s 792ms 4

When I delete these channels with spacewalk-remove-channel: 2s 877ms
clone-fake-rpm-suse-channel
clone-clone-fake-rpm-suse-channel

And I list channels with spacewalk-remove-channel 2s 914ms

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 1m 2s 675ms 14 1

Scenario:
Log in as org admin user
1s 649ms 1

Given I am authorized 1s 649ms

Scenario:
Create a single calendar
6s 670ms 9

URL: https://uyuni-master-server.sumaci.aws/pub/maintenance-windows-exchange.ics

When I follow the left menu "Schedule > Maintenance Windows > Calendars" 1s 30ms

And I wait for "1" second 1s

Then I should see a "No calendars created" text 59ms

When I click on "Create" in element "maintenance-windows" 81ms

Then I should see a "Calendar Name" text 60ms

When I enter "singlecalendar" as "name" 77ms

And I add "maintenance-windows-exchange.ics" calendar file as url 4s 7ms

And I click on "Create Calendar" 63ms

Then I should see a "Calendar successfully created" text 289ms

Scenario:
Create a multi calendar
6s 413ms 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" 70ms

And I wait for "1" second 1s

Then I should see a "Items 1 - 1 of 1" text 63ms

When I click on "Create" in element "maintenance-windows" 65ms

Then I should see a "Calendar Name" text 56ms

When I enter "multicalendar" as "name" 67ms

And I add "maintenance-windows-multi-exchange-1.ics" calendar file as url 4s 747ms

And I click on "Create Calendar" 52ms

Then I should see a "Calendar successfully created" text 289ms

Scenario:
Create a single schedule
2s 846ms 11

When I follow the left menu "Schedule > Maintenance Windows > Schedules" 74ms

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

Then I should see a "Schedule Name" text 59ms

When I enter "singleschedule" as "name" 73ms

And I choose "SINGLE" 57ms

And I click on "Add Calendar" 80ms

And I select "singlecalendar" from "calendarSelect" 1s 127ms

And I click on "Create Schedule" 65ms

Then I should see a "Schedule successfully created" text 181ms

Scenario:
Create a multi schedule
2s 832ms 11

When I follow the left menu "Schedule > Maintenance Windows > Schedules" 86ms

And I wait for "1" second 1s

Then I should see a "Items 1 - 1 of 1" text 63ms

When I click on "Create" in element "maintenance-windows" 66ms

Then I should see a "Schedule Name" text 57ms

When I enter "SAP Maintenance Window" as "name" 88ms

And I choose "MULTI" 58ms

And I click on "Add Calendar" 58ms

And I select "multicalendar" from "calendarSelect" 1s 109ms

And I click on "Create Schedule" 55ms

Then I should see a "Schedule successfully created" text 186ms

Scenario:
Create another multi schedule
2s 776ms 10

When I follow the left menu "Schedule > Maintenance Windows > Schedules" 91ms

And I wait for "1" second 1s

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

When I click on "Create" 59ms

And I enter "Core Server Window" as "name" 81ms

And I choose "MULTI" 49ms

And I click on "Add Calendar" 64ms

And I select "multicalendar" from "calendarSelect" 1s 98ms

And I click on "Create Schedule" 57ms

Then I should see a "Schedule successfully created" text 211ms

Scenario:
Assign a single system to the single schedule
2s 530ms 5

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

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

And I select "singleschedule" from "maintenance-schedule" 70ms

And I click on "Update Properties" 1s 86ms

Then I should see a "System properties changed" text 94ms

Scenario:
Assign systems to the multi schedule using SSM
4s 238ms 10

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

And I click on the clear SSM button 55ms

And I check the "rhlike_minion" client 1s 880ms

And I follow the left menu "Systems > System Set Manager > Overview" 461ms

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

And I select "SAP Maintenance Window" from "scheduleId" 1s 117ms

And I check "cancelActions" 87ms

And I click on "Assign All" 68ms

And I click on "Confirm" 69ms

Then I should see a "Maintenance schedule has been assigned" text 289ms

@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
20s 272ms 3

When I remove package "virgo-dummy" from this "rhlike_minion" without error control 1s 426ms

And I refresh packages list via spacecmd on "rhlike_minion" 8s 16ms

And I wait until refresh package list on "rhlike_minion" is finished 10s 828ms

Scenario:
Schedule package installation action
5s 289ms 10

Given I am on the Systems overview page of this "rhlike_minion" 981ms

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

And I follow "Install" 734ms

And I enter "virgo-dummy" as the filtered package name 47ms

And I click on the filter button 770ms

And I check "virgo-dummy" in the list 57ms

And I click on "Install Packages" 1s 437ms

And I select the next maintenance window 19ms

And I click on "Confirm" 1s 107ms

Then I should see a "1 package install has been scheduled for" text 60ms

Scenario:
Detach systems from schedules
2s 643ms 8

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

And I click on the clear SSM button 60ms

And I check the "sle_minion" client 430ms

And I follow the left menu "Systems > System Set Manager > Overview" 588ms

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

And I select "None - clear schedule" from "scheduleId" 1s 120ms

And I click on "Clear All" 65ms

Then I should see a "Maintenance schedule has been cleared" text 177ms

Scenario:
Cleanup: cancel all scheduled actions
1s 336ms 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 336ms

Scenario:
Delete maintenance schedules
2s 77ms 13

When I follow the left menu "Schedule > Maintenance Windows > Schedules" 541ms

And I click the "Core Server Window" item delete button 298ms

Then I should see a "Delete maintenance schedule" text 74ms

When I click on the red confirmation button 68ms

And I wait until I see "Schedule 'Core Server Window' has been deleted." text 231ms

And I click the "SAP Maintenance Window" item delete button 69ms

Then I should see a "Delete maintenance schedule" text 65ms

When I click on the red confirmation button 61ms

And I wait until I see "Schedule 'SAP Maintenance Window' has been deleted." text 302ms

And I click the "singleschedule" item delete button 67ms

Then I should see a "Delete maintenance schedule" text 63ms

When I click on the red confirmation button 57ms

And I wait until I see "Schedule 'singleschedule' has been deleted." text 174ms

Scenario:
Delete maintenance calendars
1s 99ms 9

When I follow the left menu "Schedule > Maintenance Windows > Calendars" 84ms

And I click the "singlecalendar" item delete button 244ms

Then I should see a "Delete maintenance calendar" text 69ms

When I click on the red confirmation button 60ms

And I wait until I see "Calendar 'singlecalendar' has been deleted." text 188ms

And I click the "multicalendar" item delete button 140ms

Then I should see a "Delete maintenance calendar" text 64ms

When I click on the red confirmation button 65ms

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 48s 231ms 13 2

Scenario:
Log in as org admin user
2s 214ms 1

Given I am authorized 2s 214ms

@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
18s 759ms 1

When I apply "setup_users_configuration" local salt state on "server" 18s 759ms

Scenario:
Organization my_org was correctly created
2s 316ms 5

Given I am authorized as "my_org_user" with password "my_org_user" 2s 116ms

When I follow the left menu "Home > My Organization" 72ms

Then I should see a "my_org" text in the content area 28ms

When I follow the left menu "Home > My Organization > Organization Trusts" 76ms

Then I should see a "my_org2" text in the content area 22ms

Scenario:
Organization my_org2 was correctly created
3s 338ms 5

Given I am authorized as "my_org_user2" with password "my_org_user2" 3s 163ms

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

Then I should see a "my_org2" text in the content area 22ms

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

Then I should see a "my_org" text in the content area 23ms

Scenario:
Group was correctly created
2s 469ms 5

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

When I follow the left menu "Systems > System Groups" 122ms

When I follow "minions_group" 392ms

Then I should see a "minions_group" text 70ms

And I should see a "System Group Status" text 65ms

Scenario:
User was correctly created
2s 204ms 5

Given I am authorized as "user2" with password "user2" 1s 661ms

When I follow the left menu "Systems > System Groups" 113ms

And I follow "minions_group" 310ms

Then I should see a "minions_group" text 60ms

And I should see a "System Group Status" text 58ms

Scenario:
User channels permissions were assigned
3s 516ms 5

Given I am authorized as "user2" with password "user2" 352ms

When I follow the left menu "Software > Channel List > All" 198ms

And I follow "Show All Child Channels" 58ms

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

And I follow "Managers" 2s 482ms

Scenario:
User Roles were assigned
2s 263ms 9

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

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

And I follow "user2" 438ms

Then I should see a "User Details" text 88ms

And I should see "role_activation_key_admin" as checked 24ms

And I should see "role_image_admin" as unchecked 21ms

And I should see "role_config_admin" as checked 19ms

And I should see "role_channel_admin" as unchecked 18ms

And I should see "role_system_group_admin" as unchecked 22ms

Scenario:
Activation Key was correctly created
603ms 6

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

And I follow "My Activation Key created via Salt" 353ms

Then I should see "10" in field identified by "usageLimit" 24ms

And I should see "virtualization_host" as checked 18ms

And I should see a "Push via SSH" text 76ms

And I should see "enable-config-auto-deploy" as checked 20ms

Scenario:
Cleanup: apply configuration teardown salt state to server
9s 835ms 1

When I apply "teardown_users_configuration" local salt state on "server" 9s 835ms

@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
259ms 3

When I follow the left menu "Admin > Organizations" 131ms

Then I should not see a "my_org" text 67ms

And I should not see a "my_org2" text 60ms

Scenario:
Cleanup: user was successfully removed
259ms 2

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

Then I should not see a "user2" text 97ms

Scenario:
Cleanup: activation key was successfully removed
189ms 2

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

Then I should not see a "My Activation Key created via Salt" text 83ms

@flaky
Feature:Export and import software channels with new ISS implementation 1m 4s 706ms 10

* Related GitHub Card: https://github.com/SUSE/spacewalk/issues/23113
Distribute software between servers
Run export and import with ISS v2

Scenario:
Install inter server sync package
6s 976ms 2

When I install packages "inter-server-sync" on this "server" 4s 338ms

Then "inter-server-sync" should be installed on "server" 2s 637ms

Scenario:
Log in as org admin user
1s 819ms 1

Given I am authorized 1s 819ms

Scenario:
Clone a channel with patches
2s 265ms 9

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

And I follow "Clone Channel" 366ms

And I select "Fake-RPM-SUSE-Channel" as the origin channel 108ms

And I choose "current" 59ms

And I click on "Clone Channel" 400ms

And I should see a "Create Software Channel" text 82ms

And I should see a "Current state of the channel" text 78ms

And I click on "Clone Channel" 904ms

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

Scenario:
Check that this channel has patches
1s 257ms 8

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

And I follow "Clone of Fake-RPM-SUSE-Channel" 484ms

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

And I follow "List/Remove Patches" 577ms

Then I should see a "CL-hoag-dummy-7890" link 11ms

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
24s 881ms 3

When I ensure folder "/tmp/export_iss_v2" doesn't exist on "server" 2s 628ms

When I export software channels "clone-fake-rpm-suse-channel" with ISS v2 to "/tmp/export_iss_v2" 19s 713ms

Then "/tmp/export_iss_v2" folder on server is ISS v2 export directory 2s 539ms

Scenario:
Cleanup: remove cloned channels
1s 977ms 6

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

And I follow "Clone of Fake-RPM-SUSE-Channel" 387ms

And I follow "Delete Channel" 414ms

And I check "unsubscribeSystems" 84ms

And I click on "Delete Channel" 946ms

Then I should see a "Clone of Fake-RPM-SUSE-Channel" text 71ms

Scenario:
Import data with ISS v2
17s 519ms 1

When I import data with ISS v2 from "/tmp/export_iss_v2" 17s 519ms

Scenario:
Check that this channel was imported and has patches
1s 115ms 8

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

And I follow "Clone of Fake-RPM-SUSE-Channel" 464ms

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

And I follow "List/Remove Patches" 455ms

Then I should see a "CL-hoag-dummy-7890" link 11ms

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

Scenario:
Cleanup: remove imported channel
1s 700ms 6

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

When I follow "Clone of Fake-RPM-SUSE-Channel" 463ms

And I follow "Delete Channel" 316ms

And I check "unsubscribeSystems" 68ms

And I click on "Delete Channel" 713ms

Then I should see a "Clone of Fake-RPM-SUSE-Channel" text 68ms

Scenario:
Cleanup: remove ISS v2 export folder
5s 193ms 1

When I ensure folder "/tmp/export_iss_v2" doesn't exist on "server" 5s 193ms

Feature:Export and import configuration channels with new ISS implementation 54s 352ms 10

Distribute configuration between servers
Run export and import with ISS v2

Scenario:
Install inter server sync package
5s 270ms 2

When I install packages "inter-server-sync" on this "server" 2s 751ms

Then "inter-server-sync" should be installed on "server" 2s 519ms

Scenario:
Log in as org admin user
2s 77ms 1

Given I am authorized 2s 77ms

Scenario:
Create a configuration channel
806ms 7

When I follow the left menu "Configuration > Channels" 125ms

And I follow "Create Config Channel" 327ms

And I enter "Test Config Channel" as "cofName" 68ms

And I enter "testconfigchannel" as "cofLabel" 65ms

And I enter "This is a test configuration channel" as "cofDescription" 83ms

And I click on "Create Config Channel" 68ms

Then I should see a "Test Config Channel" text 67ms

Scenario:
Add a configuration file to the test configuration channel
8s 597ms 9

When I follow the left menu "Configuration > Channels" 66ms

And I follow "Test Config Channel" 426ms

And I follow "Create Configuration File or Directory" 452ms

And I enter "/etc/s-mgr/config" as "cffPath" 68ms

And I enter "COLOR=white" in the editor 4ms

And I click on "Create Configuration File" 68ms

Then I should see a "Revision 1 of /etc/s-mgr/config from channel Test Config Channel" text 93ms

And file "/srv/susemanager/salt/manager_org_1/testconfigchannel/init.sls" should exist on server 4s 461ms

And file "/srv/susemanager/salt/manager_org_1/testconfigchannel/etc/s-mgr/config" should exist on server 2s 955ms

Scenario:
Export data with ISS v2
14s 848ms 3

When I ensure folder "/tmp/export_iss_v2" doesn't exist on "server" 2s 504ms

When I export config channels "testconfigchannel" with ISS v2 to "/tmp/export_iss_v2" 8s 111ms

Then "/tmp/export_iss_v2" folder on server is ISS v2 export directory 4s 231ms

Scenario:
Cleanup: remove the test configuration channel
3s 546ms 6

When I follow the left menu "Configuration > Channels" 61ms

And I follow "Test Config Channel" 468ms

And I follow "Delete Channel" 350ms

And I click on "Delete Config Channel" 59ms

Then file "/srv/susemanager/salt/manager_org_1/testconfigchannel/init.sls" should not exist on server 2s 598ms

And I should not see a "Test Config Channel" link 8ms

Scenario:
Import data with ISS v2
3s 121ms 1

When I import data with ISS v2 from "/tmp/export_iss_v2" 3s 121ms

Scenario:
Check that the config channel was imported
6s 811ms 4

When I follow the left menu "Configuration > Channels" 61ms

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

And file "/srv/susemanager/salt/manager_org_1/testconfigchannel/etc/s-mgr/config" should exist on server 4s 82ms

Scenario:
Cleanup: remove the test configuration channel
4s 25ms 6

When I follow the left menu "Configuration > Channels" 57ms

And I follow "Test Config Channel" 600ms

And I follow "Delete Channel" 278ms

And I click on "Delete Config Channel" 502ms

Then file "/srv/susemanager/salt/manager_org_1/testconfigchannel/init.sls" should not exist on server 2s 580ms

And I should not see a "Test Config Channel" link 5ms

Scenario:
Cleanup: remove ISS v2 export folder
5s 248ms 1

When I ensure folder "/tmp/export_iss_v2" doesn't exist on "server" 5s 248ms

@skip_if_github_validation @sle_minion @scope_salt @under_debugging @test_issue
Feature:Salt master integration with Git pillar 1m 51s 536ms 3 3

* Related GitHub Card: https://github.com/SUSE/spacewalk/issues/26878

Scenario:
Pre-requisite: Enabling repositories for installing git-core
5s 364ms 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 2s 667ms

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

Scenario:
Preparing Git pillar configuration for Salt master
26s 500ms 1 2 1

When I setup a git_pillar environment on the Salt master 6s 809ms Show Error + 
                                            
 FAIL: mgrctl exec -i 'sh /tmp/salt_git_pillar_setup.sh setup' returned status code = 106.
Output:
Setting up git_pillar environment and restarting Salt master and Salt API
Warning: Skipping repository 'SLE-Module-Basesystem15-SP7-Pool' because of the above error.
Warning: Skipping repository 'SLE-Module-Basesystem15-SP7-Updates' because of the above error.
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following 2 NEW packages are going to be installed:
  git-core libsha1detectcoll1

The following 2 packages are not supported by their vendor:
  git-core libsha1detectcoll1

2 new packages to install.

Package download size:     6.0 MiB

Package install size change:
              |      33.9 MiB  required by packages that will be installed
    33.9 MiB  |  -      0 B    released by packages that will be removed

Backend:  classic_rpmtrans
Continue? [y/n/v/...? shows all options] (y): y
Retrieving: libsha1detectcoll1-1.0.3-2.18.x86_64 (SLE_BCI) (1/2),  23.2 KiB    
Retrieving: libsha1detectcoll1-1.0.3-2.18.x86_64.rpm [..done]
Retrieving: git-core-2.51.0-150600.3.12.1.x86_64 (SLE_BCI) (2/2),   6.0 MiB    
Retrieving: git-core-2.51.0-150600.3.12.1.x86_64.rpm [.done]

Checking for file conflicts: [...done]
(1/2) Installing: libsha1detectcoll1-1.0.3-2.18.x86_64 [..done]
(2/2) Installing: git-core-2.51.0-150600.3.12.1.x86_64 [...........done]
Warning: Skipping repository 'SLE-Module-Basesystem15-SP7-Pool' because of the above error.
Warning: Skipping repository 'SLE-Module-Basesystem15-SP7-Updates' because of the above error.
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following 3 NEW packages are going to be installed:
  git perl-Error perl-Git

The following 3 packages are not supported by their vendor:
  git perl-Error perl-Git

3 new packages to install.

Package download size:   344.6 KiB

Package install size change:
              |     306.7 KiB  required by packages that will be installed
   306.7 KiB  |  -      0 B    released by packages that will be removed

Backend:  classic_rpmtrans
Continue? [y/n/v/...? shows all options] (y): y
Retrieving: perl-Error-0.17025-1.20.noarch (SLE_BCI) (1/3),  40.5 KiB    
Retrieving: perl-Error-0.17025-1.20.noarch.rpm [..done]
Retrieving: perl-Git-2.51.0-150600.3.12.1.x86_64 (SLE_BCI) (2/3), 184.6 KiB    
Retrieving: perl-Git-2.51.0-150600.3.12.1.x86_64.rpm [.done]
Retrieving: git-2.51.0-150600.3.12.1.x86_64 (SLE_BCI) (3/3), 119.5 KiB    
Retrieving: git-2.51.0-150600.3.12.1.x86_64.rpm [.done]

Checking for file conflicts: [...done]
(1/3) Installing: perl-Error-0.17025-1.20.noarch [..done]
(2/3) Installing: perl-Git-2.51.0-150600.3.12.1.x86_64 [..done]
(3/3) Installing: git-2.51.0-150600.3.12.1.x86_64 [..done]
 (ScriptError)
./features/support/remote_node.rb:172:in `run_local'
./features/support/remote_node.rb:120:in `run'
./features/step_definitions/salt_steps.rb:83:in `/^I setup a git_pillar environment on the Salt master$/'
features/secondary/srv_salt_git_pillar.feature:19:in `I setup a git_pillar environment on the Salt master'

And I wait until Salt master can reach "sle_minion" 0s

Then file "/etc/salt/master.d/zz-testing-gitpillar.conf" should exist on server 0s

19s 690ms Show Info + 
17:33:49:000 - 17:33:55:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/configuration/GlobalConfigChannelList.do
Screenshot +

Scenario:
Check for the expected pillar data after enabling Git pillar
34s 814ms 4 1 1

When I refresh the pillar data 3s 874ms

And I wait until there is no pillar refresh salt job active 4s 810ms

Then the pillar data for "org_id" should be "1" on "sle_minion" 4s 683ms

And the pillar data for "git_pillar_foobar" should be "12345" on "sle_minion" 3s 430ms Show Error + 
                                            
 Output value wasn't found: uyuni-master-suse-minion.sumaci.aws:
 (ScriptError)
./features/step_definitions/salt_steps.rb:378:in `/^the pillar data for "([^"]*)" should be "([^"]*)" on "([^"]*)"$/'
features/secondary/srv_salt_git_pillar.feature:28:in `the pillar data for "git_pillar_foobar" should be "12345" on "sle_minion"'

And the pillar data for "git_pillar_foobar" should be "12345" on the Salt master 0s

18s 15ms Show Info + 
17:34:15:000 - 17:34:32:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/configuration/GlobalConfigChannelList.do
Screenshot +

Scenario:
Cleanup: Remove Git pillar configuration for Salt master
20s 676ms 1 2 1

When I clean up the git_pillar environment on the Salt master 2s 602ms Show Error + 
                                            
 FAIL: mgrctl exec -i 'sh /tmp/salt_git_pillar_setup.sh clean' returned status code = 1.
Output:
Cleaning git_pillar environment and restarting Salt master and Salt API
 (ScriptError)
./features/support/remote_node.rb:172:in `run_local'
./features/support/remote_node.rb:120:in `run'
./features/step_definitions/salt_steps.rb:90:in `/^I clean up the git_pillar environment on the Salt master$/'
features/secondary/srv_salt_git_pillar.feature:32:in `I clean up the git_pillar environment on the Salt master'

And I wait until Salt master can reach "sle_minion" 0s

Then file "/etc/salt/master.d/zz-testing-gitpillar.conf" should not exist on server 0s

18s 74ms Show Info + 
17:34:50:000 - 17:34:53:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/configuration/GlobalConfigChannelList.do
Screenshot +

Scenario:
Cleanup: Check for the expected pillar data after disabling Git pillar
17s 25ms 4

When I refresh the pillar data 4s 560ms

Then the pillar data for "git_pillar_foobar" should be empty on "sle_minion" 4s 376ms

And the pillar data for "org_id" should be "1" on "sle_minion" 3s 503ms

And the pillar data for "git_pillar_foobar" should be empty on the Salt master 4s 585ms

Scenario:
Pre-Cleanup: Disabling repositories for uninstalling git-core
7s 153ms 2

When I remove repository "SLE-Module-Basesystem15-SP7-Updates" on "server" without error control 4s 542ms

And I remove repository "SLE-Module-Basesystem15-SP7-Pool" on "server" without error control 2s 611ms

@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 20s 485ms 5

Scenario:
Log in as org admin user
1s 878ms 1

Given I am authorized 1s 878ms

@ssh_minion
Scenario:
Reboot the SSH-managed SLES minion
3m 57s 336ms 6

Given I am on the Systems overview page of this "ssh_minion" 5s 182ms

When I follow first "Schedule System Reboot" 650ms

Then I should see a "System Reboot Confirmation" text 71ms

And I should see a "Reboot system" button 17ms

When I click on "Reboot system" 940ms

Then I wait and check that "ssh_minion" has rebooted 3m 50s 473ms

Scenario:
Schedule a reboot on a SLES Salt minion
4m 16s 909ms 8

2026-04-20 17:42:30 +0200 Still waiting for action to complete...

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

When I follow first "Schedule System Reboot" 478ms

Then I should see a "System Reboot Confirmation" text 73ms

And I should see a "Reboot system" button 14ms

And I click on "Reboot system" 828ms

Then I should see a "Reboot scheduled for system" text 88ms

When I wait at most 600 seconds until event "System reboot scheduled" is completed 4m 13s 999ms

And I should see a "Reboot completed." text 59ms

@rhlike_minion
Scenario:
Reboot the Red Hat-like minion and wait until reboot is completed
3m 59s 880ms 8

2026-04-20 17:46:46 +0200 Still waiting for action to complete...

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

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

When I click on "Reboot system" 861ms

Then I should see a "Reboot scheduled for system" text 86ms

When I wait at most 600 seconds until event "System reboot scheduled" is completed 3m 57s 289ms

Then I should see a "Reboot completed." text 56ms

@deblike_minion
Scenario:
Reboot the Debian-like minion and wait until reboot is completed
4m 4s 480ms 8

2026-04-20 17:50:51 +0200 Still waiting for action to complete...

Given I am on the Systems overview page of this "deblike_minion" 5s 698ms

When I follow first "Schedule System Reboot" 478ms

Then I should see a "System Reboot Confirmation" text 70ms

And I should see a "Reboot system" button 19ms

When I click on "Reboot system" 867ms

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 57s 193ms

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 1m 14s 721ms 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 382ms 1

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

Scenario:
Pre-requisite: downgrade milkyway-dummy to lower version
9s 735ms 9

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 887ms

And I install old package "milkyway-dummy-1.0" on this "sle_minion" 1s 454ms

And I refresh the metadata for "sle_minion" 818ms

And I follow the left menu "Admin > Task Schedules" 138ms

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

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

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

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

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

Scenario:
Schedule channel data refresh
3s 301ms 6

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

And I follow "cve-server-channels-default" 380ms

And I follow "cve-server-channels-bunch" 1s 167ms

And I click on "Single Run Schedule" 337ms

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

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

Scenario:
Display CVE audit page
218ms 3

When I follow the left menu "Audit > CVE Audit" 123ms

Then I should see a "CVE Audit" link in the left menu 26ms

And I should see a "CVE Audit" text 69ms

Scenario:
Search for a known CVE number
21s 510ms 14

When I follow the left menu "Audit > CVE Audit" 61ms

And I select "1999" from "cveIdentifierYear" 70ms

And I enter "9999" as "cveIdentifierId" 71ms

And I click on "Audit Servers" 62ms

Then I should see "sle_minion" as link 819ms

And I should see a "Affected, at least one patch available in an assigned channel" text 96ms

And I should see a "Install a new patch on this system" link 11ms

And I should see a "milkyway-dummy-2345" text 88ms

And I should see a "Download CSV" link 11ms

And I should see a "Status" button 17ms

And I should see a "Name" button 16ms

And I should see a "extra CVE data update" link 10ms

Then I follow "Install a new patch on this system" on "sle_minion" row 20s 85ms

And I should see a "Relevant Patches" text 84ms

Scenario:
Search for an unknown CVE number
468ms 5

When I follow the left menu "Audit > CVE Audit" 105ms

And I select "2012" from "cveIdentifierYear" 57ms

And I enter "2806" as "cveIdentifierId" 53ms

And I click on "Audit Servers" 52ms

Then I should see a "The specified CVE number was not found" text 198ms

Scenario:
Select a system for the System Set Manager
2s 9ms 11

And I click on the clear SSM button 57ms

And I follow the left menu "Audit > CVE Audit" 67ms

And I select "1999" from "cveIdentifierYear" 62ms

And I enter "9999" as "cveIdentifierId" 57ms

And I click on "Audit Servers" 55ms

Then I should see a "Affected, at least one patch available in an assigned channel" text 75ms

When I check the "sle_minion" client 713ms

Then I should see a "system selected" text 221ms

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

Then I should see "sle_minion" as link 446ms

And I click on the clear SSM button 51ms

Scenario:
List systems by patch status via API before patch
8s 522ms 12

Result list: [{"errata_advisories"=>[], "system_id"=>1000010004, "channel_labels"=>[], "patch_status"=>"NOT_AFFECTED"}, {"errata_advisories"=>[], "system_id"=>1000010001, "channel_labels"=>[], "patch_status"=>"NOT_AFFECTED"}, {"errata_advisories"=>[], "system_id"=>1000010003, "channel_labels"=>[], "patch_status"=>"NOT_AFFECTED"}, {"errata_advisories"=>[], "system_id"=>1000010005, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}, {"errata_advisories"=>[], "system_id"=>1000010000, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}, {"errata_advisories"=>[], "system_id"=>1000010002, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}]
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"=>["milkyway-dummy-2345"], "system_id"=>1000010003, "channel_labels"=>["fake-rpm-suse-channel"], "patch_status"=>"AFFECTED_FULL_PATCH_APPLICABLE"}, {"errata_advisories"=>[], "system_id"=>1000010004, "channel_labels"=>[], "patch_status"=>"NOT_AFFECTED"}, {"errata_advisories"=>[], "system_id"=>1000010005, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}, {"errata_advisories"=>[], "system_id"=>1000010000, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}, {"errata_advisories"=>[], "system_id"=>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" 125ms

And I follow "cve-server-channels-default" 1s 347ms

And I follow "cve-server-channels-bunch" 1s 250ms

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

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

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

When I call audit.list_systems_by_patch_status() with CVE identifier "CVE-1999-9979" 1s 382ms

Then I should get status "NOT_AFFECTED" for "sle_minion" 395ms

When I call audit.list_systems_by_patch_status() with CVE identifier "CVE-1999-9999" 1s

Then I should get status "AFFECTED_FULL_PATCH_APPLICABLE" for "sle_minion" 368ms

And I should get the "fake-rpm-suse-channel" channel label < 1ms

And I should get the "milkyway-dummy-2345" patch < 1ms

Scenario:
Apply patches
22s 398ms 10

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

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

And I follow "Patches" in the content area 88ms

And I enter "milkyway" as the filtered synopsis 52ms

And I click on the filter button 512ms

And I check "milkyway-dummy-2345" in the list 63ms

And I click on "Apply Patches" 634ms

And I click on "Confirm" 766ms

Then I should see a "patch update has been scheduled" text 89ms

And I wait until event "Patch Update: milkyway-dummy-2345" is completed 19s 78ms

Scenario:
List systems by patch status via API after patch
1s 763ms 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"=>1000010005, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}, {"errata_advisories"=>[], "system_id"=>1000010000, "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" 1s 309ms

Then I should get status "PATCHED" for "sle_minion" 453ms

Scenario:
Cleanup: remove installed packages
2s 349ms 2

When I disable repository "test_repo_rpm_pool" on this "sle_minion" without error control 759ms

And I remove package "milkyway-dummy" from this "sle_minion" without error control 1s 589ms

Scenario:
Cleanup: remove remaining systems from SSM after CVE audit tests
61ms 1

When I click on the clear SSM button 61ms

@scope_openscap @scope_res @rhlike_minion
Feature:OpenSCAP audit of Red Hat-like Salt minion 3m 41s 759ms 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
503ms 1

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

@skip_if_github_validation
Scenario:
Enable repositories for openSCAP on the Red Hat-like minion
34s 829ms 2

When I enable the repositories "Rocky-BaseOS Rocky-AppStream" on this "rhlike_minion" 384ms

And I refresh the metadata for "rhlike_minion" 34s 444ms

@skip_if_github_validation
Scenario:
Install the OpenSCAP packages on the Red Hat-like minion
1m 17s 103ms 5

Given I am on the Systems overview page of this "rhlike_minion" 1s 144ms

And I install OpenSCAP dependencies on "rhlike_minion" 37s

And I follow "Software" in the content area 74ms

And I click on "Update Package List" 576ms

And I wait until event "Package List Refresh" is completed 38s 306ms

Scenario:
Schedule an OpenSCAP audit job on the Red Hat-like minion
1m 14s 421ms 10

Given I am on the Systems overview page of this "rhlike_minion" 988ms

When I follow "Audit" in the content area 77ms

And I follow "OpenSCAP" in the content area 64ms

And I follow "Schedule" in the content area 67ms

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 69ms

And I enter "--profile xccdf_org.ssgproject.content_profile_anssi_bp28_intermediary" as "params" 126ms

And I enter "/usr/share/xml/scap/ssg/content/ssg-rhel8-ds.xml" as "path" 93ms

And I click on "Schedule" 690ms

Then I should see a "XCCDF scan has been scheduled" text 71ms

And I wait at most 500 seconds until event "OpenSCAP xccdf scanning" is completed 1m 12s 170ms

Scenario:
Check the results of the OpenSCAP scan on the Red Hat-like minion
2s 916ms 7

Given I am on the Systems overview page of this "rhlike_minion" 1s 86ms

When I follow "Audit" in the content area 84ms

And I follow "OpenSCAP" in the content area 64ms

And I follow "xccdf_org.open-scap_testresult" 1s 52ms

Then I should see a "Details of XCCDF Scan" text 215ms

And I should see a "RHEL-8" text 207ms

And I should see a "XCCDF Rule Results" text 205ms

Scenario:
Cleanup: remove audit scans retention period from Red Hat-like minion
874ms 6

When I follow the left menu "Admin > Organizations" 130ms

When I follow "SUSE Test" in the content area 79ms

And I follow "Configuration" in the content area 65ms

And I enter "0" as "scap_retention_period" 60ms

And I click on "Update Organization" 64ms

Then I should see a "Organization SUSE Test was successfully updated." text 473ms

Scenario:
Cleanup: delete audit results from Red Hat-like minion
3s 728ms 8

Given I am on the Systems overview page of this "rhlike_minion" 1s 360ms

When I follow "Audit" in the content area 66ms

And I follow "OpenSCAP" in the content area 62ms

And I follow "List Scans" in the content area 65ms

And I click on "Select All" 416ms

And I click on "Remove" 583ms

And I click on "Confirm" 1s 107ms

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
781ms 6

When I follow the left menu "Admin > Organizations" 102ms

When I follow "SUSE Test" in the content area 60ms

And I follow "Configuration" in the content area 57ms

And I enter "90" as "scap_retention_period" 43ms

And I click on "Update Organization" 451ms

Then I should see a "Organization SUSE Test was successfully updated." text 66ms

@skip_if_github_validation
Scenario:
Cleanup: remove the OpenSCAP packages from the Red Hat-like minion
5s 47ms 2

When I remove OpenSCAP dependencies from "rhlike_minion" 4s 857ms

And I disable repository "Rocky-BaseOS" on this "rhlike_minion" 189ms

@skip_if_github_validation
Scenario:
Cleanup: restore the base channel for the Red Hat-like minion
21s 554ms 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 2ms

When I follow "Software" in the content area 70ms

And I follow "Software Channels" in the content area 68ms

And I wait until I do not see "Loading..." text 65ms

And I check radio button "Fake-Base-Channel-RH-like" 177ms

And I wait until I do not see "Loading..." text 683ms

And I click on "Next" 63ms

Then I should see a "Confirm Software Channel Change" text 61ms

When I click on "Confirm" 73ms

Then I should see a "Changing the channels has been scheduled." text 295ms

And I wait until event "Subscribe channels scheduled" is completed 18s 992ms

@skip_if_github_validation @scope_res @rhlike_minion
Feature:Remote command on the Red Hat-like Salt minion 28s 979ms 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 725ms 1

Given I am authorized 1s 725ms

Scenario:
Run a remote command on the Red Hat-like minion
27s 253ms 11

When I follow the left menu "Salt > Remote Commands" 124ms

Then I should see a "Remote Commands" text in the content area 22ms

When I enter command "cat /etc/os-release" 84ms

And I enter target "rhlike_minion" 106ms

And I click on preview 11s 635ms

And I click on run 72ms

Then I should see "rhlike_minion" hostname 55ms

When I wait for "15" seconds 15s

And I expand the results for "rhlike_minion" 50ms

Then I should see a "rhel centos fedora" text 50ms

And I should see a "ROCKY_SUPPORT_PRODUCT" text 52ms

@skip_if_github_validation @scope_res @rhlike_minion
Feature:Bootstrap a SSH-managed Red Hat-like minion and do some basic operations on it 12m 52s 772ms 12

Scenario:
Log in as org admin user
1s 973ms 1

Given I am authorized 1s 973ms

Scenario:
Delete the Red Hat-like minion before SSH minion tests
4m 7s 794ms 7

When I am on the Systems overview page of this "rhlike_minion" 2s 17ms

And I follow "Delete System" 647ms

Then I should see a "Confirm System Profile Deletion" text 62ms

When I click on "Delete Profile" 62ms

And I wait until I see "has been deleted" text 4m 4s 267ms

And I wait until Salt client is inactive on "rhlike_minion" 343ms

Then "rhlike_minion" should not be registered 393ms

Scenario:
Bootstrap a SSH-managed Red Hat-like minion
2m 34s 878ms 11

The hostname of rhlike_minion is uyuni-master-rhlike-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 81ms

Then I should see a "Bootstrap Minions" text 64ms

When I check "manageWithSSH" 92ms

And I enter the hostname of "rhlike_minion" as "hostname" 146ms

And I enter "linux" as "password" 66ms

And I select the hostname of "proxy" from "proxies" if present 2s 793ms

And I click on "Bootstrap" 65ms

And I wait at most 480 seconds until I see "Bootstrap process initiated." text 47s 863ms

And I follow the left menu "Systems > System List > All" 145ms

And I wait until I see the name of "rhlike_minion", refreshing the page 57s 874ms

And I wait until onboarding is completed for "rhlike_minion" 45s 685ms

@proxy
Scenario:
Check connection from SSH-managed Red Hat-like minion to proxy
1s 241ms 4

Given I am on the Systems overview page of this "rhlike_minion" 1s 18ms

When I follow "Details" in the content area 79ms

And I follow "Connection" in the content area 76ms

Then I should see "proxy" short hostname 66ms

@proxy
Scenario:
Check registration on proxy of SSH-managed Red Hat-like minion
1s 226ms 4

Given I am on the Systems overview page of this "proxy" 978ms

When I follow "Details" in the content area 76ms

And I follow "Proxy" in the content area 70ms

Then I should see "rhlike_minion" hostname 101ms

Scenario:
Subscribe the SSH-managed Red Hat-like minion to a base channel
51s 965ms 11

Given I am on the Systems overview page of this "rhlike_minion" 1s 239ms

When I follow "Software" in the content area 69ms

And I follow "Software Channels" in the content area 64ms

And I wait until I do not see "Loading..." text 64ms

And I check radio button "Fake-Base-Channel-RH-like" 10s 70ms

And I wait until I do not see "Loading..." text 496ms

And I click on "Next" 62ms

Then I should see a "Confirm Software Channel Change" text 57ms

When I click on "Confirm" 76ms

Then I should see a "Changing the channels has been scheduled." text 299ms

And I wait until event "Subscribe channels scheduled" is completed 39s 463ms

Scenario:
Check events history for failures on SSH-managed Red Hat-like minion
1m 1s 896ms 2

Given I am on the Systems overview page of this "rhlike_minion" 988ms

Then I check for failed events on history event page 1m 907ms

Scenario:
Run a remote command on the SSH-managed Red Hat-like minion
29s 761ms 11

When I follow the left menu "Salt > Remote Commands" 143ms

Then I should see a "Remote Commands" text in the content area 20ms

When I enter command "cat /etc/os-release" 97ms

And I enter target "rhlike_minion" 106ms

And I click on preview 14s 133ms

And I click on run 47ms

Then I should see "rhlike_minion" hostname 54ms

When I wait for "15" seconds 15s

And I expand the results for "rhlike_minion" 49ms

Then I should see a "rhel centos fedora" text 55ms

And I should see a "ROCKY_SUPPORT_PRODUCT" text 51ms

Scenario:
Check events history for failures on SSH-managed Red Hat-like minion
1m 12s 43ms 2

Given I am on the Systems overview page of this "rhlike_minion" 1s 110ms

Then I check for failed events on history event page 1m 10s 932ms

Scenario:
Cleanup: delete the SSH-managed Red Hat-like minion
14s 536ms 6

When I am on the Systems overview page of this "rhlike_minion" 1s 34ms

And I follow "Delete System" 461ms

Then I should see a "Confirm System Profile Deletion" text 65ms

When I click on "Delete Profile" 70ms

And I wait until I see "has been deleted" text 12s 4ms

Then "rhlike_minion" should not be registered 898ms

Scenario:
Cleanup: bootstrap a Red Hat-like minion after SSH minion tests
1m 44s 151ms 12

The hostname of rhlike_minion is uyuni-master-rhlike-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 78ms

Then I should see a "Bootstrap Minions" text 63ms

When I enter the hostname of "rhlike_minion" as "hostname" 148ms

And I enter "22" as "port" 54ms

And I enter "root" as "user" 61ms

And I enter "linux" as "password" 67ms

And I select the hostname of "proxy" from "proxies" if present 79ms

And I click on "Bootstrap" 63ms

And I wait at most 480 seconds until I see "Bootstrap process initiated." text 20s 421ms

And I follow the left menu "Systems > System List > All" 143ms

And I wait until I see the name of "rhlike_minion", refreshing the page 57s 659ms

And I wait until onboarding is completed for "rhlike_minion" 25s 310ms

Scenario:
Cleanup: re-subscribe the Red Hat-like minion to a base channel
31s 302ms 11

Given I am on the Systems overview page of this "rhlike_minion" 967ms

When I follow "Software" in the content area 81ms

And I follow "Software Channels" in the content area 64ms

And I wait until I do not see "Loading..." text 68ms

And I check radio button "Fake-Base-Channel-RH-like" 10s 69ms

And I wait until I do not see "Loading..." text 514ms

And I click on "Next" 66ms

Then I should see a "Confirm Software Channel Change" text 61ms

When I click on "Confirm" 79ms

Then I should see a "Changing the channels has been scheduled." text 301ms

And I wait until event "Subscribe channels scheduled" is completed 19s 26ms

@skip_if_github_validation @scope_deblike @deblike_minion
Feature:Remote command on Debian-like Salt minion 15s 645ms 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 356ms 1

Given I am authorized 2s 356ms

Scenario:
Run a remote command on the Debian-like minion
13s 289ms 10

When I follow the left menu "Salt > Remote Commands" 127ms

Then I should see a "Remote Commands" text in the content area 23ms

When I enter command "cat /etc/os-release" 86ms

And I enter target "deblike_minion" 91ms

And I click on preview 11s 699ms

And I click on run 48ms

Then I should see "deblike_minion" hostname 53ms

When I wait until I see "show response" text 1s 55ms

And I expand the results for "deblike_minion" 49ms

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 30s 784ms 12

Scenario:
Log in as org admin user
2s 207ms 1

Given I am authorized 2s 207ms

Scenario:
Delete the Debian-like minion
4m 8s 597ms 7

When I am on the Systems overview page of this "deblike_minion" 2s 299ms

And I follow "Delete System" 644ms

Then I should see a "Confirm System Profile Deletion" text 61ms

When I click on "Delete Profile" 61ms

And I wait until I see "has been deleted" text 4m 3s 790ms

And I wait until Salt client is inactive on "deblike_minion" 1s 327ms

Then "deblike_minion" should not be registered 412ms

Scenario:
Bootstrap a SSH-managed Debian-like minion
2m 9s 356ms 11

The hostname of deblike_minion is uyuni-master-deblike-minion

When I follow the left menu "Systems > Bootstrapping" 80ms

Then I should see a "Bootstrap Minions" text 64ms

When I check "manageWithSSH" 91ms

And I enter the hostname of "deblike_minion" as "hostname" 119ms

And I enter "linux" as "password" 61ms

And I select the hostname of "proxy" from "proxies" if present 79ms

And I click on "Bootstrap" 64ms

And I wait at most 480 seconds until I see "Bootstrap process initiated." text 44s 193ms

And I follow the left menu "Systems > System List > All" 145ms

And I wait until I see the name of "deblike_minion", refreshing the page 31s 3ms

And I wait until onboarding is completed for "deblike_minion" 53s 453ms

@proxy
Scenario:
Check connection from SSH-managed Debian-like minion to proxy
1s 299ms 4

Given I am on the Systems overview page of this "deblike_minion" 1s 92ms

When I follow "Details" in the content area 74ms

And I follow "Connection" in the content area 66ms

Then I should see "proxy" short hostname 66ms

@proxy
Scenario:
Check registration on proxy of SSH-managed Debian-like minion
1s 492ms 4

Given I am on the Systems overview page of this "proxy" 1s 248ms

When I follow "Details" in the content area 64ms

And I follow "Proxy" in the content area 85ms

Then I should see "deblike_minion" hostname 95ms

Scenario:
Subscribe the SSH-managed Debian-like minion to a base channel
50s 791ms 11

Given I am on the Systems overview page of this "deblike_minion" 1s 95ms

When I follow "Software" in the content area 68ms

And I follow "Software Channels" in the content area 88ms

And I wait until I do not see "Loading..." text 64ms

And I check radio button "Fake-Base-Channel-Debian-like" 10s 90ms

And I wait until I do not see "Loading..." text 397ms

And I click on "Next" 64ms

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 279ms

And I wait until event "Subscribe channels scheduled" is completed 38s 505ms

Scenario:
Check events history for failures on SSH-managed Debian-like minion
1m 2s 428ms 2

Given I am on the Systems overview page of this "deblike_minion" 1s 374ms

Then I check for failed events on history event page 1m 1s 54ms

Scenario:
Run a remote command on the SSH-managed Debian-like minion
23s 158ms 10

When I follow the left menu "Salt > Remote Commands" 128ms

Then I should see a "Remote Commands" text in the content area 24ms

When I enter command "cat /etc/os-release" 97ms

And I enter target "deblike_minion" 105ms

And I click on preview 17s 245ms

And I click on run 51ms

Then I should see "deblike_minion" hostname 62ms

When I wait until I see "show response" text 5s 339ms

And I expand the results for "deblike_minion" 49ms

Then I should see a "ID=ubuntu" text 54ms

Scenario:
Check events history for failures on SSH-managed Debian-like minion
1m 12s 374ms 2

Given I am on the Systems overview page of this "deblike_minion" 1s 217ms

Then I check for failed events on history event page 1m 11s 157ms

Scenario:
Cleanup: delete the SSH-managed Debian-like minion
17s 332ms 6

When I am on the Systems overview page of this "deblike_minion" 1s 127ms

And I follow "Delete System" 460ms

Then I should see a "Confirm System Profile Deletion" text 63ms

When I click on "Delete Profile" 62ms

And I wait until I see "has been deleted" text 15s 136ms

Then "deblike_minion" should not be registered 482ms

Scenario:
Cleanup: bootstrap a Debian-like minion
1m 50s 382ms 12

The hostname of deblike_minion is uyuni-master-deblike-minion

When I follow the left menu "Systems > Bootstrapping" 83ms

Then I should see a "Bootstrap Minions" text 63ms

When I enter the hostname of "deblike_minion" as "hostname" 129ms

And I enter "22" as "port" 51ms

And I enter "root" as "user" 63ms

And I enter "linux" as "password" 60ms

And I select the hostname of "proxy" from "proxies" if present 79ms

And I click on "Bootstrap" 61ms

And I wait at most 480 seconds until I see "Bootstrap process initiated." text 26s 93ms

And I follow the left menu "Systems > System List > All" 143ms

And I wait until I see the name of "deblike_minion", refreshing the page 44s 604ms

And I wait until onboarding is completed for "deblike_minion" 38s 947ms

Scenario:
Cleanup: re-subscribe the Debian-like minion to a base channel
31s 362ms 11

Given I am on the Systems overview page of this "deblike_minion" 999ms

When I follow "Software" in the content area 98ms

And I follow "Software Channels" in the content area 69ms

And I wait until I do not see "Loading..." text 64ms

And I check radio button "Fake-Base-Channel-Debian-like" 10s 66ms

And I wait until I do not see "Loading..." text 476ms

And I click on "Next" 68ms

Then I should see a "Confirm Software Channel Change" text 57ms

When I click on "Confirm" 60ms

Then I should see a "Changing the channels has been scheduled." text 394ms

And I wait until event "Subscribe channels scheduled" is completed 19s 5ms

@scope_salt_ssh @scope_onboarding @ssh_minion @skip_if_github_validation
Feature:Register a salt-ssh system via API 4m 4s 516ms 11 1

Scenario:
Log in as org admin user
2s 405ms 1

Given I am authorized 2s 405ms

Scenario:
Delete SSH minion system profile before API bootstrap test
19s 478ms 6

Given I am on the Systems overview page of this "ssh_minion" 2s 527ms

When I follow "Delete System" 795ms

Then I should see a "Confirm System Profile Deletion" text 60ms

When I click on "Delete Profile" 77ms

And I wait until I see "has been deleted" text 15s 434ms

Then "ssh_minion" should not be registered 583ms

@proxy
Scenario:
Block direct access from server to sshminion to test proxy as jumphost
840ms 1

Given I block connections from "server" on "ssh_minion" 840ms

Scenario:
Bootstrap a SLES SSH minion via API
45s 444ms 1

When I call system.bootstrap() on host "ssh_minion" and salt-ssh "enabled" 45s 444ms

Scenario:
Check new API bootstrapped salt-ssh system in System Overview page
1m 23s 14ms 3

When I follow the left menu "Systems > System List > All" 99ms

And I wait until I see the name of "ssh_minion", refreshing the page 31s 18ms

And I wait until onboarding is completed for "ssh_minion" 51s 896ms

Scenario:
Check contact method of this Salt SSH system
1s 82ms 2

Given I am on the Systems overview page of this "ssh_minion" 994ms

Then I should see a "Push via SSH" text 88ms

@proxy
Scenario:
Check registration on proxy of SSH minion bootstrapped via API
1s 266ms 4

Given I am on the Systems overview page of this "proxy" 1s 19ms

When I follow "Details" in the content area 82ms

And I follow "Proxy" in the content area 67ms

Then I should see "ssh_minion" hostname 97ms

Scenario:
Check spacecmd system ID of SSH minion bootstrapped via API
7s 591ms 2

Given I am on the Systems overview page of this "ssh_minion" 1s 190ms

Then I run spacecmd listeventhistory for "ssh_minion" 6s 401ms

Scenario:
Check events history for failures on SSH minion after API bootstrap
41s 900ms 2

Given I am on the Systems overview page of this "ssh_minion" 1s 27ms

Then I check for failed events on history event page 40s 873ms

@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 813ms 13

Warning: Radio button 'openSUSE Tumbleweed (x86_64)' is already checked

Given I am on the Systems overview page of this "ssh_minion" 955ms

When I follow "Software" in the content area 69ms

And I follow "Software Channels" in the content area 82ms

And I wait until I do not see "Loading..." text 67ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 161ms

And I wait until I do not see "Loading..." text 413ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 39ms

And I check "Fake-RPM-SUSE-Channel" 38ms

And I click on "Next" 62ms

Then I should see a "Confirm Software Channel Change" text 69ms

When I click on "Confirm" 78ms

Then I should see a "Changing the channels has been scheduled." text 310ms

And I wait until event "Subscribe channels scheduled" is completed 38s 465ms

@proxy
Scenario:
Cleanup and flush the firewall rules
676ms 1

When I flush firewall on "ssh_minion" 676ms

@skip_if_github_validation @scope_onboarding
Feature:Bootstrap a Salt minion via the GUI using SSH key 7m 1s 669ms 7 1

Scenario:
Log in as org admin user
1s 894ms 1

Given I am authorized 1s 894ms

Scenario:
Delete SLES minion system profile before bootstrap with SSH key test
4m 8s 854ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 856ms

When I follow "Delete System" 464ms

Then I should see a "Confirm System Profile Deletion" text 64ms

When I click on "Delete Profile" 68ms

And I wait until I see "has been deleted" text 4m 5s 166ms

And I wait until Salt client is inactive on "sle_minion" 749ms

Then "sle_minion" should not be registered 483ms

Scenario:
Prepare the minion for SSH key authentication
1s 276ms 2

When I backup the SSH authorized_keys file of host "sle_minion" 407ms

And I add pre-generated SSH public key to authorized_keys of host "sle_minion" 869ms

Scenario:
Bootstrap a SLES minion using SSH key with wrong passphrase
38s 464ms 14 1 1

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 70ms

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 84ms

And I attach the file "ssh_keypair/id_rsa_bootstrap-passphrase_linux" to "privKeyFile" 39ms

And I enter "you-shall-not-pass" as "privKeyPwd" 93ms

And I click on "Bootstrap" 66ms

And I wait until I see "An error has occurred during salt execution: unable to establish ssh connection." text 7s 572ms

Then I should see a "Details" button 19ms

When I click on "Details" 71ms

And I wait at most 10 seconds until I see modal containing "Error Details" text 14ms

Then I should see a "Standard Error" text 67ms

And I should see "Permission denied, no authentication information" or "Permission denied (publickey,password,keyboard-interactive)" in the stderr textarea 20s 20ms Show Error + 
                                            
 Text 'Permission denied, no authentication information' and 'Permission denied (publickey,password,keyboard-interactive)' not found (ScriptError)
./features/step_definitions/navigation_steps.rb:734:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:733: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
43s 814ms 11

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 61ms

When I enter the hostname of "sle_minion" as "hostname" 132ms

And I enter "22" as "port" 50ms

And I enter "root" as "user" 58ms

And I check radio button "SSH Private Key" 10s 90ms

And I attach the file "ssh_keypair/id_rsa_bootstrap-passphrase_linux" to "privKeyFile" 39ms

And I enter "linux" as "privKeyPwd" 66ms

And I select the hostname of "proxy" from "proxies" if present 76ms

And I click on "Bootstrap" 74ms

And I wait at most 480 seconds until I see "Bootstrap process initiated." text 33s 85ms

Scenario:
Check new minion bootstrapped with SSH key in System Overview page
1m 25s 176ms 6

It took 4 seconds to contact the minion

When I follow the left menu "Salt > Keys" 129ms

Then I should see a "accepted" text 590ms

When I am on the Systems page 245ms

And I wait until I see the name of "sle_minion", refreshing the page 1m 11s 608ms

And I wait until onboarding is completed for "sle_minion" 8s 878ms

Then the Salt master can reach "sle_minion" 3s 722ms

Scenario:
Also check contact method of this minion
1s 45ms 2

Given I am on the Systems overview page of this "sle_minion" 961ms

Then I should see a "Default" text 84ms

Scenario:
Cleanup: restore authorized keys
1s 142ms 1

When I restore the SSH authorized_keys file of host "sle_minion" 1s 142ms

@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 43s 30ms 9 1

Scenario:
Log in as org admin user
2s 886ms 1

Given I am authorized 2s 886ms

Scenario:
Pre-requisite: remove package before ssh tunnel test
1s 681ms 1

When I remove package "milkyway-dummy" from this "ssh_minion" without error control 1s 681ms

Scenario:
Delete the Salt minion for SSH tunnel bootstrap
17s 46ms 6

Given I am on the Systems overview page of this "ssh_minion" 1s 84ms

When I follow "Delete System" 462ms

Then I should see a "Confirm System Profile Deletion" text 64ms

When I click on "Delete Profile" 62ms

And I wait until I see "has been deleted" text 14s 868ms

Then "ssh_minion" should not be registered 504ms

Scenario:
Register this minion for push via SSH tunnel
2m 34s 889ms 12

The hostname of ssh_minion is uyuni-master-suse-sshminion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 88ms

Then I should see a "Bootstrap Minions" text 62ms

And I enter the hostname of "ssh_minion" as "hostname" 157ms

And I enter "22" as "port" 65ms

And I enter "root" as "user" 62ms

And I enter "linux" as "password" 63ms

And I select "1-SUSE-SSH-TUNNEL-KEY-x86_64" from "activationKeys" 75ms

And I select the hostname of "proxy" from "proxies" if present 64ms

And I check "manageWithSSH" 87ms

And I click on "Bootstrap" 61ms

And I wait at most 480 seconds until I see "Bootstrap process initiated." text 42s 232ms

And I wait until onboarding is completed for "ssh_minion" 1m 51s 866ms

Scenario:
The contact method is SSH tunnel on this minion
1s 49ms 2

Given I am on the Systems overview page of this "ssh_minion" 965ms

Then I should see a "Push via SSH tunnel" text 83ms

Scenario:
Install a package from this SSH tunnel minion
1m 710ms 11

Given I am on the Systems overview page of this "ssh_minion" 987ms

When I follow "Software" in the content area 80ms

And I follow "Install" 520ms

And I enter "milkyway-dummy" as the filtered package name 58ms

And I click on the filter button 619ms

And I wait until I see "milkyway-dummy" text 78ms

And I check row with "milkyway-dummy" and arch of "ssh_minion" 64ms

And I click on "Install Packages" 588ms

And I click on "Confirm" 2s 225ms

Then I should see a "1 package install has been scheduled for" text 60ms

Then I wait until event "Package Install/Upgrade scheduled" is completed 55s 426ms

@flaky
Scenario:
Remove a package from this SSH tunnel minion
4m 32s 653ms 6 5 1

Given I am on the Systems overview page of this "ssh_minion" 949ms

And I follow "Software" in the content area 82ms

And I follow "List / Remove" 957ms

And I enter "milkyway-dummy" as the filtered package name 61ms

And I click on the filter button 978ms

And I wait until I see "milkyway-dummy" text 4m 10s 38ms 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

19s 585ms Show Info + 
18:40:42:000 - 18:44:55:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/packages/PackageList.do?sid=1000010012
Screenshot +

Scenario:
Run a remote command on this SSH tunnel minion
29s 731ms 11

The hostname of ssh_minion is uyuni-master-suse-sshminion.sumaci.aws

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 "echo 'My remote command output'" 108ms

And I enter the hostname of "ssh_minion" as "target" 117ms

And I click on preview 19s 232ms

Then I should see a "Target systems (1)" text 61ms

When I wait until I do not see "pending" text 49ms

And I click on run 49ms

And I wait until I see "show response" text 9s 884ms

And I expand the results for "ssh_minion" 54ms

Then I should see "My remote command output" in the command output for "ssh_minion" 17ms

Scenario:
Cleanup: delete the SSH tunnel minion
23s 915ms 6

Given I am on the Systems overview page of this "ssh_minion" 1s 209ms

When I follow "Delete System" 825ms

Then I should see a "Confirm System Profile Deletion" text 63ms

When I click on "Delete Profile" 62ms

And I wait until I see "has been deleted" text 21s 311ms

Then "ssh_minion" should not be registered 442ms

Scenario:
Cleanup: register a SSH minion after SSH tunnel tests
2m 18s 466ms 4

When I call system.bootstrap() on host "ssh_minion" and salt-ssh "enabled" 43s 563ms

And I follow the left menu "Systems > System List > All" 99ms

And I wait until I see the name of "ssh_minion", refreshing the page 17s 289ms

And I wait until onboarding is completed for "ssh_minion" 1m 17s 514ms

@skip_if_github_validation @scope_onboarding
Feature:Bootstrap a Salt minion via the GUI with an activation key 7m 35s 987ms 14 2

Scenario:
Log in as org admin user
2s 279ms 1

Given I am authorized 2s 279ms

Scenario:
Delete SLES minion system profile
4m 7s 246ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 729ms

When I follow "Delete System" 454ms

Then I should see a "Confirm System Profile Deletion" text 63ms

When I click on "Delete Profile" 70ms

And I wait until I see "has been deleted" text 4m 3s 812ms

And I wait until Salt client is inactive on "sle_minion" 732ms

Then "sle_minion" should not be registered 381ms

Scenario:
Create a configuration channel for the activation key
1s 803ms 7

When I follow the left menu "Configuration > Channels" 140ms

And I follow "Create Config Channel" 317ms

And I enter "Key Channel" as "cofName" 82ms

And I enter "keychannel" as "cofLabel" 56ms

And I enter "This is a configuration channel for the activation key" as "cofDescription" 92ms

And I click on "Create Config Channel" 65ms

Then I should see a "Key Channel" text 1s 49ms

Scenario:
Add a configuration file to the key configuration channel
1s 745ms 6

When I follow the left menu "Configuration > Channels" 66ms

And I follow "Key Channel" 464ms

And I follow "Create Configuration File or Directory" 341ms

And I enter "/etc/euler.conf" as "cffPath" 64ms

And I enter "e^i.pi=-1" in the editor 5ms

And I click on "Create Configuration File" 802ms

@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 844ms 19

When I follow the left menu "Systems > Activation Keys" 125ms

And I follow "Create Key" 346ms

And I wait for child channels to appear 1s 140ms

And I enter "Minion testing" as "description" 85ms

And I enter "MINION-TEST" as "key" 92ms

And I enter "20" as "usageLimit" 62ms

And I select "openSUSE Tumbleweed (x86_64)" from "selectedBaseChannel" 84ms

And I wait for child channels to appear 374ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 84ms

And I check "Fake-RPM-SUSE-Channel" 82ms

And I click on "Create Activation Key" 649ms

And I follow "Configuration" in the content area 76ms

And I follow first "Subscribe to Channels" in the content area 76ms

And I check "Key Channel" in the list 58ms

And I click on "Continue" 425ms

And I follow "Packages" 315ms

And I enter "orion-dummy perseus-dummy" as "packages" 68ms

And I click on "Update Activation Key" 637ms

Then I should see a "Activation key Minion testing has been modified" text 56ms

Scenario:
Bootstrap a SLES minion with an activation key
1m 47s 858ms 13

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 70ms

Then I should see a "Bootstrap Minions" text 69ms

When I enter the hostname of "sle_minion" as "hostname" 155ms

And I enter "22" as "port" 53ms

And I enter "root" as "user" 57ms

And I enter "linux" as "password" 61ms

And I select "1-MINION-TEST" from "activationKeys" 63ms

And I select the hostname of "proxy" from "proxies" if present 61ms

And I click on "Bootstrap" 60ms

And I wait until I see "Bootstrap process initiated." text 24s 577ms

And I follow the left menu "Systems > System List > All" 150ms

And I wait until I see the name of "sle_minion", refreshing the page 57s 763ms

And I wait until onboarding is completed for "sle_minion" 24s 712ms

Scenario:
Verify that minion bootstrapped with Salt key and packages
7s 710ms 5

It took 5 seconds to contact the minion

When I follow the left menu "Salt > Keys" 147ms

Then I should see a "accepted" text 344ms

And the Salt master can reach "sle_minion" 5s 250ms

When I wait for "orion-dummy" to be installed on "sle_minion" 1s 143ms

And I wait for "perseus-dummy" to be installed on "sle_minion" 825ms

Scenario:
Check system ID of bootstrapped minion
7s 46ms 2

Given I am on the Systems overview page of this "sle_minion" 971ms

Then I run spacecmd listeventhistory for "sle_minion" 6s 75ms

@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
754ms 2

Given I am on the Systems page 237ms

Then I should see a "openSUSE Tumbleweed (x86_64)" text 517ms

Scenario:
Verify that minion bootstrapped with configuration channel
1s 609ms 6

Given I am on the Systems overview page of this "sle_minion" 1s 243ms

When I follow "Configuration" in the content area 75ms

Then I should see a "1 configuration channel" text 67ms

When I follow "View Files" in the content area 75ms

Then I should see a "/etc/euler.conf" text 75ms

And I should see a "Key Channel" text 72ms

Scenario:
Cleanup: remove the package states
7s 172ms 12

Given I am on the Systems overview page of this "sle_minion" 1s 328ms

When I follow "States" in the content area 70ms

And I follow "Packages" 542ms

Then I should see a "Package States" text 63ms

When I change the state of "orion-dummy" to "Unmanaged" and "" 124ms

And I change the state of "perseus-dummy" to "Unmanaged" and "" 39ms

Then I should see a "2 Changes" text 73ms

When I click save 50ms

Then I wait until I see "Package states have been saved." text 270ms

And I click apply 48ms

And I remove package "orion-dummy" from this "sle_minion" 2s 214ms

And I remove package "perseus-dummy" from this "sle_minion" 2s 344ms

Scenario:
Cleanup: remove the key configuration channel
1s 373ms 4

When I follow the left menu "Configuration > Channels" 114ms

And I follow "Key Channel" 475ms

And I follow "Delete Channel" 300ms

And I click on "Delete Config Channel" 482ms

Scenario:
Cleanup: delete the activation key
1s 269ms 5

When I follow the left menu "Systems > Activation Keys" 122ms

And I follow "Minion testing" in the content area 68ms

And I follow "Delete Key" 410ms

And I click on "Delete Activation Key" 590ms

Then I should see a "Activation key Minion testing has been deleted." text 77ms

Scenario:
Check events history for failures on SLES minion with activation key
1m 3s 273ms 2

Given I am on the Systems overview page of this "sle_minion" 1s 20ms

Then I check for failed events on history event page 1m 2s 252ms

@skip_if_github_validation @scope_onboarding
Feature:Register a Salt minion via API 7m 27s 456ms 11 1

Scenario:
Log in as org admin user
2s 182ms 1

Given I am authorized 2s 182ms

Scenario:
Delete SLES minion system profile before API bootstrap test
4m 7s 228ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 680ms

When I follow "Delete System" 461ms

Then I should see a "Confirm System Profile Deletion" text 65ms

When I click on "Delete Profile" 63ms

And I wait until I see "has been deleted" text 4m 3s 855ms

And I wait until Salt client is inactive on "sle_minion" 714ms

Then "sle_minion" should not be registered 387ms

Scenario:
Bootstrap a SLES minion via API
24s 723ms 1

When I call system.bootstrap() on host "sle_minion" and salt-ssh "disabled" 24s 723ms

Scenario:
Check new minion bootstrapped via API in System Overview page
1m 25s 508ms 6

It took 4 seconds to contact the minion

When I follow the left menu "Salt > Keys" 135ms

Then I should see a "accepted" text 440ms

When I follow the left menu "Systems > System List > All" 181ms

And I wait until I see the name of "sle_minion", refreshing the page 1m 11s 447ms

And I wait until onboarding is completed for "sle_minion" 9s 518ms

Then the Salt master can reach "sle_minion" 3s 786ms

Scenario:
Check contact method of this minion
1s 117ms 2

Given I am on the Systems overview page of this "sle_minion" 1s 31ms

Then I should see a "Default" text 85ms

@proxy
Scenario:
Check registration on proxy of minion bootstrapped via API
1s 268ms 4

Given I am on the Systems overview page of this "proxy" 1s 2ms

When I follow "Details" in the content area 74ms

And I follow "Proxy" in the content area 95ms

Then I should see "sle_minion" hostname 96ms

Scenario:
Check spacecmd system ID of minion bootstrapped via API
8s 754ms 2

Given I am on the Systems overview page of this "sle_minion" 942ms

Then I run spacecmd listeventhistory for "sle_minion" 7s 811ms

@susemanager
Scenario:
API bootstrap: subscribe to base channel
< 1ms 14

Given I am on the Systems overview page of this "sle_minion" 0s

When I follow "Software" in the content area 0s

And I follow "Software Channels" in the content area 0s

And I wait until I do not see "Loading..." text 0s

And I check radio button "SLE-Product-SLES15-SP7-Pool for x86_64" 0s

And I wait until I do not see "Loading..." text 0s

And I include the recommended child channels 0s

And I check "SLE-Module-DevTools15-SP7-Pool for x86_64" 0s

And I check "Fake-RPM-SUSE-Channel" 0s

And I click on "Next" 0s

Then I should see a "Confirm Software Channel Change" text 0s

When I click on "Confirm" 0s

Then I should see a "Changing the channels has been scheduled." text 0s

And I wait until event "Subscribe channels scheduled" is completed 0s

@uyuni
Scenario:
API bootstrap: subscribe to base channel
21s 347ms 13

Warning: Radio button 'openSUSE Tumbleweed (x86_64)' is already checked

Given I am on the Systems overview page of this "sle_minion" 988ms

When I follow "Software" in the content area 72ms

And I follow "Software Channels" in the content area 86ms

And I wait until I do not see "Loading..." text 65ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 196ms

And I wait until I do not see "Loading..." text 420ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 40ms

And I check "Fake-RPM-SUSE-Channel" 40ms

And I click on "Next" 64ms

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 308ms

And I wait until event "Subscribe channels scheduled" is completed 18s 920ms

Scenario:
Check events history for failures on SLES minion after API bootstrap
51s 826ms 2

Given I am on the Systems overview page of this "sle_minion" 932ms

Then I check for failed events on history event page 50s 894ms

Scenario:
Bootstrap via API a non-existing system
2s 790ms 1

When I call system.bootstrap() on unknown host, I should get an API fault 2s 790ms

Scenario:
Bootstrap a salt-ssh system with activation key and default contact method
707ms 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 707ms

@skip_if_github_validation @sle_minion @scope_onboarding
Feature:Bootstrapping with reactivation key 8m 17s 224ms 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
3s 939ms 1

Given I am authorized 3s 939ms

Scenario:
Generate a re-activation key
3s 10ms 4

Given I am on the Systems overview page of this "sle_minion" 1s 807ms

When I follow "Reactivation" 477ms

And I click on "Generate New Key" 659ms

Then I should see a "Key:" text 66ms

Scenario:
Bootstrap should fail when minion already exists
913ms 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 64ms

When I enter the hostname of "sle_minion" as "hostname" 136ms

And I enter "22" as "port" 53ms

And I enter "root" as "user" 62ms

And I enter "linux" as "password" 59ms

And I click on "Bootstrap" 67ms

And I wait until I see "A salt key for this host" text 266ms

Then I should not see a "GenericSaltError" text 61ms

And I should see a "seems to already exist, please check!" text 62ms

Scenario:
Bootstrap should fail when system already exists in the server
4s 506ms 11

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

Given I delete "sle_minion" key in the Salt master 3s 657ms

When I follow the left menu "Systems > Bootstrapping" 64ms

Then I should see a "Bootstrap Minions" text 61ms

When I enter the hostname of "sle_minion" as "hostname" 125ms

And I enter "22" as "port" 48ms

And I enter "root" as "user" 54ms

And I enter "linux" as "password" 56ms

And I click on "Bootstrap" 60ms

And I wait until I see "seems to already exist, please check!" text 254ms

Then I should not see a "GenericSaltError" text 61ms

And I should see a "with minion id" text 61ms

Scenario:
Bootstrap a SLES minion with reactivation key
1m 52s 319ms 13

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws
Reactivation Key: re-1-c8737f29c37a4c03b1bd7b16aa5f1799

When I follow the left menu "Systems > Bootstrapping" 64ms

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" 49ms

And I enter "root" as "user" 53ms

And I enter "linux" as "password" 55ms

And I enter the reactivation key of "sle_minion" 1s 384ms

And I select "1-SUSE-KEY-x86_64" from "activationKeys" 73ms

And I click on "Bootstrap" 57ms

And I wait until I see "Bootstrap process initiated." text 29s 630ms

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 731ms

And I wait until onboarding is completed for "sle_minion" 1m 19s 870ms

Scenario:
Check the events history for the reactivation
3s 399ms 5

Given I am on the Systems overview page of this "sle_minion" 969ms

When I follow "Events" in the content area 73ms

And I follow "History" in the content area 79ms

And I wait until I see "Server reactivated as Salt minion" text, refreshing the page 93ms

And I wait until event "Apply states [certs, channels, packages, services.salt-minion] scheduled" is completed 2s 183ms

Scenario:
Cleanup: delete SLES minion after reactivation tests
4m 6s 122ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 491ms

When I follow "Delete System" 475ms

Then I should see a "Confirm System Profile Deletion" text 61ms

When I click on "Delete Profile" 81ms

And I wait until I see "has been deleted" text 4m 2s 776ms

And I wait until Salt client is inactive on "sle_minion" 707ms

Then "sle_minion" should not be registered 528ms

Scenario:
Cleanup: bootstrap a SLES minion after reactivation tests
2m 3s 11ms 14

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I perform a full salt minion cleanup on "sle_minion" 6s 616ms

And I follow the left menu "Systems > Bootstrapping" 87ms

Then I should see a "Bootstrap Minions" text 66ms

When I enter the hostname of "sle_minion" as "hostname" 145ms

And I enter "22" as "port" 54ms

And I enter "root" as "user" 61ms

And I enter "linux" as "password" 64ms

And I select "1-SUSE-KEY-x86_64" from "activationKeys" 75ms

And I select the hostname of "proxy" from "proxies" if present 64ms

And I click on "Bootstrap" 63ms

And I wait until I see "Bootstrap process initiated." text 35s 867ms

And I follow the left menu "Systems > System List > All" 148ms

And I wait until I see the name of "sle_minion", refreshing the page 1m 11s 257ms

And I wait until onboarding is completed for "sle_minion" 8s 438ms

@skip_if_github_validation @sle_minion @scope_salt
Feature:Management of minion keys 8m 49s 399ms 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 146ms 1

Given I am authorized 2s 146ms

Scenario:
Delete SLES minion system profile before exploring the onboarding page
4m 7s 976ms 7

Given I am on the Systems overview page of this "sle_minion" 2s 449ms

When I follow "Delete System" 555ms

Then I should see a "Confirm System Profile Deletion" text 63ms

When I click on "Delete Profile" 63ms

And I wait until I see "has been deleted" text 4m 3s 707ms

And I wait until Salt client is inactive on "sle_minion" 725ms

Then "sle_minion" should not be registered 411ms

Scenario:
Completeness of the onboarding page
155ms 2

When I follow the left menu "Salt > Keys" 130ms

Then I should see a "Keys" text in the content area 24ms

Scenario:
Minion is visible in the Pending section
17s 171ms 8

When I configure salt minion on "sle_minion" 416ms

And I restart salt-minion on "sle_minion" 628ms

And I wait at most 10 seconds until Salt master sees "sle_minion" as "unaccepted" 3s 834ms

And I follow the left menu "Salt > Keys" 60ms

And I refresh page until I see "sle_minion" hostname as text 10s 117ms

Then I should see a "Fingerprint" text 72ms

And I see "sle_minion" fingerprint 1s 974ms

And I should see a "pending" text 66ms

Scenario:
Reject and delete the pending key
22s 37ms 7

And I follow the left menu "Salt > Keys" 59ms

And I reject "sle_minion" from the Pending section 332ms

And I wait at most 10 seconds until Salt master sees "sle_minion" as "rejected" 3s 665ms

Then I should see a "rejected" text 68ms

When I stop salt-minion on "sle_minion" 4s 203ms

And I delete "sle_minion" from the Rejected section 47ms

And I refresh page until I do not see "sle_minion" hostname as text 13s 662ms

Scenario:
Accepted minion shows up as a registered system
1m 32s 252ms 9

When I start salt-minion on "sle_minion" 965ms

And I wait at most 10 seconds until Salt master sees "sle_minion" as "unaccepted" 3s 702ms

Then "sle_minion" should not be registered 427ms

When I follow the left menu "Salt > Keys" 64ms

Then I should see a "pending" text 340ms

When I accept "sle_minion" key 52ms

And I wait at most 10 seconds until Salt master sees "sle_minion" as "accepted" 3s 362ms

And I wait until onboarding is completed for "sle_minion" 1m 22s 867ms

Then "sle_minion" should be registered 468ms

Scenario:
The minion communicates with the Salt master
7s 123ms 3

It took 4 seconds to contact the minion

Then the Salt master can reach "sle_minion" 3s 714ms

When I get OS information of "sle_minion" from the Master 3s 408ms

Then it should contain the OS of "sle_minion" < 1ms

Scenario:
Delete profile of unreacheable minion
17s 240ms 9

Given I am on the Systems overview page of this "sle_minion" 977ms

When I stop salt-minion on "sle_minion" 5s 298ms

And I follow "Delete System" 447ms

Then I should see a "Confirm System Profile Deletion" text 60ms

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 673ms

When I click on "Delete Profile Without Cleanup" in "An error occurred during cleanup" modal 2s 28ms

And I wait until I see "has been deleted" text 73ms

Then "sle_minion" should not be registered 617ms

Scenario:
Cleanup: bootstrap again the minion
2m 3s 295ms 12

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I perform a full salt minion cleanup on "sle_minion" 6s 493ms

And I follow the left menu "Systems > Bootstrapping" 78ms

Then I should see a "Bootstrap Minions" text 62ms

When I enter the hostname of "sle_minion" as "hostname" 146ms

And I enter "22" as "port" 53ms

And I enter "root" as "user" 58ms

And I enter "linux" as "password" 61ms

And I select "1-SUSE-KEY-x86_64" from "activationKeys" 75ms

And I select the hostname of "proxy" from "proxies" if present 61ms

And I click on "Bootstrap" 62ms

And I wait until I see "Bootstrap process initiated." text 36s 331ms

And I wait until onboarding is completed for "sle_minion" 1m 19s 810ms

@skip_if_github_validation @scope_salt
Feature:Install a package and a patch on the SUSE client via Salt through the UI 2m 46s 867ms 11

Scenario:
Pre-requisite: enable test_repo_rpm_pool repository on SLE minion
768ms 1

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 768ms

Scenario:
Pre-requisite: install virgo-dummy-1.0 package on SLE minion
1s 847ms 2

When I refresh the metadata for "sle_minion" 995ms

And I install old package "virgo-dummy-1.0" on this "sle_minion" without error control 851ms

Scenario:
Pre-requisite: remove andromeda-dummy package from SLE minion
21s 982ms 4

When I remove package "andromeda-dummy" from this "sle_minion" without error control 1s 589ms

And I refresh the metadata for "sle_minion" 875ms

And I refresh packages list via spacecmd on "sle_minion" 6s 999ms

And I wait until refresh package list on "sle_minion" is finished 12s 517ms

Scenario:
Pre-requisite: refresh package list and check old packages installed on SLE minion
33s 477ms 4

When I refresh packages list via spacecmd on "sle_minion" 6s 24ms

And I wait until refresh package list on "sle_minion" is finished 12s 644ms

Then spacecmd should show packages "virgo-dummy-1.0" installed on "sle_minion" 7s 665ms

And I wait until package "andromeda-dummy-2.0-1.1" is removed from "sle_minion" via spacecmd 7s 143ms

Scenario:
Log in as org admin user
2s 175ms 1

Given I am authorized for the "Admin" section 2s 175ms

Scenario:
Pre-requisite: ensure the errata cache is computed before patching Salt minion
26s 956ms 11

Given I am on the Systems overview page of this "sle_minion" 2s 141ms

When I follow "Software" in the content area 73ms

And I follow "List / Remove" in the content area 85ms

And I enter "virgo-dummy" as the filtered package name 150ms

And I click on the filter button until page does contain "virgo-dummy" text 11s 385ms

When I follow the left menu "Admin > Task Schedules" 123ms

And I follow "errata-cache-default" 1s 359ms

And I follow "errata-cache-bunch" 1s 305ms

And I click on "Single Run Schedule" 1s 269ms

Then I should see a "bunch was scheduled" text 267ms

When I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 8s 794ms

Scenario:
Install a patch on the SLE minion
22s 684ms 12

Given I am on the Systems overview page of this "sle_minion" 1s 6ms

When I follow "Software" in the content area 73ms

And I follow "Patches" in the content area 69ms

And I enter "virgo" as the filtered synopsis 48ms

And I click on the filter button 10s 130ms

And I check "virgo-dummy-3456" in the list 62ms

And I check "allowVendorChange" 75ms

And I click on "Apply Patches" 606ms

And I click on "Confirm" 685ms

Then I should see a "1 patch update has been scheduled for" text 72ms

When I wait for "virgo-dummy-2.0-1.1" to be installed on "sle_minion" 8s 839ms

Then vendor change should be enabled for package actions on "sle_minion" 1s 13ms

Scenario:
Install a package on the SLE minion
13s 754ms 12

Given I am on the Systems overview page of this "sle_minion" 1s 169ms

When I follow "Software" in the content area 81ms

And I follow "Packages" 433ms

And I follow "Install" 551ms

And I enter "andromeda" as the filtered package name 125ms

And I click on the filter button 715ms

And I check "andromeda-dummy-2.0-1.1" in the list 56ms

And I click on "Install Packages" 602ms

And I click on "Confirm" 592ms

Then I should see a "1 package install has been scheduled" text 68ms

When I wait for "andromeda-dummy-2.0-1.1" to be installed on "sle_minion" 8s 545ms

Then vendor change should be enabled for package actions on "sle_minion" 812ms

Scenario:
Cleanup: disable test_repo_rpm_pool on SLE minion
445ms 1

When I disable repository "test_repo_rpm_pool" on this "sle_minion" 445ms

Scenario:
Cleanup: remove virgo-dummy package from SLE minion
21s 74ms 4

When I remove package "virgo-dummy" from this "sle_minion" without error control 1s 543ms

And I refresh the metadata for "sle_minion" 798ms

And I refresh packages list via spacecmd on "sle_minion" 6s 591ms

And I wait until refresh package list on "sle_minion" is finished 12s 140ms

Scenario:
Cleanup: remove andromeda-dummy package from SLE minion
21s 698ms 4

When I remove package "andromeda-dummy" from this "sle_minion" without error control 1s 883ms

And I refresh the metadata for "sle_minion" 844ms

And I refresh packages list via spacecmd on "sle_minion" 8s 204ms

And I wait until refresh package list on "sle_minion" is finished 10s 765ms

@skip_if_github_validation @sle_minion @scope_content_staging
Feature:Install a package on the SLES minion with staging enabled 6m 35s 972ms 8

Scenario:
Pre-requisite: install virgo-dummy-1.0 package, make sure orion-dummy is not present
3s 356ms 3

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 764ms

And I remove package "orion-dummy" from this "sle_minion" without error control 824ms

And I install package "virgo-dummy-1.0" on this "sle_minion" 1s 766ms

Scenario:
Pre-requisite: refresh package list
27s 269ms 3

When I refresh packages list via spacecmd on "sle_minion" 9s 256ms

And I wait until refresh package list on "sle_minion" is finished 11s 801ms

Then spacecmd should show packages "virgo-dummy-1.0" installed on "sle_minion" 6s 212ms

Scenario:
Log in as admin user
461ms 1

Given I am authorized for the "Admin" section 461ms

Scenario:
Pre-requisite: ensure the errata cache is computed before staging tests
5s 520ms 6

When I follow the left menu "Admin > Task Schedules" 123ms

And I follow "errata-cache-default" 1s 262ms

And I follow "errata-cache-bunch" 308ms

Then I click on "Single Run Schedule" 1s 522ms

And I should see a "bunch was scheduled" text 277ms

Then I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 2s 26ms

Scenario:
Enable content staging
1s 272ms 6

When I follow the left menu "Admin > Organizations" 70ms

And I follow first "SUSE Test" 283ms

And I follow first "Configuration" 280ms

And I check "staging_content_enabled" 82ms

And I click on "Update Organization" 490ms

Then I should see a "was successfully updated." text 63ms

Scenario:
Install package in the future and check for staging
2m 52s 425ms 13

Given I am on the Systems overview page of this "sle_minion" 1s 234ms

When I follow "Software" in the content area 74ms

And I follow "Packages" in the content area 89ms

And I follow "Install" in the content area 64ms

And I enter "orion-dummy-1.1-1.1" as the filtered package name 191ms

And I click on the filter button 721ms

And I check row with "orion-dummy-1.1-1.1" and arch of "sle_minion" 61ms

And I click on "Install Packages" 614ms

And I pick 3 minutes from now as schedule time 91ms

And I click on "Confirm" 936ms

Then I should see a "1 package install has been scheduled for" text 70ms

And I wait until the package "orion-dummy-1.1-1.1" has been cached on this "sle_minion" 1m 32s 276ms

And I wait for "orion-dummy-1.1-1.1" to be installed on "sle_minion" 1m 15s 998ms

Scenario:
Install patch in the future and check for staging
3m 935ms 11

When I follow "Software" in the content area 62ms

And I follow "Patches" in the content area 64ms

And I enter "virgo" as the filtered synopsis 41ms

And I click on the filter button 10s 159ms

And I check "virgo-dummy-3456" in the list 66ms

And I click on "Apply Patches" 614ms

And I pick 3 minutes from now as schedule time 88ms

And I click on "Confirm" 1s 10ms

Then I should see a "1 patch update has been scheduled for" text 78ms

And I wait until the package "virgo-dummy-2.0-1.1.noarch" has been cached on this "sle_minion" 1m 30s 334ms

And I wait for "virgo-dummy-2.0-1.1" to be installed on "sle_minion" 1m 18s 413ms

Scenario:
Cleanup: remove virgo-dummy package from SLES minion
4s 731ms 11

When I follow "Software" in the content area 72ms

And I follow "List / Remove" 1s 21ms

And I enter "orion-dummy" as the filtered package name 162ms

And I click on the filter button 1s 168ms

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 124ms

And I check "virgo-dummy" in the list 55ms

And I click on "Remove Packages" 606ms

And I click on "Confirm" 868ms

And I disable repository "test_repo_rpm_pool" on this "sle_minion" 544ms

@skip_if_github_validation @scope_salt @new_issue
Feature:Salt package states 2m 29s 191ms 15

* Related GitHub Card: https://github.com/SUSE/spacewalk/issues/30300

Scenario:
Pre-requisite: install old packages on SLES minion
18s 678ms 6

Salt command: salt uyuni-master-suse-minion.sumaci.aws state.highstate

When I apply highstate on "sle_minion" 10s 709ms

And I enable repository "test_repo_rpm_pool" on this "sle_minion" 753ms

And I refresh the metadata for "sle_minion" 829ms

And I install old package "milkyway-dummy-1.0" on this "sle_minion" without error control 2s 189ms

And I install old package "virgo-dummy-1.0" on this "sle_minion" without error control 2s 432ms

And I install old package "andromeda-dummy-1.0" on this "sle_minion" without error control 1s 764ms

Scenario:
Pre-requisite: refresh package list and check installed packages on SLE minion
25s 766ms 3

When I refresh packages list via spacecmd on "sle_minion" 7s 56ms

And I wait until refresh package list on "sle_minion" is finished 12s 282ms

Then spacecmd should show packages "milkyway-dummy-1.0 virgo-dummy-1.0 andromeda-dummy-1.0" installed on "sle_minion" 6s 426ms

Scenario:
Log in as admin user
1s 123ms 1

Given I am authorized for the "Admin" section 1s 123ms

Scenario:
Pre-requisite: ensure the errata cache is computed before software states tests
8s 495ms 11

Given I am on the Systems overview page of this "sle_minion" 1s 288ms

When I follow "Software" in the content area 80ms

And I follow "List / Remove" in the content area 65ms

And I enter "andromeda-dummy" as the filtered package name 151ms

And I click on the filter button until page does contain "andromeda-dummy-1.0" text 287ms

When I follow the left menu "Admin > Task Schedules" 144ms

And I follow "errata-cache-default" 1s 372ms

And I follow "errata-cache-bunch" 1s 486ms

Then I click on "Single Run Schedule" 1s 260ms

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 2s 88ms

Scenario:
Accepted minion has a base channel
1s 188ms 4

Given I am on the Systems overview page of this "sle_minion" 975ms

When I follow "Software" in the content area 60ms

And I follow "Software Channels" in the content area 82ms

Then the system should have a base channel set 70ms

Scenario:
Remove a package through the UI
12s 90ms 13

When I follow "States" in the content area 66ms

And I follow "Packages" 487ms

And I follow "Search" 66ms

And I should see a "Package States" text 66ms

And I list packages with "dummy" 1s 136ms

And I wait until I see "milkyway-dummy" text 456ms

Then "milkyway-dummy" should be installed on "sle_minion" 729ms

And I change the state of "milkyway-dummy" to "Removed" and "" 58ms

Then I should see a "1 Change" text 91ms

And I click save 53ms

Then I wait until I see "Package states have been saved." text 330ms

And I click apply 47ms

And I wait for "milkyway-dummy" to be uninstalled on "sle_minion" 8s 498ms

Scenario:
Install a package through the UI
12s 136ms 13

When I follow "States" in the content area 63ms

And I follow "Packages" 501ms

And I follow "Search" 57ms

And I should see a "Package States" text 72ms

And I list packages with "dummy" 1s 132ms

And I wait until I see "milkyway-dummy" text 475ms

Then "milkyway-dummy" should not be installed on "sle_minion" 704ms

And I change the state of "milkyway-dummy" to "Installed" and "" 45ms

Then I should see a "1 Change" text 96ms

And I click save 43ms

Then I wait until I see "Package states have been saved." text 212ms

And I click apply 39ms

And I wait for "milkyway-dummy" to be installed on "sle_minion" 8s 691ms

Scenario:
Install an already installed package through the UI
4s 336ms 13

When I follow "States" in the content area 65ms

And I follow "Packages" 586ms

And I follow "Search" 58ms

And I should see a "Package States" text 71ms

And I list packages with "dummy" 1s 129ms

And I wait until I see "virgo-dummy" text 501ms

Then "virgo-dummy-1.0" should be installed on "sle_minion" 606ms

And I change the state of "virgo-dummy" to "Installed" and "Any" 91ms

Then I should see a "1 Change" text 97ms

And I click save 55ms

Then I wait until I see "Package states have been saved." text 201ms

And I click apply 41ms

And I wait for "virgo-dummy-1.0" to be installed on "sle_minion" 830ms

Scenario:
Upgrade a package through the UI
20s 345ms 13

When I follow "States" in the content area 61ms

And I follow "Packages" 852ms

And I follow "Search" 59ms

And I should see a "Package States" text 71ms

And I list packages with "dummy" 1s 130ms

And I wait until I see "andromeda-dummy" text 505ms

Then "andromeda-dummy-1.0" should be installed on "sle_minion" 512ms

And I change the state of "andromeda-dummy" to "Installed" and "Latest" 75ms

Then I should see a "1 Change" text 96ms

And I click save 44ms

Then I wait until I see "Package states have been saved." text 351ms

And I click apply 39ms

And I wait for "andromeda-dummy-2.0-1.1" to be installed on "sle_minion" 16s 544ms

Scenario:
Verify the package states
1s 103ms 6

When I follow "States" in the content area 63ms

And I follow "Packages" 620ms

And I should see a "Package States" text 72ms

And I should see a "milkyway-dummy" text 188ms

And I should see a "andromeda-dummy" text 82ms

And I should see a "virgo-dummy" text 77ms

Scenario:
Use Salt presence mechanism on an active minion
16s 457ms 5

When I follow "States" in the content area 58ms

And I follow "Highstate" in the content area 70ms

And I click on "Show full highstate output" 240ms

And I wait for "6" seconds 6s

And I should see a "pkg_removed" or "running as PID" text in element "highstate" 10s 86ms

Scenario:
Use Salt presence mechanism on an unreachable minion
16s 732ms 6

When I follow "States" in the content area 77ms

And I run "pkill salt-minion" on "sle_minion" without error control 727ms

And I run "pkill python.original" on "sle_minion" without error control 417ms

And I follow "Highstate" in the content area 67ms

And I click on "Show full highstate output" 239ms

And I wait until I see "No reply from minion" text 15s 203ms

Scenario:
Cleanup: restart the salt service on SLES minion
973ms 1

When I restart salt-minion on "sle_minion" 973ms

Scenario:
Cleanup: set the package states as unmanaged
3s 715ms 11

Given I am on the Systems overview page of this "sle_minion" 948ms

When I follow "States" in the content area 84ms

And I follow "Packages" 512ms

And I follow "Search" 66ms

And I should see a "Package States" text 70ms

And I list packages with "dummy" 1s 152ms

And I wait until I see "andromeda-dummy" text 499ms

And I change the state of "virgo-dummy" to "Unmanaged" and "" 77ms

And I change the state of "andromeda-dummy" to "Unmanaged" and "" 45ms

And I click save 50ms

Then I wait until I see "Package states have been saved." text 206ms

Scenario:
Cleanup: remove old packages from SLES minion
6s 49ms 5

When I disable repository "test_repo_rpm_pool" on this "sle_minion" 535ms

And I remove package "milkyway-dummy" from this "sle_minion" without error control 1s 570ms

And I remove package "virgo-dummy" from this "sle_minion" without error control 1s 520ms

And I remove package "andromeda-dummy" from this "sle_minion" without error control 1s 548ms

And I refresh the metadata for "sle_minion" 874ms

@skip_if_github_validation @sle_minion @scope_salt
Feature:Verify that Salt mgrcompat state works when the new module.run syntax is enabled 13m 45s 926ms 10

Scenario:
Log in as org admin user
2s 450ms 1

Given I am authorized 2s 450ms

Scenario:
Remove mgrcompat module from minion synced modules and schedule Hardware Refresh
28s 225ms 8

Given I remove "minion/extmods/states/mgrcompat.py" from salt cache on "sle_minion" 716ms

And I remove "minion/extmods/states/__pycache__/mgrcompat*" from salt cache on "sle_minion" 398ms

And I am on the Systems overview page of this "sle_minion" 1s 203ms

When I follow "Hardware" 659ms

And I click on "Schedule Hardware Refresh" 841ms

Then I should see a "You have successfully scheduled a hardware profile refresh" text 118ms

When I wait until event "Hardware List Refresh scheduled" is completed 22s 198ms

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "sle_minion" 2s 89ms

Scenario:
Remove saltutil grain and mgrcompat module from minion and schedule Hardware Refresh
30s 79ms 10

Given I remove "minion/extmods/states/mgrcompat.py" from salt cache on "sle_minion" 405ms

And I remove "minion/extmods/states/__pycache__/mgrcompat*" from salt cache on "sle_minion" 402ms

And I store "grains: {__suse_reserved_saltutil_states_support: False}" into file "custom_grains.conf" in salt minion config directory on "sle_minion" 404ms

And I refresh salt-minion grains on "sle_minion" 1s 857ms

And I am on the Systems overview page of this "sle_minion" 1s 110ms

When I follow "Hardware" 678ms

And I click on "Schedule Hardware Refresh" 827ms

Then I should see a "You have successfully scheduled a hardware profile refresh" text 124ms

When I wait until event "Hardware List Refresh scheduled" is completed 22s 113ms

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "sle_minion" 2s 155ms

Scenario:
Delete SLES minion system profile before mgrcompat test
4m 6s 622ms 7

Given I am on the Systems overview page of this "sle_minion" 984ms

When I follow "Delete System" 459ms

Then I should see a "Confirm System Profile Deletion" text 64ms

When I click on "Delete Profile" 63ms

And I wait until I see "has been deleted" text 4m 3s 957ms

And I wait until Salt client is inactive on "sle_minion" 715ms

Then "sle_minion" should not be registered 377ms

Scenario:
Enable new module.run syntax on the minion and perform registration
1m 47s 321ms 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" 410ms

When I follow the left menu "Systems > Bootstrapping" 83ms

Then I should see a "Bootstrap Minions" text 66ms

When I enter the hostname of "sle_minion" as "hostname" 141ms

And I enter "22" as "port" 52ms

And I enter "root" as "user" 57ms

And I enter "linux" as "password" 61ms

And I select the hostname of "proxy" from "proxies" if present 76ms

And I click on "Bootstrap" 62ms

And I wait until I see "Bootstrap process initiated." text 24s 96ms

And I wait until onboarding is completed for "sle_minion" 1m 22s 213ms

Scenario:
Check if onboarding for the minion with the new module.run syntax was successful
8s 877ms 3

When I follow the left menu "Systems > System List > All" 152ms

And I wait until I see the name of "sle_minion", refreshing the page 719ms

And I wait until onboarding is completed for "sle_minion" 8s 5ms

Scenario:
Check that installed packages are visible with the new module.run syntax
2s 458ms 4

Given I am on the Systems overview page of this "sle_minion" 1s 176ms

When I follow "Software" in the content area 74ms

And I follow "List / Remove" 1s 74ms

Then I should see a "aaa_base" text 132ms

Scenario:
Check that Hardware Refresh button works on a SLE minion with new module.run syntax
26s 386ms 6

Given I am on the Systems overview page of this "sle_minion" 947ms

And I follow "Hardware" 469ms

And I click on "Schedule Hardware Refresh" 61ms

Then I should see a "You have successfully scheduled a hardware profile refresh" text 831ms

When I wait until event "Hardware List Refresh scheduled" is completed 21s 939ms

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "sle_minion" 2s 136ms

Scenario:
Cleanup: Delete profile of the minion and disable new module.run syntax
4m 7s 375ms 9

Given I am on the Systems overview page of this "sle_minion" 1s 105ms

And I remove "custom_modulerun.conf" from salt minion config directory on "sle_minion" 405ms

And I remove "custom_grains.conf" from salt minion config directory on "sle_minion" 402ms

When I follow "Delete System" 466ms

Then I should see a "Confirm System Profile Deletion" text 67ms

When I click on "Delete Profile" 64ms

And I wait until I see "has been deleted" text 4m 3s 756ms

And I wait until Salt client is inactive on "sle_minion" 711ms

Then "sle_minion" should not be registered 396ms

Scenario:
Cleanup: bootstrap again the minion after mgrcompat tests
2m 6s 128ms 12

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I perform a full salt minion cleanup on "sle_minion" 6s 82ms

And I follow the left menu "Systems > Bootstrapping" 79ms

Then I should see a "Bootstrap Minions" text 62ms

When I enter the hostname of "sle_minion" as "hostname" 145ms

And I enter "22" as "port" 52ms

And I enter "root" as "user" 57ms

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 60ms

And I click on "Bootstrap" 63ms

And I wait until I see "Bootstrap process initiated." text 37s 537ms

And I wait until onboarding is completed for "sle_minion" 1m 21s 849ms

@skip_if_github_validation @sle_minion @scope_salt @flaky
Feature:Lock packages on SLES salt minion 3m 32s 208ms 10

* Related GitHub Card: https://github.com/SUSE/spacewalk/issues/20168

Scenario:
Log in as org admin user
2s 668ms 1

Given I am authorized 2s 668ms

Scenario:
Pre-requisite: install packages needed for locking test
4s 613ms 3

When I install package "orion-dummy" on this "sle_minion" 2s 25ms

And I install package "milkyway-dummy" on this "sle_minion" 1s 700ms

And I remove package "hoag-dummy" from this "sle_minion" without error control 887ms

Scenario:
Lock a package on the client
24s 322ms 13

Given I am on the Systems overview page of this "sle_minion" 1s 558ms

When I follow "Software" in the content area 77ms

And I follow "Lock / Unlock" 594ms

And I enter "hoag-dummy-1.1-1.1" as the filtered package name 55ms

And I click on the filter button 758ms

And I check row with "hoag-dummy-1.1-1.1" and arch of "sle_minion" 63ms

And I click on "Lock" 691ms

Then I should see a "Packages has been requested for being locked." text 76ms

When I wait until event "Lock packages scheduled" is completed 18s 775ms

Then "hoag-dummy-1.1-1.1" is locked on "sle_minion" 990ms

When I follow "Software" in the content area 71ms

And I follow "Lock / Unlock" 580ms

Then package "hoag-dummy-1.1-1.1" is reported as locked 28ms

Scenario:
Attempt to install a locked package on the client
29s 403ms 17

Given I am on the Systems overview page of this "sle_minion" 953ms

When I follow "Software" in the content area 58ms

And I follow "Lock / Unlock" 576ms

And package "hoag-dummy-1.1-1.1" is reported as locked 22ms

And I follow "Install" 589ms

And I enter "hoag-dummy-1.1-1.1" as the filtered package name 62ms

And I click on the filter button 615ms

And I check row with "hoag-dummy-1.1-1.1" and arch of "sle_minion" 63ms

And I click on "Install Packages" 760ms

And I click on "Confirm" 750ms

Then I should see a "1 package install has been scheduled for" text 60ms

When I follow "Events" 427ms

And I follow "History" 1s 349ms

And I wait until I see the event "Package Install/Upgrade scheduled" completed during last minute, refreshing the page 22s 962ms

And I follow the event "Package Install/Upgrade scheduled" completed during last minute 59ms

Then the package scheduled is "hoag-dummy-1.1-1.1" 17ms

And the action status is "Failed" 74ms

Scenario:
Unlock a package on the client
34s 762ms 16

Given I am on the Systems overview page of this "sle_minion" 981ms

When I follow "Software" in the content area 70ms

And I follow "Lock / Unlock" 742ms

And package "hoag-dummy-1.1-1.1" is reported as locked 28ms

And I enter "hoag-dummy-1.1-1.1" as the filtered package name 59ms

And I click on the filter button 616ms

And I check row with "hoag-dummy-1.1-1.1" and arch of "sle_minion" 24ms

And I click on "Unlock" 700ms

Then I should see a "Packages has been requested for being unlocked." text 81ms

When I wait until event "Lock packages scheduled" is completed 19s 119ms

Then "hoag-dummy-1.1-1.1" is unlocked on "sle_minion" 1s 28ms

When I follow "Software" in the content area 77ms

And I follow "Lock / Unlock" 521ms

And I enter "hoag-dummy-1.1-1.1" as the filtered package name 63ms

And I click on the filter button 627ms

Then package "hoag-dummy-1.1-1.1" is reported as unlocked 10s 19ms

Scenario:
Schedule a package lock
3s 114ms 9

Given I am on the Systems overview page of this "sle_minion" 1s 109ms

When I follow "Software" in the content area 62ms

And I follow "Lock / Unlock" 521ms

And I enter "hoag-dummy-1.1-1.1" as the filtered package name 53ms

And I click on the filter button 616ms

And I check row with "hoag-dummy-1.1-1.1" and arch of "sle_minion" 64ms

And I click on "Lock" 592ms

Then I should see a "Packages has been requested for being locked." text 83ms

And package "hoag-dummy-1.1-1.1" is reported as pending to be locked 10ms

Scenario:
Schedule another package lock
24s 871ms 16

Given I am on the Systems overview page of this "sle_minion" 1s 98ms

When I follow "Software" in the content area 65ms

And I follow "Lock / Unlock" 807ms

And I enter "milkyway-dummy-2.0-1.1" as the filtered package name 55ms

And I click on the filter button 606ms

When I check row with "milkyway-dummy-2.0-1.1" and arch of "sle_minion" 58ms

And I click on "Lock" 852ms

Then I should see a "Packages has been requested for being locked." text 79ms

And package "milkyway-dummy-2.0-1.1" is reported as pending to be locked 11ms

When I wait until event "Lock packages scheduled" is completed 18s 757ms

Then "hoag-dummy-1.1-1.1" is locked on "sle_minion" 1s 6ms

And "milkyway-dummy-2.0-1.1" is locked on "sle_minion" 705ms

When I follow "Software" in the content area 61ms

And I follow "Lock / Unlock" 642ms

Then package "hoag-dummy-1.1-1.1" is reported as locked 29ms

And package "milkyway-dummy-2.0-1.1" is reported as locked 32ms

Scenario:
Mix package locks and unlock events
39s 623ms 32

Given I am on the Systems overview page of this "sle_minion" 1s 867ms

When I follow "Software" in the content area 65ms

And I follow "Lock / Unlock" 594ms

And package "hoag-dummy-1.1-1.1" is reported as locked 25ms

And package "milkyway-dummy-2.0-1.1" is reported as locked 27ms

And I enter "orion-dummy-1.1-1.1" as the filtered package name 53ms

And I click on the filter button 623ms

When I check row with "orion-dummy-1.1-1.1" and arch of "sle_minion" 60ms

And I click on "Lock" 602ms

Then I should see a "Packages has been requested for being locked." text 78ms

And package "orion-dummy-1.1-1.1" is reported as pending to be locked 11ms

When I follow "Lock / Unlock" 540ms

And I enter "hoag-dummy-1.1-1.1" as the filtered package name 54ms

And I click on the filter button 603ms

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 131ms

And I check row with "milkyway-dummy-2.0-1.1" and arch of "sle_minion" 24ms

And I click on "Unlock" 1s 305ms

Then I should see a "Packages has been requested for being unlocked." text 83ms

And package "milkyway-dummy-2.0-1.1" is reported as pending to be unlocked 11ms

When I wait until event "Lock packages scheduled" is completed 18s 853ms

Then "hoag-dummy-1.1-1.1" is locked on "sle_minion" 1s 30ms

And "milkyway-dummy-2.0-1.1" is unlocked on "sle_minion" 727ms

And "orion-dummy-1.1-1.1" is locked on "sle_minion" 693ms

When I follow "Software" in the content area 72ms

And I follow "Lock / Unlock" 595ms

Then package "hoag-dummy-1.1-1.1" is reported as locked 37ms

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 64ms

And I click on the filter button 617ms

And package "milkyway-dummy-2.0-1.1" is reported as unlocked 10s 19ms

Scenario:
Mix package locks and unlock events part 2
45s 353ms 18

Given I am on the Systems overview page of this "sle_minion" 974ms

And I follow "Software" in the content area 76ms

And I follow "Lock / Unlock" 538ms

When I click on "Select All" 603ms

And I click on "Unlock" 839ms

Then I should see a "Packages has been requested for being unlocked." text 131ms

And only packages "hoag-dummy-1.1-1.1, orion-dummy-1.1-1.1" are reported as pending to be unlocked 37ms

When I wait until event "Lock packages scheduled" is completed 18s 779ms

Then "hoag-dummy-1.1-1.1" is unlocked on "sle_minion" 1s 39ms

And "orion-dummy-1.1-1.1" is unlocked on "sle_minion" 734ms

When I follow "Software" in the content area 71ms

And I follow "Lock / Unlock" 589ms

And I enter "hoag-dummy-1.1-1.1" as the filtered package name 68ms

And I click on the filter button 650ms

Then package "hoag-dummy-1.1-1.1" is reported as unlocked 10s 16ms

And I enter "orion-dummy-1.1-1.1" as the filtered package name 53ms

And I click on the filter button 133ms

And package "orion-dummy-1.1-1.1" is reported as unlocked 10s 14ms

Scenario:
Cleanup: remove packages after testing locks
3s 475ms 2

Then I remove package "orion-dummy" from this "sle_minion" 1s 880ms

And I remove package "milkyway-dummy" from this "sle_minion" 1s 594ms

@scope_onboarding
Feature:Empty minion profile operations 1m 25s 443ms 8

Scenario:
Log in as org admin user
1s 982ms 1

Given I am authorized 1s 982ms

Scenario:
Create an empty minion profile with HW address via API
1s 922ms 1

When I call system.create_system_profile() with name "empty-profile" and HW address "00:11:22:33:44:55" 1s 922ms

Scenario:
Create an empty minion profile with hostname via API
1s 366ms 1

When I call system.create_system_profile() with name "empty-profile-hostname" and hostname "min-retail.mgr.suse.de" 1s 366ms

Scenario:
Check the created empty minion profiles in Unprovisioned Systems page
459ms 4

And I follow the left menu "System > System List > Unprovisioned Systems" 211ms

And I wait until I see "empty-profile" text, refreshing the page 82ms

And I wait until I see "00:11:22:33:44:55" text 77ms

And I wait until I see "empty-profile-hostname" text 87ms

Scenario:
Check the empty profiles has the hostname set
861ms 3

And I follow the left menu "System > System List > Unprovisioned Systems" 72ms

And I follow "empty-profile-hostname" 719ms

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
387ms 3

When I call system.list_empty_system_profiles() 387ms

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 14s 512ms 7

When I follow the left menu "Systems > System List" 69ms

And I wait until I see the "empty-profile" system, refreshing the page 1m 11s 610ms

And I follow "empty-profile" 647ms

And I follow "Delete System" 561ms

Then I should see a "Confirm System Profile Deletion" text 64ms

When I click on "Delete Profile" 62ms

And I wait until I see "has been deleted" text 1s 496ms

Scenario:
Cleanup: Delete second empty minion profiles
3s 951ms 7

When I follow the left menu "Systems > System List" 94ms

And I wait until I see the "empty-profile-hostname" system, refreshing the page 747ms

And I follow "empty-profile-hostname" 552ms

And I follow "Delete System" 403ms

Then I should see a "Confirm System Profile Deletion" text 63ms

When I click on "Delete Profile" 55ms

And I wait until I see "has been deleted" text 2s 33ms

@scope_onboarding @custom_download_endpoint
Feature:Repos file generation based on custom pillar data 1m 40s 490ms 9 3

Scenario:
Log in as org admin user
2s 69ms 1

Given I am authorized 2s 69ms

@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 685ms 11

Warning: Radio button 'openSUSE Tumbleweed (x86_64)' is already checked

Given I am on the Systems overview page of this "sle_minion" 1s 834ms

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 66ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 242ms

And I click on "Next" 351ms

Then I should see a "Confirm Software Channel Change" text 71ms

When I click on "Confirm" 73ms

Then I should see a "Changing the channels has been scheduled." text 311ms

When I follow "scheduled" in the content area 74ms

And I wait until I see "1 system successfully completed this action." text, refreshing the page 16s 520ms

Scenario:
Check the default RPM download point values
2s 174ms 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 52ms

Then the susemanager repo file should exist on the "sle_minion" 715ms

And the repo file should contain the normal download endpoint on the "sle_minion" 407ms

Scenario:
Set the custom RPM download point
13s 176ms 5

Given I am on the Systems overview page of this "sle_minion" 1s 42ms

When I install a salt pillar top file for "pkg_endpoint" with target "*" on the server 4s 604ms

And I wait for "1" seconds 1s

And I install the package download endpoint pillar file on the server 2s 513ms

And I refresh the pillar data 4s 15ms

@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 964ms 10

Warning: Radio button 'openSUSE Tumbleweed (x86_64)' is already checked

When I follow "Software" in the content area 66ms

And I follow "Software Channels" in the content area 65ms

And I wait until I do not see "Loading..." text 71ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 180ms

And I click on "Next" 361ms

Then I should see a "Confirm Software Channel Change" text 67ms

When I click on "Confirm" 69ms

Then I should see a "Changing the channels has been scheduled." text 427ms

When I follow "scheduled" in the content area 66ms

And I wait until I see "1 system successfully completed this action." text, refreshing the page 16s 586ms

Scenario:
Check the channel.repo file to see the custom RPM download point
2s 300ms 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 195ms

Then the susemanager repo file should exist on the "sle_minion" 700ms

And the repo file should contain the custom download endpoint on the "sle_minion" 403ms

Scenario:
Cleanup: remove the custom RPM download point
10s 514ms 3

When I delete the package download endpoint pillar file from the server 3s 76ms

And I install a salt pillar top file for "disable_local_repos_off, salt_bundle_config" with target "*" on the server 3s 584ms

And I refresh the pillar data 3s 853ms

@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
31s 497ms 12

Warning: Radio button 'openSUSE Tumbleweed (x86_64)' is already checked

When I follow "Software" in the content area 63ms

And I follow "Software Channels" in the content area 60ms

And I wait until I do not see "Loading..." text 71ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 420ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 396ms

And I check "Fake-RPM-SUSE-Channel" 37ms

And I click on "Next" 60ms

Then I should see a "Confirm Software Channel Change" text 63ms

When I click on "Confirm" 77ms

Then I should see a "Changing the channels has been scheduled." text 423ms

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 747ms

Scenario:
Cleanup: recheck the default RPM download point values
1s 107ms 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" 708ms

And the repo file should contain the normal download endpoint on the "sle_minion" 399ms

@skip_if_github_validation @sle_minion @scope_action_chains @flaky
Feature:Action chains on Salt minions 8m 49s 949ms 33

* Related GitHub Card: https://github.com/SUSE/spacewalk/issues/28793

Scenario:
Log in as admin user
1s 687ms 1

Given I am authorized for the "Admin" section 1s 687ms

Scenario:
Pre-requisite: downgrade repositories to lower version on Salt minion
6s 693ms 6

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 733ms

And I remove package "andromeda-dummy" from this "sle_minion" without error control 798ms

And I remove package "virgo-dummy" from this "sle_minion" without error control 814ms

And I install package "milkyway-dummy" on this "sle_minion" without error control 1s 701ms

And I install old package "andromeda-dummy-1.0" on this "sle_minion" 1s 700ms

And I refresh the metadata for "sle_minion" 944ms

Scenario:
Pre-requisite: refresh package list and check installed packages after downgrade on SLE minion
26s 766ms 3

When I refresh packages list via spacecmd on "sle_minion" 7s 140ms

And I wait until refresh package list on "sle_minion" is finished 12s 297ms

Then spacecmd should show packages "milkyway-dummy andromeda-dummy-1.0" installed on "sle_minion" 7s 329ms

Scenario:
Pre-requisite: wait until downgrade is finished on SLE minion
1s 641ms 5

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" in the content area 67ms

And I enter "andromeda-dummy" as the filtered package name 190ms

And I click on the filter button until page does contain "andromeda-dummy-1.0" text 284ms

Scenario:
Pre-requisite: ensure the errata cache is computed before testing on Salt minion
6s 615ms 6

When I follow the left menu "Admin > Task Schedules" 156ms

And I follow "errata-cache-default" 1s 233ms

And I follow "errata-cache-bunch" 1s 304ms

And I click on "Single Run Schedule" 1s 251ms

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 400ms

Scenario:
Create a custom action chain for the Salt minion
583ms 3

When I create an action chain with label "salt_minion_action_chain" via API 373ms

And I follow the left menu "Schedule > Action Chains" 139ms

Then I should see a "salt_minion_action_chain" text 70ms

Scenario:
Add a patch installation to the action chain on Salt minion
22s 753ms 10

Given I am on the Systems overview page of this "sle_minion" 944ms

When I follow "Software" in the content area 68ms

And I follow "Patches" in the content area 65ms

And I enter "andromeda" as the filtered synopsis 47ms

And I click on the filter button 10s 114ms

And I check "andromeda-dummy-6789" in the list 68ms

And I click on "Apply Patches" 623ms

And I check radio button "schedule-by-action-chain" 10s 53ms

And I click on "Confirm" 684ms

Then I should see a "Action has been successfully added to the Action Chain" text 82ms

Scenario:
Add a package removal to the action chain on Salt minion
13s 540ms 10

Given I am on the Systems overview page of this "sle_minion" 956ms

When I follow "Software" in the content area 80ms

And I follow "List / Remove" in the content area 72ms

And I enter "milkyway-dummy" as the filtered package name 192ms

And I click on the filter button 825ms

And I check row with "milkyway-dummy" and arch of "sle_minion" 60ms

And I click on "Remove Packages" 617ms

And I check radio button "schedule-by-action-chain" 10s 75ms

And I click on "Confirm" 594ms

Then I should see a "Action has been successfully added to the Action Chain" text 65ms

Scenario:
Add a package installation to an action chain on Salt minion
12s 277ms 9

When I follow "Software" in the content area 67ms

And I follow "Install New Packages" in the content area 67ms

And I enter "virgo-dummy" as the filtered package name 128ms

And I click on the filter button 717ms

And I check "virgo-dummy" in the list 54ms

And I click on "Install Packages" 512ms

And I check radio button "schedule-by-action-chain" 10s 74ms

And I click on "Confirm" 589ms

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
1s 286ms 7

When I follow the left menu "Configuration > Channels" 127ms

And I follow "Create Config Channel" 290ms

And I enter "Action Chain Channel" as "cofName" 71ms

And I enter "actionchainchannel" as "cofLabel" 67ms

And I enter "This is a test channel" as "cofDescription" 70ms

And I click on "Create Config Channel" 596ms

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
1s 224ms 8

When I follow the left menu "Configuration > Channels" 66ms

And I follow "Action Chain Channel" 376ms

And I follow "Create Configuration File or Directory" 389ms

And I enter "/etc/action-chain.cnf" as "cffPath" 70ms

And I enter "Testchain=YES_PLEASE" in the editor 8ms

And I click on "Create Configuration File" 66ms

Then I should see a "Revision 1 of /etc/action-chain.cnf from channel Action Chain Channel" text 226ms

And I should see a "Update Configuration File" button 21ms

Scenario:
Download the configuration file from configuration channel
2s 99ms 7

When I follow the left menu "Configuration > Channels" 65ms

And I follow "Action Chain Channel" 451ms

And I follow "List/Remove Files" 370ms

And I follow "/etc/action-chain.cnf" 529ms

And I follow "Download File" 166ms

And I wait until file "/tmp/downloads/action-chain.cnf" exists on "localhost" 177ms

Then file "/tmp/downloads/action-chain.cnf" should contain "Testchain=YES_PLEASE" on "localhost" 339ms

Scenario:
Subscribe system to configuration channel for testing action chain on Salt minion
2s 576ms 8

Given I am on the Systems overview page of this "sle_minion" 908ms

When I follow "Configuration" in the content area 74ms

And I follow "Manage Configuration Channels" in the content area 65ms

And I follow first "Subscribe to Channels" in the content area 65ms

And I check "Action Chain Channel" in the list 57ms

And I click on "Continue" 59ms

And I click on "Update Channel Rankings" 1s 267ms

Then I should see a "Channel Subscriptions successfully changed for" text 76ms

Scenario:
Add a configuration file deployment to the action chain on Salt minion
12s 977ms 9

When I follow the left menu "Configuration > Channels" 109ms

And I follow "Action Chain Channel" 492ms

And I follow "Deploy Files" in the content area 81ms

And I click on "Deploy All Files" 674ms

And I check the "sle_minion" client 58ms

And I click on "Confirm & Deploy to Selected Systems" 803ms

And I check radio button "schedule-by-action-chain" 10s 68ms

And I click on "Deploy Files to Selected Systems" 615ms

Then I should see a "Action has been successfully added to the Action Chain" text 74ms

Scenario:
Add apply highstate to action chain on Salt minion
11s 157ms 4

Given I am on the Systems overview page of this "sle_minion" 945ms

When I follow "States" in the content area 76ms

And I check radio button "schedule-by-action-chain" 10s 74ms

And I click on "Apply Highstate" 60ms

Scenario:
Add a reboot action to the action chain on Salt minion
12s 363ms 5

Given I am on the Systems overview page of this "sle_minion" 975ms

When I follow first "Schedule System Reboot" 496ms

And I check radio button "schedule-by-action-chain" 10s 58ms

And I click on "Reboot system" 742ms

Then I should see a "Action has been successfully added to the Action Chain" text 91ms

Scenario:
Add a remote command to the action chain on Salt minion
10s 845ms 6

When I follow "Details" in the content area 74ms

And 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 70ms

And I check radio button "schedule-by-action-chain" 10s 68ms

And I click on "Schedule" 57ms

Then I should see a "Action has been successfully added to the Action Chain" text 506ms

Scenario:
Verify the action chain list on Salt minion
1s 808ms 10

When I follow "Schedule" 358ms

And I follow "Action Chains" 303ms

And I follow "salt_minion_action_chain" 539ms

Then I should see a "1. Apply patch(es) andromeda-dummy-6789 on 1 system" text 110ms

And I should see a "2. Remove milkyway-dummy from 1 system" text 80ms

And I should see a "3. Install or update virgo-dummy on 1 system" text 85ms

And I should see a text like "4. Deploy.*/etc/action-chain.cnf.*to 1 system" 80ms

And I should see a "5. Apply Highstate" text 86ms

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 84ms

Scenario:
Check that a different user cannot see the action chain for Salt minion
2s 906ms 4

Given I am authorized as "testing" with password "testing" 1s 640ms

When I follow "Schedule" 995ms

And I follow "Action Chains" 262ms

Then I should not see a "salt_minion_action_chain" link 7ms

Scenario:
Execute the action chain from the web UI on Salt minion
4m 26s 603ms 9

Given I am authorized for the "Admin" section 1s 844ms

When I am on the Systems overview page of this "sle_minion" 1s 611ms

And I follow "Schedule" 262ms

And I follow "Action Chains" 284ms

And I follow "salt_minion_action_chain" 450ms

And I click on "Save and Schedule" 60ms

Then I should see a "Action Chain salt_minion_action_chain has been scheduled for execution." text 967ms

When I wait for "virgo-dummy" to be installed on "sle_minion" 24s 135ms

And I wait at most 300 seconds until file "/tmp/action_chain_one_system_done" exists on "sle_minion" 3m 56s 986ms

Scenario:
Create a custom action chain for the Salt minion
597ms 3

When I create an action chain with label "salt_minion_action_chain_to_delete" via API 459ms

And I follow the left menu "Schedule > Action Chains" 75ms

Then I should see a "salt_minion_action_chain_to_delete" text 61ms

Scenario:
Add a remote command to the action chain on Salt minion
12s 171ms 6

Given I am on the Systems overview page of this "sle_minion" 986ms

When I follow "Remote Command" 506ms

And I enter as remote command this script in #!/bin/bash uptime 56ms

And I check radio button "schedule-by-action-chain" 10s 68ms

And I click on "Schedule" 472ms

Then I should see a "Action has been successfully added to the Action Chain" text 81ms

Scenario:
Delete the action chain for Salt minion
1s 275ms 5

When I follow "Schedule" 250ms

And I follow "Action Chains" 284ms

And I follow "salt_minion_action_chain_to_delete" 260ms

And I follow "Delete Action Chains" in the content area 79ms

And I click on "Delete" 400ms

Scenario:
Downgrade again repositories to lower version on Salt minion
7s 245ms 4

When I remove package "andromeda-dummy" from this "sle_minion" without error control 2s 352ms

And I remove package "virgo-dummy" from this "sle_minion" without error control 1s 523ms

And I install package "milkyway-dummy" on this "sle_minion" without error control 1s 713ms

And I install old package "andromeda-dummy-1.0" on this "sle_minion" 1s 655ms

Scenario:
Refresh package list and check installed packages after second downgrade on SLE minion
26s 94ms 3

When I refresh packages list via spacecmd on "sle_minion" 8s 308ms

And I wait until refresh package list on "sle_minion" is finished 10s 776ms

Then spacecmd should show packages "milkyway-dummy andromeda-dummy-1.0" installed on "sle_minion" 7s 9ms

Scenario:
Ensure again the errata cache is computed before testing on Salt minion
38s 869ms 6

When I follow the left menu "Admin > Task Schedules" 128ms

And I follow "errata-cache-default" 389ms

And I follow "errata-cache-bunch" 1s 243ms

And I click on "Single Run Schedule" 1s 299ms

Then I should see a "bunch was scheduled" text 289ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 35s 519ms

Scenario:
Add operations to the action chain via API for Salt minions
7s 415ms 11

Running actions:
- System reboot
- Run an arbitrary script
- Package Install/Upgrade
- Package Install/Upgrade
- Package Removal
- Removed "System reboot" action
- Removed "Run an arbitrary script" action
- Removed "Package Install/Upgrade" action
- Removed "Package Install/Upgrade" action
- Removed "Package Removal" action

Given I want to operate on this "sle_minion" 659ms

When I create an action chain with label "salt_minion_api_chain" via API 415ms

And I add a package install to the action chain via API 904ms

And I add a package removal to the action chain via API 780ms

And I add a package upgrade to the action chain via API 838ms

And I add the script "exit 1;" to the action chain via API 370ms

And I add a system reboot to the action chain via API 360ms

Then I should be able to see all these actions in the action chain via API 332ms

When I remove each action within the chain via API 2s 86ms

Then the current action chain should be empty 335ms

And I delete the action chain via API 330ms

Scenario:
Run an action chain via API on Salt minion
8s 325ms 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" 331ms

When I create an action chain with label "salt_minion_multiple_scripts" via API 356ms

And I add the script "echo -n 1 >> /tmp/action_chain.log" to the action chain via API 381ms

And I add the script "echo -n 2 >> /tmp/action_chain.log" to the action chain via API 362ms

And I add the script "echo -n 3 >> /tmp/action_chain.log" to the action chain via API 376ms

And I add the script "touch /tmp/action_chain_done" to the action chain via API 369ms

Then I should be able to see all these actions in the action chain via API 342ms

When I schedule the action chain via API 438ms

And I wait until there are no more action chains listed via API 362ms

And I wait until file "/tmp/action_chain_done" exists on "sle_minion" 3s 813ms

Then file "/tmp/action_chain.log" should contain "123" on "sle_minion" 814ms

When I wait until there are no more scheduled actions listed via API 376ms

Scenario:
Cleanup: remove Salt minion from configuration channel
1s 403ms 6

When I follow the left menu "Configuration > Channels" 155ms

And I follow "Action Chain Channel" 443ms

And I follow "Systems" in the content area 69ms

And I check the "sle_minion" client 63ms

And I click on "Unsubscribe systems" 601ms

Then I should see a "Successfully unsubscribed 1 system(s)." text 68ms

Scenario:
Cleanup: remove configuration channel for Salt minion
1s 212ms 4

When I follow the left menu "Configuration > Channels" 62ms

And I follow "Action Chain Channel" 359ms

And I follow "Delete Channel" 333ms

And I click on "Delete Config Channel" 457ms

Scenario:
Cleanup: remove packages and repository used in action chain for Salt minion
4s 362ms 4

When I remove package "andromeda-dummy" from this "sle_minion" without error control 1s 521ms

And I remove package "virgo-dummy" from this "sle_minion" without error control 803ms

And I remove package "milkyway-dummy" from this "sle_minion" without error control 1s 518ms

And I disable repository "test_repo_rpm_pool" on this "sle_minion" without error control 519ms

Scenario:
Cleanup: remove temporary files for testing action chains on Salt minion
2s 397ms 4

When I run "rm -f /tmp/action_chain.log" on "sle_minion" without error control 475ms

And I run "rm -f /tmp/action_chain_done" on "sle_minion" without error control 620ms

And I run "rm -f /etc/action-chain.cnf" on "sle_minion" without error control 678ms

And I run "rm -f /tmp/action_chain_one_system_done" on "sle_minion" without error control 622ms

Scenario:
Cleanup: remove downloaded files
170ms 1

When I run "rm -f /tmp/downloads/action-chain.cnf" on "localhost" without error control 170ms

@skip_if_github_validation @ssh_minion @scope_action_chains @scope_salt_ssh
Feature:Salt SSH action chain 10m 53s 845ms 30

Scenario:
Log in as org admin user
451ms 1

Given I am authorized for the "Admin" section 451ms

Scenario:
Pre-requisite: downgrade repositories to lower version on SSH minion
6s 408ms 6

When I enable repository "test_repo_rpm_pool" on this "ssh_minion" 731ms

And I remove package "andromeda-dummy" from this "ssh_minion" without error control 1s 250ms

And I remove package "virgo-dummy" from this "ssh_minion" without error control 1s 237ms

And I install package "milkyway-dummy" on this "ssh_minion" without error control 1s 108ms

And I install old package "andromeda-dummy-1.0" on this "ssh_minion" 1s 311ms

And I refresh the metadata for "ssh_minion" 768ms

Scenario:
Pre-requisite: refresh package list and check newly installed packages on SSH minion
37s 665ms 3

When I refresh packages list via spacecmd on "ssh_minion" 8s 28ms

And I wait until refresh package list on "ssh_minion" is finished 21s 371ms

Then spacecmd should show packages "milkyway-dummy andromeda-dummy-1.0" installed on "ssh_minion" 8s 264ms

Scenario:
Pre-requisite: wait until downgrade is finished on SSH minion
1s 624ms 5

Given I am on the Systems overview page of this "ssh_minion" 956ms

When I follow "Software" in the content area 73ms

And I follow "List / Remove" in the content area 68ms

And I enter "andromeda-dummy" as the filtered package name 236ms

And I click on the filter button until page does contain "andromeda-dummy-1.0" text 288ms

Scenario:
Pre-requisite: ensure the errata cache is computed before testing on SSH minion
36s 267ms 6

When I follow the left menu "Admin > Task Schedules" 150ms

And I follow "errata-cache-default" 1s 234ms

And I follow "errata-cache-bunch" 1s 318ms

And I click on "Single Run Schedule" 1s 281ms

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 32s 15ms

Scenario:
Create a custom action chain for the SSH minion
641ms 3

When I create an action chain with label "minssh_action_chain" via API 400ms

And I follow the left menu "Schedule > Action Chains" 175ms

Then I wait until I see "minssh_action_chain" text 65ms

Scenario:
Add a patch installation to the action chain on SSH minion
22s 920ms 10

Given I am on the Systems overview page of this "ssh_minion" 1s 159ms

When I follow "Software" in the content area 77ms

And I follow "Patches" in the content area 89ms

And I enter "andromeda" as the filtered synopsis 49ms

And I click on the filter button 10s 99ms

And I check "andromeda-dummy-6789" in the list 62ms

And I click on "Apply Patches" 630ms

And I check radio button "schedule-by-action-chain" 10s 73ms

And I click on "Confirm" 602ms

Then I should see a "Action has been successfully added to the Action Chain" text 76ms

Scenario:
Add a package removal to the action chain on SSH minion
12s 612ms 9

When I follow "Software" in the content area 73ms

And I follow "List / Remove" in the content area 66ms

And I enter "milkyway-dummy" as the filtered package name 207ms

And I click on the filter button 859ms

And I check row with "milkyway-dummy" and arch of "ssh_minion" 60ms

And I click on "Remove Packages" 592ms

And I check radio button "schedule-by-action-chain" 10s 82ms

And I click on "Confirm" 605ms

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 SSH minion
12s 223ms 9

When I follow "Software" in the content area 70ms

And I follow "Install New Packages" in the content area 64ms

And I enter "virgo-dummy" as the filtered package name 104ms

And I click on the filter button 622ms

And I check "virgo-dummy" in the list 54ms

And I click on "Install Packages" 588ms

And I check radio button "schedule-by-action-chain" 10s 61ms

And I click on "Confirm" 594ms

Then I should see a "Action has been successfully added to the Action Chain" text 63ms

Scenario:
Create a configuration channel for testing action chain on SSH minion
1s 291ms 7

When I follow the left menu "Configuration > Channels" 122ms

And I follow "Create Config Channel" 289ms

And I enter "Action Chain Channel" as "cofName" 71ms

And I enter "actionchainchannel" as "cofLabel" 66ms

And I enter "This is a test channel" as "cofDescription" 74ms

And I click on "Create Config Channel" 602ms

Then I should see a "Action Chain Channel" text 64ms

Scenario:
Add a configuration file to configuration channel for testing action chain on SSH minion
1s 542ms 8

When I follow the left menu "Configuration > Channels" 66ms

And I follow "Action Chain Channel" 358ms

And I follow "Create Configuration File or Directory" 346ms

And I enter "/etc/action-chain.cnf" as "cffPath" 71ms

And I enter "Testchain=YES_PLEASE" in the editor 4ms

And I click on "Create Configuration File" 573ms

Then I should see a "Revision 1 of /etc/action-chain.cnf from channel Action Chain Channel" text 102ms

And I should see a "Update Configuration File" button 19ms

Scenario:
Subscribe system to configuration channel for testing action chain on SSH minion
3s 56ms 8

Given I am on the Systems overview page of this "ssh_minion" 1s 52ms

When I follow "Configuration" in the content area 72ms

And I follow "Manage Configuration Channels" in the content area 65ms

And I follow first "Subscribe to Channels" in the content area 70ms

And I check "Action Chain Channel" in the list 58ms

And I click on "Continue" 60ms

And I click on "Update Channel Rankings" 1s 596ms

Then I should see a "Channel Subscriptions successfully changed for" text 80ms

Scenario:
Add a configuration file deployment to the action chain on SSH minion
13s 244ms 9

When I follow the left menu "Configuration > Channels" 105ms

And I follow "Action Chain Channel" 436ms

And I follow "Deploy Files" in the content area 66ms

And I click on "Deploy All Files" 617ms

And I check the "ssh_minion" client 60ms

And I click on "Confirm & Deploy to Selected Systems" 1s 37ms

And I check radio button "schedule-by-action-chain" 10s 60ms

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 77ms

Scenario:
Add apply highstate to action chain on SSH minion
11s 164ms 4

Given I am on the Systems overview page of this "ssh_minion" 963ms

When I follow "States" in the content area 70ms

And I check radio button "schedule-by-action-chain" 10s 69ms

And I click on "Apply Highstate" 60ms

Scenario:
Add a reboot action to the action chain on SSH minion
12s 592ms 5

Given I am on the Systems overview page of this "ssh_minion" 1s 129ms

When I follow first "Schedule System Reboot" 489ms

And I check radio button "schedule-by-action-chain" 10s 57ms

And I click on "Reboot system" 827ms

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 SSH minion
10s 870ms 6

When I follow "Details" in the content area 77ms

When I follow "Remote Command" in the content area 66ms

And I enter as remote command this script in #!/bin/bash touch /tmp/action_chain_one_system_done 68ms

And I check radio button "schedule-by-action-chain" 10s 59ms

And I click on "Schedule" 520ms

Then I should see a "Action has been successfully added to the Action Chain" text 78ms

Scenario:
Verify the action chain list on SSH minion
1s 32ms 9

When I follow the left menu "Schedule > Action Chains" 127ms

And I follow "minssh_action_chain" 312ms

Then I should see a "1. Apply patch(es) andromeda-dummy-6789 on 1 system" text 84ms

And I should see a "2. Remove milkyway-dummy from 1 system" text 96ms

And I should see a "3. Install or update virgo-dummy on 1 system" text 83ms

And I should see a text like "4. Deploy.*/etc/action-chain.cnf.*to 1 system" 81ms

And I should see a "5. Apply Highstate" text 80ms

And I should see a "6. Reboot 1 system" text 84ms

And I should see a "7. Run a remote command on 1 system" text 78ms

Scenario:
Check that a different user cannot see the action chain for SSH minion
2s 70ms 3

Given I am authorized as "testing" with password "testing" 1s 950ms

When I follow the left menu "Schedule > Action Chains" 109ms

Then I should not see a "minssh_action_chain" link 10ms

Scenario:
Execute the action chain from the web UI on SSH minion
3s 50ms 6

Given I am authorized for the "Admin" section 1s 749ms

When I follow the left menu "Schedule > Action Chains" 102ms

And I wait until I see "minssh_action_chain" text 97ms

And I follow "minssh_action_chain" 309ms

Then I click on "Save and Schedule" 57ms

And I should see a "Action Chain minssh_action_chain has been scheduled for execution." text 732ms

Scenario:
Verify that the action chain was executed successfully
5m 21s 794ms 2

When I wait for "virgo-dummy" to be installed on "ssh_minion" 48s 481ms

And I wait at most 300 seconds until file "/tmp/action_chain_one_system_done" exists on "ssh_minion" 4m 33s 312ms

Scenario:
Create a custom action chain for the SSH minion
649ms 3

When I create an action chain with label "minssh_action_chain_to_delete" via API 515ms

And I follow the left menu "Schedule > Action Chains" 66ms

Then I should see a "minssh_action_chain_to_delete" text 68ms

Scenario:
Add a remote command to the action chain on SSH minion
11s 964ms 6

Given I am on the Systems overview page of this "ssh_minion" 1s 91ms

When I follow "Remote Command" 497ms

And I enter as remote command this script in #!/bin/bash uptime 54ms

And I check radio button "schedule-by-action-chain" 10s 69ms

And I click on "Schedule" 56ms

Then I should see a "Action has been successfully added to the Action Chain" text 194ms

Scenario:
Delete the action chain for SSH minion
925ms 4

When I follow the left menu "Schedule > Action Chains" 129ms

And I follow "minssh_action_chain_to_delete" 299ms

And I follow "Delete Action Chains" in the content area 74ms

Then I click on "Delete" 422ms

Scenario:
Cleanup: roll back action chain effects on SSH minion
1m 22s 899ms 21

Given I am on the Systems overview page of this "ssh_minion" 1s 109ms

When I run "rm /tmp/action_chain_done" on "ssh_minion" without error control 393ms

And I enable repository "test_repo_rpm_pool" on this "ssh_minion" 491ms

And I remove package "andromeda-dummy" from this "ssh_minion" without error control 1s 740ms

And I remove package "virgo-dummy" from this "ssh_minion" without error control 1s 251ms

And I install package "milkyway-dummy" on this "ssh_minion" without error control 1s 469ms

And I install old package "andromeda-dummy-1.0" on this "ssh_minion" 1s 299ms

And I follow "Software" in the content area 69ms

And I click on "Update Package List" 644ms

And I follow "Events" in the content area 68ms

And I wait until I do not see "Package List Refresh scheduled" text, refreshing the page 24s 155ms

And I follow "Software" in the content area 79ms

And I follow "List / Remove" in the content area 65ms

And I enter "andromeda-dummy" as the filtered package name 249ms

And I click on the filter button until page does contain "andromeda-dummy-1.0" text 283ms

When I follow the left menu "Admin > Task Schedules" 159ms

And I follow "errata-cache-default" 1s 239ms

And I follow "errata-cache-bunch" 1s 289ms

And I click on "Single Run Schedule" 1s 576ms

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 44s 983ms

Scenario:
Add operations to the action chain via API for SSH minions
6s 995ms 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" 367ms

When I create an action chain with label "minssh_api_chain" via API 342ms

And I add a package install to the action chain via API 797ms

And I add a package removal to the action chain via API 811ms

And I add a package upgrade to the action chain via API 1s 58ms

And I add the script "exit 1;" to the action chain via API 589ms

Then I should be able to see all these actions in the action chain via API 469ms

When I remove each action within the chain via API 1s 833ms

Then the current action chain should be empty 379ms

And I delete the action chain via API 345ms

Scenario:
Run an action chain via API on SSH minion
30s 137ms 12

Running actions:
- Run an arbitrary script
- Run an arbitrary script
- Run an arbitrary script
- Run an arbitrary script

And I want to operate on this "ssh_minion" 337ms

When I create an action chain with label "minssh_multiple_scripts" via API 353ms

And I add the script "echo -n 1 >> /tmp/action_chain.log" to the action chain via API 358ms

And I add the script "echo -n 2 >> /tmp/action_chain.log" to the action chain via API 369ms

And I add the script "echo -n 3 >> /tmp/action_chain.log" to the action chain via API 350ms

And I add the script "touch /tmp/action_chain_done" to the action chain via API 370ms

Then I should be able to see all these actions in the action chain via API 351ms

When I schedule the action chain via API 601ms

Then I wait until there are no more action chains listed via API 751ms

When I wait until file "/tmp/action_chain_done" exists on "ssh_minion" 25s 74ms

Then file "/tmp/action_chain.log" should contain "123" on "ssh_minion" 783ms

When I wait until there are no more scheduled actions listed via API 435ms

Scenario:
Cleanup: remove SSH minion from configuration channel
1s 421ms 6

When I follow the left menu "Configuration > Channels" 148ms

And I follow "Action Chain Channel" 535ms

And I follow "Systems" in the content area 67ms

And I check the "ssh_minion" client 75ms

And I click on "Unsubscribe systems" 530ms

Then I should see a "Successfully unsubscribed 1 system(s)." text 63ms

Scenario:
Cleanup: remove configuration channel for SSH minion
1s 61ms 4

When I follow the left menu "Configuration > Channels" 60ms

And I follow "Action Chain Channel" 359ms

And I follow "Delete Channel" 296ms

And I click on "Delete Config Channel" 345ms

Scenario:
Cleanup: remove packages and repository used in action chain for SSH minion
3s 704ms 4

When I remove package "andromeda-dummy" from this "ssh_minion" without error control 1s 260ms

And I remove package "virgo-dummy" from this "ssh_minion" without error control 784ms

And I remove package "milkyway-dummy" from this "ssh_minion" without error control 1s 230ms

And I disable repository "test_repo_rpm_pool" on this "ssh_minion" without error control 428ms

Scenario:
Cleanup: remove temporary files for testing action chains on SSH minion
1s 561ms 4

When I run "rm -f /tmp/action_chain.log" on "ssh_minion" without error control 389ms

And I run "rm -f /tmp/action_chain_done" on "ssh_minion" without error control 387ms

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 391ms

@skip_if_github_validation @ssh_minion @sle_minion @scope_action_chains
Feature:Action chains on several systems at once 3m 19s 277ms 12

Scenario:
Log in as admin user
441ms 1

Given I am authorized for the "Admin" section 441ms

Scenario:
Pre-requisite: downgrade packages before action chain test on several systems
7s 862ms 8

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 743ms

And I enable repository "test_repo_rpm_pool" on this "ssh_minion" 727ms

And I remove package "andromeda-dummy" from this "ssh_minion" without error control 786ms

And I remove package "andromeda-dummy" from this "sle_minion" without error control 803ms

And I install package "andromeda-dummy-1.0" on this "sle_minion" 1s 928ms

And I install package "andromeda-dummy-1.0" on this "ssh_minion" 1s 320ms

And I refresh the metadata for "sle_minion" 799ms

And I refresh the metadata for "ssh_minion" 752ms

Scenario:
Pre-requisite: refresh package list and check installed packages before action chain test on several systems
1m 5s 506ms 6

When I refresh packages list via spacecmd on "sle_minion" 6s 576ms

And I wait until refresh package list on "sle_minion" is finished 12s 434ms

Then spacecmd should show packages "andromeda-dummy-1.0" installed on "sle_minion" 6s 383ms

When I refresh packages list via spacecmd on "ssh_minion" 7s 759ms

And I wait until refresh package list on "ssh_minion" is finished 23s 985ms

Then spacecmd should show packages "andromeda-dummy-1.0" installed on "ssh_minion" 8s 367ms

Scenario:
Pre-requisite: wait until downgrade is finished before action chain test on several systems
1s 603ms 5

Given I am on the Systems overview page of this "sle_minion" 924ms

When I follow "Software" in the content area 68ms

And I follow "List / Remove" in the content area 66ms

And I enter "andromeda-dummy" as the filtered package name 256ms

And I click on the filter button until page does contain "andromeda-dummy-1.0" text 286ms

Scenario:
Pre-requisite: ensure the errata cache is computed before action chain test on several systems
53s 773ms 13

When I follow the left menu "Admin > Task Schedules" 144ms

And I follow "errata-cache-default" 1s 226ms

And I follow "errata-cache-bunch" 1s 325ms

And I click on "Single Run Schedule" 1s 231ms

Then I should see a "bunch was scheduled" text 283ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 42s 27ms

Given I am on the Systems overview page of this "ssh_minion" 953ms

When I follow the left menu "Admin > Task Schedules" 132ms

And I follow "errata-cache-default" 1s 334ms

And I follow "errata-cache-bunch" 1s 225ms

And I click on "Single Run Schedule" 1s 540ms

Then I should see a "bunch was scheduled" text 274ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 2s 73ms

Scenario:
Create a custom action chain for two systems
545ms 3

When I create an action chain with label "two_systems_action_chain" via API 341ms

And I follow the left menu "Schedule > Action Chains" 136ms

Then I should see a "two_systems_action_chain" text 67ms

Scenario:
Add an action chain using system set manager for SSH minion and SLE minion
24s 585ms 22

When I follow the left menu "Systems > System List > All" 186ms

And I check the "sle_minion" client 526ms

And I check the "ssh_minion" client 61ms

And I follow the left menu "Systems > System Set Manager > Overview" 582ms

And I follow "Install" in the content area 69ms

And I follow "Fake-RPM-SUSE-Channel" in the content area 67ms

And I enter "andromeda-dummy" as the filtered package name 60ms

And I click on the filter button 420ms

And I check "andromeda-dummy" in the list 56ms

And I click on "Install Packages" 351ms

Then I should see "sle_minion" hostname 76ms

And I should see "ssh_minion" hostname 79ms

When I check radio button "schedule-by-action-chain" 10s 54ms

And I click on "Confirm" 577ms

Then I should see a "Package installations are being scheduled" text 62ms

When I follow the left menu "Systems > System Set Manager > Overview" 69ms

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 71ms

And I check radio button "schedule-by-action-chain" 10s 52ms

And I click on "Schedule" 57ms

Then I should see "sle_minion" hostname 938ms

And I should see "ssh_minion" hostname 91ms

Scenario:
Verify action chain for two systems
2s 821ms 8

Given I am on the Systems overview page of this "sle_minion" 1s 125ms

When I follow "Schedule" 293ms

And I follow "Action Chains" 265ms

And I follow "two_systems_action_chain" 316ms

And I should see a "1. Install or update andromeda-dummy on 2 systems" text 67ms

And I should see a "2. Run a remote command on 2 systems" text 67ms

And I click on "Save and Schedule" 57ms

Then I should see a "Action Chain two_systems_action_chain has been scheduled for execution." text 627ms

Scenario:
Verify that the action chain from the system set manager was executed successfully
37s 265ms 4

When I wait until file "/tmp/action_chain_done" exists on "ssh_minion" 35s 753ms

And I wait until file "/tmp/action_chain_done" exists on "sle_minion" 704ms

Then "andromeda-dummy" should be installed on "ssh_minion" 401ms

And "andromeda-dummy" should be installed on "sle_minion" 406ms

Scenario:
Cleanup: remove package and repository used in action chain for several systems
3s 849ms 4

When I remove package "andromeda-dummy" from this "sle_minion" without error control 1s 479ms

And I remove package "andromeda-dummy" from this "ssh_minion" without error control 1s 438ms

And I disable repository "test_repo_rpm_pool" on this "sle_minion" without error control 434ms

And I disable repository "test_repo_rpm_pool" on this "ssh_minion" without error control 497ms

Scenario:
Cleanup: remove temporary files for testing action chains on several systems
952ms 2

When I run "rm /tmp/action_chain_done" on "sle_minion" without error control 396ms

And I run "rm /tmp/action_chain_done" on "ssh_minion" without error control 556ms

Scenario:
Cleanup: remove remaining systems from SSM after action chain tests on several systems
69ms 1

When I click on the clear SSM button 69ms

@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 10m 47s 105ms 31 1

Scenario:
Log in as admin user
549ms 1

Given I am authorized for the "Admin" section 549ms

Scenario:
Create an IP forwarding config state channel
1s 666ms 10

When I follow the left menu "Configuration > Channels" 125ms

And I follow "Create State Channel" 376ms

And I wait until I see "New Config State Channel" text 58ms

And I enter "My State Channel for Recurring Actions" as "cofName" 94ms

And I enter "statechannel-recurring" as "cofLabel" 77ms

And I enter "This is a state channel to be used in recurring actions" as "cofDescription" 96ms

And I enter "enable_ip_forwarding:\n cmd.run:\n - name: echo 1 > /proc/sys/net/ipv4/conf/all/forwarding" in the editor 4ms

And I click on "Create Config State Channel" 697ms

Then I wait until I see "Channel Properties" text 69ms

And I wait until I see "My State Channel for Recurring Actions" text 65ms

Scenario:
Enable IP forwarding through a custom state recurring action
1m 29s 804ms 21

Execution time: 20:21

When I am on the "Recurring Actions" page of this "sle_minion" 1s 51ms

Then I should see a "No schedules created. Use Create to add a schedule" text 65ms

When I click on "Create" 96ms

And I wait until I see "Action Type" text 89ms

And I enter "IP forwarding custom state recurring action" as "scheduleName" 273ms

And I select "Custom state" from "actionTypeDescription" 1s 140ms

And I wait until I see "Configure states to execute" text 103ms

And I check radio button "schedule-daily" 10s 86ms

And I enter 1 minutes from now as "time-daily_time" 103ms

And I check "statechannel-recurring-cbox" 89ms

And I click on "Save Changes" 69ms

And I wait until I see "Edit State Ranks" text 95ms

And I click on "Confirm" 74ms

And I click on "Create Schedule" 61ms

Then I wait until I see "Schedule successfully created" text 430ms

And I should see a "IP forwarding custom state recurring action" text 184ms

And I should see a "Minion" text 67ms

When I follow "Events" 412ms

And I follow "History" 484ms

Then I wait at most 420 seconds until event "Apply recurring states [manager_org_1.statechannel-recurring] schedule" is completed 1m 13s 733ms

And file "/proc/sys/net/ipv4/conf/all/forwarding" should contain "1" on "sle_minion" 1s 90ms

Scenario:
Edit the IP forwarding custom state recurring action
1m 2s 19

Execution time: 20:22

When I am on the "Recurring Actions" page of this "sle_minion" 1s 34ms

Then I should see a "IP forwarding custom state recurring action" text 277ms

When I click the "IP forwarding custom state recurring action" item edit button 66ms

And I wait until I see "Update Schedule" text 317ms

And I enter "custom_state_schedule_name_changed" as "scheduleName" 563ms

And I enter 1 minutes from now as "time-daily_time" 101ms

And I uncheck "statechannel-recurring-cbox" 10s 98ms

And I check "Sync States-cbox" 84ms

And I click on "Save Changes" 67ms

And I wait until I see "Edit State Ranks" text 95ms

And I click on "Confirm" 81ms

And I click on "Update Schedule" 64ms

Then I wait until I see "Schedule successfully updated" text 784ms

And I should see a "custom_state_schedule_name_changed" text 168ms

And I should see a "Minion" text 72ms

When I follow "Events" 416ms

And I follow "History" 487ms

Then I wait at most 420 seconds until event "Apply recurring states [util.syncstates] scheduled" is completed 47s 143ms

And I wait until I see "SLS: util.syncstates" text 74ms

@skip_if_github_validation
Scenario:
Cleanup: Disable IP forwarding
14s 942ms 9

When I follow the left menu "Salt > Remote Commands" 124ms

Then I should see a "Remote Commands" text in the content area 33ms

When I enter command "echo 0 > /proc/sys/net/ipv4/conf/all/forwarding" 136ms

And I enter target "sle_minion" 103ms

And I click on preview 11s 558ms

And I click on run 48ms

Then I should see "sle_minion" hostname 64ms

And I wait until I see "show response" text 1s 789ms

And file "/proc/sys/net/ipv4/conf/all/forwarding" should contain "0" on "sle_minion" 1s 82ms

Scenario:
Cleanup: Delete the minion Custom state Recurring Action
1s 788ms 6

When I am on the "Recurring Actions" page of this "sle_minion" 1s 19ms

Then I should see a "custom_state_schedule_name_changed" text 264ms

When I click the "custom_state_schedule_name_changed" item delete button 78ms

And I wait until I see "Delete Recurring Action Schedule" text 74ms

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 285ms

Scenario:
Create a minion Highstate Recurring Action
48s 919ms 16

Execution time: 20:23

When I am on the "Recurring Actions" page of this "sle_minion" 1s 139ms

Then I should see a "No schedules created. Use Create to add a schedule" text 59ms

When I click on "Create" 97ms

And I wait until I see "Schedule Name" text 89ms

And I enter "Minion Highstate Recurring Action" as "scheduleName" 246ms

And I select "Highstate" from "actionTypeDescription" 1s 129ms

And I check radio button "schedule-daily" 10s 70ms

And I enter 1 minutes from now as "time-daily_time" 94ms

And I click on the "disabled" toggler 55ms

And I click on "Create Schedule" 63ms

Then I wait until I see "Schedule successfully created" text 344ms

And I should see a "Minion Highstate Recurring Action" text 163ms

And I should see a "Minion" text 66ms

When I follow "Events" 395ms

And I follow "History" 503ms

And I wait until I see the event "Apply highstate in test-mode scheduled" completed during last minute, refreshing the page 34s 399ms

Scenario:
Edit the minion Highstate Recurring Action
14s 336ms 13

When I am on the "Recurring Actions" page of this "sle_minion" 1s 13ms

Then I should see a "Minion Highstate Recurring Action" text 268ms

When I click the "Minion Highstate Recurring Action" item edit button 66ms

And I wait until I see "Update Schedule" text 309ms

And I enter "schedule_name_minion" as "scheduleName" 353ms

And I check radio button "schedule-weekly" 10s 69ms

And I select "Wednesday" from "date_weekly" 1s 134ms

And I enter "01:35" as "time-weekly_time" 102ms

And I click on "Update Schedule" 67ms

Then I wait until I see "Schedule successfully updated" text 642ms

And I should see a "schedule_name_minion" text 174ms

And I should see a "Minion" text 66ms

And I should see a "0 35 1 ? * 4" text 67ms

Scenario:
View the minion Highstate Recurring Action details
1s 663ms 6

When I am on the "Recurring Actions" page of this "sle_minion" 1s 21ms

Then I should see a "schedule_name_minion" text 170ms

When I click the "schedule_name_minion" item details button 71ms

Then I should see a "Every Wednesday at 01:35" text 267ms

When I click on "Back" 70ms

Then I should see a "Schedules" text 61ms

Scenario:
Create a System group for testing
3s 765ms 11

When I follow the left menu "Systems > System Groups" 94ms

And I follow "Create Group" 277ms

And I enter "Recurring-Action-test-group" as "name" 73ms

And I enter "This is for testing" as "description" 64ms

And I click on "Create Group" 403ms

Then I should see a "System group Recurring-Action-test-group created." text 64ms

When I am on the "Groups" page of this "sle_minion" 1s 16ms

And I follow first "Join" 453ms

And I check the first row in the list 77ms

And I click on "Join Groups" 1s 169ms

Then I wait until I see "1 system groups added" text 69ms

Scenario:
Pre-requisite: subscribe system to Fake Channel
31s 975ms 12

Given I am on the Systems overview page of this "sle_minion" 963ms

When I follow "Software" in the content area 69ms

And I follow "Software Channels" in the content area 71ms

And I wait until I do not see "Loading..." text 66ms

And I check radio button "Fake-Base-Channel-SUSE-like" 10s 65ms

And I wait until I do not see "Loading..." text 435ms

And I check "Fake-Child-Channel-SUSE-like" 78ms

And I click on "Next" 60ms

Then I should see a "Confirm Software Channel Change" text 59ms

When I click on "Confirm" 80ms

Then I should see a "Changing the channels has been scheduled." text 387ms

And I wait until event "Subscribe channels scheduled" is completed 19s 638ms

@skip_if_github_validation
Scenario:
Pre-requisite: downgrade milkyway-dummy to lower version
1m 41s 651ms 9

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 744ms

And I install old package "milkyway-dummy-1.0" on this "sle_minion" 2s 204ms

And I refresh the metadata for "sle_minion" 706ms

And I follow the left menu "Admin > Task Schedules" 122ms

And I follow "errata-cache-default" 1s 264ms

And I follow "errata-cache-bunch" 394ms

And I click on "Single Run Schedule" 1s 268ms

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 1m 34s 674ms

Scenario:
Pre-requisite: check that there are updates available
998ms 2

Given I am on the Systems overview page of this "sle_minion" 912ms

And I wait until I see "Software Updates Available" text, refreshing the page 86ms

Scenario:
Create a recurring action to apply "uptodate" state to a system group
1m 24s 637ms 24

Execution time: 20:27

When I follow the left menu "Systems > System Groups" 78ms

And I follow "Recurring-Action-test-group" 327ms

And I follow "Recurring Actions" in the content area 68ms

Then I should see a "No schedules created. Use Create to add a schedule" text 63ms

When I click on "Create" 97ms

And I wait until I see "Schedule Name" text 88ms

And I enter "Recurring action to keep Recurring-Action-test-group uptodate" as "scheduleName" 386ms

And I select "Custom state" from "actionTypeDescription" 1s 129ms

And I wait until I see "Configure states to execute" text 104ms

And I check radio button "schedule-daily" 10s 74ms

And I enter 1 minutes from now as "time-daily_time" 96ms

And I check "Update System-cbox" 91ms

And I click on "Save Changes" 68ms

And I wait until I see "Edit State Ranks" text 95ms

And I click on "Confirm" 75ms

And I click on "Create Schedule" 66ms

Then I wait until I see "Schedule successfully created" text 286ms

And I should see a "Recurring action to keep Recurring-Action-test-group uptodate" text 67ms

And I should see a "Group" text 65ms

When I am on the "Events" page of this "sle_minion" 986ms

And I follow "History" 475ms

Then I wait until I see the event "Apply recurring states [uptodate] scheduled" completed during last minute, refreshing the page 1m 8s 783ms

When I am on the Systems overview page of this "sle_minion" 968ms

Then I wait at most 500 seconds until I do not see "System is up to date" text, refreshing the page 88ms

@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 33ms 14

Given I am on the Systems overview page of this "sle_minion" 999ms

When I follow "Software" in the content area 68ms

And I disable repository "test_repo_rpm_pool" on this "sle_minion" without error control 737ms

And I follow "Software Channels" in the content area 64ms

And I wait until I do not see "Loading..." text 68ms

And I check default base channel radio button of this "sle_minion" 420ms

And I wait for child channels to appear 694ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 79ms

And I check "Fake-RPM-SUSE-Channel" 77ms

And I click on "Next" 60ms

Then I should see a "Confirm Software Channel Change" text 64ms

When I click on "Confirm" 74ms

Then I should see a "Changing the channels has been scheduled." text 298ms

And I wait until event "Subscribe channels scheduled" is completed 19s 326ms

Scenario:
Edit the group Recurring Action
14s 225ms 14

When I follow the left menu "Systems > System Groups" 70ms

And I follow "Recurring-Action-test-group" 521ms

And I follow "Recurring Actions" in the content area 64ms

Then I should see a "Recurring action to keep Recurring-Action-test-group uptodate" text 363ms

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 307ms

And I enter "schedule_name_group" as "scheduleName" 581ms

And I check radio button "schedule-hourly" 10s 80ms

And I enter "35" as "minutes" 70ms

And I click on "Update Schedule" 69ms

Then I wait until I see "Schedule successfully updated" text 1s 618ms

And I should see a "schedule_name_group" text 279ms

And I should see a "Group" text 66ms

And I should see a "0 35 * ? * *" text 66ms

Scenario:
View the group recurring actions details
1s 324ms 10

When I follow the left menu "Systems > System Groups" 74ms

And I follow "Recurring-Action-test-group" 388ms

And I follow "Recurring Actions" in the content area 68ms

Then I should see a "schedule_name" text 264ms

When I click the "schedule_name" item details button 63ms

Then I should see a "Every hour at minute 35" text 260ms

And I should see a "Recurring-Action-test-group" link 12ms

And I should see a "Update System" text 67ms

When I click on "Back" 66ms

Then I should see a "Schedules" text 59ms

Scenario:
Create a yourorg Recurring Action
1m 11s 594ms 21

Execution time: 20:29

When I follow the left menu "Home > My Organization > Recurring Actions" 188ms

Then I should see a "No schedules created. Use Create to add a schedule" text 57ms

When I click on "Create" 83ms

And I wait until I see "Schedule Name" text 89ms

And I enter "schedule_name" as "scheduleName" 113ms

And I select "Custom state" from "actionTypeDescription" 1s 122ms

And I wait until I see "Configure states to execute" text 97ms

And I check radio button "schedule-daily" 10s 92ms

And I enter 1 minutes from now as "time-daily_time" 98ms

And I click on the "disabled" toggler 55ms

And I check "Package Profile Update-cbox" 86ms

And I click on "Save Changes" 69ms

And I wait until I see "Edit State Ranks" text 91ms

And I click on "Confirm" 76ms

And I click on "Create Schedule" 65ms

Then I wait until I see "Schedule successfully created" text 274ms

And I should see a "schedule_name" text 63ms

And I should see a "Organization" text 67ms

When I am on the "Events" page of this "sle_minion" 1s 18ms

And I follow "History" 408ms

Then I wait until I see the event "Apply recurring states [packages.profileupdate] scheduled" completed during last minute, refreshing the page 57s 376ms

Scenario:
Edit the yourorg Recurring Action
14s 505ms 13

When I follow the left menu "Home > My Organization > Recurring Actions" 207ms

Then I should see a "schedule_name" text 435ms

When I click the "schedule_name" item edit button 64ms

And I wait until I see "Update Schedule" text 313ms

And I enter "schedule_name_edit" as "scheduleName" 272ms

And I check radio button "schedule-monthly" 10s 87ms

And I select "7" from "date_monthly" 1s 143ms

And I enter "05:17" as "time-monthly_time" 108ms

And I click on "Update Schedule" 66ms

Then I wait until I see "Schedule successfully updated" text 1s 602ms

And I should see a "schedule_name_edit" text 73ms

And I should see a "Organization" text 64ms

And I should see a "0 17 5 7 * ?" text 66ms

Scenario:
View the yourorg recurring actions details
946ms 7

When I follow the left menu "Home > My Organization > Recurring Actions" 86ms

Then I should see a "schedule_name" text 342ms

When I click the "schedule_name" item details button 65ms

Then I should see a "Every 7th of the month at 05:17" text 249ms

And I should see a "Package Profile Update" text 75ms

When I click on "Back" 69ms

Then I should see a "Schedules" text 56ms

Scenario:
Cleanup: Delete the yourorg Recurring Action
1s 463ms 7

When I follow the left menu "Home > My Organization > Recurring Actions" 76ms

Then I should see a "schedule_name_edit" text 256ms

When I click the "schedule_name" item delete button 73ms

And I wait until I see "Delete Recurring Action Schedule" text 65ms

And I click on the red confirmation button 66ms

Then I wait until I see "Schedule 'schedule_name_edit' has been deleted." text 760ms

And I should see a "No schedules created. Use Create to add a schedule" text 164ms

Scenario:
Create an admin org Recurring Action
37s 136ms 23

Execution time: 20:30

When I follow the left menu "Admin > Organizations" 114ms

And I follow "SUSE Test" in the content area 71ms

And I follow "Recurring Actions" in the content area 64ms

Then I should see a "No schedules created. Use Create to add a schedule" text 61ms

When I click on "Create" 84ms

And I wait until I see "Schedule Name" text 95ms

And I select "Custom state" from "actionTypeDescription" 1s 131ms

And I wait until I see "Configure states to execute" text 97ms

And I enter "schedule_name" as "scheduleName" 132ms

And I check radio button "schedule-daily" 10s 68ms

And I enter 1 minutes from now as "time-daily_time" 96ms

And I click on the "disabled" toggler 56ms

And I check "Hardware Profile Update-cbox" 86ms

And I click on "Save Changes" 65ms

And I wait until I see "Edit State Ranks" text 102ms

And I click on "Confirm" 75ms

And I click on "Create Schedule" 61ms

Then I wait until I see "Schedule successfully created" text 250ms

And I should see a "schedule_name" text 81ms

And I should see a "Organization" text 66ms

When I am on the "Events" page of this "sle_minion" 982ms

And I follow "History" 397ms

Then I wait until I see the event "Apply recurring states [hardware.profileupdate] scheduled" completed during last minute, refreshing the page 22s 891ms

Scenario:
Edit the admin org Recurring Action
12s 545ms 14

When I follow the left menu "Admin > Organizations" 139ms

And I follow "SUSE Test" in the content area 70ms

And I follow "Recurring Actions" in the content area 63ms

Then I should see a "schedule_name" text 352ms

When I click the "schedule_name" item edit button 63ms

And I wait until I see "Update Schedule" text 392ms

And I enter "schedule_name_org" as "scheduleName" 237ms

And I check radio button "schedule-cron" 10s 72ms

And I enter "0 0 15 3 * ?" as "cron" 209ms

And I click on "Update Schedule" 66ms

Then I wait until I see "Schedule successfully updated" text 588ms

And I should see a "schedule_name_org" text 163ms

And I should see a "Organization" text 63ms

And I should see a "0 0 15 3 * ?" text 63ms

Scenario:
View the admin org recurring actions details
872ms 8

When I follow the left menu "Admin > Organizations" 60ms

And I follow "SUSE Test" in the content area 61ms

And I follow "Recurring Actions" in the content area 56ms

Then I should see a "schedule_name" text 255ms

When I click the "schedule_name" item details button 60ms

Then I should see a "Every 3rd of the month at 15:00" text 254ms

When I click on "Back" 66ms

Then I should see a "Schedules" text 57ms

Scenario:
View all types of recurring actions in the list of all actions
1s 22ms 8

When I follow the left menu "Schedule > Recurring Actions" 124ms

Then I should not see a "Create" text 55ms

And I should see a "schedule_name_minion" text 502ms

And I should see a "Minion" text 68ms

And I should see a "schedule_name_group" text 67ms

And I should see a "Group" text 68ms

And I should see a "schedule_name_org" text 67ms

And I should see a "Organization" text 67ms

Scenario:
View details in list of all actions
1s 446ms 6

When I follow the left menu "Schedule > Recurring Actions" 58ms

And I click the "schedule_name_minion" item details button 527ms

Then I should see a "Every Wednesday at 01:35" text 233ms

And I should not see a "Schedules" text in the content area 30ms

When I click on "Back" 57ms

Then I should see a "schedule_name_group" text 539ms

Scenario:
Cleanup: Delete the admin org Recurring Action
871ms 8

When I follow the left menu "Admin > Organizations" 105ms

And I follow "SUSE Test" in the content area 59ms

And I follow "Recurring Actions" in the content area 56ms

Then I should see a "schedule_name_org" text 251ms

When I click the "schedule_name_org" item delete button 76ms

And I wait until I see "Delete Recurring Action Schedule" text 68ms

And I click on the red confirmation button 65ms

Then I wait until I see "Schedule 'schedule_name_org' has been deleted." text 187ms

Scenario:
Cleanup: Delete the group Recurring Action
1s 731ms 9

When I follow the left menu "Systems > System Groups" 115ms

And I follow "Recurring-Action-test-group" 336ms

And I follow "Recurring Actions" in the content area 60ms

Then I should see a "schedule_name_group" text 361ms

When I click the "schedule_name_group" item delete button 66ms

And I wait until I see "Delete Recurring Action Schedule" text 70ms

And I click on the red confirmation button 56ms

Then I wait until I see "Schedule 'schedule_name_group' has been deleted." text 595ms

And I should see a "No schedules created. Use Create to add a schedule" text 69ms

Scenario:
Cleanup: Delete the minion Highstate Recurring Action
2s 722ms 7

When I am on the "Recurring Actions" page of this "sle_minion" 999ms

Then I should see a "schedule_name_minion" text 270ms

When I click the "schedule_name_minion" item delete button 62ms

And I wait until I see "Delete Recurring Action Schedule" text 72ms

And I click on the red confirmation button 59ms

Then I wait until I see "Schedule 'schedule_name_minion' has been deleted." text 1s 192ms

And I should see a "No schedules created. Use Create to add a schedule" text 66ms

Scenario:
Cleanup: Delete the system group created for group recurring action tests
1s 689ms 5

When I follow the left menu "Systems > System Groups" 60ms

And I follow "Recurring-Action-test-group" 295ms

And I follow "Delete Group" 235ms

And I click on "Confirm Deletion" 1s 37ms

Then I should see a "Your organization has no system groups." text 61ms

Scenario:
Cleanup: Remove "My State Channel for Recurring Actions" config channel
1s 272ms 5

When I follow the left menu "Configuration > Channels" 119ms

And I follow "My State Channel for Recurring Actions" 369ms

And I follow "Delete Channel" 290ms

And I click on "Delete Config Channel" 440ms

Then I should see a "Channel 'My State Channel for Recurring Actions' has been deleted" text 52ms

@skip_if_github_validation @scc_credentials @scope_changing_software_channels @sle_minion
Feature:Assign child channel to a system 1m 29s 421ms 8 6

Scenario:
Log in as org admin user
2s 27ms 1

Given I am authorized 2s 27ms

@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
4s 961ms 15

Warning: Radio button 'openSUSE Tumbleweed (x86_64)' is already checked

Given I am on the Systems overview page of this "sle_minion" 1s 912ms

When I follow "Software" in the content area 69ms

And I follow "Software Channels" in the content area 64ms

And I wait until I do not see "Loading..." text 69ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 219ms

Then radio button "openSUSE Tumbleweed (x86_64)" should be checked 15ms

When I wait until I do not see "Loading..." text 1s 845ms

And I uncheck "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" by label 35ms

Then I should see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" as unchecked 44ms

When I uncheck "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" by label 77ms

Then I should see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" as unchecked 15ms

When I click on "Next" 61ms

Then I should see a "Confirm Software Channel Change" text 64ms

When I click on "Confirm" 60ms

Then I should see a "Changing the channels has been scheduled." text 405ms

@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 46ms 3

When I refresh the metadata for "sle_minion" 7s 341ms

Then channel "openSUSE Tumbleweed (x86_64)" should be enabled on "sle_minion" 839ms

And channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" should be disabled on "sle_minion" 864ms

@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
33s 185ms 14

When I follow "Software" in the content area 64ms

And I follow "Software Channels" in the content area 59ms

And I wait until I do not see "Loading..." text 64ms

Then radio button "openSUSE Tumbleweed (x86_64)" should be checked 291ms

When I wait until I do not see "Loading..." text 595ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" by label 78ms

Then I should see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" as checked 14ms

When I click on "Next" 60ms

Then I should see a "Confirm Software Channel Change" text 63ms

When I click on "Confirm" 62ms

Then I should see a "Changing the channels has been scheduled." text 533ms

When I follow "scheduled" in the content area 80ms

And I wait until I see "1 system successfully completed this action." text, refreshing the page 29s 822ms

Then channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" should be enabled on "sle_minion" 1s 393ms

Scenario:
Check channel change has completed for the system
3s 562ms 3

Given I am on the Systems overview page of this "sle_minion" 1s 65ms

When I wait until event "Subscribe channels scheduled" is completed 2s 438ms

Then I should see a "The client completed this action on" text 57ms

@susemanager
Scenario:
Check the system is subscribed to the new channels
< 1ms 6

When I follow "Software" in the content area 0s

And I follow "Software Channels" in the content area 0s

And I wait until I do not see "Loading..." text 0s

Then radio button "SLE-Product-SLES15-SP7-Pool for x86_64" should be checked 0s

And I wait until I do not see "Loading..." text 0s

And I should see "SLE15-SP7-Installer-Updates for x86_64" as checked 0s

@uyuni
Scenario:
Check the system is subscribed to the new channels
809ms 6

When I follow "Software" in the content area 74ms

And I follow "Software Channels" in the content area 65ms

And I wait until I do not see "Loading..." text 68ms

Then radio button "openSUSE Tumbleweed (x86_64)" should be checked 166ms

And I wait until I do not see "Loading..." text 417ms

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
3s 81ms 3

When I refresh the metadata for "sle_minion" 1s 412ms

Then channel "openSUSE Tumbleweed (x86_64)" should be enabled on "sle_minion" 884ms

And channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" should be enabled on "sle_minion" 784ms

@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 748ms 18

When I follow "Software" in the content area 57ms

And I follow "Software Channels" in the content area 58ms

And I wait until I do not see "Loading..." text 64ms

Then radio button "openSUSE Tumbleweed (x86_64)" should be checked 86ms

And I wait until I do not see "Loading..." text 420ms

And I wait until I see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" text 74ms

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 15ms

When I check "Fake-RPM-SUSE-Channel" 38ms

And I click on "Next" 60ms

Then I should see a "Confirm Software Channel Change" text 68ms

When I click on "Confirm" 75ms

And I wait until I see "Changing the channels has been scheduled." text 398ms

And I follow "scheduled" in the content area 73ms

And I wait until I see "1 system successfully completed this action." text, refreshing the page 30s 333ms

Then channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" should be disabled on "sle_minion" 755ms

@scope_retracted_patches
Feature:Retracted patches 12m 41s 407ms 11 1

Scenario:
Log in as org admin user
1s 845ms 1

Given I am authorized 1s 845ms

Scenario:
Installed retracted package should show icon in the system packages list
10m 42s 284ms 3 9 1

When I install package "rute-dummy=2.1-1.1" on this "sle_minion" 2s 390ms

And I refresh packages list via spacecmd on "sle_minion" 8s 799ms

And I wait until refresh package list on "sle_minion" is finished 10m 10s 324ms Show Error + 
                                            
 execution expired (Timeout::Error)
./features/support/commonlib.rb:89:in `repeat_until_timeout'
./features/step_definitions/command_steps.rb:1292:in `/^I wait until refresh package list on "(.*?)" is finished$/'
features/secondary/min_retracted_patches.feature:14:in `I wait until refresh package list on "sle_minion" is finished'

And I am on the "Software" page of this "sle_minion" 0s

And I follow "Packages" 0s

And I follow "List / Remove" 0s

And I enter "rute-dummy" as the filtered package name 0s

And I click on the filter button until page does contain "rute-dummy" text 0s

Then the table row for "rute-dummy-2.1-1.1" should contain "retracted" icon 0s

When I remove package "rute-dummy" from this "sle_minion" 0s

And I refresh packages list via spacecmd on "sle_minion" 0s

And I wait until package "rute-dummy" is removed from "sle_minion" via spacecmd 0s

20s 769ms Show Info + 
20:32:49:000 - 20:43:10:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/YourRhn.do
Screenshot +

Scenario:
Retracted package should not be available for installation
13s 244ms 7

When I am on the "Software" page of this "sle_minion" 1s 101ms

And I follow "Packages" 491ms

And I follow "Install" 640ms

And I enter "rute-dummy" as the filtered package name 49ms

And I click on the filter button until page does contain "rute-dummy" text 10s 829ms

Then I should see a "rute-dummy-2.0-1.2" text 66ms

And I should not see a "rute-dummy-2.1-1.1" text 65ms

Scenario:
Retracted package should not be available for upgrade
39s 510ms 10

When I install old package "rute-dummy=2.0-1.2" on this "sle_minion" 2s 262ms

And I refresh packages list via spacecmd on "sle_minion" 6s 684ms

And I wait until refresh package list on "sle_minion" is finished 12s 359ms

And I am on the "Software" page of this "sle_minion" 1s 51ms

And I follow "Packages" 418ms

And I follow "Upgrade" 645ms

Then I should not see a "rute-dummy-2.1-1.1" text 103ms

When I remove package "rute-dummy" from this "sle_minion" 1s 768ms

And I refresh packages list via spacecmd on "sle_minion" 6s 927ms

And I wait until package "rute-dummy" is removed from "sle_minion" via spacecmd 7s 288ms

Scenario:
Retracted patch should not affect any system
40s 587ms 13

When I install package "rute-dummy=2.0-1.2" on this "sle_minion" 1s 968ms

And I refresh packages list via spacecmd on "sle_minion" 6s 955ms

And I wait until refresh package list on "sle_minion" is finished 12s 908ms

And I follow the left menu "Software > Channel List > All" 181ms

And I follow "Show All Child Channels" 77ms

And I follow "Fake-RPM-SUSE-Channel" 599ms

And I follow "Patches" in the content area 75ms

And I follow "rute-dummy-0817" 515ms

And I follow "Affected Systems" 289ms

Then I should see a "No systems." text 67ms

When I remove package "rute-dummy" from this "sle_minion" 1s 774ms

And I refresh packages list via spacecmd on "sle_minion" 7s 836ms

And I wait until package "rute-dummy" is removed from "sle_minion" via spacecmd 7s 338ms

Scenario:
Target systems for stable packages should not be empty
2s 260ms 7

When I follow the left menu "Software > Channel List > All" 183ms

And I follow "Show All Child Channels" 66ms

And I follow "Fake-RPM-SUSE-Channel" 597ms

And I follow "Packages" in the content area 71ms

And I follow "rute-dummy-2.0-1.2.x86_64" 654ms

And I follow "Target Systems" 547ms

And I refresh page until I see "sle_minion" hostname as text 139ms

Scenario:
Target systems for retracted packages should be empty
11s 751ms 7

When I follow the left menu "Software > Channel List > All" 134ms

And I follow "Show All Child Channels" 55ms

And I follow "Fake-RPM-SUSE-Channel" 596ms

And I follow "Packages" in the content area 68ms

And I follow "rute-dummy-2.1-1.1.x86_64" 570ms

And I follow "Target Systems" 309ms

Then I should not see "sle_minion" hostname 10s 16ms

Scenario:
Retracted packages in the patch detail
4s 818ms 15

When I follow the left menu "Patches > Patch List > All" 191ms

And I enter "dummy" as the filtered synopsis 75ms

And I click on the filter button 798ms

And I follow "rute-dummy-0815" 464ms

Then I should see a "Status: Retracted" text 63ms

When I go back 402ms

And I enter "dummy" as the filtered synopsis 50ms

And I click on the filter button 670ms

And I follow "rute-dummy-0816" 372ms

Then I should see a "Status: Stable" text 69ms

When I go back 430ms

And I enter "dummy" as the filtered synopsis 47ms

And I click on the filter button 658ms

And I follow "rute-dummy-0817" 457ms

Then I should see a "Status: Retracted" text 66ms

Scenario:
Retracted packages in the patches list
852ms 6

When I follow the left menu "Patches > Patch List > All" 82ms

And I enter "dummy" as the filtered synopsis 40ms

And I click on the filter button 672ms

Then the table row for "rute-dummy-0815" should contain "retracted" icon 22ms

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
928ms 7

When I follow the left menu "Software > Channel List > All" 176ms

And I follow "Show All Child Channels" 62ms

And I follow "Fake-RPM-SUSE-Channel" 579ms

And I follow "Patches" in the content area 69ms

Then the table row for "rute-dummy-0815" should contain "retracted" icon 15ms

And the table row for "rute-dummy-0816" should not contain "retracted" icon 11ms

And the table row for "rute-dummy-0817" should contain "retracted" icon 13ms

Scenario:
Retracted packages in the channel packages list
806ms 7

When I follow the left menu "Software > Channel List > All" 69ms

And I follow "Show All Child Channels" 47ms

And I follow "Fake-RPM-SUSE-Channel" 576ms

And I follow "Packages" in the content area 63ms

Then the table row for "rute-dummy-2.0-1.1.x86_64" should contain "retracted" icon 18ms

Then the table row for "rute-dummy-2.0-1.2.x86_64" should not contain "retracted" icon 14ms

Then the table row for "rute-dummy-2.1-1.1.x86_64" should contain "retracted" icon 16ms

Scenario:
SSM: Retracted package should not be available for installation
2s 516ms 10

When I follow the left menu "Systems > System List > All" 181ms

And I click on the clear SSM button 64ms

And I check the "sle_minion" client 459ms

And I follow the left menu "Systems > System Set Manager > Overview" 610ms

And I follow "Packages" in the content area 61ms

And I follow "Install" 547ms

And I follow "Fake-RPM-SUSE-Channel" 368ms

Then I should see a "rute-dummy-2.0-1.2" text 85ms

And I should not see a "rute-dummy-2.1-1.1" text 84ms

And I click on the clear SSM button 52ms

@skip_if_github_validation @containerized_server @proxy @build_host @private_net @pxeboot_minion @scope_cobbler @bug_reported
Feature:PXE boot a terminal with Cobbler and containerized proxy < 1ms 19

* Related GitHub Card: https://github.com/SUSE/spacewalk/issues/29863
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 3s 772ms 11

* Related GitHub Card: https://github.com/SUSE/spacewalk/issues/29840

Scenario:
Log in as admin user
2s 73ms 1

Given I am authorized for the "Admin" section 2s 73ms

Scenario:
Create a new user in a timezone different than server's timezone
7s 877ms 11

When I follow the left menu "Users > User List > Active" 178ms

And I follow "Create User" 425ms

And I enter "MalaysianUser" as "login" 62ms

And I enter "MalaysianUser" as "desiredpassword" 66ms

And I enter "MalaysianUser" as "desiredpasswordConfirm" 73ms

And I select "Mr." from "prefix" 49ms

And I enter "Test" as "firstNames" 52ms

And I enter "User" as "lastName" 52ms

And I enter "galaxy-noise@localhost" as "email" 71ms

And I select "(GMT+0800) Malaysia" from "timezone" 64ms

And I click on "Create Login" 6s 779ms

Scenario:
Add roles for the Malaysian user
11s 565ms 9

When I follow the left menu "Users > User List > Active" 97ms

And I follow "MalaysianUser" 282ms

And the "role_satellite_admin" checkbox should be disabled 10s 9ms

And I check "role_org_admin" 78ms

And I check "role_system_group_admin" 76ms

And I check "role_channel_admin" 74ms

And I check "role_activation_key_admin" 75ms

And I check "role_config_admin" 76ms

And I click on "Update" 794ms

Scenario:
Login as the new Malaysian user
1s 931ms 2

Given I am authorized as "MalaysianUser" with password "MalaysianUser" 1s 919ms

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 897ms 10

Given I am on the Systems overview page of this "sle_minion" 1s 709ms

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" 658ms

And I follow "Events" in the content area 70ms

And I follow "Pending" in the content area 65ms

And I wait at most 180 seconds until I do not see "Remote Command on" text, refreshing the page 16s 639ms

And I follow "History" in the content area 67ms

And I follow first "scheduled by MalaysianUser" 503ms

Then I should see a "MYT" text 62ms

Scenario:
Login as the new Malaysian user if the previous scenario failed
508ms 2

Given I am authorized as "MalaysianUser" with password "MalaysianUser" 490ms

Then I should see a "MalaysianUser" link 17ms

Scenario:
Schedule a remote script in the future and see the correct timezone as a pop up
1s 924ms 6

Given I am on the Systems overview page of this "sle_minion" 1s 582ms

When I follow "Remote Command" in the content area 60ms

And I enter as remote command this script in #!/bin/bash ls 57ms

And I enter "00:00" as "date_timepicker_widget_input" 76ms

And I click on "Schedule" 62ms

Then I should see a "00:00:00 MYT" text 83ms

Scenario:
Login as the new Malaysian user if the previous scenario failed
616ms 2

Given I am authorized as "MalaysianUser" with password "MalaysianUser" 607ms

Then I should see a "MalaysianUser" link 9ms

Scenario:
Cleanup: Log in as admin user again and remove scheduled actions
4s 884ms 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 820ms

And I cancel all scheduled actions via API 2s 63ms

Scenario:
Cleanup: Remove role
11s 868ms 9

When I follow the left menu "Users > User List > Active" 211ms

And I follow "MalaysianUser" 448ms

And I uncheck "role_org_admin" 10s 93ms

And I click on "Update" 1s 22ms

Then I should see "role_org_admin" as unchecked 17ms

And I should see "role_system_group_admin" as checked 18ms

And I should see "role_channel_admin" as checked 18ms

And I should see "role_activation_key_admin" as checked 18ms

And I should see "role_config_admin" as checked 19ms

Scenario:
Cleanup: Delete user
624ms 1

When I delete user "MalaysianUser" 624ms

@scope_ansible @sle_minion @test_issue
Feature:Operate an Ansible control node in a normal minion 10m 55s 240ms 15 2 2

* Related GitHub Card: https://github.com/SUSE/spacewalk/issues/29691

Scenario:
Log in as org admin user
445ms 1

Given I am authorized for the "Admin" section 445ms

Scenario:
Pre-requisite: Deploy test playbooks and inventory file
3s 745ms 1

When I deploy testing playbooks and inventory files to "sle_minion" 3s 745ms

@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 159ms 5

Given I am on the Systems overview page of this "sle_minion" 916ms

When I follow "Properties" in the content area 72ms

And I check "ansible_control_node" 80ms

And I click on "Update Properties" 1s 993ms

Then I wait until I see "Ansible Control Node type has been applied." text 96ms

Scenario:
Apply highstate and check that Ansible is installed
24s 915ms 5 1

Given I am on the Systems overview page of this "sle_minion" 1s 11ms

When I follow "States" in the content area 68ms

And I click on "Apply Highstate" 72ms

And I wait until event "Apply highstate scheduled" is completed 2s 622ms

Then "ansible" should be installed on "sle_minion" 632ms Show Error + 
                                            
 FAIL: rpm -q ansible returned status code = 1.
Output:
package ansible is not installed
 (ScriptError)
./features/support/remote_node.rb:172:in `run_local'
./features/support/remote_node.rb:120:in `run'
./features/step_definitions/command_steps.rb:207:in `/^"([^"]*)" should be installed on "([^"]*)"$/'
features/secondary/min_ansible_control_node.feature:40:in `"ansible" should be installed on "sle_minion"'

20s 508ms Show Info + 
20:47:50:000 - 20:47:55:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010020&aid=194
Screenshot +

Scenario:
The Ansible tab appears in the system overview page
1s 180ms 3

Given I am on the Systems overview page of this "sle_minion" 1s 48ms

When I follow "Ansible" in the content area 68ms

Then I should see a "Ansible Control Node Configuration" text 63ms

Scenario:
Configure some inventory and playbooks path
1s 511ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 13ms

When I follow "Ansible" in the content area 62ms

Then I should see a "Ansible Control Node Configuration" text 63ms

And I enter "/srv/playbooks/" as "new_playbook_path_input" 148ms

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 32s 756ms 6 1

Given I am on the Systems overview page of this "sle_minion" 1s 19ms

When I follow "Ansible" in the content area 62ms

And I follow "Inventories" in the content area 64ms

And I wait until I see "/srv/playbooks/orion_dummy/hosts" text 257ms

And I click on the inventory accordion for "/srv/playbooks/orion_dummy/hosts" 48ms

Then I wait until I see "myself" text, refreshing the page 4m 13s 86ms Show Error + 
                                            
 execution expired (Timeout::Error)
./features/support/commonlib.rb:89: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'

18s 217ms Show Info + 
20:48:19:000 - 20:52:35: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 352ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 116ms

When I follow "Ansible" in the content area 78ms

And I follow "Playbooks" in the content area 64ms

And I wait until I see "/srv/playbooks" text 248ms

And I click on "/srv/playbooks" 56ms

Then I wait until I see "/srv/playbooks/orion_dummy/playbook_orion_dummy.yml" text 4s 724ms

And I wait until I see "/srv/playbooks/basic_tests.yml" text 64ms

Scenario:
Run a playbook using custom inventory
31s 488ms 13

Given I am on the Systems overview page of this "sle_minion" 1s 10ms

When I follow "Ansible" in the content area 60ms

And I follow "Playbooks" in the content area 59ms

And I wait until I see "/srv/playbooks" text 246ms

And I click on "/srv/playbooks" 50ms

And I wait until I see "/srv/playbooks/orion_dummy/playbook_orion_dummy.yml" text 4s 569ms

And I click on "orion_dummy/playbook_orion_dummy.yml" 59ms

And I wait until I see "Playbook Content" text 979ms

And I select "/srv/playbooks/orion_dummy/hosts" from "inventory-path-select" 1s 121ms

And I click on "Schedule" 71ms

Then I should see a "Playbook execution has been scheduled" text 370ms

And I wait until event "Execute playbook 'playbook_orion_dummy.yml' scheduled" is completed 22s 204ms

And file "/tmp/file.txt" should exist on "sle_minion" 683ms

Scenario:
Run the basic tests playbook
43s 840ms 19

Given I am on the Systems overview page of this "sle_minion" 885ms

When I follow "Ansible" in the content area 81ms

And I follow "Playbooks" in the content area 64ms

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 567ms

And I click on "basic_tests.yml" 59ms

And I wait until I see "Playbook Content" text 931ms

And I click on "Schedule" 77ms

And I wait until I see "Playbook execution has been scheduled" text 292ms

And I wait for "2" seconds 2s

And I follow "scheduled" in the content area 71ms

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 506ms

When I follow "1 system" 293ms

And I wait until I see the system name of "sle_minion" 74ms

And I follow this "sle_minion" link 401ms

Then I should see a "42" text 75ms

And I should see a "101010" text 69ms

And I should see a "(code 0)" text 81ms

Scenario:
Run the basic tests playbook while editing variables and changing their values
44s 896ms 21

Given I am on the Systems overview page of this "sle_minion" 900ms

When I follow "Ansible" in the content area 77ms

And I follow "Playbooks" in the content area 64ms

And I wait until I see "/srv/playbooks" text 248ms

And I click on "/srv/playbooks" 58ms

And I wait until I see "/srv/playbooks/basic_tests.yml" text 4s 613ms

And I click on "basic_tests.yml" 59ms

And I wait until I see "Playbook Content" text 982ms

And I click on "Edit variables" 93ms

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" 94ms

And I click on "Schedule" 70ms

And I wait until I see "Playbook execution has been scheduled" text 299ms

And I wait for "2" seconds 2s

And I follow "scheduled" in the content area 72ms

Then I wait until I see "1 system successfully completed this action" text or "1 system failed to complete this action" text, refreshing the page 33s 453ms

When I follow "1 system" 285ms

And I wait until I see the system name of "sle_minion" 66ms

And I follow this "sle_minion" link 454ms

Then I should see a "4200" text 89ms

And I should see a "(code 0)" text 66ms

Scenario:
Run the basic tests playbook while editing the EMPTY variables and changing their values
45s 999ms 22

Given I am on the Systems overview page of this "sle_minion" 897ms

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 249ms

And I click on "/srv/playbooks" 58ms

And I wait until I see "/srv/playbooks/basic_tests.yml" text 4s 665ms

And I click on "basic_tests.yml" 62ms

And I wait until I see "Playbook Content" text 934ms

And I click on "Edit variables" 95ms

And I enter data from table with value as field name 1s 40ms
1 p1
2 p2
3 p3
4 p4
5 p5
(21 + 21) * 1000 p1_empty
(21 + 21) * 100 + (21 + 21) p2_empty

And I click on "Save" 96ms

And I click on "Schedule" 68ms

And I wait until I see "Playbook execution has been scheduled" text 981ms

And I wait for "2" seconds 2s

And I follow "scheduled" in the content area 75ms

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 666ms

When I follow "1 system" 294ms

And I wait until I see the system name of "sle_minion" 69ms

And I follow this "sle_minion" link 378ms

Then I should see a "42000" text 74ms

And I should see a "4242" text 70ms

And I should see a "(code 0)" text 71ms

@skip_if_github_validation
Scenario:
Run the basic tests playbook while editing the NULL variable and changing its value
45s 322ms 21

Given I am on the Systems overview page of this "sle_minion" 912ms

When I follow "Ansible" in the content area 76ms

And I follow "Playbooks" in the content area 64ms

And I wait until I see "/srv/playbooks" text 251ms

And I click on "/srv/playbooks" 59ms

And I wait until I see "/srv/playbooks/basic_tests.yml" text 4s 715ms

And I click on "basic_tests.yml" 59ms

And I wait until I see "Playbook Content" text 997ms

And I click on "Edit variables" 88ms

And I enter data from table with value as field name 1s 23ms
1 p1
2 p2
3 p3
4 p4
5 p5
1e p1_empty
2e p2_empty
256 * 256 p_null

And I click on "Save" 100ms

And I click on "Schedule" 70ms

And I wait until I see "Playbook execution has been scheduled" text 471ms

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 468ms

When I follow "1 system" 295ms

And I wait until I see the system name of "sle_minion" 68ms

And I follow this "sle_minion" link 383ms

Then I should see a "65536" text 73ms

And I should see a "(code 0)" text 70ms

@skip_if_github_validation
Scenario:
Run the basic tests playbook on SAVE operation of YAML editor with pre-crafted strings
44s 555ms 22

Given I am on the Systems overview page of this "sle_minion" 918ms

When I follow "Ansible" in the content area 77ms

And I follow "Playbooks" in the content area 65ms

And I wait until I see "/srv/playbooks" text 339ms

And I click on "/srv/playbooks" 55ms

And I wait until I see "/srv/playbooks/basic_tests.yml" text 4s 684ms

And I click on "basic_tests.yml" 61ms

And I wait until I see "Playbook Content" text 1s 90ms

And I click on "Edit variables" 97ms

And I click on "Edit YAML" 78ms

And I click on "Save" 93ms

And I click on "Schedule" 69ms

And I wait until I see "Playbook execution has been scheduled" text 306ms

And I wait for "2" seconds 2s

And I follow "scheduled" in the content area 75ms

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 500ms

When I follow "1 system" 285ms

And I wait until I see the system name of "sle_minion" 68ms

And I follow this "sle_minion" link 467ms

Then I should see a "42" text 72ms

And I should see a "101010" text 69ms

And I should see a "(code 0)" text 76ms

Scenario:
Run the basic tests playbook on SAVE operation of YAML editor with safe values
45s 382ms 26

Given I am on the Systems overview page of this "sle_minion" 1s 26ms

When I follow "Ansible" in the content area 77ms

And I follow "Playbooks" in the content area 63ms

And I wait until I see "/srv/playbooks" text 155ms

And I click on "/srv/playbooks" 57ms

And I wait until I see "/srv/playbooks/basic_tests.yml" text 4s 598ms

And I click on "basic_tests.yml" 60ms

And I wait until I see "Playbook Content" text 1s 18ms

And I click on "Edit variables" 88ms

And I enter data from table with value as field name 881ms
abc p1
def p2
ghi p3
jkl p4
16 * 16 * 16 p5

And I click on "Edit YAML" 73ms

And I click on "Save" 106ms

And I click on "Schedule" 71ms

And I wait until I see "Playbook execution has been scheduled" text 301ms

And I wait for "2" seconds 2s

And I follow "scheduled" in the content area 72ms

Then I wait until I see "1 system successfully completed this action" text or "1 system failed to complete this action" text, refreshing the page 33s 551ms

When I follow "1 system" 294ms

And I wait until I see the system name of "sle_minion" 66ms

And I follow this "sle_minion" link 382ms

Then I should see a "abc" text 72ms

And I should see a "def" text 70ms

And I should see a "ghi" text 68ms

And I should see a "jkl" text 73ms

And I should see a "4096" text 69ms

And I should see a "(code 0)" text 75ms

Scenario:
Cleanup: Disable Ansible and remove test playbooks and inventory file
15s 131ms 7

Given I am on the Systems overview page of this "sle_minion" 907ms

When I follow "Properties" in the content area 76ms

And I uncheck "ansible_control_node" 10s 85ms

And I click on "Update Properties" 1s 591ms

Then I should see a "System properties changed" text 90ms

And I remove package "orion-dummy" from this "sle_minion" without error control 1s 991ms

And I remove "/tmp/file.txt" from "sle_minion" 388ms

@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"
24s 557ms 4

Given I am on the Systems overview page of this "sle_minion" 1s 74ms

When I follow "States" in the content area 77ms

And I click on "Apply Highstate" 61ms

And I wait until event "Apply highstate scheduled" is completed 23s 343ms

@sle_minion @proxy
Feature:Move a minion from a proxy to direct connection 10m 51s 624ms 13

Scenario:
Log in as org admin user
1s 975ms 1

Given I am authorized 1s 975ms

Scenario:
Delete minion system profile before bootstrap
4m 7s 600ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 807ms

When I follow "Delete System" 570ms

Then I should see a "Confirm System Profile Deletion" text 59ms

When I click on "Delete Profile" 67ms

And I wait until I see "has been deleted" text 4m 3s 970ms

And I wait until Salt client is inactive on "sle_minion" 714ms

Then "sle_minion" should not be registered 410ms

Scenario:
Bootstrap a minion
1m 53s 674ms 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 63ms

When I enter the hostname of "sle_minion" as "hostname" 142ms

And I enter "22" as "port" 54ms

And I enter "root" as "user" 62ms

And I enter "linux" as "password" 64ms

And I select "1-SUSE-KEY-x86_64" from "activationKeys" 75ms

And I select the hostname of "proxy" from "proxies" if present 64ms

And I click on "Bootstrap" 65ms

And I wait until I see "Bootstrap process initiated." text 30s 664ms

And I wait until onboarding is completed for "sle_minion" 1m 22s 334ms

Scenario:
Check the new bootstrapped minion in System Overview page
4s 274ms 3

It took 4 seconds to contact the minion

When I follow the left menu "Salt > Keys" 125ms

Then I should see a "accepted" text 434ms

And the Salt master can reach "sle_minion" 3s 713ms

Scenario:
Check initial connection from minion to proxy
1s 202ms 4

Given I am on the Systems overview page of this "sle_minion" 988ms

When I follow "Details" in the content area 73ms

And I follow "Connection" in the content area 70ms

Then I should see "proxy" short hostname 70ms

Scenario:
Check initial registration on proxy of minion
1s 275ms 4

Given I am on the Systems overview page of this "proxy" 1s 51ms

When I follow "Details" in the content area 62ms

And I follow "Proxy" in the content area 66ms

Then I should see "sle_minion" hostname 95ms

Scenario:
Change from proxy to direct connection
38s 10ms 11

Given I am on the Systems overview page of this "sle_minion" 1s 49ms

When I follow "Details" in the content area 62ms

And I follow "Connection" in the content area 75ms

And I follow "Change" in the content area 66ms

And I select "None" from "proxies" 69ms

And I click on "Change Proxy" 59ms

And I wait until I see "scheduled" text 444ms

And I follow "Events" 529ms

And I follow "History" 637ms

And I wait until I see the event "Apply states [bootstrap.set_proxy] scheduled" completed during last minute, refreshing the page 11s 458ms

And I wait until I see the event "Apply states [channels] scheduled" completed during last minute, refreshing the page 23s 557ms

Scenario:
Check direct connection
1s 125ms 4

Given I am on the Systems overview page of this "sle_minion" 941ms

When I follow "Details" in the content area 63ms

And I follow "Connection" in the content area 59ms

Then I should see a "This system connects directly and not through a Proxy" text 61ms

Scenario:
Change connection back to a proxy via SSM
2m 1s 876ms 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 54ms

And I check the "sle_minion" client 462ms

And I should see "1" systems selected for SSM 201ms

And I follow the left menu "Systems > System Set Manager > Overview" 525ms

And I follow "proxy server" in the content area 79ms

And I select the hostname of "proxy" from "proxies" if present 72ms

And I click on "Change Proxy" 58ms

And I wait until I see "scheduled" text 282ms

Scenario:
Check events on the minion
36s 365ms 5

Given I am on the Systems overview page of this "sle_minion" 1s 157ms

And I follow "Events" 461ms

And I follow "History" 453ms

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 281ms

Scenario:
Check registration on proxy of minion
1s 195ms 4

Given I am on the Systems overview page of this "proxy" 966ms

When I follow "Details" in the content area 69ms

And I follow "Proxy" in the content area 65ms

Then I should see "sle_minion" hostname 94ms

Scenario:
Check connection from minion to proxy
1s 112ms 4

Given I am on the Systems overview page of this "sle_minion" 918ms

When I follow "Details" in the content area 60ms

And I follow "Connection" in the content area 65ms

Then I should see "proxy" short hostname 67ms

Scenario:
Check events history for failures on the minion
1m 21s 935ms 2

Given I am on the Systems overview page of this "sle_minion" 960ms

Then I check for failed events on history event page 1m 20s 975ms

@ssh_minion @scope_salt_ssh @proxy
Feature:Move a SSH minion from a proxy to direct connection 7m 11s 467ms 11

Scenario:
Log in as org admin user
3s 543ms 1

Given I am authorized 3s 543ms

Scenario:
Delete minion system profile before bootstrap
19s 368ms 6

Given I am on the Systems overview page of this "ssh_minion" 2s 104ms

When I follow "Delete System" 473ms

Then I should see a "Confirm System Profile Deletion" text 66ms

When I click on "Delete Profile" 64ms

And I wait until I see "has been deleted" text 16s 150ms

Then "ssh_minion" should not be registered 508ms

Scenario:
Bootstrap a minion
2m 25s 270ms 11

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 67ms

When I check "manageWithSSH" 91ms

And I enter the hostname of "ssh_minion" as "hostname" 146ms

And I enter "root" as "user" 60ms

And I enter "linux" as "password" 64ms

And I select "1-SUSE-SSH-KEY-x86_64" from "activationKeys" 76ms

And I select the hostname of "proxy" from "proxies" if present 64ms

And I click on "Bootstrap" 64ms

And I wait at most 480 seconds until I see "Bootstrap process initiated." text 42s 231ms

And I wait until onboarding is completed for "ssh_minion" 1m 42s 319ms

Scenario:
Check initial connection from minion to proxy
1s 218ms 4

Given I am on the Systems overview page of this "ssh_minion" 1s 7ms

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 61ms

Scenario:
Check initial registration on proxy of minion
1s 632ms 4

Given I am on the Systems overview page of this "proxy" 1s 385ms

When I follow "Details" in the content area 82ms

And I follow "Proxy" in the content area 66ms

Then I should see "ssh_minion" hostname 97ms

Scenario:
Change from proxy to direct connection
36s 888ms 10

Given I am on the Systems overview page of this "ssh_minion" 1s 25ms

When I follow "Details" in the content area 63ms

And I follow "Connection" in the content area 63ms

And I follow "Change" in the content area 69ms

And I select "None" from "proxies" 71ms

And I click on "Change Proxy" 59ms

And I wait until I see "scheduled" text 347ms

And I follow "Events" 395ms

And I follow "History" 405ms

And I wait until I see the event "Apply states [channels] scheduled" completed during last minute, refreshing the page 34s 388ms

Scenario:
Check direct connection
1s 322ms 4

Given I am on the Systems overview page of this "ssh_minion" 1s 126ms

When I follow "Details" in the content area 64ms

And I follow "Connection" in the content area 67ms

Then I should see a "This system connects directly and not through a Proxy" text 62ms

Scenario:
Change connection to a proxy
2m 37s 284ms 11

Given I wait for "120" seconds 2m

Given I am on the Systems overview page of this "ssh_minion" 1s 23ms

When I follow "Details" in the content area 62ms

And I follow "Connection" in the content area 59ms

And I follow "Change" in the content area 65ms

And I select the hostname of "proxy" from "proxies" if present 76ms

And I click on "Change Proxy" 60ms

And I wait until I see "scheduled" text 364ms

And I follow "Events" 465ms

And I follow "History" 490ms

And I wait until I see the event "Apply states [channels] scheduled" completed during last minute, refreshing the page 34s 617ms

Scenario:
Check registration on proxy of minion
1s 200ms 4

Given I am on the Systems overview page of this "proxy" 968ms

When I follow "Details" in the content area 65ms

And I follow "Proxy" in the content area 67ms

Then I should see "ssh_minion" hostname 98ms

Scenario:
Check connection from minion to proxy
1s 422ms 4

Given I am on the Systems overview page of this "ssh_minion" 1s 220ms

When I follow "Details" in the content area 63ms

And I follow "Connection" in the content area 75ms

Then I should see "proxy" short hostname 63ms

Scenario:
Check events history for failures on the minion
1m 2s 316ms 2

Given I am on the Systems overview page of this "ssh_minion" 1s 337ms

Then I check for failed events on history event page 1m 979ms

Feature:Sanity check that all logfiles exist 25s 939ms 1

In order to be secure
As an authorized user
I want to watch different logfiles

Scenario:
All logfiles should be available
25s 939ms 9

Then I wait until file "/var/log/rhn/rhn_web_ui.log" exists on server 3s 688ms

And I wait until file "/var/log/rhn/rhn_web_api.log" exists on server 2s 697ms

And I wait until file "/var/log/rhn/rhn_web_frontend.log" exists on server 2s 527ms

And I wait until file "/var/log/rhn/rhn_taskomatic_daemon.log" exists on server 2s 535ms

And I wait until file "/var/log/rhn/search/rhn_search_daemon.log" exists on server 2s 607ms

And I wait until file "/var/log/rhn/search/rhn_search.log" exists on server 4s 145ms

And I wait until file "/var/log/rhn/reposync.log" exists on server 2s 723ms

And I wait until file "/var/log/salt/master" exists on server 2s 518ms

And I wait until file "/var/log/salt/api" exists on server 2s 494ms

@scope_cobbler
Feature:Run Cobbler Sync via WebUI 37s 490ms 6 1

Scenario:
Login as admin
2s 146ms 1

Given I am authorized for the "Admin" section 2s 146ms

Scenario:
Start Cobbler monitoring
15s 855ms 2

When I start local monitoring of Cobbler 13s 329ms

And I backup Cobbler settings file 2s 525ms

@uyuni
Scenario:
Check that the Cobbler Settings Page exists
707ms 7

When I follow the left menu "Admin > Manager Configuration > Cobbler" 423ms

Then I should see a "Uyuni Configuration - Cobbler. " text 69ms

And I should see a "Setup your Uyuni Cobbler settings below. " text 58ms

And I should see a "Cobbler sync is used to repair or rebuild the contents /srv/tftpboot or /srv/www/cobbler when manual modification of cobbler has occurred. " text 60ms

And I should see a "For more information refer to the 'cobbler' man page. " text 57ms

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
194ms 3

When I follow the left menu "Admin > Manager Configuration > Cobbler" 69ms

And I click on "Update" 56ms

Then I should see a "Cobbler Sync action was successfully executed. Look at /var/log/cobbler/*.log for more information" text 68ms

Scenario:
Run Cobbler Sync via button and verify task timestamp in Last Execution Times Page
10s 993ms 4

When I follow the left menu "Admin > Manager Configuration > Cobbler" 76ms

And I click on "Update" 415ms

And I follow the left menu "Admin > Task Engine Status > Last Execution Times" 490ms

Then I should see the correct timestamp for task "Cobbler Sync:" 10s 10ms

@skip_if_github_validation
Scenario:
Check for errors in Cobbler monitoring
7s 593ms 1

Then the local logs for Cobbler should not contain errors 7s 593ms

@skip_if_github_validation @scope_cobbler
Feature:Cobbler and distribution autoinstallation 2m 9s 120ms 26

Scenario:
Start Cobbler monitoring
16s 354ms 2

When I start local monitoring of Cobbler 13s 837ms

And I backup Cobbler settings file 2s 517ms

Scenario:
Log in as testing user
2s 639ms 2

Given I am authorized as "testing" with password "testing" 1s 743ms

And I am logged in via the Cobbler API as user "testing" with password "testing" 896ms

Scenario:
Copy cobbler profiles on the server
9s 287ms 1

When I copy autoinstall mocked files on server 9s 287ms

Scenario:
Ask cobbler to create a distribution via API
642ms 2

Given cobblerd is running 2ms

When I create "testdistro" kickstart tree via the API 639ms

Scenario:
Create dummy profile
966ms 2

Given cobblerd is running 2ms

When I create a "testprofile" profile via the API using import file for "testdistro" distribution 964ms

Scenario:
Check cobbler created distro and profile
344ms 3

When I follow the left menu "Systems > Autoinstallation > Profiles" 208ms

Then I should see a "testprofile" text 71ms

And I should see a "testdistro" text 64ms

Scenario:
Create SUSE distribution with installer updates
2s 215ms 12

When I follow the left menu "Systems > Autoinstallation > Distributions" 75ms

And I follow "Create Distribution" 316ms

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" 267ms

And I select "SUSE Linux Enterprise 15" from "installtype" 59ms

And I click on "Create Autoinstallable Distribution" 761ms

And I wait until I see "Autoinstallable Distribution Created" text 74ms

Then I should see a "Autoinstallable Distributions" text 67ms

And I should see a "SLE-15-FAKE" link 11ms

When I follow "SLE-15-FAKE" 403ms

Then I should see "self_update=http://" in field identified by "kernelopts" 22ms

Scenario:
Create a distribution via the UI
1s 322ms 8

When I follow the left menu "Systems > Autoinstallation > Distributions" 69ms

And I follow "Create Distribution" 909ms

When I enter "fedora_kickstart_distro" as "label" 67ms

And I enter "/var/autoinstall/Fedora_12_i386/" as "basepath" 75ms

And I select "Fedora" from "installtype" 56ms

And I click on "Create Autoinstallable Distribution" 53ms

Then I should see a "Autoinstallable Distributions" text 77ms

And I should see a "fedora_kickstart_distro" link 12ms

Scenario:
Create a distribution via the API, without kernel options
1s 352ms 3

When I create "fedora_kickstart_distro_api" kickstart tree via the API 1s 264ms

When I follow the left menu "Systems > Autoinstallation > Distributions" 75ms

Then I should see a "fedora_kickstart_distro_api" link 12ms

Scenario:
Create a distribution via the API, with kernel options
689ms 3

When I create a kickstart tree with kernel options via the API 607ms

When I follow the left menu "Systems > Autoinstallation > Distributions" 67ms

Then I should see a "fedora_kickstart_distro_kernel_api" link 15ms

Scenario:
Update a distribution via the API
1s 684ms 6

When I update a kickstart tree via the API 1s 186ms

When I follow the left menu "Systems > Autoinstallation > Distributions" 66ms

And I follow "fedora_kickstart_distro_api" 320ms

Then option "Generic RPM" is selected as "installtype" 69ms

And I should see "self_update=0" in field identified by "kernelopts" 19ms

And I should see "self_update=1" in field identified by "postkernelopts" 21ms

Scenario:
Create a profile via the UI
3s 354ms 10

When I follow the left menu "Systems > Autoinstallation > Profiles" 75ms

And I follow "Create Kickstart Profile" 309ms

When I enter "fedora_kickstart_profile" as "kickstartLabel" 72ms

And I click on "Next" 335ms

And I click on "Next" 377ms

And I enter "linux" as "rootPassword" 49ms

And I enter "linux" as "rootPasswordConfirm" 56ms

And I click on "Finish" 1s 978ms

Then I should see a "Autoinstallation: fedora_kickstart_profile" text 86ms

And I should see a "Autoinstallation Details" link 12ms

Scenario:
Upload a profile via the UI
3s 10ms 8

When I follow the left menu "Systems > Autoinstallation > Profiles" 70ms

And I follow "Upload Kickstart/AutoYaST File" 361ms

When I enter "fedora_kickstart_profile_upload" as "kickstartLabel" 80ms

And I select "fedora_kickstart_distro" from "kstreeId" 46ms

And I attach the file "/example.ks" to "fileUpload" 33ms

And I click on "Create" 2s 222ms

Then I should see a "Autoinstallation: fedora_kickstart_profile_upload" text 95ms

And I should see a "Autoinstallation Details" text 99ms

Scenario:
Add an unprovisioned range to the created profile
2s 604ms 13

When I follow the left menu "Systems > Autoinstallation > Profiles" 72ms

And I follow "fedora_kickstart_profile" 652ms

And I follow "Unprovisioned Autoinstallation" 400ms

And I enter "10" as "octet1a" 54ms

And I enter "10" as "octet1b" 50ms

And I enter "0" as "octet1c" 48ms

And I enter "100" as "octet1d" 50ms

And I enter "10" as "octet2a" 51ms

And I enter "10" as "octet2b" 49ms

And I enter "0" as "octet2c" 49ms

And I enter "200" as "octet2d" 51ms

And I click on "Add IP Range" 1s 4ms

Then I should see a "Successfully added IP Range" text 69ms

Scenario:
Add a variable to the uploaded profile
1s 810ms 7

When I follow the left menu "Systems > Autoinstallation > Profiles" 73ms

And I follow "fedora_kickstart_profile_upload" 674ms

And I follow "Variables" 376ms

And I enter "my_var=A_Test_String" as "variables" 70ms

And I click on "Update Variables" 61ms

And I follow "Autoinstallation File" 491ms

Then I should see a "A_Test_String" text 62ms

Scenario:
Add a kernel option to the created profile
3s 837ms 5

When I follow the left menu "Systems > Autoinstallation > Profiles" 86ms

And I follow "fedora_kickstart_profile" 538ms

And I enter "kernel_option=a_value" as "kernel_options" 80ms

And I click on "Update" 62ms

And I wait until file "/srv/tftpboot/pxelinux.cfg/default" contains "kernel_option=a_value" on server 3s 70ms

Scenario:
Add a kernel option to the uploaded profile
4s 631ms 5

When I follow the left menu "Systems > Autoinstallation > Profiles" 71ms

And I follow "fedora_kickstart_profile_upload" 574ms

And I enter "kernel_option2=a_value2" as "kernel_options" 68ms

And I click on "Update" 1s 261ms

And I wait until file "/srv/tftpboot/pxelinux.cfg/default" contains "kernel_option2=a_value2" on server 2s 654ms

Scenario:
Check default snippets
1s 296ms 6

When I follow the left menu "Systems > Autoinstallation > Autoinstallation Snippets" 78ms

And I follow "Default Snippets" 308ms

And I enter "spacewalk/sles_no_signature_checks" as the filtered snippet name 88ms

And I click on the filter button 494ms

And I follow "spacewalk/sles_no_signature_checks" 311ms

Then I should see "<signature-handling>" in the textarea 16ms

Scenario:
Create a snippet
1s 86ms 6

When I follow the left menu "Systems > Autoinstallation > Autoinstallation Snippets" 69ms

And I follow "Create Snippet" 284ms

And I enter "created_test_snippet" as "name" 67ms

And I enter "<test_element>a text string</test_element>" in the editor 5ms

And I click on "Create Snippet" 586ms

Then I should see a "created_test_snippet created successfully." text 73ms

Scenario:
Delete a snippet
1s 229ms 5

When I follow the left menu "Systems > Autoinstallation > Autoinstallation Snippets" 72ms

And I follow "created_test_snippet" 318ms

And I follow "Delete Snippet" 328ms

And I click on "Delete Snippet" 449ms

Then I should see a "created_test_snippet deleted successfully." text 60ms

Scenario:
Test for PXE environment files
19s 423ms 8

Given cobblerd is running 12ms

When I wait until file "/srv/tftpboot/pxelinux.cfg/default" exists on server 2s 526ms

And I wait until file "/srv/tftpboot/pxelinux.cfg/default" contains "inst.ks=.*fedora_kickstart_profile:1" on server 2s 594ms

And I wait until file "/srv/tftpboot/pxelinux.cfg/default" contains "inst.ks=.*fedora_kickstart_profile_upload:1" on server 2s 492ms

And I wait until file "/srv/tftpboot/images/fedora_kickstart_distro:1:SUSETest/initrd.img" exists on server 2s 471ms

And I wait until file "/srv/tftpboot/images/fedora_kickstart_distro:1:SUSETest/vmlinuz" exists on server 2s 497ms

And I wait until file "/srv/tftpboot/menu.c32" exists on server 4s 195ms

And I wait until file "/srv/tftpboot/pxelinux.0" exists on server 2s 632ms

Scenario:
Trigger the creation of a cobbler system record
7s 378ms 7

When I clear the caches on the server 2s 904ms

And I am on the Systems overview page of this "sle_minion" 991ms

And I follow "Provisioning" 739ms

And I click on profile "testprofile" 51ms

And I click on "Create PXE installation configuration" 56ms

Then I should see a "System record created" text 91ms

And I wait until file "/srv/tftpboot/pxelinux.cfg/01-*" contains "autoyast=" on server 2s 543ms

Scenario:
Create a cobbler system record via API
14s 130ms 5

When I create a system record 677ms

And I wait until file "/srv/tftpboot/pxelinux.cfg/01-00-22-22-77-ee-cc" contains "inst.ks=.*testserver:1" on server 3s 733ms

Then the cobbler report should contain "testserver.example.com" for cobbler system name "testserver:1" 3s 224ms

And the cobbler report should contain "1.1.1.1" for cobbler system name "testserver:1" 3s 284ms

And the cobbler report should contain "00:22:22:77:ee:cc" for cobbler system name "testserver:1" 3s 210ms

Scenario:
Cleanup: delete test profiles and distributions using API
15s 263ms 12

When I wait for "10" seconds 10s

When I delete profile and distribution using the API for "testdistro" kickstart tree 508ms

When I delete profile and distribution using the API for "fedora_kickstart_distro" kickstart tree 486ms

When I delete profile and distribution using the API for "fedora_kickstart_distro_api" kickstart tree 375ms

When I delete profile and distribution using the API for "fedora_kickstart_distro_kernel_api" kickstart tree 1s 107ms

When I delete profile and distribution using the API for "SLE-15-FAKE" kickstart tree 2s 351ms

When I follow the left menu "Systems > Autoinstallation > Distributions" 143ms

And I should not see a "testdistro" text 61ms

And I should not see a "fedora_kickstart_distro" text 58ms

And I should not see a "fedora_kickstart_distro_api" text 57ms

And I should not see a "fedora_kickstart_distro_kernel_api" text 56ms

And I should not see a "SLE-15-FAKE" text 57ms

@flaky
Scenario:
Check for errors in Cobbler monitoring
12s 558ms 2

When I wait for "5" seconds 5s

Then the local logs for Cobbler should not contain errors 7s 558ms

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 3m 40s 4ms 19

Builds several ISOs with Cobbler and checks the configuration files and ISOs afterwards.

Scenario:
Start Cobbler monitoring
15s 580ms 2

When I start local monitoring of Cobbler 12s 956ms

And I backup Cobbler settings file 2s 624ms

Scenario:
Log in as testing user in the Cobbler buildiso context
1s 325ms 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" 856ms

Scenario:
Copy cobbler profiles on the server in the Cobbler buildiso context
10s 544ms 1

When I copy autoinstall mocked files on server 10s 544ms

Scenario:
Create a dummy distro in the Cobbler buildiso context
58ms 2

Given cobblerd is running 2ms

When I create distro "buildisodistro" 55ms

Scenario:
Create dummy profiles in the Cobbler buildiso context
255ms 4

Given distro "buildisodistro" exists 3ms

When I create profile "orchid" for distro "buildisodistro" 74ms

And I create profile "flame" for distro "buildisodistro" 74ms

And I create profile "pearl" for distro "buildisodistro" 101ms

Scenario:
Check cobbler created a distro and profiles in the Cobbler buildiso context
477ms 5

When I follow the left menu "Systems > Autoinstallation > Profiles" 198ms

Then I should see a "buildisodistro" text 71ms

And I should see a "orchid" text 69ms

And I should see a "flame" text 68ms

And I should see a "pearl" text 69ms

Scenario:
Create dummy system in the Cobbler buildiso context
3s 258ms 3

Given profile "orchid" exists 8ms

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" 3s 198ms

Scenario:
Prepare the Cobbler buildiso context
9s 96ms 1

When I prepare Cobbler for the buildiso command 9s 96ms

Scenario:
Run Cobbler buildiso with all profiles and check isolinux config file in the Cobbler buildiso context
38s 226ms 4

When I run Cobbler buildiso for distro "buildisodistro" and all profiles 23s 554ms

And I check Cobbler buildiso ISO "profile_all" with xorriso 9s 459ms

And I check the Cobbler parameter "nameserver" with value "9.9.9.9" in the isolinux.cfg 2s 568ms

And I cleanup xorriso temp files 2s 643ms

Scenario:
Run Cobbler buildiso with selected profile in the Cobbler buildiso context
17s 209ms 3

When I run Cobbler buildiso for distro "buildisodistro" and profile "orchid" 4s 369ms

And I check Cobbler buildiso ISO "orchid" with xorriso 10s 354ms

And I cleanup xorriso temp files 2s 485ms

Scenario:
Run Cobbler buildiso with selected profile and without dns entries in the Cobbler buildiso context
19s 227ms 3

When I run Cobbler buildiso for distro "buildisodistro" and profile "orchid" without dns entries 9s 14ms

And I check Cobbler buildiso ISO "orchid" with xorriso 7s 608ms

And I cleanup xorriso temp files 2s 604ms

Scenario:
Run Cobbler buildiso airgapped with all profiles in the Cobbler buildiso context
45s 412ms 3

When I run Cobbler buildiso "airgapped" for distro "buildisodistro" 32s 967ms

And I check Cobbler buildiso ISO "airgapped" with xorriso 9s 944ms

And I cleanup xorriso temp files 2s 501ms

Scenario:
Run Cobbler buildiso standalone with all profiles in the Cobbler buildiso context
45s 742ms 3

When I run Cobbler buildiso "standalone" for distro "buildisodistro" 33s 586ms

And I check Cobbler buildiso ISO "standalone" with xorriso 9s 450ms

And I cleanup xorriso temp files 2s 706ms

Scenario:
Cleanup: delete test system in the Cobbler buildiso context
503ms 2

Given I am authorized as "testing" with password "testing" 481ms

When I remove system "testsystem" 21ms

Scenario:
Cleanup: delete test profile in the Cobbler buildiso context
1s 623ms 8

Given I am authorized as "testing" with password "testing" 1s 75ms

And I remove profile "orchid" 102ms

And I remove profile "flame" 67ms

And I remove profile "pearl" 33ms

When I follow the left menu "Systems > Autoinstallation > Profiles" 163ms

Then I should not see a "orchid" text 65ms

And I should not see a "flame" text 56ms

And I should not see a "flame" text 59ms

Scenario:
Cleanup: delete test distro in the Cobbler buildiso context
685ms 4

Given I am authorized as "testing" with password "testing" 443ms

And I remove distro "buildisodistro" 20ms

And I follow the left menu "Systems > Autoinstallation > Profiles" 157ms

Then I should not see a "buildisodistro" text 64ms

Scenario:
Cleanup: Remove buildiso tmpdir and built ISO file in the Cobbler buildiso context
3s 458ms 1

When I cleanup after Cobbler buildiso 3s 458ms

@flaky
Scenario:
Check for errors in Cobbler monitoring
7s 314ms 1

Then the local logs for Cobbler should not contain errors 7s 314ms

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 21s 718ms 12

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 2ms

Scenario:
Copy cobbler profiles on the server
12s 466ms 2

When I copy autoinstall mocked files on server 9s 950ms

And I backup Cobbler settings file 2s 516ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 2ms

Scenario:
Log in as testing user
10s 878ms 1

Given I am authorized as "testing" with password "testing" 10s 878ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 5ms

Scenario:
Start Cobbler monitoring
13s 170ms 1

When I start local monitoring of Cobbler 13s 170ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 3ms

Scenario:
Create a Cobbler distribution via the UI
1s 584ms 10

When I follow the left menu "Systems > Autoinstallation > Distributions" 211ms

And I follow "Create Distribution" 302ms

When I enter "isedistro_ui" as "label" 58ms

And I enter "/var/autoinstall/Fedora_12_i386/" as "basepath" 79ms

And I select "Fedora" from "installtype" 65ms

And I click on "Create Autoinstallable Distribution" 636ms

Then I should see a "Autoinstallable Distributions" text 69ms

And I should see a "isedistro_ui" link 12ms

When I follow the left menu "Systems > Autoinstallation > Distributions" 75ms

Then I should see a "isedistro_ui" text 74ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 2ms

Scenario:
Create a Cobbler profile via the UI
2s 133ms 12

When I follow the left menu "Systems > Autoinstallation > Profiles" 72ms

And I follow "Create Kickstart Profile" 621ms

When I enter "iseprofile_ui" as "kickstartLabel" 62ms

And I click on "Next" 364ms

And I click on "Next" 608ms

And I enter "linux" as "rootPassword" 51ms

And I enter "linux" as "rootPasswordConfirm" 54ms

And I click on "Finish" 60ms

Then I should see a "Autoinstallation: iseprofile_ui" text 83ms

And I should see a "Autoinstallation Details" link 12ms

When I follow the left menu "Systems > Autoinstallation > Profiles" 73ms

Then I should see a "iseprofile_ui" text 67ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 5ms

Scenario:
Change profile variables using the UI
11s 990ms 7

When I follow the left menu "Systems > Autoinstallation > Profiles" 65ms

And I follow "iseprofile_ui" 593ms

And I follow "Variables" 307ms

And I enter "ise_ui_test=ISE_UI_TEST" as "variables" 75ms

And I click on "Update Variables" 418ms

And I refresh the page 10s 460ms

Then I should see a "ISE_UI_TEST" text 68ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 12ms

Scenario:
Create a Cobbler distribution via the UI in the XML-RPC context
840ms 10

When I follow the left menu "Systems > Autoinstallation > Distributions" 73ms

And I follow "Create Distribution" 296ms

When I enter "isedistro_api" as "label" 56ms

And I enter "/var/autoinstall/Fedora_12_i386/" as "basepath" 78ms

And I select "Fedora" from "installtype" 49ms

And I click on "Create Autoinstallable Distribution" 52ms

Then I should see a "Autoinstallable Distributions" text 74ms

And I should see a "isedistro_api" link 12ms

When I follow the left menu "Systems > Autoinstallation > Distributions" 76ms

Then I should see a "isedistro_api" text 69ms

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
1s 569ms 12

When I follow the left menu "Systems > Autoinstallation > Profiles" 71ms

And I follow "Create Kickstart Profile" 381ms

When I enter "iseprofile_api" as "kickstartLabel" 59ms

And I click on "Next" 247ms

And I click on "Next" 426ms

And I enter "linux" as "rootPassword" 46ms

And I enter "linux" as "rootPasswordConfirm" 50ms

And I click on "Finish" 53ms

Then I should see a "Autoinstallation: iseprofile_api" text 83ms

And I should see a "Autoinstallation Details" link 8ms

When I follow the left menu "Systems > Autoinstallation > Profiles" 69ms

Then I should see a "iseprofile_api" text 70ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 7ms

Scenario:
Create a Cobbler system via the XML-RPC API
516ms 1

When I create a system record with name "isesystem_api" and kickstart label "iseprofile_api" 516ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 9ms

Scenario:
Create and modify a System profile using the XML-RPC API
1s 441ms 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 441ms
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 127ms 6

When I wait for "10" seconds 10s

When I delete profile and distribution using the API for "isedistro_ui" kickstart tree 500ms

When I delete profile and distribution using the API for "isedistro_api" kickstart tree 424ms

When I follow the left menu "Systems > Autoinstallation > Distributions" 71ms

And I should not see a "isedistro_ui" text 70ms

And I should not see a "isedistro_api" text 59ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 2ms

@flaky
Scenario:
Check for errors in Cobbler monitoring
13s 999ms 2

When I wait for "5" seconds 5s

Then the local logs for Cobbler should not contain errors 8s 999ms

@scope_visualization
Feature:Manage users 1m 37s 928ms 15 2

Scenario:
Log in as admin user
37s 945ms 1

Given I am authorized for the "Admin" section 37s 945ms

Scenario:
Display active users page
524ms 9

When I follow the left menu "Users > User List > Active" 210ms

Then I should see a "Active Users" text 182ms

And I should see a "Create User" link 12ms

And I should see a "User List" link in the left menu 24ms

And I should see a "Active" link in the left menu 23ms

And I should see a "Deactivated" link in the left menu 24ms

And I should see a "All" link in the left menu 25ms

And I should see a "admin" link in the table first column 10ms

And I should see a "Download CSV" link 11ms

Scenario:
Create a new user
9s 878ms 13

When I follow the left menu "Users > User List > Active" 74ms

And I follow "Create User" 296ms

And I enter "user1" as "login" 57ms

And I enter "user1" as "desiredpassword" 56ms

And I enter "user1" as "desiredpasswordConfirm" 57ms

And I select "Mr." from "prefix" 50ms

And I enter "Test" as "firstNames" 57ms

And I enter "User" as "lastName" 54ms

And I enter "galaxy-noise@localhost" as "email" 75ms

And I click on "Create Login" 8s 721ms

Then I should see a "Account user1 created, login information sent to galaxy-noise@localhost" text 180ms

And I should see a "user1" link 12ms

And I should see a "normal user" text 182ms

Scenario:
Login as the new user
1s 415ms 2

Given I am authorized as "user1" with password "user1" 1s 407ms

Then I should see a "user1" link 8ms

Scenario:
Access user details
2s 577ms 21

Given I am authorized for the "Admin" section 1s 135ms

When I follow the left menu "Users > User List > Active" 174ms

And I follow "user1" 504ms

Then I should see a "User Details" text 80ms

And I should see a "Delete User" link 11ms

And I should see a "Deactivate User" link 12ms

And I should see a "Details" link 14ms

And I should see a "System Groups" link 15ms

And I should see a "Systems" link in the content area 24ms

And I should see a "Channel Permissions" link 10ms

And I should see a "Preferences" link in the content area 21ms

And I should see a "Addresses" link 17ms

And I should see a "user1" text 71ms

And option "Mr." is selected as "prefix" 66ms

And I should see "Test" in field identified by "firstNames" 23ms

And I should see "User" in field identified by "lastName" 23ms

And I should see a "galaxy-noise@localhost" text 72ms

And I should see a "Administrative Roles" text 75ms

And I should see a "Roles:" text 74ms

And I should see a "Created:" text 72ms

And I should see a "Last Sign In:" text 76ms

@susemanager
Scenario:
Add roles
< 1ms 23

When I follow the left menu "Users > User List > Active" 0s

And I follow "user1" 0s

When the "role_satellite_admin" checkbox should be disabled 0s

And I check "role_org_admin" 0s

And I check "role_system_group_admin" 0s

And I check "role_channel_admin" 0s

And I check "role_activation_key_admin" 0s

And I check "role_config_admin" 0s

And I click on "Update" 0s

Then the "role_satellite_admin" checkbox should be disabled 0s

And I should see a "SUSE Multi-Linux Manager Administrator" text 0s

And I should see "role_org_admin" as checked 0s

And I should see a "Organization Administrator" text 0s

And I should see "role_system_group_admin" as checked 0s

And I should see a "System Group Administrator" text 0s

And I should see "role_channel_admin" as checked 0s

And I should see a "Channel Administrator" text 0s

And I should see "role_activation_key_admin" as checked 0s

And I should see a "Activation Key Administrator" text 0s

And I should see "role_config_admin" as checked 0s

And I should see a "Configuration Administrator" text 0s

And I should see "role_regular_user" as checked 0s

And I should see a "Regular User" text 0s

@uyuni
Scenario:
Add roles
22s 474ms 23

When I follow the left menu "Users > User List > Active" 72ms

And I follow "user1" 467ms

When the "role_satellite_admin" checkbox should be disabled 10s 2ms

And I check "role_org_admin" 79ms

And I check "role_system_group_admin" 74ms

And I check "role_channel_admin" 74ms

And I check "role_activation_key_admin" 75ms

And I check "role_config_admin" 75ms

And I click on "Update" 919ms

Then the "role_satellite_admin" checkbox should be disabled 10s 12ms

And I should see a "Uyuni Administrator" text 78ms

And I should see "role_org_admin" as checked 15ms

And I should see a "Organization Administrator" text 72ms

And I should see "role_system_group_admin" as checked 15ms

And I should see a "System Group Administrator" text 71ms

And I should see "role_channel_admin" as checked 15ms

And I should see a "Channel Administrator" text 72ms

And I should see "role_activation_key_admin" as checked 15ms

And I should see a "Activation Key Administrator" text 77ms

And I should see "role_config_admin" as checked 22ms

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 73ms

Scenario:
Verify user list
94ms 2

When I follow the left menu "Users > User List > Active" 69ms

Then table row for "user1" should contain "Organization Administrator" 25ms

Scenario:
Fail to deactivate organization administrator
1s 452ms 8

When I follow the left menu "Users > User List > Active" 72ms

And I follow "user1" 465ms

When I follow "Deactivate User" 404ms

Then I should see a "This action will deactivate this user. This user will no longer be able to log in or perform actions unless it is reactivated." text 54ms

When I click on "Deactivate User" 59ms

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 80ms

When I follow "Deactivated" 252ms

Then I should see a "No deactivated users." text 64ms

Scenario:
Remove role
11s 315ms 10

When I follow the left menu "Users > User List > Active" 68ms

And I follow "user1" 488ms

When I uncheck "role_org_admin" 10s 57ms

And I click on "Update" 604ms

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 16ms

And I should see "role_config_admin" as checked 17ms

And I should see "role_regular_user" as checked 15ms

Scenario:
Deactivate ordinary user
2s 495ms 13

When I follow the left menu "Users > User List > Active" 74ms

And I follow "user1" 483ms

Then I should see "role_org_admin" as unchecked 16ms

When I follow "Deactivate User" 402ms

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" 595ms

Then I should see a "Active Users" text 184ms

And I should not see a "user1" link 8ms

When I follow "Deactivated" 270ms

Then I should see a "Deactivated Users" text 67ms

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 647ms 11

When I follow the left menu "Users > User List > Active" 69ms

And I follow "Deactivated" 259ms

And I follow "user1" 375ms

Then I should see a "Reactivate User" link 11ms

When I follow "Reactivate User" 330ms

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 57ms

When I click on "Reactivate User" 65ms

Then I should see a "Active Users" text 188ms

And I should see a "user1" link 9ms

When I follow "Deactivated" 274ms

Then I should not see a "user1" link 5ms

Scenario:
Delete user
1s 765ms 8

When I follow the left menu "Users > User List > Active" 68ms

And I follow "user1" 497ms

When I follow "Delete User" 337ms

Then I should see a "Confirm User Deletion" text 54ms

And I should see a "This will delete this user permanently." text 51ms

When I click on "Delete User" 563ms

Then I should see a "Active Users" text 185ms

And I should not see a "user1" link 5ms

Scenario:
Display the CSV separator preference
2s 278ms 6

Given I am authorized as "testing" with password "testing" 1s 783ms

When I follow the left menu "Home > My Preferences" 68ms

Then I should see a "CSV Files" text 133ms

And I should see a "Configure a separator character to be used in downloadable CSV files:" text 96ms

And I should see a "Comma" text 96ms

And I should see a "Semicolon" text 99ms

Scenario:
Configure the CSV separator char to semicolon
1s 292ms 6

Given I am authorized as "testing" with password "testing" 512ms

When I follow the left menu "Home > My Preferences" 61ms

And I choose ";" 90ms

And I click on "Save Preferences" 500ms

Then I should see a "Preferences modified" text 106ms

And radio button "radio-semicolon" should be checked 20ms

Scenario:
Cleanup: configure the CSV separator char to comma
768ms 6

Given I am authorized as "testing" with password "testing" 470ms

When I follow the left menu "Home > My Preferences" 59ms

And I choose "," 53ms

And I click on "Save Preferences" 61ms

Then I should see a "Preferences modified" text 104ms

And radio button "radio-comma" should be checked 20ms

@scope_visualization
Feature:Web UI - Main landing page menu, texts and links 13s 839ms 43

Scenario:
Log in as admin user
2s 41ms 1

Given I am authorized for the "Admin" section 2s 41ms

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 30ms

Then I should see a "Overview" text 56ms

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 22ms

And I should see a "My Organization" link in the left menu 21ms

Scenario:
The user account submenu under the Home menu
250ms 6

When I follow the left menu "Home > User Account" 66ms

Then I should see a "My Account" text 92ms

And I should see a "My Account" link in the left menu 22ms

And I should see a "Addresses" link in the left menu 23ms

And I should see a "Change Email" link in the left menu 23ms

And I should see a "Account Deactivation" link in the left menu 21ms

Scenario:
The my orginization menu under the Home menu
198ms 5

When I follow the left menu "Home > My Organization" 65ms

Then I should see a "Organization Configuration" text 65ms

And I should see a "Configuration" link in the left menu 26ms

And I should see a "Organization Trusts" link in the left menu 20ms

And I should see a "Configuration Channels" link in the left menu 20ms

Scenario:
The Salt menu
184ms 5

When I follow the left menu "Salt" 57ms

Then I should see a "Keys" text 58ms

And I should see a "Keys" link in the left menu 23ms

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
167ms 4

When I follow the left menu "Content Lifecycle" 70ms

Then I should see a "Content Lifecycle Projects" text 53ms

And I should see a "Projects" link in the left menu 21ms

And I should see a "Filters" link in the left menu 23ms

Scenario:
The images menu
202ms 6

When I follow the left menu "Images" 54ms

Then I should see a "Images" text 62ms

And I should see a "Image List" link in the left menu 22ms

And I should see a "Build" link in the left menu 20ms

And I should see a "Profiles" link in the left menu 21ms

And I should see a "Stores" link in the left menu 21ms

Scenario:
The audit menu
230ms 6

When I follow the left menu "Audit" 53ms

Then I should see a "CVE Audit" text 90ms

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 20ms

And I should see a "OpenSCAP" link in the left menu 21ms

And I should see a "Confidential Computing" link in the left menu 20ms

Scenario:
The OpenSCAP submenu menu
203ms 5

When I follow the left menu "Audit > OpenSCAP" 73ms

Then I should see a "OpenSCAP Scans" text 60ms

And I should see a "All Scans" link in the left menu 24ms

And I should see a "XCCDF Diff" link in the left menu 22ms

And I should see a "Advanced Search" link in the left menu 21ms

Scenario:
The configuration menu
183ms 5

When I follow the left menu "Configuration" 57ms

Then I should see a "Configuration Overview" text 60ms

And I should see a "Overview" link in the left menu 20ms

And I should see a "Channels" link in the left menu 23ms

And I should see a "Files" link in the left menu 21ms

Scenario:
The files menu under the configuration menu
173ms 4

When I follow the left menu "Configuration > Files" 72ms

Then I should see a "Centrally-Managed Configuration Files" text 56ms

And I should see a "Centrally Managed" link in the left menu 22ms

And I should see a "Locally Managed" link in the left menu 22ms

Scenario:
The systems submenu in the configuration menu
167ms 4

When I follow the left menu "Configuration > Systems" 68ms

Then I should see a "Managed Systems" text 56ms

And I should see a "Managed" link in the left menu 22ms

And I should see a "Target" link in the left menu 20ms

Scenario:
The schedule menu
202ms 6

When I follow the left menu "Schedule" 55ms

Then I should see a "Pending Actions" text 61ms

And I should see a "Pending Actions" link in the left menu 22ms

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 20ms

And I should see a "Action Chains" link in the left menu 20ms

Scenario:
The users menu
395ms 8

When I follow the left menu "Users" 55ms

Then I should see a "Active Users" text 184ms

And I should see a "Users" link in the left menu 24ms

And I should see a "User List" link in the left menu 21ms

And I should see a "Active" link in the left menu 21ms

And I should see a "Deactivated" link in the left menu 21ms

And I should see a "All" link in the left menu 24ms

And I should see a "System Group Configuration" link in the left menu 41ms

Scenario:
The admin menu
323ms 10

When I follow the left menu "Admin" 56ms

Then I should see a "Setup Wizard" text 96ms

And I should see a "Setup Wizard" link in the left menu 23ms

And I should see a "Organizations" link in the left menu 22ms

And I should see a "Users" link in the left menu 19ms

And I should see a "Manager Configuration" link in the left menu 20ms

And I should see a "Hub Configuration" link in the left menu 20ms

And I should see a "Task Schedules" link in the left menu 20ms

And I should see a "Task Engine Status" link in the left menu 20ms

And I should see a "Show Tomcat Logs" link in the left menu 24ms

Scenario:
The Setup Wizard submenu of the admin menu
134ms 4

When I follow the left menu "Admin > Setup Wizard" 69ms

Then I should see a "HTTP Proxy" link in the left menu 22ms

And I should see a "Organization Credentials" link in the left menu 21ms

And I should see a "Products" link in the left menu 20ms

Scenario:
The manager configuration submenu of the admin menu
264ms 8

When I follow the left menu "Admin > Manager Configuration" 65ms

Then I should see a "Configuration - General Configuration" text 70ms

And I should see a "General" link in the left menu 24ms

And I should see a "Bootstrap Script" link in the left menu 21ms

And I should see a "Organizations" link in the left menu 18ms

And I should see a "Restart" link in the left menu 22ms

And I should see a "Cobbler" link in the left menu 21ms

And I should see a "Monitoring" link in the left menu 20ms

Scenario:
The Hub configuration submenu of the admin menu
193ms 5

When I follow the left menu "Admin > Hub Configuration" 63ms

Then I should see a "Peripherals Configuration" text 61ms

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 22ms

And I should see a "Access Tokens" link in the left menu 21ms

Scenario:
The Task Engine Status submenu of the admin menu
111ms 3

When I follow the left menu "Admin > Task Engine Status" 69ms

Then I should see a "Last Execution Times" link in the left menu 21ms

And I should see a "Runtime Status" link in the left menu 20ms

Scenario:
The menu direct link accesses the first submenu level only
738ms 6

When I follow the left menu "Patches > Patch List" 124ms

Then I should see a "Patches Relevant to Your Systems" text in the content area 239ms

And I should not see a "The following patch list represents all patches accessible by your organization." text in the content area 194ms

When I follow the left menu "Configuration > Files" 147ms

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 14ms

Scenario:
Idempotency of complete menu path and direct link
307ms 4

When I follow the left menu "Software > Manage" 114ms

Then I should see a "Software Channel Management" text in the content area 57ms

When I follow the left menu "Software > Manage > Channels" 80ms

Then I should see a "Software Channel Management" text in the content area 54ms

Scenario:
Completeness of the side navigation bar and the content frame
554ms 13

When I am on the Systems page 297ms

Then I should see a "Systems" text in the content area 27ms

And I should see a "All" link in the left menu 21ms

And I should see a "Systems" link in the left menu 25ms

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 28ms

And I should see a "Advanced Search" link in the left menu 22ms

And I should see a "Activation Keys" link in the left menu 22ms

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 22ms

And I should see a "Autoinstallation" link in the left menu 22ms

And I should see a "Download CSV" link 11ms

And I should see a Sign Out link 7ms

Scenario:
Sidebar link destination for Systems
256ms 7

When I follow the left menu "Systems > System List" 65ms

Then I should see a "All" link in the left menu 21ms

And I should see a "Virtual Systems" link in the left menu 26ms

And I should see a "Duplicate Systems" link in the left menu 24ms

And I should see a "System Currency" link in the left menu 22ms

And I should see a "System Types" link in the left menu 21ms

And I should see a "Systems" text 73ms

Scenario:
Sidebar link destination for Systems => Virtual Systems
173ms 3

When I follow the left menu "Systems > System List > Virtual Systems" 94ms

Then I should see a "Virtual Systems" text 75ms

And the current path is "/rhn/manager/systems/list/virtual" 4ms

Scenario:
Sidebar link destination for Systems => Duplicate Systems
194ms 7

When I follow the left menu "Systems > System List > Duplicate Systems" 77ms

Then I should see a "Duplicate Systems" text 68ms

And the current path is "/rhn/systems/DuplicateIPList.do" 3ms

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 11ms

And I should see a "Duplicate MAC Address" link 11ms

Scenario:
Sidebar link destination for Systems => System Currency
199ms 3

When I follow the left menu "Systems > System List > System Currency" 75ms

Then I should see a "System Currency Report" text 122ms

And the current path is "/rhn/systems/SystemCurrency.do" 2ms

Scenario:
Sidebar link destination for Systems => System Types
638ms 7

When I follow the left menu "Systems > System List > System Types" 77ms

Then I should see a "System Types" text 117ms

And I should see a "Management:" text 112ms

And I should see a "Salt:" text 111ms

And I should see a "Foreign:" text 110ms

And I should see a "Virtualization Host:" text 105ms

And the current path is "/rhn/systems/SystemEntitlements.do" 2ms

Scenario:
Sidebar link destination for Systems => System Groups
190ms 4

When I follow the left menu "Systems > System Groups" 64ms

Then I should see a "System Groups" text 58ms

And I should see a "Create Group" link 11ms

And I should see a "Your organization has no system groups." text 56ms

Scenario:
Sidebar link destination for Systems => System Set Manager
726ms 12

When I follow the left menu "Systems > System Set Manager > Overview" 442ms

Then I should see a "System Set Manager" text 81ms

And I should see a "Task Log" link in the left menu 22ms

And I should see a "Overview" link in the content area 20ms

And I should see a "Systems" link in the content area 16ms

And I should see a "Patches" link in the content area 22ms

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 19ms

And I should see a "Configuration" link in the content area 18ms

And I should see a "Provisioning" link in the content area 21ms

And I should see a "Misc" link in the content area 21ms

Scenario:
Sidebar link destination for Systems => Advanced Search
134ms 2

When I follow the left menu "Systems > Advanced Search" 63ms

Then I should see a "Advanced Search" text 70ms

Scenario:
Sidebar link destination for Systems => Activation Keys
239ms 4

When I follow the left menu "Systems > Activation Keys" 64ms

Then I should see a "Activation Keys" text 79ms

And I should see a "Create Key" link 12ms

And I should see a "The following activation keys have been created for use by your organization." text 83ms

Scenario:
Sidebar link destination for Systems => Stored Profiles
178ms 3

When I follow the left menu "Systems > Stored Profiles" 61ms

Then I should see a "Stored Profiles" text 60ms

And I should see a "No stored profiles." text 56ms

Scenario:
Sidebar link destination for Systems => Custom System Info
192ms 4

When I follow the left menu "Systems > Custom System Info" 67ms

Then I should see a "Custom System Info Keys" text 60ms

And I should see a "Create Key" link 8ms

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" 126ms

Then I should see a "Autoinstallation Overview" text 77ms

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 20ms

And I should see a "Distributions" link in the left menu 20ms

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 10ms

Scenario:
Sidebar link destination for Systems => Autoinstallation => Profiles
199ms 4

When I follow the left menu "Systems > Autoinstallation > Profiles" 75ms

Then I should see a "Autoinstallation Profiles" text 64ms

And I should see a "Create Kickstart Profile" link 32ms

And I should see a "Upload Kickstart/AutoYaST File" link 26ms

Scenario:
Sidebar link destination for Systems => Autoinstallation => Unprovisioned
197ms 3

When I follow the left menu "Systems > Autoinstallation > Unprovisioned" 74ms

Then I should see a "Unprovisioned Autoinstallation By IP" text 63ms

And I should see a "No Ip Ranges Found" text 59ms

Scenario:
Sidebar link destination for Systems => Autoinstallation => GPG and SSL Keys
168ms 5

When I follow the left menu "Systems > Autoinstallation > GPG and SSL Keys" 68ms

Then I should see a "GPG Public Keys and SSL Certificates" text 64ms

And I should see a "Create Stored Key/Cert" link 11ms

And I should see a "Reference Guide" link 12ms

And I should see a "RHN-ORG-TRUSTED-SSL-CERT" link 10ms

Scenario:
Sidebar link destination for Systems => Autoinstallation => Distributions
219ms 4

When I follow the left menu "Systems > Autoinstallation > Distributions" 71ms

Then I should see a "Autoinstallable Distributions" text 75ms

And I should see a "No autoinstallable distributions available." text 60ms

And I should see a "Create Distribution" link 11ms

Scenario:
Sidebar link destination for Systems => Autoinstallation => File Preservation
154ms 4

When I follow the left menu "Systems > Autoinstallation > File Preservation" 73ms

Then I should see a "File Preservation" text 61ms

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" 73ms

Then I should see a "Autoinstallation Snippets" text 62ms

And I should see a "No autoinstallation snippets found." text 63ms

And I should see a "Create Snippet" link 11ms

And I should see a "Default Snippets" link in the content area 21ms

And I should see a "Custom Snippets" link in the content area 21ms

And I should see a "All Snippets" link in the content area 20ms

Scenario:
"Create Kickstart Profile" page Systems => Autoinstallation => Profiles => Create Kickstart Profile
510ms 3

When I follow the left menu "Systems > Autoinstallation > Profiles" 67ms

And I follow "Create Kickstart Profile" 380ms

Then I should see a "Step 1: Create Kickstart Profile" text 62ms

Scenario:
"Upload Kickstart/AutoYaST File" page Systems => Autoinstallation => Profiles => Upload Kickstart/AutoYaST File
625ms 5

When I follow the left menu "Systems > Autoinstallation > Profiles" 68ms

And I follow "Upload Kickstart/AutoYaST File" 332ms

Then I should see a "Create Autoinstallation Profile" text 80ms

And I should see a "File Contents:" text 73ms

And I should see a "Autoinstallation Details" text 70ms

Scenario:
"Create kickstart distribution" page Systems => Autoinstallation => Distributions => create new kickstart distribution
514ms 4

When I follow the left menu "Systems > Autoinstallation > Distributions" 69ms

And I follow "Create Distribution" 304ms

Then I should see a "Create Autoinstallable Distribution" text 71ms

And I should see a "Distribution Label" text 68ms

@scope_configuration_channels
Feature:Check if source packages were successfully synced 6s 43ms 3

Scenario:
Log in as org admin user
1s 964ms 1

Given I am authorized 1s 964ms

Scenario:
Check sources for noarch package
2s 209ms 6

When I follow the left menu "Software > Channel List > All" 177ms

And I follow "Show All Child Channels" 74ms

And I follow "Fake-RPM-SUSE-Channel" 736ms

And I follow "Packages" 590ms

And I follow "virgo-dummy-2.0-1.1.noarch" 558ms

Then I should see a "virgo-dummy-2.0-1.1.src.rpm" text 72ms

Scenario:
Check sources for x86_64 package
1s 869ms 6

When I follow the left menu "Software > Channel List > All" 115ms

And I follow "Show All Child Channels" 56ms

And I follow "Fake-RPM-SUSE-Channel" 572ms

And I follow "Packages" 481ms

And I follow "blackhole-dummy-1.0-1.1.x86_64" 578ms

Then I should see a "blackhole-dummy-1.0-1.1.src.rpm" text 66ms

@scope_visualization
Feature:Change the user's password 15s 655ms 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 996ms 1

Given I am authorized for the "Admin" section 1s 996ms

Scenario:
Change the password to a new password
1s 294ms 10

When I follow the left menu "Home > User Account > My Account" 164ms

And I enter "GoodPass" as "desiredpassword" 69ms

And I enter "GoodPass" as "desiredpasswordConfirm" 57ms

And I click on "Update" 60ms

Then I should see a "User information updated" text 78ms

When I sign out 359ms

And I enter "admin" as "username" 51ms

And I enter "GoodPass" as "password" 56ms

And I click on "Sign In" 55ms

Then I should be logged in 341ms

Scenario:
Revert the new password to a valid standard password
1s 291ms 10

When I follow the left menu "Home > User Account > My Account" 117ms

And I enter "admin" as "desiredpassword" 51ms

And I enter "admin" as "desiredpasswordConfirm" 51ms

And I click on "Update" 52ms

Then I should see a "User information updated" text 75ms

When I sign out 408ms

And I enter "admin" as "username" 49ms

And I enter "admin" as "password" 53ms

And I click on "Sign In" 54ms

Then I should be logged in 377ms

Scenario:
Try an invalid password
11s 73ms 10

When I follow the left menu "Home > User Account > My Account" 117ms

And I enter "A" as "desiredpassword" 72ms

And I enter "A" as "desiredpasswordConfirm" 46ms

And I click on "Update" 308ms

Then I should see a "Passwords must be at least 4 characters." text 62ms

When I sign out 309ms

And I enter "admin" as "username" 51ms

And I enter "A" as "password" 47ms

And I click on "Sign In" 53ms

Then I should not be authorized 10s 5ms

@scope_configuration_channels
Feature:Clone a channel 37s 257ms 12

Scenario:
Log in as org admin user
10s 677ms 1

Given I am authorized 10s 677ms

Scenario:
Clone a channel without patches
2s 386ms 10

When I follow the left menu "Software > Manage > Channels" 182ms

And I follow "Clone Channel" 461ms

And I select "Fake-RPM-SUSE-Channel" as the origin channel 74ms

And I choose "original" 52ms

And I click on "Clone Channel" 445ms

And I enter "Fake-Clone-RPM-SLES15SP7-Channel" as "Channel Name" 119ms

And I should see a "Create Software Channel" text 79ms

And I should see a "Original state of the channel" text 82ms

And I click on "Clone Channel" 807ms

Then I should see a "Fake-Clone-RPM-SLES15SP7-Channel" text 79ms

Scenario:
Check that this channel has no patches
1s 548ms 5

When I follow the left menu "Software > Manage > Channels" 76ms

And I follow "Fake-Clone-RPM-SLES15SP7-Channel" 581ms

And I follow "Patches" in the content area 71ms

And I follow "List/Remove Patches" 760ms

Then I should see a "There are no patches associated with this channel." text 59ms

Scenario:
Clone a channel with patches
3s 8ms 10

When I follow the left menu "Software > Manage > Channels" 68ms

And I follow "Clone Channel" 563ms

And I select "Fake-RPM-SUSE-Channel" as the origin channel 62ms

And I choose "current" 51ms

And I click on "Clone Channel" 973ms

And I enter "Fake-Clone-2-RPM-SLES15SP7-Channel" as "Channel Name" 119ms

And I should see a "Create Software Channel" text 83ms

And I should see a "Current state of the channel" text 74ms

And I click on "Clone Channel" 930ms

Then I should see a "Fake-Clone-2-RPM-SLES15SP7-Channel" text 80ms

Scenario:
Check that this channel has patches
1s 526ms 8

When I follow the left menu "Software > Manage > Channels" 76ms

And I follow "Fake-Clone-2-RPM-SLES15SP7-Channel" 584ms

And I follow "Patches" in the content area 60ms

And I follow "List/Remove Patches" 759ms

Then I should see a "CL-hoag-dummy-7890" link 11ms

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 11ms

Scenario:
Clone a channel with selected patches
4s 638ms 18

When I follow the left menu "Software > Manage > Channels" 71ms

And I follow "Clone Channel" 470ms

And I select "Fake-RPM-SUSE-Channel" as the origin channel 53ms

And I choose "select" 50ms

And I click on "Clone Channel" 426ms

And I enter "Fake-Clone-3-RPM-SLES15SP7-Channel" as "Channel Name" 118ms

And I should see a "Create Software Channel" text 79ms

And I should see a "Select patches" text 76ms

And I click on "Clone Channel" 903ms

And I should see a "Fake-Clone-3-RPM-SLES15SP7-Channel" text 93ms

And I should see a "Channel Fake-Clone-3-RPM-SLES15SP7-Channel cloned from channel Fake-RPM-SUSE-Channel." text 89ms

And I should see a "You may now wish to clone the patches associated with Fake-RPM-SUSE-Channel." text 94ms

And I check the row with the "hoag-dummy-7890" link 63ms

And I check the row with the "virgo-dummy-3456" link 56ms

And I click on "Clone Patches" 960ms

And I click on "Confirm" 1s 13ms

Then I should see a "CL-hoag-dummy-7890" link 8ms

And I should see a "CL-virgo-dummy-3456" link 7ms

Scenario:
Check that new patches exists
1s 439ms 8

When I follow the left menu "Patches > Patch List > All" 185ms

And I enter "dummy" as the filtered synopsis 42ms

And I click on the filter button 700ms

And I select "500" from "1154021400_PAGE_SIZE_LABEL" 476ms

Then I should see a "CL-hoag-dummy-7890" link 10ms

And I should see a "CL-virgo-dummy-3456" link 8ms

And I should see a "CL-milkyway-dummy-2345" link 7ms

And I should see a "CL-andromeda-dummy-6789" link 7ms

Scenario:
Check CL-hoag-dummy-7890 patches
1s 855ms 8

When I follow the left menu "Patches > Patch List > All" 81ms

And I enter "dummy" as the filtered synopsis 37ms

And I click on the filter button 671ms

And I select "500" from "1154021400_PAGE_SIZE_LABEL" 481ms

And I follow "CL-hoag-dummy-7890" 449ms

Then I should see a "CL-hoag-dummy-7890 - Security Advisory" text 62ms

And I should see a "mcalmer" text 60ms

And I should see a "https://bugzilla.opensuse.org/show_bug.cgi?id=704608" link 11ms

Scenario:
Check CM-virgo-dummy-3456 patches
1s 951ms 8

When I follow the left menu "Patches > Patch List > All" 69ms

And I enter "dummy" as the filtered synopsis 37ms

And I click on the filter button 669ms

And I select "500" from "1154021400_PAGE_SIZE_LABEL" 483ms

And I follow "CL-virgo-dummy-3456" 555ms

Then I should see a "CL-virgo-dummy-3456 - Bug Fix Advisory" text 62ms

And I should see a "mcalmer" text 60ms

And I should see a "CVE-1999-9998" link 11ms

Scenario:
Compare channel packages
2s 327ms 9

When I follow the left menu "Software > Manage > Channels" 202ms

And I follow "Fake-Clone-2-RPM-SLES15SP7-Channel" 576ms

And I follow "Packages" in the content area 69ms

And I follow "Compare" 622ms

And I select "Fake-Clone-3-RPM-SLES15SP7-Channel" from "selected_channel" 64ms

And I click on "View Packages" 568ms

Then I should see a "andromeda-dummy" text 96ms

And I should see a "2.0-1.1" link 33ms

And I should see a "This channel only" text 92ms

Scenario:
Cleanup: remove cloned channels
5s 835ms 21

When I follow the left menu "Software > Manage > Channels" 71ms

And I follow "Fake-Clone-RPM-SLES15SP7-Channel" 568ms

And I follow "Delete Channel" 411ms

And I check "unsubscribeSystems" 80ms

And I click on "Delete Channel" 765ms

Then I should see a "Fake-Clone-RPM-SLES15SP7-Channel" text 65ms

And I should see a "has been deleted." text 60ms

Given I follow the left menu "Software > Manage > Channels" 77ms

When I follow "Fake-Clone-2-RPM-SLES15SP7-Channel" 598ms

And I follow "Delete Channel" 394ms

And I check "unsubscribeSystems" 69ms

And I click on "Delete Channel" 52ms

Then I should see a "Fake-Clone-2-RPM-SLES15SP7-Channel" text 73ms

And I should see a "has been deleted." text 59ms

Given I follow the left menu "Software > Manage > Channels" 72ms

When I follow "Fake-Clone-3-RPM-SLES15SP7-Channel" 951ms

And I follow "Delete Channel" 397ms

And I check "unsubscribeSystems" 65ms

And I click on "Delete Channel" 872ms

Then I should see a "Fake-Clone-3-RPM-SLES15SP7-Channel" text 65ms

And I should see a "has been deleted." text 60ms

Scenario:
Cleanup: remove remaining systems from SSM after channel cloning tests
62ms 1

When I click on the clear SSM button 62ms

Feature:Manipulate activation keys 15s 419ms 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 668ms 1

Given I am authorized 1s 668ms

Scenario:
Create an activation key for i586
1s 738ms 8

When I follow the left menu "Systems > Activation Keys" 121ms

And I follow "Create Key" 259ms

And I wait until I do not see "Loading..." text 254ms

And I enter "SUSE Test Key i586" as "description" 73ms

And I enter "SUSE-TEST-i586" as "key" 72ms

And I check "virtualization_host" 84ms

And I click on "Create Activation Key" 795ms

Then I should see a "Activation key SUSE Test Key i586 has been created." text 77ms

Scenario:
Change limit of the i586 activation key
2s 461ms 7

When I follow the left menu "Systems > Activation Keys" 68ms

And I follow "SUSE Test Key i586" 360ms

And I wait until I do not see "Loading..." text 572ms

And I enter "20" as "usageLimit" 51ms

And I click on "Update Activation Key" 1s 307ms

Then I wait until I see "Activation key SUSE Test Key i586 has been modified." text 75ms

And I should see "20" in field identified by "usageLimit" 25ms

Scenario:
Change the base channel of the i586 activation key
1s 814ms 6

When I follow the left menu "Systems > Activation Keys" 63ms

And I follow "SUSE Test Key i586" 439ms

And I wait until I do not see "Loading..." text 486ms

And I select "Fake-Base-Channel-i586" from "selectedBaseChannel" 72ms

And I click on "Update Activation Key" 681ms

Then I wait until I see "Activation key SUSE Test Key i586 has been modified." text 71ms

Scenario:
Delete the i586 activation key
1s 707ms 6

When I follow the left menu "Systems > Activation Keys" 64ms

And I follow "SUSE Test Key i586" in the content area 71ms

And I wait until I do not see "Loading..." text 560ms

And I follow "Delete Key" 325ms

And I click on "Delete Activation Key" 602ms

Then I should see a "Activation key SUSE Test Key i586 has been deleted." text 82ms

Scenario:
Create an activation key with a channel and a package list for i586
1s 771ms 12

When I follow the left menu "Systems > Activation Keys" 72ms

And I follow "Create Key" 250ms

And I wait until I do not see "Loading..." text 226ms

And I enter "SUSE Test PKG Key i586" as "description" 72ms

And I enter "SUSE-TEST-2-i586" as "key" 70ms

And I enter "20" as "usageLimit" 48ms

And I select "Fake-Base-Channel-i586" from "selectedBaseChannel" 55ms

And I click on "Create Activation Key" 59ms

And I follow "Packages" 333ms

And I enter "sed" as "packages" 50ms

And I click on "Update Activation Key" 473ms

Then I should see a "Activation key SUSE Test PKG Key i586 has been modified." text 59ms

Scenario:
Delete the i586 activation key with packages
1s 11ms 5

When I follow the left menu "Systems > Activation Keys" 65ms

And I follow "SUSE Test PKG Key i586" in the content area 71ms

And I follow "Delete Key" 319ms

And I click on "Delete Activation Key" 473ms

Then I should see a "Activation key SUSE Test PKG Key i586 has been deleted." text 80ms

@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 217ms 12

When I follow the left menu "Systems > Activation Keys" 68ms

And I follow "Create Key" 252ms

And I wait until I do not see "Loading..." text 226ms

And I enter "SUSE Test PKG Key x86_64" as "description" 73ms

And I enter "SUSE-TEST-x86_64" as "key" 68ms

And I enter "20" as "usageLimit" 50ms

And I select "openSUSE Tumbleweed (x86_64)" from "selectedBaseChannel" 58ms

And I click on "Create Activation Key" 921ms

And I follow "Packages" 333ms

And I enter "sed" as "packages" 49ms

And I click on "Update Activation Key" 54ms

Then I should see a "Activation key SUSE Test PKG Key x86_64 has been modified." text 60ms

@scc_credentials
Scenario:
Delete the x86_64 activation key with packages
1s 27ms 5

When I follow the left menu "Systems > Activation Keys" 67ms

And I follow "SUSE Test PKG Key x86_64" in the content area 70ms

And I follow "Delete Key" 320ms

And I click on "Delete Activation Key" 490ms

Then I should see a "Activation key SUSE Test PKG Key x86_64 has been deleted." text 79ms

@scope_api
Feature:API "activationkey" namespace 3s 659ms 4

Scenario:
List all activation keys
410ms 1

Then I should get some activation keys 410ms

Scenario:
Create activation key
1s 193ms 2

When I create an activation key with id "testkey", description "Key for testing", limit of 10 and contact method "default" 822ms

Then I should get the new activation key "1-testkey" 370ms

Scenario:
Activation key details
717ms 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" 360ms

Then I get the description "Key description" for the activation key "1-testkey" 356ms

Scenario:
Cleanup: delete activation key
1s 337ms 1

When I delete the activation key "1-testkey" 1s 337ms

@scope_visualization
Feature:Main landing page options and preferences 57s 847ms 10 2

Scenario:
Clear browser cookies for main landing page validation
16ms 1

When I clear browser cookies 16ms

Scenario:
Access the Login page
662ms 3

Given I am not authorized 438ms

When I go to the home page 205ms

Then I should see a "Sign In" text 18ms

@uyuni
Scenario:
Access the API Documentation
10s 520ms 4

Given I am not authorized 10s 185ms

When I go to the home page 135ms

And I follow "API Documentation" 149ms

Then I should see a "API Overview" text 49ms

@susemanager
Scenario:
Access the Copyright Notice
< 1ms 10

Given I am authorized 0s

When I follow the left menu "Help" 0s

And I switch to last opened window 0s

Then I should see a "SUSE Multi-Linux Manager Guides" text 0s

When I click on the Legal button 0s

And I wait until I see "Copyright Notice" text 0s

And I follow "Copyright Notice" 0s

Then I should see a "Copyright Notice" text 0s

And I should see a "SUSE Multi-Linux Manager LICENSE AGREEMENT" text 0s

When I close the last opened window 0s

@susemanager
Scenario:
Access the EULA
< 1ms 10

Given I am authorized 0s

When I follow the left menu "Help" 0s

And I switch to last opened window 0s

Then I should see a "SUSE Multi-Linux Manager Guides" text 0s

When I click on the Legal button 0s

And I wait until I see "End User License Agreement" text 0s

And I follow "End User License Agreement" 0s

Then I should see a "End User License Agreement" text 0s

And I should see a "End User License Agreement for SUSE Software" text 0s

When I close the last opened window 0s

Scenario:
Log into Uyuni
11s 7ms 6

Given I am not authorized 10s 234ms

When I go to the home page 179ms

And I enter "testing" as "username" 68ms

And I enter "testing" as "password" 59ms

And I click on "Sign In" 67ms

Then I should be logged in 399ms

Scenario:
Log out of Uyuni
13s 417ms 3

Given I am authorized 2s 609ms

When I sign out 805ms

Then I should not be authorized 10s 2ms

Scenario:
Top level bar
11s 701ms 7

Given I am authorized for the "Admin" section 10s 694ms

When I go to the home page 906ms

And I should see a "Manage" link 17ms

And I should see a "admin" text 54ms

And I should see a "SUSE Test" link 11ms

And I should see a "Preferences" link 10ms

And I should see a Sign Out link 7ms

Scenario:
Main menu as regular user
2s 372ms 15

Given I am authorized as "testing" with password "testing" 2s 219ms

Then I should see a "Home" link 11ms

And I should see a "Systems" link 13ms

And I should see a "Salt" link 10ms

And I should see a "Images" link 10ms

And I should see a "Patches" link 11ms

And I should see a "Software" link 10ms

And I should see a "Content Lifecycle" link 10ms

And I should see a "Audit" link 10ms

And I should see a "Configuration" link 12ms

And I should see a "Schedule" link 10ms

And I should see a "Users" link 10ms

And I should not see a "Admin" link 7ms

And I should see a "Help" link 11ms

And I should see a "External Links" link 10ms

Scenario:
Log in as admin user
3s 751ms 1

Given I am authorized for the "Admin" section 3s 751ms

Scenario:
Main menu as administrator
109ms 13

Then I should see a "Home" link 8ms

And I should see a "Systems" link 9ms

And I should see a "Salt" link 7ms

And I should see a "Images" link 8ms

And I should see a "Patches" link 8ms

And I should see a "Software" link 7ms

And I should see a "Audit" link 8ms

And I should see a "Configuration" link 11ms

And I should see a "Schedule" link 8ms

And I should see a "Users" link 7ms

And I should see a "Admin" link 7ms

And I should see a "Help" link 7ms

And I should see a "External Links" link 7ms

Scenario:
Main content
4s 288ms 8

Given I am authorized 2s 657ms

Then I should see a "Tasks" text 864ms

And I should see a "Inactive Systems" text 108ms

And I should see a "Most Critical Systems" text 143ms

And I should see a "Recently Scheduled Actions" text 130ms

And I should see a "Relevant Security Patches" text 125ms

And I should see a "System Group Name" text 126ms

And I should see a "Recently Registered Systems" text 132ms

@scope_api
Feature:API "user" namespace 26s 366ms 5

Scenario:
List users
6s 744ms 2

When I call user.list_users() 6s 744ms

Then I should get at least user "admin" < 1ms

Scenario:
List roles
330ms 2

When I call user.list_roles() on user "admin" 330ms

Then I should get at least one role that matches "_admin" suffix < 1ms

Scenario:
Create user
16s 757ms 4

When I make sure "testuser" is not present 7s 918ms

And I call user.create() with login "testuser" 1s 622ms

And I call user.list_users() 7s 216ms

Then I should get at least user "testuser" < 1ms

Scenario:
Role operations
2s 38ms 6

When I call user.add_role() on "testuser" with the role "org_admin" 559ms

And I call user.list_roles() on user "testuser" 445ms

Then I should get role "org_admin" < 1ms

When I call user.remove_role() on "testuser" with the role "org_admin" 533ms

And I call user.list_roles() on user "testuser" 501ms

Then I should not get role "org_admin" < 1ms

Scenario:
Cleanup: user tests
494ms 1

When I delete user "testuser" 494ms

@scope_salt
Feature:Endpoint to download packages 15s 167ms 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
4s 749ms 3

9fdba534f57a78acf1d42c76d3d783903863d507c20c1100f676508bc0bc2bed

Given I have a valid token for organization "1" 4s 694ms

When I try to download "virgo-dummy-2.0-1.1.noarch.rpm" from channel "fake-rpm-suse-channel" 55ms

Then the download should get no error < 1ms

Scenario:
Download package, user with an invalid token for the org
32ms 3

0e3e5d3bd76d3207d4b625b9ed5fb59a7ac7076ce2e92313332ed9a75c611c921a4ee5e043bb39adfd463ff70ccde724e65af6b176af661e76d1d41d44cd8280

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" 31ms

Then the download should get a 403 response < 1ms

Scenario:
Download package, user with an expired valid token for the org
2s 598ms 3

9fdba534f57a78acf1d42c76d3d783903863d507c20c1100f676508bc0bc2bed

Given I have an expired valid token for organization "1" 2s 557ms

When I try to download "virgo-dummy-2.0-1.1.noarch.rpm" from channel "fake-rpm-suse-channel" 41ms

Then the download should get a 403 response < 1ms

Scenario:
Download package, user with an non expired valid token for the org
2s 645ms 3

9fdba534f57a78acf1d42c76d3d783903863d507c20c1100f676508bc0bc2bed

Given I have a valid token expiring tomorrow for organization "1" 2s 611ms

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
2s 532ms 3

9fdba534f57a78acf1d42c76d3d783903863d507c20c1100f676508bc0bc2bed

Given I have a not yet usable valid token for organization "1" 2s 504ms

When I try to download "virgo-dummy-2.0-1.1.noarch.rpm" from channel "fake-rpm-suse-channel" 27ms

Then the download should get a 403 response < 1ms

Scenario:
Download package, user with a valid token for the org and specific channels
2s 581ms 3

9fdba534f57a78acf1d42c76d3d783903863d507c20c1100f676508bc0bc2bed

Given I have a valid token for organization "1" and channel "foobar" 2s 553ms

When I try to download "virgo-dummy-2.0-1.1.noarch.rpm" from channel "fake-rpm-suse-channel" 28ms

Then the download should get a 403 response < 1ms

@scope_building_container_images @no_auth_registry
Feature:Advanced content management 24s 755ms 8

Scenario:
Log in as docker user
1s 764ms 1

Given I am authorized as "docker" with password "docker" 1s 764ms

Scenario:
Create an image store as Docker admin
1s 292ms 6

When I follow the left menu "Images > Stores" 134ms

And I follow "Create" 305ms

And I enter "docker_admin" as "label" 96ms

And I enter the URI of the registry as "uri" 154ms

And I click on "create-btn" 68ms

Then I wait until table row contains a "galaxy-registry" text 532ms

@scc_credentials
Scenario:
Create a profile as Docker admin
3s 849ms 7

GITPROFILES: https://github.com/uyuni-project/uyuni.git#:testsuite/features/profiles/temporary

When I follow the left menu "Images > Profiles" 69ms

And I follow "Create" 340ms

And I enter "suse_docker_admin" as "label" 126ms

And I select "galaxy-registry" from "imageStore" 1s 126ms

And I select "1-SUSE-KEY-x86_64" from "activationKey" 1s 116ms

And I enter "Docker/serverhost" relative to profiles as "path" 1s 11ms

And I click on "create-btn" 58ms

Scenario:
Create a user without rights nor roles
11s 591ms 2

New user norole created with roles:

Given I am authorized for the "Admin" section 1s 904ms

When I create a user with name "norole" and password "norole" with roles "" 9s 686ms

Scenario:
Log in as docker user
1s 795ms 1

Given I am authorized as "docker" with password "docker" 1s 795ms

@scc_credentials
Scenario:
Cleanup: remove Docker profile
1s 292ms 6

Given I am authorized as "docker" with password "docker" 707ms

When I follow the left menu "Images > Profiles" 117ms

And I check the row with the "suse_docker_admin" text 162ms

And I click on "Delete" 74ms

And I click on the red confirmation button 69ms

And I should see a "Image profile has been deleted." text 161ms

Scenario:
Cleanup: remove image store
486ms 5

When I follow the left menu "Images > Stores" 60ms

And I check the row with the "docker_admin" text 115ms

And I click on "Delete" 60ms

And I click on the red confirmation button 87ms

And I should see a "Image store has been deleted." text 162ms

Scenario:
Cleanup: delete no role user
2s 683ms 2

Given I am authorized for the "Admin" section 1s 404ms

When I delete user "norole" 1s 278ms

@scope_visualization
Feature:Pick dates 17s 270ms 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 536ms 2

Given I am authorized 1s 652ms

And I am on the Systems overview page of this "sle_minion" 4s 884ms

Scenario:
Date picker is by default set to today
10s 185ms 3

When I follow "Remote Command" in the content area 75ms

And I open the date picker 83ms

Then the date picker title should be the current month and year 10s 27ms

Scenario:
Picking a time sets the hidden fields
547ms 8

When I follow "Details" in the content area 83ms

And I follow "Remote Command" in the content area 59ms

And I enter "ls" as "Script" 98ms

And I pick "2022-08-27" as date 102ms

And I pick "17:30" as time 126ms

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 4ms

@scope_visualization
Feature:Work with Union and Intersection buttons in the group list 25s 136ms 16

Scenario:
Log in as org admin user
1s 856ms 1

Given I am authorized 1s 856ms

Scenario:
Create a sles group
1s 227ms 6

When I follow the left menu "Systems > System Groups" 129ms

When I follow "Create Group" 400ms

And I enter "sles" as "name" 48ms

And I enter "SLES systems" as "description" 59ms

And I click on "Create Group" 517ms

Then I should see a "System group sles created." text 72ms

Scenario:
Add systems to the sles group
3s 215ms 6

When I follow the left menu "Systems > System Groups" 64ms

When I follow "sles" 691ms

And I follow "Target Systems" 812ms

And I check the "sle_minion" client 60ms

And I click on "Add Systems" 1s 495ms

Then I should see a "added to sles server group." text 91ms

@rhlike_minion
Scenario:
Create a rhlike group
585ms 6

When I follow the left menu "Systems > System Groups" 61ms

When I follow "Create Group" 290ms

And I enter "rhlike" as "name" 49ms

And I enter "Red Hat-like systems" as "description" 62ms

And I click on "Create Group" 56ms

Then I should see a "System group rhlike created." text 66ms

@rhlike_minion
Scenario:
Add systems to the rhlike group
3s 788ms 6

When I follow the left menu "Systems > System Groups" 64ms

When I follow "rhlike" 306ms

And I follow "Target Systems" 462ms

And I check the "rhlike_minion" client 1s 811ms

And I click on "Add Systems" 1s 46ms

Then I should see a "1 systems were added to rhlike server group." text 96ms

@deblike_minion
Scenario:
Create a deblike group
967ms 6

When I follow the left menu "Systems > System Groups" 63ms

When I follow "Create Group" 299ms

And I enter "deblike" as "name" 49ms

And I enter "Debian-like systems" as "description" 61ms

And I click on "Create Group" 53ms

Then I should see a "System group deblike created." text 439ms

@deblike_minion
Scenario:
Add systems to the deblike group
6s 552ms 6

When I follow the left menu "Systems > System Groups" 63ms

When I follow "deblike" 353ms

And I follow "Target Systems" 432ms

And I check the "deblike_minion" client 4s 333ms

And I click on "Add Systems" 1s 269ms

Then I should see a "1 systems were added to deblike server group." text 100ms

Scenario:
Add the sles group to SSM
229ms 4

When I follow the left menu "Systems > System Groups" 62ms

When I click on "Use in SSM" in row "sles" 71ms

And I should see a "Selected Systems List" text 70ms

And I should see "sle_minion" as link 24ms

@rhlike_minion
Scenario:
Add a union of 2 groups to SSM - Red Hat-like
697ms 6

When I follow the left menu "Systems > System Groups" 58ms

When I check "sles" in the list 57ms

And I check "rhlike" in the list 58ms

And I click on "Work With Union" 497ms

And I should see "sle_minion" as link 11ms

And I should see "rhlike_minion" as link 13ms

@rhlike_minion
Scenario:
Add an intersection of 2 groups to SSM - Red Hat-like
587ms 6

When I follow the left menu "Systems > System Groups" 60ms

When I check "sles" in the list 51ms

And I check "rhlike" in the list 51ms

And I click on "Work With Intersection" 407ms

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
612ms 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 56ms

And I click on "Work With Union" 415ms

And I should see "sle_minion" as link 15ms

And I should see "deblike_minion" as link 15ms

@deblike_minion
Scenario:
Add an intersection of 2 groups to SSM - Debian-like
580ms 6

When I follow the left menu "Systems > System Groups" 61ms

When I check "sles" in the list 52ms

And I check "deblike" in the list 51ms

And I click on "Work With Intersection" 401ms

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 306ms 5

When I follow the left menu "Systems > System Groups" 58ms

When I follow "sles" in the content area 71ms

And I follow "Delete Group" in the content area 64ms

And I click on "Confirm Deletion" 1s 39ms

Then I should see a "deleted" text 72ms

@rhlike_minion
Scenario:
Cleanup: remove the rhlike group
1s 363ms 5

When I follow the left menu "Systems > System Groups" 72ms

When I follow "rhlike" in the content area 66ms

And I follow "Delete Group" in the content area 59ms

And I click on "Confirm Deletion" 52ms

Then I should see a "deleted" text 1s 112ms

@deblike_minion
Scenario:
Cleanup: remove the deblike group
1s 500ms 5

When I follow the left menu "Systems > System Groups" 70ms

When I follow "deblike" in the content area 68ms

And I follow "Delete Group" in the content area 61ms

And I click on "Confirm Deletion" 1s 234ms

Then I should see a "deleted" text 65ms

Scenario:
Cleanup: remove remaining systems from SSM after group union and intersection tests
64ms 1

When I click on the clear SSM button 64ms

@scope_visualization @scope_onboarding
Feature:Custom system info key-value pairs 14s 437ms 7

Scenario:
Log in as org admin user
1s 988ms 1

Given I am authorized 1s 988ms

Scenario:
Create a new key
1s 91ms 7

When I follow the left menu "Systems > Custom System Info" 120ms

And I follow "Create Key" 273ms

And I should see a "Create Custom Info Key" text 56ms

And I enter "key-label" as "label" 57ms

And I enter "key-desc" as "description" 61ms

And I click on "Create Key" 457ms

Then I should see a "Successfully added 1 custom key." text 64ms

Scenario:
Add a value to a system
3s 436ms 9

When I follow the left menu "Systems > System List > All" 134ms

And I follow this "sle_minion" link 1s 150ms

And I follow "Custom Info" 457ms

And I follow "Create Value" 443ms

And I follow "key-label" 479ms

And I enter "key-value" as "value" 57ms

And I click on "Update Key" 635ms

Then I should see a "key-label" text 66ms

And I should see a "key-value" link 12ms

Scenario:
Edit the value
2s 781ms 9

When I follow the left menu "Systems > System List > All" 119ms

And I follow this "sle_minion" link 984ms

And I follow "Custom Info" 449ms

And I follow "key-value" 437ms

And I should see a "Edit Custom Value" text 68ms

And I enter "key-value-edited" as "value" 68ms

And I click on "Update Key" 577ms

Then I should see a "key-label" text 65ms

And I should see a "key-value-edited" link 12ms

Scenario:
Edit the key description
1s 59ms 6

When I follow the left menu "Systems > Custom System Info" 62ms

And I follow "key-label" 351ms

And I enter "key-desc-edited" as "description" 86ms

And I click on "Update Key" 487ms

Then I should see a "key-label" link 11ms

And I should see a "key-desc-edited" text 58ms

Scenario:
Delete the value
2s 936ms 8

When I follow the left menu "Systems > Custom System Info" 60ms

And I follow "key-label" 272ms

And I follow this "sle_minion" link 606ms

And I follow "Custom Info" 436ms

And I follow "key-value-edited" 464ms

And I follow "Delete Value" 437ms

And I click on "Remove Value" 594ms

Then I should see a "No custom information defined for this system." text 65ms

Scenario:
Delete the key
1s 142ms 5

When I follow the left menu "Systems > Custom System Info" 63ms

And I follow "key-label" 269ms

And I follow "Delete Key" 313ms

And I click on "Delete Key" 438ms

Then I should not see a "key-label" text 56ms

@scope_tomcat
Feature:Basic web security measures and recommendations 58ms 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
21ms 9

When I retrieve a "css" static resource 21ms

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
20ms 2

Given I retrieve a "javascript" static resource 20ms

Then the response header "X-WebKit-CSP" should not be present < 1ms

@scope_salt
Feature:Salt is configured and running 26s 56ms 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
2s 995ms 4

When I get the contents of the remote file "/etc/salt/master.d/susemanager.conf" 2s 994ms

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
9s 665ms 3

Then salt-api should be listening on local port 9080 2s 496ms

And salt-master should be listening on public port 4505 2s 679ms

And salt-master should be listening on public port 4506 4s 489ms

Scenario:
There are no top.sls files in certain folders
13s 395ms 10

When I run "ls /srv/susemanager/salt/top.sls" on "server" without error control 3s 342ms

Then the command should fail < 1ms

When I run "ls /srv/susemanager/salt/top.sls" on "server" without error control 2s 492ms

Then the command should fail < 1ms

When I run "ls /srv/susemanager/pillar/top.sls" on "server" without error control 2s 487ms

Then the command should fail < 1ms

When I run "ls /usr/share/susemanager/salt/top.sls" on "server" without error control 2s 503ms

Then the command should fail < 1ms

When I run "ls /usr/share/susemanager/pillar/top.sls" on "server" without error control 2s 569ms

Then the command should fail < 1ms

@scope_configuration_channels
Feature:The channels page 22s 982ms 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 788ms 1

Given I am authorized 10s 788ms

Scenario:
Completeness of the channels page
593ms 15

When I follow the left menu "Software > Channel List > All" 194ms

Then I should see a "Full Software Channel List" text 125ms

And I should see a "Channel List" link in the left menu 26ms

And I should see a "All" link in the left menu 25ms

And I should see a "Popular" link in the left menu 22ms

And I should see a "My Channels" link in the left menu 21ms

And I should see a "Shared" link in the left menu 21ms

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 22ms

And I should see a "All" link in the content area 23ms

And I should see a "Popular" link in the content area 17ms

And I should see a "My Channels" link in the content area 16ms

And I should see a "Shared" link in the content area 17ms

And I should see a "Retired" link in the content area 17ms

Scenario:
Popular channels
136ms 2

When I follow the left menu "Software > Channel List > Popular" 77ms

Then I should see a "Popular" text 58ms

Scenario:
Check packages in test channel
2s 89ms 10

When I follow the left menu "Software > Channel List > All" 74ms

And I follow "Show All Child Channels" 62ms

And I follow "Fake-RPM-SUSE-Channel" 767ms

And I follow "Packages" 657ms

Then I should see package "andromeda-dummy-2.0-1.1.noarch" 93ms

And I should see package "hoag-dummy-1.1-1.1.i586" 87ms

And I should see package "hoag-dummy-1.1-1.1.x86_64" 88ms

And I should see package "milkyway-dummy-2.0-1.1.i586" 85ms

And I should see package "milkyway-dummy-2.0-1.1.x86_64" 84ms

And I should see package "virgo-dummy-2.0-1.1.noarch" 85ms

Scenario:
Check package metadata
2s 101ms 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" 587ms

And I follow "Packages" 566ms

And I follow "andromeda-dummy-2.0-1.1.noarch" 544ms

Then I should see a "This is the andromeda dummy package used for testing SUSE Manager" text 72ms

And I should see a "Fake-RPM-SUSE-Channel" link 12ms

And I should see a "build.opensuse.org" text 63ms

And I should see a "SHA512sum:" text 63ms

And I should see a "packages/1/199/andromeda-dummy/2.0-1.1/noarch/19940cc4a9f0d38a038a4455b0f1cf1290c4a4296b27f5a62f4aae60585ac6e2677e88c3c3127d487116ed8d9b1787379e23aafac46bc14408864926bedee693/andromeda-dummy-2.0-1.1.noarch.rpm" text 65ms

Scenario:
Check package dependencies page
2s 506ms 9

When I follow the left menu "Software > Channel List > All" 114ms

And I follow "Show All Child Channels" 45ms

And I follow "Fake-RPM-SUSE-Channel" 590ms

And I follow "Packages" 568ms

And I follow "andromeda-dummy-2.0-1.1.noarch" 567ms

And I follow "Dependencies" 465ms

Then I should see a "pam" text 51ms

And I should see a "rpmlib(PayloadIsXz) <= 5.2-1" text 49ms

And I should see a "andromeda-dummy = 2.0-1.1" text 52ms

Scenario:
Check package change log page
2s 378ms 8

When I follow the left menu "Software > Channel List > All" 108ms

And I follow "Show All Child Channels" 46ms

And I follow "Fake-RPM-SUSE-Channel" 693ms

And I follow "Packages" 601ms

And I follow "andromeda-dummy-2.0-1.1.noarch" 452ms

And I follow "Change Log" 378ms

Then I should see a "mc@suse.de" text 47ms

And I should see a "version 2.0" text 49ms

Scenario:
Check package file list page
2s 388ms 9

When I follow the left menu "Software > Channel List > All" 109ms

And I follow "Show All Child Channels" 61ms

And I follow "Fake-RPM-SUSE-Channel" 611ms

And I follow "Packages" 505ms

And I follow "andromeda-dummy-2.0-1.1.noarch" 544ms

And I follow "File List" 382ms

Then I should see a "This package contains the following files." text 57ms

And I should see a "/usr/share/doc/packages/andromeda-dummy/COPYING" text 57ms

And I should see a "sha256: 32b1062f7da84967e7019d01ab805935caa7ab7321a7ced0e30ebe75e5df1670" text 57ms

@scope_visualization
Feature:Managing channels 11s 898ms 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
2s 305ms 1

Given I am authorized 2s 305ms

Scenario:
Fail when trying to add a duplicate channel
1s 305ms 10

When I follow the left menu "Software > Manage > Channels" 187ms

And I follow "Create Channel" 497ms

And I enter "Fake-Base-Channel-SUSE-like" as "Channel Name" 86ms

And I enter "fake-base-channel-suse-like" as "Channel Label" 84ms

And I select "None" from "Parent Channel" 57ms

And I select "x86_64" from "Architecture:" 49ms

And I enter "Base channel for testing" as "Channel Summary" 89ms

And I enter "No more desdcription for base channel." as "Channel Description" 97ms

And I click on "Create Channel" 67ms

Then I should see a "The channel name 'Fake-Base-Channel-SUSE-like' is already in use, please enter a different name" text 87ms

Scenario:
Fail when trying to use invalid characters in the channel label
771ms 7

When I follow the left menu "Software > Manage > Channels" 78ms

And I follow "Create Channel" 367ms

And I enter "test123" as "Channel Name" 63ms

And I enter "tesT123" as "Channel Label" 58ms

And I enter "test123" as "Channel Summary" 59ms

And I click on "Create Channel" 59ms

Then I should see a "Invalid channel label, please see the format described below" text 84ms

Scenario:
Fail when trying to use invalid characters in the channel name
1s 79ms 7

When I follow the left menu "Software > Manage > Channels" 75ms

And I follow "Create Channel" 366ms

And I enter "!test123" as "Channel Name" 61ms

And I enter "test123" as "Channel Label" 61ms

And I enter "test123" as "Channel Summary" 59ms

And I click on "Create Channel" 371ms

Then I should see a "Invalid channel name, please see the format described below" text 83ms

@scc_credentials
Scenario:
Fail when trying to use reserved names for channels
839ms 7

When I follow the left menu "Software > Manage > Channels" 74ms

And I follow "Create Channel" 408ms

And I enter "openSUSE-Leap-15.6-Pool for x86_64" as "Channel Name" 88ms

And I enter "test123" as "Channel Label" 61ms

And I enter "test123" as "Channel Summary" 63ms

And I click on "Create Channel" 61ms

Then I should see a "The channel name 'openSUSE-Leap-15.6-Pool for x86_64' is reserved, please enter a different name" text 81ms

@scc_credentials
Scenario:
Fail when trying to use reserved labels for channels
1s 125ms 7

When I follow the left menu "Software > Manage > Channels" 75ms

And I follow "Create Channel" 369ms

And I enter "test123" as "Channel Name" 72ms

And I enter "opensuse-leap-15.6-pool-x86_64" as "Channel Label" 82ms

And I enter "test123" as "Channel Summary" 58ms

And I click on "Create Channel" 384ms

Then I should see a "The channel label 'opensuse-leap-15.6-pool-x86_64' is reserved, please enter a different name" text 82ms

Scenario:
Create a channel that will be changed
946ms 7

When I follow the left menu "Software > Manage > Channels" 76ms

And I follow "Create Channel" 471ms

And I enter "aaaSLE-12-Cloud-Compute5-Pool for x86_64" as "Channel Name" 107ms

And I enter "sle-we12aaa-pool-x86_64-sap" as "Channel Label" 79ms

And I enter "test123" as "Channel Summary" 61ms

And I click on "Create Channel" 65ms

Then I should see a "Channel aaaSLE-12-Cloud-Compute5-Pool for x86_64 created." text 84ms

@scc_credentials
Scenario:
Fail when trying to change the channel name to a reserved name
1s 411ms 5

When I follow the left menu "Software > Manage > Channels" 78ms

And I follow "aaaSLE-12-Cloud-Compute5-Pool for x86_64" 570ms

And I enter "openSUSE-Leap-15.6-Pool for x86_64" as "Channel Name" 123ms

And I click on "Update Channel" 563ms

Then I should see a "The channel name 'openSUSE-Leap-15.6-Pool for x86_64' is reserved, please enter a different name" text 75ms

Scenario:
Cleanup: Delete created channel
2s 113ms 6

When I follow the left menu "Software > Manage > Channels" 81ms

And I follow "aaaSLE-12-Cloud-Compute5-Pool for x86_64" 663ms

And I follow "Delete Channel" 477ms

And I check "unsubscribeSystems" 84ms

And I click on "Delete Channel" 714ms

Then I should see a "Channel aaaSLE-12-Cloud-Compute5-Pool for x86_64 has been deleted." text 91ms

@scope_visualization
Feature:Left Menu Filter 2s 625ms 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 857ms 1

Given I am authorized for the "Admin" section 1s 857ms

Scenario:
Search a word and expect the right result
115ms 2

When I enter "Admin" as the left menu search field 88ms

Then I should see a "Admin" link in the left menu 27ms

Scenario:
Search a partial word and expect the right result
131ms 2

When I enter "Formula" as the left menu search field 109ms

Then I should see a "Formula Catalog" link in the left menu 21ms

Scenario:
Search a word with a different case and expect the right result
107ms 2

When I enter "saLT" as the left menu search field 81ms

Then I should see a "Salt" link in the left menu 26ms

@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
278ms 3

When I enter "Uyuni" as the left menu search field 86ms

Then I should see a "Uyuni Server" text 80ms

And I should see a "Uyuni Proxy" text 111ms

Scenario:
Search a non-existing word and expect no results
134ms 2

When I enter "Null" as the left menu search field 126ms

Then I should see left menu empty 8ms

@scope_api
Feature:API "channel" namespace and sub-namespaces 8s 958ms 10

Scenario:
Create a custom software channel
814ms 2

When I create the following channels: 379ms
LABEL NAME SUMMARY ARCH PARENT
foobar foobar foobar channel-x86_64

Then "foobar" should get listed with a call of listSoftwareChannels 434ms

Scenario:
Create a repository
1s 921ms 4

When I create a repo with label "foobar" and url 345ms

And I associate repo "foobar" with channel "foobar" 538ms

Then channel "foobar" should have attribute "last_modified" that is a date 516ms

And channel "foobar" should not have attribute "yumrepo_last_sync" 520ms

Scenario:
Create a custom software channel as the child of another one
1s 354ms 3

When I create the following channels: 404ms
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 386ms

And "foobar" should be the parent channel of "foobar-child" 564ms

Scenario:
List software channels
391ms 1

Then something should get listed with a call of listSoftwareChannels 391ms

Scenario:
Delete a child software channel
906ms 2

When I delete the software channel with label "foobar-child" 514ms

Then "foobar-child" should not get listed with a call of listSoftwareChannels 392ms

Scenario:
Delete a software channel
1s 257ms 3

When I delete the repo with label "foobar" 358ms

And I delete the software channel with label "foobar" 504ms

Then "foobar" should not get listed with a call of listSoftwareChannels 394ms

Scenario:
Check last synchronization of a synced channel
379ms 1

Then channel "fake-child-channel-i586" should have attribute "yumrepo_last_sync" that is a date 379ms

@rhlike_minion
Scenario:
Verify if a channel is modular via the API
789ms 2

When I verify channel "fake-base-channel-appstream" is modular via the API 358ms

And I verify channel "fake-rpm-suse-channel" is not modular via the API 431ms

@rhlike_minion
Scenario:
List modular channels via the API
495ms 1

When channel "Fake-Base-Channel-AppStream" is present in the modular channels listed via the API 495ms

@rhlike_minion
Scenario:
List available module streams for a given channel via the API
647ms 1

When "scorpio" module streams "2.0, 2.1" are available for channel "fake-base-channel-appstream" via the API 647ms

@scope_visualization
Feature:Patches page 13s 723ms 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
2s 198ms 1

Given I am authorized 2s 198ms

Scenario:
Patches left menu
480ms 11

When I follow the left menu "Patches > Patch List > Relevant" 189ms

Then I should see a "Patches Relevant to Your Systems" text 140ms

And I should see a "Relevant" link in the left menu 21ms

And I should see a "All" link in the left menu 23ms

And I should see a "Advanced Search" link in the left menu 21ms

And I should see a "Manage Patches" link in the left menu 20ms

And I should see a "Clone Patches" link in the left menu 23ms

And I should see a "Bugfix Patches" link 10ms

And I should see a "Enhancement Patches" link 10ms

And I should see a "Security Patches" link 10ms

And I should see a Sign Out link 7ms

Scenario:
Create new bugfix patch with bnc URL
2s 893ms 18

When I follow the left menu "Patches > Manage Patches" 67ms

And I follow "Create Patch" 334ms

When I enter "Test Patch" as "synopsis" 78ms

And I enter "Test Advisory" as "advisoryName" 86ms

And I enter "Test Product" as "product" 109ms

And I enter "test@test.org" as "errataFrom" 89ms

And I enter "Test Topic" as "topic" 76ms

And I enter "Test Description" as "description" 85ms

And I enter "Test Solution" as "solution" 82ms

And I enter "620212" as "buglistId" 66ms

And I enter "Test Summary" as "buglistSummary" 82ms

And I enter "https://bugzilla.opensuse.org/show_bug.cgi?id=620212" as "buglistUrl" 196ms

And I enter "test,keywords" as "keywords" 85ms

And I enter "Test Reference" as "refersTo" 81ms

And I enter "Test Note" as "notes" 72ms

And I check test channel 67ms

And I click on "Create Patch" 1s 151ms

Then I should see a "Patch: Test Advisory-1" text 79ms

Scenario:
Create new enhancement patch with no bnc URL
2s 725ms 17

When I follow the left menu "Patches > Manage Patches" 62ms

And I follow "Create Patch" 323ms

When I enter "Enhancement Patch" as "synopsis" 104ms

And I enter "Enhancement Advisory" as "advisoryName" 99ms

And I select "Product Enhancement Advisory" from "advisoryType" 81ms

And I enter "Enhancement Product" as "product" 104ms

And I enter "Enhancement Topic" as "topic" 94ms

And I enter "Enhancement Description" as "description" 98ms

And I enter "Enhancement Solution" as "solution" 91ms

And I enter "1234" as "buglistId" 57ms

And I enter "Enhancement Summary" as "buglistSummary" 92ms

And I enter "Enhancement,keywords" as "keywords" 94ms

And I enter "Enhancement Reference" as "refersTo" 94ms

And I enter "Enhancement Note" as "notes" 87ms

And I check test channel 58ms

And I click on "Create Patch" 1s 102ms

Then I should see a "Patch: Enhancement Advisory-1" text 76ms

Scenario:
Delete enhancement patch
1s 265ms 5

When I follow the left menu "Patches > Manage Patches" 63ms

And I check "Enhancement Advisory" patch 62ms

And I click on "Delete Patches" 461ms

And I click on "Confirm" 569ms

Then I should see a "Successfully deleted 1 patches." text 108ms

Scenario:
Verify patch presence in web UI
1s 866ms 15

When I follow the left menu "Patches > Patch List > All" 138ms

And I follow "Bugfix Patches" in the content area 77ms

And I enter "Test Patch" as the filtered synopsis 56ms

And I click on the filter button 611ms

And I follow "Test Advisory" 453ms

Then I should see a "Test Patch" text 61ms

And I should see a "test@test.org" text 62ms

And I should see a "Test Topic" text 62ms

And I should see a "Test Description" text 59ms

And I should see a "Test Solution" text 65ms

And I should see a "Fake-Base-Channel-SUSE-like" link 12ms

And I should see a "Test Summary" link 12ms

And I should see a "keywords, test" text 59ms

And I should see a "Test Reference" text 59ms

And I should see a "Test Note" text 73ms

Scenario:
Assert that patch is now in test base channel
888ms 4

When I follow the left menu "Software > Channel List > All" 179ms

And I follow "Fake-Base-Channel-SUSE-like" 575ms

And I follow "Patches" in the content area 65ms

Then I should see a "Test Patch" text 68ms

Scenario:
Delete patch
1s 405ms 5

When I follow the left menu "Patches > Manage Patches" 105ms

And I check "Test Advisory" patch 57ms

And I click on "Delete Patches" 527ms

And I click on "Confirm" 48ms

Then I should see a "Successfully deleted 1 patches." text 666ms

@scc_credentials @scope_content_lifecycle_management
Feature:Content lifecycle 10m 50s 354ms 46 4

Scenario:
Log in as org admin user
1s 750ms 1

Given I am authorized 1s 750ms

Scenario:
Create CLM filter to remove all fonts packages
3s 147ms 10

When I follow the left menu "Content Lifecycle > Filters" 122ms

And I click on "Create Filter" 87ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 11ms

Then I should see a "Create a new filter" text 69ms

And I enter "remove fonts packages" as "filter_name" 130ms

And I select "Package (Name)" from "type" 1s 139ms

And I select "contains" from "matcher" 1s 120ms

And I enter "fonts" as "name" 83ms

And I click on "Save" in "Create a new filter" modal 321ms

Then I should see a "remove fonts packages" text 60ms

Scenario:
Create a content lifecycle project
1s 479ms 9

When I follow the left menu "Content Lifecycle > Projects" 67ms

And I follow "Create Project" 416ms

Then I should see a "Create a new Content Lifecycle Project" text 68ms

And I should see a "Project Properties" text 49ms

When I enter "clp_label" as "label" 67ms

And I enter "clp_name" as "name" 59ms

And I enter "clp_desc" as "description" 64ms

And I click on "Create" 66ms

And I wait until I see "Content Lifecycle Project - clp_name" text 617ms

Scenario:
Verify the content lifecycle project page
882ms 9

When I follow the left menu "Content Lifecycle > Projects" 60ms

Then I should see a "clp_name" text 56ms

And I should see a "clp_desc" text 59ms

When I follow "clp_name" 397ms

Then I should see a "Project Properties" text 63ms

And I should see a "Versions history" text 62ms

And I should see a "Sources" text 64ms

And I should see a "Filters" text 58ms

And I should see a "Environment Lifecycle" text 59ms

@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 300ms 8

When I follow the left menu "Content Lifecycle > Projects" 61ms

And I follow "clp_name" 485ms

And I click on "Attach/Detach Sources" 74ms

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 123ms

And I click on "Save" 87ms

And I wait until I see "openSUSE Tumbleweed (x86_64)" text 284ms

Then I should see a "Version 1: (draft - not built) - Check the changes below" text 62ms

@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
617ms 4

When I follow the left menu "Content Lifecycle > Projects" 63ms

And I follow "clp_name" 424ms

Then I should see a "openSUSE Tumbleweed (x86_64)" text 66ms

And I should see a "Build (1)" text 62ms

Scenario:
Add fonts packages filter to the project
1s 189ms 10

When I follow the left menu "Content Lifecycle > Projects" 61ms

And I follow "clp_name" 393ms

Then I should see a "Content Lifecycle Project - clp_name" text 65ms

When I click on "Attach/Detach Filters" 68ms

And I check the "remove fonts packages" CLM filter 162ms

And I click on "Save" 54ms

And I wait until I see "Deny" text 193ms

Then I should see a "remove fonts packages" text 64ms

When I follow the left menu "Content Lifecycle > Filters" 64ms

Then I should see a "clp_name" text 61ms

Scenario:
Add environments to the project
3s 836ms 25

When I follow the left menu "Content Lifecycle > Projects" 59ms

And I follow "clp_name" 357ms

Then I should see a "No environments created" text 70ms

When I click on "Add Environment" 75ms

And I enter "dev_name" as "name" 79ms

And I enter "dev_label" as "label" 76ms

And I enter "dev_desc" as "description" 70ms

And I click on "Save" 59ms

Then I wait until I see "dev_name" text 313ms

And I should see a "dev_desc" text 73ms

When I click on "Add Environment" 73ms

And I enter "prod_name" as "name" 79ms

And I enter "prod_label" as "label" 79ms

And I enter "prod_desc" as "description" 75ms

And I click on "Save" 57ms

Then I wait until I see "prod_name" text 343ms

And I should see a "prod_desc" text 76ms

When I click on "Add Environment" 67ms

And I enter "qa_name" as "name" 76ms

And I enter "qa_label" as "label" 76ms

And I enter "qa_desc" as "description" 72ms

And I select "prod_name" from "predecessorLabel" 1s 124ms

And I click on "Save" 59ms

Then I wait until I see "qa_name" text 244ms

And I should see a "qa_desc" text 91ms

@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
1m 1s 824ms 9

When I follow the left menu "Content Lifecycle > Projects" 60ms

And I follow "clp_name" 585ms

Then I should see a "not built" text in the environment "qa_name" 23ms

When I click on "Build (2)" 108ms

Then I should see a "Version 1 history" text 95ms

When I enter "test version message 1" as "message" 66ms

And I click the environment build button 59ms

And I wait until I see "Version 1: test version message 1" text in the environment "dev_name" 418ms

And I wait at most 600 seconds until I see "Built" text in the environment "dev_name" 1m 407ms

Scenario:
Promote the sources in the project
1m 57s 516ms 15

When I follow the left menu "Content Lifecycle > Projects" 82ms

Then I should see a "clp_name" text 61ms

And I should see a "clp_desc" text 54ms

And I should see a "dev_name > qa_name > prod_name" text 54ms

When I follow "clp_name" 401ms

Then I should see a "qa_desc" text in the environment "qa_name" 22ms

And I should see a "not built" text in the environment "qa_name" 18ms

When I click promote from Development to QA 61ms

Then I should see a "Version 1: test version message 1" text 96ms

And I click on "Promote environment" in "Promote version 1 into qa_name" modal 338ms

Then I wait at most 600 seconds until I see "Built" text in the environment "qa_name" 1m 440ms

When I click promote from QA to Production 66ms

Then I should see a "Version 1: test version message 1" text 98ms

And I click on "Promote environment" in "Promote version 1 into prod_name" modal 346ms

Then I wait at most 600 seconds until I see "Built" text in the environment "prod_name" 55s 372ms

@skip_if_github_validation
Scenario:
Add new sources and promote again
3m 1s 249ms 27

When I follow the left menu "Content Lifecycle > Projects" 81ms

And I follow "clp_name" 514ms

Then I should see a "Build (0)" text 110ms

When I click on "Attach/Detach Sources" 89ms

And I uncheck "Vendors" 11s 328ms

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 77ms

And I click on "Save" 71ms

Then I wait until I see "Fake-Base-Channel-SUSE-like" text 391ms

And I wait until I see "Build (1)" text 92ms

And I should see a "Version 2: (draft - not built) - Check the changes below" text 97ms

When I click on "Build (1)" 69ms

Then I wait until I see "Version 2 history" text 96ms

When I enter "test version message 2" as "message" 64ms

And I click the environment build button 90ms

Then I wait until I see "Version 2: test version message 2" text in the environment "dev_name" 356ms

And I wait at most 600 seconds until I see "Built" text in the environment "dev_name" 45s 430ms

When I click promote from Development to QA 65ms

Then I should see a "Version 2: test version message 2" text 108ms

And I click on "Promote environment" in "Promote version 2 into qa_name" modal 496ms

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 436ms

When I click promote from QA to Production 63ms

Then I should see a "Version 2: test version message 2" text 95ms

And I click on "Promote environment" in "Promote version 2 into prod_name" modal 462ms

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 428ms

Scenario:
Create a CLM filter of type Package(NEVRA) that allows packages whose version and release number are lower to a defined one
13s 833ms 15

When I follow the left menu "Content Lifecycle > Filters" 81ms

And I click on "Create Filter" 71ms

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 72ms

When I enter "mercury" as "filter_name" 77ms

And I select "Package (NEVRA)" from "type" 1s 131ms

And I select "lower" from "matcher" 1s 118ms

And I enter "mercury" as "Package Name" 95ms

And I enter "mercury" as "Epoch" 90ms

And I enter "0.0.0" as "version" 72ms

And I enter "0.0.0" as "Release" 87ms

And I enter "x86_64" as "Architecture" 88ms

And I check radio button "Allow" 10s 64ms

And I click on "Save" in "Create a new filter" modal 704ms

Then I should see a "Filter created successfully" text 63ms

Scenario:
Create a CLM filter of type Package(NEVRA) that denys packages whose version and release number are lower to a defined one
3s 175ms 15

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 61ms

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 72ms

When I enter "venus" as "filter_name" 61ms

And I select "Package (NEVRA)" from "type" 1s 123ms

And I select "lower" from "matcher" 1s 103ms

And I enter "venus" as "Package Name" 78ms

And I enter "venus" as "Epoch" 74ms

And I enter "0.0.0" as "version" 69ms

And I enter "0.0.0" as "Release" 78ms

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 214ms

Then I should see a "Filter created successfully" text 64ms

Scenario:
Create CLM filter that allows packages of type Package (Provides Name)
2s 904ms 10

When I follow the left menu "Content Lifecycle > Filters" 62ms

And I click on "Create Filter" 61ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 74ms

When I enter "cereal" as "filter_name" 61ms

And I select "Package (Provides Name)" from "type" 1s 133ms

And I select "provides name" from "matcher" 1s 113ms

And I enter "cereal" as "Provides Name" 84ms

And I click on "Save" in "Create a new filter" modal 236ms

Then I should see a "Filter created successfully" text 66ms

Scenario:
Create CLM filter that denys packages of type Package (Provides Name)
2s 912ms 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 62ms

And I click on "Create Filter" 76ms

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 "potato" as "filter_name" 60ms

And I select "Package (Provides Name)" from "type" 1s 127ms

And I select "provides name" from "matcher" 1s 97ms

And I enter "potato" as "Provides Name" 79ms

And I check radio button "Deny" 16ms

And I click on "Save" in "Create a new filter" modal 231ms

Then I should see a "Filter created successfully" text 73ms

Scenario:
Create CLM filter of type Package (Build date) that allows packages whose date is lower than a defined one
12s 917ms 10

When I follow the left menu "Content Lifecycle > Filters" 60ms

And I click on "Create Filter" 61ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 87ms

When I enter "cherry" as "filter_name" 59ms

And I select "Package (Build date)" from "type" 1s 140ms

And I select "lower" from "matcher" 1s 104ms

And I check radio button "Allow" 10s 78ms

And I click on "Save" in "Create a new filter" modal 244ms

Then I should see a "Filter created successfully" text 73ms

Scenario:
Create CLM filter of type Package (Build date) that denys packages whose date is lower than a defined one
2s 873ms 10

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 61ms

And I click on "Create Filter" 65ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 9ms

Then I should see a "Create a new filter" text 85ms

When I enter "drummer" as "filter_name" 64ms

And I select "Package (Build date)" from "type" 1s 120ms

And I select "lower" from "matcher" 1s 108ms

And I check radio button "Deny" 16ms

And I click on "Save" in "Create a new filter" modal 260ms

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 16ms 11

When I follow the left menu "Content Lifecycle > Filters" 61ms

And I click on "Create Filter" 65ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 87ms

When I enter "africa-patch" as "filter_name" 77ms

And I select "Patch (Advisory Name)" from "type" 1s 129ms

And I select "equals" from "matcher" 1s 101ms

And I enter "africa" as "Advisory name" 86ms

And I check radio button "Allow" 10s 73ms

And I click on "Save" in "Create a new filter" modal 244ms

Then I should see a "Filter created successfully" text 80ms

Scenario:
Create CLM filter of type Patch(Advisory Name) that denys patches that are equal to a defined one
2s 943ms 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 66ms

And I click on "Create Filter" 63ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 94ms

When I enter "asia-patch" as "filter_name" 79ms

And I select "Patch (Advisory Name)" from "type" 1s 112ms

And I select "equals" from "matcher" 1s 108ms

And I enter "asia" as "Advisory name" 77ms

And I check radio button "Deny" 16ms

And I click on "Save" in "Create a new filter" modal 235ms

Then I should see a "Filter created successfully" text 81ms

Scenario:
Create CLM filter of type Patch(Advisory Type) that allows Security Advisory patches that are equal to a defined one
12s 947ms 11

Warning: Radio button 'Security Advisory' is already checked

When I follow the left menu "Content Lifecycle > Filters" 62ms

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 94ms

When I enter "key" as "filter_name" 52ms

And I select "Patch (Advisory Type)" from "type" 1s 130ms

And I select "equals" from "matcher" 1s 107ms

And I check radio button "Security Advisory" 20ms

And I check radio button "Allow" 10s 71ms

And I click on "Save" in "Create a new filter" modal 242ms

Then I should see a "Filter created successfully" text 85ms

Scenario:
Create CLM filter of type Patch(Advisory Type) that denys Security Advisory patches that are equal to a defined one
2s 945ms 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" 63ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 98ms

When I enter "geminis-patch" as "filter_name" 81ms

And I select "Patch (Advisory Type)" from "type" 1s 126ms

And I select "equals" from "matcher" 1s 101ms

And I check radio button "Security Advisory" 17ms

And I check radio button "Deny" 16ms

And I click on "Save" in "Create a new filter" modal 283ms

Then I should see a "Filter created successfully" text 88ms

Scenario:
Create CLM filter of type Patch(Synopsis) that allows patches that that are equal to a defined one
13s 61ms 11

When I follow the left menu "Content Lifecycle > Filters" 62ms

And I click on "Create Filter" 67ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 101ms

When I enter "aries-patch" as "filter_name" 74ms

And I select "Patch (Synopsis)" from "type" 1s 125ms

And I select "equals" from "matcher" 1s 109ms

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 91ms

Scenario:
Create CLM filter of type Patch(Synopsis) that denys patches that are equal to a defined one
3s 85ms 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 63ms

And I click on "Create Filter" 84ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 23ms

Then I should see a "Create a new filter" text 103ms

When I enter "andromeda-patch" as "filter_name" 90ms

And I select "Patch (Synopsis)" from "type" 1s 119ms

And I select "equals" from "matcher" 1s 113ms

And I enter "andromeda" as "Synopsis" 98ms

And I check radio button "Deny" 16ms

And I click on "Save" in "Create a new filter" modal 278ms

Then I should see a "Filter created successfully" text 94ms

Scenario:
Create CLM filter of type Patch(Keyword) that allows patches that contains Package Manager Restart Required keyword in its name
23s 87ms 11

When I follow the left menu "Content Lifecycle > Filters" 60ms

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 105ms

When I enter "mars-patch" as "filter_name" 73ms

And I select "Patch (Keyword)" from "type" 1s 125ms

And I select "contains" from "matcher" 1s 122ms

And I check radio button "Package Manager Restart Required" 10s 89ms

And I check radio button "Allow" 10s 75ms

And I click on "Save" in "Create a new filter" modal 263ms

Then I should see a "Filter created successfully" text 97ms

Scenario:
Create CLM filter of type Patch(Keyword) that denys patches that contains Package Manager Restart Required Keyword in its name
13s 44ms 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 62ms

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 107ms

When I enter "eurasia-patch" as "filter_name" 83ms

And I select "Patch (Keyword)" from "type" 1s 118ms

And I select "contains" from "matcher" 1s 115ms

And I check radio button "Package Manager Restart Required" 10s 74ms

And I check radio button "Deny" 22ms

And I click on "Save" in "Create a new filter" modal 284ms

Then I should see a "Filter created successfully" text 100ms

Scenario:
Create CLM filter of type Patch(Issue date) that allows patches whose date is greater or equal than a defined one
13s 77ms 10

When I follow the left menu "Content Lifecycle > Filters" 65ms

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 115ms

When I enter "milkyway-patch" as "filter_name" 89ms

And I select "Patch (Issue date)" from "type" 1s 149ms

And I select "greater or equal" from "matcher" 1s 120ms

And I check radio button "Allow" 10s 66ms

And I click on "Save" in "Create a new filter" modal 291ms

Then I should see a "Filter created successfully" text 103ms

Scenario:
Create CLM filter of type Patch(Issue date) that denys patches whose date is greater or equal than a defined one
3s 116ms 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 58ms

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 113ms

When I enter "venus-patch" as "filter_name" 78ms

And I select "Patch (Issue date)" from "type" 1s 143ms

And I select "greater or equal" from "matcher" 1s 108ms

When I enter "solar" as "filter_name" 143ms

And I check radio button "Deny" 17ms

And I click on "Save" in "Create a new filter" modal 266ms

Then I should see a "Filter created successfully" text 110ms

Scenario:
Create CLM filter of type Patch(Contains Package Name) that allows patches that are equal to a specific one
13s 195ms 11

When I follow the left menu "Content Lifecycle > Filters" 58ms

And I click on "Create Filter" 91ms

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 116ms

When I enter "Triangulum-patch" as "filter_name" 90ms

And I select "Patch (Contains Package Name)" from "type" 1s 124ms

And I select "equals" from "matcher" 1s 111ms

When I enter "Triangulum-patch" as "Package Name" 131ms

And I check radio button "Allow" 10s 73ms

And I click on "Save" in "Create a new filter" modal 275ms

Then I should see a "Filter created successfully" text 110ms

Scenario:
Create CLM filter of type Patch(Contains Package Name) that denys patches that are equal to a specific one
3s 179ms 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 68ms

And I click on "Create Filter" 106ms

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 121ms

When I enter "Pinwheel-patch" as "filter_name" 86ms

And I select "Patch (Contains Package Name)" from "type" 1s 119ms

And I select "equals" from "matcher" 1s 123ms

When I enter "Pinwheel-patch" as "Package Name" 121ms

And I check radio button "Deny" 18ms

And I click on "Save" in "Create a new filter" modal 292ms

Then I should see a "Filter created successfully" text 112ms

Scenario:
Create CLM filter that allows patches of type Patch(Contains Package Name) that matches to a specific one
13s 254ms 11

When I follow the left menu "Content Lifecycle > Filters" 59ms

And I click on "Create Filter" 68ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 125ms

When I enter "Sunflower-patch" as "filter_name" 89ms

And I select "Patch (Contains Package Name)" from "type" 1s 117ms

And I select "matches" from "matcher" 1s 124ms

When I enter "Sunflower-patch" as "Package Name" 119ms

And I check radio button "Allow" 10s 65ms

And I click on "Save" in "Create a new filter" modal 314ms

Then I should see a "Filter created successfully" text 160ms

Scenario:
Create CLM filter of type Patch(Contains Package Name) that denys patches that matches to a specific one
3s 536ms 11

Warning: Radio button 'Deny' is already checked

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 126ms

When I enter "Whirlpool-patch" as "filter_name" 94ms

And I select "Patch (Contains Package Name)" from "type" 1s 129ms

And I select "matches" from "matcher" 1s 119ms

When I enter "Whirlpool-patch" as "Package Name" 132ms

And I check radio button "Deny" 17ms

And I click on "Save" in "Create a new filter" modal 649ms

Then I should see a "Filter created successfully" text 119ms

Scenario:
Create CLM filter of type Patch(Contains Package Provides Name) that allows patches with a specific name
13s 741ms 11

When I follow the left menu "Content Lifecycle > Filters" 60ms

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 134ms

When I enter "Antennae-patch" as "filter_name" 89ms

And I select "Patch (Contains Package Provides Name)" from "type" 1s 144ms

And I select "provides name" from "matcher" 1s 114ms

When I enter "Antennae-patch" as "Package Provides Name" 128ms

And I check radio button "Allow" 10s 81ms

And I click on "Save" in "Create a new filter" modal 787ms

Then I should see a "Filter created successfully" text 123ms

Scenario:
Create CLM filter of type Patch(Contains Package Provides Name) that denys patches with a specific name
3s 127ms 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 58ms

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 140ms

When I enter "hat-patch" as "filter_name" 71ms

And I select "Patch (Contains Package Provides Name)" from "type" 1s 128ms

And I select "provides name" from "matcher" 1s 119ms

When I enter "hat-patch" as "Package Provides Name" 94ms

And I check radio button "Deny" 16ms

And I click on "Save" in "Create a new filter" modal 292ms

Then I should see a "Filter created successfully" text 125ms

Scenario:
Create CLM filter of type Patch(Contains Package) that allows patches whose version is lower than a specific one
13s 520ms 14

When I follow the left menu "Content Lifecycle > Filters" 63ms

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 135ms

When I enter "Hubble-patch" as "filter_name" 81ms

And I select "Patch (Contains Package)" from "type" 1s 128ms

And I select "version lower than" from "matcher" 1s 120ms

When I enter "Hubble-patch" as "Package Name" 114ms

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" 81ms

And I check radio button "Allow" 10s 78ms

And I click on "Save" in "Create a new filter" modal 314ms

Then I should see a "Filter created successfully" text 126ms

Scenario:
Create CLM filter of type Patch(Contains Package) that denys patches whose version is lower than a specific one
3s 438ms 14

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 66ms

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 144ms

When I enter "galaxy-patch" as "filter_name" 79ms

And I select "Patch (Contains Package)" from "type" 1s 127ms

And I select "version lower than" from "matcher" 1s 118ms

When I enter "galaxy-patch" as "Package Name" 114ms

And I enter "galaxy-patch" as "Epoch" 103ms

And I enter "0.0.0" as "Version" 73ms

And I enter "0.0.0" as "Release" 78ms

And I check radio button "Deny" 16ms

And I click on "Save" in "Create a new filter" modal 299ms

Then I should see a "Filter created successfully" text 135ms

Scenario:
Create CLM filter of type Patch(Contains Package) that allows patches whose version is lower or equal than a specific one
13s 588ms 14

When I follow the left menu "Content Lifecycle > Filters" 63ms

And I click on "Create Filter" 71ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 9ms

Then I should see a "Create a new filter" text 137ms

When I enter "earth-patch" as "filter_name" 159ms

And I select "Patch (Contains Package)" from "type" 1s 123ms

And I select "version lower or equal" from "matcher" 1s 113ms

When I enter "earth-patch" as "Package Name" 114ms

And I enter "earth-patch" as "Epoch" 99ms

And I enter "0.0.0" as "Version" 73ms

And I enter "0.0.0" as "Release" 80ms

And I check radio button "Allow" 10s 82ms

And I click on "Save" in "Create a new filter" modal 327ms

Then I should see a "Filter created successfully" text 132ms

Scenario:
Create CLM filter of type Patch(Contains Package) that denys patches whose version is lower or equal than a specific one
3s 457ms 14

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 63ms

And I click on "Create Filter" 74ms

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" 75ms

And I select "Patch (Contains Package)" from "type" 1s 126ms

And I select "version lower or equal" from "matcher" 1s 118ms

When I enter "moon-patch" as "Package Name" 111ms

And I enter "moon-patch" as "Epoch" 99ms

And I enter "0.0.0" as "Version" 75ms

And I enter "0.0.0" as "Release" 78ms

And I check radio button "Deny" 18ms

And I click on "Save" in "Create a new filter" modal 316ms

Then I should see a "Filter created successfully" text 144ms

Scenario:
Create CLM filter to enable Ruby 2.7 module
3s 284ms 11

When I follow the left menu "Content Lifecycle > Filters" 67ms

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 145ms

And I enter "ruby 2.7 module" as "filter_name" 94ms

And I select "Module (Stream)" from "type" 1s 128ms

And I select "equals" from "matcher" 1s 130ms

And I enter "ruby" as "moduleName" 83ms

And I enter "2.7" as "moduleStream" 62ms

And I click on "Save" in "Create a new filter" modal 357ms

Then I should see a "Filter created successfully" text 135ms

Scenario:
Create CLM filter that allows Product Temporary Fix (All)
3s 96ms 10

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 65ms

And I click on "Create Filter" 81ms

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 143ms

When I enter "mars" as "filter_name" 55ms

And I select "Product Temporary Fix (All)" from "type" 1s 140ms

And I select "all" from "matcher" 1s 121ms

And I check radio button "Deny" 18ms

And I click on "Save" in "Create a new filter" modal 321ms

Then I should see a "Filter created successfully" text 141ms

Scenario:
Create CLM filter that denys Product Temporary Fix (All)
3s 194ms 10

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 60ms

And I click on "Create Filter" 90ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 15ms

Then I should see a "Create a new filter" text 194ms

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 119ms

And I check radio button "Deny" 18ms

And I click on "Save" in "Create a new filter" modal 342ms

Then I should see a "Filter created successfully" text 134ms

Scenario:
Create CLM filter of type Product Temporary Fix (Number) that allows packages of a version lower than a specific one
13s 232ms 11

When I follow the left menu "Content Lifecycle > Filters" 59ms

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 151ms

When I enter "jupiter-patch" as "filter_name" 84ms

And I select "Product Temporary Fix (Number)" from "type" 1s 131ms

And I select "lower" from "matcher" 1s 124ms

And I enter "1" as "Number" 70ms

And I check radio button "Allow" 10s 81ms

And I click on "Save" in "Create a new filter" modal 310ms

Then I should see a "Filter created successfully" text 135ms

Scenario:
Create CLM filter of type Product Temporary Fix (Number) that denys packages of a version lower than a specific one
3s 229ms 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 66ms

And I click on "Create Filter" 115ms

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 151ms

When I enter "pluto-patch" as "filter_name" 81ms

And I select "Product Temporary Fix (Number)" from "type" 1s 140ms

And I select "lower" from "matcher" 1s 114ms

And I enter "2" as "Number" 63ms

And I check radio button "Deny" 17ms

And I click on "Save" in "Create a new filter" modal 337ms

Then I should see a "Filter created successfully" text 132ms

@skip_if_github_validation
Scenario:
Create CLM filter that allows packages versions that are equal to a specific Product Temporary Fix (Fixes Package Name)
13s 258ms 11

When I follow the left menu "Content Lifecycle > Filters" 65ms

And I click on "Create Filter" 75ms

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 150ms

When I enter "comet-patch" as "filter_name" 81ms

And I select "Product Temporary Fix (Fixes Package Name)" from "type" 1s 131ms

And I select "equals" from "matcher" 1s 110ms

And I enter "comet-patch" as "Package Name" 108ms

And I check radio button "Allow" 10s 55ms

And I click on "Save" in "Create a new filter" modal 338ms

Then I should see a "Filter created successfully" text 132ms

Scenario:
Cleanup: remove the Content Lifecycle Management project
880ms 5

When I follow the left menu "Content Lifecycle > Projects" 62ms

And I follow "clp_name" 475ms

And I click on "Delete" 83ms

And I click on "Delete" in "Delete Project" modal 98ms

Then I should not see a "clp_name" text 160ms

Scenario:
Cleanup: remove the CLM filters
4s 585ms 33

When I follow the left menu "Content Lifecycle > Filters" 56ms

And I click on "Select unused" 87ms

And I click on "Delete" 92ms

And I click on "Delete" in "Delete Selected Filter(s)" modal 116ms

Then I should not see a "remove fonts packages" text 142ms

And I should not see a "africa-patch" text 2s 567ms

And I should not see a "andromeda-patch" text 50ms

And I should not see a "Antennae-patch" text 50ms

And I should not see a "aries-patch" text 51ms

And I should not see a "asia-patch" text 51ms

And I should not see a "cereal" text 52ms

And I should not see a "comet-patch" text 53ms

And I should not see a "cherry" text 57ms

And I should not see a "drummer" text 53ms

And I should not see a "earth-patch" text 53ms

And I should not see a "galaxy-patch" text 53ms

And I should not see a "hat-patch" text 53ms

And I should not see a "Hubble-patch" text 60ms

And I should not see a "mars" text 130ms

And I should not see a "mars-patch" text 77ms

And I should not see a "mercury" text 52ms

And I should not see a "milkyway-patch" text 52ms

And I should not see a "moon-patch" text 53ms

And I should not see a "Pinwheel-patch" text 51ms

And I should not see a "pluto-patch" text 51ms

And I should not see a "solar" text 51ms

And I should not see a "Sunflower-patch" text 54ms

And I should not see a "Triangulum-patch" text 51ms

And I should not see a "venus" text 51ms

And I should not see a "Whirlpool-patch" text 50ms

And I should not see a "remove fonts packages" text 50ms

And I should not see a "ruby 2.7 module" text 51ms

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
6s 815ms 3

When I delete these channels with spacewalk-remove-channel: 4s 34ms
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 2s 780ms

Then I shouldn't get "clp_label" < 1ms

@scope_recurring_actions
Feature:Change the schedule of a task 41s 373ms 4

Scenario:
Log in as admin user
2s 141ms 1

Given I am authorized for the "Admin" section 2s 141ms

Scenario:
Change the schedule of task sandbox-cleanup-default to weekly
13s 782ms 10

When I follow the left menu "Admin > Task Schedules" 122ms

And I follow "sandbox-cleanup-default" 1s 382ms

And I check radio button "weekly" 10s 75ms

And I select "Friday" from "date_day_week" 65ms

And I click on "Update Schedule" 683ms

Then I should see a "Schedule sandbox-cleanup-default has been updated." text 88ms

When I follow the left menu "Admin > Task Schedules" 73ms

And I follow "sandbox-cleanup-default" 1s 195ms

Then I should see a "Friday" text 79ms

And radio button "weekly" should be checked 15ms

Scenario:
Change the schedule of task sandbox-cleanup-default to monthly
11s 881ms 9

When I follow the left menu "Admin > Task Schedules" 59ms

And I follow "sandbox-cleanup-default" 397ms

And I check radio button "monthly" 10s 73ms

And I select "17" from "date_day_month" 65ms

And I click on "Update Schedule" 728ms

Then I should see a "Schedule sandbox-cleanup-default has been updated." text 83ms

When I follow the left menu "Admin > Task Schedules" 63ms

And I follow "sandbox-cleanup-default" 393ms

Then radio button "monthly" should be checked 15ms

Scenario:
Change the schedule of task sandbox-cleanup-default back to daily
13s 567ms 8

When I follow the left menu "Admin > Task Schedules" 60ms

And I follow "sandbox-cleanup-default" 1s 365ms

And I check radio button "daily" 10s 74ms

And I click on "Update Schedule" 703ms

Then I should see a "Schedule sandbox-cleanup-default has been updated." text 85ms

When I follow the left menu "Admin > Task Schedules" 64ms

And I follow "sandbox-cleanup-default" 1s 197ms

Then radio button "daily" should be checked 15ms

@scope_visualization
Feature:Test the notification/notification-messages feature 13s 101ms 4

Scenario:
Log in as org admin user
1s 897ms 1

Given I am authorized 1s 897ms

Scenario:
Check the unread notification counter is correct
10s 418ms 4

All notification-messages are read, I expect no notification badge

When I follow the left menu "Home > Notification Messages" 68ms

And I wait until I see "The server has collected the following notification messages." text 266ms

Then I follow "Unread Messages" 62ms

And the notification badge and the table should count the same amount of messages 10s 20ms

Scenario:
Delete notification-messages
393ms 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 241ms

Then I follow "All Messages" 66ms

Then I check the first notification message 13ms

And I delete it via the "Delete" button 12ms

Scenario:
Flag a notification-message as read
392ms 5

There are no notification messages, nothing to do then

When I follow the left menu "Home > Notification Messages" 61ms

And I wait until I see "The server has collected the following notification messages." text 246ms

Then I follow "All Messages" 57ms

Then I check the first notification message 13ms

And I mark as read it via the "Mark as Read" button 12ms

Feature:Pay as you go 2m 12s 541ms 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 722ms 1

Given I am authorized for the "Admin" section 1s 722ms

Scenario:
Enter minimal information for payg ssh connection data
1s 625ms 11

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 190ms

And I click on "Add PAYG Connection" 350ms

And I enter "My Instance" as "description" 94ms

And I enter "my-host.local" as "host" 94ms

And I enter "root" as "username" 58ms

And I click on "Create" 62ms

Then I should see a "PAYG my-host.local created successfully" text 692ms

And I should see a "My Instance" text in element "Info-panel-wrapper" 19ms

And I should see a "my-host.local" text in element "Instance-panel-wrapper" 22ms

And I should see a "root" text in element "Instance-panel-wrapper" 19ms

And I should see a "Delete" button 19ms

Scenario:
Enter full information for payg ssh connection data
1m 2s 835ms 31

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 72ms

And I click on "Add PAYG Connection" 396ms

And I enter "My Full Instance" as "description" 95ms

And I enter "my-host-full.local" as "host" 120ms

And I enter "21" as "port" 51ms

And I enter "rootFull" as "username" 67ms

And I enter "passwordFull" as "password" 78ms

And I enter "keyFull" as "key" 71ms

And I enter "keyPasswordFull" as "key_password" 89ms

And I enter "my-bastion.local" as "bastion_host" 94ms

And I enter "22" as "bastion_port" 53ms

And I enter "b_rootFull" as "bastion_username" 76ms

And I enter "b_passwordFull" as "bastion_password" 87ms

And I enter "b_keyFull" as "bastion_key" 78ms

And I enter "b_keyPasswordFull" as "bastion_key_password" 98ms

And I click on "Create" 54ms

Then I should see a "PAYG my-host-full.local created successfully" text 997ms

And I should see a "My Full Instance" text in element "Info-panel-wrapper" 16ms

And I should see a "my-host-full.local" text in element "Instance-panel-wrapper" 19ms

And I should see a "21" text in element "Instance-panel-wrapper" 17ms

And I should see a "rootFull" text in element "Instance-panel-wrapper" 17ms

And I should not see a "passwordFull" text in element "Instance-panel-wrapper" 10s 25ms

And I should not see a "keyFull" text in element "Instance-panel-wrapper" 10s 11ms

And I should not see a "keyPasswordFull" text in element "Instance-panel-wrapper" 10s 33ms

And I should see a "my-bastion.local" text in element "Bastion-panel-wrapper" 20ms

And I should see a "22" text in element "Bastion-panel-wrapper" 19ms

And I should see a "b_rootFull" text in element "Bastion-panel-wrapper" 19ms

And I should not see a "b_passwordFull" text in element "Bastion-panel-wrapper" 10s 11ms

And I should not see a "b_keyFull" text in element "Bastion-panel-wrapper" 10s 8ms

And I should not see a "b_keyPasswordFull" text in element "Bastion-panel-wrapper" 10s 11ms

And I should see a "Delete" button 21ms

Scenario:
Check pay-as-you-go list
271ms 5

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 94ms

Then I should see a "my-host.local" link 19ms

And I should see a "My Instance" text 78ms

And I should see a "my-host-full.local" link 11ms

And I should see a "My Full Instance" text 68ms

Scenario:
Edit connection description
1s 1ms 7

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 68ms

And I follow "my-host-full.local" 391ms

And I click on "Edit Information" 66ms

And I enter "My new Full Instance" as "description" 127ms

And I click on "Save" in "Information" modal 254ms

Then I should see a "PAYG properties updated successfully" text 72ms

And I should see a "My new Full Instance" text in element "Info-panel-wrapper" 20ms

Scenario:
Edit instance ssh connection data
31s 929ms 15

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 66ms

And I follow "my-host-full.local" 403ms

And I click on "Edit Instance" 66ms

And I enter "221" as "port" 64ms

And I enter "NewRootFull" as "username" 101ms

And I enter "NewPasswordFull" as "password" 92ms

And I enter "newKeyFull" as "key" 82ms

And I enter "newKeyPasswordFull" as "key_password" 95ms

And I click on "Save" in "Instance SSH connection" modal 748ms

Then I should see a "PAYG properties updated successfully" text 71ms

And I should see a "221" text in element "Instance-panel-wrapper" 22ms

And I should see a "NewRootFull" text in element "Instance-panel-wrapper" 18ms

And I should not see a "NewPasswordFull" text in element "Instance-panel-wrapper" 10s 30ms

And I should not see a "newKeyFull" text in element "Instance-panel-wrapper" 10s 31ms

And I should not see a "newKeyPasswordFull" text in element "Instance-panel-wrapper" 10s 31ms

Scenario:
Edit bastion ssh connection data
31s 685ms 17

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 95ms

And I follow "my-host-full.local" 416ms

And I click on "Edit Bastion" 67ms

And I enter "my-new-bastion.local" as "bastion_host" 161ms

And I enter "222" as "bastion_port" 62ms

And I enter "b_new_rootFull" as "bastion_username" 115ms

And I enter "b_new_passwordFull" as "bastion_password" 92ms

And I enter "b_new_keyFull" as "bastion_key" 91ms

And I enter "b_new_keyPasswordFull" as "bastion_key_password" 102ms

And I click on "Save" in "Bastion SSH connection" modal 278ms

Then I should see a "PAYG properties updated successfully" text 79ms

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" 18ms

And I should not see a "b_new_passwordFull" text in element "Bastion-panel-wrapper" 10s 24ms

And I should not see a "b_new_keyFull" text in element "Bastion-panel-wrapper" 10s 16ms

And I should not see a "b_new_keyPasswordFull" text in element "Bastion-panel-wrapper" 10s 20ms

Scenario:
Cleanup: delete minimal information for payg ssh connection data
767ms 6

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 97ms

And I follow "my-host.local" 343ms

And I click on "Delete" 72ms

And I click on "Delete" in "Delete PAYG Connection" modal 97ms

Then I should not see a "my-host.local" link 8ms

And I should not see a "my-host.local" text 148ms

Scenario:
Cleanup: delete full information for payg ssh connection data
701ms 6

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 70ms

And I follow "my-host-full.local" 405ms

And I click on "Delete" 60ms

And I click on "Delete" in "Delete PAYG Connection" modal 84ms

Then I should not see a "my-bastion.local" link 7ms

And I should not see a "my-host.local" text 72ms

@sle_minion @scc_credentials @skip_if_github_validation @under_debugging
Feature:Push a package with unset vendor 1m 18s 398ms 2 2

* Related GitHub Card: https://github.com/SUSE/spacewalk/issues/24979
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 949ms 1

Given I am authorized 1s 949ms

Scenario:
Pre-requisite: mgr-push package must be installed on the SLES minion
23s 830ms 12

Given I am on the Systems overview page of this "sle_minion" 1s 543ms

When I follow "Software" in the content area 74ms

And I wait until I see "Upgrade Packages" text 65ms

And I follow "Install" 528ms

And I wait until I see "Installable Packages" text 120ms

And I enter "mgr-push" as the filtered package name 46ms

And I click on the filter button 619ms

And I check "mgr-push" in the list 65ms

And I click on "Install Packages" 610ms

And I click on "Confirm" 681ms

Then I should see a "1 package install has been scheduled for" text 59ms

And I wait until event "Package Install/Upgrade scheduled" is completed 19s 416ms

Scenario:
Push a package with unset vendor through the SLES minion
21s 919ms 2 1 1

When I copy unset package file on "sle_minion" 2s 52ms

And I push package "/root/subscription-tools-1.0-0.noarch.rpm" into "fake-base-channel-suse-like" channel through "sle_minion" 658ms 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 = 1.
Output:
 (ScriptError)
./features/support/remote_node.rb:172:in `run_local'
./features/support/remote_node.rb:120:in `run'
./features/step_definitions/common_steps.rb:327:in `/^I push package "([^"]*)" into "([^"]*)" channel through "([^"]*)"$/'
features/secondary/srv_push_package.feature:34: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

19s 207ms Show Info + 
21:56:32:000 - 21:56:35:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010023&aid=313
Screenshot +

Scenario:
Check vendor of package displayed in web UI
30s 699ms 4 2 1

When I follow the left menu "Software > Channel List > All" 203ms

And I follow "Fake-Base-Channel-SUSE-like" 572ms

And I follow "Packages" 485ms

And I follow "subscription-tools-1.0-0.noarch" 10s 11ms Show Error + 
                                            
 Unable to find link "subscription-tools-1.0-0.noarch" (Capybara::ElementNotFound)
./features/support/commonlib.rb:192:in `click_link_and_wait'
./features/step_definitions/navigation_steps.rb:366:in `/^I follow "([^"]*)"$/'
features/secondary/srv_push_package.feature:41: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

19s 426ms Show Info + 
21:56:54:000 - 21:57:06:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/ChannelPackages.do?cid=121
Screenshot +

@skip_if_github_validation @scope_reportdb @bug_reported
Feature:Report database 1m 54s 24ms 9 1

* Related GitHub Card: https://github.com/SUSE/spacewalk/issues/29433
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 747ms 1

Given I am authorized for the "Admin" section 1s 747ms

Scenario:
Populate the report database after bootstrapping minions
15s 186ms 1

When I schedule a task to update ReportDB 15s 186ms

Scenario:
Connect to the ReportDB on the server with admin user
5s 865ms 2

Then I should be able to connect to the ReportDB on the server 3s 145ms

And there should be a user allowed to create roles on the ReportDB 2s 719ms

Scenario:
Create read-only user
8s 397ms 2

When I create a read-only user for the ReportDB 5s 659ms

Then I should see the read-only user listed on the ReportDB user accounts 2s 737ms

Scenario:
External read-only user can connect to ReportDB and make queries
66ms 2

When I connect to the ReportDB with read-only user from external machine 64ms

Then I should be able to query the ReportDB 1ms

Scenario:
Read-only user can't make changes in the ReportDB
4ms 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
5s 491ms 3

Given I know the ReportDB admin user credentials 5s 370ms

Then I should be able to connect to the ReportDB with the ReportDB admin user 59ms

And I should not be able to connect to product database with the ReportDB admin user 61ms

Scenario:
The systems should match between the UI and the ReportDB
10s 200ms 3

When I follow the left menu "Systems > System List > All" 190ms

And I make a list of the existing systems 10s 9ms

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
36s 56ms 4

Search by hostname: uyuni-master-suse-minion
[{"last_boot"=>"2026-04-20T18:02:01Z", "name"=>"uyuni-master-suse-minion.sumaci.aws", "id"=>1000010023, "last_checkin"=>"2026-04-20T19:56:28Z"}]

Given I have a property "City" with value "Arrakeen" on "sle_minion" 16s 336ms

And I know the current synced_date for "sle_minion" 1ms

When I schedule a task to update ReportDB 19s 716ms

Then I should find the updated "City" property as "Arrakeen" on the "sle_minion", on ReportDB 1ms

Scenario:
Cleanup: delete read-only user
31s 9ms 2 1

When I delete the read-only user for the ReportDB 6s 8ms

Then I shouldn't see the read-only user listed on the ReportDB user accounts 4s 819ms Show Error + 
                                            
 Created read-only user on the ReportDB remains listed (ScriptError)
./features/step_definitions/command_steps.rb:1435:in `/^I shouldn't see the read-only user listed on the ReportDB user accounts$/'
features/secondary/srv_reportdb.feature:58:in `I shouldn't see the read-only user listed on the ReportDB user accounts'

20s 181ms Show Info + 
21:59:02:000 - 21:59:13: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 874ms 12 3

* Related GitHub Card: https://github.com/SUSE/spacewalk/issues/23463

Scenario:
Log in as org admin user
2s 284ms 1

Given I am authorized 2s 284ms

Scenario:
Check if Distribution Channel Mapping page exists
304ms 8

When I follow the left menu "Software > Distribution Channel Mapping" 130ms

Then I should see a "Distribution Channel Mapping" text 53ms

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 20ms

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 20ms

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 346ms 9

When I follow the left menu "Software > Distribution Channel Mapping" 62ms

And I follow "Create Distribution Channel Mapping" 394ms

Then I should see a "Create Distribution Channel Map" text 57ms

When I enter "openSUSE Tumbleweed" as "os" 67ms

And I enter "20250928" as "release" 76ms

And I select "x86_64" from "architecture" 68ms

And I select "openSUSE Tumbleweed (x86_64)" from "channel_label" 60ms

And I click on "Create Mapping" 533ms

Then I should see a "openSUSE Tumbleweed" link in the content area 26ms

@deblike_minion
Scenario:
Create new map for amd64 Ubuntu clients with test base channel
1s 131ms 9

When I follow the left menu "Software > Distribution Channel Mapping" 63ms

And I follow "Create Distribution Channel Mapping" 350ms

Then I should see a "Create Distribution Channel Map" text 56ms

When I enter "Ubuntu 24.04" as "os" 55ms

And I enter "24.04" as "release" 46ms

And I select "AMD64 Debian" from "architecture" 55ms

And I select "Fake-Base-Channel-Debian-like" from "channel_label" 57ms

And I click on "Create Mapping" 423ms

Then I should see a "Ubuntu 24.04" link in the content area 23ms

@scc_credentials
Scenario:
Create new map for iSeries SUSE clients using test channel
819ms 9

When I follow the left menu "Software > Distribution Channel Mapping" 62ms

And I follow "Create Distribution Channel Mapping" 367ms

Then I should see a "Create Distribution Channel Map" text 56ms

When I enter "SUSE Linux Enterprise Server 15 SP 4 iSeries" as "os" 88ms

And I enter "15.5" as "release" 50ms

And I select "iSeries" from "architecture" 58ms

And I select "Fake-Base-Channel-i586" from "channel_label" 57ms

And I click on "Create Mapping" 53ms

Then I should see a "SUSE Linux Enterprise Server 15 SP 4 iSeries" link in the content area 24ms

@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 241ms 11

When I follow the left menu "Software > Distribution Channel Mapping" 68ms

Then I should see the text "openSUSE Tumbleweed" in the Operating System field 10s 8ms

And I should see the text "x86_64" in the Architecture field 10s 8ms

And I should see the text "opensuse_tumbleweed-x86_64" in the Channel Label field 10s 8ms

When I follow "openSUSE Tumbleweed" 316ms

Then I should see a "Update Distribution Channel Map" text 57ms

When I enter "openSUSE Tumbleweed modified" as "os" 103ms

And I select "openSUSE Tumbleweed (x86_64)" from "channel_label" 45ms

And I click on "Update Mapping" 599ms

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 12ms

@deblike_minion
Scenario:
Update map for amd64 Ubuntu clients using test base channel
40s 558ms 8

When I follow the left menu "Software > Distribution Channel Mapping" 82ms

Then I should see the text "Ubuntu 24.04" in the Operating System field 10s 9ms

And I should see the text "AMD64 Debian" in the Architecture field 10s 8ms

And I should see the text "fake-base-channel-debian-like" in the Channel Label field 10s

When I follow "Ubuntu 24.04" 299ms

And I enter "Ubuntu 24.04 modified" as "os" 90ms

And I click on "Update Mapping" 61ms

Then I should see the text "Ubuntu 24.04 modified" in the Operating System field 10s 6ms

@scc_credentials
Scenario:
Update map for IA-32 SUSE clients using amd deb test channel
51s 293ms 10

When I follow the left menu "Software > Distribution Channel Mapping" 75ms

Then I should see the text "SUSE Linux Enterprise Server 15 SP 4 iSeries" in the Operating System field 10s

And I should see the text "iSeries" in the Architecture field 10s 5ms

And I should see the text "fake-base-channel-i586" in the Channel Label field 10s 7ms

When I follow "SUSE Linux Enterprise Server 15 SP 4 iSeries" 375ms

And I enter "SUSE Linux Enterprise Server 15 SP 4 iSeries modified" as "os" 149ms

And I select "Fake-Base-Channel-Debian-like" from "channel_label" 66ms

And I click on "Update Mapping" 599ms

Then I should see the text "SUSE Linux Enterprise Server 15 SP 4 iSeries modified" in the Operating System field 10s 12ms

And I should see the text "fake-base-channel-debian-like" in the Channel Label field 10s

@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 203ms 10

When I follow the left menu "Software > Distribution Channel Mapping" 83ms

Then I should see the text "openSUSE Tumbleweed modified" in the Operating System field 10s 2ms

And I should see the text "x86_64" in the Architecture field 10s 3ms

When I follow "openSUSE Tumbleweed modified" 290ms

Then I should see a "Update Distribution Channel Map" text 56ms

And I should see a "Delete Distribution Channel" link 12ms

When I follow "Delete Distribution Channel Mapping" 254ms

Then I should see a "Delete Distribution Channel Map" text 53ms

When I click on "Delete Mapping" 437ms

Then I should not see a "openSUSE Tumbleweed modified" link 8ms

@deblike_minion
Scenario:
Cleanup: delete the map created for amd64 Ubuntu clients
21s 204ms 10

When I follow the left menu "Software > Distribution Channel Mapping" 79ms

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 4ms

When I follow "Ubuntu 24.04 modified" 290ms

Then I should see a "Update Distribution Channel Map" text 62ms

And I should see a "Delete Distribution Channel" link 11ms

When I follow "Delete Distribution Channel Mapping" 248ms

Then I should see a "Delete Distribution Channel Map" text 50ms

When I click on "Delete Mapping" 442ms

Then I should not see a "Ubuntu 24.04 modified" link 8ms

@scc_credentials
Scenario:
Cleanup: delete the map created for i586 clients
21s 330ms 10

When I follow the left menu "Software > Distribution Channel Mapping" 79ms

Then I should see the text "SUSE Linux Enterprise Server 15 SP 4 iSeries modified" in the Operating System field 10s 4ms

And I should see the text "x86_64" in the Architecture field 10s 10ms

When I follow "SUSE Linux Enterprise Server 15 SP 4 iSeries modified" 352ms

Then I should see a "Update Distribution Channel Map" text 56ms

And I should see a "Delete Distribution Channel" link 12ms

When I follow "Delete Distribution Channel Mapping" 255ms

Then I should see a "Delete Distribution Channel Map" text 49ms

When I click on "Delete Mapping" 501ms

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
155ms 3

When I follow the left menu "Software > Distribution Channel Mapping" 78ms

Then I should see a "Distribution Channel Mapping" text 56ms

And I should see a "No distribution channel mappings currently exist." text in the content area 20ms

Feature:Task Engine Status 29s 720ms 4 2

Scenario:
Login as admin
1s 684ms 1

Given I am authorized for the "Admin" section 1s 684ms

@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 162ms 6

When I follow the left menu "Admin > Task Engine Status > Last Execution Times" 824ms

Then I should see a "Task Engine Status" text 104ms

And I should see a "The following is a status report for the various tasks run by the Uyuni task engine:" text 92ms

And I should see a "Runtime Status" text 96ms

And I should see a "Last Execution Times" link in the left menu 24ms

And I should see a "Runtime Status" link in the left menu 20ms

Scenario:
Check if the Runtime Status Page exists
686ms 6

When I follow the left menu "Admin > Task Engine Status > Runtime Status" 73ms

Then I should see a "Task Engine Status" text 58ms

And I should see a "Last Execution Times" text 56ms

And I should see a "The server is running or has finished executing the following tasks during the latest 5 minutes." text 462ms

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 17ms

Scenario:
Run a remote command on the server to check if it shows up on Last Execution Times page
26s 186ms 6

When I follow the left menu "Admin > Task Engine Status > Last Execution Times" 70ms

And I run "cobbler sync" on "server" 5s 515ms

And I refresh the page 10s 389ms

Then I should see a "Cobbler Sync:" text 98ms

And I should see the correct timestamp for task "Cobbler Sync:" 10s 14ms

And I should see a "FINISHED" text 97ms

@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 650ms 2

@ssh_minion
Scenario:
Check the relevant errata for a system
5s 143ms 1

When I retrieve the relevant errata for ssh_minion 5s 143ms

@ssh_minion @rhlike_minion @deblike_minion
Scenario:
Check the relevant errata for multiple systems
1s 507ms 1

When I retrieve the relevant errata for ssh_minion, rhlike_minion, deblike_minion 1s 507ms

@scope_salt @skip_if_github_validation @bug_reported
Feature:Health Check tool based on a supportconfig 6m 24s 201ms 2 3

* Related GitHub Card: https://github.com/SUSE/spacewalk/issues/29416
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 16s 16ms 2

When I generate a supportconfig for the server 1m 14s 691ms

Then I obtain and extract the supportconfig from the server 1s 325ms

Scenario:
Execute Health Check tool with server supportconfig
20s 62ms 1 1 1

When I start the health check tool with supportconfig "/root/server-supportconfig/uyuni-server-supportconfig/" on "localhost" 447ms Show Error + 
                                            
 FAIL: mgr-health-check -v -s /root/server-supportconfig/uyuni-server-supportconfig/ start returned status code = 1.
Output:
┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃                                 Health Check                                 ┃
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛
[22:06:02] 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:172:in `run_local'
./features/support/remote_node.rb:120:in `run'
./features/step_definitions/command_steps.rb:1804:in `/^I start the health check tool with supportconfig "([^"]*)" on "([^"]*)"$/'
features/secondary/srv_health_check_supportconfig.feature:18: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

19s 615ms Show Info + 
22:06:02:000 - 22:06:02:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/admin/TaskStatus.do
Screenshot +

Scenario:
Health Check containers are healthy and running
4m 29s 349ms 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:89:in `repeat_until_timeout'
./features/support/remote_node.rb:189:in `run_until_ok'
./features/step_definitions/command_steps.rb:1581:in `/^I wait until port "([^"]*)" is listening on "([^"]*)" (host|container)$/'
features/secondary/srv_health_check_supportconfig.feature:22: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

19s 349ms Show Info + 
22:06:22:000 - 22:10:32:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/admin/TaskStatus.do
Screenshot +

Scenario:
Health Check containers are exposing metrics
18s 50ms 1 1

Then I check that the health check tool exposes metrics on "localhost" 197ms 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:172:in `run_local'
./features/support/remote_node.rb:120:in `run'
./features/step_definitions/command_steps.rb:1832:in `/^I check that the health check tool exposes metrics on "([^"]*)"$/'
features/secondary/srv_health_check_supportconfig.feature:28:in `I check that the health check tool exposes metrics on "localhost"'

17s 853ms Show Info + 
22:10:51:000 - 22:10:51:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/admin/TaskStatus.do
Screenshot +

Scenario:
I can stop the Health Check tool
721ms 3

When I stop health check tool on "localhost" 355ms

Then I check that the health check tool is not running on "localhost" 179ms

And I remove test supportconfig on "localhost" 186ms

@skip_if_github_validation
Feature:Password Policy Management 3m 10s 720ms 12 5

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 720ms 1

Given I am authorized as "admin" with password "admin" 1s 720ms

Scenario:
Navigate to Password Policy settings page
851ms 2

When I follow the left menu "Admin > Manager Configuration > Password Policy" 779ms

Then I should see a "Server Configuration - Password Policy" text 71ms

Scenario:
Configure password complexity restrictions
670ms 5

When I set the minimum password length to "5" 51ms

And I set the maximum password length to "12" 51ms

And I enable the following restrictions: 321ms
Require Digits
Require Lowercase Characters
Require Uppercase Characters
Require Special Characters
Restrict Characters Occurrences
Restrict Consecutive Characters

And I click on "Save" 58ms

And I should see a "Password Policy Changed" text 187ms

Scenario:
Verify password complexity restrictions are saved correctly
10s 415ms 2

When I refresh the page 10s 368ms

Then the following restrictions should be enabled: 47ms
Require Digits
Require Lowercase Characters
Require Uppercase Characters
Require Special Characters
Restrict Characters Occurrences
Restrict Consecutive Characters

Scenario:
Update special characters list and maximum character occurrence
368ms 4

When I set the special characters list to "$@?" 66ms

And I set the maximum allowed occurrence of any character to "3" 49ms

And I click on "Save" 53ms

And I should see a "Password Policy Changed" text 199ms

Scenario Outline:
Reject invalid passwords based on policy enforcement
9s 743ms 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 743ms

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 217ms 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 217ms

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
10s 716ms 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" 10s 716ms

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
10s 445ms 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" 10s 445ms

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 553ms 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 553ms

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
31s 34ms 2 1

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" 13s 176ms

Then the user creation should fail with error containing "Passwords must contain at least one special character, allowed special characters are: $@?" < 1ms Show Error + 
                                            
 Expected user creation to fail, but status was 'success' (RuntimeError)
./features/step_definitions/common_steps.rb:356:in `/^the user creation should fail with error containing "([^"]*)"$/'
features/secondary/srv_password_restriction.feature:58:49:in `the user creation should fail with error containing "Passwords must contain at least one special character, allowed special characters are: $@?"'

17s 857ms Show Info + 
22:12:28:000 - 22:12:42:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/admin/config/password-policy
Screenshot +

Scenario Outline:
Reject invalid passwords based on policy enforcement
56s 479ms 1 2

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" 10s 5ms

Then the user creation should fail with error containing "consecutive_characters_presents" < 1ms Show Error + 
                                            
 Expected user creation to fail, but status was 'success' (RuntimeError)
./features/step_definitions/common_steps.rb:356:in `/^the user creation should fail with error containing "([^"]*)"$/'
features/secondary/srv_password_restriction.feature:59:49:in `the user creation should fail with error containing "consecutive_characters_presents"'

46s 473ms Show Error + 
                                            
 User is not logged in (ScriptError)
./features/step_definitions/navigation_steps.rb:655:in `/^I should be logged in$/'
./features/step_definitions/navigation_steps.rb:635:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/support/env.rb:222:in `block in relog_and_visit_previous_url'
./features/support/env.rb:220:in `relog_and_visit_previous_url'
./features/support/env.rb:200:in `handle_screenshot_and_relog'
./features/support/env.rb:162:in `After'
Show Info + 
22:13:00:000 - 22:13:10:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/admin/config/password-policy
Screenshot +

Scenario Outline:
Reject invalid passwords based on policy enforcement
9s 674ms 1 1

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 674ms

Then the user creation should fail with error containing "Password characters occurrences exceeded maximum allowed 3" < 1ms Show Error + 
                                            
 Expected user creation to fail, but status was 'success' (RuntimeError)
./features/step_definitions/common_steps.rb:356:in `/^the user creation should fail with error containing "([^"]*)"$/'
features/secondary/srv_password_restriction.feature:60:49:in `the user creation should fail with error containing "Password characters occurrences exceeded maximum allowed 3"'

Scenario Outline:
Reject invalid passwords based on policy enforcement
9s 694ms 1 1

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 694ms

Then the user creation should fail with error containing "Passwords cannot be more than 12 characters" < 1ms Show Error + 
                                            
 Expected user creation to fail, but status was 'success' (RuntimeError)
./features/step_definitions/common_steps.rb:356:in `/^the user creation should fail with error containing "([^"]*)"$/'
features/secondary/srv_password_restriction.feature:61:49:in `the user creation should fail with error containing "Passwords cannot be more than 12 characters"'

Scenario:
Accept valid password complying with policy
9s 706ms 2

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 706ms

Then the user creation should succeed < 1ms

Scenario:
Reset password policy to default settings
10s 12ms 4 1

When I follow the left menu "Admin > Manager Configuration > Password Policy" 10s 12ms Show Error + 
                                            
 Unable to find xpath "//aside/div[@id='nav']/nav/ul/li/div/a[contains(.,'Admin')]/parent::div/parent::li" (Capybara::ElementNotFound)
./features/step_definitions/navigation_steps.rb:441:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:433:in `each'
./features/step_definitions/navigation_steps.rb:433:in `each_with_index'
./features/step_definitions/navigation_steps.rb:433:in `/^I follow the left menu "([^"]*)"$/'
features/secondary/srv_password_restriction.feature:68:in `I follow the left menu "Admin ) Manager Configuration ) Password Policy"'

And I click on "Reset" 0s

And I should see a "Password Policy Reset to Default" text 0s

And I refresh the page 0s

Then the following restrictions should be disabled: 0s
Require Digits
Require Lowercase Characters
Require Uppercase Characters
Require Special Characters
Restrict Characters Occurrences
Restrict Consecutive Characters

Scenario:
Cleanup: Delete test user
417ms 1

When I delete user "password_policy_user" 417ms

@skip_if_github_validation @build_host @scope_building_container_images @scope_cve_audit @no_auth_registry
Feature:Build container images and CVE audit them 19m 36s 274ms 16 14

Scenario:
Log in as org admin user
10s 716ms 1

Given I am authorized 10s 716ms

Scenario:
Create a simple image profile without activation key
2s 760ms 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" 436ms

And I enter "suse_simple" as "label" 98ms

And I select "galaxy-registry" from "imageStore" 1s 134ms

And I enter "Docker" relative to profiles as "path" 909ms

And I click on "create-btn" 58ms

Scenario:
Create a simple real image profile without activation key
2s 781ms 6

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" 477ms

And I enter "suse_real_simple" as "label" 126ms

And I select "galaxy-registry" from "imageStore" 1s 106ms

And I enter "Docker/serverhost" relative to profiles as "path" 956ms

And I click on "create-btn" 51ms

@scc_credentials
Scenario:
Create an image profile with activation key
3s 834ms 7

GITPROFILES: https://github.com/uyuni-project/uyuni.git#:testsuite/features/profiles/temporary

When I follow the left menu "Images > Profiles" 61ms

And I follow "Create" 480ms

And I enter "suse_key" as "label" 79ms

And I select "galaxy-registry" from "imageStore" 1s 130ms

And I select "1-SUSE-KEY-x86_64" from "activationKey" 1s 123ms

And I enter "Docker" relative to profiles as "path" 901ms

And I click on "create-btn" 57ms

@scc_credentials
Scenario:
Create a simple real image profile with activation key
3s 919ms 7

GITPROFILES: https://github.com/uyuni-project/uyuni.git#:testsuite/features/profiles/temporary

When I follow the left menu "Images > Profiles" 58ms

And I follow "Create" 476ms

And I enter "suse_real_key" as "label" 134ms

And I select "galaxy-registry" from "imageStore" 1s 114ms

And I select "1-SUSE-KEY-x86_64" from "activationKey" 1s 102ms

And I enter "Docker/serverhost" relative to profiles as "path" 976ms

And I click on "create-btn" 55ms

@scc_credentials
Scenario:
Build the suse_key image with and without activation key
1m 6s 861ms 3 2 1

Event Details: ---------- ID: mgr_registries_login Function: module.run Name: docker.login Result: true Comment: Module function docker.login executed Started: 22:16:37.710523 Duration: 1.361 SLS: images.docker Changed: ret: retcode: 0.0 Errors: [ ] Results: { } ---------- ID: mgr_buildimage Function: 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: 22:16:37.712188 Duration: 13300.667 SLS: images.docker Changed: {} ---------- ID: mgr_pushimage Function: module.run Name: docker.push Result: false Comment: One or more requisite failed: images.docker.mgr_buildimage Started: 22:16:51.013384 Duration: 0.005 SLS: images.docker Changed: {} ---------- ID: mgr_registries_logout Function: module.run Name: docker.logout Result: false Comment: One or more requisite failed: images.docker.mgr_pushimage Started: 22:16:51.013656 Duration: 0.003 SLS: images.docker Changed: {} ---------- ID: mgr_buildimage_docker_collect_logs Function: file.touch Name: /var/log/image-build314.log Result: true Comment: Updated times on file /var/log/image-build314.log Started: 22:16:51.016256 Duration: 7.25 SLS: images.docker Changed: touched: /var/log/image-build314.log ---------- ID: mgr_buildimage_docker_collect_logs Function: module.run Name: cp.push Result: true Comment: Module function cp.push executed Started: 22:16:51.023634 Duration: 8.813 SLS: images.docker Changed: ret: true

Given I am on the Systems overview page of this "build_host" 3s 520ms

When I schedule the build of image "suse_key" via API calls 1s 55ms

And I wait at most 660 seconds until event "Image Build suse_key scheduled" is completed 41s 473ms 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:100:in `block in repeat_until_timeout'
./features/support/commonlib.rb:89: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

20s 812ms Show Info + 
22:16:31:000 - 22:17:18:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010004&aid=314
Screenshot +

Scenario:
Check the list of packages is not empty
19s 702ms 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 707ms 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'

18s 995ms Show Info + 
22:17:38:000 - 22:17:39:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010004&aid=314
Screenshot +

Scenario:
Build the suse_simple image with and without activation key
1m 2s 696ms 3 2 1

Event Details: ---------- ID: mgr_registries_login Function: module.run Name: docker.login Result: true Comment: Module function docker.login executed Started: 22:18:02.377860 Duration: 1.446 SLS: images.docker Changed: ret: retcode: 0.0 Errors: [ ] Results: { } ---------- ID: mgr_buildimage Function: 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: 22:18:02.379617 Duration: 13669.218 SLS: images.docker Changed: {} ---------- ID: mgr_pushimage Function: module.run Name: docker.push Result: false Comment: One or more requisite failed: images.docker.mgr_buildimage Started: 22:18:16.049415 Duration: 0.005 SLS: images.docker Changed: {} ---------- ID: mgr_registries_logout Function: module.run Name: docker.logout Result: false Comment: One or more requisite failed: images.docker.mgr_pushimage Started: 22:18:16.049699 Duration: 0.004 SLS: images.docker Changed: {} ---------- ID: mgr_buildimage_docker_collect_logs Function: file.touch Name: /var/log/image-build315.log Result: true Comment: Updated times on file /var/log/image-build315.log Started: 22:18:16.052969 Duration: 7.544 SLS: images.docker Changed: touched: /var/log/image-build315.log ---------- ID: mgr_buildimage_docker_collect_logs Function: module.run Name: cp.push Result: true Comment: Module function cp.push executed Started: 22:18:16.060641 Duration: 10.108 SLS: images.docker Changed: ret: true

Given I am on the Systems overview page of this "build_host" 1s 55ms

When I schedule the build of image "suse_simple" via API calls 1s 460ms

And I wait at most 660 seconds until event "Image Build suse_simple scheduled" is completed 41s 629ms 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:100:in `block in repeat_until_timeout'
./features/support/commonlib.rb:89: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

18s 550ms Show Info + 
22:17:58:000 - 22:18:42:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010004&aid=315
Screenshot +

Scenario:
Check the list of packages is not empty
20s 986ms 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 701ms 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'

20s 284ms Show Info + 
22:19:01:000 - 22:19:01:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010004&aid=315
Screenshot +

@scc_credentials
Scenario:
Build the suse_real_key image with and without activation key
2m 58s 545ms 4 3 1

Given I am on the Systems overview page of this "build_host" 1s 56ms

When I schedule the build of image "suse_real_key" via API calls 865ms

And I wait at most 660 seconds until event "Image Build suse_real_key scheduled" is completed 2m 34s 305ms

And I wait at most 60 seconds until all "3" container images are built correctly on the Image List page 1s 426ms 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:100:in `block in repeat_until_timeout'
./features/support/commonlib.rb:89: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

20s 891ms Show Info + 
22:19:22:000 - 22:21:59:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

Scenario:
Check the list of packages is not empty
20s 10ms 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 803ms 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'

19s 206ms Show Info + 
22:22:20:000 - 22:22:21: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 52s 572ms 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"=>"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 1s 32ms

And I wait at most 900 seconds until image "suse_key" with version "Latest_key-activation1" is built successfully via API 1m 32s 518ms 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:100:in `block in repeat_until_timeout'
./features/support/commonlib.rb:89: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

19s 22ms Show Info + 
22:22:40:000 - 22:24:14:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

Scenario:
Check the list of packages is not empty
21s 554ms 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"=>"bb9db2190ad8c96e809e06016f7ca880ba15565161165a7f7ea75c1d73aa0266", "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 899ms 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'

20s 655ms Show Info + 
22:24:33:000 - 22:24:34:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

Scenario:
Build suse_simple image with different versions
43s 738ms 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"=>"bb9db2190ad8c96e809e06016f7ca880ba15565161165a7f7ea75c1d73aa0266", "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 824ms

And I wait at most 900 seconds until image "suse_simple" with version "Latest_simple" is built successfully via API 21s 999ms 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:100:in `block in repeat_until_timeout'
./features/support/commonlib.rb:89: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

20s 914ms Show Info + 
22:24:55:000 - 22:25:17:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

Scenario:
Check the list of packages is not empty
19s 569ms 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"=>"bb9db2190ad8c96e809e06016f7ca880ba15565161165a7f7ea75c1d73aa0266", "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 675ms 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'

18s 894ms Show Info + 
22:25:38:000 - 22:25:39: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 2ms 3

When I delete the image "suse_key" with version "Latest_key-activation1" via API calls 725ms

Then the image "suse_simple" with version "Latest_key-activation1" doesn't exist via API calls 357ms

When I wait until no Salt job is running on "build_host" 1s 919ms

Scenario:
Delete image via API calls without key
2s 877ms 3

When I delete the image "suse_simple" with version "Latest_simple" via API calls 876ms

Then the image "suse_simple" with version "Latest_simple" doesn't exist via API calls 456ms

When I wait until no Salt job is running on "build_host" 1s 544ms

Scenario:
Rebuild suse_simple image
42s 206ms 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"=>"bb9db2190ad8c96e809e06016f7ca880ba15565161165a7f7ea75c1d73aa0266", "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 908ms

And I wait at most 900 seconds until image "suse_simple" with version "Latest_simple" is built successfully via API 22s 487ms 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:100:in `block in repeat_until_timeout'
./features/support/commonlib.rb:89: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

18s 810ms Show Info + 
22:26:04:000 - 22:26:27:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

Scenario:
Check the list of packages is not empty
22s 95ms 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"=>"bb9db2190ad8c96e809e06016f7ca880ba15565161165a7f7ea75c1d73aa0266", "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 2s 492ms 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'

19s 603ms Show Info + 
22:26:46:000 - 22:26:49:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

@scc_credentials
Scenario:
Rebuild suse_key image
43s 554ms 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"=>"bb9db2190ad8c96e809e06016f7ca880ba15565161165a7f7ea75c1d73aa0266", "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 760ms

And I wait at most 900 seconds until image "suse_key" with version "Latest_key-activation1" is built successfully via API 22s 18ms 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:100:in `block in repeat_until_timeout'
./features/support/commonlib.rb:89: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

20s 775ms Show Info + 
22:27:08:000 - 22:27:31:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

Scenario:
Check the list of packages is not empty
20s 438ms 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"=>"bb9db2190ad8c96e809e06016f7ca880ba15565161165a7f7ea75c1d73aa0266", "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 960ms 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'

19s 478ms Show Info + 
22:27:52:000 - 22:27:53:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

@scc_credentials
Scenario:
Build an image via the GUI
3m 43s 12ms 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"=>"bb9db2190ad8c96e809e06016f7ca880ba15565161165a7f7ea75c1d73aa0266", "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}
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"=>"bb9db2190ad8c96e809e06016f7ca880ba15565161165a7f7ea75c1d73aa0266", "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"=>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"=>"a887419efdd0ae67350a6ed932a96f7dc5f2dda5a9c46a1832534b851d7e9e5a", "files"=>[], "id"=>8, "arch"=>"x86_64", "enhancementErrata"=>0}

When I follow the left menu "Images > Build" 82ms

And I select "suse_real_key" from "profileId" 1s 146ms

And I enter "GUI_BUILT_IMAGE" as "version" 319ms

And I select the hostname of "build_host" from "buildHostId" 1s 135ms

And I click on "submit-btn" 65ms

And I wait until no Salt job is running on "build_host" 2m 27s 938ms

Then I wait until I see "GUI_BUILT_IMAGE" text 100ms

And I wait at most 900 seconds until image "suse_real_key" with version "GUI_BUILT_IMAGE" is built successfully via API 5s 876ms

And I wait at most 300 seconds until image "suse_real_key" with version "GUI_BUILT_IMAGE" is inspected successfully via API 1m 6s 346ms

@scc_credentials
Scenario:
Login as Docker image administrator and build an image
3m 35s 317ms 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"=>"bb9db2190ad8c96e809e06016f7ca880ba15565161165a7f7ea75c1d73aa0266", "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"=>"a887419efdd0ae67350a6ed932a96f7dc5f2dda5a9c46a1832534b851d7e9e5a", "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"=>"bb9db2190ad8c96e809e06016f7ca880ba15565161165a7f7ea75c1d73aa0266", "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"=>"a887419efdd0ae67350a6ed932a96f7dc5f2dda5a9c46a1832534b851d7e9e5a", "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"=>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"=>"b86ffa4986994293f64f16c5a818d28ddce2eeb71aa74c5ab8f00f5d51b9d957", "files"=>[], "id"=>9, "arch"=>"x86_64", "enhancementErrata"=>0}

Given I am authorized as "docker" with password "docker" 1s 515ms

When I follow the left menu "Images > Build" 128ms

And I select "suse_real_key" from "profileId" 1s 118ms

And I enter "GUI_DOCKERADMIN" as "version" 242ms

And I select the hostname of "build_host" from "buildHostId" 1s 113ms

And I click on "submit-btn" 56ms

And I wait until no Salt job is running on "build_host" 2m 17s 100ms

Then I wait until I see "GUI_DOCKERADMIN" text 100ms

And I wait at most 900 seconds until image "suse_real_key" with version "GUI_DOCKERADMIN" is built successfully via API 5s 717ms

And I wait at most 300 seconds until image "suse_real_key" with version "GUI_DOCKERADMIN" is inspected successfully via API 1m 8s 222ms

@scc_credentials
Scenario:
Audit images, searching for a known CVE number
896ms 5

When I follow the left menu "Audit > CVE Audit" 136ms

And I select "1999" from "cveIdentifierYear" 73ms

And I enter "9999" as "cveIdentifierId" 61ms

And I click on "Audit Images" 60ms

Then I should see a "No action required" text 564ms

Scenario:
Audit images, searching for an unknown CVE number
398ms 5

When I follow the left menu "Audit > CVE Audit" 66ms

And I select "2012" from "cveIdentifierYear" 57ms

And I enter "2806" as "cveIdentifierId" 55ms

And I click on "Audit Images" 53ms

Then I should see a "The specified CVE number was not found" text 165ms

@scc_credentials
Scenario:
Cleanup: delete all images with key
6s 284ms 6

Given I am authorized as "admin" with password "admin" 1s 380ms

When I delete the image "suse_key" with version "latest" via API calls 1s 628ms

And I delete the image "suse_key" with version "Latest_key-activation1" via API calls 726ms

And I delete the image "suse_real_key" with version "latest" via API calls 813ms

And I delete the image "suse_real_key" with version "GUI_BUILT_IMAGE" via API calls 847ms

And I delete the image "suse_real_key" with version "GUI_DOCKERADMIN" via API calls 886ms

Scenario:
Cleanup: delete images without key
2s 431ms 3

Given I am authorized as "admin" with password "admin" 405ms

When I delete the image "suse_simple" with version "latest" via API calls 1s 249ms

And I delete the image "suse_simple" with version "Latest_simple" via API calls 777ms

@scc_credentials
Scenario:
Cleanup: delete all profiles with key
802ms 7

When I follow the left menu "Images > Profiles" 131ms

And I check "suse_key" in the list 189ms

And I check "suse_real_key" in the list 60ms

And I click on "Delete" 81ms

And I should see a "Are you sure you want to delete selected profiles?" text 83ms

And I click on the red confirmation button 67ms

And I wait until I see "Image profiles have been deleted" text 189ms

Scenario:
Cleanup: delete all profiles without key
720ms 7

When I follow the left menu "Images > Profiles" 65ms

And I check "suse_simple" in the list 198ms

And I check "suse_real_simple" in the list 64ms

And I click on "Delete" 67ms

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 182ms

Scenario:
Cleanup: Make sure no job is left running on buildhost
1s 982ms 1

When I wait until no Salt job is running on "build_host" 1s 982ms

@skip_if_github_validation @build_host @scope_building_container_images @auth_registry
Feature:Build image with authenticated registry 1m 13s 243ms 6 2

Scenario:
Log in as docker user
1s 512ms 1

Given I am authorized as "docker" with password "docker" 1s 512ms

Scenario:
Create an authenticated image store as Docker admin
1s 221ms 7

AUTH_REGISTRY_CREDENTIALS: cucutest|cucusecret

When I follow the left menu "Images > Stores" 124ms

And I follow "Create" 312ms

And I enter "auth_registry" as "label" 118ms

And I check "useCredentials" 107ms

And I enter URI, username and password for registry 428ms

And I click on "create-btn" 72ms

Then I wait until I see "registry" text 57ms

@scc_credentials
Scenario:
Create a profile for the authenticated image store as Docker admin
4s 924ms 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" 290ms

And I enter "auth_registry_profile" as "label" 204ms

And I select "auth_registry" from "imageStore" 1s 134ms

And I select "1-SUSE-KEY-x86_64" from "activationKey" 1s 118ms

And I enter "Docker/authprofile" relative to profiles as "path" 1s 22ms

And I click on "create-btn" 57ms

Then I wait until I see "auth_registry_profile" text 1s 16ms

@scc_credentials
Scenario:
Build an image in the authenticated image store
42s 92ms 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" 67ms

And I select "auth_registry_profile" from "profileId" 1s 135ms

And I enter "latest" as "version" 152ms

And I select the hostname of "build_host" from "buildHostId" 1s 131ms

And I click on "submit-btn" 67ms

Then I wait until I see "auth_registry_profile" text 74ms

When I wait at most 900 seconds until image "auth_registry_profile" with version "latest" is built successfully via API 21s 204ms 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:100:in `block in repeat_until_timeout'
./features/support/commonlib.rb:89: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

18s 258ms Show Info + 
22:36:06:000 - 22:36:30:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

Scenario:
Check the list of packages is not empty
20s 181ms 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 460ms 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'

19s 720ms Show Info + 
22:36:48:000 - 22:36:48: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 489ms 6

When I follow the left menu "Images > Profiles" 83ms

And I check the row with the "auth_registry_profile" text 143ms

And I click on "Delete" 85ms

And I click on the red confirmation button 63ms

And I should see a "Image profile has been deleted." text 152ms

And I wait until no Salt job is running on "build_host" 1s 961ms

Scenario:
Cleanup: remove authenticated image store
464ms 5

When I follow the left menu "Images > Stores" 65ms

And I check the row with the "auth_registry" text 111ms

And I click on "Delete" 68ms

And I click on the red confirmation button 55ms

And I should see a "Image store has been deleted." text 163ms

Scenario:
Cleanup: delete registry image
358ms 1

When I delete the image "auth_registry_profile" with version "latest" via API calls 358ms

@scope_visualization
Feature:The system details of each minion and client provides an overview of the system 2m 12s 539ms 9

Scenario:
Log in as org admin user
1s 420ms 1

Given I am authorized 1s 420ms

@sle_minion
Scenario:
SLE minion hardware refresh
24s 628ms 6

Given I navigate to the Systems overview page of this "sle_minion" 2s 570ms

When I follow "Hardware" 486ms

And I click on "Schedule Hardware Refresh" 728ms

Then I should see a "You have successfully scheduled a hardware profile refresh" text 122ms

When I wait until event "Hardware List Refresh scheduled" is completed 18s 675ms

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "sle_minion" 2s 44ms

@sle_minion
Scenario:
Minion grains are displayed correctly on the details page
4s 111ms 19

I should see kernel version: 6.19.11-1-default
IPv4 address: 172.16.3.8
IPv6 address: fe80::4a5:e3ff:fe64:c473

Given I am on the Systems overview page of this "sle_minion" 1s 154ms

Then the hostname for "sle_minion" should be correct 87ms

And the kernel for "sle_minion" should be correct 481ms

And the OS version for "sle_minion" should be correct < 1ms

And the IPv4 address for "sle_minion" should be correct 91ms

And the IPv6 address for "sle_minion" should be correct 408ms

And the system ID for "sle_minion" should be correct 564ms

And the system name for "sle_minion" should be correct 83ms

And the uptime for "sle_minion" should be correct 406ms

And I should see a "UUID" text 79ms

And I should see a "Virtualization" text 92ms

And I should see a "Installed Products" text 81ms

And I should see a "Checked In" text 81ms

And I should see a "Registered" text 84ms

And I should see a "Contact Method" text 80ms

And I should see a "Auto Patch Update" text 87ms

And I should see a "Maintenance Schedule" text 80ms

And I should see a "Description" text 80ms

And I should see a "Location" text 84ms

@rhlike_minion
Scenario:
Red Hat-like minion hardware refresh
22s 716ms 6

Given I am on the Systems overview page of this "rhlike_minion" 952ms

When I follow "Hardware" 635ms

And I click on "Schedule Hardware Refresh" 695ms

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 18s 733ms

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "rhlike_minion" 1s 579ms

@rhlike_minion
Scenario:
Red Hat-like minion grains are displayed correctly on the details page
3s 139ms 19

I should see kernel version: 4.18.0-553.el8_10.x86_64
IPv4 address: 172.16.3.10
IPv6 address: fe80::4b6:e3ff:fe25:fc83

Given I am on the Systems overview page of this "rhlike_minion" 962ms

Then the hostname for "rhlike_minion" should be correct 96ms

And the kernel for "rhlike_minion" should be correct 271ms

And the OS version for "rhlike_minion" should be correct < 1ms

And the IPv4 address for "rhlike_minion" should be correct 83ms

And the IPv6 address for "rhlike_minion" should be correct 188ms

And the system ID for "rhlike_minion" should be correct 432ms

And the system name for "rhlike_minion" should be correct 87ms

And the uptime for "rhlike_minion" should be correct 189ms

And I should see a "UUID" text 80ms

And I should see a "Virtualization" text 83ms

And I should see a "Installed Products" text 79ms

And I should see a "Checked In" text 84ms

And I should see a "Registered" text 81ms

And I should see a "Contact Method" text 80ms

And I should see a "Auto Patch Update" text 83ms

And I should see a "Maintenance Schedule" text 84ms

And I should see a "Description" text 84ms

And I should see a "Location" text 81ms

@deblike_minion
Scenario:
Debian-like minion hardware refresh
26s 884ms 6

Given I am on the Systems overview page of this "deblike_minion" 891ms

When I follow "Hardware" 595ms

And I click on "Schedule Hardware Refresh" 798ms

Then I should see a "You have successfully scheduled a hardware profile refresh" text 129ms

When I wait until event "Hardware List Refresh scheduled" is completed 22s 129ms

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "deblike_minion" 2s 340ms

@deblike_minion
Scenario:
Debian-like minion grains are displayed correctly on the details page
3s 165ms 19

I should see kernel version: 6.17.0-1010-aws
IPv4 address: 172.16.3.11
IPv6 address: fe80::41b:11ff:fef2:1197

Given I am on the Systems overview page of this "deblike_minion" 909ms

Then the hostname for "deblike_minion" should be correct 93ms

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 86ms

And the IPv6 address for "deblike_minion" should be correct 213ms

And the system ID for "deblike_minion" should be correct 437ms

And the system name for "deblike_minion" should be correct 86ms

And the uptime for "deblike_minion" should be correct 214ms

And I should see a "UUID" text 84ms

And I should see a "Virtualization" text 81ms

And I should see a "Installed Products" text 80ms

And I should see a "Checked In" text 82ms

And I should see a "Registered" text 81ms

And I should see a "Contact Method" text 83ms

And I should see a "Auto Patch Update" text 86ms

And I should see a "Maintenance Schedule" text 85ms

And I should see a "Description" text 84ms

And I should see a "Location" text 85ms

@ssh_minion
Scenario:
SSH-managed minion hardware refresh
42s 100ms 5

Given I am on the Systems overview page of this "ssh_minion" 991ms

When I follow "Hardware" 789ms

And I click on "Schedule Hardware Refresh" 905ms

Then I should see a "You have successfully scheduled a hardware profile refresh" text 127ms

And I wait until event "Hardware List Refresh scheduled" is completed 39s 286ms

@ssh_minion
Scenario:
SSH-managed minion grains are displayed correctly on the details page
4s 373ms 19

I should see kernel version: 6.19.11-1-default
IPv4 address: 172.16.3.9
IPv6 address: fe80::45e:daff:fec5:5d23

Given I am on the Systems overview page of this "ssh_minion" 1s 53ms

Then the hostname for "ssh_minion" should be correct 93ms

And the kernel for "ssh_minion" should be correct 885ms

And the OS version for "ssh_minion" should be correct < 1ms

And the IPv4 address for "ssh_minion" should be correct 85ms

And the IPv6 address for "ssh_minion" should be correct 453ms

And the system ID for "ssh_minion" should be correct 434ms

And the system name for "ssh_minion" should be correct 86ms

And the uptime for "ssh_minion" should be correct 447ms

And I should see a "UUID" text 81ms

And I should see a "Virtualization" text 86ms

And I should see a "Installed Products" text 82ms

And I should see a "Checked In" text 82ms

And I should see a "Registered" text 83ms

And I should see a "Contact Method" text 82ms

And I should see a "Auto Patch Update" text 84ms

And I should see a "Maintenance Schedule" text 82ms

And I should see a "Description" text 85ms

And I should see a "Location" text 82ms

@scope_ssm @sle_minion @scope_visualization @test_issue @flaky
Feature:Manage a group of systems and the Systems Set Manager 3m 22s 425ms 24 2

* Related GitHub Card: https://github.com/SUSE/spacewalk/issues/27650

Scenario:
Log in as org admin user
435ms 1

Given I am authorized for the "Admin" section 435ms

@skip_if_github_validation
Scenario:
Pre-requisite: install dummy packages to allow patching
5s 53ms 4

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 727ms

And I refresh the metadata for "sle_minion" 803ms

And I install old package "andromeda-dummy-1.0" on this "sle_minion" 1s 768ms

And I install old package "virgo-dummy-1.0" on this "sle_minion" 1s 754ms

Scenario:
Pre-requisite: ensure that fake patches are available
6s 730ms 6

When I follow the left menu "Admin > Task Schedules" 159ms

And I follow "errata-cache-default" 1s 385ms

And I follow "errata-cache-bunch" 1s 527ms

And I click on "Single Run Schedule" 1s 252ms

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 2s 132ms

Scenario:
Pre-requisite: ensure that fake channels were created
11s 266ms 7

When I follow the left menu "Patches > Patch List > Relevant" 215ms

Then I should see an update in the list 66ms

When I wait until I see "andromeda-dummy" text, refreshing the page 225ms

Then I should see a "andromeda-dummy-6789" link 12ms

When I enter "virgo-dummy" as the filtered synopsis 138ms

And I click on the filter button until page does contain "virgo-dummy-3456" text 10s 596ms

Then I should see a "virgo-dummy-3456" link 11ms

Scenario:
Fail to create a group with only its name
831ms 5

When I follow the left menu "Systems > System Groups" 119ms

And I follow "Create Group" 205ms

And I enter "new-systems-group" as "name" 66ms

And I click on "Create Group" 380ms

Then I should see a "Both name and description are required for System Groups." text 60ms

Scenario:
Fail to create a group with only its description
446ms 5

When I follow the left menu "Systems > System Groups" 65ms

And I follow "Create Group" 208ms

And I enter "My new group" as "description" 55ms

And I click on "Create Group" 55ms

Then I should see a "Both name and description are required for System Groups." text 61ms

Scenario:
Create a group
875ms 6

When I follow the left menu "Systems > System Groups" 64ms

And I follow "Create Group" 208ms

And I enter "new-systems-group" as "name" 60ms

And I enter "My new group" as "description" 55ms

And I click on "Create Group" 415ms

Then I should see a "System group new-systems-group created." text 70ms

Scenario:
Add the SLE minion to the group and to SSM
2s 632ms 7

When I follow the left menu "Systems > System Groups" 65ms

And I follow "new-systems-group" 313ms

And I follow "Target Systems" 492ms

And I check the "sle_minion" client 67ms

And I click on "Add Systems" 1s 74ms

Then I should see a "1 systems were added to new-systems-group server group." text 94ms

When I click on "Add Selected to SSM" 524ms

Scenario:
The SLE minion is part of the new group
1s 67ms 3

Given I am on the Systems overview page of this "sle_minion" 924ms

When I follow "Groups" in the content area 72ms

Then I should see a "new-systems-group" text 70ms

Scenario:
Apply a patch to systems in the system group
27s 801ms 14

When I follow the left menu "Systems > System Groups" 58ms

And I follow "new-systems-group" 333ms

And I follow first "Patches" 378ms

When I enter "virgo-dummy" as the filtered synopsis 119ms

And I click on the filter button until page does contain "virgo-dummy-3456" text 226ms

Then I should see a "virgo-dummy-3456" link 18ms

When I follow "virgo-dummy-3456" 591ms

And I follow first "Affected Systems" 308ms

And I check the "sle_minion" client 53ms

And I click on "Apply Patches" 488ms

And I click on "Confirm" 904ms

Then I should see a "Patch virgo-dummy-3456 has been scheduled for 1 system" text 232ms

And I am on the Systems overview page of this "sle_minion" 2s 126ms

And I wait until event "Patch Update: virgo-dummy-3456 - Test update for virgo-dummy scheduled by admin" is completed 21s 962ms

Scenario:
Apply a patch to systems in the SSM
43s 489ms 14

When I follow the left menu "Systems > System Set Manager > Overview" 463ms

And I follow first "Patches" 334ms

When I enter "andromeda-dummy" as the filtered synopsis 143ms

And I click on the filter button 478ms

When I wait until I see "andromeda-dummy-6789" text, refreshing the page 67ms

Then I should see a "andromeda-dummy-6789" link 11ms

When I follow "andromeda-dummy-6789" 446ms

And I follow first "Affected Systems" 305ms

And I check the "sle_minion" client 61ms

And I click on "Apply Patches" 830ms

And I click on "Confirm" 61ms

Then I should see a "Patch andromeda-dummy-6789 has been scheduled for 1 system" text 934ms

And I am on the Systems overview page of this "sle_minion" 928ms

And I wait until event "Patch Update: andromeda-dummy-6789 - Test update for andromeda-dummy scheduled by admin" is completed 38s 422ms

@skip_if_github_validation
Scenario:
Pre-requisite: re-select sle_minion in SSM for package operations
253ms 4

When I follow the left menu "Systems > System Groups" 83ms

And I click on "Use in SSM" in row "new-systems-group" 74ms

Then I should see a "Selected Systems List" text 80ms

And I should see "sle_minion" as link 14ms

@skip_if_github_validation
Scenario:
Delete a package from systems in the SSM
13s 217ms 10

When I follow the left menu "Systems > System Set Manager > Overview" 83ms

And I follow "Packages" 366ms

And I follow "Remove" 516ms

And I wait until I see "Package Removal" text, refreshing the page 229ms

And I enter "virgo-dummy" as the filtered package name 150ms

And I click on the filter button until page does contain "virgo-dummy-2.0-1.1" text 10s 905ms

And I check "virgo-dummy-2.0-1.1" in the list 63ms

And I click on "Remove Packages" 430ms

And I click on "Confirm" 403ms

Then I should see a "Package removals are being scheduled, it may take several minutes for this to complete." text 68ms

@skip_if_github_validation
Scenario:
Pre-requisite: re-select sle_minion in SSM for package install
237ms 4

When I follow the left menu "Systems > System Groups" 76ms

And I click on "Use in SSM" in row "new-systems-group" 73ms

Then I should see a "Selected Systems List" text 72ms

And I should see "sle_minion" as link 15ms

@skip_if_github_validation
Scenario:
Install a package to systems in the SSM
3s 53ms 13

When I follow the left menu "Systems > System Set Manager > Overview" 77ms

And I follow "Packages" 353ms

And I follow "Install" 424ms

And I wait until I see "Fake-RPM-SUSE-Channel" text, refreshing the page 69ms

Then I should see a "Fake-RPM-SUSE-Channel" text 69ms

When I follow "Fake-RPM-SUSE-Channel" 306ms

Then I should see a "virgo-dummy-2.0-1.1" text 95ms

And I enter "virgo-dummy" as the filtered package name 53ms

And I click on the filter button until page does contain "virgo-dummy-2.0-1.1" text 92ms

When I check "virgo-dummy-2.0-1.1" in the list 66ms

And I click on "Install Packages" 395ms

And I click on "Confirm" 986ms

Then I should see a "Package installations are being scheduled, it may take several minutes for this to complete." text 60ms

@rhlike_minion
Scenario:
Add the Red Hat-like minion to the group in a different way
2s 275ms 8

When I follow the left menu "Systems > System Groups" 75ms

Then I should see a "System Groups" text 79ms

When I follow "new-systems-group" 313ms

And I follow "Target Systems" 501ms

Then I should see a "The following are systems that may be added to this group." text 97ms

When I check the "rhlike_minion" client 65ms

And I click on "Add Systems" 1s 47ms

Then I should see a "1 systems were added to new-systems-group server group" text 94ms

Scenario:
Add the new group to SSM
270ms 5

When I follow the left menu "Systems > System Groups" 76ms

And I click on "Use in SSM" in row "new-systems-group" 77ms

Then I should see a "Selected Systems List" text 88ms

And I should see "rhlike_minion" as link 14ms

And I should see "sle_minion" as link 13ms

@skip_if_containerized_server
Scenario:
Install the locale formula package on the server
< 1ms 1

When I manually install the "locale" formula on the server 0s

Scenario:
I synchronize all Salt dynamic modules on "sle_minion"
5s 125ms 1

When I synchronize all Salt dynamic modules on "sle_minion" 5s 125ms

Scenario:
New formula page is rendered for the system group
10s 991ms 6

When I follow the left menu "Systems > System Groups" 71ms

And I follow "new-systems-group" 321ms

And I follow "Formulas" 413ms

Then I should see a "Choose formulas:" text 60ms

And I should see a "General System Configuration" text 94ms

And the "locale" formula should be unchecked 10s 29ms

@rhlike_minion
Scenario:
Apply the highstate to the group
45s 10ms 10

When I follow the left menu "Systems > System Groups" 60ms

Then I should see a "System Groups" text 70ms

When I follow "new-systems-group" 313ms

And I follow "States" 476ms

And I click on "Apply Highstate" 63ms

Then I should see a "Applying the highstate has been scheduled." text 441ms

When I follow "scheduled" 280ms

Then I should see a "Apply states (highstate)" text 64ms

And I should see a "Action Details" text 54ms

And I wait until I see "2 systems successfully completed this action." text, refreshing the page 43s 183ms

Scenario:
Remove SLE minion from new group
2s 721ms 5

Given I am on the Systems overview page of this "sle_minion" 1s 9ms

When I follow "Groups" 602ms

And I check "new-systems-group" in the list 69ms

And I click on "Leave Groups" 974ms

Then I should see a "1 system groups removed." text 66ms

@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
479ms 7

When I follow the left menu "Systems > System Groups" 75ms

When I follow "new-systems-group" in the content area 83ms

And I follow "Delete Group" in the content area 77ms

And I click on "Confirm Deletion" 57ms

Then I should see a "System group" text 60ms

And I should see a "new-systems-group" text 60ms

And I should see a "deleted" text 64ms

Scenario:
Cleanup: regenerate search index for later tests
13s 490ms 1

Search by hostname: uyuni-master-suse-minion
[{"last_boot"=>"2026-04-20T18:02:01Z", "name"=>"uyuni-master-suse-minion.sumaci.aws", "id"=>1000010023, "last_checkin"=>"2026-04-20T20:42:59Z"}]

When I clean the search index on the server 13s 490ms

Scenario:
Cleanup: remove dummy packages
4s 667ms 4

When I disable repository "test_repo_rpm_pool" on this "sle_minion" without error control 723ms

And I refresh the metadata for "sle_minion" 833ms

And I remove package "andromeda-dummy" from this "sle_minion" without error control 1s 563ms

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 40s 870ms 27 1

Scenario:
Log in as org admin user
498ms 1

Given I am authorized 498ms

Scenario:
Create a configuration channel for mixed client types
1s 586ms 7

When I follow the left menu "Configuration > Channels" 124ms

And I follow "Create Config Channel" 269ms

And I enter "Mixed Channel" as "cofName" 68ms

And I enter "mixedchannel" as "cofLabel" 61ms

And I enter "This is a configuration channel for different system types" as "cofDescription" 99ms

And I click on "Create Config Channel" 892ms

Then I should see a "Mixed Channel" text 69ms

Scenario:
Add a configuration file to the mixed configuration channel
10s 365ms 9

When I follow the left menu "Configuration > Channels" 64ms

And I follow "Mixed Channel" 486ms

And I follow "Create Configuration File or Directory" 632ms

And I enter "/etc/s-mgr/config" as "cffPath" 66ms

And I enter "COLOR=white" in the editor 5ms

And I click on "Create Configuration File" 745ms

Then I should see a "Revision 1 of /etc/s-mgr/config from channel Mixed Channel" text 97ms

And file "/srv/susemanager/salt/manager_org_1/mixedchannel/init.sls" should exist on server 5s 348ms

And file "/srv/susemanager/salt/manager_org_1/mixedchannel/etc/s-mgr/config" should exist on server 2s 917ms

@sle_minion
Scenario:
Subscribe a Salt minion to the configuration channel
3s 91ms 8

When I am on the Systems overview page of this "sle_minion" 1s 114ms

And I follow "Configuration" in the content area 68ms

And I follow "Manage Configuration Channels" in the content area 67ms

And I follow first "Subscribe to Channels" in the content area 65ms

And I check "Mixed Channel" in the list 62ms

And I click on "Continue" 746ms

And I click on "Update Channel Rankings" 890ms

Then I should see a "Channel Subscriptions successfully changed for" text 76ms

@rhlike_minion
Scenario:
Subscribe a Red Hat-like minion to the configuration channel
3s 166ms 8

When I am on the Systems overview page of this "rhlike_minion" 1s 340ms

And I follow "Configuration" in the content area 63ms

And I follow "Manage Configuration Channels" in the content area 86ms

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" 50ms

And I click on "Update Channel Rankings" 1s 436ms

Then I should see a "Channel Subscriptions successfully changed for" text 79ms

@deblike_minion
Scenario:
Subscribe a Debian-like minion to the configuration channel
3s 930ms 8

When I am on the Systems overview page of this "deblike_minion" 1s 578ms

And I follow "Configuration" in the content area 63ms

And I follow "Manage Configuration Channels" in the content area 83ms

And I follow first "Subscribe to Channels" in the content area 63ms

And I check "Mixed Channel" in the list 51ms

And I click on "Continue" 706ms

And I click on "Update Channel Rankings" 1s 302ms

Then I should see a "Channel Subscriptions successfully changed for" text 80ms

@ssh_minion
Scenario:
Subscribe a SSH minion to the configuration channel
2s 653ms 8

When I am on the Systems overview page of this "ssh_minion" 1s 641ms

And I follow "Configuration" in the content area 60ms

And I follow "Manage Configuration Channels" in the content area 76ms

And I follow first "Subscribe to Channels" in the content area 59ms

And I check "Mixed Channel" in the list 51ms

And I click on "Continue" 52ms

And I click on "Update Channel Rankings" 635ms

Then I should see a "Channel Subscriptions successfully changed for" text 76ms

Scenario:
Deploy the file to all systems
2s 40ms 7

When I follow the left menu "Configuration > Channels" 117ms

And I follow "Mixed Channel" 446ms

And I follow "Deploy all configuration files to all subscribed systems" 515ms

Then I should see a "/etc/s-mgr/config" link 11ms

When I click on "Deploy Files to Selected Systems" 812ms

Then I should see a "revision-deploys are being scheduled," text 68ms

And I should see a "0 revision-deploys overridden." text 69ms

@sle_minion
Scenario:
Check that file has been created on SLE minion
2s 951ms 2

When I wait until file "/etc/s-mgr/config" exists on "sle_minion" 2s 165ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "sle_minion" 785ms

@rhlike_minion
Scenario:
Check that file has been created on Red Hat-like minion
648ms 2

When I wait until file "/etc/s-mgr/config" exists on "rhlike_minion" 291ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "rhlike_minion" 357ms

@deblike_minion
Scenario:
Check that file has been created on Debian-like minion
1s 278ms 2

When I wait until file "/etc/s-mgr/config" exists on "deblike_minion" 877ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "deblike_minion" 401ms

@ssh_minion
Scenario:
Check that file has been created on SSH minion
7s 560ms 2

When I wait until file "/etc/s-mgr/config" exists on "ssh_minion" 6s 595ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "ssh_minion" 965ms

@sle_minion
Scenario:
Apply highstate to override changed content on SLE minion
16s 104ms 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" 387ms

And I apply highstate on "sle_minion" 14s 633ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "sle_minion" 1s 83ms

@rhlike_minion
Scenario:
Apply highstate to override changed content on Red Hat-like minion
4m 31s 11ms 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" 271ms

And I apply highstate on "rhlike_minion" 4m 10s 918ms Show Error + 
                                            
 execution expired (Timeout::Error)
./features/support/commonlib.rb:89:in `repeat_until_timeout'
./features/support/remote_node.rb:189: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

19s 822ms Show Info + 
22:44:38:000 - 22:48:49: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
10s 529ms 3

Salt command: salt uyuni-master-deblike-minion state.highstate

When I store "COLOR=blue" into file "/etc/s-mgr/config" on "deblike_minion" 901ms

And I apply highstate on "deblike_minion" 9s 222ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "deblike_minion" 405ms

@ssh_minion
Scenario:
Apply highstate to override changed content on SSH minion
36s 615ms 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" 769ms

And I apply highstate on "ssh_minion" 34s 956ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "ssh_minion" 888ms

@rhlike_minion
Scenario:
Unsubscribe Red Hat-like minion and delete configuration files
1s 573ms 7

When I follow the left menu "Configuration > Channels" 78ms

And I follow "Mixed Channel" 446ms

And I follow "Systems" in the content area 68ms

And I check the "rhlike_minion" client 68ms

And I click on "Unsubscribe systems" 544ms

Then I should see a "Successfully unsubscribed 1 system(s)." text 83ms

And I destroy "/etc/s-mgr" directory on "rhlike_minion" 284ms

@deblike_minion
Scenario:
Unsubscribe Debian-like minion and delete configuration files
1s 883ms 7

When I follow the left menu "Configuration > Channels" 60ms

And I follow "Mixed Channel" 420ms

And I follow "Systems" in the content area 59ms

And I check the "deblike_minion" client 59ms

And I click on "Unsubscribe systems" 772ms

Then I should see a "Successfully unsubscribed 1 system(s)." text 72ms

And I destroy "/etc/s-mgr" directory on "deblike_minion" 438ms

@ssh_minion
Scenario:
Unsubscribe SSH minion and delete configuration files
1s 280ms 7

When I follow the left menu "Configuration > Channels" 62ms

And I follow "Mixed Channel" 514ms

And I follow "Systems" in the content area 59ms

And I check the "ssh_minion" client 54ms

And I click on "Unsubscribe systems" 49ms

Then I should see a "Successfully unsubscribed 1 system(s)." text 74ms

And I destroy "/etc/s-mgr" directory on "ssh_minion" 466ms

@sle_minion
Scenario:
Change file on Salt minion and compare
5s 934ms 13

When I am on the Systems overview page of this "sle_minion" 1s 37ms

And I store "COLOR=red" into file "/etc/s-mgr/config" on "sle_minion" 702ms

And I follow "Configuration" in the content area 74ms

And I follow "Compare Files" in the content area 78ms

And I check "/etc/s-mgr/config" in the list 57ms

And I click on "Compare Files" 57ms

And I click on "Schedule Compare" 898ms

Then I should see a "1 files scheduled for comparison." text 72ms

When I wait until event "Show differences between profiled config files and deployed config files scheduled" is completed 2s 428ms

Then I should see a "Differences exist" link 11ms

When I follow "Differences exist" 384ms

Then I should see a "+COLOR=white" text 65ms

And I should see a "-COLOR=red" text 65ms

@sle_minion
Scenario:
Check configuration channel and files via API for Salt minion
1s 26ms 3

Then channel "mixedchannel" should exist 333ms

And channel "mixedchannel" should contain file "/etc/s-mgr/config" 353ms

And "sle_minion" should be subscribed to channel "mixedchannel" 340ms

@sle_minion
Scenario:
Extend configuration channel and deploy files via API for Salt minion
4s 884ms 6

When I store "COLOR=green" into file "/etc/s-mgr/config" on "sle_minion" 390ms

And I add file "/etc/s-mgr/other" containing "NAME=Dante" to channel "mixedchannel" 471ms

And I deploy all systems registered to channel "mixedchannel" 592ms

And I wait until file "/etc/s-mgr/other" exists on "sle_minion" 1s 845ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "sle_minion" 792ms

And file "/etc/s-mgr/other" should contain "NAME=Dante" on "sle_minion" 791ms

@sle_minion
Scenario:
Unsubscribe systems via API for Salt minion
1s 121ms 2

When I unsubscribe "sle_minion" from configuration channel "mixedchannel" 758ms

Then "sle_minion" should not be subscribed to channel "mixedchannel" 363ms

@sle_minion
Scenario:
Re-add SLE Minion via SSM
2s 888ms 10

When I follow the left menu "Systems > System List > All" 131ms

And I click on the clear SSM button 76ms

And I check the "sle_minion" client 439ms

And I follow the left menu "Systems > System Set Manager > Overview" 565ms

And I follow "config channel subscriptions" in the content area 67ms

And I check "Mixed Channel" in the list 55ms

And I click on "Continue" 60ms

And I click on "Apply Subscriptions" 773ms

And I click on "Confirm" 656ms

Then I should see a "Configuration channel subscriptions changed for 1 system successfully." text 62ms

@sle_minion
Scenario:
Cleanup: remove remaining Salt minion from configuration channel
1s 245ms 6

When I follow the left menu "Configuration > Channels" 125ms

And I follow "Mixed Channel" 428ms

And I follow "Systems" in the content area 65ms

And I check the "sle_minion" client 53ms

And I click on "Unsubscribe systems" 514ms

Then I should see a "Successfully unsubscribed 1 system(s)." text 57ms

Scenario:
Cleanup: remove the mixed configuration channel
4s 255ms 5

When I follow the left menu "Configuration > Channels" 65ms

And I follow "Mixed Channel" 360ms

And I follow "Delete Channel" 297ms

And I click on "Delete Config Channel" 373ms

Then file "/srv/susemanager/salt/manager_org_1/mixedchannel/init.sls" should not exist on server 3s 159ms

@sle_minion
Scenario:
Cleanup: delete configuration files on remaining Salt minion
688ms 1

When I destroy "/etc/s-mgr" directory on "sle_minion" 688ms

Scenario:
Cleanup: remove remaining systems from SSM after tests of configuration channel on all clients
53ms 1

When I click on the clear SSM button 53ms

@scope_changing_software_channels @scc_credentials
Feature:Channel subscription via SSM 5m 20s 815ms 14 5

Scenario:
Log in as org admin user
536ms 1

Given I am authorized 536ms

@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 105ms 22

When I follow the left menu "Systems > System List > All" 190ms

And I click on the clear SSM button 47ms

And I check the "sle_minion" client 435ms

And I should see "1" systems selected for SSM 97ms

And I follow the left menu "Systems > System Set Manager > Overview" 446ms

And I follow "channel memberships" in the content area 65ms

Then I should see a "Base Channel" text 64ms

And I should see a "Next" text 86ms

When I select "Fake-Base-Channel-SUSE-like" from drop-down in table line with "openSUSE Tumbleweed (x86_64)" 58ms

And I click on "Next" 60ms

Then I should see a "Child Channels" text 413ms

And I should see a "Fake-Base-Channel-SUSE-like" text 71ms

And I should see a "1 system(s) to subscribe" text 71ms

When I choose radio button "Subscribe" for child channel "Fake-Child-Channel-SUSE-like" 67ms

And I click on "Next" 60ms

Then I should see a "Channel Changes Overview" text 69ms

And I should see a "1 system(s) to subscribe" text 75ms

When I schedule action to 3 minutes from now 242ms

And I click on "Confirm" 53ms

And I remember when I scheduled an action < 1ms

Then I wait until I see "Channel Changes Actions" text 405ms

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 826ms 7

Given I am on the Systems overview page of this "sle_minion" 906ms

When I follow "Software" in the content area 72ms

And I follow "Software Channels" in the content area 65ms

And I wait until I do not see "Loading..." text 70ms

Then radio button "openSUSE Tumbleweed (x86_64)" should be checked 172ms

And I wait until I do not see "Loading..." text 519ms

And I should see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" as unchecked 18ms

@sle_minion @susemanager
Scenario:
Check via API old channels are still the same on SLES minion before channel change completes
< 1ms 3

When I refresh the metadata for "sle_minion" 0s

Then channel "SLE-Product-SLES15-SP7-Pool for x86_64" should be enabled on "sle_minion" 0s

And channel "SLE15-SP7-Installer-Updates for x86_64" should be disabled on "sle_minion" 0s

@sle_minion @uyuni
Scenario:
Check via API old channels are still the same on openSUSE minion before channel change completes
3s 179ms 3

When I refresh the metadata for "sle_minion" 1s 209ms

Then channel "openSUSE Tumbleweed (x86_64)" should be enabled on "sle_minion" 1s 45ms

And channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" should be disabled on "sle_minion" 924ms

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 786ms 3

Given I am on the Systems overview page of this "sle_minion" 1s 836ms

When I wait until event "Subscribe channels scheduled" is completed 1m 12s 885ms

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
2s 58ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 171ms

When I follow "Software" in the content area 79ms

And I follow "Software Channels" in the content area 66ms

And I wait until I do not see "Loading..." text 71ms

Then radio button "Fake-Base-Channel-SUSE-like" should be checked 131ms

And I wait until I do not see "Loading..." text 519ms

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 723ms 4

When I refresh the metadata for "sle_minion" 1s 604ms

Then "2" channels should be enabled on "sle_minion" 730ms

And channel "Fake-Base-Channel-SUSE-like" should be enabled on "sle_minion" 693ms

And channel "Fake-Child-Channel-SUSE-like" should be enabled on "sle_minion" 694ms

@rhlike_minion
Scenario:
System default channel can't be determined on the Red Hat-like minion
2s 627ms 20

When I follow the left menu "Systems > System List > All" 137ms

And I click on the clear SSM button 78ms

And I check the "rhlike_minion" client 400ms

Then I should see "1" systems selected for SSM 99ms

When I follow the left menu "Systems > System Set Manager > Overview" 452ms

And I follow "channel memberships" in the content area 69ms

And I select "System Default Base Channel" from drop-down in table line with "Fake-Base-Channel-RH-like" 228ms

And I click on "Next" 61ms

Then I should see a "Child Channels" text 188ms

And I should see a "Couldn't determine new base channel" text 69ms

And I should see a "1 system(s) incompatible" text 64ms

When I click on "Next" 59ms

Then I should see a "Channel Changes Overview" text 64ms

And I should see a "Couldn't determine new base channel" text 86ms

And I should see a "1 system(s) incompatible" text 71ms

When I click on "Confirm" 58ms

Then I should see a "Channel Changes Actions" text 298ms

And I should see a "Items 1 - 1 of 1" text 65ms

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 280ms 4

Given I am on the Systems overview page of this "rhlike_minion" 935ms

When I follow "Software" in the content area 65ms

And I follow "Software Channels" in the content area 59ms

Then radio button "Fake-Base-Channel-RH-like" should be checked 220ms

@deblike_minion
Scenario:
System default channel can't be determined on the Debian-like minion
3s 133ms 20

When I follow the left menu "Systems > System List > All" 118ms

And I click on the clear SSM button 46ms

And I check the "deblike_minion" client 434ms

Then I should see "1" systems selected for SSM 143ms

When I follow the left menu "Systems > System Set Manager > Overview" 494ms

And I follow "channel memberships" in the content area 59ms

And I select "System Default Base Channel" from drop-down in table line with "Fake-Base-Channel-Debian-like" 269ms

And I click on "Next" 58ms

Then I should see a "Child Channels" text 429ms

And I should see a "Couldn't determine new base channel" text 64ms

And I should see a "1 system(s) incompatible" text 63ms

When I click on "Next" 58ms

Then I should see a "Channel Changes Overview" text 65ms

And I should see a "Couldn't determine new base channel" text 64ms

And I should see a "1 system(s) incompatible" text 67ms

When I click on "Confirm" 54ms

Then I should see a "Channel Changes Actions" text 511ms

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 374ms 4

Given I am on the Systems overview page of this "deblike_minion" 1s 33ms

When I follow "Software" in the content area 63ms

And I follow "Software Channels" in the content area 57ms

Then radio button "Fake-Base-Channel-Debian-like" should be checked 220ms

@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 113ms 15

Given I am on the Systems overview page of this "sle_minion" 929ms

When I follow "Software" in the content area 62ms

And I follow "Software Channels" in the content area 62ms

And I wait until I do not see "Loading..." text 69ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 10s 69ms

And I wait until I do not see "Loading..." text 532ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 78ms

And I check "Fake-RPM-SUSE-Channel" 76ms

And I click on "Next" 55ms

Then I should see a "Confirm Software Channel Change" text 69ms

When I click on "Confirm" 70ms

Then I should see a "Changing the channels has been scheduled." text 437ms

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 29s 816ms

Then channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" should be disabled on "sle_minion" 707ms

Scenario:
Cleanup: remove remaining systems from SSM after channel subscription tests
70ms 1

When I click on the clear SSM button 70ms

@scope_changing_software_channels @scc_credentials
Feature:Channel subscription with recommended or required dependencies 46s 519ms 5 2

Scenario:
Log in as org admin user
502ms 1

Given I am authorized 502ms

Scenario:
Pre-requisite: remove remaining systems from SSM after software channel tests
52ms 1

When I click on the clear SSM button 52ms

@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
43s 659ms 10

Given I am on the Systems overview page of this "sle_minion" 2s 471ms

When I follow "Software" in the content area 75ms

And I follow "Software Channels" in the content area 67ms

And I wait for child channels to appear 219ms

And I check radio button "(none, disable service)" 10s 91ms

And I wait for child channels to appear 246ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 10s 82ms

Then I should see the child channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" "unselected" and "disabled" 10s 130ms

When I select the child channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" 10s 154ms

Then I should see the child channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" "selected" 120ms

@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 235ms 10

When I follow the left menu "Systems > System List > All" 139ms

And I check the "sle_minion" client 692ms

Then I should see "1" systems selected for SSM 167ms

When I follow the left menu "Systems > System Set Manager > Overview" 591ms

And I follow "channel memberships" in the content area 70ms

Then I should see a "Base Channel" text 75ms

And I should see a "Next" text 63ms

When I select "No Change" from drop-down in table line with "openSUSE Tumbleweed (x86_64)" 49ms

And I click on "Next" 63ms

Then I should see the toggler "disabled" 322ms

Scenario:
Cleanup: remove remaining systems from SSM after software channel tests
69ms 1

When I click on the clear SSM button 69ms

@flaky @scope_res @scope_salt @rhlike_minion
Feature:Install a patch on the Red Hat-like minion via Salt through the UI 2m 48s 154ms 9 1

Scenario:
Pre-requisite: enable test_repo_rpm_pool repository on the Red Hat-like minion
282ms 1

When I enable repository "test_repo_rpm_pool" on this "rhlike_minion" 282ms

Scenario:
Pre-requisite: install virgo-dummy-1.0 package on Red Hat-like minion
1s 502ms 1

When I install package "virgo-dummy-1.0" on this "rhlike_minion" 1s 502ms

Scenario:
Pre-requisite: remove andromeda-dummy package from Red Hat-like minion
1s 545ms 1

When I remove package "andromeda-dummy" from this "rhlike_minion" 1s 545ms

Scenario:
Pre-requisite: refresh package list and check newly installed packages on Red Hat-like minion
53s 565ms 2 2

When I refresh packages list via spacecmd on "rhlike_minion" 6s 303ms 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:172:in `run_local'
./features/support/remote_node.rb:120:in `run'
./features/step_definitions/command_steps.rb:1262: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

47s 261ms Show Error + 
                                            
 User is not logged in (ScriptError)
./features/step_definitions/navigation_steps.rb:655:in `/^I should be logged in$/'
./features/step_definitions/navigation_steps.rb:635:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/support/env.rb:222:in `block in relog_and_visit_previous_url'
./features/support/env.rb:220:in `relog_and_visit_previous_url'
./features/support/env.rb:200:in `handle_screenshot_and_relog'
./features/support/env.rb:162:in `After'
Show Info + 
22:57:23:000 - 22:57:29:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channel/ssm/ChannelSubscriptions.do
Screenshot +

Scenario:
Log in as org admin user
10s 721ms 1

Given I am authorized for the "Admin" section 10s 721ms

Scenario:
Pre-requisite: re-subscribe the Red Hat-like minion to a base channel
24s 870ms 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 692ms

When I follow "Software" in the content area 77ms

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-RH-like" 187ms

And I wait until I do not see "Loading..." text 421ms

And I click on "Next" 61ms

Then I should see a "Confirm Software Channel Change" text 62ms

When I click on "Confirm" 75ms

Then I should see a "Changing the channels has been scheduled." text 300ms

And I wait until event "Subscribe channels scheduled" is completed 21s 855ms

Scenario:
Schedule errata refresh to reflect channel assignment on Red Hat-like minion
16s 883ms 10

When I follow "Software" in the content area 60ms

And I follow "List / Remove" in the content area 65ms

And I enter "virgo-dummy" as the filtered package name 187ms

And I click on the filter button until page does contain "virgo-dummy" text 10s 979ms

When I follow the left menu "Admin > Task Schedules" 123ms

And I follow "errata-cache-default" 407ms

And I follow "errata-cache-bunch" 1s 278ms

And I click on "Single Run Schedule" 1s 237ms

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 275ms

Scenario:
Install a patch on the Red Hat-like minion
11s 954ms 8

Given I am on the Systems overview page of this "rhlike_minion" 922ms

When I follow "Software" in the content area 72ms

And I follow "Patches" in the content area 65ms

When I check "virgo-dummy-3456" in the list 64ms

And I click on "Apply Patches" 643ms

And I click on "Confirm" 672ms

Then I should see a "1 patch update has been scheduled for" text 79ms

And I wait for "virgo-dummy-2.0-1.1" to be installed on "rhlike_minion" 9s 434ms

Scenario:
Install a package on the Red Hat-like minion
20s 806ms 7

When I follow "Software" in the content area 62ms

And I follow "Install" 445ms

And I check "andromeda-dummy" in the list 56ms

And I click on "Install Packages" 635ms

And I click on "Confirm" 676ms

Then I should see a "1 package install has been scheduled for" text 79ms

And I wait until event "Package Install/Upgrade scheduled" is completed 18s 849ms

Scenario:
Cleanup: remove virgo-dummy and andromeda-dummy packages from Red Hat-like minion
26s 21ms 13

When I follow "Software" in the content area 74ms

And I follow "List / Remove" 959ms

And I enter "andromeda" as the filtered package name 121ms

And I click on the filter button 806ms

And I check "andromeda-dummy" in the list 59ms

And I enter "virgo-dummy" as the filtered package name 40ms

And I click on the filter button 123ms

And I check "virgo-dummy" in the list 55ms

And I click on "Remove Packages" 600ms

And I click on "Confirm" 688ms

Then I should see a "2 package removals have been scheduled" text 63ms

And I wait until event "Package Removal scheduled" is completed 22s 124ms

And I disable repository "test_repo_rpm_pool" on this "rhlike_minion" 303ms

@scope_monitoring @scope_res @rhlike_minion
Feature:Monitor MLM environment with Prometheus on a Red Hat-like Salt minion 1m 13s 732ms 10

In order to monitor Uyuni server
As an authorized user
I want to enable Prometheus exporters

Scenario:
Log in as org admin user
454ms 1

Given I am authorized 454ms

Scenario:
Apply Prometheus exporter formulas on the Red Hat-like minion
3s 347ms 7

Given I am on the Systems overview page of this "rhlike_minion" 1s 953ms

When I follow "Formulas" in the content area 78ms

Then I should see a "Choose formulas:" text 65ms

And I should see a "Monitoring" text 379ms

When I check the "prometheus-exporters" formula 75ms

And I click on "Save" 64ms

And I wait until I see "Formula saved" text 731ms

Scenario:
Configure Prometheus exporter formula on the Red Hat-like minion
3s 542ms 9

When I follow "Formulas" in the content area 60ms

And I follow "Prometheus Exporters" in the content area 366ms

And I click on "Expand All Sections" 350ms

Then I should see a "Enable and configure Prometheus exporters for managed systems." text 117ms

When I check "node" exporter 50ms

And I check "apache" exporter 86ms

And I check "postgres" exporter 82ms

And I click on "Save" 65ms

Then I should see a "Formula saved" text 2s 363ms

Scenario:
Enable tools_update_repo tools_pool_repo so the exporters packages are available
371ms 1

When I enable the repositories "tools_update_repo tools_pool_repo" on this "rhlike_minion" without error control 371ms

@skip_if_github_validation
Scenario:
Apply highstate for Prometheus exporters on the Red Hat-like minion
40s 82ms 4

When I follow "States" in the content area 79ms

And I click on "Apply Highstate" 78ms

Then I should see a "Applying the highstate has been scheduled." text 555ms

And I wait until event "Apply highstate scheduled" is completed 39s 368ms

@skip_if_github_validation
Scenario:
Wait for service
691ms 3

When I wait until "node" exporter service is active on "rhlike_minion" 314ms

And I wait until "apache" exporter service is active on "rhlike_minion" 190ms

And I wait until "postgres" exporter service is active on "rhlike_minion" 185ms

Scenario:
Visit monitoring endpoints on the Red Hat-like minion
568ms 3

When I visit "Prometheus node exporter" endpoint of this "rhlike_minion" 183ms

And I visit "Prometheus apache exporter" endpoint of this "rhlike_minion" 192ms

And I visit "Prometheus postgres exporter" endpoint of this "rhlike_minion" 192ms

Scenario:
Cleanup: undo Prometheus exporter formulas on the Red Hat-like minion
1s 569ms 4

When I follow "Formulas" in the content area 80ms

And I uncheck the "prometheus-exporters" formula 260ms

And I click on "Save" 65ms

Then I wait until I see "Formula saved" text 1s 162ms

@skip_if_github_validation
Scenario:
Cleanup: apply highstate after test monitoring on the Red Hat-like minion
22s 815ms 4

When I follow "States" in the content area 69ms

And I click on "Apply Highstate" 65ms

Then I should see a "Applying the highstate has been scheduled." text 565ms

And I wait until event "Apply highstate scheduled" is completed 22s 114ms

Scenario:
Cleanup: Disable tools_update_repo tools_pool_repo because they are no longer needed
288ms 1

When I disable the repositories "tools_update_repo tools_pool_repo" on this "rhlike_minion" without error control 288ms

@skip_if_github_validation @scope_salt
Feature:Install a package and a patch on the SUSE SSH client via Salt through the UI 5m 19s 780ms 11

Scenario:
Pre-requisite: enable test_repo_rpm_pool repository on SSH minion
806ms 1

When I enable repository "test_repo_rpm_pool" on this "ssh_minion" 806ms

Scenario:
Pre-requisite: install virgo-dummy-1.0 package on SSH minion
2s 491ms 2

When I refresh the metadata for "ssh_minion" 970ms

And I install old package "virgo-dummy-1.0" on this "ssh_minion" without error control 1s 520ms

Scenario:
Pre-requisite: remove andromeda-dummy package from SSH minion
38s 352ms 4

When I remove package "andromeda-dummy" from this "ssh_minion" without error control 964ms

And I refresh the metadata for "ssh_minion" 887ms

And I refresh packages list via spacecmd on "ssh_minion" 9s 319ms

And I wait until refresh package list on "ssh_minion" is finished 27s 181ms

Scenario:
Pre-requisite: refresh package list and check old packages installed on SSH minion
52s 345ms 4

When I refresh packages list via spacecmd on "ssh_minion" 9s 303ms

And I wait until refresh package list on "ssh_minion" is finished 28s 168ms

Then spacecmd should show packages "virgo-dummy-1.0" installed on "ssh_minion" 7s 493ms

And I wait until package "andromeda-dummy-2.0-1.1" is removed from "ssh_minion" via spacecmd 7s 379ms

Scenario:
Log in as org admin user
1s 45ms 1

Given I am authorized for the "Admin" section 1s 45ms

Scenario:
Pre-requisite: ensure the errata cache is computed before patching Salt minion
27s 712ms 11

Given I am on the Systems overview page of this "ssh_minion" 2s 254ms

When I follow "Software" in the content area 78ms

And I follow "List / Remove" in the content area 65ms

And I enter "virgo-dummy" as the filtered package name 200ms

And I click on the filter button until page does contain "virgo-dummy" text 12s 72ms

When I follow the left menu "Admin > Task Schedules" 122ms

And I follow "errata-cache-default" 1s 219ms

And I follow "errata-cache-bunch" 1s 382ms

And I click on "Single Run Schedule" 1s 269ms

Then I should see a "bunch was scheduled" text 273ms

When I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 8s 773ms

Scenario:
Install a patch on the SSH minion
49s 124ms 12

Given I am on the Systems overview page of this "ssh_minion" 1s 536ms

When I follow "Software" in the content area 70ms

And I follow "Patches" in the content area 63ms

And I enter "virgo" as the filtered synopsis 46ms

And I click on the filter button 10s 121ms

And I check "virgo-dummy-3456" in the list 60ms

And I check "allowVendorChange" 76ms

And I click on "Apply Patches" 855ms

And I click on "Confirm" 937ms

Then I should see a "1 patch update has been scheduled for" text 72ms

When I wait for "virgo-dummy-2.0-1.1" to be installed on "ssh_minion" 34s 237ms

Then vendor change should be enabled for package actions on "ssh_minion" 1s 44ms

Scenario:
Install a package on the SSH minion
57s 688ms 12

Given I am on the Systems overview page of this "ssh_minion" 1s 785ms

When I follow "Software" in the content area 75ms

And I follow "Packages" 501ms

And I follow "Install" 593ms

And I enter "andromeda" as the filtered package name 112ms

And I click on the filter button 627ms

And I check "andromeda-dummy-2.0-1.1" in the list 57ms

And I click on "Install Packages" 667ms

And I click on "Confirm" 697ms

Then I should see a "1 package install has been scheduled" text 67ms

When I wait for "andromeda-dummy-2.0-1.1" to be installed on "ssh_minion" 51s 486ms

Then vendor change should be enabled for package actions on "ssh_minion" 1s 17ms

Scenario:
Cleanup: disable test_repo_rpm_pool on SSH minion
607ms 1

When I disable repository "test_repo_rpm_pool" on this "ssh_minion" 607ms

Scenario:
Cleanup: remove virgo-dummy package from SSH minion
52s 512ms 4

When I remove package "virgo-dummy" from this "ssh_minion" without error control 1s 709ms

And I refresh the metadata for "ssh_minion" 920ms

And I refresh packages list via spacecmd on "ssh_minion" 7s 703ms

And I wait until refresh package list on "ssh_minion" is finished 42s 179ms

Scenario:
Cleanup: remove andromeda-dummy package from SSH minion
37s 93ms 4

When I remove package "andromeda-dummy" from this "ssh_minion" without error control 1s 515ms

And I refresh the metadata for "ssh_minion" 888ms

And I refresh packages list via spacecmd on "ssh_minion" 9s 275ms

And I wait until refresh package list on "ssh_minion" is finished 25s 413ms

@scope_ansible @scope_salt_ssh @ssh_minion
Feature:Operate an Ansible control node in SSH minion 4m 51s 802ms 12 2

Scenario:
Log in as org admin user
491ms 1

Given I am authorized for the "Admin" section 491ms

Scenario:
Pre-requisite: Deploy test playbooks and inventory file
4s 146ms 1

When I deploy testing playbooks and inventory files to "ssh_minion" 4s 146ms

@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
4s 87ms 5

Given I am on the Systems overview page of this "ssh_minion" 1s 74ms

When I follow "Properties" in the content area 70ms

And I check "ansible_control_node" 81ms

And I click on "Update Properties" 2s 775ms

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 32s 828ms 5

Given I am on the Systems overview page of this "ssh_minion" 2s 304ms

When I follow "States" in the content area 67ms

And I click on "Apply Highstate" 93ms

And I wait until event "Apply highstate scheduled" is completed 1m 29s 841ms

Then "ansible" should be installed on "ssh_minion" 520ms

Scenario:
The Ansible tab appears in the system overview page
1s 482ms 3

Given I am on the Systems overview page of this "ssh_minion" 1s 346ms

When I follow "Ansible" in the content area 75ms

Then I should see a "Ansible Control Node Configuration" text 61ms

Scenario:
Configure some inventory and playbooks path
1s 817ms 7

Given I am on the Systems overview page of this "ssh_minion" 1s 240ms

When I follow "Ansible" in the content area 61ms

Then I should see a "Ansible Control Node Configuration" text 61ms

And I enter "/srv/playbooks/" as "new_playbook_path_input" 234ms

And I click on "new_playbook_path_save" 57ms

And I enter "/srv/playbooks/orion_dummy/hosts" as "new_inventory_path_input" 98ms

And I click on "new_inventory_path_save" 63ms

Scenario:
Display inventories
24s 971ms 6

Given I am on the Systems overview page of this "ssh_minion" 1s 174ms

When I follow "Ansible" in the content area 62ms

And I follow "Inventories" in the content area 63ms

And I wait until I see "/srv/playbooks/orion_dummy/hosts" text 336ms

And I click on the inventory accordion for "/srv/playbooks/orion_dummy/hosts" 47ms

Then I wait until I see "myself" text 23s 286ms

Scenario:
Discover playbooks and display them
12s 496ms 6

Given I am on the Systems overview page of this "ssh_minion" 1s 126ms

When I follow "Ansible" in the content area 78ms

And I follow "Playbooks" in the content area 62ms

And I wait until I see "/srv/playbooks" text 246ms

And I click on "/srv/playbooks" 57ms

Then I wait until I see "/srv/playbooks/orion_dummy/playbook_orion_dummy.yml" text 10s 924ms

Scenario:
Run a playbook using custom inventory
1m 2s 762ms 13

Given I am on the Systems overview page of this "ssh_minion" 2s 321ms

When I follow "Ansible" in the content area 67ms

And I follow "Playbooks" in the content area 58ms

And I wait until I see "/srv/playbooks" text 240ms

And I click on "/srv/playbooks" 57ms

And I wait until I see "/srv/playbooks/orion_dummy/playbook_orion_dummy.yml" text 11s 31ms

And I click on "orion_dummy/playbook_orion_dummy.yml" 59ms

And I wait until I see "Playbook Content" text 7s 736ms

And I select "/srv/playbooks/orion_dummy/hosts" from "inventory-path-select" 1s 127ms

And I click on "Schedule" 71ms

Then I should see a "Playbook execution has been scheduled" text 364ms

And I wait until event "Execute playbook 'playbook_orion_dummy.yml' scheduled" is completed 38s 792ms

And file "/tmp/file.txt" should exist on "ssh_minion" 833ms

Scenario:
Cleanup: Disable Ansible and remove test playbooks and inventory file
15s 846ms 7

Given I am on the Systems overview page of this "ssh_minion" 1s 373ms

When I follow "Properties" in the content area 81ms

And I uncheck "ansible_control_node" 10s 76ms

And I click on "Update Properties" 1s 815ms

Then I should see a "System properties changed" text 91ms

And I remove package "orion-dummy" from this "ssh_minion" without error control 1s 970ms

And I remove "/tmp/file.txt" from "ssh_minion" 436ms

@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 931ms 4

Given I am on the Systems overview page of this "ssh_minion" 1s 86ms

When I follow "Properties" in the content area 73ms

And I uncheck "ansible_control_node" 10s 38ms

And I click on "Update Properties" 1s 732ms

Scenario:
Cleanup: Apply highstate to disable the minion as an "Ansible control node"
57s 940ms 4

Given I am on the Systems overview page of this "ssh_minion" 1s 311ms

When I follow "States" in the content area 75ms

And I click on "Apply Highstate" 59ms

And I wait until event "Apply highstate scheduled" is completed 56s 494ms

@scope_monitoring @scope_res @deblike_minion
Feature:Monitor MLM environment with Prometheus on a Debian-like Salt minion 1m 31s 81ms 10

In order to monitor Uyuni server
As an authorized user
I want to enable Prometheus exporters

Scenario:
Log in as org admin user
453ms 1

Given I am authorized 453ms

Scenario:
Apply Prometheus exporter formulas on the Debian-like minion
3s 274ms 7

Given I am on the Systems overview page of this "deblike_minion" 1s 829ms

When I follow "Formulas" in the content area 81ms

Then I should see a "Choose formulas:" text 65ms

And I should see a "Monitoring" text 291ms

When I check the "prometheus-exporters" formula 77ms

And I click on "Save" 64ms

And I wait until I see "Formula saved" text 865ms

Scenario:
Configure Prometheus exporter formula on the Debian-like minion
2s 696ms 9

When I follow "Formulas" in the content area 62ms

And I follow "Prometheus Exporters" in the content area 424ms

And I click on "Expand All Sections" 332ms

Then I should see a "Enable and configure Prometheus exporters for managed systems." text 119ms

When I check "node" exporter 50ms

And I check "apache" exporter 89ms

And I check "postgres" exporter 84ms

And I click on "Save" 86ms

Then I should see a "Formula saved" text 1s 444ms

Scenario:
Enable tools_update_repo tools_pool_repo so the exporters packages are available
1s 283ms 1

When I enable the repositories "tools_update_repo tools_pool_repo" on this "deblike_minion" without error control 1s 283ms

@skip_if_github_validation
Scenario:
Apply highstate for Prometheus exporters on the Debian-like minion
56s 483ms 4

When I follow "States" in the content area 76ms

And I click on "Apply Highstate" 61ms

Then I should see a "Applying the highstate has been scheduled." text 558ms

And I wait until event "Apply highstate scheduled" is completed 55s 786ms

@skip_if_github_validation
Scenario:
Wait for services
868ms 3

When I wait until "node" exporter service is active on "deblike_minion" 448ms

And I wait until "apache" exporter service is active on "deblike_minion" 210ms

And I wait until "postgres" exporter service is active on "deblike_minion" 209ms

Scenario:
Visit monitoring endpoints on the Debian-like minion
613ms 3

And I visit "Prometheus node exporter" endpoint of this "deblike_minion" 207ms

And I visit "Prometheus apache exporter" endpoint of this "deblike_minion" 204ms

And I visit "Prometheus postgres exporter" endpoint of this "deblike_minion" 202ms

Scenario:
Cleanup: undo Prometheus exporter formulas on the Debian-like minion
1s 521ms 4

When I follow "Formulas" in the content area 79ms

And I uncheck the "prometheus-exporters" formula 235ms

And I click on "Save" 64ms

Then I wait until I see "Formula saved" text 1s 142ms

@skip_if_github_validation
Scenario:
Cleanup: apply highstate after test monitoring on the Debian-like minion
22s 988ms 4

When I follow "States" in the content area 68ms

And I click on "Apply Highstate" 58ms

Then I should see a "Applying the highstate has been scheduled." text 561ms

And I wait until event "Apply highstate scheduled" is completed 22s 300ms

Scenario:
Cleanup: Disable tools_update_repo tools_pool_repo because they are no longer needed
895ms 1

When I disable the repositories "tools_update_repo tools_pool_repo" on this "deblike_minion" without error control 895ms

@deblike_minion @scope_deblike @scope_content_staging
Feature:Install a package on the Debian-like minion with staging enabled 4m 382ms 7 1

Scenario:
Pre-requisite: install virgo-dummy-1.0 package, make sure orion-dummy is not present on Debian-like minion
1s 784ms 4

When I enable repository "test_repo_deb_pool" on this "deblike_minion" 419ms

And I run "apt update" on "deblike_minion" 860ms

And I remove package "orion-dummy" from this "deblike_minion" 253ms

And I install old package "virgo-dummy=1.0" on this "deblike_minion" 249ms

Scenario:
Pre-requisite: refresh package list on Debian-like minion
29s 884ms 3

When I refresh packages list via spacecmd on "deblike_minion" 8s 890ms

And I wait until refresh package list on "deblike_minion" is finished 13s 664ms

Then spacecmd should show packages "virgo-dummy-1.0" installed on "deblike_minion" 7s 328ms

Scenario:
Log in as admin user
670ms 1

Given I am authorized for the "Admin" section 670ms

Scenario:
Pre-requisite: ensure the errata cache is computed for Debian-like minion
6s 605ms 6

When I follow the left menu "Admin > Task Schedules" 136ms

And I follow "errata-cache-default" 1s 389ms

And I follow "errata-cache-bunch" 1s 297ms

Then I click on "Single Run Schedule" 1s 251ms

And I should see a "bunch was scheduled" text 278ms

Then I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 2s 252ms

Scenario:
Enable content staging for Debian-like minion
1s 621ms 6

When I follow the left menu "Admin > Organizations" 70ms

And I follow first "SUSE Test" 427ms

And I follow first "Configuration" 415ms

And I check "staging_content_enabled" 42ms

And I click on "Update Organization" 602ms

Then I should see a "was successfully updated." text 63ms

Scenario:
Install package in the future and check for staging on Debian-like minion
2m 46s 107ms 13

Given I am on the Systems overview page of this "deblike_minion" 1s 352ms

And I follow "Software" in the content area 72ms

And I follow "Packages" in the content area 64ms

And I follow "Install" in the content area 66ms

And I enter "orion-dummy-1.1-X" as the filtered package name 61ms

And I click on the filter button 619ms

When I check "orion-dummy-1.1-X" in the list 58ms

And I click on "Install Packages" 684ms

And I pick 3 minutes from now as schedule time 92ms

And I click on "Confirm" 755ms

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" 45s 447ms

And I wait for "orion-dummy-1.1" to be installed on "deblike_minion" 1m 56s 768ms

Scenario:
Install patch in the future and check for staging on Debian-like minion
31s 125ms 3 8 1

When I follow "Software" in the content area 63ms

And I follow "Patches" in the content area 66ms

And I enter "virgo" as the filtered synopsis 10s 4ms Show Error + 
                                            
 Unable to find css "input[placeholder='Filter by Synopsis: ']" (Capybara::ElementNotFound)
./features/step_definitions/navigation_steps.rb:966: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

20s 991ms Show Info + 
23:18:07:000 - 23:18:18: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 583ms 4

And I remove package "orion-dummy" from this "deblike_minion" 1s 54ms

And I remove package "virgo-dummy" from this "deblike_minion" 333ms

And I disable repository "test_repo_deb_pool" on this "deblike_minion" 200ms

And I run "apt update" on "deblike_minion" 993ms

@scope_deblike @scope_salt @deblike_minion
Feature:Install and upgrade package on the Debian-like minion via Salt through the UI 1m 47s 356ms 9 1 1

Scenario:
Pre-requisite: enable test_repo_deb_pool repository on the Debian-like minion
424ms 1

When I enable repository "test_repo_deb_pool" on this "deblike_minion" 424ms

Scenario:
Pre-requisite: install virgo-dummy-1.0 package on Debian-like minion
2s 727ms 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,396 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 811ms

And I install old package "virgo-dummy=1.0" on this "deblike_minion" 1s 915ms

Scenario:
Pre-requisite: remove andromeda-dummy package from Debian-like minion
360ms 1

When I remove package "andromeda-dummy" from this "deblike_minion" 360ms

Scenario:
Log in as org admin user
466ms 1

Given I am authorized 466ms

Scenario:
Pre-requisite: refresh package list and check newly installed packages on Debian-like minion
44s 773ms 7

Given I am on the Systems overview page of this "deblike_minion" 2s 269ms

When I follow "Software" in the content area 79ms

And I click on "Update Package List" 982ms

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 371ms

And I wait until package "virgo-dummy" is installed on "deblike_minion" via spacecmd 7s 477ms

And I wait until package "andromeda-dummy" is removed from "deblike_minion" via spacecmd 9s 524ms

Scenario:
Install a patch on the Debian-like minion
30s 592ms 3 4 1

When I follow "Software" in the content area 60ms

And I follow "Patches" in the content area 67ms

When I check "3456-1" in the list 10s 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:1038: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

20s 463ms Show Info + 
23:19:45:000 - 23:19:56: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
26s 158ms 8

When I follow "Software" in the content area 74ms

And I follow "Install" 519ms

And I check "andromeda-dummy-2.0" in the list 62ms

And I click on "Install Packages" 741ms

And I click on "Confirm" 841ms

And I should see a "1 package install has been scheduled for" text 70ms

When I wait until event "Package Install/Upgrade scheduled" is completed 22s 938ms

Then Deb package "andromeda-dummy" with version "2.0" should be installed on "deblike_minion" 909ms

Scenario:
Cleanup: disable test_repo_deb_pool on Debian-like minion
195ms 1

When I disable repository "test_repo_deb_pool" on this "deblike_minion" 195ms

Scenario:
Cleanup: remove virgo-dummy package from Debian-like minion
336ms 1

When I remove package "virgo-dummy" from this "deblike_minion" 336ms

Scenario:
Cleanup: remove andromeda-dummy package from Debian-like minion
1s 320ms 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" 339ms

And I run "apt update" on "deblike_minion" with logging 981ms

@skip_if_github_validation @sle_minion @scope_onboarding
Feature:Negative tests for bootstrapping normal minions 21s 16ms 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
704ms 1

Given I am authorized 704ms

Scenario:
Bootstrap should fail when minion already exists
997ms 10

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 126ms

Then I should see a "Bootstrap Minions" text 84ms

When I enter the hostname of "sle_minion" as "hostname" 147ms

And I enter "22" as "port" 54ms

And I enter "root" as "user" 59ms

And I enter "linux" as "password" 64ms

And I click on "Bootstrap" 67ms

And I wait until I see "A salt key for this host" text 265ms

Then I should not see a "GenericSaltError" text 65ms

And I should see a "seems to already exist, please check!" text 63ms

Scenario:
Bootstrap a SLES minion with wrong hostname
3s 6ms 14

When I follow the left menu "Systems > Bootstrapping" 63ms

Then I should see a "Bootstrap Minions" text 65ms

When I enter "not-existing-name" as "hostname" 84ms

And I enter "22" as "port" 49ms

And I enter "root" as "user" 52ms

And I enter "linux" as "password" 55ms

And I click on "Bootstrap" 65ms

And I wait until I see "An error has occurred during salt execution: unable to establish ssh connection." text 2s 321ms

Then I should see a "Details" button 16ms

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 74ms

And I should see "Could not resolve hostname not-existing-name: Name or service not known" in the stderr textarea 15ms

When I close the modal dialog 54ms

Scenario:
Bootstrap a SLES minion with wrong SSH credentials
13s 438ms 14

The hostname of localhost is uyuni-master-controller.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 61ms

Then I should see a "Bootstrap Minions" text 66ms

When I enter the hostname of "localhost" as "hostname" 122ms

And I enter "22" as "port" 47ms

And I enter "FRANZ" as "user" 56ms

And I enter "KAFKA" as "password" 57ms

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 12s 730ms

Then I should see a "Details" button 17ms

When I click on "Details" 71ms

And I wait at most 10 seconds until I see modal containing "Error Details" text 11ms

Then I should see a "Standard Error" text 70ms

And I should see "Permission denied (publickey" or "Password authentication failed" in the stderr textarea 15ms

When I close the modal dialog 53ms

Scenario:
Bootstrap a SLES minion with wrong SSH port number
2s 868ms 14

The hostname of localhost is uyuni-master-controller.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 78ms

Then I should see a "Bootstrap Minions" text 63ms

When I enter the hostname of "localhost" as "hostname" 130ms

And I enter "11" as "port" 48ms

And I enter "root" as "user" 52ms

And I enter "linux" as "password" 54ms

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 176ms

Then I should see a "Details" button 14ms

When I click on "Details" 57ms

And I wait at most 10 seconds until I see modal containing "Error Details" text 8ms

Then I should see a "Standard Error" text 69ms

And I should see "port 11: Connection refused" or "port 11: Network is unreachable" in the stderr textarea 12ms

When I close the modal dialog 46ms

@skip_if_github_validation @scope_formulas @bug_reported
Feature:Use salt formulas 5m 28s 705ms 20 2

* Related GitHub Card: https://github.com/SUSE/spacewalk/issues/29492
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
484ms 1

Given I am authorized 484ms

@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"
5s 495ms 1

When I synchronize all Salt dynamic modules on "sle_minion" 5s 495ms

Scenario:
The new formula appears on the server
449ms 2

When I follow the left menu "Salt > Formula Catalog" 151ms

Then I should see a "locale" text in the content area 298ms

Scenario:
Enable the formula on the minion
13s 435ms 9

Given I am on the Systems overview page of this "sle_minion" 1s 909ms

When I follow "Formulas" in the content area 75ms

Then I should see a "Choose formulas:" text 63ms

And I should see a "General System Configuration" text 381ms

And I should see a "Locale" text 87ms

When I check the "locale" formula 77ms

And I click on "Save" 64ms

And I wait until I see "Formula saved." text 751ms

Then the "locale" formula should be checked 10s 23ms

Scenario:
Parametrize the formula on the minion
2s 126ms 8

When I follow "Formulas" in the content area 61ms

And I follow first "Locale" in the content area 243ms

And I click on "Expand All Sections" 454ms

And I select "Etc/GMT-5" in timezone name field 62ms

And I select "French" in language field 50ms

And I select "French (Canada)" in keyboard layout field 46ms

And I click on "Save Formula" 61ms

Then I should see a "Formula saved" text 1s 146ms

Scenario:
Check the pillar data after saving the formula
23s 782ms 5

When I refresh the pillar data 5s 509ms

Then the pillar data for "formulas" should be "- locale" on "sle_minion" 4s 272ms

And the pillar data for "timezone:name" should be "Etc/GMT-5" on "sle_minion" 6s 19ms

And the pillar data for "keyboard_and_language:keyboard_layout" should be "French (Canada)" on "sle_minion" 4s 440ms

And the pillar data for "keyboard_and_language:language" should be "French" on "sle_minion" 3s 541ms

@ssh_minion
Scenario:
No other minion is affected by the formula
31s 368ms 3

Then the pillar data for "formulas" should be empty on "ssh_minion" 11s 64ms

And the pillar data for "timezone" should be empty on "ssh_minion" 9s 924ms

And the pillar data for "keyboard_and_language" should be empty on "ssh_minion" 10s 379ms

Scenario:
Use the parametrized formula in test mode
25s 259ms 7

Given I am on the Systems overview page of this "sle_minion" 2s 241ms

And I follow "States" in the content area 72ms

Then I should see the toggler "disabled" 11ms

When I click on the "disabled" toggler 46ms

And I click on "Apply Highstate" 60ms

Then I should see a "Applying the highstate has been scheduled." text 351ms

And I wait at most 300 seconds until event "Apply highstate in test-mode scheduled" is completed 22s 475ms

Scenario:
Apply the parametrized formula via the highstate
42s 505ms 9

When I enable repository "sle_update_repo" on this "sle_minion" without error control 725ms

And I follow "States" in the content area 74ms

And I click on "Apply Highstate" 60ms

Then I should see a "Applying the highstate has been scheduled." text 627ms

When I wait until event "Apply highstate scheduled" is completed 38s 733ms

Then the timezone on "sle_minion" should be "+05" 683ms

And the keymap on "sle_minion" should be "ca" 389ms

And the language on "sle_minion" should be "fr_FR.UTF-8" 782ms

And I disable repository "sle_update_repo" on this "sle_minion" without error control 428ms

Scenario:
Reset the formula on the minion
1s 598ms 5

When I follow "Formulas" in the content area 82ms

And I follow first "Locale" in the content area 322ms

And I click on "Clear values" and confirm alert box 516ms

And I click on "Save Formula" 82ms

Then I should see a "Formula saved" text 595ms

Scenario:
Check the pillar data after resetting the formula
22s 263ms 5

When I refresh the pillar data 4s 447ms

Then the pillar data for "formulas" should be "- locale" on "sle_minion" 4s 509ms

And the pillar data for "timezone:name" should be "CET" on "sle_minion" 5s 265ms

And the pillar data for "keyboard_and_language:keyboard_layout" should be "English (US)" on "sle_minion" 3s 745ms

And the pillar data for "keyboard_and_language:language" should be "English (US)" on "sle_minion" 4s 295ms

Scenario:
Apply the reset formula via the highstate
41s 467ms 7

And I follow "States" in the content area 69ms

And I click on "Apply Highstate" 61ms

Then I should see a "Applying the highstate has been scheduled." text 447ms

When I wait until event "Apply highstate scheduled" is completed 39s 31ms

Then the timezone on "sle_minion" should be "CET" 679ms

And the keymap on "sle_minion" should be "us" 392ms

And the language on "sle_minion" should be "en_US.UTF-8" 785ms

Scenario:
Disable the formula on the minion
11s 575ms 8

When I follow "Formulas" in the content area 79ms

Then I should see a "Choose formulas:" text 66ms

And I should see a "General System Configuration" text 314ms

And I should see a "Locale" text 90ms

When I uncheck the "locale" formula 75ms

And I click on "Save" 63ms

And I wait until I see "Formula saved." text 856ms

Then the "locale" formula should be unchecked 10s 29ms

Scenario:
Check the pillar data after disabling the formula
17s 283ms 4

When I refresh the pillar data 4s 748ms

Then the pillar data for "formulas" should be empty on "sle_minion" 3s 674ms

And the pillar data for "timezone" should be empty on "sle_minion" 4s 176ms

And the pillar data for "keyboard_and_language" should be empty on "sle_minion" 4s 683ms

Scenario:
Assign locale formula to minion via group formula
5s 453ms 17

When I follow the left menu "Systems > System Groups" 74ms

When I follow "Create Group" 426ms

And I enter "locale-formula-group" as "name" 75ms

And I enter "Test group with locale formula added" as "description" 77ms

And I click on "Create Group" 539ms

Then I should see a "System group locale-formula-group created." text 67ms

When I follow "Formulas" in the content area 72ms

Then I should see a "Choose formulas:" text 61ms

And I should see a "General System Configuration" text 286ms

And I should see a "Locale" text 89ms

When I check the "locale" formula 71ms

And I click on "Save" 63ms

And I wait until I see "Formula saved." text 603ms

And I follow "Target" 1s 407ms

And I check the "sle_minion" client 61ms

And I click on "Add Systems" 1s 373ms

Then I should see a "1 systems were added to locale-formula-group server group." text 101ms

Scenario:
Check the pillar data after assigning group formula
20s 811ms 5

When I refresh the pillar data 4s 145ms

Then the pillar data for "formulas" should be "- locale" on "sle_minion" 5s 130ms

And the pillar data for "timezone:name" should be "CET" on "sle_minion" 4s 448ms

And the pillar data for "keyboard_and_language:keyboard_layout" should be "English (US)" on "sle_minion" 3s 533ms

And the pillar data for "keyboard_and_language:language" should be "English (US)" on "sle_minion" 3s 553ms

@ssh_minion
Scenario:
No other minion is affected by the group formula
34s 823ms 3

Then the pillar data for "formulas" should be empty on "ssh_minion" 12s 75ms

And the pillar data for "timezone" should be empty on "ssh_minion" 11s 73ms

And the pillar data for "keyboard_and_language" should be empty on "ssh_minion" 11s 674ms

Scenario:
Cleanup: remove "locale-formula-group" system group
1s 935ms 7

When I follow the left menu "Systems > System Groups" 75ms

And I follow "locale-formula-group" in the content area 76ms

And I follow "Delete Group" in the content area 74ms

When I click on "Confirm Deletion" 1s 529ms

Then I should see a "System group" text 59ms

And I should see a "locale-formula-group" text 62ms

And I should see a "deleted" text 57ms

Scenario:
Cleanup: reset locale values on the minion
26s 520ms 8

Given I am on the Systems overview page of this "sle_minion" 1s 215ms

And I follow "States" in the content area 69ms

And I click on "Apply Highstate" 63ms

Then I should see a "Applying the highstate has been scheduled." text 429ms

When I wait until event "Apply highstate scheduled" is completed 22s 887ms

Then the timezone on "sle_minion" should be "CET" 677ms

And the keymap on "sle_minion" should be "us" 392ms

And the language on "sle_minion" should be "en_US.UTF-8" 785ms

@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
65ms 1

When I click on the clear SSM button 65ms

@flaky @scope_formulas
Feature:Use advanced features of Salt formulas 7m 37s 431ms 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
441ms 1

Given I am authorized 441ms

Scenario:
Install a test formula package on the server
16s 252ms 5

When I install "form.yml" to custom formula metadata directory "testform" 9s 689ms

And I install "metadata.yml" to custom formula metadata directory "testform" 6s 196ms

When I follow the left menu "Salt > Formula Catalog" 125ms

And I enter "testform" as the filtered formula name 84ms

Then I should see a "testform" text 156ms

Scenario:
Assign test formula to minion via group formula
4s 66ms 17

When I follow the left menu "Systems > System Groups" 119ms

When I follow "Create Group" 273ms

And I enter "test-formula-group" as "name" 66ms

And I enter "Test group with testform formula added" as "description" 78ms

And I click on "Create Group" 481ms

Then I should see a "System group test-formula-group created." text 72ms

When I follow "Formulas" in the content area 69ms

Then I should see a "Choose formulas:" text 62ms

And I should see a "General System Configuration" text 293ms

And I should see a "Testform" text 98ms

When I check the "testform" formula 74ms

And I click on "Save" 63ms

And I wait until I see "Formula saved." text 489ms

And I follow "Target Systems" 484ms

And I check the "sle_minion" client 62ms

And I click on "Add Systems" 1s 179ms

Then I should see a "1 systems were added to test-formula-group server group." text 98ms

Scenario:
Verify default values
1m 35s 468ms 25

When I refresh the pillar data 3s 947ms

Then the pillar data for "testing:str" should be "" on "sle_minion" 3s 408ms

And the pillar data for "testing:str_def" should be "defvalue" on "sle_minion" 3s 580ms

And the pillar data for "testing:str_or_null" should be "None" on "sle_minion" 5s 76ms

And the pillar data for "testing" should not contain "str_opt" on "sle_minion" 3s 416ms

And the pillar data for "testing:num" should be "" on "sle_minion" 3s 486ms

And the pillar data for "testing:num_def" should be "0" on "sle_minion" 4s 572ms

And the pillar data for "testing:num_or_null" should be "None" on "sle_minion" 3s 471ms

And the pillar data for "testing" should not contain "num_opt" on "sle_minion" 3s 441ms

And the pillar data for "testing:pw" should be "" on "sle_minion" 3s 386ms

And the pillar data for "testing:pw_or_null" should be "None" on "sle_minion" 4s 706ms

And the pillar data for "testing" should not contain "pw_opt" on "sle_minion" 3s 557ms

And the pillar data for "testing:list_of_strings" should contain "def_item1" on "sle_minion" 3s 517ms

And the pillar data for "testing:list_of_strings" should contain "def_item2" on "sle_minion" 3s 425ms

And the pillar data for "testing:dict_of_strings:name1" should be "def_value1" on "sle_minion" 4s 591ms

And the pillar data for "testing:dict_of_strings:name2" should be "def_value2" on "sle_minion" 4s 349ms

And the pillar data for "testing:list_of_dicts:0:name" should be "def_user" on "sle_minion" 3s 454ms

And the pillar data for "testing:list_of_dicts:0:password" should be "secret1" on "sle_minion" 3s 373ms

And the pillar data for "testing:list_of_dicts:0" should not contain "full_name" on "sle_minion" 4s 822ms

And the pillar data for "testing:dict_of_dicts:def_user:name" should be "root" on "sle_minion" 3s 561ms

And the pillar data for "testing:dict_of_dicts:def_user:password" should be "secret2" on "sle_minion" 3s 405ms

And the pillar data for "testing:dict_of_dicts:def_user:full_name" should be "None" on "sle_minion" 3s 416ms

And the pillar data for "testing:recursive_dict_of_dicts:def_gr1:group_name" should be "default group 1" on "sle_minion" 4s 622ms

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" 3s 455ms

And the pillar data for "testing:recursive_dict_of_dicts:def_gr1:entries:def_entry1:entry_desc" should be "some text" on "sle_minion" 3s 420ms

Scenario:
Fill in and verify non-default values in group formula
46s 945ms 30

When I follow the left menu "Systems > System Groups" 64ms

When I follow "test-formula-group" in the content area 71ms

And I follow "Formulas" in the content area 71ms

And I follow first "Testform" in the content area 439ms

And I click on "Expand All Sections" 598ms

And I enter "text1" as "testing#str" 112ms

And I enter "text2" as "testing#str_def" 137ms

And I enter "text3" as "testing#str_or_null" 81ms

And I enter "text4" as "testing#str_opt" 83ms

And I enter "1" as "testing#num" 59ms

And I enter "2" as "testing#num_def" 81ms

And I enter "3" as "testing#num_or_null" 62ms

And I enter "4" as "testing#num_opt" 65ms

And I enter "pw1" as "testing#pw" 96ms

And I enter "pw2" as "testing#pw_or_null" 96ms

And I enter "pw3" as "testing#pw_opt" 77ms

And I click on "Save Formula" 103ms

Then I should see a "Formula saved" text 735ms

When I wait for "1" seconds 1s

Then the pillar data for "testing:str" should be "text1" on "sle_minion" 5s 286ms

And the pillar data for "testing:str_def" should be "text2" on "sle_minion" 3s 452ms

And the pillar data for "testing:str_or_null" should be "text3" on "sle_minion" 3s 517ms

And the pillar data for "testing:str_opt" should be "text4" on "sle_minion" 5s 106ms

And the pillar data for "testing:num" should be "1" on "sle_minion" 3s 452ms

And the pillar data for "testing:num_def" should be "2" on "sle_minion" 3s 579ms

And the pillar data for "testing:num_or_null" should be "3" on "sle_minion" 3s 433ms

And the pillar data for "testing:num_opt" should be "4" on "sle_minion" 4s 596ms

And the pillar data for "testing:pw" should be "pw1" on "sle_minion" 3s 667ms

And the pillar data for "testing:pw_or_null" should be "pw2" on "sle_minion" 3s 425ms

And the pillar data for "testing:pw_opt" should be "pw3" on "sle_minion" 3s 385ms

Scenario:
Clear values in group formula and verify the defaults again
1m 34s 357ms 32

When I follow the left menu "Systems > System Groups" 88ms

When I follow "test-formula-group" in the content area 80ms

And I follow "Formulas" in the content area 64ms

And I follow first "Testform" in the content area 207ms

And I click on "Clear values" and confirm alert box 263ms

And I click on "Save Formula" 87ms

Then I should see a "Formula saved" text 573ms

When I wait for "1" seconds 1s

Then the pillar data for "testing:str" should be "" on "sle_minion" 4s 600ms

And the pillar data for "testing:str_def" should be "defvalue" on "sle_minion" 3s 410ms

And the pillar data for "testing:str_or_null" should be "None" on "sle_minion" 3s 376ms

And the pillar data for "testing" should not contain "str_opt" on "sle_minion" 4s 853ms

And the pillar data for "testing:num" should be "" on "sle_minion" 3s 152ms

And the pillar data for "testing:num_def" should be "0" on "sle_minion" 3s 402ms

And the pillar data for "testing:num_or_null" should be "None" on "sle_minion" 3s 425ms

And the pillar data for "testing" should not contain "num_opt" on "sle_minion" 4s 804ms

And the pillar data for "testing:pw" should be "" on "sle_minion" 3s 429ms

And the pillar data for "testing:pw_or_null" should be "None" on "sle_minion" 3s 416ms

And the pillar data for "testing" should not contain "pw_opt" on "sle_minion" 3s 569ms

And the pillar data for "testing:list_of_strings" should contain "def_item1" on "sle_minion" 4s 575ms

And the pillar data for "testing:list_of_strings" should contain "def_item2" on "sle_minion" 3s 521ms

And the pillar data for "testing:dict_of_strings:name1" should be "def_value1" on "sle_minion" 3s 465ms

And the pillar data for "testing:dict_of_strings:name2" should be "def_value2" on "sle_minion" 3s 434ms

And the pillar data for "testing:list_of_dicts:0:name" should be "def_user" on "sle_minion" 4s 613ms

And the pillar data for "testing:list_of_dicts:0:password" should be "secret1" on "sle_minion" 3s 460ms

And the pillar data for "testing:list_of_dicts:0" should not contain "full_name" on "sle_minion" 3s 523ms

And the pillar data for "testing:dict_of_dicts:def_user:name" should be "root" on "sle_minion" 3s 426ms

And the pillar data for "testing:dict_of_dicts:def_user:password" should be "secret2" on "sle_minion" 4s 496ms

And the pillar data for "testing:dict_of_dicts:def_user:full_name" should be "None" on "sle_minion" 4s 143ms

And the pillar data for "testing:recursive_dict_of_dicts:def_gr1:group_name" should be "default group 1" on "sle_minion" 3s 445ms

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" 3s 382ms

And the pillar data for "testing:recursive_dict_of_dicts:def_gr1:entries:def_entry1:entry_desc" should be "some text" on "sle_minion" 5s 62ms

Scenario:
Fill in and verify mix of default and non-default values in group formula
44s 637ms 23

When I follow the left menu "Systems > System Groups" 61ms

When I follow "test-formula-group" in the content area 59ms

And I follow "Formulas" in the content area 68ms

And I follow first "Testform" in the content area 224ms

And I click on "Expand All Sections" 206ms

And I enter "text1" as "testing#str" 103ms

And I enter "1" as "testing#num" 75ms

And I enter "2" as "testing#num_def" 74ms

And I enter "pw1" as "testing#pw" 100ms

And I click on "Save Formula" 81ms

Then I should see a "Formula saved" text 746ms

When I wait for "1" seconds 1s

Then the pillar data for "testing:str" should be "text1" on "sle_minion" 3s 428ms

And the pillar data for "testing:str_def" should be "defvalue" on "sle_minion" 3s 477ms

And the pillar data for "testing:str_or_null" should be "None" on "sle_minion" 4s 791ms

And the pillar data for "testing" should not contain "str_opt" on "sle_minion" 3s 473ms

And the pillar data for "testing:num" should be "1" on "sle_minion" 3s 423ms

And the pillar data for "testing:num_def" should be "2" on "sle_minion" 3s 516ms

And the pillar data for "testing:num_or_null" should be "None" on "sle_minion" 4s 685ms

And the pillar data for "testing" should not contain "num_opt" on "sle_minion" 3s 294ms

And the pillar data for "testing:pw" should be "pw1" on "sle_minion" 3s 429ms

And the pillar data for "testing:pw_or_null" should be "None" on "sle_minion" 3s 432ms

And the pillar data for "testing" should not contain "pw_opt" on "sle_minion" 4s 883ms

Scenario:
Verify that minion form inherits the values from group form
45s 189ms 16

Given I am on the Systems overview page of this "sle_minion" 1s 152ms

When I follow "Formulas" in the content area 68ms

And I follow first "Testform" in the content area 209ms

And I click on "Save Formula" 345ms

Then I should see a "Formula saved" text 670ms

And the pillar data for "testing:str" should be "text1" on "sle_minion" 3s 504ms

And the pillar data for "testing:str_def" should be "defvalue" on "sle_minion" 3s 399ms

And the pillar data for "testing:str_or_null" should be "None" on "sle_minion" 4s 733ms

And the pillar data for "testing" should not contain "str_opt" on "sle_minion" 4s 400ms

And the pillar data for "testing:num" should be "1" on "sle_minion" 3s 368ms

And the pillar data for "testing:num_def" should be "2" on "sle_minion" 3s 450ms

And the pillar data for "testing:num_or_null" should be "None" on "sle_minion" 4s 977ms

And the pillar data for "testing" should not contain "num_opt" on "sle_minion" 3s 461ms

And the pillar data for "testing:pw" should be "pw1" on "sle_minion" 3s 406ms

And the pillar data for "testing:pw_or_null" should be "None" on "sle_minion" 3s 422ms

And the pillar data for "testing" should not contain "pw_opt" on "sle_minion" 4s 618ms

Scenario:
Fill in and verify non-default values in minion formula
44s 766ms 28

When I follow "Formulas" in the content area 75ms

And I follow first "Testform" in the content area 270ms

And I click on "Expand All Sections" 225ms

And I enter "min_text1" as "testing#str" 184ms

And I enter "min_text2" as "testing#str_def" 165ms

And I enter "min_text3" as "testing#str_or_null" 113ms

And I enter "min_text4" as "testing#str_opt" 115ms

And I enter "101" as "testing#num" 78ms

And I enter "102" as "testing#num_def" 92ms

And I enter "103" as "testing#num_or_null" 76ms

And I enter "104" as "testing#num_opt" 84ms

And I enter "min_pw1" as "testing#pw" 125ms

And I enter "min_pw2" as "testing#pw_or_null" 117ms

And I enter "min_pw3" as "testing#pw_opt" 114ms

And I click on "Save Formula" 80ms

Then I should see a "Formula saved" text 748ms

When I wait for "1" seconds 1s

Then the pillar data for "testing:str" should be "min_text1" on "sle_minion" 3s 399ms

And the pillar data for "testing:str_def" should be "min_text2" on "sle_minion" 3s 534ms

And the pillar data for "testing:str_or_null" should be "min_text3" on "sle_minion" 4s 429ms

And the pillar data for "testing:str_opt" should be "min_text4" on "sle_minion" 3s 520ms

And the pillar data for "testing:num" should be "101" on "sle_minion" 3s 400ms

And the pillar data for "testing:num_def" should be "102" on "sle_minion" 3s 391ms

And the pillar data for "testing:num_or_null" should be "103" on "sle_minion" 4s 540ms

And the pillar data for "testing:num_opt" should be "104" on "sle_minion" 3s 495ms

And the pillar data for "testing:pw" should be "min_pw1" on "sle_minion" 3s 452ms

And the pillar data for "testing:pw_or_null" should be "min_pw2" on "sle_minion" 3s 416ms

And the pillar data for "testing:pw_opt" should be "min_pw3" on "sle_minion" 4s 512ms

Scenario:
Clear values in minion formula and verify that the pillar is set to group values
44s 422ms 17

When I follow "Formulas" in the content area 85ms

And I follow first "Testform" in the content area 269ms

And I click on "Clear values" and confirm alert box 440ms

And I click on "Save Formula" 69ms

Then I should see a "Formula saved" text 583ms

When I wait for "1" seconds 1s

Then the pillar data for "testing:str" should be "text1" on "sle_minion" 3s 362ms

And the pillar data for "testing:str_def" should be "defvalue" on "sle_minion" 3s 429ms

And the pillar data for "testing:str_or_null" should be "None" on "sle_minion" 4s 953ms

And the pillar data for "testing" should not contain "str_opt" on "sle_minion" 3s 437ms

And the pillar data for "testing:num" should be "1" on "sle_minion" 3s 423ms

And the pillar data for "testing:num_def" should be "2" on "sle_minion" 3s 357ms

And the pillar data for "testing:num_or_null" should be "None" on "sle_minion" 5s 17ms

And the pillar data for "testing" should not contain "num_opt" on "sle_minion" 3s 646ms

And the pillar data for "testing:pw" should be "pw1" on "sle_minion" 3s 357ms

And the pillar data for "testing:pw_or_null" should be "None" on "sle_minion" 3s 453ms

And the pillar data for "testing" should not contain "pw_opt" on "sle_minion" 4s 536ms

Scenario:
Cleanup: remove formula from minion
11s 98ms 5

When I follow "Formulas" in the content area 69ms

And I uncheck the "testform" formula 269ms

And I click on "Save" 64ms

And I wait until I see "Formula saved." text 664ms

Then the "testform" formula should be unchecked 10s 31ms

Scenario:
Cleanup: remove "test-formula-group" system group
9s 784ms 9

When I follow the left menu "Systems > System Groups" 79ms

And I follow "test-formula-group" in the content area 71ms

And I follow "Delete Group" in the content area 72ms

When I click on "Confirm Deletion" 61ms

Then I should see a "System group" text 63ms

Then I should see a "test-formula-group" text 57ms

And I should see a "deleted" text 62ms

And I wait until there is no pillar refresh salt job active 5s 912ms

Then the pillar data for "testing" should be empty on "sle_minion" 3s 401ms

@skip_if_github_validation @scope_openscap
Feature:OpenSCAP audit of Salt minion 2m 11s 963ms 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
2s 324ms 2

Given I am authorized for the "Admin" section 480ms

And I am on the Systems overview page of this "sle_minion" 1s 843ms

@Uyuni
Scenario:
Enable required repositories
724ms 1

When I enable repository "repo-oss" on this "sle_minion" without error control 724ms

@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
22s 187ms 2 3 1

When I refresh the metadata for "sle_minion" 828ms

And I install OpenSCAP dependencies on "sle_minion" 674ms 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:172:in `run_local'
./features/support/remote_node.rb:120:in `run'
./features/step_definitions/command_steps.rb:989:in `/^I install packages? "([^"]*)" on this "([^"]*)"((?: without error control)?)$/'
./features/step_definitions/command_steps.rb:967: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

20s 684ms Show Info + 
23:35:31:000 - 23:35:33: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 238ms 3 5 1

When I follow "Audit" in the content area 72ms

And I follow "OpenSCAP" in the content area 77ms

And I follow "Schedule" in the content area 72ms

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 16ms Show Error + 
                                            
 execution expired (Timeout::Error)
./features/support/commonlib.rb:89: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
10s 11ms 8 1

When I follow "Audit" in the content area 10s 11ms Show Error + 
                                            
 Unable to find xpath "//section" (Capybara::ElementNotFound)
./features/step_definitions/navigation_steps.rb:387: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
10s 10ms 8 1

When I follow "Audit" in the content area 10s 10ms Show Error + 
                                            
 Unable to find xpath "//section" (Capybara::ElementNotFound)
./features/step_definitions/navigation_steps.rb:387: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
10s 12ms 6 1

When I follow "Audit" in the content area 10s 12ms Show Error + 
                                            
 Unable to find xpath "//section" (Capybara::ElementNotFound)
./features/step_definitions/navigation_steps.rb:387: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
10s 4ms 5 1

When I follow the left menu "Admin > Organizations" 10s 4ms Show Error + 
                                            
 Unable to find xpath "//aside/div[@id='nav']/nav/ul/li/div/a[contains(.,'Admin')]/parent::div/parent::li" (Capybara::ElementNotFound)
./features/step_definitions/navigation_steps.rb:441:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:433:in `each'
./features/step_definitions/navigation_steps.rb:433:in `each_with_index'
./features/step_definitions/navigation_steps.rb:433: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
31s 115ms 2 6 1

Requested /rhn/systems/details/Overview.do?sid=1000010023, got https://uyuni-master-server.sumaci.aws/rhn/manager/login?url_bounce=%2Frhn%2Fsystems%2Fdetails%2FOverview.do%3Fsid%3D1000010023&request_method=GET

Given I am on the Systems overview page of this "sle_minion" 838ms

When I follow "Audit" in the content area 10s 35ms Show Error + 
                                            
 Unable to find link "Audit" within #(Capybara::Node::Element tag="section" path="/HTML/BODY[1]/DIV[1]/DIV[1]/SECTION[1]") (Capybara::ElementNotFound)
./features/support/commonlib.rb:192:in `click_link_and_wait'
./features/step_definitions/navigation_steps.rb:366:in `/^I follow "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:388:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:387:in `/^I follow "([^"]*)" in the (.+)$/'
features/secondary/min_salt_openscap_audit.feature:121: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 "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

20s 241ms Show Info + 
23:39:00:000 - 23:39:11:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/login?url_bounce=%2Frhn%2Fsystems%2Fdetails%2FOverview.do%3Fsid%3D1000010023&request_method=GET
Screenshot +

Scenario:
Cleanup: restore audit scans retention period
812ms 6

When I follow the left menu "Admin > Organizations" 132ms

When I follow "SUSE Test" in the content area 69ms

And I follow "Configuration" in the content area 64ms

And I enter "90" as "scap_retention_period" 52ms

And I click on "Update Organization" 423ms

Then I should see a "Organization SUSE Test was successfully updated." text 70ms

Scenario:
Cleanup: remove the OpenSCAP packages from the SLE minion
1s 91ms 1

When I remove OpenSCAP dependencies from "sle_minion" 1s 91ms

@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 1m 1s 944ms 4

Scenario:
Log in as org admin user
433ms 1

Given I am authorized 433ms

Scenario:
Create a user-defined state
17s 843ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 527ms

When I follow "States" in the content area 83ms

And I install a user-defined state for "sle_minion" on the server 9s 772ms

And I follow "Highstate" in the content area 65ms

And I click on "Show full highstate output" 351ms

And I wait for "6" seconds 6s

Then I should see a "user_defined_state" or "running as PID" text in element "highstate" 43ms

Scenario:
Trigger highstate from API
23s 627ms 3

When I schedule a highstate for "sle_minion" via API 884ms

And I wait until event "Apply highstate scheduled" is completed 22s 65ms

Then file "/tmp/test_user_defined_state" should exist on "sle_minion" 677ms

Scenario:
Cleanup: remove user-defined state and the file it created
20s 40ms 7

When I follow "States" in the content area 83ms

And I uninstall the user-defined state from the server 3s 204ms

And I uninstall the managed file from "sle_minion" 397ms

And I follow "Highstate" in the content area 66ms

And I click on "Show full highstate output" 237ms

And I wait for "6" seconds 6s

Then I should not see a "user_defined_state" text in element "highstate" 10s 52ms

@scope_salt
Feature:Verify the minion registration 30s 6ms 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
458ms 1

Given I am authorized 458ms

Scenario:
Check the Salt entitlement
1s 658ms 2

Given I am on the Systems overview page of this "sle_minion" 1s 561ms

Then I should see a "[Salt]" text 97ms

Scenario:
Check that installed packages are visible
1s 252ms 3

When I follow "Software" in the content area 98ms

And I follow "List / Remove" 850ms

Then I should see a "aaa_base" text 303ms

Scenario:
Check that Hardware Refresh button works on a SLES Salt minion
25s 649ms 6

When I follow "Details" in the content area 73ms

And I follow "Hardware" in the content area 70ms

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 594ms

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "sle_minion" 2s 8ms

Scenario:
Check that Update Properties button works
987ms 4

When I follow "Details" in the content area 59ms

And I follow "Hardware" in the content area 79ms

And I click on "Update Properties" 728ms

Then I should see a "Networking properties updated." text 120ms

@sle_minion @scope_configuration_channels
Feature:Configuration state channels 1m 55s 421ms 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
414ms 1

Given I am authorized 414ms

Scenario:
Create a state channel
1s 743ms 12

When I follow the left menu "Configuration > Channels" 124ms

And I follow "Create State Channel" 284ms

Then I should see a "New Config State Channel" text 58ms

When I enter "My State Channel" as "cofName" 72ms

And I enter "statechannel" as "cofLabel" 60ms

And I enter "This is a state channel" as "cofDescription" 73ms

And I enter "touch /root/foobar:\n cmd.run:\n - creates: /root/foobar" in the editor 5ms

And I click on "Create Config State Channel" 800ms

Then I should see a "State Channel" text 69ms

And I should see a "Channel Properties" text 63ms

And I should see a "Channel Information" text 62ms

And I should see a "Configuration Actions" text 67ms

Scenario:
Subscribe a minion to the state channel
2s 789ms 8

When I am on the Systems overview page of this "sle_minion" 1s 16ms

And I follow "Configuration" in the content area 70ms

And I follow "Manage Configuration Channels" in the content area 68ms

And I follow first "Subscribe to Channels" in the content area 63ms

And I check "My State Channel" in the list 63ms

And I click on "Continue" 613ms

And I click on "Update Channel Rankings" 816ms

Then I should see a "Channel Subscriptions successfully changed for" text 78ms

Scenario:
Salt state details
1s 199ms 7

When I follow the left menu "Configuration > Channels" 109ms

And I follow "My State Channel" 436ms

Then I should see a "1 system subscribed" text 66ms

When I follow "View/Edit 'init.sls' File" 349ms

Then I should see a "Revision 1 of /init.sls from channel My State Channel" text 81ms

And I should see a "File Contents" text 76ms

And I should see a "touch /root/foobar:" text 79ms

Scenario:
Apply the new state
24s 508ms 8

When I am on the Systems overview page of this "sle_minion" 928ms

And I follow "States" in the content area 68ms

And I follow "Configuration Channels" in the content area 67ms

Then I should see a "Execute States" button 219ms

When I click on "Execute States" 78ms

Then I should see a "Applying the config channels has been scheduled" text 269ms

When I wait until event "Apply states [custom] scheduled" is completed 22s 189ms

And I wait until file "/root/foobar" exists on "sle_minion" 686ms

Scenario:
Try to remove init.sls file
1s 960ms 7

When I follow the left menu "Configuration > Channels" 103ms

And I follow "My State Channel" 434ms

And I follow "View/Edit 'init.sls' File" 324ms

When I follow "Delete" 331ms

And I click on "Delete Configuration Revision" 591ms

Then I should see a "Cannot delete the only revision for the init.sls file" text 85ms

And I should see a "Revision 1 of /init.sls from channel My State Channel" text 89ms

Scenario:
Cleanup: remove the state channel and the file
1s 781ms 7

When I follow the left menu "Configuration > Channels" 61ms

And I follow "My State Channel" 419ms

And I follow "Delete Channel" 311ms

Then I should see a "Are you sure you want to delete this config channel?" text 56ms

When I click on "Delete Config Channel" 61ms

Then I should see a "Channel 'My State Channel' has been deleted." text 477ms

And I remove "/root/foobar" from "sle_minion" 393ms

Scenario:
Create the 1st state channel
948ms 12

When I follow the left menu "Configuration > Channels" 68ms

And I follow "Create State Channel" 264ms

Then I should see a "New Config State Channel" text 57ms

When I enter "My State Channel" as "cofName" 70ms

And I enter "statechannel" as "cofLabel" 82ms

And I enter "This is a state channel" as "cofDescription" 67ms

And I enter "touch /root/statechannel:\n cmd.run:\n - creates: /root/statechannel" in the editor 4ms

And I click on "Create Config State Channel" 69ms

Then I should see a "State Channel" text 68ms

And I should see a "Channel Properties" text 63ms

And I should see a "Channel Information" text 65ms

And I should see a "Configuration Actions" text 64ms

Scenario:
Create the 2nd state channel with same name
2s 490ms 12

When I follow the left menu "Configuration > Channels" 62ms

And I follow "Create State Channel" 291ms

Then I should see a "New Config State Channel" text 58ms

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" 1s 630ms

Then I should see a "State Channel" text 67ms

And I should see a "Channel Properties" text 63ms

And I should see a "Channel Information" text 66ms

And I should see a "Configuration Actions" text 64ms

Scenario:
Create the 3rd state channel with spacecmd
27s 796ms 9

When I create channel "statechannel3" from spacecmd of type "state" 3s 493ms

And I follow the left menu "Configuration > Channels" 60ms

Then I should see a "statechannel3" text 66ms

When I update init.sls from spacecmd with content "touch /tmp/statechannel3:\n cmd.run:\n - creates: /tmp/statechannel3" for channel "statechannel3" 8s 204ms

And I get "/init.sls" file details for channel "statechannel3" via spacecmd 4s 565ms

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" 8s 309ms

And I get "/init.sls" file details for channel "statechannel3" via spacecmd 3s 97ms

Then I should see "Revision: 100" in the output < 1ms

Scenario:
Subscribe a minion to 1st and 2nd state channels
2s 345ms 15

When I am on the Systems overview page of this "sle_minion" 939ms

And I follow "States" in the content area 78ms

And I follow "Configuration Channels" in the content area 89ms

And I click on "Search" in element "search-row" 72ms

Then I should see a "My State Channel" text 274ms

And I should see a "statechannel" text 73ms

And I should see a "statechannel2" text 70ms

When I check "statechannel-cbox" 89ms

And I check "statechannel2-cbox" 79ms

And I click on "Save Changes" 66ms

And I wait until I see "Edit Channel Ranks" text 62ms

Then I should see a "My State Channel (statechannel)" text 60ms

And I should see a "My State Channel (statechannel2)" text 64ms

When I click on "Confirm" 57ms

Then I should see a "State assignments have been saved." text 267ms

Scenario:
Apply the Configuration channel state
24s 23ms 9

When I follow "States" in the content area 59ms

And I follow "Configuration Channels" in the content area 58ms

And I click on "Search" in element "search-row" 64ms

And I wait until I see "Execute States" text 65ms

And I click on "Execute States" 86ms

Then I should see a "Applying the config channels has been scheduled" text 394ms

And I wait until event "Apply states [custom] scheduled" is completed 22s 215ms

And I wait until file "/root/statechannel" exists on "sle_minion" 687ms

And I wait until file "/root/statechannel2" exists on "sle_minion" 390ms

Scenario:
Subscribe a minion to the 3rd state channel
1s 190ms 12

When I follow "States" in the content area 59ms

And I follow "Configuration Channels" in the content area 58ms

Then I should see a "My State Channel" text 272ms

And I should see a "statechannel3" text 67ms

When I check "statechannel3-cbox" 88ms

And I click on "Save Changes" 68ms

And I wait until I see "Edit Channel Ranks" text 61ms

And I should see a "My State Channel (statechannel)" text 61ms

And I should see a "My State Channel (statechannel2)" text 62ms

And I should see a "statechannel3 (statechannel3)" text 60ms

When I click on "Confirm" 57ms

Then I should see a "State assignments have been saved." text 273ms

Scenario:
Apply the Configuration channel state with spacecmd
16s 519ms 2

When I schedule apply configchannels for "sle_minion" 8s 163ms

And I wait until file "/root/statechannel3" exists on "sle_minion" 8s 355ms

Scenario:
Cleanup: remove the 1st state channel and the deployed file
2s 80ms 7

When I follow the left menu "Configuration > Channels" 124ms

And I follow first "My State Channel" 548ms

And I follow "Delete Channel" 298ms

Then I should see a "Are you sure you want to delete this config channel?" text 59ms

When I click on "Delete Config Channel" 591ms

Then I should see a "Channel 'My State Channel' has been deleted." text 70ms

When I remove "/root/statechannel" from "sle_minion" 387ms

Scenario:
Cleanup: remove the 2nd state channel and the deployed file
1s 889ms 7

When I follow the left menu "Configuration > Channels" 63ms

And I follow first "My State Channel" 519ms

And I follow "Delete Channel" 295ms

Then I should see a "Are you sure you want to delete this config channel?" text 56ms

When I click on "Delete Config Channel" 498ms

Then I should see a "Channel 'My State Channel' has been deleted." text 63ms

When I remove "/root/statechannel2" from "sle_minion" 393ms

Scenario:
Cleanup: remove the 3rd state channel and the deployed file
1s 739ms 7

When I follow the left menu "Configuration > Channels" 63ms

And I follow first "statechannel3" 439ms

And I follow "Delete Channel" 293ms

Then I should see a "Are you sure you want to delete this config channel?" text 57ms

When I click on "Delete Config Channel" 438ms

Then I should see a "Channel 'statechannel3' has been deleted." text 53ms

When I remove "/root/statechannel3" from "sle_minion" 393ms

Feature:Configuration state channels via API 54s 753ms 3

Scenario:
Create a state channel via API
50s 688ms 2 2

When I create state channel "statechannel1" via API 2s 37ms Show Error + 
                                            
 Unexpected HTTP status code 401 (ScriptError)
./features/support/http_client.rb:91:in `call'
./features/support/api_test.rb:80:in `ensure in block (2 levels) in call'
./features/support/api_test.rb:81:in `block (2 levels) in call'
./features/support/api_test.rb:75:in `synchronize'
./features/support/api_test.rb:75:in `block in call'
features/secondary/min_config_state_channel_api.feature:7:in `I create state channel "statechannel1" via API'

And I call configchannel.get_file_revision() with file "/init.sls", revision "1" and channel "statechannel1" via API 0s

Then I should get file contents "" 0s

48s 650ms Show Error + 
                                            
 User is not logged in (ScriptError)
./features/step_definitions/navigation_steps.rb:655:in `/^I should be logged in$/'
./features/step_definitions/navigation_steps.rb:635:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/support/env.rb:222:in `block in relog_and_visit_previous_url'
./features/support/env.rb:220:in `relog_and_visit_previous_url'
./features/support/env.rb:200:in `handle_screenshot_and_relog'
./features/support/env.rb:162:in `After'
Show Info + 
23:43:50:000 - 23:44:03:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/configuration/GlobalConfigChannelList.do
Screenshot +

Scenario:
Create a state channel with contents via API
2s 33ms 2 1

When I create state channel "statechannel2" containing "touch /root/foobar:\n cmd.run:\n - creates: /root/foobar" via API 2s 33ms Show Error + 
                                            
 Unexpected HTTP status code 401 (ScriptError)
./features/support/http_client.rb:91:in `call'
./features/support/api_test.rb:80:in `ensure in block (2 levels) in call'
./features/support/api_test.rb:81:in `block (2 levels) in call'
./features/support/api_test.rb:75:in `synchronize'
./features/support/api_test.rb:75:in `block in call'
features/secondary/min_config_state_channel_api.feature:12:in `I create state channel "statechannel2" containing "touch /root/foobar:\n  cmd.run:\n    - creates: /root/foobar" via API'

And I call configchannel.get_file_revision() with file "/init.sls", revision "1" and channel "statechannel2" via API 0s

Then I should get file contents "touch /root/foobar:\n cmd.run:\n - creates: /root/foobar" 0s

Scenario:
Cleanup: remove state channels via API
2s 32ms 1 1

Then I delete channel "statechannel1" via API without error control 2s 32ms Show Error + 
                                            
 Unexpected HTTP status code 401 (ScriptError)
./features/support/http_client.rb:91:in `call'
./features/support/api_test.rb:80:in `ensure in block (2 levels) in call'
./features/support/api_test.rb:81:in `block (2 levels) in call'
./features/support/api_test.rb:75:in `synchronize'
./features/support/api_test.rb:75:in `block in call'
features/secondary/min_config_state_channel_api.feature:17:in `I delete channel "statechannel1" via API without error control'

And I delete channel "statechannel2" via API without error control 0s

@skip_if_github_validation @scope_salt
Feature:System package list is updated if packages are manually installed or removed 1m 39s 142ms 7

Scenario:
Pre-requisite: install milkyway-dummy-1.0 package
3s 383ms 3

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 724ms

And I refresh the metadata for "sle_minion" 940ms

And I install old package "milkyway-dummy-1.0" on this "sle_minion" without error control 1s 718ms

Scenario:
Pre-requisite: refresh package list and check installed packages on SLE minion client
25s 991ms 3

When I refresh packages list via spacecmd on "sle_minion" 7s 549ms

And I wait until refresh package list on "sle_minion" is finished 12s 260ms

Then spacecmd should show packages "milkyway-dummy-1.0" installed on "sle_minion" 6s 182ms

Scenario:
Log in as org admin user
10s 753ms 1

Given I am authorized for the "Admin" section 10s 753ms

Scenario:
Pre-requisite: ensure the errata cache is computed before package list tests
18s 825ms 11

Given I am on the Systems overview page of this "sle_minion" 1s 677ms

When I follow "Software" in the content area 79ms

And I follow "List / Remove" in the content area 64ms

And I enter "milkyway-dummy" as the filtered package name 164ms

And I click on the filter button until page does contain "milkyway-dummy-1.0" text 11s 33ms

And I follow the left menu "Admin > Task Schedules" 127ms

And I follow "errata-cache-default" 427ms

And I follow "errata-cache-bunch" 1s 249ms

And I click on "Single Run Schedule" 1s 529ms

Then I should see a "bunch was scheduled" text 265ms

When I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 2s 208ms

Scenario:
Remove manually a package on a minion
23s 45ms 8

Given I am on the Systems overview page of this "sle_minion" 1s 16ms

When I follow "Software" in the content area 73ms

And I follow "List / Remove" 916ms

And I enter "milkyway-dummy" as the filtered package name 149ms

And I click on the filter button 1s 134ms

Then I should see a "milkyway-dummy" text 71ms

When I remove package "milkyway-dummy" from this "sle_minion" 1s 845ms

And I click on the filter button until page does not contain "milkyway-dummy" text 17s 838ms

Scenario:
Install manually a package on a minion
14s 104ms 7

When I follow "Software" in the content area 75ms

And I follow "List / Remove" 832ms

And I enter "milkyway-dummy" as the filtered package name 161ms

And I click on the filter button 825ms

Then I should not see a "milkyway-dummy" text 64ms

When I install package "milkyway-dummy" on this "sle_minion" 2s 69ms

And I click on the filter button until page does not contain "milkyway-dummy" text 10s 75ms

Scenario:
Cleanup: remove milkyway-dummy packages from SLES minion
3s 38ms 3

When I disable repository "test_repo_rpm_pool" on this "sle_minion" 740ms

And I remove package "milkyway-dummy" from this "sle_minion" without error control 1s 559ms

And I refresh the metadata for "sle_minion" 738ms

@susemanager @sle_minion @scope_monitoring @skip_if_github_validation
Feature:Monitor MLM environment with Prometheus on a SLE Salt minion < 1ms 9

In order to monitor Uyuni server
As an authorized user
I want to enable Prometheus exporters

Scenario:
Log in as org admin user
< 1ms 1

Given I am authorized 0s

Scenario:
Apply Prometheus and Prometheus exporter formulas
< 1ms 8

Given I am on the Systems overview page of this "sle_minion" 0s

When I follow "Formulas" in the content area 0s

And I should see a "Choose formulas:" text 0s

And I should see a "Monitoring" text 0s

And I check the "prometheus" formula 0s

And I check the "prometheus-exporters" formula 0s

And I click on "Save" 0s

Then I wait until I see "Formula saved" text 0s

Scenario:
Configure Prometheus formula
< 1ms 7

When I follow "Formulas" in the content area 0s

And I follow "Prometheus" in the content area 0s

And I click on "Expand All Sections" 0s

And I enter "admin" as "Username" 0s

And I enter "admin" as "Password" 0s

And I click on "Save Formula" 0s

Then I should see a "Formula saved" text 0s

Scenario:
Configure Prometheus exporter formula
< 1ms 9

When I follow "Formulas" in the content area 0s

And I follow "Prometheus Exporters" in the content area 0s

And I click on "Expand All Sections" 0s

And I should see a "Enable and configure Prometheus exporters for managed systems." text 0s

And I check "node" exporter 0s

And I check "apache" exporter 0s

And I check "postgres" exporter 0s

And I click on "Save" 0s

Then I should see a "Formula saved" text 0s

Scenario:
Apply highstate for Prometheus exporters
< 1ms 4

When I follow "States" in the content area 0s

And I click on "Apply Highstate" 0s

Then I should see a "Applying the highstate has been scheduled." text 0s

And I wait until event "Apply highstate scheduled" is completed 0s

Scenario:
Wait for services
< 1ms 4

When I wait until "prometheus" service is active on "sle_minion" 0s

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

Scenario:
Visit monitoring endpoints on the minion
< 1ms 4

When I visit "Prometheus" endpoint of this "sle_minion" 0s

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

Scenario:
Cleanup: undo Prometheus and Prometheus exporter formulas
< 1ms 5

When I follow "Formulas" in the content area 0s

And I uncheck the "prometheus" formula 0s

And I uncheck the "prometheus-exporters" formula 0s

And I click on "Save" 0s

Then I wait until I see "Formula saved" text 0s

Scenario:
Cleanup: apply highstate after test monitoring
< 1ms 4

And I follow "States" in the content area 0s

And I click on "Apply Highstate" 0s

Then I should see a "Applying the highstate has been scheduled." text 0s

And I wait until event "Apply highstate scheduled" is completed 0s

@skip_if_github_validation @no_mirror
Feature:SCC user credentials in the Setup Wizard < 1ms 7

As a systems administrator
In order to manage organization's access to SUSE Customer Service
I want to create, edit, and delete its credentials

Scenario:
Log in as admin user
< 1ms 1

Given I am authorized for the "Admin" section 0s

Scenario:
Enter some invalid organization credentials
< 1ms 7

When I follow the left menu "Admin > Setup Wizard > Organization Credentials" 0s

And I ask to add new credentials 0s

And I enter "SCC user" as "edit-user" 0s

And I enter "SCC password" as "edit-password" 0s

And I click on "Save" 0s

Then I should see a "SCC user" text 0s

And the credentials for "SCC user" should be invalid 0s

Scenario:
Make the credentials primary
< 1ms 3

When I follow the left menu "Admin > Setup Wizard > Organization Credentials" 0s

And I make the credentials for "SCC user" primary 0s

Then the credentials for "SCC user" should be primary 0s

Scenario:
Check the associated subscription list
< 1ms 4

When I follow the left menu "Admin > Setup Wizard > Organization Credentials" 0s

And I view the subscription list for "SCC user" 0s

And I wait until I see "No subscriptions available" text 0s

And I click on "Close" 0s

Scenario:
Enter duplicate SCC credentials
< 1ms 14

Given I am authorized for the "Admin" section 0s

When I follow the left menu "Admin > Setup Wizard > Organization Credentials" 0s

And I ask to add new credentials 0s

And I enter "invalidname" as "edit-user" 0s

And I enter "invalidpw" as "edit-password" 0s

And I click on "Save" 0s

Then the credentials for "invalidname" should be invalid 0s

When I ask to add new credentials 0s

And I enter "invalidname" as "edit-user" 0s

And I enter "invalidpw" as "edit-password" 0s

And I click on "Save" 0s

Then I should see a "Credentials with this username already exist" text 0s

When I click on "Cancel" 0s

Then the credentials for "invalidname" should be invalid 0s

Scenario:
Edit credentials
< 1ms 11

Given I am authorized for the "Admin" section 0s

When I follow the left menu "Admin > Setup Wizard > Organization Credentials" 0s

And I ask to edit the credentials for "invalidname" 0s

And I enter "SCC user" as "edit-user" 0s

And I enter "geekogeeko" as "edit-password" 0s

And I click on "Save" 0s

Then I should see a "Credentials with this username already exist" text 0s

When I enter "invalidgeeko" as "edit-user" 0s

And I click on "Save" 0s

Then I should see a "invalidgeeko" text 0s

And the credentials for "invalidgeeko" should be invalid 0s

Scenario:
Cleanup: delete the new organization credentials
< 1ms 9

When I follow the left menu "Admin > Setup Wizard > Organization Credentials" 0s

And I wait for the trash icon to appear for "SCC user" 0s

And I ask to delete the credentials for "SCC user" 0s

And I click on "Delete" in "Are you sure you want to delete these credentials?" modal 0s

Then I wait until I do not see "SCC user" text 0s

When I wait for the trash icon to appear for "invalidgeeko" 0s

And I ask to delete the credentials for "invalidgeeko" 0s

And I click on "Delete" in "Are you sure you want to delete these credentials?" modal 0s

Then I wait until I do not see "invalidgeeko" text 0s

@scope_cve_audit
Feature:Support for new CVE-ID syntax 7s 101ms 4

Scenario:
Log in as org admin user
515ms 1

Given I am authorized 515ms

Scenario:
Check perseus-dummy-7891 patches
1s 455ms 7

When I follow the left menu "Patches > Patch List > All" 198ms

And I enter "dummy" as the filtered synopsis 172ms

And I click on the filter button 545ms

And I follow "perseus-dummy-7891" 447ms

Then I should see a "perseus-dummy-7891 - Security Advisory" text 67ms

And I should see a "CVE-1999-12345" link 13ms

And I should see a "CVE-1999-99781" link 11ms

Scenario:
Check local metadata for long CVE IDs
4s 233ms 5

When I refresh the metadata for "sle_minion" 1s 52ms

Then I should have 'reference.*id="CVE-1999-12345' in the patch metadata for "sle_minion" 791ms

And I should have 'reference.*id="CVE-1999-99781' in the patch metadata for "sle_minion" 793ms

And I should have 'reference.*http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-1999-12345' in the patch metadata for "sle_minion" 801ms

And I should have 'reference.*http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-1999-99781' in the patch metadata for "sle_minion" 793ms

Scenario:
Search for CVE ID with the new format
897ms 5

When I follow the left menu "Patches > Advanced Search" 65ms

When I enter "CVE-1999-12345" as "search_string" in the content area 81ms

And I click on "Search" 646ms

Then I should see a "Advanced Search" text 81ms

And I should see a "perseus-dummy-7891" link in the content area 22ms

@scope_onboarding
Feature:Display patches 1m 11s 863ms 8

Scenario:
Log in as org admin user
467ms 1

Given I am authorized for the "Admin" section 467ms

Scenario:
Pre-require: enable old packages to fake a possible installation
10s 791ms 10

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 728ms

And I refresh the metadata for "sle_minion" 759ms

And I install old package "andromeda-dummy-1.0" on this "sle_minion" 1s 648ms

And I install old package "virgo-dummy-1.0" on this "sle_minion" 1s 634ms

When I follow the left menu "Admin > Task Schedules" 126ms

And I follow "errata-cache-default" 1s 194ms

And I follow "errata-cache-bunch" 1s 599ms

And I click on "Single Run Schedule" 411ms

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 420ms

Scenario:
Check all patches exist
31s 280ms 8

When I follow the left menu "Patches > Patch List > Relevant" 210ms

Then I should see an update in the list 92ms

When I wait until I see "andromeda-dummy" text, refreshing the page 30s 315ms

Then I should see a "andromeda-dummy-6789" link 12ms

When I enter "virgo-dummy" as the filtered synopsis 120ms

And I click on the filter button 453ms

And I wait until I see "virgo-dummy" text 63ms

Then I should see a "virgo-dummy-3456" link 11ms

Scenario:
Check SLES release 6789 patches
1s 349ms 6

When I follow the left menu "Patches > Patch List > Relevant" 86ms

And I follow "andromeda-dummy-6789" 1s 55ms

Then I should see a "andromeda-dummy-6789 - Bug Fix Advisory" text 66ms

And I should see a "Test update for andromeda-dummy" text 63ms

And I should see a "Fake-RPM-SUSE-Channel" link 11ms

And I should see a "reboot_suggested" text 67ms

Scenario:
Check packages of SLES release 6789 patches
1s 390ms 6

When I follow the left menu "Patches > Patch List > Relevant" 69ms

And I follow "andromeda-dummy-6789" 564ms

And I follow "Packages" 674ms

Then I should see a "Fake-RPM-SUSE-Channel" link 9ms

And I should see a "sha512:19940cc4a9f0d38a038a4455b0f1cf1290c4a4296b27f5a62f4aae60585ac6e2677e88c3c3127d487116ed8d9b1787379e23aafac46bc14408864926bedee693" text 57ms

And I should see a "andromeda-dummy-2.0-1.1-noarch" link 15ms

Scenario:
Check relevant patches for this client
11s 461ms 8

Given I am on the Systems overview page of this "sle_minion" 942ms

When I follow "Software" in the content area 74ms

And I follow "Patches" in the content area 67ms

Then I should see a "Relevant Patches" text 82ms

When I enter "dummy" as the filtered synopsis 37ms

And I click on the filter button 10s 105ms

Then I should see a "Test update for andromeda-dummy" text 73ms

And I should see a "Test update for virgo-dummy" text 78ms

Scenario:
Cleanup: regenerate search index for later tests
10s 524ms 1

Search by hostname: uyuni-master-suse-minion
[{"last_boot"=>"2026-04-20T18:02:00Z", "name"=>"uyuni-master-suse-minion.sumaci.aws", "id"=>1000010023, "last_checkin"=>"2026-04-20T21:48:47Z"}]

When I clean the search index on the server 10s 524ms

Scenario:
Cleanup: remove old packages
4s 598ms 4

When I disable repository "test_repo_rpm_pool" on this "sle_minion" without error control 728ms

And I refresh the metadata for "sle_minion" 784ms

And I remove package "andromeda-dummy" from this "sle_minion" without error control 1s 556ms

And I remove package "virgo-dummy" from this "sle_minion" without error control 1s 529ms

@sle_minion @susemanager @scope_project_lotus @test_issue
Feature:Project Lotus < 1ms 12

* Related GitHub Card: https://github.com/SUSE/spacewalk/issues/23448
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 59s 437ms 4 1

* Related GitHub Card: https://github.com/SUSE/spacewalk/issues/25872

Scenario:
Call spacewalk-debug on server
40s 180ms 1

When I execute spacewalk-debug on the server 40s 180ms

Scenario:
Check the tomcat logs on server
2s 979ms 1

Then the tomcat logs should not contain errors 2s 979ms

Scenario:
Check salt event log for failures on server
8s 862ms 1

Then the salt event log on server should contain no failures 8s 862ms Show Error + 
                                            
 
Found 21 failures in salt event log:

# Failure 2 , _stamp: 2026-04-20T20:16:51.040184 {
    "__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": 13300.667,
    "name": "docker.build",
    "result": false,
    "start_time": "22:16:37.712188"
}

# Failure 3 , _stamp: 2026-04-20T20:16:51.040184 {
    "__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": "22:16:51.013384"
}

# Failure 4 , _stamp: 2026-04-20T20:16:51.040184 {
    "__id__": "mgr_registries_logout",
    "__run_num__": 3,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "One or more requisite failed: images.docker.mgr_pushimage",
    "duration": 0.003,
    "name": "docker.logout",
    "result": false,
    "start_time": "22:16:51.013656"
}

# Failure 5 , _stamp: 2026-04-20T20:18:16.079415 {
    "__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": 13669.218,
    "name": "docker.build",
    "result": false,
    "start_time": "22:18:02.379617"
}

# Failure 6 , _stamp: 2026-04-20T20:18:16.079415 {
    "__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": "22:18:16.049415"
}

# Failure 7 , _stamp: 2026-04-20T20:18:16.079415 {
    "__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": "22:18:16.049699"
}

# Failure 8 , _stamp: 2026-04-20T20:24:05.719276 {
    "__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": 13275.324,
    "name": "docker.build",
    "result": false,
    "start_time": "22:23:52.413405"
}

# Failure 9 , _stamp: 2026-04-20T20:24:05.719276 {
    "__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": "22:24:05.689169"
}

# Failure 10 , _stamp: 2026-04-20T20:24:05.719276 {
    "__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": "22:24:05.689496"
}

# Failure 11 , _stamp: 2026-04-20T20:25:10.068085 {
    "__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": 13103.559,
    "name": "docker.build",
    "result": false,
    "start_time": "22:24:56.936833"
}

# Failure 12 , _stamp: 2026-04-20T20:25:10.068085 {
    "__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": "22:25:10.040836"
}

# Failure 13 , _stamp: 2026-04-20T20:25:10.068085 {
    "__id__": "mgr_registries_logout",
    "__run_num__": 3,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "One or more requisite failed: images.docker.mgr_pushimage",
    "duration": 0.003,
    "name": "docker.logout",
    "result": false,
    "start_time": "22:25:10.041106"
}

# Failure 14 , _stamp: 2026-04-20T20:26:20.080789 {
    "__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": 13729.287,
    "name": "docker.build",
    "result": false,
    "start_time": "22:26:06.322212"
}

# Failure 15 , _stamp: 2026-04-20T20:26:20.080789 {
    "__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": "22:26:20.051973"
}

# Failure 16 , _stamp: 2026-04-20T20:26:20.080789 {
    "__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": "22:26:20.052252"
}

# Failure 17 , _stamp: 2026-04-20T20:27:24.086962 {
    "__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": 13542.346,
    "name": "docker.build",
    "result": false,
    "start_time": "22:27:10.516830"
}

# Failure 18 , _stamp: 2026-04-20T20:27:24.086962 {
    "__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": "22:27:24.059642"
}

# Failure 19 , _stamp: 2026-04-20T20:27:24.086962 {
    "__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": "22:27:24.059915"
}

# Failure 20 , _stamp: 2026-04-20T20:36:23.674723 {
    "__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": 13391.104,
    "name": "docker.build",
    "result": false,
    "start_time": "22:36:10.255439"
}

# Failure 21 , _stamp: 2026-04-20T20:36:23.674723 {
    "__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": "22:36:23.647009"
}

# Failure 22 , _stamp: 2026-04-20T20:36:23.674723 {
    "__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": "22:36:23.647279"
}

 (ScriptError)
./features/step_definitions/salt_steps.rb:526:in `/^the salt event log on server should contain no failures$/'
features/finishing/srv_debug.feature:16:in `the salt event log on server should contain no failures'

Scenario:
Check the taskomatic logs on server
4s 626ms 1

Then the taskomatic logs should not contain errors 4s 626ms

Scenario:
Check for out of memory errors
2s 789ms 1

Then the log messages should not contain out of memory errors 2s 789ms

Feature:Debug the clients after the testsuite has run 2m 45s 270ms 1

Scenario:
Extract the logs from all our clients
2m 45s 270ms 1

When I extract the log files from all our active nodes 2m 45s 270ms

@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