All Scenarios

1527

Passed Scenarios

1251

Failed Scenarios

49

Skipped Scenarios

227

Execution Time: 458m 3s 866ms

Expand All | Collapse All

Metadata

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

Feature:Sanity checks 1m 21s 970ms 10 2

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

Scenario:
The server is healthy
27s 397ms 11

Then "server" should have a FQDN 794ms

And reverse resolution should work for "server" 2s 443ms

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

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

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

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

And service "salt-api" is active on "server" 4s 108ms

And service "salt-master" is active on "server" 2s 471ms

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

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

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

@proxy
Scenario:
The proxy is healthy
6s 567ms 4

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

And reverse resolution should work for "proxy" 295ms

And "proxy" should communicate with the server using public interface 2s 832ms

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

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

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

And reverse resolution should work for "sle_minion" 416ms

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

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

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

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

And reverse resolution should work for "build_host" 219ms

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

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

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

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

And reverse resolution should work for "ssh_minion" 426ms

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

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

@rhlike_minion
Scenario:
The Red Hat-like minion is healthy
6s 826ms 4

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

And reverse resolution should work for "rhlike_minion" 190ms

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

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

@deblike_minion
Scenario:
The Debian-like minion is healthy
8s 719ms 4

Then "deblike_minion" should have a FQDN 5s 508ms

And reverse resolution should work for "deblike_minion" 218ms

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

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

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

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

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

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

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

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

Feature:Very first settings 58s 750ms 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 533ms 1

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

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

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

Scenario:
Wait for refresh of list of products to finish
8s 88ms 1

When I wait until mgr-sync refresh is finished 8s 88ms

Scenario:
Create testing username
3s 652ms 12

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

And I follow "Create User" 667ms

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

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

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

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

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

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

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

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

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

And I should see a "testing" link 17ms

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

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

And I follow "testing" 465ms

And I check "role_org_admin" 84ms

And I check "role_system_group_admin" 77ms

And I check "role_channel_admin" 79ms

And I check "role_activation_key_admin" 77ms

And I check "role_config_admin" 76ms

And I click on "Update" 1s 122ms

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

And I should see a "testing" text 79ms

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

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

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

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 551ms 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 406ms 5

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

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

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

And I click on "Save Preferences" 602ms

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

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

Given I am authorized as "testing" with password "testing" 3s 424ms

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

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

And I click on "Save Preferences" 497ms

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

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

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

New user kiwikiwi created with roles: image_admin

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

When I create a user with name "kiwikiwi" and password "kiwikiwi" with roles "image_admin" 4s 84ms

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

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

New user docker created with roles: image_admin

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

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

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

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

And I follow "Create" 726ms

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

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

And I click on "create-btn" 83ms

Then I wait until table row contains a "galaxy-registry" text 2s 9ms

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

Feature:Do not let Taskomatic tasks interfere with our CI tests 27s 852ms 3

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

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

Scenario:
Disable scheduled reposyncs
4s 903ms 5

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

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

And I choose "disabled" 55ms

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

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

Scenario:
Disable scheduled Cobbler syncs
3s 45ms 5

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

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

And I choose "disabled" 46ms

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

And I click on "Disable Schedule" 51ms

@scc_credentials
Feature:List available channels and enable them 2m 2s 836ms 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 848ms 5

When I refresh SCC 37s 430ms

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

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

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

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

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

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

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

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

When I remove the mgr-sync cache file 3s 83ms

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

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 37s 879ms 9 9

@scc_credentials
Scenario:
Refresh SCC
33s 874ms 1

When I refresh SCC 33s 874ms

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

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

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

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

Then I should see a "Arch" text 130ms

And I should see a "Channels" text 121ms

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

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

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

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

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

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

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

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

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

@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 28s 916ms 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: Found 'Sync of channel completed.' for opensuse_tumbleweed-uyuni-client-x86_64 at line 21.
SUCCESS: opensuse_tumbleweed-uyuni-client-x86_64 is fully synchronized.
DEBUG: Channel 'opensuse_tumbleweed-uyuni-client-devel-x86_64' not found in reposync.log
DEBUG: Channel 'opensuse_tumbleweed-uyuni-client-devel-x86_64' not found in reposync.log
DEBUG: Found channel 'opensuse_tumbleweed-uyuni-client-devel-x86_64' at line 25. Checking for completion...
DEBUG: Sync for opensuse_tumbleweed-uyuni-client-devel-x86_64 still in progress (no completion message found).
DEBUG: Found channel 'opensuse_tumbleweed-uyuni-client-devel-x86_64' at line 25. Checking for completion...
DEBUG: 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 762ms

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

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

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

When I wait until all synchronized channels for "tumbleweed" have finished 52s 78ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Then the SLE15 SP7 product should be added 5s 926ms

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

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

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

@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
5m 2s 940ms 2

SUCCESS: Channel opensuse_tumbleweed-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel opensuse_tumbleweed-x86_64 synchronization took 108 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 13 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 22 seconds.
SUCCESS: Channel opensuse_tumbleweed-x86_64 initialized. No '.new' files and repo size > 0.
INFO: Channel opensuse_tumbleweed-x86_64 synchronization took 108 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 22 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 11 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 6 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 346 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 1038 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 46 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 50 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 52 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 127 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 317 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 71 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 732 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 175 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 35 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 29 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 57 seconds.

When I wait until all synchronized channels have solved their dependencies 5m 2s 940ms

Then all channels have been synced without errors < 1ms

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

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

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

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

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

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

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

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

@scc_credentials @skip_if_github_validation
Scenario:
Report the synchronization duration for SLES 15 SP7
< 1ms 1

When I report the synchronization duration for "sles15-sp7" < 1ms

Feature:Create fake channels 25s 563ms 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
475ms 1

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

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

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

And I follow "Create Channel" 421ms

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

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

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

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

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

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

And I click on "Create Channel" 724ms

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

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

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

And I follow "Create Channel" 313ms

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

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

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

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

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

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

And I click on "Create Channel" 590ms

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

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

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

And I follow "Create Channel" 316ms

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

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

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

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

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

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

And I click on "Create Channel" 597ms

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

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

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

And I follow "Create Channel" 273ms

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

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

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

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

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

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

And I click on "Create Channel" 571ms

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

Scenario:
Add a fake child channel into the fake base channel i586
2s 320ms 10

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

And I follow "Create Channel" 592ms

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

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

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

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

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

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

And I click on "Create Channel" 53ms

Then I should see a "Channel Fake-Child-Channel-i586 created." text 1s 178ms

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

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

And I follow "Create Channel" 330ms

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

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

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

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

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

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

And I click on "Create Channel" 538ms

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

Scenario:
Add a child channel into the test base channel x86_64
988ms 10

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

And I follow "Create Channel" 337ms

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

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

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

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

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

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

And I click on "Create Channel" 55ms

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

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

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

And I follow "Create Channel" 363ms

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

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

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

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

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

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

And I uncheck "gpg_check" 10s 79ms

And I click on "Create Channel" 573ms

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

@rhlike_minion
Scenario:
Add a RedHat-like base channel
988ms 10

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

And I follow "Create Channel" 364ms

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

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

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

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

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

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

And I click on "Create Channel" 57ms

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

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

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

And I follow "Create Channel" 361ms

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

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

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

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

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

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

And I click on "Create Channel" 523ms

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

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

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

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

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

And I follow "Create Repository" 342ms

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

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

And I click on "Create Repository" 436ms

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

And I should see "metadataSigned" as checked 19ms

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

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

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

And I uncheck "metadataSigned" 10s 80ms

And I click on "Update Repository" 442ms

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

And I should see "metadataSigned" as unchecked 15ms

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

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

And I follow "Create Repository" 218ms

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

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

And I click on "Create Repository" 53ms

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

And I should see "metadataSigned" as checked 17ms

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

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

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

And I uncheck "metadataSigned" 10s 53ms

And I click on "Update Repository" 424ms

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

And I should see "metadataSigned" as unchecked 15ms

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

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

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

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

And I click on "Update Channel" 62ms

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

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

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

And I click on "Save Repositories" 602ms

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

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

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

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

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

And I click on "Update Channel" 572ms

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

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

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

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

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

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

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

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

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

And I click on "Update Channel" 612ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

And I follow "Create Repository" 395ms

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

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

And I uncheck "metadataSigned" 10s 65ms

And I click on "Create Repository" 425ms

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

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

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

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

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

And I click on "Update Channel" 528ms

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

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

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

And I click on "Save Repositories" 591ms

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

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

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

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

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

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

And I click on "Save Repositories" 664ms

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

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

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

And I follow "Create Repository" 311ms

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

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

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

And I click on "Create Repository" 55ms

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

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

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

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

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

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

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

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

@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 48ms 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
435ms 1

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

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

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

And I follow "Create Channel" 283ms

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

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

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

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

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

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

And I click on "Create Channel" 639ms

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

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

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

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

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

And I follow "Create Channel" 456ms

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

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

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

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

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

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

And I click on "Create Channel" 59ms

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

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

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

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

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

And I follow "Create Channel" 275ms

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

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

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

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

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

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

And I click on "Create Channel" 545ms

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

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

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

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

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

And I follow "Create Channel" 407ms

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

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

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

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

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

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

And I click on "Create Channel" 599ms

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

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

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

Feature:Synchronize fake channels 2m 18s 174ms 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
6s 513ms 2

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

And I enable source package syncing 5s 731ms

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

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

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

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

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

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

And I follow "Sync" 351ms

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

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

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

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

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

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

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

@skip_if_github_validation
Scenario:
Synchronize Fake-Child-Channel-i586 channel
16s 766ms 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 451ms

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

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

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

And I follow "Sync" 334ms

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

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

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

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

Scenario:
Synchronize Test-Child-Channel-x86_64 channel
16s 374ms 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 443ms

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

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

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

And I follow "Sync" 876ms

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

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

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

@sle_minion
Scenario:
Synchronize Fake-Child-Channel-SUSE-like channel
16s 497ms 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 493ms

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

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

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

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

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

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

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

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

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

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

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

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

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

And I follow "Sync" 362ms

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

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

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

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

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

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

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

And I follow "Sync" 424ms

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

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

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

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

@rhlike_minion
Scenario:
Synchronize Fake-Base-Channel-AppStream channel
17s 369ms 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 432ms

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

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

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

And I follow "Sync" 333ms

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

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

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

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

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

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

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

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

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

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 1s 902ms

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

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

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

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

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

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

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

Scenario:
Cleanup disable source package syncing
4s 841ms 1

Then I disable source package syncing 4s 841ms

@skip_if_github_validation
Feature:Synchronize development channels 1m 29s 761ms 4

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

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

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

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

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

And I follow "Sync" 345ms

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

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 136ms 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 443ms

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

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

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

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

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

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

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

@rhlike_minion
Scenario:
Synchronize Devel-RH-like-Channel channel
40s 864ms 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 552ms

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

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

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

And I follow "Sync" 337ms

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

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

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

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

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

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

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

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

And I follow "Sync" 346ms

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

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

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

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

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

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

@sle_minion
Scenario:
Create an activation key with a channel
2s 143ms 2

When I create an activation key with id "SUSE-KEY-x86_64", description "SUSE Test Key x86_64", limit of 20 and contact method "default" 1s 772ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 485ms

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 538ms

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

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

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

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

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

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

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

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

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

And I click on "Update Activation Key" 0s

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 518ms

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

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

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

And I wait until "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
3s 199ms 20

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

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

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

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

And I wait for child channels to appear 534ms

And I include the recommended child channels 181ms

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

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

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

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

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

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

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

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

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

And I wait until "SLE-Module-Systems-Management-15-SP7-Updates for x86_64" has been checked 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" 671ms

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

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

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

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

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

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

And I wait for child channels to appear 316ms

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

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

And I click on "Update Activation Key" 616ms

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

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

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

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

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

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

And I wait for child channels to appear 315ms

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

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

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

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

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

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

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

And I wait for child channels to appear 518ms

And I include the recommended child channels 164ms

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

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

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

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

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

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

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

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

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

And I wait for child channels to appear 760ms

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

And I click on "Update Activation Key" 448ms

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

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

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

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

And I wait for child channels to appear 761ms

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

And I click on "Update Activation Key" 434ms

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

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

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

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

And I wait for child channels to appear 753ms

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

And I click on "Update Activation Key" 485ms

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

Feature:Create bootstrap repositories 26s 263ms 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
6s 328ms 1

When I create the bootstrap repositories including custom channels 6s 328ms

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

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

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

@containerized_server @scope_containerized_proxy @proxy
Feature:Setup containerized proxy 3m 42s 145ms 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 963ms 1

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

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

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

Scenario:
Bootstrap the proxy host as a salt minion
37s 508ms 9

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 61ms

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

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

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

Scenario:
Wait until the proxy host appears
1m 22s 829ms 1

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

Scenario:
Generate containerized proxy configuration
12s 989ms 2

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

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

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
18s 711ms 1

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

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

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

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

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

And I wait until "uyuni-proxy-squid" service is active on "proxy" 5s 166ms

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

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

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

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

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

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

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

When I follow the left menu "Systems" 59ms

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

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

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

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

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

@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 39s 414ms 7

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

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

Scenario:
Bootstrap a Debian-like minion
2m 34s 686ms 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" 152ms

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

When I enter the hostname of "deblike_minion" as "hostname" 6s 112ms

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

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

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

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

And I select the hostname of "proxy" from "proxies" if present 2s 789ms

And I click on "Bootstrap" 108ms

And I wait until I see "Bootstrap process initiated." text 48s 449ms

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

And I wait until I see the name of "deblike_minion", refreshing the page 1m 13s 572ms

And I wait until onboarding is completed for "deblike_minion" 21s 103ms

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

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

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

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

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

Then I should see "proxy" short hostname 112ms

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

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

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

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

Then I should see "deblike_minion" hostname 193ms

Scenario:
Subscribe the Debian-like minion to a base channel
27s 444ms 11

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

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

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

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

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

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

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

And I click on "Next" 91ms

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

When I click on "Confirm" 105ms

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

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

Scenario:
Detect latest Salt changes on the Debian-like minion
726ms 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" 726ms

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

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

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

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

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

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

Scenario:
Bootstrap a Red Hat-like minion
2m 18s 415ms 13

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

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

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

When I enter the hostname of "rhlike_minion" as "hostname" 2s 217ms

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

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

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

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

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

And I click on "Bootstrap" 87ms

And I wait until I see "Bootstrap process initiated." text 38s 113ms

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

And I wait until I see the name of "rhlike_minion", refreshing the page 31s 887ms

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

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

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

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

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

Then I should see "proxy" short hostname 166ms

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

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

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

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

Then I should see "rhlike_minion" hostname 212ms

Scenario:
Subscribe the Red Hat-like minion to a base channel
30s 951ms 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 791ms

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

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

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

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

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

And I click on "Next" 97ms

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

When I click on "Confirm" 142ms

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

And I wait until event "Subscribe channels scheduled by admin" is completed 26s 469ms

Scenario:
Detect latest Salt changes on the Red Hat-like minion
415ms 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" 415ms

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

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

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

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

Scenario:
Clean up sumaform leftovers on build host
9s 525ms 1

When I perform a full salt minion cleanup on "build_host" 9s 525ms

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

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

Scenario:
Bootstrap a build host
55s 381ms 10

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

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

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

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

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

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

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

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

And I select the hostname of "proxy" from "proxies" if present 4s 173ms

And I click on "Bootstrap" 121ms

And I wait until I see "Bootstrap process initiated." text 49s 816ms

Scenario:
Check the new bootstrapped build host in System Overview page
2m 1s 754ms 6

It took 4 seconds to contact the minion

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

Then I should see a "accepted" text 948ms

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

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

And I wait at most 500 seconds until onboarding is completed for "build_host" 57s 757ms

Then the Salt master can reach "build_host" 4s 447ms

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

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

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

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

Then I should see "proxy" short hostname 95ms

@proxy
Scenario:
Check registration on build host of minion
1s 290ms 4

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

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

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

Then I should see "build_host" hostname 136ms

Scenario:
Detect latest Salt changes on the SLES build host
649ms 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" 649ms

Scenario:
Check that the build host is a build host
1s 556ms 3

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

Then I should see a "[Container Build Host]" text 128ms

Then I should see a "[OS Image Build Host]" text 131ms

Scenario:
Check events history for failures on SLES build host
1m 12s 176ms 2

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

Then I check for failed events on history event page 1m 10s 983ms

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

Scenario:
Clean up sumaform leftovers on SLES minion
10s 227ms 1

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

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

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

Scenario:
Bootstrap a SLES minion
53s 205ms 11

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

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

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

When I enter the hostname of "sle_minion" as "hostname" 224ms

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

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

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

And I select "1-SUSE-KEY-x86_64" from "activationKeys" 257ms

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

And I click on "Bootstrap" 100ms

And I wait until I see "Bootstrap process initiated." text 48s 159ms

And I report the bootstrap duration for "sle_minion" < 1ms

Scenario:
Check the new bootstrapped minion in System List page
1m 43s 672ms 8

It took 6 seconds to contact the minion

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

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

Then I should see a "accepted" text 100ms

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

And I wait until I see the name of "sle_minion", refreshing the page 59s 196ms

And I wait until onboarding is completed for "sle_minion" 37s 638ms

Then the Salt master can reach "sle_minion" 5s 691ms

And I report the onboarding duration for "sle_minion" < 1ms

@susemanager
Scenario:
Use correct kernel image on the SLES minion
< 1ms 2

When I remove package "kernel-default-base" from this "sle_minion" 0s

And I install package "kernel-default" on this "sle_minion" 0s

@susemanager
Scenario:
Reboot the SLES minion to use the new kernel
< 1ms 1

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

@proxy
Scenario:
Check connection from minion to proxy
2s 812ms 4

Given I am on the Systems overview page of this "sle_minion" 2s 456ms

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

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

Then I should see "proxy" short hostname 121ms

@proxy
Scenario:
Check registration on proxy of minion
1s 545ms 4

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

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

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

Then I should see "sle_minion" hostname 130ms

@ssh_minion
Feature:Bootstrap a Salt host managed via salt-ssh 3m 41s 733ms 5 2

Scenario:
Clean up sumaform leftovers on SLES SSH minion
10s 410ms 1

When I perform a full salt minion cleanup on "ssh_minion" 10s 410ms

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

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

Scenario:
Bootstrap a SLES SSH minion
2m 48s 497ms 11

The hostname of ssh_minion is uyuni-master-suse-sshminion.sumaci.aws

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

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

When I check "manageWithSSH" 180ms

And I enter the hostname of "ssh_minion" as "hostname" 269ms

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

And I select the hostname of "proxy" from "proxies" if present 4s 140ms

And I click on "Bootstrap" 200ms

And I wait until I see "Bootstrap process initiated." text 1m 1s 275ms

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

And I wait until I see the name of "ssh_minion", refreshing the page 46s 345ms

And I wait until onboarding is completed for "ssh_minion" 55s 269ms

@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 418ms 4

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

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

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

Then I should see "proxy" short hostname 94ms

@proxy
Scenario:
Check registration on proxy of SSH minion
1s 582ms 4

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

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

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

Then I should see "ssh_minion" hostname 120ms

@scope_visualization
Feature:Secure connection 230ms 4

Scenario:
Connecting to the server insecurely
1ms 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 91ms

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

When I connect to the server securely while using incorrect certificate as a CA certificate file 54ms

Then the secure connection should fail due to unverified certificate signature < 1ms

Feature:List available products 7s 516ms 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
7s 516ms 1 1

When I execute mgr-sync "list products" with user "admin" and password "admin" 7s 515ms

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:206: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 31s 245ms 12

Scenario:
Fake an IPMI host
14s 236ms 1

When the server starts mocking an IPMI host 14s 236ms

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

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

Scenario:
Start Cobbler monitoring
13s 594ms 1

When I start local monitoring of Cobbler 13s 594ms

Scenario:
Check the power management page
5s 786ms 6

Given I am on the Systems overview page of this "sle_minion" 5s 462ms

When I follow "Provisioning" in the content area 87ms

And I follow "Power Management" in the content area 68ms

Then I should see a "Power Management Settings" text 74ms

And I should see a "IPMI" text 68ms

And I should see a "Save" button 25ms

Scenario:
Save power management values
14s 814ms 9

When I enter "fakeipmi" as "powerAddress" 55ms

And I enter "ipmiusr" as "powerUsername" 56ms

And I enter "test" as "powerPassword" 52ms

And I click on "Save" 58ms

Then I should see a "Power settings saved" text 75ms

And the cobbler report should contain "Power Management Address : fakeipmi" for "sle_minion" 4s 837ms

And the cobbler report should contain "Power Management Username : ipmiusr" for "sle_minion" 3s 217ms

And the cobbler report should contain "Power Management Password : test" for "sle_minion" 3s 262ms

And the cobbler report should contain "Power Management Type : ipmilan" for "sle_minion" 3s 197ms

Scenario:
Test IPMI functions
20s 274ms 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" 2s 801ms

And I click on "Get status" 1s 4ms

Then I should see the power is "On" 24ms

When I click on "Power Off" 3s 20ms

Then I should see a "system has been powered off" text 69ms

And I should see the power is "Unknown" 20ms

When I click on "Get status" 1s 55ms

Then I should see the power is "Off" 20ms

When I click on "Power On" 51ms

Then I should see a "system has been powered on" text 79ms

When I click on "Get status" 734ms

Then I should see the power is "On" 21ms

When I click on "Reboot" 10s 502ms

Then I should see a "system has been rebooted" text 70ms

When I click on "Get status" 653ms

Then I should see the power is "On" 21ms

Scenario:
Check power management SSM configuration
17s 326ms 21

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

And I click on the clear SSM button 120ms

And I check the "sle_minion" client 442ms

And I follow the left menu "Systems > System Set Manager > Overview" 485ms

And I follow "Configure power management" in the content area 69ms

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

And I should see a "Network address" text 74ms

And I should see a "Username" text 73ms

And I should see a "Password" text 71ms

And I should see a "System identifier" text 77ms

And I should see a "Update" button 17ms

When I enter "testing" as "powerUsername" 49ms

And I enter "qwertz" as "powerPassword" 49ms

And I click on "Update" 58ms

Then I should see a "Configuration successfully saved for 1 system(s)" text 447ms

And the cobbler report should contain "Power Management Username : testing" for "sle_minion" 3s 558ms

And the cobbler report should contain "Power Management Password : qwertz" for "sle_minion" 4s 972ms

And the cobbler report should contain "Power Management Address : fakeipmi" for "sle_minion" 3s 220ms

And the cobbler report should contain "Power Management Type : ipmilan" for "sle_minion" 3s 221ms

Scenario:
Check power management SSM operation
209ms 6

And I follow the left menu "Systems > System Set Manager > Overview" 76ms

When I follow "power management operations" in the content area 71ms

Then I should see "sle_minion" as link 12ms

And I should see a "Power On" button 16ms

And I should see a "Power Off" button 16ms

And I should see a "Reboot" button 16ms

Scenario:
Cleanup: reset IPMI values
15s 684ms 8

Given I want to operate on this "sle_minion" 359ms

When I set power management value "" for "powerAddress" 363ms

And I set power management value "" for "powerUsername" 379ms

And I set power management value "" for "powerPassword" 377ms

Then the cobbler report should contain "Power Management Address :" for "sle_minion" 3s 273ms

And the cobbler report should contain "Power Management Username :" for "sle_minion" 4s 447ms

And the cobbler report should contain "Power Management Password :" for "sle_minion" 3s 241ms

And the cobbler report should contain "Power Management Type : ipmilan" for "sle_minion" 3s 241ms

Scenario:
Cleanup: tear down the IPMI host
513ms 1

When the server stops mocking an IPMI host 513ms

Scenario:
Cleanup: remove remaining systems from SSM after power management tests
52ms 1

When I click on the clear SSM button 52ms

Scenario:
Check for errors in Cobbler monitoring
10s 974ms 1

Then the local logs for Cobbler should not contain errors 10s 974ms

@skip_if_github_validation @scope_api @sle_minion
Feature:IPMI Power management API 50s 640ms 6

Scenario:
Setup an IPMI host for API test
2s 794ms 2

When the server starts mocking an IPMI host 2s 434ms

And I want to operate on this "sle_minion" 359ms

Scenario:
Check the power management settings for API test
383ms 2

When I fetch power management values 383ms

Then power management results should have "ipmilan" for "powerType" < 1ms

Scenario:
Save power management values for API test
16s 28ms 8

When I set power management value "fakeipmi" for "powerAddress" 383ms

And I set power management value "ipmiusr" for "powerUsername" 372ms

And I set power management value "test" for "powerPassword" 378ms

And I set power management value "ipmilan" for "powerType" 373ms

Then the cobbler report should contain "Power Management Address : fakeipmi" for "sle_minion" 4s 875ms

And the cobbler report should contain "Power Management Username : ipmiusr" for "sle_minion" 3s 220ms

And the cobbler report should contain "Power Management Password : test" for "sle_minion" 3s 203ms

And the cobbler report should contain "Power Management Type : ipmilan" for "sle_minion" 3s 219ms

Scenario:
Test IPMI functions for API test
15s 162ms 6

When I turn power on 2s 686ms

Then the power status is "on" 615ms

When I turn power off 2s 755ms

Then the power status is "off" 542ms

When I do power management reboot 7s 914ms

Then the power status is "on" 647ms

Scenario:
Cleanup: reset IPMI values for API test
15s 802ms 7

When I set power management value "" for "powerAddress" 473ms

And I set power management value "" for "powerUsername" 403ms

And I set power management value "" for "powerPassword" 392ms

Then the cobbler report should contain "Power Management Address :" for "sle_minion" 4s 828ms

And the cobbler report should contain "Power Management Username :" for "sle_minion" 3s 230ms

And the cobbler report should contain "Power Management Password :" for "sle_minion" 3s 201ms

And the cobbler report should contain "Power Management Type : ipmilan" for "sle_minion" 3s 273ms

Scenario:
Cleanup: tear down the IPMI host for API test
470ms 1

When the server stops mocking an IPMI host 470ms

@skip_if_github_validation @scope_power_management @scope_cobbler @sle_minion
Feature:Redfish Power management 1m 38s 781ms 11

Scenario:
Setup a Redfish host
12s 225ms 1

When the controller starts mocking a Redfish host 12s 225ms

Scenario:
Log in as admin user
442ms 1

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

Scenario:
Start Cobbler monitoring
14s 287ms 1

When I start local monitoring of Cobbler 14s 287ms

Scenario:
Save power management values for Redfish
16s 969ms 13

Given I am on the Systems overview page of this "sle_minion" 964ms

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

And I follow "Power Management" in the content area 67ms

And I enter the controller hostname as the redfish server address 99ms

And I enter "ipmiusr" as "powerUsername" 50ms

And I enter "test" as "powerPassword" 47ms

And I select "Redfish" from "powerType" 70ms

And I click on "Save" 555ms

Then I should see a "Power settings saved" text 68ms

And the cobbler report should contain ":8443" for "sle_minion" 3s 324ms

And the cobbler report should contain "Power Management Username : ipmiusr" for "sle_minion" 3s 199ms

And the cobbler report should contain "Power Management Password : test" for "sle_minion" 3s 241ms

And the cobbler report should contain "Power Management Type : redfish" for "sle_minion" 5s 213ms

Scenario:
Test Redfish functions
12s 847ms 18

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

And I follow "Power Management" in the content area 71ms

And I click on "Power On" 872ms

And I click on "Get status" 906ms

Then I should see the power is "On" 23ms

When I click on "Power Off" 911ms

Then I should see a "system has been powered off" text 72ms

And I should see the power is "Unknown" 21ms

When I click on "Get status" 789ms

Then I should see the power is "Off" 21ms

When I click on "Power On" 868ms

Then I should see a "system has been powered on" text 72ms

When I click on "Get status" 867ms

Then I should see the power is "On" 20ms

When I click on "Reboot" 6s 292ms

Then I should see a "system has been rebooted" text 75ms

When I click on "Get status" 876ms

Then I should see the power is "On" 20ms

Scenario:
Check power management SSM configuration for Redfish
17s 548ms 21

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

And I click on the clear SSM button 48ms

And I check the "sle_minion" client 469ms

And I follow the left menu "Systems > System Set Manager > Overview" 541ms

And I follow "Configure power management" in the content area 66ms

Then I should see "sle_minion" as link 17ms

And I should see a "Change Power Management Configuration" text 76ms

And I should see a "Type" text 72ms

And I should see a "Network address" text 72ms

And I should see a "Username" text 75ms

And I should see a "Password" text 73ms

And I should see a "System identifier" text 73ms

And I should see a "Update" button 17ms

When I enter "testing" as "powerUsername" 51ms

And I enter "qwertz" as "powerPassword" 49ms

And I click on "Update" 436ms

Then I should see a "Configuration successfully saved for 1 system(s)" text 81ms

And the cobbler report should contain "Power Management Username : testing" for "sle_minion" 3s 700ms

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

And the cobbler report should contain "Power Management Type : redfish" for "sle_minion" 5s 30ms

Scenario:
Check power management SSM operation for Redfish
205ms 6

And I follow the left menu "Systems > System Set Manager > Overview" 76ms

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

And I should see a "Reboot" button 16ms

Scenario:
Cleanup: reset Redfish values
16s 871ms 9

Given I want to operate on this "sle_minion" 456ms

When I set power management value "" for "powerAddress" 458ms

And I set power management value "" for "powerUsername" 409ms

And I set power management value "" for "powerPassword" 423ms

And I set power management value "ipmilan" for "powerType" 377ms

Then the cobbler report should contain "Power Management Address :" for "sle_minion" 3s 169ms

And the cobbler report should contain "Power Management Username :" for "sle_minion" 3s 169ms

And the cobbler report should contain "Power Management Password :" for "sle_minion" 5s 150ms

And the cobbler report should contain "Power Management Type : ipmilan" for "sle_minion" 3s 255ms

Scenario:
Cleanup: tear down the Redfish host
47ms 1

When the controller stops mocking a Redfish host 47ms

Scenario:
Cleanup: remove remaining systems from SSM after Redfish power management tests
61ms 1

When I click on the clear SSM button 61ms

Scenario:
Check for errors in Cobbler monitoring
7s 275ms 1

Then the local logs for Cobbler should not contain errors 7s 275ms

@scope_configuration_channels
Feature:Delete channels with child or clone is not allowed 17s 613ms 9

Using the UI, we cannot delete a channel if it has a child
or a clone created from it

Scenario:
Log in as org admin user
1s 804ms 1

Given I am authorized 1s 804ms

Scenario:
Clone the first channel before deletion from UI test
1s 906ms 8

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

And I follow "Clone Channel" 368ms

And I select "Fake-Base-Channel-SUSE-like" as the origin channel 66ms

And I click on "Clone Channel" 379ms

Then I should see a "Create Software Channel" text 86ms

And I should see a "Current state of the channel" text 75ms

When I click on "Clone Channel" 667ms

Then I should see a "Clone of Fake-Base-Channel-SUSE-like" text 75ms

Scenario:
Clone the second channel using first channel as base
1s 868ms 8

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

And I follow "Clone Channel" 470ms

And I select "Clone of Fake-Base-Channel-SUSE-like" as the origin channel 42ms

And I click on "Clone Channel" 376ms

Then I should see a "Create Software Channel" text 80ms

And I should see a "Current state of the channel" text 74ms

When I click on "Clone Channel" 674ms

Then I should see a "Clone of Clone of Fake-Base-Channel-SUSE-like" text 76ms

Scenario:
Try to delete channel with clone
1s 603ms 7

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

And I follow "Clone of Fake-Base-Channel-SUSE-like" 492ms

And I follow "Delete Channel" 393ms

And I check "unsubscribeSystems" 79ms

And I click on "Delete Channel" 437ms

Then I should see a "Clone of Fake-Base-Channel-SUSE-like" text 66ms

And I should see a "Unable to delete channel" text 61ms

Scenario:
Delete channel without clones neither children
1s 797ms 7

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

And I follow "Clone of Clone of Fake-Base-Channel-SUSE-like" 479ms

And I follow "Delete Channel" 380ms

And I check "unsubscribeSystems" 67ms

And I click on "Delete Channel" 614ms

Then I should see a "Clone of Clone of Fake-Base-Channel-SUSE-like" text 92ms

And I should see a "has been deleted" text 92ms

Scenario:
Clone a child channel to the clone of x86_64 test channel
2s 512ms 9

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

And I follow "Clone Channel" 377ms

And I select "Fake-RPM-SUSE-Channel" as the origin channel 61ms

And I click on "Clone Channel" 403ms

Then I should see a "Create Software Channel" text 77ms

And I should see a "Current state of the channel" text 80ms

When I select "Clone of Fake-Base-Channel-SUSE-like" from "Parent Channel" 63ms

And I click on "Clone Channel" 1s 292ms

Then I should see a "Clone of Fake-RPM-SUSE-Channel" text 77ms

Scenario:
Try delete channel with child
1s 516ms 8

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

And I follow "Clone of Fake-Base-Channel-SUSE-like" 362ms

And I follow "Delete Channel" 406ms

And I check "unsubscribeSystems" 66ms

And I click on "Delete Channel" 52ms

Then I should see a "Clone of Fake-Base-Channel-SUSE-like" text 438ms

And I should see a "channel has child channels associated" text 58ms

And I should see a "must delete those channels first before deleting the parent." text 57ms

Scenario:
Cleanup: remove cloned child channel
1s 780ms 7

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

And I follow "Clone of Fake-RPM-SUSE-Channel" 389ms

And I follow "Delete Channel" 384ms

And I check "unsubscribeSystems" 67ms

And I click on "Delete Channel" 731ms

Then I should see a "Clone of Fake-RPM-SUSE-Channel" text 63ms

And I should see a "has been deleted." text 67ms

Scenario:
Cleanup: remove cloned parent channel
2s 823ms 7

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

And I follow "Clone of Fake-Base-Channel-SUSE-like" 465ms

And I follow "Delete Channel" 389ms

And I check "unsubscribeSystems" 66ms

And I click on "Delete Channel" 1s 650ms

Then I should see a "Clone of Fake-Base-Channel-SUSE-like" text 88ms

And I should see a "has been deleted." text 83ms

@scope_configuration_channels
Feature:Deleting channels with children or clones is not allowed 19s 824ms 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
2s 3ms 1

Given I am authorized 2s 3ms

Scenario:
Clone the first channel before deletion from tool test
2s 263ms 8

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

And I follow "Clone Channel" 480ms

And I select "Fake-RPM-SUSE-Channel" as the origin channel 53ms

And I click on "Clone Channel" 411ms

Then I should see a "Create Software Channel" text 78ms

And I should see a "Current state of the channel" text 74ms

When I click on "Clone Channel" 917ms

Then I should see a "Clone of Fake-RPM-SUSE-Channel" text 73ms

Scenario:
Clone a second channel using first channel as base
1s 855ms 8

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

And I follow "Clone Channel" 449ms

And I select "Clone of Fake-RPM-SUSE-Channel" as the origin channel 64ms

And I click on "Clone Channel" 374ms

Then I should see a "Create Software Channel" text 78ms

And I should see a "Current state of the channel" text 75ms

When I click on "Clone Channel" 661ms

Then I should see a "Clone of Clone of Fake-RPM-SUSE-Channel" text 77ms

Scenario:
Verify if both clone channels exists
3s 182ms 3

When I list channels with spacewalk-remove-channel 3s 182ms

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 748ms 5

When I delete these channels with spacewalk-remove-channel: 2s 747ms
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
7s 770ms 4

When I delete these channels with spacewalk-remove-channel: 4s 627ms
clone-fake-rpm-suse-channel
clone-clone-fake-rpm-suse-channel

And I list channels with spacewalk-remove-channel 3s 143ms

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 7s 948ms 14 1

Scenario:
Log in as org admin user
1s 910ms 1

Given I am authorized 1s 910ms

Scenario:
Create a single calendar
7s 389ms 9

URL: https://uyuni-master-server.sumaci.aws/pub/maintenance-windows-exchange.ics

When I follow the left menu "Schedule > Maintenance Windows > Calendars" 1s 88ms

And I wait for "1" second 1s

Then I should see a "No calendars created" text 56ms

When I click on "Create" in element "maintenance-windows" 76ms

Then I should see a "Calendar Name" text 52ms

When I enter "singlecalendar" as "name" 75ms

And I add "maintenance-windows-exchange.ics" calendar file as url 4s 714ms

And I click on "Create Calendar" 61ms

Then I should see a "Calendar successfully created" text 263ms

Scenario:
Create a multi calendar
5s 441ms 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" 80ms

And I wait for "1" second 1s

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

When I click on "Create" in element "maintenance-windows" 62ms

Then I should see a "Calendar Name" text 53ms

When I enter "multicalendar" as "name" 65ms

And I add "maintenance-windows-multi-exchange-1.ics" calendar file as url 3s 789ms

And I click on "Create Calendar" 66ms

Then I should see a "Calendar successfully created" text 263ms

Scenario:
Create a single schedule
2s 812ms 11

When I follow the left menu "Schedule > Maintenance Windows > Schedules" 79ms

And I wait for "1" second 1s

Then I should see a "No schedules created" text 55ms

When I click on "Create" in element "maintenance-windows" 64ms

Then I should see a "Schedule Name" text 54ms

When I enter "singleschedule" as "name" 73ms

And I choose "SINGLE" 55ms

And I click on "Add Calendar" 76ms

And I select "singlecalendar" from "calendarSelect" 1s 116ms

And I click on "Create Schedule" 61ms

Then I should see a "Schedule successfully created" text 175ms

Scenario:
Create a multi schedule
2s 815ms 11

When I follow the left menu "Schedule > Maintenance Windows > Schedules" 89ms

And I wait for "1" second 1s

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

When I click on "Create" in element "maintenance-windows" 64ms

Then I should see a "Schedule Name" text 55ms

When I enter "SAP Maintenance Window" as "name" 86ms

And I choose "MULTI" 58ms

And I click on "Add Calendar" 60ms

And I select "multicalendar" from "calendarSelect" 1s 99ms

And I click on "Create Schedule" 52ms

Then I should see a "Schedule successfully created" text 187ms

Scenario:
Create another multi schedule
2s 740ms 10

When I follow the left menu "Schedule > Maintenance Windows > Schedules" 93ms

And I wait for "1" second 1s

Then I should see a "Items 1 - 2 of 2" text 62ms

When I click on "Create" 57ms

And I enter "Core Server Window" as "name" 76ms

And I choose "MULTI" 48ms

And I click on "Add Calendar" 56ms

And I select "multicalendar" from "calendarSelect" 1s 105ms

And I click on "Create Schedule" 52ms

Then I should see a "Schedule successfully created" text 187ms

Scenario:
Assign a single system to the single schedule
2s 136ms 5

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

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

And I select "singleschedule" from "maintenance-schedule" 65ms

And I click on "Update Properties" 890ms

Then I should see a "System properties changed" text 83ms

Scenario:
Assign systems to the multi schedule using SSM
4s 344ms 10

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

And I click on the clear SSM button 61ms

And I check the "rhlike_minion" client 1s 961ms

And I follow the left menu "Systems > System Set Manager > Overview" 598ms

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

And I select "SAP Maintenance Window" from "scheduleId" 1s 127ms

And I check "cancelActions" 84ms

And I click on "Assign All" 64ms

And I click on "Confirm" 67ms

Then I should see a "Maintenance schedule has been assigned" text 180ms

@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
25s 974ms 3

When I remove package "virgo-dummy" from this "rhlike_minion" without error control 1s 754ms

And I refresh packages list via spacecmd on "rhlike_minion" 7s 96ms

And I wait until refresh package list on "rhlike_minion" is finished 17s 123ms

Scenario:
Schedule package installation action
4s 848ms 10

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

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

And I follow "Install" 569ms

And I enter "virgo-dummy" as the filtered package name 48ms

And I click on the filter button 621ms

And I check "virgo-dummy" in the list 56ms

And I click on "Install Packages" 1s 155ms

And I select the next maintenance window 18ms

And I click on "Confirm" 1s 240ms

Then I should see a "1 package install has been scheduled for" text 65ms

Scenario:
Detach systems from schedules
2s 873ms 8

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

And I click on the clear SSM button 53ms

And I check the "sle_minion" client 640ms

And I follow the left menu "Systems > System Set Manager > Overview" 528ms

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

And I select "None - clear schedule" from "scheduleId" 1s 123ms

And I click on "Clear All" 62ms

Then I should see a "Maintenance schedule has been cleared" text 276ms

Scenario:
Cleanup: cancel all scheduled actions
1s 684ms 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 684ms

Scenario:
Delete maintenance schedules
1s 899ms 13

When I follow the left menu "Schedule > Maintenance Windows > Schedules" 481ms

And I click the "Core Server Window" item delete button 333ms

Then I should see a "Delete maintenance schedule" text 69ms

When I click on the red confirmation button 69ms

And I wait until I see "Schedule 'Core Server Window' has been deleted." text 198ms

And I click the "SAP Maintenance Window" item delete button 67ms

Then I should see a "Delete maintenance schedule" text 68ms

When I click on the red confirmation button 62ms

And I wait until I see "Schedule 'SAP Maintenance Window' has been deleted." text 190ms

And I click the "singleschedule" item delete button 65ms

Then I should see a "Delete maintenance schedule" text 60ms

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

When I follow the left menu "Schedule > Maintenance Windows > Calendars" 83ms

And I click the "singlecalendar" item delete button 208ms

Then I should see a "Delete maintenance calendar" text 70ms

When I click on the red confirmation button 59ms

And I wait until I see "Calendar 'singlecalendar' has been deleted." text 185ms

And I click the "multicalendar" item delete button 161ms

Then I should see a "Delete maintenance calendar" text 73ms

When I click on the red confirmation button 60ms

And I wait until I see "Calendar 'multicalendar' has been deleted." text 174ms

@flaky @scope_visualization @scope_salt
Feature:Create organizations, users, groups, and activation keys using Salt states 47s 955ms 13 2

Scenario:
Log in as org admin user
2s 797ms 1

Given I am authorized 2s 797ms

@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
17s 761ms 1

When I apply "setup_users_configuration" local salt state on "server" 17s 761ms

Scenario:
Organization my_org was correctly created
2s 269ms 5

Given I am authorized as "my_org_user" with password "my_org_user" 2s 71ms

When I follow the left menu "Home > My Organization" 69ms

Then I should see a "my_org" text in the content area 28ms

When I follow the left menu "Home > My Organization > Organization Trusts" 77ms

Then I should see a "my_org2" text in the content area 22ms

Scenario:
Organization my_org2 was correctly created
2s 40ms 5

Given I am authorized as "my_org_user2" with password "my_org_user2" 1s 864ms

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

Then I should see a "my_org2" text in the content area 24ms

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 668ms 5

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

When I follow the left menu "Systems > System Groups" 126ms

When I follow "minions_group" 389ms

Then I should see a "minions_group" text 72ms

And I should see a "System Group Status" text 65ms

Scenario:
User was correctly created
2s 328ms 5

Given I am authorized as "user2" with password "user2" 1s 773ms

When I follow the left menu "Systems > System Groups" 108ms

And I follow "minions_group" 324ms

Then I should see a "minions_group" text 64ms

And I should see a "System Group Status" text 58ms

Scenario:
User channels permissions were assigned
3s 812ms 5

Given I am authorized as "user2" with password "user2" 336ms

When I follow the left menu "Software > Channel List > All" 191ms

And I follow "Show All Child Channels" 60ms

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

And I follow "Managers" 2s 801ms

Scenario:
User Roles were assigned
2s 133ms 9

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

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

And I follow "user2" 450ms

Then I should see a "User Details" text 73ms

And I should see "role_activation_key_admin" as checked 21ms

And I should see "role_image_admin" as unchecked 18ms

And I should see "role_config_admin" as checked 18ms

And I should see "role_channel_admin" as unchecked 21ms

And I should see "role_system_group_admin" as unchecked 19ms

Scenario:
Activation Key was correctly created
616ms 6

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

And I follow "My Activation Key created via Salt" 360ms

Then I should see "10" in field identified by "usageLimit" 24ms

And I should see "virtualization_host" as checked 19ms

And I should see a "Push via SSH" text 70ms

And I should see "enable-config-auto-deploy" as checked 23ms

Scenario:
Cleanup: apply configuration teardown salt state to server
10s 826ms 1

When I apply "teardown_users_configuration" local salt state on "server" 10s 826ms

@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
257ms 3

When I follow the left menu "Admin > Organizations" 130ms

Then I should not see a "my_org" text 65ms

And I should not see a "my_org2" text 61ms

Scenario:
Cleanup: user was successfully removed
264ms 2

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

Then I should not see a "user2" text 103ms

Scenario:
Cleanup: activation key was successfully removed
179ms 2

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

Then I should not see a "My Activation Key created via Salt" text 77ms

@flaky
Feature:Export and import software channels with new ISS implementation 1m 2s 781ms 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
8s 294ms 2

When I install packages "inter-server-sync" on this "server" 4s 118ms

Then "inter-server-sync" should be installed on "server" 4s 175ms

Scenario:
Log in as org admin user
1s 803ms 1

Given I am authorized 1s 803ms

Scenario:
Clone a channel with patches
1s 979ms 9

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

And I follow "Clone Channel" 373ms

And I select "Fake-RPM-SUSE-Channel" as the origin channel 71ms

And I choose "current" 53ms

And I click on "Clone Channel" 378ms

And I should see a "Create Software Channel" text 81ms

And I should see a "Current state of the channel" text 77ms

And I click on "Clone Channel" 679ms

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

Scenario:
Check that this channel has patches
1s 208ms 8

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

And I follow "Clone of Fake-RPM-SUSE-Channel" 495ms

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

And I follow "List/Remove Patches" 515ms

Then I should see a "CL-hoag-dummy-7890" link 12ms

And I should see a "CL-virgo-dummy-3456" link 11ms

And I should see a "CL-milkyway-dummy-2345" link 10ms

And I should see a "CL-andromeda-dummy-6789" link 11ms

Scenario:
Export data with ISS v2
25s 494ms 3

When I ensure folder "/tmp/export_iss_v2" doesn't exist on "server" 2s 545ms

When I export software channels "clone-fake-rpm-suse-channel" with ISS v2 to "/tmp/export_iss_v2" 20s 324ms

Then "/tmp/export_iss_v2" folder on server is ISS v2 export directory 2s 625ms

Scenario:
Cleanup: remove cloned channels
1s 683ms 6

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

And I follow "Clone of Fake-RPM-SUSE-Channel" 375ms

And I follow "Delete Channel" 332ms

And I check "unsubscribeSystems" 83ms

And I click on "Delete Channel" 746ms

Then I should see a "Clone of Fake-RPM-SUSE-Channel" text 70ms

Scenario:
Import data with ISS v2
14s 270ms 1

When I import data with ISS v2 from "/tmp/export_iss_v2" 14s 270ms

Scenario:
Check that this channel was imported and has patches
1s 30ms 8

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

And I follow "Clone of Fake-RPM-SUSE-Channel" 383ms

And I follow "Patches" in the content area 70ms

And I follow "List/Remove Patches" 456ms

Then I should see a "CL-hoag-dummy-7890" link 11ms

And I should see a "CL-virgo-dummy-3456" link 10ms

And I should see a "CL-milkyway-dummy-2345" link 10ms

And I should see a "CL-andromeda-dummy-6789" link 11ms

Scenario:
Cleanup: remove imported channel
1s 892ms 6

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

When I follow "Clone of Fake-RPM-SUSE-Channel" 479ms

And I follow "Delete Channel" 403ms

And I check "unsubscribeSystems" 67ms

And I click on "Delete Channel" 806ms

Then I should see a "Clone of Fake-RPM-SUSE-Channel" text 64ms

Scenario:
Cleanup: remove ISS v2 export folder
5s 124ms 1

When I ensure folder "/tmp/export_iss_v2" doesn't exist on "server" 5s 124ms

Feature:Export and import configuration channels with new ISS implementation 52s 462ms 10

Distribute configuration between servers
Run export and import with ISS v2

Scenario:
Install inter server sync package
5s 287ms 2

When I install packages "inter-server-sync" on this "server" 2s 758ms

Then "inter-server-sync" should be installed on "server" 2s 528ms

Scenario:
Log in as org admin user
1s 930ms 1

Given I am authorized 1s 930ms

Scenario:
Create a configuration channel
1s 489ms 7

When I follow the left menu "Configuration > Channels" 120ms

And I follow "Create Config Channel" 310ms

And I enter "Test Config Channel" as "cofName" 67ms

And I enter "testconfigchannel" as "cofLabel" 63ms

And I enter "This is a test configuration channel" as "cofDescription" 77ms

And I click on "Create Config Channel" 788ms

Then I should see a "Test Config Channel" text 61ms

Scenario:
Add a configuration file to the test configuration channel
7s 676ms 9

When I follow the left menu "Configuration > Channels" 64ms

And I follow "Test Config Channel" 486ms

And I follow "Create Configuration File or Directory" 514ms

And I enter "/etc/s-mgr/config" as "cffPath" 69ms

And I enter "COLOR=white" in the editor 4ms

And I click on "Create Configuration File" 1s 162ms

Then I should see a "Revision 1 of /etc/s-mgr/config from channel Test Config Channel" text 102ms

And file "/srv/susemanager/salt/manager_org_1/testconfigchannel/init.sls" should exist on server 2s 733ms

And file "/srv/susemanager/salt/manager_org_1/testconfigchannel/etc/s-mgr/config" should exist on server 2s 536ms

Scenario:
Export data with ISS v2
13s 518ms 3

When I ensure folder "/tmp/export_iss_v2" doesn't exist on "server" 2s 512ms

When I export config channels "testconfigchannel" with ISS v2 to "/tmp/export_iss_v2" 8s 434ms

Then "/tmp/export_iss_v2" folder on server is ISS v2 export directory 2s 571ms

Scenario:
Cleanup: remove the test configuration channel
3s 739ms 6

When I follow the left menu "Configuration > Channels" 63ms

And I follow "Test Config Channel" 491ms

And I follow "Delete Channel" 359ms

And I click on "Delete Config Channel" 58ms

Then file "/srv/susemanager/salt/manager_org_1/testconfigchannel/init.sls" should not exist on server 2s 759ms

And I should not see a "Test Config Channel" link 8ms

Scenario:
Import data with ISS v2
3s 196ms 1

When I import data with ISS v2 from "/tmp/export_iss_v2" 3s 196ms

Scenario:
Check that the config channel was imported
6s 647ms 4

When I follow the left menu "Configuration > Channels" 60ms

Then I should see a "Test Config Channel" link 8ms

And file "/srv/susemanager/salt/manager_org_1/testconfigchannel/init.sls" should exist on server 2s 528ms

And file "/srv/susemanager/salt/manager_org_1/testconfigchannel/etc/s-mgr/config" should exist on server 4s 49ms

Scenario:
Cleanup: remove the test configuration channel
3s 742ms 6

When I follow the left menu "Configuration > Channels" 57ms

And I follow "Test Config Channel" 555ms

And I follow "Delete Channel" 342ms

And I click on "Delete Config Channel" 52ms

Then file "/srv/susemanager/salt/manager_org_1/testconfigchannel/init.sls" should not exist on server 2s 728ms

And I should not see a "Test Config Channel" link 5ms

Scenario:
Cleanup: remove ISS v2 export folder
5s 236ms 1

When I ensure folder "/tmp/export_iss_v2" doesn't exist on "server" 5s 236ms

@skip_if_github_validation @sle_minion @scope_salt
Feature:Salt master integration with Git pillar 1m 53s 215ms 3 3

Scenario:
Pre-requisite: Enabling repositories for installing git-core
5s 298ms 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 722ms

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

Scenario:
Preparing Git pillar configuration for Salt master
27s 195ms 1 2 1

When I setup a git_pillar environment on the Salt master 7s 519ms 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 (5.7 MiB/s)]

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:15: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 676ms Show Info + 
11:34:48:000 - 11:34: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
35s 456ms 4 1 1

When I refresh the pillar data 4s 107ms

And I wait until there is no pillar refresh salt job active 6s 101ms

Then the pillar data for "org_id" should be "1" on "sle_minion" 3s 450ms

And the pillar data for "git_pillar_foobar" should be "12345" on "sle_minion" 3s 487ms 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:23: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 311ms Show Info + 
11:35:15:000 - 11:35:32:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/configuration/GlobalConfigChannelList.do
Screenshot +

Scenario:
Cleanup: Remove Git pillar configuration for Salt master
22s 489ms 1 2 1

When I clean up the git_pillar environment on the Salt master 2s 496ms 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:27: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

19s 993ms Show Info + 
11:35:50:000 - 11:35: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 593ms 4

When I refresh the pillar data 4s 87ms

Then the pillar data for "git_pillar_foobar" should be empty on "sle_minion" 3s 416ms

And the pillar data for "org_id" should be "1" on "sle_minion" 4s 682ms

And the pillar data for "git_pillar_foobar" should be empty on the Salt master 5s 406ms

Scenario:
Pre-Cleanup: Disabling repositories for uninstalling git-core
5s 181ms 2

When I remove repository "SLE-Module-Basesystem15-SP7-Updates" on "server" without error control 2s 486ms

And I remove repository "SLE-Module-Basesystem15-SP7-Pool" on "server" without error control 2s 694ms

@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 25s 55ms 5

Scenario:
Log in as org admin user
1s 961ms 1

Given I am authorized 1s 961ms

@ssh_minion
Scenario:
Reboot the SSH-managed SLES minion
3m 58s 70ms 6

Given I am on the Systems overview page of this "ssh_minion" 5s 281ms

When I follow first "Schedule System Reboot" 483ms

Then I should see a "System Reboot Confirmation" text 74ms

And I should see a "Reboot system" button 17ms

When I click on "Reboot system" 846ms

Then I wait and check that "ssh_minion" has rebooted 3m 51s 366ms

Scenario:
Schedule a reboot on a SLES Salt minion
4m 33s 496ms 8

2026-04-22 11:43:33 +0200 Still waiting for action to complete...

Given I am on the Systems overview page of this "sle_minion" 980ms

When I follow first "Schedule System Reboot" 476ms

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

Then I should see a "Reboot scheduled for system" text 89ms

When I wait at most 600 seconds until event "System reboot scheduled" is completed 4m 30s 953ms

And I should see a "Reboot completed." text 57ms

@rhlike_minion
Scenario:
Reboot the Red Hat-like minion and wait until reboot is completed
3m 45s 543ms 8

2026-04-22 11:48:08 +0200 Still waiting for action to complete...

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

When I follow first "Schedule System Reboot" 571ms

Then I should see a "System Reboot Confirmation" text 69ms

And I should see a "Reboot system" button 18ms

When I click on "Reboot system" 1s 251ms

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 42s 435ms

Then I should see a "Reboot completed." text 69ms

@deblike_minion
Scenario:
Reboot the Debian-like minion and wait until reboot is completed
4m 5s 984ms 8

2026-04-22 11:51:58 +0200 Still waiting for action to complete...

Given I am on the Systems overview page of this "deblike_minion" 6s 108ms

When I follow first "Schedule System Reboot" 488ms

Then I should see a "System Reboot Confirmation" text 67ms

And I should see a "Reboot system" button 18ms

When I click on "Reboot system" 888ms

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 58s 268ms

Then I should see a "Reboot completed." text 59ms

@skip_if_github_validation @sle_minion @scope_cve_audit
Feature:CVE Audit on SLE Salt Minions 1m 16s 64ms 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
1s 985ms 1

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

Scenario:
Pre-requisite: downgrade milkyway-dummy to lower version
11s 90ms 9

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 1s 20ms

And I install old package "milkyway-dummy-1.0" on this "sle_minion" 2s 666ms

And I refresh the metadata for "sle_minion" 949ms

And I follow the left menu "Admin > Task Schedules" 138ms

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

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

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

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

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

Scenario:
Schedule channel data refresh
5s 57ms 6

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

And I follow "cve-server-channels-default" 1s 89ms

And I follow "cve-server-channels-bunch" 1s 239ms

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

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

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

Scenario:
Display CVE audit page
216ms 3

When I follow the left menu "Audit > CVE Audit" 119ms

Then I should see a "CVE Audit" link in the left menu 26ms

And I should see a "CVE Audit" text 70ms

Scenario:
Search for a known CVE number
21s 614ms 14

When I follow the left menu "Audit > CVE Audit" 60ms

And I select "1999" from "cveIdentifierYear" 68ms

And I enter "9999" as "cveIdentifierId" 69ms

And I click on "Audit Servers" 59ms

Then I should see "sle_minion" as link 921ms

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

And I should see a "Download CSV" link 11ms

And I should see a "Status" button 19ms

And I should see a "Name" button 17ms

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

And I should see a "Relevant Patches" text 84ms

Scenario:
Search for an unknown CVE number
456ms 5

When I follow the left menu "Audit > CVE Audit" 107ms

And I select "2012" from "cveIdentifierYear" 56ms

And I enter "2806" as "cveIdentifierId" 55ms

And I click on "Audit Servers" 50ms

Then I should see a "The specified CVE number was not found" text 187ms

Scenario:
Select a system for the System Set Manager
1s 984ms 11

And I click on the clear SSM button 60ms

And I follow the left menu "Audit > CVE Audit" 65ms

And I select "1999" from "cveIdentifierYear" 47ms

And I enter "9999" as "cveIdentifierId" 56ms

And I click on "Audit Servers" 53ms

Then I should see a "Affected, at least one patch available in an assigned channel" text 86ms

When I check the "sle_minion" client 733ms

Then I should see a "system selected" text 218ms

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

Then I should see "sle_minion" as link 431ms

And I click on the clear SSM button 49ms

Scenario:
List systems by patch status via API before patch
7s 470ms 12

Result list: [{"errata_advisories"=>[], "system_id"=>1000010003, "channel_labels"=>[], "patch_status"=>"NOT_AFFECTED"}, {"errata_advisories"=>[], "system_id"=>1000010001, "channel_labels"=>[], "patch_status"=>"NOT_AFFECTED"}, {"errata_advisories"=>[], "system_id"=>1000010004, "channel_labels"=>[], "patch_status"=>"NOT_AFFECTED"}, {"errata_advisories"=>[], "system_id"=>1000010002, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}, {"errata_advisories"=>[], "system_id"=>1000010005, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}, {"errata_advisories"=>[], "system_id"=>1000010000, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}]
Result list: [{"errata_advisories"=>["milkyway-dummy-2345"], "system_id"=>1000010003, "channel_labels"=>["fake-rpm-suse-channel"], "patch_status"=>"AFFECTED_FULL_PATCH_APPLICABLE"}, {"errata_advisories"=>["milkyway-dummy-2345"], "system_id"=>1000010001, "channel_labels"=>["fake-base-channel-rh-like"], "patch_status"=>"AFFECTED_FULL_PATCH_APPLICABLE"}, {"errata_advisories"=>[], "system_id"=>1000010004, "channel_labels"=>[], "patch_status"=>"NOT_AFFECTED"}, {"errata_advisories"=>[], "system_id"=>1000010002, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}, {"errata_advisories"=>[], "system_id"=>1000010005, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}, {"errata_advisories"=>[], "system_id"=>1000010000, "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" 128ms

And I follow "cve-server-channels-default" 1s 377ms

And I follow "cve-server-channels-bunch" 1s 168ms

And I click on "Single Run Schedule" 302ms

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

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

When I call audit.list_systems_by_patch_status() with CVE identifier "CVE-1999-9979" 1s 278ms

Then I should get status "NOT_AFFECTED" for "sle_minion" 410ms

When I call audit.list_systems_by_patch_status() with CVE identifier "CVE-1999-9999" 1s 46ms

Then I should get status "AFFECTED_FULL_PATCH_APPLICABLE" for "sle_minion" 359ms

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

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

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

And I follow "Patches" in the content area 66ms

And I enter "milkyway" as the filtered synopsis 51ms

And I click on the filter button 541ms

And I check "milkyway-dummy-2345" in the list 60ms

And I click on "Apply Patches" 608ms

And I click on "Confirm" 766ms

Then I should see a "patch update has been scheduled" text 88ms

And I wait until event "Patch Update: milkyway-dummy-2345" is completed 18s 900ms

Scenario:
List systems by patch status via API after patch
1s 354ms 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"=>1000010002, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}, {"errata_advisories"=>[], "system_id"=>1000010005, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}, {"errata_advisories"=>[], "system_id"=>1000010000, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}]

And I call audit.list_systems_by_patch_status() with CVE identifier "CVE-1999-9999" 997ms

Then I should get status "PATCHED" for "sle_minion" 356ms

Scenario:
Cleanup: remove installed packages
2s 566ms 2

When I disable repository "test_repo_rpm_pool" on this "sle_minion" without error control 823ms

And I remove package "milkyway-dummy" from this "sle_minion" without error control 1s 742ms

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 47s 251ms 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
437ms 1

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

@skip_if_github_validation
Scenario:
Enable repositories for openSCAP on the Red Hat-like minion
34s 738ms 2

When I enable the repositories "Rocky-BaseOS Rocky-AppStream" on this "rhlike_minion" 445ms

And I refresh the metadata for "rhlike_minion" 34s 292ms

@skip_if_github_validation
Scenario:
Install the OpenSCAP packages on the Red Hat-like minion
1m 22s 698ms 5

Given I am on the Systems overview page of this "rhlike_minion" 980ms

And I install OpenSCAP dependencies on "rhlike_minion" 42s 590ms

And I follow "Software" in the content area 75ms

And I click on "Update Package List" 594ms

And I wait until event "Package List Refresh" is completed 38s 457ms

Scenario:
Schedule an OpenSCAP audit job on the Red Hat-like minion
1m 13s 895ms 10

Given I am on the Systems overview page of this "rhlike_minion" 932ms

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

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

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

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

And I enter "--profile xccdf_org.ssgproject.content_profile_anssi_bp28_intermediary" as "params" 127ms

And I enter "/usr/share/xml/scap/ssg/content/ssg-rhel8-ds.xml" as "path" 93ms

And I click on "Schedule" 903ms

Then I should see a "XCCDF scan has been scheduled" text 69ms

And I wait at most 500 seconds until event "OpenSCAP xccdf scanning" is completed 1m 11s 489ms

Scenario:
Check the results of the OpenSCAP scan on the Red Hat-like minion
2s 754ms 7

Given I am on the Systems overview page of this "rhlike_minion" 996ms

When I follow "Audit" in the content area 83ms

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

And I follow "xccdf_org.open-scap_testresult" 946ms

Then I should see a "Details of XCCDF Scan" text 232ms

And I should see a "RHEL-8" text 223ms

And I should see a "XCCDF Rule Results" text 203ms

Scenario:
Cleanup: remove audit scans retention period from Red Hat-like minion
1s 16ms 6

When I follow the left menu "Admin > Organizations" 135ms

When I follow "SUSE Test" in the content area 66ms

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

And I enter "0" as "scap_retention_period" 67ms

And I click on "Update Organization" 62ms

Then I should see a "Organization SUSE Test was successfully updated." text 619ms

Scenario:
Cleanup: delete audit results from Red Hat-like minion
4s 571ms 8

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

When I follow "Audit" in the content area 61ms

And I follow "OpenSCAP" in the content area 54ms

And I follow "List Scans" in the content area 64ms

And I click on "Select All" 414ms

And I click on "Remove" 1s 82ms

And I click on "Confirm" 1s 779ms

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
769ms 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 56ms

And I enter "90" as "scap_retention_period" 44ms

And I click on "Update Organization" 434ms

Then I should see a "Organization SUSE Test was successfully updated." text 69ms

@skip_if_github_validation
Scenario:
Cleanup: remove the OpenSCAP packages from the Red Hat-like minion
5s 209ms 2

When I remove OpenSCAP dependencies from "rhlike_minion" 5s 15ms

And I disable repository "Rocky-BaseOS" on this "rhlike_minion" 194ms

@skip_if_github_validation
Scenario:
Cleanup: restore the base channel for the Red Hat-like minion
21s 160ms 11

Warning: Radio button 'Fake-Base-Channel-RH-like' is already checked

Given I am on the Systems overview page of this "rhlike_minion" 918ms

When I follow "Software" in the content area 68ms

And I follow "Software Channels" in the content area 69ms

And I wait until I do not see "Loading..." text 68ms

And I check radio button "Fake-Base-Channel-RH-like" 211ms

And I wait until I do not see "Loading..." text 432ms

And I click on "Next" 64ms

Then I should see a "Confirm Software Channel Change" text 61ms

When I click on "Confirm" 78ms

Then I should see a "Changing the channels has been scheduled." text 305ms

And I wait until event "Subscribe channels scheduled" is completed 18s 883ms

@skip_if_github_validation @scope_res @rhlike_minion
Feature:Remote command on the Red Hat-like Salt minion 28s 574ms 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 659ms 1

Given I am authorized 1s 659ms

Scenario:
Run a remote command on the Red Hat-like minion
26s 915ms 11

When I follow the left menu "Salt > Remote Commands" 125ms

Then I should see a "Remote Commands" text in the content area 28ms

When I enter command "cat /etc/os-release" 86ms

And I enter target "rhlike_minion" 108ms

And I click on preview 11s 296ms

And I click on run 46ms

Then I should see "rhlike_minion" hostname 51ms

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 60ms

And I should see a "ROCKY_SUPPORT_PRODUCT" text 61ms

@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 36s 310ms 12

Scenario:
Log in as org admin user
1s 986ms 1

Given I am authorized 1s 986ms

Scenario:
Delete the Red Hat-like minion before SSH minion tests
4m 7s 288ms 7

When I am on the Systems overview page of this "rhlike_minion" 2s 48ms

And I follow "Delete System" 474ms

Then I should see a "Confirm System Profile Deletion" text 63ms

When I click on "Delete Profile" 80ms

And I wait until I see "has been deleted" text 4m 3s 882ms

And I wait until Salt client is inactive on "rhlike_minion" 341ms

Then "rhlike_minion" should not be registered 396ms

Scenario:
Bootstrap a SSH-managed Red Hat-like minion
2m 15s 990ms 11

The hostname of rhlike_minion is uyuni-master-rhlike-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 82ms

Then I should see a "Bootstrap Minions" text 61ms

When I check "manageWithSSH" 90ms

And I enter the hostname of "rhlike_minion" as "hostname" 144ms

And I enter "linux" as "password" 86ms

And I select the hostname of "proxy" from "proxies" if present 2s 920ms

And I click on "Bootstrap" 64ms

And I wait at most 480 seconds until I see "Bootstrap process initiated." text 49s 85ms

And I follow the left menu "Systems > System List > All" 155ms

And I wait until I see the name of "rhlike_minion", refreshing the page 44s 426ms

And I wait until onboarding is completed for "rhlike_minion" 38s 871ms

@proxy
Scenario:
Check connection from SSH-managed Red Hat-like minion to proxy
1s 236ms 4

Given I am on the Systems overview page of this "rhlike_minion" 1s 17ms

When I follow "Details" in the content area 78ms

And I follow "Connection" in the content area 68ms

Then I should see "proxy" short hostname 71ms

@proxy
Scenario:
Check registration on proxy of SSH-managed Red Hat-like minion
1s 478ms 4

Given I am on the Systems overview page of this "proxy" 1s 232ms

When I follow "Details" in the content area 62ms

And I follow "Proxy" in the content area 66ms

Then I should see "rhlike_minion" hostname 116ms

Scenario:
Subscribe the SSH-managed Red Hat-like minion to a base channel
52s 929ms 11

Given I am on the Systems overview page of this "rhlike_minion" 1s 192ms

When I follow "Software" in the content area 68ms

And I follow "Software Channels" in the content area 72ms

And I wait until I do not see "Loading..." text 70ms

And I check radio button "Fake-Base-Channel-RH-like" 10s 87ms

And I wait until I do not see "Loading..." text 423ms

And I click on "Next" 63ms

Then I should see a "Confirm Software Channel Change" text 57ms

When I click on "Confirm" 77ms

Then I should see a "Changing the channels has been scheduled." text 276ms

And I wait until event "Subscribe channels scheduled" is completed 40s 538ms

Scenario:
Check events history for failures on SSH-managed Red Hat-like minion
1m 2s 358ms 2

Given I am on the Systems overview page of this "rhlike_minion" 1s 30ms

Then I check for failed events on history event page 1m 1s 328ms

Scenario:
Run a remote command on the SSH-managed Red Hat-like minion
29s 807ms 11

When I follow the left menu "Salt > Remote Commands" 125ms

Then I should see a "Remote Commands" text in the content area 20ms

When I enter command "cat /etc/os-release" 98ms

And I enter target "rhlike_minion" 109ms

And I click on preview 14s 189ms

And I click on run 47ms

Then I should see "rhlike_minion" hostname 62ms

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 52ms

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 65ms 2

Given I am on the Systems overview page of this "rhlike_minion" 996ms

Then I check for failed events on history event page 1m 11s 69ms

Scenario:
Cleanup: delete the SSH-managed Red Hat-like minion
14s 647ms 6

When I am on the Systems overview page of this "rhlike_minion" 987ms

And I follow "Delete System" 463ms

Then I should see a "Confirm System Profile Deletion" text 63ms

When I click on "Delete Profile" 80ms

And I wait until I see "has been deleted" text 12s 568ms

Then "rhlike_minion" should not be registered 484ms

Scenario:
Cleanup: bootstrap a Red Hat-like minion after SSH minion tests
1m 45s 212ms 12

The hostname of rhlike_minion is uyuni-master-rhlike-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 84ms

Then I should see a "Bootstrap Minions" text 62ms

When I enter the hostname of "rhlike_minion" as "hostname" 147ms

And I enter "22" as "port" 55ms

And I enter "root" as "user" 61ms

And I enter "linux" as "password" 93ms

And I select the hostname of "proxy" from "proxies" if present 78ms

And I click on "Bootstrap" 64ms

And I wait at most 480 seconds until I see "Bootstrap process initiated." text 21s 533ms

And I follow the left menu "Systems > System List > All" 139ms

And I wait until I see the name of "rhlike_minion", refreshing the page 57s 823ms

And I wait until onboarding is completed for "rhlike_minion" 25s 68ms

Scenario:
Cleanup: re-subscribe the Red Hat-like minion to a base channel
31s 308ms 11

Given I am on the Systems overview page of this "rhlike_minion" 1s 37ms

When I follow "Software" in the content area 75ms

And I follow "Software Channels" in the content area 66ms

And I wait until I do not see "Loading..." text 75ms

And I check radio button "Fake-Base-Channel-RH-like" 10s 81ms

And I wait until I do not see "Loading..." text 511ms

And I click on "Next" 63ms

Then I should see a "Confirm Software Channel Change" text 59ms

When I click on "Confirm" 94ms

Then I should see a "Changing the channels has been scheduled." text 281ms

And I wait until event "Subscribe channels scheduled" is completed 18s 962ms

@skip_if_github_validation @scope_deblike @deblike_minion
Feature:Remote command on Debian-like Salt minion 15s 529ms 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 164ms 1

Given I am authorized 2s 164ms

Scenario:
Run a remote command on the Debian-like minion
13s 365ms 10

When I follow the left menu "Salt > Remote Commands" 128ms

Then I should see a "Remote Commands" text in the content area 21ms

When I enter command "cat /etc/os-release" 88ms

And I enter target "deblike_minion" 94ms

And I click on preview 11s 757ms

And I click on run 49ms

Then I should see "deblike_minion" hostname 52ms

When I wait until I see "show response" text 1s 72ms

And I expand the results for "deblike_minion" 49ms

Then I should see a "ID=ubuntu" text 51ms

@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 39s 914ms 12

Scenario:
Log in as org admin user
2s 495ms 1

Given I am authorized 2s 495ms

Scenario:
Delete the Debian-like minion
4m 8s 379ms 7

When I am on the Systems overview page of this "deblike_minion" 2s 18ms

And I follow "Delete System" 467ms

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 4m 3s 599ms

And I wait until Salt client is inactive on "deblike_minion" 1s 784ms

Then "deblike_minion" should not be registered 383ms

Scenario:
Bootstrap a SSH-managed Debian-like minion
2m 15s 564ms 11

The hostname of deblike_minion is uyuni-master-deblike-minion

When I follow the left menu "Systems > Bootstrapping" 81ms

Then I should see a "Bootstrap Minions" text 62ms

When I check "manageWithSSH" 116ms

And I enter the hostname of "deblike_minion" as "hostname" 124ms

And I enter "linux" as "password" 66ms

And I select the hostname of "proxy" from "proxies" if present 84ms

And I click on "Bootstrap" 64ms

And I wait at most 480 seconds until I see "Bootstrap process initiated." text 51s 604ms

And I follow the left menu "Systems > System List > All" 147ms

And I wait until I see the name of "deblike_minion", refreshing the page 30s 848ms

And I wait until onboarding is completed for "deblike_minion" 52s 361ms

@proxy
Scenario:
Check connection from SSH-managed Debian-like minion to proxy
1s 351ms 4

Given I am on the Systems overview page of this "deblike_minion" 1s 142ms

When I follow "Details" in the content area 76ms

And I follow "Connection" in the content area 68ms

Then I should see "proxy" short hostname 64ms

@proxy
Scenario:
Check registration on proxy of SSH-managed Debian-like minion
1s 193ms 4

Given I am on the Systems overview page of this "proxy" 960ms

When I follow "Details" in the content area 61ms

And I follow "Proxy" in the content area 67ms

Then I should see "deblike_minion" hostname 103ms

Scenario:
Subscribe the SSH-managed Debian-like minion to a base channel
50s 893ms 11

Given I am on the Systems overview page of this "deblike_minion" 1s 196ms

When I follow "Software" in the content area 72ms

And I follow "Software Channels" in the content area 67ms

And I wait until I do not see "Loading..." text 64ms

And I check radio button "Fake-Base-Channel-Debian-like" 10s 84ms

And I wait until I do not see "Loading..." text 396ms

And I click on "Next" 62ms

Then I should see a "Confirm Software Channel Change" text 57ms

When I click on "Confirm" 77ms

Then I should see a "Changing the channels has been scheduled." text 279ms

And I wait until event "Subscribe channels scheduled" is completed 38s 533ms

Scenario:
Check events history for failures on SSH-managed Debian-like minion
1m 2s 193ms 2

Given I am on the Systems overview page of this "deblike_minion" 1s 94ms

Then I check for failed events on history event page 1m 1s 98ms

Scenario:
Run a remote command on the SSH-managed Debian-like minion
22s 429ms 10

When I follow the left menu "Salt > Remote Commands" 141ms

Then I should see a "Remote Commands" text in the content area 23ms

When I enter command "cat /etc/os-release" 95ms

And I enter target "deblike_minion" 93ms

And I click on preview 15s 918ms

And I click on run 49ms

Then I should see "deblike_minion" hostname 66ms

When I wait until I see "show response" text 5s 939ms

And I expand the results for "deblike_minion" 48ms

Then I should see a "ID=ubuntu" text 53ms

Scenario:
Check events history for failures on SSH-managed Debian-like minion
1m 12s 243ms 2

Given I am on the Systems overview page of this "deblike_minion" 1s 210ms

Then I check for failed events on history event page 1m 11s 33ms

Scenario:
Cleanup: delete the SSH-managed Debian-like minion
19s 377ms 6

When I am on the Systems overview page of this "deblike_minion" 2s 801ms

And I follow "Delete System" 459ms

Then I should see a "Confirm System Profile Deletion" text 66ms

When I click on "Delete Profile" 62ms

And I wait until I see "has been deleted" text 15s 497ms

Then "deblike_minion" should not be registered 489ms

Scenario:
Cleanup: bootstrap a Debian-like minion
1m 52s 854ms 12

The hostname of deblike_minion is uyuni-master-deblike-minion

When I follow the left menu "Systems > Bootstrapping" 81ms

Then I should see a "Bootstrap Minions" text 62ms

When I enter the hostname of "deblike_minion" as "hostname" 127ms

And I enter "22" as "port" 54ms

And I enter "root" as "user" 58ms

And I enter "linux" as "password" 61ms

And I select the hostname of "proxy" from "proxies" if present 79ms

And I click on "Bootstrap" 65ms

And I wait at most 480 seconds until I see "Bootstrap process initiated." text 29s 307ms

And I follow the left menu "Systems > System List > All" 142ms

And I wait until I see the name of "deblike_minion", refreshing the page 44s 197ms

And I wait until onboarding is completed for "deblike_minion" 38s 616ms

Scenario:
Cleanup: re-subscribe the Debian-like minion to a base channel
30s 939ms 11

Given I am on the Systems overview page of this "deblike_minion" 987ms

When I follow "Software" in the content area 82ms

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 "Fake-Base-Channel-Debian-like" 10s 75ms

And I wait until I do not see "Loading..." text 383ms

And I click on "Next" 61ms

Then I should see a "Confirm Software Channel Change" text 59ms

When I click on "Confirm" 77ms

Then I should see a "Changing the channels has been scheduled." text 278ms

And I wait until event "Subscribe channels scheduled" is completed 18s 796ms

@scope_salt_ssh @scope_onboarding @ssh_minion @skip_if_github_validation
Feature:Register a salt-ssh system via API 4m 22s 784ms 11 1

Scenario:
Log in as org admin user
2s 101ms 1

Given I am authorized 2s 101ms

Scenario:
Delete SSH minion system profile before API bootstrap test
19s 542ms 6

Given I am on the Systems overview page of this "ssh_minion" 1s 732ms

When I follow "Delete System" 454ms

Then I should see a "Confirm System Profile Deletion" text 61ms

When I click on "Delete Profile" 64ms

And I wait until I see "has been deleted" text 16s 655ms

Then "ssh_minion" should not be registered 575ms

@proxy
Scenario:
Block direct access from server to sshminion to test proxy as jumphost
1s 146ms 1

Given I block connections from "server" on "ssh_minion" 1s 146ms

Scenario:
Bootstrap a SLES SSH minion via API
50s 79ms 1

When I call system.bootstrap() on host "ssh_minion" and salt-ssh "enabled" 50s 79ms

Scenario:
Check new API bootstrapped salt-ssh system in System Overview page
1m 34s 937ms 3

When I follow the left menu "Systems > System List > All" 98ms

And I wait until I see the name of "ssh_minion", refreshing the page 17s 191ms

And I wait until onboarding is completed for "ssh_minion" 1m 17s 646ms

Scenario:
Check contact method of this Salt SSH system
1s 149ms 2

Given I am on the Systems overview page of this "ssh_minion" 1s 65ms

Then I should see a "Push via SSH" text 83ms

@proxy
Scenario:
Check registration on proxy of SSH minion bootstrapped via API
1s 203ms 4

Given I am on the Systems overview page of this "proxy" 961ms

When I follow "Details" in the content area 77ms

And I follow "Proxy" in the content area 66ms

Then I should see "ssh_minion" hostname 99ms

Scenario:
Check spacecmd system ID of SSH minion bootstrapped via API
8s 495ms 2

Given I am on the Systems overview page of this "ssh_minion" 1s 100ms

Then I run spacecmd listeventhistory for "ssh_minion" 7s 395ms

Scenario:
Check events history for failures on SSH minion after API bootstrap
41s 962ms 2

Given I am on the Systems overview page of this "ssh_minion" 1s 12ms

Then I check for failed events on history event page 40s 950ms

@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
41s 412ms 13

Warning: Radio button 'openSUSE Tumbleweed (x86_64)' is already checked

Given I am on the Systems overview page of this "ssh_minion" 1s 36ms

When I follow "Software" in the content area 72ms

And I follow "Software Channels" in the content area 64ms

And I wait until I do not see "Loading..." text 72ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 172ms

And I wait until I do not see "Loading..." text 417ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 38ms

And I check "Fake-RPM-SUSE-Channel" 37ms

And I click on "Next" 60ms

Then I should see a "Confirm Software Channel Change" text 62ms

When I click on "Confirm" 58ms

Then I should see a "Changing the channels has been scheduled." text 557ms

And I wait until event "Subscribe channels scheduled" is completed 38s 762ms

@proxy
Scenario:
Cleanup and flush the firewall rules
752ms 1

When I flush firewall on "ssh_minion" 752ms

@skip_if_github_validation @scope_onboarding
Feature:Bootstrap a Salt minion via the GUI using SSH key 7m 30s 744ms 7 1

Scenario:
Log in as org admin user
2s 26ms 1

Given I am authorized 2s 26ms

Scenario:
Delete SLES minion system profile before bootstrap with SSH key test
4m 8s 782ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 643ms

When I follow "Delete System" 480ms

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 5s 303ms

And I wait until Salt client is inactive on "sle_minion" 847ms

Then "sle_minion" should not be registered 383ms

Scenario:
Prepare the minion for SSH key authentication
1s 346ms 2

When I backup the SSH authorized_keys file of host "sle_minion" 420ms

And I add pre-generated SSH public key to authorized_keys of host "sle_minion" 926ms

Scenario:
Bootstrap a SLES minion using SSH key with wrong passphrase
38s 472ms 14 1 1

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 81ms

Then I should see a "Bootstrap Minions" text 64ms

When I enter the hostname of "sle_minion" as "hostname" 142ms

And I enter "22" as "port" 52ms

And I enter "root" as "user" 59ms

And I check radio button "SSH Private Key" 10s 75ms

And I attach the file "ssh_keypair/id_rsa_bootstrap-passphrase_linux" to "privKeyFile" 37ms

And I enter "you-shall-not-pass" as "privKeyPwd" 91ms

And I click on "Bootstrap" 60ms

And I wait until I see "An error has occurred during salt execution: unable to establish ssh connection." text 7s 602ms

Then I should see a "Details" button 18ms

When I click on "Details" 72ms

And I wait at most 10 seconds until I see modal containing "Error Details" text 12ms

Then I should see a "Standard Error" text 66ms

And I should see "Permission denied, no authentication information" or "Permission denied (publickey,password,keyboard-interactive)" in the stderr textarea 20s 32ms 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
1m 10s 382ms 11

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 77ms

Then I should see a "Bootstrap Minions" text 61ms

When I enter the hostname of "sle_minion" as "hostname" 133ms

And I enter "22" as "port" 51ms

And I enter "root" as "user" 56ms

And I check radio button "SSH Private Key" 10s 69ms

And I attach the file "ssh_keypair/id_rsa_bootstrap-passphrase_linux" to "privKeyFile" 37ms

And I enter "linux" as "privKeyPwd" 60ms

And I select the hostname of "proxy" from "proxies" if present 73ms

And I click on "Bootstrap" 66ms

And I wait at most 480 seconds until I see "Bootstrap process initiated." text 59s 694ms

Scenario:
Check new minion bootstrapped with SSH key in System Overview page
1m 27s 261ms 6

It took 4 seconds to contact the minion

When I follow the left menu "Salt > Keys" 146ms

Then I should see a "accepted" text 336ms

When I am on the Systems page 243ms

And I wait until I see the name of "sle_minion", refreshing the page 30s 637ms

And I wait until onboarding is completed for "sle_minion" 52s 147ms

Then the Salt master can reach "sle_minion" 3s 750ms

Scenario:
Also check contact method of this minion
1s 247ms 2

Given I am on the Systems overview page of this "sle_minion" 1s 163ms

Then I should see a "Default" text 84ms

Scenario:
Cleanup: restore authorized keys
1s 224ms 1

When I restore the SSH authorized_keys file of host "sle_minion" 1s 224ms

@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 55s 353ms 9 1

Scenario:
Log in as org admin user
2s 1

Given I am authorized 2s

Scenario:
Pre-requisite: remove package before ssh tunnel test
1s 849ms 1

When I remove package "milkyway-dummy" from this "ssh_minion" without error control 1s 849ms

Scenario:
Delete the Salt minion for SSH tunnel bootstrap
17s 767ms 6

Given I am on the Systems overview page of this "ssh_minion" 1s 106ms

When I follow "Delete System" 473ms

Then I should see a "Confirm System Profile Deletion" text 60ms

When I click on "Delete Profile" 65ms

And I wait until I see "has been deleted" text 15s 368ms

Then "ssh_minion" should not be registered 693ms

Scenario:
Register this minion for push via SSH tunnel
2m 37s 335ms 12

The hostname of ssh_minion is uyuni-master-suse-sshminion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 84ms

Then I should see a "Bootstrap Minions" text 61ms

And I enter the hostname of "ssh_minion" as "hostname" 152ms

And I enter "22" as "port" 54ms

And I enter "root" as "user" 59ms

And I enter "linux" as "password" 62ms

And I select "1-SUSE-SSH-TUNNEL-KEY-x86_64" from "activationKeys" 70ms

And I select the hostname of "proxy" from "proxies" if present 66ms

And I check "manageWithSSH" 85ms

And I click on "Bootstrap" 60ms

And I wait at most 480 seconds until I see "Bootstrap process initiated." text 44s 953ms

And I wait until onboarding is completed for "ssh_minion" 1m 51s 624ms

Scenario:
The contact method is SSH tunnel on this minion
1s 42ms 2

Given I am on the Systems overview page of this "ssh_minion" 954ms

Then I should see a "Push via SSH tunnel" text 87ms

Scenario:
Install a package from this SSH tunnel minion
59s 215ms 11

Given I am on the Systems overview page of this "ssh_minion" 1s 39ms

When I follow "Software" in the content area 76ms

And I follow "Install" 591ms

And I enter "milkyway-dummy" as the filtered package name 58ms

And I click on the filter button 616ms

And I wait until I see "milkyway-dummy" text 77ms

And I check row with "milkyway-dummy" and arch of "ssh_minion" 62ms

And I click on "Install Packages" 774ms

And I click on "Confirm" 813ms

Then I should see a "1 package install has been scheduled for" text 61ms

Then I wait until event "Package Install/Upgrade scheduled" is completed 55s 43ms

@flaky
Scenario:
Remove a package from this SSH tunnel minion
4m 34s 125ms 6 5 1

Given I am on the Systems overview page of this "ssh_minion" 1s 129ms

And I follow "Software" in the content area 81ms

And I follow "List / Remove" 990ms

And I enter "milkyway-dummy" as the filtered package name 61ms

And I click on the filter button 809ms

And I wait until I see "milkyway-dummy" text 4m 10s 20ms 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

21s 32ms Show Info + 
12:42:34:000 - 12:46:48: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
30s 788ms 11

The hostname of ssh_minion is uyuni-master-suse-sshminion.sumaci.aws

When I follow the left menu "Salt > Remote Commands" 134ms

Then I should see a "Remote Commands" text in the content area 21ms

When I enter command "echo 'My remote command output'" 106ms

And I enter the hostname of "ssh_minion" as "target" 116ms

And I click on preview 19s 765ms

Then I should see a "Target systems (1)" text 61ms

When I wait until I do not see "pending" text 50ms

And I click on run 48ms

And I wait until I see "show response" text 10s 412ms

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 335ms 6

Given I am on the Systems overview page of this "ssh_minion" 1s 47ms

When I follow "Delete System" 463ms

Then I should see a "Confirm System Profile Deletion" text 61ms

When I click on "Delete Profile" 63ms

And I wait until I see "has been deleted" text 21s 258ms

Then "ssh_minion" should not be registered 441ms

Scenario:
Cleanup: register a SSH minion after SSH tunnel tests
2m 27s 892ms 4

When I call system.bootstrap() on host "ssh_minion" and salt-ssh "enabled" 44s 582ms

And I follow the left menu "Systems > System List > All" 97ms

And I wait until I see the name of "ssh_minion", refreshing the page 30s 839ms

And I wait until onboarding is completed for "ssh_minion" 1m 12s 372ms

@skip_if_github_validation @scope_onboarding
Feature:Bootstrap a Salt minion via the GUI with an activation key 7m 26s 857ms 14 2

Scenario:
Log in as org admin user
1s 920ms 1

Given I am authorized 1s 920ms

Scenario:
Delete SLES minion system profile
4m 7s 567ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 700ms

When I follow "Delete System" 456ms

Then I should see a "Confirm System Profile Deletion" text 62ms

When I click on "Delete Profile" 64ms

And I wait until I see "has been deleted" text 4m 3s 852ms

And I wait until Salt client is inactive on "sle_minion" 875ms

Then "sle_minion" should not be registered 555ms

Scenario:
Create a configuration channel for the activation key
876ms 7

When I follow the left menu "Configuration > Channels" 131ms

And I follow "Create Config Channel" 312ms

And I enter "Key Channel" as "cofName" 67ms

And I enter "keychannel" as "cofLabel" 55ms

And I enter "This is a configuration channel for the activation key" as "cofDescription" 93ms

And I click on "Create Config Channel" 64ms

Then I should see a "Key Channel" text 152ms

Scenario:
Add a configuration file to the key configuration channel
987ms 6

When I follow the left menu "Configuration > Channels" 64ms

And I follow "Key Channel" 415ms

And I follow "Create Configuration File or Directory" 373ms

And I enter "/etc/euler.conf" as "cffPath" 64ms

And I enter "e^i.pi=-1" in the editor 4ms

And I click on "Create Configuration File" 65ms

@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 982ms 19

When I follow the left menu "Systems > Activation Keys" 127ms

And I follow "Create Key" 336ms

And I wait for child channels to appear 1s 437ms

And I enter "Minion testing" as "description" 86ms

And I enter "MINION-TEST" as "key" 83ms

And I enter "20" as "usageLimit" 86ms

And I select "openSUSE Tumbleweed (x86_64)" from "selectedBaseChannel" 80ms

And I wait for child channels to appear 374ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 81ms

And I check "Fake-RPM-SUSE-Channel" 74ms

And I click on "Create Activation Key" 617ms

And I follow "Configuration" in the content area 74ms

And I follow first "Subscribe to Channels" in the content area 63ms

And I check "Key Channel" in the list 55ms

And I click on "Continue" 495ms

And I follow "Packages" 312ms

And I enter "orion-dummy perseus-dummy" as "packages" 66ms

And I click on "Update Activation Key" 468ms

Then I should see a "Activation key Minion testing has been modified" text 57ms

Scenario:
Bootstrap a SLES minion with an activation key
1m 50s 296ms 13

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 71ms

Then I should see a "Bootstrap Minions" text 67ms

When I enter the hostname of "sle_minion" as "hostname" 133ms

And I enter "22" as "port" 51ms

And I enter "root" as "user" 58ms

And I enter "linux" as "password" 61ms

And I select "1-MINION-TEST" from "activationKeys" 60ms

And I select the hostname of "proxy" from "proxies" if present 60ms

And I click on "Bootstrap" 90ms

And I wait until I see "Bootstrap process initiated." text 27s 91ms

And I follow the left menu "Systems > System List > All" 145ms

And I wait until I see the name of "sle_minion", refreshing the page 44s 227ms

And I wait until onboarding is completed for "sle_minion" 38s 177ms

Scenario:
Verify that minion bootstrapped with Salt key and packages
8s 115ms 5

It took 6 seconds to contact the minion

When I follow the left menu "Salt > Keys" 123ms

Then I should see a "accepted" text 338ms

And the Salt master can reach "sle_minion" 5s 315ms

When I wait for "orion-dummy" to be installed on "sle_minion" 1s 389ms

And I wait for "perseus-dummy" to be installed on "sle_minion" 947ms

Scenario:
Check system ID of bootstrapped minion
7s 144ms 2

Given I am on the Systems overview page of this "sle_minion" 969ms

Then I run spacecmd listeventhistory for "sle_minion" 6s 174ms

@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
872ms 2

Given I am on the Systems page 239ms

Then I should see a "openSUSE Tumbleweed (x86_64)" text 632ms

Scenario:
Verify that minion bootstrapped with configuration channel
1s 552ms 6

Given I am on the Systems overview page of this "sle_minion" 1s 205ms

When I follow "Configuration" in the content area 72ms

Then I should see a "1 configuration channel" text 68ms

When I follow "View Files" in the content area 65ms

Then I should see a "/etc/euler.conf" text 72ms

And I should see a "Key Channel" text 67ms

Scenario:
Cleanup: remove the package states
7s 73ms 12

Given I am on the Systems overview page of this "sle_minion" 1s 184ms

When I follow "States" in the content area 66ms

And I follow "Packages" 529ms

Then I should see a "Package States" text 64ms

When I change the state of "orion-dummy" to "Unmanaged" and "" 140ms

And I change the state of "perseus-dummy" to "Unmanaged" and "" 40ms

Then I should see a "2 Changes" text 69ms

When I click save 49ms

Then I wait until I see "Package states have been saved." text 266ms

And I click apply 47ms

And I remove package "orion-dummy" from this "sle_minion" 2s 332ms

And I remove package "perseus-dummy" from this "sle_minion" 2s 281ms

Scenario:
Cleanup: remove the key configuration channel
1s 359ms 4

When I follow the left menu "Configuration > Channels" 112ms

And I follow "Key Channel" 431ms

And I follow "Delete Channel" 301ms

And I click on "Delete Config Channel" 515ms

Scenario:
Cleanup: delete the activation key
1s 97ms 5

When I follow the left menu "Systems > Activation Keys" 117ms

And I follow "Minion testing" in the content area 87ms

And I follow "Delete Key" 306ms

And I click on "Delete Activation Key" 505ms

Then I should see a "Activation key Minion testing has been deleted." text 81ms

Scenario:
Check events history for failures on SLES minion with activation key
53s 11ms 2

Given I am on the Systems overview page of this "sle_minion" 984ms

Then I check for failed events on history event page 52s 26ms

@skip_if_github_validation @scope_onboarding
Feature:Register a Salt minion via API 7m 30s 52ms 11 1

Scenario:
Log in as org admin user
2s 744ms 1

Given I am authorized 2s 744ms

Scenario:
Delete SLES minion system profile before API bootstrap test
4m 7s 781ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 919ms

When I follow "Delete System" 656ms

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 853ms

And I wait until Salt client is inactive on "sle_minion" 790ms

Then "sle_minion" should not be registered 433ms

Scenario:
Bootstrap a SLES minion via API
26s 605ms 1

When I call system.bootstrap() on host "sle_minion" and salt-ssh "disabled" 26s 605ms

Scenario:
Check new minion bootstrapped via API in System Overview page
1m 25s 537ms 6

It took 5 seconds to contact the minion

When I follow the left menu "Salt > Keys" 132ms

Then I should see a "accepted" text 343ms

When I follow the left menu "Systems > System List > All" 183ms

And I wait until I see the name of "sle_minion", refreshing the page 1m 11s 559ms

And I wait until onboarding is completed for "sle_minion" 8s 496ms

Then the Salt master can reach "sle_minion" 4s 822ms

Scenario:
Check contact method of this minion
1s 219ms 2

Given I am on the Systems overview page of this "sle_minion" 1s 134ms

Then I should see a "Default" text 84ms

@proxy
Scenario:
Check registration on proxy of minion bootstrapped via API
1s 284ms 4

Given I am on the Systems overview page of this "proxy" 1s 46ms

When I follow "Details" in the content area 72ms

And I follow "Proxy" in the content area 66ms

Then I should see "sle_minion" hostname 99ms

Scenario:
Check spacecmd system ID of minion bootstrapped via API
7s 141ms 2

Given I am on the Systems overview page of this "sle_minion" 1s 62ms

Then I run spacecmd listeventhistory for "sle_minion" 6s 78ms

@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
22s 29ms 13

Warning: Radio button 'openSUSE Tumbleweed (x86_64)' is already checked

Given I am on the Systems overview page of this "sle_minion" 954ms

When I follow "Software" in the content area 70ms

And I follow "Software Channels" in the content area 67ms

And I wait until I do not see "Loading..." text 68ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 407ms

And I wait until I do not see "Loading..." text 598ms

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" 82ms

Then I should see a "Confirm Software Channel Change" text 65ms

When I click on "Confirm" 58ms

Then I should see a "Changing the channels has been scheduled." text 538ms

And I wait until event "Subscribe channels scheduled" is completed 19s 39ms

Scenario:
Check events history for failures on SLES minion after API bootstrap
51s 996ms 2

Given I am on the Systems overview page of this "sle_minion" 983ms

Then I check for failed events on history event page 51s 12ms

Scenario:
Bootstrap via API a non-existing system
2s 812ms 1

When I call system.bootstrap() on unknown host, I should get an API fault 2s 812ms

Scenario:
Bootstrap a salt-ssh system with activation key and default contact method
899ms 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 899ms

@skip_if_github_validation @sle_minion @scope_onboarding
Feature:Bootstrapping with reactivation key 8m 30s 281ms 8

In order to re-register valid minions
As an authorized user
I want to avoid re-registration with invalid input parameters

Scenario:
Log in as org admin user
2s 29ms 1

Given I am authorized 2s 29ms

Scenario:
Generate a re-activation key
3s 59ms 4

Given I am on the Systems overview page of this "sle_minion" 1s 868ms

When I follow "Reactivation" 486ms

And I click on "Generate New Key" 635ms

Then I should see a "Key:" text 69ms

Scenario:
Bootstrap should fail when minion already exists
878ms 10

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 77ms

Then I should see a "Bootstrap Minions" text 62ms

When I enter the hostname of "sle_minion" as "hostname" 132ms

And I enter "22" as "port" 52ms

And I enter "root" as "user" 54ms

And I enter "linux" as "password" 54ms

And I click on "Bootstrap" 65ms

And I wait until I see "A salt key for this host" text 257ms

Then I should not see a "GenericSaltError" text 60ms

And I should see a "seems to already exist, please check!" text 61ms

Scenario:
Bootstrap should fail when system already exists in the server
6s 34ms 11

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

Given I delete "sle_minion" key in the Salt master 5s 177ms

When I follow the left menu "Systems > Bootstrapping" 62ms

Then I should see a "Bootstrap Minions" text 71ms

When I enter the hostname of "sle_minion" as "hostname" 129ms

And I enter "22" as "port" 45ms

And I enter "root" as "user" 51ms

And I enter "linux" as "password" 54ms

And I click on "Bootstrap" 56ms

And I wait until I see "seems to already exist, please check!" text 266ms

Then I should not see a "GenericSaltError" text 59ms

And I should see a "with minion id" text 59ms

Scenario:
Bootstrap a SLES minion with reactivation key
1m 57s 934ms 13

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws
Reactivation Key: re-1-4706fc0306ca4ac0be3f792db3d3d57d

When I follow the left menu "Systems > Bootstrapping" 60ms

Then I should see a "Bootstrap Minions" text 62ms

When I enter the hostname of "sle_minion" as "hostname" 123ms

And I enter "22" as "port" 47ms

And I enter "root" as "user" 51ms

And I enter "linux" as "password" 57ms

And I enter the reactivation key of "sle_minion" 1s 18ms

And I select "1-SUSE-KEY-x86_64" from "activationKeys" 72ms

And I click on "Bootstrap" 55ms

And I wait until I see "Bootstrap process initiated." text 35s 279ms

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 714ms

And I wait until onboarding is completed for "sle_minion" 1m 20s 246ms

Scenario:
Check the events history for the reactivation
3s 500ms 5

Given I am on the Systems overview page of this "sle_minion" 1s 59ms

When I follow "Events" in the content area 74ms

And I follow "History" in the content area 58ms

And I wait until I see "Server reactivated as Salt minion" text, refreshing the page 85ms

And I wait until event "Apply states [certs, channels, packages, services.salt-minion] scheduled" is completed 2s 223ms

Scenario:
Cleanup: delete SLES minion after reactivation tests
4m 5s 701ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 27ms

When I follow "Delete System" 474ms

Then I should see a "Confirm System Profile Deletion" text 60ms

When I click on "Delete Profile" 63ms

And I wait until I see "has been deleted" text 4m 2s 818ms

And I wait until Salt client is inactive on "sle_minion" 802ms

Then "sle_minion" should not be registered 454ms

Scenario:
Cleanup: bootstrap a SLES minion after reactivation tests
2m 11s 143ms 14

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I perform a full salt minion cleanup on "sle_minion" 7s 162ms

And I follow the left menu "Systems > Bootstrapping" 80ms

Then I should see a "Bootstrap Minions" text 62ms

When I enter the hostname of "sle_minion" as "hostname" 143ms

And I enter "22" as "port" 52ms

And I enter "root" as "user" 57ms

And I enter "linux" as "password" 60ms

And I select "1-SUSE-KEY-x86_64" from "activationKeys" 74ms

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 39s 941ms

And I follow the left menu "Systems > System List > All" 143ms

And I wait until I see the name of "sle_minion", refreshing the page 57s 868ms

And I wait until onboarding is completed for "sle_minion" 25s 373ms

@skip_if_github_validation @sle_minion @scope_salt
Feature:Management of minion keys 8m 54s 992ms 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 691ms 1

Given I am authorized 2s 691ms

Scenario:
Delete SLES minion system profile before exploring the onboarding page
4m 7s 333ms 7

Given I am on the Systems overview page of this "sle_minion" 2s 27ms

When I follow "Delete System" 472ms

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 579ms

And I wait until Salt client is inactive on "sle_minion" 756ms

Then "sle_minion" should not be registered 369ms

Scenario:
Completeness of the onboarding page
168ms 2

When I follow the left menu "Salt > Keys" 131ms

Then I should see a "Keys" text in the content area 37ms

Scenario:
Minion is visible in the Pending section
17s 410ms 8

When I configure salt minion on "sle_minion" 468ms

And I restart salt-minion on "sle_minion" 701ms

And I wait at most 10 seconds until Salt master sees "sle_minion" as "unaccepted" 3s 724ms

And I follow the left menu "Salt > Keys" 62ms

And I refresh page until I see "sle_minion" hostname as text 10s 148ms

Then I should see a "Fingerprint" text 71ms

And I see "sle_minion" fingerprint 2s 166ms

And I should see a "pending" text 66ms

Scenario:
Reject and delete the pending key
21s 873ms 7

And I follow the left menu "Salt > Keys" 56ms

And I reject "sle_minion" from the Pending section 309ms

And I wait at most 10 seconds until Salt master sees "sle_minion" as "rejected" 3s 873ms

Then I should see a "rejected" text 68ms

When I stop salt-minion on "sle_minion" 3s 912ms

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 604ms

Scenario:
Accepted minion shows up as a registered system
1m 32s 350ms 9

When I start salt-minion on "sle_minion" 1s 1ms

And I wait at most 10 seconds until Salt master sees "sle_minion" as "unaccepted" 3s 585ms

Then "sle_minion" should not be registered 478ms

When I follow the left menu "Salt > Keys" 62ms

Then I should see a "pending" text 418ms

When I accept "sle_minion" key 50ms

And I wait at most 10 seconds until Salt master sees "sle_minion" as "accepted" 4s 269ms

And I wait until onboarding is completed for "sle_minion" 1m 22s 103ms

Then "sle_minion" should be registered 381ms

Scenario:
The minion communicates with the Salt master
8s 732ms 3

It took 5 seconds to contact the minion

Then the Salt master can reach "sle_minion" 4s 767ms

When I get OS information of "sle_minion" from the Master 3s 964ms

Then it should contain the OS of "sle_minion" < 1ms

Scenario:
Delete profile of unreacheable minion
15s 270ms 9

Given I am on the Systems overview page of this "sle_minion" 956ms

When I stop salt-minion on "sle_minion" 3s 618ms

And I follow "Delete System" 370ms

Then I should see a "Confirm System Profile Deletion" text 63ms

When I click on "Delete Profile" 62ms

Then I wait until I see "Cleanup timed out. Please check if the machine is reachable." text 7s 564ms

When I click on "Delete Profile Without Cleanup" in "An error occurred during cleanup" modal 2s 101ms

And I wait until I see "has been deleted" text 72ms

Then "sle_minion" should not be registered 459ms

Scenario:
Cleanup: bootstrap again the minion
2m 9s 162ms 12

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I perform a full salt minion cleanup on "sle_minion" 7s 160ms

And I follow the left menu "Systems > Bootstrapping" 75ms

Then I should see a "Bootstrap Minions" text 65ms

When I enter the hostname of "sle_minion" as "hostname" 143ms

And I enter "22" as "port" 53ms

And I enter "root" as "user" 59ms

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" 60ms

And I wait until I see "Bootstrap process initiated." text 39s 458ms

And I wait until onboarding is completed for "sle_minion" 1m 21s 891ms

@skip_if_github_validation @scope_salt
Feature:Install a package and a patch on the SUSE client via Salt through the UI 2m 46s 70ms 11

Scenario:
Pre-requisite: enable test_repo_rpm_pool repository on SLE minion
854ms 1

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 854ms

Scenario:
Pre-requisite: install virgo-dummy-1.0 package on SLE minion
2s 28ms 2

When I refresh the metadata for "sle_minion" 1s 52ms

And I install old package "virgo-dummy-1.0" on this "sle_minion" without error control 975ms

Scenario:
Pre-requisite: remove andromeda-dummy package from SLE minion
22s 826ms 4

When I remove package "andromeda-dummy" from this "sle_minion" without error control 1s 734ms

And I refresh the metadata for "sle_minion" 932ms

And I refresh packages list via spacecmd on "sle_minion" 8s 473ms

And I wait until refresh package list on "sle_minion" is finished 11s 686ms

Scenario:
Pre-requisite: refresh package list and check old packages installed on SLE minion
33s 391ms 4

When I refresh packages list via spacecmd on "sle_minion" 6s 23ms

And I wait until refresh package list on "sle_minion" is finished 12s 321ms

Then spacecmd should show packages "virgo-dummy-1.0" installed on "sle_minion" 6s 252ms

And I wait until package "andromeda-dummy-2.0-1.1" is removed from "sle_minion" via spacecmd 8s 794ms

Scenario:
Log in as org admin user
2s 352ms 1

Given I am authorized for the "Admin" section 2s 352ms

Scenario:
Pre-requisite: ensure the errata cache is computed before patching Salt minion
18s 965ms 11

Given I am on the Systems overview page of this "sle_minion" 1s 838ms

When I follow "Software" in the content area 75ms

And I follow "List / Remove" in the content area 66ms

And I enter "virgo-dummy" as the filtered package name 186ms

And I click on the filter button until page does contain "virgo-dummy" text 11s 232ms

When I follow the left menu "Admin > Task Schedules" 120ms

And I follow "errata-cache-default" 379ms

And I follow "errata-cache-bunch" 1s 296ms

And I click on "Single Run Schedule" 1s 283ms

Then I should see a "bunch was scheduled" text 279ms

When I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 2s 207ms

Scenario:
Install a patch on the SLE minion
25s 524ms 12

Given I am on the Systems overview page of this "sle_minion" 938ms

When I follow "Software" in the content area 70ms

And I follow "Patches" in the content area 78ms

And I enter "virgo" as the filtered synopsis 46ms

And I click on the filter button 10s 159ms

And I check "virgo-dummy-3456" in the list 60ms

And I check "allowVendorChange" 74ms

And I click on "Apply Patches" 624ms

And I click on "Confirm" 683ms

Then I should see a "1 patch update has been scheduled for" text 77ms

When I wait for "virgo-dummy-2.0-1.1" to be installed on "sle_minion" 11s 757ms

Then vendor change should be enabled for package actions on "sle_minion" 954ms

Scenario:
Install a package on the SLE minion
14s 224ms 12

Given I am on the Systems overview page of this "sle_minion" 939ms

When I follow "Software" in the content area 78ms

And I follow "Packages" 436ms

And I follow "Install" 572ms

And I enter "andromeda" as the filtered package name 102ms

And I click on the filter button 718ms

And I check "andromeda-dummy-2.0-1.1" in the list 55ms

And I click on "Install Packages" 609ms

And I click on "Confirm" 947ms

Then I should see a "1 package install has been scheduled" text 63ms

When I wait for "andromeda-dummy-2.0-1.1" to be installed on "sle_minion" 8s 640ms

Then vendor change should be enabled for package actions on "sle_minion" 1s 59ms

Scenario:
Cleanup: disable test_repo_rpm_pool on SLE minion
501ms 1

When I disable repository "test_repo_rpm_pool" on this "sle_minion" 501ms

Scenario:
Cleanup: remove virgo-dummy package from SLE minion
23s 664ms 4

When I remove package "virgo-dummy" from this "sle_minion" without error control 1s 822ms

And I refresh the metadata for "sle_minion" 893ms

And I refresh packages list via spacecmd on "sle_minion" 8s 342ms

And I wait until refresh package list on "sle_minion" is finished 12s 605ms

Scenario:
Cleanup: remove andromeda-dummy package from SLE minion
21s 739ms 4

When I remove package "andromeda-dummy" from this "sle_minion" without error control 2s 46ms

And I refresh the metadata for "sle_minion" 896ms

And I refresh packages list via spacecmd on "sle_minion" 6s 400ms

And I wait until refresh package list on "sle_minion" is finished 12s 396ms

@skip_if_github_validation @sle_minion @scope_content_staging
Feature:Install a package on the SLES minion with staging enabled 7m 17s 287ms 8

Scenario:
Pre-requisite: install virgo-dummy-1.0 package, make sure orion-dummy is not present
3s 786ms 3

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 789ms

And I remove package "orion-dummy" from this "sle_minion" without error control 902ms

And I install package "virgo-dummy-1.0" on this "sle_minion" 2s 95ms

Scenario:
Pre-requisite: refresh package list
27s 335ms 3

When I refresh packages list via spacecmd on "sle_minion" 6s 676ms

And I wait until refresh package list on "sle_minion" is finished 12s 747ms

Then spacecmd should show packages "virgo-dummy-1.0" installed on "sle_minion" 7s 911ms

Scenario:
Log in as admin user
451ms 1

Given I am authorized for the "Admin" section 451ms

Scenario:
Pre-requisite: ensure the errata cache is computed before staging tests
36s 94ms 6

When I follow the left menu "Admin > Task Schedules" 124ms

And I follow "errata-cache-default" 1s 254ms

And I follow "errata-cache-bunch" 1s 281ms

Then I click on "Single Run Schedule" 1s 281ms

And I should see a "bunch was scheduled" text 294ms

Then I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 31s 858ms

Scenario:
Enable content staging
1s 56ms 6

When I follow the left menu "Admin > Organizations" 83ms

And I follow first "SUSE Test" 230ms

And I follow first "Configuration" 208ms

And I check "staging_content_enabled" 84ms

And I click on "Update Organization" 379ms

Then I should see a "was successfully updated." text 70ms

Scenario:
Install package in the future and check for staging
3m 4s 182ms 13

Given I am on the Systems overview page of this "sle_minion" 1s 31ms

When I follow "Software" in the content area 71ms

And I follow "Packages" in the content area 63ms

And I follow "Install" in the content area 64ms

And I enter "orion-dummy-1.1-1.1" as the filtered package name 194ms

And I click on the filter button 730ms

And I check row with "orion-dummy-1.1-1.1" and arch of "sle_minion" 59ms

And I click on "Install Packages" 610ms

And I pick 3 minutes from now as schedule time 88ms

And I click on "Confirm" 1s 13ms

Then I should see a "1 package install has been scheduled for" text 66ms

And I wait until the package "orion-dummy-1.1-1.1" has been cached on this "sle_minion" 1m 13s 471ms

And I wait for "orion-dummy-1.1-1.1" to be installed on "sle_minion" 1m 46s 717ms

Scenario:
Install patch in the future and check for staging
3m 350ms 11

When I follow "Software" in the content area 63ms

And I follow "Patches" in the content area 65ms

And I enter "virgo" as the filtered synopsis 39ms

And I click on the filter button 10s 118ms

And I check "virgo-dummy-3456" in the list 66ms

And I click on "Apply Patches" 605ms

And I pick 3 minutes from now as schedule time 103ms

And I click on "Confirm" 963ms

Then I should see a "1 patch update has been scheduled for" text 75ms

And I wait until the package "virgo-dummy-2.0-1.1.noarch" has been cached on this "sle_minion" 1m 21s 50ms

And I wait for "virgo-dummy-2.0-1.1" to be installed on "sle_minion" 1m 27s 198ms

Scenario:
Cleanup: remove virgo-dummy package from SLES minion
4s 29ms 11

When I follow "Software" in the content area 73ms

And I follow "List / Remove" 725ms

And I enter "orion-dummy" as the filtered package name 159ms

And I click on the filter button 857ms

And I check row with "orion-dummy" and arch of "sle_minion" 64ms

And I enter "virgo-dummy" as the filtered package name 43ms

And I click on the filter button 131ms

And I check "virgo-dummy" in the list 63ms

And I click on "Remove Packages" 606ms

And I click on "Confirm" 687ms

And I disable repository "test_repo_rpm_pool" on this "sle_minion" 616ms

@skip_if_github_validation @scope_salt
Feature:Salt package states 2m 30s 32ms 15

Scenario:
Pre-requisite: install old packages on SLES minion
20s 722ms 6

Salt command: salt uyuni-master-suse-minion.sumaci.aws state.highstate

When I apply highstate on "sle_minion" 11s 619ms

And I enable repository "test_repo_rpm_pool" on this "sle_minion" 898ms

And I refresh the metadata for "sle_minion" 1s 1ms

And I install old package "milkyway-dummy-1.0" on this "sle_minion" without error control 2s 951ms

And I install old package "virgo-dummy-1.0" on this "sle_minion" without error control 2s 215ms

And I install old package "andromeda-dummy-1.0" on this "sle_minion" without error control 2s 37ms

Scenario:
Pre-requisite: refresh package list and check installed packages on SLE minion
26s 991ms 3

When I refresh packages list via spacecmd on "sle_minion" 8s 68ms

And I wait until refresh package list on "sle_minion" is finished 12s 652ms

Then spacecmd should show packages "milkyway-dummy-1.0 virgo-dummy-1.0 andromeda-dummy-1.0" installed on "sle_minion" 6s 270ms

Scenario:
Log in as admin user
997ms 1

Given I am authorized for the "Admin" section 997ms

Scenario:
Pre-requisite: ensure the errata cache is computed before software states tests
8s 621ms 11

Given I am on the Systems overview page of this "sle_minion" 1s 307ms

When I follow "Software" in the content area 71ms

And I follow "List / Remove" in the content area 65ms

And I enter "andromeda-dummy" as the filtered package name 224ms

And I click on the filter button until page does contain "andromeda-dummy-1.0" text 295ms

When I follow the left menu "Admin > Task Schedules" 142ms

And I follow "errata-cache-default" 1s 227ms

And I follow "errata-cache-bunch" 1s 382ms

Then I click on "Single Run Schedule" 1s 558ms

And I should see a "bunch was scheduled" text 298ms

Then I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 2s 48ms

Scenario:
Accepted minion has a base channel
1s 164ms 4

Given I am on the Systems overview page of this "sle_minion" 956ms

When I follow "Software" in the content area 67ms

And I follow "Software Channels" in the content area 66ms

Then the system should have a base channel set 74ms

Scenario:
Remove a package through the UI
12s 470ms 13

When I follow "States" in the content area 64ms

And I follow "Packages" 488ms

And I follow "Search" 64ms

And I should see a "Package States" text 70ms

And I list packages with "dummy" 1s 153ms

And I wait until I see "milkyway-dummy" text 479ms

Then "milkyway-dummy" should be installed on "sle_minion" 805ms

And I change the state of "milkyway-dummy" to "Removed" and "" 59ms

Then I should see a "1 Change" text 89ms

And I click save 50ms

Then I wait until I see "Package states have been saved." text 205ms

And I click apply 47ms

And I wait for "milkyway-dummy" to be uninstalled on "sle_minion" 8s 889ms

Scenario:
Install a package through the UI
17s 451ms 13

When I follow "States" in the content area 64ms

And I follow "Packages" 547ms

And I follow "Search" 62ms

And I should see a "Package States" text 69ms

And I list packages with "dummy" 1s 130ms

And I wait until I see "milkyway-dummy" text 491ms

Then "milkyway-dummy" should not be installed on "sle_minion" 535ms

And I change the state of "milkyway-dummy" to "Installed" and "" 44ms

Then I should see a "1 Change" text 93ms

And I click save 42ms

Then I wait until I see "Package states have been saved." text 339ms

And I click apply 39ms

And I wait for "milkyway-dummy" to be installed on "sle_minion" 13s 991ms

Scenario:
Install an already installed package through the UI
4s 984ms 13

When I follow "States" in the content area 64ms

And I follow "Packages" 556ms

And I follow "Search" 57ms

And I should see a "Package States" text 74ms

And I list packages with "dummy" 1s 131ms

And I wait until I see "virgo-dummy" text 501ms

Then "virgo-dummy-1.0" should be installed on "sle_minion" 696ms

And I change the state of "virgo-dummy" to "Installed" and "Any" 105ms

Then I should see a "1 Change" text 109ms

And I click save 51ms

Then I wait until I see "Package states have been saved." text 362ms

And I click apply 47ms

And I wait for "virgo-dummy-1.0" to be installed on "sle_minion" 1s 226ms

Scenario:
Upgrade a package through the UI
19s 940ms 13

When I follow "States" in the content area 74ms

And I follow "Packages" 487ms

And I follow "Search" 64ms

And I should see a "Package States" text 77ms

And I list packages with "dummy" 1s 147ms

And I wait until I see "andromeda-dummy" text 492ms

Then "andromeda-dummy-1.0" should be installed on "sle_minion" 615ms

And I change the state of "andromeda-dummy" to "Installed" and "Latest" 88ms

Then I should see a "1 Change" text 102ms

And I click save 50ms

Then I wait until I see "Package states have been saved." text 236ms

And I click apply 46ms

And I wait for "andromeda-dummy-2.0-1.1" to be installed on "sle_minion" 16s 454ms

Scenario:
Verify the package states
1s 9ms 6

When I follow "States" in the content area 75ms

And I follow "Packages" 504ms

And I should see a "Package States" text 67ms

And I should see a "milkyway-dummy" text 194ms

And I should see a "andromeda-dummy" text 82ms

And I should see a "virgo-dummy" text 84ms

Scenario:
Use Salt presence mechanism on an active minion
6s 528ms 5

When I follow "States" in the content area 58ms

And I follow "Highstate" in the content area 65ms

And I click on "Show full highstate output" 356ms

And I wait for "6" seconds 6s

And I should see a "pkg_removed" or "running as PID" text in element "highstate" 46ms

Scenario:
Use Salt presence mechanism on an unreachable minion
16s 295ms 6

When I follow "States" in the content area 61ms

And I run "pkill salt-minion" on "sle_minion" without error control 447ms

And I run "pkill python.original" on "sle_minion" without error control 435ms

And I follow "Highstate" in the content area 57ms

And I click on "Show full highstate output" 195ms

And I wait until I see "No reply from minion" text 15s 99ms

Scenario:
Cleanup: restart the salt service on SLES minion
1s 86ms 1

When I restart salt-minion on "sle_minion" 1s 86ms

Scenario:
Cleanup: set the package states as unmanaged
4s 667ms 11

Given I am on the Systems overview page of this "sle_minion" 1s 203ms

When I follow "States" in the content area 80ms

And I follow "Packages" 1s 223ms

And I follow "Search" 64ms

And I should see a "Package States" text 73ms

And I list packages with "dummy" 1s 149ms

And I wait until I see "andromeda-dummy" text 487ms

And I change the state of "virgo-dummy" to "Unmanaged" and "" 63ms

And I change the state of "andromeda-dummy" to "Unmanaged" and "" 46ms

And I click save 51ms

Then I wait until I see "Package states have been saved." text 223ms

Scenario:
Cleanup: remove old packages from SLES minion
7s 98ms 5

When I disable repository "test_repo_rpm_pool" on this "sle_minion" 509ms

And I remove package "milkyway-dummy" from this "sle_minion" without error control 1s 839ms

And I remove package "virgo-dummy" from this "sle_minion" without error control 1s 877ms

And I remove package "andromeda-dummy" from this "sle_minion" without error control 1s 829ms

And I refresh the metadata for "sle_minion" 1s 42ms

@skip_if_github_validation @sle_minion @scope_salt
Feature:Verify that Salt mgrcompat state works when the new module.run syntax is enabled 13m 54s 31ms 10

Scenario:
Log in as org admin user
1s 760ms 1

Given I am authorized 1s 760ms

Scenario:
Remove mgrcompat module from minion synced modules and schedule Hardware Refresh
28s 674ms 8

Given I remove "minion/extmods/states/mgrcompat.py" from salt cache on "sle_minion" 798ms

And I remove "minion/extmods/states/__pycache__/mgrcompat*" from salt cache on "sle_minion" 449ms

And I am on the Systems overview page of this "sle_minion" 957ms

When I follow "Hardware" 588ms

And I click on "Schedule Hardware Refresh" 880ms

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 448ms

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "sle_minion" 2s 433ms

Scenario:
Remove saltutil grain and mgrcompat module from minion and schedule Hardware Refresh
30s 700ms 10

Given I remove "minion/extmods/states/mgrcompat.py" from salt cache on "sle_minion" 433ms

And I remove "minion/extmods/states/__pycache__/mgrcompat*" from salt cache on "sle_minion" 444ms

And I store "grains: {__suse_reserved_saltutil_states_support: False}" into file "custom_grains.conf" in salt minion config directory on "sle_minion" 439ms

And I refresh salt-minion grains on "sle_minion" 2s 105ms

And I am on the Systems overview page of this "sle_minion" 1s 66ms

When I follow "Hardware" 587ms

And I click on "Schedule Hardware Refresh" 784ms

Then I should see a "You have successfully scheduled a hardware profile refresh" text 126ms

When I wait until event "Hardware List Refresh scheduled" is completed 22s 356ms

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "sle_minion" 2s 355ms

Scenario:
Delete SLES minion system profile before mgrcompat test
4m 6s 433ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 11ms

When I follow "Delete System" 477ms

Then I should see a "Confirm System Profile Deletion" text 66ms

When I click on "Delete Profile" 62ms

And I wait until I see "has been deleted" text 4m 3s 644ms

And I wait until Salt client is inactive on "sle_minion" 792ms

Then "sle_minion" should not be registered 378ms

Scenario:
Enable new module.run syntax on the minion and perform registration
1m 49s 368ms 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" 426ms

When I follow the left menu "Systems > Bootstrapping" 79ms

Then I should see a "Bootstrap Minions" text 63ms

When I enter the hostname of "sle_minion" as "hostname" 144ms

And I enter "22" as "port" 53ms

And I enter "root" as "user" 62ms

And I enter "linux" as "password" 95ms

And I select the hostname of "proxy" from "proxies" if present 77ms

And I click on "Bootstrap" 62ms

And I wait until I see "Bootstrap process initiated." text 25s 988ms

And I wait until onboarding is completed for "sle_minion" 1m 22s 315ms

Scenario:
Check if onboarding for the minion with the new module.run syntax was successful
8s 833ms 3

When I follow the left menu "Systems > System List > All" 136ms

And I wait until I see the name of "sle_minion", refreshing the page 650ms

And I wait until onboarding is completed for "sle_minion" 8s 46ms

Scenario:
Check that installed packages are visible with the new module.run syntax
1s 962ms 4

Given I am on the Systems overview page of this "sle_minion" 1s 34ms

When I follow "Software" in the content area 72ms

And I follow "List / Remove" 728ms

Then I should see a "aaa_base" text 127ms

Scenario:
Check that Hardware Refresh button works on a SLE minion with new module.run syntax
28s 201ms 6

Given I am on the Systems overview page of this "sle_minion" 1s 838ms

And I follow "Hardware" 728ms

And I click on "Schedule Hardware Refresh" 833ms

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 22s 231ms

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "sle_minion" 2s 445ms

Scenario:
Cleanup: Delete profile of the minion and disable new module.run syntax
4m 7s 674ms 9

Given I am on the Systems overview page of this "sle_minion" 1s 156ms

And I remove "custom_modulerun.conf" from salt minion config directory on "sle_minion" 468ms

And I remove "custom_grains.conf" from salt minion config directory on "sle_minion" 418ms

When I follow "Delete System" 459ms

Then I should see a "Confirm System Profile Deletion" text 67ms

When I click on "Delete Profile" 63ms

And I wait until I see "has been deleted" text 4m 3s 861ms

And I wait until Salt client is inactive on "sle_minion" 808ms

Then "sle_minion" should not be registered 370ms

Scenario:
Cleanup: bootstrap again the minion after mgrcompat tests
2m 10s 424ms 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 711ms

And I follow the left menu "Systems > Bootstrapping" 80ms

Then I should see a "Bootstrap Minions" text 64ms

When I enter the hostname of "sle_minion" as "hostname" 144ms

And I enter "22" as "port" 57ms

And I enter "root" as "user" 57ms

And I enter "linux" as "password" 63ms

And I select "1-SUSE-KEY-x86_64" from "activationKeys" 72ms

And I select the hostname of "proxy" from "proxies" if present 59ms

And I click on "Bootstrap" 62ms

And I wait until I see "Bootstrap process initiated." text 40s 100ms

And I wait until onboarding is completed for "sle_minion" 1m 22s 951ms

@skip_if_github_validation @sle_minion @scope_salt @flaky
Feature:Lock packages on SLES salt minion 3m 42s 961ms 10

* Related GitHub Card: https://github.com/SUSE/spacewalk/issues/20168

Scenario:
Log in as org admin user
2s 123ms 1

Given I am authorized 2s 123ms

Scenario:
Pre-requisite: install packages needed for locking test
5s 129ms 3

When I install package "orion-dummy" on this "sle_minion" 2s 271ms

And I install package "milkyway-dummy" on this "sle_minion" 1s 908ms

And I remove package "hoag-dummy" from this "sle_minion" without error control 949ms

Scenario:
Lock a package on the client
27s 649ms 13

Given I am on the Systems overview page of this "sle_minion" 1s 101ms

When I follow "Software" in the content area 75ms

And I follow "Lock / Unlock" 598ms

And I enter "hoag-dummy-1.1-1.1" as the filtered package name 55ms

And I click on the filter button 773ms

And I check row with "hoag-dummy-1.1-1.1" and arch of "sle_minion" 62ms

And I click on "Lock" 949ms

Then I should see a "Packages has been requested for being locked." text 84ms

When I wait until event "Lock packages scheduled" is completed 22s 104ms

Then "hoag-dummy-1.1-1.1" is locked on "sle_minion" 1s 76ms

When I follow "Software" in the content area 76ms

And I follow "Lock / Unlock" 662ms

Then package "hoag-dummy-1.1-1.1" is reported as locked 28ms

Scenario:
Attempt to install a locked package on the client
28s 239ms 17

Given I am on the Systems overview page of this "sle_minion" 1s 87ms

When I follow "Software" in the content area 60ms

And I follow "Lock / Unlock" 499ms

And package "hoag-dummy-1.1-1.1" is reported as locked 22ms

And I follow "Install" 603ms

And I enter "hoag-dummy-1.1-1.1" as the filtered package name 64ms

And I click on the filter button 632ms

And I check row with "hoag-dummy-1.1-1.1" and arch of "sle_minion" 63ms

And I click on "Install Packages" 592ms

And I click on "Confirm" 671ms

Then I should see a "1 package install has been scheduled for" text 61ms

When I follow "Events" 371ms

And I follow "History" 461ms

And I wait until I see the event "Package Install/Upgrade scheduled" completed during last minute, refreshing the page 22s 898ms

And I follow the event "Package Install/Upgrade scheduled" completed during last minute 61ms

Then the package scheduled is "hoag-dummy-1.1-1.1" 16ms

And the action status is "Failed" 69ms

Scenario:
Unlock a package on the client
34s 122ms 16

Given I am on the Systems overview page of this "sle_minion" 1s 4ms

When I follow "Software" in the content area 62ms

And I follow "Lock / Unlock" 574ms

And package "hoag-dummy-1.1-1.1" is reported as locked 21ms

And I enter "hoag-dummy-1.1-1.1" as the filtered package name 51ms

And I click on the filter button 622ms

And I check row with "hoag-dummy-1.1-1.1" and arch of "sle_minion" 16ms

And I click on "Unlock" 609ms

Then I should see a "Packages has been requested for being unlocked." text 79ms

When I wait until event "Lock packages scheduled" is completed 18s 668ms

Then "hoag-dummy-1.1-1.1" is unlocked on "sle_minion" 1s 109ms

When I follow "Software" in the content area 71ms

And I follow "Lock / Unlock" 511ms

And I enter "hoag-dummy-1.1-1.1" as the filtered package name 70ms

And I click on the filter button 623ms

Then package "hoag-dummy-1.1-1.1" is reported as unlocked 10s 24ms

Scenario:
Schedule a package lock
3s 251ms 9

Given I am on the Systems overview page of this "sle_minion" 1s 241ms

When I follow "Software" in the content area 61ms

And I follow "Lock / Unlock" 514ms

And I enter "hoag-dummy-1.1-1.1" as the filtered package name 61ms

And I click on the filter button 619ms

And I check row with "hoag-dummy-1.1-1.1" and arch of "sle_minion" 64ms

And I click on "Lock" 590ms

Then I should see a "Packages has been requested for being locked." text 85ms

And package "hoag-dummy-1.1-1.1" is reported as pending to be locked 11ms

Scenario:
Schedule another package lock
25s 157ms 16

Given I am on the Systems overview page of this "sle_minion" 1s 17ms

When I follow "Software" in the content area 63ms

And I follow "Lock / Unlock" 503ms

And I enter "milkyway-dummy-2.0-1.1" as the filtered package name 59ms

And I click on the filter button 648ms

When I check row with "milkyway-dummy-2.0-1.1" and arch of "sle_minion" 60ms

And I click on "Lock" 1s 293ms

Then I should see a "Packages has been requested for being locked." text 81ms

And package "milkyway-dummy-2.0-1.1" is reported as pending to be locked 10ms

When I wait until event "Lock packages scheduled" is completed 18s 825ms

Then "hoag-dummy-1.1-1.1" is locked on "sle_minion" 1s 126ms

And "milkyway-dummy-2.0-1.1" is locked on "sle_minion" 800ms

When I follow "Software" in the content area 72ms

And I follow "Lock / Unlock" 531ms

Then package "hoag-dummy-1.1-1.1" is reported as locked 28ms

And package "milkyway-dummy-2.0-1.1" is reported as locked 33ms

Scenario:
Mix package locks and unlock events
44s 388ms 32

Given I am on the Systems overview page of this "sle_minion" 1s 12ms

When I follow "Software" in the content area 63ms

And I follow "Lock / Unlock" 644ms

And package "hoag-dummy-1.1-1.1" is reported as locked 21ms

And package "milkyway-dummy-2.0-1.1" is reported as locked 28ms

And I enter "orion-dummy-1.1-1.1" as the filtered package name 65ms

And I click on the filter button 651ms

When I check row with "orion-dummy-1.1-1.1" and arch of "sle_minion" 64ms

And I click on "Lock" 613ms

Then I should see a "Packages has been requested for being locked." text 82ms

And package "orion-dummy-1.1-1.1" is reported as pending to be locked 10ms

When I follow "Lock / Unlock" 529ms

And I enter "hoag-dummy-1.1-1.1" as the filtered package name 62ms

And I click on the filter button 643ms

And I uncheck row with "hoag-dummy-1.1-1.1" and arch of "sle_minion" 59ms

And I enter "milkyway-dummy-2.0-1.1" as the filtered package name 55ms

And I click on the filter button 128ms

And I check row with "milkyway-dummy-2.0-1.1" and arch of "sle_minion" 21ms

And I click on "Unlock" 1s 744ms

Then I should see a "Packages has been requested for being unlocked." text 82ms

And package "milkyway-dummy-2.0-1.1" is reported as pending to be unlocked 10ms

When I wait until event "Lock packages scheduled" is completed 23s 313ms

Then "hoag-dummy-1.1-1.1" is locked on "sle_minion" 1s 197ms

And "milkyway-dummy-2.0-1.1" is unlocked on "sle_minion" 901ms

And "orion-dummy-1.1-1.1" is locked on "sle_minion" 810ms

When I follow "Software" in the content area 71ms

And I follow "Lock / Unlock" 747ms

Then package "hoag-dummy-1.1-1.1" is reported as locked 27ms

And package "orion-dummy-1.1-1.1" is reported as locked 30ms

And I enter "milkyway-dummy-2.0-1.1" as the filtered package name 61ms

And I click on the filter button 610ms

And package "milkyway-dummy-2.0-1.1" is reported as unlocked 10s 19ms

Scenario:
Mix package locks and unlock events part 2
48s 852ms 18

Given I am on the Systems overview page of this "sle_minion" 1s 126ms

And I follow "Software" in the content area 63ms

And I follow "Lock / Unlock" 579ms

When I click on "Select All" 617ms

And I click on "Unlock" 825ms

Then I should see a "Packages has been requested for being unlocked." text 115ms

And only packages "hoag-dummy-1.1-1.1, orion-dummy-1.1-1.1" are reported as pending to be unlocked 36ms

When I wait until event "Lock packages scheduled" is completed 22s 93ms

Then "hoag-dummy-1.1-1.1" is unlocked on "sle_minion" 1s 105ms

And "orion-dummy-1.1-1.1" is unlocked on "sle_minion" 783ms

When I follow "Software" in the content area 76ms

And I follow "Lock / Unlock" 515ms

And I enter "hoag-dummy-1.1-1.1" as the filtered package name 63ms

And I click on the filter button 634ms

Then package "hoag-dummy-1.1-1.1" is reported as unlocked 10s 14ms

And I enter "orion-dummy-1.1-1.1" as the filtered package name 54ms

And I click on the filter button 127ms

And package "orion-dummy-1.1-1.1" is reported as unlocked 10s 18ms

Scenario:
Cleanup: remove packages after testing locks
4s 47ms 2

Then I remove package "orion-dummy" from this "sle_minion" 2s 223ms

And I remove package "milkyway-dummy" from this "sle_minion" 1s 823ms

@scope_onboarding
Feature:Empty minion profile operations 58s 525ms 8

Scenario:
Log in as org admin user
2s 389ms 1

Given I am authorized 2s 389ms

Scenario:
Create an empty minion profile with HW address via API
2s 787ms 1

When I call system.create_system_profile() with name "empty-profile" and HW address "00:11:22:33:44:55" 2s 787ms

Scenario:
Create an empty minion profile with hostname via API
915ms 1

When I call system.create_system_profile() with name "empty-profile-hostname" and hostname "min-retail.mgr.suse.de" 915ms

Scenario:
Check the created empty minion profiles in Unprovisioned Systems page
454ms 4

And I follow the left menu "System > System List > Unprovisioned Systems" 204ms

And I wait until I see "empty-profile" text, refreshing the page 92ms

And I wait until I see "00:11:22:33:44:55" text 78ms

And I wait until I see "empty-profile-hostname" text 78ms

Scenario:
Check the empty profiles has the hostname set
758ms 3

And I follow the left menu "System > System List > Unprovisioned Systems" 70ms

And I follow "empty-profile-hostname" 615ms

Then I wait until I see "min-retail.mgr.suse.de" text, refreshing the page 72ms

Scenario:
Check the empty minion profiles visible via API
442ms 3

When I call system.list_empty_system_profiles() 442ms

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
46s 844ms 7

When I follow the left menu "Systems > System List" 70ms

And I wait until I see the "empty-profile" system, refreshing the page 44s 456ms

And I follow "empty-profile" 703ms

And I follow "Delete System" 491ms

Then I should see a "Confirm System Profile Deletion" text 64ms

When I click on "Delete Profile" 61ms

And I wait until I see "has been deleted" text 996ms

Scenario:
Cleanup: Delete second empty minion profiles
3s 934ms 7

When I follow the left menu "Systems > System List" 83ms

And I wait until I see the "empty-profile-hostname" system, refreshing the page 728ms

And I follow "empty-profile-hostname" 566ms

And I follow "Delete System" 409ms

Then I should see a "Confirm System Profile Deletion" text 59ms

When I click on "Delete Profile" 54ms

And I wait until I see "has been deleted" text 2s 31ms

@scope_onboarding @custom_download_endpoint
Feature:Repos file generation based on custom pillar data 2m 7s 936ms 9 3

Scenario:
Log in as org admin user
1s 705ms 1

Given I am authorized 1s 705ms

@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
33s 14ms 11

Warning: Radio button 'openSUSE Tumbleweed (x86_64)' is already checked

Given I am on the Systems overview page of this "sle_minion" 1s 651ms

When I follow "Software" in the content area 84ms

And I follow "Software Channels" in the content area 64ms

And I wait until I do not see "Loading..." text 77ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 186ms

And I click on "Next" 340ms

Then I should see a "Confirm Software Channel Change" text 84ms

When I click on "Confirm" 73ms

Then I should see a "Changing the channels has been scheduled." text 415ms

When I follow "scheduled" in the content area 77ms

And I wait until I see "1 system successfully completed this action." text, refreshing the page 29s 959ms

Scenario:
Check the default RPM download point values
2s 557ms 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 178ms

Then the susemanager repo file should exist on the "sle_minion" 886ms

And the repo file should contain the normal download endpoint on the "sle_minion" 492ms

Scenario:
Set the custom RPM download point
13s 479ms 5

Given I am on the Systems overview page of this "sle_minion" 1s 20ms

When I install a salt pillar top file for "pkg_endpoint" with target "*" on the server 4s 601ms

And I wait for "1" seconds 1s

And I install the package download endpoint pillar file on the server 2s 538ms

And I refresh the pillar data 4s 319ms

@susemanager
Scenario:
Select the channels of the SLES minion again so new RPM end point will be taken into account
< 1ms 10

When I follow "Software" in the content area 0s

And I follow "Software Channels" in the content area 0s

And I wait until I do not see "Loading..." text 0s

And I wait until I see "SLE-Module-Basesystem15-SP7-Pool for x86_64" text 0s

And I click on "Next" 0s

Then I should see a "Confirm Software Channel Change" text 0s

When I click on "Confirm" 0s

Then I should see a "Changing the channels has been scheduled." text 0s

When I follow "scheduled" in the content area 0s

And I wait until I see "1 system successfully completed this action." text, refreshing the page 0s

@uyuni
Scenario:
Select the channels of the openSUSE minion again so new RPM end point will be taken into account
31s 299ms 10

Warning: Radio button 'openSUSE Tumbleweed (x86_64)' is already checked

When I follow "Software" in the content area 81ms

And I follow "Software Channels" in the content area 63ms

And I wait until I do not see "Loading..." text 70ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 207ms

And I click on "Next" 349ms

Then I should see a "Confirm Software Channel Change" text 65ms

When I click on "Confirm" 75ms

Then I should see a "Changing the channels has been scheduled." text 447ms

When I follow "scheduled" in the content area 72ms

And I wait until I see "1 system successfully completed this action." text, refreshing the page 29s 865ms

Scenario:
Check the channel.repo file to see the custom RPM download point
2s 493ms 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 156ms

Then the susemanager repo file should exist on the "sle_minion" 859ms

And the repo file should contain the custom download endpoint on the "sle_minion" 477ms

Scenario:
Cleanup: remove the custom RPM download point
10s 725ms 3

When I delete the package download endpoint pillar file from the server 3s 216ms

And I install a salt pillar top file for "disable_local_repos_off, salt_bundle_config" with target "*" on the server 3s 572ms

And I refresh the pillar data 3s 935ms

@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 442ms 12

Warning: Radio button 'openSUSE Tumbleweed (x86_64)' is already checked

When I follow "Software" in the content area 81ms

And I follow "Software Channels" in the content area 65ms

And I wait until I do not see "Loading..." text 72ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 232ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 349ms

And I check "Fake-RPM-SUSE-Channel" 37ms

And I click on "Next" 60ms

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 562ms

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 761ms

Scenario:
Cleanup: recheck the default RPM download point values
1s 218ms 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" 784ms

And the repo file should contain the normal download endpoint on the "sle_minion" 434ms

@skip_if_github_validation @sle_minion @scope_action_chains @flaky
Feature:Action chains on Salt minions 9m 26s 5ms 33

* Related GitHub Card: https://github.com/SUSE/spacewalk/issues/28793

Scenario:
Log in as admin user
1s 931ms 1

Given I am authorized for the "Admin" section 1s 931ms

Scenario:
Pre-requisite: downgrade repositories to lower version on Salt minion
7s 700ms 6

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 798ms

And I remove package "andromeda-dummy" from this "sle_minion" without error control 869ms

And I remove package "virgo-dummy" from this "sle_minion" without error control 931ms

And I install package "milkyway-dummy" on this "sle_minion" without error control 1s 999ms

And I install old package "andromeda-dummy-1.0" on this "sle_minion" 1s 971ms

And I refresh the metadata for "sle_minion" 1s 131ms

Scenario:
Pre-requisite: refresh package list and check installed packages after downgrade on SLE minion
27s 629ms 3

When I refresh packages list via spacecmd on "sle_minion" 6s 851ms

And I wait until refresh package list on "sle_minion" is finished 12s 952ms

Then spacecmd should show packages "milkyway-dummy andromeda-dummy-1.0" installed on "sle_minion" 7s 824ms

Scenario:
Pre-requisite: wait until downgrade is finished on SLE minion
1s 721ms 5

Given I am on the Systems overview page of this "sle_minion" 1s 87ms

When I follow "Software" in the content area 76ms

And I follow "List / Remove" in the content area 65ms

And I enter "andromeda-dummy" as the filtered package name 197ms

And I click on the filter button until page does contain "andromeda-dummy-1.0" text 294ms

Scenario:
Pre-requisite: ensure the errata cache is computed before testing on Salt minion
33s 39ms 6

When I follow the left menu "Admin > Task Schedules" 144ms

And I follow "errata-cache-default" 1s 256ms

And I follow "errata-cache-bunch" 1s 325ms

And I click on "Single Run Schedule" 1s 288ms

Then I should see a "bunch was scheduled" text 282ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 28s 741ms

Scenario:
Create a custom action chain for the Salt minion
597ms 3

When I create an action chain with label "salt_minion_action_chain" via API 385ms

And I follow the left menu "Schedule > Action Chains" 145ms

Then I should see a "salt_minion_action_chain" text 66ms

Scenario:
Add a patch installation to the action chain on Salt minion
23s 86ms 10

Given I am on the Systems overview page of this "sle_minion" 1s 99ms

When I follow "Software" in the content area 70ms

And I follow "Patches" in the content area 66ms

And I enter "andromeda" as the filtered synopsis 51ms

And I click on the filter button 10s 162ms

And I check "andromeda-dummy-6789" in the list 60ms

And I click on "Apply Patches" 645ms

And I check radio button "schedule-by-action-chain" 10s 77ms

And I click on "Confirm" 766ms

Then I should see a "Action has been successfully added to the Action Chain" text 87ms

Scenario:
Add a package removal to the action chain on Salt minion
14s 293ms 10

Given I am on the Systems overview page of this "sle_minion" 1s 10ms

When I follow "Software" in the content area 79ms

And I follow "List / Remove" in the content area 67ms

And I enter "milkyway-dummy" as the filtered package name 197ms

And I click on the filter button 1s 189ms

And I check row with "milkyway-dummy" and arch of "sle_minion" 59ms

And I click on "Remove Packages" 618ms

And I check radio button "schedule-by-action-chain" 10s 56ms

And I click on "Confirm" 952ms

Then I should see a "Action has been successfully added to the Action Chain" text 64ms

Scenario:
Add a package installation to an action chain on Salt minion
12s 580ms 9

When I follow "Software" in the content area 69ms

And I follow "Install New Packages" in the content area 73ms

And I enter "virgo-dummy" as the filtered package name 110ms

And I click on the filter button 746ms

And I check "virgo-dummy" in the list 56ms

And I click on "Install Packages" 608ms

And I check radio button "schedule-by-action-chain" 10s 71ms

And I click on "Confirm" 781ms

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 Salt minion
1s 247ms 7

When I follow the left menu "Configuration > Channels" 119ms

And I follow "Create Config Channel" 270ms

And I enter "Action Chain Channel" as "cofName" 68ms

And I enter "actionchainchannel" as "cofLabel" 62ms

And I enter "This is a test channel" as "cofDescription" 65ms

And I click on "Create Config Channel" 596ms

Then I should see a "Action Chain Channel" text 64ms

Scenario:
Add a configuration file to configuration channel for testing action chain on Salt minion
1s 48ms 8

When I follow the left menu "Configuration > Channels" 64ms

And I follow "Action Chain Channel" 361ms

And I follow "Create Configuration File or Directory" 351ms

And I enter "/etc/action-chain.cnf" as "cffPath" 71ms

And I enter "Testchain=YES_PLEASE" in the editor 8ms

And I click on "Create Configuration File" 67ms

Then I should see a "Revision 1 of /etc/action-chain.cnf from channel Action Chain Channel" text 105ms

And I should see a "Update Configuration File" button 18ms

Scenario:
Download the configuration file from configuration channel
1s 909ms 7

When I follow the left menu "Configuration > Channels" 62ms

And I follow "Action Chain Channel" 424ms

And I follow "List/Remove Files" 319ms

And I follow "/etc/action-chain.cnf" 420ms

And I follow "Download File" 181ms

And I wait until file "/tmp/downloads/action-chain.cnf" exists on "localhost" 175ms

Then file "/tmp/downloads/action-chain.cnf" should contain "Testchain=YES_PLEASE" on "localhost" 325ms

Scenario:
Subscribe system to configuration channel for testing action chain on Salt minion
2s 653ms 8

Given I am on the Systems overview page of this "sle_minion" 916ms

When I follow "Configuration" in the content area 72ms

And I follow "Manage Configuration Channels" in the content area 66ms

And I follow first "Subscribe to Channels" in the content area 74ms

And I check "Action Chain Channel" in the list 56ms

And I click on "Continue" 617ms

And I click on "Update Channel Rankings" 769ms

Then I should see a "Channel Subscriptions successfully changed for" text 79ms

Scenario:
Add a configuration file deployment to the action chain on Salt minion
13s 1ms 9

When I follow the left menu "Configuration > Channels" 108ms

And I follow "Action Chain Channel" 437ms

And I follow "Deploy Files" in the content area 65ms

And I click on "Deploy All Files" 665ms

And I check the "sle_minion" client 58ms

And I click on "Confirm & Deploy to Selected Systems" 808ms

And I check radio button "schedule-by-action-chain" 10s 69ms

And I click on "Deploy Files to Selected Systems" 712ms

Then I should see a "Action has been successfully added to the Action Chain" text 75ms

Scenario:
Add apply highstate to action chain on Salt minion
11s 489ms 4

Given I am on the Systems overview page of this "sle_minion" 1s 282ms

When I follow "States" in the content area 68ms

And I check radio button "schedule-by-action-chain" 10s 78ms

And I click on "Apply Highstate" 60ms

Scenario:
Add a reboot action to the action chain on Salt minion
12s 366ms 5

Given I am on the Systems overview page of this "sle_minion" 964ms

When I follow first "Schedule System Reboot" 486ms

And I check radio button "schedule-by-action-chain" 10s 54ms

And I click on "Reboot system" 762ms

Then I should see a "Action has been successfully added to the Action Chain" text 97ms

Scenario:
Add a remote command to the action chain on Salt minion
10s 423ms 6

When I follow "Details" in the content area 74ms

And 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 70ms

And I check radio button "schedule-by-action-chain" 10s 71ms

And I click on "Schedule" 57ms

Then I should see a "Action has been successfully added to the Action Chain" text 83ms

Scenario:
Verify the action chain list on Salt minion
1s 748ms 10

When I follow "Schedule" 347ms

And I follow "Action Chains" 266ms

And I follow "salt_minion_action_chain" 523ms

Then I should see a "1. Apply patch(es) andromeda-dummy-6789 on 1 system" text 100ms

And I should see a "2. Remove milkyway-dummy from 1 system" text 89ms

And I should see a "3. Install or update virgo-dummy on 1 system" text 86ms

And I should see a text like "4. Deploy.*/etc/action-chain.cnf.*to 1 system" 80ms

And I should see a "5. Apply Highstate" text 82ms

And I should see a "6. Reboot 1 system" text 86ms

And I should see a "7. Run a remote command on 1 system" text 83ms

Scenario:
Check that a different user cannot see the action chain for Salt minion
3s 514ms 4

Given I am authorized as "testing" with password "testing" 2s 200ms

When I follow "Schedule" 985ms

And I follow "Action Chains" 320ms

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 35s 572ms 9

Given I am authorized for the "Admin" section 1s 786ms

When I am on the Systems overview page of this "sle_minion" 1s 740ms

And I follow "Schedule" 280ms

And I follow "Action Chains" 264ms

And I follow "salt_minion_action_chain" 303ms

And I click on "Save and Schedule" 84ms

Then I should see a "Action Chain salt_minion_action_chain has been scheduled for execution." text 830ms

When I wait for "virgo-dummy" to be installed on "sle_minion" 27s 427ms

And I wait at most 300 seconds until file "/tmp/action_chain_one_system_done" exists on "sle_minion" 4m 2s 854ms

Scenario:
Create a custom action chain for the Salt minion
606ms 3

When I create an action chain with label "salt_minion_action_chain_to_delete" via API 464ms

And I follow the left menu "Schedule > Action Chains" 75ms

Then I should see a "salt_minion_action_chain_to_delete" text 66ms

Scenario:
Add a remote command to the action chain on Salt minion
12s 190ms 6

Given I am on the Systems overview page of this "sle_minion" 983ms

When I follow "Remote Command" 509ms

And I enter as remote command this script in #!/bin/bash uptime 55ms

And I check radio button "schedule-by-action-chain" 10s 67ms

And I click on "Schedule" 492ms

Then I should see a "Action has been successfully added to the Action Chain" text 82ms

Scenario:
Delete the action chain for Salt minion
1s 376ms 5

When I follow "Schedule" 272ms

And I follow "Action Chains" 293ms

And I follow "salt_minion_action_chain_to_delete" 316ms

And I follow "Delete Action Chains" in the content area 81ms

And I click on "Delete" 412ms

Scenario:
Downgrade again repositories to lower version on Salt minion
8s 643ms 4

When I remove package "andromeda-dummy" from this "sle_minion" without error control 2s 734ms

And I remove package "virgo-dummy" from this "sle_minion" without error control 1s 810ms

And I install package "milkyway-dummy" on this "sle_minion" without error control 2s 11ms

And I install old package "andromeda-dummy-1.0" on this "sle_minion" 2s 86ms

Scenario:
Refresh package list and check installed packages after second downgrade on SLE minion
26s 437ms 3

When I refresh packages list via spacecmd on "sle_minion" 6s 471ms

And I wait until refresh package list on "sle_minion" is finished 12s 289ms

Then spacecmd should show packages "milkyway-dummy andromeda-dummy-1.0" installed on "sle_minion" 7s 675ms

Scenario:
Ensure again the errata cache is computed before testing on Salt minion
33s 60ms 6

When I follow the left menu "Admin > Task Schedules" 124ms

And I follow "errata-cache-default" 1s 369ms

And I follow "errata-cache-bunch" 1s 306ms

And I click on "Single Run Schedule" 1s 335ms

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 28s 634ms

Scenario:
Add operations to the action chain via API for Salt minions
7s 321ms 11

Running actions:
- Package Install/Upgrade
- Run an arbitrary script
- Package Removal
- Package Install/Upgrade
- System reboot
- Removed "Package Install/Upgrade" action
- Removed "Run an arbitrary script" action
- Removed "Package Removal" action
- Removed "Package Install/Upgrade" action
- Removed "System reboot" action

Given I want to operate on this "sle_minion" 345ms

When I create an action chain with label "salt_minion_api_chain" via API 423ms

And I add a package install to the action chain via API 1s 82ms

And I add a package removal to the action chain via API 895ms

And I add a package upgrade to the action chain via API 809ms

And I add the script "exit 1;" to the action chain via API 357ms

And I add a system reboot to the action chain via API 361ms

Then I should be able to see all these actions in the action chain via API 362ms

When I remove each action within the chain via API 2s 29ms

Then the current action chain should be empty 329ms

And I delete the action chain via API 323ms

Scenario:
Run an action chain via API on Salt minion
8s 861ms 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" 343ms

When I create an action chain with label "salt_minion_multiple_scripts" via API 339ms

And I add the script "echo -n 1 >> /tmp/action_chain.log" to the action chain via API 351ms

And I add the script "echo -n 2 >> /tmp/action_chain.log" to the action chain via API 345ms

And I add the script "echo -n 3 >> /tmp/action_chain.log" to the action chain via API 358ms

And I add the script "touch /tmp/action_chain_done" to the action chain via API 384ms

Then I should be able to see all these actions in the action chain via API 455ms

When I schedule the action chain via API 659ms

And I wait until there are no more action chains listed via API 449ms

And I wait until file "/tmp/action_chain_done" exists on "sle_minion" 4s

Then file "/tmp/action_chain.log" should contain "123" on "sle_minion" 842ms

When I wait until there are no more scheduled actions listed via API 329ms

Scenario:
Cleanup: remove Salt minion from configuration channel
1s 380ms 6

When I follow the left menu "Configuration > Channels" 150ms

And I follow "Action Chain Channel" 440ms

And I follow "Systems" in the content area 67ms

And I check the "sle_minion" client 65ms

And I click on "Unsubscribe systems" 56ms

Then I should see a "Successfully unsubscribed 1 system(s)." text 600ms

Scenario:
Cleanup: remove configuration channel for Salt minion
790ms 4

When I follow the left menu "Configuration > Channels" 65ms

And I follow "Action Chain Channel" 367ms

And I follow "Delete Channel" 297ms

And I click on "Delete Config Channel" 59ms

Scenario:
Cleanup: remove packages and repository used in action chain for Salt minion
5s 232ms 4

When I remove package "andromeda-dummy" from this "sle_minion" without error control 1s 729ms

And I remove package "virgo-dummy" from this "sle_minion" without error control 915ms

And I remove package "milkyway-dummy" from this "sle_minion" without error control 1s 944ms

And I disable repository "test_repo_rpm_pool" on this "sle_minion" without error control 643ms

Scenario:
Cleanup: remove temporary files for testing action chains on Salt minion
2s 359ms 4

When I run "rm -f /tmp/action_chain.log" on "sle_minion" without error control 775ms

And I run "rm -f /tmp/action_chain_done" on "sle_minion" without error control 555ms

And I run "rm -f /etc/action-chain.cnf" on "sle_minion" without error control 538ms

And I run "rm -f /tmp/action_chain_one_system_done" on "sle_minion" without error control 489ms

Scenario:
Cleanup: remove downloaded files
191ms 1

When I run "rm -f /tmp/downloads/action-chain.cnf" on "localhost" without error control 191ms

@skip_if_github_validation @ssh_minion @scope_action_chains @scope_salt_ssh
Feature:Salt SSH action chain 10m 55s 48ms 30

Scenario:
Log in as org admin user
463ms 1

Given I am authorized for the "Admin" section 463ms

Scenario:
Pre-requisite: downgrade repositories to lower version on SSH minion
7s 599ms 6

When I enable repository "test_repo_rpm_pool" on this "ssh_minion" 797ms

And I remove package "andromeda-dummy" from this "ssh_minion" without error control 1s 469ms

And I remove package "virgo-dummy" from this "ssh_minion" without error control 1s 581ms

And I install package "milkyway-dummy" on this "ssh_minion" without error control 1s 379ms

And I install old package "andromeda-dummy-1.0" on this "ssh_minion" 1s 492ms

And I refresh the metadata for "ssh_minion" 878ms

Scenario:
Pre-requisite: refresh package list and check newly installed packages on SSH minion
39s 356ms 3

When I refresh packages list via spacecmd on "ssh_minion" 6s 568ms

And I wait until refresh package list on "ssh_minion" is finished 26s 481ms

Then spacecmd should show packages "milkyway-dummy andromeda-dummy-1.0" installed on "ssh_minion" 6s 306ms

Scenario:
Pre-requisite: wait until downgrade is finished on SSH minion
1s 648ms 5

Given I am on the Systems overview page of this "ssh_minion" 980ms

When I follow "Software" in the content area 82ms

And I follow "List / Remove" in the content area 65ms

And I enter "andromeda-dummy" as the filtered package name 227ms

And I click on the filter button until page does contain "andromeda-dummy-1.0" text 291ms

Scenario:
Pre-requisite: ensure the errata cache is computed before testing on SSH minion
32s 968ms 6

When I follow the left menu "Admin > Task Schedules" 147ms

And I follow "errata-cache-default" 1s 226ms

And I follow "errata-cache-bunch" 1s 403ms

And I click on "Single Run Schedule" 1s 280ms

Then I should see a "bunch was scheduled" text 276ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 28s 634ms

Scenario:
Create a custom action chain for the SSH minion
579ms 3

When I create an action chain with label "minssh_action_chain" via API 356ms

And I follow the left menu "Schedule > Action Chains" 151ms

Then I wait until I see "minssh_action_chain" text 71ms

Scenario:
Add a patch installation to the action chain on SSH minion
23s 12ms 10

Given I am on the Systems overview page of this "ssh_minion" 985ms

When I follow "Software" in the content area 70ms

And I follow "Patches" in the content area 63ms

And I enter "andromeda" as the filtered synopsis 52ms

And I click on the filter button 10s 107ms

And I check "andromeda-dummy-6789" in the list 60ms

And I click on "Apply Patches" 842ms

And I check radio button "schedule-by-action-chain" 10s 71ms

And I click on "Confirm" 679ms

Then I should see a "Action has been successfully added to the Action Chain" text 78ms

Scenario:
Add a package removal to the action chain on SSH minion
12s 934ms 9

When I follow "Software" in the content area 72ms

And I follow "List / Remove" in the content area 83ms

And I enter "milkyway-dummy" as the filtered package name 212ms

And I click on the filter button 1s 171ms

And I check row with "milkyway-dummy" and arch of "ssh_minion" 60ms

And I click on "Remove Packages" 603ms

And I check radio button "schedule-by-action-chain" 10s 77ms

And I click on "Confirm" 587ms

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 221ms 9

When I follow "Software" in the content area 69ms

And I follow "Install New Packages" in the content area 64ms

And I enter "virgo-dummy" as the filtered package name 120ms

And I click on the filter button 626ms

And I check "virgo-dummy" in the list 53ms

And I click on "Install Packages" 581ms

And I check radio button "schedule-by-action-chain" 10s 48ms

And I click on "Confirm" 594ms

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 SSH minion
1s 240ms 7

When I follow the left menu "Configuration > Channels" 119ms

And I follow "Create Config Channel" 287ms

And I enter "Action Chain Channel" as "cofName" 69ms

And I enter "actionchainchannel" as "cofLabel" 65ms

And I enter "This is a test channel" as "cofDescription" 68ms

And I click on "Create Config Channel" 565ms

Then I should see a "Action Chain Channel" text 65ms

Scenario:
Add a configuration file to configuration channel for testing action chain on SSH minion
1s 538ms 8

When I follow the left menu "Configuration > Channels" 65ms

And I follow "Action Chain Channel" 362ms

And I follow "Create Configuration File or Directory" 338ms

And I enter "/etc/action-chain.cnf" as "cffPath" 73ms

And I enter "Testchain=YES_PLEASE" in the editor 4ms

And I click on "Create Configuration File" 576ms

Then I should see a "Revision 1 of /etc/action-chain.cnf from channel Action Chain Channel" text 98ms

And I should see a "Update Configuration File" button 18ms

Scenario:
Subscribe system to configuration channel for testing action chain on SSH minion
2s 991ms 8

Given I am on the Systems overview page of this "ssh_minion" 983ms

When I follow "Configuration" in the content area 74ms

And I follow "Manage Configuration Channels" in the content area 66ms

And I follow first "Subscribe to Channels" in the content area 64ms

And I check "Action Chain Channel" in the list 57ms

And I click on "Continue" 56ms

And I click on "Update Channel Rankings" 1s 611ms

Then I should see a "Channel Subscriptions successfully changed for" text 77ms

Scenario:
Add a configuration file deployment to the action chain on SSH minion
13s 785ms 9

When I follow the left menu "Configuration > Channels" 103ms

And I follow "Action Chain Channel" 496ms

And I follow "Deploy Files" in the content area 86ms

And I click on "Deploy All Files" 58ms

And I check the "ssh_minion" client 59ms

And I click on "Confirm & Deploy to Selected Systems" 937ms

And I check radio button "schedule-by-action-chain" 10s 57ms

And I click on "Deploy Files to Selected Systems" 1s 912ms

Then I should see a "Action has been successfully added to the Action Chain" text 73ms

Scenario:
Add apply highstate to action chain on SSH minion
11s 693ms 4

Given I am on the Systems overview page of this "ssh_minion" 1s 478ms

When I follow "States" in the content area 93ms

And I check radio button "schedule-by-action-chain" 10s 62ms

And I click on "Apply Highstate" 59ms

Scenario:
Add a reboot action to the action chain on SSH minion
12s 678ms 5

Given I am on the Systems overview page of this "ssh_minion" 1s 88ms

When I follow first "Schedule System Reboot" 588ms

And I check radio button "schedule-by-action-chain" 10s 79ms

And I click on "Reboot system" 828ms

Then I should see a "Action has been successfully added to the Action Chain" text 93ms

Scenario:
Add a remote command to the action chain on SSH minion
10s 857ms 6

When I follow "Details" in the content area 77ms

When I follow "Remote Command" in the content area 88ms

And I enter as remote command this script in #!/bin/bash touch /tmp/action_chain_one_system_done 67ms

And I check radio button "schedule-by-action-chain" 10s 59ms

And I click on "Schedule" 478ms

Then I should see a "Action has been successfully added to the Action Chain" text 86ms

Scenario:
Verify the action chain list on SSH minion
1s 43ms 9

When I follow the left menu "Schedule > Action Chains" 125ms

And I follow "minssh_action_chain" 304ms

Then I should see a "1. Apply patch(es) andromeda-dummy-6789 on 1 system" text 90ms

And I should see a "2. Remove milkyway-dummy from 1 system" text 86ms

And I should see a "3. Install or update virgo-dummy on 1 system" text 101ms

And I should see a text like "4. Deploy.*/etc/action-chain.cnf.*to 1 system" 82ms

And I should see a "5. Apply Highstate" text 85ms

And I should see a "6. Reboot 1 system" text 82ms

And I should see a "7. Run a remote command on 1 system" text 84ms

Scenario:
Check that a different user cannot see the action chain for SSH minion
2s 238ms 3

Given I am authorized as "testing" with password "testing" 2s 117ms

When I follow the left menu "Schedule > Action Chains" 108ms

Then I should not see a "minssh_action_chain" link 12ms

Scenario:
Execute the action chain from the web UI on SSH minion
3s 279ms 6

Given I am authorized for the "Admin" section 1s 926ms

When I follow the left menu "Schedule > Action Chains" 103ms

And I wait until I see "minssh_action_chain" text 82ms

And I follow "minssh_action_chain" 299ms

Then I click on "Save and Schedule" 57ms

And I should see a "Action Chain minssh_action_chain has been scheduled for execution." text 810ms

Scenario:
Verify that the action chain was executed successfully
5m 22s 722ms 2

When I wait for "virgo-dummy" to be installed on "ssh_minion" 51s 413ms

And I wait at most 300 seconds until file "/tmp/action_chain_one_system_done" exists on "ssh_minion" 4m 31s 309ms

Scenario:
Create a custom action chain for the SSH minion
488ms 3

When I create an action chain with label "minssh_action_chain_to_delete" via API 360ms

And I follow the left menu "Schedule > Action Chains" 65ms

Then I should see a "minssh_action_chain_to_delete" text 62ms

Scenario:
Add a remote command to the action chain on SSH minion
12s 536ms 6

Given I am on the Systems overview page of this "ssh_minion" 1s 269ms

When I follow "Remote Command" 511ms

And I enter as remote command this script in #!/bin/bash uptime 55ms

And I check radio button "schedule-by-action-chain" 10s 67ms

And I click on "Schedule" 57ms

Then I should see a "Action has been successfully added to the Action Chain" text 575ms

Scenario:
Delete the action chain for SSH minion
950ms 4

When I follow the left menu "Schedule > Action Chains" 127ms

And I follow "minssh_action_chain_to_delete" 345ms

And I follow "Delete Action Chains" in the content area 72ms

Then I click on "Delete" 405ms

Scenario:
Cleanup: roll back action chain effects on SSH minion
1m 20s 717ms 21

Given I am on the Systems overview page of this "ssh_minion" 1s 207ms

When I run "rm /tmp/action_chain_done" on "ssh_minion" without error control 411ms

And I enable repository "test_repo_rpm_pool" on this "ssh_minion" 513ms

And I remove package "andromeda-dummy" from this "ssh_minion" without error control 1s 945ms

And I remove package "virgo-dummy" from this "ssh_minion" without error control 1s 341ms

And I install package "milkyway-dummy" on this "ssh_minion" without error control 1s 697ms

And I install old package "andromeda-dummy-1.0" on this "ssh_minion" 1s 587ms

And I follow "Software" in the content area 68ms

And I click on "Update Package List" 67ms

And I follow "Events" in the content area 656ms

And I wait until I do not see "Package List Refresh scheduled" text, refreshing the page 24s 241ms

And I follow "Software" in the content area 81ms

And I follow "List / Remove" in the content area 72ms

And I enter "andromeda-dummy" as the filtered package name 180ms

And I click on the filter button until page does contain "andromeda-dummy-1.0" text 287ms

When I follow the left menu "Admin > Task Schedules" 151ms

And I follow "errata-cache-default" 1s 370ms

And I follow "errata-cache-bunch" 1s 330ms

And I click on "Single Run Schedule" 1s 585ms

Then I should see a "bunch was scheduled" text 277ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 41s 641ms

Scenario:
Add operations to the action chain via API for SSH minions
6s 225ms 10

Running actions:
- Package Install/Upgrade
- Run an arbitrary script
- Package Removal
- Package Install/Upgrade
- Removed "Package Install/Upgrade" action
- Removed "Run an arbitrary script" action
- Removed "Package Removal" action
- Removed "Package Install/Upgrade" action

Given I want to operate on this "ssh_minion" 389ms

When I create an action chain with label "minssh_api_chain" via API 364ms

And I add a package install to the action chain via API 806ms

And I add a package removal to the action chain via API 818ms

And I add a package upgrade to the action chain via API 777ms

And I add the script "exit 1;" to the action chain via API 371ms

Then I should be able to see all these actions in the action chain via API 342ms

When I remove each action within the chain via API 1s 691ms

Then the current action chain should be empty 342ms

And I delete the action chain via API 321ms

Scenario:
Run an action chain via API on SSH minion
31s 33ms 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" 335ms

When I create an action chain with label "minssh_multiple_scripts" via API 342ms

And I add the script "echo -n 1 >> /tmp/action_chain.log" to the action chain via API 359ms

And I add the script "echo -n 2 >> /tmp/action_chain.log" to the action chain via API 344ms

And I add the script "echo -n 3 >> /tmp/action_chain.log" to the action chain via API 366ms

And I add the script "touch /tmp/action_chain_done" to the action chain via API 449ms

Then I should be able to see all these actions in the action chain via API 404ms

When I schedule the action chain via API 503ms

Then I wait until there are no more action chains listed via API 686ms

When I wait until file "/tmp/action_chain_done" exists on "ssh_minion" 26s 20ms

Then file "/tmp/action_chain.log" should contain "123" on "ssh_minion" 866ms

When I wait until there are no more scheduled actions listed via API 352ms

Scenario:
Cleanup: remove SSH minion from configuration channel
1s 413ms 6

When I follow the left menu "Configuration > Channels" 147ms

And I follow "Action Chain Channel" 520ms

And I follow "Systems" in the content area 71ms

And I check the "ssh_minion" client 75ms

And I click on "Unsubscribe systems" 529ms

Then I should see a "Successfully unsubscribed 1 system(s)." text 68ms

Scenario:
Cleanup: remove configuration channel for SSH minion
1s 76ms 4

When I follow the left menu "Configuration > Channels" 60ms

And I follow "Action Chain Channel" 431ms

And I follow "Delete Channel" 231ms

And I click on "Delete Config Channel" 351ms

Scenario:
Cleanup: remove packages and repository used in action chain for SSH minion
4s 64ms 4

When I remove package "andromeda-dummy" from this "ssh_minion" without error control 1s 348ms

And I remove package "virgo-dummy" from this "ssh_minion" without error control 861ms

And I remove package "milkyway-dummy" from this "ssh_minion" without error control 1s 390ms

And I disable repository "test_repo_rpm_pool" on this "ssh_minion" without error control 463ms

Scenario:
Cleanup: remove temporary files for testing action chains on SSH minion
1s 689ms 4

When I run "rm -f /tmp/action_chain.log" on "ssh_minion" without error control 444ms

And I run "rm -f /tmp/action_chain_done" on "ssh_minion" without error control 411ms

And I run "rm -f /etc/action-chain.cnf" on "ssh_minion" without error control 414ms

And I run "rm -f /tmp/action_chain_one_system_done" on "ssh_minion" without error control 419ms

@skip_if_github_validation @ssh_minion @sle_minion @scope_action_chains
Feature:Action chains on several systems at once 3m 20s 859ms 12

Scenario:
Log in as admin user
451ms 1

Given I am authorized for the "Admin" section 451ms

Scenario:
Pre-requisite: downgrade packages before action chain test on several systems
9s 618ms 8

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 909ms

And I enable repository "test_repo_rpm_pool" on this "ssh_minion" 791ms

And I remove package "andromeda-dummy" from this "ssh_minion" without error control 900ms

And I remove package "andromeda-dummy" from this "sle_minion" without error control 944ms

And I install package "andromeda-dummy-1.0" on this "sle_minion" 2s 393ms

And I install package "andromeda-dummy-1.0" on this "ssh_minion" 1s 583ms

And I refresh the metadata for "sle_minion" 1s 187ms

And I refresh the metadata for "ssh_minion" 909ms

Scenario:
Pre-requisite: refresh package list and check installed packages before action chain test on several systems
1m 5s 756ms 6

When I refresh packages list via spacecmd on "sle_minion" 8s 326ms

And I wait until refresh package list on "sle_minion" is finished 10s 648ms

Then spacecmd should show packages "andromeda-dummy-1.0" installed on "sle_minion" 7s 793ms

When I refresh packages list via spacecmd on "ssh_minion" 6s 159ms

And I wait until refresh package list on "ssh_minion" is finished 26s 688ms

Then spacecmd should show packages "andromeda-dummy-1.0" installed on "ssh_minion" 6s 139ms

Scenario:
Pre-requisite: wait until downgrade is finished before action chain test on several systems
1s 533ms 5

Given I am on the Systems overview page of this "sle_minion" 935ms

When I follow "Software" in the content area 70ms

And I follow "List / Remove" in the content area 66ms

And I enter "andromeda-dummy" as the filtered package name 175ms

And I click on the filter button until page does contain "andromeda-dummy-1.0" text 285ms

Scenario:
Pre-requisite: ensure the errata cache is computed before action chain test on several systems
50s 658ms 13

When I follow the left menu "Admin > Task Schedules" 142ms

And I follow "errata-cache-default" 1s 253ms

And I follow "errata-cache-bunch" 1s 475ms

And I click on "Single Run Schedule" 1s 300ms

Then I should see a "bunch was scheduled" text 275ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 38s 594ms

Given I am on the Systems overview page of this "ssh_minion" 987ms

When I follow the left menu "Admin > Task Schedules" 135ms

And I follow "errata-cache-default" 1s 345ms

And I follow "errata-cache-bunch" 1s 303ms

And I click on "Single Run Schedule" 1s 283ms

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 290ms

Scenario:
Create a custom action chain for two systems
551ms 3

When I create an action chain with label "two_systems_action_chain" via API 351ms

And I follow the left menu "Schedule > Action Chains" 135ms

Then I should see a "two_systems_action_chain" text 64ms

Scenario:
Add an action chain using system set manager for SSH minion and SLE minion
24s 570ms 22

When I follow the left menu "Systems > System List > All" 178ms

And I check the "sle_minion" client 511ms

And I check the "ssh_minion" client 61ms

And I follow the left menu "Systems > System Set Manager > Overview" 483ms

And I follow "Install" in the content area 89ms

And I follow "Fake-RPM-SUSE-Channel" in the content area 68ms

And I enter "andromeda-dummy" as the filtered package name 58ms

And I click on the filter button 419ms

And I check "andromeda-dummy" in the list 55ms

And I click on "Install Packages" 334ms

Then I should see "sle_minion" hostname 81ms

And I should see "ssh_minion" hostname 78ms

When I check radio button "schedule-by-action-chain" 10s 54ms

And I click on "Confirm" 881ms

Then I should see a "Package installations are being scheduled" text 64ms

When I follow the left menu "Systems > System Set Manager > Overview" 65ms

And I follow "remote commands" in the content area 68ms

And I enter as remote command this script in #!/bin/bash touch /tmp/action_chain_done 62ms

And I check radio button "schedule-by-action-chain" 10s 61ms

And I click on "Schedule" 706ms

Then I should see "sle_minion" hostname 93ms

And I should see "ssh_minion" hostname 88ms

Scenario:
Verify action chain for two systems
3s 8ms 8

Given I am on the Systems overview page of this "sle_minion" 1s 220ms

When I follow "Schedule" 363ms

And I follow "Action Chains" 262ms

And I follow "two_systems_action_chain" 339ms

And I should see a "1. Install or update andromeda-dummy on 2 systems" text 72ms

And I should see a "2. Run a remote command on 2 systems" text 66ms

And I click on "Save and Schedule" 58ms

Then I should see a "Action Chain two_systems_action_chain has been scheduled for execution." text 624ms

Scenario:
Verify that the action chain from the system set manager was executed successfully
39s 333ms 4

When I wait until file "/tmp/action_chain_done" exists on "ssh_minion" 37s 640ms

And I wait until file "/tmp/action_chain_done" exists on "sle_minion" 805ms

Then "andromeda-dummy" should be installed on "ssh_minion" 428ms

And "andromeda-dummy" should be installed on "sle_minion" 459ms

Scenario:
Cleanup: remove package and repository used in action chain for several systems
4s 449ms 4

When I remove package "andromeda-dummy" from this "sle_minion" without error control 1s 724ms

And I remove package "andromeda-dummy" from this "ssh_minion" without error control 1s 561ms

And I disable repository "test_repo_rpm_pool" on this "sle_minion" without error control 519ms

And I disable repository "test_repo_rpm_pool" on this "ssh_minion" without error control 644ms

Scenario:
Cleanup: remove temporary files for testing action chains on several systems
858ms 2

When I run "rm /tmp/action_chain_done" on "sle_minion" without error control 445ms

And I run "rm /tmp/action_chain_done" on "ssh_minion" without error control 413ms

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 9m 41s 220ms 31 1

Scenario:
Log in as admin user
455ms 1

Given I am authorized for the "Admin" section 455ms

Scenario:
Create an IP forwarding config state channel
1s 640ms 10

When I follow the left menu "Configuration > Channels" 123ms

And I follow "Create State Channel" 290ms

And I wait until I see "New Config State Channel" text 62ms

And I enter "My State Channel for Recurring Actions" as "cofName" 93ms

And I enter "statechannel-recurring" as "cofLabel" 66ms

And I enter "This is a state channel to be used in recurring actions" as "cofDescription" 97ms

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" 66ms

Then I wait until I see "Channel Properties" text 771ms

And I wait until I see "My State Channel for Recurring Actions" text 64ms

Scenario:
Enable IP forwarding through a custom state recurring action
1m 30s 73ms 21

Execution time: 14:25

When I am on the "Recurring Actions" page of this "sle_minion" 1s 175ms

Then I should see a "No schedules created. Use Create to add a schedule" text 204ms

When I click on "Create" 95ms

And I wait until I see "Action Type" text 93ms

And I enter "IP forwarding custom state recurring action" as "scheduleName" 279ms

And I select "Custom state" from "actionTypeDescription" 1s 135ms

And I wait until I see "Configure states to execute" text 107ms

And I check radio button "schedule-daily" 10s 93ms

And I enter 1 minutes from now as "time-daily_time" 98ms

And I check "statechannel-recurring-cbox" 87ms

And I click on "Save Changes" 64ms

And I wait until I see "Edit State Ranks" text 96ms

And I click on "Confirm" 74ms

And I click on "Create Schedule" 64ms

Then I wait until I see "Schedule successfully created" text 439ms

And I should see a "IP forwarding custom state recurring action" text 284ms

And I should see a "Minion" text 74ms

When I follow "Events" 479ms

And I follow "History" 467ms

Then I wait at most 420 seconds until event "Apply recurring states [manager_org_1.statechannel-recurring] schedule" is completed 1m 13s 481ms

And file "/proc/sys/net/ipv4/conf/all/forwarding" should contain "1" on "sle_minion" 1s 174ms

Scenario:
Edit the IP forwarding custom state recurring action
1m 2s 207ms 19

Execution time: 14:26

When I am on the "Recurring Actions" page of this "sle_minion" 1s 176ms

Then I should see a "IP forwarding custom state recurring action" text 266ms

When I click the "IP forwarding custom state recurring action" item edit button 65ms

And I wait until I see "Update Schedule" text 309ms

And I enter "custom_state_schedule_name_changed" as "scheduleName" 567ms

And I enter 1 minutes from now as "time-daily_time" 99ms

And I uncheck "statechannel-recurring-cbox" 10s 80ms

And I check "Sync States-cbox" 86ms

And I click on "Save Changes" 67ms

And I wait until I see "Edit State Ranks" text 103ms

And I click on "Confirm" 77ms

And I click on "Update Schedule" 64ms

Then I wait until I see "Schedule successfully updated" text 783ms

And I should see a "custom_state_schedule_name_changed" text 537ms

And I should see a "Minion" text 69ms

When I follow "Events" 748ms

And I follow "History" 535ms

Then I wait at most 420 seconds until event "Apply recurring states [util.syncstates] scheduled" is completed 46s 503ms

And I wait until I see "SLS: util.syncstates" text 63ms

@skip_if_github_validation
Scenario:
Cleanup: Disable IP forwarding
15s 628ms 9

When I follow the left menu "Salt > Remote Commands" 127ms

Then I should see a "Remote Commands" text in the content area 24ms

When I enter command "echo 0 > /proc/sys/net/ipv4/conf/all/forwarding" 140ms

And I enter target "sle_minion" 104ms

And I click on preview 11s 588ms

And I click on run 48ms

Then I should see "sle_minion" hostname 66ms

And I wait until I see "show response" text 2s 295ms

And file "/proc/sys/net/ipv4/conf/all/forwarding" should contain "0" on "sle_minion" 1s 232ms

Scenario:
Cleanup: Delete the minion Custom state Recurring Action
1s 860ms 6

When I am on the "Recurring Actions" page of this "sle_minion" 1s 34ms

Then I should see a "custom_state_schedule_name_changed" text 306ms

When I click the "custom_state_schedule_name_changed" item delete button 73ms

And I wait until I see "Delete Recurring Action Schedule" text 73ms

And I click on the red confirmation button 65ms

Then I wait until I see "Schedule 'custom_state_schedule_name_changed' has been deleted." text 306ms

Scenario:
Create a minion Highstate Recurring Action
48s 702ms 16

Execution time: 14:27

When I am on the "Recurring Actions" page of this "sle_minion" 969ms

Then I should see a "No schedules created. Use Create to add a schedule" text 95ms

When I click on "Create" 98ms

And I wait until I see "Schedule Name" text 92ms

And I enter "Minion Highstate Recurring Action" as "scheduleName" 240ms

And I select "Highstate" from "actionTypeDescription" 1s 128ms

And I check radio button "schedule-daily" 10s 91ms

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" 58ms

Then I wait until I see "Schedule successfully created" text 350ms

And I should see a "Minion Highstate Recurring Action" text 169ms

And I should see a "Minion" text 74ms

When I follow "Events" 356ms

And I follow "History" 389ms

And I wait until I see the event "Apply highstate in test-mode scheduled" completed during last minute, refreshing the page 34s 438ms

Scenario:
Edit the minion Highstate Recurring Action
14s 318ms 13

When I am on the "Recurring Actions" page of this "sle_minion" 1s 25ms

Then I should see a "Minion Highstate Recurring Action" text 273ms

When I click the "Minion Highstate Recurring Action" item edit button 75ms

And I wait until I see "Update Schedule" text 299ms

And I enter "schedule_name_minion" as "scheduleName" 356ms

And I check radio button "schedule-weekly" 10s 79ms

And I select "Wednesday" from "date_weekly" 1s 124ms

And I enter "01:35" as "time-weekly_time" 100ms

And I click on "Update Schedule" 61ms

Then I wait until I see "Schedule successfully updated" text 620ms

And I should see a "schedule_name_minion" text 168ms

And I should see a "Minion" text 66ms

And I should see a "0 35 1 ? * 4" text 66ms

Scenario:
View the minion Highstate Recurring Action details
1s 688ms 6

When I am on the "Recurring Actions" page of this "sle_minion" 1s 46ms

Then I should see a "schedule_name_minion" text 175ms

When I click the "schedule_name_minion" item details button 67ms

Then I should see a "Every Wednesday at 01:35" text 269ms

When I click on "Back" 65ms

Then I should see a "Schedules" text 64ms

Scenario:
Create a System group for testing
3s 704ms 11

When I follow the left menu "Systems > System Groups" 79ms

And I follow "Create Group" 267ms

And I enter "Recurring-Action-test-group" as "name" 79ms

And I enter "This is for testing" as "description" 65ms

And I click on "Create Group" 62ms

Then I should see a "System group Recurring-Action-test-group created." text 69ms

When I am on the "Groups" page of this "sle_minion" 1s 278ms

And I follow first "Join" 457ms

And I check the first row in the list 74ms

And I click on "Join Groups" 1s 195ms

Then I wait until I see "1 system groups added" text 73ms

Scenario:
Pre-requisite: subscribe system to Fake Channel
45s 499ms 12

Given I am on the Systems overview page of this "sle_minion" 1s 128ms

When I follow "Software" in the content area 74ms

And I follow "Software Channels" in the content area 88ms

And I wait until I do not see "Loading..." text 73ms

And I check radio button "Fake-Base-Channel-SUSE-like" 10s 74ms

And I wait until I do not see "Loading..." text 428ms

And I check "Fake-Child-Channel-SUSE-like" 77ms

And I click on "Next" 60ms

Then I should see a "Confirm Software Channel Change" text 60ms

When I click on "Confirm" 74ms

Then I should see a "Changing the channels has been scheduled." text 412ms

And I wait until event "Subscribe channels scheduled" is completed 32s 946ms

@skip_if_github_validation
Scenario:
Pre-requisite: downgrade milkyway-dummy to lower version
22s 956ms 9

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 833ms

And I install old package "milkyway-dummy-1.0" on this "sle_minion" 2s 563ms

And I refresh the metadata for "sle_minion" 837ms

And I follow the left menu "Admin > Task Schedules" 122ms

And I follow "errata-cache-default" 394ms

And I follow "errata-cache-bunch" 1s 306ms

And I click on "Single Run Schedule" 1s 280ms

Then I should see a "bunch was scheduled" text 275ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 15s 342ms

Scenario:
Pre-requisite: check that there are updates available
1s 9ms 2

Given I am on the Systems overview page of this "sle_minion" 922ms

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 774ms 24

Execution time: 14:30

When I follow the left menu "Systems > System Groups" 79ms

And I follow "Recurring-Action-test-group" 322ms

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" 100ms

And I wait until I see "Schedule Name" text 91ms

And I enter "Recurring action to keep Recurring-Action-test-group uptodate" as "scheduleName" 379ms

And I select "Custom state" from "actionTypeDescription" 1s 133ms

And I wait until I see "Configure states to execute" text 108ms

And I check radio button "schedule-daily" 10s 83ms

And I enter 1 minutes from now as "time-daily_time" 102ms

And I check "Update System-cbox" 88ms

And I click on "Save Changes" 65ms

And I wait until I see "Edit State Ranks" text 96ms

And I click on "Confirm" 74ms

And I click on "Create Schedule" 63ms

Then I wait until I see "Schedule successfully created" text 290ms

And I should see a "Recurring action to keep Recurring-Action-test-group uptodate" text 68ms

And I should see a "Group" text 67ms

When I am on the "Events" page of this "sle_minion" 1s 125ms

And I follow "History" 476ms

Then I wait until I see the event "Apply recurring states [uptodate] scheduled" completed during last minute, refreshing the page 1m 8s 844ms

When I am on the Systems overview page of this "sle_minion" 886ms

Then I wait at most 500 seconds until I do not see "System is up to date" text, refreshing the page 91ms

@susemanager
Scenario:
Cleanup: subscribe system back to default base channel
< 1ms 24

Given I am on the Systems overview page of this "sle_minion" 0s

When I follow "Software" in the content area 0s

And I disable repository "test_repo_rpm_pool" on this "sle_minion" without error control 0s

And I follow "Software Channels" in the content area 0s

And I wait until I do not see "Loading..." text 0s

And I check default base channel radio button of this "sle_minion" 0s

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

And I wait until "SLE-Module-Basesystem15-SP7-Pool for x86_64" has been checked 0s

And I wait until "SLE-Module-Basesystem15-SP7-Updates for x86_64" has been checked 0s

And I wait until "SLE-Module-Server-Applications15-SP7-Pool for x86_64" has been checked 0s

And I wait until "SLE-Module-Server-Applications15-SP7-Updates for x86_64" has been checked 0s

And I check "SLE-Module-DevTools15-SP7-Pool for x86_64" 0s

And I wait until "SLE-Module-DevTools15-SP7-Updates for x86_64" has been checked 0s

And I wait until "SLE-Module-Desktop-Applications15-SP7-Pool for x86_64" has been checked 0s

And I wait until "SLE-Module-Desktop-Applications15-SP7-Updates for x86_64" has been checked 0s

And I check "SLE-Module-Containers15-SP7-Pool for x86_64" 0s

And I wait until "SLE-Module-Containers15-SP7-Updates for x86_64" has been checked 0s

And I check "Fake-RPM-SUSE-Channel" 0s

And I click on "Next" 0s

Then I should see a "Confirm Software Channel Change" text 0s

When I click on "Confirm" 0s

Then I should see a "Changing the channels has been scheduled." text 0s

And I wait until event "Subscribe channels scheduled" is completed 0s

@uyuni
Scenario:
Cleanup: subscribe system back to default base channel
23s 982ms 14

Given I am on the Systems overview page of this "sle_minion" 943ms

When I follow "Software" in the content area 69ms

And I disable repository "test_repo_rpm_pool" on this "sle_minion" without error control 847ms

And I follow "Software Channels" in the content area 67ms

And I wait until I do not see "Loading..." text 71ms

And I check default base channel radio button of this "sle_minion" 453ms

And I wait for child channels to appear 615ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 101ms

And I check "Fake-RPM-SUSE-Channel" 74ms

And I click on "Next" 59ms

Then I should see a "Confirm Software Channel Change" text 64ms

When I click on "Confirm" 73ms

Then I should see a "Changing the channels has been scheduled." text 297ms

And I wait until event "Subscribe channels scheduled" is completed 20s 241ms

Scenario:
Edit the group Recurring Action
12s 966ms 14

When I follow the left menu "Systems > System Groups" 70ms

And I follow "Recurring-Action-test-group" 306ms

And I follow "Recurring Actions" in the content area 63ms

Then I should see a "Recurring action to keep Recurring-Action-test-group uptodate" text 263ms

When I click the "Recurring action to keep Recurring-Action-test-group uptodate" item edit button 68ms

And I wait until I see "Update Schedule" text 310ms

And I enter "schedule_name_group" as "scheduleName" 587ms

And I check radio button "schedule-hourly" 10s 64ms

And I enter "35" as "minutes" 70ms

And I click on "Update Schedule" 68ms

Then I wait until I see "Schedule successfully updated" text 603ms

And I should see a "schedule_name_group" text 353ms

And I should see a "Group" text 66ms

And I should see a "0 35 * ? * *" text 70ms

Scenario:
View the group recurring actions details
1s 263ms 10

When I follow the left menu "Systems > System Groups" 62ms

And I follow "Recurring-Action-test-group" 320ms

And I follow "Recurring Actions" in the content area 68ms

Then I should see a "schedule_name" text 266ms

When I click the "schedule_name" item details button 64ms

Then I should see a "Every hour at minute 35" text 271ms

And I should see a "Recurring-Action-test-group" link 11ms

And I should see a "Update System" text 69ms

When I click on "Back" 66ms

Then I should see a "Schedules" text 61ms

Scenario:
Create a yourorg Recurring Action
1m 12s 153ms 21

Execution time: 14:32

When I follow the left menu "Home > My Organization > Recurring Actions" 190ms

Then I should see a "No schedules created. Use Create to add a schedule" text 60ms

When I click on "Create" 82ms

And I wait until I see "Schedule Name" text 89ms

And I enter "schedule_name" as "scheduleName" 104ms

And I select "Custom state" from "actionTypeDescription" 1s 128ms

And I wait until I see "Configure states to execute" text 102ms

And I check radio button "schedule-daily" 10s 77ms

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" 67ms

And I wait until I see "Edit State Ranks" text 94ms

And I click on "Confirm" 97ms

And I click on "Create Schedule" 66ms

Then I wait until I see "Schedule successfully created" text 249ms

And I should see a "schedule_name" text 162ms

And I should see a "Organization" text 68ms

When I am on the "Events" page of this "sle_minion" 1s 130ms

And I follow "History" 421ms

Then I wait until I see the event "Apply recurring states [packages.profileupdate] scheduled" completed during last minute, refreshing the page 57s 719ms

Scenario:
Edit the yourorg Recurring Action
13s 459ms 13

When I follow the left menu "Home > My Organization > Recurring Actions" 221ms

Then I should see a "schedule_name" text 268ms

When I click the "schedule_name" item edit button 64ms

And I wait until I see "Update Schedule" text 306ms

And I enter "schedule_name_edit" as "scheduleName" 287ms

And I check radio button "schedule-monthly" 10s 67ms

And I select "7" from "date_monthly" 1s 137ms

And I enter "05:17" as "time-monthly_time" 116ms

And I click on "Update Schedule" 66ms

Then I wait until I see "Schedule successfully updated" text 624ms

And I should see a "schedule_name_edit" text 165ms

And I should see a "Organization" text 67ms

And I should see a "0 17 5 7 * ?" text 63ms

Scenario:
View the yourorg recurring actions details
858ms 7

When I follow the left menu "Home > My Organization > Recurring Actions" 90ms

Then I should see a "schedule_name" text 254ms

When I click the "schedule_name" item details button 66ms

Then I should see a "Every 7th of the month at 05:17" text 248ms

And I should see a "Package Profile Update" text 70ms

When I click on "Back" 68ms

Then I should see a "Schedules" text 59ms

Scenario:
Cleanup: Delete the yourorg Recurring Action
1s 392ms 7

When I follow the left menu "Home > My Organization > Recurring Actions" 77ms

Then I should see a "schedule_name_edit" text 257ms

When I click the "schedule_name" item delete button 73ms

And I wait until I see "Delete Recurring Action Schedule" text 66ms

And I click on the red confirmation button 66ms

Then I wait until I see "Schedule 'schedule_name_edit' has been deleted." text 684ms

And I should see a "No schedules created. Use Create to add a schedule" text 165ms

Scenario:
Create an admin org Recurring Action
37s 719ms 23

Execution time: 14:33

When I follow the left menu "Admin > Organizations" 117ms

And I follow "SUSE Test" in the content area 70ms

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 64ms

When I click on "Create" 85ms

And I wait until I see "Schedule Name" text 99ms

And I select "Custom state" from "actionTypeDescription" 1s 116ms

And I wait until I see "Configure states to execute" text 104ms

And I enter "schedule_name" as "scheduleName" 138ms

And I check radio button "schedule-daily" 10s 66ms

And I enter 1 minutes from now as "time-daily_time" 96ms

And I click on the "disabled" toggler 54ms

And I check "Hardware Profile Update-cbox" 88ms

And I click on "Save Changes" 66ms

And I wait until I see "Edit State Ranks" text 100ms

And I click on "Confirm" 90ms

And I click on "Create Schedule" 64ms

Then I wait until I see "Schedule successfully created" text 258ms

And I should see a "schedule_name" text 169ms

And I should see a "Organization" text 69ms

When I am on the "Events" page of this "sle_minion" 1s 86ms

And I follow "History" 461ms

Then I wait until I see the event "Apply recurring states [hardware.profileupdate] scheduled" completed during last minute, refreshing the page 23s 185ms

Scenario:
Edit the admin org Recurring Action
12s 324ms 14

When I follow the left menu "Admin > Organizations" 135ms

And I follow "SUSE Test" in the content area 69ms

And I follow "Recurring Actions" in the content area 63ms

Then I should see a "schedule_name" text 265ms

When I click the "schedule_name" item edit button 64ms

And I wait until I see "Update Schedule" text 317ms

And I enter "schedule_name_org" as "scheduleName" 257ms

And I check radio button "schedule-cron" 10s 75ms

And I enter "0 0 15 3 * ?" as "cron" 198ms

And I click on "Update Schedule" 64ms

Then I wait until I see "Schedule successfully updated" text 610ms

And I should see a "schedule_name_org" text 71ms

And I should see a "Organization" text 66ms

And I should see a "0 0 15 3 * ?" text 64ms

Scenario:
View the admin org recurring actions details
902ms 8

When I follow the left menu "Admin > Organizations" 71ms

And I follow "SUSE Test" in the content area 64ms

And I follow "Recurring Actions" in the content area 58ms

Then I should see a "schedule_name" text 261ms

When I click the "schedule_name" item details button 62ms

Then I should see a "Every 3rd of the month at 15:00" text 256ms

When I click on "Back" 68ms

Then I should see a "Schedules" text 59ms

Scenario:
View all types of recurring actions in the list of all actions
956ms 8

When I follow the left menu "Schedule > Recurring Actions" 121ms

Then I should not see a "Create" text 56ms

And I should see a "schedule_name_minion" text 421ms

And I should see a "Minion" text 74ms

And I should see a "schedule_name_group" text 73ms

And I should see a "Group" text 69ms

And I should see a "schedule_name_org" text 69ms

And I should see a "Organization" text 69ms

Scenario:
View details in list of all actions
1s 271ms 6

When I follow the left menu "Schedule > Recurring Actions" 58ms

And I click the "schedule_name_minion" item details button 461ms

Then I should see a "Every Wednesday at 01:35" text 150ms

And I should not see a "Schedules" text in the content area 27ms

When I click on "Back" 57ms

Then I should see a "schedule_name_group" text 515ms

Scenario:
Cleanup: Delete the admin org Recurring Action
991ms 8

When I follow the left menu "Admin > Organizations" 108ms

And I follow "SUSE Test" in the content area 57ms

And I follow "Recurring Actions" in the content area 57ms

Then I should see a "schedule_name_org" text 351ms

When I click the "schedule_name_org" item delete button 75ms

And I wait until I see "Delete Recurring Action Schedule" text 68ms

And I click on the red confirmation button 66ms

Then I wait until I see "Schedule 'schedule_name_org' has been deleted." text 206ms

Scenario:
Cleanup: Delete the group Recurring Action
1s 721ms 9

When I follow the left menu "Systems > System Groups" 121ms

And I follow "Recurring-Action-test-group" 314ms

And I follow "Recurring Actions" in the content area 58ms

Then I should see a "schedule_name_group" text 262ms

When I click the "schedule_name_group" item delete button 64ms

And I wait until I see "Delete Recurring Action Schedule" text 70ms

And I click on the red confirmation button 55ms

Then I wait until I see "Schedule 'schedule_name_group' has been deleted." text 706ms

And I should see a "No schedules created. Use Create to add a schedule" text 67ms

Scenario:
Cleanup: Delete the minion Highstate Recurring Action
1s 838ms 7

When I am on the "Recurring Actions" page of this "sle_minion" 1s 20ms

Then I should see a "schedule_name_minion" text 162ms

When I click the "schedule_name_minion" item delete button 62ms

And I wait until I see "Delete Recurring Action Schedule" text 69ms

And I click on the red confirmation button 57ms

Then I wait until I see "Schedule 'schedule_name_minion' has been deleted." text 406ms

And I should see a "No schedules created. Use Create to add a schedule" text 59ms

Scenario:
Cleanup: Delete the system group created for group recurring action tests
1s 831ms 5

When I follow the left menu "Systems > System Groups" 60ms

And I follow "Recurring-Action-test-group" 304ms

And I follow "Delete Group" 307ms

And I click on "Confirm Deletion" 1s 98ms

Then I should see a "Your organization has no system groups." text 60ms

Scenario:
Cleanup: Remove "My State Channel for Recurring Actions" config channel
1s 68ms 5

When I follow the left menu "Configuration > Channels" 122ms

And I follow "My State Channel for Recurring Actions" 424ms

And I follow "Delete Channel" 315ms

And I click on "Delete Config Channel" 61ms

Then I should see a "Channel 'My State Channel for Recurring Actions' has been deleted" text 144ms

@skip_if_github_validation @scc_credentials @scope_changing_software_channels @sle_minion
Feature:Assign child channel to a system 1m 28s 877ms 8 6

Scenario:
Log in as org admin user
2s 104ms 1

Given I am authorized 2s 104ms

@susemanager
Scenario:
Pre-requisite: unsubscribe from old channels
< 1ms 13

Given I am on the Systems overview page of this "sle_minion" 0s

When I follow "Software" in the content area 0s

And I follow "Software Channels" in the content area 0s

And I wait until I do not see "Loading..." text 0s

And I check radio button "SLE-Product-SLES15-SP7-Pool for x86_64" 0s

Then radio button "SLE-Product-SLES15-SP7-Pool for x86_64" should be checked 0s

And I wait until I do not see "Loading..." text 0s

When I uncheck "SLE15-SP7-Installer-Updates for x86_64" 0s

And I should see "SLE15-SP7-Installer-Updates for x86_64" as unchecked 0s

And I click on "Next" 0s

Then I should see a "Confirm Software Channel Change" text 0s

When I click on "Confirm" 0s

Then I should see a "Changing the channels has been scheduled." text 0s

@uyuni
Scenario:
Pre-requisite: unsubscribe from old channels
3s 464ms 15

Warning: Radio button 'openSUSE Tumbleweed (x86_64)' is already checked

Given I am on the Systems overview page of this "sle_minion" 1s 759ms

When I follow "Software" in the content area 65ms

And I follow "Software Channels" in the content area 66ms

And I wait until I do not see "Loading..." text 65ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 234ms

Then radio button "openSUSE Tumbleweed (x86_64)" should be checked 14ms

When I wait until I do not see "Loading..." text 500ms

And I uncheck "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" by label 35ms

Then I should see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" as unchecked 14ms

When I uncheck "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" by label 75ms

Then I should see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" as unchecked 14ms

When I click on "Next" 61ms

Then I should see a "Confirm Software Channel Change" text 63ms

When I click on "Confirm" 76ms

Then I should see a "Changing the channels has been scheduled." text 417ms

@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 732ms 3

When I refresh the metadata for "sle_minion" 7s 955ms

Then channel "openSUSE Tumbleweed (x86_64)" should be enabled on "sle_minion" 819ms

And channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" should be disabled on "sle_minion" 957ms

@susemanager
Scenario:
Assign a child channel to the system
< 1ms 13

When I follow "Software" in the content area 0s

And I follow "Software Channels" in the content area 0s

And I wait until I do not see "Loading..." text 0s

Then radio button "SLE-Product-SLES15-SP7-Pool for x86_64" should be checked 0s

And I wait until I do not see "Loading..." text 0s

And I check "SLE15-SP7-Installer-Updates for x86_64" 0s

And I click on "Next" 0s

Then I should see a "Confirm Software Channel Change" text 0s

And I click on "Confirm" 0s

Then I should see a "Changing the channels has been scheduled." text 0s

When I follow "scheduled" in the content area 0s

And I wait until I see "1 system successfully completed this action." text, refreshing the page 0s

Then channel "SLE15-SP7-Installer-Updates for x86_64" should be enabled on "sle_minion" 0s

@uyuni
Scenario:
Assign a child channel to the system
32s 485ms 14

When I follow "Software" in the content area 64ms

And I follow "Software Channels" in the content area 57ms

And I wait until I do not see "Loading..." text 65ms

Then radio button "openSUSE Tumbleweed (x86_64)" should be checked 228ms

When I wait until I do not see "Loading..." text 507ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" by label 79ms

Then I should see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" as checked 14ms

When I click on "Next" 61ms

Then I should see a "Confirm Software Channel Change" text 66ms

When I click on "Confirm" 73ms

Then I should see a "Changing the channels has been scheduled." text 418ms

When I follow "scheduled" in the content area 79ms

And I wait until I see "1 system successfully completed this action." text, refreshing the page 29s 905ms

Then channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" should be enabled on "sle_minion" 864ms

Scenario:
Check channel change has completed for the system
3s 516ms 3

Given I am on the Systems overview page of this "sle_minion" 993ms

When I wait until event "Subscribe channels scheduled" is completed 2s 461ms

Then I should see a "The client completed this action on" text 61ms

@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
1s 926ms 6

When I follow "Software" in the content area 70ms

And I follow "Software Channels" in the content area 63ms

And I wait until I do not see "Loading..." text 65ms

Then radio button "openSUSE Tumbleweed (x86_64)" should be checked 306ms

And I wait until I do not see "Loading..." text 1s 401ms

And I should see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" as checked 19ms

@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 176ms 3

When I refresh the metadata for "sle_minion" 1s 534ms

Then channel "openSUSE Tumbleweed (x86_64)" should be enabled on "sle_minion" 791ms

And channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" should be enabled on "sle_minion" 849ms

@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 470ms 18

When I follow "Software" in the content area 60ms

And I follow "Software Channels" in the content area 54ms

And I wait until I do not see "Loading..." text 65ms

Then radio button "openSUSE Tumbleweed (x86_64)" should be checked 207ms

And I wait until I do not see "Loading..." text 414ms

And I wait until I see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" text 78ms

And I uncheck "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" by label 76ms

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 76ms

Then I should see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" as checked 14ms

When I check "Fake-RPM-SUSE-Channel" 38ms

And I click on "Next" 60ms

Then I should see a "Confirm Software Channel Change" text 70ms

When I click on "Confirm" 74ms

And I wait until I see "Changing the channels has been scheduled." text 400ms

And I follow "scheduled" in the content area 73ms

And I wait until I see "1 system successfully completed this action." text, refreshing the page 29s 926ms

Then channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" should be disabled on "sle_minion" 764ms

@scope_retracted_patches
Feature:Retracted patches 2m 55s 502ms 12

Scenario:
Log in as org admin user
2s 52ms 1

Given I am authorized 2s 52ms

Scenario:
Installed retracted package should show icon in the system packages list
53s 358ms 12

When I install package "rute-dummy=2.1-1.1" on this "sle_minion" 2s 710ms

And I refresh packages list via spacecmd on "sle_minion" 8s 213ms

And I wait until refresh package list on "sle_minion" is finished 11s 249ms

And I am on the "Software" page of this "sle_minion" 1s 77ms

And I follow "Packages" 485ms

And I follow "List / Remove" 724ms

And I enter "rute-dummy" as the filtered package name 47ms

And I click on the filter button until page does contain "rute-dummy" text 11s 14ms

Then the table row for "rute-dummy-2.1-1.1" should contain "retracted" icon 21ms

When I remove package "rute-dummy" from this "sle_minion" 2s 189ms

And I refresh packages list via spacecmd on "sle_minion" 8s 362ms

And I wait until package "rute-dummy" is removed from "sle_minion" via spacecmd 7s 262ms

Scenario:
Retracted package should not be available for installation
13s 52ms 7

When I am on the "Software" page of this "sle_minion" 1s 105ms

And I follow "Packages" 548ms

And I follow "Install" 502ms

And I enter "rute-dummy" as the filtered package name 54ms

And I click on the filter button until page does contain "rute-dummy" text 10s 701ms

Then I should see a "rute-dummy-2.0-1.2" text 69ms

And I should not see a "rute-dummy-2.1-1.1" text 71ms

Scenario:
Retracted package should not be available for upgrade
43s 292ms 10

When I install old package "rute-dummy=2.0-1.2" on this "sle_minion" 2s 284ms

And I refresh packages list via spacecmd on "sle_minion" 9s 140ms

And I wait until refresh package list on "sle_minion" is finished 12s 13ms

And I am on the "Software" page of this "sle_minion" 1s 376ms

And I follow "Packages" 411ms

And I follow "Upgrade" 566ms

Then I should not see a "rute-dummy-2.1-1.1" text 104ms

When I remove package "rute-dummy" from this "sle_minion" 2s 11ms

And I refresh packages list via spacecmd on "sle_minion" 6s 217ms

And I wait until package "rute-dummy" is removed from "sle_minion" via spacecmd 9s 165ms

Scenario:
Retracted patch should not affect any system
39s 261ms 13

When I install package "rute-dummy=2.0-1.2" on this "sle_minion" 2s 307ms

And I refresh packages list via spacecmd on "sle_minion" 8s 254ms

And I wait until refresh package list on "sle_minion" is finished 10s 840ms

And I follow the left menu "Software > Channel List > All" 183ms

And I follow "Show All Child Channels" 64ms

And I follow "Fake-RPM-SUSE-Channel" 600ms

And I follow "Patches" in the content area 69ms

And I follow "rute-dummy-0817" 505ms

And I follow "Affected Systems" 378ms

Then I should see a "No systems." text 59ms

When I remove package "rute-dummy" from this "sle_minion" 2s 170ms

And I refresh packages list via spacecmd on "sle_minion" 6s 511ms

And I wait until package "rute-dummy" is removed from "sle_minion" via spacecmd 7s 315ms

Scenario:
Target systems for stable packages should not be empty
2s 751ms 7

When I follow the left menu "Software > Channel List > All" 179ms

And I follow "Show All Child Channels" 54ms

And I follow "Fake-RPM-SUSE-Channel" 775ms

And I follow "Packages" in the content area 72ms

And I follow "rute-dummy-2.0-1.2.x86_64" 750ms

And I follow "Target Systems" 771ms

And I refresh page until I see "sle_minion" hostname as text 147ms

Scenario:
Target systems for retracted packages should be empty
11s 741ms 7

When I follow the left menu "Software > Channel List > All" 134ms

And I follow "Show All Child Channels" 57ms

And I follow "Fake-RPM-SUSE-Channel" 586ms

And I follow "Packages" in the content area 68ms

And I follow "rute-dummy-2.1-1.1.x86_64" 568ms

And I follow "Target Systems" 300ms

Then I should not see "sle_minion" hostname 10s 25ms

Scenario:
Retracted packages in the patch detail
4s 911ms 15

When I follow the left menu "Patches > Patch List > All" 185ms

And I enter "dummy" as the filtered synopsis 47ms

And I click on the filter button 643ms

And I follow "rute-dummy-0815" 468ms

Then I should see a "Status: Retracted" text 63ms

When I go back 463ms

And I enter "dummy" as the filtered synopsis 50ms

And I click on the filter button 844ms

And I follow "rute-dummy-0816" 373ms

Then I should see a "Status: Stable" text 64ms

When I go back 471ms

And I enter "dummy" as the filtered synopsis 48ms

And I click on the filter button 674ms

And I follow "rute-dummy-0817" 448ms

Then I should see a "Status: Retracted" text 65ms

Scenario:
Retracted packages in the patches list
860ms 6

When I follow the left menu "Patches > Patch List > All" 85ms

And I enter "dummy" as the filtered synopsis 40ms

And I click on the filter button 679ms

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 14ms

And the table row for "rute-dummy-0817" should contain "retracted" icon 17ms

Scenario:
Retracted patches in the channel patches list
949ms 7

When I follow the left menu "Software > Channel List > All" 181ms

And I follow "Show All Child Channels" 68ms

And I follow "Fake-RPM-SUSE-Channel" 590ms

And I follow "Patches" in the content area 68ms

Then the table row for "rute-dummy-0815" should contain "retracted" icon 15ms

And the table row for "rute-dummy-0816" should not contain "retracted" icon 10ms

And the table row for "rute-dummy-0817" should contain "retracted" icon 13ms

Scenario:
Retracted packages in the channel packages list
824ms 7

When I follow the left menu "Software > Channel List > All" 70ms

And I follow "Show All Child Channels" 56ms

And I follow "Fake-RPM-SUSE-Channel" 575ms

And I follow "Packages" in the content area 66ms

Then the table row for "rute-dummy-2.0-1.1.x86_64" should contain "retracted" icon 24ms

Then the table row for "rute-dummy-2.0-1.2.x86_64" should not contain "retracted" icon 14ms

Then the table row for "rute-dummy-2.1-1.1.x86_64" should contain "retracted" icon 18ms

Scenario:
SSM: Retracted package should not be available for installation
2s 446ms 10

When I follow the left menu "Systems > System List > All" 179ms

And I click on the clear SSM button 60ms

And I check the "sle_minion" client 452ms

And I follow the left menu "Systems > System Set Manager > Overview" 557ms

And I follow "Packages" in the content area 60ms

And I follow "Install" 470ms

And I follow "Fake-RPM-SUSE-Channel" 443ms

Then I should see a "rute-dummy-2.0-1.2" text 86ms

And I should not see a "rute-dummy-2.1-1.1" text 85ms

And I click on the clear SSM button 49ms

@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 @test_issue
Feature:Correct timezone display 1m 10s 693ms 11

* Related GitHub Card: https://github.com/SUSE/spacewalk/issues/29840

Scenario:
Log in as admin user
2s 584ms 1

Given I am authorized for the "Admin" section 2s 584ms

Scenario:
Create a new user in a timezone different than server's timezone
1s 35ms 11

When I follow the left menu "Users > User List > Active" 179ms

And I follow "Create User" 280ms

And I enter "MalaysianUser" as "login" 63ms

And I enter "MalaysianUser" as "desiredpassword" 62ms

And I enter "MalaysianUser" as "desiredpasswordConfirm" 69ms

And I select "Mr." from "prefix" 54ms

And I enter "Test" as "firstNames" 61ms

And I enter "User" as "lastName" 56ms

And I enter "galaxy-noise@localhost" as "email" 73ms

And I select "(GMT+0800) Malaysia" from "timezone" 66ms

And I click on "Create Login" 67ms

Scenario:
Add roles for the Malaysian user
11s 431ms 9

When I follow the left menu "Users > User List > Active" 97ms

And I follow "MalaysianUser" 384ms

And the "role_satellite_admin" checkbox should be disabled 10s 10ms

And I check "role_org_admin" 82ms

And I check "role_system_group_admin" 75ms

And I check "role_channel_admin" 81ms

And I check "role_activation_key_admin" 76ms

And I check "role_config_admin" 75ms

And I click on "Update" 548ms

Scenario:
Login as the new Malaysian user
1s 937ms 2

Given I am authorized as "MalaysianUser" with password "MalaysianUser" 1s 926ms

Then I should see a "MalaysianUser" link 11ms

Scenario:
Schedule a remote script to run now and see the correct timezone details in history
33s 544ms 11

Given I am on the Systems overview page of this "sle_minion" 1s 706ms

When I follow "Remote Command" in the content area 77ms

And I enter as remote command this script in #!/bin/bash ls 51ms

And I click on "Schedule" 683ms

And I wait until I see "Remote Command has been scheduled successfully" text 80ms

And I follow "Events" in the content area 70ms

And I follow "Pending" in the content area 78ms

And I wait at most 180 seconds until I do not see "Remote Command on" text, refreshing the page 30s 164ms

And I follow "History" in the content area 68ms

And I follow first "scheduled by MalaysianUser" 500ms

Then I should see a "MYT" text 61ms

Scenario:
Login as the new Malaysian user if the previous scenario failed
561ms 2

Given I am authorized as "MalaysianUser" with password "MalaysianUser" 550ms

Then I should see a "MalaysianUser" link 11ms

Scenario:
Schedule a remote script in the future and see the correct timezone as a pop up
2s 494ms 6

Given I am on the Systems overview page of this "sle_minion" 1s 671ms

When I follow "Remote Command" in the content area 69ms

And I enter as remote command this script in #!/bin/bash ls 55ms

And I enter "00:00" as "date_timepicker_widget_input" 74ms

And I click on "Schedule" 546ms

Then I should see a "00:00:00 MYT" text 76ms

Scenario:
Login as the new Malaysian user if the previous scenario failed
504ms 2

Given I am authorized as "MalaysianUser" with password "MalaysianUser" 496ms

Then I should see a "MalaysianUser" link 8ms

Scenario:
Cleanup: Log in as admin user again and remove scheduled actions
4s 232ms 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 493ms

And I cancel all scheduled actions via API 1s 739ms

Scenario:
Cleanup: Remove role
11s 622ms 9

When I follow the left menu "Users > User List > Active" 214ms

And I follow "MalaysianUser" 420ms

And I uncheck "role_org_admin" 10s 116ms

And I click on "Update" 778ms

Then I should see "role_org_admin" as unchecked 16ms

And I should see "role_system_group_admin" as checked 18ms

And I should see "role_channel_admin" as checked 18ms

And I should see "role_activation_key_admin" as checked 18ms

And I should see "role_config_admin" as checked 19ms

Scenario:
Cleanup: Delete user
743ms 1

When I delete user "MalaysianUser" 743ms

@scope_ansible @sle_minion @test_issue
Feature:Operate an Ansible control node in a normal minion 12m 11s 554ms 16 1 2

* Related GitHub Card: https://github.com/SUSE/spacewalk/issues/29691

Scenario:
Log in as org admin user
455ms 1

Given I am authorized for the "Admin" section 455ms

Scenario:
Pre-requisite: Deploy test playbooks and inventory file
4s 243ms 1

When I deploy testing playbooks and inventory files to "sle_minion" 4s 243ms

@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 246ms 5

Given I am on the Systems overview page of this "sle_minion" 958ms

When I follow "Properties" in the content area 81ms

And I check "ansible_control_node" 86ms

And I click on "Update Properties" 2s 22ms

Then I wait until I see "Ansible Control Node type has been applied." text 98ms

Scenario:
Apply highstate and check that Ansible is installed
57s 886ms 5

Given I am on the Systems overview page of this "sle_minion" 987ms

When I follow "States" in the content area 70ms

And I click on "Apply Highstate" 59ms

And I wait until event "Apply highstate scheduled" is completed 55s 859ms

Then "ansible" should be installed on "sle_minion" 909ms

Scenario:
The Ansible tab appears in the system overview page
1s 322ms 3

Given I am on the Systems overview page of this "sle_minion" 1s 181ms

When I follow "Ansible" in the content area 80ms

Then I should see a "Ansible Control Node Configuration" text 61ms

Scenario:
Configure some inventory and playbooks path
1s 463ms 7

Given I am on the Systems overview page of this "sle_minion" 940ms

When I follow "Ansible" in the content area 62ms

Then I should see a "Ansible Control Node Configuration" text 59ms

And I enter "/srv/playbooks/" as "new_playbook_path_input" 181ms

And I click on "new_playbook_path_save" 57ms

And I enter "/srv/playbooks/orion_dummy/hosts" as "new_inventory_path_input" 100ms

And I click on "new_inventory_path_save" 62ms

Scenario:
Display inventories
4m 35s 76ms 6 1

Given I am on the Systems overview page of this "sle_minion" 1s 551ms

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 242ms

And I click on the inventory accordion for "/srv/playbooks/orion_dummy/hosts" 51ms

Then I wait until I see "myself" text, refreshing the page 4m 13s 47ms 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'

20s 56ms Show Info + 
14:42:15:000 - 14:46:31:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/systems/details/ansible/inventories?sid=1000010020&
Screenshot +

Scenario:
Discover playbooks and display them
7s 48ms 7

Given I am on the Systems overview page of this "sle_minion" 940ms

When I follow "Ansible" in the content area 79ms

And I follow "Playbooks" in the content area 63ms

And I wait until I see "/srv/playbooks" text 251ms

And I click on "/srv/playbooks" 56ms

Then I wait until I see "/srv/playbooks/orion_dummy/playbook_orion_dummy.yml" text 5s 589ms

And I wait until I see "/srv/playbooks/basic_tests.yml" text 66ms

Scenario:
Run a playbook using custom inventory
49s 675ms 13

Given I am on the Systems overview page of this "sle_minion" 948ms

When I follow "Ansible" in the content area 65ms

And I follow "Playbooks" in the content area 61ms

And I wait until I see "/srv/playbooks" text 430ms

And I click on "/srv/playbooks" 49ms

And I wait until I see "/srv/playbooks/orion_dummy/playbook_orion_dummy.yml" text 5s 565ms

And I click on "orion_dummy/playbook_orion_dummy.yml" 59ms

And I wait until I see "Playbook Content" text 1s 255ms

And I select "/srv/playbooks/orion_dummy/hosts" from "inventory-path-select" 1s 128ms

And I click on "Schedule" 70ms

Then I should see a "Playbook execution has been scheduled" text 373ms

And I wait until event "Execute playbook 'playbook_orion_dummy.yml' scheduled" is completed 38s 845ms

And file "/tmp/file.txt" should exist on "sle_minion" 822ms

Scenario:
Run the basic tests playbook
45s 146ms 19

Given I am on the Systems overview page of this "sle_minion" 891ms

When I follow "Ansible" in the content area 81ms

And I follow "Playbooks" in the content area 63ms

And I wait until I see "/srv/playbooks" text 248ms

And I click on "/srv/playbooks" 57ms

And I wait until I see "/srv/playbooks/basic_tests.yml" text 5s 377ms

And I click on "basic_tests.yml" 61ms

And I wait until I see "Playbook Content" text 1s 187ms

And I click on "Schedule" 71ms

And I wait until I see "Playbook execution has been scheduled" text 470ms

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 536ms

When I follow "1 system" 276ms

And I wait until I see the system name of "sle_minion" 68ms

And I follow this "sle_minion" link 446ms

Then I should see a "42" text 92ms

And I should see a "101010" text 74ms

And I should see a "(code 0)" text 71ms

Scenario:
Run the basic tests playbook while editing variables and changing their values
45s 915ms 21

Given I am on the Systems overview page of this "sle_minion" 1s 56ms

When I follow "Ansible" in the content area 70ms

And I follow "Playbooks" in the content area 65ms

And I wait until I see "/srv/playbooks" text 247ms

And I click on "/srv/playbooks" 57ms

And I wait until I see "/srv/playbooks/basic_tests.yml" text 5s 366ms

And I click on "basic_tests.yml" 60ms

And I wait until I see "Playbook Content" text 1s 79ms

And I click on "Edit variables" 87ms

And I enter data from table with value as field name 850ms
(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 304ms

And I wait for "2" seconds 2s

And I follow "scheduled" in the content area 76ms

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 458ms

When I follow "1 system" 295ms

And I wait until I see the system name of "sle_minion" 66ms

And I follow this "sle_minion" link 468ms

Then I should see a "4200" text 68ms

And I should see a "(code 0)" text 71ms

Scenario:
Run the basic tests playbook while editing the EMPTY variables and changing their values
46s 429ms 22

Given I am on the Systems overview page of this "sle_minion" 958ms

When I follow "Ansible" in the content area 77ms

And I follow "Playbooks" in the content area 66ms

And I wait until I see "/srv/playbooks" text 281ms

And I click on "/srv/playbooks" 58ms

And I wait until I see "/srv/playbooks/basic_tests.yml" text 5s 473ms

And I click on "basic_tests.yml" 59ms

And I wait until I see "Playbook Content" text 1s 90ms

And I click on "Edit variables" 86ms

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 485ms

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 468ms

When I follow "1 system" 292ms

And I wait until I see the system name of "sle_minion" 70ms

And I follow this "sle_minion" link 455ms

Then I should see a "42000" text 76ms

And I should see a "4242" text 80ms

And I should see a "(code 0)" text 69ms

@skip_if_github_validation
Scenario:
Run the basic tests playbook while editing the NULL variable and changing its value
45s 853ms 21

Given I am on the Systems overview page of this "sle_minion" 954ms

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 158ms

And I click on "/srv/playbooks" 58ms

And I wait until I see "/srv/playbooks/basic_tests.yml" text 5s 313ms

And I click on "basic_tests.yml" 60ms

And I wait until I see "Playbook Content" text 1s 97ms

And I click on "Edit variables" 84ms

And I enter data from table with value as field name 1s 10ms
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" 96ms

And I click on "Schedule" 68ms

And I wait until I see "Playbook execution has been scheduled" text 305ms

And I wait for "2" seconds 2s

And I follow "scheduled" in the content area 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 469ms

When I follow "1 system" 278ms

And I wait until I see the system name of "sle_minion" 67ms

And I follow this "sle_minion" link 452ms

Then I should see a "65536" text 79ms

And I should see a "(code 0)" text 82ms

@skip_if_github_validation
Scenario:
Run the basic tests playbook on SAVE operation of YAML editor with pre-crafted strings
45s 468ms 22

Given I am on the Systems overview page of this "sle_minion" 1s 189ms

When I follow "Ansible" in the content area 74ms

And I follow "Playbooks" in the content area 63ms

And I wait until I see "/srv/playbooks" text 339ms

And I click on "/srv/playbooks" 57ms

And I wait until I see "/srv/playbooks/basic_tests.yml" text 5s 556ms

And I click on "basic_tests.yml" 61ms

And I wait until I see "Playbook Content" text 965ms

And I click on "Edit variables" 84ms

And I click on "Edit YAML" 65ms

And I click on "Save" 98ms

And I click on "Schedule" 59ms

And I wait until I see "Playbook execution has been scheduled" text 311ms

And I wait for "2" seconds 2s

And I follow "scheduled" in the content area 68ms

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 445ms

When I follow "1 system" 294ms

And I wait until I see the system name of "sle_minion" 70ms

And I follow this "sle_minion" link 441ms

Then I should see a "42" text 77ms

And I should see a "101010" text 71ms

And I should see a "(code 0)" text 70ms

Scenario:
Run the basic tests playbook on SAVE operation of YAML editor with safe values
46s 145ms 26

Given I am on the Systems overview page of this "sle_minion" 1s 44ms

When I follow "Ansible" in the content area 75ms

And I follow "Playbooks" in the content area 66ms

And I wait until I see "/srv/playbooks" text 158ms

And I click on "/srv/playbooks" 57ms

And I wait until I see "/srv/playbooks/basic_tests.yml" text 5s 378ms

And I click on "basic_tests.yml" 59ms

And I wait until I see "Playbook Content" text 1s 9ms

And I click on "Edit variables" 86ms

And I enter data from table with value as field name 852ms
abc p1
def p2
ghi p3
jkl p4
16 * 16 * 16 p5

And I click on "Edit YAML" 70ms

And I click on "Save" 100ms

And I click on "Schedule" 61ms

And I wait until I see "Playbook execution has been scheduled" text 311ms

And I wait for "2" seconds 2s

And I follow "scheduled" in the content area 73ms

Then I wait until I see "1 system successfully completed this action" text or "1 system failed to complete this action" text, refreshing the page 33s 470ms

When I follow "1 system" 292ms

And I wait until I see the system name of "sle_minion" 67ms

And I follow this "sle_minion" link 461ms

Then I should see a "abc" text 76ms

And I should see a "def" text 84ms

And I should see a "ghi" text 73ms

And I should see a "jkl" text 69ms

And I should see a "4096" text 69ms

And I should see a "(code 0)" text 74ms

Scenario:
Cleanup: Disable Ansible and remove test playbooks and inventory file
15s 815ms 7

Given I am on the Systems overview page of this "sle_minion" 917ms

When I follow "Properties" in the content area 78ms

And I uncheck "ansible_control_node" 10s 92ms

And I click on "Update Properties" 1s 723ms

Then I should see a "System properties changed" text 96ms

And I remove package "orion-dummy" from this "sle_minion" without error control 2s 444ms

And I remove "/tmp/file.txt" from "sle_minion" 462ms

@susemanager
Scenario:
Cleanup: Unsubscribe SUSE minions from SLE-Module-Python3-15-SP7-Pool for x86_64
< 1ms 9

Given I am on the Systems overview page of this "sle_minion" 0s

When I follow "Software" in the content area 0s

And I follow "Software Channels" in the content area 0s

And I uncheck "SLE-Module-Python3-15-SP7-Pool for x86_64" by label 0s

And I click on "Next" 0s

And I click on "Confirm" 0s

And I wait until I see "Changing the channels has been scheduled." text 0s

And I follow "scheduled" 0s

And I wait until I see "1 system successfully completed this action" text, refreshing the page 0s

Scenario:
Cleanup: Apply highstate to disable the minion as an "Ansible control node"
40s 360ms 4

Given I am on the Systems overview page of this "sle_minion" 869ms

When I follow "States" in the content area 75ms

And I click on "Apply Highstate" 61ms

And I wait until event "Apply highstate scheduled" is completed 39s 354ms

@sle_minion @proxy
Feature:Move a minion from a proxy to direct connection 10m 59s 223ms 13

Scenario:
Log in as org admin user
1s 986ms 1

Given I am authorized 1s 986ms

Scenario:
Delete minion system profile before bootstrap
4m 8s 649ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 860ms

When I follow "Delete System" 752ms

Then I should see a "Confirm System Profile Deletion" text 61ms

When I click on "Delete Profile" 62ms

And I wait until I see "has been deleted" text 4m 4s 675ms

And I wait until Salt client is inactive on "sle_minion" 796ms

Then "sle_minion" should not be registered 439ms

Scenario:
Bootstrap a minion
1m 59s 19ms 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 77ms

When I enter the hostname of "sle_minion" as "hostname" 144ms

And I enter "22" as "port" 54ms

And I enter "root" as "user" 58ms

And I enter "linux" as "password" 63ms

And I select "1-SUSE-KEY-x86_64" from "activationKeys" 73ms

And I select the hostname of "proxy" from "proxies" if present 59ms

And I click on "Bootstrap" 59ms

And I wait until I see "Bootstrap process initiated." text 35s 428ms

And I wait until onboarding is completed for "sle_minion" 1m 22s 915ms

Scenario:
Check the new bootstrapped minion in System Overview page
4s 222ms 3

It took 4 seconds to contact the minion

When I follow the left menu "Salt > Keys" 134ms

Then I should see a "accepted" text 350ms

And the Salt master can reach "sle_minion" 3s 737ms

Scenario:
Check initial connection from minion to proxy
1s 238ms 4

Given I am on the Systems overview page of this "sle_minion" 1s 31ms

When I follow "Details" in the content area 71ms

And I follow "Connection" in the content area 65ms

Then I should see "proxy" short hostname 69ms

Scenario:
Check initial registration on proxy of minion
1s 332ms 4

Given I am on the Systems overview page of this "proxy" 1s 103ms

When I follow "Details" in the content area 59ms

And I follow "Proxy" in the content area 70ms

Then I should see "sle_minion" hostname 98ms

Scenario:
Change from proxy to direct connection
37s 35ms 11

Given I am on the Systems overview page of this "sle_minion" 1s 230ms

When I follow "Details" in the content area 60ms

And I follow "Connection" in the content area 62ms

And I follow "Change" in the content area 63ms

And I select "None" from "proxies" 69ms

And I click on "Change Proxy" 56ms

And I wait until I see "scheduled" text 274ms

And I follow "Events" 408ms

And I follow "History" 419ms

And I wait until I see the event "Apply states [bootstrap.set_proxy] scheduled" completed during last minute, refreshing the page 11s 468ms

And I wait until I see the event "Apply states [channels] scheduled" completed during last minute, refreshing the page 22s 919ms

Scenario:
Check direct connection
1s 189ms 4

Given I am on the Systems overview page of this "sle_minion" 1s 1ms

When I follow "Details" in the content area 62ms

And I follow "Connection" in the content area 63ms

Then I should see a "This system connects directly and not through a Proxy" text 62ms

Scenario:
Change connection back to a proxy via SSM
2m 1s 731ms 10

Given I wait for "120" seconds 2m

When I follow the left menu "Systems > System List > All" 133ms

And I click on the clear SSM button 63ms

And I check the "sle_minion" client 354ms

And I should see "1" systems selected for SSM 126ms

And I follow the left menu "Systems > System Set Manager > Overview" 477ms

And I follow "proxy server" in the content area 71ms

And I select the hostname of "proxy" from "proxies" if present 79ms

And I click on "Change Proxy" 58ms

And I wait until I see "scheduled" text 367ms

Scenario:
Check events on the minion
38s 297ms 5

Given I am on the Systems overview page of this "sle_minion" 2s 756ms

And I follow "Events" 560ms

And I follow "History" 426ms

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 542ms

Scenario:
Check registration on proxy of minion
1s 237ms 4

Given I am on the Systems overview page of this "proxy" 998ms

When I follow "Details" in the content area 69ms

And I follow "Proxy" in the content area 69ms

Then I should see "sle_minion" hostname 100ms

Scenario:
Check connection from minion to proxy
1s 250ms 4

Given I am on the Systems overview page of this "sle_minion" 1s 52ms

When I follow "Details" in the content area 63ms

And I follow "Connection" in the content area 65ms

Then I should see "proxy" short hostname 69ms

Scenario:
Check events history for failures on the minion
1m 22s 34ms 2

Given I am on the Systems overview page of this "sle_minion" 1s 46ms

Then I check for failed events on history event page 1m 20s 987ms

@ssh_minion @scope_salt_ssh @proxy
Feature:Move a SSH minion from a proxy to direct connection 7m 38s 368ms 11

Scenario:
Log in as org admin user
2s 753ms 1

Given I am authorized 2s 753ms

Scenario:
Delete minion system profile before bootstrap
19s 561ms 6

Given I am on the Systems overview page of this "ssh_minion" 2s 176ms

When I follow "Delete System" 488ms

Then I should see a "Confirm System Profile Deletion" text 65ms

When I click on "Delete Profile" 62ms

And I wait until I see "has been deleted" text 16s 279ms

Then "ssh_minion" should not be registered 488ms

Scenario:
Bootstrap a minion
2m 28s 393ms 11

The hostname of ssh_minion is uyuni-master-suse-sshminion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 81ms

Then I should see a "Bootstrap Minions" text 61ms

When I check "manageWithSSH" 90ms

And I enter the hostname of "ssh_minion" as "hostname" 147ms

And I enter "root" as "user" 64ms

And I enter "linux" as "password" 58ms

And I select "1-SUSE-SSH-KEY-x86_64" from "activationKeys" 72ms

And I select the hostname of "proxy" from "proxies" if present 65ms

And I click on "Bootstrap" 61ms

And I wait at most 480 seconds until I see "Bootstrap process initiated." text 45s 882ms

And I wait until onboarding is completed for "ssh_minion" 1m 41s 808ms

Scenario:
Check initial connection from minion to proxy
1s 274ms 4

Given I am on the Systems overview page of this "ssh_minion" 1s 58ms

When I follow "Details" in the content area 80ms

And I follow "Connection" in the content area 69ms

Then I should see "proxy" short hostname 66ms

Scenario:
Check initial registration on proxy of minion
1s 248ms 4

Given I am on the Systems overview page of this "proxy" 1s 18ms

When I follow "Details" in the content area 63ms

And I follow "Proxy" in the content area 70ms

Then I should see "ssh_minion" hostname 96ms

Scenario:
Change from proxy to direct connection
48s 583ms 10

Given I am on the Systems overview page of this "ssh_minion" 1s 97ms

When I follow "Details" in the content area 60ms

And I follow "Connection" in the content area 63ms

And I follow "Change" in the content area 67ms

And I select "None" from "proxies" 69ms

And I click on "Change Proxy" 59ms

And I wait until I see "scheduled" text 358ms

And I follow "Events" 411ms

And I follow "History" 446ms

And I wait until I see the event "Apply states [channels] scheduled" completed during last minute, refreshing the page 45s 948ms

Scenario:
Check direct connection
2s 83ms 4

Given I am on the Systems overview page of this "ssh_minion" 1s 899ms

When I follow "Details" in the content area 62ms

And I follow "Connection" in the content area 59ms

Then I should see a "This system connects directly and not through a Proxy" text 62ms

Scenario:
Change connection to a proxy
2m 48s 487ms 11

Given I wait for "120" seconds 2m

Given I am on the Systems overview page of this "ssh_minion" 1s 11ms

When I follow "Details" in the content area 64ms

And I follow "Connection" in the content area 60ms

And I follow "Change" in the content area 65ms

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 368ms

And I follow "Events" 395ms

And I follow "History" 418ms

And I wait until I see the event "Apply states [channels] scheduled" completed during last minute, refreshing the page 45s 971ms

Scenario:
Check registration on proxy of minion
1s 206ms 4

Given I am on the Systems overview page of this "proxy" 972ms

When I follow "Details" in the content area 63ms

And I follow "Proxy" in the content area 73ms

Then I should see "ssh_minion" hostname 96ms

Scenario:
Check connection from minion to proxy
1s 273ms 4

Given I am on the Systems overview page of this "ssh_minion" 1s 85ms

When I follow "Details" in the content area 62ms

And I follow "Connection" in the content area 60ms

Then I should see "proxy" short hostname 64ms

Scenario:
Check events history for failures on the minion
1m 3s 502ms 2

Given I am on the Systems overview page of this "ssh_minion" 1s 162ms

Then I check for failed events on history event page 1m 2s 340ms

Feature:Sanity check that all logfiles exist 27s 407ms 1

In order to be secure
As an authorized user
I want to watch different logfiles

Scenario:
All logfiles should be available
27s 407ms 9

Then I wait until file "/var/log/rhn/rhn_web_ui.log" exists on server 4s 815ms

And I wait until file "/var/log/rhn/rhn_web_api.log" exists on server 3s 128ms

And I wait until file "/var/log/rhn/rhn_web_frontend.log" exists on server 2s 599ms

And I wait until file "/var/log/rhn/rhn_taskomatic_daemon.log" exists on server 2s 488ms

And I wait until file "/var/log/rhn/search/rhn_search_daemon.log" exists on server 2s 586ms

And I wait until file "/var/log/rhn/search/rhn_search.log" exists on server 2s 507ms

And I wait until file "/var/log/rhn/reposync.log" exists on server 4s 244ms

And I wait until file "/var/log/salt/master" exists on server 2s 547ms

And I wait until file "/var/log/salt/api" exists on server 2s 490ms

@scope_cobbler
Feature:Run Cobbler Sync via WebUI 37s 536ms 6 1

Scenario:
Login as admin
2s 231ms 1

Given I am authorized for the "Admin" section 2s 231ms

Scenario:
Start Cobbler monitoring
15s 717ms 2

When I start local monitoring of Cobbler 13s 251ms

And I backup Cobbler settings file 2s 466ms

@uyuni
Scenario:
Check that the Cobbler Settings Page exists
795ms 7

When I follow the left menu "Admin > Manager Configuration > Cobbler" 509ms

Then I should see a "Uyuni Configuration - Cobbler. " text 64ms

And I should see a "Setup your Uyuni Cobbler settings below. " text 62ms

And I should see a "Cobbler sync is used to repair or rebuild the contents /srv/tftpboot or /srv/www/cobbler when manual modification of cobbler has occurred. " text 59ms

And I should see a "For more information refer to the 'cobbler' man page. " text 59ms

And I should see a "Run Cobbler Sync" text in the content area 22ms

And I should see a "Update" button 17ms

@susemanager
Scenario:
Check that the Cobbler Settings Page exists
< 1ms 7

When I follow the left menu "Admin > Manager Configuration > Cobbler" 0s

Then I should see a "SUSE Multi-Linux Manager Configuration - Cobbler. " text 0s

And I should see a "Setup your SUSE Multi-Linux Manager Cobbler settings below. " text 0s

And I should see a "Cobbler sync is used to repair or rebuild the contents /srv/tftpboot or /srv/www/cobbler when manual modification of cobbler has occurred. " text 0s

And I should see a "For more information refer to the 'cobbler' man page. " text 0s

And I should see a "Run Cobbler Sync" text in the content area 0s

And I should see a "Update" button 0s

Scenario:
Run Cobbler Sync via button and validate UI output
500ms 3

When I follow the left menu "Admin > Manager Configuration > Cobbler" 66ms

And I click on "Update" 355ms

Then I should see a "Cobbler Sync action was successfully executed. Look at /var/log/cobbler/*.log for more information" text 78ms

Scenario:
Run Cobbler Sync via button and verify task timestamp in Last Execution Times Page
10s 789ms 4

When I follow the left menu "Admin > Manager Configuration > Cobbler" 78ms

And I click on "Update" 319ms

And I follow the left menu "Admin > Task Engine Status > Last Execution Times" 376ms

Then I should see the correct timestamp for task "Cobbler Sync:" 10s 15ms

@skip_if_github_validation
Scenario:
Check for errors in Cobbler monitoring
7s 502ms 1

Then the local logs for Cobbler should not contain errors 7s 502ms

@skip_if_github_validation @scope_cobbler
Feature:Cobbler and distribution autoinstallation 2m 12s 863ms 26

Scenario:
Start Cobbler monitoring
16s 694ms 2

When I start local monitoring of Cobbler 14s 185ms

And I backup Cobbler settings file 2s 509ms

Scenario:
Log in as testing user
4s 347ms 2

Given I am authorized as "testing" with password "testing" 3s 87ms

And I am logged in via the Cobbler API as user "testing" with password "testing" 1s 259ms

Scenario:
Copy cobbler profiles on the server
7s 896ms 1

When I copy autoinstall mocked files on server 7s 896ms

Scenario:
Ask cobbler to create a distribution via API
635ms 2

Given cobblerd is running 2ms

When I create "testdistro" kickstart tree via the API 633ms

Scenario:
Create dummy profile
975ms 2

Given cobblerd is running 2ms

When I create a "testprofile" profile via the API using import file for "testdistro" distribution 973ms

Scenario:
Check cobbler created distro and profile
362ms 3

When I follow the left menu "Systems > Autoinstallation > Profiles" 220ms

Then I should see a "testprofile" text 74ms

And I should see a "testdistro" text 67ms

Scenario:
Create SUSE distribution with installer updates
2s 706ms 12

When I follow the left menu "Systems > Autoinstallation > Distributions" 74ms

And I follow "Create Distribution" 455ms

And I enter "SLE-15-FAKE" as "label" 61ms

And I enter "/var/autoinstall/SLES15-SP7-x86_64/DVD1/" as "basepath" 89ms

And I select "SLE-Product-SLES15-SP7-Pool for x86_64" from "channelid" 313ms

And I select "SUSE Linux Enterprise 15" from "installtype" 59ms

And I click on "Create Autoinstallable Distribution" 1s 69ms

And I wait until I see "Autoinstallable Distribution Created" text 70ms

Then I should see a "Autoinstallable Distributions" text 73ms

And I should see a "SLE-15-FAKE" link 11ms

When I follow "SLE-15-FAKE" 404ms

Then I should see "self_update=http://" in field identified by "kernelopts" 22ms

Scenario:
Create a distribution via the UI
1s 638ms 8

When I follow the left menu "Systems > Autoinstallation > Distributions" 72ms

And I follow "Create Distribution" 462ms

When I enter "fedora_kickstart_distro" as "label" 67ms

And I enter "/var/autoinstall/Fedora_12_i386/" as "basepath" 78ms

And I select "Fedora" from "installtype" 61ms

And I click on "Create Autoinstallable Distribution" 813ms

Then I should see a "Autoinstallable Distributions" text 70ms

And I should see a "fedora_kickstart_distro" link 12ms

Scenario:
Create a distribution via the API, without kernel options
781ms 3

When I create "fedora_kickstart_distro_api" kickstart tree via the API 693ms

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
1s 237ms 3

When I create a kickstart tree with kernel options via the API 1s 160ms

When I follow the left menu "Systems > Autoinstallation > Distributions" 66ms

Then I should see a "fedora_kickstart_distro_kernel_api" link 11ms

Scenario:
Update a distribution via the API
1s 309ms 6

When I update a kickstart tree via the API 721ms

When I follow the left menu "Systems > Autoinstallation > Distributions" 66ms

And I follow "fedora_kickstart_distro_api" 408ms

Then option "Generic RPM" is selected as "installtype" 72ms

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 367ms 10

When I follow the left menu "Systems > Autoinstallation > Profiles" 69ms

And I follow "Create Kickstart Profile" 396ms

When I enter "fedora_kickstart_profile" as "kickstartLabel" 72ms

And I click on "Next" 58ms

And I click on "Next" 637ms

And I enter "linux" as "rootPassword" 50ms

And I enter "linux" as "rootPasswordConfirm" 54ms

And I click on "Finish" 1s 934ms

Then I should see a "Autoinstallation: fedora_kickstart_profile" text 80ms

And I should see a "Autoinstallation Details" link 11ms

Scenario:
Upload a profile via the UI
2s 691ms 8

When I follow the left menu "Systems > Autoinstallation > Profiles" 72ms

And I follow "Upload Kickstart/AutoYaST File" 502ms

When I enter "fedora_kickstart_profile_upload" as "kickstartLabel" 78ms

And I select "fedora_kickstart_distro" from "kstreeId" 44ms

And I attach the file "/example.ks" to "fileUpload" 33ms

And I click on "Create" 1s 767ms

Then I should see a "Autoinstallation: fedora_kickstart_profile_upload" text 98ms

And I should see a "Autoinstallation Details" text 93ms

Scenario:
Add an unprovisioned range to the created profile
2s 473ms 13

When I follow the left menu "Systems > Autoinstallation > Profiles" 72ms

And I follow "fedora_kickstart_profile" 573ms

And I follow "Unprovisioned Autoinstallation" 396ms

And I enter "10" as "octet1a" 48ms

And I enter "10" as "octet1b" 51ms

And I enter "0" as "octet1c" 49ms

And I enter "100" as "octet1d" 52ms

And I enter "10" as "octet2a" 49ms

And I enter "10" as "octet2b" 54ms

And I enter "0" as "octet2c" 48ms

And I enter "200" as "octet2d" 50ms

And I click on "Add IP Range" 953ms

Then I should see a "Successfully added IP Range" text 71ms

Scenario:
Add a variable to the uploaded profile
2s 312ms 7

When I follow the left menu "Systems > Autoinstallation > Profiles" 71ms

And I follow "fedora_kickstart_profile_upload" 768ms

And I follow "Variables" 376ms

And I enter "my_var=A_Test_String" as "variables" 69ms

And I click on "Update Variables" 459ms

And I follow "Autoinstallation File" 502ms

Then I should see a "A_Test_String" text 65ms

Scenario:
Add a kernel option to the created profile
4s 803ms 5

When I follow the left menu "Systems > Autoinstallation > Profiles" 98ms

And I follow "fedora_kickstart_profile" 548ms

And I enter "kernel_option=a_value" as "kernel_options" 78ms

And I click on "Update" 1s 84ms

And I wait until file "/srv/tftpboot/pxelinux.cfg/default" contains "kernel_option=a_value" on server 2s 993ms

Scenario:
Add a kernel option to the uploaded profile
4s 557ms 5

When I follow the left menu "Systems > Autoinstallation > Profiles" 73ms

And I follow "fedora_kickstart_profile_upload" 580ms

And I enter "kernel_option2=a_value2" as "kernel_options" 72ms

And I click on "Update" 1s 256ms

And I wait until file "/srv/tftpboot/pxelinux.cfg/default" contains "kernel_option2=a_value2" on server 2s 574ms

Scenario:
Check default snippets
1s 355ms 6

When I follow the left menu "Systems > Autoinstallation > Autoinstallation Snippets" 81ms

And I follow "Default Snippets" 294ms

And I enter "spacewalk/sles_no_signature_checks" as the filtered snippet name 91ms

And I click on the filter button 486ms

And I follow "spacewalk/sles_no_signature_checks" 385ms

Then I should see "<signature-handling>" in the textarea 16ms

Scenario:
Create a snippet
992ms 6

When I follow the left menu "Systems > Autoinstallation > Autoinstallation Snippets" 71ms

And I follow "Create Snippet" 356ms

And I enter "created_test_snippet" as "name" 65ms

And I enter "<test_element>a text string</test_element>" in the editor 4ms

And I click on "Create Snippet" 418ms

Then I should see a "created_test_snippet created successfully." text 76ms

Scenario:
Delete a snippet
1s 219ms 5

When I follow the left menu "Systems > Autoinstallation > Autoinstallation Snippets" 73ms

And I follow "created_test_snippet" 323ms

And I follow "Delete Snippet" 311ms

And I click on "Delete Snippet" 448ms

Then I should see a "created_test_snippet deleted successfully." text 62ms

Scenario:
Test for PXE environment files
19s 116ms 8

Given cobblerd is running 13ms

When I wait until file "/srv/tftpboot/pxelinux.cfg/default" exists on server 2s 503ms

And I wait until file "/srv/tftpboot/pxelinux.cfg/default" contains "inst.ks=.*fedora_kickstart_profile:1" on server 2s 632ms

And I wait until file "/srv/tftpboot/pxelinux.cfg/default" contains "inst.ks=.*fedora_kickstart_profile_upload:1" on server 2s 499ms

And I wait until file "/srv/tftpboot/images/fedora_kickstart_distro:1:SUSETest/initrd.img" exists on server 2s 495ms

And I wait until file "/srv/tftpboot/images/fedora_kickstart_distro:1:SUSETest/vmlinuz" exists on server 2s 520ms

And I wait until file "/srv/tftpboot/menu.c32" exists on server 4s 160ms

And I wait until file "/srv/tftpboot/pxelinux.0" exists on server 2s 291ms

Scenario:
Trigger the creation of a cobbler system record
8s 552ms 7

When I clear the caches on the server 2s 972ms

And I am on the Systems overview page of this "sle_minion" 1s 17ms

And I follow "Provisioning" 666ms

And I click on profile "testprofile" 52ms

And I click on "Create PXE installation configuration" 1s 138ms

Then I should see a "System record created" text 87ms

And I wait until file "/srv/tftpboot/pxelinux.cfg/01-*" contains "autoyast=" on server 2s 617ms

Scenario:
Create a cobbler system record via API
15s 17ms 5

When I create a system record 821ms

And I wait until file "/srv/tftpboot/pxelinux.cfg/01-00-22-22-77-ee-cc" contains "inst.ks=.*testserver:1" on server 4s 556ms

Then the cobbler report should contain "testserver.example.com" for cobbler system name "testserver:1" 3s 218ms

And the cobbler report should contain "1.1.1.1" for cobbler system name "testserver:1" 3s 191ms

And the cobbler report should contain "00:22:22:77:ee:cc" for cobbler system name "testserver:1" 3s 230ms

Scenario:
Cleanup: delete test profiles and distributions using API
15s 30ms 12

When I wait for "10" seconds 10s

When I delete profile and distribution using the API for "testdistro" kickstart tree 570ms

When I delete profile and distribution using the API for "fedora_kickstart_distro" kickstart tree 597ms

When I delete profile and distribution using the API for "fedora_kickstart_distro_api" kickstart tree 1s 492ms

When I delete profile and distribution using the API for "fedora_kickstart_distro_kernel_api" kickstart tree 1s 471ms

When I delete profile and distribution using the API for "SLE-15-FAKE" kickstart tree 461ms

When I follow the left menu "Systems > Autoinstallation > Distributions" 142ms

And I should not see a "testdistro" text 61ms

And I should not see a "fedora_kickstart_distro" text 57ms

And I should not see a "fedora_kickstart_distro_api" text 58ms

And I should not see a "fedora_kickstart_distro_kernel_api" text 58ms

And I should not see a "SLE-15-FAKE" text 58ms

@flaky
Scenario:
Check for errors in Cobbler monitoring
12s 782ms 2

When I wait for "5" seconds 5s

Then the local logs for Cobbler should not contain errors 7s 782ms

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 33s 866ms 19

Builds several ISOs with Cobbler and checks the configuration files and ISOs afterwards.

Scenario:
Start Cobbler monitoring
14s 392ms 2

When I start local monitoring of Cobbler 11s 893ms

And I backup Cobbler settings file 2s 498ms

Scenario:
Log in as testing user in the Cobbler buildiso context
1s 176ms 2

Given I am authorized as "testing" with password "testing" 457ms

And I am logged in via the Cobbler API as user "testing" with password "testing" 719ms

Scenario:
Copy cobbler profiles on the server in the Cobbler buildiso context
8s 202ms 1

When I copy autoinstall mocked files on server 8s 202ms

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
263ms 4

Given distro "buildisodistro" exists 4ms

When I create profile "orchid" for distro "buildisodistro" 77ms

And I create profile "flame" for distro "buildisodistro" 77ms

And I create profile "pearl" for distro "buildisodistro" 103ms

Scenario:
Check cobbler created a distro and profiles in the Cobbler buildiso context
472ms 5

When I follow the left menu "Systems > Autoinstallation > Profiles" 187ms

Then I should see a "buildisodistro" text 73ms

And I should see a "orchid" text 71ms

And I should see a "flame" text 70ms

And I should see a "pearl" text 69ms

Scenario:
Create dummy system in the Cobbler buildiso context
4s 179ms 3

Given profile "orchid" exists 9ms

When I create system "testsystem" for profile "orchid" 53ms

And I add the Cobbler parameter "name-servers" with value "9.9.9.9" to item "system" with name "testsystem" 4s 116ms

Scenario:
Prepare the Cobbler buildiso context
7s 421ms 1

When I prepare Cobbler for the buildiso command 7s 421ms

Scenario:
Run Cobbler buildiso with all profiles and check isolinux config file in the Cobbler buildiso context
37s 677ms 4

When I run Cobbler buildiso for distro "buildisodistro" and all profiles 23s 319ms

And I check Cobbler buildiso ISO "profile_all" with xorriso 7s 632ms

And I check the Cobbler parameter "nameserver" with value "9.9.9.9" in the isolinux.cfg 2s 533ms

And I cleanup xorriso temp files 4s 192ms

Scenario:
Run Cobbler buildiso with selected profile in the Cobbler buildiso context
16s 509ms 3

When I run Cobbler buildiso for distro "buildisodistro" and profile "orchid" 4s 422ms

And I check Cobbler buildiso ISO "orchid" with xorriso 7s 625ms

And I cleanup xorriso temp files 4s 461ms

Scenario:
Run Cobbler buildiso with selected profile and without dns entries in the Cobbler buildiso context
18s 958ms 3

When I run Cobbler buildiso for distro "buildisodistro" and profile "orchid" without dns entries 6s 860ms

And I check Cobbler buildiso ISO "orchid" with xorriso 9s 554ms

And I cleanup xorriso temp files 2s 543ms

Scenario:
Run Cobbler buildiso airgapped with all profiles in the Cobbler buildiso context
47s 182ms 3

When I run Cobbler buildiso "airgapped" for distro "buildisodistro" 34s 998ms

And I check Cobbler buildiso ISO "airgapped" with xorriso 7s 638ms

And I cleanup xorriso temp files 4s 545ms

Scenario:
Run Cobbler buildiso standalone with all profiles in the Cobbler buildiso context
44s 42ms 3

When I run Cobbler buildiso "standalone" for distro "buildisodistro" 33s 770ms

And I check Cobbler buildiso ISO "standalone" with xorriso 7s 608ms

And I cleanup xorriso temp files 2s 663ms

Scenario:
Cleanup: delete test system in the Cobbler buildiso context
504ms 2

Given I am authorized as "testing" with password "testing" 472ms

When I remove system "testsystem" 31ms

Scenario:
Cleanup: delete test profile in the Cobbler buildiso context
1s 565ms 8

Given I am authorized as "testing" with password "testing" 1s 22ms

And I remove profile "orchid" 111ms

And I remove profile "flame" 67ms

And I remove profile "pearl" 25ms

When I follow the left menu "Systems > Autoinstallation > Profiles" 156ms

Then I should not see a "orchid" text 63ms

And I should not see a "flame" text 58ms

And I should not see a "flame" text 60ms

Scenario:
Cleanup: delete test distro in the Cobbler buildiso context
708ms 4

Given I am authorized as "testing" with password "testing" 434ms

And I remove distro "buildisodistro" 50ms

And I follow the left menu "Systems > Autoinstallation > Profiles" 158ms

Then I should not see a "buildisodistro" text 65ms

Scenario:
Cleanup: Remove buildiso tmpdir and built ISO file in the Cobbler buildiso context
2s 939ms 1

When I cleanup after Cobbler buildiso 2s 939ms

@flaky
Scenario:
Check for errors in Cobbler monitoring
7s 611ms 1

Then the local logs for Cobbler should not contain errors 7s 611ms

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 27s 361ms 12

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 2ms

Scenario:
Copy cobbler profiles on the server
12s 995ms 2

When I copy autoinstall mocked files on server 9s 682ms

And I backup Cobbler settings file 3s 312ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 2ms

Scenario:
Log in as testing user
11s 898ms 1

Given I am authorized as "testing" with password "testing" 11s 898ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 4ms

Scenario:
Start Cobbler monitoring
12s 688ms 1

When I start local monitoring of Cobbler 12s 688ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 3ms

Scenario:
Create a Cobbler distribution via the UI
1s 996ms 10

When I follow the left menu "Systems > Autoinstallation > Distributions" 210ms

And I follow "Create Distribution" 363ms

When I enter "isedistro_ui" as "label" 64ms

And I enter "/var/autoinstall/Fedora_12_i386/" as "basepath" 79ms

And I select "Fedora" from "installtype" 66ms

And I click on "Create Autoinstallable Distribution" 972ms

Then I should see a "Autoinstallable Distributions" text 80ms

And I should see a "isedistro_ui" link 13ms

When I follow the left menu "Systems > Autoinstallation > Distributions" 75ms

Then I should see a "isedistro_ui" text 70ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 4ms

Scenario:
Create a Cobbler profile via the UI
3s 554ms 12

When I follow the left menu "Systems > Autoinstallation > Profiles" 72ms

And I follow "Create Kickstart Profile" 418ms

When I enter "iseprofile_ui" as "kickstartLabel" 59ms

And I click on "Next" 340ms

And I click on "Next" 423ms

And I enter "linux" as "rootPassword" 50ms

And I enter "linux" as "rootPasswordConfirm" 55ms

And I click on "Finish" 1s 904ms

Then I should see a "Autoinstallation: iseprofile_ui" text 76ms

And I should see a "Autoinstallation Details" link 12ms

When I follow the left menu "Systems > Autoinstallation > Profiles" 71ms

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
12s 44ms 7

When I follow the left menu "Systems > Autoinstallation > Profiles" 66ms

And I follow "iseprofile_ui" 601ms

And I follow "Variables" 318ms

And I enter "ise_ui_test=ISE_UI_TEST" as "variables" 76ms

And I click on "Update Variables" 404ms

And I refresh the page 10s 512ms

Then I should see a "ISE_UI_TEST" text 64ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 5ms

Scenario:
Create a Cobbler distribution via the UI in the XML-RPC context
1s 508ms 10

When I follow the left menu "Systems > Autoinstallation > Distributions" 71ms

And I follow "Create Distribution" 294ms

When I enter "isedistro_api" as "label" 57ms

And I enter "/var/autoinstall/Fedora_12_i386/" as "basepath" 78ms

And I select "Fedora" from "installtype" 48ms

And I click on "Create Autoinstallable Distribution" 729ms

Then I should see a "Autoinstallable Distributions" text 73ms

And I should see a "isedistro_api" link 11ms

When I follow the left menu "Systems > Autoinstallation > Distributions" 72ms

Then I should see a "isedistro_api" text 71ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 5ms

Scenario:
Create a Cobbler profile via the UI in the XML-RPC context
2s 747ms 12

When I follow the left menu "Systems > Autoinstallation > Profiles" 68ms

And I follow "Create Kickstart Profile" 380ms

When I enter "iseprofile_api" as "kickstartLabel" 58ms

And I click on "Next" 52ms

And I click on "Next" 328ms

And I enter "linux" as "rootPassword" 51ms

And I enter "linux" as "rootPasswordConfirm" 50ms

And I click on "Finish" 1s 520ms

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" 72ms

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
547ms 1

When I create a system record with name "isesystem_api" and kickstart label "iseprofile_api" 547ms

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 830ms 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 830ms
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 78ms 6

When I wait for "10" seconds 10s

When I delete profile and distribution using the API for "isedistro_ui" kickstart tree 447ms

When I delete profile and distribution using the API for "isedistro_api" kickstart tree 440ms

When I follow the left menu "Systems > Autoinstallation > Distributions" 71ms

And I should not see a "isedistro_ui" text 60ms

And I should not see a "isedistro_api" text 57ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 8ms

@flaky
Scenario:
Check for errors in Cobbler monitoring
14s 469ms 2

When I wait for "5" seconds 5s

Then the local logs for Cobbler should not contain errors 9s 469ms

@scope_visualization
Feature:Manage users 1m 38s 875ms 15 2

Scenario:
Log in as admin user
38s 82ms 1

Given I am authorized for the "Admin" section 38s 82ms

Scenario:
Display active users page
552ms 9

When I follow the left menu "Users > User List > Active" 223ms

Then I should see a "Active Users" text 197ms

And I should see a "Create User" link 11ms

And I should see a "User List" link in the left menu 24ms

And I should see a "Active" link in the left menu 26ms

And I should see a "Deactivated" link in the left menu 22ms

And I should see a "All" link in the left menu 24ms

And I should see a "admin" link in the table first column 10ms

And I should see a "Download CSV" link 10ms

Scenario:
Create a new user
8s 499ms 13

When I follow the left menu "Users > User List > Active" 69ms

And I follow "Create User" 302ms

And I enter "user1" as "login" 55ms

And I enter "user1" as "desiredpassword" 52ms

And I enter "user1" as "desiredpasswordConfirm" 56ms

And I select "Mr." from "prefix" 44ms

And I enter "Test" as "firstNames" 56ms

And I enter "User" as "lastName" 55ms

And I enter "galaxy-noise@localhost" as "email" 78ms

And I click on "Create Login" 7s 348ms

Then I should see a "Account user1 created, login information sent to galaxy-noise@localhost" text 184ms

And I should see a "user1" link 12ms

And I should see a "normal user" text 180ms

Scenario:
Login as the new user
1s 754ms 2

Given I am authorized as "user1" with password "user1" 1s 745ms

Then I should see a "user1" link 8ms

Scenario:
Access user details
3s 456ms 21

Given I am authorized for the "Admin" section 2s 208ms

When I follow the left menu "Users > User List > Active" 166ms

And I follow "user1" 314ms

Then I should see a "User Details" text 93ms

And I should see a "Delete User" link 11ms

And I should see a "Deactivate User" link 11ms

And I should see a "Details" link 14ms

And I should see a "System Groups" link 13ms

And I should see a "Systems" link in the content area 23ms

And I should see a "Channel Permissions" link 11ms

And I should see a "Preferences" link in the content area 21ms

And I should see a "Addresses" link 13ms

And I should see a "user1" text 73ms

And option "Mr." is selected as "prefix" 64ms

And I should see "Test" in field identified by "firstNames" 23ms

And I should see "User" in field identified by "lastName" 22ms

And I should see a "galaxy-noise@localhost" text 72ms

And I should see a "Administrative Roles" text 72ms

And I should see a "Roles:" text 77ms

And I should see a "Created:" text 72ms

And I should see a "Last Sign In:" text 73ms

@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 240ms 23

When I follow the left menu "Users > User List > Active" 71ms

And I follow "user1" 289ms

When the "role_satellite_admin" checkbox should be disabled 10s 5ms

And I check "role_org_admin" 100ms

And I check "role_system_group_admin" 75ms

And I check "role_channel_admin" 74ms

And I check "role_activation_key_admin" 74ms

And I check "role_config_admin" 73ms

And I click on "Update" 845ms

Then the "role_satellite_admin" checkbox should be disabled 10s 2ms

And I should see a "Uyuni Administrator" text 77ms

And I should see "role_org_admin" as checked 15ms

And I should see a "Organization Administrator" text 78ms

And I should see "role_system_group_admin" as checked 15ms

And I should see a "System Group Administrator" text 72ms

And I should see "role_channel_admin" as checked 30ms

And I should see a "Channel Administrator" text 71ms

And I should see "role_activation_key_admin" as checked 14ms

And I should see a "Activation Key Administrator" text 73ms

And I should see "role_config_admin" as checked 14ms

And I should see a "Configuration Administrator" text 72ms

And I should see "role_regular_user" as checked 18ms

And I should see a "Regular User" text 72ms

Scenario:
Verify user list
100ms 2

When I follow the left menu "Users > User List > Active" 72ms

Then table row for "user1" should contain "Organization Administrator" 28ms

Scenario:
Fail to deactivate organization administrator
2s 143ms 8

When I follow the left menu "Users > User List > Active" 68ms

And I follow "user1" 469ms

When I follow "Deactivate User" 407ms

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" 573ms

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 81ms

When I follow "Deactivated" 434ms

Then I should see a "No deactivated users." text 58ms

Scenario:
Remove role
11s 319ms 10

When I follow the left menu "Users > User List > Active" 66ms

And I follow "user1" 472ms

When I uncheck "role_org_admin" 10s 79ms

And I click on "Update" 595ms

Then I should see "role_org_admin" as unchecked 17ms

And I should see "role_system_group_admin" as checked 19ms

And I should see "role_channel_admin" as checked 19ms

And I should see "role_activation_key_admin" as checked 15ms

And I should see "role_config_admin" as checked 16ms

And I should see "role_regular_user" as checked 15ms

Scenario:
Deactivate ordinary user
2s 400ms 13

When I follow the left menu "Users > User List > Active" 69ms

And I follow "user1" 481ms

Then I should see "role_org_admin" as unchecked 26ms

When I follow "Deactivate User" 322ms

Then I should see a "This action will deactivate this user. This user will no longer be able to log in or perform actions unless it is reactivated." text 52ms

When I click on "Deactivate User" 564ms

Then I should see a "Active Users" text 185ms

And I should not see a "user1" link 8ms

When I follow "Deactivated" 295ms

Then I should see a "Deactivated Users" text 67ms

And I should see a "user1" link 8ms

When I follow "All" 305ms

Then I should see a "user1" link 11ms

@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 903ms 11

When I follow the left menu "Users > User List > Active" 67ms

And I follow "Deactivated" 444ms

And I follow "user1" 372ms

Then I should see a "Reactivate User" link 11ms

When I follow "Reactivate User" 408ms

Then I should see a "This action will allow this user to access Uyuni. This user will retain all permissions, roles, and data that he or she had before being deactivated." text 56ms

When I click on "Reactivate User" 59ms

Then I should see a "Active Users" text 192ms

And I should see a "user1" link 8ms

When I follow "Deactivated" 274ms

Then I should not see a "user1" link 5ms

Scenario:
Delete user
1s 724ms 8

When I follow the left menu "Users > User List > Active" 96ms

And I follow "user1" 472ms

When I follow "Delete User" 323ms

Then I should see a "Confirm User Deletion" text 52ms

And I should see a "This will delete this user permanently." text 49ms

When I click on "Delete User" 546ms

Then I should see a "Active Users" text 178ms

And I should not see a "user1" link 5ms

Scenario:
Display the CSV separator preference
2s 206ms 6

Given I am authorized as "testing" with password "testing" 1s 737ms

When I follow the left menu "Home > My Preferences" 67ms

Then I should see a "CSV Files" text 103ms

And I should see a "Configure a separator character to be used in downloadable CSV files:" text 101ms

And I should see a "Comma" text 98ms

And I should see a "Semicolon" text 97ms

Scenario:
Configure the CSV separator char to semicolon
1s 360ms 6

Given I am authorized as "testing" with password "testing" 557ms

When I follow the left menu "Home > My Preferences" 59ms

And I choose ";" 61ms

And I click on "Save Preferences" 551ms

Then I should see a "Preferences modified" text 108ms

And radio button "radio-semicolon" should be checked 21ms

Scenario:
Cleanup: configure the CSV separator char to comma
1s 129ms 6

Given I am authorized as "testing" with password "testing" 444ms

When I follow the left menu "Home > My Preferences" 59ms

And I choose "," 75ms

And I click on "Save Preferences" 421ms

Then I should see a "Preferences modified" text 107ms

And radio button "radio-comma" should be checked 20ms

@scope_visualization
Feature:Web UI - Main landing page menu, texts and links 13s 383ms 43

Scenario:
Log in as admin user
1s 801ms 1

Given I am authorized for the "Admin" section 1s 801ms

Scenario:
The Home menu
230ms 7

When I follow the left menu "Home" 56ms

And I should see a "Overview" link in the left menu 32ms

Then I should see a "Overview" text 56ms

And I should see a "Notification Messages" link in the left menu 21ms

And I should see a "User Account" link in the left menu 20ms

And I should see a "My Preferences" link in the left menu 20ms

And I should see a "My Organization" link in the left menu 23ms

Scenario:
The user account submenu under the Home menu
223ms 6

When I follow the left menu "Home > User Account" 64ms

Then I should see a "My Account" text 73ms

And I should see a "My Account" link in the left menu 22ms

And I should see a "Addresses" link in the left menu 20ms

And I should see a "Change Email" link in the left menu 21ms

And I should see a "Account Deactivation" link in the left menu 20ms

Scenario:
The my orginization menu under the Home menu
197ms 5

When I follow the left menu "Home > My Organization" 64ms

Then I should see a "Organization Configuration" text 63ms

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
182ms 5

When I follow the left menu "Salt" 54ms

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 25ms

Scenario:
The content lifeycle menu
161ms 4

When I follow the left menu "Content Lifecycle" 66ms

Then I should see a "Content Lifecycle Projects" text 52ms

And I should see a "Projects" link in the left menu 21ms

And I should see a "Filters" link in the left menu 21ms

Scenario:
The images menu
205ms 6

When I follow the left menu "Images" 54ms

Then I should see a "Images" text 59ms

And I should see a "Image List" link in the left menu 24ms

And I should see a "Build" link in the left menu 20ms

And I should see a "Profiles" link in the left menu 23ms

And I should see a "Stores" link in the left menu 22ms

Scenario:
The audit menu
217ms 6

When I follow the left menu "Audit" 53ms

Then I should see a "CVE Audit" text 70ms

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 25ms

And I should see a "OpenSCAP" link in the left menu 23ms

And I should see a "Confidential Computing" link in the left menu 21ms

Scenario:
The OpenSCAP submenu menu
202ms 5

When I follow the left menu "Audit > OpenSCAP" 71ms

Then I should see a "OpenSCAP Scans" text 66ms

And I should see a "All Scans" link in the left menu 22ms

And I should see a "XCCDF Diff" link in the left menu 20ms

And I should see a "Advanced Search" link in the left menu 21ms

Scenario:
The configuration menu
180ms 5

When I follow the left menu "Configuration" 55ms

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
169ms 4

When I follow the left menu "Configuration > Files" 69ms

Then I should see a "Centrally-Managed Configuration Files" text 54ms

And I should see a "Centrally Managed" link in the left menu 21ms

And I should see a "Locally Managed" link in the left menu 24ms

Scenario:
The systems submenu in the configuration menu
163ms 4

When I follow the left menu "Configuration > Systems" 65ms

Then I should see a "Managed Systems" text 53ms

And I should see a "Managed" link in the left menu 22ms

And I should see a "Target" link in the left menu 22ms

Scenario:
The schedule menu
213ms 6

When I follow the left menu "Schedule" 59ms

Then I should see a "Pending Actions" text 61ms

And I should see a "Pending Actions" link in the left menu 24ms

And I should see a "Failed Actions" link in the left menu 22ms

And I should see a "Archived Actions" link in the left menu 22ms

And I should see a "Action Chains" link in the left menu 21ms

Scenario:
The users menu
413ms 8

When I follow the left menu "Users" 54ms

Then I should see a "Active Users" text 198ms

And I should see a "Users" link in the left menu 35ms

And I should see a "User List" link in the left menu 36ms

And I should see a "Active" link in the left menu 22ms

And I should see a "Deactivated" link in the left menu 21ms

And I should see a "All" link in the left menu 23ms

And I should see a "System Group Configuration" link in the left menu 20ms

Scenario:
The admin menu
295ms 10

When I follow the left menu "Admin" 55ms

Then I should see a "Setup Wizard" text 74ms

And I should see a "Setup Wizard" link in the left menu 22ms

And I should see a "Organizations" link in the left menu 20ms

And I should see a "Users" link in the left menu 19ms

And I should see a "Manager Configuration" link in the left menu 21ms

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 20ms

Scenario:
The Setup Wizard submenu of the admin menu
133ms 4

When I follow the left menu "Admin > Setup Wizard" 66ms

Then I should see a "HTTP Proxy" link in the left menu 24ms

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
261ms 8

When I follow the left menu "Admin > Manager Configuration" 64ms

Then I should see a "Configuration - General Configuration" text 70ms

And I should see a "General" link in the left menu 21ms

And I should see a "Bootstrap Script" link in the left menu 20ms

And I should see a "Organizations" link in the left menu 17ms

And I should see a "Restart" link in the left menu 24ms

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
186ms 5

When I follow the left menu "Admin > Hub Configuration" 63ms

Then I should see a "Peripherals Configuration" text 58ms

And I should see a "Peripherals Configuration" link in the left menu 22ms

And I should see a "Hub Details" link in the left menu 20ms

And I should see a "Access Tokens" link in the left menu 20ms

Scenario:
The Task Engine Status submenu of the admin menu
112ms 3

When I follow the left menu "Admin > Task Engine Status" 67ms

Then 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:
The menu direct link accesses the first submenu level only
747ms 6

When I follow the left menu "Patches > Patch List" 118ms

Then I should see a "Patches Relevant to Your Systems" text in the content area 252ms

And I should not see a "The following patch list represents all patches accessible by your organization." text in the content area 218ms

When I follow the left menu "Configuration > Files" 125ms

Then I should see a "Centrally-Managed Configuration Files" text in the content area 16ms

And I should not see a "Locally Managed Configuration Files" text in the content area 15ms

Scenario:
Idempotency of complete menu path and direct link
302ms 4

When I follow the left menu "Software > Manage" 115ms

Then I should see a "Software Channel Management" text in the content area 55ms

When I follow the left menu "Software > Manage > Channels" 79ms

Then I should see a "Software Channel Management" text in the content area 52ms

Scenario:
Completeness of the side navigation bar and the content frame
533ms 13

When I am on the Systems page 288ms

Then I should see a "Systems" text in the content area 33ms

And I should see a "All" link in the left menu 24ms

And I should see a "Systems" link in the left menu 24ms

And I should see a "System Groups" link in the left menu 21ms

And I should see a "System Set Manager" link in the left menu 22ms

And I should see a "Advanced Search" link in the left menu 18ms

And I should see a "Activation Keys" link in the left menu 20ms

And I should see a "Stored Profiles" link in the left menu 20ms

And I should see a "Custom System Info" link in the left menu 20ms

And I should see a "Autoinstallation" link in the left menu 20ms

And I should see a "Download CSV" link 10ms

And I should see a Sign Out link 7ms

Scenario:
Sidebar link destination for Systems
245ms 7

When I follow the left menu "Systems > System List" 62ms

Then I should see a "All" link in the left menu 20ms

And I should see a "Virtual Systems" link in the left menu 21ms

And I should see a "Duplicate Systems" link in the left menu 21ms

And I should see a "System Currency" link in the left menu 21ms

And I should see a "System Types" link in the left menu 20ms

And I should see a "Systems" text 76ms

Scenario:
Sidebar link destination for Systems => Virtual Systems
152ms 3

When I follow the left menu "Systems > System List > Virtual Systems" 78ms

Then I should see a "Virtual Systems" text 70ms

And the current path is "/rhn/manager/systems/list/virtual" 3ms

Scenario:
Sidebar link destination for Systems => Duplicate Systems
208ms 7

When I follow the left menu "Systems > System List > Duplicate Systems" 82ms

Then I should see a "Duplicate Systems" text 71ms

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 13ms

And I should see a "Duplicate IPv6 Address" link 12ms

And I should see a "Duplicate MAC Address" link 13ms

Scenario:
Sidebar link destination for Systems => System Currency
176ms 3

When I follow the left menu "Systems > System List > System Currency" 73ms

Then I should see a "System Currency Report" text 100ms

And the current path is "/rhn/systems/SystemCurrency.do" 2ms

Scenario:
Sidebar link destination for Systems => System Types
646ms 7

When I follow the left menu "Systems > System List > System Types" 72ms

Then I should see a "System Types" text 113ms

And I should see a "Management:" text 133ms

And I should see a "Salt:" text 107ms

And I should see a "Foreign:" text 106ms

And I should see a "Virtualization Host:" text 111ms

And the current path is "/rhn/systems/SystemEntitlements.do" 2ms

Scenario:
Sidebar link destination for Systems => System Groups
189ms 4

When I follow the left menu "Systems > System Groups" 64ms

Then I should see a "System Groups" text 57ms

And I should see a "Create Group" link 11ms

And I should see a "Your organization has no system groups." text 55ms

Scenario:
Sidebar link destination for Systems => System Set Manager
711ms 12

When I follow the left menu "Systems > System Set Manager > Overview" 429ms

Then I should see a "System Set Manager" text 85ms

And I should see a "Task Log" link in the left menu 24ms

And I should see a "Overview" link in the content area 22ms

And I should see a "Systems" link in the content area 17ms

And I should see a "Patches" link in the content area 20ms

And I should see a "Packages" link in the content area 20ms

And I should see a "Groups" link in the content area 19ms

And I should see a "Channels" link in the content area 16ms

And I should see a "Configuration" link in the content area 16ms

And I should see a "Provisioning" link in the content area 19ms

And I should see a "Misc" link in the content area 19ms

Scenario:
Sidebar link destination for Systems => Advanced Search
142ms 2

When I follow the left menu "Systems > Advanced Search" 64ms

Then I should see a "Advanced Search" text 77ms

Scenario:
Sidebar link destination for Systems => Activation Keys
236ms 4

When I follow the left menu "Systems > Activation Keys" 63ms

Then I should see a "Activation Keys" text 82ms

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 78ms

Scenario:
Sidebar link destination for Systems => Stored Profiles
176ms 3

When I follow the left menu "Systems > Stored Profiles" 60ms

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
196ms 4

When I follow the left menu "Systems > Custom System Info" 67ms

Then I should see a "Custom System Info Keys" text 59ms

And I should see a "Create Key" link 8ms

And I should see a "No Custom Info Keys Found" text 60ms

Scenario:
Sidebar link destination for Systems => Autoinstallation
380ms 13

When I follow the left menu "Systems > Autoinstallation > Overview" 122ms

Then I should see a "Autoinstallation Overview" text 74ms

And I should see a "Profiles" link in the left menu 18ms

And I should see a "Unprovisioned" link in the left menu 23ms

And I should see a "GPG and SSL Keys" link in the left menu 22ms

And I should see a "Distributions" link in the left menu 23ms

And I should see a "File Preservation" link in the left menu 21ms

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
152ms 4

When I follow the left menu "Systems > Autoinstallation > Profiles" 71ms

Then I should see a "Autoinstallation Profiles" text 64ms

And I should see a "Create Kickstart Profile" link 8ms

And I should see a "Upload Kickstart/AutoYaST File" link 7ms

Scenario:
Sidebar link destination for Systems => Autoinstallation => Unprovisioned
195ms 3

When I follow the left menu "Systems > Autoinstallation > Unprovisioned" 73ms

Then I should see a "Unprovisioned Autoinstallation By IP" text 62ms

And I should see a "No Ip Ranges Found" text 59ms

Scenario:
Sidebar link destination for Systems => Autoinstallation => GPG and SSL Keys
218ms 5

When I follow the left menu "Systems > Autoinstallation > GPG and SSL Keys" 73ms

Then I should see a "GPG Public Keys and SSL Certificates" text 72ms

And I should see a "Create Stored Key/Cert" link 23ms

And I should see a "Reference Guide" link 37ms

And I should see a "RHN-ORG-TRUSTED-SSL-CERT" link 11ms

Scenario:
Sidebar link destination for Systems => Autoinstallation => Distributions
213ms 4

When I follow the left menu "Systems > Autoinstallation > Distributions" 74ms

Then I should see a "Autoinstallable Distributions" text 65ms

And I should see a "No autoinstallable distributions available." text 62ms

And I should see a "Create Distribution" link 11ms

Scenario:
Sidebar link destination for Systems => Autoinstallation => File Preservation
147ms 4

When I follow the left menu "Systems > Autoinstallation > File Preservation" 72ms

Then I should see a "File Preservation" text 56ms

And I should see a "Reference Guide" link 7ms

And I should see a "Create File Preservation List" link 10ms

Scenario:
Sidebar link destination for Systems => Autoinstallation => Autoinstallation Snippets
280ms 7

When I follow the left menu "Systems > Autoinstallation > Autoinstallation Snippets" 80ms

Then I should see a "Autoinstallation Snippets" text 65ms

And I should see a "No autoinstallation snippets found." text 60ms

And I should see a "Create Snippet" link 11ms

And I should see a "Default Snippets" link in the content area 21ms

And I should see a "Custom Snippets" link in the content area 20ms

And I should see a "All Snippets" link in the content area 19ms

Scenario:
"Create Kickstart Profile" page Systems => Autoinstallation => Profiles => Create Kickstart Profile
429ms 3

When I follow the left menu "Systems > Autoinstallation > Profiles" 68ms

And I follow "Create Kickstart Profile" 293ms

Then I should see a "Step 1: Create Kickstart Profile" text 67ms

Scenario:
"Upload Kickstart/AutoYaST File" page Systems => Autoinstallation => Profiles => Upload Kickstart/AutoYaST File
636ms 5

When I follow the left menu "Systems > Autoinstallation > Profiles" 66ms

And I follow "Upload Kickstart/AutoYaST File" 357ms

Then I should see a "Create Autoinstallation Profile" text 74ms

And I should see a "File Contents:" text 69ms

And I should see a "Autoinstallation Details" text 68ms

Scenario:
"Create kickstart distribution" page Systems => Autoinstallation => Distributions => create new kickstart distribution
509ms 4

When I follow the left menu "Systems > Autoinstallation > Distributions" 69ms

And I follow "Create Distribution" 303ms

Then I should see a "Create Autoinstallable Distribution" text 71ms

And I should see a "Distribution Label" text 65ms

@scope_configuration_channels
Feature:Check if source packages were successfully synced 5s 564ms 3

Scenario:
Log in as org admin user
1s 780ms 1

Given I am authorized 1s 780ms

Scenario:
Check sources for noarch package
1s 976ms 6

When I follow the left menu "Software > Channel List > All" 180ms

And I follow "Show All Child Channels" 58ms

And I follow "Fake-RPM-SUSE-Channel" 595ms

And I follow "Packages" 507ms

And I follow "virgo-dummy-2.0-1.1.noarch" 561ms

Then I should see a "virgo-dummy-2.0-1.1.src.rpm" text 72ms

Scenario:
Check sources for x86_64 package
1s 807ms 6

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" 585ms

And I follow "Packages" 493ms

And I follow "blackhole-dummy-1.0-1.1.x86_64" 496ms

Then I should see a "blackhole-dummy-1.0-1.1.src.rpm" text 72ms

@scope_visualization
Feature:Change the user's password 16s 7ms 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 751ms 1

Given I am authorized for the "Admin" section 1s 751ms

Scenario:
Change the password to a new password
1s 647ms 10

When I follow the left menu "Home > User Account > My Account" 132ms

And I enter "GoodPass" as "desiredpassword" 80ms

And I enter "GoodPass" as "desiredpasswordConfirm" 57ms

And I click on "Update" 408ms

Then I should see a "User information updated" text 73ms

When I sign out 301ms

And I enter "admin" as "username" 50ms

And I enter "GoodPass" as "password" 57ms

And I click on "Sign In" 55ms

Then I should be logged in 430ms

Scenario:
Revert the new password to a valid standard password
1s 618ms 10

When I follow the left menu "Home > User Account > My Account" 113ms

And I enter "admin" as "desiredpassword" 59ms

And I enter "admin" as "desiredpasswordConfirm" 48ms

And I click on "Update" 444ms

Then I should see a "User information updated" text 73ms

When I sign out 376ms

And I enter "admin" as "username" 49ms

And I enter "admin" as "password" 50ms

And I click on "Sign In" 54ms

Then I should be logged in 348ms

Scenario:
Try an invalid password
10s 989ms 10

When I follow the left menu "Home > User Account > My Account" 112ms

And I enter "A" as "desiredpassword" 48ms

And I enter "A" as "desiredpasswordConfirm" 46ms

And I click on "Update" 201ms

Then I should see a "Passwords must be at least 4 characters." text 72ms

When I sign out 357ms

And I enter "admin" as "username" 49ms

And I enter "A" as "password" 46ms

And I click on "Sign In" 53ms

Then I should not be authorized 10s

@scope_configuration_channels
Feature:Clone a channel 38s 968ms 12

Scenario:
Log in as org admin user
10s 774ms 1

Given I am authorized 10s 774ms

Scenario:
Clone a channel without patches
2s 589ms 10

When I follow the left menu "Software > Manage > Channels" 195ms

And I follow "Clone Channel" 556ms

And I select "Fake-RPM-SUSE-Channel" as the origin channel 72ms

And I choose "original" 52ms

And I click on "Clone Channel" 493ms

And I enter "Fake-Clone-RPM-SLES15SP7-Channel" as "Channel Name" 122ms

And I should see a "Create Software Channel" text 87ms

And I should see a "Original state of the channel" text 75ms

And I click on "Clone Channel" 849ms

Then I should see a "Fake-Clone-RPM-SLES15SP7-Channel" text 83ms

Scenario:
Check that this channel has no patches
1s 458ms 5

When I follow the left menu "Software > Manage > Channels" 75ms

And I follow "Fake-Clone-RPM-SLES15SP7-Channel" 581ms

And I follow "Patches" in the content area 70ms

And I follow "List/Remove Patches" 675ms

Then I should see a "There are no patches associated with this channel." text 55ms

Scenario:
Clone a channel with patches
1s 467ms 10

When I follow the left menu "Software > Manage > Channels" 67ms

And I follow "Clone Channel" 465ms

And I select "Fake-RPM-SUSE-Channel" as the origin channel 52ms

And I choose "current" 50ms

And I click on "Clone Channel" 429ms

And I enter "Fake-Clone-2-RPM-SLES15SP7-Channel" as "Channel Name" 117ms

And I should see a "Create Software Channel" text 80ms

And I should see a "Current state of the channel" text 74ms

And I click on "Clone Channel" 54ms

Then I should see a "Fake-Clone-2-RPM-SLES15SP7-Channel" text 76ms

Scenario:
Check that this channel has patches
1s 442ms 8

When I follow the left menu "Software > Manage > Channels" 72ms

And I follow "Fake-Clone-2-RPM-SLES15SP7-Channel" 569ms

And I follow "Patches" in the content area 58ms

And I follow "List/Remove Patches" 696ms

Then I should see a "CL-hoag-dummy-7890" link 12ms

And I should see a "CL-virgo-dummy-3456" link 11ms

And I should see a "CL-milkyway-dummy-2345" link 10ms

And I should see a "CL-andromeda-dummy-6789" link 11ms

Scenario:
Clone a channel with selected patches
5s 911ms 18

When I follow the left menu "Software > Manage > Channels" 67ms

And I follow "Clone Channel" 459ms

And I select "Fake-RPM-SUSE-Channel" as the origin channel 53ms

And I choose "select" 49ms

And I click on "Clone Channel" 462ms

And I enter "Fake-Clone-3-RPM-SLES15SP7-Channel" as "Channel Name" 120ms

And I should see a "Create Software Channel" text 80ms

And I should see a "Select patches" text 79ms

And I click on "Clone Channel" 1s 19ms

And I should see a "Fake-Clone-3-RPM-SLES15SP7-Channel" text 89ms

And I should see a "Channel Fake-Clone-3-RPM-SLES15SP7-Channel cloned from channel Fake-RPM-SUSE-Channel." text 86ms

And I should see a "You may now wish to clone the patches associated with Fake-RPM-SUSE-Channel." text 85ms

And I check the row with the "hoag-dummy-7890" link 62ms

And I check the row with the "virgo-dummy-3456" link 55ms

And I click on "Clone Patches" 2s 99ms

And I click on "Confirm" 1s 21ms

Then I should see a "CL-hoag-dummy-7890" link 10ms

And I should see a "CL-virgo-dummy-3456" link 7ms

Scenario:
Check that new patches exists
1s 465ms 8

When I follow the left menu "Patches > Patch List > All" 179ms

And I enter "dummy" as the filtered synopsis 50ms

And I click on the filter button 690ms

And I select "500" from "1154021400_PAGE_SIZE_LABEL" 502ms

Then I should see a "CL-hoag-dummy-7890" link 11ms

And I should see a "CL-virgo-dummy-3456" link 13ms

And I should see a "CL-milkyway-dummy-2345" link 8ms

And I should see a "CL-andromeda-dummy-6789" link 8ms

Scenario:
Check CL-hoag-dummy-7890 patches
1s 870ms 8

When I follow the left menu "Patches > Patch List > All" 74ms

And I enter "dummy" as the filtered synopsis 37ms

And I click on the filter button 690ms

And I select "500" from "1154021400_PAGE_SIZE_LABEL" 485ms

And I follow "CL-hoag-dummy-7890" 448ms

Then I should see a "CL-hoag-dummy-7890 - Security Advisory" text 61ms

And I should see a "mcalmer" text 59ms

And I should see a "https://bugzilla.opensuse.org/show_bug.cgi?id=704608" link 11ms

Scenario:
Check CM-virgo-dummy-3456 patches
1s 809ms 8

When I follow the left menu "Patches > Patch List > All" 66ms

And I enter "dummy" as the filtered synopsis 38ms

And I click on the filter button 660ms

And I select "500" from "1154021400_PAGE_SIZE_LABEL" 483ms

And I follow "CL-virgo-dummy-3456" 422ms

Then I should see a "CL-virgo-dummy-3456 - Bug Fix Advisory" text 64ms

And I should see a "mcalmer" text 61ms

And I should see a "CVE-1999-9998" link 11ms

Scenario:
Compare channel packages
2s 238ms 9

When I follow the left menu "Software > Manage > Channels" 198ms

And I follow "Fake-Clone-2-RPM-SLES15SP7-Channel" 579ms

And I follow "Packages" in the content area 71ms

And I follow "Compare" 559ms

And I select "Fake-Clone-3-RPM-SLES15SP7-Channel" from "selected_channel" 63ms

And I click on "View Packages" 566ms

Then I should see a "andromeda-dummy" text 94ms

And I should see a "2.0-1.1" link 16ms

And I should see a "This channel only" text 88ms

Scenario:
Cleanup: remove cloned channels
7s 884ms 21

When I follow the left menu "Software > Manage > Channels" 72ms

And I follow "Fake-Clone-RPM-SLES15SP7-Channel" 1s 362ms

And I follow "Delete Channel" 483ms

And I check "unsubscribeSystems" 97ms

And I click on "Delete Channel" 855ms

Then I should see a "Fake-Clone-RPM-SLES15SP7-Channel" text 64ms

And I should see a "has been deleted." text 59ms

Given I follow the left menu "Software > Manage > Channels" 73ms

When I follow "Fake-Clone-2-RPM-SLES15SP7-Channel" 582ms

And I follow "Delete Channel" 474ms

And I check "unsubscribeSystems" 66ms

And I click on "Delete Channel" 1s 605ms

Then I should see a "Fake-Clone-2-RPM-SLES15SP7-Channel" text 62ms

And I should see a "has been deleted." text 66ms

Given I follow the left menu "Software > Manage > Channels" 74ms

When I follow "Fake-Clone-3-RPM-SLES15SP7-Channel" 571ms

And I follow "Delete Channel" 393ms

And I check "unsubscribeSystems" 66ms

And I click on "Delete Channel" 723ms

Then I should see a "Fake-Clone-3-RPM-SLES15SP7-Channel" text 62ms

And I should see a "has been deleted." text 66ms

Scenario:
Cleanup: remove remaining systems from SSM after channel cloning tests
56ms 1

When I click on the clear SSM button 56ms

Feature:Manipulate activation keys 16s 208ms 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 786ms 1

Given I am authorized 1s 786ms

Scenario:
Create an activation key for i586
1s 811ms 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 305ms

And I enter "SUSE Test Key i586" as "description" 71ms

And I enter "SUSE-TEST-i586" as "key" 69ms

And I check "virtualization_host" 80ms

And I click on "Create Activation Key" 829ms

Then I should see a "Activation key SUSE Test Key i586 has been created." text 74ms

Scenario:
Change limit of the i586 activation key
1s 684ms 7

When I follow the left menu "Systems > Activation Keys" 71ms

And I follow "SUSE Test Key i586" 334ms

And I wait until I do not see "Loading..." text 403ms

And I enter "20" as "usageLimit" 50ms

And I click on "Update Activation Key" 723ms

Then I wait until I see "Activation key SUSE Test Key i586 has been modified." text 76ms

And I should see "20" in field identified by "usageLimit" 24ms

Scenario:
Change the base channel of the i586 activation key
2s 406ms 6

When I follow the left menu "Systems > Activation Keys" 60ms

And I follow "SUSE Test Key i586" 415ms

And I wait until I do not see "Loading..." text 489ms

And I select "Fake-Base-Channel-i586" from "selectedBaseChannel" 72ms

And I click on "Update Activation Key" 1s 295ms

Then I wait until I see "Activation key SUSE Test Key i586 has been modified." text 73ms

Scenario:
Delete the i586 activation key
1s 526ms 6

When I follow the left menu "Systems > Activation Keys" 65ms

And I follow "SUSE Test Key i586" in the content area 69ms

And I wait until I do not see "Loading..." text 488ms

And I follow "Delete Key" 330ms

And I click on "Delete Activation Key" 490ms

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
2s 315ms 12

When I follow the left menu "Systems > Activation Keys" 65ms

And I follow "Create Key" 326ms

And I wait until I do not see "Loading..." text 290ms

And I enter "SUSE Test PKG Key i586" as "description" 71ms

And I enter "SUSE-TEST-2-i586" as "key" 68ms

And I enter "20" as "usageLimit" 44ms

And I select "Fake-Base-Channel-i586" from "selectedBaseChannel" 51ms

And I click on "Create Activation Key" 919ms

And I follow "Packages" 317ms

And I enter "sed" as "packages" 48ms

And I click on "Update Activation Key" 54ms

Then I should see a "Activation key SUSE Test PKG Key i586 has been modified." text 57ms

Scenario:
Delete the i586 activation key with packages
985ms 5

When I follow the left menu "Systems > Activation Keys" 62ms

And I follow "SUSE Test PKG Key i586" in the content area 68ms

And I follow "Delete Key" 299ms

And I click on "Delete Activation Key" 471ms

Then I should see a "Activation key SUSE Test PKG Key i586 has been deleted." text 82ms

@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 571ms 12

When I follow the left menu "Systems > Activation Keys" 86ms

And I follow "Create Key" 247ms

And I wait until I do not see "Loading..." text 221ms

And I enter "SUSE Test PKG Key x86_64" as "description" 77ms

And I enter "SUSE-TEST-x86_64" as "key" 67ms

And I enter "20" as "usageLimit" 49ms

And I select "openSUSE Tumbleweed (x86_64)" from "selectedBaseChannel" 59ms

And I click on "Create Activation Key" 849ms

And I follow "Packages" 400ms

And I enter "sed" as "packages" 44ms

And I click on "Update Activation Key" 407ms

Then I should see a "Activation key SUSE Test PKG Key x86_64 has been modified." text 58ms

@scc_credentials
Scenario:
Delete the x86_64 activation key with packages
1s 119ms 5

When I follow the left menu "Systems > Activation Keys" 62ms

And I follow "SUSE Test PKG Key x86_64" in the content area 69ms

And I follow "Delete Key" 315ms

And I click on "Delete Activation Key" 591ms

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 782ms 4

Scenario:
List all activation keys
408ms 1

Then I should get some activation keys 408ms

Scenario:
Create activation key
1s 381ms 2

When I create an activation key with id "testkey", description "Key for testing", limit of 10 and contact method "default" 932ms

Then I should get the new activation key "1-testkey" 449ms

Scenario:
Activation key details
880ms 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" 460ms

Then I get the description "Key description" for the activation key "1-testkey" 420ms

Scenario:
Cleanup: delete activation key
1s 111ms 1

When I delete the activation key "1-testkey" 1s 111ms

@scope_visualization
Feature:Main landing page options and preferences 57s 82ms 10 2

Scenario:
Clear browser cookies for main landing page validation
17ms 1

When I clear browser cookies 17ms

Scenario:
Access the Login page
654ms 3

Given I am not authorized 457ms

When I go to the home page 176ms

Then I should see a "Sign In" text 19ms

@uyuni
Scenario:
Access the API Documentation
10s 564ms 4

Given I am not authorized 10s 202ms

When I go to the home page 155ms

And I follow "API Documentation" 157ms

Then I should see a "API Overview" text 49ms

@susemanager
Scenario:
Access the Copyright Notice
< 1ms 10

Given I am authorized 0s

When I follow the left menu "Help" 0s

And I switch to last opened window 0s

Then I should see a "SUSE Multi-Linux Manager Guides" text 0s

When I click on the Legal button 0s

And I wait until I see "Copyright Notice" text 0s

And I follow "Copyright Notice" 0s

Then I should see a "Copyright Notice" text 0s

And I should see a "SUSE Multi-Linux Manager LICENSE AGREEMENT" text 0s

When I close the last opened window 0s

@susemanager
Scenario:
Access the EULA
< 1ms 10

Given I am authorized 0s

When I follow the left menu "Help" 0s

And I switch to last opened window 0s

Then I should see a "SUSE Multi-Linux Manager Guides" text 0s

When I click on the Legal button 0s

And I wait until I see "End User License Agreement" text 0s

And I follow "End User License Agreement" 0s

Then I should see a "End User License Agreement" text 0s

And I should see a "End User License Agreement for SUSE Software" text 0s

When I close the last opened window 0s

Scenario:
Log into Uyuni
10s 861ms 6

Given I am not authorized 10s 195ms

When I go to the home page 132ms

And I enter "testing" as "username" 65ms

And I enter "testing" as "password" 58ms

And I click on "Sign In" 62ms

Then I should be logged in 346ms

Scenario:
Log out of Uyuni
13s 695ms 3

Given I am authorized 2s 916ms

When I sign out 774ms

Then I should not be authorized 10s 3ms

Scenario:
Top level bar
11s 697ms 7

Given I am authorized for the "Admin" section 10s 642ms

When I go to the home page 958ms

And I should see a "Manage" link 15ms

And I should see a "admin" text 51ms

And I should see a "SUSE Test" link 11ms

And I should see a "Preferences" link 11ms

And I should see a Sign Out link 6ms

Scenario:
Main menu as regular user
2s 502ms 15

Given I am authorized as "testing" with password "testing" 2s 342ms

Then I should see a "Home" link 11ms

And I should see a "Systems" link 14ms

And I should see a "Salt" link 10ms

And I should see a "Images" link 11ms

And I should see a "Patches" link 12ms

And I should see a "Software" link 10ms

And I should see a "Content Lifecycle" link 13ms

And I should see a "Audit" link 11ms

And I should see a "Configuration" link 13ms

And I should see a "Schedule" link 10ms

And I should see a "Users" link 11ms

And I should not see a "Admin" link 7ms

And I should see a "Help" link 10ms

And I should see a "External Links" link 10ms

Scenario:
Log in as admin user
2s 214ms 1

Given I am authorized for the "Admin" section 2s 214ms

Scenario:
Main menu as administrator
106ms 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 7ms

And I should see a "Patches" link 8ms

And I should see a "Software" link 7ms

And I should see a "Audit" link 7ms

And I should see a "Configuration" link 10ms

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 766ms 8

Given I am authorized 3s 108ms

Then I should see a "Tasks" text 752ms

And I should see a "Inactive Systems" text 258ms

And I should see a "Most Critical Systems" text 119ms

And I should see a "Recently Scheduled Actions" text 134ms

And I should see a "Relevant Security Patches" text 130ms

And I should see a "System Group Name" text 131ms

And I should see a "Recently Registered Systems" text 131ms

@scope_api
Feature:API "user" namespace 25s 336ms 5

Scenario:
List users
7s 535ms 2

When I call user.list_users() 7s 535ms

Then I should get at least user "admin" < 1ms

Scenario:
List roles
315ms 2

When I call user.list_roles() on user "admin" 315ms

Then I should get at least one role that matches "_admin" suffix < 1ms

Scenario:
Create user
15s 127ms 4

When I make sure "testuser" is not present 7s 341ms

And I call user.create() with login "testuser" 390ms

And I call user.list_users() 7s 395ms

Then I should get at least user "testuser" < 1ms

Scenario:
Role operations
1s 860ms 6

When I call user.add_role() on "testuser" with the role "org_admin" 353ms

And I call user.list_roles() on user "testuser" 437ms

Then I should get role "org_admin" < 1ms

When I call user.remove_role() on "testuser" with the role "org_admin" 538ms

And I call user.list_roles() on user "testuser" 530ms

Then I should not get role "org_admin" < 1ms

Scenario:
Cleanup: user tests
497ms 1

When I delete user "testuser" 497ms

@scope_salt
Feature:Endpoint to download packages 14s 972ms 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
3s 11ms 3

a94e0473dac5aba6efa9d39946eee06a9b961f91faa6904f1c96464b90396c1b

Given I have a valid token for organization "1" 2s 961ms

When I try to download "virgo-dummy-2.0-1.1.noarch.rpm" from channel "fake-rpm-suse-channel" 49ms

Then the download should get no error < 1ms

Scenario:
Download package, user with an invalid token for the org
28ms 3

a9323dd91532303ca9b93544eb1246874d048537b57eca5f9eedb892444a8d4bc366d4c8242db9c7dd237d7c2ee91c1b206add9ee85428fad59caedf9c324c5a

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" 27ms

Then the download should get a 403 response < 1ms

Scenario:
Download package, user with an expired valid token for the org
2s 533ms 3

a94e0473dac5aba6efa9d39946eee06a9b961f91faa6904f1c96464b90396c1b

Given I have an expired 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" 28ms

Then the download should get a 403 response < 1ms

Scenario:
Download package, user with an non expired valid token for the org
2s 555ms 3

a94e0473dac5aba6efa9d39946eee06a9b961f91faa6904f1c96464b90396c1b

Given I have a valid token expiring tomorrow for organization "1" 2s 522ms

When I try to download "virgo-dummy-2.0-1.1.noarch.rpm" from channel "fake-rpm-suse-channel" 32ms

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 553ms 3

a94e0473dac5aba6efa9d39946eee06a9b961f91faa6904f1c96464b90396c1b

Given I have a not yet usable valid token for organization "1" 2s 523ms

When I try to download "virgo-dummy-2.0-1.1.noarch.rpm" from channel "fake-rpm-suse-channel" 29ms

Then the download should get a 403 response < 1ms

Scenario:
Download package, user with a valid token for the org and specific channels
4s 264ms 3

a94e0473dac5aba6efa9d39946eee06a9b961f91faa6904f1c96464b90396c1b

Given I have a valid token for organization "1" and channel "foobar" 4s 224ms

When I try to download "virgo-dummy-2.0-1.1.noarch.rpm" from channel "fake-rpm-suse-channel" 39ms

Then the download should get a 403 response < 1ms

@scope_building_container_images @no_auth_registry
Feature:Advanced content management 23s 782ms 8

Scenario:
Log in as docker user
1s 645ms 1

Given I am authorized as "docker" with password "docker" 1s 645ms

Scenario:
Create an image store as Docker admin
1s 972ms 6

When I follow the left menu "Images > Stores" 124ms

And I follow "Create" 282ms

And I enter "docker_admin" as "label" 95ms

And I enter the URI of the registry as "uri" 144ms

And I click on "create-btn" 63ms

Then I wait until table row contains a "galaxy-registry" text 1s 262ms

@scc_credentials
Scenario:
Create a profile as Docker admin
3s 949ms 7

GITPROFILES: https://github.com/uyuni-project/uyuni.git#:testsuite/features/profiles/temporary

When I follow the left menu "Images > Profiles" 64ms

And I follow "Create" 470ms

And I enter "suse_docker_admin" as "label" 119ms

And I select "galaxy-registry" from "imageStore" 1s 139ms

And I select "1-SUSE-KEY-x86_64" from "activationKey" 1s 120ms

And I enter "Docker/serverhost" relative to profiles as "path" 977ms

And I click on "create-btn" 56ms

Scenario:
Create a user without rights nor roles
10s 960ms 2

New user norole created with roles:

Given I am authorized for the "Admin" section 1s 14ms

When I create a user with name "norole" and password "norole" with roles "" 9s 946ms

Scenario:
Log in as docker user
1s 672ms 1

Given I am authorized as "docker" with password "docker" 1s 672ms

@scc_credentials
Scenario:
Cleanup: remove Docker profile
1s 71ms 6

Given I am authorized as "docker" with password "docker" 558ms

When I follow the left menu "Images > Profiles" 105ms

And I check the row with the "suse_docker_admin" text 118ms

And I click on "Delete" 73ms

And I click on the red confirmation button 62ms

And I should see a "Image profile has been deleted." text 152ms

Scenario:
Cleanup: remove image store
441ms 5

When I follow the left menu "Images > Stores" 64ms

And I check the row with the "docker_admin" text 102ms

And I click on "Delete" 64ms

And I click on the red confirmation button 56ms

And I should see a "Image store has been deleted." text 154ms

Scenario:
Cleanup: delete no role user
2s 68ms 2

Given I am authorized for the "Admin" section 1s 158ms

When I delete user "norole" 909ms

@scope_visualization
Feature:Pick dates 18s 194ms 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
7s 468ms 2

Given I am authorized 1s 822ms

And I am on the Systems overview page of this "sle_minion" 5s 646ms

Scenario:
Date picker is by default set to today
10s 179ms 3

When I follow "Remote Command" in the content area 72ms

And I open the date picker 81ms

Then the date picker title should be the current month and year 10s 26ms

Scenario:
Picking a time sets the hidden fields
546ms 8

When I follow "Details" in the content area 82ms

And I follow "Remote Command" in the content area 55ms

And I enter "ls" as "Script" 97ms

And I pick "2022-08-27" as date 107ms

And I pick "17:30" as time 127ms

Then the date field should be set to "2022-08-27" 35ms

And the time field should be set to "17:30" 36ms

And the date picker should be closed 3ms

@scope_visualization
Feature:Work with Union and Intersection buttons in the group list 26s 737ms 16

Scenario:
Log in as org admin user
1s 776ms 1

Given I am authorized 1s 776ms

Scenario:
Create a sles group
1s 11ms 6

When I follow the left menu "Systems > System Groups" 126ms

When I follow "Create Group" 275ms

And I enter "sles" as "name" 48ms

And I enter "SLES systems" as "description" 59ms

And I click on "Create Group" 427ms

Then I should see a "System group sles created." text 73ms

Scenario:
Add systems to the sles group
2s 328ms 6

When I follow the left menu "Systems > System Groups" 63ms

When I follow "sles" 317ms

And I follow "Target Systems" 522ms

And I check the "sle_minion" client 60ms

And I click on "Add Systems" 1s 271ms

Then I should see a "added to sles server group." text 91ms

@rhlike_minion
Scenario:
Create a rhlike group
966ms 6

When I follow the left menu "Systems > System Groups" 58ms

When I follow "Create Group" 290ms

And I enter "rhlike" as "name" 63ms

And I enter "Red Hat-like systems" as "description" 60ms

And I click on "Create Group" 428ms

Then I should see a "System group rhlike created." text 65ms

@rhlike_minion
Scenario:
Add systems to the rhlike group
5s 552ms 6

When I follow the left menu "Systems > System Groups" 63ms

When I follow "rhlike" 305ms

And I follow "Target Systems" 470ms

And I check the "rhlike_minion" client 1s 860ms

And I click on "Add Systems" 2s 758ms

Then I should see a "1 systems were added to rhlike server group." text 93ms

@deblike_minion
Scenario:
Create a deblike group
996ms 6

When I follow the left menu "Systems > System Groups" 66ms

When I follow "Create Group" 295ms

And I enter "deblike" as "name" 48ms

And I enter "Debian-like systems" as "description" 59ms

And I click on "Create Group" 457ms

Then I should see a "System group deblike created." text 68ms

@deblike_minion
Scenario:
Add systems to the deblike group
7s 88ms 6

When I follow the left menu "Systems > System Groups" 63ms

When I follow "deblike" 309ms

And I follow "Target Systems" 451ms

And I check the "deblike_minion" client 5s 21ms

And I click on "Add Systems" 1s 147ms

Then I should see a "1 systems were added to deblike server group." text 94ms

Scenario:
Add the sles group to SSM
220ms 4

When I follow the left menu "Systems > System Groups" 60ms

When I click on "Use in SSM" in row "sles" 71ms

And I should see a "Selected Systems List" text 72ms

And I should see "sle_minion" as link 15ms

@rhlike_minion
Scenario:
Add a union of 2 groups to SSM - Red Hat-like
642ms 6

When I follow the left menu "Systems > System Groups" 57ms

When I check "sles" in the list 88ms

And I check "rhlike" in the list 56ms

And I click on "Work With Union" 414ms

And I should see "sle_minion" as link 10ms

And I should see "rhlike_minion" as link 13ms

@rhlike_minion
Scenario:
Add an intersection of 2 groups to SSM - Red Hat-like
676ms 6

When I follow the left menu "Systems > System Groups" 59ms

When I check "sles" in the list 60ms

And I check "rhlike" in the list 50ms

And I click on "Work With Intersection" 490ms

And I should not see a "sle_minion" link 7ms

And I should not see a "rhlike_minion" link 7ms

@deblike_minion
Scenario:
Add a union of 2 groups to SSM - Debian-like
745ms 6

When I follow the left menu "Systems > System Groups" 57ms

When I check "sles" in the list 49ms

And I check "deblike" in the list 54ms

And I click on "Work With Union" 559ms

And I should see "sle_minion" as link 10ms

And I should see "deblike_minion" as link 13ms

@deblike_minion
Scenario:
Add an intersection of 2 groups to SSM - Debian-like
569ms 6

When I follow the left menu "Systems > System Groups" 57ms

When I check "sles" in the list 51ms

And I check "deblike" in the list 50ms

And I click on "Work With Intersection" 397ms

And I should not see a "sle_minion" link 4ms

And I should not see a "deblike_minion" link 7ms

Scenario:
Cleanup: remove the sles group
1s 480ms 5

When I follow the left menu "Systems > System Groups" 58ms

When I follow "sles" in the content area 69ms

And I follow "Delete Group" in the content area 63ms

And I click on "Confirm Deletion" 54ms

Then I should see a "deleted" text 1s 234ms

@rhlike_minion
Scenario:
Cleanup: remove the rhlike group
1s 349ms 5

When I follow the left menu "Systems > System Groups" 63ms

When I follow "rhlike" in the content area 64ms

And I follow "Delete Group" in the content area 59ms

And I click on "Confirm Deletion" 1s 90ms

Then I should see a "deleted" text 71ms

@deblike_minion
Scenario:
Cleanup: remove the deblike group
1s 265ms 5

When I follow the left menu "Systems > System Groups" 65ms

When I follow "deblike" in the content area 61ms

And I follow "Delete Group" in the content area 62ms

And I click on "Confirm Deletion" 1s 20ms

Then I should see a "deleted" text 56ms

Scenario:
Cleanup: remove remaining systems from SSM after group union and intersection tests
66ms 1

When I click on the clear SSM button 66ms

@scope_visualization @scope_onboarding
Feature:Custom system info key-value pairs 15s 338ms 7

Scenario:
Log in as org admin user
1s 991ms 1

Given I am authorized 1s 991ms

Scenario:
Create a new key
1s 54ms 7

When I follow the left menu "Systems > Custom System Info" 116ms

And I follow "Create Key" 276ms

And I should see a "Create Custom Info Key" text 57ms

And I enter "key-label" as "label" 56ms

And I enter "key-desc" as "description" 60ms

And I click on "Create Key" 421ms

Then I should see a "Successfully added 1 custom key." text 66ms

Scenario:
Add a value to a system
3s 935ms 9

When I follow the left menu "Systems > System List > All" 134ms

And I follow this "sle_minion" link 1s 93ms

And I follow "Custom Info" 842ms

And I follow "Create Value" 673ms

And I follow "key-label" 441ms

And I enter "key-value" as "value" 55ms

And I click on "Update Key" 612ms

Then I should see a "key-label" text 69ms

And I should see a "key-value" link 11ms

Scenario:
Edit the value
2s 855ms 9

When I follow the left menu "Systems > System List > All" 114ms

And I follow this "sle_minion" link 1s 64ms

And I follow "Custom Info" 439ms

And I follow "key-value" 460ms

And I should see a "Edit Custom Value" text 63ms

And I enter "key-value-edited" as "value" 67ms

And I click on "Update Key" 567ms

Then I should see a "key-label" text 66ms

And I should see a "key-value-edited" link 11ms

Scenario:
Edit the key description
1s 187ms 6

When I follow the left menu "Systems > Custom System Info" 62ms

And I follow "key-label" 346ms

And I enter "key-desc-edited" as "description" 85ms

And I click on "Update Key" 623ms

Then I should see a "key-label" link 11ms

And I should see a "key-desc-edited" text 58ms

Scenario:
Delete the value
3s 215ms 8

When I follow the left menu "Systems > Custom System Info" 61ms

And I follow "key-label" 280ms

And I follow this "sle_minion" link 694ms

And I follow "Custom Info" 530ms

And I follow "key-value-edited" 453ms

And I follow "Delete Value" 513ms

And I click on "Remove Value" 614ms

Then I should see a "No custom information defined for this system." text 66ms

Scenario:
Delete the key
1s 98ms 5

When I follow the left menu "Systems > Custom System Info" 61ms

And I follow "key-label" 271ms

And I follow "Delete Key" 276ms

And I click on "Delete Key" 432ms

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
21ms 2

Given I retrieve a "javascript" static resource 21ms

Then the response header "X-WebKit-CSP" should not be present < 1ms

@scope_salt
Feature:Salt is configured and running 26s 503ms 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 824ms 4

When I get the contents of the remote file "/etc/salt/master.d/susemanager.conf" 2s 824ms

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 489ms 3

Then salt-api should be listening on local port 9080 4s 418ms

And salt-master should be listening on public port 4505 2s 535ms

And salt-master should be listening on public port 4506 2s 534ms

Scenario:
There are no top.sls files in certain folders
14s 189ms 10

When I run "ls /srv/susemanager/salt/top.sls" on "server" without error control 2s 477ms

Then the command should fail < 1ms

When I run "ls /srv/susemanager/salt/top.sls" on "server" without error control 2s 473ms

Then the command should fail < 1ms

When I run "ls /srv/susemanager/pillar/top.sls" on "server" without error control 2s 598ms

Then the command should fail < 1ms

When I run "ls /usr/share/susemanager/salt/top.sls" on "server" without error control 4s 108ms

Then the command should fail < 1ms

When I run "ls /usr/share/susemanager/pillar/top.sls" on "server" without error control 2s 531ms

Then the command should fail < 1ms

@scope_configuration_channels
Feature:The channels page 22s 764ms 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 741ms 1

Given I am authorized 10s 741ms

Scenario:
Completeness of the channels page
554ms 15

When I follow the left menu "Software > Channel List > All" 190ms

Then I should see a "Full Software Channel List" text 95ms

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 21ms

And I should see a "My Channels" link in the left menu 20ms

And I should see a "Shared" link in the left menu 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 23ms

And I should see a "All" link in the content area 22ms

And I should see a "Popular" link in the content area 17ms

And I should see a "My Channels" link in the content area 16ms

And I should see a "Shared" link in the content area 16ms

And I should see a "Retired" link in the content area 16ms

Scenario:
Popular channels
138ms 2

When I follow the left menu "Software > Channel List > Popular" 72ms

Then I should see a "Popular" text 66ms

Scenario:
Check packages in test channel
2s 116ms 10

When I follow the left menu "Software > Channel List > All" 69ms

And I follow "Show All Child Channels" 53ms

And I follow "Fake-RPM-SUSE-Channel" 778ms

And I follow "Packages" 670ms

Then I should see package "andromeda-dummy-2.0-1.1.noarch" 97ms

And I should see package "hoag-dummy-1.1-1.1.i586" 89ms

And I should see package "hoag-dummy-1.1-1.1.x86_64" 86ms

And I should see package "milkyway-dummy-2.0-1.1.i586" 89ms

And I should see package "milkyway-dummy-2.0-1.1.x86_64" 88ms

And I should see package "virgo-dummy-2.0-1.1.noarch" 92ms

Scenario:
Check package metadata
2s 137ms 10

When I follow the left menu "Software > Channel List > All" 68ms

And I follow "Show All Child Channels" 47ms

And I follow "Fake-RPM-SUSE-Channel" 689ms

And I follow "Packages" 493ms

And I follow "andromeda-dummy-2.0-1.1.noarch" 555ms

Then I should see a "This is the andromeda dummy package used for testing SUSE Manager" text 71ms

And I should see a "Fake-RPM-SUSE-Channel" link 11ms

And I should see a "build.opensuse.org" text 64ms

And I should see a "SHA512sum:" text 67ms

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 67ms

Scenario:
Check package dependencies page
2s 648ms 9

When I follow the left menu "Software > Channel List > All" 109ms

And I follow "Show All Child Channels" 45ms

And I follow "Fake-RPM-SUSE-Channel" 760ms

And I follow "Packages" 561ms

And I follow "andromeda-dummy-2.0-1.1.noarch" 633ms

And I follow "Dependencies" 377ms

Then I should see a "pam" text 53ms

And I should see a "rpmlib(PayloadIsXz) <= 5.2-1" text 51ms

And I should see a "andromeda-dummy = 2.0-1.1" text 55ms

Scenario:
Check package change log page
2s 273ms 8

When I follow the left menu "Software > Channel List > All" 105ms

And I follow "Show All Child Channels" 55ms

And I follow "Fake-RPM-SUSE-Channel" 593ms

And I follow "Packages" 565ms

And I follow "andromeda-dummy-2.0-1.1.noarch" 550ms

And I follow "Change Log" 303ms

Then I should see a "mc@suse.de" text 51ms

And I should see a "version 2.0" text 46ms

Scenario:
Check package file list page
2s 153ms 9

When I follow the left menu "Software > Channel List > All" 108ms

And I follow "Show All Child Channels" 47ms

And I follow "Fake-RPM-SUSE-Channel" 583ms

And I follow "Packages" 492ms

And I follow "andromeda-dummy-2.0-1.1.noarch" 453ms

And I follow "File List" 300ms

Then I should see a "This package contains the following files." text 56ms

And I should see a "/usr/share/doc/packages/andromeda-dummy/COPYING" text 56ms

And I should see a "sha256: 32b1062f7da84967e7019d01ab805935caa7ab7321a7ced0e30ebe75e5df1670" text 54ms

@scope_visualization
Feature:Managing channels 11s 621ms 9

In Order to distribute software to the clients
As an authorized user
I want to manage channels

Scenario:
Log in as org admin user
1s 872ms 1

Given I am authorized 1s 872ms

Scenario:
Fail when trying to add a duplicate channel
1s 158ms 10

When I follow the left menu "Software > Manage > Channels" 181ms

And I follow "Create Channel" 380ms

And I enter "Fake-Base-Channel-SUSE-like" as "Channel Name" 92ms

And I enter "fake-base-channel-suse-like" as "Channel Label" 82ms

And I select "None" from "Parent Channel" 54ms

And I select "x86_64" from "Architecture:" 46ms

And I enter "Base channel for testing" as "Channel Summary" 83ms

And I enter "No more desdcription for base channel." as "Channel Description" 93ms

And I click on "Create Channel" 65ms

Then I should see a "The channel name 'Fake-Base-Channel-SUSE-like' is already in use, please enter a different name" text 79ms

Scenario:
Fail when trying to use invalid characters in the channel label
1s 93ms 7

When I follow the left menu "Software > Manage > Channels" 73ms

And I follow "Create Channel" 385ms

And I enter "test123" as "Channel Name" 55ms

And I enter "tesT123" as "Channel Label" 59ms

And I enter "test123" as "Channel Summary" 57ms

And I click on "Create Channel" 381ms

Then I should see a "Invalid channel label, please see the format described below" text 79ms

Scenario:
Fail when trying to use invalid characters in the channel name
958ms 7

When I follow the left menu "Software > Manage > Channels" 70ms

And I follow "Create Channel" 573ms

And I enter "!test123" as "Channel Name" 58ms

And I enter "test123" as "Channel Label" 58ms

And I enter "test123" as "Channel Summary" 57ms

And I click on "Create Channel" 59ms

Then I should see a "Invalid channel name, please see the format described below" text 81ms

@scc_credentials
Scenario:
Fail when trying to use reserved names for channels
889ms 7

When I follow the left menu "Software > Manage > Channels" 74ms

And I follow "Create Channel" 473ms

And I enter "openSUSE-Leap-15.6-Pool for x86_64" as "Channel Name" 89ms

And I enter "test123" as "Channel Label" 56ms

And I enter "test123" as "Channel Summary" 54ms

And I click on "Create Channel" 60ms

Then I should see a "The channel name 'openSUSE-Leap-15.6-Pool for x86_64' is reserved, please enter a different name" text 80ms

@scc_credentials
Scenario:
Fail when trying to use reserved labels for channels
991ms 7

When I follow the left menu "Software > Manage > Channels" 72ms

And I follow "Create Channel" 360ms

And I enter "test123" as "Channel Name" 54ms

And I enter "opensuse-leap-15.6-pool-x86_64" as "Channel Label" 83ms

And I enter "test123" as "Channel Summary" 57ms

And I click on "Create Channel" 282ms

Then I should see a "The channel label 'opensuse-leap-15.6-pool-x86_64' is reserved, please enter a different name" text 80ms

Scenario:
Create a channel that will be changed
1s 514ms 7

When I follow the left menu "Software > Manage > Channels" 72ms

And I follow "Create Channel" 380ms

And I enter "aaaSLE-12-Cloud-Compute5-Pool for x86_64" as "Channel Name" 94ms

And I enter "sle-we12aaa-pool-x86_64-sap" as "Channel Label" 75ms

And I enter "test123" as "Channel Summary" 55ms

And I click on "Create Channel" 759ms

Then I should see a "Channel aaaSLE-12-Cloud-Compute5-Pool for x86_64 created." text 76ms

@scc_credentials
Scenario:
Fail when trying to change the channel name to a reserved name
1s 346ms 5

When I follow the left menu "Software > Manage > Channels" 72ms

And I follow "aaaSLE-12-Cloud-Compute5-Pool for x86_64" 558ms

And I enter "openSUSE-Leap-15.6-Pool for x86_64" as "Channel Name" 125ms

And I click on "Update Channel" 512ms

Then I should see a "The channel name 'openSUSE-Leap-15.6-Pool for x86_64' is reserved, please enter a different name" text 78ms

Scenario:
Cleanup: Delete created channel
1s 795ms 6

When I follow the left menu "Software > Manage > Channels" 73ms

And I follow "aaaSLE-12-Cloud-Compute5-Pool for x86_64" 563ms

And I follow "Delete Channel" 402ms

And I check "unsubscribeSystems" 78ms

And I click on "Delete Channel" 589ms

Then I should see a "Channel aaaSLE-12-Cloud-Compute5-Pool for x86_64 has been deleted." text 88ms

@scope_visualization
Feature:Left Menu Filter 2s 611ms 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 883ms 1

Given I am authorized for the "Admin" section 1s 883ms

Scenario:
Search a word and expect the right result
106ms 2

When I enter "Admin" as the left menu search field 81ms

Then I should see a "Admin" link in the left menu 24ms

Scenario:
Search a partial word and expect the right result
119ms 2

When I enter "Formula" as the left menu search field 95ms

Then I should see a "Formula Catalog" link in the left menu 23ms

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 83ms

Then I should see a "Salt" link in the left menu 23ms

@susemanager
Scenario:
Search a word and expect several results
< 1ms 4

When I enter "SUSE" as the left menu search field 0s

Then I should see a "SUSE" text 0s

And I should see a "SUSE Multi-Linux Manager Server" text 0s

And I should see a "SUSE Multi-Linux Manager Proxy" text 0s

@uyuni
Scenario:
Search a word and expect several results
250ms 3

When I enter "Uyuni" as the left menu search field 82ms

Then I should see a "Uyuni Server" text 59ms

And I should see a "Uyuni Proxy" text 108ms

Scenario:
Search a non-existing word and expect no results
143ms 2

When I enter "Null" as the left menu search field 135ms

Then I should see left menu empty 7ms

@scope_api
Feature:API "channel" namespace and sub-namespaces 10s 63ms 10

Scenario:
Create a custom software channel
1s 17ms 2

When I create the following channels: 478ms
LABEL NAME SUMMARY ARCH PARENT
foobar foobar foobar channel-x86_64

Then "foobar" should get listed with a call of listSoftwareChannels 539ms

Scenario:
Create a repository
2s 39ms 4

When I create a repo with label "foobar" and url 450ms

And I associate repo "foobar" with channel "foobar" 523ms

Then channel "foobar" should have attribute "last_modified" that is a date 540ms

And channel "foobar" should not have attribute "yumrepo_last_sync" 525ms

Scenario:
Create a custom software channel as the child of another one
1s 406ms 3

When I create the following channels: 423ms
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 417ms

And "foobar" should be the parent channel of "foobar-child" 564ms

Scenario:
List software channels
476ms 1

Then something should get listed with a call of listSoftwareChannels 476ms

Scenario:
Delete a child software channel
1s 106ms 2

When I delete the software channel with label "foobar-child" 570ms

Then "foobar-child" should not get listed with a call of listSoftwareChannels 535ms

Scenario:
Delete a software channel
2s 67ms 3

When I delete the repo with label "foobar" 435ms

And I delete the software channel with label "foobar" 1s 246ms

Then "foobar" should not get listed with a call of listSoftwareChannels 385ms

Scenario:
Check last synchronization of a synced channel
394ms 1

Then channel "fake-child-channel-i586" should have attribute "yumrepo_last_sync" that is a date 394ms

@rhlike_minion
Scenario:
Verify if a channel is modular via the API
762ms 2

When I verify channel "fake-base-channel-appstream" is modular via the API 395ms

And I verify channel "fake-rpm-suse-channel" is not modular via the API 366ms

@rhlike_minion
Scenario:
List modular channels via the API
365ms 1

When channel "Fake-Base-Channel-AppStream" is present in the modular channels listed via the API 365ms

@rhlike_minion
Scenario:
List available module streams for a given channel via the API
427ms 1

When "scorpio" module streams "2.0, 2.1" are available for channel "fake-base-channel-appstream" via the API 427ms

@scope_visualization
Feature:Patches page 13s 340ms 8

In order to use the Patches page
As a authorized user
I want to see all the texts and links

Scenario:
Log in as org admin user
1s 866ms 1

Given I am authorized 1s 866ms

Scenario:
Patches left menu
461ms 11

When I follow the left menu "Patches > Patch List > Relevant" 181ms

Then I should see a "Patches Relevant to Your Systems" text 134ms

And I should see a "Relevant" link in the left menu 21ms

And I should see a "All" link in the left menu 22ms

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 19ms

And I should see a "Clone Patches" link in the left menu 20ms

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 651ms 18

When I follow the left menu "Patches > Manage Patches" 66ms

And I follow "Create Patch" 333ms

When I enter "Test Patch" as "synopsis" 98ms

And I enter "Test Advisory" as "advisoryName" 83ms

And I enter "Test Product" as "product" 80ms

And I enter "test@test.org" as "errataFrom" 86ms

And I enter "Test Topic" as "topic" 75ms

And I enter "Test Description" as "description" 86ms

And I enter "Test Solution" as "solution" 84ms

And I enter "620212" as "buglistId" 65ms

And I enter "Test Summary" as "buglistSummary" 81ms

And I enter "https://bugzilla.opensuse.org/show_bug.cgi?id=620212" as "buglistUrl" 194ms

And I enter "test,keywords" as "keywords" 80ms

And I enter "Test Reference" as "refersTo" 80ms

And I enter "Test Note" as "notes" 71ms

And I check test channel 63ms

And I click on "Create Patch" 944ms

Then I should see a "Patch: Test Advisory-1" text 75ms

Scenario:
Create new enhancement patch with no bnc URL
2s 944ms 17

When I follow the left menu "Patches > Manage Patches" 62ms

And I follow "Create Patch" 347ms

When I enter "Enhancement Patch" as "synopsis" 94ms

And I enter "Enhancement Advisory" as "advisoryName" 93ms

And I select "Product Enhancement Advisory" from "advisoryType" 74ms

And I enter "Enhancement Product" as "product" 92ms

And I enter "Enhancement Topic" as "topic" 86ms

And I enter "Enhancement Description" as "description" 97ms

And I enter "Enhancement Solution" as "solution" 91ms

And I enter "1234" as "buglistId" 59ms

And I enter "Enhancement Summary" as "buglistSummary" 89ms

And I enter "Enhancement,keywords" as "keywords" 94ms

And I enter "Enhancement Reference" as "refersTo" 91ms

And I enter "Enhancement Note" as "notes" 81ms

And I check test channel 55ms

And I click on "Create Patch" 1s 354ms

Then I should see a "Patch: Enhancement Advisory-1" text 77ms

Scenario:
Delete enhancement patch
1s 358ms 5

When I follow the left menu "Patches > Manage Patches" 62ms

And I check "Enhancement Advisory" patch 65ms

And I click on "Delete Patches" 548ms

And I click on "Confirm" 569ms

Then I should see a "Successfully deleted 1 patches." text 112ms

Scenario:
Verify patch presence in web UI
1s 709ms 15

When I follow the left menu "Patches > Patch List > All" 137ms

And I follow "Bugfix Patches" in the content area 117ms

And I enter "Test Patch" as the filtered synopsis 49ms

And I click on the filter button 458ms

And I follow "Test Advisory" 430ms

Then I should see a "Test Patch" text 64ms

And I should see a "test@test.org" text 65ms

And I should see a "Test Topic" text 59ms

And I should see a "Test Description" text 64ms

And I should see a "Test Solution" text 59ms

And I should see a "Fake-Base-Channel-SUSE-like" link 11ms

And I should see a "Test Summary" link 10ms

And I should see a "keywords, test" text 60ms

And I should see a "Test Reference" text 61ms

And I should see a "Test Note" text 60ms

Scenario:
Assert that patch is now in test base channel
875ms 4

When I follow the left menu "Software > Channel List > All" 177ms

And I follow "Fake-Base-Channel-SUSE-like" 569ms

And I follow "Patches" in the content area 64ms

Then I should see a "Test Patch" text 63ms

Scenario:
Delete patch
1s 472ms 5

When I follow the left menu "Patches > Manage Patches" 105ms

And I check "Test Advisory" patch 56ms

And I click on "Delete Patches" 634ms

And I click on "Confirm" 569ms

Then I should see a "Successfully deleted 1 patches." text 106ms

@scc_credentials @scope_content_lifecycle_management
Feature:Content lifecycle 10m 49s 69ms 46 4

Scenario:
Log in as org admin user
1s 852ms 1

Given I am authorized 1s 852ms

Scenario:
Create CLM filter to remove all fonts packages
3s 85ms 10

When I follow the left menu "Content Lifecycle > Filters" 119ms

And I click on "Create Filter" 121ms

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 63ms

And I enter "remove fonts packages" as "filter_name" 128ms

And I select "Package (Name)" from "type" 1s 137ms

And I select "contains" from "matcher" 1s 108ms

And I enter "fonts" as "name" 74ms

And I click on "Save" in "Create a new filter" modal 261ms

Then I should see a "remove fonts packages" text 57ms

Scenario:
Create a content lifecycle project
1s 386ms 9

When I follow the left menu "Content Lifecycle > Projects" 63ms

And I follow "Create Project" 360ms

Then I should see a "Create a new Content Lifecycle Project" text 52ms

And I should see a "Project Properties" text 51ms

When I enter "clp_label" as "label" 68ms

And I enter "clp_name" as "name" 58ms

And I enter "clp_desc" as "description" 64ms

And I click on "Create" 60ms

And I wait until I see "Content Lifecycle Project - clp_name" text 606ms

Scenario:
Verify the content lifecycle project page
811ms 9

When I follow the left menu "Content Lifecycle > Projects" 63ms

Then I should see a "clp_name" text 56ms

And I should see a "clp_desc" text 53ms

When I follow "clp_name" 340ms

Then I should see a "Project Properties" text 62ms

And I should see a "Versions history" text 58ms

And I should see a "Sources" text 62ms

And I should see a "Filters" text 56ms

And I should see a "Environment Lifecycle" text 57ms

@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 126ms 8

When I follow the left menu "Content Lifecycle > Projects" 59ms

And I follow "clp_name" 340ms

And I click on "Attach/Detach Sources" 72ms

And I select "openSUSE Tumbleweed (x86_64)" from "selectedBaseChannel" 1s 108ms

And I wait until I see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" text 125ms

And I click on "Save" 63ms

And I wait until I see "openSUSE Tumbleweed (x86_64)" text 295ms

Then I should see a "Version 1: (draft - not built) - Check the changes below" text 61ms

@susemanager
Scenario:
Verify added sources
< 1ms 4

When I follow the left menu "Content Lifecycle > Projects" 0s

And I follow "clp_name" 0s

Then I should see a "SLE-Product-SLES15-SP7-Updates for x86_64" text 0s

And I should see a "Build (2)" text 0s

@uyuni
Scenario:
Verify added sources
629ms 4

When I follow the left menu "Content Lifecycle > Projects" 56ms

And I follow "clp_name" 439ms

Then I should see a "openSUSE Tumbleweed (x86_64)" text 68ms

And I should see a "Build (1)" text 64ms

Scenario:
Add fonts packages filter to the project
1s 430ms 10

When I follow the left menu "Content Lifecycle > Projects" 60ms

And I follow "clp_name" 501ms

Then I should see a "Content Lifecycle Project - clp_name" text 66ms

When I click on "Attach/Detach Filters" 66ms

And I check the "remove fonts packages" CLM filter 276ms

And I click on "Save" 52ms

And I wait until I see "Deny" text 224ms

Then I should see a "remove fonts packages" text 64ms

When I follow the left menu "Content Lifecycle > Filters" 57ms

Then I should see a "clp_name" text 59ms

Scenario:
Add environments to the project
3s 838ms 25

When I follow the left menu "Content Lifecycle > Projects" 60ms

And I follow "clp_name" 444ms

Then I should see a "No environments created" text 67ms

When I click on "Add Environment" 72ms

And I enter "dev_name" as "name" 77ms

And I enter "dev_label" as "label" 75ms

And I enter "dev_desc" as "description" 69ms

And I click on "Save" 57ms

Then I wait until I see "dev_name" text 305ms

And I should see a "dev_desc" text 68ms

When I click on "Add Environment" 68ms

And I enter "prod_name" as "name" 71ms

And I enter "prod_label" as "label" 77ms

And I enter "prod_desc" as "description" 71ms

And I click on "Save" 54ms

Then I wait until I see "prod_name" text 338ms

And I should see a "prod_desc" text 77ms

When I click on "Add Environment" 65ms

And I enter "qa_name" as "name" 69ms

And I enter "qa_label" as "label" 77ms

And I enter "qa_desc" as "description" 69ms

And I select "prod_name" from "predecessorLabel" 1s 114ms

And I click on "Save" 58ms

Then I wait until I see "qa_name" text 236ms

And I should see a "qa_desc" text 86ms

@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 468ms 9

When I follow the left menu "Content Lifecycle > Projects" 58ms

And I follow "clp_name" 396ms

Then I should see a "not built" text in the environment "qa_name" 21ms

When I click on "Build (2)" 76ms

Then I should see a "Version 1 history" text 95ms

When I enter "test version message 1" as "message" 63ms

And I click the environment build button 56ms

And I wait until I see "Version 1: test version message 1" text in the environment "dev_name" 327ms

And I wait at most 600 seconds until I see "Built" text in the environment "dev_name" 1m 371ms

Scenario:
Promote the sources in the project
1m 57s 388ms 15

When I follow the left menu "Content Lifecycle > Projects" 79ms

Then I should see a "clp_name" text 58ms

And I should see a "clp_desc" text 57ms

And I should see a "dev_name > qa_name > prod_name" text 52ms

When I follow "clp_name" 421ms

Then I should see a "qa_desc" text in the environment "qa_name" 23ms

And I should see a "not built" text in the environment "qa_name" 18ms

When I click promote from Development to QA 64ms

Then I should see a "Version 1: test version message 1" text 93ms

And I click on "Promote environment" in "Promote version 1 into qa_name" modal 360ms

Then I wait at most 600 seconds until I see "Built" text in the environment "qa_name" 55s 346ms

When I click promote from QA to Production 63ms

Then I should see a "Version 1: test version message 1" text 96ms

And I click on "Promote environment" in "Promote version 1 into prod_name" modal 299ms

Then I wait at most 600 seconds until I see "Built" text in the environment "prod_name" 1m 353ms

@skip_if_github_validation
Scenario:
Add new sources and promote again
3m 959ms 27

When I follow the left menu "Content Lifecycle > Projects" 81ms

And I follow "clp_name" 457ms

Then I should see a "Build (0)" text 96ms

When I click on "Attach/Detach Sources" 75ms

And I uncheck "Vendors" 10s 999ms

And I enter "Fake-Base-Channel-SUSE-like" in the placeholder "Search a channel" 130ms

And I add the "Fake-Base-Channel-SUSE-like" channel to sources 75ms

And I click on "Save" 68ms

Then I wait until I see "Fake-Base-Channel-SUSE-like" text 544ms

And I wait until I see "Build (1)" text 91ms

And I should see a "Version 2: (draft - not built) - Check the changes below" text 91ms

When I click on "Build (1)" 70ms

Then I wait until I see "Version 2 history" text 98ms

When I enter "test version message 2" as "message" 68ms

And I click the environment build button 55ms

Then I wait until I see "Version 2: test version message 2" text in the environment "dev_name" 378ms

And I wait at most 600 seconds until I see "Built" text in the environment "dev_name" 45s 534ms

When I click promote from Development to QA 63ms

Then I should see a "Version 2: test version message 2" text 105ms

And I click on "Promote environment" in "Promote version 2 into qa_name" modal 432ms

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 432ms

When I click promote from QA to Production 62ms

Then I should see a "Version 2: test version message 2" text 100ms

And I click on "Promote environment" in "Promote version 2 into prod_name" modal 429ms

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 413ms

Scenario:
Create a CLM filter of type Package(NEVRA) that allows packages whose version and release number are lower to a defined one
13s 381ms 15

When I follow the left menu "Content Lifecycle > Filters" 83ms

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 71ms

When I enter "mercury" as "filter_name" 76ms

And I select "Package (NEVRA)" from "type" 1s 129ms

And I select "lower" from "matcher" 1s 124ms

And I enter "mercury" as "Package Name" 96ms

And I enter "mercury" as "Epoch" 91ms

And I enter "0.0.0" as "version" 73ms

And I enter "0.0.0" as "Release" 106ms

And I enter "x86_64" as "Architecture" 86ms

And I check radio button "Allow" 10s 64ms

And I click on "Save" in "Create a new filter" modal 233ms

Then I should see a "Filter created successfully" text 59ms

Scenario:
Create a CLM filter of type Package(NEVRA) that denys packages whose version and release number are lower to a defined one
3s 176ms 15

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 56ms

And I click on "Create Filter" 60ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 73ms

When I enter "venus" as "filter_name" 58ms

And I select "Package (NEVRA)" from "type" 1s 129ms

And I select "lower" from "matcher" 1s 108ms

And I enter "venus" as "Package Name" 78ms

And I enter "venus" as "Epoch" 71ms

And I enter "0.0.0" as "version" 71ms

And I enter "0.0.0" as "Release" 74ms

And I enter "x86_64" as "Architecture" 76ms

And I check radio button "Deny" 20ms

And I click on "Save" in "Create a new filter" modal 224ms

Then I should see a "Filter created successfully" text 62ms

Scenario:
Create CLM filter that allows packages of type Package (Provides Name)
2s 882ms 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 73ms

When I enter "cereal" as "filter_name" 60ms

And I select "Package (Provides Name)" from "type" 1s 127ms

And I select "provides name" from "matcher" 1s 103ms

And I enter "cereal" as "Provides Name" 83ms

And I click on "Save" in "Create a new filter" modal 238ms

Then I should see a "Filter created successfully" text 66ms

Scenario:
Create CLM filter that denys packages of type Package (Provides Name)
2s 925ms 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 56ms

And I click on "Create Filter" 61ms

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 78ms

When I enter "potato" as "filter_name" 59ms

And I select "Package (Provides Name)" from "type" 1s 114ms

And I select "provides name" from "matcher" 1s 106ms

And I enter "potato" as "Provides Name" 120ms

And I check radio button "Deny" 17ms

And I click on "Save" in "Create a new filter" modal 231ms

Then I should see a "Filter created successfully" text 69ms

Scenario:
Create CLM filter of type Package (Build date) that allows packages whose date is lower than a defined one
13s 34ms 10

When I follow the left menu "Content Lifecycle > Filters" 61ms

And I click on "Create Filter" 62ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 7ms

Then I should see a "Create a new filter" text 80ms

When I enter "cherry" as "filter_name" 59ms

And I select "Package (Build date)" from "type" 1s 129ms

And I select "lower" from "matcher" 1s 147ms

And I check radio button "Allow" 10s 127ms

And I click on "Save" in "Create a new filter" modal 281ms

Then I should see a "Filter created successfully" text 76ms

Scenario:
Create CLM filter of type Package (Build date) that denys packages whose date is lower than a defined one
2s 836ms 10

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 57ms

And I click on "Create Filter" 62ms

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 81ms

When I enter "drummer" as "filter_name" 63ms

And I select "Package (Build date)" from "type" 1s 128ms

And I select "lower" from "matcher" 1s 105ms

And I check radio button "Deny" 15ms

And I click on "Save" in "Create a new filter" modal 233ms

Then I should see a "Filter created successfully" text 79ms

Scenario:
Create CLM filter of type Patch(Advisory Name) that allows patches that are equal to a defined one
13s 7ms 11

When I follow the left menu "Content Lifecycle > Filters" 65ms

And I click on "Create Filter" 64ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 7ms

Then I should see a "Create a new filter" text 87ms

When I enter "africa-patch" as "filter_name" 77ms

And I select "Patch (Advisory Name)" from "type" 1s 115ms

And I select "equals" from "matcher" 1s 100ms

And I enter "africa" as "Advisory name" 86ms

And I check radio button "Allow" 10s 60ms

And I click on "Save" in "Create a new filter" modal 263ms

Then I should see a "Filter created successfully" text 78ms

Scenario:
Create CLM filter of type Patch(Advisory Name) that denys patches that are equal to a defined one
2s 996ms 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 60ms

And I click on "Create Filter" 62ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 90ms

When I enter "asia-patch" as "filter_name" 78ms

And I select "Patch (Advisory Name)" from "type" 1s 120ms

And I select "equals" from "matcher" 1s 112ms

And I enter "asia" as "Advisory name" 72ms

And I check radio button "Deny" 17ms

And I click on "Save" in "Create a new filter" modal 286ms

Then I should see a "Filter created successfully" text 87ms

Scenario:
Create CLM filter of type Patch(Advisory Type) that allows Security Advisory patches that are equal to a defined one
12s 957ms 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" 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 88ms

When I enter "key" as "filter_name" 51ms

And I select "Patch (Advisory Type)" from "type" 1s 125ms

And I select "equals" from "matcher" 1s 103ms

And I check radio button "Security Advisory" 20ms

And I check radio button "Allow" 10s 65ms

And I click on "Save" in "Create a new filter" modal 272ms

Then I should see a "Filter created successfully" text 84ms

Scenario:
Create CLM filter of type Patch(Advisory Type) that denys Security Advisory patches that are equal to a defined one
2s 939ms 11

Warning: Radio button 'Security Advisory' is already checked
Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 57ms

And I click on "Create Filter" 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 100ms

When I enter "geminis-patch" as "filter_name" 120ms

And I select "Patch (Advisory Type)" from "type" 1s 117ms

And I select "equals" from "matcher" 1s 103ms

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 246ms

Then I should see a "Filter created successfully" text 87ms

Scenario:
Create CLM filter of type Patch(Synopsis) that allows patches that that are equal to a defined one
13s 29ms 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 99ms

When I enter "aries-patch" as "filter_name" 74ms

And I select "Patch (Synopsis)" from "type" 1s 116ms

And I select "equals" from "matcher" 1s 104ms

And I enter "aries" as "Synopsis" 83ms

And I check radio button "Allow" 10s 73ms

And I click on "Save" in "Create a new filter" modal 248ms

Then I should see a "Filter created successfully" text 89ms

Scenario:
Create CLM filter of type Patch(Synopsis) that denys patches that are equal to a defined one
3s 16ms 11

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 9ms

Then I should see a "Create a new filter" text 102ms

When I enter "andromeda-patch" as "filter_name" 86ms

And I select "Patch (Synopsis)" from "type" 1s 124ms

And I select "equals" from "matcher" 1s 102ms

And I enter "andromeda" as "Synopsis" 91ms

And I check radio button "Deny" 16ms

And I click on "Save" in "Create a new filter" modal 258ms

Then I should see a "Filter created successfully" text 98ms

Scenario:
Create CLM filter of type Patch(Keyword) that allows patches that contains Package Manager Restart Required keyword in its name
23s 148ms 11

When I follow the left menu "Content Lifecycle > Filters" 62ms

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 105ms

When I enter "mars-patch" as "filter_name" 73ms

And I select "Patch (Keyword)" from "type" 1s 129ms

And I select "contains" from "matcher" 1s 116ms

And I check radio button "Package Manager Restart Required" 10s 94ms

And I check radio button "Allow" 10s 81ms

And I click on "Save" in "Create a new filter" modal 314ms

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 30ms 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 64ms

And I click on "Create Filter" 68ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 9ms

Then I should see a "Create a new filter" text 112ms

When I enter "eurasia-patch" as "filter_name" 81ms

And I select "Patch (Keyword)" from "type" 1s 124ms

And I select "contains" from "matcher" 1s 103ms

And I check radio button "Package Manager Restart Required" 10s 64ms

And I check radio button "Deny" 17ms

And I click on "Save" in "Create a new filter" modal 281ms

Then I should see a "Filter created successfully" text 102ms

Scenario:
Create CLM filter of type Patch(Issue date) that allows patches whose date is greater or equal than a defined one
13s 202ms 10

When I follow the left menu "Content Lifecycle > Filters" 61ms

And I click on "Create Filter" 118ms

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 110ms

When I enter "milkyway-patch" as "filter_name" 85ms

And I select "Patch (Issue date)" from "type" 1s 141ms

And I select "greater or equal" from "matcher" 1s 117ms

And I check radio button "Allow" 10s 71ms

And I click on "Save" in "Create a new filter" modal 377ms

Then I should see a "Filter created successfully" text 108ms

Scenario:
Create CLM filter of type Patch(Issue date) that denys patches whose date is greater or equal than a defined one
3s 205ms 11

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 8ms

Then I should see a "Create a new filter" text 113ms

When I enter "venus-patch" as "filter_name" 77ms

And I select "Patch (Issue date)" from "type" 1s 124ms

And I select "greater or equal" from "matcher" 1s 113ms

When I enter "solar" as "filter_name" 141ms

And I check radio button "Deny" 16ms

And I click on "Save" in "Create a new filter" modal 329ms

Then I should see a "Filter created successfully" text 141ms

Scenario:
Create CLM filter of type Patch(Contains Package Name) that allows patches that are equal to a specific one
13s 394ms 11

When I follow the left menu "Content Lifecycle > Filters" 64ms

And I click on "Create Filter" 72ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 118ms

When I enter "Triangulum-patch" as "filter_name" 95ms

And I select "Patch (Contains Package Name)" from "type" 1s 129ms

And I select "equals" from "matcher" 1s 120ms

When I enter "Triangulum-patch" as "Package Name" 144ms

And I check radio button "Allow" 10s 63ms

And I click on "Save" in "Create a new filter" modal 467ms

Then I should see a "Filter created successfully" text 108ms

Scenario:
Create CLM filter of type Patch(Contains Package Name) that denys patches that are equal to a specific one
3s 213ms 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 121ms

When I enter "Pinwheel-patch" as "filter_name" 88ms

And I select "Patch (Contains Package Name)" from "type" 1s 128ms

And I select "equals" from "matcher" 1s 116ms

When I enter "Pinwheel-patch" as "Package Name" 115ms

And I check radio button "Deny" 16ms

And I click on "Save" in "Create a new filter" modal 375ms

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 240ms 11

When I follow the left menu "Content Lifecycle > Filters" 64ms

And I click on "Create Filter" 67ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 123ms

When I enter "Sunflower-patch" as "filter_name" 91ms

And I select "Patch (Contains Package Name)" from "type" 1s 125ms

And I select "matches" from "matcher" 1s 116ms

When I enter "Sunflower-patch" as "Package Name" 125ms

And I check radio button "Allow" 10s 79ms

And I click on "Save" in "Create a new filter" modal 318ms

Then I should see a "Filter created successfully" text 118ms

Scenario:
Create CLM filter of type Patch(Contains Package Name) that denys patches that matches to a specific one
3s 186ms 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 64ms

And I click on "Create Filter" 70ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 128ms

When I enter "Whirlpool-patch" as "filter_name" 94ms

And I select "Patch (Contains Package Name)" from "type" 1s 118ms

And I select "matches" from "matcher" 1s 114ms

When I enter "Whirlpool-patch" as "Package Name" 135ms

And I check radio button "Deny" 17ms

And I click on "Save" in "Create a new filter" modal 313ms

Then I should see a "Filter created successfully" text 120ms

Scenario:
Create CLM filter of type Patch(Contains Package Provides Name) that allows patches with a specific name
13s 261ms 11

When I follow the left menu "Content Lifecycle > Filters" 57ms

And I click on "Create Filter" 82ms

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 128ms

When I enter "Antennae-patch" as "filter_name" 89ms

And I select "Patch (Contains Package Provides Name)" from "type" 1s 126ms

And I select "provides name" from "matcher" 1s 112ms

When I enter "Antennae-patch" as "Package Provides Name" 127ms

And I check radio button "Allow" 10s 74ms

And I click on "Save" in "Create a new filter" modal 317ms

Then I should see a "Filter created successfully" text 136ms

Scenario:
Create CLM filter of type Patch(Contains Package Provides Name) that denys patches with a specific name
3s 218ms 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 63ms

And I click on "Create Filter" 69ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 140ms

When I enter "hat-patch" as "filter_name" 71ms

And I select "Patch (Contains Package Provides Name)" from "type" 1s 131ms

And I select "provides name" from "matcher" 1s 107ms

When I enter "hat-patch" as "Package Provides Name" 100ms

And I check radio button "Deny" 18ms

And I click on "Save" in "Create a new filter" modal 380ms

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 551ms 14

When I follow the left menu "Content Lifecycle > Filters" 58ms

And I click on "Create Filter" 69ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 138ms

When I enter "Hubble-patch" as "filter_name" 82ms

And I select "Patch (Contains Package)" from "type" 1s 128ms

And I select "version lower than" from "matcher" 1s 119ms

When I enter "Hubble-patch" as "Package Name" 122ms

And I enter "Hubble-patch" as "Epoch" 115ms

And I enter "0.0.0" as "Version" 81ms

And I enter "0.0.0" as "Release" 87ms

And I check radio button "Allow" 10s 78ms

And I click on "Save" in "Create a new filter" modal 324ms

Then I should see a "Filter created successfully" text 134ms

Scenario:
Create CLM filter of type Patch(Contains Package) that denys patches whose version is lower than a specific one
3s 437ms 14

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 58ms

And I click on "Create Filter" 69ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 9ms

Then I should see a "Create a new filter" text 145ms

When I enter "galaxy-patch" as "filter_name" 83ms

And I select "Patch (Contains Package)" from "type" 1s 128ms

And I select "version lower than" from "matcher" 1s 108ms

When I enter "galaxy-patch" as "Package Name" 120ms

And I enter "galaxy-patch" as "Epoch" 110ms

And I enter "0.0.0" as "Version" 75ms

And I enter "0.0.0" as "Release" 78ms

And I check radio button "Deny" 17ms

And I click on "Save" in "Create a new filter" modal 298ms

Then I should see a "Filter created successfully" text 132ms

Scenario:
Create CLM filter of type Patch(Contains Package) that allows patches whose version is lower or equal than a specific one
13s 546ms 14

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 160ms

When I enter "earth-patch" as "filter_name" 79ms

And I select "Patch (Contains Package)" from "type" 1s 135ms

And I select "version lower or equal" from "matcher" 1s 114ms

When I enter "earth-patch" as "Package Name" 115ms

And I enter "earth-patch" as "Epoch" 106ms

And I enter "0.0.0" as "Version" 76ms

And I enter "0.0.0" as "Release" 78ms

And I check radio button "Allow" 10s 78ms

And I click on "Save" in "Create a new filter" modal 319ms

Then I should see a "Filter created successfully" text 133ms

Scenario:
Create CLM filter of type Patch(Contains Package) that denys patches whose version is lower or equal than a specific one
3s 470ms 14

Warning: Radio button 'Deny' is already checked

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 8ms

Then I should see a "Create a new filter" text 145ms

When I enter "moon-patch" as "filter_name" 83ms

And I select "Patch (Contains Package)" from "type" 1s 125ms

And I select "version lower or equal" from "matcher" 1s 116ms

When I enter "moon-patch" as "Package Name" 113ms

And I enter "moon-patch" as "Epoch" 102ms

And I enter "0.0.0" as "Version" 76ms

And I enter "0.0.0" as "Release" 85ms

And I check radio button "Deny" 17ms

And I click on "Save" in "Create a new filter" modal 328ms

Then I should see a "Filter created successfully" text 134ms

Scenario:
Create CLM filter to enable Ruby 2.7 module
3s 273ms 11

When I follow the left menu "Content Lifecycle > Filters" 59ms

And I click on "Create Filter" 71ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 9ms

Then I should see a "Create a new filter" text 151ms

And I enter "ruby 2.7 module" as "filter_name" 99ms

And I select "Module (Stream)" from "type" 1s 133ms

And I select "equals" from "matcher" 1s 131ms

And I enter "ruby" as "moduleName" 78ms

And I enter "2.7" as "moduleStream" 64ms

And I click on "Save" in "Create a new filter" modal 339ms

Then I should see a "Filter created successfully" text 134ms

Scenario:
Create CLM filter that allows Product Temporary Fix (All)
3s 106ms 10

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 63ms

And I click on "Create Filter" 72ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 146ms

When I enter "mars" as "filter_name" 63ms

And I select "Product Temporary Fix (All)" from "type" 1s 132ms

And I select "all" from "matcher" 1s 123ms

And I check radio button "Deny" 17ms

And I click on "Save" in "Create a new filter" modal 339ms

Then I should see a "Filter created successfully" text 137ms

Scenario:
Create CLM filter that denys Product Temporary Fix (All)
3s 112ms 10

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 64ms

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 153ms

When I enter "mercury-patch" as "filter_name" 90ms

And I select "Product Temporary Fix (All)" from "type" 1s 138ms

And I select "all" from "matcher" 1s 111ms

And I check radio button "Deny" 17ms

And I click on "Save" in "Create a new filter" modal 313ms

Then I should see a "Filter created successfully" text 140ms

Scenario:
Create CLM filter of type Product Temporary Fix (Number) that allows packages of a version lower than a specific one
13s 268ms 11

When I follow the left menu "Content Lifecycle > Filters" 63ms

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 139ms

When I enter "jupiter-patch" as "filter_name" 90ms

And I select "Product Temporary Fix (Number)" from "type" 1s 126ms

And I select "lower" from "matcher" 1s 121ms

And I enter "1" as "Number" 79ms

And I check radio button "Allow" 10s 80ms

And I click on "Save" in "Create a new filter" modal 344ms

Then I should see a "Filter created successfully" text 139ms

Scenario:
Create CLM filter of type Product Temporary Fix (Number) that denys packages of a version lower than a specific one
3s 844ms 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 65ms

And I click on "Create Filter" 73ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 147ms

When I enter "pluto-patch" as "filter_name" 80ms

And I select "Product Temporary Fix (Number)" from "type" 1s 122ms

And I select "lower" from "matcher" 1s 116ms

And I enter "2" as "Number" 64ms

And I check radio button "Deny" 17ms

And I click on "Save" in "Create a new filter" modal 1s 13ms

Then I should see a "Filter created successfully" text 134ms

@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 332ms 11

When I follow the left menu "Content Lifecycle > Filters" 60ms

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 152ms

When I enter "comet-patch" as "filter_name" 80ms

And I select "Product Temporary Fix (Fixes Package Name)" from "type" 1s 124ms

And I select "equals" from "matcher" 1s 113ms

And I enter "comet-patch" as "Package Name" 111ms

And I check radio button "Allow" 10s 85ms

And I click on "Save" in "Create a new filter" modal 353ms

Then I should see a "Filter created successfully" text 136ms

Scenario:
Cleanup: remove the Content Lifecycle Management project
1s 87ms 5

When I follow the left menu "Content Lifecycle > Projects" 71ms

And I follow "clp_name" 577ms

And I click on "Delete" 79ms

And I click on "Delete" in "Delete Project" modal 103ms

Then I should not see a "clp_name" text 255ms

Scenario:
Cleanup: remove the CLM filters
4s 605ms 33

When I follow the left menu "Content Lifecycle > Filters" 57ms

And I click on "Select unused" 83ms

And I click on "Delete" 93ms

And I click on "Delete" in "Delete Selected Filter(s)" modal 116ms

Then I should not see a "remove fonts packages" text 144ms

And I should not see a "africa-patch" text 2s 686ms

And I should not see a "andromeda-patch" text 51ms

And I should not see a "Antennae-patch" text 49ms

And I should not see a "aries-patch" text 52ms

And I should not see a "asia-patch" text 52ms

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 53ms

And I should not see a "drummer" text 53ms

And I should not see a "earth-patch" text 58ms

And I should not see a "galaxy-patch" text 54ms

And I should not see a "hat-patch" text 51ms

And I should not see a "Hubble-patch" text 51ms

And I should not see a "mars" text 52ms

And I should not see a "mars-patch" text 51ms

And I should not see a "mercury" text 50ms

And I should not see a "milkyway-patch" text 50ms

And I should not see a "moon-patch" text 52ms

And I should not see a "Pinwheel-patch" text 57ms

And I should not see a "pluto-patch" text 53ms

And I should not see a "solar" text 52ms

And I should not see a "Sunflower-patch" text 50ms

And I should not see a "Triangulum-patch" text 50ms

And I should not see a "venus" text 52ms

And I should not see a "Whirlpool-patch" text 52ms

And I should not see a "remove fonts packages" text 52ms

And I should not see a "ruby 2.7 module" text 57ms

And I should not see a "key" text 50ms

@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 169ms 3

When I delete these channels with spacewalk-remove-channel: 3s 258ms
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 911ms

Then I shouldn't get "clp_label" < 1ms

@scope_recurring_actions
Feature:Change the schedule of a task 44s 243ms 4

Scenario:
Log in as admin user
2s 209ms 1

Given I am authorized for the "Admin" section 2s 209ms

Scenario:
Change the schedule of task sandbox-cleanup-default to weekly
13s 836ms 10

When I follow the left menu "Admin > Task Schedules" 122ms

And I follow "sandbox-cleanup-default" 1s 391ms

And I check radio button "weekly" 10s 79ms

And I select "Friday" from "date_day_week" 62ms

And I click on "Update Schedule" 705ms

Then I should see a "Schedule sandbox-cleanup-default has been updated." text 87ms

When I follow the left menu "Admin > Task Schedules" 77ms

And I follow "sandbox-cleanup-default" 1s 214ms

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
13s 665ms 9

When I follow the left menu "Admin > Task Schedules" 57ms

And I follow "sandbox-cleanup-default" 1s 206ms

And I check radio button "monthly" 10s 79ms

And I select "17" from "date_day_month" 64ms

And I click on "Update Schedule" 724ms

Then I should see a "Schedule sandbox-cleanup-default has been updated." text 82ms

When I follow the left menu "Admin > Task Schedules" 62ms

And I follow "sandbox-cleanup-default" 1s 372ms

Then radio button "monthly" should be checked 15ms

Scenario:
Change the schedule of task sandbox-cleanup-default back to daily
14s 531ms 8

When I follow the left menu "Admin > Task Schedules" 57ms

And I follow "sandbox-cleanup-default" 1s 50ms

And I check radio button "daily" 10s 59ms

And I click on "Update Schedule" 1s 896ms

Then I should see a "Schedule sandbox-cleanup-default has been updated." text 85ms

When I follow the left menu "Admin > Task Schedules" 62ms

And I follow "sandbox-cleanup-default" 1s 304ms

Then radio button "daily" should be checked 15ms

@scope_visualization
Feature:Test the notification/notification-messages feature 13s 134ms 4

Scenario:
Log in as org admin user
1s 961ms 1

Given I am authorized 1s 961ms

Scenario:
Check the unread notification counter is correct
10s 401ms 4

All notification-messages are read, I expect no notification badge

When I follow the left menu "Home > Notification Messages" 71ms

And I wait until I see "The server has collected the following notification messages." text 242ms

Then I follow "Unread Messages" 60ms

And the notification badge and the table should count the same amount of messages 10s 26ms

Scenario:
Delete notification-messages
381ms 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 229ms

Then I follow "All Messages" 65ms

Then I check the first notification message 13ms

And I delete it via the "Delete" button 12ms

Scenario:
Flag a notification-message as read
390ms 5

There are no notification messages, nothing to do then

When I follow the left menu "Home > Notification Messages" 55ms

And I wait until I see "The server has collected the following notification messages." text 250ms

Then I follow "All Messages" 58ms

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 13s 76ms 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
2s 233ms 1

Given I am authorized for the "Admin" section 2s 233ms

Scenario:
Enter minimal information for payg ssh connection data
1s 667ms 11

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 183ms

And I click on "Add PAYG Connection" 424ms

And I enter "My Instance" as "description" 93ms

And I enter "my-host.local" as "host" 86ms

And I enter "root" as "username" 55ms

And I click on "Create" 69ms

Then I should see a "PAYG my-host.local created successfully" text 671ms

And I should see a "My Instance" text in element "Info-panel-wrapper" 20ms

And I should see a "my-host.local" text in element "Instance-panel-wrapper" 22ms

And I should see a "root" text in element "Instance-panel-wrapper" 19ms

And I should see a "Delete" button 20ms

Scenario:
Enter full information for payg ssh connection data
1m 3s 104ms 31

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 75ms

And I click on "Add PAYG Connection" 384ms

And I enter "My Full Instance" as "description" 96ms

And I enter "my-host-full.local" as "host" 105ms

And I enter "21" as "port" 51ms

And I enter "rootFull" as "username" 68ms

And I enter "passwordFull" as "password" 74ms

And I enter "keyFull" as "key" 70ms

And I enter "keyPasswordFull" as "key_password" 91ms

And I enter "my-bastion.local" as "bastion_host" 90ms

And I enter "22" as "bastion_port" 52ms

And I enter "b_rootFull" as "bastion_username" 74ms

And I enter "b_passwordFull" as "bastion_password" 87ms

And I enter "b_keyFull" as "bastion_key" 81ms

And I enter "b_keyPasswordFull" as "bastion_key_password" 93ms

And I click on "Create" 55ms

Then I should see a "PAYG my-host-full.local created successfully" text 1s 246ms

And I should see a "My Full Instance" text in element "Info-panel-wrapper" 17ms

And I should see a "my-host-full.local" text in element "Instance-panel-wrapper" 18ms

And I should see a "21" text in element "Instance-panel-wrapper" 20ms

And I should see a "rootFull" text in element "Instance-panel-wrapper" 19ms

And I should not see a "passwordFull" text in element "Instance-panel-wrapper" 10s 47ms

And I should not see a "keyFull" text in element "Instance-panel-wrapper" 10s 33ms

And I should not see a "keyPasswordFull" text in element "Instance-panel-wrapper" 10s 16ms

And I should see a "my-bastion.local" text in element "Bastion-panel-wrapper" 20ms

And I should see a "22" text in element "Bastion-panel-wrapper" 17ms

And I should see a "b_rootFull" text in element "Bastion-panel-wrapper" 17ms

And I should not see a "b_passwordFull" text in element "Bastion-panel-wrapper" 10s 28ms

And I should not see a "b_keyFull" text in element "Bastion-panel-wrapper" 10s 17ms

And I should not see a "b_keyPasswordFull" text in element "Bastion-panel-wrapper" 10s 10ms

And I should see a "Delete" button 20ms

Scenario:
Check pay-as-you-go list
277ms 5

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 93ms

Then I should see a "my-host.local" link 26ms

And I should see a "My Instance" text 74ms

And I should see a "my-host-full.local" link 11ms

And I should see a "My Full Instance" text 71ms

Scenario:
Edit connection description
899ms 7

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 65ms

And I follow "my-host-full.local" 328ms

And I click on "Edit Information" 67ms

And I enter "My new Full Instance" as "description" 120ms

And I click on "Save" in "Information" modal 221ms

Then I should see a "PAYG properties updated successfully" text 75ms

And I should see a "My new Full Instance" text in element "Info-panel-wrapper" 20ms

Scenario:
Edit instance ssh connection data
31s 735ms 15

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 68ms

And I follow "my-host-full.local" 439ms

And I click on "Edit Instance" 66ms

And I enter "221" as "port" 60ms

And I enter "NewRootFull" as "username" 101ms

And I enter "NewPasswordFull" as "password" 86ms

And I enter "newKeyFull" as "key" 82ms

And I enter "newKeyPasswordFull" as "key_password" 96ms

And I click on "Save" in "Instance SSH connection" modal 552ms

Then I should see a "PAYG properties updated successfully" text 76ms

And I should see a "221" text in element "Instance-panel-wrapper" 25ms

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 18ms

And I should not see a "newKeyFull" text in element "Instance-panel-wrapper" 10s 15ms

And I should not see a "newKeyPasswordFull" text in element "Instance-panel-wrapper" 10s 25ms

Scenario:
Edit bastion ssh connection data
31s 630ms 17

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 95ms

And I follow "my-host-full.local" 393ms

And I click on "Edit Bastion" 66ms

And I enter "my-new-bastion.local" as "bastion_host" 156ms

And I enter "222" as "bastion_port" 59ms

And I enter "b_new_rootFull" as "bastion_username" 105ms

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" 99ms

And I click on "Save" in "Bastion SSH connection" modal 263ms

Then I should see a "PAYG properties updated successfully" text 75ms

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" 17ms

And I should not see a "b_new_passwordFull" text in element "Bastion-panel-wrapper" 10s 29ms

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 25ms

Scenario:
Cleanup: delete minimal information for payg ssh connection data
886ms 6

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 93ms

And I follow "my-host.local" 394ms

And I click on "Delete" 72ms

And I click on "Delete" in "Delete PAYG Connection" modal 96ms

Then I should not see a "my-host.local" link 8ms

And I should not see a "my-host.local" text 220ms

Scenario:
Cleanup: delete full information for payg ssh connection data
642ms 6

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 71ms

And I follow "my-host-full.local" 332ms

And I click on "Delete" 61ms

And I click on "Delete" in "Delete PAYG Connection" modal 91ms

Then I should not see a "my-bastion.local" link 8ms

And I should not see a "my-host.local" text 77ms

@sle_minion @scc_credentials @skip_if_github_validation
Feature:Push a package with unset vendor 1m 39s 384ms 2 2

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
2s 442ms 1

Given I am authorized 2s 442ms

Scenario:
Pre-requisite: mgr-push package must be installed on the SLES minion
43s 574ms 12

Given I am on the Systems overview page of this "sle_minion" 1s 959ms

When I follow "Software" in the content area 76ms

And I wait until I see "Upgrade Packages" text 62ms

And I follow "Install" 562ms

And I wait until I see "Installable Packages" text 122ms

And I enter "mgr-push" as the filtered package name 42ms

And I click on the filter button 626ms

And I check "mgr-push" in the list 64ms

And I click on "Install Packages" 626ms

And I click on "Confirm" 746ms

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 38s 626ms

Scenario:
Push a package with unset vendor through the SLES minion
23s 299ms 2 1 1

When I copy unset package file on "sle_minion" 2s 204ms

And I push package "/root/subscription-tools-1.0-0.noarch.rpm" into "fake-base-channel-suse-like" channel through "sle_minion" 797ms 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:31: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

20s 297ms Show Info + 
15:51:58:000 - 15:52:01:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010023&aid=316
Screenshot +

Scenario:
Check vendor of package displayed in web UI
30s 67ms 4 2 1

When I follow the left menu "Software > Channel List > All" 200ms

And I follow "Fake-Base-Channel-SUSE-like" 590ms

And I follow "Packages" 488ms

And I follow "subscription-tools-1.0-0.noarch" 10s 15ms 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:38: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

18s 771ms Show Info + 
15:52:22:000 - 15:52:33: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 38ms 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
2s 256ms 1

Given I am authorized for the "Admin" section 2s 256ms

Scenario:
Populate the report database after bootstrapping minions
15s 114ms 1

When I schedule a task to update ReportDB 15s 114ms

Scenario:
Connect to the ReportDB on the server with admin user
5s 734ms 2

Then I should be able to connect to the ReportDB on the server 3s 88ms

And there should be a user allowed to create roles on the ReportDB 2s 646ms

Scenario:
Create read-only user
8s 682ms 2

When I create a read-only user for the ReportDB 3s 998ms

Then I should see the read-only user listed on the ReportDB user accounts 4s 684ms

Scenario:
External read-only user can connect to ReportDB and make queries
67ms 2

When I connect to the ReportDB with read-only user from external machine 65ms

Then I should be able to query the ReportDB 1ms

Scenario:
Read-only user can't make changes in the ReportDB
5ms 6

Then I should not be able to "insert" data in a ReportDB "table" as a read-only user 2ms

And I should not be able to "update" data in a ReportDB "table" as a read-only user 1ms

And I should not be able to "delete" data in a ReportDB "table" as a read-only user < 1ms

And I should not be able to "insert" data in a ReportDB "view" as a read-only user < 1ms

And I should not be able to "update" data in a ReportDB "view" as a read-only user < 1ms

And I should not be able to "delete" data in a ReportDB "view" as a read-only user < 1ms

Scenario:
ReportDB admin user can't access product database from external machine
5s 235ms 3

Given I know the ReportDB admin user credentials 5s 113ms

Then I should be able to connect to the ReportDB with the ReportDB admin user 60ms

And I should not be able to connect to product database with the ReportDB admin user 61ms

Scenario:
The systems should match between the UI and the ReportDB
10s 190ms 3

When I follow the left menu "Systems > System List > All" 188ms

And I make a list of the existing systems 10s 1ms

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
37s 837ms 4

Search by hostname: uyuni-master-suse-minion
[{"last_boot"=>"2026-04-22T12:06:01Z", "name"=>"uyuni-master-suse-minion.sumaci.aws", "id"=>1000010023, "last_checkin"=>"2026-04-22T13:51:37Z"}]

Given I have a property "City" with value "Arrakeen" on "sle_minion" 15s 971ms

And I know the current synced_date for "sle_minion" 1ms

When I schedule a task to update ReportDB 21s 863ms

Then I should find the updated "City" property as "Arrakeen" on the "sle_minion", on ReportDB 1ms

Scenario:
Cleanup: delete read-only user
28s 914ms 2 1

When I delete the read-only user for the ReportDB 5s 265ms

Then I shouldn't see the read-only user listed on the ReportDB user accounts 2s 900ms Show Error + 
                                            
 Created read-only user on the ReportDB remains listed (ScriptError)
./features/step_definitions/command_steps.rb:1427: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 748ms Show Info + 
15:54:31:000 - 15:54:39: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 34s 748ms 12 3

* Related GitHub Card: https://github.com/SUSE/spacewalk/issues/23463

Scenario:
Log in as org admin user
2s 61ms 1

Given I am authorized 2s 61ms

Scenario:
Check if Distribution Channel Mapping page exists
308ms 8

When I follow the left menu "Software > Distribution Channel Mapping" 129ms

Then I should see a "Distribution Channel Mapping" text 54ms

And I should see a "Channel List" link in the left menu 25ms

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 21ms

And I should see a "Create Distribution Channel Mapping" link 10ms

And I should see a "No distribution channel mappings currently exist." text in the content area 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 859ms 9

When I follow the left menu "Software > Distribution Channel Mapping" 61ms

And I follow "Create Distribution Channel Mapping" 739ms

Then I should see a "Create Distribution Channel Map" text 57ms

When I enter "openSUSE Tumbleweed" as "os" 72ms

And I enter "20250928" as "release" 56ms

And I select "x86_64" from "architecture" 65ms

And I select "openSUSE Tumbleweed (x86_64)" from "channel_label" 59ms

And I click on "Create Mapping" 60ms

Then I should see a "openSUSE Tumbleweed" link in the content area 686ms

@deblike_minion
Scenario:
Create new map for amd64 Ubuntu clients with test base channel
1s 238ms 9

When I follow the left menu "Software > Distribution Channel Mapping" 64ms

And I follow "Create Distribution Channel Mapping" 335ms

Then I should see a "Create Distribution Channel Map" text 57ms

When I enter "Ubuntu 24.04" as "os" 57ms

And I enter "24.04" as "release" 47ms

And I select "AMD64 Debian" from "architecture" 54ms

And I select "Fake-Base-Channel-Debian-like" from "channel_label" 55ms

And I click on "Create Mapping" 543ms

Then I should see a "Ubuntu 24.04" link in the content area 22ms

@scc_credentials
Scenario:
Create new map for iSeries SUSE clients using test channel
1s 209ms 9

When I follow the left menu "Software > Distribution Channel Mapping" 64ms

And I follow "Create Distribution Channel Mapping" 285ms

Then I should see a "Create Distribution Channel Map" text 58ms

When I enter "SUSE Linux Enterprise Server 15 SP 4 iSeries" as "os" 89ms

And I enter "15.5" as "release" 47ms

And I select "iSeries" from "architecture" 56ms

And I select "Fake-Base-Channel-i586" from "channel_label" 55ms

And I click on "Create Mapping" 530ms

Then I should see a "SUSE Linux Enterprise Server 15 SP 4 iSeries" link in the content area 22ms

@scc_credentials @susemanager
Scenario:
Update map for x86_64 SUSE clients using test-x86_64 channel
< 1ms 11

When I follow the left menu "Software > Distribution Channel Mapping" 0s

Then I should see the text "SUSE Linux Enterprise Server 15 SP 4" in the Operating System field 0s

And I should see the text "x86_64" in the Architecture field 0s

And I should see the text "sle-product-sles15-sp7-pool-x86_64" in the Channel Label field 0s

When I follow "SUSE Linux Enterprise Server 15 SP 4" 0s

Then I should see a "Update Distribution Channel Map" text 0s

When I enter "SUSE Linux Enterprise Server 15 SP 4 modified" as "os" 0s

And I select "SLE-Product-SLES15-SP7-Pool for x86_64" from "channel_label" 0s

And I click on "Update Mapping" 0s

Then I should see the text "SUSE Linux Enterprise Server 15 SP 4 modified" in the Operating System field 0s

And I should see the text "sle-product-sles15-sp7-pool-x86_64" in the Channel Label field 0s

@scc_credentials @uyuni
Scenario:
Update map for x86_64 openSUSE clients using test-x86_64 channel
50s 690ms 11

When I follow the left menu "Software > Distribution Channel Mapping" 70ms

Then I should see the text "openSUSE Tumbleweed" in the Operating System field 10s 2ms

And I should see the text "x86_64" in the Architecture field 10s 11ms

And I should see the text "opensuse_tumbleweed-x86_64" in the Channel Label field 10s 7ms

When I follow "openSUSE Tumbleweed" 308ms

Then I should see a "Update Distribution Channel Map" text 56ms

When I enter "openSUSE Tumbleweed modified" as "os" 102ms

And I select "openSUSE Tumbleweed (x86_64)" from "channel_label" 47ms

And I click on "Update Mapping" 63ms

Then I should see the text "openSUSE Tumbleweed modified" in the Operating System field 10s 10ms

And I should see the text "opensuse_tumbleweed-x86_64" in the Channel Label field 10s 7ms

@deblike_minion
Scenario:
Update map for amd64 Ubuntu clients using test base channel
41s 163ms 8

When I follow the left menu "Software > Distribution Channel Mapping" 83ms

Then I should see the text "Ubuntu 24.04" in the Operating System field 10s 7ms

And I should see the text "AMD64 Debian" in the Architecture field 10s 6ms

And I should see the text "fake-base-channel-debian-like" in the Channel Label field 10s 5ms

When I follow "Ubuntu 24.04" 364ms

And I enter "Ubuntu 24.04 modified" as "os" 90ms

And I click on "Update Mapping" 599ms

Then I should see the text "Ubuntu 24.04 modified" in the Operating System field 10s 5ms

@scc_credentials
Scenario:
Update map for IA-32 SUSE clients using amd deb test channel
52s 193ms 10

When I follow the left menu "Software > Distribution Channel Mapping" 77ms

Then I should see the text "SUSE Linux Enterprise Server 15 SP 4 iSeries" in the Operating System field 10s 8ms

And I should see the text "iSeries" in the Architecture field 10s 9ms

And I should see the text "fake-base-channel-i586" in the Channel Label field 10s 11ms

When I follow "SUSE Linux Enterprise Server 15 SP 4 iSeries" 1s 232ms

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" 625ms

Then I should see the text "SUSE Linux Enterprise Server 15 SP 4 iSeries modified" in the Operating System field 10s 11ms

And I should see the text "fake-base-channel-debian-like" in the Channel Label field 10s 1ms

@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 302ms 10

When I follow the left menu "Software > Distribution Channel Mapping" 82ms

Then I should see the text "openSUSE Tumbleweed modified" in the Operating System field 10s 5ms

And I should see the text "x86_64" in the Architecture field 10s 13ms

When I follow "openSUSE Tumbleweed modified" 308ms

Then I should see a "Update Distribution Channel Map" text 54ms

And I should see a "Delete Distribution Channel" link 11ms

When I follow "Delete Distribution Channel Mapping" 307ms

Then I should see a "Delete Distribution Channel Map" text 55ms

When I click on "Delete Mapping" 455ms

Then I should not see a "openSUSE Tumbleweed modified" link 8ms

@deblike_minion
Scenario:
Cleanup: delete the map created for amd64 Ubuntu clients
21s 372ms 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 1ms

And I should see the text "AMD64 Debian" in the Architecture field 10s 1ms

When I follow "Ubuntu 24.04 modified" 362ms

Then I should see a "Update Distribution Channel Map" text 54ms

And I should see a "Delete Distribution Channel" link 11ms

When I follow "Delete Distribution Channel Mapping" 317ms

Then I should see a "Delete Distribution Channel Map" text 49ms

When I click on "Delete Mapping" 484ms

Then I should not see a "Ubuntu 24.04 modified" link 9ms

@scc_credentials
Scenario:
Cleanup: delete the map created for i586 clients
21s 195ms 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 6ms

When I follow "SUSE Linux Enterprise Server 15 SP 4 iSeries modified" 289ms

Then I should see a "Update Distribution Channel Map" text 55ms

And I should see a "Delete Distribution Channel" link 11ms

When I follow "Delete Distribution Channel Mapping" 262ms

Then I should see a "Delete Distribution Channel Map" text 51ms

When I click on "Delete Mapping" 425ms

Then I should not see a "SUSE Linux Enterprise Server 15 SP 4 iSeries modified" link 8ms

Scenario:
Sanity check whether the page is in its default state
152ms 3

When I follow the left menu "Software > Distribution Channel Mapping" 75ms

Then I should see a "Distribution Channel Mapping" text 54ms

And I should see a "No distribution channel mappings currently exist." text in the content area 22ms

Feature:Task Engine Status 29s 783ms 4 2

Scenario:
Login as admin
1s 834ms 1

Given I am authorized for the "Admin" section 1s 834ms

@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 715ms 6

When I follow the left menu "Admin > Task Engine Status > Last Execution Times" 1s 395ms

Then I should see a "Task Engine Status" text 91ms

And I should see a "The following is a status report for the various tasks run by the Uyuni task engine:" text 93ms

And I should see a "Runtime Status" text 87ms

And I should see a "Last Execution Times" link in the left menu 25ms

And I should see a "Runtime Status" link in the left menu 21ms

Scenario:
Check if the Runtime Status Page exists
572ms 6

When I follow the left menu "Admin > Task Engine Status > Runtime Status" 73ms

Then I should see a "Task Engine Status" text 55ms

And I should see a "Last Execution Times" text 54ms

And I should see a "The server is running or has finished executing the following tasks during the latest 5 minutes." text 339ms

And I should see a "Last Execution Times" link in the left menu 32ms

And I should see a "Runtime Status" link in the left menu 16ms

Scenario:
Run a remote command on the server to check if it shows up on Last Execution Times page
25s 661ms 6

When I follow the left menu "Admin > Task Engine Status > Last Execution Times" 68ms

And I run "cobbler sync" on "server" 5s 53ms

And I refresh the page 10s 341ms

Then I should see a "Cobbler Sync:" text 96ms

And I should see the correct timestamp for task "Cobbler Sync:" 10s 3ms

And I should see a "FINISHED" text 98ms

@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 794ms 2

@ssh_minion
Scenario:
Check the relevant errata for a system
5s 110ms 1

When I retrieve the relevant errata for ssh_minion 5s 110ms

@ssh_minion @rhlike_minion @deblike_minion
Scenario:
Check the relevant errata for multiple systems
1s 683ms 1

When I retrieve the relevant errata for ssh_minion, rhlike_minion, deblike_minion 1s 683ms

@scope_salt @skip_if_github_validation
Feature:Health Check tool based on a supportconfig 6m 25s 227ms 2 3

A supportconfig generated from the Uyuni server
should be able to be parsed by Health Check tool.

Scenario:
A supportconfig is taken from the server
1m 17s 44ms 2

When I generate a supportconfig for the server 1m 15s 803ms

Then I obtain and extract the supportconfig from the server 1s 240ms

Scenario:
Execute Health Check tool with server supportconfig
19s 929ms 1 1 1

When I start the health check tool with supportconfig "/root/server-supportconfig/uyuni-server-supportconfig/" on "localhost" 452ms Show Error + 
                                            
 FAIL: mgr-health-check -v -s /root/server-supportconfig/uyuni-server-supportconfig/ start returned status code = 1.
Output:
┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃                                 Health Check                                 ┃
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛
[16:01:31] 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:1796:in `/^I start the health check tool with supportconfig "([^"]*)" on "([^"]*)"$/'
features/secondary/srv_health_check_supportconfig.feature:15: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 477ms Show Info + 
16:01:31:000 - 16:01:31:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/admin/TaskStatus.do
Screenshot +

Scenario:
Health Check containers are healthy and running
4m 29s 506ms 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:1573:in `/^I wait until port "([^"]*)" is listening on "([^"]*)" (host|container)$/'
features/secondary/srv_health_check_supportconfig.feature:19: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 505ms Show Info + 
16:01:51:000 - 16:06:01:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/admin/TaskStatus.do
Screenshot +

Scenario:
Health Check containers are exposing metrics
17s 973ms 1 1

Then I check that the health check tool exposes metrics on "localhost" 192ms 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:1824:in `/^I check that the health check tool exposes metrics on "([^"]*)"$/'
features/secondary/srv_health_check_supportconfig.feature:25:in `I check that the health check tool exposes metrics on "localhost"'

17s 781ms Show Info + 
16:06:20:000 - 16:06:21:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/admin/TaskStatus.do
Screenshot +

Scenario:
I can stop the Health Check tool
773ms 3

When I stop health check tool on "localhost" 409ms

Then I check that the health check tool is not running on "localhost" 186ms

And I remove test supportconfig on "localhost" 177ms

@skip_if_github_validation
Feature:Password Policy Management 3m 11s 999ms 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 729ms 1

Given I am authorized as "admin" with password "admin" 1s 729ms

Scenario:
Navigate to Password Policy settings page
973ms 2

When I follow the left menu "Admin > Manager Configuration > Password Policy" 861ms

Then I should see a "Server Configuration - Password Policy" text 112ms

Scenario:
Configure password complexity restrictions
667ms 5

When I set the minimum password length to "5" 51ms

And I set the maximum password length to "12" 52ms

And I enable the following restrictions: 315ms
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 188ms

Scenario:
Verify password complexity restrictions are saved correctly
10s 443ms 2

When I refresh the page 10s 395ms

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
363ms 4

When I set the special characters list to "$@?" 64ms

And I set the maximum allowed occurrence of any character to "3" 49ms

And I click on "Save" 52ms

And I should see a "Password Policy Changed" text 196ms

Scenario Outline:
Reject invalid passwords based on policy enforcement
10s 318ms 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" 10s 318ms

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 125ms 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 125ms

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 786ms 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 786ms

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 553ms 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 553ms

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 546ms 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 546ms

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
30s 588ms 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" 12s 464ms

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: $@?"'

18s 123ms Show Info + 
16:07:58:000 - 16:08:11: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 746ms 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 433ms

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 313ms 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:234:in `block in relog_and_visit_previous_url'
./features/support/env.rb:232:in `relog_and_visit_previous_url'
./features/support/env.rb:212:in `handle_screenshot_and_relog'
./features/support/env.rb:173:in `After'
Show Info + 
16:08:29:000 - 16:08:39: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
10s 90ms 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" 10s 90ms

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 800ms 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 800ms

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 828ms 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 828ms

Then the user creation should succeed < 1ms

Scenario:
Reset password policy to default settings
10s 8ms 4 1

When I follow the left menu "Admin > Manager Configuration > Password Policy" 10s 8ms 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
429ms 1

When I delete user "password_policy_user" 429ms

@skip_if_github_validation @build_host @scope_building_container_images @scope_cve_audit @no_auth_registry
Feature:Build container images and CVE audit them 20m 33s 770ms 16 14

Scenario:
Log in as org admin user
10s 735ms 1

Given I am authorized 10s 735ms

Scenario:
Create a simple image profile without activation key
2s 812ms 6

GITPROFILES: https://github.com/uyuni-project/uyuni.git#:testsuite/features/profiles/temporary

When I follow the left menu "Images > Profiles" 126ms

And I follow "Create" 498ms

And I enter "suse_simple" as "label" 98ms

And I select "galaxy-registry" from "imageStore" 1s 122ms

And I enter "Docker" relative to profiles as "path" 901ms

And I click on "create-btn" 64ms

Scenario:
Create a simple real image profile without activation key
2s 860ms 6

GITPROFILES: https://github.com/uyuni-project/uyuni.git#:testsuite/features/profiles/temporary

When I follow the left menu "Images > Profiles" 63ms

And I follow "Create" 530ms

And I enter "suse_real_simple" as "label" 110ms

And I select "galaxy-registry" from "imageStore" 1s 129ms

And I enter "Docker/serverhost" relative to profiles as "path" 975ms

And I click on "create-btn" 51ms

@scc_credentials
Scenario:
Create an image profile with activation key
3s 831ms 7

GITPROFILES: https://github.com/uyuni-project/uyuni.git#:testsuite/features/profiles/temporary

When I follow the left menu "Images > Profiles" 56ms

And I follow "Create" 505ms

And I enter "suse_key" as "label" 85ms

And I select "galaxy-registry" from "imageStore" 1s 109ms

And I select "1-SUSE-KEY-x86_64" from "activationKey" 1s 122ms

And I enter "Docker" relative to profiles as "path" 898ms

And I click on "create-btn" 52ms

@scc_credentials
Scenario:
Create a simple real image profile with activation key
3s 928ms 7

GITPROFILES: https://github.com/uyuni-project/uyuni.git#:testsuite/features/profiles/temporary

When I follow the left menu "Images > Profiles" 62ms

And I follow "Create" 471ms

And I enter "suse_real_key" as "label" 99ms

And I select "galaxy-registry" from "imageStore" 1s 136ms

And I select "1-SUSE-KEY-x86_64" from "activationKey" 1s 109ms

And I enter "Docker/serverhost" relative to profiles as "path" 996ms

And I click on "create-btn" 53ms

@scc_credentials
Scenario:
Build the suse_key image with and without activation key
1m 7s 225ms 3 2 1

Event Details: ---------- ID: mgr_registries_login Function: module.run Name: docker.login Result: true Comment: Module function docker.login executed Started: 16:12:09.090632 Duration: 1.428 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: 16:12:09.092607 Duration: 14150.198 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: 16:12:23.243373 Duration: 0.007 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: 16:12:23.243914 Duration: 0.004 SLS: images.docker Changed: {} ---------- ID: mgr_buildimage_docker_collect_logs Function: file.touch Name: /var/log/image-build317.log Result: true Comment: Updated times on file /var/log/image-build317.log Started: 16:12:23.247051 Duration: 8.358 SLS: images.docker Changed: touched: /var/log/image-build317.log ---------- ID: mgr_buildimage_docker_collect_logs Function: module.run Name: cp.push Result: true Comment: Module function cp.push executed Started: 16:12:23.255542 Duration: 47.149 SLS: images.docker Changed: ret: true

Given I am on the Systems overview page of this "build_host" 3s 628ms

When I schedule the build of image "suse_key" via API calls 1s 137ms

And I wait at most 660 seconds until event "Image Build suse_key scheduled" is completed 41s 814ms 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 644ms Show Info + 
16:12:03:000 - 16:12:49:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010004&aid=317
Screenshot +

Scenario:
Check the list of packages is not empty
19s 523ms 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 726ms 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 797ms Show Info + 
16:13:10:000 - 16:13:11:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010004&aid=317
Screenshot +

Scenario:
Build the suse_simple image with and without activation key
1m 2s 806ms 3 2 1

Event Details: ---------- ID: mgr_registries_login Function: module.run Name: docker.login Result: true Comment: Module function docker.login executed Started: 16:13:33.938196 Duration: 1.462 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: 16:13:33.940174 Duration: 13699.674 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: 16:13:47.640329 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: 16:13:47.640684 Duration: 0.004 SLS: images.docker Changed: {} ---------- ID: mgr_buildimage_docker_collect_logs Function: file.touch Name: /var/log/image-build318.log Result: true Comment: Updated times on file /var/log/image-build318.log Started: 16:13:47.643454 Duration: 7.771 SLS: images.docker Changed: touched: /var/log/image-build318.log ---------- ID: mgr_buildimage_docker_collect_logs Function: module.run Name: cp.push Result: true Comment: Module function cp.push executed Started: 16:13:47.651350 Duration: 10.167 SLS: images.docker Changed: ret: true

Given I am on the Systems overview page of this "build_host" 1s 80ms

When I schedule the build of image "suse_simple" via API calls 1s 177ms

And I wait at most 660 seconds until event "Image Build suse_simple scheduled" is completed 41s 667ms 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 880ms Show Info + 
16:13:29:000 - 16:14:13:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010004&aid=318
Screenshot +

Scenario:
Check the list of packages is not empty
21s 341ms 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 684ms 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 657ms Show Info + 
16:14:32:000 - 16:14:33:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010004&aid=318
Screenshot +

@scc_credentials
Scenario:
Build the suse_real_key image with and without activation key
3m 32s 245ms 4 3 1

2026-04-22 16:17:36 +0200 Still waiting for action to complete...

Given I am on the Systems overview page of this "build_host" 1s 225ms

When I schedule the build of image "suse_real_key" via API calls 965ms

And I wait at most 660 seconds until event "Image Build suse_real_key scheduled" is completed 3m 8s 69ms

And I wait at most 60 seconds until all "3" container images are built correctly on the Image List page 1s 458ms 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 525ms Show Info + 
16:14:54:000 - 16:18:05:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

Scenario:
Check the list of packages is not empty
20s 395ms 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 873ms 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 521ms Show Info + 
16:18:26:000 - 16:18:27: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 55s 521ms 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 809ms

And I wait at most 900 seconds until image "suse_key" with version "Latest_key-activation1" is built successfully via API 1m 33s 712ms 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

20s 999ms Show Info + 
16:18:46:000 - 16:20:21:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

Scenario:
Check the list of packages is not empty
20s 105ms 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"=>"1b719b3c602d6a329f8c7b1119273612c5a9f5c8b7b61836503783cedbbbb5f2", "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 672ms 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'

19s 433ms Show Info + 
16:20:42:000 - 16:20:43:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

Scenario:
Build suse_simple image with different versions
42s 852ms 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"=>"1b719b3c602d6a329f8c7b1119273612c5a9f5c8b7b61836503783cedbbbb5f2", "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 758ms

And I wait at most 900 seconds until image "suse_simple" with version "Latest_simple" is built successfully via API 22s 70ms 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 23ms Show Info + 
16:21:02:000 - 16:21:25:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

Scenario:
Check the list of packages is not empty
19s 144ms 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"=>"1b719b3c602d6a329f8c7b1119273612c5a9f5c8b7b61836503783cedbbbb5f2", "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 714ms 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 429ms Show Info + 
16:21:45:000 - 16:21:46:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

@scc_credentials
Scenario:
Delete image via API calls with key
4s 89ms 3

When I delete the image "suse_key" with version "Latest_key-activation1" via API calls 1s 297ms

Then the image "suse_simple" with version "Latest_key-activation1" doesn't exist via API calls 614ms

When I wait until no Salt job is running on "build_host" 2s 178ms

Scenario:
Delete image via API calls without key
2s 960ms 3

When I delete the image "suse_simple" with version "Latest_simple" via API calls 830ms

Then the image "suse_simple" with version "Latest_simple" doesn't exist via API calls 403ms

When I wait until no Salt job is running on "build_host" 1s 727ms

Scenario:
Rebuild suse_simple image
41s 589ms 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"=>"1b719b3c602d6a329f8c7b1119273612c5a9f5c8b7b61836503783cedbbbb5f2", "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 769ms

And I wait at most 900 seconds until image "suse_simple" with version "Latest_simple" is built successfully via API 22s 33ms 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 785ms Show Info + 
16:22:11:000 - 16:22:34:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

Scenario:
Check the list of packages is not empty
21s 398ms 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"=>"1b719b3c602d6a329f8c7b1119273612c5a9f5c8b7b61836503783cedbbbb5f2", "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 894ms 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'

20s 504ms Show Info + 
16:22:53:000 - 16:22:54:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

@scc_credentials
Scenario:
Rebuild suse_key image
43s 453ms 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"=>"1b719b3c602d6a329f8c7b1119273612c5a9f5c8b7b61836503783cedbbbb5f2", "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 822ms

And I wait at most 900 seconds until image "suse_key" with version "Latest_key-activation1" is built successfully via API 21s 873ms 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 757ms Show Info + 
16:23:14:000 - 16:23:37:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

Scenario:
Check the list of packages is not empty
20s 644ms 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"=>"1b719b3c602d6a329f8c7b1119273612c5a9f5c8b7b61836503783cedbbbb5f2", "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 677ms 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 967ms Show Info + 
16:23:58:000 - 16:23:58:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

@scc_credentials
Scenario:
Build an image via the GUI
3m 49s 677ms 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"=>"1b719b3c602d6a329f8c7b1119273612c5a9f5c8b7b61836503783cedbbbb5f2", "obsolete"=>false, "id"=>3, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>1}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>6, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>7, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_real_key", "checksum"=>"", "obsolete"=>false, "id"=>8, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>0}]
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010004, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>8, "arch"=>"x86_64", "enhancementErrata"=>0}
List of images: [{"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>1, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>2, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_real_key", "checksum"=>"1b719b3c602d6a329f8c7b1119273612c5a9f5c8b7b61836503783cedbbbb5f2", "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"=>"9ba650433ecf7bbf83313ec1eb5689a7e3ea4f233a359b863e855f8ae3ebcf71", "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 148ms

And I enter "GUI_BUILT_IMAGE" as "version" 299ms

And I select the hostname of "build_host" from "buildHostId" 1s 115ms

And I click on "submit-btn" 63ms

And I wait until no Salt job is running on "build_host" 2m 35s 959ms

Then I wait until I see "GUI_BUILT_IMAGE" text 99ms

And I wait at most 900 seconds until image "suse_real_key" with version "GUI_BUILT_IMAGE" is built successfully via API 5s 762ms

And I wait at most 300 seconds until image "suse_real_key" with version "GUI_BUILT_IMAGE" is inspected successfully via API 1m 5s 145ms

@scc_credentials
Scenario:
Login as Docker image administrator and build an image
3m 51s 656ms 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"=>"1b719b3c602d6a329f8c7b1119273612c5a9f5c8b7b61836503783cedbbbb5f2", "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"=>"9ba650433ecf7bbf83313ec1eb5689a7e3ea4f233a359b863e855f8ae3ebcf71", "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"=>"1b719b3c602d6a329f8c7b1119273612c5a9f5c8b7b61836503783cedbbbb5f2", "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"=>"9ba650433ecf7bbf83313ec1eb5689a7e3ea4f233a359b863e855f8ae3ebcf71", "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"=>"ea963cb8ea7331473d0971f8deaddf6a91ddadf27d26e5645a70f135449b610f", "files"=>[], "id"=>9, "arch"=>"x86_64", "enhancementErrata"=>0}

Given I am authorized as "docker" with password "docker" 2s 56ms

When I follow the left menu "Images > Build" 116ms

And I select "suse_real_key" from "profileId" 1s 119ms

And I enter "GUI_DOCKERADMIN" as "version" 242ms

And I select the hostname of "build_host" from "buildHostId" 1s 110ms

And I click on "submit-btn" 55ms

And I wait until no Salt job is running on "build_host" 2m 33s 595ms

Then I wait until I see "GUI_DOCKERADMIN" text 99ms

And I wait at most 900 seconds until image "suse_real_key" with version "GUI_DOCKERADMIN" is built successfully via API 5s 373ms

And I wait at most 300 seconds until image "suse_real_key" with version "GUI_DOCKERADMIN" is inspected successfully via API 1m 7s 887ms

@scc_credentials
Scenario:
Audit images, searching for a known CVE number
882ms 5

When I follow the left menu "Audit > CVE Audit" 121ms

And I select "1999" from "cveIdentifierYear" 88ms

And I enter "9999" as "cveIdentifierId" 63ms

And I click on "Audit Images" 58ms

Then I should see a "No action required" text 549ms

Scenario:
Audit images, searching for an unknown CVE number
406ms 5

When I follow the left menu "Audit > CVE Audit" 65ms

And I select "2012" from "cveIdentifierYear" 57ms

And I enter "2806" as "cveIdentifierId" 58ms

And I click on "Audit Images" 50ms

Then I should see a "The specified CVE number was not found" text 174ms

@scc_credentials
Scenario:
Cleanup: delete all images with key
5s 330ms 6

Given I am authorized as "admin" with password "admin" 1s 176ms

When I delete the image "suse_key" with version "latest" via API calls 1s 355ms

And I delete the image "suse_key" with version "Latest_key-activation1" via API calls 690ms

And I delete the image "suse_real_key" with version "latest" via API calls 735ms

And I delete the image "suse_real_key" with version "GUI_BUILT_IMAGE" via API calls 692ms

And I delete the image "suse_real_key" with version "GUI_DOCKERADMIN" via API calls 679ms

Scenario:
Cleanup: delete images without key
2s 327ms 3

Given I am authorized as "admin" with password "admin" 395ms

When I delete the image "suse_simple" with version "latest" via API calls 1s 223ms

And I delete the image "suse_simple" with version "Latest_simple" via API calls 708ms

@scc_credentials
Scenario:
Cleanup: delete all profiles with key
1s 342ms 7

When I follow the left menu "Images > Profiles" 131ms

And I check "suse_key" in the list 744ms

And I check "suse_real_key" in the list 58ms

And I click on "Delete" 79ms

And I should see a "Are you sure you want to delete selected profiles?" text 78ms

And I click on the red confirmation button 67ms

And I wait until I see "Image profiles have been deleted" text 180ms

Scenario:
Cleanup: delete all profiles without key
608ms 7

When I follow the left menu "Images > Profiles" 60ms

And I check "suse_simple" in the list 127ms

And I check "suse_real_simple" in the list 58ms

And I click on "Delete" 59ms

And I should see a "Are you sure you want to delete selected profiles?" text 67ms

And I click on the red confirmation button 64ms

And I wait until I see "Image profiles have been deleted" text 170ms

Scenario:
Cleanup: Make sure no job is left running on buildhost
2s 72ms 1

When I wait until no Salt job is running on "build_host" 2s 72ms

@skip_if_github_validation @build_host @scope_building_container_images @auth_registry
Feature:Build image with authenticated registry 1m 13s 311ms 6 2

Scenario:
Log in as docker user
2s 52ms 1

Given I am authorized as "docker" with password "docker" 2s 52ms

Scenario:
Create an authenticated image store as Docker admin
1s 154ms 7

AUTH_REGISTRY_CREDENTIALS: cucutest|cucusecret

When I follow the left menu "Images > Stores" 108ms

And I follow "Create" 271ms

And I enter "auth_registry" as "label" 94ms

And I check "useCredentials" 147ms

And I enter URI, username and password for registry 412ms

And I click on "create-btn" 64ms

Then I wait until I see "registry" text 55ms

@scc_credentials
Scenario:
Create a profile for the authenticated image store as Docker admin
4s 338ms 8

GITPROFILES: https://github.com/uyuni-project/uyuni.git#:testsuite/features/profiles/temporary

When I follow the left menu "Images > Profiles" 75ms

And I follow "Create" 409ms

And I enter "auth_registry_profile" as "label" 146ms

And I select "auth_registry" from "imageStore" 1s 123ms

And I select "1-SUSE-KEY-x86_64" from "activationKey" 1s 124ms

And I enter "Docker/authprofile" relative to profiles as "path" 1s 15ms

And I click on "create-btn" 56ms

Then I wait until I see "auth_registry_profile" text 387ms

@scc_credentials
Scenario:
Build an image in the authenticated image store
43s 469ms 7 4 1

List of images: [{"external"=>false, "name"=>"auth_registry_profile", "checksum"=>"", "obsolete"=>false, "id"=>10, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"auth_registry", "revision"=>0}]
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010004, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"auth_registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"auth_registry_profile", "name"=>"auth_registry_profile", "checksum"=>"", "files"=>[], "id"=>10, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010004, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"auth_registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"auth_registry_profile", "name"=>"auth_registry_profile", "checksum"=>"", "files"=>[], "id"=>10, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010004, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"auth_registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"auth_registry_profile", "name"=>"auth_registry_profile", "checksum"=>"", "files"=>[], "id"=>10, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010004, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"auth_registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"failed", "external"=>false, "profileLabel"=>"auth_registry_profile", "name"=>"auth_registry_profile", "checksum"=>"", "files"=>[], "id"=>10, "arch"=>"x86_64", "enhancementErrata"=>0}

When I follow the left menu "Images > Build" 66ms

And I select "auth_registry_profile" from "profileId" 1s 134ms

And I enter "latest" as "version" 141ms

And I select the hostname of "build_host" from "buildHostId" 1s 119ms

And I click on "submit-btn" 60ms

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 205ms 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

19s 667ms Show Info + 
16:32:34:000 - 16:32:58:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

Scenario:
Check the list of packages is not empty
18s 758ms 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 356ms 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'

18s 402ms Show Info + 
16:33:18:000 - 16:33:18: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 712ms 6

When I follow the left menu "Images > Profiles" 77ms

And I check the row with the "auth_registry_profile" text 122ms

And I click on "Delete" 85ms

And I click on the red confirmation button 66ms

And I should see a "Image profile has been deleted." text 144ms

And I wait until no Salt job is running on "build_host" 2s 215ms

Scenario:
Cleanup: remove authenticated image store
464ms 5

When I follow the left menu "Images > Stores" 64ms

And I check the row with the "auth_registry" text 114ms

And I click on "Delete" 65ms

And I click on the red confirmation button 57ms

And I should see a "Image store has been deleted." text 161ms

Scenario:
Cleanup: delete registry image
361ms 1

When I delete the image "auth_registry_profile" with version "latest" via API calls 361ms

@scope_visualization
Feature:The system details of each minion and client provides an overview of the system 2m 36s 427ms 9

Scenario:
Log in as org admin user
1s 133ms 1

Given I am authorized 1s 133ms

@sle_minion
Scenario:
SLE minion hardware refresh
44s 440ms 6

Given I navigate to the Systems overview page of this "sle_minion" 2s 441ms

When I follow "Hardware" 507ms

And I click on "Schedule Hardware Refresh" 83ms

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 38s 931ms

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "sle_minion" 2s 353ms

@sle_minion
Scenario:
Minion grains are displayed correctly on the details page
4s 64ms 19

I should see kernel version: 6.19.11-1-default
IPv4 address: 172.16.3.8
IPv6 address: fe80::427:a3ff:fe60:477f

Given I am on the Systems overview page of this "sle_minion" 963ms

Then the hostname for "sle_minion" should be correct 94ms

And the kernel for "sle_minion" should be correct 534ms

And the OS version for "sle_minion" should be correct < 1ms

And the IPv4 address for "sle_minion" should be correct 85ms

And the IPv6 address for "sle_minion" should be correct 457ms

And the system ID for "sle_minion" should be correct 447ms

And the system name for "sle_minion" should be correct 84ms

And the uptime for "sle_minion" should be correct 560ms

And I should see a "UUID" text 81ms

And I should see a "Virtualization" text 82ms

And I should see a "Installed Products" text 86ms

And I should see a "Checked In" text 83ms

And I should see a "Registered" text 84ms

And I should see a "Contact Method" text 84ms

And I should see a "Auto Patch Update" text 82ms

And I should see a "Maintenance Schedule" text 81ms

And I should see a "Description" text 83ms

And I should see a "Location" text 83ms

@rhlike_minion
Scenario:
Red Hat-like minion hardware refresh
26s 586ms 6

Given I am on the Systems overview page of this "rhlike_minion" 1s 166ms

When I follow "Hardware" 658ms

And I click on "Schedule Hardware Refresh" 735ms

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 22s 55ms

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "rhlike_minion" 1s 848ms

@rhlike_minion
Scenario:
Red Hat-like minion grains are displayed correctly on the details page
3s 155ms 19

I should see kernel version: 4.18.0-553.el8_10.x86_64
IPv4 address: 172.16.3.10
IPv6 address: fe80::4f7:2fff:fe05:2939

Given I am on the Systems overview page of this "rhlike_minion" 920ms

Then the hostname for "rhlike_minion" should be correct 102ms

And the kernel for "rhlike_minion" should be correct 279ms

And the OS version for "rhlike_minion" should be correct < 1ms

And the IPv4 address for "rhlike_minion" should be correct 82ms

And the IPv6 address for "rhlike_minion" should be correct 203ms

And the system ID for "rhlike_minion" should be correct 456ms

And the system name for "rhlike_minion" should be correct 95ms

And the uptime for "rhlike_minion" should be correct 200ms

And I should see a "UUID" text 79ms

And I should see a "Virtualization" text 80ms

And I should see a "Installed Products" text 79ms

And I should see a "Checked In" text 78ms

And I should see a "Registered" text 87ms

And I should see a "Contact Method" text 80ms

And I should see a "Auto Patch Update" text 79ms

And I should see a "Maintenance Schedule" text 83ms

And I should see a "Description" text 81ms

And I should see a "Location" text 84ms

@deblike_minion
Scenario:
Debian-like minion hardware refresh
28s 153ms 6

Given I am on the Systems overview page of this "deblike_minion" 1s 628ms

When I follow "Hardware" 577ms

And I click on "Schedule Hardware Refresh" 772ms

Then I should see a "You have successfully scheduled a hardware profile refresh" text 118ms

When I wait until event "Hardware List Refresh scheduled" is completed 21s 826ms

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "deblike_minion" 3s 229ms

@deblike_minion
Scenario:
Debian-like minion grains are displayed correctly on the details page
3s 549ms 19

I should see kernel version: 6.17.0-1010-aws
IPv4 address: 172.16.3.11
IPv6 address: fe80::4fa:ceff:fe62:6869

Given I am on the Systems overview page of this "deblike_minion" 975ms

Then the hostname for "deblike_minion" should be correct 94ms

And the kernel for "deblike_minion" should be correct 352ms

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 318ms

And the system ID for "deblike_minion" should be correct 556ms

And the system name for "deblike_minion" should be correct 88ms

And the uptime for "deblike_minion" should be correct 256ms

And I should see a "UUID" text 80ms

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 86ms

And I should see a "Registered" text 83ms

And I should see a "Contact Method" text 81ms

And I should see a "Auto Patch Update" text 80ms

And I should see a "Maintenance Schedule" text 82ms

And I should see a "Description" text 82ms

And I should see a "Location" text 81ms

@ssh_minion
Scenario:
SSH-managed minion hardware refresh
41s 30ms 5

Given I am on the Systems overview page of this "ssh_minion" 1s 18ms

When I follow "Hardware" 604ms

And I click on "Schedule Hardware Refresh" 853ms

Then I should see a "You have successfully scheduled a hardware profile refresh" text 119ms

And I wait until event "Hardware List Refresh scheduled" is completed 38s 435ms

@ssh_minion
Scenario:
SSH-managed minion grains are displayed correctly on the details page
4s 313ms 19

I should see kernel version: 6.19.11-1-default
IPv4 address: 172.16.3.9
IPv6 address: fe80::469:26ff:fe6f:94f1

Given I am on the Systems overview page of this "ssh_minion" 997ms

Then the hostname for "ssh_minion" should be correct 95ms

And the kernel for "ssh_minion" should be correct 826ms

And the OS version for "ssh_minion" should be correct < 1ms

And the IPv4 address for "ssh_minion" should be correct 83ms

And the IPv6 address for "ssh_minion" should be correct 433ms

And the system ID for "ssh_minion" should be correct 537ms

And the system name for "ssh_minion" should be correct 93ms

And the uptime for "ssh_minion" should be correct 423ms

And I should see a "UUID" text 79ms

And I should see a "Virtualization" text 80ms

And I should see a "Installed Products" text 84ms

And I should see a "Checked In" text 79ms

And I should see a "Registered" text 87ms

And I should see a "Contact Method" text 80ms

And I should see a "Auto Patch Update" text 84ms

And I should see a "Maintenance Schedule" text 79ms

And I should see a "Description" text 79ms

And I should see a "Location" text 88ms

@scope_ssm @sle_minion @scope_visualization
Feature:Manage a group of systems and the Systems Set Manager 3m 52s 645ms 24 2

Scenario:
Log in as org admin user
422ms 1

Given I am authorized for the "Admin" section 422ms

@skip_if_github_validation
Scenario:
Pre-requisite: install dummy packages to allow patching
6s 226ms 4

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 827ms

And I refresh the metadata for "sle_minion" 1s 124ms

And I install old package "andromeda-dummy-1.0" on this "sle_minion" 2s 181ms

And I install old package "virgo-dummy-1.0" on this "sle_minion" 2s 92ms

Scenario:
Pre-requisite: ensure that fake patches are available
16s 425ms 6

When I follow the left menu "Admin > Task Schedules" 164ms

And I follow "errata-cache-default" 1s 238ms

And I follow "errata-cache-bunch" 1s 288ms

And I click on "Single Run Schedule" 1s 301ms

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 12s 149ms

Scenario:
Pre-requisite: ensure that fake channels were created
944ms 7

When I follow the left menu "Patches > Patch List > Relevant" 218ms

Then I should see an update in the list 67ms

When I wait until I see "andromeda-dummy" text, refreshing the page 243ms

Then I should see a "andromeda-dummy-6789" link 11ms

When I enter "virgo-dummy" as the filtered synopsis 129ms

And I click on the filter button until page does contain "virgo-dummy-3456" text 262ms

Then I should see a "virgo-dummy-3456" link 11ms

Scenario:
Fail to create a group with only its name
838ms 5

When I follow the left menu "Systems > System Groups" 132ms

And I follow "Create Group" 288ms

And I enter "new-systems-group" as "name" 67ms

And I click on "Create Group" 292ms

Then I should see a "Both name and description are required for System Groups." text 58ms

Scenario:
Fail to create a group with only its description
454ms 5

When I follow the left menu "Systems > System Groups" 61ms

And I follow "Create Group" 210ms

And I enter "My new group" as "description" 70ms

And I click on "Create Group" 53ms

Then I should see a "Both name and description are required for System Groups." text 59ms

Scenario:
Create a group
580ms 6

When I follow the left menu "Systems > System Groups" 63ms

And I follow "Create Group" 277ms

And I enter "new-systems-group" as "name" 61ms

And I enter "My new group" as "description" 53ms

And I click on "Create Group" 53ms

Then I should see a "System group new-systems-group created." text 70ms

Scenario:
Add the SLE minion to the group and to SSM
3s 101ms 7

When I follow the left menu "Systems > System Groups" 61ms

And I follow "new-systems-group" 308ms

And I follow "Target Systems" 568ms

And I check the "sle_minion" client 65ms

And I click on "Add Systems" 1s 395ms

Then I should see a "1 systems were added to new-systems-group server group." text 96ms

When I click on "Add Selected to SSM" 605ms

Scenario:
The SLE minion is part of the new group
1s 340ms 3

Given I am on the Systems overview page of this "sle_minion" 1s 198ms

When I follow "Groups" in the content area 71ms

Then I should see a "new-systems-group" text 70ms

Scenario:
Apply a patch to systems in the system group
42s 788ms 14

When I follow the left menu "Systems > System Groups" 83ms

And I follow "new-systems-group" 301ms

And I follow first "Patches" 392ms

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 257ms

Then I should see a "virgo-dummy-3456" link 8ms

When I follow "virgo-dummy-3456" 461ms

And I follow first "Affected Systems" 298ms

And I check the "sle_minion" client 56ms

And I click on "Apply Patches" 478ms

And I click on "Confirm" 646ms

Then I should see a "Patch virgo-dummy-3456 has been scheduled for 1 system" text 253ms

And I am on the Systems overview page of this "sle_minion" 941ms

And I wait until event "Patch Update: virgo-dummy-3456 - Test update for virgo-dummy scheduled by admin" is completed 38s 489ms

Scenario:
Apply a patch to systems in the SSM
43s 582ms 14

When I follow the left menu "Systems > System Set Manager > Overview" 517ms

And I follow first "Patches" 461ms

When I enter "andromeda-dummy" as the filtered synopsis 182ms

And I click on the filter button 469ms

When I wait until I see "andromeda-dummy-6789" text, refreshing the page 73ms

Then I should see a "andromeda-dummy-6789" link 12ms

When I follow "andromeda-dummy-6789" 770ms

And I follow first "Affected Systems" 399ms

And I check the "sle_minion" client 61ms

And I click on "Apply Patches" 669ms

And I click on "Confirm" 60ms

Then I should see a "Patch andromeda-dummy-6789 has been scheduled for 1 system" text 471ms

And I am on the Systems overview page of this "sle_minion" 1s 26ms

And I wait until event "Patch Update: andromeda-dummy-6789 - Test update for andromeda-dummy scheduled by admin" is completed 38s 407ms

@skip_if_github_validation
Scenario:
Pre-requisite: re-select sle_minion in SSM for package operations
248ms 4

When I follow the left menu "Systems > System Groups" 82ms

And I click on "Use in SSM" in row "new-systems-group" 75ms

Then I should see a "Selected Systems List" text 75ms

And I should see "sle_minion" as link 14ms

@skip_if_github_validation
Scenario:
Delete a package from systems in the SSM
12s 868ms 10

When I follow the left menu "Systems > System Set Manager > Overview" 76ms

And I follow "Packages" 438ms

And I follow "Remove" 549ms

And I wait until I see "Package Removal" text, refreshing the page 230ms

And I enter "virgo-dummy" as the filtered package name 114ms

And I click on the filter button until page does contain "virgo-dummy-2.0-1.1" text 10s 565ms

And I check "virgo-dummy-2.0-1.1" in the list 61ms

And I click on "Remove Packages" 351ms

And I click on "Confirm" 419ms

Then I should see a "Package removals are being scheduled, it may take several minutes for this to complete." text 61ms

@skip_if_github_validation
Scenario:
Pre-requisite: re-select sle_minion in SSM for package install
235ms 4

When I follow the left menu "Systems > System Groups" 74ms

And I click on "Use in SSM" in row "new-systems-group" 71ms

Then I should see a "Selected Systems List" text 75ms

And I should see "sle_minion" as link 14ms

@skip_if_github_validation
Scenario:
Install a package to systems in the SSM
3s 122ms 13

When I follow the left menu "Systems > System Set Manager > Overview" 77ms

And I follow "Packages" 366ms

And I follow "Install" 422ms

And I wait until I see "Fake-RPM-SUSE-Channel" text, refreshing the page 70ms

Then I should see a "Fake-RPM-SUSE-Channel" text 64ms

When I follow "Fake-RPM-SUSE-Channel" 319ms

Then I should see a "virgo-dummy-2.0-1.1" text 94ms

And I enter "virgo-dummy" as the filtered package name 52ms

And I click on the filter button until page does contain "virgo-dummy-2.0-1.1" text 89ms

When I check "virgo-dummy-2.0-1.1" in the list 57ms

And I click on "Install Packages" 389ms

And I click on "Confirm" 1s 56ms

Then I should see a "Package installations are being scheduled, it may take several minutes for this to complete." text 61ms

@rhlike_minion
Scenario:
Add the Red Hat-like minion to the group in a different way
2s 290ms 8

When I follow the left menu "Systems > System Groups" 61ms

Then I should see a "System Groups" text 68ms

When I follow "new-systems-group" 389ms

And I follow "Target Systems" 467ms

Then I should see a "The following are systems that may be added to this group." text 101ms

When I check the "rhlike_minion" client 58ms

And I click on "Add Systems" 1s 54ms

Then I should see a "1 systems were added to new-systems-group server group" text 91ms

Scenario:
Add the new group to SSM
230ms 5

When I follow the left menu "Systems > System Groups" 59ms

And I click on "Use in SSM" in row "new-systems-group" 57ms

Then I should see a "Selected Systems List" text 80ms

And I should see "rhlike_minion" as link 19ms

And I should see "sle_minion" as link 12ms

@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 232ms 1

When I synchronize all Salt dynamic modules on "sle_minion" 5s 232ms

Scenario:
New formula page is rendered for the system group
11s 169ms 6

When I follow the left menu "Systems > System Groups" 59ms

And I follow "new-systems-group" 312ms

And I follow "Formulas" 408ms

Then I should see a "Choose formulas:" text 63ms

And I should see a "General System Configuration" text 288ms

And the "locale" formula should be unchecked 10s 37ms

@rhlike_minion
Scenario:
Apply the highstate to the group
59s 22ms 10

When I follow the left menu "Systems > System Groups" 61ms

Then I should see a "System Groups" text 66ms

When I follow "new-systems-group" 297ms

And I follow "States" 438ms

And I click on "Apply Highstate" 60ms

Then I should see a "Applying the highstate has been scheduled." text 322ms

When I follow "scheduled" 280ms

Then I should see a "Apply states (highstate)" text 57ms

And I should see a "Action Details" text 55ms

And I wait until I see "2 systems successfully completed this action." text, refreshing the page 57s 380ms

Scenario:
Remove SLE minion from new group
2s 687ms 5

Given I am on the Systems overview page of this "sle_minion" 962ms

When I follow "Groups" 485ms

And I check "new-systems-group" in the list 64ms

And I click on "Leave Groups" 1s 110ms

Then I should see a "1 system groups removed." text 64ms

@skip_if_containerized_server
Scenario:
Cleanup: uninstall formula from the server
< 1ms 1

When I manually uninstall the "locale" formula from the server 0s

Scenario:
Cleanup: remove the new group
1s 438ms 7

When I follow the left menu "Systems > System Groups" 75ms

When I follow "new-systems-group" in the content area 70ms

And I follow "Delete Group" in the content area 68ms

And I click on "Confirm Deletion" 1s 42ms

Then I should see a "System group" text 59ms

And I should see a "new-systems-group" text 62ms

And I should see a "deleted" text 58ms

Scenario:
Cleanup: regenerate search index for later tests
11s 847ms 1

Search by hostname: uyuni-master-suse-minion
[{"last_boot"=>"2026-04-22T12:06:01Z", "name"=>"uyuni-master-suse-minion.sumaci.aws", "id"=>1000010023, "last_checkin"=>"2026-04-22T14:40:22Z"}]

When I clean the search index on the server 11s 847ms

Scenario:
Cleanup: remove dummy packages
5s 544ms 4

When I disable repository "test_repo_rpm_pool" on this "sle_minion" without error control 838ms

And I refresh the metadata for "sle_minion" 952ms

And I remove package "andromeda-dummy" from this "sle_minion" without error control 1s 821ms

And I remove package "virgo-dummy" from this "sle_minion" without error control 1s 932ms

@scope_configuration_channels @new_issue
Feature:Management of configuration of all types of clients in a single channel 6m 46s 216ms 27 1

* Related GitHub Card: https://github.com/SUSE/spacewalk/issues/30398

Scenario:
Log in as org admin user
495ms 1

Given I am authorized 495ms

Scenario:
Create a configuration channel for mixed client types
819ms 7

When I follow the left menu "Configuration > Channels" 121ms

And I follow "Create Config Channel" 342ms

And I enter "Mixed Channel" as "cofName" 66ms

And I enter "mixedchannel" as "cofLabel" 59ms

And I enter "This is a configuration channel for different system types" as "cofDescription" 97ms

And I click on "Create Config Channel" 63ms

Then I should see a "Mixed Channel" text 67ms

Scenario:
Add a configuration file to the mixed configuration channel
10s 587ms 9

When I follow the left menu "Configuration > Channels" 63ms

And I follow "Mixed Channel" 440ms

And I follow "Create Configuration File or Directory" 325ms

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" 732ms

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 6s 52ms

And file "/srv/susemanager/salt/manager_org_1/mixedchannel/etc/s-mgr/config" should exist on server 2s 801ms

@sle_minion
Scenario:
Subscribe a Salt minion to the configuration channel
3s 511ms 8

When I am on the Systems overview page of this "sle_minion" 1s 233ms

And I follow "Configuration" in the content area 68ms

And I follow "Manage Configuration Channels" in the content area 69ms

And I follow first "Subscribe to Channels" in the content area 64ms

And I check "Mixed Channel" in the list 62ms

And I click on "Continue" 58ms

And I click on "Update Channel Rankings" 1s 875ms

Then I should see a "Channel Subscriptions successfully changed for" text 79ms

@rhlike_minion
Scenario:
Subscribe a Red Hat-like minion to the configuration channel
4s 338ms 8

When I am on the Systems overview page of this "rhlike_minion" 1s 811ms

And I follow "Configuration" in the content area 59ms

And I follow "Manage Configuration Channels" in the content area 61ms

And I follow first "Subscribe to Channels" in the content area 57ms

And I check "Mixed Channel" in the list 50ms

And I click on "Continue" 1s 7ms

And I click on "Update Channel Rankings" 1s 213ms

Then I should see a "Channel Subscriptions successfully changed for" text 76ms

@deblike_minion
Scenario:
Subscribe a Debian-like minion to the configuration channel
3s 227ms 8

When I am on the Systems overview page of this "deblike_minion" 1s 319ms

And I follow "Configuration" in the content area 65ms

And I follow "Manage Configuration Channels" in the content area 59ms

And I follow first "Subscribe to Channels" in the content area 58ms

And I check "Mixed Channel" in the list 51ms

And I click on "Continue" 51ms

And I click on "Update Channel Rankings" 1s 546ms

Then I should see a "Channel Subscriptions successfully changed for" text 75ms

@ssh_minion
Scenario:
Subscribe a SSH minion to the configuration channel
3s 29ms 8

When I am on the Systems overview page of this "ssh_minion" 1s 209ms

And I follow "Configuration" in the content area 62ms

And I follow "Manage Configuration Channels" in the content area 61ms

And I follow first "Subscribe to Channels" in the content area 56ms

And I check "Mixed Channel" in the list 50ms

And I click on "Continue" 691ms

And I click on "Update Channel Rankings" 821ms

Then I should see a "Channel Subscriptions successfully changed for" text 77ms

Scenario:
Deploy the file to all systems
2s 186ms 7

When I follow the left menu "Configuration > Channels" 120ms

And I follow "Mixed Channel" 489ms

And I follow "Deploy all configuration files to all subscribed systems" 528ms

Then I should see a "/etc/s-mgr/config" link 11ms

When I click on "Deploy Files to Selected Systems" 899ms

Then I should see a "revision-deploys are being scheduled," text 68ms

And I should see a "0 revision-deploys overridden." text 68ms

@sle_minion
Scenario:
Check that file has been created on SLE minion
3s 169ms 2

When I wait until file "/etc/s-mgr/config" exists on "sle_minion" 2s 295ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "sle_minion" 873ms

@rhlike_minion
Scenario:
Check that file has been created on Red Hat-like minion
692ms 2

When I wait until file "/etc/s-mgr/config" exists on "rhlike_minion" 306ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "rhlike_minion" 385ms

@deblike_minion
Scenario:
Check that file has been created on Debian-like minion
1s 555ms 2

When I wait until file "/etc/s-mgr/config" exists on "deblike_minion" 1s 108ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "deblike_minion" 447ms

@ssh_minion
Scenario:
Check that file has been created on SSH minion
7s 370ms 2

When I wait until file "/etc/s-mgr/config" exists on "ssh_minion" 6s 522ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "ssh_minion" 847ms

@sle_minion
Scenario:
Apply highstate to override changed content on SLE minion
18s 425ms 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" 438ms

And I apply highstate on "sle_minion" 16s 744ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "sle_minion" 1s 242ms

@rhlike_minion
Scenario:
Apply highstate to override changed content on Red Hat-like minion
4m 28s 741ms 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" 293ms

And I apply highstate on "rhlike_minion" 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/salt_steps.rb:650:in `/^I apply highstate on "([^"]*)"$/'
features/secondary/allcli_config_channel.feature:115:in `I apply highstate on "rhlike_minion"'

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "rhlike_minion" 0s

18s 446ms Show Info + 
16:42:05:000 - 16:46:15: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
11s 355ms 3

Salt command: salt uyuni-master-deblike-minion state.highstate

When I store "COLOR=blue" into file "/etc/s-mgr/config" on "deblike_minion" 1s 220ms

And I apply highstate on "deblike_minion" 9s 683ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "deblike_minion" 451ms

@ssh_minion
Scenario:
Apply highstate to override changed content on SSH minion
35s 340ms 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" 730ms

And I apply highstate on "ssh_minion" 33s 789ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "ssh_minion" 820ms

@rhlike_minion
Scenario:
Unsubscribe Red Hat-like minion and delete configuration files
1s 130ms 7

When I follow the left menu "Configuration > Channels" 78ms

And I follow "Mixed Channel" 451ms

And I follow "Systems" in the content area 68ms

And I check the "rhlike_minion" client 74ms

And I click on "Unsubscribe systems" 55ms

Then I should see a "Successfully unsubscribed 1 system(s)." text 85ms

And I destroy "/etc/s-mgr" directory on "rhlike_minion" 316ms

@deblike_minion
Scenario:
Unsubscribe Debian-like minion and delete configuration files
3s 120ms 7

When I follow the left menu "Configuration > Channels" 60ms

And I follow "Mixed Channel" 1s 704ms

And I follow "Systems" in the content area 59ms

And I check the "deblike_minion" client 61ms

And I click on "Unsubscribe systems" 670ms

Then I should see a "Successfully unsubscribed 1 system(s)." text 73ms

And I destroy "/etc/s-mgr" directory on "deblike_minion" 489ms

@ssh_minion
Scenario:
Unsubscribe SSH minion and delete configuration files
1s 738ms 7

When I follow the left menu "Configuration > Channels" 61ms

And I follow "Mixed Channel" 501ms

And I follow "Systems" in the content area 61ms

And I check the "ssh_minion" client 54ms

And I click on "Unsubscribe systems" 560ms

Then I should see a "Successfully unsubscribed 1 system(s)." text 71ms

And I destroy "/etc/s-mgr" directory on "ssh_minion" 428ms

@sle_minion
Scenario:
Change file on Salt minion and compare
6s 437ms 13

When I am on the Systems overview page of this "sle_minion" 927ms

And I store "COLOR=red" into file "/etc/s-mgr/config" on "sle_minion" 812ms

And I follow "Configuration" in the content area 71ms

And I follow "Compare Files" in the content area 66ms

And I check "/etc/s-mgr/config" in the list 56ms

And I click on "Compare Files" 626ms

And I click on "Schedule Compare" 864ms

Then I should see a "1 files scheduled for comparison." text 73ms

When I wait until event "Show differences between profiled config files and deployed config files scheduled" is completed 2s 333ms

Then I should see a "Differences exist" link 12ms

When I follow "Differences exist" 459ms

Then I should see a "+COLOR=white" text 69ms

And I should see a "-COLOR=red" text 62ms

@sle_minion
Scenario:
Check configuration channel and files via API for Salt minion
1s 310ms 3

Then channel "mixedchannel" should exist 420ms

And channel "mixedchannel" should contain file "/etc/s-mgr/config" 491ms

And "sle_minion" should be subscribed to channel "mixedchannel" 398ms

@sle_minion
Scenario:
Extend configuration channel and deploy files via API for Salt minion
5s 332ms 6

When I store "COLOR=green" into file "/etc/s-mgr/config" on "sle_minion" 449ms

And I add file "/etc/s-mgr/other" containing "NAME=Dante" to channel "mixedchannel" 538ms

And I deploy all systems registered to channel "mixedchannel" 580ms

And I wait until file "/etc/s-mgr/other" exists on "sle_minion" 1s 961ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "sle_minion" 872ms

And file "/etc/s-mgr/other" should contain "NAME=Dante" on "sle_minion" 929ms

@sle_minion
Scenario:
Unsubscribe systems via API for Salt minion
1s 61ms 2

When I unsubscribe "sle_minion" from configuration channel "mixedchannel" 727ms

Then "sle_minion" should not be subscribed to channel "mixedchannel" 334ms

@sle_minion
Scenario:
Re-add SLE Minion via SSM
3s 411ms 10

When I follow the left menu "Systems > System List > All" 132ms

And I click on the clear SSM button 64ms

And I check the "sle_minion" client 428ms

And I follow the left menu "Systems > System Set Manager > Overview" 481ms

And I follow "config channel subscriptions" in the content area 65ms

And I check "Mixed Channel" in the list 57ms

And I click on "Continue" 596ms

And I click on "Apply Subscriptions" 645ms

And I click on "Confirm" 874ms

Then I should see a "Configuration channel subscriptions changed for 1 system successfully." text 63ms

@sle_minion
Scenario:
Cleanup: remove remaining Salt minion from configuration channel
1s 464ms 6

When I follow the left menu "Configuration > Channels" 117ms

And I follow "Mixed Channel" 510ms

And I follow "Systems" in the content area 63ms

And I check the "sle_minion" client 51ms

And I click on "Unsubscribe systems" 663ms

Then I should see a "Successfully unsubscribed 1 system(s)." text 57ms

Scenario:
Cleanup: remove the mixed configuration channel
5s 547ms 5

When I follow the left menu "Configuration > Channels" 62ms

And I follow "Mixed Channel" 369ms

And I follow "Delete Channel" 301ms

And I click on "Delete Config Channel" 59ms

Then file "/srv/susemanager/salt/manager_org_1/mixedchannel/init.sls" should not exist on server 4s 754ms

@sle_minion
Scenario:
Cleanup: delete configuration files on remaining Salt minion
762ms 1

When I destroy "/etc/s-mgr" directory on "sle_minion" 762ms

Scenario:
Cleanup: remove remaining systems from SSM after tests of configuration channel on all clients
51ms 1

When I click on the clear SSM button 51ms

@scope_changing_software_channels @scc_credentials
Feature:Channel subscription via SSM 5m 21s 96ms 14 5

Scenario:
Log in as org admin user
430ms 1

Given I am authorized 430ms

@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 421ms 22

When I follow the left menu "Systems > System List > All" 175ms

And I click on the clear SSM button 48ms

And I check the "sle_minion" client 450ms

And I should see "1" systems selected for SSM 172ms

And I follow the left menu "Systems > System Set Manager > Overview" 502ms

And I follow "channel memberships" in the content area 66ms

Then I should see a "Base Channel" text 109ms

And I should see a "Next" text 64ms

When I select "Fake-Base-Channel-SUSE-like" from drop-down in table line with "openSUSE Tumbleweed (x86_64)" 231ms

And I click on "Next" 60ms

Then I should see a "Child Channels" text 400ms

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" 59ms

Then I should see a "Channel Changes Overview" text 65ms

And I should see a "1 system(s) to subscribe" text 80ms

When I schedule action to 3 minutes from now 243ms

And I click on "Confirm" 52ms

And I remember when I scheduled an action < 1ms

Then I wait until I see "Channel Changes Actions" text 406ms

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 992ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 5ms

When I follow "Software" in the content area 69ms

And I follow "Software Channels" in the content area 69ms

And I wait until I do not see "Loading..." text 78ms

Then radio button "openSUSE Tumbleweed (x86_64)" should be checked 317ms

And I wait until I do not see "Loading..." text 434ms

And I should see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" as unchecked 18ms

@sle_minion @susemanager
Scenario:
Check via API old channels are still the same on SLES minion before channel change completes
< 1ms 3

When I refresh the metadata for "sle_minion" 0s

Then channel "SLE-Product-SLES15-SP7-Pool for x86_64" should be enabled on "sle_minion" 0s

And channel "SLE15-SP7-Installer-Updates for x86_64" should be disabled on "sle_minion" 0s

@sle_minion @uyuni
Scenario:
Check via API old channels are still the same on openSUSE minion before channel change completes
2s 804ms 3

When I refresh the metadata for "sle_minion" 1s 371ms

Then channel "openSUSE Tumbleweed (x86_64)" should be enabled on "sle_minion" 687ms

And channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" should be disabled on "sle_minion" 745ms

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 706ms 3

Given I am on the Systems overview page of this "sle_minion" 955ms

When I wait until event "Subscribe channels scheduled" is completed 1m 13s 687ms

Then I should see a "The client completed this action on" text 62ms

@sle_minion
Scenario:
Check the SLES minion is subscribed to the new channels
1s 881ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 71ms

When I follow "Software" in the content area 76ms

And I follow "Software Channels" in the content area 68ms

And I wait until I do not see "Loading..." text 69ms

Then radio button "Fake-Base-Channel-SUSE-like" should be checked 142ms

And I wait until I do not see "Loading..." text 433ms

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
4s 98ms 4

When I refresh the metadata for "sle_minion" 1s 615ms

Then "2" channels should be enabled on "sle_minion" 723ms

And channel "Fake-Base-Channel-SUSE-like" should be enabled on "sle_minion" 825ms

And channel "Fake-Child-Channel-SUSE-like" should be enabled on "sle_minion" 933ms

@rhlike_minion
Scenario:
System default channel can't be determined on the Red Hat-like minion
2s 886ms 20

When I follow the left menu "Systems > System List > All" 133ms

And I click on the clear SSM button 64ms

And I check the "rhlike_minion" client 420ms

Then I should see "1" systems selected for SSM 122ms

When I follow the left menu "Systems > System Set Manager > Overview" 474ms

And I follow "channel memberships" in the content area 67ms

And I select "System Default Base Channel" from drop-down in table line with "Fake-Base-Channel-RH-like" 336ms

And I click on "Next" 61ms

Then I should see a "Child Channels" text 301ms

And I should see a "Couldn't determine new base channel" text 66ms

And I should see a "1 system(s) incompatible" text 70ms

When I click on "Next" 59ms

Then I should see a "Channel Changes Overview" text 65ms

And I should see a "Couldn't determine new base channel" text 76ms

And I should see a "1 system(s) incompatible" text 72ms

When I click on "Confirm" 59ms

Then I should see a "Channel Changes Actions" text 295ms

And I should see a "Items 1 - 1 of 1" text 66ms

And a table line should contain system "rhlike_minion", "Could not determine system default channel" 21ms

And I click on the clear SSM button 50ms

@rhlike_minion
Scenario:
Cleanup: make sure the Red Hat-like minion is still unchanged
1s 653ms 4

Given I am on the Systems overview page of this "rhlike_minion" 970ms

When I follow "Software" in the content area 61ms

And I follow "Software Channels" in the content area 59ms

Then radio button "Fake-Base-Channel-RH-like" should be checked 562ms

@deblike_minion
Scenario:
System default channel can't be determined on the Debian-like minion
2s 535ms 20

When I follow the left menu "Systems > System List > All" 118ms

And I click on the clear SSM button 51ms

And I check the "deblike_minion" client 424ms

Then I should see "1" systems selected for SSM 96ms

When I follow the left menu "Systems > System Set Manager > Overview" 442ms

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" 187ms

And I click on "Next" 54ms

Then I should see a "Child Channels" text 214ms

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" 57ms

Then I should see a "Channel Changes Overview" text 67ms

And I should see a "Couldn't determine new base channel" text 83ms

And I should see a "1 system(s) incompatible" text 76ms

When I click on "Confirm" 51ms

Then I should see a "Channel Changes Actions" text 286ms

And I should see a "Items 1 - 1 of 1" text 68ms

And a table line should contain system "deblike_minion", "Could not determine system default channel" 18ms

And I click on the clear SSM button 48ms

@deblike_minion
Scenario:
Cleanup: make sure the Debian-like minion is still unchanged
1s 308ms 4

Given I am on the Systems overview page of this "deblike_minion" 923ms

When I follow "Software" in the content area 62ms

And I follow "Software Channels" in the content area 67ms

Then radio button "Fake-Base-Channel-Debian-like" should be checked 254ms

@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 314ms 15

Given I am on the Systems overview page of this "sle_minion" 1s 10ms

When I follow "Software" in the content area 61ms

And I follow "Software Channels" in the content area 60ms

And I wait until I do not see "Loading..." text 68ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 10s 79ms

And I wait until I do not see "Loading..." text 432ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 77ms

And I check "Fake-RPM-SUSE-Channel" 76ms

And I click on "Next" 58ms

Then I should see a "Confirm Software Channel Change" text 66ms

When I click on "Confirm" 70ms

Then I should see a "Changing the channels has been scheduled." text 432ms

When I follow "scheduled" in the content area 78ms

And I wait until I see "1 system successfully completed this action." text, refreshing the page 29s 862ms

Then channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" should be disabled on "sle_minion" 879ms

Scenario:
Cleanup: remove remaining systems from SSM after channel subscription tests
62ms 1

When I click on the clear SSM button 62ms

@scope_changing_software_channels @scc_credentials
Feature:Channel subscription with recommended or required dependencies 45s 509ms 5 2

Scenario:
Log in as org admin user
452ms 1

Given I am authorized 452ms

Scenario:
Pre-requisite: remove remaining systems from SSM after software channel tests
51ms 1

When I click on the clear SSM button 51ms

@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 54ms 10

Given I am on the Systems overview page of this "sle_minion" 1s 888ms

When I follow "Software" in the content area 71ms

And I follow "Software Channels" in the content area 66ms

And I wait for child channels to appear 222ms

And I check radio button "(none, disable service)" 10s 89ms

And I wait for child channels to appear 225ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 10s 74ms

Then I should see the child channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" "unselected" and "disabled" 10s 123ms

When I select the child channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" 10s 174ms

Then I should see the child channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" "selected" 117ms

@susemanager
Scenario:
Play with recommended and required child channels selection in SSM
< 1ms 16

When I follow the left menu "Systems > System List > All" 0s

And I check the "sle_minion" client 0s

Then I should see "1" systems selected for SSM 0s

When I follow the left menu "Systems > System Set Manager > Overview" 0s

And I follow "channel memberships" in the content area 0s

Then I should see a "Base Channel" text 0s

And I should see a "Next" text 0s

And I should see a table line with "SLE-Product-SLES15-SP7-Pool for x86_64", "1" 0s

When I select "System Default Base Channel" from drop-down in table line with "SLE-Product-SLES15-SP7-Pool for x86_64" 0s

And I click on "Next" 0s

Then I should see the toggler "disabled" 0s

And I should see a "SLE-Module-Basesystem15-SP7-Pool for x86_64" text 0s

And I should see "No change" "selected" for the "SLE-Module-Basesystem15-SP7-Pool for x86_64" channel 0s

When I click on the "disabled" toggler 0s

Then I should see "Subscribe" "selected" for the "SLE-Module-Basesystem15-SP7-Pool for x86_64" channel 0s

And I should see "No change" "unselected" for the "SLE-Module-Basesystem15-SP7-Pool for x86_64" channel 0s

@uyuni
Scenario:
Play with recommended and required child channels selection in SSM
1s 896ms 10

When I follow the left menu "Systems > System List > All" 138ms

And I check the "sle_minion" client 486ms

Then I should see "1" systems selected for SSM 120ms

When I follow the left menu "Systems > System Set Manager > Overview" 485ms

And I follow "channel memberships" in the content area 77ms

Then I should see a "Base Channel" text 69ms

And I should see a "Next" text 66ms

When I select "No Change" from drop-down in table line with "openSUSE Tumbleweed (x86_64)" 40ms

And I click on "Next" 63ms

Then I should see the toggler "disabled" 347ms

Scenario:
Cleanup: remove remaining systems from SSM after software channel tests
54ms 1

When I click on the clear SSM button 54ms

@flaky @scope_res @scope_salt @rhlike_minion
Feature:Install a patch on the Red Hat-like minion via Salt through the UI 3m 12s 909ms 9 1

Scenario:
Pre-requisite: enable test_repo_rpm_pool repository on the Red Hat-like minion
326ms 1

When I enable repository "test_repo_rpm_pool" on this "rhlike_minion" 326ms

Scenario:
Pre-requisite: install virgo-dummy-1.0 package on Red Hat-like minion
1s 797ms 1

When I install package "virgo-dummy-1.0" on this "rhlike_minion" 1s 797ms

Scenario:
Pre-requisite: remove andromeda-dummy package from Red Hat-like minion
1s 652ms 1

When I remove package "andromeda-dummy" from this "rhlike_minion" 1s 652ms

Scenario:
Pre-requisite: refresh package list and check newly installed packages on Red Hat-like minion
56s 996ms 2 2

When I refresh packages list via spacecmd on "rhlike_minion" 7s 929ms 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:1254: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

49s 66ms 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:234:in `block in relog_and_visit_previous_url'
./features/support/env.rb:232:in `relog_and_visit_previous_url'
./features/support/env.rb:212:in `handle_screenshot_and_relog'
./features/support/env.rb:173:in `After'
Show Info + 
16:54:51:000 - 16:54:59:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channel/ssm/ChannelSubscriptions.do
Screenshot +

Scenario:
Log in as org admin user
10s 762ms 1

Given I am authorized for the "Admin" section 10s 762ms

Scenario:
Pre-requisite: re-subscribe the Red Hat-like minion to a base channel
25s 528ms 11

Warning: Radio button 'Fake-Base-Channel-RH-like' is already checked

Given I am on the Systems overview page of this "rhlike_minion" 2s 271ms

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 69ms

And I check radio button "Fake-Base-Channel-RH-like" 173ms

And I wait until I do not see "Loading..." text 420ms

And I click on "Next" 62ms

Then I should see a "Confirm Software Channel Change" text 62ms

When I click on "Confirm" 76ms

Then I should see a "Changing the channels has been scheduled." text 303ms

And I wait until event "Subscribe channels scheduled" is completed 21s 941ms

Scenario:
Schedule errata refresh to reflect channel assignment on Red Hat-like minion
36s 985ms 10

When I follow "Software" in the content area 61ms

And I follow "List / Remove" in the content area 69ms

And I enter "virgo-dummy" as the filtered package name 168ms

And I click on the filter button until page does contain "virgo-dummy" text 11s 120ms

When I follow the left menu "Admin > Task Schedules" 127ms

And I follow "errata-cache-default" 419ms

And I follow "errata-cache-bunch" 1s 293ms

And I click on "Single Run Schedule" 1s 271ms

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 22s 179ms

Scenario:
Install a patch on the Red Hat-like minion
12s 177ms 8

Given I am on the Systems overview page of this "rhlike_minion" 948ms

When I follow "Software" in the content area 81ms

And I follow "Patches" in the content area 66ms

When I check "virgo-dummy-3456" in the list 65ms

And I click on "Apply Patches" 624ms

And I click on "Confirm" 671ms

Then I should see a "1 patch update has been scheduled for" text 88ms

And I wait for "virgo-dummy-2.0-1.1" to be installed on "rhlike_minion" 9s 630ms

Scenario:
Install a package on the Red Hat-like minion
20s 899ms 7

When I follow "Software" in the content area 65ms

And I follow "Install" 571ms

And I check "andromeda-dummy" in the list 65ms

And I click on "Install Packages" 630ms

And I click on "Confirm" 714ms

Then I should see a "1 package install has been scheduled for" text 67ms

And I wait until event "Package Install/Upgrade scheduled" is completed 18s 784ms

Scenario:
Cleanup: remove virgo-dummy and andromeda-dummy packages from Red Hat-like minion
25s 781ms 13

When I follow "Software" in the content area 78ms

And I follow "List / Remove" 612ms

And I enter "andromeda" as the filtered package name 123ms

And I click on the filter button 850ms

And I check "andromeda-dummy" in the list 61ms

And I enter "virgo-dummy" as the filtered package name 43ms

And I click on the filter button 130ms

And I check "virgo-dummy" in the list 71ms

And I click on "Remove Packages" 785ms

And I click on "Confirm" 687ms

Then I should see a "2 package removals have been scheduled" text 68ms

And I wait until event "Package Removal scheduled" is completed 21s 920ms

And I disable repository "test_repo_rpm_pool" on this "rhlike_minion" 346ms

@scope_monitoring @scope_res @rhlike_minion
Feature:Monitor MLM environment with Prometheus on a Red Hat-like Salt minion 1m 10s 982ms 10

In order to monitor Uyuni server
As an authorized user
I want to enable Prometheus exporters

Scenario:
Log in as org admin user
489ms 1

Given I am authorized 489ms

Scenario:
Apply Prometheus exporter formulas on the Red Hat-like minion
2s 976ms 7

Given I am on the Systems overview page of this "rhlike_minion" 1s 761ms

When I follow "Formulas" in the content area 75ms

Then I should see a "Choose formulas:" text 68ms

And I should see a "Monitoring" text 187ms

When I check the "prometheus-exporters" formula 75ms

And I click on "Save" 65ms

And I wait until I see "Formula saved" text 742ms

Scenario:
Configure Prometheus exporter formula on the Red Hat-like minion
2s 346ms 9

When I follow "Formulas" in the content area 60ms

And I follow "Prometheus Exporters" in the content area 266ms

And I click on "Expand All Sections" 287ms

Then I should see a "Enable and configure Prometheus exporters for managed systems." text 115ms

When I check "node" exporter 48ms

And I check "apache" exporter 86ms

And I check "postgres" exporter 87ms

And I click on "Save" 67ms

Then I should see a "Formula saved" text 1s 325ms

Scenario:
Enable tools_update_repo tools_pool_repo so the exporters packages are available
633ms 1

When I enable the repositories "tools_update_repo tools_pool_repo" on this "rhlike_minion" without error control 633ms

@skip_if_github_validation
Scenario:
Apply highstate for Prometheus exporters on the Red Hat-like minion
39s 209ms 4

When I follow "States" in the content area 73ms

And I click on "Apply Highstate" 59ms

Then I should see a "Applying the highstate has been scheduled." text 452ms

And I wait until event "Apply highstate scheduled" is completed 38s 624ms

@skip_if_github_validation
Scenario:
Wait for service
725ms 3

When I wait until "node" exporter service is active on "rhlike_minion" 327ms

And I wait until "apache" exporter service is active on "rhlike_minion" 200ms

And I wait until "postgres" exporter service is active on "rhlike_minion" 196ms

Scenario:
Visit monitoring endpoints on the Red Hat-like minion
615ms 3

When I visit "Prometheus node exporter" endpoint of this "rhlike_minion" 211ms

And I visit "Prometheus apache exporter" endpoint of this "rhlike_minion" 201ms

And I visit "Prometheus postgres exporter" endpoint of this "rhlike_minion" 202ms

Scenario:
Cleanup: undo Prometheus exporter formulas on the Red Hat-like minion
1s 399ms 4

When I follow "Formulas" in the content area 80ms

And I uncheck the "prometheus-exporters" formula 222ms

And I click on "Save" 62ms

Then I wait until I see "Formula saved" text 1s 34ms

@skip_if_github_validation
Scenario:
Cleanup: apply highstate after test monitoring on the Red Hat-like minion
22s 280ms 4

When I follow "States" in the content area 66ms

And I click on "Apply Highstate" 73ms

Then I should see a "Applying the highstate has been scheduled." text 453ms

And I wait until event "Apply highstate scheduled" is completed 21s 687ms

Scenario:
Cleanup: Disable tools_update_repo tools_pool_repo because they are no longer needed
305ms 1

When I disable the repositories "tools_update_repo tools_pool_repo" on this "rhlike_minion" without error control 305ms

@skip_if_github_validation @scope_salt
Feature:Install a package and a patch on the SUSE SSH client via Salt through the UI 4m 47s 747ms 11

Scenario:
Pre-requisite: enable test_repo_rpm_pool repository on SSH minion
852ms 1

When I enable repository "test_repo_rpm_pool" on this "ssh_minion" 852ms

Scenario:
Pre-requisite: install virgo-dummy-1.0 package on SSH minion
2s 549ms 2

When I refresh the metadata for "ssh_minion" 1s 6ms

And I install old package "virgo-dummy-1.0" on this "ssh_minion" without error control 1s 543ms

Scenario:
Pre-requisite: remove andromeda-dummy package from SSH minion
36s 792ms 4

When I remove package "andromeda-dummy" from this "ssh_minion" without error control 866ms

And I refresh the metadata for "ssh_minion" 891ms

And I refresh packages list via spacecmd on "ssh_minion" 7s 92ms

And I wait until refresh package list on "ssh_minion" is finished 27s 941ms

Scenario:
Pre-requisite: refresh package list and check old packages installed on SSH minion
47s 793ms 4

When I refresh packages list via spacecmd on "ssh_minion" 6s 134ms

And I wait until refresh package list on "ssh_minion" is finished 26s 301ms

Then spacecmd should show packages "virgo-dummy-1.0" installed on "ssh_minion" 6s 388ms

And I wait until package "andromeda-dummy-2.0-1.1" is removed from "ssh_minion" via spacecmd 8s 968ms

Scenario:
Log in as org admin user
437ms 1

Given I am authorized for the "Admin" section 437ms

Scenario:
Pre-requisite: ensure the errata cache is computed before patching Salt minion
18s 495ms 11

Given I am on the Systems overview page of this "ssh_minion" 1s 619ms

When I follow "Software" in the content area 81ms

And I follow "List / Remove" in the content area 65ms

And I enter "virgo-dummy" as the filtered package name 152ms

And I click on the filter button until page does contain "virgo-dummy" text 10s 918ms

When I follow the left menu "Admin > Task Schedules" 122ms

And I follow "errata-cache-default" 414ms

And I follow "errata-cache-bunch" 1s 300ms

And I click on "Single Run Schedule" 1s 259ms

Then I should see a "bunch was scheduled" text 281ms

When I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 2s 277ms

Scenario:
Install a patch on the SSH minion
45s 881ms 12

Given I am on the Systems overview page of this "ssh_minion" 923ms

When I follow "Software" in the content area 72ms

And I follow "Patches" in the content area 66ms

And I enter "virgo" as the filtered synopsis 47ms

And I click on the filter button 10s 141ms

And I check "virgo-dummy-3456" in the list 61ms

And I check "allowVendorChange" 77ms

And I click on "Apply Patches" 650ms

And I click on "Confirm" 682ms

Then I should see a "1 patch update has been scheduled for" text 73ms

When I wait for "virgo-dummy-2.0-1.1" to be installed on "ssh_minion" 31s 856ms

Then vendor change should be enabled for package actions on "ssh_minion" 1s 227ms

Scenario:
Install a package on the SSH minion
52s 73ms 12

Given I am on the Systems overview page of this "ssh_minion" 1s 90ms

When I follow "Software" in the content area 81ms

And I follow "Packages" 514ms

And I follow "Install" 716ms

And I enter "andromeda" as the filtered package name 90ms

And I click on the filter button 872ms

And I check "andromeda-dummy-2.0-1.1" in the list 57ms

And I click on "Install Packages" 681ms

And I click on "Confirm" 783ms

Then I should see a "1 package install has been scheduled" text 70ms

When I wait for "andromeda-dummy-2.0-1.1" to be installed on "ssh_minion" 46s 40ms

Then vendor change should be enabled for package actions on "ssh_minion" 1s 72ms

Scenario:
Cleanup: disable test_repo_rpm_pool on SSH minion
716ms 1

When I disable repository "test_repo_rpm_pool" on this "ssh_minion" 716ms

Scenario:
Cleanup: remove virgo-dummy package from SSH minion
46s 806ms 4

When I remove package "virgo-dummy" from this "ssh_minion" without error control 1s 385ms

And I refresh the metadata for "ssh_minion" 971ms

And I refresh packages list via spacecmd on "ssh_minion" 6s 658ms

And I wait until refresh package list on "ssh_minion" is finished 37s 791ms

Scenario:
Cleanup: remove andromeda-dummy package from SSH minion
35s 349ms 4

When I remove package "andromeda-dummy" from this "ssh_minion" without error control 1s 383ms

And I refresh the metadata for "ssh_minion" 977ms

And I refresh packages list via spacecmd on "ssh_minion" 6s 161ms

And I wait until refresh package list on "ssh_minion" is finished 26s 826ms

@scope_ansible @scope_salt_ssh @ssh_minion
Feature:Operate an Ansible control node in SSH minion 4m 37s 954ms 12 2

Scenario:
Log in as org admin user
627ms 1

Given I am authorized for the "Admin" section 627ms

Scenario:
Pre-requisite: Deploy test playbooks and inventory file
3s 973ms 1

When I deploy testing playbooks and inventory files to "ssh_minion" 3s 973ms

@susemanager
Scenario:
Pre-requisite: Subscribe SUSE minions to SLE-Module-Python3-15-SP7-Pool for x86_64
< 1ms 9

Given I am on the Systems overview page of this "ssh_minion" 0s

When I follow "Software" in the content area 0s

And I follow "Software Channels" in the content area 0s

And I check "SLE-Module-Python3-15-SP7-Pool for x86_64" by label 0s

And I click on "Next" 0s

And I click on "Confirm" 0s

And I wait until I see "Changing the channels has been scheduled." text 0s

And I follow "scheduled" 0s

And I wait until I see "1 system successfully completed this action" text, refreshing the page 0s

Scenario:
Enable "Ansible control node" system type
2s 883ms 5

Given I am on the Systems overview page of this "ssh_minion" 965ms

When I follow "Properties" in the content area 68ms

And I check "ansible_control_node" 87ms

And I click on "Update Properties" 1s 669ms

Then I wait until I see "Ansible Control Node type has been applied." text 92ms

Scenario:
Apply highstate and check that Ansible is installed
1m 30s 298ms 5

Given I am on the Systems overview page of this "ssh_minion" 1s 119ms

When I follow "States" in the content area 68ms

And I click on "Apply Highstate" 80ms

And I wait until event "Apply highstate scheduled" is completed 1m 28s 547ms

Then "ansible" should be installed on "ssh_minion" 481ms

Scenario:
The Ansible tab appears in the system overview page
1s 164ms 3

Given I am on the Systems overview page of this "ssh_minion" 1s 19ms

When I follow "Ansible" in the content area 82ms

Then I should see a "Ansible Control Node Configuration" text 62ms

Scenario:
Configure some inventory and playbooks path
1s 466ms 7

Given I am on the Systems overview page of this "ssh_minion" 973ms

When I follow "Ansible" in the content area 64ms

Then I should see a "Ansible Control Node Configuration" text 61ms

And I enter "/srv/playbooks/" as "new_playbook_path_input" 146ms

And I click on "new_playbook_path_save" 57ms

And I enter "/srv/playbooks/orion_dummy/hosts" as "new_inventory_path_input" 99ms

And I click on "new_inventory_path_save" 64ms

Scenario:
Display inventories
23s 618ms 6

Given I am on the Systems overview page of this "ssh_minion" 1s 51ms

When I follow "Ansible" in the content area 62ms

And I follow "Inventories" in the content area 66ms

And I wait until I see "/srv/playbooks/orion_dummy/hosts" text 369ms

And I click on the inventory accordion for "/srv/playbooks/orion_dummy/hosts" 53ms

Then I wait until I see "myself" text 22s 15ms

Scenario:
Discover playbooks and display them
11s 202ms 6

Given I am on the Systems overview page of this "ssh_minion" 966ms

When I follow "Ansible" in the content area 80ms

And I follow "Playbooks" in the content area 91ms

And I wait until I see "/srv/playbooks" text 251ms

And I click on "/srv/playbooks" 58ms

Then I wait until I see "/srv/playbooks/orion_dummy/playbook_orion_dummy.yml" text 9s 754ms

Scenario:
Run a playbook using custom inventory
58s 680ms 13

Given I am on the Systems overview page of this "ssh_minion" 988ms

When I follow "Ansible" in the content area 67ms

And I follow "Playbooks" in the content area 67ms

And I wait until I see "/srv/playbooks" text 250ms

And I click on "/srv/playbooks" 49ms

And I wait until I see "/srv/playbooks/orion_dummy/playbook_orion_dummy.yml" text 10s 320ms

And I click on "orion_dummy/playbook_orion_dummy.yml" 60ms

And I wait until I see "Playbook Content" text 6s 180ms

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 380ms

And I wait until event "Execute playbook 'playbook_orion_dummy.yml' scheduled" is completed 38s 369ms

And file "/tmp/file.txt" should exist on "ssh_minion" 752ms

Scenario:
Cleanup: Disable Ansible and remove test playbooks and inventory file
15s 351ms 7

Given I am on the Systems overview page of this "ssh_minion" 960ms

When I follow "Properties" in the content area 78ms

And I uncheck "ansible_control_node" 10s 96ms

And I click on "Update Properties" 1s 906ms

Then I should see a "System properties changed" text 94ms

And I remove package "orion-dummy" from this "ssh_minion" without error control 1s 799ms

And I remove "/tmp/file.txt" from "ssh_minion" 414ms

@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 372ms 4

Given I am on the Systems overview page of this "ssh_minion" 1s 70ms

When I follow "Properties" in the content area 77ms

And I uncheck "ansible_control_node" 10s 25ms

And I click on "Update Properties" 1s 199ms

Scenario:
Cleanup: Apply highstate to disable the minion as an "Ansible control node"
56s 315ms 4

Given I am on the Systems overview page of this "ssh_minion" 1s 96ms

When I follow "States" in the content area 75ms

And I click on "Apply Highstate" 83ms

And I wait until event "Apply highstate scheduled" is completed 55s 60ms

@scope_monitoring @scope_res @deblike_minion
Feature:Monitor MLM environment with Prometheus on a Debian-like Salt minion 1m 31s 542ms 10

In order to monitor Uyuni server
As an authorized user
I want to enable Prometheus exporters

Scenario:
Log in as org admin user
443ms 1

Given I am authorized 443ms

Scenario:
Apply Prometheus exporter formulas on the Debian-like minion
2s 856ms 7

Given I am on the Systems overview page of this "deblike_minion" 1s 725ms

When I follow "Formulas" in the content area 97ms

Then I should see a "Choose formulas:" text 62ms

And I should see a "Monitoring" text 186ms

When I check the "prometheus-exporters" formula 77ms

And I click on "Save" 66ms

And I wait until I see "Formula saved" text 640ms

Scenario:
Configure Prometheus exporter formula on the Debian-like minion
2s 790ms 9

When I follow "Formulas" in the content area 64ms

And I follow "Prometheus Exporters" in the content area 242ms

And I click on "Expand All Sections" 469ms

Then I should see a "Enable and configure Prometheus exporters for managed systems." text 113ms

When I check "node" exporter 53ms

And I check "apache" exporter 88ms

And I check "postgres" exporter 86ms

And I click on "Save" 69ms

Then I should see a "Formula saved" text 1s 600ms

Scenario:
Enable tools_update_repo tools_pool_repo so the exporters packages are available
1s 422ms 1

When I enable the repositories "tools_update_repo tools_pool_repo" on this "deblike_minion" without error control 1s 422ms

@skip_if_github_validation
Scenario:
Apply highstate for Prometheus exporters on the Debian-like minion
55s 782ms 4

When I follow "States" in the content area 79ms

And I click on "Apply Highstate" 60ms

Then I should see a "Applying the highstate has been scheduled." text 462ms

And I wait until event "Apply highstate scheduled" is completed 55s 179ms

@skip_if_github_validation
Scenario:
Wait for services
1s 2ms 3

When I wait until "node" exporter service is active on "deblike_minion" 479ms

And I wait until "apache" exporter service is active on "deblike_minion" 271ms

And I wait until "postgres" exporter service is active on "deblike_minion" 250ms

Scenario:
Visit monitoring endpoints on the Debian-like minion
703ms 3

And I visit "Prometheus node exporter" endpoint of this "deblike_minion" 237ms

And I visit "Prometheus apache exporter" endpoint of this "deblike_minion" 235ms

And I visit "Prometheus postgres exporter" endpoint of this "deblike_minion" 230ms

Scenario:
Cleanup: undo Prometheus exporter formulas on the Debian-like minion
1s 998ms 4

When I follow "Formulas" in the content area 84ms

And I uncheck the "prometheus-exporters" formula 278ms

And I click on "Save" 64ms

Then I wait until I see "Formula saved" text 1s 570ms

@skip_if_github_validation
Scenario:
Cleanup: apply highstate after test monitoring on the Debian-like minion
23s 417ms 4

When I follow "States" in the content area 82ms

And I click on "Apply Highstate" 60ms

Then I should see a "Applying the highstate has been scheduled." text 552ms

And I wait until event "Apply highstate scheduled" is completed 22s 721ms

Scenario:
Cleanup: Disable tools_update_repo tools_pool_repo because they are no longer needed
1s 123ms 1

When I disable the repositories "tools_update_repo tools_pool_repo" on this "deblike_minion" without error control 1s 123ms

@deblike_minion @scope_deblike @scope_content_staging
Feature:Install a package on the Debian-like minion with staging enabled 4m 15s 71ms 7 1

Scenario:
Pre-requisite: install virgo-dummy-1.0 package, make sure orion-dummy is not present on Debian-like minion
2s 3ms 4

When I enable repository "test_repo_deb_pool" on this "deblike_minion" 469ms

And I run "apt update" on "deblike_minion" 962ms

And I remove package "orion-dummy" from this "deblike_minion" 277ms

And I install old package "virgo-dummy=1.0" on this "deblike_minion" 293ms

Scenario:
Pre-requisite: refresh package list on Debian-like minion
25s 826ms 3

When I refresh packages list via spacecmd on "deblike_minion" 8s 371ms

And I wait until refresh package list on "deblike_minion" is finished 10s 645ms

Then spacecmd should show packages "virgo-dummy-1.0" installed on "deblike_minion" 6s 809ms

Scenario:
Log in as admin user
492ms 1

Given I am authorized for the "Admin" section 492ms

Scenario:
Pre-requisite: ensure the errata cache is computed for Debian-like minion
9s 803ms 6

When I follow the left menu "Admin > Task Schedules" 129ms

And I follow "errata-cache-default" 1s 238ms

And I follow "errata-cache-bunch" 1s 307ms

Then I click on "Single Run Schedule" 1s 568ms

And I should see a "bunch was scheduled" text 276ms

Then I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 5s 282ms

Scenario:
Enable content staging for Debian-like minion
1s 250ms 6

When I follow the left menu "Admin > Organizations" 68ms

And I follow first "SUSE Test" 293ms

And I follow first "Configuration" 275ms

And I check "staging_content_enabled" 41ms

And I click on "Update Organization" 508ms

Then I should see a "was successfully updated." text 64ms

Scenario:
Install package in the future and check for staging on Debian-like minion
3m 3s 874ms 13

Given I am on the Systems overview page of this "deblike_minion" 1s 259ms

And I follow "Software" in the content area 68ms

And I follow "Packages" in the content area 67ms

And I follow "Install" in the content area 62ms

And I enter "orion-dummy-1.1-X" as the filtered package name 60ms

And I click on the filter button 496ms

When I check "orion-dummy-1.1-X" in the list 60ms

And I click on "Install Packages" 597ms

And I pick 3 minutes from now as schedule time 87ms

And I click on "Confirm" 671ms

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" 43s 265ms

And I wait for "orion-dummy-1.1" to be installed on "deblike_minion" 2m 17s 112ms

Scenario:
Install patch in the future and check for staging on Debian-like minion
28s 852ms 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 13ms 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

18s 708ms Show Info + 
17:15:08:000 - 17:15:19: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 968ms 4

And I remove package "orion-dummy" from this "deblike_minion" 1s 217ms

And I remove package "virgo-dummy" from this "deblike_minion" 365ms

And I disable repository "test_repo_deb_pool" on this "deblike_minion" 242ms

And I run "apt update" on "deblike_minion" 1s 143ms

@scope_deblike @scope_salt @deblike_minion
Feature:Install and upgrade package on the Debian-like minion via Salt through the UI 1m 44s 995ms 9 1 1

Scenario:
Pre-requisite: enable test_repo_deb_pool repository on the Debian-like minion
517ms 1

When I enable repository "test_repo_deb_pool" on this "deblike_minion" 517ms

Scenario:
Pre-requisite: install virgo-dummy-1.0 package on Debian-like minion
3s 444ms 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 (5,235 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 1s 41ms

And I install old package "virgo-dummy=1.0" on this "deblike_minion" 2s 403ms

Scenario:
Pre-requisite: remove andromeda-dummy package from Debian-like minion
414ms 1

When I remove package "andromeda-dummy" from this "deblike_minion" 414ms

Scenario:
Log in as org admin user
488ms 1

Given I am authorized 488ms

Scenario:
Pre-requisite: refresh package list and check newly installed packages on Debian-like minion
43s 119ms 7

Given I am on the Systems overview page of this "deblike_minion" 1s 884ms

When I follow "Software" in the content area 75ms

And I click on "Update Package List" 1s 371ms

And I follow "Events" in the content area 70ms

And I wait until I do not see "Package List Refresh scheduled" text, refreshing the page 24s 205ms

And I wait until package "virgo-dummy" is installed on "deblike_minion" via spacecmd 8s 245ms

And I wait until package "andromeda-dummy" is removed from "deblike_minion" via spacecmd 7s 266ms

Scenario:
Install a patch on the Debian-like minion
28s 240ms 3 4 1

When I follow "Software" in the content area 60ms

And I follow "Patches" in the content area 61ms

When I check "3456-1" in the list 10s 3ms Show Error + 
                                            
 Unable to find xpath "//table/tbody/tr[.//td[contains(.,'3456-1')]]//input[@type='checkbox']" (Capybara::ElementNotFound)
./features/support/navigation_step_helper.rb:32:in `toggle_checkbox_in_list'
./features/support/navigation_step_helper.rb:10:in `toggle_checkbox_in_package_list'
./features/step_definitions/navigation_steps.rb: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

18s 115ms Show Info + 
17:16:42:000 - 17:16:53: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 671ms 8

When I follow "Software" in the content area 67ms

And I follow "Install" 448ms

And I check "andromeda-dummy-2.0" in the list 60ms

And I click on "Install Packages" 648ms

And I click on "Confirm" 772ms

And I should see a "1 package install has been scheduled for" text 62ms

When I wait until event "Package Install/Upgrade scheduled" is completed 23s 447ms

Then Deb package "andromeda-dummy" with version "2.0" should be installed on "deblike_minion" 1s 163ms

Scenario:
Cleanup: disable test_repo_deb_pool on Debian-like minion
222ms 1

When I disable repository "test_repo_deb_pool" on this "deblike_minion" 222ms

Scenario:
Cleanup: remove virgo-dummy package from Debian-like minion
382ms 1

When I remove package "virgo-dummy" from this "deblike_minion" 382ms

Scenario:
Cleanup: remove andromeda-dummy package from Debian-like minion
1s 494ms 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" 363ms

And I run "apt update" on "deblike_minion" with logging 1s 130ms

@skip_if_github_validation @sle_minion @scope_onboarding
Feature:Negative tests for bootstrapping normal minions 21s 449ms 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
421ms 1

Given I am authorized 421ms

Scenario:
Bootstrap should fail when minion already exists
1s 20ms 10

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 133ms

Then I should see a "Bootstrap Minions" text 83ms

When I enter the hostname of "sle_minion" as "hostname" 144ms

And I enter "22" as "port" 55ms

And I enter "root" as "user" 59ms

And I enter "linux" as "password" 66ms

And I click on "Bootstrap" 67ms

And I wait until I see "A salt key for this host" text 281ms

Then I should not see a "GenericSaltError" text 63ms

And I should see a "seems to already exist, please check!" text 64ms

Scenario:
Bootstrap a SLES minion with wrong hostname
2s 751ms 14

When I follow the left menu "Systems > Bootstrapping" 64ms

Then I should see a "Bootstrap Minions" text 66ms

When I enter "not-existing-name" as "hostname" 82ms

And I enter "22" as "port" 48ms

And I enter "root" as "user" 52ms

And I enter "linux" as "password" 56ms

And I click on "Bootstrap" 56ms

And I wait until I see "An error has occurred during salt execution: unable to establish ssh connection." text 2s 65ms

Then I should see a "Details" button 20ms

When I click on "Details" 82ms

And I wait at most 10 seconds until I see modal containing "Error Details" text 11ms

Then I should see a "Standard Error" text 73ms

And I should see "Could not resolve hostname not-existing-name: Name or service not known" in the stderr textarea 16ms

When I close the modal dialog 54ms

Scenario:
Bootstrap a SLES minion with wrong SSH credentials
14s 389ms 14

The hostname of localhost is uyuni-master-controller.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 62ms

Then I should see a "Bootstrap Minions" text 65ms

When I enter the hostname of "localhost" as "hostname" 125ms

And I enter "22" as "port" 47ms

And I enter "FRANZ" as "user" 57ms

And I enter "KAFKA" as "password" 55ms

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 13s 708ms

Then I should see a "Details" button 13ms

When I click on "Details" 58ms

And I wait at most 10 seconds until I see modal containing "Error Details" text 8ms

Then I should see a "Standard Error" text 70ms

And I should see "Permission denied (publickey" or "Password authentication failed" in the stderr textarea 13ms

When I close the modal dialog 45ms

Scenario:
Bootstrap a SLES minion with wrong SSH port number
2s 866ms 14

The hostname of localhost is uyuni-master-controller.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 65ms

Then I should see a "Bootstrap Minions" text 65ms

When I enter the hostname of "localhost" as "hostname" 122ms

And I enter "11" as "port" 49ms

And I enter "root" as "user" 54ms

And I enter "linux" as "password" 56ms

And I click on "Bootstrap" 61ms

And I wait until I see "An error has occurred during salt execution: unable to establish ssh connection." text 2s 179ms

Then I should see a "Details" button 13ms

When I click on "Details" 60ms

And I wait at most 10 seconds until I see modal containing "Error Details" text 7ms

Then I should see a "Standard Error" text 70ms

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 47ms

@skip_if_github_validation @scope_formulas @bug_reported
Feature:Use salt formulas 5m 43s 2ms 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
443ms 1

Given I am authorized 443ms

@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 508ms 1

When I synchronize all Salt dynamic modules on "sle_minion" 5s 508ms

Scenario:
The new formula appears on the server
354ms 2

When I follow the left menu "Salt > Formula Catalog" 126ms

Then I should see a "locale" text in the content area 228ms

Scenario:
Enable the formula on the minion
12s 753ms 9

Given I am on the Systems overview page of this "sle_minion" 1s 522ms

When I follow "Formulas" in the content area 77ms

Then I should see a "Choose formulas:" text 66ms

And I should see a "General System Configuration" text 192ms

And I should see a "Locale" text 89ms

When I check the "locale" formula 76ms

And I click on "Save" 64ms

And I wait until I see "Formula saved." text 638ms

Then the "locale" formula should be checked 10s 26ms

Scenario:
Parametrize the formula on the minion
1s 566ms 8

When I follow "Formulas" in the content area 63ms

And I follow first "Locale" in the content area 245ms

And I click on "Expand All Sections" 316ms

And I select "Etc/GMT-5" in timezone name field 63ms

And I select "French" in language field 51ms

And I select "French (Canada)" in keyboard layout field 48ms

And I click on "Save Formula" 62ms

Then I should see a "Formula saved" text 714ms

Scenario:
Check the pillar data after saving the formula
19s 276ms 5

When I refresh the pillar data 4s 350ms

Then the pillar data for "formulas" should be "- locale" on "sle_minion" 3s 408ms

And the pillar data for "timezone:name" should be "Etc/GMT-5" on "sle_minion" 3s 542ms

And the pillar data for "keyboard_and_language:keyboard_layout" should be "French (Canada)" on "sle_minion" 4s 474ms

And the pillar data for "keyboard_and_language:language" should be "French" on "sle_minion" 3s 500ms

@ssh_minion
Scenario:
No other minion is affected by the formula
31s 434ms 3

Then the pillar data for "formulas" should be empty on "ssh_minion" 11s 311ms

And the pillar data for "timezone" should be empty on "ssh_minion" 10s 84ms

And the pillar data for "keyboard_and_language" should be empty on "ssh_minion" 10s 39ms

Scenario:
Use the parametrized formula in test mode
40s 354ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 7ms

And I follow "States" in the content area 69ms

Then I should see the toggler "disabled" 11ms

When I click on the "disabled" toggler 45ms

And I click on "Apply Highstate" 59ms

Then I should see a "Applying the highstate has been scheduled." text 340ms

And I wait at most 300 seconds until event "Apply highstate in test-mode scheduled" is completed 38s 821ms

Scenario:
Apply the parametrized formula via the highstate
43s 434ms 9

When I enable repository "sle_update_repo" on this "sle_minion" without error control 845ms

And I follow "States" in the content area 77ms

And I click on "Apply Highstate" 61ms

Then I should see a "Applying the highstate has been scheduled." text 441ms

When I wait until event "Apply highstate scheduled" is completed 38s 941ms

Then the timezone on "sle_minion" should be "+05" 937ms

And the keymap on "sle_minion" should be "ca" 474ms

And the language on "sle_minion" should be "fr_FR.UTF-8" 992ms

And I disable repository "sle_update_repo" on this "sle_minion" without error control 662ms

Scenario:
Reset the formula on the minion
1s 529ms 5

When I follow "Formulas" in the content area 80ms

And I follow first "Locale" in the content area 377ms

And I click on "Clear values" and confirm alert box 402ms

And I click on "Save Formula" 68ms

Then I should see a "Formula saved" text 600ms

Scenario:
Check the pillar data after resetting the formula
19s 458ms 5

When I refresh the pillar data 4s 421ms

Then the pillar data for "formulas" should be "- locale" on "sle_minion" 3s 449ms

And the pillar data for "timezone:name" should be "CET" on "sle_minion" 4s 651ms

And the pillar data for "keyboard_and_language:keyboard_layout" should be "English (US)" on "sle_minion" 3s 488ms

And the pillar data for "keyboard_and_language:language" should be "English (US)" on "sle_minion" 3s 447ms

Scenario:
Apply the reset formula via the highstate
41s 641ms 7

And I follow "States" in the content area 73ms

And I click on "Apply Highstate" 59ms

Then I should see a "Applying the highstate has been scheduled." text 464ms

When I wait until event "Apply highstate scheduled" is completed 38s 657ms

Then the timezone on "sle_minion" should be "CET" 903ms

And the keymap on "sle_minion" should be "us" 563ms

And the language on "sle_minion" should be "en_US.UTF-8" 920ms

Scenario:
Disable the formula on the minion
11s 355ms 8

When I follow "Formulas" in the content area 79ms

Then I should see a "Choose formulas:" text 71ms

And I should see a "General System Configuration" text 183ms

And I should see a "Locale" text 88ms

When I uncheck the "locale" formula 74ms

And I click on "Save" 62ms

And I wait until I see "Formula saved." text 771ms

Then the "locale" formula should be unchecked 10s 23ms

Scenario:
Check the pillar data after disabling the formula
16s 165ms 4

When I refresh the pillar data 4s 413ms

Then the pillar data for "formulas" should be empty on "sle_minion" 3s 473ms

And the pillar data for "timezone" should be empty on "sle_minion" 3s 420ms

And the pillar data for "keyboard_and_language" should be empty on "sle_minion" 4s 858ms

Scenario:
Assign locale formula to minion via group formula
3s 620ms 17

When I follow the left menu "Systems > System Groups" 75ms

When I follow "Create Group" 283ms

And I enter "locale-formula-group" as "name" 89ms

And I enter "Test group with locale formula added" as "description" 77ms

And I click on "Create Group" 62ms

Then I should see a "System group locale-formula-group created." text 73ms

When I follow "Formulas" in the content area 74ms

Then I should see a "Choose formulas:" text 71ms

And I should see a "General System Configuration" text 208ms

And I should see a "Locale" text 86ms

When I check the "locale" formula 77ms

And I click on "Save" 62ms

And I wait until I see "Formula saved." text 491ms

And I follow "Target" 502ms

And I check the "sle_minion" client 61ms

And I click on "Add Systems" 1s 221ms

Then I should see a "1 systems were added to locale-formula-group server group." text 99ms

Scenario:
Check the pillar data after assigning group formula
19s 798ms 5

When I refresh the pillar data 4s 220ms

Then the pillar data for "formulas" should be "- locale" on "sle_minion" 3s 437ms

And the pillar data for "timezone:name" should be "CET" on "sle_minion" 5s 248ms

And the pillar data for "keyboard_and_language:keyboard_layout" should be "English (US)" on "sle_minion" 3s 426ms

And the pillar data for "keyboard_and_language:language" should be "English (US)" on "sle_minion" 3s 464ms

@ssh_minion
Scenario:
No other minion is affected by the group formula
29s 762ms 3

Then the pillar data for "formulas" should be empty on "ssh_minion" 10s 338ms

And the pillar data for "timezone" should be empty on "ssh_minion" 9s 734ms

And the pillar data for "keyboard_and_language" should be empty on "ssh_minion" 9s 690ms

Scenario:
Cleanup: remove "locale-formula-group" system group
1s 451ms 7

When I follow the left menu "Systems > System Groups" 76ms

And I follow "locale-formula-group" in the content area 79ms

And I follow "Delete Group" in the content area 73ms

When I click on "Confirm Deletion" 1s 41ms

Then I should see a "System group" text 61ms

And I should see a "locale-formula-group" text 57ms

And I should see a "deleted" text 61ms

Scenario:
Cleanup: reset locale values on the minion
43s 22ms 8

Given I am on the Systems overview page of this "sle_minion" 959ms

And I follow "States" in the content area 70ms

And I click on "Apply Highstate" 59ms

Then I should see a "Applying the highstate has been scheduled." text 891ms

When I wait until event "Apply highstate scheduled" is completed 38s 752ms

Then the timezone on "sle_minion" should be "CET" 861ms

And the keymap on "sle_minion" should be "us" 469ms

And the language on "sle_minion" should be "en_US.UTF-8" 958ms

@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
70ms 1

When I click on the clear SSM button 70ms

@flaky @scope_formulas
Feature:Use advanced features of Salt formulas 7m 39s 71ms 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
438ms 1

Given I am authorized 438ms

Scenario:
Install a test formula package on the server
15s 808ms 5

When I install "form.yml" to custom formula metadata directory "testform" 9s 145ms

And I install "metadata.yml" to custom formula metadata directory "testform" 6s 208ms

When I follow the left menu "Salt > Formula Catalog" 133ms

And I enter "testform" as the filtered formula name 83ms

Then I should see a "testform" text 238ms

Scenario:
Assign test formula to minion via group formula
4s 81ms 17

When I follow the left menu "Systems > System Groups" 121ms

When I follow "Create Group" 283ms

And I enter "test-formula-group" as "name" 67ms

And I enter "Test group with testform formula added" as "description" 78ms

And I click on "Create Group" 484ms

Then I should see a "System group test-formula-group created." text 68ms

When I follow "Formulas" in the content area 75ms

Then I should see a "Choose formulas:" text 60ms

And I should see a "General System Configuration" text 198ms

And I should see a "Testform" text 90ms

When I check the "testform" formula 75ms

And I click on "Save" 62ms

And I wait until I see "Formula saved." text 502ms

And I follow "Target Systems" 435ms

And I check the "sle_minion" client 61ms

And I click on "Add Systems" 1s 313ms

Then I should see a "1 systems were added to test-formula-group server group." text 100ms

Scenario:
Verify default values
1m 35s 667ms 25

When I refresh the pillar data 4s 553ms

Then the pillar data for "testing:str" should be "" on "sle_minion" 3s 487ms

And the pillar data for "testing:str_def" should be "defvalue" on "sle_minion" 3s 475ms

And the pillar data for "testing:str_or_null" should be "None" on "sle_minion" 3s 404ms

And the pillar data for "testing" should not contain "str_opt" on "sle_minion" 4s 863ms

And the pillar data for "testing:num" should be "" on "sle_minion" 4s 29ms

And the pillar data for "testing:num_def" should be "0" on "sle_minion" 3s 397ms

And the pillar data for "testing:num_or_null" should be "None" on "sle_minion" 3s 401ms

And the pillar data for "testing" should not contain "num_opt" on "sle_minion" 5s 280ms

And the pillar data for "testing:pw" should be "" on "sle_minion" 3s 475ms

And the pillar data for "testing:pw_or_null" should be "None" on "sle_minion" 3s 443ms

And the pillar data for "testing" should not contain "pw_opt" on "sle_minion" 3s 480ms

And the pillar data for "testing:list_of_strings" should contain "def_item1" on "sle_minion" 4s 582ms

And the pillar data for "testing:list_of_strings" should contain "def_item2" on "sle_minion" 3s 481ms

And the pillar data for "testing:dict_of_strings:name1" should be "def_value1" on "sle_minion" 3s 429ms

And the pillar data for "testing:dict_of_strings:name2" should be "def_value2" on "sle_minion" 3s 535ms

And the pillar data for "testing:list_of_dicts:0:name" should be "def_user" on "sle_minion" 4s 479ms

And the pillar data for "testing:list_of_dicts:0:password" should be "secret1" on "sle_minion" 3s 447ms

And the pillar data for "testing:list_of_dicts:0" should not contain "full_name" on "sle_minion" 3s 456ms

And the pillar data for "testing:dict_of_dicts:def_user:name" should be "root" on "sle_minion" 3s 422ms

And the pillar data for "testing:dict_of_dicts:def_user:password" should be "secret2" on "sle_minion" 4s 581ms

And the pillar data for "testing:dict_of_dicts:def_user:full_name" should be "None" on "sle_minion" 3s 510ms

And the pillar data for "testing:recursive_dict_of_dicts:def_gr1:group_name" should be "default group 1" on "sle_minion" 3s 549ms

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 463ms

And the pillar data for "testing:recursive_dict_of_dicts:def_gr1:entries:def_entry1:entry_desc" should be "some text" on "sle_minion" 4s 435ms

Scenario:
Fill in and verify non-default values in group formula
46s 284ms 30

When I follow the left menu "Systems > System Groups" 61ms

When I follow "test-formula-group" in the content area 76ms

And I follow "Formulas" in the content area 65ms

And I follow first "Testform" in the content area 262ms

And I click on "Expand All Sections" 278ms

And I enter "text1" as "testing#str" 98ms

And I enter "text2" as "testing#str_def" 132ms

And I enter "text3" as "testing#str_or_null" 86ms

And I enter "text4" as "testing#str_opt" 100ms

And I enter "1" as "testing#num" 58ms

And I enter "2" as "testing#num_def" 82ms

And I enter "3" as "testing#num_or_null" 62ms

And I enter "4" as "testing#num_opt" 63ms

And I enter "pw1" as "testing#pw" 92ms

And I enter "pw2" as "testing#pw_or_null" 92ms

And I enter "pw3" as "testing#pw_opt" 75ms

And I click on "Save Formula" 99ms

Then I should see a "Formula saved" text 733ms

When I wait for "1" seconds 1s

Then the pillar data for "testing:str" should be "text1" on "sle_minion" 3s 465ms

And the pillar data for "testing:str_def" should be "text2" on "sle_minion" 3s 413ms

And the pillar data for "testing:str_or_null" should be "text3" on "sle_minion" 5s 186ms

And the pillar data for "testing:str_opt" should be "text4" on "sle_minion" 3s 393ms

And the pillar data for "testing:num" should be "1" on "sle_minion" 3s 433ms

And the pillar data for "testing:num_def" should be "2" on "sle_minion" 5s 285ms

And the pillar data for "testing:num_or_null" should be "3" on "sle_minion" 3s 427ms

And the pillar data for "testing:num_opt" should be "4" on "sle_minion" 3s 532ms

And the pillar data for "testing:pw" should be "pw1" on "sle_minion" 3s 506ms

And the pillar data for "testing:pw_or_null" should be "pw2" on "sle_minion" 4s 546ms

And the pillar data for "testing:pw_opt" should be "pw3" on "sle_minion" 3s 569ms

Scenario:
Clear values in group formula and verify the defaults again
1m 34s 392ms 32

When I follow the left menu "Systems > System Groups" 85ms

When I follow "test-formula-group" in the content area 75ms

And I follow "Formulas" in the content area 76ms

And I follow first "Testform" in the content area 224ms

And I click on "Clear values" and confirm alert box 533ms

And I click on "Save Formula" 88ms

Then I should see a "Formula saved" text 670ms

When I wait for "1" seconds 1s

Then the pillar data for "testing:str" should be "" on "sle_minion" 3s 397ms

And the pillar data for "testing:str_def" should be "defvalue" on "sle_minion" 4s 534ms

And the pillar data for "testing:str_or_null" should be "None" on "sle_minion" 3s 485ms

And the pillar data for "testing" should not contain "str_opt" on "sle_minion" 3s 555ms

And the pillar data for "testing:num" should be "" on "sle_minion" 3s 475ms

And the pillar data for "testing:num_def" should be "0" on "sle_minion" 5s 2ms

And the pillar data for "testing:num_or_null" should be "None" on "sle_minion" 4s 109ms

And the pillar data for "testing" should not contain "num_opt" on "sle_minion" 3s 444ms

And the pillar data for "testing:pw" should be "" on "sle_minion" 3s 426ms

And the pillar data for "testing:pw_or_null" should be "None" on "sle_minion" 5s 198ms

And the pillar data for "testing" should not contain "pw_opt" on "sle_minion" 3s 469ms

And the pillar data for "testing:list_of_strings" should contain "def_item1" on "sle_minion" 3s 394ms

And the pillar data for "testing:list_of_strings" should contain "def_item2" on "sle_minion" 3s 632ms

And the pillar data for "testing:dict_of_strings:name1" should be "def_value1" on "sle_minion" 4s 623ms

And the pillar data for "testing:dict_of_strings:name2" should be "def_value2" on "sle_minion" 3s 405ms

And the pillar data for "testing:list_of_dicts:0:name" should be "def_user" on "sle_minion" 3s 534ms

And the pillar data for "testing:list_of_dicts:0:password" should be "secret1" on "sle_minion" 3s 609ms

And the pillar data for "testing:list_of_dicts:0" should not contain "full_name" on "sle_minion" 4s 427ms

And the pillar data for "testing:dict_of_dicts:def_user:name" should be "root" on "sle_minion" 3s 461ms

And the pillar data for "testing:dict_of_dicts:def_user:password" should be "secret2" on "sle_minion" 3s 461ms

And the pillar data for "testing:dict_of_dicts:def_user:full_name" should be "None" on "sle_minion" 3s 478ms

And the pillar data for "testing:recursive_dict_of_dicts:def_gr1:group_name" should be "default group 1" on "sle_minion" 4s 505ms

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 590ms

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 414ms

Scenario:
Fill in and verify mix of default and non-default values in group formula
44s 797ms 23

When I follow the left menu "Systems > System Groups" 71ms

When I follow "test-formula-group" in the content area 72ms

And I follow "Formulas" in the content area 65ms

And I follow first "Testform" in the content area 206ms

And I click on "Expand All Sections" 216ms

And I enter "text1" as "testing#str" 115ms

And I enter "1" as "testing#num" 62ms

And I enter "2" as "testing#num_def" 86ms

And I enter "pw1" as "testing#pw" 85ms

And I click on "Save Formula" 84ms

Then I should see a "Formula saved" text 744ms

When I wait for "1" seconds 1s

Then the pillar data for "testing:str" should be "text1" on "sle_minion" 4s 425ms

And the pillar data for "testing:str_def" should be "defvalue" on "sle_minion" 3s 980ms

And the pillar data for "testing:str_or_null" should be "None" on "sle_minion" 3s 456ms

And the pillar data for "testing" should not contain "str_opt" on "sle_minion" 3s 415ms

And the pillar data for "testing:num" should be "1" on "sle_minion" 4s 629ms

And the pillar data for "testing:num_def" should be "2" on "sle_minion" 3s 458ms

And the pillar data for "testing:num_or_null" should be "None" on "sle_minion" 3s 404ms

And the pillar data for "testing" should not contain "num_opt" on "sle_minion" 3s 617ms

And the pillar data for "testing:pw" should be "pw1" on "sle_minion" 4s 652ms

And the pillar data for "testing:pw_or_null" should be "None" on "sle_minion" 3s 491ms

And the pillar data for "testing" should not contain "pw_opt" on "sle_minion" 3s 452ms

Scenario:
Verify that minion form inherits the values from group form
45s 90ms 16

Given I am on the Systems overview page of this "sle_minion" 1s 396ms

When I follow "Formulas" in the content area 74ms

And I follow first "Testform" in the content area 304ms

And I click on "Save Formula" 221ms

Then I should see a "Formula saved" text 562ms

And the pillar data for "testing:str" should be "text1" on "sle_minion" 5s 59ms

And the pillar data for "testing:str_def" should be "defvalue" on "sle_minion" 3s 440ms

And the pillar data for "testing:str_or_null" should be "None" on "sle_minion" 3s 554ms

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 "1" on "sle_minion" 4s 512ms

And the pillar data for "testing:num_def" should be "2" on "sle_minion" 3s 705ms

And the pillar data for "testing:num_or_null" should be "None" on "sle_minion" 3s 451ms

And the pillar data for "testing" should not contain "num_opt" on "sle_minion" 3s 422ms

And the pillar data for "testing:pw" should be "pw1" on "sle_minion" 3s 436ms

And the pillar data for "testing:pw_or_null" should be "None" on "sle_minion" 5s 113ms

And the pillar data for "testing" should not contain "pw_opt" on "sle_minion" 3s 418ms

Scenario:
Fill in and verify non-default values in minion formula
45s 483ms 28

When I follow "Formulas" in the content area 65ms

And I follow first "Testform" in the content area 217ms

And I click on "Expand All Sections" 220ms

And I enter "min_text1" as "testing#str" 175ms

And I enter "min_text2" as "testing#str_def" 161ms

And I enter "min_text3" as "testing#str_or_null" 103ms

And I enter "min_text4" as "testing#str_opt" 107ms

And I enter "101" as "testing#num" 99ms

And I enter "102" as "testing#num_def" 85ms

And I enter "103" as "testing#num_or_null" 69ms

And I enter "104" as "testing#num_opt" 77ms

And I enter "min_pw1" as "testing#pw" 136ms

And I enter "min_pw2" as "testing#pw_or_null" 100ms

And I enter "min_pw3" as "testing#pw_opt" 116ms

And I click on "Save Formula" 102ms

Then I should see a "Formula saved" text 744ms

When I wait for "1" seconds 1s

Then the pillar data for "testing:str" should be "min_text1" on "sle_minion" 4s 612ms

And the pillar data for "testing:str_def" should be "min_text2" on "sle_minion" 3s 448ms

And the pillar data for "testing:str_or_null" should be "min_text3" on "sle_minion" 3s 385ms

And the pillar data for "testing:str_opt" should be "min_text4" on "sle_minion" 3s 472ms

And the pillar data for "testing:num" should be "101" on "sle_minion" 4s 928ms

And the pillar data for "testing:num_def" should be "102" on "sle_minion" 3s 420ms

And the pillar data for "testing:num_or_null" should be "103" on "sle_minion" 3s 487ms

And the pillar data for "testing:num_opt" should be "104" on "sle_minion" 3s 584ms

And the pillar data for "testing:pw" should be "min_pw1" on "sle_minion" 4s 563ms

And the pillar data for "testing:pw_or_null" should be "min_pw2" on "sle_minion" 3s 500ms

And the pillar data for "testing:pw_opt" should be "min_pw3" on "sle_minion" 3s 492ms

Scenario:
Clear values in minion formula and verify that the pillar is set to group values
44s 670ms 17

When I follow "Formulas" in the content area 86ms

And I follow first "Testform" in the content area 167ms

And I click on "Clear values" and confirm alert box 345ms

And I click on "Save Formula" 73ms

Then I should see a "Formula saved" text 588ms

When I wait for "1" seconds 1s

Then the pillar data for "testing:str" should be "text1" on "sle_minion" 4s 886ms

And the pillar data for "testing:str_def" should be "defvalue" on "sle_minion" 3s 546ms

And the pillar data for "testing:str_or_null" should be "None" on "sle_minion" 3s 445ms

And the pillar data for "testing" should not contain "str_opt" on "sle_minion" 3s 449ms

And the pillar data for "testing:num" should be "1" on "sle_minion" 3s 428ms

And the pillar data for "testing:num_def" should be "2" on "sle_minion" 5s 205ms

And the pillar data for "testing:num_or_null" should be "None" on "sle_minion" 3s 382ms

And the pillar data for "testing" should not contain "num_opt" on "sle_minion" 3s 357ms

And the pillar data for "testing:pw" should be "pw1" on "sle_minion" 4s 843ms

And the pillar data for "testing:pw_or_null" should be "None" on "sle_minion" 3s 455ms

And the pillar data for "testing" should not contain "pw_opt" on "sle_minion" 3s 408ms

Scenario:
Cleanup: remove formula from minion
11s 38ms 5

When I follow "Formulas" in the content area 60ms

And I uncheck the "testform" formula 214ms

And I click on "Save" 81ms

And I wait until I see "Formula saved." text 646ms

Then the "testform" formula should be unchecked 10s 35ms

Scenario:
Cleanup: remove "test-formula-group" system group
11s 317ms 9

When I follow the left menu "Systems > System Groups" 82ms

And I follow "test-formula-group" in the content area 75ms

And I follow "Delete Group" in the content area 67ms

When I click on "Confirm Deletion" 1s 9ms

Then I should see a "System group" text 62ms

Then I should see a "test-formula-group" text 56ms

And I should see a "deleted" text 58ms

And I wait until there is no pillar refresh salt job active 5s 309ms

Then the pillar data for "testing" should be empty on "sle_minion" 4s 594ms

@skip_if_github_validation @scope_openscap
Feature:OpenSCAP audit of Salt minion 2m 10s 321ms 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 310ms 2

Given I am authorized for the "Admin" section 443ms

And I am on the Systems overview page of this "sle_minion" 1s 866ms

@Uyuni
Scenario:
Enable required repositories
866ms 1

When I enable repository "repo-oss" on this "sle_minion" without error control 866ms

@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 248ms 2 3 1

When I refresh the metadata for "sle_minion" 1s 32ms

And I install OpenSCAP dependencies on "sle_minion" 832ms 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:981:in `/^I install packages? "([^"]*)" on this "([^"]*)"((?: without error control)?)$/'
./features/step_definitions/command_steps.rb:959: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 384ms Show Info + 
17:32:31:000 - 17:32: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 221ms 3 5 1

When I follow "Audit" in the content area 75ms

And I follow "OpenSCAP" in the content area 67ms

And I follow "Schedule" in the content area 65ms

And I wait at most 30 seconds until I do not see "This system does not yet have OpenSCAP scan capability." text, refreshing the page 33s 13ms 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 3ms 8 1

When I follow "Audit" in the content area 10s 3ms 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 8ms 8 1

When I follow "Audit" in the content area 10s 8ms 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 8ms 6 1

When I follow "Audit" in the content area 10s 8ms 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 3ms 5 1

When I follow the left menu "Admin > Organizations" 10s 3ms 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
29s 13ms 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" 828ms

When I follow "Audit" in the content area 10s 18ms 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

18s 166ms Show Info + 
17:35:58:000 - 17:36:09: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" 128ms

When I follow "SUSE Test" in the content area 66ms

And I follow "Configuration" in the content area 63ms

And I enter "90" as "scap_retention_period" 63ms

And I click on "Update Organization" 422ms

Then I should see a "Organization SUSE Test was successfully updated." text 68ms

Scenario:
Cleanup: remove the OpenSCAP packages from the SLE minion
1s 323ms 1

When I remove OpenSCAP dependencies from "sle_minion" 1s 323ms

@Uyuni
Scenario:
Cleanup: Disable required repositories
499ms 1

When I disable repository "repo-oss" on this "sle_minion" without error control 499ms

@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 18s 137ms 4

Scenario:
Log in as org admin user
435ms 1

Given I am authorized 435ms

Scenario:
Create a user-defined state
17s 127ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 555ms

When I follow "States" in the content area 72ms

And I install a user-defined state for "sle_minion" on the server 9s 73ms

And I follow "Highstate" in the content area 65ms

And I click on "Show full highstate output" 317ms

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
40s 692ms 3

When I schedule a highstate for "sle_minion" via API 875ms

And I wait until event "Apply highstate scheduled" is completed 38s 871ms

Then file "/tmp/test_user_defined_state" should exist on "sle_minion" 945ms

Scenario:
Cleanup: remove user-defined state and the file it created
19s 882ms 7

When I follow "States" in the content area 83ms

And I uninstall the user-defined state from the server 3s 14ms

And I uninstall the managed file from "sle_minion" 470ms

And I follow "Highstate" in the content area 64ms

And I click on "Show full highstate output" 227ms

And I wait for "6" seconds 6s

Then I should not see a "user_defined_state" text in element "highstate" 10s 21ms

@scope_salt
Feature:Verify the minion registration 47s 925ms 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
427ms 1

Given I am authorized 427ms

Scenario:
Check the Salt entitlement
1s 623ms 2

Given I am on the Systems overview page of this "sle_minion" 1s 530ms

Then I should see a "[Salt]" text 93ms

Scenario:
Check that installed packages are visible
1s 149ms 3

When I follow "Software" in the content area 84ms

And I follow "List / Remove" 773ms

Then I should see a "aaa_base" text 291ms

Scenario:
Check that Hardware Refresh button works on a SLES Salt minion
43s 803ms 6

When I follow "Details" in the content area 70ms

And I follow "Hardware" in the content area 66ms

And I click on "Schedule Hardware Refresh" 896ms

Then I should see a "You have successfully scheduled a hardware profile refresh" text 117ms

When I wait until event "Hardware List Refresh scheduled" is completed 39s 851ms

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "sle_minion" 2s 801ms

Scenario:
Check that Update Properties button works
921ms 4

When I follow "Details" in the content area 85ms

And I follow "Hardware" in the content area 71ms

And I click on "Update Properties" 637ms

Then I should see a "Networking properties updated." text 127ms

@sle_minion @scope_configuration_channels
Feature:Configuration state channels 1m 57s 456ms 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
645ms 1

Given I am authorized 645ms

Scenario:
Create a state channel
1s 767ms 12

When I follow the left menu "Configuration > Channels" 127ms

And I follow "Create State Channel" 282ms

Then I should see a "New Config State Channel" text 59ms

When I enter "My State Channel" as "cofName" 72ms

And I enter "statechannel" as "cofLabel" 59ms

And I enter "This is a state channel" as "cofDescription" 69ms

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" 827ms

Then I should see a "State Channel" text 68ms

And I should see a "Channel Properties" text 69ms

And I should see a "Channel Information" text 63ms

And I should see a "Configuration Actions" text 61ms

Scenario:
Subscribe a minion to the state channel
2s 769ms 8

When I am on the Systems overview page of this "sle_minion" 1s 72ms

And I follow "Configuration" in the content area 67ms

And I follow "Manage Configuration Channels" in the content area 73ms

And I follow first "Subscribe to Channels" in the content area 63ms

And I check "My State Channel" in the list 60ms

And I click on "Continue" 562ms

And I click on "Update Channel Rankings" 788ms

Then I should see a "Channel Subscriptions successfully changed for" text 81ms

Scenario:
Salt state details
1s 207ms 7

When I follow the left menu "Configuration > Channels" 113ms

And I follow "My State Channel" 448ms

Then I should see a "1 system subscribed" text 71ms

When I follow "View/Edit 'init.sls' File" 336ms

Then I should see a "Revision 1 of /init.sls from channel My State Channel" text 82ms

And I should see a "File Contents" text 77ms

And I should see a "touch /root/foobar:" text 77ms

Scenario:
Apply the new state
24s 992ms 8

When I am on the Systems overview page of this "sle_minion" 977ms

And I follow "States" in the content area 68ms

And I follow "Configuration Channels" in the content area 63ms

Then I should see a "Execute States" button 299ms

When I click on "Execute States" 52ms

Then I should see a "Applying the config channels has been scheduled" text 465ms

When I wait until event "Apply states [custom] scheduled" is completed 22s 271ms

And I wait until file "/root/foobar" exists on "sle_minion" 792ms

Scenario:
Try to remove init.sls file
1s 507ms 7

When I follow the left menu "Configuration > Channels" 104ms

And I follow "My State Channel" 528ms

And I follow "View/Edit 'init.sls' File" 397ms

When I follow "Delete" 256ms

And I click on "Delete Configuration Revision" 60ms

Then I should see a "Cannot delete the only revision for the init.sls file" text 83ms

And I should see a "Revision 1 of /init.sls from channel My State Channel" text 77ms

Scenario:
Cleanup: remove the state channel and the file
1s 979ms 7

When I follow the left menu "Configuration > Channels" 68ms

And I follow "My State Channel" 497ms

And I follow "Delete Channel" 370ms

Then I should see a "Are you sure you want to delete this config channel?" text 57ms

When I click on "Delete Config Channel" 493ms

Then I should see a "Channel 'My State Channel' has been deleted." text 52ms

And I remove "/root/foobar" from "sle_minion" 439ms

Scenario:
Create the 1st state channel
1s 539ms 12

When I follow the left menu "Configuration > Channels" 61ms

And I follow "Create State Channel" 268ms

Then I should see a "New Config State Channel" text 58ms

When I enter "My State Channel" as "cofName" 71ms

And I enter "statechannel" as "cofLabel" 58ms

And I enter "This is a state channel" as "cofDescription" 69ms

And I enter "touch /root/statechannel:\n cmd.run:\n - creates: /root/statechannel" in the editor 5ms

And I click on "Create Config State Channel" 67ms

Then I should see a "State Channel" text 684ms

And I should see a "Channel Properties" text 65ms

And I should see a "Channel Information" text 63ms

And I should see a "Configuration Actions" text 65ms

Scenario:
Create the 2nd state channel with same name
1s 490ms 12

When I follow the left menu "Configuration > Channels" 64ms

And I follow "Create State Channel" 246ms

Then I should see a "New Config State Channel" text 58ms

When I enter "My State Channel" as "cofName" 62ms

And I enter "statechannel2" as "cofLabel" 56ms

And I enter "This is a state channel" as "cofDescription" 62ms

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" 55ms

Then I should see a "State Channel" text 687ms

And I should see a "Channel Properties" text 66ms

And I should see a "Channel Information" text 66ms

And I should see a "Configuration Actions" text 61ms

Scenario:
Create the 3rd state channel with spacecmd
29s 839ms 9

When I create channel "statechannel3" from spacecmd of type "state" 3s 419ms

And I follow the left menu "Configuration > Channels" 60ms

Then I should see a "statechannel3" text 107ms

When I update init.sls from spacecmd with content "touch /tmp/statechannel3:\n cmd.run:\n - creates: /tmp/statechannel3" for channel "statechannel3" 10s 176ms

And I get "/init.sls" file details for channel "statechannel3" via spacecmd 3s 125ms

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" 9s 853ms

And I get "/init.sls" file details for channel "statechannel3" via spacecmd 3s 96ms

Then I should see "Revision: 100" in the output < 1ms

Scenario:
Subscribe a minion to 1st and 2nd state channels
2s 247ms 15

When I am on the Systems overview page of this "sle_minion" 948ms

And I follow "States" in the content area 72ms

And I follow "Configuration Channels" in the content area 69ms

And I click on "Search" in element "search-row" 73ms

Then I should see a "My State Channel" text 178ms

And I should see a "statechannel" text 69ms

And I should see a "statechannel2" text 67ms

When I check "statechannel-cbox" 86ms

And I check "statechannel2-cbox" 82ms

And I click on "Save Changes" 67ms

And I wait until I see "Edit Channel Ranks" text 62ms

Then I should see a "My State Channel (statechannel)" text 62ms

And I should see a "My State Channel (statechannel2)" text 63ms

When I click on "Confirm" 58ms

Then I should see a "State assignments have been saved." text 285ms

Scenario:
Apply the Configuration channel state
24s 27ms 9

When I follow "States" in the content area 60ms

And I follow "Configuration Channels" in the content area 61ms

And I click on "Search" in element "search-row" 60ms

And I wait until I see "Execute States" text 68ms

And I click on "Execute States" 60ms

Then I should see a "Applying the config channels has been scheduled" text 299ms

And I wait until event "Apply states [custom] scheduled" is completed 22s 142ms

And I wait until file "/root/statechannel" exists on "sle_minion" 826ms

And I wait until file "/root/statechannel2" exists on "sle_minion" 447ms

Scenario:
Subscribe a minion to the 3rd state channel
1s 199ms 12

When I follow "States" in the content area 65ms

And I follow "Configuration Channels" in the content area 57ms

Then I should see a "My State Channel" text 263ms

And I should see a "statechannel3" text 71ms

When I check "statechannel3-cbox" 89ms

And I click on "Save Changes" 66ms

And I wait until I see "Edit Channel Ranks" text 63ms

And I should see a "My State Channel (statechannel)" text 62ms

And I should see a "My State Channel (statechannel2)" text 62ms

And I should see a "statechannel3 (statechannel3)" text 62ms

When I click on "Confirm" 60ms

Then I should see a "State assignments have been saved." text 274ms

Scenario:
Apply the Configuration channel state with spacecmd
16s 291ms 2

When I schedule apply configchannels for "sle_minion" 6s 434ms

And I wait until file "/root/statechannel3" exists on "sle_minion" 9s 856ms

Scenario:
Cleanup: remove the 1st state channel and the deployed file
2s 41ms 7

When I follow the left menu "Configuration > Channels" 124ms

And I follow first "My State Channel" 497ms

And I follow "Delete Channel" 307ms

Then I should see a "Are you sure you want to delete this config channel?" text 59ms

When I click on "Delete Config Channel" 61ms

Then I should see a "Channel 'My State Channel' has been deleted." text 535ms

When I remove "/root/statechannel" from "sle_minion" 454ms

Scenario:
Cleanup: remove the 2nd state channel and the deployed file
1s 880ms 7

When I follow the left menu "Configuration > Channels" 67ms

And I follow first "My State Channel" 434ms

And I follow "Delete Channel" 294ms

Then I should see a "Are you sure you want to delete this config channel?" text 58ms

When I click on "Delete Config Channel" 52ms

Then I should see a "Channel 'My State Channel' has been deleted." text 528ms

When I remove "/root/statechannel2" from "sle_minion" 444ms

Scenario:
Cleanup: remove the 3rd state channel and the deployed file
2s 29ms 7

When I follow the left menu "Configuration > Channels" 65ms

And I follow first "statechannel3" 447ms

And I follow "Delete Channel" 367ms

Then I should see a "Are you sure you want to delete this config channel?" text 58ms

When I click on "Delete Config Channel" 53ms

Then I should see a "Channel 'statechannel3' has been deleted." text 601ms

When I remove "/root/statechannel3" from "sle_minion" 435ms

Feature:Configuration state channels via API 54s 878ms 3

Scenario:
Create a state channel via API
50s 810ms 2 2

When I create state channel "statechannel1" via API 2s 36ms 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 774ms 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:234:in `block in relog_and_visit_previous_url'
./features/support/env.rb:232:in `relog_and_visit_previous_url'
./features/support/env.rb:212:in `handle_screenshot_and_relog'
./features/support/env.rb:173:in `After'
Show Info + 
17:41:21:000 - 17:41:33: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 34ms 1 1

Then I delete channel "statechannel1" via API without error control 2s 34ms 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 41s 861ms 7

Scenario:
Pre-requisite: install milkyway-dummy-1.0 package
3s 888ms 3

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 859ms

And I refresh the metadata for "sle_minion" 971ms

And I install old package "milkyway-dummy-1.0" on this "sle_minion" without error control 2s 58ms

Scenario:
Pre-requisite: refresh package list and check installed packages on SLE minion client
27s 187ms 3

When I refresh packages list via spacecmd on "sle_minion" 8s 878ms

And I wait until refresh package list on "sle_minion" is finished 11s 974ms

Then spacecmd should show packages "milkyway-dummy-1.0" installed on "sle_minion" 6s 335ms

Scenario:
Log in as org admin user
10s 762ms 1

Given I am authorized for the "Admin" section 10s 762ms

Scenario:
Pre-requisite: ensure the errata cache is computed before package list tests
19s 882ms 11

Given I am on the Systems overview page of this "sle_minion" 1s 786ms

When I follow "Software" in the content area 80ms

And I follow "List / Remove" in the content area 66ms

And I enter "milkyway-dummy" as the filtered package name 172ms

And I click on the filter button until page does contain "milkyway-dummy-1.0" text 11s 185ms

And I follow the left menu "Admin > Task Schedules" 124ms

And I follow "errata-cache-default" 1s 204ms

And I follow "errata-cache-bunch" 1s 279ms

And I click on "Single Run Schedule" 1s 546ms

Then I should see a "bunch was scheduled" text 274ms

When I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 2s 159ms

Scenario:
Remove manually a package on a minion
21s 734ms 8

Given I am on the Systems overview page of this "sle_minion" 1s 6ms

When I follow "Software" in the content area 72ms

And I follow "List / Remove" 681ms

And I enter "milkyway-dummy" as the filtered package name 150ms

And I click on the filter button 1s 138ms

Then I should see a "milkyway-dummy" text 72ms

When I remove package "milkyway-dummy" from this "sle_minion" 2s 345ms

And I click on the filter button until page does not contain "milkyway-dummy" text 16s 266ms

Scenario:
Install manually a package on a minion
14s 684ms 7

When I follow "Software" in the content area 74ms

And I follow "List / Remove" 788ms

And I enter "milkyway-dummy" as the filtered package name 166ms

And I click on the filter button 841ms

Then I should not see a "milkyway-dummy" text 66ms

When I install package "milkyway-dummy" on this "sle_minion" 2s 644ms

And I click on the filter button until page does not contain "milkyway-dummy" text 10s 101ms

Scenario:
Cleanup: remove milkyway-dummy packages from SLES minion
3s 722ms 3

When I disable repository "test_repo_rpm_pool" on this "sle_minion" 866ms

And I remove package "milkyway-dummy" from this "sle_minion" without error control 1s 987ms

And I refresh the metadata for "sle_minion" 868ms

@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 884ms 4

Scenario:
Log in as org admin user
436ms 1

Given I am authorized 436ms

Scenario:
Check perseus-dummy-7891 patches
1s 393ms 7

When I follow the left menu "Patches > Patch List > All" 199ms

And I enter "dummy" as the filtered synopsis 127ms

And I click on the filter button 566ms

And I follow "perseus-dummy-7891" 378ms

Then I should see a "perseus-dummy-7891 - Security Advisory" text 74ms

And I should see a "CVE-1999-12345" link 34ms

And I should see a "CVE-1999-99781" link 12ms

Scenario:
Check local metadata for long CVE IDs
4s 976ms 5

When I refresh the metadata for "sle_minion" 1s 265ms

Then I should have 'reference.*id="CVE-1999-12345' in the patch metadata for "sle_minion" 926ms

And I should have 'reference.*id="CVE-1999-99781' in the patch metadata for "sle_minion" 972ms

And I should have 'reference.*http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-1999-12345' in the patch metadata for "sle_minion" 908ms

And I should have 'reference.*http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-1999-99781' in the patch metadata for "sle_minion" 902ms

Scenario:
Search for CVE ID with the new format
1s 77ms 5

When I follow the left menu "Patches > Advanced Search" 65ms

When I enter "CVE-1999-12345" as "search_string" in the content area 80ms

And I click on "Search" 820ms

Then I should see a "Advanced Search" text 89ms

And I should see a "perseus-dummy-7891" link in the content area 22ms

@scope_onboarding
Feature:Display patches 1m 43s 105ms 8

Scenario:
Log in as org admin user
492ms 1

Given I am authorized for the "Admin" section 492ms

Scenario:
Pre-require: enable old packages to fake a possible installation
12s 522ms 10

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 875ms

And I refresh the metadata for "sle_minion" 900ms

And I install old package "andromeda-dummy-1.0" on this "sle_minion" 2s 47ms

And I install old package "virgo-dummy-1.0" on this "sle_minion" 2s 86ms

When I follow the left menu "Admin > Task Schedules" 125ms

And I follow "errata-cache-default" 1s 212ms

And I follow "errata-cache-bunch" 1s 294ms

And I click on "Single Run Schedule" 1s 559ms

Then I should see a "bunch was scheduled" text 280ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 2s 140ms

Scenario:
Check all patches exist
59s 297ms 8

When I follow the left menu "Patches > Patch List > Relevant" 206ms

Then I should see an update in the list 76ms

When I wait until I see "andromeda-dummy" text, refreshing the page 58s 267ms

Then I should see a "andromeda-dummy-6789" link 21ms

When I enter "virgo-dummy" as the filtered synopsis 134ms

And I click on the filter button 511ms

And I wait until I see "virgo-dummy" text 68ms

Then I should see a "virgo-dummy-3456" link 11ms

Scenario:
Check SLES release 6789 patches
921ms 6

When I follow the left menu "Patches > Patch List > Relevant" 85ms

And I follow "andromeda-dummy-6789" 616ms

Then I should see a "andromeda-dummy-6789 - Bug Fix Advisory" text 69ms

And I should see a "Test update for andromeda-dummy" text 66ms

And I should see a "Fake-RPM-SUSE-Channel" link 12ms

And I should see a "reboot_suggested" text 69ms

Scenario:
Check packages of SLES release 6789 patches
1s 207ms 6

When I follow the left menu "Patches > Patch List > Relevant" 70ms

And I follow "andromeda-dummy-6789" 345ms

And I follow "Packages" 696ms

Then I should see a "Fake-RPM-SUSE-Channel" link 9ms

And I should see a "sha512:19940cc4a9f0d38a038a4455b0f1cf1290c4a4296b27f5a62f4aae60585ac6e2677e88c3c3127d487116ed8d9b1787379e23aafac46bc14408864926bedee693" text 59ms

And I should see a "andromeda-dummy-2.0-1.1-noarch" link 25ms

Scenario:
Check relevant patches for this client
11s 822ms 8

Given I am on the Systems overview page of this "sle_minion" 1s 266ms

When I follow "Software" in the content area 80ms

And I follow "Patches" in the content area 67ms

Then I should see a "Relevant Patches" text 84ms

When I enter "dummy" as the filtered synopsis 46ms

And I click on the filter button 10s 126ms

Then I should see a "Test update for andromeda-dummy" text 76ms

And I should see a "Test update for virgo-dummy" text 75ms

Scenario:
Cleanup: regenerate search index for later tests
11s 60ms 1

Search by hostname: uyuni-master-suse-minion
[{"last_boot"=>"2026-04-22T12:06:01Z", "name"=>"uyuni-master-suse-minion.sumaci.aws", "id"=>1000010023, "last_checkin"=>"2026-04-22T15:46:17Z"}]

When I clean the search index on the server 11s 60ms

Scenario:
Cleanup: remove old packages
5s 781ms 4

When I disable repository "test_repo_rpm_pool" on this "sle_minion" without error control 893ms

And I refresh the metadata for "sle_minion" 1s 19ms

And I remove package "andromeda-dummy" from this "sle_minion" without error control 1s 912ms

And I remove package "virgo-dummy" from this "sle_minion" without error control 1s 955ms

@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

@test_issue
Feature:Debug the server after the testsuite has run 55s 867ms 4 1

* Related GitHub Card: https://github.com/SUSE/spacewalk/issues/25872

Scenario:
Call spacewalk-debug on server
39s 671ms 1

When I execute spacewalk-debug on the server 39s 671ms

Scenario:
Check the tomcat logs on server
3s 141ms 1

Then the tomcat logs should not contain errors 3s 141ms

Scenario:
Check salt event log for failures on server
7s 297ms 1

Then the salt event log on server should contain no failures 7s 297ms Show Error + 
                                            
 
Found 21 failures in salt event log:

# Failure 2 , _stamp: 2026-04-22T14:12:23.310843 {
    "__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": 14150.198,
    "name": "docker.build",
    "result": false,
    "start_time": "16:12:09.092607"
}

# Failure 3 , _stamp: 2026-04-22T14:12:23.310843 {
    "__id__": "mgr_pushimage",
    "__run_num__": 2,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "One or more requisite failed: images.docker.mgr_buildimage",
    "duration": 0.007,
    "name": "docker.push",
    "result": false,
    "start_time": "16:12:23.243373"
}

# Failure 4 , _stamp: 2026-04-22T14:12:23.310843 {
    "__id__": "mgr_registries_logout",
    "__run_num__": 3,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "One or more requisite failed: images.docker.mgr_pushimage",
    "duration": 0.004,
    "name": "docker.logout",
    "result": false,
    "start_time": "16:12:23.243914"
}

# Failure 5 , _stamp: 2026-04-22T14:13:47.669693 {
    "__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": 13699.674,
    "name": "docker.build",
    "result": false,
    "start_time": "16:13:33.940174"
}

# Failure 6 , _stamp: 2026-04-22T14:13:47.669693 {
    "__id__": "mgr_pushimage",
    "__run_num__": 2,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "One or more requisite failed: images.docker.mgr_buildimage",
    "duration": 0.005,
    "name": "docker.push",
    "result": false,
    "start_time": "16:13:47.640329"
}

# Failure 7 , _stamp: 2026-04-22T14:13:47.669693 {
    "__id__": "mgr_registries_logout",
    "__run_num__": 3,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "One or more requisite failed: images.docker.mgr_pushimage",
    "duration": 0.004,
    "name": "docker.logout",
    "result": false,
    "start_time": "16:13:47.640684"
}

# Failure 8 , _stamp: 2026-04-22T14:20:14.861042 {
    "__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": 13806.249,
    "name": "docker.build",
    "result": false,
    "start_time": "16:20:01.020186"
}

# Failure 9 , _stamp: 2026-04-22T14:20:14.861042 {
    "__id__": "mgr_pushimage",
    "__run_num__": 2,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "One or more requisite failed: images.docker.mgr_buildimage",
    "duration": 0.005,
    "name": "docker.push",
    "result": false,
    "start_time": "16:20:14.826927"
}

# Failure 10 , _stamp: 2026-04-22T14:20:14.861042 {
    "__id__": "mgr_registries_logout",
    "__run_num__": 3,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "One or more requisite failed: images.docker.mgr_pushimage",
    "duration": 0.004,
    "name": "docker.logout",
    "result": false,
    "start_time": "16:20:14.827206"
}

# Failure 11 , _stamp: 2026-04-22T14:21:18.163955 {
    "__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": 13755.155,
    "name": "docker.build",
    "result": false,
    "start_time": "16:21:04.375259"
}

# Failure 12 , _stamp: 2026-04-22T14:21:18.163955 {
    "__id__": "mgr_pushimage",
    "__run_num__": 2,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "One or more requisite failed: images.docker.mgr_buildimage",
    "duration": 0.005,
    "name": "docker.push",
    "result": false,
    "start_time": "16:21:18.130924"
}

# Failure 13 , _stamp: 2026-04-22T14:21:18.163955 {
    "__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": "16:21:18.131209"
}

# Failure 14 , _stamp: 2026-04-22T14:22:27.906481 {
    "__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": 14299.89,
    "name": "docker.build",
    "result": false,
    "start_time": "16:22:13.571180"
}

# Failure 15 , _stamp: 2026-04-22T14:22:27.906481 {
    "__id__": "mgr_pushimage",
    "__run_num__": 2,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "One or more requisite failed: images.docker.mgr_buildimage",
    "duration": 0.007,
    "name": "docker.push",
    "result": false,
    "start_time": "16:22:27.871831"
}

# Failure 16 , _stamp: 2026-04-22T14:22:27.906481 {
    "__id__": "mgr_registries_logout",
    "__run_num__": 3,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "One or more requisite failed: images.docker.mgr_pushimage",
    "duration": 0.006,
    "name": "docker.logout",
    "result": false,
    "start_time": "16:22:27.872163"
}

# Failure 17 , _stamp: 2026-04-22T14:23:30.925618 {
    "__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": 14179.894,
    "name": "docker.build",
    "result": false,
    "start_time": "16:23:16.706170"
}

# Failure 18 , _stamp: 2026-04-22T14:23:30.925618 {
    "__id__": "mgr_pushimage",
    "__run_num__": 2,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "One or more requisite failed: images.docker.mgr_buildimage",
    "duration": 0.006,
    "name": "docker.push",
    "result": false,
    "start_time": "16:23:30.886642"
}

# Failure 19 , _stamp: 2026-04-22T14:23:30.925618 {
    "__id__": "mgr_registries_logout",
    "__run_num__": 3,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "One or more requisite failed: images.docker.mgr_pushimage",
    "duration": 0.004,
    "name": "docker.logout",
    "result": false,
    "start_time": "16:23:30.886939"
}

# Failure 20 , _stamp: 2026-04-22T14:32:53.422263 {
    "__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": 14467.372,
    "name": "docker.build",
    "result": false,
    "start_time": "16:32:38.920122"
}

# Failure 21 , _stamp: 2026-04-22T14:32:53.422263 {
    "__id__": "mgr_pushimage",
    "__run_num__": 2,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "One or more requisite failed: images.docker.mgr_buildimage",
    "duration": 0.006,
    "name": "docker.push",
    "result": false,
    "start_time": "16:32:53.388001"
}

# Failure 22 , _stamp: 2026-04-22T14:32:53.422263 {
    "__id__": "mgr_registries_logout",
    "__run_num__": 3,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "One or more requisite failed: images.docker.mgr_pushimage",
    "duration": 0.005,
    "name": "docker.logout",
    "result": false,
    "start_time": "16:32:53.388542"
}

 (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
3s 162ms 1

Then the taskomatic logs should not contain errors 3s 162ms

Scenario:
Check for out of memory errors
2s 594ms 1

Then the log messages should not contain out of memory errors 2s 594ms

Feature:Debug the clients after the testsuite has run 2m 55s 576ms 1

Scenario:
Extract the logs from all our clients
2m 55s 576ms 1

When I extract the log files from all our active nodes 2m 55s 576ms

@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