All Scenarios

1517

Passed Scenarios

1258

Failed Scenarios

42

Skipped Scenarios

217

Execution Time: 392m 18s 411ms

Expand All | Collapse All

Metadata

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

Feature:Sanity checks 44s 362ms 10 2

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

Scenario:
The server is healthy
11s 797ms 19

Then "server" should have a FQDN 384ms

And reverse resolution should work for "server" 616ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

And reverse resolution should work for "proxy" 345ms

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

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

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

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

And reverse resolution should work for "sle_minion" 453ms

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

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

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

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

And reverse resolution should work for "build_host" 318ms

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

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

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

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

And reverse resolution should work for "ssh_minion" 475ms

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

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

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

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

And reverse resolution should work for "rhlike_minion" 184ms

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

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

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

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

And reverse resolution should work for "deblike_minion" 215ms

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

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

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

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

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

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

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

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

Feature:Very first settings 50s 599ms 6 2

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

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

@skip_if_containerized_server
Scenario:
Create admin user and first organization
< 1ms 12

Given I access the host the first time 0s

When I go to the home page 0s

And I enter "SUSE Test" as "orgName" 0s

And I enter "admin" as "login" 0s

And I enter "admin" as "desiredpassword" 0s

And I enter "admin" as "desiredpasswordConfirm" 0s

And I select "Mr." from "prefix" 0s

And I enter "Admin" as "firstNames" 0s

And I enter "Admin" as "lastName" 0s

And I enter "galaxy-noise@localhost" as "email" 0s

And I click on "Create Organization" 0s

Then I am logged in 0s

Scenario:
Log in as admin user
41s 783ms 1

Given I am authorized for the "Admin" section 41s 783ms

Scenario:
Wait for refresh of list of products to finish
3s 247ms 1

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

Scenario:
Create testing username
2s 385ms 12

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

And I follow "Create User" 701ms

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

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

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

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

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

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

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

And I click on "Create Login" 965ms

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

And I should see a "testing" link 11ms

Scenario:
Grant testing user administrative priviledges
1s 784ms 10

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

And I follow "testing" 547ms

And I check "role_org_admin" 79ms

And I check "role_system_group_admin" 72ms

And I check "role_channel_admin" 72ms

And I check "role_activation_key_admin" 73ms

And I check "role_config_admin" 72ms

And I click on "Update" 639ms

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

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

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

* Wed Jan 14 2026 Marek Czernek
- Use internal deb classes instead of external aptsource lib
- Speed up wheel key.finger call (bsc#1240532)
- Add security patches (bsc#1254903,bsc#1254905,bsc#1254904)
- Simplify and speed up utils.find_json function (bsc#1246130)
- Added:
* use-internal-salt.utils.pkg.deb-classes-instead-of-a.patch
* speedup-wheel-key.finger-call-bsc-1240532-713.patch

When I query latest Salt changes on "server" 755ms

Feature:Turn "disable_local_repos" feature on highstate off 3s 704ms 1

In order to test the product using shortcuts
As root user
I want to add pillar data to disable that feature

Scenario:
Create custom pillar to turn off "disable_local_repos"
3s 704ms 1

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

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

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

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

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

And I ask to add new credentials 0s

And I enter the SCC credentials 0s

And I click on "Save" 0s

And I wait until the SCC credentials are valid 0s

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

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

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

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

And I click on "Save Preferences" 640ms

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

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

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

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

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

And I click on "Save Preferences" 624ms

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

Feature:Prepare server for using Kiwi 4s 325ms 1

Scenario:
Create a Kiwi user with image administrators rights
4s 325ms 2

New user kiwikiwi created with roles: image_admin

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

When I create a user with name "kiwikiwi" and password "kiwikiwi" with roles "image_admin" 1s 873ms

Feature:Prepare server for using Docker 5s 18ms 2

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

New user docker created with roles: image_admin

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

When I create a user with name "docker" and password "docker" with roles "image_admin" 1s 618ms

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

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

And I follow "Create" 471ms

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

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

And I click on "create-btn" 56ms

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

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

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

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

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

Scenario:
Disable scheduled reposyncs
4s 501ms 5

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

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

And I choose "disabled" 62ms

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

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

Scenario:
Disable scheduled Cobbler syncs
4s 664ms 5

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

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

And I choose "disabled" 44ms

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

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

@scc_credentials
Feature:List available channels and enable them 1m 39s 256ms 5 1

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

Scenario:
List available channels
33s 353ms 5

When I refresh SCC 31s 78ms

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

Then I should get "[ ] SLE-Product-SLES15-SP7-Pool for x86_64 SUSE Linux Enterprise Server 15 SP7 x86_64 [sle-product-sles15-sp7-pool-x86_64]" < 1ms

And I should get " [ ] SLE-Product-SLES15-SP7-Updates for x86_64 SUSE Linux Enterprise Server 15 SP7 x86_64 [sle-product-sles15-sp7-updates-x86_64]" < 1ms

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

Scenario:
List available mandatory channels
1s 503ms 4

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

Then I should get "[ ] SLE-Product-SLES15-SP7-Pool for x86_64 SUSE Linux Enterprise Server 15 SP7 x86_64 [sle-product-sles15-sp7-pool-x86_64]" < 1ms

And I should get " [ ] SLE-Product-SLES15-SP7-Updates for x86_64 SUSE Linux Enterprise Server 15 SP7 x86_64 [sle-product-sles15-sp7-updates-x86_64]" < 1ms

And I shouldn't get " [ ] SLE15-SP7-Installer-Updates for x86_64 SUSE Linux Enterprise Server 15 SP7 x86_64 [sle15-sp7-installer-updates-x86_64]" < 1ms

Scenario:
List Server product
1s 444ms 2

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

Then I should get "[ ] SUSE Linux Enterprise Server 15 SP7 x86_64" < 1ms

@proxy @susemanager
Scenario:
List all products for SUSE Multi-Linux Manager
< 1ms 6

When I execute mgr-sync "list products --expand" 0s

Then I should get "[ ] SUSE Linux Enterprise Server 15 SP7 x86_64" 0s

And I should get " [ ] SUSE Multi-Linux Manager Proxy Extension 5.1 x86_64" 0s

And I should get " [ ] SUSE Multi-Linux Manager Proxy Extension for SLE 5.1 x86_64" 0s

And I should get " [ ] (R) SUSE Multi-Linux Manager Client Tools for SUSE Liberty Linux 7, RHEL and clones 7 x86_64" 0s

And I should get " [ ] (R) SUSE Multi-Linux Manager Client Tools for SLE 15 x86_64" 0s

Scenario:
List products with filter
1s 514ms 4

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

Then I should get "[ ] SUSE Linux Enterprise Server 15 SP7 x86_64" < 1ms

And I shouldn't get "ppc64" < 1ms

And I shouldn't get "s390x" < 1ms

Scenario:
Let mgr-sync time out
1m 1s 440ms 3

When I remove the mgr-sync cache file 666ms

And I execute mgr-sync refresh 1m 774ms

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

Feature:Synchronize products in the products page of the Setup Wizard 45m 28s 125ms 8 9

@scc_credentials
Scenario:
Refresh SCC
27s 832ms 1

When I refresh SCC 27s 832ms

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

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

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

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

Then I should see a "Arch" text 122ms

And I should see a "Channels" text 124ms

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

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

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

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

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

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

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

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

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

@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
1m 58s 649ms 4

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

When I use spacewalk-common-channel to add channel "opensuse_tumbleweed" with arch "x86_64" 7s 650ms

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

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

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

@containerized_server @proxy @uyuni
Scenario:
Add Uyuni Proxy product for Tumbleweed, including Uyuni Client Tools
55s 631ms 2

Channel opensuse_tumbleweed-x86_64 added
Channel opensuse_tumbleweed-uyuni-client-devel-x86_64 added
Channel uyuni-proxy-devel-tumbleweed-x86_64 added
Channel opensuse_tumbleweed-x86_64 finished reposync
Channel opensuse_tumbleweed-uyuni-client-devel-x86_64 finished reposync
Channel uyuni-proxy-devel-tumbleweed-x86_64 finished reposync
All channels for uyuni-proxy have been fully synced

When I use spacewalk-common-channel to add all "uyuni-proxy" channels with arch "x86_64" 21s 539ms

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

@scc_credentials @uyuni @build_host
Scenario:
Synchronize SLES 15 SP7 product with recommended sub-products for Retail feature
41m 17s 90ms 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]
Channel sle-product-sles15-sp7-pool-x86_64 finished reposync
Channel sles15-sp7-devel-uyuni-client-x86_64 finished reposync
1 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-product-sles15-sp7-updates-x86_64 finished reposync
Channel sle15-sp7-installer-updates-x86_64 finished reposync
2 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
3 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
4 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
5 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-basesystem15-sp7-pool-x86_64 finished reposync
6 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
7 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
8 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
9 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
10 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
11 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-basesystem15-sp7-updates-x86_64 finished reposync
12 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-server-applications15-sp7-pool-x86_64 finished reposync
Channel sle-module-server-applications15-sp7-updates-x86_64 finished reposync
13 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-python3-15-sp7-updates-x86_64 finished reposync
Channel sle-module-python3-15-sp7-pool-x86_64 finished reposync
Channel sle-module-systems-management-15-sp7-updates-x86_64 finished reposync
14 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-systems-management-15-sp7-pool-x86_64 finished reposync
15 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
16 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
17 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
18 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-desktop-applications15-sp7-updates-x86_64 finished reposync
19 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
20 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-desktop-applications15-sp7-pool-x86_64 finished reposync
21 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
22 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
23 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
24 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
25 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
26 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
27 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
28 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-devtools15-sp7-updates-x86_64 finished reposync
29 minutes out of 102 waiting for 'sles15-sp7' channels to finish reposync
Channel sle-module-devtools15-sp7-pool-x86_64 finished reposync
All channels for sles15-sp7 have been fully synced

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 53ms

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

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

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

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

And I wait until all synchronized channels for "sles15-sp7" have finished 40m 55s 977ms

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

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

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

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

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

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

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

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

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

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

And I click the Add Product button 0s

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

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

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

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

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

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

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

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

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

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

When I click the Add Product button 0s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Feature:Create fake channels 24s 931ms 11 1

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

Scenario:
Log in as admin user
489ms 1

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

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

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

And I follow "Create Channel" 328ms

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

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

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

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

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

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

And I click on "Create Channel" 608ms

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

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

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

And I follow "Create Channel" 315ms

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

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

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

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

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

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

And I click on "Create Channel" 58ms

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

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

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

And I follow "Create Channel" 320ms

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

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

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

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

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

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

And I click on "Create Channel" 610ms

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

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

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

And I follow "Create Channel" 320ms

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

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

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

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

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

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

And I click on "Create Channel" 57ms

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

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

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

And I follow "Create Channel" 326ms

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

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

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

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

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

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

And I click on "Create Channel" 589ms

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

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

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

And I follow "Create Channel" 325ms

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

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

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

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

And I click on "Create Channel" 532ms

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

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

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

And I follow "Create Channel" 260ms

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

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

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

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

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

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

And I click on "Create Channel" 564ms

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

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

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

And I follow "Create Channel" 248ms

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

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

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

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

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

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

And I uncheck "gpg_check" 10s 100ms

And I click on "Create Channel" 518ms

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

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

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

And I follow "Create Channel" 253ms

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

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

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

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

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

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

And I click on "Create Channel" 507ms

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

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

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

And I follow "Create Channel" 292ms

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

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

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

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

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

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

And I click on "Create Channel" 57ms

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

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

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

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

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

And I follow "Create Repository" 313ms

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

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

And I click on "Create Repository" 61ms

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

And I should see "metadataSigned" as checked 20ms

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

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

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

And I uncheck "metadataSigned" 10s 73ms

And I click on "Update Repository" 454ms

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

And I should see "metadataSigned" as unchecked 16ms

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

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

And I follow "Create Repository" 241ms

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

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

And I click on "Create Repository" 428ms

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

And I should see "metadataSigned" as checked 16ms

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

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

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

And I uncheck "metadataSigned" 10s 54ms

And I click on "Update Repository" 427ms

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

And I should see "metadataSigned" as unchecked 15ms

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

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

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

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

And I click on "Update Channel" 624ms

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

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

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

And I click on "Save Repositories" 654ms

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

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

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

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

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

And I click on "Update Channel" 631ms

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

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

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

And I click on "Save Repositories" 899ms

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

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

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

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

And I click on "Update Channel" 56ms

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

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

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

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

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

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

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

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

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

And I click on "Update Channel" 554ms

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

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

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

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

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

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

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

And I follow "Create Repository" 238ms

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

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

And I uncheck "metadataSigned" 10s 80ms

And I click on "Create Repository" 439ms

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

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

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

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

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

And I click on "Update Channel" 493ms

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

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

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

And I click on "Save Repositories" 507ms

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

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

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

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

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

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

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

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

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

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

And I follow "Create Repository" 327ms

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

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

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

And I click on "Create Repository" 417ms

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

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

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

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

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

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

And I click on "Save Repositories" 755ms

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

@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 27s 974ms 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
524ms 1

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

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

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

And I follow "Create Channel" 286ms

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

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

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

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

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

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

And I click on "Create Channel" 572ms

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

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

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

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

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

And I follow "Create Channel" 268ms

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

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

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

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

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

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

And I click on "Create Channel" 60ms

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

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

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

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

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

And I follow "Create Channel" 371ms

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

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

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

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

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

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

And I click on "Create Channel" 557ms

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

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

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

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

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

And I follow "Create Channel" 274ms

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

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

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

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

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

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

And I click on "Create Channel" 59ms

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

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

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

Feature:Synchronize fake channels 1m 17s 690ms 12 2

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

Scenario:
Log in as admin user
1s 928ms 2

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

And I enable source package syncing 1s 496ms

@sle_minion
Scenario:
Synchronize Fake-RPM-SUSE-Channel channel
3s 890ms 9

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

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

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

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

And I follow "Sync" 437ms

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

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

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

And I wait until the channel "fake-rpm-suse-channel" has been synced 497ms

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

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

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

@skip_if_github_validation
Scenario:
Synchronize Fake-Child-Channel-i586 channel
3s 645ms 9

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

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

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

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

And I follow "Sync" 350ms

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

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

And I wait until the channel "fake-child-channel-i586" has been synced 399ms

Scenario:
Synchronize Test-Child-Channel-x86_64 channel
4s 161ms 9

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

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

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

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

And I follow "Sync" 698ms

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

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

And I wait until the channel "test-child-channel-x86_64" has been synced 385ms

@sle_minion
Scenario:
Synchronize Fake-Child-Channel-SUSE-like channel
35s 464ms 9

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

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

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

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

And I follow "Sync" 779ms

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

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

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

@deblike_minion
Scenario:
Synchronize Fake-Base-Channel-Debian-like channel
3s 692ms 9

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

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

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

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

And I follow "Sync" 349ms

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

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

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

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

@rhlike_minion
Scenario:
Synchronize Fake-Base-Channel-RH-like channel
4s 212ms 9

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

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

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

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

And I follow "Sync" 803ms

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

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

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

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

@rhlike_minion
Scenario:
Synchronize Fake-Base-Channel-AppStream channel
4s 10ms 9

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

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

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

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

And I follow "Sync" 437ms

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

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

And I wait until the channel "fake-base-channel-appstream" has been synced 445ms

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

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

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

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

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

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

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

Scenario:
Refresh the channel's repository data
4s 9ms 6

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

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

And I follow "channel-repodata-bunch" 274ms

And I click on "Single Run Schedule" 310ms

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

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

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

Then I disable source package syncing 1s 1ms

@skip_if_github_validation
Feature:Synchronize development channels 16s 697ms 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
3s 939ms 9

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

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

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

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

And I follow "Sync" 522ms

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

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

And I wait until the channel "devel-suse-channel" has been synced 369ms

@deblike_minion
Scenario:
Synchronize Devel-Debian-like-Channel channel
4s 141ms 9

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

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

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

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

And I follow "Sync" 615ms

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

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

And I wait until the channel "devel-debian-like-channel" has been synced 404ms

@rhlike_minion
Scenario:
Synchronize Devel-RH-like-Channel channel
4s 274ms 9

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

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

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

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

And I follow "Sync" 882ms

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

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

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

And I wait until the channel "devel-rh-like-channel" has been synced 380ms

@build_host @uyuni
Scenario:
Synchronize Devel-Build-Host-Channel channel
4s 343ms 9

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

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

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

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

And I follow "Sync" 861ms

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

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

Feature:Create activation keys 18s 300ms 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
699ms 1

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

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

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

@rhlike_minion
Scenario:
Create an activation key for RedHat-like minion
3s 32ms 2

When I create an activation key with id "RH-LIKE-KEY", description "RedHat like Test Key", base channel "fake-base-channel-rh-like", limit of 20 and contact method "default" 1s 870ms

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

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

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

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

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

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

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

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

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

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

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

@build_host
Scenario:
Create an activation key for the build host
2s 591ms 3

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

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

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

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

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

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

Feature:Update activation keys 23s 636ms 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
487ms 1

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 628ms

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

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

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

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

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

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

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

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

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

And I click on "Update Activation Key" 0s

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 629ms

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

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

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

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

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

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

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

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

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

And I click on "Update Activation Key" 0s

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 614ms

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

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

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

And I wait until "ManagerTools-SL-Micro-6.1 for x86_64" has been checked 0s

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

And I check "SUSE-Multi-Linux-Manager-Retail-Branch-Server-5.1 for x86_64" 0s

And I click on "Update Activation Key" 0s

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

@scc_credentials @susemanager @proxy @containerized_server @skip_if_transactional_server
Scenario:
Update the SLES proxy key with synced base product
< 1ms 11

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

And I wait until "ManagerTools-SLE15-Pool for x86_64 SP7" has been checked 0s

And I check "SUSE-Manager-Proxy-5.1-Pool for x86_64" 0s

And I check "SUSE-Manager-Proxy-5.1-Updates for x86_64" 0s

And I click on "Update Activation Key" 0s

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

@uyuni @proxy @containerized_server @skip_if_cloud
Scenario:
Update the openSUSE Tumbleweed Proxy Host key with synced base product
< 1ms 8

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

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

And I wait for child channels to appear 0s

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

And I wait for child channels to appear 0s

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 0s

And I click on "Update Activation Key" 0s

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

@scc_credentials @build_host
Scenario:
Update build host key with synced base product
3s 446ms 20

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

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

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

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

And I wait for child channels to appear 547ms

And I include the recommended child channels 176ms

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

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

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

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 724ms

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

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

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

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

And I wait for child channels to appear 958ms

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

And I wait for child channels to appear 314ms

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

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

And I click on "Update Activation Key" 57ms

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

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

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

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

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

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 "Devel-Build-Host-Channel" 83ms

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

And I click on "Update Activation Key" 577ms

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

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

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

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

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

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

And I wait for child channels to appear 435ms

And I include the recommended child channels 178ms

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

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

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

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

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

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

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

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

And I click on "Update Activation Key" 569ms

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

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

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

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

And I wait for child channels to appear 0s

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

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

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

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

And I click on "Update Activation Key" 0s

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

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

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

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

And I wait for child channels to appear 0s

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

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

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

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

And I click on "Update Activation Key" 0s

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

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

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

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

And I wait for child channels to appear 917ms

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

And I click on "Update Activation Key" 559ms

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

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

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

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

And I wait for child channels to appear 926ms

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

And I click on "Update Activation Key" 584ms

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

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

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

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

And I wait for child channels to appear 928ms

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

And I click on "Update Activation Key" 604ms

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

Feature:Create bootstrap repositories 8s 948ms 4

In order to be able to enroll clients with MU repositories
As the system administrator
I create all bootstrap repos with --with-custom-channels option

Scenario:
Create the bootstrap repositories including custom channels
2s 251ms 1

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

@sle_minion
Scenario:
Create the bootstrap repository for SUSE Minion
2s 233ms 1

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

When I create the bootstrap repository for "sle_minion" on the server 2s 233ms

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

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

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

@build_host
Scenario:
Create the bootstrap repository for Build Host
2s 294ms 1

base_channel: SLE-Product-SLES15-SP7-Pool for x86_64
channel: SLE-15-SP7-x86_64
parent_channel: sle-product-sles15-sp7-pool-x86_64
Creating the bootstrap repository on the server:
mgr-create-bootstrap-repo --create SLE-15-SP7-x86_64 --with-parent-channel sle-product-sles15-sp7-pool-x86_64 --with-custom-channels

When I create the bootstrap repository for "build_host" on the server 2s 294ms

@containerized_server @scope_containerized_proxy @proxy
Feature:Setup containerized proxy 3m 30s 508ms 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 412ms 1

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

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

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

Scenario:
Bootstrap the proxy host as a salt minion
34s 977ms 9

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 62ms

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

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

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

Scenario:
Generate containerized proxy configuration
14s 213ms 2

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

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

Scenario:
Set up the containerized proxy service to support Avahi
< 1ms 1

Record not added - avahi domain was not detected

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

Scenario:
Run a containerized proxy
17s 259ms 1

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

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

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

And I wait until "uyuni-proxy-httpd" service is active on "proxy" 2s 760ms

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

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

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

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

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

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

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

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

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

When I follow the left menu "Systems" 61ms

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

Scenario:
Check if Monitoring can be enabled on the containerized proxy
10s 986ms 3

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

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

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

@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 12s 789ms 7

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

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

Scenario:
Bootstrap a Debian-like minion
2m 15s 230ms 14

The hostname of deblike_minion is uyuni-master-deblike-minion.sumaci.aws
* Mon Jan 19 2026 Marek Czernek
- Make syntax in httputil_test compatible with Python 3.6
- Fix KeyError in postgres module with PostgreSQL 17 (bsc#1254325)
- Added:
* fix-tornado-s-httputil_test-syntax-for-python-3.6.patch
* backport-add-maintain-m-privilege-to-postgres-module.patch
* Wed Jan 14 2026 Marek Czernek
- Use internal deb classes instead of external aptsource lib
* Drop dependency on saltbundlepy-apt
- Speed up wheel key.finger call (bsc#1240532)
- Add security patches (bsc#1254903,bsc#1254905,bsc#1254904)
- Simplify and speed up utils.find_json function (bsc#1246130)
- Added:
* use-internal-salt.utils.pkg.deb-classes-instead-of-a.patch
* speedup-wheel-key.finger-call-bsc-1240532-713.patch

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 97ms

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

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

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

And I wait until onboarding is completed for "deblike_minion" 44s 369ms

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

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

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

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

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

Then I should see "proxy" short hostname 89ms

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

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

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

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

Then I should see "deblike_minion" hostname 146ms

Scenario:
Subscribe the Debian-like minion to a base channel
23s 894ms 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 610ms

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

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

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

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

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

And I click on "Next" 89ms

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

When I click on "Confirm" 74ms

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

And I wait until event "Subscribe channels scheduled by admin" is completed 19s 866ms

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

* Mon Jan 19 2026 Marek Czernek
- Make syntax in httputil_test compatible with Python 3.6
- Fix KeyError in postgres module with PostgreSQL 17 (bsc#1254325)
- Added:
* fix-tornado-s-httputil_test-syntax-for-python-3.6.patch
* backport-add-maintain-m-privilege-to-postgres-module.patch
* Wed Jan 14 2026 Marek Czernek
- Use internal deb classes instead of external aptsource lib
* Drop dependency on saltbundlepy-apt
- Speed up wheel key.finger call (bsc#1240532)
- Add security patches (bsc#1254903,bsc#1254905,bsc#1254904)
- Simplify and speed up utils.find_json function (bsc#1246130)
- Added:
* use-internal-salt.utils.pkg.deb-classes-instead-of-a.patch
* speedup-wheel-key.finger-call-bsc-1240532-713.patch

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

Scenario:
Check events history for failures on Debian-like minion
51s 897ms 2

Given I am on the Systems overview page of this "deblike_minion" 865ms

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

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

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

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

Scenario:
Bootstrap a Red Hat-like minion
2m 6s 787ms 13

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

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

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

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

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

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

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

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

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

And I click on "Bootstrap" 74ms

And I wait until I see "Bootstrap process initiated." text 32s 283ms

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

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

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

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

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

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

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

Then I should see "proxy" short hostname 134ms

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

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

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

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

Then I should see "rhlike_minion" hostname 109ms

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

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

Given I am on the Systems overview page of this "rhlike_minion" 991ms

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

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

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

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

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

And I click on "Next" 111ms

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

When I click on "Confirm" 113ms

Then I should see a "Changing the channels has been scheduled." text 451ms

And I wait until event "Subscribe channels scheduled by admin" is completed 20s 242ms

Scenario:
Detect latest Salt changes on the Red Hat-like minion
319ms 1

* Mon Jan 19 2026 Marek Czernek
- Make syntax in httputil_test compatible with Python 3.6
- Fix KeyError in postgres module with PostgreSQL 17 (bsc#1254325)
- Added:
* fix-tornado-s-httputil_test-syntax-for-python-3.6.patch
* backport-add-maintain-m-privilege-to-postgres-module.patch

* Wed Jan 14 2026 Marek Czernek
- Use internal deb classes instead of external aptsource lib
* Drop dependency on saltbundlepy-apt
- Speed up wheel key.finger call (bsc#1240532)
- Add security patches (bsc#1254903,bsc#1254905,bsc#1254904)
- Simplify and speed up utils.find_json function (bsc#1246130)
- Added:
* use-internal-salt.utils.pkg.deb-classes-instead-of-a.patch

When I query latest Salt changes on "rhlike_minion" 319ms

Scenario:
Check events history for failures on Red Hat-like minion
52s 778ms 2

Given I am on the Systems overview page of this "rhlike_minion" 1s 390ms

Then I check for failed events on history event page 51s 388ms

@build_host
Feature:Bootstrap a build host via the GUI 4m 24s 429ms 9

Scenario:
Clean up sumaform leftovers on build host
8s 134ms 1

When I perform a full salt minion cleanup on "build_host" 8s 134ms

Scenario:
Log in as admin user
38s 15ms 1

Given I am authorized for the "Admin" section 38s 15ms

Scenario:
Bootstrap a build host
45s 979ms 10

The hostname of build_host is uyuni-master-build-host.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 266ms

Then I should see a "Bootstrap Minions" text 202ms

When I enter the hostname of "build_host" as "hostname" 247ms

And I enter "22" as "port" 78ms

And I enter "root" as "user" 95ms

And I enter "linux" as "password" 112ms

And I select "1-BUILD-HOST-KEY-x86_64" from "activationKeys" 202ms

And I select the hostname of "proxy" from "proxies" if present 3s 55ms

And I click on "Bootstrap" 114ms

And I wait until I see "Bootstrap process initiated." text 41s 603ms

Scenario:
Check the new bootstrapped build host in System Overview page
1m 33s 215ms 6

It took 4 seconds to contact the minion

When I follow the left menu "Salt > Keys" 216ms

Then I should see a "accepted" text 588ms

When I follow the left menu "Systems > System List > All" 286ms

And I wait at most 500 seconds until I see the name of "build_host", refreshing the page 29s 409ms

And I wait at most 500 seconds until onboarding is completed for "build_host" 59s 461ms

Then the Salt master can reach "build_host" 3s 252ms

@proxy
Scenario:
Check connection from build host to proxy
1s 708ms 4

Given I am on the Systems overview page of this "build_host" 1s 278ms

When I follow "Details" in the content area 124ms

And I follow "Connection" in the content area 135ms

Then I should see "proxy" short hostname 168ms

@proxy
Scenario:
Check registration on build host of minion
1s 857ms 4

Given I am on the Systems overview page of this "proxy" 1s 467ms

When I follow "Details" in the content area 100ms

And I follow "Proxy" in the content area 83ms

Then I should see "build_host" hostname 205ms

Scenario:
Detect latest Salt changes on the SLES build host
642ms 1

* Mon Jan 19 2026 marek.czernek@suse.com
- Make syntax in httputil_test compatible with Python 3.6
- Fix KeyError in postgres module with PostgreSQL 17 (bsc#1254325)
- Added:
* fix-tornado-s-httputil_test-syntax-for-python-3.6.patch
* backport-add-maintain-m-privilege-to-postgres-module.patch

* Wed Jan 14 2026 marek.czernek@suse.com
- Use internal deb classes instead of external aptsource lib
* Drop dependency on saltbundlepy-apt
- Speed up wheel key.finger call (bsc#1240532)
- Add security patches (bsc#1254903,bsc#1254905,bsc#1254904)
- Simplify and speed up utils.find_json function (bsc#1246130)
- Added:
* use-internal-salt.utils.pkg.deb-classes-instead-of-a.patch

When I query latest Salt changes on "build_host" 642ms

Scenario:
Check that the build host is a build host
1s 988ms 3

Given I am on the Systems overview page of this "build_host" 1s 731ms

Then I should see a "[Container Build Host]" text 138ms

Then I should see a "[OS Image Build Host]" text 118ms

Scenario:
Check events history for failures on SLES build host
1m 12s 887ms 2

Given I am on the Systems overview page of this "build_host" 1s 904ms

Then I check for failed events on history event page 1m 10s 983ms

@sle_minion
Feature:Bootstrap a Salt minion via the GUI 3m 10s 719ms 6 2

Scenario:
Clean up sumaform leftovers on SLES minion
9s 962ms 1

When I perform a full salt minion cleanup on "sle_minion" 9s 962ms

Scenario:
Log in as admin user
38s 642ms 1

Given I am authorized for the "Admin" section 38s 642ms

Scenario:
Bootstrap a SLES minion
44s 23ms 11

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 266ms

Then I should see a "Bootstrap Minions" text 128ms

When I enter the hostname of "sle_minion" as "hostname" 263ms

And I enter "22" as "port" 94ms

And I enter "root" as "user" 116ms

And I enter "linux" as "password" 100ms

And I select "1-SUSE-KEY-x86_64" from "activationKeys" 117ms

And I select the hostname of "proxy" from "proxies" if present 3s 582ms

And I click on "Bootstrap" 136ms

And I wait until I see "Bootstrap process initiated." text 39s 217ms

And I report the bootstrap duration for "sle_minion" < 1ms

Scenario:
Check the new bootstrapped minion in System List page
1m 34s 516ms 8

It took 2 seconds to contact the minion

When I follow the left menu "Salt > Keys" 224ms

And I wait until I do not see "Loading..." text 759ms

Then I should see a "accepted" text 120ms

When I follow the left menu "Systems > System List > All" 273ms

And I wait until I see the name of "sle_minion", refreshing the page 31s 469ms

And I wait until onboarding is completed for "sle_minion" 59s 548ms

Then the Salt master can reach "sle_minion" 2s 120ms

And I report the onboarding duration for "sle_minion" < 1ms

@susemanager
Scenario:
Use correct kernel image on the SLES minion
< 1ms 2

When I remove package "kernel-default-base" from this "sle_minion" 0s

And I install package "kernel-default" on this "sle_minion" 0s

@susemanager
Scenario:
Reboot the SLES minion to use the new kernel
< 1ms 1

When I reboot the "sle_minion" host through SSH, waiting until it comes back 0s

@proxy
Scenario:
Check connection from minion to proxy
1s 660ms 4

Given I am on the Systems overview page of this "sle_minion" 1s 314ms

When I follow "Details" in the content area 129ms

And I follow "Connection" in the content area 101ms

Then I should see "proxy" short hostname 114ms

@proxy
Scenario:
Check registration on proxy of minion
1s 914ms 4

Given I am on the Systems overview page of this "proxy" 1s 517ms

When I follow "Details" in the content area 129ms

And I follow "Proxy" in the content area 116ms

Then I should see "sle_minion" hostname 150ms

@ssh_minion
Feature:Bootstrap a Salt host managed via salt-ssh 3m 42s 67ms 5 2

Scenario:
Clean up sumaform leftovers on SLES SSH minion
10s 773ms 1

When I perform a full salt minion cleanup on "ssh_minion" 10s 773ms

Scenario:
Log in as admin user
38s 845ms 1

Given I am authorized for the "Admin" section 38s 845ms

Scenario:
Bootstrap a SLES SSH minion
2m 50s 97ms 11

The hostname of ssh_minion is uyuni-master-suse-sshminion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 286ms

Then I should see a "Bootstrap Minions" text 159ms

When I check "manageWithSSH" 130ms

And I enter the hostname of "ssh_minion" as "hostname" 233ms

And I enter "linux" as "password" 87ms

And I select the hostname of "proxy" from "proxies" if present 3s 348ms

And I click on "Bootstrap" 178ms

And I wait until I see "Bootstrap process initiated." text 1m 467ms

And I follow the left menu "Systems > System List > All" 208ms

And I wait until I see the name of "ssh_minion", refreshing the page 1m 13s 130ms

And I wait until onboarding is completed for "ssh_minion" 31s 867ms

@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 188ms 4

Given I am on the Systems overview page of this "ssh_minion" 904ms

When I follow "Details" in the content area 101ms

And I follow "Connection" in the content area 88ms

Then I should see "proxy" short hostname 93ms

@proxy
Scenario:
Check registration on proxy of SSH minion
1s 163ms 4

Given I am on the Systems overview page of this "proxy" 836ms

When I follow "Details" in the content area 84ms

And I follow "Proxy" in the content area 110ms

Then I should see "ssh_minion" hostname 131ms

@scope_visualization
Feature:Secure connection 252ms 4

Scenario:
Connecting to the server insecurely
2ms 2

Error: 302 302

When I connect to the server insecurely 1ms

Then the connection should redirect to the secured channel < 1ms

Scenario:
Connecting to the server securely
101ms 3

When I connect to the server securely 101ms

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
66ms 2

When I connect to the server securely while using incorrect certificate as a CA certificate file 66ms

Then the secure connection should fail due to unverified certificate signature < 1ms

Feature:List available products 2s 570ms 1 2

In order to use software channels
As root user
I want to list available products from command line

@susemanager
Scenario:
List available products
< 1ms 2

When I execute mgr-sync "list products" with user "admin" and password "admin" 0s

Then I should get "[ ] SUSE Linux Enterprise Desktop 15 SP3 x86_64" 0s

@uyuni
Scenario:
List available products
2s 570ms 1 1

When I execute mgr-sync "list products" with user "admin" and password "admin" 2s 570ms

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:191:in `/^I should get "([^"]*)"$/'
features/secondary/srv_mgr_sync_list_products.feature:17:in `I should get "[ ] openSUSE Leap 15.6 x86_64"'

@susemanager
Scenario:
List all available products
< 1ms 4

When I execute mgr-sync "list products -e" 0s

Then I should get "[ ] SUSE Linux Enterprise Desktop 15 SP3 x86_64" 0s

And I should get " [ ] (R) Basesystem Module 15 SP3 x86_64" 0s

And I should get " [ ] Desktop Applications Module 15 SP3 x86_64" 0s

@skip_if_containerized_server @skip_if_github_validation @scope_monitoring
Feature:Disable and re-enable monitoring of the server < 1ms 7

Scenario:
Log in as admin user
< 1ms 1

Given I am authorized for the "Admin" section 0s

Scenario:
Disable monitoring from the UI
< 1ms 11

When I follow the left menu "Admin > Manager Configuration > Monitoring" 0s

And I wait until I see "Server self monitoring" text 0s

And I click on "Disable" 0s

And I wait until button "Disable" becomes enabled 0s

Then I should see a "Monitoring disabled successfully." text 0s

And I should see a list item with text "System" and a failing bullet 0s

And I should see a list item with text "PostgreSQL database" and a failing bullet 0s

And I should see a list item with text "Server self monitoring" and a warning bullet 0s

And I should see a list item with text "Taskomatic (Java JMX)" and a warning bullet 0s

And I should see a list item with text "Tomcat (Java JMX)" and a warning bullet 0s

And I should see a "Restarting Tomcat and Taskomatic is needed for the configuration changes to take effect." text 0s

Scenario:
Restart spacewalk services to apply config changes after disabling monitoring
< 1ms 1

When I restart the spacewalk service 0s

Scenario:
Check that monitoring is disabled
< 1ms 18

Given I am authorized for the "Admin" section 0s

When I follow the left menu "Admin > Manager Configuration > Monitoring" 0s

And I wait until I see "Server self monitoring" text 0s

Then I should see a "Enable" button 0s

And I should see a "Disable" button 0s

And I should see a list item with text "System" and a failing bullet 0s

And I should see a list item with text "PostgreSQL database" and a failing bullet 0s

And I should see a list item with text "Server self monitoring" and a failing bullet 0s

And I should see a list item with text "Taskomatic (Java JMX)" and a failing bullet 0s

And I should see a list item with text "Tomcat (Java JMX)" and a failing bullet 0s

And I should not see a "Restarting Tomcat and Taskomatic is needed for the configuration changes to take effect." text 0s

And file "/etc/rhn/rhn.conf" should contain "prometheus_monitoring_enabled = 0" on server 0s

And file "/etc/sysconfig/tomcat/systemd/jmx.conf" should not exist on server 0s

And file "/etc/sysconfig/taskomatic/systemd/jmx.conf" should not exist on server 0s

And port "3333" should be closed 0s

And port "3334" should be closed 0s

And port "5556" should be closed 0s

And port "5557" should be closed 0s

Scenario:
Enable monitoring from the UI
< 1ms 11

When I follow the left menu "Admin > Manager Configuration > Monitoring" 0s

And I wait until I see "Server self monitoring" text 0s

And I click on "Enable" 0s

And I wait until button "Enable" becomes enabled 0s

Then I should see a "Monitoring enabled successfully." text 0s

And I should see a list item with text "System" and a success bullet 0s

And I should see a list item with text "PostgreSQL database" and a success bullet 0s

And I should see a list item with text "Server self monitoring" and a pending bullet 0s

And I should see a list item with text "Taskomatic (Java JMX)" and a pending bullet 0s

And I should see a list item with text "Tomcat (Java JMX)" and a pending bullet 0s

And I should see a "Restarting Tomcat and Taskomatic is needed for the configuration changes to take effect." text 0s

Scenario:
Restart spacewalk services to apply config changes after enabling monitoring
< 1ms 1

When I restart the spacewalk service 0s

Scenario:
Check that monitoring is enabled
< 1ms 18

Given I am authorized for the "Admin" section 0s

When I follow the left menu "Admin > Manager Configuration > Monitoring" 0s

And I wait until I see "Server self monitoring" text 0s

Then I should see a "Enable" button 0s

And I should see a "Disable" button 0s

And I should see a list item with text "System" and a success bullet 0s

And I should see a list item with text "PostgreSQL database" and a success bullet 0s

And I should see a list item with text "Server self monitoring" and a success bullet 0s

And I should see a list item with text "Taskomatic (Java JMX)" and a success bullet 0s

And I should see a list item with text "Tomcat (Java JMX)" and a success bullet 0s

And I should not see a "Restarting Tomcat and Taskomatic is needed for the configuration changes to take effect." text 0s

And file "/etc/rhn/rhn.conf" should contain "prometheus_monitoring_enabled = 1" on server 0s

And file "/etc/sysconfig/tomcat/systemd/jmx.conf" should contain "jmx_prometheus_javaagent.jar=5556" on server 0s

And file "/etc/sysconfig/taskomatic/systemd/jmx.conf" should contain "jmx_prometheus_javaagent.jar=5557" on server 0s

And port "3333" should be closed 0s

And port "3334" should be closed 0s

And port "5556" should be open 0s

And port "5557" should be open 0s

@skip_if_github_validation @skip_if_cloud @scope_virtual_host_manager
Feature:Virtual host manager web UI < 1ms 9

Scenario:
Log in as org admin user
< 1ms 1

Given I am authorized 0s

Scenario:
Check the VHM page
< 1ms 3

When I follow the left menu "Systems > Virtual Host Managers" 0s

Then I should see a "Virtual Host Managers" text 0s

And I should see a "No Virtual Host Managers." text 0s

Scenario:
Check VMware page
< 1ms 8

When I click on "Create" 0s

And I follow "VMWare-based" 0s

Then I should see a "Add a VMWare-based Virtual Host Manager" text 0s

And I should see a "Label" text 0s

And I should see a "Hostname" text 0s

And I should see a "Port" text 0s

And I should see a "Username" text 0s

And I should see a "Password" text 0s

Scenario:
Create Virtual Host
< 1ms 9

When I follow the left menu "Systems > Virtual Host Managers" 0s

And I copy vCenter configuration file on server 0s

And I click on "Create" 0s

When I follow "File-based" 0s

Then I should see a "Add a File-based Virtual Host Manager" text 0s

When I enter "file-vmware" as "label" 0s

And I enter "file:///var/tmp/vCenter.json" as "module_url" 0s

And I click on "Create" 0s

Then I should see a "file-vmware" link 0s

Scenario:
Run virtual-host-gatherer
< 1ms 6

When I follow the left menu "Systems > Virtual Host Managers" 0s

And I follow "file-vmware" 0s

Then I should see a "file:///var/tmp/vCenter.json" text 0s

And I should see a "SUSE Test" text 0s

When I click on "Refresh Data" 0s

Then I should see a "Refreshing the data for this Virtual Host Manager has been triggered." text 0s

Scenario:
Check new virtual hosts
< 1ms 7

Given I am on the Systems page 0s

And I wait until I see "10.162.186.111" text, refreshing the page 0s

When I follow "10.162.186.111" 0s

Then I should see a "OS: VMware ESXi" text 0s

When I follow the left menu "Systems > System List > Virtual Systems" 0s

Then I should see a "vCenter" text 0s

And I should see a "NSX-l3gateway" text 0s

Scenario:
Delete Virtual Host Manager
< 1ms 7

When I follow the left menu "Systems > Virtual Host Managers" 0s

And I follow "file-vmware" 0s

Then I should see a "file:///var/tmp/vCenter.json" text 0s

When I click on "Delete" in element "virtual-host-managers" 0s

And I click on "Delete" in "Delete Virtual Host Manager" modal 0s

And I wait until I see "Virtual Host Manager has been deleted." text 0s

Then I should see a "No Virtual Host Managers." text 0s

Scenario:
Cleanup: delete virtual host 10.162.186.111
< 1ms 5

Given I am on the Systems page 0s

When I follow "10.162.186.111" 0s

And I follow "Delete System" 0s

And I click on "Delete Profile" 0s

And I wait until I see "has been deleted" text 0s

Scenario:
Cleanup: delete virtual host 10.162.186.112
< 1ms 5

Given I am on the Systems page 0s

When I follow "10.162.186.112" 0s

And I follow "Delete System" 0s

And I click on "Delete Profile" 0s

And I wait until I see "has been deleted" text 0s

@skip_if_github_validation @scope_power_management @scope_cobbler @sle_minion
Feature:IPMI Power management 1m 43s 753ms 12

Scenario:
Fake an IPMI host
9s 487ms 1

When the server starts mocking an IPMI host 9s 487ms

Scenario:
Log in as admin user
37s 664ms 1

Given I am authorized for the "Admin" section 37s 664ms

Scenario:
Start Cobbler monitoring
6s 637ms 1

When I start local monitoring of Cobbler 6s 637ms

Scenario:
Check the power management page
5s 193ms 6

Given I am on the Systems overview page of this "sle_minion" 4s 880ms

When I follow "Provisioning" in the content area 78ms

And I follow "Power Management" in the content area 64ms

Then I should see a "Power Management Settings" text 71ms

And I should see a "IPMI" text 70ms

And I should see a "Save" button 26ms

Scenario:
Save power management values
6s 90ms 9

When I enter "fakeipmi" as "powerAddress" 54ms

And I enter "ipmiusr" as "powerUsername" 52ms

And I enter "test" as "powerPassword" 51ms

And I click on "Save" 55ms

Then I should see a "Power settings saved" text 72ms

And the cobbler report should contain "Power Management Address : fakeipmi" for "sle_minion" 1s 760ms

And the cobbler report should contain "Power Management Username : ipmiusr" for "sle_minion" 1s 335ms

And the cobbler report should contain "Power Management Password : test" for "sle_minion" 1s 339ms

And the cobbler report should contain "Power Management Type : ipmilan" for "sle_minion" 1s 367ms

Scenario:
Test IPMI functions
18s 264ms 18

When I follow "Provisioning" in the content area 62ms

And I follow "Power Management" in the content area 57ms

And I click on "Power On" 55ms

And I click on "Get status" 3s 444ms

Then I should see the power is "On" 24ms

When I click on "Power Off" 2s 843ms

Then I should see a "system has been powered off" text 76ms

And I should see the power is "Unknown" 19ms

When I click on "Get status" 618ms

Then I should see the power is "Off" 22ms

When I click on "Power On" 55ms

Then I should see a "system has been powered on" text 72ms

When I click on "Get status" 53ms

Then I should see the power is "On" 21ms

When I click on "Reboot" 10s 92ms

Then I should see a "system has been rebooted" text 75ms

When I click on "Get status" 645ms

Then I should see the power is "On" 22ms

Scenario:
Check power management SSM configuration
8s 56ms 21

When I follow the left menu "Systems > System List > All" 168ms

And I click on the clear SSM button 117ms

And I check the "sle_minion" client 435ms

And I follow the left menu "Systems > System Set Manager > Overview" 443ms

And I follow "Configure power management" in the content area 62ms

Then I should see "sle_minion" as link 18ms

And I should see a "Change Power Management Configuration" text 78ms

And I should see a "Type" text 83ms

And I should see a "Network address" text 76ms

And I should see a "Username" text 76ms

And I should see a "Password" text 75ms

And I should see a "System identifier" text 73ms

And I should see a "Update" button 17ms

When I enter "testing" as "powerUsername" 48ms

And I enter "qwertz" as "powerPassword" 48ms

And I click on "Update" 58ms

Then I should see a "Configuration successfully saved for 1 system(s)" text 462ms

And the cobbler report should contain "Power Management Username : testing" for "sle_minion" 1s 729ms

And the cobbler report should contain "Power Management Password : qwertz" for "sle_minion" 1s 342ms

And the cobbler report should contain "Power Management Address : fakeipmi" for "sle_minion" 1s 322ms

And the cobbler report should contain "Power Management Type : ipmilan" for "sle_minion" 1s 318ms

Scenario:
Check power management SSM operation
211ms 6

And I follow the left menu "Systems > System Set Manager > Overview" 76ms

When I follow "power management operations" in the content area 70ms

Then I should see "sle_minion" as link 13ms

And I should see a "Power On" button 17ms

And I should see a "Power Off" button 16ms

And I should see a "Reboot" button 17ms

Scenario:
Cleanup: reset IPMI values
6s 691ms 8

Given I want to operate on this "sle_minion" 361ms

When I set power management value "" for "powerAddress" 325ms

And I set power management value "" for "powerUsername" 327ms

And I set power management value "" for "powerPassword" 312ms

Then the cobbler report should contain "Power Management Address :" for "sle_minion" 1s 339ms

And the cobbler report should contain "Power Management Username :" for "sle_minion" 1s 354ms

And the cobbler report should contain "Power Management Password :" for "sle_minion" 1s 342ms

And the cobbler report should contain "Power Management Type : ipmilan" for "sle_minion" 1s 326ms

Scenario:
Cleanup: tear down the IPMI host
470ms 1

When the server stops mocking an IPMI host 470ms

Scenario:
Cleanup: remove remaining systems from SSM after power management tests
51ms 1

When I click on the clear SSM button 51ms

Scenario:
Check for errors in Cobbler monitoring
4s 932ms 1

Then the local logs for Cobbler should not contain errors 4s 932ms

@skip_if_github_validation @scope_api @sle_minion
Feature:IPMI Power management API 29s 522ms 6

Scenario:
Setup an IPMI host for API test
923ms 2

When the server starts mocking an IPMI host 625ms

And I want to operate on this "sle_minion" 297ms

Scenario:
Check the power management settings for API test
327ms 2

When I fetch power management values 327ms

Then power management results should have "ipmilan" for "powerType" < 1ms

Scenario:
Save power management values for API test
6s 665ms 8

When I set power management value "fakeipmi" for "powerAddress" 322ms

And I set power management value "ipmiusr" for "powerUsername" 329ms

And I set power management value "test" for "powerPassword" 328ms

And I set power management value "ipmilan" for "powerType" 319ms

Then the cobbler report should contain "Power Management Address : fakeipmi" for "sle_minion" 1s 329ms

And the cobbler report should contain "Power Management Username : ipmiusr" for "sle_minion" 1s 328ms

And the cobbler report should contain "Power Management Password : test" for "sle_minion" 1s 367ms

And the cobbler report should contain "Power Management Type : ipmilan" for "sle_minion" 1s 340ms

Scenario:
Test IPMI functions for API test
14s 404ms 6

When I turn power on 2s 615ms

Then the power status is "on" 470ms

When I turn power off 2s 600ms

Then the power status is "off" 492ms

When I do power management reboot 7s 752ms

Then the power status is "on" 472ms

Scenario:
Cleanup: reset IPMI values for API test
6s 720ms 7

When I set power management value "" for "powerAddress" 321ms

And I set power management value "" for "powerUsername" 345ms

And I set power management value "" for "powerPassword" 336ms

Then the cobbler report should contain "Power Management Address :" for "sle_minion" 1s 683ms

And the cobbler report should contain "Power Management Username :" for "sle_minion" 1s 333ms

And the cobbler report should contain "Power Management Password :" for "sle_minion" 1s 364ms

And the cobbler report should contain "Power Management Type : ipmilan" for "sle_minion" 1s 335ms

Scenario:
Cleanup: tear down the IPMI host for API test
480ms 1

When the server stops mocking an IPMI host 480ms

@skip_if_github_validation @scope_power_management @scope_cobbler @sle_minion
Feature:Redfish Power management 42s 590ms 11

Scenario:
Setup a Redfish host
7s 227ms 1

When the controller starts mocking a Redfish host 7s 227ms

Scenario:
Log in as admin user
448ms 1

Given I am authorized for the "Admin" section 448ms

Scenario:
Start Cobbler monitoring
6s 355ms 1

When I start local monitoring of Cobbler 6s 355ms

Scenario:
Save power management values for Redfish
6s 786ms 13

Given I am on the Systems overview page of this "sle_minion" 863ms

When I follow "Provisioning" in the content area 71ms

And I follow "Power Management" in the content area 65ms

And I enter the controller hostname as the redfish server address 97ms

And I enter "ipmiusr" as "powerUsername" 53ms

And I enter "test" as "powerPassword" 48ms

And I select "Redfish" from "powerType" 69ms

And I click on "Save" 58ms

Then I should see a "Power settings saved" text 77ms

And the cobbler report should contain ":8443" for "sle_minion" 1s 370ms

And the cobbler report should contain "Power Management Username : ipmiusr" for "sle_minion" 1s 329ms

And the cobbler report should contain "Power Management Password : test" for "sle_minion" 1s 340ms

And the cobbler report should contain "Power Management Type : redfish" for "sle_minion" 1s 340ms

Scenario:
Test Redfish functions
3s 147ms 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" 56ms

And I click on "Get status" 818ms

Then I should see the power is "On" 23ms

When I click on "Power Off" 57ms

Then I should see a "system has been powered off" text 74ms

And I should see the power is "Unknown" 20ms

When I click on "Get status" 806ms

Then I should see the power is "Off" 22ms

When I click on "Power On" 54ms

Then I should see a "system has been powered on" text 73ms

When I click on "Get status" 55ms

Then I should see the power is "On" 22ms

When I click on "Reboot" 61ms

Then I should see a "system has been rebooted" text 74ms

When I click on "Get status" 782ms

Then I should see the power is "On" 20ms

Scenario:
Check power management SSM configuration for Redfish
7s 974ms 21

When I follow the left menu "Systems > System List > All" 132ms

And I click on the clear SSM button 46ms

And I check the "sle_minion" client 421ms

And I follow the left menu "Systems > System Set Manager > Overview" 492ms

And I follow "Configure power management" in the content area 69ms

Then I should see "sle_minion" as link 13ms

And I should see a "Change Power Management Configuration" text 75ms

And I should see a "Type" text 74ms

And I should see a "Network address" text 77ms

And I should see a "Username" text 78ms

And I should see a "Password" text 76ms

And I should see a "System identifier" text 73ms

And I should see a "Update" button 13ms

When I enter "testing" as "powerUsername" 49ms

And I enter "qwertz" as "powerPassword" 50ms

And I click on "Update" 392ms

Then I should see a "Configuration successfully saved for 1 system(s)" text 80ms

And the cobbler report should contain "Power Management Username : testing" for "sle_minion" 1s 714ms

And the cobbler report should contain "Power Management Password : qwertz" for "sle_minion" 1s 345ms

And the cobbler report should contain ":8443" for "sle_minion" 1s 351ms

And the cobbler report should contain "Power Management Type : redfish" for "sle_minion" 1s 347ms

Scenario:
Check power management SSM operation for Redfish
182ms 6

And I follow the left menu "Systems > System Set Manager > Overview" 72ms

When I follow "power management operations" in the content area 60ms

Then I should see "sle_minion" as link 10ms

And I should see a "Power On" button 13ms

And I should see a "Power Off" button 13ms

And I should see a "Reboot" button 12ms

Scenario:
Cleanup: reset Redfish values
6s 968ms 9

Given I want to operate on this "sle_minion" 316ms

When I set power management value "" for "powerAddress" 317ms

And I set power management value "" for "powerUsername" 309ms

And I set power management value "" for "powerPassword" 325ms

And I set power management value "ipmilan" for "powerType" 314ms

Then the cobbler report should contain "Power Management Address :" for "sle_minion" 1s 359ms

And the cobbler report should contain "Power Management Username :" for "sle_minion" 1s 336ms

And the cobbler report should contain "Power Management Password :" for "sle_minion" 1s 355ms

And the cobbler report should contain "Power Management Type : ipmilan" for "sle_minion" 1s 332ms

Scenario:
Cleanup: tear down the Redfish host
49ms 1

When the controller stops mocking a Redfish host 49ms

Scenario:
Cleanup: remove remaining systems from SSM after Redfish power management tests
52ms 1

When I click on the clear SSM button 52ms

Scenario:
Check for errors in Cobbler monitoring
3s 396ms 1

Then the local logs for Cobbler should not contain errors 3s 396ms

@scope_configuration_channels
Feature:Delete channels with child or clone is not allowed 15s 836ms 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 753ms 1

Given I am authorized 1s 753ms

Scenario:
Clone the first channel before deletion from UI test
1s 881ms 8

When I follow the left menu "Software > Manage > Channels" 180ms

And I follow "Clone Channel" 376ms

And I select "Fake-Base-Channel-SUSE-like" as the origin channel 67ms

And I click on "Clone Channel" 407ms

Then I should see a "Create Software Channel" text 80ms

And I should see a "Current state of the channel" text 78ms

When I click on "Clone Channel" 611ms

Then I should see a "Clone of Fake-Base-Channel-SUSE-like" text 80ms

Scenario:
Clone the second channel using first channel as base
1s 737ms 8

When I follow the left menu "Software > Manage > Channels" 78ms

And I follow "Clone Channel" 380ms

And I select "Clone of Fake-Base-Channel-SUSE-like" as the origin channel 67ms

And I click on "Clone Channel" 371ms

Then I should see a "Create Software Channel" text 80ms

And I should see a "Current state of the channel" text 78ms

When I click on "Clone Channel" 602ms

Then I should see a "Clone of Clone of Fake-Base-Channel-SUSE-like" text 77ms

Scenario:
Try to delete channel with clone
1s 503ms 7

When I follow the left menu "Software > Manage > Channels" 72ms

And I follow "Clone of Fake-Base-Channel-SUSE-like" 380ms

And I follow "Delete Channel" 401ms

And I check "unsubscribeSystems" 81ms

And I click on "Delete Channel" 445ms

Then I should see a "Clone of Fake-Base-Channel-SUSE-like" text 61ms

And I should see a "Unable to delete channel" text 59ms

Scenario:
Delete channel without clones neither children
1s 599ms 7

When I follow the left menu "Software > Manage > Channels" 72ms

And I follow "Clone of Clone of Fake-Base-Channel-SUSE-like" 386ms

And I follow "Delete Channel" 321ms

And I check "unsubscribeSystems" 68ms

And I click on "Delete Channel" 569ms

Then I should see a "Clone of Clone of Fake-Base-Channel-SUSE-like" text 90ms

And I should see a "has been deleted" text 89ms

Scenario:
Clone a child channel to the clone of x86_64 test channel
2s 224ms 9

When I follow the left menu "Software > Manage > Channels" 72ms

And I follow "Clone Channel" 362ms

And I select "Fake-RPM-SUSE-Channel" as the origin channel 63ms

And I click on "Clone Channel" 438ms

Then I should see a "Create Software Channel" text 81ms

And I should see a "Current state of the channel" text 75ms

When I select "Clone of Fake-Base-Channel-SUSE-like" from "Parent Channel" 65ms

And I click on "Clone Channel" 986ms

Then I should see a "Clone of Fake-RPM-SUSE-Channel" text 77ms

Scenario:
Try delete channel with child
1s 433ms 8

When I follow the left menu "Software > Manage > Channels" 72ms

And I follow "Clone of Fake-Base-Channel-SUSE-like" 375ms

And I follow "Delete Channel" 314ms

And I check "unsubscribeSystems" 68ms

And I click on "Delete Channel" 420ms

Then I should see a "Clone of Fake-Base-Channel-SUSE-like" text 60ms

And I should see a "channel has child channels associated" text 61ms

And I should see a "must delete those channels first before deleting the parent." text 58ms

Scenario:
Cleanup: remove cloned child channel
1s 889ms 7

When I follow the left menu "Software > Manage > Channels" 73ms

And I follow "Clone of Fake-RPM-SUSE-Channel" 397ms

And I follow "Delete Channel" 388ms

And I check "unsubscribeSystems" 68ms

And I click on "Delete Channel" 838ms

Then I should see a "Clone of Fake-RPM-SUSE-Channel" text 62ms

And I should see a "has been deleted." text 61ms

Scenario:
Cleanup: remove cloned parent channel
1s 813ms 7

When I follow the left menu "Software > Manage > Channels" 77ms

And I follow "Clone of Fake-Base-Channel-SUSE-like" 371ms

And I follow "Delete Channel" 310ms

And I check "unsubscribeSystems" 66ms

And I click on "Delete Channel" 806ms

Then I should see a "Clone of Fake-Base-Channel-SUSE-like" text 94ms

And I should see a "has been deleted." text 86ms

@scope_configuration_channels
Feature:Deleting channels with children or clones is not allowed 9s 759ms 6

Using the tool spacewalk-remove-channel, we cannot delete a channel if it has a child
or a clone created from it

Scenario:
Log in as org admin user
1s 873ms 1

Given I am authorized 1s 873ms

Scenario:
Clone the first channel before deletion from tool test
1s 726ms 8

When I follow the left menu "Software > Manage > Channels" 175ms

And I follow "Clone Channel" 349ms

And I select "Fake-RPM-SUSE-Channel" as the origin channel 53ms

And I click on "Clone Channel" 56ms

Then I should see a "Create Software Channel" text 84ms

And I should see a "Current state of the channel" text 74ms

When I click on "Clone Channel" 854ms

Then I should see a "Clone of Fake-RPM-SUSE-Channel" text 77ms

Scenario:
Clone a second channel using first channel as base
1s 815ms 8

When I follow the left menu "Software > Manage > Channels" 74ms

And I follow "Clone Channel" 372ms

And I select "Clone of Fake-RPM-SUSE-Channel" as the origin channel 63ms

And I click on "Clone Channel" 368ms

Then I should see a "Create Software Channel" text 81ms

And I should see a "Current state of the channel" text 75ms

When I click on "Clone Channel" 706ms

Then I should see a "Clone of Clone of Fake-RPM-SUSE-Channel" text 74ms

Scenario:
Verify if both clone channels exists
1s 354ms 3

When I list channels with spacewalk-remove-channel 1s 354ms

Then I should get "clone-fake-rpm-suse-channel" < 1ms

And I should get "clone-clone-fake-rpm-suse-channel" < 1ms

Scenario:
Delete channel with one clone
945ms 5

When I delete these channels with spacewalk-remove-channel: 945ms
clone-fake-rpm-suse-channel

Then I should get "Error: cannot remove channel" < 1ms

And I should get "clone channel(s) exist" < 1ms

And I should get "clone-fake-rpm-suse-channel" < 1ms

And I should get "clone-clone-fake-rpm-suse-channel" < 1ms

Scenario:
Delete base channel and clone
2s 44ms 4

When I delete these channels with spacewalk-remove-channel: 1s 4ms
clone-fake-rpm-suse-channel
clone-clone-fake-rpm-suse-channel

And I list channels with spacewalk-remove-channel 1s 40ms

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 @flaky
Feature:Maintenance windows 1m 2s 662ms 13 1 1

Scenario:
Log in as org admin user
1s 737ms 1

Given I am authorized 1s 737ms

Scenario:
Create a single calendar
4s 471ms 9

URL: https://uyuni-master-server.sumaci.aws/pub/maintenance-windows-exchange.ics

When I follow the left menu "Schedule > Maintenance Windows > Calendars" 950ms

And I wait for "1" second 1s

Then I should see a "No calendars created" text 54ms

When I click on "Create" in element "maintenance-windows" 79ms

Then I should see a "Calendar Name" text 56ms

When I enter "singlecalendar" as "name" 76ms

And I add "maintenance-windows-exchange.ics" calendar file as url 1s 909ms

And I click on "Create Calendar" 58ms

Then I should see a "Calendar successfully created" text 285ms

Scenario:
Create a multi calendar
3s 539ms 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" 84ms

And I wait for "1" second 1s

Then I should see a "Items 1 - 1 of 1" text 61ms

When I click on "Create" in element "maintenance-windows" 64ms

Then I should see a "Calendar Name" text 55ms

When I enter "multicalendar" as "name" 66ms

And I add "maintenance-windows-multi-exchange-1.ics" calendar file as url 1s 882ms

And I click on "Create Calendar" 52ms

Then I should see a "Calendar successfully created" text 272ms

Scenario:
Create a single schedule
2s 840ms 11

When I follow the left menu "Schedule > Maintenance Windows > Schedules" 88ms

And I wait for "1" second 1s

Then I should see a "No schedules created" text 54ms

When I click on "Create" in element "maintenance-windows" 62ms

Then I should see a "Schedule Name" text 58ms

When I enter "singleschedule" as "name" 68ms

And I choose "SINGLE" 55ms

And I click on "Add Calendar" 70ms

And I select "singlecalendar" from "calendarSelect" 1s 117ms

And I click on "Create Schedule" 62ms

Then I should see a "Schedule successfully created" text 201ms

Scenario:
Create a multi schedule
2s 793ms 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 57ms

When I click on "Create" in element "maintenance-windows" 62ms

Then I should see a "Schedule Name" text 57ms

When I enter "SAP Maintenance Window" as "name" 86ms

And I choose "MULTI" 55ms

And I click on "Add Calendar" 56ms

And I select "multicalendar" from "calendarSelect" 1s 98ms

And I click on "Create Schedule" 52ms

Then I should see a "Schedule successfully created" text 176ms

Scenario:
Create another multi schedule
2s 737ms 10

When I follow the left menu "Schedule > Maintenance Windows > Schedules" 91ms

And I wait for "1" second 1s

Then I should see a "Items 1 - 2 of 2" text 66ms

When I click on "Create" 60ms

And I enter "Core Server Window" as "name" 76ms

And I choose "MULTI" 48ms

And I click on "Add Calendar" 58ms

And I select "multicalendar" from "calendarSelect" 1s 103ms

And I click on "Create Schedule" 51ms

Then I should see a "Schedule successfully created" text 179ms

Scenario:
Assign a single system to the single schedule
1s 960ms 5

Given I am on the Systems overview page of this "sle_minion" 859ms

When I follow "Properties" in the content area 74ms

And I select "singleschedule" from "maintenance-schedule" 60ms

And I click on "Update Properties" 876ms

Then I should see a "System properties changed" text 89ms

Scenario:
Assign systems to the multi schedule using SSM
4s 108ms 10

When I follow the left menu "Systems > System List > All" 136ms

And I click on the clear SSM button 62ms

And I check the "rhlike_minion" client 1s 792ms

And I follow the left menu "Systems > System Set Manager > Overview" 426ms

And I follow "Assign" in the content area 67ms

And I select "SAP Maintenance Window" from "scheduleId" 1s 115ms

And I check "cancelActions" 85ms

And I click on "Assign All" 66ms

And I click on "Confirm" 67ms

Then I should see a "Maintenance schedule has been assigned" text 288ms

@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
17s 964ms 3

When I remove package "virgo-dummy" from this "rhlike_minion" without error control 1s 395ms

And I refresh packages list via spacecmd on "rhlike_minion" 2s 604ms

And I wait until refresh package list on "rhlike_minion" is finished 13s 964ms

Scenario:
Schedule package installation action
4s 342ms 10

Given I am on the Systems overview page of this "rhlike_minion" 926ms

When I follow "Software" in the content area 70ms

And I follow "Install" 573ms

And I enter "virgo-dummy" as the filtered package name 57ms

And I click on the filter button 632ms

And I check "virgo-dummy" in the list 60ms

And I click on "Install Packages" 988ms

And I select the next maintenance window 19ms

And I click on "Confirm" 952ms

Then I should see a "1 package install has been scheduled for" text 62ms

Scenario:
Detach systems from schedules
2s 530ms 8

When I follow the left menu "Systems > System List > All" 112ms

And I click on the clear SSM button 52ms

And I check the "sle_minion" client 496ms

And I follow the left menu "Systems > System Set Manager > Overview" 447ms

And I follow "Assign" in the content area 62ms

And I select "None - clear schedule" from "scheduleId" 1s 113ms

And I click on "Clear All" 65ms

Then I should see a "Maintenance schedule has been cleared" text 179ms

Scenario:
Cleanup: cancel all scheduled actions
703ms 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 703ms

Scenario:
Delete maintenance schedules
1s 905ms 13

When I follow the left menu "Schedule > Maintenance Windows > Schedules" 470ms

And I click the "Core Server Window" item delete button 288ms

Then I should see a "Delete maintenance schedule" text 69ms

When I click on the red confirmation button 67ms

And I wait until I see "Schedule 'Core Server Window' has been deleted." text 184ms

And I click the "SAP Maintenance Window" item delete button 67ms

Then I should see a "Delete maintenance schedule" text 71ms

When I click on the red confirmation button 57ms

And I wait until I see "Schedule 'SAP Maintenance Window' has been deleted." text 182ms

And I click the "singleschedule" item delete button 137ms

Then I should see a "Delete maintenance schedule" text 64ms

When I click on the red confirmation button 58ms

And I wait until I see "singleschedule' has been deleted." text 185ms

Scenario:
Delete maintenance calendars
11s 27ms 1 7 1

When I follow the left menu "Schedule > Maintenance Windows > Calendars" 85ms

And I click the "singlecalendar" item delete button 10s 941ms Show Error + 
                                            
 element click intercepted: Element (i class="fa fa-trash no-margin")(/i) is not clickable at point (997, 259). Other element would receive the click: (div class="tooltip-inner")...(/div)
  (Session info: chrome=144.0.7559.96) (Selenium::WebDriver::Error::ElementClickInterceptedError)
./features/step_definitions/content_lifecycle_steps.rb:66:in `/^I click the "([^"]*)" item (.*?) button$/'
features/secondary/srv_maintenance_windows.feature:161:in `I click the "singlecalendar" item delete button'

Then I should see a "Delete maintenance calendar" text 0s

When I click on the red confirmation button 0s

And I wait until I see "Calendar 'singlecalendar' has been deleted." text 0s

And I click the "multicalendar" item delete button 0s

Then I should see a "Delete maintenance calendar" text 0s

When I click on the red confirmation button 0s

And I wait until I see "Calendar 'multicalendar' has been deleted." text 0s

@flaky @scope_visualization @scope_salt
Feature:Create organizations, users, groups, and activation keys using Salt states 37s 290ms 13 2

Scenario:
Log in as org admin user
1s 733ms 1

Given I am authorized 1s 733ms

@skip_if_containerized_server
Scenario:
Apply configuration salt state to server
< 1ms 1

When I manually install the "uyuni-config" formula on the server 0s

Scenario:
Apply setup_users_configuration state to server
12s 828ms 1

When I apply "setup_users_configuration" local salt state on "server" 12s 828ms

Scenario:
Organization my_org was correctly created
2s 153ms 5

Given I am authorized as "my_org_user" with password "my_org_user" 1s 938ms

When I follow the left menu "Home > My Organization" 78ms

Then I should see a "my_org" text in the content area 33ms

When I follow the left menu "Home > My Organization > Organization Trusts" 79ms

Then I should see a "my_org2" text in the content area 22ms

Scenario:
Organization my_org2 was correctly created
2s 32ms 5

Given I am authorized as "my_org_user2" with password "my_org_user2" 1s 854ms

When I follow the left menu "Home > My Organization" 62ms

Then I should see a "my_org2" text in the content area 23ms

When I follow the left menu "Home > My Organization > Organization Trusts" 69ms

Then I should see a "my_org" text in the content area 23ms

Scenario:
Group was correctly created
2s 398ms 5

Given I am authorized for the "Admin" section 1s 816ms

When I follow the left menu "Systems > System Groups" 122ms

When I follow "minions_group" 320ms

Then I should see a "minions_group" text 69ms

And I should see a "System Group Status" text 69ms

Scenario:
User was correctly created
2s 168ms 5

Given I am authorized as "user2" with password "user2" 1s 637ms

When I follow the left menu "Systems > System Groups" 109ms

And I follow "minions_group" 306ms

Then I should see a "minions_group" text 57ms

And I should see a "System Group Status" text 57ms

Scenario:
User channels permissions were assigned
3s 353ms 5

Given I am authorized as "user2" with password "user2" 396ms

When I follow the left menu "Software > Channel List > All" 187ms

And I follow "Show All Child Channels" 65ms

And I follow "Fake-RPM-SUSE-Channel" 419ms

And I follow "Managers" 2s 284ms

Scenario:
User Roles were assigned
1s 960ms 9

Given I am authorized for the "Admin" section 1s 302ms

When I follow the left menu "Users > User List > Active" 176ms

And I follow "user2" 299ms

Then I should see a "User Details" text 78ms

And I should see "role_activation_key_admin" as checked 23ms

And I should see "role_image_admin" as unchecked 19ms

And I should see "role_config_admin" as checked 20ms

And I should see "role_channel_admin" as unchecked 19ms

And I should see "role_system_group_admin" as unchecked 18ms

Scenario:
Activation Key was correctly created
509ms 6

When I follow the left menu "Systems > Activation Keys" 110ms

And I follow "My Activation Key created via Salt" 263ms

Then I should see "10" in field identified by "usageLimit" 25ms

And I should see "virtualization_host" as checked 18ms

And I should see a "Push via SSH" text 71ms

And I should see "enable-config-auto-deploy" as checked 20ms

Scenario:
Cleanup: apply configuration teardown salt state to server
7s 443ms 1

When I apply "teardown_users_configuration" local salt state on "server" 7s 443ms

@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
262ms 3

When I follow the left menu "Admin > Organizations" 119ms

Then I should not see a "my_org" text 80ms

And I should not see a "my_org2" text 62ms

Scenario:
Cleanup: user was successfully removed
261ms 2

When I follow the left menu "Users > User List > Active" 161ms

Then I should not see a "user2" text 99ms

Scenario:
Cleanup: activation key was successfully removed
183ms 2

When I follow the left menu "Systems > Activation Keys" 103ms

Then I should not see a "My Activation Key created via Salt" text 80ms

@flaky
Feature:Export and import software channels with new ISS implementation 43s 746ms 10

Distribute software between servers
Run export and import with ISS v2

Scenario:
Install inter server sync package
3s 261ms 2

When I install packages "inter-server-sync" on this "server" 2s 634ms

Then "inter-server-sync" should be installed on "server" 626ms

Scenario:
Log in as org admin user
1s 774ms 1

Given I am authorized 1s 774ms

Scenario:
Clone a channel with patches
1s 992ms 9

When I follow the left menu "Software > Manage > Channels" 183ms

And I follow "Clone Channel" 367ms

And I select "Fake-RPM-SUSE-Channel" as the origin channel 84ms

And I choose "current" 54ms

And I click on "Clone Channel" 380ms

And I should see a "Create Software Channel" text 76ms

And I should see a "Current state of the channel" text 77ms

And I click on "Clone Channel" 694ms

Then I should see a "Clone of Fake-RPM-SUSE-Channel" text 74ms

Scenario:
Check that this channel has patches
1s 44ms 8

When I follow the left menu "Software > Manage > Channels" 77ms

And I follow "Clone of Fake-RPM-SUSE-Channel" 383ms

And I follow "Patches" in the content area 72ms

And I follow "List/Remove Patches" 458ms

Then I should see a "CL-hoag-dummy-7890" link 12ms

And I should see a "CL-virgo-dummy-3456" link 12ms

And I should see a "CL-milkyway-dummy-2345" link 13ms

And I should see a "CL-andromeda-dummy-6789" link 12ms

Scenario:
Export data with ISS v2
16s 798ms 3

When I ensure folder "/tmp/export_iss_v2" doesn't exist on "server" 666ms

When I export software channels "clone-fake-rpm-suse-channel" with ISS v2 to "/tmp/export_iss_v2" 15s 432ms

Then "/tmp/export_iss_v2" folder on server is ISS v2 export directory 699ms

Scenario:
Cleanup: remove cloned channels
1s 762ms 6

When I follow the left menu "Software > Manage > Channels" 73ms

And I follow "Clone of Fake-RPM-SUSE-Channel" 483ms

And I follow "Delete Channel" 320ms

And I check "unsubscribeSystems" 83ms

And I click on "Delete Channel" 737ms

Then I should see a "Clone of Fake-RPM-SUSE-Channel" text 65ms

Scenario:
Import data with ISS v2
12s 966ms 1

When I import data with ISS v2 from "/tmp/export_iss_v2" 12s 966ms

Scenario:
Check that this channel was imported and has patches
1s 96ms 8

When I follow the left menu "Software > Manage > Channels" 73ms

And I follow "Clone of Fake-RPM-SUSE-Channel" 474ms

And I follow "Patches" in the content area 58ms

And I follow "List/Remove Patches" 457ms

Then I should see a "CL-hoag-dummy-7890" link 8ms

And I should see a "CL-virgo-dummy-3456" link 8ms

And I should see a "CL-milkyway-dummy-2345" link 7ms

And I should see a "CL-andromeda-dummy-6789" link 7ms

Scenario:
Cleanup: remove imported channel
1s 651ms 6

When I follow the left menu "Software > Manage > Channels" 73ms

When I follow "Clone of Fake-RPM-SUSE-Channel" 474ms

And I follow "Delete Channel" 314ms

And I check "unsubscribeSystems" 68ms

And I click on "Delete Channel" 659ms

Then I should see a "Clone of Fake-RPM-SUSE-Channel" text 61ms

Scenario:
Cleanup: remove ISS v2 export folder
1s 396ms 1

When I ensure folder "/tmp/export_iss_v2" doesn't exist on "server" 1s 396ms

Feature:Export and import configuration channels with new ISS implementation 24s 391ms 10

Distribute configuration between servers
Run export and import with ISS v2

Scenario:
Install inter server sync package
1s 500ms 2

When I install packages "inter-server-sync" on this "server" 853ms

Then "inter-server-sync" should be installed on "server" 646ms

Scenario:
Log in as org admin user
1s 586ms 1

Given I am authorized 1s 586ms

Scenario:
Create a configuration channel
1s 969ms 7

When I follow the left menu "Configuration > Channels" 800ms

And I follow "Create Config Channel" 263ms

And I enter "Test Config Channel" as "cofName" 72ms

And I enter "testconfigchannel" as "cofLabel" 67ms

And I enter "This is a test configuration channel" as "cofDescription" 78ms

And I click on "Create Config Channel" 65ms

Then I should see a "Test Config Channel" text 621ms

Scenario:
Add a configuration file to the test configuration channel
3s 115ms 9

When I follow the left menu "Configuration > Channels" 65ms

And I follow "Test Config Channel" 414ms

And I follow "Create Configuration File or Directory" 373ms

And I enter "/etc/s-mgr/config" as "cffPath" 69ms

And I enter "COLOR=white" in the editor 6ms

And I click on "Create Configuration File" 66ms

Then I should see a "Revision 1 of /etc/s-mgr/config from channel Test Config Channel" text 699ms

And file "/srv/susemanager/salt/manager_org_1/testconfigchannel/init.sls" should exist on server 756ms

And file "/srv/susemanager/salt/manager_org_1/testconfigchannel/etc/s-mgr/config" should exist on server 665ms

Scenario:
Export data with ISS v2
7s 33ms 3

When I ensure folder "/tmp/export_iss_v2" doesn't exist on "server" 646ms

When I export config channels "testconfigchannel" with ISS v2 to "/tmp/export_iss_v2" 5s 707ms

Then "/tmp/export_iss_v2" folder on server is ISS v2 export directory 679ms

Scenario:
Cleanup: remove the test configuration channel
1s 805ms 6

When I follow the left menu "Configuration > Channels" 70ms

And I follow "Test Config Channel" 419ms

And I follow "Delete Channel" 361ms

And I click on "Delete Config Channel" 59ms

Then file "/srv/susemanager/salt/manager_org_1/testconfigchannel/init.sls" should not exist on server 885ms

And I should not see a "Test Config Channel" link 8ms

Scenario:
Import data with ISS v2
2s 617ms 1

When I import data with ISS v2 from "/tmp/export_iss_v2" 2s 617ms

Scenario:
Check that the config channel was imported
1s 486ms 4

When I follow the left menu "Configuration > Channels" 81ms

Then I should see a "Test Config Channel" link 9ms

And file "/srv/susemanager/salt/manager_org_1/testconfigchannel/init.sls" should exist on server 734ms

And file "/srv/susemanager/salt/manager_org_1/testconfigchannel/etc/s-mgr/config" should exist on server 660ms

Scenario:
Cleanup: remove the test configuration channel
1s 949ms 6

When I follow the left menu "Configuration > Channels" 60ms

And I follow "Test Config Channel" 400ms

And I follow "Delete Channel" 281ms

And I click on "Delete Config Channel" 497ms

Then file "/srv/susemanager/salt/manager_org_1/testconfigchannel/init.sls" should not exist on server 704ms

And I should not see a "Test Config Channel" link 5ms

Scenario:
Cleanup: remove ISS v2 export folder
1s 327ms 1

When I ensure folder "/tmp/export_iss_v2" doesn't exist on "server" 1s 327ms

@skip_if_github_validation @sle_minion @scope_salt @new_issue @flaky
Feature:Salt master integration with Git pillar 56s 727ms 6

Scenario:
Pre-requisite: Enabling repositories for installing git-core
1s 514ms 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 750ms

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 763ms

Scenario:
Preparing Git pillar configuration for Salt master
19s 832ms 3

When I setup a git_pillar environment on the Salt master 6s 116ms

And I wait until Salt master can reach "sle_minion" 13s 23ms

Then file "/etc/salt/master.d/zz-testing-gitpillar.conf" should exist on server 692ms

Scenario:
Check for the expected pillar data after enabling Git pillar
11s 289ms 5

When I refresh the pillar data 2s 360ms

And I wait until there is no pillar refresh salt job active 2s 897ms

Then the pillar data for "org_id" should be "1" on "sle_minion" 1s 607ms

And the pillar data for "git_pillar_foobar" should be "12345" on "sle_minion" 1s 555ms

And the pillar data for "git_pillar_foobar" should be "12345" on the Salt master 2s 868ms

Scenario:
Cleanup: Remove Git pillar configuration for Salt master
14s 754ms 3

When I clean up the git_pillar environment on the Salt master 962ms

And I wait until Salt master can reach "sle_minion" 13s 112ms

Then file "/etc/salt/master.d/zz-testing-gitpillar.conf" should not exist on server 679ms

Scenario:
Cleanup: Check for the expected pillar data after disabling Git pillar
8s 10ms 4

When I refresh the pillar data 2s 171ms

Then the pillar data for "git_pillar_foobar" should be empty on "sle_minion" 1s 547ms

And the pillar data for "org_id" should be "1" on "sle_minion" 1s 556ms

And the pillar data for "git_pillar_foobar" should be empty on the Salt master 2s 735ms

Scenario:
Pre-Cleanup: Disabling repositories for uninstalling git-core
1s 325ms 2

When I remove repository "SLE-Module-Basesystem15-SP7-Updates" on "server" without error control 653ms

And I remove repository "SLE-Module-Basesystem15-SP7-Pool" on "server" without error control 671ms

@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 3s 762ms 5

Scenario:
Log in as org admin user
1s 821ms 1

Given I am authorized 1s 821ms

@ssh_minion
Scenario:
Reboot the SSH-managed SLES minion
3m 57s 72ms 6

Given I am on the Systems overview page of this "ssh_minion" 5s 231ms

When I follow first "Schedule System Reboot" 464ms

Then I should see a "System Reboot Confirmation" text 80ms

And I should see a "Reboot system" button 31ms

When I click on "Reboot system" 789ms

Then I wait and check that "ssh_minion" has rebooted 3m 50s 475ms

Scenario:
Schedule a reboot on a SLES Salt minion
4m 17s 36ms 8

2026-02-02 10:53:37 +0100 Still waiting for action to complete...

Given I am on the Systems overview page of this "sle_minion" 923ms

When I follow first "Schedule System Reboot" 487ms

Then I should see a "System Reboot Confirmation" text 71ms

And I should see a "Reboot system" button 15ms

And I click on "Reboot system" 800ms

Then I should see a "Reboot scheduled for system" text 87ms

When I wait at most 600 seconds until event "System reboot scheduled" is completed 4m 14s 591ms

And I should see a "Reboot completed." text 59ms

@rhlike_minion
Scenario:
Reboot the Red Hat-like minion and wait until reboot is completed
4m 168ms 8

2026-02-02 10:58:10 +0100 Still waiting for action to complete...

Given I am on the Systems overview page of this "rhlike_minion" 846ms

When I follow first "Schedule System Reboot" 481ms

Then I should see a "System Reboot Confirmation" text 70ms

And I should see a "Reboot system" button 19ms

When I click on "Reboot system" 728ms

Then I should see a "Reboot scheduled for system" text 90ms

When I wait at most 600 seconds until event "System reboot scheduled" is completed 3m 57s 871ms

Then I should see a "Reboot completed." text 60ms

@deblike_minion
Scenario:
Reboot the Debian-like minion and wait until reboot is completed
3m 47s 663ms 8

2026-02-02 11:02:14 +0100 Still waiting for action to complete...

Given I am on the Systems overview page of this "deblike_minion" 5s 321ms

When I follow first "Schedule System Reboot" 482ms

Then I should see a "System Reboot Confirmation" text 68ms

And I should see a "Reboot system" button 20ms

When I click on "Reboot system" 756ms

Then I should see a "Reboot scheduled for system" text 87ms

When I wait at most 600 seconds until event "System reboot scheduled" is completed 3m 40s 864ms

Then I should see a "Reboot completed." text 61ms

@skip_if_github_validation @sle_minion @scope_cve_audit
Feature:CVE Audit on SLE Salt Minions 1m 12s 535ms 12

In order to check if systems are patched against certain vulnerabilities
As an authorized user
I want to see the Salt Minions that need to be patched

Scenario:
Log in as admin user
2s 158ms 1

Given I am authorized for the "Admin" section 2s 158ms

Scenario:
Pre-requisite: downgrade milkyway-dummy to lower version
10s 174ms 9

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 1s 6ms

And I install old package "milkyway-dummy-1.0" on this "sle_minion" 1s 604ms

And I refresh the metadata for "sle_minion" 845ms

And I follow the left menu "Admin > Task Schedules" 144ms

And I follow "errata-cache-default" 1s 224ms

And I follow "errata-cache-bunch" 1s 283ms

And I click on "Single Run Schedule" 1s 274ms

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 2s 514ms

Scenario:
Schedule channel data refresh
4s 50ms 6

When I follow the left menu "Admin > Task Schedules" 69ms

And I follow "cve-server-channels-default" 1s 73ms

And I follow "cve-server-channels-bunch" 1s 226ms

And I click on "Single Run Schedule" 337ms

Then I should see a "bunch was scheduled" text 63ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 1s 281ms

Scenario:
Display CVE audit page
237ms 3

When I follow the left menu "Audit > CVE Audit" 136ms

Then I should see a "CVE Audit" link in the left menu 30ms

And I should see a "CVE Audit" text 71ms

Scenario:
Search for a known CVE number
21s 405ms 14

When I follow the left menu "Audit > CVE Audit" 64ms

And I select "1999" from "cveIdentifierYear" 76ms

And I enter "9999" as "cveIdentifierId" 73ms

And I click on "Audit Servers" 62ms

Then I should see "sle_minion" as link 730ms

And I should see a "Affected, at least one patch available in an assigned channel" text 90ms

And I should see a "Install a new patch on this system" link 12ms

And I should see a "milkyway-dummy-2345" text 87ms

And I should see a "Download CSV" link 11ms

And I should see a "Status" button 17ms

And I should see a "Name" button 18ms

And I should see a "extra CVE data update" link 11ms

Then I follow "Install a new patch on this system" on "sle_minion" row 20s 67ms

And I should see a "Relevant Patches" text 79ms

Scenario:
Search for an unknown CVE number
468ms 5

When I follow the left menu "Audit > CVE Audit" 108ms

And I select "2012" from "cveIdentifierYear" 58ms

And I enter "2806" as "cveIdentifierId" 55ms

And I click on "Audit Servers" 55ms

Then I should see a "The specified CVE number was not found" text 189ms

Scenario:
Select a system for the System Set Manager
1s 962ms 11

And I click on the clear SSM button 68ms

And I follow the left menu "Audit > CVE Audit" 67ms

And I select "1999" from "cveIdentifierYear" 51ms

And I enter "9999" as "cveIdentifierId" 53ms

And I click on "Audit Servers" 54ms

Then I should see a "Affected, at least one patch available in an assigned channel" text 71ms

When I check the "sle_minion" client 687ms

Then I should see a "system selected" text 218ms

When I follow the left menu "Systems > System List > All" 190ms

Then I should see "sle_minion" as link 445ms

And I click on the clear SSM button 55ms

Scenario:
List systems by patch status via API before patch
6s 822ms 12

Result list: [{"errata_advisories"=>[], "system_id"=>1000010001, "channel_labels"=>[], "patch_status"=>"NOT_AFFECTED"}, {"errata_advisories"=>[], "system_id"=>1000010003, "channel_labels"=>[], "patch_status"=>"NOT_AFFECTED"}, {"errata_advisories"=>[], "system_id"=>1000010004, "channel_labels"=>[], "patch_status"=>"NOT_AFFECTED"}, {"errata_advisories"=>[], "system_id"=>1000010000, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}, {"errata_advisories"=>[], "system_id"=>1000010002, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}, {"errata_advisories"=>[], "system_id"=>1000010005, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}]
Result list: [{"errata_advisories"=>["milkyway-dummy-2345"], "system_id"=>1000010001, "channel_labels"=>["fake-base-channel-rh-like"], "patch_status"=>"AFFECTED_FULL_PATCH_APPLICABLE"}, {"errata_advisories"=>["milkyway-dummy-2345"], "system_id"=>1000010004, "channel_labels"=>["fake-rpm-suse-channel"], "patch_status"=>"AFFECTED_FULL_PATCH_APPLICABLE"}, {"errata_advisories"=>[], "system_id"=>1000010003, "channel_labels"=>[], "patch_status"=>"NOT_AFFECTED"}, {"errata_advisories"=>[], "system_id"=>1000010000, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}, {"errata_advisories"=>[], "system_id"=>1000010002, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}, {"errata_advisories"=>[], "system_id"=>1000010005, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}]
result: {"errata_advisories"=>["milkyway-dummy-2345"], "system_id"=>1000010004, "channel_labels"=>["fake-rpm-suse-channel"], "patch_status"=>"AFFECTED_FULL_PATCH_APPLICABLE"}

When I follow the left menu "Admin > Task Schedules" 139ms

And I follow "cve-server-channels-default" 392ms

And I follow "cve-server-channels-bunch" 1s 236ms

And I click on "Single Run Schedule" 1s 297ms

Then I should see a "bunch was scheduled" text 62ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 1s 272ms

When I call audit.list_systems_by_patch_status() with CVE identifier "CVE-1999-9979" 951ms

Then I should get status "NOT_AFFECTED" for "sle_minion" 296ms

When I call audit.list_systems_by_patch_status() with CVE identifier "CVE-1999-9999" 875ms

Then I should get status "AFFECTED_FULL_PATCH_APPLICABLE" for "sle_minion" 298ms

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
21s 867ms 10

Given I am on the Systems overview page of this "sle_minion" 802ms

When I follow "Software" in the content area 75ms

And I follow "Patches" in the content area 68ms

And I enter "milkyway" as the filtered synopsis 48ms

And I click on the filter button 526ms

And I check "milkyway-dummy-2345" in the list 62ms

And I click on "Apply Patches" 613ms

And I click on "Confirm" 688ms

Then I should see a "patch update has been scheduled" text 83ms

And I wait until event "Patch Update: milkyway-dummy-2345" is completed 18s 898ms

Scenario:
List systems by patch status via API after patch
1s 147ms 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"=>1000010003, "channel_labels"=>[], "patch_status"=>"NOT_AFFECTED"}, {"errata_advisories"=>[], "system_id"=>1000010004, "channel_labels"=>[], "patch_status"=>"PATCHED"}, {"errata_advisories"=>[], "system_id"=>1000010000, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}, {"errata_advisories"=>[], "system_id"=>1000010002, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}, {"errata_advisories"=>[], "system_id"=>1000010005, "channel_labels"=>[], "patch_status"=>"UNKNOWN"}]

And I call audit.list_systems_by_patch_status() with CVE identifier "CVE-1999-9999" 867ms

Then I should get status "PATCHED" for "sle_minion" 279ms

Scenario:
Cleanup: remove installed packages
2s 176ms 2

When I disable repository "test_repo_rpm_pool" on this "sle_minion" without error control 771ms

And I remove package "milkyway-dummy" from this "sle_minion" without error control 1s 405ms

Scenario:
Cleanup: remove remaining systems from SSM after CVE audit tests
64ms 1

When I click on the clear SSM button 64ms

@scope_openscap @scope_res @rhlike_minion
Feature:OpenSCAP audit of Red Hat-like Salt minion 3m 16s 783ms 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
447ms 1

Given I am authorized for the "Admin" section 447ms

@skip_if_github_validation
Scenario:
Enable repositories for openSCAP on the Red Hat-like minion
26s 182ms 2

When I enable the repositories "Rocky-BaseOS Rocky-AppStream" on this "rhlike_minion" 358ms

And I refresh the metadata for "rhlike_minion" 25s 824ms

@skip_if_github_validation
Scenario:
Install the OpenSCAP packages on the Red Hat-like minion
1m 19s 790ms 5

Given I am on the Systems overview page of this "rhlike_minion" 825ms

And I install OpenSCAP dependencies on "rhlike_minion" 39s 985ms

And I follow "Software" in the content area 77ms

And I click on "Update Package List" 518ms

And I wait until event "Package List Refresh" is completed 38s 383ms

Scenario:
Schedule an OpenSCAP audit job on the Red Hat-like minion
56s 981ms 10

Given I am on the Systems overview page of this "rhlike_minion" 786ms

When I follow "Audit" in the content area 87ms

And I follow "OpenSCAP" in the content area 69ms

And I follow "Schedule" in the content area 68ms

And I wait at most 30 seconds until I do not see "This system does not yet have OpenSCAP scan capability." text, refreshing the page 68ms

And I enter "--profile xccdf_org.ssgproject.content_profile_anssi_bp28_intermediary" as "params" 128ms

And I enter "/usr/share/xml/scap/ssg/content/ssg-rhel8-ds.xml" as "path" 96ms

And I click on "Schedule" 599ms

Then I should see a "XCCDF scan has been scheduled" text 71ms

And I wait at most 500 seconds until event "OpenSCAP xccdf scanning" is completed 55s 3ms

Scenario:
Check the results of the OpenSCAP scan on the Red Hat-like minion
2s 482ms 7

Given I am on the Systems overview page of this "rhlike_minion" 811ms

When I follow "Audit" in the content area 86ms

And I follow "OpenSCAP" in the content area 69ms

And I follow "xccdf_org.open-scap_testresult" 883ms

Then I should see a "Details of XCCDF Scan" text 214ms

And I should see a "RHEL-8" text 204ms

And I should see a "XCCDF Rule Results" text 212ms

Scenario:
Cleanup: remove audit scans retention period from Red Hat-like minion
491ms 6

When I follow the left menu "Admin > Organizations" 156ms

When I follow "SUSE Test" in the content area 73ms

And I follow "Configuration" in the content area 69ms

And I enter "0" as "scap_retention_period" 60ms

And I click on "Update Organization" 63ms

Then I should see a "Organization SUSE Test was successfully updated." text 67ms

Scenario:
Cleanup: delete audit results from Red Hat-like minion
3s 757ms 8

Given I am on the Systems overview page of this "rhlike_minion" 834ms

When I follow "Audit" in the content area 66ms

And I follow "OpenSCAP" in the content area 58ms

And I follow "List Scans" in the content area 97ms

And I click on "Select All" 410ms

And I click on "Remove" 498ms

And I click on "Confirm" 1s 726ms

Then I should see a " SCAP Scan(s) deleted. 0 SCAP Scan(s) retained" text 64ms

Scenario:
Cleanup: restore audit scans retention period on Red Hat-like minion
404ms 6

When I follow the left menu "Admin > Organizations" 106ms

When I follow "SUSE Test" in the content area 69ms

And I follow "Configuration" in the content area 60ms

And I enter "90" as "scap_retention_period" 45ms

And I click on "Update Organization" 57ms

Then I should see a "Organization SUSE Test was successfully updated." text 66ms

@skip_if_github_validation
Scenario:
Cleanup: remove the OpenSCAP packages from the Red Hat-like minion
4s 633ms 2

When I remove OpenSCAP dependencies from "rhlike_minion" 4s 453ms

And I disable repository "Rocky-BaseOS" on this "rhlike_minion" 180ms

@skip_if_github_validation
Scenario:
Cleanup: restore the base channel for the Red Hat-like minion
21s 611ms 11

Warning: Radio button 'Fake-Base-Channel-RH-like' is already checked

Given I am on the Systems overview page of this "rhlike_minion" 786ms

When I follow "Software" in the content area 73ms

And I follow "Software Channels" in the content area 68ms

And I wait until I do not see "Loading..." text 70ms

And I check radio button "Fake-Base-Channel-RH-like" 271ms

And I wait until I do not see "Loading..." text 338ms

And I click on "Next" 69ms

Then I should see a "Confirm Software Channel Change" text 61ms

When I click on "Confirm" 74ms

Then I should see a "Changing the channels has been scheduled." text 952ms

And I wait until event "Subscribe channels scheduled" is completed 18s 844ms

@skip_if_github_validation @scope_res @rhlike_minion @new_issue
Feature:Remote command on the Red Hat-like Salt minion 28s 684ms 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 780ms 1

Given I am authorized 1s 780ms

Scenario:
Run a remote command on the Red Hat-like minion
26s 904ms 11

When I follow the left menu "Salt > Remote Commands" 134ms

Then I should see a "Remote Commands" text in the content area 24ms

When I enter command "cat /etc/os-release" 88ms

And I enter target "rhlike_minion" 114ms

And I click on preview 11s 283ms

And I click on run 48ms

Then I should see "rhlike_minion" hostname 54ms

When I wait for "15" seconds 15s

And I expand the results for "rhlike_minion" 51ms

Then I should see a "rhel centos fedora" text 53ms

And I should see a "ROCKY_SUPPORT_PRODUCT" text 50ms

@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 26s 934ms 12

Scenario:
Log in as org admin user
1s 623ms 1

Given I am authorized 1s 623ms

Scenario:
Delete the Red Hat-like minion before SSH minion tests
4m 7s 93ms 7

When I am on the Systems overview page of this "rhlike_minion" 1s 546ms

And I follow "Delete System" 476ms

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 4m 4s 290ms

And I wait until Salt client is inactive on "rhlike_minion" 305ms

Then "rhlike_minion" should not be registered 348ms

Scenario:
Bootstrap a SSH-managed Red Hat-like minion
2m 17s 34ms 11

The hostname of rhlike_minion is uyuni-master-rhlike-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 84ms

Then I should see a "Bootstrap Minions" text 75ms

When I check "manageWithSSH" 93ms

And I enter the hostname of "rhlike_minion" as "hostname" 141ms

And I enter "linux" as "password" 60ms

And I select the hostname of "proxy" from "proxies" if present 2s 768ms

And I click on "Bootstrap" 65ms

And I wait at most 480 seconds until I see "Bootstrap process initiated." text 47s 66ms

And I follow the left menu "Systems > System List > All" 143ms

And I wait until I see the name of "rhlike_minion", refreshing the page 58s 186ms

And I wait until onboarding is completed for "rhlike_minion" 28s 346ms

@proxy
Scenario:
Check connection from SSH-managed Red Hat-like minion to proxy
1s 140ms 4

Given I am on the Systems overview page of this "rhlike_minion" 927ms

When I follow "Details" in the content area 77ms

And I follow "Connection" in the content area 67ms

Then I should see "proxy" short hostname 67ms

@proxy
Scenario:
Check registration on proxy of SSH-managed Red Hat-like minion
1s 116ms 4

Given I am on the Systems overview page of this "proxy" 885ms

When I follow "Details" in the content area 66ms

And I follow "Proxy" in the content area 70ms

Then I should see "rhlike_minion" hostname 94ms

Scenario:
Subscribe the SSH-managed Red Hat-like minion to a base channel
50s 840ms 11

Given I am on the Systems overview page of this "rhlike_minion" 905ms

When I follow "Software" in the content area 75ms

And I follow "Software Channels" in the content area 87ms

And I wait until I do not see "Loading..." text 67ms

And I check radio button "Fake-Base-Channel-RH-like" 10s 90ms

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 59ms

When I click on "Confirm" 78ms

Then I should see a "Changing the channels has been scheduled." text 284ms

And I wait until event "Subscribe channels scheduled" is completed 38s 693ms

Scenario:
Check events history for failures on SSH-managed Red Hat-like minion
1m 1s 797ms 2

Given I am on the Systems overview page of this "rhlike_minion" 865ms

Then I check for failed events on history event page 1m 932ms

Scenario:
Run a remote command on the SSH-managed Red Hat-like minion
29s 635ms 11

When I follow the left menu "Salt > Remote Commands" 132ms

Then I should see a "Remote Commands" text in the content area 23ms

When I enter command "cat /etc/os-release" 98ms

And I enter target "rhlike_minion" 108ms

And I click on preview 13s 996ms

And I click on run 49ms

Then I should see "rhlike_minion" hostname 65ms

When I wait for "15" seconds 15s

And I expand the results for "rhlike_minion" 53ms

Then I should see a "rhel centos fedora" text 54ms

And I should see a "ROCKY_SUPPORT_PRODUCT" text 53ms

Scenario:
Check events history for failures on SSH-managed Red Hat-like minion
1m 11s 922ms 2

Given I am on the Systems overview page of this "rhlike_minion" 897ms

Then I check for failed events on history event page 1m 11s 24ms

Scenario:
Cleanup: delete the SSH-managed Red Hat-like minion
13s 453ms 6

When I am on the Systems overview page of this "rhlike_minion" 886ms

And I follow "Delete System" 464ms

Then I should see a "Confirm System Profile Deletion" text 62ms

When I click on "Delete Profile" 82ms

And I wait until I see "has been deleted" text 11s 548ms

Then "rhlike_minion" should not be registered 408ms

Scenario:
Cleanup: bootstrap a Red Hat-like minion after SSH minion tests
1m 40s 373ms 12

The hostname of rhlike_minion is uyuni-master-rhlike-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 82ms

Then I should see a "Bootstrap Minions" text 64ms

When I enter the hostname of "rhlike_minion" as "hostname" 146ms

And I enter "22" as "port" 55ms

And I enter "root" as "user" 60ms

And I enter "linux" as "password" 62ms

And I select the hostname of "proxy" from "proxies" if present 78ms

And I click on "Bootstrap" 65ms

And I wait at most 480 seconds until I see "Bootstrap process initiated." text 19s 672ms

And I follow the left menu "Systems > System List > All" 151ms

And I wait until I see the name of "rhlike_minion", refreshing the page 1m 11s 793ms

And I wait until onboarding is completed for "rhlike_minion" 8s 141ms

Scenario:
Cleanup: re-subscribe the Red Hat-like minion to a base channel
30s 902ms 11

Given I am on the Systems overview page of this "rhlike_minion" 865ms

When I follow "Software" in the content area 79ms

And I follow "Software Channels" in the content area 68ms

And I wait until I do not see "Loading..." text 69ms

And I check radio button "Fake-Base-Channel-RH-like" 10s 82ms

And I wait until I do not see "Loading..." text 415ms

And I click on "Next" 78ms

Then I should see a "Confirm Software Channel Change" text 61ms

When I click on "Confirm" 77ms

Then I should see a "Changing the channels has been scheduled." text 289ms

And I wait until event "Subscribe channels scheduled" is completed 18s 813ms

@skip_if_github_validation @scope_deblike @deblike_minion
Feature:Remote command on Debian-like Salt minion 15s 236ms 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 554ms 1

Given I am authorized 2s 554ms

Scenario:
Run a remote command on the Debian-like minion
12s 682ms 10

When I follow the left menu "Salt > Remote Commands" 128ms

Then I should see a "Remote Commands" text in the content area 22ms

When I enter command "cat /etc/os-release" 90ms

And I enter target "deblike_minion" 111ms

And I click on preview 11s 367ms

And I click on run 49ms

Then I should see "deblike_minion" hostname 57ms

When I wait until I see "show response" text 747ms

And I expand the results for "deblike_minion" 53ms

Then I should see a "ID=ubuntu" text 53ms

@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 7s 783ms 12

Scenario:
Log in as org admin user
1s 789ms 1

Given I am authorized 1s 789ms

Scenario:
Delete the Debian-like minion
4m 7s 577ms 7

When I am on the Systems overview page of this "deblike_minion" 1s 532ms

And I follow "Delete System" 476ms

Then I should see a "Confirm System Profile Deletion" text 65ms

When I click on "Delete Profile" 95ms

And I wait until I see "has been deleted" text 4m 3s 799ms

And I wait until Salt client is inactive on "deblike_minion" 1s 285ms

Then "deblike_minion" should not be registered 323ms

Scenario:
Bootstrap a SSH-managed Debian-like minion
1m 59s 912ms 11

The hostname of deblike_minion is uyuni-master-deblike-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 86ms

Then I should see a "Bootstrap Minions" text 63ms

When I check "manageWithSSH" 94ms

And I enter the hostname of "deblike_minion" as "hostname" 142ms

And I enter "linux" as "password" 62ms

And I select the hostname of "proxy" from "proxies" if present 78ms

And I click on "Bootstrap" 70ms

And I wait at most 480 seconds until I see "Bootstrap process initiated." text 38s 966ms

And I follow the left menu "Systems > System List > All" 149ms

And I wait until I see the name of "deblike_minion", refreshing the page 1m 11s 823ms

And I wait until onboarding is completed for "deblike_minion" 8s 374ms

@proxy
Scenario:
Check connection from SSH-managed Debian-like minion to proxy
1s 181ms 4

Given I am on the Systems overview page of this "deblike_minion" 966ms

When I follow "Details" in the content area 76ms

And I follow "Connection" in the content area 69ms

Then I should see "proxy" short hostname 69ms

@proxy
Scenario:
Check registration on proxy of SSH-managed Debian-like minion
1s 131ms 4

Given I am on the Systems overview page of this "proxy" 872ms

When I follow "Details" in the content area 69ms

And I follow "Proxy" in the content area 91ms

Then I should see "deblike_minion" hostname 97ms

Scenario:
Subscribe the SSH-managed Debian-like minion to a base channel
50s 620ms 11

Given I am on the Systems overview page of this "deblike_minion" 961ms

When I follow "Software" in the content area 73ms

And I follow "Software Channels" in the content area 67ms

And I wait until I do not see "Loading..." text 72ms

And I check radio button "Fake-Base-Channel-Debian-like" 10s 77ms

And I wait until I do not see "Loading..." text 402ms

And I click on "Next" 65ms

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 301ms

And I wait until event "Subscribe channels scheduled" is completed 38s 457ms

Scenario:
Check events history for failures on SSH-managed Debian-like minion
1m 2s 40ms 2

Given I am on the Systems overview page of this "deblike_minion" 1s 35ms

Then I check for failed events on history event page 1m 1s 5ms

Scenario:
Run a remote command on the SSH-managed Debian-like minion
19s 997ms 10

When I follow the left menu "Salt > Remote Commands" 133ms

Then I should see a "Remote Commands" text in the content area 24ms

When I enter command "cat /etc/os-release" 97ms

And I enter target "deblike_minion" 108ms

And I click on preview 14s 741ms

And I click on run 49ms

Then I should see "deblike_minion" hostname 66ms

When I wait until I see "show response" text 4s 673ms

And I expand the results for "deblike_minion" 50ms

Then I should see a "ID=ubuntu" text 52ms

Scenario:
Check events history for failures on SSH-managed Debian-like minion
1m 11s 972ms 2

Given I am on the Systems overview page of this "deblike_minion" 964ms

Then I check for failed events on history event page 1m 11s 7ms

Scenario:
Cleanup: delete the SSH-managed Debian-like minion
14s 868ms 6

When I am on the Systems overview page of this "deblike_minion" 981ms

And I follow "Delete System" 386ms

Then I should see a "Confirm System Profile Deletion" text 67ms

When I click on "Delete Profile" 67ms

And I wait until I see "has been deleted" text 12s 569ms

Then "deblike_minion" should not be registered 795ms

Scenario:
Cleanup: bootstrap a Debian-like minion
1m 45s 834ms 12

The hostname of deblike_minion is uyuni-master-deblike-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 83ms

Then I should see a "Bootstrap Minions" text 65ms

When I enter the hostname of "deblike_minion" as "hostname" 152ms

And I enter "22" as "port" 54ms

And I enter "root" as "user" 63ms

And I enter "linux" as "password" 63ms

And I select the hostname of "proxy" from "proxies" if present 83ms

And I click on "Bootstrap" 68ms

And I wait at most 480 seconds until I see "Bootstrap process initiated." text 22s 163ms

And I follow the left menu "Systems > System List > All" 171ms

And I wait until I see the name of "deblike_minion", refreshing the page 44s 519ms

And I wait until onboarding is completed for "deblike_minion" 38s 343ms

Scenario:
Cleanup: re-subscribe the Debian-like minion to a base channel
30s 857ms 11

Given I am on the Systems overview page of this "deblike_minion" 837ms

When I follow "Software" in the content area 79ms

And I follow "Software Channels" in the content area 71ms

And I wait until I do not see "Loading..." text 68ms

And I check radio button "Fake-Base-Channel-Debian-like" 10s 91ms

And I wait until I do not see "Loading..." text 396ms

And I click on "Next" 65ms

Then I should see a "Confirm Software Channel Change" text 59ms

When I click on "Confirm" 61ms

Then I should see a "Changing the channels has been scheduled." text 292ms

And I wait until event "Subscribe channels scheduled" is completed 18s 833ms

@scope_salt_ssh @scope_onboarding @ssh_minion @skip_if_github_validation
Feature:Register a salt-ssh system via API 4m 39s 892ms 11 1

Scenario:
Log in as org admin user
1s 879ms 1

Given I am authorized 1s 879ms

Scenario:
Delete SSH minion system profile before API bootstrap test
18s 25ms 6

Given I am on the Systems overview page of this "ssh_minion" 1s 533ms

When I follow "Delete System" 396ms

Then I should see a "Confirm System Profile Deletion" text 64ms

When I click on "Delete Profile" 66ms

And I wait until I see "has been deleted" text 15s 571ms

Then "ssh_minion" should not be registered 392ms

@proxy
Scenario:
Block direct access from server to sshminion to test proxy as jumphost
1s 79ms 1

Given I block connections from "server" on "ssh_minion" 1s 79ms

Scenario:
Bootstrap a SLES SSH minion via API
50s 548ms 1

When I call system.bootstrap() on host "ssh_minion" and salt-ssh "enabled" 50s 548ms

Scenario:
Check new API bootstrapped salt-ssh system in System Overview page
1m 42s 715ms 3

When I follow the left menu "Systems > System List > All" 100ms

And I wait until I see the name of "ssh_minion", refreshing the page 31s 16ms

And I wait until onboarding is completed for "ssh_minion" 1m 11s 598ms

Scenario:
Check contact method of this Salt SSH system
976ms 2

Given I am on the Systems overview page of this "ssh_minion" 887ms

Then I should see a "Push via SSH" text 88ms

@proxy
Scenario:
Check registration on proxy of SSH minion bootstrapped via API
1s 141ms 4

Given I am on the Systems overview page of this "proxy" 883ms

When I follow "Details" in the content area 79ms

And I follow "Proxy" in the content area 71ms

Then I should see "ssh_minion" hostname 106ms

Scenario:
Check spacecmd system ID of SSH minion bootstrapped via API
3s 469ms 2

Given I am on the Systems overview page of this "ssh_minion" 875ms

Then I run spacecmd listeventhistory for "ssh_minion" 2s 594ms

Scenario:
Check events history for failures on SSH minion after API bootstrap
41s 727ms 2

Given I am on the Systems overview page of this "ssh_minion" 855ms

Then I check for failed events on history event page 40s 871ms

@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
57s 425ms 13

Warning: Radio button 'openSUSE Tumbleweed (x86_64)' is already checked

Given I am on the Systems overview page of this "ssh_minion" 887ms

When I follow "Software" in the content area 72ms

And I follow "Software Channels" in the content area 66ms

And I wait until I do not see "Loading..." text 89ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 242ms

And I wait until I do not see "Loading..." text 509ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 43ms

And I check "Fake-RPM-SUSE-Channel" 42ms

And I click on "Next" 65ms

Then I should see a "Confirm Software Channel Change" text 64ms

When I click on "Confirm" 79ms

Then I should see a "Changing the channels has been scheduled." text 316ms

And I wait until event "Subscribe channels scheduled" is completed 54s 944ms

@proxy
Scenario:
Cleanup and flush the firewall rules
904ms 1

When I flush firewall on "ssh_minion" 904ms

@skip_if_github_validation @scope_onboarding
Feature:Bootstrap a Salt minion via the GUI using SSH key 7m 3s 211ms 7 1

Scenario:
Log in as org admin user
1s 913ms 1

Given I am authorized 1s 913ms

Scenario:
Delete SLES minion system profile before bootstrap with SSH key test
4m 7s 323ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 645ms

When I follow "Delete System" 459ms

Then I should see a "Confirm System Profile Deletion" text 64ms

When I click on "Delete Profile" 65ms

And I wait until I see "has been deleted" text 4m 4s 37ms

And I wait until Salt client is inactive on "sle_minion" 738ms

Then "sle_minion" should not be registered 312ms

Scenario:
Prepare the minion for SSH key authentication
1s 312ms 2

When I backup the SSH authorized_keys file of host "sle_minion" 417ms

And I add pre-generated SSH public key to authorized_keys of host "sle_minion" 894ms

Scenario:
Bootstrap a SLES minion using SSH key with wrong passphrase
38s 423ms 14 1 1

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 84ms

Then I should see a "Bootstrap Minions" text 67ms

When I enter the hostname of "sle_minion" as "hostname" 149ms

And I enter "22" as "port" 57ms

And I enter "root" as "user" 59ms

And I check radio button "SSH Private Key" 10s 71ms

And I attach the file "ssh_keypair/id_rsa_bootstrap-passphrase_linux" to "privKeyFile" 40ms

And I enter "you-shall-not-pass" as "privKeyPwd" 104ms

And I click on "Bootstrap" 70ms

And I wait until I see "An error has occurred during salt execution: unable to establish ssh connection." text 7s 513ms

Then I should see a "Details" button 18ms

When I click on "Details" 73ms

And I wait at most 10 seconds until I see modal containing "Error Details" text 11ms

Then I should see a "Standard Error" text 69ms

And I should see "Permission denied, no authentication information" or "Permission denied (publickey,password,keyboard-interactive)" in the stderr textarea 20s 31ms Show Error + 
                                            
 Text 'Permission denied, no authentication information' and 'Permission denied (publickey,password,keyboard-interactive)' not found (ScriptError)
./features/step_definitions/navigation_steps.rb:707:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:706:in `/^I should see "([^"]*)" or "([^"]*)" in the ([^ ]+) textarea$/'
features/secondary/min_bootstrap_ssh_key.feature:44:in `I should see "Permission denied, no authentication information" or "Permission denied (publickey,password,keyboard-interactive)" in the stderr textarea'

When I close the modal dialog 0s

Scenario:
Bootstrap a SLES minion using SSH key
43s 25ms 11

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" 136ms

And I enter "22" as "port" 54ms

And I enter "root" as "user" 60ms

And I check radio button "SSH Private Key" 10s 75ms

And I attach the file "ssh_keypair/id_rsa_bootstrap-passphrase_linux" to "privKeyFile" 41ms

And I enter "linux" as "privKeyPwd" 67ms

And I select the hostname of "proxy" from "proxies" if present 80ms

And I click on "Bootstrap" 66ms

And I wait at most 480 seconds until I see "Bootstrap process initiated." text 32s 296ms

Scenario:
Check new minion bootstrapped with SSH key in System Overview page
1m 29s 106ms 6

It took 2 seconds to contact the minion

When I follow the left menu "Salt > Keys" 136ms

Then I should see a "accepted" text 436ms

When I am on the Systems page 253ms

And I wait until I see the name of "sle_minion", refreshing the page 58s 326ms

And I wait until onboarding is completed for "sle_minion" 28s 37ms

Then the Salt master can reach "sle_minion" 1s 914ms

Scenario:
Also check contact method of this minion
929ms 2

Given I am on the Systems overview page of this "sle_minion" 848ms

Then I should see a "Default" text 81ms

Scenario:
Cleanup: restore authorized keys
1s 177ms 1

When I restore the SSH authorized_keys file of host "sle_minion" 1s 177ms

@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 50s 919ms 9 1

Scenario:
Log in as org admin user
1s 774ms 1

Given I am authorized 1s 774ms

Scenario:
Pre-requisite: remove package before ssh tunnel test
1s 894ms 1

When I remove package "milkyway-dummy" from this "ssh_minion" without error control 1s 894ms

Scenario:
Delete the Salt minion for SSH tunnel bootstrap
17s 69ms 6

Given I am on the Systems overview page of this "ssh_minion" 906ms

When I follow "Delete System" 383ms

Then I should see a "Confirm System Profile Deletion" text 64ms

When I click on "Delete Profile" 66ms

And I wait until I see "has been deleted" text 15s 280ms

Then "ssh_minion" should not be registered 367ms

Scenario:
Register this minion for push via SSH tunnel
2m 40s 482ms 12

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 79ms

And I enter the hostname of "ssh_minion" as "hostname" 151ms

And I enter "22" as "port" 53ms

And I enter "root" as "user" 58ms

And I enter "linux" as "password" 61ms

And I select "1-SUSE-SSH-TUNNEL-KEY-x86_64" from "activationKeys" 76ms

And I select the hostname of "proxy" from "proxies" if present 70ms

And I check "manageWithSSH" 88ms

And I click on "Bootstrap" 64ms

And I wait at most 480 seconds until I see "Bootstrap process initiated." text 45s 243ms

And I wait until onboarding is completed for "ssh_minion" 1m 54s 450ms

Scenario:
The contact method is SSH tunnel on this minion
962ms 2

Given I am on the Systems overview page of this "ssh_minion" 874ms

Then I should see a "Push via SSH tunnel" text 88ms

Scenario:
Install a package from this SSH tunnel minion
58s 831ms 11

Given I am on the Systems overview page of this "ssh_minion" 1s 52ms

When I follow "Software" in the content area 78ms

And I follow "Install" 466ms

And I enter "milkyway-dummy" as the filtered package name 67ms

And I click on the filter button 643ms

And I wait until I see "milkyway-dummy" text 72ms

And I check row with "milkyway-dummy" and arch of "ssh_minion" 67ms

And I click on "Install Packages" 610ms

And I click on "Confirm" 657ms

Then I should see a "1 package install has been scheduled for" text 59ms

Then I wait until event "Package Install/Upgrade scheduled" is completed 55s 55ms

@flaky
Scenario:
Remove a package from this SSH tunnel minion
4m 27s 245ms 6 5 1

Given I am on the Systems overview page of this "ssh_minion" 865ms

And I follow "Software" in the content area 93ms

And I follow "List / Remove" 899ms

And I enter "milkyway-dummy" as the filtered package name 63ms

And I click on the filter button 807ms

And I wait until I see "milkyway-dummy" text 4m 10s 52ms 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

14s 464ms Show Info + 
11:49:51:000 - 11:54:05: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
31s 27ms 11

The hostname of ssh_minion is uyuni-master-suse-sshminion.sumaci.aws

When I follow the left menu "Salt > Remote Commands" 143ms

Then I should see a "Remote Commands" text in the content area 22ms

When I enter command "echo 'My remote command output'" 111ms

And I enter the hostname of "ssh_minion" as "target" 112ms

And I click on preview 20s 461ms

Then I should see a "Target systems (1)" text 59ms

When I wait until I do not see "pending" text 50ms

And I click on run 56ms

And I wait until I see "show response" text 9s 932ms

And I expand the results for "ssh_minion" 57ms

Then I should see "My remote command output" in the command output for "ssh_minion" 18ms

Scenario:
Cleanup: delete the SSH tunnel minion
25s 141ms 6

Given I am on the Systems overview page of this "ssh_minion" 931ms

When I follow "Delete System" 465ms

Then I should see a "Confirm System Profile Deletion" text 61ms

When I click on "Delete Profile" 66ms

And I wait until I see "has been deleted" text 23s 86ms

Then "ssh_minion" should not be registered 529ms

Scenario:
Cleanup: register a SSH minion after SSH tunnel tests
2m 26s 489ms 4

When I call system.bootstrap() on host "ssh_minion" and salt-ssh "enabled" 46s 580ms

And I follow the left menu "Systems > System List > All" 99ms

And I wait until I see the name of "ssh_minion", refreshing the page 1m 11s 931ms

And I wait until onboarding is completed for "ssh_minion" 27s 879ms

@skip_if_github_validation @scope_onboarding
Feature:Bootstrap a Salt minion via the GUI with an activation key 7m 23s 852ms 14 2

Scenario:
Log in as org admin user
1s 766ms 1

Given I am authorized 1s 766ms

Scenario:
Delete SLES minion system profile
4m 6s 921ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 587ms

When I follow "Delete System" 453ms

Then I should see a "Confirm System Profile Deletion" text 61ms

When I click on "Delete Profile" 68ms

And I wait until I see "has been deleted" text 4m 3s 715ms

And I wait until Salt client is inactive on "sle_minion" 723ms

Then "sle_minion" should not be registered 311ms

Scenario:
Create a configuration channel for the activation key
1s 600ms 7

When I follow the left menu "Configuration > Channels" 352ms

And I follow "Create Config Channel" 276ms

And I enter "Key Channel" as "cofName" 72ms

And I enter "keychannel" as "cofLabel" 59ms

And I enter "This is a configuration channel for the activation key" as "cofDescription" 96ms

And I click on "Create Config Channel" 679ms

Then I should see a "Key Channel" text 62ms

Scenario:
Add a configuration file to the key configuration channel
1s 640ms 6

When I follow the left menu "Configuration > Channels" 71ms

And I follow "Key Channel" 412ms

And I follow "Create Configuration File or Directory" 332ms

And I enter "/etc/euler.conf" as "cffPath" 68ms

And I enter "e^i.pi=-1" in the editor 5ms

And I click on "Create Configuration File" 750ms

@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 901ms 19

When I follow the left menu "Systems > Activation Keys" 132ms

And I follow "Create Key" 368ms

And I wait for child channels to appear 1s 278ms

And I enter "Minion testing" as "description" 109ms

And I enter "MINION-TEST" as "key" 95ms

And I enter "20" as "usageLimit" 63ms

And I select "openSUSE Tumbleweed (x86_64)" from "selectedBaseChannel" 93ms

And I wait for child channels to appear 382ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 95ms

And I check "Fake-RPM-SUSE-Channel" 91ms

And I click on "Create Activation Key" 504ms

And I follow "Configuration" in the content area 78ms

And I follow first "Subscribe to Channels" in the content area 69ms

And I check "Key Channel" in the list 70ms

And I click on "Continue" 802ms

And I follow "Packages" 478ms

And I enter "orion-dummy perseus-dummy" as "packages" 68ms

And I click on "Update Activation Key" 61ms

Then I should see a "Activation key Minion testing has been modified" text 57ms

Scenario:
Bootstrap a SLES minion with an activation key
1m 47s 210ms 13

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 70ms

Then I should see a "Bootstrap Minions" text 65ms

When I enter the hostname of "sle_minion" as "hostname" 137ms

And I enter "22" as "port" 57ms

And I enter "root" as "user" 61ms

And I enter "linux" as "password" 68ms

And I select "1-MINION-TEST" from "activationKeys" 66ms

And I select the hostname of "proxy" from "proxies" if present 68ms

And I click on "Bootstrap" 65ms

And I wait until I see "Bootstrap process initiated." text 23s 391ms

And I follow the left menu "Systems > System List > All" 162ms

And I wait until I see the name of "sle_minion", refreshing the page 44s 695ms

And I wait until onboarding is completed for "sle_minion" 38s 301ms

Scenario:
Verify that minion bootstrapped with Salt key and packages
4s 358ms 5

It took 2 seconds to contact the minion

When I follow the left menu "Salt > Keys" 135ms

Then I should see a "accepted" text 355ms

And the Salt master can reach "sle_minion" 1s 879ms

When I wait for "orion-dummy" to be installed on "sle_minion" 1s 150ms

And I wait for "perseus-dummy" to be installed on "sle_minion" 837ms

Scenario:
Check system ID of bootstrapped minion
3s 110ms 2

Given I am on the Systems overview page of this "sle_minion" 847ms

Then I run spacecmd listeventhistory for "sle_minion" 2s 262ms

@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
815ms 2

Given I am on the Systems page 252ms

Then I should see a "openSUSE Tumbleweed (x86_64)" text 563ms

Scenario:
Verify that minion bootstrapped with configuration channel
1s 218ms 6

Given I am on the Systems overview page of this "sle_minion" 845ms

When I follow "Configuration" in the content area 78ms

Then I should see a "1 configuration channel" text 74ms

When I follow "View Files" in the content area 70ms

Then I should see a "/etc/euler.conf" text 73ms

And I should see a "Key Channel" text 76ms

Scenario:
Cleanup: remove the package states
5s 710ms 12

Given I am on the Systems overview page of this "sle_minion" 813ms

When I follow "States" in the content area 73ms

And I follow "Packages" 493ms

Then I should see a "Package States" text 65ms

When I change the state of "orion-dummy" to "Unmanaged" and "" 155ms

And I change the state of "perseus-dummy" to "Unmanaged" and "" 41ms

Then I should see a "2 Changes" text 74ms

When I click save 52ms

Then I wait until I see "Package states have been saved." text 285ms

And I click apply 48ms

And I remove package "orion-dummy" from this "sle_minion" 1s 597ms

And I remove package "perseus-dummy" from this "sle_minion" 2s 8ms

Scenario:
Cleanup: remove the key configuration channel
1s 129ms 4

When I follow the left menu "Configuration > Channels" 325ms

And I follow "Key Channel" 425ms

And I follow "Delete Channel" 312ms

And I click on "Delete Config Channel" 65ms

Scenario:
Cleanup: delete the activation key
1s 468ms 5

When I follow the left menu "Systems > Activation Keys" 129ms

And I follow "Minion testing" in the content area 77ms

And I follow "Delete Key" 485ms

And I click on "Delete Activation Key" 691ms

Then I should see a "Activation key Minion testing has been deleted." text 84ms

Scenario:
Check events history for failures on SLES minion with activation key
1m 2s 2

Given I am on the Systems overview page of this "sle_minion" 916ms

Then I check for failed events on history event page 1m 1s 83ms

@skip_if_github_validation @scope_onboarding
Feature:Register a Salt minion via API 7m 20s 983ms 11 1

Scenario:
Log in as org admin user
2s 25ms 1

Given I am authorized 2s 25ms

Scenario:
Delete SLES minion system profile before API bootstrap test
4m 7s 160ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 600ms

When I follow "Delete System" 563ms

Then I should see a "Confirm System Profile Deletion" text 66ms

When I click on "Delete Profile" 66ms

And I wait until I see "has been deleted" text 4m 3s 745ms

And I wait until Salt client is inactive on "sle_minion" 778ms

Then "sle_minion" should not be registered 339ms

Scenario:
Bootstrap a SLES minion via API
23s 775ms 1

When I call system.bootstrap() on host "sle_minion" and salt-ssh "disabled" 23s 775ms

Scenario:
Check new minion bootstrapped via API in System Overview page
1m 25s 797ms 6

It took 1 seconds to contact the minion

When I follow the left menu "Salt > Keys" 139ms

Then I should see a "accepted" text 447ms

When I follow the left menu "Systems > System List > All" 193ms

And I wait until I see the name of "sle_minion", refreshing the page 17s 363ms

And I wait until onboarding is completed for "sle_minion" 1m 5s 750ms

Then the Salt master can reach "sle_minion" 1s 902ms

Scenario:
Check contact method of this minion
1s 2

Given I am on the Systems overview page of this "sle_minion" 906ms

Then I should see a "Default" text 93ms

@proxy
Scenario:
Check registration on proxy of minion bootstrapped via API
1s 200ms 4

Given I am on the Systems overview page of this "proxy" 934ms

When I follow "Details" in the content area 85ms

And I follow "Proxy" in the content area 82ms

Then I should see "sle_minion" hostname 97ms

Scenario:
Check spacecmd system ID of minion bootstrapped via API
3s 288ms 2

Given I am on the Systems overview page of this "sle_minion" 894ms

Then I run spacecmd listeventhistory for "sle_minion" 2s 393ms

@susemanager
Scenario:
API bootstrap: subscribe to base channel
< 1ms 14

Given I am on the Systems overview page of this "sle_minion" 0s

When I follow "Software" in the content area 0s

And I follow "Software Channels" in the content area 0s

And I wait until I do not see "Loading..." text 0s

And I check radio button "SLE-Product-SLES15-SP7-Pool for x86_64" 0s

And I wait until I do not see "Loading..." text 0s

And I include the recommended child channels 0s

And I check "SLE-Module-DevTools15-SP7-Pool for x86_64" 0s

And I check "Fake-RPM-SUSE-Channel" 0s

And I click on "Next" 0s

Then I should see a "Confirm Software Channel Change" text 0s

When I click on "Confirm" 0s

Then I should see a "Changing the channels has been scheduled." text 0s

And I wait until event "Subscribe channels scheduled" is completed 0s

@uyuni
Scenario:
API bootstrap: subscribe to base channel
21s 226ms 13

Warning: Radio button 'openSUSE Tumbleweed (x86_64)' is already checked

Given I am on the Systems overview page of this "sle_minion" 910ms

When I follow "Software" in the content area 75ms

And I follow "Software Channels" in the content area 88ms

And I wait until I do not see "Loading..." text 69ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 231ms

And I wait until I do not see "Loading..." text 433ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 43ms

And I check "Fake-RPM-SUSE-Channel" 41ms

And I click on "Next" 84ms

Then I should see a "Confirm Software Channel Change" text 64ms

When I click on "Confirm" 77ms

Then I should see a "Changing the channels has been scheduled." text 299ms

And I wait until event "Subscribe channels scheduled" is completed 18s 805ms

Scenario:
Check events history for failures on SLES minion after API bootstrap
51s 847ms 2

Given I am on the Systems overview page of this "sle_minion" 893ms

Then I check for failed events on history event page 50s 954ms

Scenario:
Bootstrap via API a non-existing system
2s 833ms 1

When I call system.bootstrap() on unknown host, I should get an API fault 2s 833ms

Scenario:
Bootstrap a salt-ssh system with activation key and default contact method
827ms 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 827ms

@skip_if_github_validation @sle_minion @scope_onboarding
Feature:Bootstrapping with reactivation key 8m 1s 326ms 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
1s 962ms 1

Given I am authorized 1s 962ms

Scenario:
Generate a re-activation key
2s 451ms 4

Given I am on the Systems overview page of this "sle_minion" 1s 400ms

When I follow "Reactivation" 485ms

And I click on "Generate New Key" 494ms

Then I should see a "Key:" text 70ms

Scenario:
Bootstrap should fail when minion already exists
939ms 10

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 84ms

Then I should see a "Bootstrap Minions" text 65ms

When I enter the hostname of "sle_minion" as "hostname" 146ms

And I enter "22" as "port" 56ms

And I enter "root" as "user" 61ms

And I enter "linux" as "password" 60ms

And I click on "Bootstrap" 70ms

And I wait until I see "A salt key for this host" text 268ms

Then I should not see a "GenericSaltError" text 63ms

And I should see a "seems to already exist, please check!" text 63ms

Scenario:
Bootstrap should fail when system already exists in the server
2s 738ms 11

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

Given I delete "sle_minion" key in the Salt master 1s 842ms

When I follow the left menu "Systems > Bootstrapping" 67ms

Then I should see a "Bootstrap Minions" text 63ms

When I enter the hostname of "sle_minion" as "hostname" 130ms

And I enter "22" as "port" 52ms

And I enter "root" as "user" 57ms

And I enter "linux" as "password" 62ms

And I click on "Bootstrap" 61ms

And I wait until I see "seems to already exist, please check!" text 264ms

Then I should not see a "GenericSaltError" text 63ms

And I should see a "with minion id" text 73ms

Scenario:
Bootstrap a SLES minion with reactivation key
1m 58s 126ms 13

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws
Reactivation Key: re-1-c81cec5f855c47f78b20e1f5b3460102

When I follow the left menu "Systems > Bootstrapping" 67ms

Then I should see a "Bootstrap Minions" text 64ms

When I enter the hostname of "sle_minion" as "hostname" 130ms

And I enter "22" as "port" 52ms

And I enter "root" as "user" 57ms

And I enter "linux" as "password" 60ms

And I enter the reactivation key of "sle_minion" 804ms

And I select "1-SUSE-KEY-x86_64" from "activationKeys" 80ms

And I click on "Bootstrap" 60ms

And I wait until I see "Bootstrap process initiated." text 30s 295ms

And I follow the left menu "Systems > System List > All" 158ms

And I wait until I see the name of "sle_minion", refreshing the page 732ms

And I wait until onboarding is completed for "sle_minion" 1m 25s 559ms

Scenario:
Check the events history for the reactivation
3s 188ms 5

Given I am on the Systems overview page of this "sle_minion" 892ms

When I follow "Events" in the content area 82ms

And I follow "History" in the content area 62ms

And I wait until I see "Server reactivated as Salt minion" text, refreshing the page 89ms

And I wait until event "Apply states [certs, channels, packages, services.salt-minion] scheduled" is completed 2s 60ms

Scenario:
Cleanup: delete SLES minion after reactivation tests
4m 5s 293ms 7

Given I am on the Systems overview page of this "sle_minion" 870ms

When I follow "Delete System" 482ms

Then I should see a "Confirm System Profile Deletion" text 62ms

When I click on "Delete Profile" 70ms

And I wait until I see "has been deleted" text 4m 2s 718ms

And I wait until Salt client is inactive on "sle_minion" 761ms

Then "sle_minion" should not be registered 328ms

Scenario:
Cleanup: bootstrap a SLES minion after reactivation tests
1m 46s 626ms 13

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 85ms

Then I should see a "Bootstrap Minions" text 86ms

When I enter the hostname of "sle_minion" as "hostname" 155ms

And I enter "22" as "port" 52ms

And I enter "root" as "user" 60ms

And I enter "linux" as "password" 64ms

And I select "1-SUSE-KEY-x86_64" from "activationKeys" 81ms

And I select the hostname of "proxy" from "proxies" if present 69ms

And I click on "Bootstrap" 64ms

And I wait until I see "Bootstrap process initiated." text 22s 782ms

And I follow the left menu "Systems > System List > All" 154ms

And I wait until I see the name of "sle_minion", refreshing the page 44s 732ms

And I wait until onboarding is completed for "sle_minion" 38s 237ms

@skip_if_github_validation @sle_minion @scope_salt
Feature:Management of minion keys 8m 28s 514ms 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
1s 991ms 1

Given I am authorized 1s 991ms

Scenario:
Delete SLES minion system profile before exploring the onboarding page
4m 7s 173ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 583ms

When I follow "Delete System" 477ms

Then I should see a "Confirm System Profile Deletion" text 63ms

When I click on "Delete Profile" 69ms

And I wait until I see "has been deleted" text 4m 3s 852ms

And I wait until Salt client is inactive on "sle_minion" 748ms

Then "sle_minion" should not be registered 378ms

Scenario:
Completeness of the onboarding page
170ms 2

When I follow the left menu "Salt > Keys" 144ms

Then I should see a "Keys" text in the content area 25ms

Scenario:
Minion is visible in the Pending section
15s 310ms 8

When I configure salt minion on "sle_minion" 430ms

And I restart salt-minion on "sle_minion" 664ms

And I wait at most 10 seconds until Salt master sees "sle_minion" as "unaccepted" 1s 772ms

And I follow the left menu "Salt > Keys" 91ms

And I refresh page until I see "sle_minion" hostname as text 10s 167ms

Then I should see a "Fingerprint" text 78ms

And I see "sle_minion" fingerprint 2s 31ms

And I should see a "pending" text 73ms

Scenario:
Reject and delete the pending key
18s 920ms 7

And I follow the left menu "Salt > Keys" 63ms

And I reject "sle_minion" from the Pending section 304ms

And I wait at most 10 seconds until Salt master sees "sle_minion" as "rejected" 1s 831ms

Then I should see a "rejected" text 69ms

When I stop salt-minion on "sle_minion" 2s 864ms

And I delete "sle_minion" from the Rejected section 63ms

And I refresh page until I do not see "sle_minion" hostname as text 13s 723ms

Scenario:
Accepted minion shows up as a registered system
1m 41s 264ms 9

When I start salt-minion on "sle_minion" 969ms

And I wait at most 10 seconds until Salt master sees "sle_minion" as "unaccepted" 1s 788ms

Then "sle_minion" should not be registered 348ms

When I follow the left menu "Salt > Keys" 67ms

Then I should see a "pending" text 343ms

When I accept "sle_minion" key 53ms

And I wait at most 10 seconds until Salt master sees "sle_minion" as "accepted" 1s 494ms

And I wait until onboarding is completed for "sle_minion" 1m 35s 870ms

Then "sle_minion" should be registered 328ms

Scenario:
The minion communicates with the Salt master
3s 463ms 3

It took 2 seconds to contact the minion

Then the Salt master can reach "sle_minion" 1s 884ms

When I get OS information of "sle_minion" from the Master 1s 578ms

Then it should contain the OS of "sle_minion" < 1ms

Scenario:
Delete profile of unreacheable minion
16s 775ms 9

Given I am on the Systems overview page of this "sle_minion" 860ms

When I stop salt-minion on "sle_minion" 5s 84ms

And I follow "Delete System" 385ms

Then I should see a "Confirm System Profile Deletion" text 63ms

When I click on "Delete Profile" 69ms

Then I wait until I see "Cleanup timed out. Please check if the machine is reachable." text 7s 687ms

When I click on "Delete Profile Without Cleanup" in "An error occurred during cleanup" modal 2s 113ms

And I wait until I see "has been deleted" text 74ms

Then "sle_minion" should not be registered 437ms

Scenario:
Cleanup: bootstrap again the minion
1m 43s 445ms 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 80ms

When I enter the hostname of "sle_minion" as "hostname" 149ms

And I enter "22" as "port" 56ms

And I enter "root" as "user" 59ms

And I enter "linux" as "password" 63ms

And I select "1-SUSE-KEY-x86_64" from "activationKeys" 79ms

And I select the hostname of "proxy" from "proxies" if present 66ms

And I click on "Bootstrap" 66ms

And I wait until I see "Bootstrap process initiated." text 22s 929ms

And I wait until onboarding is completed for "sle_minion" 1m 19s 810ms

@skip_if_github_validation @scope_salt
Feature:Install a package and a patch on the SUSE client via Salt through the UI 1m 44s 519ms 11

Scenario:
Pre-requisite: enable test_repo_rpm_pool repository on SLE minion
777ms 1

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 777ms

Scenario:
Pre-requisite: install virgo-dummy-1.0 package on SLE minion
1s 721ms 2

When I refresh the metadata for "sle_minion" 905ms

And I install old package "virgo-dummy-1.0" on this "sle_minion" without error control 816ms

Scenario:
Pre-requisite: remove andromeda-dummy package from SLE minion
10s 117ms 4

When I remove package "andromeda-dummy" from this "sle_minion" without error control 1s 327ms

And I refresh the metadata for "sle_minion" 829ms

And I refresh packages list via spacecmd on "sle_minion" 3s 174ms

And I wait until refresh package list on "sle_minion" is finished 4s 785ms

Scenario:
Pre-requisite: refresh package list and check old packages installed on SLE minion
12s 662ms 4

When I refresh packages list via spacecmd on "sle_minion" 2s 214ms

And I wait until refresh package list on "sle_minion" is finished 4s 806ms

Then spacecmd should show packages "virgo-dummy-1.0" installed on "sle_minion" 2s 332ms

And I wait until package "andromeda-dummy-2.0-1.1" is removed from "sle_minion" via spacecmd 3s 309ms

Scenario:
Log in as org admin user
2s 129ms 1

Given I am authorized for the "Admin" section 2s 129ms

Scenario:
Pre-requisite: ensure the errata cache is computed before patching Salt minion
18s 428ms 11

Given I am on the Systems overview page of this "sle_minion" 1s 374ms

When I follow "Software" in the content area 80ms

And I follow "List / Remove" in the content area 69ms

And I enter "virgo-dummy" as the filtered package name 202ms

And I click on the filter button until page does contain "virgo-dummy" text 11s 11ms

When I follow the left menu "Admin > Task Schedules" 134ms

And I follow "errata-cache-default" 1s 252ms

And I follow "errata-cache-bunch" 340ms

And I click on "Single Run Schedule" 1s 280ms

Then I should see a "bunch was scheduled" text 268ms

When I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 2s 413ms

Scenario:
Install a patch on the SLE minion
22s 529ms 12

Given I am on the Systems overview page of this "sle_minion" 850ms

When I follow "Software" in the content area 76ms

And I follow "Patches" in the content area 68ms

And I enter "virgo" as the filtered synopsis 50ms

And I click on the filter button 10s 159ms

And I check "virgo-dummy-3456" in the list 66ms

And I check "allowVendorChange" 83ms

And I click on "Apply Patches" 555ms

And I click on "Confirm" 698ms

Then I should see a "1 patch update has been scheduled for" text 79ms

When I wait for "virgo-dummy-2.0-1.1" to be installed on "sle_minion" 8s 994ms

Then vendor change should be enabled for package actions on "sle_minion" 845ms

Scenario:
Install a package on the SLE minion
13s 406ms 12

Given I am on the Systems overview page of this "sle_minion" 835ms

When I follow "Software" in the content area 70ms

And I follow "Packages" 378ms

And I follow "Install" 566ms

And I enter "andromeda" as the filtered package name 109ms

And I click on the filter button 748ms

And I check "andromeda-dummy-2.0-1.1" in the list 61ms

And I click on "Install Packages" 547ms

And I click on "Confirm" 605ms

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 "sle_minion" 8s 599ms

Then vendor change should be enabled for package actions on "sle_minion" 813ms

Scenario:
Cleanup: disable test_repo_rpm_pool on SLE minion
448ms 1

When I disable repository "test_repo_rpm_pool" on this "sle_minion" 448ms

Scenario:
Cleanup: remove virgo-dummy package from SLE minion
12s 867ms 4

When I remove package "virgo-dummy" from this "sle_minion" without error control 1s 359ms

And I refresh the metadata for "sle_minion" 810ms

And I refresh packages list via spacecmd on "sle_minion" 3s 610ms

And I wait until refresh package list on "sle_minion" is finished 7s 86ms

Scenario:
Cleanup: remove andromeda-dummy package from SLE minion
9s 428ms 4

When I remove package "andromeda-dummy" from this "sle_minion" without error control 1s 677ms

And I refresh the metadata for "sle_minion" 827ms

And I refresh packages list via spacecmd on "sle_minion" 2s 172ms

And I wait until refresh package list on "sle_minion" is finished 4s 751ms

@skip_if_github_validation @sle_minion @scope_content_staging
Feature:Install a package on the SLES minion with staging enabled 6m 53s 790ms 8

Scenario:
Pre-requisite: install virgo-dummy-1.0 package, make sure orion-dummy is not present
3s 627ms 3

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 447ms

And I remove package "orion-dummy" from this "sle_minion" without error control 909ms

And I install package "virgo-dummy-1.0" on this "sle_minion" 2s 270ms

Scenario:
Pre-requisite: refresh package list
9s 524ms 3

When I refresh packages list via spacecmd on "sle_minion" 2s 425ms

And I wait until refresh package list on "sle_minion" is finished 4s 794ms

Then spacecmd should show packages "virgo-dummy-1.0" installed on "sle_minion" 2s 304ms

Scenario:
Log in as admin user
461ms 1

Given I am authorized for the "Admin" section 461ms

Scenario:
Pre-requisite: ensure the errata cache is computed before staging tests
32s 82ms 6

When I follow the left menu "Admin > Task Schedules" 135ms

And I follow "errata-cache-default" 1s 245ms

And I follow "errata-cache-bunch" 344ms

Then I click on "Single Run Schedule" 1s 296ms

And I should see a "bunch was scheduled" text 274ms

Then I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 28s 784ms

Scenario:
Enable content staging
1s 217ms 6

When I follow the left menu "Admin > Organizations" 88ms

And I follow first "SUSE Test" 310ms

And I follow first "Configuration" 222ms

And I check "staging_content_enabled" 93ms

And I click on "Update Organization" 432ms

Then I should see a "was successfully updated." text 69ms

Scenario:
Install package in the future and check for staging
3m 1s 377ms 13

Given I am on the Systems overview page of this "sle_minion" 842ms

When I follow "Software" in the content area 76ms

And I follow "Packages" in the content area 68ms

And I follow "Install" in the content area 83ms

And I enter "orion-dummy-1.1-1.1" as the filtered package name 174ms

And I click on the filter button 739ms

And I check row with "orion-dummy-1.1-1.1" and arch of "sle_minion" 63ms

And I click on "Install Packages" 532ms

And I pick 3 minutes from now as schedule time 96ms

And I click on "Confirm" 800ms

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 24s 476ms

And I wait for "orion-dummy-1.1-1.1" to be installed on "sle_minion" 1m 33s 356ms

Scenario:
Install patch in the future and check for staging
3m 1s 563ms 11

When I follow "Software" in the content area 67ms

And I follow "Patches" in the content area 69ms

And I enter "virgo" as the filtered synopsis 42ms

And I click on the filter button 10s 125ms

And I check "virgo-dummy-3456" in the list 72ms

And I click on "Apply Patches" 544ms

And I pick 3 minutes from now as schedule time 95ms

And I click on "Confirm" 635ms

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 7s 53ms

And I wait for "virgo-dummy-2.0-1.1" to be installed on "sle_minion" 1m 42s 780ms

Scenario:
Cleanup: remove virgo-dummy package from SLES minion
3s 935ms 11

When I follow "Software" in the content area 78ms

And I follow "List / Remove" 651ms

And I enter "orion-dummy" as the filtered package name 150ms

And I click on the filter button 888ms

And I check row with "orion-dummy" and arch of "sle_minion" 69ms

And I enter "virgo-dummy" as the filtered package name 45ms

And I click on the filter button 134ms

And I check "virgo-dummy" in the list 79ms

And I click on "Remove Packages" 539ms

And I click on "Confirm" 724ms

And I disable repository "test_repo_rpm_pool" on this "sle_minion" 573ms

@skip_if_github_validation @scope_salt
Feature:Salt package states 2m 4s 560ms 15

Scenario:
Pre-requisite: install old packages on SLES minion
23s 22ms 6

Salt command: salt uyuni-master-suse-minion.sumaci.aws state.highstate

When I apply highstate on "sle_minion" 15s 844ms

And I enable repository "test_repo_rpm_pool" on this "sle_minion" 789ms

And I refresh the metadata for "sle_minion" 842ms

And I install old package "milkyway-dummy-1.0" on this "sle_minion" without error control 1s 977ms

And I install old package "virgo-dummy-1.0" on this "sle_minion" without error control 2s 20ms

And I install old package "andromeda-dummy-1.0" on this "sle_minion" without error control 1s 549ms

Scenario:
Pre-requisite: refresh package list and check installed packages on SLE minion
14s 121ms 3

When I refresh packages list via spacecmd on "sle_minion" 2s 355ms

And I wait until refresh package list on "sle_minion" is finished 9s 468ms

Then spacecmd should show packages "milkyway-dummy-1.0 virgo-dummy-1.0 andromeda-dummy-1.0" installed on "sle_minion" 2s 298ms

Scenario:
Log in as admin user
902ms 1

Given I am authorized for the "Admin" section 902ms

Scenario:
Pre-requisite: ensure the errata cache is computed before software states tests
7s 511ms 11

Given I am on the Systems overview page of this "sle_minion" 1s 201ms

When I follow "Software" in the content area 78ms

And I follow "List / Remove" in the content area 69ms

And I enter "andromeda-dummy" as the filtered package name 241ms

And I click on the filter button until page does contain "andromeda-dummy-1.0" text 289ms

When I follow the left menu "Admin > Task Schedules" 146ms

And I follow "errata-cache-default" 1s 117ms

And I follow "errata-cache-bunch" 327ms

Then I click on "Single Run Schedule" 1s 562ms

And I should see a "bunch was scheduled" text 274ms

Then I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 2s 202ms

Scenario:
Accepted minion has a base channel
1s 48ms 4

Given I am on the Systems overview page of this "sle_minion" 834ms

When I follow "Software" in the content area 68ms

And I follow "Software Channels" in the content area 70ms

Then the system should have a base channel set 75ms

Scenario:
Remove a package through the UI
9s 477ms 13

When I follow "States" in the content area 72ms

And I follow "Packages" 455ms

And I follow "Search" 68ms

And I should see a "Package States" text 75ms

And I list packages with "dummy" 1s 156ms

And I wait until I see "milkyway-dummy" text 441ms

Then "milkyway-dummy" should be installed on "sle_minion" 720ms

And I change the state of "milkyway-dummy" to "Removed" and "" 65ms

Then I should see a "1 Change" text 97ms

And I click save 55ms

Then I wait until I see "Package states have been saved." text 212ms

And I click apply 51ms

And I wait for "milkyway-dummy" to be uninstalled on "sle_minion" 6s 4ms

Scenario:
Install a package through the UI
12s 399ms 13

When I follow "States" in the content area 66ms

And I follow "Packages" 580ms

And I follow "Search" 60ms

And I should see a "Package States" text 77ms

And I list packages with "dummy" 1s 136ms

And I wait until I see "milkyway-dummy" text 467ms

Then "milkyway-dummy" should not be installed on "sle_minion" 538ms

And I change the state of "milkyway-dummy" to "Installed" and "" 49ms

Then I should see a "1 Change" text 94ms

And I click save 47ms

Then I wait until I see "Package states have been saved." text 217ms

And I click apply 42ms

And I wait for "milkyway-dummy" to be installed on "sle_minion" 9s 19ms

Scenario:
Install an already installed package through the UI
4s 981ms 13

When I follow "States" in the content area 69ms

And I follow "Packages" 513ms

And I follow "Search" 61ms

And I should see a "Package States" text 74ms

And I list packages with "dummy" 1s 140ms

And I wait until I see "virgo-dummy" text 476ms

Then "virgo-dummy-1.0" should be installed on "sle_minion" 780ms

And I change the state of "virgo-dummy" to "Installed" and "Any" 119ms

Then I should see a "1 Change" text 97ms

And I click save 55ms

Then I wait until I see "Package states have been saved." text 242ms

And I click apply 49ms

And I wait for "virgo-dummy-1.0" to be installed on "sle_minion" 1s 299ms

Scenario:
Upgrade a package through the UI
17s 220ms 13

When I follow "States" in the content area 83ms

And I follow "Packages" 444ms

And I follow "Search" 69ms

And I should see a "Package States" text 73ms

And I list packages with "dummy" 1s 154ms

And I wait until I see "andromeda-dummy" text 485ms

Then "andromeda-dummy-1.0" should be installed on "sle_minion" 571ms

And I change the state of "andromeda-dummy" to "Installed" and "Latest" 81ms

Then I should see a "1 Change" text 104ms

And I click save 59ms

Then I wait until I see "Package states have been saved." text 217ms

And I click apply 44ms

And I wait for "andromeda-dummy-2.0-1.1" to be installed on "sle_minion" 13s 831ms

Scenario:
Verify the package states
1s 2ms 6

When I follow "States" in the content area 64ms

And I follow "Packages" 507ms

And I should see a "Package States" text 79ms

And I should see a "milkyway-dummy" text 193ms

And I should see a "andromeda-dummy" text 78ms

And I should see a "virgo-dummy" text 79ms

Scenario:
Use Salt presence mechanism on an active minion
6s 486ms 5

When I follow "States" in the content area 67ms

And I follow "Highstate" in the content area 78ms

And I click on "Show full highstate output" 292ms

And I wait for "6" seconds 6s

And I should see a "pkg_removed" or "running as PID" text in element "highstate" 47ms

Scenario:
Use Salt presence mechanism on an unreachable minion
16s 326ms 6

When I follow "States" in the content area 63ms

And I run "pkill salt-minion" on "sle_minion" without error control 416ms

And I run "pkill python.original" on "sle_minion" without error control 419ms

And I follow "Highstate" in the content area 62ms

And I click on "Show full highstate output" 241ms

And I wait until I see "No reply from minion" text 15s 122ms

Scenario:
Cleanup: restart the salt service on SLES minion
989ms 1

When I restart salt-minion on "sle_minion" 989ms

Scenario:
Cleanup: set the package states as unmanaged
3s 599ms 11

Given I am on the Systems overview page of this "sle_minion" 839ms

When I follow "States" in the content area 88ms

And I follow "Packages" 506ms

And I follow "Search" 69ms

And I should see a "Package States" text 76ms

And I list packages with "dummy" 1s 155ms

And I wait until I see "andromeda-dummy" text 467ms

And I change the state of "virgo-dummy" to "Unmanaged" and "" 84ms

And I change the state of "andromeda-dummy" to "Unmanaged" and "" 48ms

And I click save 52ms

Then I wait until I see "Package states have been saved." text 211ms

Scenario:
Cleanup: remove old packages from SLES minion
5s 471ms 5

When I disable repository "test_repo_rpm_pool" on this "sle_minion" 461ms

And I remove package "milkyway-dummy" from this "sle_minion" without error control 1s 341ms

And I remove package "virgo-dummy" from this "sle_minion" without error control 1s 417ms

And I remove package "andromeda-dummy" from this "sle_minion" without error control 1s 359ms

And I refresh the metadata for "sle_minion" 891ms

@skip_if_github_validation @sle_minion @scope_salt
Feature:Verify that Salt mgrcompat state works when the new module.run syntax is enabled 13m 15s 203ms 10

Scenario:
Log in as org admin user
1s 768ms 1

Given I am authorized 1s 768ms

Scenario:
Remove mgrcompat module from minion synced modules and schedule Hardware Refresh
27s 458ms 8

Given I remove "minion/extmods/states/mgrcompat.py" from salt cache on "sle_minion" 408ms

And I remove "minion/extmods/states/__pycache__/mgrcompat*" from salt cache on "sle_minion" 403ms

And I am on the Systems overview page of this "sle_minion" 955ms

When I follow "Hardware" 531ms

And I click on "Schedule Hardware Refresh" 64ms

Then I should see a "You have successfully scheduled a hardware profile refresh" text 776ms

When I wait until event "Hardware List Refresh scheduled" is completed 22s 128ms

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "sle_minion" 2s 189ms

Scenario:
Remove saltutil grain and mgrcompat module from minion and schedule Hardware Refresh
26s 439ms 10

Given I remove "minion/extmods/states/mgrcompat.py" from salt cache on "sle_minion" 411ms

And I remove "minion/extmods/states/__pycache__/mgrcompat*" from salt cache on "sle_minion" 402ms

And I store "grains: {__suse_reserved_saltutil_states_support: False}" into file "custom_grains.conf" in salt minion config directory on "sle_minion" 405ms

And I refresh salt-minion grains on "sle_minion" 1s 914ms

And I am on the Systems overview page of this "sle_minion" 873ms

When I follow "Hardware" 501ms

And I click on "Schedule Hardware Refresh" 746ms

Then I should see a "You have successfully scheduled a hardware profile refresh" text 123ms

When I wait until event "Hardware List Refresh scheduled" is completed 18s 806ms

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "sle_minion" 2s 254ms

Scenario:
Delete SLES minion system profile before mgrcompat test
4m 6s 76ms 7

Given I am on the Systems overview page of this "sle_minion" 826ms

When I follow "Delete System" 396ms

Then I should see a "Confirm System Profile Deletion" text 63ms

When I click on "Delete Profile" 68ms

And I wait until I see "has been deleted" text 4m 3s 644ms

And I wait until Salt client is inactive on "sle_minion" 740ms

Then "sle_minion" should not be registered 336ms

Scenario:
Enable new module.run syntax on the minion and perform registration
1m 42s 873ms 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" 412ms

When I follow the left menu "Systems > Bootstrapping" 85ms

Then I should see a "Bootstrap Minions" text 77ms

When I enter the hostname of "sle_minion" as "hostname" 159ms

And I enter "22" as "port" 58ms

And I enter "root" as "user" 63ms

And I enter "linux" as "password" 67ms

And I select the hostname of "proxy" from "proxies" if present 84ms

And I click on "Bootstrap" 68ms

And I wait until I see "Bootstrap process initiated." text 22s 885ms

And I wait until onboarding is completed for "sle_minion" 1m 18s 910ms

Scenario:
Check if onboarding for the minion with the new module.run syntax was successful
8s 721ms 3

When I follow the left menu "Systems > System List > All" 145ms

And I wait until I see the name of "sle_minion", refreshing the page 721ms

And I wait until onboarding is completed for "sle_minion" 7s 854ms

Scenario:
Check that installed packages are visible with the new module.run syntax
1s 894ms 4

Given I am on the Systems overview page of this "sle_minion" 872ms

When I follow "Software" in the content area 78ms

And I follow "List / Remove" 820ms

Then I should see a "aaa_base" text 123ms

Scenario:
Check that Hardware Refresh button works on a SLE minion with new module.run syntax
26s 655ms 6

Given I am on the Systems overview page of this "sle_minion" 935ms

And I follow "Hardware" 587ms

And I click on "Schedule Hardware Refresh" 825ms

Then I should see a "You have successfully scheduled a hardware profile refresh" text 115ms

When I wait until event "Hardware List Refresh scheduled" is completed 21s 954ms

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "sle_minion" 2s 235ms

Scenario:
Cleanup: Delete profile of the minion and disable new module.run syntax
4m 7s 44ms 9

Given I am on the Systems overview page of this "sle_minion" 888ms

And I remove "custom_modulerun.conf" from salt minion config directory on "sle_minion" 402ms

And I remove "custom_grains.conf" from salt minion config directory on "sle_minion" 400ms

When I follow "Delete System" 388ms

Then I should see a "Confirm System Profile Deletion" text 66ms

When I click on "Delete Profile" 69ms

And I wait until I see "has been deleted" text 4m 3s 739ms

And I wait until Salt client is inactive on "sle_minion" 749ms

Then "sle_minion" should not be registered 337ms

Scenario:
Cleanup: bootstrap again the minion after mgrcompat tests
1m 46s 271ms 11

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 84ms

Then I should see a "Bootstrap Minions" text 74ms

When I enter the hostname of "sle_minion" as "hostname" 159ms

And I enter "22" as "port" 53ms

And I enter "root" as "user" 60ms

And I enter "linux" as "password" 61ms

And I select "1-SUSE-KEY-x86_64" from "activationKeys" 85ms

And I select the hostname of "proxy" from "proxies" if present 68ms

And I click on "Bootstrap" 65ms

And I wait until I see "Bootstrap process initiated." text 22s 992ms

And I wait until onboarding is completed for "sle_minion" 1m 22s 565ms

@skip_if_github_validation @sle_minion @scope_salt @flaky
Feature:Lock packages on SLES salt minion 3m 41s 814ms 10

Scenario:
Log in as org admin user
2s 100ms 1

Given I am authorized 2s 100ms

Scenario:
Pre-requisite: install packages needed for locking test
4s 161ms 3

When I install package "orion-dummy" on this "sle_minion" 1s 848ms

And I install package "milkyway-dummy" on this "sle_minion" 1s 494ms

And I remove package "hoag-dummy" from this "sle_minion" without error control 818ms

Scenario:
Lock a package on the client
24s 761ms 13

Given I am on the Systems overview page of this "sle_minion" 1s 39ms

When I follow "Software" in the content area 83ms

And I follow "Lock / Unlock" 621ms

And I enter "hoag-dummy-1.1-1.1" as the filtered package name 60ms

And I click on the filter button 644ms

And I check row with "hoag-dummy-1.1-1.1" and arch of "sle_minion" 71ms

And I click on "Lock" 1s 619ms

Then I should see a "Packages has been requested for being locked." text 80ms

When I wait until event "Lock packages scheduled" is completed 18s 895ms

Then "hoag-dummy-1.1-1.1" is locked on "sle_minion" 1s 12ms

When I follow "Software" in the content area 73ms

And I follow "Lock / Unlock" 528ms

Then package "hoag-dummy-1.1-1.1" is reported as locked 29ms

Scenario:
Attempt to install a locked package on the client
28s 619ms 17

Given I am on the Systems overview page of this "sle_minion" 917ms

When I follow "Software" in the content area 67ms

And I follow "Lock / Unlock" 614ms

And package "hoag-dummy-1.1-1.1" is reported as locked 22ms

And I follow "Install" 606ms

And I enter "hoag-dummy-1.1-1.1" as the filtered package name 71ms

And I click on the filter button 652ms

And I check row with "hoag-dummy-1.1-1.1" and arch of "sle_minion" 69ms

And I click on "Install Packages" 616ms

And I click on "Confirm" 773ms

Then I should see a "1 package install has been scheduled for" text 68ms

When I follow "Events" 447ms

And I follow "History" 430ms

And I wait until I see the event "Package Install/Upgrade scheduled" completed during last minute, refreshing the page 23s 97ms

And I follow the event "Package Install/Upgrade scheduled" completed during last minute 63ms

Then the package scheduled is "hoag-dummy-1.1-1.1" 18ms

And the action status is "Failed" 81ms

Scenario:
Unlock a package on the client
34s 53ms 16

Given I am on the Systems overview page of this "sle_minion" 902ms

When I follow "Software" in the content area 79ms

And I follow "Lock / Unlock" 543ms

And package "hoag-dummy-1.1-1.1" is reported as locked 30ms

And I enter "hoag-dummy-1.1-1.1" as the filtered package name 72ms

And I click on the filter button 654ms

And I check row with "hoag-dummy-1.1-1.1" and arch of "sle_minion" 25ms

And I click on "Unlock" 535ms

Then I should see a "Packages has been requested for being unlocked." text 85ms

When I wait until event "Lock packages scheduled" is completed 18s 840ms

Then "hoag-dummy-1.1-1.1" is unlocked on "sle_minion" 957ms

When I follow "Software" in the content area 73ms

And I follow "Lock / Unlock" 528ms

And I enter "hoag-dummy-1.1-1.1" as the filtered package name 69ms

And I click on the filter button 640ms

Then package "hoag-dummy-1.1-1.1" is reported as unlocked 10s 14ms

Scenario:
Schedule a package lock
3s 9

Given I am on the Systems overview page of this "sle_minion" 908ms

When I follow "Software" in the content area 64ms

And I follow "Lock / Unlock" 538ms

And I enter "hoag-dummy-1.1-1.1" as the filtered package name 59ms

And I click on the filter button 625ms

And I check row with "hoag-dummy-1.1-1.1" and arch of "sle_minion" 67ms

And I click on "Lock" 646ms

Then I should see a "Packages has been requested for being locked." text 77ms

And package "hoag-dummy-1.1-1.1" is reported as pending to be locked 12ms

Scenario:
Schedule another package lock
24s 838ms 16

Given I am on the Systems overview page of this "sle_minion" 926ms

When I follow "Software" in the content area 66ms

And I follow "Lock / Unlock" 543ms

And I enter "milkyway-dummy-2.0-1.1" as the filtered package name 61ms

And I click on the filter button 637ms

When I check row with "milkyway-dummy-2.0-1.1" and arch of "sle_minion" 65ms

And I click on "Lock" 1s 327ms

Then I should see a "Packages has been requested for being locked." text 79ms

And package "milkyway-dummy-2.0-1.1" is reported as pending to be locked 12ms

When I wait until event "Lock packages scheduled" is completed 18s 797ms

Then "hoag-dummy-1.1-1.1" is locked on "sle_minion" 975ms

And "milkyway-dummy-2.0-1.1" is locked on "sle_minion" 657ms

When I follow "Software" in the content area 77ms

And I follow "Lock / Unlock" 537ms

Then package "hoag-dummy-1.1-1.1" is reported as locked 35ms

And package "milkyway-dummy-2.0-1.1" is reported as locked 38ms

Scenario:
Mix package locks and unlock events
52s 286ms 32

Given I am on the Systems overview page of this "sle_minion" 907ms

When I follow "Software" in the content area 67ms

And I follow "Lock / Unlock" 540ms

And package "hoag-dummy-1.1-1.1" is reported as locked 24ms

And package "milkyway-dummy-2.0-1.1" is reported as locked 36ms

And I enter "orion-dummy-1.1-1.1" as the filtered package name 65ms

And I click on the filter button 646ms

When I check row with "orion-dummy-1.1-1.1" and arch of "sle_minion" 69ms

And I click on "Lock" 544ms

Then I should see a "Packages has been requested for being locked." text 79ms

And package "orion-dummy-1.1-1.1" is reported as pending to be locked 12ms

When I follow "Lock / Unlock" 539ms

And I enter "hoag-dummy-1.1-1.1" as the filtered package name 85ms

And I click on the filter button 621ms

And I uncheck row with "hoag-dummy-1.1-1.1" and arch of "sle_minion" 68ms

And I enter "milkyway-dummy-2.0-1.1" as the filtered package name 58ms

And I click on the filter button 138ms

And I check row with "milkyway-dummy-2.0-1.1" and arch of "sle_minion" 24ms

And I click on "Unlock" 1s 340ms

Then I should see a "Packages has been requested for being unlocked." text 88ms

And package "milkyway-dummy-2.0-1.1" is reported as pending to be unlocked 12ms

When I wait until event "Lock packages scheduled" is completed 32s 528ms

Then "hoag-dummy-1.1-1.1" is locked on "sle_minion" 1s 2ms

And "milkyway-dummy-2.0-1.1" is unlocked on "sle_minion" 661ms

And "orion-dummy-1.1-1.1" is locked on "sle_minion" 646ms

When I follow "Software" in the content area 78ms

And I follow "Lock / Unlock" 553ms

Then package "hoag-dummy-1.1-1.1" is reported as locked 30ms

And package "orion-dummy-1.1-1.1" is reported as locked 38ms

And I enter "milkyway-dummy-2.0-1.1" as the filtered package name 76ms

And I click on the filter button 675ms

And package "milkyway-dummy-2.0-1.1" is reported as unlocked 10s 19ms

Scenario:
Mix package locks and unlock events part 2
44s 971ms 18

Given I am on the Systems overview page of this "sle_minion" 897ms

And I follow "Software" in the content area 79ms

And I follow "Lock / Unlock" 541ms

When I click on "Select All" 512ms

And I click on "Unlock" 737ms

Then I should see a "Packages has been requested for being unlocked." text 122ms

And only packages "hoag-dummy-1.1-1.1, orion-dummy-1.1-1.1" are reported as pending to be unlocked 39ms

When I wait until event "Lock packages scheduled" is completed 18s 803ms

Then "hoag-dummy-1.1-1.1" is unlocked on "sle_minion" 999ms

And "orion-dummy-1.1-1.1" is unlocked on "sle_minion" 657ms

When I follow "Software" in the content area 78ms

And I follow "Lock / Unlock" 545ms

And I enter "hoag-dummy-1.1-1.1" as the filtered package name 71ms

And I click on the filter button 661ms

Then package "hoag-dummy-1.1-1.1" is reported as unlocked 10s 12ms

And I enter "orion-dummy-1.1-1.1" as the filtered package name 56ms

And I click on the filter button 136ms

And package "orion-dummy-1.1-1.1" is reported as unlocked 10s 17ms

Scenario:
Cleanup: remove packages after testing locks
3s 21ms 2

Then I remove package "orion-dummy" from this "sle_minion" 1s 679ms

And I remove package "milkyway-dummy" from this "sle_minion" 1s 342ms

@scope_onboarding
Feature:Empty minion profile operations 42s 535ms 8

Scenario:
Log in as org admin user
2s 44ms 1

Given I am authorized 2s 44ms

Scenario:
Create an empty minion profile with HW address via API
1s 133ms 1

When I call system.create_system_profile() with name "empty-profile" and HW address "00:11:22:33:44:55" 1s 133ms

Scenario:
Create an empty minion profile with hostname via API
600ms 1

When I call system.create_system_profile() with name "empty-profile-hostname" and hostname "min-retail.mgr.suse.de" 600ms

Scenario:
Check the created empty minion profiles in Unprovisioned Systems page
452ms 4

And I follow the left menu "System > System List > Unprovisioned Systems" 207ms

And I wait until I see "empty-profile" text, refreshing the page 84ms

And I wait until I see "00:11:22:33:44:55" text 79ms

And I wait until I see "empty-profile-hostname" text 80ms

Scenario:
Check the empty profiles has the hostname set
724ms 3

And I follow the left menu "System > System List > Unprovisioned Systems" 79ms

And I follow "empty-profile-hostname" 568ms

Then I wait until I see "min-retail.mgr.suse.de" text, refreshing the page 75ms

Scenario:
Check the empty minion profiles visible via API
364ms 3

When I call system.list_empty_system_profiles() 364ms

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
33s 218ms 7

When I follow the left menu "Systems > System List" 75ms

And I wait until I see the "empty-profile" system, refreshing the page 31s 116ms

And I follow "empty-profile" 597ms

And I follow "Delete System" 428ms

Then I should see a "Confirm System Profile Deletion" text 66ms

When I click on "Delete Profile" 69ms

And I wait until I see "has been deleted" text 866ms

Scenario:
Cleanup: Delete second empty minion profiles
3s 996ms 7

When I follow the left menu "Systems > System List" 80ms

And I wait until I see the "empty-profile-hostname" system, refreshing the page 752ms

And I follow "empty-profile-hostname" 505ms

And I follow "Delete System" 417ms

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 2s 109ms

@scope_onboarding @custom_download_endpoint
Feature:Repos file generation based on custom pillar data 1m 13s 962ms 9 3

Scenario:
Log in as org admin user
1s 818ms 1

Given I am authorized 1s 818ms

@susemanager
Scenario:
Select the channels of the SLES minion
< 1ms 13

Given I am on the Systems overview page of this "sle_minion" 0s

When I follow "Software" in the content area 0s

And I follow "Software Channels" in the content area 0s

And I wait until I do not see "Loading..." text 0s

And I check radio button "SLE-Product-SLES15-SP7-Pool for x86_64" 0s

And I wait until I see "SLE-Module-Basesystem15-SP7-Pool for x86_64" text 0s

And I uncheck "SLE-Module-Basesystem15-SP7-Pool for x86_64" 0s

And I click on "Next" 0s

Then I should see a "Confirm Software Channel Change" text 0s

When I click on "Confirm" 0s

Then I should see a "Changing the channels has been scheduled." text 0s

When I follow "scheduled" in the content area 0s

And I wait until I see "1 system successfully completed this action." text, refreshing the page 0s

@uyuni
Scenario:
Select the channels of the openSUSE minion
19s 440ms 11

Warning: Radio button 'openSUSE Tumbleweed (x86_64)' is already checked

Given I am on the Systems overview page of this "sle_minion" 1s 565ms

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 76ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 222ms

And I click on "Next" 330ms

Then I should see a "Confirm Software Channel Change" text 65ms

When I click on "Confirm" 81ms

Then I should see a "Changing the channels has been scheduled." text 325ms

When I follow "scheduled" in the content area 81ms

And I wait until I see "1 system successfully completed this action." text, refreshing the page 16s 547ms

Scenario:
Check the default RPM download point values
2s 73ms 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" 893ms

Then the susemanager repo file should exist on the "sle_minion" 766ms

And the repo file should contain the normal download endpoint on the "sle_minion" 414ms

Scenario:
Set the custom RPM download point
6s 700ms 5

Given I am on the Systems overview page of this "sle_minion" 870ms

When I install a salt pillar top file for "pkg_endpoint" with target "*" on the server 2s 93ms

And I wait for "1" seconds 1s

And I install the package download endpoint pillar file on the server 643ms

And I refresh the pillar data 2s 91ms

@susemanager
Scenario:
Select the channels of the SLES minion again so new RPM end point will be taken into account
< 1ms 10

When I follow "Software" in the content area 0s

And I follow "Software Channels" in the content area 0s

And I wait until I do not see "Loading..." text 0s

And I wait until I see "SLE-Module-Basesystem15-SP7-Pool for x86_64" text 0s

And I click on "Next" 0s

Then I should see a "Confirm Software Channel Change" text 0s

When I click on "Confirm" 0s

Then I should see a "Changing the channels has been scheduled." text 0s

When I follow "scheduled" in the content area 0s

And I wait until I see "1 system successfully completed this action." text, refreshing the page 0s

@uyuni
Scenario:
Select the channels of the openSUSE minion again so new RPM end point will be taken into account
17s 941ms 10

Warning: Radio button 'openSUSE Tumbleweed (x86_64)' is already checked

When I follow "Software" in the content area 70ms

And I follow "Software Channels" in the content area 71ms

And I wait until I do not see "Loading..." text 75ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 167ms

And I click on "Next" 370ms

Then I should see a "Confirm Software Channel Change" text 82ms

When I click on "Confirm" 78ms

Then I should see a "Changing the channels has been scheduled." text 314ms

When I follow "scheduled" in the content area 91ms

And I wait until I see "1 system successfully completed this action." text, refreshing the page 16s 619ms

Scenario:
Check the channel.repo file to see the custom RPM download point
2s 40ms 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" 884ms

Then the susemanager repo file should exist on the "sle_minion" 750ms

And the repo file should contain the custom download endpoint on the "sle_minion" 405ms

Scenario:
Cleanup: remove the custom RPM download point
4s 827ms 3

When I delete the package download endpoint pillar file from the server 1s 14ms

And I install a salt pillar top file for "disable_local_repos_off, salt_bundle_config" with target "*" on the server 1s 738ms

And I refresh the pillar data 2s 73ms

@susemanager
Scenario:
Cleanup: select the channels of the SLES minion as before
< 1ms 15

When I follow "Software" in the content area 0s

And I follow "Software Channels" in the content area 0s

And I wait until I do not see "Loading..." text 0s

And I check radio button "SLE-Product-SLES15-SP7-Pool for x86_64" 0s

And I wait until I see "SLE15-SP7-Installer-Updates for x86_64" text 0s

And I include the recommended child channels 0s

And I check "SLE-Module-DevTools15-SP7-Pool for x86_64" 0s

And I check "Fake-RPM-SUSE-Channel" 0s

And I check "SLE-Module-Containers15-SP7-Pool for x86_64" 0s

And I click on "Next" 0s

Then I should see a "Confirm Software Channel Change" text 0s

When I click on "Confirm" 0s

Then I should see a "Changing the channels has been scheduled." text 0s

When I follow "scheduled" in the content area 0s

And I wait until I see "1 system successfully completed this action." text, refreshing the page 0s

@uyuni
Scenario:
Cleanup: select the channels of the openSUSE minion as before
17s 982ms 12

Warning: Radio button 'openSUSE Tumbleweed (x86_64)' is already checked

When I follow "Software" in the content area 89ms

And I follow "Software Channels" in the content area 73ms

And I wait until I do not see "Loading..." text 79ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 167ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 348ms

And I check "Fake-RPM-SUSE-Channel" 42ms

And I click on "Next" 66ms

Then I should see a "Confirm Software Channel Change" text 69ms

When I click on "Confirm" 81ms

Then I should see a "Changing the channels has been scheduled." text 316ms

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 16s 569ms

Scenario:
Cleanup: recheck the default RPM download point values
1s 138ms 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" 720ms

And the repo file should contain the normal download endpoint on the "sle_minion" 418ms

@skip_if_github_validation @sle_minion @scope_action_chains @flaky
Feature:Action chains on Salt minions 8m 24s 480ms 33

Scenario:
Log in as admin user
1s 810ms 1

Given I am authorized for the "Admin" section 1s 810ms

Scenario:
Pre-requisite: downgrade repositories to lower version on Salt minion
6s 31ms 6

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 456ms

And I remove package "andromeda-dummy" from this "sle_minion" without error control 799ms

And I remove package "virgo-dummy" from this "sle_minion" without error control 787ms

And I install package "milkyway-dummy" on this "sle_minion" without error control 1s 516ms

And I install old package "andromeda-dummy-1.0" on this "sle_minion" 1s 525ms

And I refresh the metadata for "sle_minion" 945ms

Scenario:
Pre-requisite: refresh package list and check installed packages after downgrade on SLE minion
10s 541ms 3

When I refresh packages list via spacecmd on "sle_minion" 3s 481ms

And I wait until refresh package list on "sle_minion" is finished 4s 771ms

Then spacecmd should show packages "milkyway-dummy andromeda-dummy-1.0" installed on "sle_minion" 2s 288ms

Scenario:
Pre-requisite: wait until downgrade is finished on SLE minion
1s 495ms 5

Given I am on the Systems overview page of this "sle_minion" 851ms

When I follow "Software" in the content area 75ms

And I follow "List / Remove" in the content area 88ms

And I enter "andromeda-dummy" as the filtered package name 190ms

And I click on the filter button until page does contain "andromeda-dummy-1.0" text 289ms

Scenario:
Pre-requisite: ensure the errata cache is computed before testing on Salt minion
51s 908ms 6

When I follow the left menu "Admin > Task Schedules" 150ms

And I follow "errata-cache-default" 1s 115ms

And I follow "errata-cache-bunch" 310ms

And I click on "Single Run Schedule" 1s 570ms

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 48s 485ms

Scenario:
Create a custom action chain for the Salt minion
520ms 3

When I create an action chain with label "salt_minion_action_chain" via API 294ms

And I follow the left menu "Schedule > Action Chains" 158ms

Then I should see a "salt_minion_action_chain" text 67ms

Scenario:
Add a patch installation to the action chain on Salt minion
22s 587ms 10

Given I am on the Systems overview page of this "sle_minion" 800ms

When I follow "Software" in the content area 77ms

And I follow "Patches" in the content area 69ms

And I enter "andromeda" as the filtered synopsis 57ms

And I click on the filter button 10s 174ms

And I check "andromeda-dummy-6789" in the list 66ms

And I click on "Apply Patches" 559ms

And I check radio button "schedule-by-action-chain" 10s 71ms

And I click on "Confirm" 630ms

Then I should see a "Action has been successfully added to the Action Chain" text 81ms

Scenario:
Add a package removal to the action chain on Salt minion
13s 492ms 10

Given I am on the Systems overview page of this "sle_minion" 850ms

When I follow "Software" in the content area 80ms

And I follow "List / Remove" in the content area 95ms

And I enter "milkyway-dummy" as the filtered package name 194ms

And I click on the filter button 857ms

And I check row with "milkyway-dummy" and arch of "sle_minion" 65ms

And I click on "Remove Packages" 654ms

And I check radio button "schedule-by-action-chain" 10s 72ms

And I click on "Confirm" 552ms

Then I should see a "Action has been successfully added to the Action Chain" text 67ms

Scenario:
Add a package installation to an action chain on Salt minion
12s 243ms 9

When I follow "Software" in the content area 75ms

And I follow "Install New Packages" in the content area 70ms

And I enter "virgo-dummy" as the filtered package name 124ms

And I click on the filter button 717ms

And I check "virgo-dummy" in the list 62ms

And I click on "Install Packages" 543ms

And I check radio button "schedule-by-action-chain" 10s 58ms

And I click on "Confirm" 516ms

Then I should see a "Action has been successfully added to the Action Chain" text 75ms

Scenario:
Create a configuration channel for testing action chain on Salt minion
1s 461ms 7

When I follow the left menu "Configuration > Channels" 324ms

And I follow "Create Config Channel" 280ms

And I enter "Action Chain Channel" as "cofName" 74ms

And I enter "actionchainchannel" as "cofLabel" 67ms

And I enter "This is a test channel" as "cofDescription" 72ms

And I click on "Create Config Channel" 575ms

Then I should see a "Action Chain Channel" text 66ms

Scenario:
Add a configuration file to configuration channel for testing action chain on Salt minion
996ms 8

When I follow the left menu "Configuration > Channels" 69ms

And I follow "Action Chain Channel" 310ms

And I follow "Create Configuration File or Directory" 331ms

And I enter "/etc/action-chain.cnf" as "cffPath" 79ms

And I enter "Testchain=YES_PLEASE" in the editor 11ms

And I click on "Create Configuration File" 71ms

Then I should see a "Revision 1 of /etc/action-chain.cnf from channel Action Chain Channel" text 102ms

And I should see a "Update Configuration File" button 19ms

Scenario:
Download the configuration file from configuration channel
1s 941ms 7

When I follow the left menu "Configuration > Channels" 75ms

And I follow "Action Chain Channel" 368ms

And I follow "List/Remove Files" 337ms

And I follow "/etc/action-chain.cnf" 450ms

And I follow "Download File" 193ms

And I wait until file "/tmp/downloads/action-chain.cnf" exists on "localhost" 171ms

Then file "/tmp/downloads/action-chain.cnf" should contain "Testchain=YES_PLEASE" on "localhost" 345ms

Scenario:
Subscribe system to configuration channel for testing action chain on Salt minion
2s 504ms 8

Given I am on the Systems overview page of this "sle_minion" 807ms

When I follow "Configuration" in the content area 81ms

And I follow "Manage Configuration Channels" in the content area 92ms

And I follow first "Subscribe to Channels" in the content area 70ms

And I check "Action Chain Channel" in the list 60ms

And I click on "Continue" 578ms

And I click on "Update Channel Rankings" 733ms

Then I should see a "Channel Subscriptions successfully changed for" text 79ms

Scenario:
Add a configuration file deployment to the action chain on Salt minion
12s 897ms 9

When I follow the left menu "Configuration > Channels" 306ms

And I follow "Action Chain Channel" 393ms

And I follow "Deploy Files" in the content area 73ms

And I click on "Deploy All Files" 559ms

And I check the "sle_minion" client 63ms

And I click on "Confirm & Deploy to Selected Systems" 697ms

And I check radio button "schedule-by-action-chain" 10s 69ms

And I click on "Deploy Files to Selected Systems" 664ms

Then I should see a "Action has been successfully added to the Action Chain" text 69ms

Scenario:
Add apply highstate to action chain on Salt minion
11s 23ms 4

Given I am on the Systems overview page of this "sle_minion" 790ms

When I follow "States" in the content area 85ms

And I check radio button "schedule-by-action-chain" 10s 82ms

And I click on "Apply Highstate" 65ms

Scenario:
Add a reboot action to the action chain on Salt minion
12s 117ms 5

Given I am on the Systems overview page of this "sle_minion" 806ms

When I follow first "Schedule System Reboot" 416ms

And I check radio button "schedule-by-action-chain" 10s 86ms

And I click on "Reboot system" 709ms

Then I should see a "Action has been successfully added to the Action Chain" text 99ms

Scenario:
Add a remote command to the action chain on Salt minion
10s 469ms 6

When I follow "Details" in the content area 83ms

And I follow "Remote Command" in the content area 77ms

And I enter as remote command this script in #!/bin/bash touch /tmp/action_chain_one_system_done 74ms

And I check radio button "schedule-by-action-chain" 10s 82ms

And I click on "Schedule" 65ms

Then I should see a "Action has been successfully added to the Action Chain" text 86ms

Scenario:
Verify the action chain list on Salt minion
1s 521ms 10

When I follow "Schedule" 266ms

And I follow "Action Chains" 283ms

And I follow "salt_minion_action_chain" 319ms

Then I should see a "1. Apply patch(es) andromeda-dummy-6789 on 1 system" text 132ms

And I should see a "2. Remove milkyway-dummy from 1 system" text 84ms

And I should see a "3. Install or update virgo-dummy on 1 system" text 88ms

And I should see a text like "4. Deploy.*/etc/action-chain.cnf.*to 1 system" 83ms

And I should see a "5. Apply Highstate" text 89ms

And I should see a "6. Reboot 1 system" text 88ms

And I should see a "7. Run a remote command on 1 system" text 85ms

Scenario:
Check that a different user cannot see the action chain for Salt minion
2s 809ms 4

Given I am authorized as "testing" with password "testing" 1s 713ms

When I follow "Schedule" 819ms

And I follow "Action Chains" 267ms

Then I should not see a "salt_minion_action_chain" link 8ms

Scenario:
Execute the action chain from the web UI on Salt minion
4m 25s 920ms 9

Given I am authorized for the "Admin" section 1s 712ms

When I am on the Systems overview page of this "sle_minion" 1s 306ms

And I follow "Schedule" 283ms

And I follow "Action Chains" 273ms

And I follow "salt_minion_action_chain" 323ms

And I click on "Save and Schedule" 82ms

Then I should see a "Action Chain salt_minion_action_chain has been scheduled for execution." text 672ms

When I wait for "virgo-dummy" to be installed on "sle_minion" 21s 897ms

And I wait at most 300 seconds until file "/tmp/action_chain_one_system_done" exists on "sle_minion" 3m 59s 368ms

Scenario:
Create a custom action chain for the Salt minion
441ms 3

When I create an action chain with label "salt_minion_action_chain_to_delete" via API 288ms

And I follow the left menu "Schedule > Action Chains" 80ms

Then I should see a "salt_minion_action_chain_to_delete" text 72ms

Scenario:
Add a remote command to the action chain on Salt minion
11s 948ms 6

Given I am on the Systems overview page of this "sle_minion" 809ms

When I follow "Remote Command" 423ms

And I enter as remote command this script in #!/bin/bash uptime 58ms

And I check radio button "schedule-by-action-chain" 10s 92ms

And I click on "Schedule" 470ms

Then I should see a "Action has been successfully added to the Action Chain" text 93ms

Scenario:
Delete the action chain for Salt minion
1s 357ms 5

When I follow "Schedule" 272ms

And I follow "Action Chains" 302ms

And I follow "salt_minion_action_chain_to_delete" 253ms

And I follow "Delete Action Chains" in the content area 110ms

And I click on "Delete" 418ms

Scenario:
Downgrade again repositories to lower version on Salt minion
7s 218ms 4

When I remove package "andromeda-dummy" from this "sle_minion" without error control 2s 227ms

And I remove package "virgo-dummy" from this "sle_minion" without error control 1s 368ms

And I install package "milkyway-dummy" on this "sle_minion" without error control 1s 635ms

And I install old package "andromeda-dummy-1.0" on this "sle_minion" 1s 987ms

Scenario:
Refresh package list and check installed packages after second downgrade on SLE minion
9s 677ms 3

When I refresh packages list via spacecmd on "sle_minion" 2s 678ms

And I wait until refresh package list on "sle_minion" is finished 4s 724ms

Then spacecmd should show packages "milkyway-dummy andromeda-dummy-1.0" installed on "sle_minion" 2s 274ms

Scenario:
Ensure again the errata cache is computed before testing on Salt minion
6s 921ms 6

When I follow the left menu "Admin > Task Schedules" 131ms

And I follow "errata-cache-default" 439ms

And I follow "errata-cache-bunch" 308ms

And I click on "Single Run Schedule" 441ms

Then I should see a "bunch was scheduled" text 278ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 5s 320ms

Scenario:
Add operations to the action chain via API for Salt minions
5s 853ms 11

Running actions:
- Package Install/Upgrade
- Package Removal
- System reboot
- Package Install/Upgrade
- Run an arbitrary script
- Removed "Package Install/Upgrade" action
- Removed "Package Removal" action
- Removed "System reboot" action
- Removed "Package Install/Upgrade" action
- Removed "Run an arbitrary script" action

Given I want to operate on this "sle_minion" 282ms

When I create an action chain with label "salt_minion_api_chain" via API 286ms

And I add a package install to the action chain via API 680ms

And I add a package removal to the action chain via API 634ms

And I add a package upgrade to the action chain via API 695ms

And I add the script "exit 1;" to the action chain via API 340ms

And I add a system reboot to the action chain via API 334ms

Then I should be able to see all these actions in the action chain via API 329ms

When I remove each action within the chain via API 1s 709ms

Then the current action chain should be empty 276ms

And I delete the action chain via API 283ms

Scenario:
Run an action chain via API on Salt minion
7s 727ms 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" 288ms

When I create an action chain with label "salt_minion_multiple_scripts" via API 293ms

And I add the script "echo -n 1 >> /tmp/action_chain.log" to the action chain via API 305ms

And I add the script "echo -n 2 >> /tmp/action_chain.log" to the action chain via API 299ms

And I add the script "echo -n 3 >> /tmp/action_chain.log" to the action chain via API 291ms

And I add the script "touch /tmp/action_chain_done" to the action chain via API 295ms

Then I should be able to see all these actions in the action chain via API 286ms

When I schedule the action chain via API 369ms

And I wait until there are no more action chains listed via API 302ms

And I wait until file "/tmp/action_chain_done" exists on "sle_minion" 3s 873ms

Then file "/tmp/action_chain.log" should contain "123" on "sle_minion" 840ms

When I wait until there are no more scheduled actions listed via API 281ms

Scenario:
Cleanup: remove Salt minion from configuration channel
1s 520ms 6

When I follow the left menu "Configuration > Channels" 361ms

And I follow "Action Chain Channel" 383ms

And I follow "Systems" in the content area 73ms

And I check the "sle_minion" client 86ms

And I click on "Unsubscribe systems" 543ms

Then I should see a "Successfully unsubscribed 1 system(s)." text 71ms

Scenario:
Cleanup: remove configuration channel for Salt minion
815ms 4

When I follow the left menu "Configuration > Channels" 68ms

And I follow "Action Chain Channel" 371ms

And I follow "Delete Channel" 311ms

And I click on "Delete Config Channel" 63ms

Scenario:
Cleanup: remove packages and repository used in action chain for Salt minion
4s 111ms 4

When I remove package "andromeda-dummy" from this "sle_minion" without error control 1s 372ms

And I remove package "virgo-dummy" from this "sle_minion" without error control 783ms

And I remove package "milkyway-dummy" from this "sle_minion" without error control 1s 381ms

And I disable repository "test_repo_rpm_pool" on this "sle_minion" without error control 573ms

Scenario:
Cleanup: remove temporary files for testing action chains on Salt minion
2s 413ms 4

When I run "rm -f /tmp/action_chain.log" on "sle_minion" without error control 516ms

And I run "rm -f /tmp/action_chain_done" on "sle_minion" without error control 698ms

And I run "rm -f /etc/action-chain.cnf" on "sle_minion" without error control 638ms

And I run "rm -f /tmp/action_chain_one_system_done" on "sle_minion" without error control 560ms

Scenario:
Cleanup: remove downloaded files
178ms 1

When I run "rm -f /tmp/downloads/action-chain.cnf" on "localhost" without error control 178ms

@skip_if_github_validation @ssh_minion @scope_action_chains @scope_salt_ssh
Feature:Salt SSH action chain 10m 2s 3ms 30

Scenario:
Log in as org admin user
439ms 1

Given I am authorized for the "Admin" section 439ms

Scenario:
Pre-requisite: downgrade repositories to lower version on SSH minion
6s 404ms 6

When I enable repository "test_repo_rpm_pool" on this "ssh_minion" 788ms

And I remove package "andromeda-dummy" from this "ssh_minion" without error control 1s 173ms

And I remove package "virgo-dummy" from this "ssh_minion" without error control 1s 184ms

And I install package "milkyway-dummy" on this "ssh_minion" without error control 1s 165ms

And I install old package "andromeda-dummy-1.0" on this "ssh_minion" 1s 278ms

And I refresh the metadata for "ssh_minion" 815ms

Scenario:
Pre-requisite: refresh package list and check newly installed packages on SSH minion
26s 119ms 3

When I refresh packages list via spacecmd on "ssh_minion" 2s 627ms

And I wait until refresh package list on "ssh_minion" is finished 21s 110ms

Then spacecmd should show packages "milkyway-dummy andromeda-dummy-1.0" installed on "ssh_minion" 2s 380ms

Scenario:
Pre-requisite: wait until downgrade is finished on SSH minion
1s 721ms 5

Given I am on the Systems overview page of this "ssh_minion" 1s 33ms

When I follow "Software" in the content area 73ms

And I follow "List / Remove" in the content area 74ms

And I enter "andromeda-dummy" as the filtered package name 243ms

And I click on the filter button until page does contain "andromeda-dummy-1.0" text 296ms

Scenario:
Pre-requisite: ensure the errata cache is computed before testing on SSH minion
6s 756ms 6

When I follow the left menu "Admin > Task Schedules" 149ms

And I follow "errata-cache-default" 1s 261ms

And I follow "errata-cache-bunch" 1s 239ms

And I click on "Single Run Schedule" 1s 309ms

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 522ms

Scenario:
Create a custom action chain for the SSH minion
520ms 3

When I create an action chain with label "minssh_action_chain" via API 301ms

And I follow the left menu "Schedule > Action Chains" 145ms

Then I wait until I see "minssh_action_chain" text 73ms

Scenario:
Add a patch installation to the action chain on SSH minion
22s 493ms 10

Given I am on the Systems overview page of this "ssh_minion" 841ms

When I follow "Software" in the content area 67ms

And I follow "Patches" in the content area 70ms

And I enter "andromeda" as the filtered synopsis 49ms

And I click on the filter button 10s 129ms

And I check "andromeda-dummy-6789" in the list 66ms

And I click on "Apply Patches" 558ms

And I check radio button "schedule-by-action-chain" 10s 80ms

And I click on "Confirm" 545ms

Then I should see a "Action has been successfully added to the Action Chain" text 84ms

Scenario:
Add a package removal to the action chain on SSH minion
12s 617ms 9

When I follow "Software" in the content area 79ms

And I follow "List / Remove" in the content area 69ms

And I enter "milkyway-dummy" as the filtered package name 219ms

And I click on the filter button 882ms

And I check row with "milkyway-dummy" and arch of "ssh_minion" 66ms

And I click on "Remove Packages" 633ms

And I check radio button "schedule-by-action-chain" 10s 57ms

And I click on "Confirm" 527ms

Then I should see a "Action has been successfully added to the Action Chain" text 80ms

Scenario:
Add a package installation to an action chain on SSH minion
12s 159ms 9

When I follow "Software" in the content area 73ms

And I follow "Install New Packages" in the content area 70ms

And I enter "virgo-dummy" as the filtered package name 97ms

And I click on the filter button 652ms

And I check "virgo-dummy" in the list 61ms

And I click on "Install Packages" 535ms

And I check radio button "schedule-by-action-chain" 10s 75ms

And I click on "Confirm" 526ms

Then I should see a "Action has been successfully added to the Action Chain" text 67ms

Scenario:
Create a configuration channel for testing action chain on SSH minion
960ms 7

When I follow the left menu "Configuration > Channels" 315ms

And I follow "Create Config Channel" 297ms

And I enter "Action Chain Channel" as "cofName" 73ms

And I enter "actionchainchannel" as "cofLabel" 69ms

And I enter "This is a test channel" as "cofDescription" 70ms

And I click on "Create Config Channel" 66ms

Then I should see a "Action Chain Channel" text 67ms

Scenario:
Add a configuration file to configuration channel for testing action chain on SSH minion
1s 108ms 8

When I follow the left menu "Configuration > Channels" 67ms

And I follow "Action Chain Channel" 386ms

And I follow "Create Configuration File or Directory" 379ms

And I enter "/etc/action-chain.cnf" as "cffPath" 77ms

And I enter "Testchain=YES_PLEASE" in the editor 5ms

And I click on "Create Configuration File" 72ms

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 20ms

Scenario:
Subscribe system to configuration channel for testing action chain on SSH minion
2s 624ms 8

Given I am on the Systems overview page of this "ssh_minion" 914ms

When I follow "Configuration" in the content area 77ms

And I follow "Manage Configuration Channels" in the content area 77ms

And I follow first "Subscribe to Channels" in the content area 69ms

And I check "Action Chain Channel" in the list 59ms

And I click on "Continue" 582ms

And I click on "Update Channel Rankings" 760ms

Then I should see a "Channel Subscriptions successfully changed for" text 84ms

Scenario:
Add a configuration file deployment to the action chain on SSH minion
12s 983ms 9

When I follow the left menu "Configuration > Channels" 319ms

And I follow "Action Chain Channel" 397ms

And I follow "Deploy Files" in the content area 70ms

And I click on "Deploy All Files" 671ms

And I check the "ssh_minion" client 62ms

And I click on "Confirm & Deploy to Selected Systems" 672ms

And I check radio button "schedule-by-action-chain" 10s 58ms

And I click on "Deploy Files to Selected Systems" 655ms

Then I should see a "Action has been successfully added to the Action Chain" text 76ms

Scenario:
Add apply highstate to action chain on SSH minion
11s 122ms 4

Given I am on the Systems overview page of this "ssh_minion" 913ms

When I follow "States" in the content area 73ms

And I check radio button "schedule-by-action-chain" 10s 71ms

And I click on "Apply Highstate" 64ms

Scenario:
Add a reboot action to the action chain on SSH minion
12s 204ms 5

Given I am on the Systems overview page of this "ssh_minion" 844ms

When I follow first "Schedule System Reboot" 417ms

And I check radio button "schedule-by-action-chain" 10s 67ms

And I click on "Reboot system" 779ms

Then I should see a "Action has been successfully added to the Action Chain" text 94ms

Scenario:
Add a remote command to the action chain on SSH minion
10s 863ms 6

When I follow "Details" in the content area 85ms

When I follow "Remote Command" in the content area 73ms

And I enter as remote command this script in #!/bin/bash touch /tmp/action_chain_one_system_done 75ms

And I check radio button "schedule-by-action-chain" 10s 78ms

And I click on "Schedule" 463ms

Then I should see a "Action has been successfully added to the Action Chain" text 87ms

Scenario:
Verify the action chain list on SSH minion
1s 29ms 9

When I follow the left menu "Schedule > Action Chains" 137ms

And I follow "minssh_action_chain" 274ms

Then I should see a "1. Apply patch(es) andromeda-dummy-6789 on 1 system" text 88ms

And I should see a "2. Remove milkyway-dummy from 1 system" text 83ms

And I should see a "3. Install or update virgo-dummy on 1 system" text 92ms

And I should see a text like "4. Deploy.*/etc/action-chain.cnf.*to 1 system" 90ms

And I should see a "5. Apply Highstate" text 91ms

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 89ms

Scenario:
Check that a different user cannot see the action chain for SSH minion
1s 784ms 3

Given I am authorized as "testing" with password "testing" 1s 642ms

When I follow the left menu "Schedule > Action Chains" 113ms

Then I should not see a "minssh_action_chain" link 28ms

Scenario:
Execute the action chain from the web UI on SSH minion
2s 880ms 6

Given I am authorized for the "Admin" section 1s 685ms

When I follow the left menu "Schedule > Action Chains" 109ms

And I wait until I see "minssh_action_chain" text 93ms

And I follow "minssh_action_chain" 241ms

Then I click on "Save and Schedule" 65ms

And I should see a "Action Chain minssh_action_chain has been scheduled for execution." text 684ms

Scenario:
Verify that the action chain was executed successfully
5m 16s 965ms 2

When I wait for "virgo-dummy" to be installed on "ssh_minion" 46s 341ms

And I wait at most 300 seconds until file "/tmp/action_chain_one_system_done" exists on "ssh_minion" 4m 30s 623ms

Scenario:
Create a custom action chain for the SSH minion
466ms 3

When I create an action chain with label "minssh_action_chain_to_delete" via API 318ms

And I follow the left menu "Schedule > Action Chains" 72ms

Then I should see a "minssh_action_chain_to_delete" text 76ms

Scenario:
Add a remote command to the action chain on SSH minion
12s 392ms 6

Given I am on the Systems overview page of this "ssh_minion" 1s 116ms

When I follow "Remote Command" 516ms

And I enter as remote command this script in #!/bin/bash uptime 60ms

And I check radio button "schedule-by-action-chain" 10s 84ms

And I click on "Schedule" 519ms

Then I should see a "Action has been successfully added to the Action Chain" text 95ms

Scenario:
Delete the action chain for SSH minion
1s 30ms 4

When I follow the left menu "Schedule > Action Chains" 147ms

And I follow "minssh_action_chain_to_delete" 324ms

And I follow "Delete Action Chains" in the content area 97ms

Then I click on "Delete" 462ms

Scenario:
Cleanup: roll back action chain effects on SSH minion
1m 22s 699ms 21

Given I am on the Systems overview page of this "ssh_minion" 1s 1ms

When I run "rm /tmp/action_chain_done" on "ssh_minion" without error control 419ms

And I enable repository "test_repo_rpm_pool" on this "ssh_minion" 511ms

And I remove package "andromeda-dummy" from this "ssh_minion" without error control 1s 704ms

And I remove package "virgo-dummy" from this "ssh_minion" without error control 1s 156ms

And I install package "milkyway-dummy" on this "ssh_minion" without error control 1s 359ms

And I install old package "andromeda-dummy-1.0" on this "ssh_minion" 1s 227ms

And I follow "Software" in the content area 74ms

And I click on "Update Package List" 507ms

And I follow "Events" in the content area 77ms

And I wait until I do not see "Package List Refresh scheduled" text, refreshing the page 24s 396ms

And I follow "Software" in the content area 88ms

And I follow "List / Remove" in the content area 74ms

And I enter "andromeda-dummy" as the filtered package name 204ms

And I click on the filter button until page does contain "andromeda-dummy-1.0" text 292ms

When I follow the left menu "Admin > Task Schedules" 161ms

And I follow "errata-cache-default" 1s 239ms

And I follow "errata-cache-bunch" 1s 248ms

And I click on "Single Run Schedule" 1s 299ms

Then I should see a "bunch was scheduled" text 298ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 45s 353ms

Scenario:
Add operations to the action chain via API for SSH minions
5s 169ms 10

Running actions:
- Package Install/Upgrade
- Run an arbitrary script
- Package Install/Upgrade
- Package Removal
- Removed "Package Install/Upgrade" action
- Removed "Run an arbitrary script" action
- Removed "Package Install/Upgrade" action
- Removed "Package Removal" action

Given I want to operate on this "ssh_minion" 295ms

When I create an action chain with label "minssh_api_chain" via API 296ms

And I add a package install to the action chain via API 676ms

And I add a package removal to the action chain via API 648ms

And I add a package upgrade to the action chain via API 673ms

And I add the script "exit 1;" to the action chain via API 308ms

Then I should be able to see all these actions in the action chain via API 282ms

When I remove each action within the chain via API 1s 433ms

Then the current action chain should be empty 276ms

And I delete the action chain via API 279ms

Scenario:
Run an action chain via API on SSH minion
28s 447ms 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" 285ms

When I create an action chain with label "minssh_multiple_scripts" via API 281ms

And I add the script "echo -n 1 >> /tmp/action_chain.log" to the action chain via API 301ms

And I add the script "echo -n 2 >> /tmp/action_chain.log" to the action chain via API 290ms

And I add the script "echo -n 3 >> /tmp/action_chain.log" to the action chain via API 345ms

And I add the script "touch /tmp/action_chain_done" to the action chain via API 304ms

Then I should be able to see all these actions in the action chain via API 287ms

When I schedule the action chain via API 347ms

Then I wait until there are no more action chains listed via API 307ms

When I wait until file "/tmp/action_chain_done" exists on "ssh_minion" 24s 558ms

Then file "/tmp/action_chain.log" should contain "123" on "ssh_minion" 833ms

When I wait until there are no more scheduled actions listed via API 304ms

Scenario:
Cleanup: remove SSH minion from configuration channel
1s 500ms 6

When I follow the left menu "Configuration > Channels" 385ms

And I follow "Action Chain Channel" 378ms

And I follow "Systems" in the content area 75ms

And I check the "ssh_minion" client 70ms

And I click on "Unsubscribe systems" 524ms

Then I should see a "Successfully unsubscribed 1 system(s)." text 65ms

Scenario:
Cleanup: remove configuration channel for SSH minion
1s 139ms 4

When I follow the left menu "Configuration > Channels" 66ms

And I follow "Action Chain Channel" 377ms

And I follow "Delete Channel" 242ms

And I click on "Delete Config Channel" 452ms

Scenario:
Cleanup: remove packages and repository used in action chain for SSH minion
3s 758ms 4

When I remove package "andromeda-dummy" from this "ssh_minion" without error control 1s 190ms

And I remove package "virgo-dummy" from this "ssh_minion" without error control 863ms

And I remove package "milkyway-dummy" from this "ssh_minion" without error control 1s 243ms

And I disable repository "test_repo_rpm_pool" on this "ssh_minion" without error control 461ms

Scenario:
Cleanup: remove temporary files for testing action chains on SSH minion
1s 637ms 4

When I run "rm -f /tmp/action_chain.log" on "ssh_minion" without error control 426ms

And I run "rm -f /tmp/action_chain_done" on "ssh_minion" without error control 406ms

And I run "rm -f /etc/action-chain.cnf" on "ssh_minion" without error control 398ms

And I run "rm -f /tmp/action_chain_one_system_done" on "ssh_minion" without error control 405ms

@skip_if_github_validation @ssh_minion @sle_minion @scope_action_chains
Feature:Action chains on several systems at once 2m 30s 331ms 12

Scenario:
Log in as admin user
434ms 1

Given I am authorized for the "Admin" section 434ms

Scenario:
Pre-requisite: downgrade packages before action chain test on several systems
7s 494ms 8

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 786ms

And I enable repository "test_repo_rpm_pool" on this "ssh_minion" 459ms

And I remove package "andromeda-dummy" from this "ssh_minion" without error control 796ms

And I remove package "andromeda-dummy" from this "sle_minion" without error control 783ms

And I install package "andromeda-dummy-1.0" on this "sle_minion" 1s 805ms

And I install package "andromeda-dummy-1.0" on this "ssh_minion" 1s 211ms

And I refresh the metadata for "sle_minion" 851ms

And I refresh the metadata for "ssh_minion" 799ms

Scenario:
Pre-requisite: refresh package list and check installed packages before action chain test on several systems
37s 923ms 6

When I refresh packages list via spacecmd on "sle_minion" 3s 15ms

And I wait until refresh package list on "sle_minion" is finished 7s 159ms

Then spacecmd should show packages "andromeda-dummy-1.0" installed on "sle_minion" 2s 295ms

When I refresh packages list via spacecmd on "ssh_minion" 2s 212ms

And I wait until refresh package list on "ssh_minion" is finished 20s 961ms

Then spacecmd should show packages "andromeda-dummy-1.0" installed on "ssh_minion" 2s 278ms

Scenario:
Pre-requisite: wait until downgrade is finished before action chain test on several systems
1s 485ms 5

Given I am on the Systems overview page of this "sle_minion" 862ms

When I follow "Software" in the content area 79ms

And I follow "List / Remove" in the content area 71ms

And I enter "andromeda-dummy" as the filtered package name 185ms

And I click on the filter button until page does contain "andromeda-dummy-1.0" text 288ms

Scenario:
Pre-requisite: ensure the errata cache is computed before action chain test on several systems
34s 195ms 13

When I follow the left menu "Admin > Task Schedules" 145ms

And I follow "errata-cache-default" 1s 118ms

And I follow "errata-cache-bunch" 1s 379ms

And I click on "Single Run Schedule" 1s 319ms

Then I should see a "bunch was scheduled" text 281ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 22s 241ms

Given I am on the Systems overview page of this "ssh_minion" 833ms

When I follow the left menu "Admin > Task Schedules" 141ms

And I follow "errata-cache-default" 1s 356ms

And I follow "errata-cache-bunch" 1s 293ms

And I click on "Single Run Schedule" 1s 301ms

Then I should see a "bunch was scheduled" text 281ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 2s 502ms

Scenario:
Create a custom action chain for two systems
497ms 3

When I create an action chain with label "two_systems_action_chain" via API 275ms

And I follow the left menu "Schedule > Action Chains" 145ms

Then I should see a "two_systems_action_chain" text 76ms

Scenario:
Add an action chain using system set manager for SSH minion and SLE minion
24s 43ms 22

When I follow the left menu "Systems > System List > All" 198ms

And I check the "sle_minion" client 496ms

And I check the "ssh_minion" client 67ms

And I follow the left menu "Systems > System Set Manager > Overview" 418ms

And I follow "Install" in the content area 79ms

And I follow "Fake-RPM-SUSE-Channel" in the content area 73ms

And I enter "andromeda-dummy" as the filtered package name 80ms

And I click on the filter button 433ms

And I check "andromeda-dummy" in the list 63ms

And I click on "Install Packages" 346ms

Then I should see "sle_minion" hostname 77ms

And I should see "ssh_minion" hostname 78ms

When I check radio button "schedule-by-action-chain" 10s 85ms

And I click on "Confirm" 428ms

Then I should see a "Package installations are being scheduled" text 67ms

When I follow the left menu "Systems > System Set Manager > Overview" 73ms

And I follow "remote commands" in the content area 73ms

And I enter as remote command this script in #!/bin/bash touch /tmp/action_chain_done 69ms

And I check radio button "schedule-by-action-chain" 10s 69ms

And I click on "Schedule" 572ms

Then I should see "sle_minion" hostname 96ms

And I should see "ssh_minion" hostname 90ms

Scenario:
Verify action chain for two systems
2s 679ms 8

Given I am on the Systems overview page of this "sle_minion" 826ms

When I follow "Schedule" 289ms

And I follow "Action Chains" 327ms

And I follow "two_systems_action_chain" 317ms

And I should see a "1. Install or update andromeda-dummy on 2 systems" text 74ms

And I should see a "2. Run a remote command on 2 systems" text 77ms

And I click on "Save and Schedule" 64ms

Then I should see a "Action Chain two_systems_action_chain has been scheduled for execution." text 702ms

Scenario:
Verify that the action chain from the system set manager was executed successfully
36s 786ms 4

When I wait until file "/tmp/action_chain_done" exists on "ssh_minion" 35s 141ms

And I wait until file "/tmp/action_chain_done" exists on "sle_minion" 801ms

Then "andromeda-dummy" should be installed on "ssh_minion" 423ms

And "andromeda-dummy" should be installed on "sle_minion" 419ms

Scenario:
Cleanup: remove package and repository used in action chain for several systems
3s 841ms 4

When I remove package "andromeda-dummy" from this "sle_minion" without error control 1s 344ms

And I remove package "andromeda-dummy" from this "ssh_minion" without error control 1s 406ms

And I disable repository "test_repo_rpm_pool" on this "sle_minion" without error control 449ms

And I disable repository "test_repo_rpm_pool" on this "ssh_minion" without error control 641ms

Scenario:
Cleanup: remove temporary files for testing action chains on several systems
872ms 2

When I run "rm /tmp/action_chain_done" on "sle_minion" without error control 409ms

And I run "rm /tmp/action_chain_done" on "ssh_minion" without error control 463ms

Scenario:
Cleanup: remove remaining systems from SSM after action chain tests on several systems
74ms 1

When I click on the clear SSM button 74ms

@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 58s 394ms 31 1

Scenario:
Log in as admin user
445ms 1

Given I am authorized for the "Admin" section 445ms

Scenario:
Create an IP forwarding config state channel
2s 110ms 10

When I follow the left menu "Configuration > Channels" 752ms

And I follow "Create State Channel" 243ms

And I wait until I see "New Config State Channel" text 70ms

And I enter "My State Channel for Recurring Actions" as "cofName" 98ms

And I enter "statechannel-recurring" as "cofLabel" 72ms

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 9ms

And I click on "Create Config State Channel" 616ms

Then I wait until I see "Channel Properties" text 76ms

And I wait until I see "My State Channel for Recurring Actions" text 72ms

Scenario:
Enable IP forwarding through a custom state recurring action
48s 959ms 21

Execution time: 13:22

When I am on the "Recurring Actions" page of this "sle_minion" 915ms

Then I should see a "No schedules created. Use Create to add a schedule" text 70ms

When I click on "Create" 99ms

And I wait until I see "Action Type" text 95ms

And I enter "IP forwarding custom state recurring action" as "scheduleName" 289ms

And I select "Custom state" from "actionTypeDescription" 1s 149ms

And I wait until I see "Configure states to execute" text 108ms

And I check radio button "schedule-daily" 10s 91ms

And I enter 1 minutes from now as "time-daily_time" 111ms

And I check "statechannel-recurring-cbox" 97ms

And I click on "Save Changes" 75ms

And I wait until I see "Edit State Ranks" text 108ms

And I click on "Confirm" 107ms

And I click on "Create Schedule" 79ms

Then I wait until I see "Schedule successfully created" text 268ms

And I should see a "IP forwarding custom state recurring action" text 182ms

And I should see a "Minion" text 75ms

When I follow "Events" 367ms

And I follow "History" 415ms

Then I wait at most 420 seconds until event "Apply recurring states [manager_org_1.statechannel-recurring] schedule" is completed 33s 56ms

And file "/proc/sys/net/ipv4/conf/all/forwarding" should contain "1" on "sle_minion" 1s 194ms

Scenario:
Edit the IP forwarding custom state recurring action
1m 624ms 19

Execution time: 13:23

When I am on the "Recurring Actions" page of this "sle_minion" 865ms

Then I should see a "IP forwarding custom state recurring action" text 189ms

When I click the "IP forwarding custom state recurring action" item edit button 72ms

And I wait until I see "Update Schedule" text 231ms

And I enter "custom_state_schedule_name_changed" as "scheduleName" 629ms

And I enter 1 minutes from now as "time-daily_time" 110ms

And I uncheck "statechannel-recurring-cbox" 10s 105ms

And I check "Sync States-cbox" 87ms

And I click on "Save Changes" 68ms

And I wait until I see "Edit State Ranks" text 98ms

And I click on "Confirm" 83ms

And I click on "Update Schedule" 68ms

Then I wait until I see "Schedule successfully updated" text 461ms

And I should see a "custom_state_schedule_name_changed" text 74ms

And I should see a "Minion" text 73ms

When I follow "Events" 311ms

And I follow "History" 432ms

Then I wait at most 420 seconds until event "Apply recurring states [util.syncstates] scheduled" is completed 46s 588ms

And I wait until I see "SLS: util.syncstates" text 71ms

@skip_if_github_validation
Scenario:
Cleanup: Disable IP forwarding
13s 858ms 9

When I follow the left menu "Salt > Remote Commands" 133ms

Then I should see a "Remote Commands" text in the content area 26ms

When I enter command "echo 0 > /proc/sys/net/ipv4/conf/all/forwarding" 139ms

And I enter target "sle_minion" 109ms

And I click on preview 11s 353ms

And I click on run 53ms

Then I should see "sle_minion" hostname 60ms

And I wait until I see "show response" text 828ms

And file "/proc/sys/net/ipv4/conf/all/forwarding" should contain "0" on "sle_minion" 1s 154ms

Scenario:
Cleanup: Delete the minion Custom state Recurring Action
1s 675ms 6

When I am on the "Recurring Actions" page of this "sle_minion" 967ms

Then I should see a "custom_state_schedule_name_changed" text 285ms

When I click the "custom_state_schedule_name_changed" item delete button 82ms

And I wait until I see "Delete Recurring Action Schedule" text 73ms

And I click on the red confirmation button 72ms

Then I wait until I see "Schedule 'custom_state_schedule_name_changed' has been deleted." text 193ms

Scenario:
Create a minion Highstate Recurring Action
48s 626ms 16

Execution time: 13:24

When I am on the "Recurring Actions" page of this "sle_minion" 840ms

Then I should see a "No schedules created. Use Create to add a schedule" text 69ms

When I click on "Create" 103ms

And I wait until I see "Schedule Name" text 99ms

And I enter "Minion Highstate Recurring Action" as "scheduleName" 252ms

And I select "Highstate" from "actionTypeDescription" 1s 138ms

And I check radio button "schedule-daily" 10s 70ms

And I enter 1 minutes from now as "time-daily_time" 100ms

And I click on the "disabled" toggler 59ms

And I click on "Create Schedule" 64ms

Then I wait until I see "Schedule successfully created" text 261ms

And I should see a "Minion Highstate Recurring Action" text 75ms

And I should see a "Minion" text 77ms

When I follow "Events" 363ms

And I follow "History" 410ms

And I wait until I see the event "Apply highstate in test-mode scheduled" completed during last minute, refreshing the page 34s 637ms

Scenario:
Edit the minion Highstate Recurring Action
13s 766ms 13

When I am on the "Recurring Actions" page of this "sle_minion" 822ms

Then I should see a "Minion Highstate Recurring Action" text 264ms

When I click the "Minion Highstate Recurring Action" item edit button 71ms

And I wait until I see "Update Schedule" text 221ms

And I enter "schedule_name_minion" as "scheduleName" 376ms

And I check radio button "schedule-weekly" 10s 89ms

And I select "Wednesday" from "date_weekly" 1s 137ms

And I enter "01:35" as "time-weekly_time" 100ms

And I click on "Update Schedule" 66ms

Then I wait until I see "Schedule successfully updated" text 376ms

And I should see a "schedule_name_minion" text 77ms

And I should see a "Minion" text 78ms

And I should see a "0 35 1 ? * 4" text 83ms

Scenario:
View the minion Highstate Recurring Action details
1s 633ms 6

When I am on the "Recurring Actions" page of this "sle_minion" 853ms

Then I should see a "schedule_name_minion" text 283ms

When I click the "schedule_name_minion" item details button 68ms

Then I should see a "Every Wednesday at 01:35" text 295ms

When I click on "Back" 66ms

Then I should see a "Schedules" text 65ms

Scenario:
Create a System group for testing
3s 409ms 11

When I follow the left menu "Systems > System Groups" 108ms

And I follow "Create Group" 294ms

And I enter "Recurring-Action-test-group" as "name" 75ms

And I enter "This is for testing" as "description" 64ms

And I click on "Create Group" 424ms

Then I should see a "System group Recurring-Action-test-group created." text 75ms

When I am on the "Groups" page of this "sle_minion" 909ms

And I follow first "Join" 380ms

And I check the first row in the list 77ms

And I click on "Join Groups" 924ms

Then I wait until I see "1 system groups added" text 74ms

Scenario:
Pre-requisite: subscribe system to Fake Channel
31s 236ms 12

Given I am on the Systems overview page of this "sle_minion" 842ms

When I follow "Software" in the content area 75ms

And I follow "Software Channels" in the content area 68ms

And I wait until I do not see "Loading..." text 75ms

And I check radio button "Fake-Base-Channel-SUSE-like" 10s 69ms

And I wait until I do not see "Loading..." text 448ms

And I check "Fake-Child-Channel-SUSE-like" 106ms

And I click on "Next" 62ms

Then I should see a "Confirm Software Channel Change" text 68ms

When I click on "Confirm" 78ms

Then I should see a "Changing the channels has been scheduled." text 297ms

And I wait until event "Subscribe channels scheduled" is completed 19s 44ms

@skip_if_github_validation
Scenario:
Pre-requisite: downgrade milkyway-dummy to lower version
1m 42s 636ms 9

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 787ms

And I install old package "milkyway-dummy-1.0" on this "sle_minion" 2s 55ms

And I refresh the metadata for "sle_minion" 805ms

And I follow the left menu "Admin > Task Schedules" 120ms

And I follow "errata-cache-default" 1s 288ms

And I follow "errata-cache-bunch" 1s 324ms

And I click on "Single Run Schedule" 1s 248ms

Then I should see a "bunch was scheduled" text 278ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 1m 34s 727ms

Scenario:
Pre-requisite: check that there are updates available
854ms 2

Given I am on the Systems overview page of this "sle_minion" 759ms

And I wait until I see "Software Updates Available" text, refreshing the page 95ms

Scenario:
Create a recurring action to apply "uptodate" state to a system group
1m 24s 401ms 24

Execution time: 13:28

When I follow the left menu "Systems > System Groups" 78ms

And I follow "Recurring-Action-test-group" 227ms

And I follow "Recurring Actions" in the content area 66ms

Then I should see a "No schedules created. Use Create to add a schedule" text 64ms

When I click on "Create" 91ms

And I wait until I see "Schedule Name" text 94ms

And I enter "Recurring action to keep Recurring-Action-test-group uptodate" as "scheduleName" 358ms

And I select "Custom state" from "actionTypeDescription" 1s 131ms

And I wait until I see "Configure states to execute" text 109ms

And I check radio button "schedule-daily" 10s 84ms

And I enter 1 minutes from now as "time-daily_time" 97ms

And I check "Update System-cbox" 84ms

And I click on "Save Changes" 65ms

And I wait until I see "Edit State Ranks" text 95ms

And I click on "Confirm" 73ms

And I click on "Create Schedule" 60ms

Then I wait until I see "Schedule successfully created" text 295ms

And I should see a "Recurring action to keep Recurring-Action-test-group uptodate" text 71ms

And I should see a "Group" text 68ms

When I am on the "Events" page of this "sle_minion" 855ms

And I follow "History" 554ms

Then I wait until I see the event "Apply recurring states [uptodate] scheduled" completed during last minute, refreshing the page 1m 8s 945ms

When I am on the Systems overview page of this "sle_minion" 738ms

Then I wait at most 500 seconds until I do not see "System is up to date" text, refreshing the page 89ms

@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
22s 547ms 14

Given I am on the Systems overview page of this "sle_minion" 806ms

When I follow "Software" in the content area 68ms

And I disable repository "test_repo_rpm_pool" on this "sle_minion" without error control 784ms

And I follow "Software Channels" in the content area 64ms

And I wait until I do not see "Loading..." text 74ms

And I check default base channel radio button of this "sle_minion" 466ms

And I wait for child channels to appear 715ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 95ms

And I check "Fake-RPM-SUSE-Channel" 73ms

And I click on "Next" 58ms

Then I should see a "Confirm Software Channel Change" text 65ms

When I click on "Confirm" 69ms

Then I should see a "Changing the channels has been scheduled." text 298ms

And I wait until event "Subscribe channels scheduled" is completed 18s 905ms

Scenario:
Edit the group Recurring Action
12s 425ms 14

When I follow the left menu "Systems > System Groups" 69ms

And I follow "Recurring-Action-test-group" 311ms

And I follow "Recurring Actions" in the content area 86ms

Then I should see a "Recurring action to keep Recurring-Action-test-group uptodate" text 274ms

When I click the "Recurring action to keep Recurring-Action-test-group uptodate" item edit button 64ms

And I wait until I see "Update Schedule" text 216ms

And I enter "schedule_name_group" as "scheduleName" 576ms

And I check radio button "schedule-hourly" 10s 88ms

And I enter "35" as "minutes" 78ms

And I click on "Update Schedule" 64ms

Then I wait until I see "Schedule successfully updated" text 265ms

And I should see a "schedule_name_group" text 184ms

And I should see a "Group" text 67ms

And I should see a "0 35 * ? * *" text 74ms

Scenario:
View the group recurring actions details
1s 258ms 10

When I follow the left menu "Systems > System Groups" 73ms

And I follow "Recurring-Action-test-group" 312ms

And I follow "Recurring Actions" in the content area 65ms

Then I should see a "schedule_name" text 278ms

When I click the "schedule_name" item details button 65ms

Then I should see a "Every hour at minute 35" text 259ms

And I should see a "Recurring-Action-test-group" link 11ms

And I should see a "Update System" text 71ms

When I click on "Back" 61ms

Then I should see a "Schedules" text 59ms

Scenario:
Create a yourorg Recurring Action
1m 11s 829ms 21

Execution time: 13:30

When I follow the left menu "Home > My Organization > Recurring Actions" 321ms

Then I should see a "No schedules created. Use Create to add a schedule" text 60ms

When I click on "Create" 81ms

And I wait until I see "Schedule Name" text 87ms

And I enter "schedule_name" as "scheduleName" 110ms

And I select "Custom state" from "actionTypeDescription" 1s 130ms

And I wait until I see "Configure states to execute" text 99ms

And I check radio button "schedule-daily" 10s 93ms

And I enter 1 minutes from now as "time-daily_time" 96ms

And I click on the "disabled" toggler 53ms

And I check "Package Profile Update-cbox" 86ms

And I click on "Save Changes" 65ms

And I wait until I see "Edit State Ranks" text 95ms

And I click on "Confirm" 75ms

And I click on "Create Schedule" 61ms

Then I wait until I see "Schedule successfully created" text 247ms

And I should see a "schedule_name" text 166ms

And I should see a "Organization" text 64ms

When I am on the "Events" page of this "sle_minion" 887ms

And I follow "History" 407ms

Then I wait until I see the event "Apply recurring states [packages.profileupdate] scheduled" completed during last minute, refreshing the page 57s 535ms

Scenario:
Edit the yourorg Recurring Action
13s 134ms 13

When I follow the left menu "Home > My Organization > Recurring Actions" 338ms

Then I should see a "schedule_name" text 268ms

When I click the "schedule_name" item edit button 62ms

And I wait until I see "Update Schedule" text 309ms

And I enter "schedule_name_edit" as "scheduleName" 263ms

And I check radio button "schedule-monthly" 10s 79ms

And I select "7" from "date_monthly" 1s 142ms

And I enter "05:17" as "time-monthly_time" 103ms

And I click on "Update Schedule" 61ms

Then I wait until I see "Schedule successfully updated" text 285ms

And I should see a "schedule_name_edit" text 84ms

And I should see a "Organization" text 71ms

And I should see a "0 17 5 7 * ?" text 64ms

Scenario:
View the yourorg recurring actions details
776ms 7

When I follow the left menu "Home > My Organization > Recurring Actions" 85ms

Then I should see a "schedule_name" text 259ms

When I click the "schedule_name" item details button 67ms

Then I should see a "Every 7th of the month at 05:17" text 172ms

And I should see a "Package Profile Update" text 69ms

When I click on "Back" 64ms

Then I should see a "Schedules" text 56ms

Scenario:
Cleanup: Delete the yourorg Recurring Action
1s 617ms 7

When I follow the left menu "Home > My Organization > Recurring Actions" 78ms

Then I should see a "schedule_name_edit" text 260ms

When I click the "schedule_name" item delete button 73ms

And I wait until I see "Delete Recurring Action Schedule" text 72ms

And I click on the red confirmation button 56ms

Then I wait until I see "Schedule 'schedule_name_edit' has been deleted." text 1s 20ms

And I should see a "No schedules created. Use Create to add a schedule" text 55ms

Scenario:
Create an admin org Recurring Action
37s 304ms 23

Execution time: 13:31

When I follow the left menu "Admin > Organizations" 110ms

And I follow "SUSE Test" in the content area 68ms

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 65ms

When I click on "Create" 79ms

And I wait until I see "Schedule Name" text 96ms

And I select "Custom state" from "actionTypeDescription" 1s 122ms

And I wait until I see "Configure states to execute" text 102ms

And I enter "schedule_name" as "scheduleName" 126ms

And I check radio button "schedule-daily" 10s 120ms

And I enter 1 minutes from now as "time-daily_time" 97ms

And I click on the "disabled" toggler 54ms

And I check "Hardware Profile Update-cbox" 86ms

And I click on "Save Changes" 64ms

And I wait until I see "Edit State Ranks" text 96ms

And I click on "Confirm" 73ms

And I click on "Create Schedule" 64ms

Then I wait until I see "Schedule successfully created" text 270ms

And I should see a "schedule_name" text 71ms

And I should see a "Organization" text 66ms

When I am on the "Events" page of this "sle_minion" 879ms

And I follow "History" 402ms

Then I wait until I see the event "Apply recurring states [hardware.profileupdate] scheduled" completed during last minute, refreshing the page 23s 118ms

Scenario:
Edit the admin org Recurring Action
12s 52ms 14

When I follow the left menu "Admin > Organizations" 127ms

And I follow "SUSE Test" in the content area 64ms

And I follow "Recurring Actions" in the content area 63ms

Then I should see a "schedule_name" text 275ms

When I click the "schedule_name" item edit button 63ms

And I wait until I see "Update Schedule" text 320ms

And I enter "schedule_name_org" as "scheduleName" 278ms

And I check radio button "schedule-cron" 10s 86ms

And I enter "0 0 15 3 * ?" as "cron" 215ms

And I click on "Update Schedule" 63ms

Then I wait until I see "Schedule successfully updated" text 283ms

And I should see a "schedule_name_org" text 70ms

And I should see a "Organization" text 65ms

And I should see a "0 0 15 3 * ?" text 73ms

Scenario:
View the admin org recurring actions details
859ms 8

When I follow the left menu "Admin > Organizations" 73ms

And I follow "SUSE Test" in the content area 67ms

And I follow "Recurring Actions" in the content area 63ms

Then I should see a "schedule_name" text 278ms

When I click the "schedule_name" item details button 68ms

Then I should see a "Every 3rd of the month at 15:00" text 183ms

When I click on "Back" 66ms

Then I should see a "Schedules" text 58ms

Scenario:
View all types of recurring actions in the list of all actions
982ms 8

When I follow the left menu "Schedule > Recurring Actions" 121ms

Then I should not see a "Create" text 65ms

And I should see a "schedule_name_minion" text 434ms

And I should see a "Minion" text 70ms

And I should see a "schedule_name_group" text 69ms

And I should see a "Group" text 72ms

And I should see a "schedule_name_org" text 70ms

And I should see a "Organization" text 79ms

Scenario:
View details in list of all actions
1s 300ms 6

When I follow the left menu "Schedule > Recurring Actions" 56ms

And I click the "schedule_name_minion" item details button 449ms

Then I should see a "Every Wednesday at 01:35" text 169ms

And I should not see a "Schedules" text in the content area 28ms

When I click on "Back" 55ms

Then I should see a "schedule_name_group" text 541ms

Scenario:
Cleanup: Delete the admin org Recurring Action
916ms 8

When I follow the left menu "Admin > Organizations" 106ms

And I follow "SUSE Test" in the content area 68ms

And I follow "Recurring Actions" in the content area 62ms

Then I should see a "schedule_name_org" text 272ms

When I click the "schedule_name_org" item delete button 81ms

And I wait until I see "Delete Recurring Action Schedule" text 70ms

And I click on the red confirmation button 79ms

Then I wait until I see "Schedule 'schedule_name_org' has been deleted." text 175ms

Scenario:
Cleanup: Delete the group Recurring Action
1s 919ms 9

When I follow the left menu "Systems > System Groups" 119ms

And I follow "Recurring-Action-test-group" 239ms

And I follow "Recurring Actions" in the content area 57ms

Then I should see a "schedule_name_group" text 191ms

When I click the "schedule_name_group" item delete button 64ms

And I wait until I see "Delete Recurring Action Schedule" text 78ms

And I click on the red confirmation button 81ms

Then I wait until I see "Schedule 'schedule_name_group' has been deleted." text 1s 17ms

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 987ms 7

When I am on the "Recurring Actions" page of this "sle_minion" 930ms

Then I should see a "schedule_name_minion" text 276ms

When I click the "schedule_name_minion" item delete button 65ms

And I wait until I see "Delete Recurring Action Schedule" text 71ms

And I click on the red confirmation button 55ms

Then I wait until I see "Schedule 'schedule_name_minion' has been deleted." text 414ms

And I should see a "No schedules created. Use Create to add a schedule" text 173ms

Scenario:
Cleanup: Delete the system group created for group recurring action tests
1s 732ms 5

When I follow the left menu "Systems > System Groups" 58ms

And I follow "Recurring-Action-test-group" 319ms

And I follow "Delete Group" 230ms

And I click on "Confirm Deletion" 1s 64ms

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 509ms 5

When I follow the left menu "Configuration > Channels" 373ms

And I follow "My State Channel for Recurring Actions" 353ms

And I follow "Delete Channel" 317ms

And I click on "Delete Config Channel" 58ms

Then I should see a "Channel 'My State Channel for Recurring Actions' has been deleted" text 407ms

@skip_if_github_validation @scc_credentials @scope_changing_software_channels @sle_minion
Feature:Assign child channel to a system 57s 879ms 8 6

Scenario:
Log in as org admin user
1s 859ms 1

Given I am authorized 1s 859ms

@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
2s 953ms 15

Warning: Radio button 'openSUSE Tumbleweed (x86_64)' is already checked

Given I am on the Systems overview page of this "sle_minion" 1s 431ms

When I follow "Software" in the content area 66ms

And I follow "Software Channels" in the content area 64ms

And I wait until I do not see "Loading..." text 66ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 213ms

Then radio button "openSUSE Tumbleweed (x86_64)" should be checked 15ms

When I wait until I do not see "Loading..." text 433ms

And I uncheck "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" by label 36ms

Then I should see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" as unchecked 15ms

When I uncheck "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" by label 105ms

Then I should see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" as unchecked 14ms

When I click on "Next" 60ms

Then I should see a "Confirm Software Channel Change" text 63ms

When I click on "Confirm" 71ms

Then I should see a "Changing the channels has been scheduled." text 295ms

@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
8s 713ms 3

When I refresh the metadata for "sle_minion" 7s 526ms

Then channel "openSUSE Tumbleweed (x86_64)" should be enabled on "sle_minion" 601ms

And channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" should be disabled on "sle_minion" 585ms

@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
18s 804ms 14

When I follow "Software" in the content area 63ms

And I follow "Software Channels" in the content area 58ms

And I wait until I do not see "Loading..." text 72ms

Then radio button "openSUSE Tumbleweed (x86_64)" should be checked 227ms

When I wait until I do not see "Loading..." text 420ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" by label 76ms

Then I should see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" as checked 14ms

When I click on "Next" 58ms

Then I should see a "Confirm Software Channel Change" text 73ms

When I click on "Confirm" 66ms

Then I should see a "Changing the channels has been scheduled." text 311ms

When I follow "scheduled" in the content area 69ms

And I wait until I see "1 system successfully completed this action." text, refreshing the page 16s 631ms

Then channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" should be enabled on "sle_minion" 661ms

Scenario:
Check channel change has completed for the system
3s 203ms 3

Given I am on the Systems overview page of this "sle_minion" 845ms

When I wait until event "Subscribe channels scheduled" is completed 2s 294ms

Then I should see a "The client completed this action on" text 63ms

@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
903ms 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 64ms

Then radio button "openSUSE Tumbleweed (x86_64)" should be checked 173ms

And I wait until I do not see "Loading..." text 512ms

And I should see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" as checked 17ms

@susemanager
Scenario:
Check via API the new channels are enabled on the system
< 1ms 3

When I refresh the metadata for "sle_minion" 0s

Then channel "SLE-Product-SLES15-SP7-Pool for x86_64" should be enabled on "sle_minion" 0s

And channel "SLE15-SP7-Installer-Updates for x86_64" should be enabled on "sle_minion" 0s

@uyuni
Scenario:
Check via API the new channels are enabled on the system
2s 564ms 3

When I refresh the metadata for "sle_minion" 1s 377ms

Then channel "openSUSE Tumbleweed (x86_64)" should be enabled on "sle_minion" 607ms

And channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" should be enabled on "sle_minion" 580ms

@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
18s 876ms 18

When I follow "Software" in the content area 55ms

And I follow "Software Channels" in the content area 51ms

And I wait until I do not see "Loading..." text 71ms

Then radio button "openSUSE Tumbleweed (x86_64)" should be checked 206ms

And I wait until I do not see "Loading..." text 426ms

And I wait until I see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" text 79ms

And I uncheck "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" by label 77ms

Then I should see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" as unchecked 14ms

When I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" by label 74ms

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" 78ms

And I wait until I see "Changing the channels has been scheduled." text 397ms

And I follow "scheduled" in the content area 70ms

And I wait until I see "1 system successfully completed this action." text, refreshing the page 16s 510ms

Then channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" should be disabled on "sle_minion" 577ms

@scope_retracted_patches
Feature:Retracted patches 1m 52s 729ms 12

Scenario:
Log in as org admin user
1s 832ms 1

Given I am authorized 1s 832ms

Scenario:
Installed retracted package should show icon in the system packages list
32s 705ms 12

When I install package "rute-dummy=2.1-1.1" on this "sle_minion" 2s 101ms

And I refresh packages list via spacecmd on "sle_minion" 3s 623ms

And I wait until refresh package list on "sle_minion" is finished 4s 905ms

And I am on the "Software" page of this "sle_minion" 943ms

And I follow "Packages" 418ms

And I follow "List / Remove" 742ms

And I enter "rute-dummy" as the filtered package name 67ms

And I click on the filter button until page does contain "rute-dummy" text 11s 154ms

Then the table row for "rute-dummy-2.1-1.1" should contain "retracted" icon 20ms

When I remove package "rute-dummy" from this "sle_minion" 1s 671ms

And I refresh packages list via spacecmd on "sle_minion" 3s 575ms

And I wait until package "rute-dummy" is removed from "sle_minion" via spacecmd 3s 481ms

Scenario:
Retracted package should not be available for installation
12s 809ms 7

When I am on the "Software" page of this "sle_minion" 968ms

And I follow "Packages" 409ms

And I follow "Install" 510ms

And I enter "rute-dummy" as the filtered package name 59ms

And I click on the filter button until page does contain "rute-dummy" text 10s 717ms

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 74ms

Scenario:
Retracted package should not be available for upgrade
19s 111ms 10

When I install old package "rute-dummy=2.0-1.2" on this "sle_minion" 1s 932ms

And I refresh packages list via spacecmd on "sle_minion" 2s 593ms

And I wait until refresh package list on "sle_minion" is finished 4s 855ms

And I am on the "Software" page of this "sle_minion" 978ms

And I follow "Packages" 443ms

And I follow "Upgrade" 505ms

Then I should not see a "rute-dummy-2.1-1.1" text 107ms

When I remove package "rute-dummy" from this "sle_minion" 1s 743ms

And I refresh packages list via spacecmd on "sle_minion" 2s 515ms

And I wait until package "rute-dummy" is removed from "sle_minion" via spacecmd 3s 437ms

Scenario:
Retracted patch should not affect any system
23s 338ms 13

When I install package "rute-dummy=2.0-1.2" on this "sle_minion" 1s 488ms

And I refresh packages list via spacecmd on "sle_minion" 2s 241ms

And I wait until refresh package list on "sle_minion" is finished 9s 610ms

And I follow the left menu "Software > Channel List > All" 178ms

And I follow "Show All Child Channels" 54ms

And I follow "Fake-RPM-SUSE-Channel" 605ms

And I follow "Patches" in the content area 65ms

And I follow "rute-dummy-0817" 512ms

And I follow "Affected Systems" 293ms

Then I should see a "No systems." text 70ms

When I remove package "rute-dummy" from this "sle_minion" 1s 686ms

And I refresh packages list via spacecmd on "sle_minion" 2s 912ms

And I wait until package "rute-dummy" is removed from "sle_minion" via spacecmd 3s 617ms

Scenario:
Target systems for stable packages should not be empty
2s 148ms 7

When I follow the left menu "Software > Channel List > All" 171ms

And I follow "Show All Child Channels" 54ms

And I follow "Fake-RPM-SUSE-Channel" 751ms

And I follow "Packages" in the content area 70ms

And I follow "rute-dummy-2.0-1.2.x86_64" 554ms

And I follow "Target Systems" 396ms

And I refresh page until I see "sle_minion" hostname as text 149ms

Scenario:
Target systems for retracted packages should be empty
11s 543ms 7

When I follow the left menu "Software > Channel List > All" 125ms

And I follow "Show All Child Channels" 51ms

And I follow "Fake-RPM-SUSE-Channel" 594ms

And I follow "Packages" in the content area 65ms

And I follow "rute-dummy-2.1-1.1.x86_64" 379ms

And I follow "Target Systems" 300ms

Then I should not see "sle_minion" hostname 10s 27ms

Scenario:
Retracted packages in the patch detail
4s 695ms 15

When I follow the left menu "Patches > Patch List > All" 177ms

And I enter "dummy" as the filtered synopsis 65ms

And I click on the filter button 650ms

And I follow "rute-dummy-0815" 437ms

Then I should see a "Status: Retracted" text 63ms

When I go back 513ms

And I enter "dummy" as the filtered synopsis 37ms

And I click on the filter button 679ms

And I follow "rute-dummy-0816" 369ms

Then I should see a "Status: Stable" text 69ms

When I go back 513ms

And I enter "dummy" as the filtered synopsis 36ms

And I click on the filter button 663ms

And I follow "rute-dummy-0817" 353ms

Then I should see a "Status: Retracted" text 64ms

Scenario:
Retracted packages in the patches list
657ms 6

When I follow the left menu "Patches > Patch List > All" 78ms

And I enter "dummy" as the filtered synopsis 36ms

And I click on the filter button 488ms

Then the table row for "rute-dummy-0815" should contain "retracted" icon 21ms

And the table row for "rute-dummy-0816" should not contain "retracted" icon 15ms

And the table row for "rute-dummy-0817" should contain "retracted" icon 17ms

Scenario:
Retracted patches in the channel patches list
966ms 7

When I follow the left menu "Software > Channel List > All" 196ms

And I follow "Show All Child Channels" 62ms

And I follow "Fake-RPM-SUSE-Channel" 585ms

And I follow "Patches" in the content area 69ms

Then the table row for "rute-dummy-0815" should contain "retracted" icon 28ms

And the table row for "rute-dummy-0816" should not contain "retracted" icon 11ms

And the table row for "rute-dummy-0817" should contain "retracted" icon 13ms

Scenario:
Retracted packages in the channel packages list
805ms 7

When I follow the left menu "Software > Channel List > All" 69ms

And I follow "Show All Child Channels" 43ms

And I follow "Fake-RPM-SUSE-Channel" 576ms

And I follow "Packages" in the content area 63ms

Then the table row for "rute-dummy-2.0-1.1.x86_64" should contain "retracted" icon 20ms

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 17ms

Scenario:
SSM: Retracted package should not be available for installation
2s 115ms 10

When I follow the left menu "Systems > System List > All" 169ms

And I click on the clear SSM button 59ms

And I check the "sle_minion" client 445ms

And I follow the left menu "Systems > System Set Manager > Overview" 439ms

And I follow "Packages" in the content area 58ms

And I follow "Install" 412ms

And I follow "Fake-RPM-SUSE-Channel" 306ms

Then I should see a "rute-dummy-2.0-1.2" text 87ms

And I should not see a "rute-dummy-2.1-1.1" text 89ms

And I click on the clear SSM button 46ms

@skip_if_github_validation @containerized_server @proxy @build_host @private_net @pxeboot_minion @scope_cobbler
Feature:PXE boot a terminal with Cobbler and containerized proxy < 1ms 19

In order to automate client system installations with a containerized proxy
As the system administrator
I want to PXE boot one host with Cobbler

Scenario:
Log in as admin user
< 1ms 1

Given I am authorized for the "Admin" section 0s

Scenario:
Start Cobbler monitoring
< 1ms 1

When I start local monitoring of Cobbler 0s

Scenario:
Prepare the autoinstallation files on the server
< 1ms 3

When I install packages "tftpboot-installation-SLE-15-SP7-x86_64 expect" on this "build_host" 0s

And I copy "/usr/share/tftpboot-installation" from "build_host" to "server" via scp in the path "/tmp" 0s

And I copy the distribution inside the container on the server 0s

Scenario:
Create auto installation distribution
< 1ms 9

When I follow the left menu "Systems > Autoinstallation > Distributions" 0s

And I follow "Create Distribution" 0s

And I enter "SLE-15-SP7-TFTP" as "label" 0s

And I enter "/srv/www/distributions/SLE-15-SP7-TFTP/" as "basepath" 0s

And I select "SLE-Product-SLES15-SP7-Pool for x86_64" from "channelid" 0s

And I select "SUSE Linux Enterprise 15" from "installtype" 0s

And I click on "Create Autoinstallable Distribution" 0s

Then I should see a "Autoinstallable Distributions" text 0s

And I should see a "SLE-15-SP7-TFTP" link 0s

Scenario:
Fix kernel parameters
< 1ms 5

When I follow the left menu "Systems > Autoinstallation > Distributions" 0s

And I follow "SLE-15-SP7-TFTP" 0s

And I enter "useonlinerepo insecure=1 install=http://proxy.example.org/ks/dist/SLE-15-SP7-TFTP self_update=http://proxy.example.org/ks/dist/child/sle15-sp7-installer-updates-x86_64/SLE-15-SP7-TFTP" as "kernelopts" 0s

And I click on "Update Autoinstallable Distribution" 0s

Then I should see a "Autoinstallable Distribution Updated" text 0s

@susemanager
Scenario:
Create auto installation profile
< 1ms 8

When I follow the left menu "Systems > Autoinstallation > Profiles" 0s

And I follow "Upload Kickstart/AutoYaST File" 0s

And I enter "15-sp7-cobbler" as "kickstartLabel" 0s

And I select "SLE-15-SP7-TFTP" from "kstreeId" 0s

And I attach the file "/sle-15-sp7-autoyast.xml" to "fileUpload" 0s

And I click on "Create" 0s

Then I should see a "Autoinstallation: 15-sp7-cobbler" text 0s

And I should see a "Autoinstallation Details" text 0s

@uyuni
Scenario:
Create auto installation profile
< 1ms 8

When I follow the left menu "Systems > Autoinstallation > Profiles" 0s

And I follow "Upload Kickstart/AutoYaST File" 0s

And I enter "15-sp7-cobbler" as "kickstartLabel" 0s

And I select "SLE-15-SP7-TFTP" from "kstreeId" 0s

And I attach the file "/sle-15-sp7-autoyast-uyuni.xml" to "fileUpload" 0s

And I click on "Create" 0s

Then I should see a "Autoinstallation: 15-sp7-cobbler" text 0s

And I should see a "Autoinstallation Details" text 0s

Scenario:
Configure auto installation profile
< 1ms 7

When I enter "self_update=0" as "kernel_options" 0s

And I click on "Update" 0s

And I follow "Variables" 0s

And I enter "distrotree=SLE-15-SP7-TFTP\nregistration_key=1-TERMINAL-KEY-x86_64\nredhat_management_server=proxy.example.org" as "variables" text area 0s

And I click on "Update Variables" 0s

And I follow "Autoinstallation File" 0s

Then I should see a "SLE-15-SP7-TFTP" text 0s

Scenario:
Migration of Cobbler settings
< 1ms 4

Given cobblerd is running 0s

And cobbler settings are successfully migrated 0s

When I restart cobbler on the server 0s

Then service "cobblerd" is active on "server" 0s

Scenario:
PXE boot the PXE boot minion
< 1ms 6

When I set the default PXE menu entry to the target profile on the "server" 0s

And I reboot the Cobbler terminal "pxeboot_minion" 0s

And I wait for "60" seconds 0s

And I set the default PXE menu entry to the local boot on the "server" 0s

And I wait at most 1200 seconds until Salt master sees "pxeboot_minion" as "unaccepted" 0s

And I accept "pxeboot_minion" key in the Salt master 0s

Scenario:
Assure the PXE boot minion is onboarded
< 1ms 4

Given I am on the Systems page 0s

When I wait until I see the name of "pxeboot_minion", refreshing the page 0s

And I wait until onboarding is completed for "pxeboot_minion" 0s

Then "pxeboot_minion" should have been reformatted 0s

Scenario:
Check connection from PXE boot minion to the proxy
< 1ms 3

When I follow "Details" in the content area 0s

And I follow "Connection" in the content area 0s

Then I should see a "proxy.example.org" text 0s

Scenario:
Install a package on the PXE boot minion
< 1ms 10

When I install the GPG key of the test packages repository on the PXE boot minion 0s

And I follow "Software" in the content area 0s

And I follow "Install" 0s

And I enter "virgo-dummy-2.0-1.1" as the filtered package name 0s

And I click on the filter button 0s

And I check "virgo-dummy-2.0-1.1" in the list 0s

And I click on "Install Packages" 0s

And I click on "Confirm" 0s

Then I should see a "1 package install has been scheduled" text 0s

When I wait until event "Package Install/Upgrade scheduled by admin" is completed 0s

Scenario:
Download the profile from the UI
< 1ms 5

When I follow the left menu "Systems > Autoinstallation > Profiles" 0s

And I follow "15-sp7-cobbler" 0s

And I follow "Autoinstallation File" in the content area 0s

And I follow "Download Autoinstallation File" 0s

Then I should see a "<profile " text 0s

Scenario:
Cleanup: remove the auto installation profile
< 1ms 6

When I follow the left menu "Systems > Autoinstallation > Profiles" 0s

And I follow "15-sp7-cobbler" 0s

And I follow "Delete Autoinstallation" 0s

And I click on "Delete Autoinstallation" 0s

And I wait until I do not see "15-sp7-cobbler" text 0s

And I wait up to 5 minutes to see "TASK COMPLETE" in the last lines of "var/log/cobbler/cobbler.log" on "server" 0s

Scenario:
Cleanup: remove the auto installation distribution
< 1ms 6

When I follow the left menu "Systems > Autoinstallation > Distributions" 0s

And I follow "SLE-15-SP7-TFTP" 0s

And I follow "Delete Distribution" 0s

And I click on "Delete Distribution" 0s

And I wait until I do not see "SLE-15-SP7-TFTP" text 0s

And I wait up to 5 minutes to see "TASK COMPLETE" in the last lines of "var/log/cobbler/cobbler.log" on "server" 0s

Scenario:
Cleanup: remove the auto installation files
< 1ms 2

When I remove packages "tftpboot-installation-SLE-15-SP7-x86_64 expect" from this "build_host" 0s

And I remove the autoinstallation files from the server 0s

Scenario:
Cleanup: delete the PXE boot minion
< 1ms 3

When I delete "pxeboot_minion" system using the api 0s

And I wait until Salt client is inactive on the PXE boot minion 0s

Then "pxeboot_minion" should not be registered 0s

@flaky
Scenario:
Check for errors in Cobbler monitoring
< 1ms 1

Then the local logs for Cobbler should not contain errors 0s

@containerized_server @skip_if_github_validation @build_host @proxy @private_net @pxeboot_minion @scope_retail
Feature:PXE boot a Retail terminal behind a containerized proxy < 1ms 17

In order to manage my terminals in a Retail context
As the system administrator
I PXE boot one of the terminals

Scenario:
Log in as admin user
< 1ms 1

Given I am authorized for the "Admin" section 0s

Scenario:
Create hardware type group
< 1ms 6

When I follow the left menu "Systems > System Groups" 0s

And I follow "Create Group" 0s

And I enter "HWTYPE:Intel-Genuine" as "name" 0s

And I enter "Terminal hardware type: genuine Intel" as "description" 0s

And I click on "Create Group" 0s

Then I should see a "System group HWTYPE:Intel-Genuine created." text 0s

Scenario:
Create branch terminals group
< 1ms 6

When I follow the left menu "Systems > System Groups" 0s

And I follow "Create Group" 0s

And I enter "example" as "name" 0s

And I enter "Terminal branch: example.org" as "description" 0s

And I click on "Create Group" 0s

Then I should see a "System group example created." text 0s

Scenario:
Create all terminals group
< 1ms 6

When I follow the left menu "Systems > System Groups" 0s

And I follow "Create Group" 0s

And I enter "TERMINALS" as "name" 0s

And I enter "All terminals" as "description" 0s

And I click on "Create Group" 0s

Then I should see a "System group TERMINALS created." text 0s

Scenario:
Create all branch servers group
< 1ms 6

When I follow the left menu "Systems > System Groups" 0s

And I follow "Create Group" 0s

And I enter "SERVERS" as "name" 0s

And I enter "All branch servers" as "description" 0s

And I click on "Create Group" 0s

Then I should see a "System group SERVERS created." text 0s

Scenario:
Enable Saltboot Group formula for branch terminals group
< 1ms 7

When I follow the left menu "Systems > System Groups" 0s

And I follow "example" in the content area 0s

And I follow "Formulas" in the content area 0s

And I check the "saltboot-group" formula 0s

And I click on "Save" 0s

And I wait until I see "Formula saved." text 0s

Then the "saltboot-group" formula should be checked 0s

Scenario:
Parametrize the Saltboot Group formula
< 1ms 8

When I follow the left menu "Systems > System Groups" 0s

And I follow "example" in the content area 0s

And I follow "Formulas" in the content area 0s

And I follow first "Saltboot Group" in the content area 0s

And I enter "proxy.example.org" as "Image download server" 0s

And I check containerized proxy box 0s

And I click on "Save Formula" 0s

Then I should see a "Formula saved" text 0s

Scenario:
Enable Saltboot formula for hardware type group
< 1ms 7

When I follow the left menu "Systems > System Groups" 0s

And I follow "HWTYPE:Intel-Genuine" in the content area 0s

And I follow "Formulas" in the content area 0s

And I check the "saltboot" formula 0s

And I click on "Save" 0s

And I wait until I see "Formula saved." text 0s

Then the "saltboot" formula should be checked 0s

Scenario:
Parametrize the Saltboot formula
< 1ms 23

When I follow the left menu "Systems > System Groups" 0s

And I follow "HWTYPE:Intel-Genuine" in the content area 0s

And I follow "Formulas" in the content area 0s

And I follow first "Saltboot" in the content area 0s

And I click on "Expand All Sections" 0s

And I enter "disk1" in disk id field 0s

And I enter "/dev/vda" in disk device field 0s

And I select "msdos" in disk label field 0s

And I enter "p1" in first partition id field 0s

And I enter "256" in first partition size field 0s

And I select "swap" in first filesystem format field 0s

And I select "swap" in first partition flags field 0s

And I press "Add Item" in partitions section 0s

And I enter "p2" in second partition id field 0s

And I enter "/data" in second mount point field 0s

And I select "xfs" in second filesystem format field 0s

And I enter "secret-password" in second partition password field 0s

And I press "Add Item" in partitions section 0s

And I enter "p3" in third partition id field 0s

And I enter "/" in third mount point field 0s

And I enter the image name for "pxeboot_minion" in third OS image field 0s

And I click on "Save Formula" 0s

Then I should see a "Formula saved" text 0s

Scenario:
PXE boot the PXE boot minion
< 1ms 3

When I reboot the Retail terminal "pxeboot_minion" 0s

And I wait at most 180 seconds until Salt master sees "pxeboot_minion" as "unaccepted" 0s

And I accept "pxeboot_minion" key in the Salt master 0s

Scenario:
Assure the PXE boot minion is onboarded
< 1ms 12

Given I am on the Systems page 0s

When I wait until I see the name of "pxeboot_minion", refreshing the page 0s

And I follow this "pxeboot_minion" link 0s

And I follow "Events" 0s

And I follow "History" 0s

And I wait until I see "added system entitlement" text, refreshing the page 0s

And I wait until event "Apply states [saltboot]" is completed 0s

And I follow "Software" in the content area 0s

And I follow "Software Channels" in the content area 0s

And I wait until radio button "SLE-Product-SLES15-SP7-Pool for x86_64" is checked, refreshing the page 0s

And I wait until event "Package List Refresh" is completed 0s

Then "pxeboot_minion" should have been reformatted 0s

Scenario:
Check connection from terminal to branch server
< 1ms 4

When I navigate to the Systems overview page of this "pxeboot_minion" 0s

And I follow "Details" in the content area 0s

And I follow "Connection" in the content area 0s

Then I should see a "proxy.example.org" text 0s

Scenario:
Install a package on the new Retail terminal
< 1ms 11

When I navigate to the Systems overview page of this "pxeboot_minion" 0s

And I install the GPG key of the test packages repository on the PXE boot minion 0s

And I follow "Software" in the content area 0s

And I follow "Install" 0s

And I enter "virgo" as the filtered package name 0s

And I click on the filter button 0s

And I check "virgo-dummy-2.0-1.1" in the list 0s

And I click on "Install Packages" 0s

And I click on "Confirm" 0s

Then I should see a "1 package install has been scheduled" text 0s

When I wait until event "Package Install/Upgrade scheduled by admin" is completed 0s

Scenario:
Remove the package from the new Retail terminal
< 1ms 10

When I navigate to the Systems overview page of this "pxeboot_minion" 0s

And I follow "Software" in the content area 0s

And I follow "List / Remove" 0s

And I enter "virgo" as the filtered package name 0s

And I click on the filter button 0s

And I check "virgo-dummy-2.0-1.1" in the list 0s

And I click on "Remove Packages" 0s

And I click on "Confirm" 0s

Then I should see a "1 package removal has been scheduled" text 0s

When I wait until event "Package Removal scheduled by admin" is completed 0s

Scenario:
Cleanup: let the terminal be reinstalled again
< 1ms 6

When I navigate to the Systems overview page of this "pxeboot_minion" 0s

And I follow "Remote Command" 0s

And I enter "#!/bin/sh\nrm /etc/ImageVersion*" as "script_body" text area 0s

And I click on "Schedule" 0s

Then I should see a "Remote Command has been scheduled" text 0s

When I wait until event "Remote Command" is completed 0s

Scenario:
Cleanup: delete the new Retail terminal
< 1ms 7

When I navigate to the Systems overview page of this "pxeboot_minion" 0s

And I follow "Delete System" 0s

Then I should see a "Confirm System Profile Deletion" text 0s

When I click on "Delete Profile" 0s

And I wait until I see "has been deleted" text 0s

And I wait until Salt client is inactive on the PXE boot minion 0s

Then "pxeboot_minion" should not be registered 0s

Scenario:
Cleanup: delete the terminal groups
< 1ms 17

When I follow the left menu "Systems > System Groups" 0s

And I follow "HWTYPE:Intel-Genuine" in the content area 0s

And I follow "Delete Group" in the content area 0s

And I click on "Confirm Deletion" 0s

Then I should see a "deleted" text 0s

When I follow "example" in the content area 0s

And I follow "Delete Group" in the content area 0s

And I click on "Confirm Deletion" 0s

Then I should see a "deleted" text 0s

When I follow "TERMINALS" in the content area 0s

And I follow "Delete Group" in the content area 0s

And I click on "Confirm Deletion" 0s

Then I should see a "deleted" text 0s

When I follow "SERVERS" in the content area 0s

And I follow "Delete Group" in the content area 0s

And I click on "Confirm Deletion" 0s

Then I should see a "deleted" text 0s

@containerized_server @skip_if_github_validation @proxy @private_net @pxeboot_minion @scope_retail @test_issue
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
Feature:Correct timezone display 54s 32ms 11

Scenario:
Log in as admin user
1s 790ms 1

Given I am authorized for the "Admin" section 1s 790ms

Scenario:
Create a new user in a timezone different than server's timezone
1s 85ms 11

When I follow the left menu "Users > User List > Active" 168ms

And I follow "Create User" 300ms

And I enter "MalaysianUser" as "login" 80ms

And I enter "MalaysianUser" as "desiredpassword" 76ms

And I enter "MalaysianUser" as "desiredpasswordConfirm" 82ms

And I select "Mr." from "prefix" 45ms

And I enter "Test" as "firstNames" 57ms

And I enter "User" as "lastName" 58ms

And I enter "galaxy-noise@localhost" as "email" 91ms

And I select "(GMT+0800) Malaysia" from "timezone" 64ms

And I click on "Create Login" 59ms

Scenario:
Add roles for the Malaysian user
11s 666ms 9

When I follow the left menu "Users > User List > Active" 568ms

And I follow "MalaysianUser" 267ms

And the "role_satellite_admin" checkbox should be disabled 10s 6ms

And I check "role_org_admin" 76ms

And I check "role_system_group_admin" 80ms

And I check "role_channel_admin" 74ms

And I check "role_activation_key_admin" 73ms

And I check "role_config_admin" 74ms

And I click on "Update" 443ms

Scenario:
Login as the new Malaysian user
1s 733ms 2

Given I am authorized as "MalaysianUser" with password "MalaysianUser" 1s 722ms

Then I should see a "MalaysianUser" link 11ms

Scenario:
Schedule a remote script to run now and see the correct timezone details in history
20s 29ms 10

Given I am on the Systems overview page of this "sle_minion" 1s 827ms

When I follow "Remote Command" in the content area 94ms

And I enter as remote command this script in #!/bin/bash ls 48ms

And I click on "Schedule" 664ms

And I follow "Events" in the content area 70ms

And I follow "Pending" in the content area 63ms

And I wait at most 180 seconds until I do not see "Remote Command on" text, refreshing the page 16s 640ms

And I follow "History" in the content area 69ms

And I follow first "scheduled by MalaysianUser" 488ms

Then I should see a "MYT" text 61ms

Scenario:
Login as the new Malaysian user if the previous scenario failed
457ms 2

Given I am authorized as "MalaysianUser" with password "MalaysianUser" 449ms

Then I should see a "MalaysianUser" link 7ms

Scenario:
Schedule a remote script in the future and see the correct timezone as a pop up
1s 802ms 6

Given I am on the Systems overview page of this "sle_minion" 1s 482ms

When I follow "Remote Command" in the content area 66ms

And I enter as remote command this script in #!/bin/bash ls 46ms

And I enter "00:00" as "date_timepicker_widget_input" 69ms

And I click on "Schedule" 51ms

Then I should see a "00:00:00 MYT" text 86ms

Scenario:
Login as the new Malaysian user if the previous scenario failed
508ms 2

Given I am authorized as "MalaysianUser" with password "MalaysianUser" 500ms

Then I should see a "MalaysianUser" link 7ms

Scenario:
Cleanup: Log in as admin user again and remove scheduled actions
3s 493ms 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 299ms

And I cancel all scheduled actions via API 1s 193ms

Scenario:
Cleanup: Remove role
11s 133ms 9

When I follow the left menu "Users > User List > Active" 197ms

And I follow "MalaysianUser" 263ms

And I uncheck "role_org_admin" 10s 92ms

And I click on "Update" 485ms

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 23ms

And I should see "role_activation_key_admin" as checked 18ms

And I should see "role_config_admin" as checked 17ms

Scenario:
Cleanup: Delete user
332ms 1

When I delete user "MalaysianUser" 332ms

@scope_ansible @sle_minion
Feature:Operate an Ansible control node in a normal minion 3m 3s 74ms 11 2

Scenario:
Log in as org admin user
448ms 1

Given I am authorized for the "Admin" section 448ms

Scenario:
Pre-requisite: Deploy test playbooks and inventory file
2s 556ms 1

When I deploy testing playbooks and inventory files to "sle_minion" 2s 556ms

@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
2s 782ms 5

Given I am on the Systems overview page of this "sle_minion" 762ms

When I follow "Properties" in the content area 70ms

And I check "ansible_control_node" 80ms

And I click on "Update Properties" 1s 769ms

Then I wait until I see "Ansible Control Node type has been applied." text 100ms

Scenario:
Apply highstate and check that Ansible is installed
57s 298ms 5

Given I am on the Systems overview page of this "sle_minion" 895ms

When I follow "States" in the content area 67ms

And I click on "Apply Highstate" 57ms

And I wait until event "Apply highstate scheduled" is completed 55s 479ms

Then "ansible" should be installed on "sle_minion" 798ms

Scenario:
The Ansible tab appears in the system overview page
991ms 3

Given I am on the Systems overview page of this "sle_minion" 850ms

When I follow "Ansible" in the content area 78ms

Then I should see a "Ansible Control Node Configuration" text 62ms

Scenario:
Configure some inventory and playbooks path
1s 315ms 7

Given I am on the Systems overview page of this "sle_minion" 844ms

When I follow "Ansible" in the content area 57ms

Then I should see a "Ansible Control Node Configuration" text 59ms

And I enter "/srv/playbooks/" as "new_playbook_path_input" 142ms

And I click on "new_playbook_path_save" 55ms

And I enter "/srv/playbooks/orion_dummy/hosts" as "new_inventory_path_input" 94ms

And I click on "new_inventory_path_save" 60ms

Scenario:
Display inventories
8s 696ms 6

Given I am on the Systems overview page of this "sle_minion" 879ms

When I follow "Ansible" in the content area 58ms

And I follow "Inventories" in the content area 74ms

And I wait until I see "/srv/playbooks/orion_dummy/hosts" text 249ms

And I click on "/srv/playbooks/orion_dummy/hosts" 56ms

Then I wait until I see "myself" text 7s 378ms

Scenario:
Discover playbooks and display them
6s 15ms 6

Given I am on the Systems overview page of this "sle_minion" 795ms

When I follow "Ansible" in the content area 58ms

And I follow "Playbooks" in the content area 62ms

And I wait until I see "/srv/playbooks" text 166ms

And I click on "/srv/playbooks" 76ms

Then I wait until I see "/srv/playbooks/orion_dummy/playbook_orion_dummy.yml" text 4s 856ms

Scenario:
Run a playbook using custom inventory
48s 222ms 13

Given I am on the Systems overview page of this "sle_minion" 886ms

When I follow "Ansible" in the content area 59ms

And I follow "Playbooks" in the content area 57ms

And I wait until I see "/srv/playbooks" text 250ms

And I click on "/srv/playbooks" 47ms

And I wait until I see "/srv/playbooks/orion_dummy/playbook_orion_dummy.yml" text 4s 855ms

And I click on "orion_dummy/playbook_orion_dummy.yml" 62ms

And I wait until I see "Playbook Content" text 938ms

And I select "/srv/playbooks/orion_dummy/hosts" from "inventory-path-select" 1s 112ms

And I click on "Schedule" 66ms

Then I should see a "Playbook execution has been scheduled" text 364ms

And I wait until event "Execute playbook 'playbook_orion_dummy.yml' scheduled" is completed 38s 790ms

And file "/tmp/file.txt" should exist on "sle_minion" 729ms

Scenario:
Cleanup: Disable Ansible and remove test playbooks and inventory file
15s 4ms 7

Given I am on the Systems overview page of this "sle_minion" 780ms

When I follow "Properties" in the content area 76ms

And I uncheck "ansible_control_node" 10s 75ms

And I click on "Update Properties" 1s 526ms

Then I should see a "System properties changed" text 96ms

And I remove package "orion-dummy" from this "sle_minion" without error control 2s 26ms

And I remove "/tmp/file.txt" from "sle_minion" 422ms

@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"
39s 742ms 4

Given I am on the Systems overview page of this "sle_minion" 794ms

When I follow "States" in the content area 73ms

And I click on "Apply Highstate" 58ms

And I wait until event "Apply highstate scheduled" is completed 38s 816ms

@sle_minion @proxy
Feature:Move a minion from a proxy to direct connection 10m 44s 322ms 13

Scenario:
Log in as org admin user
1s 735ms 1

Given I am authorized 1s 735ms

Scenario:
Delete minion system profile before bootstrap
4m 6s 745ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 279ms

When I follow "Delete System" 462ms

Then I should see a "Confirm System Profile Deletion" text 70ms

When I click on "Delete Profile" 79ms

And I wait until I see "has been deleted" text 4m 3s 802ms

And I wait until Salt client is inactive on "sle_minion" 745ms

Then "sle_minion" should not be registered 305ms

Scenario:
Bootstrap a minion
1m 51s 168ms 11

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 79ms

Then I should see a "Bootstrap Minions" text 72ms

When I enter the hostname of "sle_minion" as "hostname" 151ms

And I enter "22" as "port" 50ms

And I enter "root" as "user" 53ms

And I enter "linux" as "password" 57ms

And I select "1-SUSE-KEY-x86_64" from "activationKeys" 70ms

And I select the hostname of "proxy" from "proxies" if present 60ms

And I click on "Bootstrap" 59ms

And I wait until I see "Bootstrap process initiated." text 30s 995ms

And I wait until onboarding is completed for "sle_minion" 1m 19s 516ms

Scenario:
Check the new bootstrapped minion in System Overview page
2s 380ms 3

It took 2 seconds to contact the minion

When I follow the left menu "Salt > Keys" 121ms

Then I should see a "accepted" text 340ms

And the Salt master can reach "sle_minion" 1s 918ms

Scenario:
Check initial connection from minion to proxy
1s 177ms 4

Given I am on the Systems overview page of this "sle_minion" 974ms

When I follow "Details" in the content area 71ms

And I follow "Connection" in the content area 64ms

Then I should see "proxy" short hostname 66ms

Scenario:
Check initial registration on proxy of minion
1s 111ms 4

Given I am on the Systems overview page of this "proxy" 879ms

When I follow "Details" in the content area 63ms

And I follow "Proxy" in the content area 63ms

Then I should see "sle_minion" hostname 105ms

Scenario:
Change from proxy to direct connection
36s 809ms 11

Given I am on the Systems overview page of this "sle_minion" 881ms

When I follow "Details" in the content area 58ms

And I follow "Connection" in the content area 76ms

And I follow "Change" in the content area 64ms

And I select "None" from "proxies" 68ms

And I click on "Change Proxy" 57ms

And I wait until I see "scheduled" text 254ms

And I follow "Events" 407ms

And I follow "History" 434ms

And I wait until I see the event "Apply states [bootstrap.set_proxy] scheduled" completed during last minute, refreshing the page 11s 492ms

And I wait until I see the event "Apply states [channels] scheduled" completed during last minute, refreshing the page 23s 15ms

Scenario:
Check direct connection
1s 72ms 4

Given I am on the Systems overview page of this "sle_minion" 892ms

When I follow "Details" in the content area 60ms

And I follow "Connection" in the content area 55ms

Then I should see a "This system connects directly and not through a Proxy" text 64ms

Scenario:
Change connection back to a proxy via SSM
2m 1s 673ms 10

Given I wait for "120" seconds 2m

When I follow the left menu "Systems > System List > All" 131ms

And I click on the clear SSM button 76ms

And I check the "sle_minion" client 430ms

And I should see "1" systems selected for SSM 148ms

And I follow the left menu "Systems > System Set Manager > Overview" 427ms

And I follow "proxy server" in the content area 70ms

And I select the hostname of "proxy" from "proxies" if present 76ms

And I click on "Change Proxy" 55ms

And I wait until I see "scheduled" text 256ms

Scenario:
Check events on the minion
36s 398ms 5

Given I am on the Systems overview page of this "sle_minion" 1s 87ms

And I follow "Events" 378ms

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 495ms

Scenario:
Check registration on proxy of minion
1s 98ms 4

Given I am on the Systems overview page of this "proxy" 867ms

When I follow "Details" in the content area 67ms

And I follow "Proxy" in the content area 65ms

Then I should see "sle_minion" hostname 98ms

Scenario:
Check connection from minion to proxy
1s 80ms 4

Given I am on the Systems overview page of this "sle_minion" 883ms

When I follow "Details" in the content area 62ms

And I follow "Connection" in the content area 63ms

Then I should see "proxy" short hostname 70ms

Scenario:
Check events history for failures on the minion
1m 21s 870ms 2

Given I am on the Systems overview page of this "sle_minion" 904ms

Then I check for failed events on history event page 1m 20s 965ms

@ssh_minion @scope_salt_ssh @proxy
Feature:Move a SSH minion from a proxy to direct connection 7m 15s 91ms 11

Scenario:
Log in as org admin user
1s 967ms 1

Given I am authorized 1s 967ms

Scenario:
Delete minion system profile before bootstrap
17s 337ms 6

Given I am on the Systems overview page of this "ssh_minion" 1s 609ms

When I follow "Delete System" 379ms

Then I should see a "Confirm System Profile Deletion" text 62ms

When I click on "Delete Profile" 61ms

And I wait until I see "has been deleted" text 14s 815ms

Then "ssh_minion" should not be registered 408ms

Scenario:
Bootstrap a minion
2m 24s 99ms 11

The hostname of ssh_minion is uyuni-master-suse-sshminion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 84ms

Then I should see a "Bootstrap Minions" text 66ms

When I check "manageWithSSH" 88ms

And I enter the hostname of "ssh_minion" as "hostname" 137ms

And I enter "root" as "user" 53ms

And I enter "linux" as "password" 56ms

And I select "1-SUSE-SSH-KEY-x86_64" from "activationKeys" 70ms

And I select the hostname of "proxy" from "proxies" if present 59ms

And I click on "Bootstrap" 58ms

And I wait at most 480 seconds until I see "Bootstrap process initiated." text 41s 504ms

And I wait until onboarding is completed for "ssh_minion" 1m 41s 918ms

Scenario:
Check initial connection from minion to proxy
1s 69ms 4

Given I am on the Systems overview page of this "ssh_minion" 863ms

When I follow "Details" in the content area 71ms

And I follow "Connection" in the content area 64ms

Then I should see "proxy" short hostname 70ms

Scenario:
Check initial registration on proxy of minion
1s 73ms 4

Given I am on the Systems overview page of this "proxy" 852ms

When I follow "Details" in the content area 60ms

And I follow "Proxy" in the content area 65ms

Then I should see "ssh_minion" hostname 95ms

Scenario:
Change from proxy to direct connection
36s 649ms 10

Given I am on the Systems overview page of this "ssh_minion" 807ms

When I follow "Details" in the content area 59ms

And I follow "Connection" in the content area 57ms

And I follow "Change" in the content area 65ms

And I select "None" from "proxies" 68ms

And I click on "Change Proxy" 56ms

And I wait until I see "scheduled" text 243ms

And I follow "Events" 405ms

And I follow "History" 435ms

And I wait until I see the event "Apply states [channels] scheduled" completed during last minute, refreshing the page 34s 450ms

Scenario:
Check direct connection
1s 11ms 4

Given I am on the Systems overview page of this "ssh_minion" 837ms

When I follow "Details" in the content area 58ms

And I follow "Connection" in the content area 55ms

Then I should see a "This system connects directly and not through a Proxy" text 60ms

Scenario:
Change connection to a proxy
2m 48s 124ms 11

Given I wait for "120" seconds 2m

Given I am on the Systems overview page of this "ssh_minion" 813ms

When I follow "Details" in the content area 60ms

And I follow "Connection" in the content area 58ms

And I follow "Change" in the content area 55ms

And I select the hostname of "proxy" from "proxies" if present 55ms

And I click on "Change Proxy" 48ms

And I wait until I see "scheduled" text 355ms

And I follow "Events" 321ms

And I follow "History" 394ms

And I wait until I see the event "Apply states [channels] scheduled" completed during last minute, refreshing the page 45s 961ms

Scenario:
Check registration on proxy of minion
1s 43ms 4

Given I am on the Systems overview page of this "proxy" 819ms

When I follow "Details" in the content area 63ms

And I follow "Proxy" in the content area 64ms

Then I should see "ssh_minion" hostname 95ms

Scenario:
Check connection from minion to proxy
1s 24ms 4

Given I am on the Systems overview page of this "ssh_minion" 837ms

When I follow "Details" in the content area 60ms

And I follow "Connection" in the content area 55ms

Then I should see "proxy" short hostname 70ms

Scenario:
Check events history for failures on the minion
1m 1s 690ms 2

Given I am on the Systems overview page of this "ssh_minion" 835ms

Then I check for failed events on history event page 1m 854ms

Feature:Sanity check that all logfiles exist 6s 359ms 1

In order to be secure
As an authorized user
I want to watch different logfiles

Scenario:
All logfiles should be available
6s 359ms 9

Then I wait until file "/var/log/rhn/rhn_web_ui.log" exists on server 1s 18ms

And I wait until file "/var/log/rhn/rhn_web_api.log" exists on server 681ms

And I wait until file "/var/log/rhn/rhn_web_frontend.log" exists on server 650ms

And I wait until file "/var/log/rhn/rhn_taskomatic_daemon.log" exists on server 673ms

And I wait until file "/var/log/rhn/search/rhn_search_daemon.log" exists on server 656ms

And I wait until file "/var/log/rhn/search/rhn_search.log" exists on server 642ms

And I wait until file "/var/log/rhn/reposync.log" exists on server 675ms

And I wait until file "/var/log/salt/master" exists on server 675ms

And I wait until file "/var/log/salt/api" exists on server 684ms

@scope_cobbler
Feature:Run Cobbler Sync via WebUI 24s 647ms 6 1

Scenario:
Login as admin
2s 2ms 1

Given I am authorized for the "Admin" section 2s 2ms

Scenario:
Start Cobbler monitoring
7s 13ms 2

When I start local monitoring of Cobbler 6s 321ms

And I backup Cobbler settings file 691ms

@uyuni
Scenario:
Check that the Cobbler Settings Page exists
690ms 7

When I follow the left menu "Admin > Manager Configuration > Cobbler" 412ms

Then I should see a "Uyuni Configuration - Cobbler. " text 67ms

And I should see a "Setup your Uyuni Cobbler settings below. " text 58ms

And I should see a "Cobbler sync is used to repair or rebuild the contents /srv/tftpboot or /srv/www/cobbler when manual modification of cobbler has occurred. " text 56ms

And I should see a "For more information refer to the 'cobbler' man page. " text 57ms

And I should see a "Run Cobbler Sync" text in the content area 22ms

And I should see a "Update" button 16ms

@susemanager
Scenario:
Check that the Cobbler Settings Page exists
< 1ms 7

When I follow the left menu "Admin > Manager Configuration > Cobbler" 0s

Then I should see a "SUSE Multi-Linux Manager Configuration - Cobbler. " text 0s

And I should see a "Setup your SUSE Multi-Linux Manager Cobbler settings below. " text 0s

And I should see a "Cobbler sync is used to repair or rebuild the contents /srv/tftpboot or /srv/www/cobbler when manual modification of cobbler has occurred. " text 0s

And I should see a "For more information refer to the 'cobbler' man page. " text 0s

And I should see a "Run Cobbler Sync" text in the content area 0s

And I should see a "Update" button 0s

Scenario:
Run Cobbler Sync via button and validate UI output
471ms 3

When I follow the left menu "Admin > Manager Configuration > Cobbler" 67ms

And I click on "Update" 53ms

Then I should see a "Cobbler Sync action was successfully executed. Look at /var/log/cobbler/*.log for more information" text 350ms

Scenario:
Run Cobbler Sync via button and verify task timestamp in Last Execution Times Page
10s 752ms 4

When I follow the left menu "Admin > Manager Configuration > Cobbler" 73ms

And I click on "Update" 312ms

And I follow the left menu "Admin > Task Engine Status > Last Execution Times" 330ms

Then I should see the correct timestamp for task "Cobbler Sync:" 10s 35ms

@skip_if_github_validation
Scenario:
Check for errors in Cobbler monitoring
3s 717ms 1

Then the local logs for Cobbler should not contain errors 3s 717ms

@skip_if_github_validation @scope_cobbler @new_issue
Feature:Cobbler and distribution autoinstallation 1m 21s 303ms 26

Scenario:
Start Cobbler monitoring
6s 586ms 2

When I start local monitoring of Cobbler 5s 939ms

And I backup Cobbler settings file 647ms

Scenario:
Log in as testing user
2s 21ms 2

Given I am authorized as "testing" with password "testing" 1s 705ms

And I am logged in via the Cobbler API as user "testing" with password "testing" 316ms

Scenario:
Copy cobbler profiles on the server
6s 188ms 1

When I copy autoinstall mocked files on server 6s 188ms

Scenario:
Ask cobbler to create a distribution via API
558ms 2

Given cobblerd is running 2ms

When I create "testdistro" kickstart tree via the API 555ms

Scenario:
Create dummy profile
748ms 2

Given cobblerd is running 2ms

When I create a "testprofile" profile via the API using import file for "testdistro" distribution 746ms

Scenario:
Check cobbler created distro and profile
625ms 3

When I follow the left menu "Systems > Autoinstallation > Profiles" 488ms

Then I should see a "testprofile" text 72ms

And I should see a "testdistro" text 64ms

Scenario:
Create SUSE distribution with installer updates
2s 268ms 12

When I follow the left menu "Systems > Autoinstallation > Distributions" 77ms

And I follow "Create Distribution" 298ms

And I enter "SLE-15-FAKE" as "label" 61ms

And I enter "/var/autoinstall/SLES15-SP7-x86_64/DVD1/" as "basepath" 86ms

And I select "SLE-Product-SLES15-SP7-Pool for x86_64" from "channelid" 383ms

And I select "SUSE Linux Enterprise 15" from "installtype" 56ms

And I click on "Create Autoinstallable Distribution" 823ms

And I wait until I see "Autoinstallable Distribution Created" text 73ms

Then I should see a "Autoinstallable Distributions" text 67ms

And I should see a "SLE-15-FAKE" link 11ms

When I follow "SLE-15-FAKE" 305ms

Then I should see "self_update=http://" in field identified by "kernelopts" 23ms

Scenario:
Create a distribution via the UI
1s 388ms 8

When I follow the left menu "Systems > Autoinstallation > Distributions" 66ms

And I follow "Create Distribution" 374ms

When I enter "fedora_kickstart_distro" as "label" 65ms

And I enter "/var/autoinstall/Fedora_12_i386/" as "basepath" 73ms

And I select "Fedora" from "installtype" 55ms

And I click on "Create Autoinstallable Distribution" 662ms

Then I should see a "Autoinstallable Distributions" text 78ms

And I should see a "fedora_kickstart_distro" link 11ms

Scenario:
Create a distribution via the API, without kernel options
610ms 3

When I create "fedora_kickstart_distro_api" kickstart tree via the API 528ms

When I follow the left menu "Systems > Autoinstallation > Distributions" 70ms

Then I should see a "fedora_kickstart_distro_api" link 11ms

Scenario:
Create a distribution via the API, with kernel options
670ms 3

When I create a kickstart tree with kernel options via the API 595ms

When I follow the left menu "Systems > Autoinstallation > Distributions" 64ms

Then I should see a "fedora_kickstart_distro_kernel_api" link 11ms

Scenario:
Update a distribution via the API
1s 46ms 6

When I update a kickstart tree via the API 538ms

When I follow the left menu "Systems > Autoinstallation > Distributions" 68ms

And I follow "fedora_kickstart_distro_api" 324ms

Then option "Generic RPM" is selected as "installtype" 70ms

And I should see "self_update=0" in field identified by "kernelopts" 18ms

And I should see "self_update=1" in field identified by "postkernelopts" 25ms

Scenario:
Create a profile via the UI
2s 911ms 10

When I follow the left menu "Systems > Autoinstallation > Profiles" 66ms

And I follow "Create Kickstart Profile" 380ms

When I enter "fedora_kickstart_profile" as "kickstartLabel" 70ms

And I click on "Next" 57ms

And I click on "Next" 390ms

And I enter "linux" as "rootPassword" 51ms

And I enter "linux" as "rootPasswordConfirm" 52ms

And I click on "Finish" 1s 755ms

Then I should see a "Autoinstallation: fedora_kickstart_profile" text 76ms

And I should see a "Autoinstallation Details" link 11ms

Scenario:
Upload a profile via the UI
2s 246ms 8

When I follow the left menu "Systems > Autoinstallation > Profiles" 67ms

And I follow "Upload Kickstart/AutoYaST File" 342ms

When I enter "fedora_kickstart_profile_upload" as "kickstartLabel" 72ms

And I select "fedora_kickstart_distro" from "kstreeId" 44ms

And I attach the file "/example.ks" to "fileUpload" 32ms

And I click on "Create" 58ms

Then I should see a "Autoinstallation: fedora_kickstart_profile_upload" text 1s 532ms

And I should see a "Autoinstallation Details" text 96ms

Scenario:
Add an unprovisioned range to the created profile
2s 362ms 13

When I follow the left menu "Systems > Autoinstallation > Profiles" 70ms

And I follow "fedora_kickstart_profile" 741ms

And I follow "Unprovisioned Autoinstallation" 308ms

And I enter "10" as "octet1a" 48ms

And I enter "10" as "octet1b" 49ms

And I enter "0" as "octet1c" 47ms

And I enter "100" as "octet1d" 48ms

And I enter "10" as "octet2a" 47ms

And I enter "10" as "octet2b" 46ms

And I enter "0" as "octet2c" 44ms

And I enter "200" as "octet2d" 48ms

And I click on "Add IP Range" 789ms

Then I should see a "Successfully added IP Range" text 71ms

Scenario:
Add a variable to the uploaded profile
1s 962ms 7

When I follow the left menu "Systems > Autoinstallation > Profiles" 69ms

And I follow "fedora_kickstart_profile_upload" 575ms

And I follow "Variables" 271ms

And I enter "my_var=A_Test_String" as "variables" 66ms

And I click on "Update Variables" 447ms

And I follow "Autoinstallation File" 475ms

Then I should see a "A_Test_String" text 56ms

Scenario:
Add a kernel option to the created profile
2s 866ms 5

When I follow the left menu "Systems > Autoinstallation > Profiles" 67ms

And I follow "fedora_kickstart_profile" 534ms

And I enter "kernel_option=a_value" as "kernel_options" 75ms

And I click on "Update" 1s 66ms

And I wait until file "/srv/tftpboot/pxelinux.cfg/default" contains "kernel_option=a_value" on server 1s 122ms

Scenario:
Add a kernel option to the uploaded profile
5s 287ms 5

When I follow the left menu "Systems > Autoinstallation > Profiles" 70ms

And I follow "fedora_kickstart_profile_upload" 567ms

And I enter "kernel_option2=a_value2" as "kernel_options" 84ms

And I click on "Update" 1s 126ms

And I wait until file "/srv/tftpboot/pxelinux.cfg/default" contains "kernel_option2=a_value2" on server 3s 438ms

Scenario:
Check default snippets
1s 3ms 6

When I follow the left menu "Systems > Autoinstallation > Autoinstallation Snippets" 76ms

And I follow "Default Snippets" 291ms

And I enter "spacewalk/sles_no_signature_checks" as the filtered snippet name 86ms

And I click on the filter button 304ms

And I follow "spacewalk/sles_no_signature_checks" 228ms

Then I should see "<signature-handling>" in the textarea 15ms

Scenario:
Create a snippet
932ms 6

When I follow the left menu "Systems > Autoinstallation > Autoinstallation Snippets" 66ms

And I follow "Create Snippet" 279ms

And I enter "created_test_snippet" as "name" 65ms

And I enter "<test_element>a text string</test_element>" in the editor 3ms

And I click on "Create Snippet" 61ms

Then I should see a "created_test_snippet created successfully." text 454ms

Scenario:
Delete a snippet
1s 39ms 5

When I follow the left menu "Systems > Autoinstallation > Autoinstallation Snippets" 74ms

And I follow "created_test_snippet" 239ms

And I follow "Delete Snippet" 224ms

And I click on "Delete Snippet" 51ms

Then I should see a "created_test_snippet deleted successfully." text 449ms

Scenario:
Test for PXE environment files
4s 704ms 8

Given cobblerd is running 14ms

When I wait until file "/srv/tftpboot/pxelinux.cfg/default" exists on server 671ms

And I wait until file "/srv/tftpboot/pxelinux.cfg/default" contains "inst.ks=.*fedora_kickstart_profile:1" on server 686ms

And I wait until file "/srv/tftpboot/pxelinux.cfg/default" contains "inst.ks=.*fedora_kickstart_profile_upload:1" on server 637ms

And I wait until file "/srv/tftpboot/images/fedora_kickstart_distro:1:SUSETest/initrd.img" exists on server 673ms

And I wait until file "/srv/tftpboot/images/fedora_kickstart_distro:1:SUSETest/vmlinuz" exists on server 681ms

And I wait until file "/srv/tftpboot/menu.c32" exists on server 652ms

And I wait until file "/srv/tftpboot/pxelinux.0" exists on server 685ms

Scenario:
Trigger the creation of a cobbler system record
4s 324ms 7

When I clear the caches on the server 961ms

And I am on the Systems overview page of this "sle_minion" 857ms

And I follow "Provisioning" 664ms

And I click on profile "testprofile" 55ms

And I click on "Create PXE installation configuration" 1s 4ms

Then I should see a "System record created" text 85ms

And I wait until file "/srv/tftpboot/pxelinux.cfg/01-*" contains "autoyast=" on server 695ms

Scenario:
Create a cobbler system record via API
5s 220ms 5

When I create a system record 502ms

And I wait until file "/srv/tftpboot/pxelinux.cfg/01-00-22-22-77-ee-cc" contains "inst.ks=.*testserver:1" on server 697ms

Then the cobbler report should contain "testserver.example.com" for cobbler system name "testserver:1" 1s 339ms

And the cobbler report should contain "1.1.1.1" for cobbler system name "testserver:1" 1s 341ms

And the cobbler report should contain "00:22:22:77:ee:cc" for cobbler system name "testserver:1" 1s 339ms

Scenario:
Cleanup: delete test profiles and distributions using API
14s 925ms 12

When I wait for "10" seconds 10s

When I delete profile and distribution using the API for "testdistro" kickstart tree 450ms

When I delete profile and distribution using the API for "fedora_kickstart_distro" kickstart tree 440ms

When I delete profile and distribution using the API for "fedora_kickstart_distro_api" kickstart tree 305ms

When I delete profile and distribution using the API for "fedora_kickstart_distro_kernel_api" kickstart tree 1s 196ms

When I delete profile and distribution using the API for "SLE-15-FAKE" kickstart tree 1s 853ms

When I follow the left menu "Systems > Autoinstallation > Distributions" 390ms

And I should not see a "testdistro" text 58ms

And I should not see a "fedora_kickstart_distro" text 56ms

And I should not see a "fedora_kickstart_distro_api" text 56ms

And I should not see a "fedora_kickstart_distro_kernel_api" text 62ms

And I should not see a "SLE-15-FAKE" text 55ms

@flaky
Scenario:
Check for errors in Cobbler monitoring
8s 799ms 2

When I wait for "5" seconds 5s

Then the local logs for Cobbler should not contain errors 3s 799ms

Scenario:
Logout from the Cobbler API
3ms 1

When I log out from Cobbler via the API 3ms

@scope_cobbler @skip_if_github_validation
Feature:Cobbler buildiso 1m 20s 609ms 19

Builds several ISOs with Cobbler and checks the configuration files and ISOs afterwards.

Scenario:
Start Cobbler monitoring
6s 652ms 2

When I start local monitoring of Cobbler 5s 967ms

And I backup Cobbler settings file 685ms

Scenario:
Log in as testing user in the Cobbler buildiso context
844ms 2

Given I am authorized as "testing" with password "testing" 436ms

And I am logged in via the Cobbler API as user "testing" with password "testing" 408ms

Scenario:
Copy cobbler profiles on the server in the Cobbler buildiso context
6s 7ms 1

When I copy autoinstall mocked files on server 6s 7ms

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
265ms 4

Given distro "buildisodistro" exists 3ms

When I create profile "orchid" for distro "buildisodistro" 76ms

And I create profile "flame" for distro "buildisodistro" 78ms

And I create profile "pearl" for distro "buildisodistro" 105ms

Scenario:
Check cobbler created a distro and profiles in the Cobbler buildiso context
621ms 5

When I follow the left menu "Systems > Autoinstallation > Profiles" 348ms

Then I should see a "buildisodistro" text 71ms

And I should see a "orchid" text 66ms

And I should see a "flame" text 68ms

And I should see a "pearl" text 67ms

Scenario:
Create dummy system in the Cobbler buildiso context
1s 444ms 3

Given profile "orchid" exists 9ms

When I create system "testsystem" for profile "orchid" 54ms

And I add the Cobbler parameter "name-servers" with value "9.9.9.9" to item "system" with name "testsystem" 1s 381ms

Scenario:
Prepare the Cobbler buildiso context
3s 691ms 1

When I prepare Cobbler for the buildiso command 3s 691ms

Scenario:
Run Cobbler buildiso with all profiles and check isolinux config file in the Cobbler buildiso context
11s 900ms 4

When I run Cobbler buildiso for distro "buildisodistro" and all profiles 8s 551ms

And I check Cobbler buildiso ISO "profile_all" with xorriso 2s 44ms

And I check the Cobbler parameter "nameserver" with value "9.9.9.9" in the isolinux.cfg 644ms

And I cleanup xorriso temp files 660ms

Scenario:
Run Cobbler buildiso with selected profile in the Cobbler buildiso context
5s 163ms 3

When I run Cobbler buildiso for distro "buildisodistro" and profile "orchid" 2s 505ms

And I check Cobbler buildiso ISO "orchid" with xorriso 2s 8ms

And I cleanup xorriso temp files 649ms

Scenario:
Run Cobbler buildiso with selected profile and without dns entries in the Cobbler buildiso context
5s 817ms 3

When I run Cobbler buildiso for distro "buildisodistro" and profile "orchid" without dns entries 3s 183ms

And I check Cobbler buildiso ISO "orchid" with xorriso 1s 961ms

And I cleanup xorriso temp files 672ms

Scenario:
Run Cobbler buildiso airgapped with all profiles in the Cobbler buildiso context
15s 235ms 3

When I run Cobbler buildiso "airgapped" for distro "buildisodistro" 12s 577ms

And I check Cobbler buildiso ISO "airgapped" with xorriso 1s 972ms

And I cleanup xorriso temp files 685ms

Scenario:
Run Cobbler buildiso standalone with all profiles in the Cobbler buildiso context
15s 107ms 3

When I run Cobbler buildiso "standalone" for distro "buildisodistro" 12s 458ms

And I check Cobbler buildiso ISO "standalone" with xorriso 2s 1ms

And I cleanup xorriso temp files 648ms

Scenario:
Cleanup: delete test system in the Cobbler buildiso context
505ms 2

Given I am authorized as "testing" with password "testing" 473ms

When I remove system "testsystem" 32ms

Scenario:
Cleanup: delete test profile in the Cobbler buildiso context
1s 915ms 8

Given I am authorized as "testing" with password "testing" 951ms

And I remove profile "orchid" 110ms

And I remove profile "flame" 86ms

And I remove profile "pearl" 22ms

When I follow the left menu "Systems > Autoinstallation > Profiles" 566ms

Then I should not see a "orchid" text 60ms

And I should not see a "flame" text 57ms

And I should not see a "flame" text 59ms

Scenario:
Cleanup: delete test distro in the Cobbler buildiso context
1s 199ms 4

Given I am authorized as "testing" with password "testing" 415ms

And I remove distro "buildisodistro" 34ms

And I follow the left menu "Systems > Autoinstallation > Profiles" 687ms

Then I should not see a "buildisodistro" text 61ms

Scenario:
Cleanup: Remove buildiso tmpdir and built ISO file in the Cobbler buildiso context
677ms 1

When I cleanup after Cobbler buildiso 677ms

@flaky
Scenario:
Check for errors in Cobbler monitoring
3s 497ms 1

Then the local logs for Cobbler should not contain errors 3s 497ms

Scenario:
Logout from the Cobbler API
3ms 1

When I log out from Cobbler via the API 3ms

@scope_cobbler @skip_if_github_validation
Feature:Edit Cobbler profiles 1m 6s 706ms 12

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 2ms

Scenario:
Copy cobbler profiles on the server
6s 643ms 2

When I copy autoinstall mocked files on server 5s 969ms

And I backup Cobbler settings file 673ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 2ms

Scenario:
Log in as testing user
10s 678ms 1

Given I am authorized as "testing" with password "testing" 10s 678ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 6ms

Scenario:
Start Cobbler monitoring
6s 609ms 1

When I start local monitoring of Cobbler 6s 609ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 3ms

Scenario:
Create a Cobbler distribution via the UI
1s 674ms 10

When I follow the left menu "Systems > Autoinstallation > Distributions" 351ms

And I follow "Create Distribution" 275ms

When I enter "isedistro_ui" as "label" 61ms

And I enter "/var/autoinstall/Fedora_12_i386/" as "basepath" 76ms

And I select "Fedora" from "installtype" 62ms

And I click on "Create Autoinstallable Distribution" 618ms

Then I should see a "Autoinstallable Distributions" text 70ms

And I should see a "isedistro_ui" link 11ms

When I follow the left menu "Systems > Autoinstallation > Distributions" 71ms

Then I should see a "isedistro_ui" text 75ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 2ms

Scenario:
Create a Cobbler profile via the UI
3s 172ms 12

When I follow the left menu "Systems > Autoinstallation > Profiles" 74ms

And I follow "Create Kickstart Profile" 339ms

When I enter "iseprofile_ui" as "kickstartLabel" 59ms

And I click on "Next" 345ms

And I click on "Next" 372ms

And I enter "linux" as "rootPassword" 51ms

And I enter "linux" as "rootPasswordConfirm" 57ms

And I click on "Finish" 1s 648ms

Then I should see a "Autoinstallation: iseprofile_ui" text 77ms

And I should see a "Autoinstallation Details" link 11ms

When I follow the left menu "Systems > Autoinstallation > Profiles" 69ms

Then I should see a "iseprofile_ui" text 66ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 5ms

Scenario:
Change profile variables using the UI
12s 77ms 7

When I follow the left menu "Systems > Autoinstallation > Profiles" 65ms

And I follow "iseprofile_ui" 599ms

And I follow "Variables" 317ms

And I enter "ise_ui_test=ISE_UI_TEST" as "variables" 80ms

And I click on "Update Variables" 384ms

And I refresh the page 10s 567ms

Then I should see a "ISE_UI_TEST" text 61ms

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 499ms 10

When I follow the left menu "Systems > Autoinstallation > Distributions" 71ms

And I follow "Create Distribution" 298ms

When I enter "isedistro_api" as "label" 62ms

And I enter "/var/autoinstall/Fedora_12_i386/" as "basepath" 74ms

And I select "Fedora" from "installtype" 46ms

And I click on "Create Autoinstallable Distribution" 47ms

Then I should see a "Autoinstallable Distributions" text 746ms

And I should see a "isedistro_api" link 11ms

When I follow the left menu "Systems > Autoinstallation > Distributions" 70ms

Then I should see a "isedistro_api" text 69ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 5ms

Scenario:
Create a Cobbler profile via the UI in the XML-RPC context
2s 837ms 12

When I follow the left menu "Systems > Autoinstallation > Profiles" 66ms

And I follow "Create Kickstart Profile" 286ms

When I enter "iseprofile_api" as "kickstartLabel" 56ms

And I click on "Next" 51ms

And I click on "Next" 639ms

And I enter "linux" as "rootPassword" 47ms

And I enter "linux" as "rootPasswordConfirm" 47ms

And I click on "Finish" 1s 413ms

Then I should see a "Autoinstallation: iseprofile_api" text 75ms

And I should see a "Autoinstallation Details" link 8ms

When I follow the left menu "Systems > Autoinstallation > Profiles" 69ms

Then I should see a "iseprofile_api" text 74ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 8ms

Scenario:
Create a Cobbler system via the XML-RPC API
448ms 1

When I create a system record with name "isesystem_api" and kickstart label "iseprofile_api" 448ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 6ms

Scenario:
Create and modify a System profile using the XML-RPC API
1s 274ms 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 274ms
inst.repo http://ise.cobbler.test
self_update http://ise.cobbler.test

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 6ms

Scenario:
Cleanup: delete test profiles and distributions using API
10s 992ms 6

When I wait for "10" seconds 10s

When I delete profile and distribution using the API for "isedistro_ui" kickstart tree 392ms

When I delete profile and distribution using the API for "isedistro_api" kickstart tree 398ms

When I follow the left menu "Systems > Autoinstallation > Distributions" 67ms

And I should not see a "isedistro_ui" text 77ms

And I should not see a "isedistro_api" text 56ms

Background:
The Cobbler service should be running
< 1ms

Given cobblerd is running 2ms

@flaky
Scenario:
Check for errors in Cobbler monitoring
8s 797ms 2

When I wait for "5" seconds 5s

Then the local logs for Cobbler should not contain errors 3s 797ms

@scope_visualization
Feature:Manage users 1m 26s 670ms 15 2

Scenario:
Log in as admin user
37s 503ms 1

Given I am authorized for the "Admin" section 37s 503ms

Scenario:
Display active users page
525ms 9

When I follow the left menu "Users > User List > Active" 207ms

Then I should see a "Active Users" text 199ms

And I should see a "Create User" link 11ms

And I should see a "User List" link in the left menu 23ms

And I should see a "Active" link in the left menu 20ms

And I should see a "Deactivated" link in the left menu 19ms

And I should see a "All" link in the left menu 22ms

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
1s 803ms 13

When I follow the left menu "Users > User List > Active" 67ms

And I follow "Create User" 272ms

And I enter "user1" as "login" 59ms

And I enter "user1" as "desiredpassword" 59ms

And I enter "user1" as "desiredpasswordConfirm" 65ms

And I select "Mr." from "prefix" 44ms

And I enter "Test" as "firstNames" 59ms

And I enter "User" as "lastName" 55ms

And I enter "galaxy-noise@localhost" as "email" 102ms

And I click on "Create Login" 63ms

Then I should see a "Account user1 created, login information sent to galaxy-noise@localhost" text 764ms

And I should see a "user1" link 11ms

And I should see a "normal user" text 178ms

Scenario:
Login as the new user
1s 523ms 2

Given I am authorized as "user1" with password "user1" 1s 515ms

Then I should see a "user1" link 7ms

Scenario:
Access user details
2s 133ms 21

Given I am authorized for the "Admin" section 978ms

When I follow the left menu "Users > User List > Active" 152ms

And I follow "user1" 271ms

Then I should see a "User Details" text 76ms

And I should see a "Delete User" link 11ms

And I should see a "Deactivate User" link 10ms

And I should see a "Details" link 13ms

And I should see a "System Groups" link 12ms

And I should see a "Systems" link in the content area 24ms

And I should see a "Channel Permissions" link 10ms

And I should see a "Preferences" link in the content area 19ms

And I should see a "Addresses" link 13ms

And I should see a "user1" text 76ms

And option "Mr." is selected as "prefix" 69ms

And I should see "Test" in field identified by "firstNames" 21ms

And I should see "User" in field identified by "lastName" 20ms

And I should see a "galaxy-noise@localhost" text 70ms

And I should see a "Administrative Roles" text 71ms

And I should see a "Roles:" text 69ms

And I should see a "Created:" text 69ms

And I should see a "Last Sign In:" text 69ms

@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
21s 778ms 23

When I follow the left menu "Users > User List > Active" 70ms

And I follow "user1" 280ms

When the "role_satellite_admin" checkbox should be disabled 10s 6ms

And I check "role_org_admin" 80ms

And I check "role_system_group_admin" 70ms

And I check "role_channel_admin" 70ms

And I check "role_activation_key_admin" 71ms

And I check "role_config_admin" 71ms

And I click on "Update" 440ms

Then the "role_satellite_admin" checkbox should be disabled 10s 8ms

And I should see a "Uyuni Administrator" text 80ms

And I should see "role_org_admin" as checked 14ms

And I should see a "Organization Administrator" text 70ms

And I should see "role_system_group_admin" as checked 14ms

And I should see a "System Group Administrator" text 74ms

And I should see "role_channel_admin" as checked 14ms

And I should see a "Channel Administrator" text 70ms

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 70ms

And I should see "role_regular_user" as checked 21ms

And I should see a "Regular User" text 74ms

Scenario:
Verify user list
91ms 2

When I follow the left menu "Users > User List > Active" 68ms

Then table row for "user1" should contain "Organization Administrator" 23ms

Scenario:
Fail to deactivate organization administrator
1s 353ms 8

When I follow the left menu "Users > User List > Active" 66ms

And I follow "user1" 256ms

When I follow "Deactivate User" 237ms

Then I should see a "This action will deactivate this user. This user will no longer be able to log in or perform actions unless it is reactivated." text 50ms

When I click on "Deactivate User" 359ms

Then I should see a "You cannot deactivate another organization administrator. Please remove the 'Organization Administrator' role from this user before attempting to deactivate their account." text 80ms

When I follow "Deactivated" 244ms

Then I should see a "No deactivated users." text 56ms

Scenario:
Remove role
10s 940ms 10

When I follow the left menu "Users > User List > Active" 64ms

And I follow "user1" 268ms

When I uncheck "role_org_admin" 10s 73ms

And I click on "Update" 443ms

Then I should see "role_org_admin" as unchecked 15ms

And I should see "role_system_group_admin" as checked 14ms

And I should see "role_channel_admin" as checked 14ms

And I should see "role_activation_key_admin" as checked 15ms

And I should see "role_config_admin" as checked 15ms

And I should see "role_regular_user" as checked 14ms

Scenario:
Deactivate ordinary user
1s 960ms 13

When I follow the left menu "Users > User List > Active" 67ms

And I follow "user1" 273ms

Then I should see "role_org_admin" as unchecked 31ms

When I follow "Deactivate User" 224ms

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" 462ms

Then I should see a "Active Users" text 186ms

And I should not see a "user1" link 8ms

When I follow "Deactivated" 251ms

Then I should see a "Deactivated Users" text 66ms

And I should see a "user1" link 8ms

When I follow "All" 319ms

Then I should see a "user1" link 8ms

@susemanager
Scenario:
Reactivate user
< 1ms 11

When I follow the left menu "Users > User List > Active" 0s

And I follow "Deactivated" 0s

And I follow "user1" 0s

Then I should see a "Reactivate User" link 0s

When I follow "Reactivate User" 0s

Then I should see a "This action will allow this user to access SUSE Multi-Linux Manager. This user will retain all permissions, roles, and data that he or she had before being deactivated." text 0s

When I click on "Reactivate User" 0s

Then I should see a "Active Users" text 0s

And I should see a "user1" link 0s

When I follow "Deactivated" 0s

Then I should not see a "user1" link 0s

@uyuni
Scenario:
Reactivate user
1s 763ms 11

When I follow the left menu "Users > User List > Active" 69ms

And I follow "Deactivated" 255ms

And I follow "user1" 226ms

Then I should see a "Reactivate User" link 11ms

When I follow "Reactivate User" 244ms

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 55ms

When I click on "Reactivate User" 57ms

Then I should see a "Active Users" text 577ms

And I should see a "user1" link 8ms

When I follow "Deactivated" 253ms

Then I should not see a "user1" link 4ms

Scenario:
Delete user
1s 355ms 8

When I follow the left menu "Users > User List > Active" 63ms

And I follow "user1" 255ms

When I follow "Delete User" 257ms

Then I should see a "Confirm User Deletion" text 55ms

And I should see a "This will delete this user permanently." text 58ms

When I click on "Delete User" 471ms

Then I should see a "Active Users" text 187ms

And I should not see a "user1" link 5ms

Scenario:
Display the CSV separator preference
2s 81ms 6

Given I am authorized as "testing" with password "testing" 1s 627ms

When I follow the left menu "Home > My Preferences" 64ms

Then I should see a "CSV Files" text 101ms

And I should see a "Configure a separator character to be used in downloadable CSV files:" text 96ms

And I should see a "Comma" text 99ms

And I should see a "Semicolon" text 91ms

Scenario:
Configure the CSV separator char to semicolon
711ms 6

Given I am authorized as "testing" with password "testing" 420ms

When I follow the left menu "Home > My Preferences" 56ms

And I choose ";" 57ms

And I click on "Save Preferences" 59ms

Then I should see a "Preferences modified" text 98ms

And radio button "radio-semicolon" should be checked 18ms

Scenario:
Cleanup: configure the CSV separator char to comma
1s 144ms 6

Given I am authorized as "testing" with password "testing" 483ms

When I follow the left menu "Home > My Preferences" 56ms

And I choose "," 57ms

And I click on "Save Preferences" 431ms

Then I should see a "Preferences modified" text 97ms

And radio button "radio-comma" should be checked 18ms

@scope_visualization @new_issue
Feature:Web UI - Main landing page menu, texts and links 12s 746ms 43

Scenario:
Log in as admin user
1s 556ms 1

Given I am authorized for the "Admin" section 1s 556ms

Scenario:
The Home menu
218ms 7

When I follow the left menu "Home" 53ms

And I should see a "Overview" link in the left menu 30ms

Then I should see a "Overview" text 50ms

And I should see a "Notification Messages" link in the left menu 22ms

And I should see a "User Account" link in the left menu 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 19ms

Scenario:
The user account submenu under the Home menu
222ms 6

When I follow the left menu "Home > User Account" 64ms

Then I should see a "My Account" text 70ms

And I should see a "My Account" link in the left menu 21ms

And I should see a "Addresses" link in the left menu 20ms

And I should see a "Change Email" link in the left menu 22ms

And I should see a "Account Deactivation" link in the left menu 22ms

Scenario:
The my orginization menu under the Home menu
185ms 5

When I follow the left menu "Home > My Organization" 62ms

Then I should see a "Organization Configuration" text 59ms

And I should see a "Configuration" link in the left menu 24ms

And I should see a "Organization Trusts" link in the left menu 19ms

And I should see a "Configuration Channels" link in the left menu 18ms

Scenario:
The Salt menu
167ms 5

When I follow the left menu "Salt" 50ms

Then I should see a "Keys" text 51ms

And I should see a "Keys" link in the left menu 24ms

And I should see a "Remote Commands" link in the left menu 20ms

And I should see a "Formula Catalog" link in the left menu 19ms

Scenario:
The content lifeycle menu
159ms 4

When I follow the left menu "Content Lifecycle" 65ms

Then I should see a "Content Lifecycle Projects" text 53ms

And I should see a "Projects" link in the left menu 20ms

And I should see a "Filters" link in the left menu 20ms

Scenario:
The images menu
208ms 6

When I follow the left menu "Images" 54ms

Then I should see a "Images" text 63ms

And I should see a "Image List" link in the left menu 26ms

And I should see a "Build" link in the left menu 22ms

And I should see a "Profiles" link in the left menu 22ms

And I should see a "Stores" link in the left menu 19ms

Scenario:
The audit menu
205ms 6

When I follow the left menu "Audit" 51ms

Then I should see a "CVE Audit" text 72ms

And I should see a "CVE Audit" link in the left menu 23ms

And I should see a "Subscription Matching" link in the left menu 19ms

And I should see a "OpenSCAP" link in the left menu 19ms

And I should see a "Confidential Computing" link in the left menu 19ms

Scenario:
The OpenSCAP submenu menu
186ms 5

When I follow the left menu "Audit > OpenSCAP" 63ms

Then I should see a "OpenSCAP Scans" text 57ms

And I should see a "All Scans" link in the left menu 20ms

And I should see a "XCCDF Diff" link in the left menu 21ms

And I should see a "Advanced Search" link in the left menu 24ms

Scenario:
The configuration menu
176ms 5

When I follow the left menu "Configuration" 52ms

Then I should see a "Configuration Overview" text 61ms

And I should see a "Overview" link in the left menu 19ms

And I should see a "Channels" link in the left menu 22ms

And I should see a "Files" link in the left menu 20ms

Scenario:
The files menu under the configuration menu
164ms 4

When I follow the left menu "Configuration > Files" 66ms

Then I should see a "Centrally-Managed Configuration Files" text 52ms

And I should see a "Centrally Managed" link in the left menu 24ms

And I should see a "Locally Managed" link in the left menu 21ms

Scenario:
The systems submenu in the configuration menu
161ms 4

When I follow the left menu "Configuration > Systems" 61ms

Then I should see a "Managed Systems" text 57ms

And I should see a "Managed" link in the left menu 22ms

And I should see a "Target" link in the left menu 20ms

Scenario:
The schedule menu
207ms 6

When I follow the left menu "Schedule" 49ms

Then I should see a "Pending Actions" text 72ms

And I should see a "Pending Actions" link in the left menu 24ms

And I should see a "Failed Actions" link in the left menu 21ms

And I should see a "Archived Actions" link in the left menu 19ms

And I should see a "Action Chains" link in the left menu 19ms

Scenario:
The users menu
356ms 8

When I follow the left menu "Users" 51ms

Then I should see a "Active Users" text 181ms

And I should see a "Users" link in the left menu 21ms

And I should see a "User List" link in the left menu 19ms

And I should see a "Active" link in the left menu 18ms

And I should see a "Deactivated" link in the left menu 22ms

And I should see a "All" link in the left menu 22ms

And I should see a "System Group Configuration" link in the left menu 19ms

Scenario:
The admin menu
283ms 10

When I follow the left menu "Admin" 52ms

Then I should see a "Setup Wizard" text 74ms

And I should see a "Setup Wizard" link in the left menu 21ms

And I should see a "Organizations" link in the left menu 19ms

And I should see a "Users" link in the left menu 16ms

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 19ms

And I should see a "Task Engine Status" link in the left menu 18ms

And I should see a "Show Tomcat Logs" link in the left menu 18ms

Scenario:
The Setup Wizard submenu of the admin menu
124ms 4

When I follow the left menu "Admin > Setup Wizard" 63ms

Then I should see a "HTTP Proxy" link in the left menu 20ms

And I should see a "Organization Credentials" link in the left menu 19ms

And I should see a "Products" link in the left menu 20ms

Scenario:
The manager configuration submenu of the admin menu
246ms 8

When I follow the left menu "Admin > Manager Configuration" 62ms

Then I should see a "Configuration - General Configuration" text 67ms

And I should see a "General" link in the left menu 23ms

And I should see a "Bootstrap Script" link in the left menu 19ms

And I should see a "Organizations" link in the left menu 16ms

And I should see a "Restart" link in the left menu 18ms

And I should see a "Cobbler" link in the left menu 20ms

And I should see a "Monitoring" link in the left menu 18ms

Scenario:
The Hub configuration submenu of the admin menu
183ms 5

When I follow the left menu "Admin > Hub Configuration" 61ms

Then I should see a "Peripherals Configuration" text 59ms

And I should see a "Peripherals Configuration" link in the left menu 21ms

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 19ms

Scenario:
The Task Engine Status submenu of the admin menu
107ms 3

When I follow the left menu "Admin > Task Engine Status" 62ms

Then I should see a "Last Execution Times" link in the left menu 21ms

And I should see a "Runtime Status" link in the left menu 23ms

Scenario:
The menu direct link accesses the first submenu level only
560ms 6

When I follow the left menu "Patches > Patch List" 113ms

Then I should see a "Patches Relevant to Your Systems" text in the content area 84ms

And I should not see a "The following patch list represents all patches accessible by your organization." text in the content area 52ms

When I follow the left menu "Configuration > Files" 279ms

Then I should see a "Centrally-Managed Configuration Files" text in the content area 15ms

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
293ms 4

When I follow the left menu "Software > Manage" 110ms

Then I should see a "Software Channel Management" text in the content area 53ms

When I follow the left menu "Software > Manage > Channels" 75ms

Then I should see a "Software Channel Management" text in the content area 53ms

Scenario:
Completeness of the side navigation bar and the content frame
541ms 13

When I am on the Systems page 277ms

Then I should see a "Systems" text in the content area 62ms

And I should see a "All" link in the left menu 19ms

And I should see a "Systems" link in the left menu 22ms

And I should see a "System Groups" link in the left menu 20ms

And I should see a "System Set Manager" link in the left menu 21ms

And I should see a "Advanced Search" link in the left menu 20ms

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 19ms

And I should see a "Autoinstallation" link in the left menu 19ms

And I should see a "Download CSV" link 10ms

And I should see a Sign Out link 6ms

Scenario:
Sidebar link destination for Systems
235ms 7

When I follow the left menu "Systems > System List" 59ms

Then I should see a "All" link in the left menu 21ms

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 20ms

And I should see a "System Currency" link in the left menu 20ms

And I should see a "System Types" link in the left menu 19ms

And I should see a "Systems" text 72ms

Scenario:
Sidebar link destination for Systems => Virtual Systems
141ms 3

When I follow the left menu "Systems > System List > Virtual Systems" 67ms

Then I should see a "Virtual Systems" text 71ms

And the current path is "/rhn/manager/systems/list/virtual" 3ms

Scenario:
Sidebar link destination for Systems => Duplicate Systems
181ms 7

When I follow the left menu "Systems > System List > Duplicate Systems" 69ms

Then I should see a "Duplicate Systems" text 68ms

And the current path is "/rhn/systems/DuplicateIPList.do" 2ms

And I should see a "Duplicate IP Address" link 10ms

And I should see a "Duplicate Hostname" link 10ms

And I should see a "Duplicate IPv6 Address" link 10ms

And I should see a "Duplicate MAC Address" link 10ms

Scenario:
Sidebar link destination for Systems => System Currency
174ms 3

When I follow the left menu "Systems > System List > System Currency" 70ms

Then I should see a "System Currency Report" text 101ms

And the current path is "/rhn/systems/SystemCurrency.do" 2ms

Scenario:
Sidebar link destination for Systems => System Types
647ms 7

When I follow the left menu "Systems > System List > System Types" 72ms

Then I should see a "System Types" text 123ms

And I should see a "Management:" text 117ms

And I should see a "Salt:" text 123ms

And I should see a "Foreign:" text 104ms

And I should see a "Virtualization Host:" text 103ms

And the current path is "/rhn/systems/SystemEntitlements.do" 2ms

Scenario:
Sidebar link destination for Systems => System Groups
186ms 4

When I follow the left menu "Systems > System Groups" 63ms

Then I should see a "System Groups" text 58ms

And I should see a "Create Group" link 10ms

And I should see a "Your organization has no system groups." text 54ms

Scenario:
Sidebar link destination for Systems => System Set Manager
662ms 12

When I follow the left menu "Systems > System Set Manager > Overview" 393ms

Then I should see a "System Set Manager" text 82ms

And I should see a "Task Log" link in the left menu 20ms

And I should see a "Overview" link in the content area 19ms

And I should see a "Systems" link in the content area 16ms

And I should see a "Patches" link in the content area 20ms

And I should see a "Packages" link in the content area 18ms

And I should see a "Groups" link in the content area 18ms

And I should see a "Channels" link in the content area 15ms

And I should see a "Configuration" link in the content area 18ms

And I should see a "Provisioning" link in the content area 19ms

And I should see a "Misc" link in the content area 18ms

Scenario:
Sidebar link destination for Systems => Advanced Search
129ms 2

When I follow the left menu "Systems > Advanced Search" 59ms

Then I should see a "Advanced Search" text 69ms

Scenario:
Sidebar link destination for Systems => Activation Keys
230ms 4

When I follow the left menu "Systems > Activation Keys" 58ms

Then I should see a "Activation Keys" text 81ms

And I should see a "Create Key" link 11ms

And I should see a "The following activation keys have been created for use by your organization." text 78ms

Scenario:
Sidebar link destination for Systems => Stored Profiles
170ms 3

When I follow the left menu "Systems > Stored Profiles" 59ms

Then I should see a "Stored Profiles" text 57ms

And I should see a "No stored profiles." text 53ms

Scenario:
Sidebar link destination for Systems => Custom System Info
181ms 4

When I follow the left menu "Systems > Custom System Info" 59ms

Then I should see a "Custom System Info Keys" text 57ms

And I should see a "Create Key" link 7ms

And I should see a "No Custom Info Keys Found" text 55ms

Scenario:
Sidebar link destination for Systems => Autoinstallation
546ms 13

When I follow the left menu "Systems > Autoinstallation > Overview" 294ms

Then I should see a "Autoinstallation Overview" text 80ms

And I should see a "Profiles" link in the left menu 19ms

And I should see a "Unprovisioned" link in the left menu 22ms

And I should see a "GPG and SSL Keys" link in the left menu 19ms

And I should see a "Distributions" link in the left menu 19ms

And I should see a "File Preservation" link in the left menu 18ms

And I should see a "Autoinstallation Snippets" link in the left menu 18ms

And I should see a "Create Kickstart Profile" link 10ms

And I should see a "Upload Kickstart/AutoYaST File" link 9ms

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 12ms

Scenario:
Sidebar link destination for Systems => Autoinstallation => Profiles
150ms 4

When I follow the left menu "Systems > Autoinstallation > Profiles" 70ms

Then I should see a "Autoinstallation Profiles" text 65ms

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
187ms 3

When I follow the left menu "Systems > Autoinstallation > Unprovisioned" 69ms

Then I should see a "Unprovisioned Autoinstallation By IP" text 59ms

And I should see a "No Ip Ranges Found" text 58ms

Scenario:
Sidebar link destination for Systems => Autoinstallation => GPG and SSL Keys
170ms 5

When I follow the left menu "Systems > Autoinstallation > GPG and SSL Keys" 70ms

Then I should see a "GPG Public Keys and SSL Certificates" text 67ms

And I should see a "Create Stored Key/Cert" link 11ms

And I should see a "Reference Guide" link 10ms

And I should see a "RHN-ORG-TRUSTED-SSL-CERT" link 10ms

Scenario:
Sidebar link destination for Systems => Autoinstallation => Distributions
207ms 4

When I follow the left menu "Systems > Autoinstallation > Distributions" 70ms

Then I should see a "Autoinstallable Distributions" text 65ms

And I should see a "No autoinstallable distributions available." text 60ms

And I should see a "Create Distribution" link 11ms

Scenario:
Sidebar link destination for Systems => Autoinstallation => File Preservation
178ms 4

When I follow the left menu "Systems > Autoinstallation > File Preservation" 70ms

Then I should see a "File Preservation" text 71ms

And I should see a "Reference Guide" link 24ms

And I should see a "Create File Preservation List" link 11ms

Scenario:
Sidebar link destination for Systems => Autoinstallation => Autoinstallation Snippets
264ms 7

When I follow the left menu "Systems > Autoinstallation > Autoinstallation Snippets" 72ms

Then I should see a "Autoinstallation Snippets" text 64ms

And I should see a "No autoinstallation snippets found." text 59ms

And I should see a "Create Snippet" link 10ms

And I should see a "Default Snippets" link in the content area 19ms

And I should see a "Custom Snippets" link in the content area 19ms

And I should see a "All Snippets" link in the content area 18ms

Scenario:
"Create Kickstart Profile" page Systems => Autoinstallation => Profiles => Create Kickstart Profile
414ms 3

When I follow the left menu "Systems > Autoinstallation > Profiles" 64ms

And I follow "Create Kickstart Profile" 287ms

Then I should see a "Step 1: Create Kickstart Profile" text 62ms

Scenario:
"Upload Kickstart/AutoYaST File" page Systems => Autoinstallation => Profiles => Upload Kickstart/AutoYaST File
588ms 5

When I follow the left menu "Systems > Autoinstallation > Profiles" 65ms

And I follow "Upload Kickstart/AutoYaST File" 315ms

Then I should see a "Create Autoinstallation Profile" text 70ms

And I should see a "File Contents:" text 66ms

And I should see a "Autoinstallation Details" text 70ms

Scenario:
"Create kickstart distribution" page Systems => Autoinstallation => Distributions => create new kickstart distribution
575ms 4

When I follow the left menu "Systems > Autoinstallation > Distributions" 67ms

And I follow "Create Distribution" 377ms

Then I should see a "Create Autoinstallable Distribution" text 67ms

And I should see a "Distribution Label" text 63ms

@scope_configuration_channels
Feature:Check if source packages were successfully synced 5s 529ms 3

Scenario:
Log in as org admin user
1s 727ms 1

Given I am authorized 1s 727ms

Scenario:
Check sources for noarch package
1s 895ms 6

When I follow the left menu "Software > Channel List > All" 161ms

And I follow "Show All Child Channels" 54ms

And I follow "Fake-RPM-SUSE-Channel" 580ms

And I follow "Packages" 488ms

And I follow "virgo-dummy-2.0-1.1.noarch" 541ms

Then I should see a "virgo-dummy-2.0-1.1.src.rpm" text 69ms

Scenario:
Check sources for x86_64 package
1s 905ms 6

When I follow the left menu "Software > Channel List > All" 111ms

And I follow "Show All Child Channels" 45ms

And I follow "Fake-RPM-SUSE-Channel" 568ms

And I follow "Packages" 577ms

And I follow "blackhole-dummy-1.0-1.1.x86_64" 533ms

Then I should see a "blackhole-dummy-1.0-1.1.src.rpm" text 68ms

@scope_visualization
Feature:Change the user's password 16s 696ms 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 477ms 1

Given I am authorized for the "Admin" section 1s 477ms

Scenario:
Change the password to a new password
1s 645ms 10

When I follow the left menu "Home > User Account > My Account" 682ms

And I enter "GoodPass" as "desiredpassword" 56ms

And I enter "GoodPass" as "desiredpasswordConfirm" 55ms

And I click on "Update" 55ms

Then I should see a "User information updated" text 67ms

When I sign out 324ms

And I enter "admin" as "username" 37ms

And I enter "GoodPass" as "password" 50ms

And I click on "Sign In" 47ms

Then I should be logged in 269ms

Scenario:
Revert the new password to a valid standard password
1s 931ms 10

When I follow the left menu "Home > User Account > My Account" 642ms

And I enter "admin" as "desiredpassword" 45ms

And I enter "admin" as "desiredpasswordConfirm" 49ms

And I click on "Update" 50ms

Then I should see a "User information updated" text 438ms

When I sign out 312ms

And I enter "admin" as "username" 38ms

And I enter "admin" as "password" 47ms

And I click on "Sign In" 48ms

Then I should be logged in 257ms

Scenario:
Try an invalid password
11s 641ms 10

When I follow the left menu "Home > User Account > My Account" 771ms

And I enter "A" as "desiredpassword" 42ms

And I enter "A" as "desiredpasswordConfirm" 43ms

And I click on "Update" 50ms

Then I should see a "Passwords must be at least 4 characters." text 298ms

When I sign out 299ms

And I enter "admin" as "username" 38ms

And I enter "A" as "password" 42ms

And I click on "Sign In" 49ms

Then I should not be authorized 10s 5ms

@scope_configuration_channels
Feature:Clone a channel 35s 849ms 12

Scenario:
Log in as org admin user
10s 638ms 1

Given I am authorized 10s 638ms

Scenario:
Clone a channel without patches
2s 4ms 10

When I follow the left menu "Software > Manage > Channels" 172ms

And I follow "Clone Channel" 459ms

And I select "Fake-RPM-SUSE-Channel" as the origin channel 70ms

And I choose "original" 50ms

And I click on "Clone Channel" 55ms

And I enter "Fake-Clone-RPM-SLES15SP7-Channel" as "Channel Name" 203ms

And I should see a "Create Software Channel" text 82ms

And I should see a "Original state of the channel" text 74ms

And I click on "Clone Channel" 762ms

Then I should see a "Fake-Clone-RPM-SLES15SP7-Channel" text 72ms

Scenario:
Check that this channel has no patches
1s 440ms 5

When I follow the left menu "Software > Manage > Channels" 73ms

And I follow "Fake-Clone-RPM-SLES15SP7-Channel" 570ms

And I follow "Patches" in the content area 69ms

And I follow "List/Remove Patches" 670ms

Then I should see a "There are no patches associated with this channel." text 56ms

Scenario:
Clone a channel with patches
2s 232ms 10

When I follow the left menu "Software > Manage > Channels" 73ms

And I follow "Clone Channel" 438ms

And I select "Fake-RPM-SUSE-Channel" as the origin channel 56ms

And I choose "current" 47ms

And I click on "Clone Channel" 420ms

And I enter "Fake-Clone-2-RPM-SLES15SP7-Channel" as "Channel Name" 185ms

And I should see a "Create Software Channel" text 76ms

And I should see a "Current state of the channel" text 71ms

And I click on "Clone Channel" 789ms

Then I should see a "Fake-Clone-2-RPM-SLES15SP7-Channel" text 71ms

Scenario:
Check that this channel has patches
1s 260ms 8

When I follow the left menu "Software > Manage > Channels" 67ms

And I follow "Fake-Clone-2-RPM-SLES15SP7-Channel" 472ms

And I follow "Patches" in the content area 57ms

And I follow "List/Remove Patches" 620ms

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 10ms

Scenario:
Clone a channel with selected patches
4s 574ms 18

When I follow the left menu "Software > Manage > Channels" 64ms

And I follow "Clone Channel" 453ms

And I select "Fake-RPM-SUSE-Channel" as the origin channel 50ms

And I choose "select" 47ms

And I click on "Clone Channel" 410ms

And I enter "Fake-Clone-3-RPM-SLES15SP7-Channel" as "Channel Name" 181ms

And I should see a "Create Software Channel" text 78ms

And I should see a "Select patches" text 75ms

And I click on "Clone Channel" 879ms

And I should see a "Fake-Clone-3-RPM-SLES15SP7-Channel" text 87ms

And I should see a "Channel Fake-Clone-3-RPM-SLES15SP7-Channel cloned from channel Fake-RPM-SUSE-Channel." text 83ms

And I should see a "You may now wish to clone the patches associated with Fake-RPM-SUSE-Channel." text 90ms

And I check the row with the "hoag-dummy-7890" link 57ms

And I check the row with the "virgo-dummy-3456" link 55ms

And I click on "Clone Patches" 951ms

And I click on "Confirm" 991ms

Then I should see a "CL-hoag-dummy-7890" link 7ms

And I should see a "CL-virgo-dummy-3456" link 7ms

Scenario:
Check that new patches exists
1s 452ms 8

When I follow the left menu "Patches > Patch List > All" 176ms

And I enter "dummy" as the filtered synopsis 39ms

And I click on the filter button 677ms

And I select "500" from "1154021400_PAGE_SIZE_LABEL" 527ms

Then I should see a "CL-hoag-dummy-7890" link 9ms

And I should see a "CL-virgo-dummy-3456" link 7ms

And I should see a "CL-milkyway-dummy-2345" link 7ms

And I should see a "CL-andromeda-dummy-6789" link 7ms

Scenario:
Check CL-hoag-dummy-7890 patches
1s 720ms 8

When I follow the left menu "Patches > Patch List > All" 67ms

And I enter "dummy" as the filtered synopsis 34ms

And I click on the filter button 530ms

And I select "500" from "1154021400_PAGE_SIZE_LABEL" 525ms

And I follow "CL-hoag-dummy-7890" 414ms

Then I should see a "CL-hoag-dummy-7890 - Security Advisory" text 65ms

And I should see a "mcalmer" text 59ms

And I should see a "https://bugzilla.opensuse.org/show_bug.cgi?id=704608" link 22ms

Scenario:
Check CM-virgo-dummy-3456 patches
1s 826ms 8

When I follow the left menu "Patches > Patch List > All" 67ms

And I enter "dummy" as the filtered synopsis 42ms

And I click on the filter button 650ms

And I select "500" from "1154021400_PAGE_SIZE_LABEL" 503ms

And I follow "CL-virgo-dummy-3456" 426ms

Then I should see a "CL-virgo-dummy-3456 - Bug Fix Advisory" text 61ms

And I should see a "mcalmer" text 63ms

And I should see a "CVE-1999-9998" link 10ms

Scenario:
Compare channel packages
1s 934ms 9

When I follow the left menu "Software > Manage > Channels" 151ms

And I follow "Fake-Clone-2-RPM-SLES15SP7-Channel" 475ms

And I follow "Packages" in the content area 66ms

And I follow "Compare" 490ms

And I select "Fake-Clone-3-RPM-SLES15SP7-Channel" from "selected_channel" 62ms

And I click on "View Packages" 486ms

Then I should see a "andromeda-dummy" text 91ms

And I should see a "2.0-1.1" link 13ms

And I should see a "This channel only" text 95ms

Scenario:
Cleanup: remove cloned channels
6s 709ms 21

When I follow the left menu "Software > Manage > Channels" 69ms

And I follow "Fake-Clone-RPM-SLES15SP7-Channel" 467ms

And I follow "Delete Channel" 385ms

And I check "unsubscribeSystems" 76ms

And I click on "Delete Channel" 731ms

Then I should see a "Fake-Clone-RPM-SLES15SP7-Channel" text 63ms

And I should see a "has been deleted." text 58ms

Given I follow the left menu "Software > Manage > Channels" 72ms

When I follow "Fake-Clone-2-RPM-SLES15SP7-Channel" 566ms

And I follow "Delete Channel" 384ms

And I check "unsubscribeSystems" 63ms

And I click on "Delete Channel" 807ms

Then I should see a "Fake-Clone-2-RPM-SLES15SP7-Channel" text 64ms

And I should see a "has been deleted." text 59ms

Given I follow the left menu "Software > Manage > Channels" 66ms

When I follow "Fake-Clone-3-RPM-SLES15SP7-Channel" 549ms

And I follow "Delete Channel" 386ms

And I check "unsubscribeSystems" 62ms

And I click on "Delete Channel" 1s 655ms

Then I should see a "Fake-Clone-3-RPM-SLES15SP7-Channel" text 61ms

And I should see a "has been deleted." text 57ms

Scenario:
Cleanup: remove remaining systems from SSM after channel cloning tests
55ms 1

When I click on the clear SSM button 55ms

Feature:Manipulate activation keys 16s 615ms 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 666ms 1

Given I am authorized 1s 666ms

Scenario:
Create an activation key for i586
1s 728ms 8

When I follow the left menu "Systems > Activation Keys" 111ms

And I follow "Create Key" 350ms

And I wait until I do not see "Loading..." text 289ms

And I enter "SUSE Test Key i586" as "description" 68ms

And I enter "SUSE-TEST-i586" as "key" 62ms

And I check "virtualization_host" 75ms

And I click on "Create Activation Key" 57ms

Then I should see a "Activation key SUSE Test Key i586 has been created." text 712ms

Scenario:
Change limit of the i586 activation key
2s 140ms 7

When I follow the left menu "Systems > Activation Keys" 63ms

And I follow "SUSE Test Key i586" 434ms

And I wait until I do not see "Loading..." text 607ms

And I enter "20" as "usageLimit" 48ms

And I click on "Update Activation Key" 893ms

Then I wait until I see "Activation key SUSE Test Key i586 has been modified." text 70ms

And I should see "20" in field identified by "usageLimit" 22ms

Scenario:
Change the base channel of the i586 activation key
1s 268ms 6

When I follow the left menu "Systems > Activation Keys" 57ms

And I follow "SUSE Test Key i586" 412ms

And I wait until I do not see "Loading..." text 606ms

And I select "Fake-Base-Channel-i586" from "selectedBaseChannel" 67ms

And I click on "Update Activation Key" 51ms

Then I wait until I see "Activation key SUSE Test Key i586 has been modified." text 72ms

Scenario:
Delete the i586 activation key
1s 758ms 6

When I follow the left menu "Systems > Activation Keys" 59ms

And I follow "SUSE Test Key i586" in the content area 64ms

And I wait until I do not see "Loading..." text 545ms

And I follow "Delete Key" 434ms

And I click on "Delete Activation Key" 576ms

Then I should see a "Activation key SUSE Test Key i586 has been deleted." text 77ms

Scenario:
Create an activation key with a channel and a package list for i586
2s 288ms 12

When I follow the left menu "Systems > Activation Keys" 62ms

And I follow "Create Key" 245ms

And I wait until I do not see "Loading..." text 283ms

And I enter "SUSE Test PKG Key i586" as "description" 65ms

And I enter "SUSE-TEST-2-i586" as "key" 61ms

And I enter "20" as "usageLimit" 42ms

And I select "Fake-Base-Channel-i586" from "selectedBaseChannel" 48ms

And I click on "Create Activation Key" 52ms

And I follow "Packages" 537ms

And I enter "sed" as "packages" 46ms

And I click on "Update Activation Key" 786ms

Then I should see a "Activation key SUSE Test PKG Key i586 has been modified." text 55ms

Scenario:
Delete the i586 activation key with packages
1s 305ms 5

When I follow the left menu "Systems > Activation Keys" 60ms

And I follow "SUSE Test PKG Key i586" in the content area 67ms

And I follow "Delete Key" 438ms

And I click on "Delete Activation Key" 661ms

Then I should see a "Activation key SUSE Test PKG Key i586 has been deleted." text 77ms

@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 942ms 12

When I follow the left menu "Systems > Activation Keys" 58ms

And I follow "Create Key" 235ms

And I wait until I do not see "Loading..." text 287ms

And I enter "SUSE Test PKG Key x86_64" as "description" 66ms

And I enter "SUSE-TEST-x86_64" as "key" 80ms

And I enter "20" as "usageLimit" 45ms

And I select "openSUSE Tumbleweed (x86_64)" from "selectedBaseChannel" 55ms

And I click on "Create Activation Key" 771ms

And I follow "Packages" 462ms

And I enter "sed" as "packages" 45ms

And I click on "Update Activation Key" 777ms

Then I should see a "Activation key SUSE Test PKG Key x86_64 has been modified." text 56ms

@scc_credentials
Scenario:
Delete the x86_64 activation key with packages
1s 516ms 5

When I follow the left menu "Systems > Activation Keys" 61ms

And I follow "SUSE Test PKG Key x86_64" in the content area 62ms

And I follow "Delete Key" 605ms

And I click on "Delete Activation Key" 45ms

Then I should see a "Activation key SUSE Test PKG Key x86_64 has been deleted." text 742ms

@scope_api
Feature:API "activationkey" namespace 10s 309ms 4

Scenario:
List all activation keys
2s 99ms 1

Then I should get some activation keys 2s 99ms

Scenario:
Create activation key
2s 906ms 2

When I create an activation key with id "testkey", description "Key for testing", limit of 10 and contact method "default" 704ms

Then I should get the new activation key "1-testkey" 2s 202ms

Scenario:
Activation key details
838ms 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" 421ms

Then I get the description "Key description" for the activation key "1-testkey" 416ms

Scenario:
Cleanup: delete activation key
4s 465ms 1

When I delete the activation key "1-testkey" 4s 465ms

@scope_visualization
Feature:Main landing page options and preferences 53s 153ms 10 2

Scenario:
Clear browser cookies for main landing page validation
16ms 1

When I clear browser cookies 16ms

Scenario:
Access the Login page
525ms 3

Given I am not authorized 377ms

When I go to the home page 132ms

Then I should see a "Sign In" text 16ms

@uyuni
Scenario:
Access the API Documentation
10s 495ms 4

Given I am not authorized 10s 176ms

When I go to the home page 124ms

And I follow "API Documentation" 147ms

Then I should see a "API Overview" text 47ms

@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 Index" text 0s

When I click on a button within the item containing "Legal" 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 Index" text 0s

When I click on a button within the item containing "Legal" 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 799ms 6

Given I am not authorized 10s 198ms

When I go to the home page 135ms

And I enter "testing" as "username" 51ms

And I enter "testing" as "password" 62ms

And I click on "Sign In" 62ms

Then I should be logged in 289ms

Scenario:
Log out of Uyuni
12s 844ms 3

Given I am authorized 2s 32ms

When I sign out 807ms

Then I should not be authorized 10s 4ms

Scenario:
Top level bar
11s 661ms 7

Given I am authorized for the "Admin" section 10s 581ms

When I go to the home page 984ms

And I should see a "Manage" link 15ms

And I should see a "admin" text 51ms

And I should see a "SUSE Test" link 10ms

And I should see a "Preferences" link 11ms

And I should see a Sign Out link 7ms

Scenario:
Main menu as regular user
2s 29ms 14

Given I am authorized 1s 888ms

Then I should see a "Home" link 10ms

And I should see a "Systems" link 12ms

And I should see a "Salt" link 10ms

And I should see a "Images" link 10ms

And I should see a "Patches" link 11ms

And I should see a "Software" link 10ms

And I should see a "Audit" link 10ms

And I should see a "Configuration" link 16ms

And I should see a "Schedule" link 10ms

And I should see a "Users" link 10ms

And I should not see a "Admin" link 7ms

And I should see a "Help" link 10ms

And I should see a "External Links" link 10ms

Scenario:
Log in as admin user
1s 683ms 1

Given I am authorized for the "Admin" section 1s 683ms

Scenario:
Main menu as administrator
104ms 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 7ms

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 10ms

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
2s 992ms 8

Given I am authorized 1s 859ms

Then I should see a "Tasks" text 398ms

And I should see a "Inactive Systems" text 108ms

And I should see a "Most Critical Systems" text 106ms

And I should see a "Recently Scheduled Actions" text 134ms

And I should see a "Relevant Security Patches" text 141ms

And I should see a "System Group Name" text 120ms

And I should see a "Recently Registered Systems" text 124ms

@scope_api
Feature:API "user" namespace 3s 596ms 5

Scenario:
List users
525ms 2

When I call user.list_users() 525ms

Then I should get at least user "admin" < 1ms

Scenario:
List roles
310ms 2

When I call user.list_roles() on user "admin" 310ms

Then I should get at least one role that matches "_admin" suffix < 1ms

Scenario:
Create user
1s 302ms 4

When I make sure "testuser" is not present 504ms

And I call user.create() with login "testuser" 287ms

And I call user.list_users() 510ms

Then I should get at least user "testuser" < 1ms

Scenario:
Role operations
1s 157ms 6

When I call user.add_role() on "testuser" with the role "org_admin" 291ms

And I call user.list_roles() on user "testuser" 293ms

Then I should get role "org_admin" < 1ms

When I call user.remove_role() on "testuser" with the role "org_admin" 292ms

And I call user.list_roles() on user "testuser" 278ms

Then I should not get role "org_admin" < 1ms

Scenario:
Cleanup: user tests
300ms 1

When I delete user "testuser" 300ms

@scope_salt
Feature:Endpoint to download packages 3s 834ms 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
28ms 2

Given I try to download "virgo-dummy-2.0-1.1.noarch.rpm" from channel "fake-rpm-suse-channel" 28ms

Then the download should get a 403 response < 1ms

Scenario:
Download package, user with a valid token for the org
1s 23ms 3

bad3822c5e7f94126f9324daab8127b4a43046ceb267e7ffe33169d23a928fed

Given I have a valid token for organization "1" 986ms

When I try to download "virgo-dummy-2.0-1.1.noarch.rpm" from channel "fake-rpm-suse-channel" 37ms

Then the download should get no error < 1ms

Scenario:
Download package, user with an invalid token for the org
29ms 3

f4645e91ef31350b31c08826a95f54784b4ea22d4b78c4e7e5471e18aaad5269259c2df3da6768b432df7f2233c0f25c52b05c7eaf458544a0b4366f8d72e73c

Given I have an invalid token for organization "1" < 1ms

When I try to download "virgo-dummy-2.0-1.1.noarch.rpm" from channel "fake-rpm-suse-channel" 28ms

Then the download should get a 403 response < 1ms

Scenario:
Download package, user with an expired valid token for the org
686ms 3

bad3822c5e7f94126f9324daab8127b4a43046ceb267e7ffe33169d23a928fed

Given I have an expired valid token for organization "1" 657ms

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
682ms 3

bad3822c5e7f94126f9324daab8127b4a43046ceb267e7ffe33169d23a928fed

Given I have a valid token expiring tomorrow for organization "1" 648ms

When I try to download "virgo-dummy-2.0-1.1.noarch.rpm" from channel "fake-rpm-suse-channel" 33ms

Then the download should get no error < 1ms

Scenario:
Download package, user with a valid token that cant be used until tomorrow for the org
707ms 3

bad3822c5e7f94126f9324daab8127b4a43046ceb267e7ffe33169d23a928fed

Given I have a not yet usable valid token for organization "1" 678ms

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
675ms 3

bad3822c5e7f94126f9324daab8127b4a43046ceb267e7ffe33169d23a928fed

Given I have a valid token for organization "1" and channel "foobar" 646ms

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

@scope_building_container_images @no_auth_registry
Feature:Advanced content management 15s 658ms 8

Scenario:
Log in as docker user
1s 409ms 1

Given I am authorized as "docker" with password "docker" 1s 409ms

Scenario:
Create an image store as Docker admin
1s 201ms 6

When I follow the left menu "Images > Stores" 132ms

And I follow "Create" 286ms

And I enter "docker_admin" as "label" 92ms

And I enter the URI of the registry as "uri" 140ms

And I click on "create-btn" 62ms

Then I wait until table row contains a "galaxy-registry" text 486ms

@scc_credentials
Scenario:
Create a profile as Docker admin
5s 492ms 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" 2s 42ms

And I enter "suse_docker_admin" as "label" 138ms

And I select "galaxy-registry" from "imageStore" 1s 118ms

And I select "1-SUSE-KEY-x86_64" from "activationKey" 1s 117ms

And I enter "Docker/serverhost" relative to profiles as "path" 945ms

And I click on "create-btn" 65ms

Scenario:
Create a user without rights nor roles
2s 280ms 2

New user norole created with roles:

Given I am authorized for the "Admin" section 936ms

When I create a user with name "norole" and password "norole" with roles "" 1s 343ms

Scenario:
Log in as docker user
1s 504ms 1

Given I am authorized as "docker" with password "docker" 1s 504ms

@scc_credentials
Scenario:
Cleanup: remove Docker profile
1s 488ms 6

Given I am authorized as "docker" with password "docker" 468ms

When I follow the left menu "Images > Profiles" 104ms

And I check the row with the "suse_docker_admin" text 379ms

And I click on "Delete" 70ms

And I click on the red confirmation button 59ms

And I should see a "Image profile has been deleted." text 407ms

Scenario:
Cleanup: remove image store
450ms 5

When I follow the left menu "Images > Stores" 58ms

And I check the row with the "docker_admin" text 128ms

And I click on "Delete" 59ms

And I click on the red confirmation button 54ms

And I should see a "Image store has been deleted." text 148ms

Scenario:
Cleanup: delete no role user
1s 830ms 2

Given I am authorized for the "Admin" section 1s 25ms

When I delete user "norole" 804ms

@scope_visualization
Feature:Pick dates 17s 108ms 3

In order to execute actions at a certain date
As a authorized user
I want to be able to easily pick dates

Scenario:
Log in as admin user
6s 384ms 2

Given I am authorized 1s 434ms

And I am on the Systems overview page of this "sle_minion" 4s 950ms

Scenario:
Date picker is by default set to today
10s 179ms 3

When I follow "Remote Command" in the content area 70ms

And I open the date picker 75ms

Then the date picker title should be the current month and year 10s 33ms

Scenario:
Picking a time sets the hidden fields
544ms 8

When I follow "Details" in the content area 76ms

And I follow "Remote Command" in the content area 57ms

And I enter "ls" as "Script" 92ms

And I pick "2022-08-27" as date 99ms

And I pick "17:30" as time 146ms

Then the date field should be set to "2022-08-27" 35ms

And the time field should be set to "17:30" 33ms

And the date picker should be closed 3ms

@scope_visualization
Feature:Work with Union and Intersection buttons in the group list 21s 286ms 16

Scenario:
Log in as org admin user
1s 594ms 1

Given I am authorized 1s 594ms

Scenario:
Create a sles group
1s 52ms 6

When I follow the left menu "Systems > System Groups" 120ms

When I follow "Create Group" 325ms

And I enter "sles" as "name" 48ms

And I enter "SLES systems" as "description" 56ms

And I click on "Create Group" 436ms

Then I should see a "System group sles created." text 64ms

Scenario:
Add systems to the sles group
1s 975ms 6

When I follow the left menu "Systems > System Groups" 59ms

When I follow "sles" 294ms

And I follow "Target Systems" 459ms

And I check the "sle_minion" client 55ms

And I click on "Add Systems" 1s 16ms

Then I should see a "added to sles server group." text 90ms

@rhlike_minion
Scenario:
Create a rhlike group
546ms 6

When I follow the left menu "Systems > System Groups" 56ms

When I follow "Create Group" 273ms

And I enter "rhlike" as "name" 46ms

And I enter "Red Hat-like systems" as "description" 56ms

And I click on "Create Group" 50ms

Then I should see a "System group rhlike created." text 63ms

@rhlike_minion
Scenario:
Add systems to the rhlike group
3s 493ms 6

When I follow the left menu "Systems > System Groups" 61ms

When I follow "rhlike" 251ms

And I follow "Target Systems" 439ms

And I check the "rhlike_minion" client 1s 722ms

And I click on "Add Systems" 929ms

Then I should see a "1 systems were added to rhlike server group." text 90ms

@deblike_minion
Scenario:
Create a deblike group
951ms 6

When I follow the left menu "Systems > System Groups" 52ms

When I follow "Create Group" 284ms

And I enter "deblike" as "name" 46ms

And I enter "Debian-like systems" as "description" 57ms

And I click on "Create Group" 50ms

Then I should see a "System group deblike created." text 460ms

@deblike_minion
Scenario:
Add systems to the deblike group
6s 339ms 6

When I follow the left menu "Systems > System Groups" 62ms

When I follow "deblike" 317ms

And I follow "Target Systems" 459ms

And I check the "deblike_minion" client 4s 468ms

And I click on "Add Systems" 936ms

Then I should see a "1 systems were added to deblike server group." text 94ms

Scenario:
Add the sles group to SSM
211ms 4

When I follow the left menu "Systems > System Groups" 58ms

When I click on "Use in SSM" in row "sles" 67ms

And I should see a "Selected Systems List" text 68ms

And I should see "sle_minion" as link 16ms

@rhlike_minion
Scenario:
Add a union of 2 groups to SSM - Red Hat-like
582ms 6

When I follow the left menu "Systems > System Groups" 55ms

When I check "sles" in the list 54ms

And I check "rhlike" in the list 52ms

And I click on "Work With Union" 394ms

And I should see "sle_minion" as link 11ms

And I should see "rhlike_minion" as link 13ms

@rhlike_minion
Scenario:
Add an intersection of 2 groups to SSM - Red Hat-like
494ms 6

When I follow the left menu "Systems > System Groups" 53ms

When I check "sles" in the list 48ms

And I check "rhlike" in the list 47ms

And I click on "Work With Intersection" 329ms

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
662ms 6

When I follow the left menu "Systems > System Groups" 53ms

When I check "sles" in the list 47ms

And I check "deblike" in the list 52ms

And I click on "Work With Union" 485ms

And I should see "sle_minion" as link 10ms

And I should see "deblike_minion" as link 12ms

@deblike_minion
Scenario:
Add an intersection of 2 groups to SSM - Debian-like
482ms 6

When I follow the left menu "Systems > System Groups" 56ms

When I check "sles" in the list 48ms

And I check "deblike" in the list 48ms

And I click on "Work With Intersection" 316ms

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 305ms 5

When I follow the left menu "Systems > System Groups" 55ms

When I follow "sles" in the content area 70ms

And I follow "Delete Group" in the content area 61ms

And I click on "Confirm Deletion" 1s 48ms

Then I should see a "deleted" text 68ms

@rhlike_minion
Scenario:
Cleanup: remove the rhlike group
1s 245ms 5

When I follow the left menu "Systems > System Groups" 61ms

When I follow "rhlike" in the content area 61ms

And I follow "Delete Group" in the content area 55ms

And I click on "Confirm Deletion" 997ms

Then I should see a "deleted" text 70ms

@deblike_minion
Scenario:
Cleanup: remove the deblike group
286ms 5

When I follow the left menu "Systems > System Groups" 61ms

When I follow "deblike" in the content area 64ms

And I follow "Delete Group" in the content area 56ms

And I click on "Confirm Deletion" 49ms

Then I should see a "deleted" text 55ms

Scenario:
Cleanup: remove remaining systems from SSM after group union and intersection tests
60ms 1

When I click on the clear SSM button 60ms

@scope_visualization @scope_onboarding
Feature:Custom system info key-value pairs 12s 702ms 7

Scenario:
Log in as org admin user
1s 688ms 1

Given I am authorized 1s 688ms

Scenario:
Create a new key
1s 14ms 7

When I follow the left menu "Systems > Custom System Info" 109ms

And I follow "Create Key" 265ms

And I should see a "Create Custom Info Key" text 52ms

And I enter "key-label" as "label" 56ms

And I enter "key-desc" as "description" 56ms

And I click on "Create Key" 411ms

Then I should see a "Successfully added 1 custom key." text 62ms

Scenario:
Add a value to a system
3s 117ms 9

When I follow the left menu "Systems > System List > All" 126ms

And I follow this "sle_minion" link 1s 53ms

And I follow "Custom Info" 429ms

And I follow "Create Value" 423ms

And I follow "key-label" 363ms

And I enter "key-value" as "value" 51ms

And I click on "Update Key" 595ms

Then I should see a "key-label" text 63ms

And I should see a "key-value" link 11ms

Scenario:
Edit the value
2s 153ms 9

When I follow the left menu "Systems > System List > All" 106ms

And I follow this "sle_minion" link 1s 15ms

And I follow "Custom Info" 346ms

And I follow "key-value" 428ms

And I should see a "Edit Custom Value" text 66ms

And I enter "key-value-edited" as "value" 66ms

And I click on "Update Key" 47ms

Then I should see a "key-label" text 64ms

And I should see a "key-value-edited" link 11ms

Scenario:
Edit the key description
872ms 6

When I follow the left menu "Systems > Custom System Info" 60ms

And I follow "key-label" 270ms

And I enter "key-desc-edited" as "description" 82ms

And I click on "Update Key" 388ms

Then I should see a "key-label" link 11ms

And I should see a "key-desc-edited" text 58ms

Scenario:
Delete the value
2s 767ms 8

When I follow the left menu "Systems > Custom System Info" 56ms

And I follow "key-label" 270ms

And I follow this "sle_minion" link 589ms

And I follow "Custom Info" 424ms

And I follow "key-value-edited" 353ms

And I follow "Delete Value" 423ms

And I click on "Remove Value" 579ms

Then I should see a "No custom information defined for this system." text 69ms

Scenario:
Delete the key
1s 87ms 5

When I follow the left menu "Systems > Custom System Info" 59ms

And I follow "key-label" 277ms

And I follow "Delete Key" 263ms

And I click on "Delete Key" 432ms

Then I should not see a "key-label" text 55ms

@scope_tomcat
Feature:Basic web security measures and recommendations 55ms 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
10ms 1

When I clear browser cookies 10ms

Scenario:
Caching should be enabled for static content
23ms 9

When I retrieve a "css" static resource 22ms

Then the response header "ETag" should not be present < 1ms

And the response header "Pragma" should not be present < 1ms

And the response header "Expires" should not be "0" < 1ms

And the response header "Set-Cookie" should not be present < 1ms

And the response header "X-Frame-Options" should contain "SAMEORIGIN" < 1ms

And the response header "X-XSS-Protection" should be "1; mode=block" < 1ms

And the response header "X-Content-Type-Options" should be "nosniff" < 1ms

And the response header "X-Permitted-Cross-Domain-Policies" should be "master-only" < 1ms

Scenario:
Obsolete and problematic headers for static content
21ms 2

Given I retrieve a "javascript" static resource 21ms

Then the response header "X-WebKit-CSP" should not be present < 1ms

@scope_salt
Feature:Salt is configured and running 6s 413ms 3

In order to operate Uyuni based on Salt
I want to use general Salt functionality and system registration

Scenario:
salt-api is properly configured
1s 19ms 4

When I get the contents of the remote file "/etc/salt/master.d/susemanager.conf" 1s 19ms

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
1s 986ms 3

Then salt-api should be listening on local port 9080 644ms

And salt-master should be listening on public port 4505 658ms

And salt-master should be listening on public port 4506 683ms

Scenario:
There are no top.sls files in certain folders
3s 407ms 10

When I run "ls /srv/susemanager/salt/top.sls" on "server" without error control 685ms

Then the command should fail < 1ms

When I run "ls /srv/susemanager/salt/top.sls" on "server" without error control 691ms

Then the command should fail < 1ms

When I run "ls /srv/susemanager/pillar/top.sls" on "server" without error control 675ms

Then the command should fail < 1ms

When I run "ls /usr/share/susemanager/salt/top.sls" on "server" without error control 700ms

Then the command should fail < 1ms

When I run "ls /usr/share/susemanager/pillar/top.sls" on "server" without error control 654ms

Then the command should fail < 1ms

@scope_configuration_channels
Feature:The channels page 21s 472ms 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 616ms 1

Given I am authorized 10s 616ms

Scenario:
Completeness of the channels page
546ms 15

When I follow the left menu "Software > Channel List > All" 178ms

Then I should see a "Full Software Channel List" text 118ms

And I should see a "Channel List" link in the left menu 25ms

And I should see a "All" link in the left menu 22ms

And I should see a "Popular" link in the left menu 19ms

And I should see a "My Channels" link in the left menu 19ms

And I should see a "Shared" link in the left menu 19ms

And I should see a "Retired" link in the left menu 18ms

And I should see a "Package Search" link in the left menu 18ms

And I should see a "Manage" link in the left menu 21ms

And I should see a "All" link in the content area 20ms

And I should see a "Popular" link in the content area 16ms

And I should see a "My Channels" link in the content area 16ms

And I should see a "Shared" link in the content area 15ms

And I should see a "Retired" link in the content area 15ms

Scenario:
Popular channels
132ms 2

When I follow the left menu "Software > Channel List > Popular" 72ms

Then I should see a "Popular" text 59ms

Scenario:
Check packages in test channel
1s 790ms 10

When I follow the left menu "Software > Channel List > All" 68ms

And I follow "Show All Child Channels" 63ms

And I follow "Fake-RPM-SUSE-Channel" 585ms

And I follow "Packages" 560ms

Then I should see package "andromeda-dummy-2.0-1.1.noarch" 88ms

And I should see package "hoag-dummy-1.1-1.1.i586" 87ms

And I should see package "hoag-dummy-1.1-1.1.x86_64" 84ms

And I should see package "milkyway-dummy-2.0-1.1.i586" 83ms

And I should see package "milkyway-dummy-2.0-1.1.x86_64" 83ms

And I should see package "virgo-dummy-2.0-1.1.noarch" 86ms

Scenario:
Check package metadata
2s 39ms 10

When I follow the left menu "Software > Channel List > All" 65ms

And I follow "Show All Child Channels" 44ms

And I follow "Fake-RPM-SUSE-Channel" 581ms

And I follow "Packages" 550ms

And I follow "andromeda-dummy-2.0-1.1.noarch" 532ms

Then I should see a "This is the andromeda dummy package used for testing SUSE Manager" text 65ms

And I should see a "Fake-RPM-SUSE-Channel" link 10ms

And I should see a "build.opensuse.org" text 62ms

And I should see a "SHA512sum:" text 63ms

And I should see a "packages/1/199/andromeda-dummy/2.0-1.1/noarch/19940cc4a9f0d38a038a4455b0f1cf1290c4a4296b27f5a62f4aae60585ac6e2677e88c3c3127d487116ed8d9b1787379e23aafac46bc14408864926bedee693/andromeda-dummy-2.0-1.1.noarch.rpm" text 63ms

Scenario:
Check package dependencies page
2s 215ms 9

When I follow the left menu "Software > Channel List > All" 102ms

And I follow "Show All Child Channels" 56ms

And I follow "Fake-RPM-SUSE-Channel" 555ms

And I follow "Packages" 564ms

And I follow "andromeda-dummy-2.0-1.1.noarch" 428ms

And I follow "Dependencies" 358ms

Then I should see a "pam" text 52ms

And I should see a "rpmlib(PayloadIsXz) <= 5.2-1" text 47ms

And I should see a "andromeda-dummy = 2.0-1.1" text 48ms

Scenario:
Check package change log page
2s 17ms 8

When I follow the left menu "Software > Channel List > All" 102ms

And I follow "Show All Child Channels" 53ms

And I follow "Fake-RPM-SUSE-Channel" 571ms

And I follow "Packages" 477ms

And I follow "andromeda-dummy-2.0-1.1.noarch" 427ms

And I follow "Change Log" 289ms

Then I should see a "mc@suse.de" text 47ms

And I should see a "version 2.0" text 47ms

Scenario:
Check package file list page
2s 113ms 9

When I follow the left menu "Software > Channel List > All" 99ms

And I follow "Show All Child Channels" 43ms

And I follow "Fake-RPM-SUSE-Channel" 575ms

And I follow "Packages" 493ms

And I follow "andromeda-dummy-2.0-1.1.noarch" 441ms

And I follow "File List" 289ms

Then I should see a "This package contains the following files." text 57ms

And I should see a "/usr/share/doc/packages/andromeda-dummy/COPYING" text 53ms

And I should see a "sha256: 32b1062f7da84967e7019d01ab805935caa7ab7321a7ced0e30ebe75e5df1670" text 59ms

@scope_visualization
Feature:Managing channels 12s 204ms 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 778ms 1

Given I am authorized 1s 778ms

Scenario:
Fail when trying to add a duplicate channel
1s 219ms 10

When I follow the left menu "Software > Manage > Channels" 169ms

And I follow "Create Channel" 369ms

And I enter "Fake-Base-Channel-SUSE-like" as "Channel Name" 114ms

And I enter "fake-base-channel-suse-like" as "Channel Label" 105ms

And I select "None" from "Parent Channel" 52ms

And I select "x86_64" from "Architecture:" 42ms

And I enter "Base channel for testing" as "Channel Summary" 98ms

And I enter "No more desdcription for base channel." as "Channel Description" 120ms

And I click on "Create Channel" 69ms

Then I should see a "The channel name 'Fake-Base-Channel-SUSE-like' is already in use, please enter a different name" text 76ms

Scenario:
Fail when trying to use invalid characters in the channel label
1s 65ms 7

When I follow the left menu "Software > Manage > Channels" 71ms

And I follow "Create Channel" 345ms

And I enter "test123" as "Channel Name" 63ms

And I enter "tesT123" as "Channel Label" 63ms

And I enter "test123" as "Channel Summary" 63ms

And I click on "Create Channel" 381ms

Then I should see a "Invalid channel label, please see the format described below" text 77ms

Scenario:
Fail when trying to use invalid characters in the channel name
1s 72ms 7

When I follow the left menu "Software > Manage > Channels" 70ms

And I follow "Create Channel" 378ms

And I enter "!test123" as "Channel Name" 64ms

And I enter "test123" as "Channel Label" 63ms

And I enter "test123" as "Channel Summary" 62ms

And I click on "Create Channel" 358ms

Then I should see a "Invalid channel name, please see the format described below" text 73ms

@scc_credentials
Scenario:
Fail when trying to use reserved names for channels
1s 132ms 7

When I follow the left menu "Software > Manage > Channels" 73ms

And I follow "Create Channel" 365ms

And I enter "openSUSE-Leap-15.6-Pool for x86_64" as "Channel Name" 116ms

And I enter "test123" as "Channel Label" 63ms

And I enter "test123" as "Channel Summary" 61ms

And I click on "Create Channel" 376ms

Then I should see a "The channel name 'openSUSE-Leap-15.6-Pool for x86_64' is reserved, please enter a different name" text 75ms

@scc_credentials
Scenario:
Fail when trying to use reserved labels for channels
1s 121ms 7

When I follow the left menu "Software > Manage > Channels" 69ms

And I follow "Create Channel" 365ms

And I enter "test123" as "Channel Name" 64ms

And I enter "opensuse-leap-15.6-pool-x86_64" as "Channel Label" 103ms

And I enter "test123" as "Channel Summary" 60ms

And I click on "Create Channel" 381ms

Then I should see a "The channel label 'opensuse-leap-15.6-pool-x86_64' is reserved, please enter a different name" text 74ms

Scenario:
Create a channel that will be changed
1s 477ms 7

When I follow the left menu "Software > Manage > Channels" 67ms

And I follow "Create Channel" 348ms

And I enter "aaaSLE-12-Cloud-Compute5-Pool for x86_64" as "Channel Name" 128ms

And I enter "sle-we12aaa-pool-x86_64-sap" as "Channel Label" 108ms

And I enter "test123" as "Channel Summary" 64ms

And I click on "Create Channel" 686ms

Then I should see a "Channel aaaSLE-12-Cloud-Compute5-Pool for x86_64 created." text 72ms

@scc_credentials
Scenario:
Fail when trying to change the channel name to a reserved name
1s 420ms 5

When I follow the left menu "Software > Manage > Channels" 71ms

And I follow "aaaSLE-12-Cloud-Compute5-Pool for x86_64" 556ms

And I enter "openSUSE-Leap-15.6-Pool for x86_64" as "Channel Name" 189ms

And I click on "Update Channel" 528ms

Then I should see a "The channel name 'openSUSE-Leap-15.6-Pool for x86_64' is reserved, please enter a different name" text 74ms

Scenario:
Cleanup: Delete created channel
1s 918ms 6

When I follow the left menu "Software > Manage > Channels" 72ms

And I follow "aaaSLE-12-Cloud-Compute5-Pool for x86_64" 552ms

And I follow "Delete Channel" 464ms

And I check "unsubscribeSystems" 75ms

And I click on "Delete Channel" 663ms

Then I should see a "Channel aaaSLE-12-Cloud-Compute5-Pool for x86_64 has been deleted." text 89ms

@scope_visualization
Feature:Left Menu Filter 2s 160ms 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 475ms 1

Given I am authorized for the "Admin" section 1s 475ms

Scenario:
Search a word and expect the right result
101ms 2

When I enter "Admin" as the left menu search field 78ms

Then I should see a "Admin" link in the left menu 23ms

Scenario:
Search a partial word and expect the right result
101ms 2

When I enter "Formula" as the left menu search field 81ms

Then I should see a "Formula Catalog" link in the left menu 19ms

Scenario:
Search a word with a different case and expect the right result
99ms 2

When I enter "saLT" as the left menu search field 79ms

Then I should see a "Salt" link in the left menu 19ms

@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
261ms 3

When I enter "Uyuni" as the left menu search field 79ms

Then I should see a "Uyuni Server" text 74ms

And I should see a "Uyuni Proxy" text 107ms

Scenario:
Search a non-existing word and expect no results
120ms 2

When I enter "Null" as the left menu search field 112ms

Then I should see left menu empty 7ms

@scope_api
Feature:API "channel" namespace and sub-namespaces 7s 446ms 10

Scenario:
Create a custom software channel
650ms 2

When I create the following channels: 312ms
LABEL NAME SUMMARY ARCH PARENT
foobar foobar foobar channel-x86_64

Then "foobar" should get listed with a call of listSoftwareChannels 337ms

Scenario:
Create a repository
1s 635ms 4

When I create a repo with label "foobar" and url 294ms

And I associate repo "foobar" with channel "foobar" 441ms

Then channel "foobar" should have attribute "last_modified" that is a date 430ms

And channel "foobar" should not have attribute "yumrepo_last_sync" 469ms

Scenario:
Create a custom software channel as the child of another one
1s 137ms 3

When I create the following channels: 358ms
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 344ms

And "foobar" should be the parent channel of "foobar-child" 433ms

Scenario:
List software channels
340ms 1

Then something should get listed with a call of listSoftwareChannels 340ms

Scenario:
Delete a child software channel
802ms 2

When I delete the software channel with label "foobar-child" 437ms

Then "foobar-child" should not get listed with a call of listSoftwareChannels 364ms

Scenario:
Delete a software channel
1s 228ms 3

When I delete the repo with label "foobar" 314ms

And I delete the software channel with label "foobar" 578ms

Then "foobar" should not get listed with a call of listSoftwareChannels 335ms

Scenario:
Check last synchronization of a synced channel
336ms 1

Then channel "fake-child-channel-i586" should have attribute "yumrepo_last_sync" that is a date 336ms

@rhlike_minion
Scenario:
Verify if a channel is modular via the API
676ms 2

When I verify channel "fake-base-channel-appstream" is modular via the API 328ms

And I verify channel "fake-rpm-suse-channel" is not modular via the API 348ms

@rhlike_minion
Scenario:
List modular channels via the API
313ms 1

When channel "Fake-Base-Channel-AppStream" is present in the modular channels listed via the API 313ms

@rhlike_minion
Scenario:
List available module streams for a given channel via the API
327ms 1

When "scorpio" module streams "2.0, 2.1" are available for channel "fake-base-channel-appstream" via the API 327ms

@scope_visualization
Feature:Patches page 11s 796ms 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 556ms 1

Given I am authorized 1s 556ms

Scenario:
Patches left menu
421ms 11

When I follow the left menu "Patches > Patch List > Relevant" 170ms

Then I should see a "Patches Relevant to Your Systems" text 109ms

And I should see a "Relevant" link in the left menu 21ms

And I should see a "All" link in the left menu 23ms

And I should see a "Advanced Search" link in the left menu 21ms

And I should see a "Manage Patches" link in the left menu 19ms

And I should see a "Clone Patches" link in the left menu 19ms

And I should see a "Bugfix Patches" link 10ms

And I should see a "Enhancement Patches" link 10ms

And I should see a "Security Patches" link 10ms

And I should see a Sign Out link 6ms

Scenario:
Create new bugfix patch with bnc URL
2s 128ms 18

When I follow the left menu "Patches > Manage Patches" 62ms

And I follow "Create Patch" 315ms

When I enter "Test Patch" as "synopsis" 79ms

And I enter "Test Advisory" as "advisoryName" 79ms

And I enter "Test Product" as "product" 75ms

And I enter "test@test.org" as "errataFrom" 88ms

And I enter "Test Topic" as "topic" 69ms

And I enter "Test Description" as "description" 80ms

And I enter "Test Solution" as "solution" 75ms

And I enter "620212" as "buglistId" 60ms

And I enter "Test Summary" as "buglistSummary" 72ms

And I enter "https://bugzilla.opensuse.org/show_bug.cgi?id=620212" as "buglistUrl" 163ms

And I enter "test,keywords" as "keywords" 79ms

And I enter "Test Reference" as "refersTo" 77ms

And I enter "Test Note" as "notes" 74ms

And I check test channel 58ms

And I click on "Create Patch" 543ms

Then I should see a "Patch: Test Advisory-1" text 70ms

Scenario:
Create new enhancement patch with no bnc URL
2s 805ms 17

When I follow the left menu "Patches > Manage Patches" 61ms

And I follow "Create Patch" 320ms

When I enter "Enhancement Patch" as "synopsis" 86ms

And I enter "Enhancement Advisory" as "advisoryName" 86ms

And I select "Product Enhancement Advisory" from "advisoryType" 65ms

And I enter "Enhancement Product" as "product" 83ms

And I enter "Enhancement Topic" as "topic" 78ms

And I enter "Enhancement Description" as "description" 90ms

And I enter "Enhancement Solution" as "solution" 82ms

And I enter "1234" as "buglistId" 50ms

And I enter "Enhancement Summary" as "buglistSummary" 82ms

And I enter "Enhancement,keywords" as "keywords" 88ms

And I enter "Enhancement Reference" as "refersTo" 89ms

And I enter "Enhancement Note" as "notes" 78ms

And I check test channel 54ms

And I click on "Create Patch" 52ms

Then I should see a "Patch: Enhancement Advisory-1" text 1s 351ms

Scenario:
Delete enhancement patch
1s 226ms 5

When I follow the left menu "Patches > Manage Patches" 59ms

And I check "Enhancement Advisory" patch 60ms

And I click on "Delete Patches" 452ms

And I click on "Confirm" 543ms

Then I should see a "Successfully deleted 1 patches." text 109ms

Scenario:
Verify patch presence in web UI
1s 593ms 15

When I follow the left menu "Patches > Patch List > All" 146ms

And I follow "Bugfix Patches" in the content area 74ms

And I enter "Test Patch" as the filtered synopsis 52ms

And I click on the filter button 466ms

And I follow "Test Advisory" 353ms

Then I should see a "Test Patch" text 59ms

And I should see a "test@test.org" text 58ms

And I should see a "Test Topic" text 58ms

And I should see a "Test Description" text 65ms

And I should see a "Test Solution" text 58ms

And I should see a "Fake-Base-Channel-SUSE-like" link 11ms

And I should see a "Test Summary" link 10ms

And I should see a "keywords, test" text 58ms

And I should see a "Test Reference" text 59ms

And I should see a "Test Note" text 60ms

Scenario:
Assert that patch is now in test base channel
759ms 4

When I follow the left menu "Software > Channel List > All" 168ms

And I follow "Fake-Base-Channel-SUSE-like" 467ms

And I follow "Patches" in the content area 62ms

Then I should see a "Test Patch" text 60ms

Scenario:
Delete patch
1s 306ms 5

When I follow the left menu "Patches > Manage Patches" 96ms

And I check "Test Advisory" patch 56ms

And I click on "Delete Patches" 515ms

And I click on "Confirm" 530ms

Then I should see a "Successfully deleted 1 patches." text 108ms

@scc_credentials @scope_content_lifecycle_management @new_issue
Feature:Content lifecycle 10m 41s 693ms 46 4

Scenario:
Log in as org admin user
1s 615ms 1

Given I am authorized 1s 615ms

Scenario:
Create CLM filter to remove all fonts packages
3s 820ms 10

When I follow the left menu "Content Lifecycle > Filters" 886ms

And I click on "Create Filter" 108ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 11ms

Then I should see a "Create a new filter" text 59ms

And I enter "remove fonts packages" as "filter_name" 114ms

And I select "Package (Name)" from "type" 1s 137ms

And I select "contains" from "matcher" 1s 115ms

And I enter "fonts" as "name" 73ms

And I click on "Save" in "Create a new filter" modal 256ms

Then I should see a "remove fonts packages" text 57ms

Scenario:
Create a content lifecycle project
1s 373ms 9

When I follow the left menu "Content Lifecycle > Projects" 58ms

And I follow "Create Project" 397ms

Then I should see a "Create a new Content Lifecycle Project" text 52ms

And I should see a "Project Properties" text 49ms

When I enter "clp_label" as "label" 61ms

And I enter "clp_name" as "name" 55ms

And I enter "clp_desc" as "description" 63ms

And I click on "Create" 56ms

And I wait until I see "Content Lifecycle Project - clp_name" text 576ms

Scenario:
Verify the content lifecycle project page
847ms 9

When I follow the left menu "Content Lifecycle > Projects" 61ms

Then I should see a "clp_name" text 55ms

And I should see a "clp_desc" text 51ms

When I follow "clp_name" 381ms

Then I should see a "Project Properties" text 61ms

And I should see a "Versions history" text 57ms

And I should see a "Sources" text 56ms

And I should see a "Filters" text 61ms

And I should see a "Environment Lifecycle" text 58ms

@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 143ms 8

When I follow the left menu "Content Lifecycle > Projects" 57ms

And I follow "clp_name" 411ms

And I click on "Attach/Detach Sources" 69ms

And I select "openSUSE Tumbleweed (x86_64)" from "selectedBaseChannel" 1s 112ms

And I wait until I see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" text 89ms

And I click on "Save" 61ms

And I wait until I see "openSUSE Tumbleweed (x86_64)" text 281ms

Then I should see a "Version 1: (draft - not built) - Check the changes below" text 59ms

@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
555ms 4

When I follow the left menu "Content Lifecycle > Projects" 57ms

And I follow "clp_name" 374ms

Then I should see a "openSUSE Tumbleweed (x86_64)" text 62ms

And I should see a "Build (1)" text 60ms

Scenario:
Add fonts packages filter to the project
1s 255ms 10

When I follow the left menu "Content Lifecycle > Projects" 63ms

And I follow "clp_name" 375ms

Then I should see a "Content Lifecycle Project - clp_name" text 65ms

When I click on "Attach/Detach Filters" 64ms

And I check the "remove fonts packages" CLM filter 179ms

And I click on "Save" 49ms

And I wait until I see "Deny" text 277ms

Then I should see a "remove fonts packages" text 67ms

When I follow the left menu "Content Lifecycle > Filters" 55ms

Then I should see a "clp_name" text 57ms

Scenario:
Add environments to the project
3s 681ms 25

When I follow the left menu "Content Lifecycle > Projects" 56ms

And I follow "clp_name" 385ms

Then I should see a "No environments created" text 70ms

When I click on "Add Environment" 68ms

And I enter "dev_name" as "name" 75ms

And I enter "dev_label" as "label" 68ms

And I enter "dev_desc" as "description" 65ms

And I click on "Save" 54ms

Then I wait until I see "dev_name" text 292ms

And I should see a "dev_desc" text 67ms

When I click on "Add Environment" 60ms

And I enter "prod_name" as "name" 69ms

And I enter "prod_label" as "label" 73ms

And I enter "prod_desc" as "description" 66ms

And I click on "Save" 53ms

Then I wait until I see "prod_name" text 317ms

And I should see a "prod_desc" text 75ms

When I click on "Add Environment" 60ms

And I enter "qa_name" as "name" 65ms

And I enter "qa_label" as "label" 70ms

And I enter "qa_desc" as "description" 66ms

And I select "prod_name" from "predecessorLabel" 1s 117ms

And I click on "Save" 54ms

Then I wait until I see "qa_name" text 235ms

And I should see a "qa_desc" text 85ms

@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 410ms 9

When I follow the left menu "Content Lifecycle > Projects" 59ms

And I follow "clp_name" 402ms

Then I should see a "not built" text in the environment "qa_name" 21ms

When I click on "Build (2)" 65ms

Then I should see a "Version 1 history" text 91ms

When I enter "test version message 1" as "message" 64ms

And I click the environment build button 55ms

And I wait until I see "Version 1: test version message 1" text in the environment "dev_name" 291ms

And I wait at most 600 seconds until I see "Built" text in the environment "dev_name" 1m 359ms

Scenario:
Promote the sources in the project
2m 2s 284ms 15

When I follow the left menu "Content Lifecycle > Projects" 75ms

Then I should see a "clp_name" text 60ms

And I should see a "clp_desc" text 51ms

And I should see a "dev_name > qa_name > prod_name" text 51ms

When I follow "clp_name" 386ms

Then I should see a "qa_desc" text in the environment "qa_name" 20ms

And I should see a "not built" text in the environment "qa_name" 16ms

When I click promote from Development to QA 57ms

Then I should see a "Version 1: test version message 1" text 94ms

And I click on "Promote environment" in "Promote version 1 into qa_name" modal 308ms

Then I wait at most 600 seconds until I see "Built" text in the environment "qa_name" 1m 351ms

When I click promote from QA to Production 60ms

Then I should see a "Version 1: test version message 1" text 95ms

And I click on "Promote environment" in "Promote version 1 into prod_name" modal 296ms

Then I wait at most 600 seconds until I see "Built" text in the environment "prod_name" 1m 356ms

@skip_if_github_validation
Scenario:
Add new sources and promote again
2m 55s 599ms 27

When I follow the left menu "Content Lifecycle > Projects" 77ms

And I follow "clp_name" 444ms

Then I should see a "Build (0)" text 93ms

When I click on "Attach/Detach Sources" 72ms

And I uncheck "Vendors" 10s 959ms

And I enter "Fake-Base-Channel-SUSE-like" in the placeholder "Search a channel" 126ms

And I add the "Fake-Base-Channel-SUSE-like" channel to sources 72ms

And I click on "Save" 69ms

Then I wait until I see "Fake-Base-Channel-SUSE-like" text 526ms

And I wait until I see "Build (1)" text 90ms

And I should see a "Version 2: (draft - not built) - Check the changes below" text 87ms

When I click on "Build (1)" 65ms

Then I wait until I see "Version 2 history" text 93ms

When I enter "test version message 2" as "message" 62ms

And I click the environment build button 53ms

Then I wait until I see "Version 2: test version message 2" text in the environment "dev_name" 333ms

And I wait at most 600 seconds until I see "Built" text in the environment "dev_name" 45s 446ms

When I click promote from Development to QA 59ms

Then I should see a "Version 2: test version message 2" text 94ms

And I click on "Promote environment" in "Promote version 2 into qa_name" modal 386ms

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 409ms

When I click promote from QA to Production 60ms

Then I should see a "Version 2: test version message 2" text 94ms

And I click on "Promote environment" in "Promote version 2 into prod_name" modal 383ms

And I wait for "1" second 1s

Then I wait at most 600 seconds until I see "Built" text in the environment "prod_name" 54s 434ms

Scenario:
Create a CLM filter of type Package(NEVRA) that allows packages whose version and release number are lower to a defined one
13s 317ms 15

When I follow the left menu "Content Lifecycle > Filters" 79ms

And I click on "Create Filter" 69ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 28ms

Then I should see a "Create a new filter" text 75ms

When I enter "mercury" as "filter_name" 74ms

And I select "Package (NEVRA)" from "type" 1s 132ms

And I select "lower" from "matcher" 1s 105ms

And I enter "mercury" as "Package Name" 85ms

And I enter "mercury" as "Epoch" 81ms

And I enter "0.0.0" as "version" 66ms

And I enter "0.0.0" as "Release" 75ms

And I enter "x86_64" as "Architecture" 83ms

And I check radio button "Allow" 10s 68ms

And I click on "Save" in "Create a new filter" modal 224ms

Then I should see a "Filter created successfully" text 65ms

Scenario:
Create a CLM filter of type Package(NEVRA) that denys packages whose version and release number are lower to a defined one
3s 107ms 15

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 58ms

And I click on "Create Filter" 57ms

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 71ms

When I enter "venus" as "filter_name" 62ms

And I select "Package (NEVRA)" from "type" 1s 107ms

And I select "lower" from "matcher" 1s 97ms

And I enter "venus" as "Package Name" 73ms

And I enter "venus" as "Epoch" 69ms

And I enter "0.0.0" as "version" 65ms

And I enter "0.0.0" as "Release" 70ms

And I enter "x86_64" as "Architecture" 70ms

And I check radio button "Deny" 18ms

And I click on "Save" in "Create a new filter" modal 209ms

Then I should see a "Filter created successfully" text 68ms

Scenario:
Create CLM filter that allows packages of type Package (Provides Name)
2s 860ms 10

When I follow the left menu "Content Lifecycle > Filters" 64ms

And I click on "Create Filter" 61ms

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 73ms

When I enter "cereal" as "filter_name" 57ms

And I select "Package (Provides Name)" from "type" 1s 112ms

And I select "provides name" from "matcher" 1s 110ms

And I enter "cereal" as "Provides Name" 80ms

And I click on "Save" in "Create a new filter" modal 221ms

Then I should see a "Filter created successfully" text 69ms

Scenario:
Create CLM filter that denys packages of type Package (Provides Name)
2s 871ms 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 59ms

And I click on "Create Filter" 59ms

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 75ms

When I enter "potato" as "filter_name" 57ms

And I select "Package (Provides Name)" from "type" 1s 113ms

And I select "provides name" from "matcher" 1s 103ms

And I enter "potato" as "Provides Name" 72ms

And I check radio button "Deny" 15ms

And I click on "Save" in "Create a new filter" modal 239ms

Then I should see a "Filter created successfully" text 67ms

Scenario:
Create CLM filter of type Package (Build date) that allows packages whose date is lower than a defined one
12s 865ms 10

When I follow the left menu "Content Lifecycle > Filters" 53ms

And I click on "Create Filter" 58ms

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 78ms

When I enter "cherry" as "filter_name" 57ms

And I select "Package (Build date)" from "type" 1s 126ms

And I select "lower" from "matcher" 1s 101ms

And I check radio button "Allow" 10s 85ms

And I click on "Save" in "Create a new filter" modal 226ms

Then I should see a "Filter created successfully" text 70ms

Scenario:
Create CLM filter of type Package (Build date) that denys packages whose date is lower than a defined one
2s 827ms 10

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 56ms

And I click on "Create Filter" 58ms

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 83ms

When I enter "drummer" as "filter_name" 59ms

And I select "Package (Build date)" from "type" 1s 127ms

And I select "lower" from "matcher" 1s 108ms

And I check radio button "Deny" 15ms

And I click on "Save" in "Create a new filter" modal 232ms

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
12s 982ms 11

When I follow the left menu "Content Lifecycle > Filters" 59ms

And I click on "Create Filter" 63ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 7ms

Then I should see a "Create a new filter" text 86ms

When I enter "africa-patch" as "filter_name" 75ms

And I select "Patch (Advisory Name)" from "type" 1s 122ms

And I select "equals" from "matcher" 1s 95ms

And I enter "africa" as "Advisory name" 80ms

And I check radio button "Allow" 10s 60ms

And I click on "Save" in "Create a new filter" modal 254ms

Then I should see a "Filter created successfully" text 76ms

Scenario:
Create CLM filter of type Patch(Advisory Name) that denys patches that are equal to a defined one
2s 900ms 11

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 92ms

When I enter "asia-patch" as "filter_name" 70ms

And I select "Patch (Advisory Name)" from "type" 1s 115ms

And I select "equals" from "matcher" 1s 97ms

And I enter "asia" as "Advisory name" 69ms

And I check radio button "Deny" 16ms

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 Type) that allows Security Advisory patches that are equal to a defined one
12s 970ms 11

Warning: Radio button 'Security Advisory' is already checked

When I follow the left menu "Content Lifecycle > Filters" 52ms

And I click on "Create Filter" 85ms

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 91ms

When I enter "key" as "filter_name" 49ms

And I select "Patch (Advisory Type)" from "type" 1s 116ms

And I select "equals" from "matcher" 1s 98ms

And I check radio button "Security Advisory" 18ms

And I check radio button "Allow" 10s 111ms

And I click on "Save" in "Create a new filter" modal 249ms

Then I should see a "Filter created successfully" text 88ms

Scenario:
Create CLM filter of type Patch(Advisory Type) that denys Security Advisory patches that are equal to a defined one
2s 912ms 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" 64ms

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 99ms

When I enter "geminis-patch" as "filter_name" 78ms

And I select "Patch (Advisory Type)" from "type" 1s 110ms

And I select "equals" from "matcher" 1s 101ms

And I check radio button "Security Advisory" 15ms

And I check radio button "Deny" 15ms

And I click on "Save" in "Create a new filter" modal 264ms

Then I should see a "Filter created successfully" text 92ms

Scenario:
Create CLM filter of type Patch(Synopsis) that allows patches that that are equal to a defined one
13s 25ms 11

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 7ms

Then I should see a "Create a new filter" text 96ms

When I enter "aries-patch" as "filter_name" 71ms

And I select "Patch (Synopsis)" from "type" 1s 114ms

And I select "equals" from "matcher" 1s 101ms

And I enter "aries" as "Synopsis" 78ms

And I check radio button "Allow" 10s 65ms

And I click on "Save" in "Create a new filter" modal 270ms

Then I should see a "Filter created successfully" text 92ms

Scenario:
Create CLM filter of type Patch(Synopsis) that denys patches that are equal to a defined one
2s 987ms 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 57ms

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 99ms

When I enter "andromeda-patch" as "filter_name" 83ms

And I select "Patch (Synopsis)" from "type" 1s 115ms

And I select "equals" from "matcher" 1s 102ms

And I enter "andromeda" as "Synopsis" 90ms

And I check radio button "Deny" 16ms

And I click on "Save" in "Create a new filter" modal 255ms

Then I should see a "Filter created successfully" text 97ms

Scenario:
Create CLM filter of type Patch(Keyword) that allows patches that contains Package Manager Restart Required keyword in its name
23s 68ms 11

When I follow the left menu "Content Lifecycle > Filters" 60ms

And I click on "Create Filter" 68ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 107ms

When I enter "mars-patch" as "filter_name" 70ms

And I select "Patch (Keyword)" from "type" 1s 127ms

And I select "contains" from "matcher" 1s 103ms

And I check radio button "Package Manager Restart Required" 10s 89ms

And I check radio button "Allow" 10s 73ms

And I click on "Save" in "Create a new filter" modal 260ms

Then I should see a "Filter created successfully" text 96ms

Scenario:
Create CLM filter of type Patch(Keyword) that denys patches that contains Package Manager Restart Required Keyword in its name
13s 31ms 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 55ms

And I click on "Create Filter" 85ms

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 114ms

When I enter "eurasia-patch" as "filter_name" 78ms

And I select "Patch (Keyword)" from "type" 1s 115ms

And I select "contains" from "matcher" 1s 106ms

And I check radio button "Package Manager Restart Required" 10s 85ms

And I check radio button "Deny" 18ms

And I click on "Save" in "Create a new filter" modal 260ms

Then I should see a "Filter created successfully" text 103ms

Scenario:
Create CLM filter of type Patch(Issue date) that allows patches whose date is greater or equal than a defined one
13s 19ms 10

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 7ms

Then I should see a "Create a new filter" text 109ms

When I enter "milkyway-patch" as "filter_name" 84ms

And I select "Patch (Issue date)" from "type" 1s 133ms

And I select "greater or equal" from "matcher" 1s 118ms

And I check radio button "Allow" 10s 88ms

And I click on "Save" in "Create a new filter" modal 258ms

Then I should see a "Filter created successfully" text 100ms

Scenario:
Create CLM filter of type Patch(Issue date) that denys patches whose date is greater or equal than a defined one
3s 112ms 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 59ms

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 116ms

When I enter "venus-patch" as "filter_name" 76ms

And I select "Patch (Issue date)" from "type" 1s 118ms

And I select "greater or equal" from "matcher" 1s 98ms

When I enter "solar" as "filter_name" 135ms

And I check radio button "Deny" 15ms

And I click on "Save" in "Create a new filter" modal 314ms

Then I should see a "Filter created successfully" text 104ms

Scenario:
Create CLM filter of type Patch(Contains Package Name) that allows patches that are equal to a specific one
13s 168ms 11

When I follow the left menu "Content Lifecycle > Filters" 58ms

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 119ms

When I enter "Triangulum-patch" as "filter_name" 88ms

And I select "Patch (Contains Package Name)" from "type" 1s 120ms

And I select "equals" from "matcher" 1s 116ms

When I enter "Triangulum-patch" as "Package Name" 123ms

And I check radio button "Allow" 10s 66ms

And I click on "Save" in "Create a new filter" modal 298ms

Then I should see a "Filter created successfully" text 106ms

Scenario:
Create CLM filter of type Patch(Contains Package Name) that denys patches that are equal to a specific one
3s 111ms 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 64ms

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 117ms

When I enter "Pinwheel-patch" as "filter_name" 81ms

And I select "Patch (Contains Package Name)" from "type" 1s 116ms

And I select "equals" from "matcher" 1s 107ms

When I enter "Pinwheel-patch" as "Package Name" 111ms

And I check radio button "Deny" 17ms

And I click on "Save" in "Create a new filter" modal 308ms

Then I should see a "Filter created successfully" text 115ms

Scenario:
Create CLM filter that allows patches of type Patch(Contains Package Name) that matches to a specific one
13s 186ms 11

When I follow the left menu "Content Lifecycle > Filters" 56ms

And I click on "Create Filter" 89ms

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 122ms

When I enter "Sunflower-patch" as "filter_name" 85ms

And I select "Patch (Contains Package Name)" from "type" 1s 121ms

And I select "matches" from "matcher" 1s 108ms

When I enter "Sunflower-patch" as "Package Name" 109ms

And I check radio button "Allow" 10s 67ms

And I click on "Save" in "Create a new filter" modal 302ms

Then I should see a "Filter created successfully" text 115ms

Scenario:
Create CLM filter of type Patch(Contains Package Name) that denys patches that matches to a specific one
3s 104ms 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 60ms

And I click on "Create Filter" 70ms

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 129ms

When I enter "Whirlpool-patch" as "filter_name" 87ms

And I select "Patch (Contains Package Name)" from "type" 1s 120ms

And I select "matches" from "matcher" 1s 95ms

When I enter "Whirlpool-patch" as "Package Name" 108ms

And I check radio button "Deny" 15ms

And I click on "Save" in "Create a new filter" modal 286ms

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 151ms 11

When I follow the left menu "Content Lifecycle > Filters" 54ms

And I click on "Create Filter" 64ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 11ms

Then I should see a "Create a new filter" text 131ms

When I enter "Antennae-patch" as "filter_name" 80ms

And I select "Patch (Contains Package Provides Name)" from "type" 1s 119ms

And I select "provides name" from "matcher" 1s 103ms

When I enter "Antennae-patch" as "Package Provides Name" 112ms

And I check radio button "Allow" 10s 65ms

And I click on "Save" in "Create a new filter" modal 289ms

Then I should see a "Filter created successfully" text 119ms

Scenario:
Create CLM filter of type Patch(Contains Package Provides Name) that denys patches with a specific name
3s 79ms 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 60ms

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 130ms

When I enter "hat-patch" as "filter_name" 65ms

And I select "Patch (Contains Package Provides Name)" from "type" 1s 124ms

And I select "provides name" from "matcher" 1s 102ms

When I enter "hat-patch" as "Package Provides Name" 89ms

And I check radio button "Deny" 20ms

And I click on "Save" in "Create a new filter" modal 284ms

Then I should see a "Filter created successfully" text 128ms

Scenario:
Create CLM filter of type Patch(Contains Package) that allows patches whose version is lower than a specific one
13s 520ms 14

When I follow the left menu "Content Lifecycle > Filters" 63ms

And I click on "Create Filter" 66ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 9ms

Then I should see a "Create a new filter" text 136ms

When I enter "Hubble-patch" as "filter_name" 77ms

And I select "Patch (Contains Package)" from "type" 1s 117ms

And I select "version lower than" from "matcher" 1s 106ms

When I enter "Hubble-patch" as "Package Name" 103ms

And I enter "Hubble-patch" as "Epoch" 104ms

And I enter "0.0.0" as "Version" 73ms

And I enter "0.0.0" as "Release" 75ms

And I check radio button "Allow" 10s 62ms

And I click on "Save" in "Create a new filter" modal 391ms

Then I should see a "Filter created successfully" text 131ms

Scenario:
Create CLM filter of type Patch(Contains Package) that denys patches whose version is lower than a specific one
3s 384ms 14

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 61ms

And I click on "Create Filter" 66ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 141ms

When I enter "galaxy-patch" as "filter_name" 76ms

And I select "Patch (Contains Package)" from "type" 1s 122ms

And I select "version lower than" from "matcher" 1s 105ms

When I enter "galaxy-patch" as "Package Name" 102ms

And I enter "galaxy-patch" as "Epoch" 97ms

And I enter "0.0.0" as "Version" 67ms

And I enter "0.0.0" as "Release" 69ms

And I check radio button "Deny" 16ms

And I click on "Save" in "Create a new filter" modal 314ms

Then I should see a "Filter created successfully" text 134ms

Scenario:
Create CLM filter of type Patch(Contains Package) that allows patches whose version is lower or equal than a specific one
13s 452ms 14

When I follow the left menu "Content Lifecycle > Filters" 59ms

And I click on "Create Filter" 66ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 9ms

Then I should see a "Create a new filter" text 144ms

When I enter "earth-patch" as "filter_name" 72ms

And I select "Patch (Contains Package)" from "type" 1s 124ms

And I select "version lower or equal" from "matcher" 1s 112ms

When I enter "earth-patch" as "Package Name" 98ms

And I enter "earth-patch" as "Epoch" 93ms

And I enter "0.0.0" as "Version" 67ms

And I enter "0.0.0" as "Release" 72ms

And I check radio button "Allow" 10s 75ms

And I click on "Save" in "Create a new filter" modal 316ms

Then I should see a "Filter created successfully" text 139ms

Scenario:
Create CLM filter of type Patch(Contains Package) that denys patches whose version is lower or equal than a specific one
3s 367ms 14

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 59ms

And I click on "Create Filter" 65ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 149ms

When I enter "moon-patch" as "filter_name" 70ms

And I select "Patch (Contains Package)" from "type" 1s 124ms

And I select "version lower or equal" from "matcher" 1s 116ms

When I enter "moon-patch" as "Package Name" 98ms

And I enter "moon-patch" as "Epoch" 93ms

And I enter "0.0.0" as "Version" 68ms

And I enter "0.0.0" as "Release" 72ms

And I check radio button "Deny" 16ms

And I click on "Save" in "Create a new filter" modal 292ms

Then I should see a "Filter created successfully" text 131ms

Scenario:
Create CLM filter to enable Ruby 2.7 module
3s 305ms 11

When I follow the left menu "Content Lifecycle > Filters" 113ms

And I click on "Create Filter" 102ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 145ms

And I enter "ruby 2.7 module" as "filter_name" 89ms

And I select "Module (Stream)" from "type" 1s 119ms

And I select "equals" from "matcher" 1s 121ms

And I enter "ruby" as "moduleName" 73ms

And I enter "2.7" as "moduleStream" 57ms

And I click on "Save" in "Create a new filter" modal 335ms

Then I should see a "Filter created successfully" text 138ms

Scenario:
Create CLM filter that allows Product Temporary Fix (All)
3s 61ms 10

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 56ms

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 148ms

When I enter "mars" as "filter_name" 54ms

And I select "Product Temporary Fix (All)" from "type" 1s 121ms

And I select "all" from "matcher" 1s 106ms

And I check radio button "Deny" 15ms

And I click on "Save" in "Create a new filter" modal 334ms

Then I should see a "Filter created successfully" text 142ms

Scenario:
Create CLM filter that denys Product Temporary Fix (All)
3s 80ms 10

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 54ms

And I click on "Create Filter" 65ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 8ms

Then I should see a "Create a new filter" text 147ms

When I enter "mercury-patch" as "filter_name" 80ms

And I select "Product Temporary Fix (All)" from "type" 1s 124ms

And I select "all" from "matcher" 1s 110ms

And I check radio button "Deny" 15ms

And I click on "Save" in "Create a new filter" modal 322ms

Then I should see a "Filter created successfully" text 151ms

Scenario:
Create CLM filter of type Product Temporary Fix (Number) that allows packages of a version lower than a specific one
13s 198ms 11

When I follow the left menu "Content Lifecycle > Filters" 59ms

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 144ms

When I enter "jupiter-patch" as "filter_name" 80ms

And I select "Product Temporary Fix (Number)" from "type" 1s 123ms

And I select "lower" from "matcher" 1s 112ms

And I enter "1" as "Number" 70ms

And I check radio button "Allow" 10s 54ms

And I click on "Save" in "Create a new filter" modal 325ms

Then I should see a "Filter created successfully" text 144ms

Scenario:
Create CLM filter of type Product Temporary Fix (Number) that denys packages of a version lower than a specific one
3s 134ms 11

Warning: Radio button 'Deny' is already checked

When I follow the left menu "Content Lifecycle > Filters" 64ms

And I click on "Create Filter" 98ms

And I wait at most 10 seconds until I see modal containing "Create a new filter" text 9ms

Then I should see a "Create a new filter" text 144ms

When I enter "pluto-patch" as "filter_name" 73ms

And I select "Product Temporary Fix (Number)" from "type" 1s 114ms

And I select "lower" from "matcher" 1s 116ms

And I enter "2" as "Number" 60ms

And I check radio button "Deny" 16ms

And I click on "Save" in "Create a new filter" modal 302ms

Then I should see a "Filter created successfully" text 133ms

@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 188ms 11

When I follow the left menu "Content Lifecycle > Filters" 55ms

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 144ms

When I enter "comet-patch" as "filter_name" 72ms

And I select "Product Temporary Fix (Fixes Package Name)" from "type" 1s 119ms

And I select "equals" from "matcher" 1s 112ms

And I enter "comet-patch" as "Package Name" 96ms

And I check radio button "Allow" 10s 78ms

And I click on "Save" in "Create a new filter" modal 292ms

Then I should see a "Filter created successfully" text 131ms

Scenario:
Cleanup: remove the Content Lifecycle Management project
1s 174ms 5

When I follow the left menu "Content Lifecycle > Projects" 64ms

And I follow "clp_name" 683ms

And I click on "Delete" 73ms

And I click on "Delete" in "Delete Project" modal 95ms

Then I should not see a "clp_name" text 258ms

Scenario:
Cleanup: remove the CLM filters
4s 266ms 32

When I follow the left menu "Content Lifecycle > Filters" 59ms

And I click on "Select unused" 115ms

And I click on "Delete" 97ms

Then I should not see a "remove fonts packages" text 142ms

And I should not see a "africa-patch" text 2s 531ms

And I should not see a "andromeda-patch" text 50ms

And I should not see a "Antennae-patch" text 50ms

And I should not see a "aries-patch" text 47ms

And I should not see a "asia-patch" text 51ms

And I should not see a "cereal" text 48ms

And I should not see a "comet-patch" text 47ms

And I should not see a "cherry" text 47ms

And I should not see a "drummer" text 47ms

And I should not see a "earth-patch" text 47ms

And I should not see a "galaxy-patch" text 47ms

And I should not see a "hat-patch" text 50ms

And I should not see a "Hubble-patch" text 47ms

And I should not see a "mars" text 52ms

And I should not see a "mars-patch" text 50ms

And I should not see a "mercury" text 48ms

And I should not see a "milkyway-patch" text 47ms

And I should not see a "moon-patch" text 48ms

And I should not see a "Pinwheel-patch" text 47ms

And I should not see a "pluto-patch" text 50ms

And I should not see a "solar" text 48ms

And I should not see a "Sunflower-patch" text 48ms

And I should not see a "Triangulum-patch" text 52ms

And I should not see a "venus" text 48ms

And I should not see a "Whirlpool-patch" text 48ms

And I should not see a "remove fonts packages" text 48ms

And I should not see a "ruby 2.7 module" text 48ms

And I should not see a "key" text 48ms

@susemanager
Scenario:
Cleanup: remove the created channels
< 1ms 4

When I delete these channels with spacewalk-remove-channel: 0s
clp_label-prod_label-fake-base-channel-suse-like
clp_label-prod_label-sle-product-sles15-sp7-updates-x86_64
clp_label-qa_label-fake-base-channel-suse-like
clp_label-qa_label-sle-product-sles15-sp7-updates-x86_64
clp_label-dev_label-fake-base-channel-suse-like
clp_label-dev_label-sle-product-sles15-sp7-updates-x86_64

And I delete these channels with spacewalk-remove-channel: 0s
clp_label-prod_label-sle-product-sles15-sp7-pool-x86_64
clp_label-qa_label-sle-product-sles15-sp7-pool-x86_64
clp_label-dev_label-sle-product-sles15-sp7-pool-x86_64

And I list channels with spacewalk-remove-channel 0s

Then I shouldn't get "clp_label" 0s

@skip_if_github_validation @uyuni
Scenario:
Cleanup: remove the created channels
2s 309ms 3

When I delete these channels with spacewalk-remove-channel: 1s 369ms
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 940ms

Then I shouldn't get "clp_label" < 1ms

@scope_recurring_actions
Feature:Change the schedule of a task 42s 945ms 4

Scenario:
Log in as admin user
1s 825ms 1

Given I am authorized for the "Admin" section 1s 825ms

Scenario:
Change the schedule of task sandbox-cleanup-default to weekly
13s 676ms 10

When I follow the left menu "Admin > Task Schedules" 114ms

And I follow "sandbox-cleanup-default" 1s 236ms

And I check radio button "weekly" 10s 75ms

And I select "Friday" from "date_day_week" 62ms

And I click on "Update Schedule" 607ms

Then I should see a "Schedule sandbox-cleanup-default has been updated." text 80ms

When I follow the left menu "Admin > Task Schedules" 64ms

And I follow "sandbox-cleanup-default" 1s 343ms

Then I should see a "Friday" text 78ms

And radio button "weekly" should be checked 15ms

Scenario:
Change the schedule of task sandbox-cleanup-default to monthly
13s 748ms 9

When I follow the left menu "Admin > Task Schedules" 55ms

And I follow "sandbox-cleanup-default" 1s 341ms

And I check radio button "monthly" 10s 83ms

And I select "17" from "date_day_month" 61ms

And I click on "Update Schedule" 701ms

Then I should see a "Schedule sandbox-cleanup-default has been updated." text 81ms

When I follow the left menu "Admin > Task Schedules" 65ms

And I follow "sandbox-cleanup-default" 1s 342ms

Then radio button "monthly" should be checked 14ms

Scenario:
Change the schedule of task sandbox-cleanup-default back to daily
13s 695ms 8

When I follow the left menu "Admin > Task Schedules" 53ms

And I follow "sandbox-cleanup-default" 1s 348ms

And I check radio button "daily" 10s 75ms

And I click on "Update Schedule" 699ms

Then I should see a "Schedule sandbox-cleanup-default has been updated." text 87ms

When I follow the left menu "Admin > Task Schedules" 58ms

And I follow "sandbox-cleanup-default" 1s 357ms

Then radio button "daily" should be checked 15ms

@scope_visualization
Feature:Test the notification/notification-messages feature 13s 35ms 4

Scenario:
Log in as org admin user
1s 882ms 1

Given I am authorized 1s 882ms

Scenario:
Check the unread notification counter is correct
10s 404ms 4

All notification-messages are read, I expect no notification badge

When I follow the left menu "Home > Notification Messages" 65ms

And I wait until I see "The server has collected the following notification messages." text 261ms

Then I follow "Unread Messages" 59ms

And the notification badge and the table should count the same amount of messages 10s 18ms

Scenario:
Delete notification-messages
316ms 5

There are no notification messages, nothing to do then

When I follow the left menu "Home > Notification Messages" 57ms

And I wait until I see "The server has collected the following notification messages." text 147ms

Then I follow "All Messages" 84ms

Then I check the first notification message 13ms

And I delete it via the "Delete" button 13ms

Scenario:
Flag a notification-message as read
432ms 5

There are no notification messages, nothing to do then

When I follow the left menu "Home > Notification Messages" 54ms

And I wait until I see "The server has collected the following notification messages." text 299ms

Then I follow "All Messages" 53ms

Then I check the first notification message 12ms

And I mark as read it via the "Mark as Read" button 11ms

Feature:Pay as you go 2m 12s 955ms 9

In order to use payg
As admin user
I want to list available ssh connections and add or remove them

Scenario:
Log in as admin user
1s 805ms 1

Given I am authorized for the "Admin" section 1s 805ms

Scenario:
Enter minimal information for payg ssh connection data
2s 70ms 11

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 822ms

And I click on "Add PAYG Connection" 335ms

And I enter "My Instance" as "description" 89ms

And I enter "my-host.local" as "host" 81ms

And I enter "root" as "username" 52ms

And I click on "Create" 64ms

Then I should see a "PAYG my-host.local created successfully" text 548ms

And I should see a "My Instance" text in element "Info-panel-wrapper" 19ms

And I should see a "my-host.local" text in element "Instance-panel-wrapper" 20ms

And I should see a "root" text in element "Instance-panel-wrapper" 18ms

And I should see a "Delete" button 18ms

Scenario:
Enter full information for payg ssh connection data
1m 2s 924ms 31

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 67ms

And I click on "Add PAYG Connection" 440ms

And I enter "My Full Instance" as "description" 91ms

And I enter "my-host-full.local" as "host" 92ms

And I enter "21" as "port" 49ms

And I enter "rootFull" as "username" 64ms

And I enter "passwordFull" as "password" 74ms

And I enter "keyFull" as "key" 68ms

And I enter "keyPasswordFull" as "key_password" 86ms

And I enter "my-bastion.local" as "bastion_host" 88ms

And I enter "22" as "bastion_port" 49ms

And I enter "b_rootFull" as "bastion_username" 84ms

And I enter "b_passwordFull" as "bastion_password" 85ms

And I enter "b_keyFull" as "bastion_key" 80ms

And I enter "b_keyPasswordFull" as "bastion_key_password" 91ms

And I click on "Create" 53ms

Then I should see a "PAYG my-host-full.local created successfully" text 1s 77ms

And I should see a "My Full Instance" text in element "Info-panel-wrapper" 16ms

And I should see a "my-host-full.local" text in element "Instance-panel-wrapper" 17ms

And I should see a "21" text in element "Instance-panel-wrapper" 17ms

And I should see a "rootFull" text in element "Instance-panel-wrapper" 17ms

And I should not see a "passwordFull" text in element "Instance-panel-wrapper" 10s 24ms

And I should not see a "keyFull" text in element "Instance-panel-wrapper" 10s 22ms

And I should not see a "keyPasswordFull" text in element "Instance-panel-wrapper" 10s 13ms

And I should see a "my-bastion.local" text in element "Bastion-panel-wrapper" 19ms

And I should see a "22" text in element "Bastion-panel-wrapper" 16ms

And I should see a "b_rootFull" text in element "Bastion-panel-wrapper" 16ms

And I should not see a "b_passwordFull" text in element "Bastion-panel-wrapper" 10s 18ms

And I should not see a "b_keyFull" text in element "Bastion-panel-wrapper" 10s 26ms

And I should not see a "b_keyPasswordFull" text in element "Bastion-panel-wrapper" 10s 31ms

And I should see a "Delete" button 18ms

Scenario:
Check pay-as-you-go list
250ms 5

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 87ms

Then I should see a "my-host.local" link 12ms

And I should see a "My Instance" text 72ms

And I should see a "my-host-full.local" link 11ms

And I should see a "My Full Instance" text 66ms

Scenario:
Edit connection description
986ms 7

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 64ms

And I follow "my-host-full.local" 416ms

And I click on "Edit Information" 62ms

And I enter "My new Full Instance" as "description" 117ms

And I click on "Save" in "Information" modal 234ms

Then I should see a "PAYG properties updated successfully" text 72ms

And I should see a "My new Full Instance" text in element "Info-panel-wrapper" 18ms

Scenario:
Edit instance ssh connection data
31s 943ms 15

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 67ms

And I follow "my-host-full.local" 381ms

And I click on "Edit Instance" 62ms

And I enter "221" as "port" 55ms

And I enter "NewRootFull" as "username" 94ms

And I enter "NewPasswordFull" as "password" 82ms

And I enter "newKeyFull" as "key" 78ms

And I enter "newKeyPasswordFull" as "key_password" 106ms

And I click on "Save" in "Instance SSH connection" modal 830ms

Then I should see a "PAYG properties updated successfully" text 72ms

And I should see a "221" text in element "Instance-panel-wrapper" 21ms

And I should see a "NewRootFull" text in element "Instance-panel-wrapper" 17ms

And I should not see a "NewPasswordFull" text in element "Instance-panel-wrapper" 10s 33ms

And I should not see a "newKeyFull" text in element "Instance-panel-wrapper" 10s 12ms

And I should not see a "newKeyPasswordFull" text in element "Instance-panel-wrapper" 10s 27ms

Scenario:
Edit bastion ssh connection data
31s 546ms 17

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 89ms

And I follow "my-host-full.local" 324ms

And I click on "Edit Bastion" 84ms

And I enter "my-new-bastion.local" as "bastion_host" 147ms

And I enter "222" as "bastion_port" 55ms

And I enter "b_new_rootFull" as "bastion_username" 101ms

And I enter "b_new_passwordFull" as "bastion_password" 86ms

And I enter "b_new_keyFull" as "bastion_key" 90ms

And I enter "b_new_keyPasswordFull" as "bastion_key_password" 96ms

And I click on "Save" in "Bastion SSH connection" modal 256ms

Then I should see a "PAYG properties updated successfully" text 76ms

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" 18ms

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 21ms

And I should not see a "b_new_keyFull" text in element "Bastion-panel-wrapper" 10s 29ms

And I should not see a "b_new_keyPasswordFull" text in element "Bastion-panel-wrapper" 10s 27ms

Scenario:
Cleanup: delete minimal information for payg ssh connection data
819ms 6

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 90ms

And I follow "my-host.local" 340ms

And I click on "Delete" 67ms

And I click on "Delete" in "Delete PAYG Connection" modal 84ms

Then I should not see a "my-host.local" link 7ms

And I should not see a "my-host.local" text 228ms

Scenario:
Cleanup: delete full information for payg ssh connection data
608ms 6

When I follow the left menu "Admin > Setup Wizard > PAYG Connections" 69ms

And I follow "my-host-full.local" 323ms

And I click on "Delete" 56ms

And I click on "Delete" in "Delete PAYG Connection" modal 76ms

Then I should not see a "my-bastion.local" link 7ms

And I should not see a "my-host.local" text 72ms

@sle_minion @scc_credentials @skip_if_github_validation @bug_reported
Feature:Push a package with unset vendor 1m 25s 720ms 1 3

In order to distribute software to the clients
As an authorized user
I want to push a package with unset vendor

Scenario:
Log in as org admin user
1s 833ms 1

Given I am authorized 1s 833ms

Scenario:
Pre-requisite: mgr-push package must be installed on the SLES minion
42s 952ms 12 1

Event Details: ---------- ID: sync_states Function: saltutil.sync_states Name: sync_states Result: true Comment: No updates to sync Started: 14:25:23.458007 Duration: 265.072 SLS: util.syncstates Changed: {} ---------- ID: mgr_absent_ca_package Function: pkg.removed Name: rhn-org-trusted-ssl-cert Result: true Comment: All specified packages are already absent Started: 14:25:28.851432 Duration: 11.181 SLS: certs Changed: {} ---------- ID: mgr_ca_cert Function: file.managed Name: /etc/pki/trust/anchors/RHN-ORG-TRUSTED-SSL-CERT Result: true Comment: File /etc/pki/trust/anchors/RHN-ORG-TRUSTED-SSL-CERT is in the correct state Started: 14:25:28.865367 Duration: 37.751 SLS: certs Changed: {} ---------- ID: update-ca-certificates Function: cmd.run Name: /usr/sbin/update-ca-certificates Result: true Comment: State was not run because none of the onchanges reqs changed Started: 14:25:28.904343 Duration: 0.005 SLS: certs Changed: {} ---------- ID: mgr_proxy_ca_cert_symlink Function: file.symlink Name: /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT Result: true Comment: onlyif condition is false Started: 14:25:28.904444 Duration: 717.024 SLS: certs Changed: {} ---------- ID: mgr_deploy_tools_uyuni_key Function: file.managed Name: /etc/pki/rpm-gpg/uyuni-tools-gpg-pubkey-0d20833e.key Result: true Comment: File /etc/pki/rpm-gpg/uyuni-tools-gpg-pubkey-0d20833e.key is in the correct state Started: 14:25:29.621629 Duration: 39.049 SLS: channels.gpg-keys Changed: {} ---------- ID: mgr_deploy_suse_addon_key Function: file.managed Name: /etc/pki/rpm-gpg/suse-addon-97a636db0bad8ecc.key Result: true Comment: File /etc/pki/rpm-gpg/suse-addon-97a636db0bad8ecc.key is in the correct state Started: 14:25:29.660810 Duration: 36.932 SLS: channels.gpg-keys Changed: {} ---------- ID: mgr_deploy_suse16_gpg_key Function: file.managed Name: /etc/pki/rpm-gpg/suse16-gpg-pubkey-09d9ea69.key Result: true Comment: File /etc/pki/rpm-gpg/suse16-gpg-pubkey-09d9ea69.key is in the correct state Started: 14:25:29.697883 Duration: 40.221 SLS: channels.gpg-keys Changed: {} ---------- ID: file_///etc/pki/rpm-gpg/uyuni-tools-gpg-pubkey-0d20833e.key Function: mgrcompat.module_run Name: pkg.add_repo_key Result: true Comment: Module function pkg.add_repo_key executed Started: 14:25:29.738379 Duration: 28.573 SLS: channels.gpg-keys Changed: ret: true ---------- ID: file_///usr/lib/rpm/gnupg/keys/gpg-pubkey-29b700a4-62b07e22.asc Function: mgrcompat.module_run Name: pkg.add_repo_key Result: true Comment: Module function pkg.add_repo_key executed Started: 14:25:29.767098 Duration: 25.614 SLS: channels.gpg-keys Changed: ret: true ---------- ID: mgrchannels_repo Function: file.managed Name: /etc/zypp/repos.d/susemanager:channels.repo Result: true Comment: File /etc/zypp/repos.d/susemanager:channels.repo is in the correct state Started: 14:25:29.792951 Duration: 141.326 SLS: channels Changed: {} ---------- ID: pkg_installed Function: pkg.installed Name: pkg_installed Result: false Comment: An error was encountered while installing package(s): Zypper command failure: Running as unit: run-p14113-i14114.scope; invocation ID: 39204ca084df410f99d2f7570b55f1e1Loading repository data... Reading installed packages... Resolving package dependencies... Problem: 1: nothing provides 'python3-defusedxml' needed by the to be installed python3-rhnlib-5.2.1-2.3.uyuni.noarch Solution 1: do not install mgr-push-5.2.1-2.3.uyuni.noarch Solution 2: break python3-rhnlib-5.2.1-2.3.uyuni.noarch by ignoring some of its dependencies Choose from above solutions by number or cancel [1/2/c/d/?] (c): c Started: 14:25:29.934777 Duration: 1905.259 SLS: packages.pkginstall Changed: {}

Given I am on the Systems overview page of this "sle_minion" 1s 518ms

When I follow "Software" in the content area 70ms

And I wait until I see "Upgrade Packages" text 67ms

And I follow "Install" 509ms

And I wait until I see "Installable Packages" text 123ms

And I enter "mgr-push" as the filtered package name 45ms

And I click on the filter button 603ms

And I check "mgr-push" in the list 61ms

And I click on "Install Packages" 608ms

And I click on "Confirm" 742ms

Then I should see a "1 package install has been scheduled for" text 64ms

And I wait until event "Package Install/Upgrade scheduled" is completed 24s 916ms Show Error + 
                                            
 unknown error - Event failed (SystemCallError)
./features/step_definitions/navigation_steps.rb:96:in `block (2 levels) in (top (required))'
./features/support/commonlib.rb:106:in `block in repeat_until_timeout'
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/step_definitions/navigation_steps.rb:88:in `/^I wait at most (\d+) seconds until the event is completed, refreshing the page$/'
./features/step_definitions/common_steps.rb:157:in `/^I wait (\d+) seconds until the event is picked up and (\d+) seconds until the event "([^"]*)" is completed$/'
./features/step_definitions/common_steps.rb:174:in `/^I wait at most (\d+) seconds until event "([^"]*)" is completed$/'
./features/step_definitions/common_steps.rb:151:in `/^I wait until event "([^"]*)" is completed$/'
features/secondary/srv_push_package.feature:29:in `I wait until event "Package Install/Upgrade scheduled" is completed'

13s 622ms Show Info + 
14:25:16:000 - 14:25:46:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010023&aid=307
Screenshot +

Scenario:
Push a package with unset vendor through the SLES minion
16s 71ms 2 1 1

When I copy unset package file on "sle_minion" 2s 38ms

And I push package "/root/subscription-tools-1.0-0.noarch.rpm" into "fake-base-channel-suse-like" channel through "sle_minion" 420ms Show Error + 
                                            
 FAIL: mgrpush -u admin -p admin --server=uyuni-master-server.sumaci.aws --nosig -c fake-base-channel-suse-like /root/subscription-tools-1.0-0.noarch.rpm returned status code = 127.
Output:
 (ScriptError)
./features/support/remote_node.rb:169:in `run_local'
./features/support/remote_node.rb:117:in `run'
./features/step_definitions/common_steps.rb:327:in `/^I push package "([^"]*)" into "([^"]*)" channel through "([^"]*)"$/'
features/secondary/srv_push_package.feature:33:in `I push package "/root/subscription-tools-1.0-0.noarch.rpm" into "fake-base-channel-suse-like" channel through "sle_minion"'

Then I should see package "subscription-tools-1.0-0.noarch" in channel "Fake-Base-Channel-SUSE-like" 0s

13s 611ms Show Info + 
14:26:00:000 - 14:26:02:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010023&aid=307
Screenshot +

Scenario:
Check vendor of package displayed in web UI
24s 862ms 4 2 1

When I follow the left menu "Software > Channel List > All" 185ms

And I follow "Fake-Base-Channel-SUSE-like" 576ms

And I follow "Packages" 474ms

And I follow "subscription-tools-1.0-0.noarch" 10s 7ms Show Error + 
                                            
 Unable to find link "subscription-tools-1.0-0.noarch" (Capybara::ElementNotFound)
./features/support/commonlib.rb:198:in `click_link_and_wait'
./features/step_definitions/navigation_steps.rb:339:in `/^I follow "([^"]*)"$/'
features/secondary/srv_push_package.feature:40:in `I follow "subscription-tools-1.0-0.noarch"'

Then I should see a "Vendor:" text 0s

And I should see a "Not defined" text 0s

13s 618ms Show Info + 
14:26:16:000 - 14:26:27:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/channels/ChannelPackages.do?cid=121
Screenshot +

@skip_if_github_validation @scope_reportdb @new_issue
Feature:Report database 1m 14s 989ms 9 1

In order to use reporting tools
As an authorized user
I want to access and use the report database named "ReportDB"

Scenario:
Log in as admin user
1s 707ms 1

Given I am authorized for the "Admin" section 1s 707ms

Scenario:
Populate the report database after bootstrapping minions
13s 637ms 1

When I schedule a task to update ReportDB 13s 637ms

Scenario:
Connect to the ReportDB on the server with admin user
2s 48ms 2

Then I should be able to connect to the ReportDB on the server 1s 244ms

And there should be a user allowed to create roles on the ReportDB 804ms

Scenario:
Create read-only user
2s 959ms 2

When I create a read-only user for the ReportDB 2s 133ms

Then I should see the read-only user listed on the ReportDB user accounts 826ms

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
4ms 6

Then I should not be able to "insert" data in a ReportDB "table" as a read-only user 1ms

And I should not be able to "update" data in a ReportDB "table" as a read-only user 1ms

And I should not be able to "delete" data in a ReportDB "table" as a read-only user < 1ms

And I should not be able to "insert" data in a ReportDB "view" as a read-only user < 1ms

And I should not be able to "update" data in a ReportDB "view" as a read-only user < 1ms

And I should not be able to "delete" data in a ReportDB "view" as a read-only user < 1ms

Scenario:
ReportDB admin user can't access product database from external machine
1s 449ms 3

Given I know the ReportDB admin user credentials 1s 325ms

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 62ms

Scenario:
The systems should match between the UI and the ReportDB
10s 192ms 3

When I follow the left menu "Systems > System List > All" 185ms

And I make a list of the existing systems 10s 5ms

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
24s 831ms 4

Search by hostname: uyuni-master-suse-minion
[{"last_boot"=>"2026-02-02T12:06:47Z", "name"=>"uyuni-master-suse-minion.sumaci.aws", "id"=>1000010023, "last_checkin"=>"2026-02-02T13:25:31Z"}]

Given I have a property "City" with value "Arrakeen" on "sle_minion" 7s 550ms

And I know the current synced_date for "sle_minion" 1ms

When I schedule a task to update ReportDB 17s 279ms

Then I should find the updated "City" property as "Arrakeen" on the "sle_minion", on ReportDB 1ms

Scenario:
Cleanup: delete read-only user
18s 90ms 2 1

When I delete the read-only user for the ReportDB 3s 279ms

Then I shouldn't see the read-only user listed on the ReportDB user accounts 1s 4ms Show Error + 
                                            
 Created read-only user on the ReportDB remains listed (ScriptError)
./features/step_definitions/command_steps.rb:1424:in `/^I shouldn't see the read-only user listed on the ReportDB user accounts$/'
features/secondary/srv_reportdb.feature:57:in `I shouldn't see the read-only user listed on the ReportDB user accounts'

13s 807ms Show Info + 
14:27:41:000 - 14:27:46:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/admin/BunchDetail.do?label=mgr-update-reporting-bunch
Screenshot +

@flaky
Feature:Distribution Channel Mapping 3m 32s 127ms 12 3

Scenario:
Log in as org admin user
1s 771ms 1

Given I am authorized 1s 771ms

Scenario:
Check if Distribution Channel Mapping page exists
277ms 8

When I follow the left menu "Software > Distribution Channel Mapping" 110ms

Then I should see a "Distribution Channel Mapping" text 50ms

And I should see a "Channel List" link in the left menu 23ms

And I should see a "Package Search" link in the left menu 19ms

And I should see a "Manage" link in the left menu 22ms

And I should see a "Distribution Channel Mapping" link in the left menu 18ms

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 22ms

@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 253ms 9

When I follow the left menu "Software > Distribution Channel Mapping" 55ms

And I follow "Create Distribution Channel Mapping" 307ms

Then I should see a "Create Distribution Channel Map" text 57ms

When I enter "openSUSE Tumbleweed" as "os" 67ms

And I enter "20250928" as "release" 53ms

And I select "x86_64" from "architecture" 62ms

And I select "openSUSE Tumbleweed (x86_64)" from "channel_label" 55ms

And I click on "Create Mapping" 570ms

Then I should see a "openSUSE Tumbleweed" link in the content area 23ms

@deblike_minion
Scenario:
Create new map for amd64 Ubuntu clients with test base channel
684ms 9

When I follow the left menu "Software > Distribution Channel Mapping" 62ms

And I follow "Create Distribution Channel Mapping" 291ms

Then I should see a "Create Distribution Channel Map" text 58ms

When I enter "Ubuntu 24.04" as "os" 53ms

And I enter "24.04" as "release" 43ms

And I select "AMD64 Debian" from "architecture" 51ms

And I select "Fake-Base-Channel-Debian-like" from "channel_label" 49ms

And I click on "Create Mapping" 49ms

Then I should see a "Ubuntu 24.04" link in the content area 23ms

@scc_credentials
Scenario:
Create new map for iSeries SUSE clients using test channel
1s 250ms 9

When I follow the left menu "Software > Distribution Channel Mapping" 56ms

And I follow "Create Distribution Channel Mapping" 346ms

Then I should see a "Create Distribution Channel Map" text 54ms

When I enter "SUSE Linux Enterprise Server 15 SP 4 iSeries" as "os" 84ms

And I enter "15.5" as "release" 44ms

And I select "iSeries" from "architecture" 51ms

And I select "Fake-Base-Channel-i586" from "channel_label" 49ms

And I click on "Create Mapping" 541ms

Then I should see a "SUSE Linux Enterprise Server 15 SP 4 iSeries" link in the content area 20ms

@scc_credentials @susemanager
Scenario:
Update map for x86_64 SUSE clients using test-x86_64 channel
< 1ms 11

When I follow the left menu "Software > Distribution Channel Mapping" 0s

Then I should see the text "SUSE Linux Enterprise Server 15 SP 4" in the Operating System field 0s

And I should see the text "x86_64" in the Architecture field 0s

And I should see the text "sle-product-sles15-sp7-pool-x86_64" in the Channel Label field 0s

When I follow "SUSE Linux Enterprise Server 15 SP 4" 0s

Then I should see a "Update Distribution Channel Map" text 0s

When I enter "SUSE Linux Enterprise Server 15 SP 4 modified" as "os" 0s

And I select "SLE-Product-SLES15-SP7-Pool for x86_64" from "channel_label" 0s

And I click on "Update Mapping" 0s

Then I should see the text "SUSE Linux Enterprise Server 15 SP 4 modified" in the Operating System field 0s

And I should see the text "sle-product-sles15-sp7-pool-x86_64" in the Channel Label field 0s

@scc_credentials @uyuni
Scenario:
Update map for x86_64 openSUSE clients using test-x86_64 channel
51s 328ms 11

When I follow the left menu "Software > Distribution Channel Mapping" 64ms

Then I should see the text "openSUSE Tumbleweed" in the Operating System field 10s 2ms

And I should see the text "x86_64" in the Architecture field 10s 13ms

And I should see the text "opensuse_tumbleweed-x86_64" in the Channel Label field 10s 13ms

When I follow "openSUSE Tumbleweed" 364ms

Then I should see a "Update Distribution Channel Map" text 54ms

When I enter "openSUSE Tumbleweed modified" as "os" 98ms

And I select "openSUSE Tumbleweed (x86_64)" from "channel_label" 43ms

And I click on "Update Mapping" 658ms

Then I should see the text "openSUSE Tumbleweed modified" in the Operating System field 10s 3ms

And I should see the text "opensuse_tumbleweed-x86_64" in the Channel Label field 10s 12ms

@deblike_minion
Scenario:
Update map for amd64 Ubuntu clients using test base channel
40s 550ms 8

When I follow the left menu "Software > Distribution Channel Mapping" 79ms

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 10ms

And I should see the text "fake-base-channel-debian-like" in the Channel Label field 10s 10ms

When I follow "Ubuntu 24.04" 295ms

And I enter "Ubuntu 24.04 modified" as "os" 85ms

And I click on "Update Mapping" 58ms

Then I should see the text "Ubuntu 24.04 modified" in the Operating System field 10s 2ms

@scc_credentials
Scenario:
Update map for IA-32 SUSE clients using amd deb test channel
51s 242ms 10

When I follow the left menu "Software > Distribution Channel Mapping" 72ms

Then I should see the text "SUSE Linux Enterprise Server 15 SP 4 iSeries" in the Operating System field 10s 3ms

And I should see the text "iSeries" in the Architecture field 10s 3ms

And I should see the text "fake-base-channel-i586" in the Channel Label field 10s 3ms

When I follow "SUSE Linux Enterprise Server 15 SP 4 iSeries" 356ms

And I enter "SUSE Linux Enterprise Server 15 SP 4 iSeries modified" as "os" 142ms

And I select "Fake-Base-Channel-Debian-like" from "channel_label" 60ms

And I click on "Update Mapping" 589ms

Then I should see the text "SUSE Linux Enterprise Server 15 SP 4 iSeries modified" in the Operating System field 10s 3ms

And I should see the text "fake-base-channel-debian-like" in the Channel Label field 10s 6ms

@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 205ms 10

When I follow the left menu "Software > Distribution Channel Mapping" 75ms

Then I should see the text "openSUSE Tumbleweed modified" in the Operating System field 10s 7ms

And I should see the text "x86_64" in the Architecture field 10s 12ms

When I follow "openSUSE Tumbleweed modified" 290ms

Then I should see a "Update Distribution Channel Map" text 53ms

And I should see a "Delete Distribution Channel" link 10ms

When I follow "Delete Distribution Channel Mapping" 244ms

Then I should see a "Delete Distribution Channel Map" text 47ms

When I click on "Delete Mapping" 454ms

Then I should not see a "openSUSE Tumbleweed modified" link 8ms

@deblike_minion
Scenario:
Cleanup: delete the map created for amd64 Ubuntu clients
21s 185ms 10

When I follow the left menu "Software > Distribution Channel Mapping" 75ms

Then I should see the text "Ubuntu 24.04 modified" in the Operating System field 10s 2ms

And I should see the text "AMD64 Debian" in the Architecture field 10s 8ms

When I follow "Ubuntu 24.04 modified" 285ms

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" 241ms

Then I should see a "Delete Distribution Channel Map" text 48ms

When I click on "Delete Mapping" 449ms

Then I should not see a "Ubuntu 24.04 modified" link 8ms

@scc_credentials
Scenario:
Cleanup: delete the map created for i586 clients
21s 237ms 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 modified" in the Operating System field 10s 7ms

And I should see the text "x86_64" in the Architecture field 10s 8ms

When I follow "SUSE Linux Enterprise Server 15 SP 4 iSeries modified" 346ms

Then I should see a "Update Distribution Channel Map" text 52ms

And I should see a "Delete Distribution Channel" link 11ms

When I follow "Delete Distribution Channel Mapping" 239ms

Then I should see a "Delete Distribution Channel Map" text 48ms

When I click on "Delete Mapping" 438ms

Then I should not see a "SUSE Linux Enterprise Server 15 SP 4 iSeries modified" link 9ms

Scenario:
Sanity check whether the page is in its default state
141ms 3

When I follow the left menu "Software > Distribution Channel Mapping" 71ms

Then I should see a "Distribution Channel Mapping" text 49ms

And I should see a "No distribution channel mappings currently exist." text in the content area 21ms

Feature:Task Engine Status 27s 936ms 4 2

Scenario:
Login as admin
1s 661ms 1

Given I am authorized for the "Admin" section 1s 661ms

@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
976ms 6

When I follow the left menu "Admin > Task Engine Status > Last Execution Times" 661ms

Then I should see a "Task Engine Status" text 86ms

And I should see a "The following is a status report for the various tasks run by the Uyuni task engine:" text 85ms

And I should see a "Runtime Status" text 91ms

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 19ms

Scenario:
Check if the Runtime Status Page exists
568ms 6

When I follow the left menu "Admin > Task Engine Status > Runtime Status" 68ms

Then I should see a "Task Engine Status" text 52ms

And I should see a "Last Execution Times" text 50ms

And I should see a "The server is running or has finished executing the following tasks during the latest 5 minutes." text 363ms

And I should see a "Last Execution Times" link in the left menu 17ms

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
24s 730ms 6

When I follow the left menu "Admin > Task Engine Status > Last Execution Times" 66ms

And I run "cobbler sync" on "server" 3s 217ms

And I refresh the page 11s 243ms

Then I should see a "Cobbler Sync:" text 89ms

And I should see the correct timestamp for task "Cobbler Sync:" 10s 16ms

And I should see a "FINISHED" text 97ms

@scc_credentials @susemanager
Scenario:
Resync a product to trigger a new task and check if it is visible on the Runtime Status page
< 1ms 13

When I follow the left menu "Admin > Task Engine Status > Runtime Status" 0s

And I follow the left menu "Admin > Setup Wizard > Products" 0s

And I wait until I do not see "Loading" text 0s

And I enter "SUSE Linux Enterprise Server 15 SP7 x86_64" as "product-description-filter" 0s

And I wait until I see "SUSE Linux Enterprise Server 15 SP7 x86_64" text 0s

Then I should see the "SUSE Linux Enterprise Server 15 SP7 x86_64" selected 0s

When I click on "Schedule channels product resync" 0s

And I follow the left menu "Admin > Task Engine Status > Runtime Status" 0s

And I wait until I see "repo-sync" text 0s

Then I should see the correct timestamp for task "repo-sync" 0s

And I should see a "running" text in the content area 0s

And I wait until I see "finished" text 0s

And I should see the correct timestamp for task "repo-sync" 0s

@scope_api
Feature:Systems errata API 5s 890ms 2

@ssh_minion
Scenario:
Check the relevant errata for a system
4s 651ms 1

When I retrieve the relevant errata for ssh_minion 4s 651ms

@ssh_minion @rhlike_minion @deblike_minion
Scenario:
Check the relevant errata for multiple systems
1s 238ms 1

When I retrieve the relevant errata for ssh_minion, rhlike_minion, deblike_minion 1s 238ms

@scope_salt @skip_if_github_validation @new_issue @bug_reported
Feature:Health Check tool based on a supportconfig 6m 34s 727ms 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 43s 367ms 2

When I generate a supportconfig for the server 1m 42s 371ms

Then I obtain and extract the supportconfig from the server 995ms

Scenario:
Execute Health Check tool with server supportconfig
13s 796ms 1 1 1

When I start the health check tool with supportconfig "/root/server-supportconfig/uyuni-server-supportconfig/" on "localhost" 447ms Show Error + 
                                            
 FAIL: mgr-health-check -v -s /root/server-supportconfig/uyuni-server-supportconfig/ start returned status code = 1.
Output:
┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃                                 Health Check                                 ┃
┗━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┛
[14:34:07] Checking connection with podman:                           main.py:43
           Executing: podman --version                               utils.py:37
           podman version 4.9.5                                      utils.py:61
           Supportconfig path not accessible, exitting                main.py:94
 (ScriptError)
./features/support/remote_node.rb:169:in `run_local'
./features/support/remote_node.rb:117:in `run'
./features/step_definitions/command_steps.rb:1793:in `/^I start the health check tool with supportconfig "([^"]*)" on "([^"]*)"$/'
features/secondary/srv_health_check_supportconfig.feature:19: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

13s 349ms Show Info + 
14:34:07:000 - 14:34:07:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/admin/TaskStatus.do
Screenshot +

Scenario:
Health Check containers are healthy and running
4m 23s 379ms 1 3 1

When I wait until port "9000" is listening on "localhost" host 4m 10s Show Error + 
                                            
 execution expired (Timeout::Error)
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/support/remote_node.rb:202:in `run_until_ok'
./features/step_definitions/command_steps.rb:1570:in `/^I wait until port "([^"]*)" is listening on "([^"]*)" (host|container)$/'
features/secondary/srv_health_check_supportconfig.feature:23: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

13s 379ms Show Info + 
14:34:20:000 - 14:38:30:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/admin/TaskStatus.do
Screenshot +

Scenario:
Health Check containers are exposing metrics
13s 416ms 1 1

Then I check that the health check tool exposes metrics on "localhost" 209ms Show Error + 
                                            
 FAIL: curl -s localhost:9000/metrics.json | python3 -c 'import sys, json; print(json.load(sys.stdin).keys())' returned status code = 1.
Output:
 (ScriptError)
./features/support/remote_node.rb:169:in `run_local'
./features/support/remote_node.rb:117:in `run'
./features/step_definitions/command_steps.rb:1821:in `/^I check that the health check tool exposes metrics on "([^"]*)"$/'
features/secondary/srv_health_check_supportconfig.feature:29:in `I check that the health check tool exposes metrics on "localhost"'

13s 207ms Show Info + 
14:38:44:000 - 14:38:44:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/admin/TaskStatus.do
Screenshot +

Scenario:
I can stop the Health Check tool
767ms 3

When I stop health check tool on "localhost" 423ms

Then I check that the health check tool is not running on "localhost" 176ms

And I remove test supportconfig on "localhost" 167ms

@skip_if_github_validation
Feature:Password Policy Management 35s 204ms 17

As an organization administrator,
I want to configure and enforce password complexity requirements,
So that user accounts comply with security policies

Scenario:
Log in as org admin user
1s 382ms 1

Given I am authorized as "admin" with password "admin" 1s 382ms

Scenario:
Navigate to Password Policy settings page
785ms 2

When I follow the left menu "Admin > Manager Configuration > Password Policy" 713ms

Then I should see a "Server Configuration - Password Policy" text 71ms

Scenario:
Configure password complexity restrictions
747ms 5

When I set the minimum password length to "5" 50ms

And I set the maximum password length to "12" 52ms

And I enable the following restrictions: 305ms
Require Digits
Require Lowercase Characters
Require Uppercase Characters
Require Special Characters
Restrict Characters Occurrences
Restrict Consecutive Characters

And I click on "Save" 55ms

And I should see a "Password Policy Changed" text 283ms

Scenario:
Verify password complexity restrictions are saved correctly
10s 488ms 2

When I refresh the page 10s 442ms

Then the following restrictions should be enabled: 46ms
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
336ms 4

When I set the special characters list to "$@?" 57ms

And I set the maximum allowed occurrence of any character to "3" 46ms

And I click on "Save" 51ms

And I should see a "Password Policy Changed" text 181ms

Scenario Outline:
Reject invalid passwords based on policy enforcement
903ms 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" 903ms

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
941ms 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" 941ms

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
872ms 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" 872ms

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
938ms 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" 938ms

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
893ms 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" 893ms

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
877ms 2

Failed to create user password_policy_user: unknown error - API failure: Passwords must contain at least one special character, allowed special characters are: $@?.

When I create a user with name "password_policy_user" and password "aB:123" with roles "config_admin,system_group_admin,activation_key_admin,image_admin" 877ms

Then the user creation should fail with error containing "Passwords must contain at least one special character, allowed special characters are: $@?" < 1ms

Scenario Outline:
Reject invalid passwords based on policy enforcement
865ms 2

Failed to create user password_policy_user: unknown error - API failure: **consecutive_characters_presents**

When I create a user with name "password_policy_user" and password "aaB$123" with roles "config_admin,system_group_admin,activation_key_admin,image_admin" 865ms

Then the user creation should fail with error containing "consecutive_characters_presents" < 1ms

Scenario Outline:
Reject invalid passwords based on policy enforcement
881ms 2

Failed to create user password_policy_user: unknown error - API failure: **consecutive_characters_presents** :: Password characters occurrences exceeded maximum allowed 3.

When I create a user with name "password_policy_user" and password "aB$a12aa3" with roles "config_admin,system_group_admin,activation_key_admin,image_admin" 881ms

Then the user creation should fail with error containing "Password characters occurrences exceeded maximum allowed 3" < 1ms

Scenario Outline:
Reject invalid passwords based on policy enforcement
879ms 2

Failed to create user password_policy_user: unknown error - API failure: Passwords cannot be more than 12 characters.

When I create a user with name "password_policy_user" and password "aBcdef$123456" with roles "config_admin,system_group_admin,activation_key_admin,image_admin" 879ms

Then the user creation should fail with error containing "Passwords cannot be more than 12 characters" < 1ms

Scenario:
Accept valid password complying with policy
2s 26ms 2

New user password_policy_user created with roles: config_admin, system_group_admin, activation_key_admin, image_admin

When I create a user with name "password_policy_user" and password "aB$123" with roles "config_admin,system_group_admin,activation_key_admin,image_admin" 2s 26ms

Then the user creation should succeed < 1ms

Scenario:
Reset password policy to default settings
11s 53ms 5

When I follow the left menu "Admin > Manager Configuration > Password Policy" 69ms

And I click on "Reset" 56ms

And I should see a "Password Policy Reset to Default" text 411ms

And I refresh the page 10s 469ms

Then the following restrictions should be disabled: 46ms
Require Digits
Require Lowercase Characters
Require Uppercase Characters
Require Special Characters
Restrict Characters Occurrences
Restrict Consecutive Characters

Scenario:
Cleanup: Delete test user
328ms 1

When I delete user "password_policy_user" 328ms

@skip_if_github_validation @build_host @scope_building_container_images @scope_cve_audit @no_auth_registry
Feature:Build container images and CVE audit them 17m 45s 833ms 16 14

Scenario:
Log in as org admin user
1s 536ms 1

Given I am authorized 1s 536ms

Scenario:
Create a simple image profile without activation key
4s 749ms 6

GITPROFILES: https://github.com/uyuni-project/uyuni.git#:testsuite/features/profiles/temporary

When I follow the left menu "Images > Profiles" 115ms

And I follow "Create" 2s 475ms

And I enter "suse_simple" as "label" 93ms

And I select "galaxy-registry" from "imageStore" 1s 134ms

And I enter "Docker" relative to profiles as "path" 865ms

And I click on "create-btn" 65ms

Scenario:
Create a simple real image profile without activation key
4s 726ms 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" 2s 472ms

And I enter "suse_real_simple" as "label" 110ms

And I select "galaxy-registry" from "imageStore" 1s 112ms

And I enter "Docker/serverhost" relative to profiles as "path" 918ms

And I click on "create-btn" 49ms

@scc_credentials
Scenario:
Create an image profile with activation key
5s 678ms 7

GITPROFILES: https://github.com/uyuni-project/uyuni.git#:testsuite/features/profiles/temporary

When I follow the left menu "Images > Profiles" 59ms

And I follow "Create" 2s 420ms

And I enter "suse_key" as "label" 77ms

And I select "galaxy-registry" from "imageStore" 1s 103ms

And I select "1-SUSE-KEY-x86_64" from "activationKey" 1s 116ms

And I enter "Docker" relative to profiles as "path" 850ms

And I click on "create-btn" 51ms

@scc_credentials
Scenario:
Create a simple real image profile with activation key
5s 898ms 7

GITPROFILES: https://github.com/uyuni-project/uyuni.git#:testsuite/features/profiles/temporary

When I follow the left menu "Images > Profiles" 57ms

And I follow "Create" 2s 560ms

And I enter "suse_real_key" as "label" 97ms

And I select "galaxy-registry" from "imageStore" 1s 102ms

And I select "1-SUSE-KEY-x86_64" from "activationKey" 1s 107ms

And I enter "Docker/serverhost" relative to profiles as "path" 922ms

And I click on "create-btn" 48ms

@scc_credentials
Scenario:
Build the suse_key image with and without activation key
59s 166ms 3 2 1

Event Details: ---------- ID: mgr_registries_login Function: mgrcompat.module_run Name: docker.login Result: true Comment: Module function docker.login executed Started: 14:40:11.783241 Duration: 2.083 SLS: images.docker Changed: ret: retcode: 0.0 Errors: [ ] Results: { } ---------- ID: mgr_buildimage Function: mgrcompat.module_run Name: docker.build Result: false Comment: Module function docker.build threw an exception. Exception: Build failed for https://github.com/uyuni-project/uyuni.git#:testsuite/features/profiles/temporary/docker_profiles/cloud_aws/Docker. Error(s) follow: manifest for ip-172-16-1-175.eu-central-1.compute.internal/suse/sle15:15.7 not found: manifest unknown: manifest unknown Started: 14:40:11.785633 Duration: 14513.719 SLS: images.docker Changed: {} ---------- ID: mgr_pushimage Function: mgrcompat.module_run Name: docker.push Result: false Comment: One or more requisite failed: images.docker.mgr_buildimage Started: 14:40:26.299834 Duration: 0.005 SLS: images.docker Changed: {} ---------- ID: mgr_registries_logout Function: mgrcompat.module_run Name: docker.logout Result: false Comment: One or more requisite failed: images.docker.mgr_pushimage Started: 14:40:26.300104 Duration: 0.004 SLS: images.docker Changed: {} ---------- ID: mgr_buildimage_docker_collect_logs Function: file.touch Name: /var/log/image-build308.log Result: true Comment: Updated times on file /var/log/image-build308.log Started: 14:40:26.302855 Duration: 8.551 SLS: images.docker Changed: touched: /var/log/image-build308.log ---------- ID: mgr_buildimage_docker_collect_logs Function: mgrcompat.module_run Name: cp.push Result: true Comment: Module function cp.push executed Started: 14:40:26.311528 Duration: 10.119 SLS: images.docker Changed: ret: true

Given I am on the Systems overview page of this "build_host" 3s 236ms

When I schedule the build of image "suse_key" via API calls 1s 63ms

And I wait at most 660 seconds until event "Image Build suse_key scheduled" is completed 41s 370ms Show Error + 
                                            
 unknown error - Event failed (SystemCallError)
./features/step_definitions/navigation_steps.rb:96:in `block (2 levels) in (top (required))'
./features/support/commonlib.rb:106:in `block in repeat_until_timeout'
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/step_definitions/navigation_steps.rb:88: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

13s 495ms Show Info + 
14:40:06:000 - 14:40:51:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010003&aid=308
Screenshot +

Scenario:
Check the list of packages is not empty
14s 279ms 1 1

List of images: [{"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>1, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}]
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"failed", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>1, "arch"=>"x86_64", "enhancementErrata"=>0}

Then the list of packages of image "suse_key" with version "latest" is not empty 834ms 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'

13s 445ms Show Info + 
14:41:05:000 - 14:41:06:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010003&aid=308
Screenshot +

Scenario:
Build the suse_simple image with and without activation key
56s 581ms 3 2 1

Event Details: ---------- ID: mgr_registries_login Function: mgrcompat.module_run Name: docker.login Result: true Comment: Module function docker.login executed Started: 14:41:22.367364 Duration: 2.078 SLS: images.docker Changed: ret: retcode: 0.0 Errors: [ ] Results: { } ---------- ID: mgr_buildimage Function: mgrcompat.module_run Name: docker.build Result: false Comment: Module function docker.build threw an exception. Exception: Build failed for https://github.com/uyuni-project/uyuni.git#:testsuite/features/profiles/temporary/docker_profiles/cloud_aws/Docker. Error(s) follow: manifest for ip-172-16-1-175.eu-central-1.compute.internal/suse/sle15:15.7 not found: manifest unknown: manifest unknown Started: 14:41:22.369745 Duration: 14691.578 SLS: images.docker Changed: {} ---------- ID: mgr_pushimage Function: mgrcompat.module_run Name: docker.push Result: false Comment: One or more requisite failed: images.docker.mgr_buildimage Started: 14:41:37.061731 Duration: 0.004 SLS: images.docker Changed: {} ---------- ID: mgr_registries_logout Function: mgrcompat.module_run Name: docker.logout Result: false Comment: One or more requisite failed: images.docker.mgr_pushimage Started: 14:41:37.062023 Duration: 0.004 SLS: images.docker Changed: {} ---------- ID: mgr_buildimage_docker_collect_logs Function: file.touch Name: /var/log/image-build309.log Result: true Comment: Updated times on file /var/log/image-build309.log Started: 14:41:37.064765 Duration: 8.429 SLS: images.docker Changed: touched: /var/log/image-build309.log ---------- ID: mgr_buildimage_docker_collect_logs Function: mgrcompat.module_run Name: cp.push Result: true Comment: Module function cp.push executed Started: 14:41:37.073316 Duration: 10.177 SLS: images.docker Changed: ret: true

Given I am on the Systems overview page of this "build_host" 920ms

When I schedule the build of image "suse_simple" via API calls 783ms

And I wait at most 660 seconds until event "Image Build suse_simple scheduled" is completed 41s 334ms Show Error + 
                                            
 unknown error - Event failed (SystemCallError)
./features/step_definitions/navigation_steps.rb:96:in `block (2 levels) in (top (required))'
./features/support/commonlib.rb:106:in `block in repeat_until_timeout'
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/step_definitions/navigation_steps.rb:88: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

13s 542ms Show Info + 
14:41:19:000 - 14:42:02:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010003&aid=309
Screenshot +

Scenario:
Check the list of packages is not empty
14s 166ms 1 1

List of images: [{"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>1, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>2, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}]
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"failed", "external"=>false, "profileLabel"=>"suse_simple", "name"=>"suse_simple", "checksum"=>"", "files"=>[], "id"=>2, "arch"=>"x86_64", "enhancementErrata"=>0}

Then the list of packages of image "suse_simple" with version "latest" is not empty 727ms 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'

13s 439ms Show Info + 
14:42:16:000 - 14:42:16:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010003&aid=309
Screenshot +

@scc_credentials
Scenario:
Build the suse_real_key image with and without activation key
2m 52s 392ms 4 3 1

Given I am on the Systems overview page of this "build_host" 890ms

When I schedule the build of image "suse_real_key" via API calls 981ms

And I wait at most 660 seconds until event "Image Build suse_real_key scheduled" is completed 2m 34s 497ms

And I wait at most 60 seconds until all "3" container images are built correctly on the Image List page 1s 629ms Show Error + 
                                            
 unknown error - error detected while building images (SystemCallError)
./features/step_definitions/docker_steps.rb:90:in `block (2 levels) in (top (required))'
./features/support/commonlib.rb:106:in `block in repeat_until_timeout'
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/step_definitions/docker_steps.rb:87:in `/^I wait at most (\d+) seconds until all "([^"]*)" container images are built correctly on the Image List page$/'
features/secondary/buildhost_docker_build_image.feature:87:in `I wait at most 60 seconds until all "3" container images are built correctly on the Image List page'

And I wait at most 900 seconds until image "suse_real_key" with version "latest" is built successfully via API 0s

And I wait at most 300 seconds until image "suse_real_key" with version "latest" is inspected successfully via API 0s

When I wait until no Salt job is running on "build_host" 0s

14s 393ms Show Info + 
14:42:30:000 - 14:45:08:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

Scenario:
Check the list of packages is not empty
15s 129ms 1 1

List of images: [{"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>1, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>2, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_real_key", "checksum"=>"", "obsolete"=>false, "id"=>3, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>1}]
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>3, "arch"=>"x86_64", "enhancementErrata"=>0}

Then the list of packages of image "suse_real_key" with version "latest" is not empty 797ms 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'

14s 332ms Show Info + 
14:45:22:000 - 14:45:23: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 47s 410ms 2 2 1

List of images: [{"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>1, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>2, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_real_key", "checksum"=>"", "obsolete"=>false, "id"=>3, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>1}, {"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>4, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0}]
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"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 895ms

And I wait at most 900 seconds until image "suse_key" with version "Latest_key-activation1" is built successfully via API 1m 32s 153ms Show Error + 
                                            
 unknown error - image build failed. (SystemCallError)
./features/step_definitions/docker_steps.rb:55:in `block (2 levels) in (top (required))'
./features/support/commonlib.rb:106:in `block in repeat_until_timeout'
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/step_definitions/docker_steps.rb:41:in `/^I wait at most (\d+) seconds until image "([^"]*)" with version "([^"]*)" is built successfully via API$/'
features/secondary/buildhost_docker_build_image.feature:99:in `I wait at most 900 seconds until image "suse_key" with version "Latest_key-activation1" is built successfully via API'

And I wait at most 300 seconds until image "suse_key" with version "Latest_key-activation1" is inspected successfully via API 0s

When I wait until no Salt job is running on "build_host" 0s

14s 360ms Show Info + 
14:45:37:000 - 14:47:11:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

Scenario:
Check the list of packages is not empty
15s 177ms 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"=>"b2920f02497a1b6ba7590358ed8fca491bbfa32b14d26e45815fecb03c356fd9", "obsolete"=>false, "id"=>3, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>1}, {"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>4, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0}]
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"failed", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>4, "arch"=>"x86_64", "enhancementErrata"=>0}

Then the list of packages of image "suse_key" with version "Latest_key-activation1" is not empty 813ms 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'

14s 363ms Show Info + 
14:47:25:000 - 14:47:26:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

Scenario:
Build suse_simple image with different versions
36s 753ms 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"=>"b2920f02497a1b6ba7590358ed8fca491bbfa32b14d26e45815fecb03c356fd9", "obsolete"=>false, "id"=>3, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>1}, {"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>4, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>5, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0}]
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_simple", "name"=>"suse_simple", "checksum"=>"", "files"=>[], "id"=>5, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_simple", "name"=>"suse_simple", "checksum"=>"", "files"=>[], "id"=>5, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_simple", "name"=>"suse_simple", "checksum"=>"", "files"=>[], "id"=>5, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"failed", "external"=>false, "profileLabel"=>"suse_simple", "name"=>"suse_simple", "checksum"=>"", "files"=>[], "id"=>5, "arch"=>"x86_64", "enhancementErrata"=>0}

When I schedule the build of image "suse_simple" with version "Latest_simple" via API calls 670ms

And I wait at most 900 seconds until image "suse_simple" with version "Latest_simple" is built successfully via API 21s 743ms Show Error + 
                                            
 unknown error - image build failed. (SystemCallError)
./features/step_definitions/docker_steps.rb:55:in `block (2 levels) in (top (required))'
./features/support/commonlib.rb:106:in `block in repeat_until_timeout'
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/step_definitions/docker_steps.rb:41:in `/^I wait at most (\d+) seconds until image "([^"]*)" with version "([^"]*)" is built successfully via API$/'
features/secondary/buildhost_docker_build_image.feature:109:in `I wait at most 900 seconds until image "suse_simple" with version "Latest_simple" is built successfully via API'

And I wait at most 300 seconds until image "suse_simple" with version "Latest_simple" is inspected successfully via API 0s

When I wait until no Salt job is running on "build_host" 0s

14s 339ms Show Info + 
14:47:40:000 - 14:48:03:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

Scenario:
Check the list of packages is not empty
15s 109ms 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"=>"b2920f02497a1b6ba7590358ed8fca491bbfa32b14d26e45815fecb03c356fd9", "obsolete"=>false, "id"=>3, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>1}, {"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>4, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>5, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0}]
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"failed", "external"=>false, "profileLabel"=>"suse_simple", "name"=>"suse_simple", "checksum"=>"", "files"=>[], "id"=>5, "arch"=>"x86_64", "enhancementErrata"=>0}

Then the list of packages of image "suse_simple" with version "Latest_simple" is not empty 805ms Show Error + 
                                            
 the list of image packages is empty (ScriptError)
./features/step_definitions/docker_steps.rb:143:in `/^the list of packages of image "([^"]*)" with version "([^"]*)" is not empty$/'
features/secondary/buildhost_docker_build_image.feature:115:in `the list of packages of image "suse_simple" with version "Latest_simple" is not empty'

14s 304ms Show Info + 
14:48:17:000 - 14:48:18:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

@scc_credentials
Scenario:
Delete image via API calls with key
3s 198ms 3

When I delete the image "suse_key" with version "Latest_key-activation1" via API calls 912ms

Then the image "suse_simple" with version "Latest_key-activation1" doesn't exist via API calls 399ms

When I wait until no Salt job is running on "build_host" 1s 887ms

Scenario:
Delete image via API calls without key
2s 674ms 3

When I delete the image "suse_simple" with version "Latest_simple" via API calls 745ms

Then the image "suse_simple" with version "Latest_simple" doesn't exist via API calls 402ms

When I wait until no Salt job is running on "build_host" 1s 526ms

Scenario:
Rebuild suse_simple image
36s 574ms 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"=>"b2920f02497a1b6ba7590358ed8fca491bbfa32b14d26e45815fecb03c356fd9", "obsolete"=>false, "id"=>3, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>1}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>6, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0}]
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_simple", "name"=>"suse_simple", "checksum"=>"", "files"=>[], "id"=>6, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_simple", "name"=>"suse_simple", "checksum"=>"", "files"=>[], "id"=>6, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_simple", "name"=>"suse_simple", "checksum"=>"", "files"=>[], "id"=>6, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"failed", "external"=>false, "profileLabel"=>"suse_simple", "name"=>"suse_simple", "checksum"=>"", "files"=>[], "id"=>6, "arch"=>"x86_64", "enhancementErrata"=>0}

When I schedule the build of image "suse_simple" with version "Latest_simple" via API calls 633ms

And I wait at most 900 seconds until image "suse_simple" with version "Latest_simple" is built successfully via API 21s 663ms Show Error + 
                                            
 unknown error - image build failed. (SystemCallError)
./features/step_definitions/docker_steps.rb:55:in `block (2 levels) in (top (required))'
./features/support/commonlib.rb:106:in `block in repeat_until_timeout'
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/step_definitions/docker_steps.rb:41:in `/^I wait at most (\d+) seconds until image "([^"]*)" with version "([^"]*)" is built successfully via API$/'
features/secondary/buildhost_docker_build_image.feature:130:in `I wait at most 900 seconds until image "suse_simple" with version "Latest_simple" is built successfully via API'

And I wait at most 300 seconds until image "suse_simple" with version "Latest_simple" is inspected successfully via API 0s

When I wait until no Salt job is running on "build_host" 0s

14s 277ms Show Info + 
14:48:38:000 - 14:49:00:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

Scenario:
Check the list of packages is not empty
14s 982ms 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"=>"b2920f02497a1b6ba7590358ed8fca491bbfa32b14d26e45815fecb03c356fd9", "obsolete"=>false, "id"=>3, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>1}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>6, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0}]
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"failed", "external"=>false, "profileLabel"=>"suse_simple", "name"=>"suse_simple", "checksum"=>"", "files"=>[], "id"=>6, "arch"=>"x86_64", "enhancementErrata"=>0}

Then the list of packages of image "suse_simple" with version "Latest_simple" is not empty 734ms 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'

14s 248ms Show Info + 
14:49:15:000 - 14:49:15:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

@scc_credentials
Scenario:
Rebuild suse_key image
37s 324ms 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"=>"b2920f02497a1b6ba7590358ed8fca491bbfa32b14d26e45815fecb03c356fd9", "obsolete"=>false, "id"=>3, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>1}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>6, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>7, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0}]
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>7, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>7, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>7, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"failed", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>7, "arch"=>"x86_64", "enhancementErrata"=>0}

When I schedule the build of image "suse_key" with version "Latest_key-activation1" via API calls 912ms

And I wait at most 900 seconds until image "suse_key" with version "Latest_key-activation1" is built successfully via API 22s 56ms Show Error + 
                                            
 unknown error - image build failed. (SystemCallError)
./features/step_definitions/docker_steps.rb:55:in `block (2 levels) in (top (required))'
./features/support/commonlib.rb:106:in `block in repeat_until_timeout'
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/step_definitions/docker_steps.rb:41:in `/^I wait at most (\d+) seconds until image "([^"]*)" with version "([^"]*)" is built successfully via API$/'
features/secondary/buildhost_docker_build_image.feature: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

14s 355ms Show Info + 
14:49:30:000 - 14:49:53:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

Scenario:
Check the list of packages is not empty
15s 110ms 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"=>"b2920f02497a1b6ba7590358ed8fca491bbfa32b14d26e45815fecb03c356fd9", "obsolete"=>false, "id"=>3, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>1}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>6, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>7, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0}]
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"failed", "external"=>false, "profileLabel"=>"suse_key", "name"=>"suse_key", "checksum"=>"", "files"=>[], "id"=>7, "arch"=>"x86_64", "enhancementErrata"=>0}

Then the list of packages of image "suse_key" with version "Latest_key-activation1" is not empty 807ms 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'

14s 302ms Show Info + 
14:50:07:000 - 14:50:08:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

@scc_credentials
Scenario:
Build an image via the GUI
3m 25s 6ms 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"=>"b2920f02497a1b6ba7590358ed8fca491bbfa32b14d26e45815fecb03c356fd9", "obsolete"=>false, "id"=>3, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>1}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>6, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>7, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_real_key", "checksum"=>"", "obsolete"=>false, "id"=>8, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>0}]
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>8, "arch"=>"x86_64", "enhancementErrata"=>0}
List of images: [{"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>1, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>2, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_real_key", "checksum"=>"b2920f02497a1b6ba7590358ed8fca491bbfa32b14d26e45815fecb03c356fd9", "obsolete"=>false, "id"=>3, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>1}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>6, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_simple", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>7, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"Latest_key-activation1", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_real_key", "checksum"=>"", "obsolete"=>false, "id"=>8, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>1}]
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>8, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>8, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>8, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>8, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>8, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>8, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>8, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>8, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>8, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>8, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>8, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>8, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>160, "type"=>"dockerfile", "inspectStatus"=>"completed", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"30d20d463e8931281db0f0d0468826fd6abc412367ebcc2f064d0a7ca0049d64", "files"=>[], "id"=>8, "arch"=>"x86_64", "enhancementErrata"=>0}

When I follow the left menu "Images > Build" 77ms

And I select "suse_real_key" from "profileId" 1s 132ms

And I enter "GUI_BUILT_IMAGE" as "version" 540ms

And I select the hostname of "build_host" from "buildHostId" 1s 117ms

And I click on "submit-btn" 58ms

And I wait until no Salt job is running on "build_host" 2m 10s 537ms

Then I wait until I see "GUI_BUILT_IMAGE" text 93ms

And I wait at most 900 seconds until image "suse_real_key" with version "GUI_BUILT_IMAGE" is built successfully via API 5s 922ms

And I wait at most 300 seconds until image "suse_real_key" with version "GUI_BUILT_IMAGE" is inspected successfully via API 1m 5s 526ms

@scc_credentials
Scenario:
Login as Docker image administrator and build an image
3m 29s 501ms 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"=>"b2920f02497a1b6ba7590358ed8fca491bbfa32b14d26e45815fecb03c356fd9", "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"=>"30d20d463e8931281db0f0d0468826fd6abc412367ebcc2f064d0a7ca0049d64", "obsolete"=>false, "id"=>8, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>1}, {"external"=>false, "name"=>"suse_real_key", "checksum"=>"", "obsolete"=>false, "id"=>9, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"GUI_DOCKERADMIN", "storeLabel"=>"galaxy-registry", "revision"=>0}]
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_DOCKERADMIN", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>9, "arch"=>"x86_64", "enhancementErrata"=>0}
List of images: [{"external"=>false, "name"=>"suse_key", "checksum"=>"", "obsolete"=>false, "id"=>1, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_simple", "checksum"=>"", "obsolete"=>false, "id"=>2, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"galaxy-registry", "revision"=>0}, {"external"=>false, "name"=>"suse_real_key", "checksum"=>"b2920f02497a1b6ba7590358ed8fca491bbfa32b14d26e45815fecb03c356fd9", "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"=>"30d20d463e8931281db0f0d0468826fd6abc412367ebcc2f064d0a7ca0049d64", "obsolete"=>false, "id"=>8, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"GUI_BUILT_IMAGE", "storeLabel"=>"galaxy-registry", "revision"=>1}, {"external"=>false, "name"=>"suse_real_key", "checksum"=>"", "obsolete"=>false, "id"=>9, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"GUI_DOCKERADMIN", "storeLabel"=>"galaxy-registry", "revision"=>1}]
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_DOCKERADMIN", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>9, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_DOCKERADMIN", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>9, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_DOCKERADMIN", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>9, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_DOCKERADMIN", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>9, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_DOCKERADMIN", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>9, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_DOCKERADMIN", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>9, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_DOCKERADMIN", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>9, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_DOCKERADMIN", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>9, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_DOCKERADMIN", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>9, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_DOCKERADMIN", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>9, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_DOCKERADMIN", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>9, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_DOCKERADMIN", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>9, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "inspectStatus"=>"picked up", "version"=>"GUI_DOCKERADMIN", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"", "files"=>[], "id"=>9, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>160, "type"=>"dockerfile", "inspectStatus"=>"completed", "version"=>"GUI_DOCKERADMIN", "storeLabel"=>"galaxy-registry", "revision"=>1, "securityErrata"=>0, "buildStatus"=>"completed", "external"=>false, "profileLabel"=>"suse_real_key", "name"=>"suse_real_key", "checksum"=>"2a8015dd044ab0bf60a6f1cd4d6a56ce43e8131a0bbd1641517ae1f5cbad2f7e", "files"=>[], "id"=>9, "arch"=>"x86_64", "enhancementErrata"=>0}

Given I am authorized as "docker" with password "docker" 1s 402ms

When I follow the left menu "Images > Build" 115ms

And I select "suse_real_key" from "profileId" 1s 111ms

And I enter "GUI_DOCKERADMIN" as "version" 471ms

And I select the hostname of "build_host" from "buildHostId" 1s 111ms

And I click on "submit-btn" 51ms

And I wait until no Salt job is running on "build_host" 2m 10s 781ms

Then I wait until I see "GUI_DOCKERADMIN" text 95ms

And I wait at most 900 seconds until image "suse_real_key" with version "GUI_DOCKERADMIN" is built successfully via API 5s 553ms

And I wait at most 300 seconds until image "suse_real_key" with version "GUI_DOCKERADMIN" is inspected successfully via API 1m 8s 806ms

@scc_credentials
Scenario:
Audit images, searching for a known CVE number
841ms 5

When I follow the left menu "Audit > CVE Audit" 116ms

And I select "1999" from "cveIdentifierYear" 78ms

And I enter "9999" as "cveIdentifierId" 56ms

And I click on "Audit Images" 57ms

Then I should see a "No action required" text 532ms

Scenario:
Audit images, searching for an unknown CVE number
373ms 5

When I follow the left menu "Audit > CVE Audit" 60ms

And I select "2012" from "cveIdentifierYear" 53ms

And I enter "2806" as "cveIdentifierId" 51ms

And I click on "Audit Images" 50ms

Then I should see a "The specified CVE number was not found" text 157ms

@scc_credentials
Scenario:
Cleanup: delete all images with key
5s 95ms 6

Given I am authorized as "admin" with password "admin" 1s 119ms

When I delete the image "suse_key" with version "latest" via API calls 1s 318ms

And I delete the image "suse_key" with version "Latest_key-activation1" via API calls 654ms

And I delete the image "suse_real_key" with version "latest" via API calls 706ms

And I delete the image "suse_real_key" with version "GUI_BUILT_IMAGE" via API calls 660ms

And I delete the image "suse_real_key" with version "GUI_DOCKERADMIN" via API calls 635ms

Scenario:
Cleanup: delete images without key
2s 483ms 3

Given I am authorized as "admin" with password "admin" 410ms

When I delete the image "suse_simple" with version "latest" via API calls 1s 443ms

And I delete the image "suse_simple" with version "Latest_simple" via API calls 629ms

@scc_credentials
Scenario:
Cleanup: delete all profiles with key
1s 347ms 7

When I follow the left menu "Images > Profiles" 130ms

And I check "suse_key" in the list 452ms

And I check "suse_real_key" in the list 57ms

And I click on "Delete" 76ms

And I should see a "Are you sure you want to delete selected profiles?" text 74ms

And I click on the red confirmation button 66ms

And I wait until I see "Image profiles have been deleted" text 489ms

Scenario:
Cleanup: delete all profiles without key
625ms 7

When I follow the left menu "Images > Profiles" 58ms

And I check "suse_simple" in the list 179ms

And I check "suse_real_simple" in the list 56ms

And I click on "Delete" 55ms

And I should see a "Are you sure you want to delete selected profiles?" text 65ms

And I click on the red confirmation button 54ms

And I wait until I see "Image profiles have been deleted" text 155ms

Scenario:
Cleanup: Make sure no job is left running on buildhost
1s 934ms 1

When I wait until no Salt job is running on "build_host" 1s 934ms

@skip_if_github_validation @build_host @scope_building_container_images @auth_registry
Feature:Build image with authenticated registry 1m 5s 62ms 6 2

Scenario:
Log in as docker user
1s 559ms 1

Given I am authorized as "docker" with password "docker" 1s 559ms

Scenario:
Create an authenticated image store as Docker admin
1s 151ms 7

AUTH_REGISTRY_CREDENTIALS: cucutest|cucusecret

When I follow the left menu "Images > Stores" 108ms

And I follow "Create" 327ms

And I enter "auth_registry" as "label" 91ms

And I check "useCredentials" 123ms

And I enter URI, username and password for registry 388ms

And I click on "create-btn" 61ms

Then I wait until I see "registry" text 50ms

@scc_credentials
Scenario:
Create a profile for the authenticated image store as Docker admin
6s 489ms 8

GITPROFILES: https://github.com/uyuni-project/uyuni.git#:testsuite/features/profiles/temporary

When I follow the left menu "Images > Profiles" 61ms

And I follow "Create" 2s 326ms

And I enter "auth_registry_profile" as "label" 151ms

And I select "auth_registry" from "imageStore" 1s 121ms

And I select "1-SUSE-KEY-x86_64" from "activationKey" 1s 112ms

And I enter "Docker/authprofile" relative to profiles as "path" 933ms

And I click on "create-btn" 52ms

Then I wait until I see "auth_registry_profile" text 729ms

@scc_credentials
Scenario:
Build an image in the authenticated image store
37s 804ms 7 4 1

List of images: []
List of images: [{"external"=>false, "name"=>"auth_registry_profile", "checksum"=>"", "obsolete"=>false, "id"=>10, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"auth_registry", "revision"=>0}]
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"auth_registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"auth_registry_profile", "name"=>"auth_registry_profile", "checksum"=>"", "files"=>[], "id"=>10, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"auth_registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"picked up", "external"=>false, "profileLabel"=>"auth_registry_profile", "name"=>"auth_registry_profile", "checksum"=>"", "files"=>[], "id"=>10, "arch"=>"x86_64", "enhancementErrata"=>0}
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"auth_registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"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" 60ms

And I select "auth_registry_profile" from "profileId" 1s 127ms

And I enter "latest" as "version" 432ms

And I select the hostname of "build_host" from "buildHostId" 1s 143ms

And I click on "submit-btn" 60ms

Then I wait until I see "auth_registry_profile" text 72ms

When I wait at most 900 seconds until image "auth_registry_profile" with version "latest" is built successfully via API 21s 173ms Show Error + 
                                            
 unknown error - image build failed. (SystemCallError)
./features/step_definitions/docker_steps.rb:55:in `block (2 levels) in (top (required))'
./features/support/commonlib.rb:106:in `block in repeat_until_timeout'
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/step_definitions/docker_steps.rb:41:in `/^I wait at most (\d+) seconds until image "([^"]*)" with version "([^"]*)" is built successfully via API$/'
features/secondary/buildhost_docker_auth_registry.feature:45:in `I wait at most 900 seconds until image "auth_registry_profile" with version "latest" is built successfully via API'

And I wait at most 300 seconds until image "auth_registry_profile" with version "latest" is inspected successfully via API 0s

And I wait until no Salt job is running on "build_host" 0s

And I refresh the page 0s

Then table row for "auth_registry_profile" should contain "1" 0s

13s 734ms Show Info + 
14:57:44:000 - 14:58:08:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/manager/cm/images
Screenshot +

Scenario:
Check the list of packages is not empty
14s 163ms 1 1

List of images: [{"external"=>false, "name"=>"auth_registry_profile", "checksum"=>"", "obsolete"=>false, "id"=>10, "arch"=>"x86_64-redhat-linux", "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"auth_registry", "revision"=>0}]
Image Details: {"outdatedPackages"=>0, "buildServerId"=>1000010003, "obsolete"=>false, "bugErrata"=>0, "installedPackages"=>0, "type"=>"dockerfile", "version"=>"latest", "storeLabel"=>"auth_registry", "revision"=>0, "securityErrata"=>0, "buildStatus"=>"failed", "external"=>false, "profileLabel"=>"auth_registry_profile", "name"=>"auth_registry_profile", "checksum"=>"", "files"=>[], "id"=>10, "arch"=>"x86_64", "enhancementErrata"=>0}

And the list of packages of image "auth_registry_profile" with version "latest" is not empty 535ms 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'

13s 628ms Show Info + 
14:58:22:000 - 14:58:23: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
3s 31ms 6

When I follow the left menu "Images > Profiles" 84ms

And I check the row with the "auth_registry_profile" text 400ms

And I click on "Delete" 74ms

And I click on the red confirmation button 61ms

And I should see a "Image profile has been deleted." text 398ms

And I wait until no Salt job is running on "build_host" 2s 11ms

Scenario:
Cleanup: remove authenticated image store
468ms 5

When I follow the left menu "Images > Stores" 60ms

And I check the row with the "auth_registry" text 123ms

And I click on "Delete" 59ms

And I click on the red confirmation button 74ms

And I should see a "Image store has been deleted." text 150ms

Scenario:
Cleanup: delete registry image
393ms 1

When I delete the image "auth_registry_profile" with version "latest" via API calls 393ms

@scope_visualization
Feature:The system details of each minion and client provides an overview of the system 2m 13s 248ms 9

Scenario:
Log in as org admin user
1s 48ms 1

Given I am authorized 1s 48ms

@sle_minion
Scenario:
SLE minion hardware refresh
27s 619ms 6

Given I navigate to the Systems overview page of this "sle_minion" 2s 299ms

When I follow "Hardware" 446ms

And I click on "Schedule Hardware Refresh" 750ms

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 810ms

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "sle_minion" 2s 194ms

@sle_minion
Scenario:
Minion grains are displayed correctly on the details page
3s 612ms 19

I should see kernel version: 6.18.2-1-default
IPv4 address: 172.16.3.8
IPv6 address: fe80::45a:31ff:fec6:371b

Given I am on the Systems overview page of this "sle_minion" 869ms

Then the hostname for "sle_minion" should be correct 89ms

And the kernel for "sle_minion" should be correct 491ms

And the OS version for "sle_minion" should be correct < 1ms

And the IPv4 address for "sle_minion" should be correct 80ms

And the IPv6 address for "sle_minion" should be correct 427ms

And the system ID for "sle_minion" should be correct 372ms

And the system name for "sle_minion" should be correct 79ms

And the uptime for "sle_minion" should be correct 428ms

And I should see a "UUID" text 76ms

And I should see a "Virtualization" text 83ms

And I should see a "Installed Products" text 75ms

And I should see a "Checked In" text 78ms

And I should see a "Registered" text 78ms

And I should see a "Contact Method" text 75ms

And I should see a "Auto Patch Update" text 76ms

And I should see a "Maintenance Schedule" text 76ms

And I should see a "Description" text 77ms

And I should see a "Location" text 75ms

@rhlike_minion
Scenario:
Red Hat-like minion hardware refresh
24s 740ms 6

Given I am on the Systems overview page of this "rhlike_minion" 836ms

When I follow "Hardware" 465ms

And I click on "Schedule Hardware Refresh" 59ms

Then I should see a "You have successfully scheduled a hardware profile refresh" text 111ms

When I wait until event "Hardware List Refresh scheduled" is completed 21s 766ms

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "rhlike_minion" 1s 500ms

@rhlike_minion
Scenario:
Red Hat-like minion grains are displayed correctly on the details page
2s 871ms 19

I should see kernel version: 4.18.0-553.el8_10.x86_64
IPv4 address: 172.16.3.10
IPv6 address: fe80::4c4:90ff:fe73:9523

Given I am on the Systems overview page of this "rhlike_minion" 814ms

Then the hostname for "rhlike_minion" should be correct 84ms

And the kernel for "rhlike_minion" should be correct 253ms

And the OS version for "rhlike_minion" should be correct < 1ms

And the IPv4 address for "rhlike_minion" should be correct 79ms

And the IPv6 address for "rhlike_minion" should be correct 184ms

And the system ID for "rhlike_minion" should be correct 421ms

And the system name for "rhlike_minion" should be correct 87ms

And the uptime for "rhlike_minion" should be correct 182ms

And I should see a "UUID" text 74ms

And I should see a "Virtualization" text 74ms

And I should see a "Installed Products" text 74ms

And I should see a "Checked In" text 80ms

And I should see a "Registered" text 75ms

And I should see a "Contact Method" text 75ms

And I should see a "Auto Patch Update" text 77ms

And I should see a "Maintenance Schedule" text 77ms

And I should see a "Description" text 80ms

And I should see a "Location" text 75ms

@deblike_minion
Scenario:
Debian-like minion hardware refresh
25s 694ms 6

Given I am on the Systems overview page of this "deblike_minion" 817ms

When I follow "Hardware" 529ms

And I click on "Schedule Hardware Refresh" 67ms

Then I should see a "You have successfully scheduled a hardware profile refresh" text 120ms

When I wait until event "Hardware List Refresh scheduled" is completed 21s 810ms

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "deblike_minion" 2s 349ms

@deblike_minion
Scenario:
Debian-like minion grains are displayed correctly on the details page
2s 956ms 19

I should see kernel version: 6.14.0-1018-aws
IPv4 address: 172.16.3.11
IPv6 address: fe80::455:2bff:fe1b:b899

Given I am on the Systems overview page of this "deblike_minion" 802ms

Then the hostname for "deblike_minion" should be correct 88ms

And the kernel for "deblike_minion" should be correct 295ms

And the OS version for "deblike_minion" should be correct < 1ms

And the IPv4 address for "deblike_minion" should be correct 80ms

And the IPv6 address for "deblike_minion" should be correct 230ms

And the system ID for "deblike_minion" should be correct 372ms

And the system name for "deblike_minion" should be correct 79ms

And the uptime for "deblike_minion" should be correct 229ms

And I should see a "UUID" text 76ms

And I should see a "Virtualization" text 87ms

And I should see a "Installed Products" text 76ms

And I should see a "Checked In" text 75ms

And I should see a "Registered" text 78ms

And I should see a "Contact Method" text 75ms

And I should see a "Auto Patch Update" text 75ms

And I should see a "Maintenance Schedule" text 79ms

And I should see a "Description" text 76ms

And I should see a "Location" text 76ms

@ssh_minion
Scenario:
SSH-managed minion hardware refresh
40s 704ms 5

Given I am on the Systems overview page of this "ssh_minion" 830ms

When I follow "Hardware" 456ms

And I click on "Schedule Hardware Refresh" 68ms

Then I should see a "You have successfully scheduled a hardware profile refresh" text 840ms

And I wait until event "Hardware List Refresh scheduled" is completed 38s 507ms

@ssh_minion
Scenario:
SSH-managed minion grains are displayed correctly on the details page
3s 999ms 19

I should see kernel version: 6.18.2-1-default
IPv4 address: 172.16.3.9
IPv6 address: fe80::4a8:a7ff:fe92:bb8b

Given I am on the Systems overview page of this "ssh_minion" 822ms

Then the hostname for "ssh_minion" should be correct 89ms

And the kernel for "ssh_minion" should be correct 827ms

And the OS version for "ssh_minion" should be correct < 1ms

And the IPv4 address for "ssh_minion" should be correct 81ms

And the IPv6 address for "ssh_minion" should be correct 426ms

And the system ID for "ssh_minion" should be correct 426ms

And the system name for "ssh_minion" should be correct 96ms

And the uptime for "ssh_minion" should be correct 434ms

And I should see a "UUID" text 77ms

And I should see a "Virtualization" text 82ms

And I should see a "Installed Products" text 80ms

And I should see a "Checked In" text 93ms

And I should see a "Registered" text 76ms

And I should see a "Contact Method" text 77ms

And I should see a "Auto Patch Update" text 75ms

And I should see a "Maintenance Schedule" text 77ms

And I should see a "Description" text 75ms

And I should see a "Location" text 78ms

@scope_ssm @sle_minion @scope_visualization @new_issue @flaky
Feature:Manage a group of systems and the Systems Set Manager 8m 25s 883ms 20 2 2

Scenario:
Log in as org admin user
1s 602ms 1

Given I am authorized for the "Admin" section 1s 602ms

@skip_if_github_validation
Scenario:
Pre-requisite: install dummy packages to allow patching
4s 984ms 4

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 788ms

And I refresh the metadata for "sle_minion" 868ms

And I install old package "andromeda-dummy-1.0" on this "sle_minion" 1s 655ms

And I install old package "virgo-dummy-1.0" on this "sle_minion" 1s 671ms

Scenario:
Pre-requisite: ensure that fake patches are available
5s 621ms 6

When I follow the left menu "Admin > Task Schedules" 131ms

And I follow "errata-cache-default" 1s 341ms

And I follow "errata-cache-bunch" 1s 252ms

And I click on "Single Run Schedule" 418ms

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 197ms

Scenario:
Pre-requisite: ensure that fake channels were created
51s 471ms 7

When I follow the left menu "Patches > Patch List > Relevant" 206ms

Then I should see an update in the list 18ms

When I wait until I see "andromeda-dummy" text, refreshing the page 85ms

Then I should see a "andromeda-dummy-6789" link 13ms

When I enter "virgo-dummy" as the filtered synopsis 45ms

And I click on the filter button until page does contain "virgo-dummy-3456" text 51s 91ms

Then I should see a "virgo-dummy-3456" link 11ms

Scenario:
Fail to create a group with only its name
573ms 5

When I follow the left menu "Systems > System Groups" 117ms

And I follow "Create Group" 269ms

And I enter "new-systems-group" as "name" 68ms

And I click on "Create Group" 58ms

Then I should see a "Both name and description are required for System Groups." text 60ms

Scenario:
Fail to create a group with only its description
761ms 5

When I follow the left menu "Systems > System Groups" 62ms

And I follow "Create Group" 291ms

And I enter "My new group" as "description" 56ms

And I click on "Create Group" 52ms

Then I should see a "Both name and description are required for System Groups." text 299ms

Scenario:
Create a group
931ms 6

When I follow the left menu "Systems > System Groups" 60ms

And I follow "Create Group" 268ms

And I enter "new-systems-group" as "name" 58ms

And I enter "My new group" as "description" 49ms

And I click on "Create Group" 49ms

Then I should see a "System group new-systems-group created." text 444ms

Scenario:
Add the SLE minion to the group and to SSM
2s 394ms 7

When I follow the left menu "Systems > System Groups" 58ms

And I follow "new-systems-group" 229ms

And I follow "Target Systems" 403ms

And I check the "sle_minion" client 60ms

And I click on "Add Systems" 1s 55ms

Then I should see a "1 systems were added to new-systems-group server group." text 92ms

When I click on "Add Selected to SSM" 494ms

Scenario:
The SLE minion is part of the new group
977ms 3

Given I am on the Systems overview page of this "sle_minion" 835ms

When I follow "Groups" in the content area 71ms

Then I should see a "new-systems-group" text 69ms

Scenario:
Apply a patch to systems in the system group
41s 416ms 14

When I follow the left menu "Systems > System Groups" 82ms

And I follow "new-systems-group" 292ms

And I follow first "Patches" 232ms

When I enter "virgo-dummy" as the filtered synopsis 44ms

And I click on the filter button until page does contain "virgo-dummy-3456" text 92ms

Then I should see a "virgo-dummy-3456" link 7ms

When I follow "virgo-dummy-3456" 361ms

And I follow first "Affected Systems" 293ms

And I check the "sle_minion" client 50ms

And I click on "Apply Patches" 539ms

And I click on "Confirm" 82ms

Then I should see a "Patch virgo-dummy-3456 has been scheduled for 1 system" text 92ms

And I am on the Systems overview page of this "sle_minion" 910ms

And I wait until event "Patch Update: virgo-dummy-3456 - Test update for virgo-dummy scheduled by admin" is completed 38s 334ms

Scenario:
Apply a patch to systems in the SSM
42s 336ms 14

When I follow the left menu "Systems > System Set Manager > Overview" 406ms

And I follow first "Patches" 371ms

When I enter "andromeda-dummy" as the filtered synopsis 61ms

And I click on the filter button 385ms

When I wait until I see "andromeda-dummy-6789" text, refreshing the page 64ms

Then I should see a "andromeda-dummy-6789" link 11ms

When I follow "andromeda-dummy-6789" 376ms

And I follow first "Affected Systems" 305ms

And I check the "sle_minion" client 60ms

And I click on "Apply Patches" 420ms

And I click on "Confirm" 589ms

Then I should see a "Patch andromeda-dummy-6789 has been scheduled for 1 system" text 90ms

And I am on the Systems overview page of this "sle_minion" 906ms

And I wait until event "Patch Update: andromeda-dummy-6789 - Test update for andromeda-dummy scheduled by admin" is completed 38s 286ms

@skip_if_github_validation
Scenario:
Delete a package from systems in the SSM
24s 608ms 5 5 1

When I follow the left menu "Systems > System Set Manager > Overview" 408ms

And I follow "Packages" 355ms

And I follow "Remove" 337ms

And I wait until I see "Package Removal" text, refreshing the page 69ms

And I enter "virgo-dummy" as the filtered package name 10s 12ms Show Error + 
                                            
 Unable to find css "input[placeholder='Filter by Package Name: ']" (Capybara::ElementNotFound)
./features/support/navigation_step_helper.rb:45:in `filter_by_package_name'
./features/step_definitions/navigation_steps.rb:925:in `/^I enter "([^"]*)" as the filtered package name$/'
features/secondary/allcli_system_group.feature:113:in `I enter "virgo-dummy" as the filtered package name'

And I click on the filter button until page does contain "virgo-dummy-2.0-1.1" text 0s

And I check "virgo-dummy-2.0-1.1" in the list 0s

And I click on "Remove Packages" 0s

And I click on "Confirm" 0s

Then I should see a "Package removals are being scheduled, it may take several minutes for this to complete." text 0s

13s 424ms Show Info + 
15:03:38:000 - 15:03:49:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/ssm/PackageRemove.do
Screenshot +

@skip_if_github_validation
Scenario:
Install a package to systems in the SSM
4m 27s 177ms 4 9 1

When I follow the left menu "Systems > System Set Manager > Overview" 71ms

And I follow "Packages" 326ms

And I follow "Install" 284ms

And I wait until I see "Fake-RPM-SUSE-Channel" text, refreshing the page 4m 13s 13ms Show Error + 
                                            
 execution expired (Timeout::Error)
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/step_definitions/navigation_steps.rb:59:in `/^I wait until I see "([^"]*)" (text|regex), refreshing the page$/'
features/secondary/allcli_system_group.feature:126:in `I wait until I see "Fake-RPM-SUSE-Channel" text, refreshing the page'

Then I should see a "Fake-RPM-SUSE-Channel" text 0s

When I follow "Fake-RPM-SUSE-Channel" 0s

Then I should see a "virgo-dummy-2.0-1.1" text 0s

And I enter "virgo-dummy" as the filtered package name 0s

And I click on the filter button until page does contain "virgo-dummy-2.0-1.1" text 0s

When I check "virgo-dummy-2.0-1.1" in the list 0s

And I click on "Install Packages" 0s

And I click on "Confirm" 0s

Then I should see a "Package installations are being scheduled, it may take several minutes for this to complete." text 0s

13s 481ms Show Info + 
15:04:03:000 - 15:08:17:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/ssm/PackageInstall.do
Screenshot +

@rhlike_minion
Scenario:
Add the Red Hat-like minion to the group in a different way
2s 120ms 8

When I follow the left menu "Systems > System Groups" 74ms

Then I should see a "System Groups" text 70ms

When I follow "new-systems-group" 307ms

And I follow "Target Systems" 396ms

Then I should see a "The following are systems that may be added to this group." text 98ms

When I check the "rhlike_minion" client 61ms

And I click on "Add Systems" 1s 21ms

Then I should see a "1 systems were added to new-systems-group server group" text 90ms

Scenario:
Add the new group to SSM
248ms 5

When I follow the left menu "Systems > System Groups" 58ms

And I click on "Use in SSM" in row "new-systems-group" 68ms

Then I should see a "Selected Systems List" text 91ms

And I should see "rhlike_minion" as link 13ms

And I should see "sle_minion" as link 16ms

@skip_if_containerized_server
Scenario:
Install the locale formula package on the server
< 1ms 1

When I manually install the "locale" formula on the server 0s

Scenario:
I synchronize all Salt dynamic modules on "sle_minion"
2s 484ms 1

When I synchronize all Salt dynamic modules on "sle_minion" 2s 484ms

Scenario:
New formula page is rendered for the system group
11s 95ms 6

When I follow the left menu "Systems > System Groups" 57ms

And I follow "new-systems-group" 289ms

And I follow "Formulas" 379ms

Then I should see a "Choose formulas:" text 59ms

And I should see a "General System Configuration" text 280ms

And the "locale" formula should be unchecked 10s 28ms

@rhlike_minion
Scenario:
Apply the highstate to the group
31s 656ms 10

When I follow the left menu "Systems > System Groups" 59ms

Then I should see a "System Groups" text 73ms

When I follow "new-systems-group" 291ms

And I follow "States" 408ms

And I click on "Apply Highstate" 56ms

Then I should see a "Applying the highstate has been scheduled." text 421ms

When I follow "scheduled" 254ms

Then I should see a "Apply states (highstate)" text 61ms

And I should see a "Action Details" text 52ms

And I wait until I see "2 systems successfully completed this action." text, refreshing the page 29s 976ms

Scenario:
Remove SLE minion from new group
2s 337ms 5

Given I am on the Systems overview page of this "sle_minion" 825ms

When I follow "Groups" 383ms

And I check "new-systems-group" in the list 63ms

And I click on "Leave Groups" 1s 1ms

Then I should see a "1 system groups removed." text 63ms

@skip_if_containerized_server
Scenario:
Cleanup: uninstall formula from the server
< 1ms 1

When I manually uninstall the "locale" formula from the server 0s

Scenario:
Cleanup: remove the new group
1s 414ms 7

When I follow the left menu "Systems > System Groups" 71ms

When I follow "new-systems-group" in the content area 69ms

And I follow "Delete Group" in the content area 71ms

And I click on "Confirm Deletion" 1s 27ms

Then I should see a "System group" text 59ms

And I should see a "new-systems-group" text 58ms

And I should see a "deleted" text 56ms

Scenario:
Cleanup: regenerate search index for later tests
5s 76ms 1

Search by hostname: uyuni-master-suse-minion
[{"last_boot"=>"2026-02-02T12:06:47Z", "name"=>"uyuni-master-suse-minion.sumaci.aws", "id"=>1000010023, "last_checkin"=>"2026-02-02T14:09:22Z"}]

When I clean the search index on the server 5s 76ms

Scenario:
Cleanup: remove dummy packages
4s 593ms 4

When I disable repository "test_repo_rpm_pool" on this "sle_minion" without error control 770ms

And I refresh the metadata for "sle_minion" 885ms

And I remove package "andromeda-dummy" from this "sle_minion" without error control 1s 426ms

And I remove package "virgo-dummy" from this "sle_minion" without error control 1s 510ms

@scope_configuration_channels
Feature:Management of configuration of all types of clients in a single channel 2m 2s 323ms 28

Scenario:
Log in as org admin user
1s 855ms 1

Given I am authorized 1s 855ms

Scenario:
Create a configuration channel for mixed client types
1s 925ms 7

When I follow the left menu "Configuration > Channels" 1s 188ms

And I follow "Create Config Channel" 404ms

And I enter "Mixed Channel" as "cofName" 59ms

And I enter "mixedchannel" as "cofLabel" 57ms

And I enter "This is a configuration channel for different system types" as "cofDescription" 91ms

And I click on "Create Config Channel" 61ms

Then I should see a "Mixed Channel" text 61ms

Scenario:
Add a configuration file to the mixed configuration channel
3s 146ms 9

When I follow the left menu "Configuration > Channels" 59ms

And I follow "Mixed Channel" 459ms

And I follow "Create Configuration File or Directory" 431ms

And I enter "/etc/s-mgr/config" as "cffPath" 64ms

And I enter "COLOR=white" in the editor 4ms

And I click on "Create Configuration File" 61ms

Then I should see a "Revision 1 of /etc/s-mgr/config from channel Mixed Channel" text 89ms

And file "/srv/susemanager/salt/manager_org_1/mixedchannel/init.sls" should exist on server 1s 241ms

And file "/srv/susemanager/salt/manager_org_1/mixedchannel/etc/s-mgr/config" should exist on server 734ms

@sle_minion
Scenario:
Subscribe a Salt minion to the configuration channel
3s 347ms 8

When I am on the Systems overview page of this "sle_minion" 1s 120ms

And I follow "Configuration" in the content area 67ms

And I follow "Manage Configuration Channels" in the content area 89ms

And I follow first "Subscribe to Channels" in the content area 61ms

And I check "Mixed Channel" in the list 53ms

And I click on "Continue" 832ms

And I click on "Update Channel Rankings" 1s 48ms

Then I should see a "Channel Subscriptions successfully changed for" text 74ms

@rhlike_minion
Scenario:
Subscribe a Red Hat-like minion to the configuration channel
3s 289ms 8

When I am on the Systems overview page of this "rhlike_minion" 1s 129ms

And I follow "Configuration" in the content area 59ms

And I follow "Manage Configuration Channels" in the content area 56ms

And I follow first "Subscribe to Channels" in the content area 54ms

And I check "Mixed Channel" in the list 50ms

And I click on "Continue" 715ms

And I click on "Update Channel Rankings" 1s 152ms

Then I should see a "Channel Subscriptions successfully changed for" text 71ms

@deblike_minion
Scenario:
Subscribe a Debian-like minion to the configuration channel
3s 420ms 8

When I am on the Systems overview page of this "deblike_minion" 1s 352ms

And I follow "Configuration" in the content area 59ms

And I follow "Manage Configuration Channels" in the content area 55ms

And I follow first "Subscribe to Channels" in the content area 55ms

And I check "Mixed Channel" in the list 48ms

And I click on "Continue" 47ms

And I click on "Update Channel Rankings" 1s 723ms

Then I should see a "Channel Subscriptions successfully changed for" text 77ms

@ssh_minion
Scenario:
Subscribe a SSH minion to the configuration channel
3s 366ms 8

When I am on the Systems overview page of this "ssh_minion" 1s 341ms

And I follow "Configuration" in the content area 58ms

And I follow "Manage Configuration Channels" in the content area 56ms

And I follow first "Subscribe to Channels" in the content area 58ms

And I check "Mixed Channel" in the list 50ms

And I click on "Continue" 765ms

And I click on "Update Channel Rankings" 962ms

Then I should see a "Channel Subscriptions successfully changed for" text 73ms

Scenario:
Deploy the file to all systems
2s 416ms 7

When I follow the left menu "Configuration > Channels" 429ms

And I follow "Mixed Channel" 484ms

And I follow "Deploy all configuration files to all subscribed systems" 529ms

Then I should see a "/etc/s-mgr/config" link 11ms

When I click on "Deploy Files to Selected Systems" 836ms

Then I should see a "revision-deploys are being scheduled," text 63ms

And I should see a "0 revision-deploys overridden." text 62ms

@sle_minion
Scenario:
Check that file has been created on SLE minion
3s 74ms 2

When I wait until file "/etc/s-mgr/config" exists on "sle_minion" 2s 225ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "sle_minion" 848ms

@rhlike_minion
Scenario:
Check that file has been created on Red Hat-like minion
618ms 2

When I wait until file "/etc/s-mgr/config" exists on "rhlike_minion" 277ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "rhlike_minion" 341ms

@deblike_minion
Scenario:
Check that file has been created on Debian-like minion
1s 401ms 2

When I wait until file "/etc/s-mgr/config" exists on "deblike_minion" 973ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "deblike_minion" 428ms

@ssh_minion
Scenario:
Check that file has been created on SSH minion
7s 178ms 2

When I wait until file "/etc/s-mgr/config" exists on "ssh_minion" 6s 355ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "ssh_minion" 823ms

@sle_minion
Scenario:
Apply highstate to override changed content on SLE minion
14s 456ms 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" 406ms

And I apply highstate on "sle_minion" 12s 902ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "sle_minion" 1s 147ms

@rhlike_minion
Scenario:
Apply highstate to override changed content on Red Hat-like minion
7s 11ms 3

Salt command: salt uyuni-master-rhlike-minion.sumaci.aws state.highstate

When I store "COLOR=blue" into file "/etc/s-mgr/config" on "rhlike_minion" 257ms

And I apply highstate on "rhlike_minion" 6s 412ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "rhlike_minion" 341ms

@deblike_minion
Scenario:
Apply highstate to override changed content on Debian-like minion
7s 581ms 3

Salt command: salt uyuni-master-deblike-minion.sumaci.aws state.highstate

When I store "COLOR=blue" into file "/etc/s-mgr/config" on "deblike_minion" 469ms

And I apply highstate on "deblike_minion" 6s 679ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "deblike_minion" 432ms

@ssh_minion
Scenario:
Apply highstate to override changed content on SSH minion
30s 751ms 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" 743ms

And I apply highstate on "ssh_minion" 29s 135ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "ssh_minion" 872ms

@rhlike_minion
Scenario:
Unsubscribe Red Hat-like minion and delete configuration files
1s 68ms 7

When I follow the left menu "Configuration > Channels" 60ms

And I follow "Mixed Channel" 475ms

And I follow "Systems" in the content area 67ms

And I check the "rhlike_minion" client 62ms

And I click on "Unsubscribe systems" 53ms

Then I should see a "Successfully unsubscribed 1 system(s)." text 75ms

And I destroy "/etc/s-mgr" directory on "rhlike_minion" 273ms

@deblike_minion
Scenario:
Unsubscribe Debian-like minion and delete configuration files
1s 692ms 7

When I follow the left menu "Configuration > Channels" 59ms

And I follow "Mixed Channel" 458ms

And I follow "Systems" in the content area 54ms

And I check the "deblike_minion" client 53ms

And I click on "Unsubscribe systems" 47ms

Then I should see a "Successfully unsubscribed 1 system(s)." text 68ms

And I destroy "/etc/s-mgr" directory on "deblike_minion" 950ms

@ssh_minion
Scenario:
Unsubscribe SSH minion and delete configuration files
1s 663ms 7

When I follow the left menu "Configuration > Channels" 59ms

And I follow "Mixed Channel" 420ms

And I follow "Systems" in the content area 55ms

And I check the "ssh_minion" client 51ms

And I click on "Unsubscribe systems" 46ms

Then I should see a "Successfully unsubscribed 1 system(s)." text 609ms

And I destroy "/etc/s-mgr" directory on "ssh_minion" 420ms

@sle_minion
Scenario:
Change file on Salt minion and compare
6s 502ms 13

When I am on the Systems overview page of this "sle_minion" 971ms

And I store "COLOR=red" into file "/etc/s-mgr/config" on "sle_minion" 719ms

And I follow "Configuration" in the content area 66ms

And I follow "Compare Files" in the content area 63ms

And I check "/etc/s-mgr/config" in the list 55ms

And I click on "Compare Files" 747ms

And I click on "Schedule Compare" 922ms

Then I should see a "1 files scheduled for comparison." text 72ms

When I wait until event "Show differences between profiled config files and deployed config files scheduled" is completed 2s 325ms

Then I should see a "Differences exist" link 10ms

When I follow "Differences exist" 424ms

Then I should see a "+COLOR=white" text 63ms

And I should see a "-COLOR=red" text 60ms

@sle_minion
Scenario:
Check configuration channel and files via API for Salt minion
1s 3

Then channel "mixedchannel" should exist 338ms

And channel "mixedchannel" should contain file "/etc/s-mgr/config" 334ms

And "sle_minion" should be subscribed to channel "mixedchannel" 326ms

@sle_minion
Scenario:
Extend configuration channel and deploy files via API for Salt minion
6s 227ms 6

When I store "COLOR=green" into file "/etc/s-mgr/config" on "sle_minion" 413ms

And I add file "/etc/s-mgr/other" containing "NAME=Dante" to channel "mixedchannel" 403ms

And I deploy all systems registered to channel "mixedchannel" 427ms

And I wait until file "/etc/s-mgr/other" exists on "sle_minion" 3s 338ms

Then file "/etc/s-mgr/config" should contain "COLOR=white" on "sle_minion" 832ms

And file "/etc/s-mgr/other" should contain "NAME=Dante" on "sle_minion" 811ms

@sle_minion
Scenario:
Unsubscribe systems via API for Salt minion
1s 26ms 2

When I unsubscribe "sle_minion" from configuration channel "mixedchannel" 712ms

Then "sle_minion" should not be subscribed to channel "mixedchannel" 314ms

@sle_minion
Scenario:
Re-add SLE Minion via SSM
3s 368ms 10

When I follow the left menu "Systems > System List > All" 125ms

And I click on the clear SSM button 70ms

And I check the "sle_minion" client 452ms

And I follow the left menu "Systems > System Set Manager > Overview" 466ms

And I follow "config channel subscriptions" in the content area 64ms

And I check "Mixed Channel" in the list 54ms

And I click on "Continue" 54ms

And I click on "Apply Subscriptions" 1s 267ms

And I click on "Confirm" 752ms

Then I should see a "Configuration channel subscriptions changed for 1 system successfully." text 60ms

@sle_minion
Scenario:
Cleanup: remove remaining Salt minion from configuration channel
1s 666ms 6

When I follow the left menu "Configuration > Channels" 366ms

And I follow "Mixed Channel" 528ms

And I follow "Systems" in the content area 61ms

And I check the "sle_minion" client 51ms

And I click on "Unsubscribe systems" 608ms

Then I should see a "Successfully unsubscribed 1 system(s)." text 51ms

Scenario:
Cleanup: remove the mixed configuration channel
2s 480ms 5

When I follow the left menu "Configuration > Channels" 57ms

And I follow "Mixed Channel" 410ms

And I follow "Delete Channel" 346ms

And I click on "Delete Config Channel" 554ms

Then file "/srv/susemanager/salt/manager_org_1/mixedchannel/init.sls" should not exist on server 1s 112ms

@sle_minion
Scenario:
Cleanup: delete configuration files on remaining Salt minion
732ms 1

When I destroy "/etc/s-mgr" directory on "sle_minion" 732ms

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 19s 179ms 14 5

Scenario:
Log in as org admin user
1s 923ms 1

Given I am authorized 1s 923ms

@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 121ms 22

When I follow the left menu "Systems > System List > All" 162ms

And I click on the clear SSM button 52ms

And I check the "sle_minion" client 459ms

And I should see "1" systems selected for SSM 121ms

And I follow the left menu "Systems > System Set Manager > Overview" 432ms

And I follow "channel memberships" in the content area 63ms

Then I should see a "Base Channel" text 63ms

And I should see a "Next" text 59ms

When I select "Fake-Base-Channel-SUSE-like" from drop-down in table line with "openSUSE Tumbleweed (x86_64)" 218ms

And I click on "Next" 57ms

Then I should see a "Child Channels" text 383ms

And I should see a "Fake-Base-Channel-SUSE-like" text 71ms

And I should see a "1 system(s) to subscribe" text 62ms

When I choose radio button "Subscribe" for child channel "Fake-Child-Channel-SUSE-like" 65ms

And I click on "Next" 55ms

Then I should see a "Channel Changes Overview" text 60ms

And I should see a "1 system(s) to subscribe" text 61ms

When I schedule action to 3 minutes from now 220ms

And I click on "Confirm" 50ms

And I remember when I scheduled an action < 1ms

Then I wait until I see "Channel Changes Actions" text 377ms

And a table line should contain system "sle_minion", "Scheduled" 19ms

@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 809ms 7

Given I am on the Systems overview page of this "sle_minion" 941ms

When I follow "Software" in the content area 67ms

And I follow "Software Channels" in the content area 64ms

And I wait until I do not see "Loading..." text 64ms

Then radio button "openSUSE Tumbleweed (x86_64)" should be checked 254ms

And I wait until I do not see "Loading..." text 400ms

And I should see "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" as unchecked 17ms

@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 499ms 3

When I refresh the metadata for "sle_minion" 1s 229ms

Then channel "openSUSE Tumbleweed (x86_64)" should be enabled on "sle_minion" 637ms

And channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" should be disabled on "sle_minion" 631ms

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 143ms 3

Given I am on the Systems overview page of this "sle_minion" 917ms

When I wait until event "Subscribe channels scheduled" is completed 1m 13s 162ms

Then I should see a "The client completed this action on" text 63ms

@sle_minion
Scenario:
Check the SLES minion is subscribed to the new channels
1s 676ms 7

Given I am on the Systems overview page of this "sle_minion" 815ms

When I follow "Software" in the content area 76ms

And I follow "Software Channels" in the content area 87ms

And I wait until I do not see "Loading..." text 66ms

Then radio button "Fake-Base-Channel-SUSE-like" should be checked 126ms

And I wait until I do not see "Loading..." text 486ms

And I should see "Fake-Child-Channel-SUSE-like" as checked 18ms

@sle_minion @susemanager
Scenario:
Check via API the new channels are enabled on the SLES minion
< 1ms 4

When I refresh the metadata for "sle_minion" 0s

Then "2" channels should be enabled on "sle_minion" 0s

And channel "Fake-Base-Channel-SUSE-like" should be enabled on "sle_minion" 0s

And channel "Fake-Child-Channel-SUSE-like" should be enabled on "sle_minion" 0s

@uyuni
Scenario:
Check via API the new channels are enabled on the openSUSE minion
3s 450ms 4

When I refresh the metadata for "sle_minion" 1s 550ms

Then "2" channels should be enabled on "sle_minion" 629ms

And channel "Fake-Base-Channel-SUSE-like" should be enabled on "sle_minion" 630ms

And channel "Fake-Child-Channel-SUSE-like" should be enabled on "sle_minion" 640ms

@rhlike_minion
Scenario:
System default channel can't be determined on the Red Hat-like minion
2s 621ms 20

When I follow the left menu "Systems > System List > All" 146ms

And I click on the clear SSM button 52ms

And I check the "rhlike_minion" client 437ms

Then I should see "1" systems selected for SSM 120ms

When I follow the left menu "Systems > System Set Manager > Overview" 399ms

And I follow "channel memberships" in the content area 64ms

And I select "System Default Base Channel" from drop-down in table line with "Fake-Base-Channel-RH-like" 234ms

And I click on "Next" 58ms

Then I should see a "Child Channels" text 275ms

And I should see a "Couldn't determine new base channel" text 60ms

And I should see a "1 system(s) incompatible" text 62ms

When I click on "Next" 56ms

Then I should see a "Channel Changes Overview" text 59ms

And I should see a "Couldn't determine new base channel" text 62ms

And I should see a "1 system(s) incompatible" text 69ms

When I click on "Confirm" 56ms

Then I should see a "Channel Changes Actions" text 274ms

And I should see a "Items 1 - 1 of 1" text 61ms

And a table line should contain system "rhlike_minion", "Could not determine system default channel" 20ms

And I click on the clear SSM button 47ms

@rhlike_minion
Scenario:
Cleanup: make sure the Red Hat-like minion is still unchanged
1s 194ms 4

Given I am on the Systems overview page of this "rhlike_minion" 841ms

When I follow "Software" in the content area 56ms

And I follow "Software Channels" in the content area 69ms

Then radio button "Fake-Base-Channel-RH-like" should be checked 227ms

@deblike_minion
Scenario:
System default channel can't be determined on the Debian-like minion
2s 562ms 20

When I follow the left menu "Systems > System List > All" 108ms

And I click on the clear SSM button 44ms

And I check the "deblike_minion" client 433ms

Then I should see "1" systems selected for SSM 140ms

When I follow the left menu "Systems > System Set Manager > Overview" 413ms

And I follow "channel memberships" in the content area 54ms

And I select "System Default Base Channel" from drop-down in table line with "Fake-Base-Channel-Debian-like" 197ms

And I click on "Next" 49ms

Then I should see a "Child Channels" text 300ms

And I should see a "Couldn't determine new base channel" text 58ms

And I should see a "1 system(s) incompatible" text 62ms

When I click on "Next" 54ms

Then I should see a "Channel Changes Overview" text 60ms

And I should see a "Couldn't determine new base channel" text 62ms

And I should see a "1 system(s) incompatible" text 71ms

When I click on "Confirm" 54ms

Then I should see a "Channel Changes Actions" text 269ms

And I should see a "Items 1 - 1 of 1" text 60ms

And a table line should contain system "deblike_minion", "Could not determine system default channel" 17ms

And I click on the clear SSM button 47ms

@deblike_minion
Scenario:
Cleanup: make sure the Debian-like minion is still unchanged
1s 221ms 4

Given I am on the Systems overview page of this "deblike_minion" 879ms

When I follow "Software" in the content area 60ms

And I follow "Software Channels" in the content area 71ms

Then radio button "Fake-Base-Channel-Debian-like" should be checked 210ms

@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
42s 885ms 15

Given I am on the Systems overview page of this "sle_minion" 866ms

When I follow "Software" in the content area 61ms

And I follow "Software Channels" in the content area 70ms

And I wait until I do not see "Loading..." text 62ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 10s 65ms

And I wait until I do not see "Loading..." text 492ms

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 75ms

And I check "Fake-RPM-SUSE-Channel" 72ms

And I click on "Next" 53ms

Then I should see a "Confirm Software Channel Change" text 61ms

When I click on "Confirm" 66ms

Then I should see a "Changing the channels has been scheduled." text 287ms

When I follow "scheduled" in the content area 70ms

And I wait until I see "1 system successfully completed this action." text, refreshing the page 29s 961ms

Then channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" should be disabled on "sle_minion" 616ms

Scenario:
Cleanup: remove remaining systems from SSM after channel subscription tests
68ms 1

When I click on the clear SSM button 68ms

@scope_changing_software_channels @scc_credentials
Feature:Channel subscription with recommended or required dependencies 46s 420ms 5 2

Scenario:
Log in as org admin user
1s 815ms 1

Given I am authorized 1s 815ms

Scenario:
Pre-requisite: remove remaining systems from SSM after software channel tests
53ms 1

When I click on the clear SSM button 53ms

@susemanager
Scenario:
Play with recommended and required child channels selection for a single system
< 1ms 15

Given I am on the Systems overview page of this "sle_minion" 0s

When I follow "Software" in the content area 0s

And I follow "Software Channels" in the content area 0s

And I wait until I do not see "Loading..." text 0s

And I check radio button "SLE-Product-SLES15-SP7-Pool for x86_64" 0s

And I wait until I do not see "Loading..." text 0s

Then I should see the child channel "SLE-Product-SLES15-SP7-Updates for x86_64" "selected" and "disabled" 0s

When I exclude the recommended child channels 0s

Then I should see the toggler "disabled" 0s

And I should see a "SLE-Module-Containers15-SP7-Pool for x86_64" text 0s

And I should see the child channel "SLE-Module-Containers15-SP7-Pool for x86_64" "unselected" 0s

When I select the child channel "SLE-Module-Containers15-SP7-Pool for x86_64" 0s

Then I should see the child channel "SLE-Module-Containers15-SP7-Pool for x86_64" "selected" 0s

When I click on the "disabled" toggler 0s

Then I should see the child channel "SLE-Module-Server-Applications15-SP7-Pool for x86_64" "selected" 0s

@uyuni
Scenario:
Play with recommended and required child channels selection for a single system
42s 568ms 10

Given I am on the Systems overview page of this "sle_minion" 1s 474ms

When I follow "Software" in the content area 68ms

And I follow "Software Channels" in the content area 62ms

And I wait for child channels to appear 197ms

And I check radio button "(none, disable service)" 10s 68ms

And I wait for child channels to appear 219ms

And I check radio button "openSUSE Tumbleweed (x86_64)" 10s 79ms

Then I should see the child channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" "unselected" and "disabled" 10s 129ms

When I select the child channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" 10s 161ms

Then I should see the child channel "Uyuni Client Tools for openSUSE Tumbleweed (x86_64)" "selected" 105ms

@susemanager
Scenario:
Play with recommended and required child channels selection in SSM
< 1ms 16

When I follow the left menu "Systems > System List > All" 0s

And I check the "sle_minion" client 0s

Then I should see "1" systems selected for SSM 0s

When I follow the left menu "Systems > System Set Manager > Overview" 0s

And I follow "channel memberships" in the content area 0s

Then I should see a "Base Channel" text 0s

And I should see a "Next" text 0s

And I should see a table line with "SLE-Product-SLES15-SP7-Pool for x86_64", "1" 0s

When I select "System Default Base Channel" from drop-down in table line with "SLE-Product-SLES15-SP7-Pool for x86_64" 0s

And I click on "Next" 0s

Then I should see the toggler "disabled" 0s

And I should see a "SLE-Module-Basesystem15-SP7-Pool for x86_64" text 0s

And I should see "No change" "selected" for the "SLE-Module-Basesystem15-SP7-Pool for x86_64" channel 0s

When I click on the "disabled" toggler 0s

Then I should see "Subscribe" "selected" for the "SLE-Module-Basesystem15-SP7-Pool for x86_64" channel 0s

And I should see "No change" "unselected" for the "SLE-Module-Basesystem15-SP7-Pool for x86_64" channel 0s

@uyuni
Scenario:
Play with recommended and required child channels selection in SSM
1s 925ms 10

When I follow the left menu "Systems > System List > All" 130ms

And I check the "sle_minion" client 517ms

Then I should see "1" systems selected for SSM 135ms

When I follow the left menu "Systems > System Set Manager > Overview" 434ms

And I follow "channel memberships" in the content area 67ms

Then I should see a "Base Channel" text 65ms

And I should see a "Next" text 69ms

When I select "No Change" from drop-down in table line with "openSUSE Tumbleweed (x86_64)" 86ms

And I click on "Next" 58ms

Then I should see the toggler "disabled" 359ms

Scenario:
Cleanup: remove remaining systems from SSM after software channel tests
57ms 1

When I click on the clear SSM button 57ms

@flaky @scope_res @scope_salt @rhlike_minion
Feature:Install a patch on the Red Hat-like minion via Salt through the UI 2m 2s 696ms 10

Scenario:
Pre-requisite: enable test_repo_rpm_pool repository on the Red Hat-like minion
280ms 1

When I enable repository "test_repo_rpm_pool" on this "rhlike_minion" 280ms

Scenario:
Pre-requisite: install virgo-dummy-1.0 package on Red Hat-like minion
1s 461ms 1

When I install package "virgo-dummy-1.0" on this "rhlike_minion" 1s 461ms

Scenario:
Pre-requisite: remove andromeda-dummy package from Red Hat-like minion
1s 351ms 1

When I remove package "andromeda-dummy" from this "rhlike_minion" 1s 351ms

Scenario:
Pre-requisite: refresh package list and check newly installed packages on Red Hat-like minion
19s 346ms 3

When I refresh packages list via spacecmd on "rhlike_minion" 3s 174ms

And I wait until refresh package list on "rhlike_minion" is finished 13s 964ms

Then spacecmd should show packages "virgo-dummy-1.0" installed on "rhlike_minion" 2s 207ms

Scenario:
Log in as org admin user
1s 562ms 1

Given I am authorized for the "Admin" section 1s 562ms

Scenario:
Pre-requisite: re-subscribe the Red Hat-like minion to a base channel
21s 298ms 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 331ms

When I follow "Software" in the content area 70ms

And I follow "Software Channels" in the content area 83ms

And I wait until I do not see "Loading..." text 67ms

And I check radio button "Fake-Base-Channel-RH-like" 157ms

And I wait until I do not see "Loading..." text 423ms

And I click on "Next" 53ms

Then I should see a "Confirm Software Channel Change" text 59ms

When I click on "Confirm" 76ms

Then I should see a "Changing the channels has been scheduled." text 285ms

And I wait until event "Subscribe channels scheduled" is completed 18s 689ms

Scenario:
Schedule errata refresh to reflect channel assignment on Red Hat-like minion
16s 800ms 10

When I follow "Software" in the content area 59ms

And I follow "List / Remove" in the content area 61ms

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 886ms

When I follow the left menu "Admin > Task Schedules" 116ms

And I follow "errata-cache-default" 396ms

And I follow "errata-cache-bunch" 1s 345ms

And I click on "Single Run Schedule" 1s 526ms

Then I should see a "bunch was scheduled" text 273ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 1s 982ms

Scenario:
Install a patch on the Red Hat-like minion
11s 914ms 8

Given I am on the Systems overview page of this "rhlike_minion" 783ms

When I follow "Software" in the content area 70ms

And I follow "Patches" in the content area 64ms

When I check "virgo-dummy-3456" in the list 62ms

And I click on "Apply Patches" 553ms

And I click on "Confirm" 996ms

Then I should see a "1 patch update has been scheduled for" text 80ms

And I wait for "virgo-dummy-2.0-1.1" to be installed on "rhlike_minion" 9s 301ms

Scenario:
Install a package on the Red Hat-like minion
23s 543ms 7

When I follow "Software" in the content area 59ms

And I follow "Install" 443ms

And I check "andromeda-dummy" in the list 53ms

And I click on "Install Packages" 607ms

And I click on "Confirm" 595ms

Then I should see a "1 package install has been scheduled for" text 61ms

And I wait until event "Package Install/Upgrade scheduled" is completed 21s 721ms

Scenario:
Cleanup: remove virgo-dummy and andromeda-dummy packages from Red Hat-like minion
25s 137ms 13

When I follow "Software" in the content area 77ms

And I follow "List / Remove" 597ms

And I enter "andromeda" as the filtered package name 118ms

And I click on the filter button 820ms

And I check "andromeda-dummy" in the list 59ms

And I enter "virgo-dummy" as the filtered package name 39ms

And I click on the filter button 124ms

And I check "virgo-dummy" in the list 53ms

And I click on "Remove Packages" 506ms

And I click on "Confirm" 588ms

Then I should see a "2 package removals have been scheduled" text 61ms

And I wait until event "Package Removal scheduled" is completed 21s 807ms

And I disable repository "test_repo_rpm_pool" on this "rhlike_minion" 281ms

@scope_monitoring @scope_res @rhlike_minion
Feature:Monitor MLM environment with Prometheus on a Red Hat-like Salt minion 1m 11s 70ms 10

In order to monitor Uyuni server
As an authorized user
I want to enable Prometheus exporters

Scenario:
Log in as org admin user
1s 566ms 1

Given I am authorized 1s 566ms

Scenario:
Apply Prometheus exporter formulas on the Red Hat-like minion
2s 692ms 7

Given I am on the Systems overview page of this "rhlike_minion" 1s 457ms

When I follow "Formulas" in the content area 72ms

Then I should see a "Choose formulas:" text 64ms

And I should see a "Monitoring" text 270ms

When I check the "prometheus-exporters" formula 73ms

And I click on "Save" 66ms

And I wait until I see "Formula saved" text 686ms

Scenario:
Configure Prometheus exporter formula on the Red Hat-like minion
2s 31ms 9

When I follow "Formulas" in the content area 61ms

And I follow "Prometheus Exporters" in the content area 262ms

And I click on "Expand All Sections" 169ms

Then I should see a "Enable and configure Prometheus exporters for managed systems." text 106ms

When I check "node" exporter 43ms

And I check "apache" exporter 81ms

And I check "postgres" exporter 79ms

And I click on "Save" 90ms

Then I should see a "Formula saved" text 1s 136ms

Scenario:
Enable tools_update_repo tools_pool_repo so the exporters packages are available
461ms 1

When I enable the repositories "tools_update_repo tools_pool_repo" on this "rhlike_minion" without error control 461ms

@skip_if_github_validation
Scenario:
Apply highstate for Prometheus exporters on the Red Hat-like minion
39s 13ms 4

When I follow "States" in the content area 69ms

And I click on "Apply Highstate" 56ms

Then I should see a "Applying the highstate has been scheduled." text 426ms

And I wait until event "Apply highstate scheduled" is completed 38s 461ms

@skip_if_github_validation
Scenario:
Wait for service
643ms 3

When I wait until "node" exporter service is active on "rhlike_minion" 285ms

And I wait until "apache" exporter service is active on "rhlike_minion" 180ms

And I wait until "postgres" exporter service is active on "rhlike_minion" 177ms

Scenario:
Visit monitoring endpoints on the Red Hat-like minion
528ms 3

When I visit "Prometheus node exporter" endpoint of this "rhlike_minion" 173ms

And I visit "Prometheus apache exporter" endpoint of this "rhlike_minion" 176ms

And I visit "Prometheus postgres exporter" endpoint of this "rhlike_minion" 179ms

Scenario:
Cleanup: undo Prometheus exporter formulas on the Red Hat-like minion
1s 451ms 4

When I follow "Formulas" in the content area 82ms

And I uncheck the "prometheus-exporters" formula 245ms

And I click on "Save" 62ms

Then I wait until I see "Formula saved" text 1s 62ms

@skip_if_github_validation
Scenario:
Cleanup: apply highstate after test monitoring on the Red Hat-like minion
22s 413ms 4

When I follow "States" in the content area 72ms

And I click on "Apply Highstate" 62ms

Then I should see a "Applying the highstate has been scheduled." text 421ms

And I wait until event "Apply highstate scheduled" is completed 21s 857ms

Scenario:
Cleanup: Disable tools_update_repo tools_pool_repo because they are no longer needed
266ms 1

When I disable the repositories "tools_update_repo tools_pool_repo" on this "rhlike_minion" without error control 266ms

@skip_if_github_validation @scope_salt
Feature:Install a package and a patch on the SUSE SSH client via Salt through the UI 3m 55s 351ms 11

Scenario:
Pre-requisite: enable test_repo_rpm_pool repository on SSH minion
873ms 1

When I enable repository "test_repo_rpm_pool" on this "ssh_minion" 873ms

Scenario:
Pre-requisite: install virgo-dummy-1.0 package on SSH minion
2s 353ms 2

When I refresh the metadata for "ssh_minion" 946ms

And I install old package "virgo-dummy-1.0" on this "ssh_minion" without error control 1s 407ms

Scenario:
Pre-requisite: remove andromeda-dummy package from SSH minion
25s 682ms 4

When I remove package "andromeda-dummy" from this "ssh_minion" without error control 1s 56ms

And I refresh the metadata for "ssh_minion" 826ms

And I refresh packages list via spacecmd on "ssh_minion" 2s 577ms

And I wait until refresh package list on "ssh_minion" is finished 21s 222ms

Scenario:
Pre-requisite: refresh package list and check old packages installed on SSH minion
28s 957ms 4

When I refresh packages list via spacecmd on "ssh_minion" 2s 192ms

And I wait until refresh package list on "ssh_minion" is finished 21s 176ms

Then spacecmd should show packages "virgo-dummy-1.0" installed on "ssh_minion" 2s 311ms

And I wait until package "andromeda-dummy-2.0-1.1" is removed from "ssh_minion" via spacecmd 3s 276ms

Scenario:
Log in as org admin user
1s 484ms 1

Given I am authorized for the "Admin" section 1s 484ms

Scenario:
Pre-requisite: ensure the errata cache is computed before patching Salt minion
19s 12ms 11

Given I am on the Systems overview page of this "ssh_minion" 1s 278ms

When I follow "Software" in the content area 76ms

And I follow "List / Remove" in the content area 60ms

And I enter "virgo-dummy" as the filtered package name 162ms

And I click on the filter button until page does contain "virgo-dummy" text 10s 902ms

When I follow the left menu "Admin > Task Schedules" 118ms

And I follow "errata-cache-default" 1s 338ms

And I follow "errata-cache-bunch" 1s 262ms

And I click on "Single Run Schedule" 1s 513ms

Then I should see a "bunch was scheduled" text 264ms

When I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 2s 33ms

Scenario:
Install a patch on the SSH minion
42s 444ms 12

Given I am on the Systems overview page of this "ssh_minion" 817ms

When I follow "Software" in the content area 68ms

And I follow "Patches" in the content area 59ms

And I enter "virgo" as the filtered synopsis 45ms

And I click on the filter button 10s 91ms

And I check "virgo-dummy-3456" in the list 62ms

And I check "allowVendorChange" 73ms

And I click on "Apply Patches" 618ms

And I click on "Confirm" 648ms

Then I should see a "1 patch update has been scheduled for" text 80ms

When I wait for "virgo-dummy-2.0-1.1" to be installed on "ssh_minion" 29s 45ms

Then vendor change should be enabled for package actions on "ssh_minion" 830ms

Scenario:
Install a package on the SSH minion
48s 42ms 12

Given I am on the Systems overview page of this "ssh_minion" 900ms

When I follow "Software" in the content area 76ms

And I follow "Packages" 425ms

And I follow "Install" 545ms

And I enter "andromeda" as the filtered package name 95ms

And I click on the filter button 595ms

And I check "andromeda-dummy-2.0-1.1" in the list 57ms

And I click on "Install Packages" 584ms

And I click on "Confirm" 666ms

Then I should see a "1 package install has been scheduled" text 62ms

When I wait for "andromeda-dummy-2.0-1.1" to be installed on "ssh_minion" 43s 217ms

Then vendor change should be enabled for package actions on "ssh_minion" 815ms

Scenario:
Cleanup: disable test_repo_rpm_pool on SSH minion
590ms 1

When I disable repository "test_repo_rpm_pool" on this "ssh_minion" 590ms

Scenario:
Cleanup: remove virgo-dummy package from SSH minion
40s 384ms 4

When I remove package "virgo-dummy" from this "ssh_minion" without error control 1s 445ms

And I refresh the metadata for "ssh_minion" 852ms

And I refresh packages list via spacecmd on "ssh_minion" 2s 612ms

And I wait until refresh package list on "ssh_minion" is finished 35s 474ms

Scenario:
Cleanup: remove andromeda-dummy package from SSH minion
25s 525ms 4

When I remove package "andromeda-dummy" from this "ssh_minion" without error control 1s 189ms

And I refresh the metadata for "ssh_minion" 870ms

And I refresh packages list via spacecmd on "ssh_minion" 2s 221ms

And I wait until refresh package list on "ssh_minion" is finished 21s 244ms

@scope_ansible @scope_salt_ssh @ssh_minion
Feature:Operate an Ansible control node in SSH minion 4m 13s 368ms 12 2

Scenario:
Log in as org admin user
427ms 1

Given I am authorized for the "Admin" section 427ms

Scenario:
Pre-requisite: Deploy test playbooks and inventory file
2s 263ms 1

When I deploy testing playbooks and inventory files to "ssh_minion" 2s 263ms

@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 208ms 5

Given I am on the Systems overview page of this "ssh_minion" 837ms

When I follow "Properties" in the content area 67ms

And I check "ansible_control_node" 80ms

And I click on "Update Properties" 1s 134ms

Then I wait until I see "Ansible Control Node type has been applied." text 88ms

Scenario:
Apply highstate and check that Ansible is installed
1m 13s 409ms 5

Given I am on the Systems overview page of this "ssh_minion" 963ms

When I follow "States" in the content area 64ms

And I click on "Apply Highstate" 58ms

And I wait until event "Apply highstate scheduled" is completed 1m 11s 826ms

Then "ansible" should be installed on "ssh_minion" 496ms

Scenario:
The Ansible tab appears in the system overview page
987ms 3

Given I am on the Systems overview page of this "ssh_minion" 848ms

When I follow "Ansible" in the content area 78ms

Then I should see a "Ansible Control Node Configuration" text 60ms

Scenario:
Configure some inventory and playbooks path
1s 401ms 7

Given I am on the Systems overview page of this "ssh_minion" 899ms

When I follow "Ansible" in the content area 58ms

Then I should see a "Ansible Control Node Configuration" text 63ms

And I enter "/srv/playbooks/" as "new_playbook_path_input" 166ms

And I click on "new_playbook_path_save" 57ms

And I enter "/srv/playbooks/orion_dummy/hosts" as "new_inventory_path_input" 94ms

And I click on "new_inventory_path_save" 61ms

Scenario:
Display inventories
14s 358ms 6

Given I am on the Systems overview page of this "ssh_minion" 932ms

When I follow "Ansible" in the content area 61ms

And I follow "Inventories" in the content area 71ms

And I wait until I see "/srv/playbooks/orion_dummy/hosts" text 247ms

And I click on "/srv/playbooks/orion_dummy/hosts" 57ms

Then I wait until I see "myself" text 12s 988ms

Scenario:
Discover playbooks and display them
19s 286ms 6

Given I am on the Systems overview page of this "ssh_minion" 856ms

When I follow "Ansible" in the content area 73ms

And I follow "Playbooks" in the content area 65ms

And I wait until I see "/srv/playbooks" text 239ms

And I click on "/srv/playbooks" 56ms

Then I wait until I see "/srv/playbooks/orion_dummy/playbook_orion_dummy.yml" text 17s 994ms

Scenario:
Run a playbook using custom inventory
56s 895ms 13

Given I am on the Systems overview page of this "ssh_minion" 840ms

When I follow "Ansible" in the content area 79ms

And I follow "Playbooks" in the content area 64ms

And I wait until I see "/srv/playbooks" text 321ms

And I click on "/srv/playbooks" 56ms

And I wait until I see "/srv/playbooks/orion_dummy/playbook_orion_dummy.yml" text 9s 51ms

And I click on "orion_dummy/playbook_orion_dummy.yml" 61ms

And I wait until I see "Playbook Content" text 5s 783ms

And I select "/srv/playbooks/orion_dummy/hosts" from "inventory-path-select" 1s 118ms

And I click on "Schedule" 67ms

Then I should see a "Playbook execution has been scheduled" text 229ms

And I wait until event "Execute playbook 'playbook_orion_dummy.yml' scheduled" is completed 38s 486ms

And file "/tmp/file.txt" should exist on "ssh_minion" 735ms

Scenario:
Cleanup: Disable Ansible and remove test playbooks and inventory file
14s 273ms 7

Given I am on the Systems overview page of this "ssh_minion" 830ms

When I follow "Properties" in the content area 92ms

And I uncheck "ansible_control_node" 10s 89ms

And I click on "Update Properties" 1s 144ms

Then I should see a "System properties changed" text 90ms

And I remove package "orion-dummy" from this "ssh_minion" without error control 1s 605ms

And I remove "/tmp/file.txt" from "ssh_minion" 419ms

@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
11s 641ms 4

Given I am on the Systems overview page of this "ssh_minion" 801ms

When I follow "Properties" in the content area 73ms

And I uncheck "ansible_control_node" 10s 44ms

And I click on "Update Properties" 722ms

Scenario:
Cleanup: Apply highstate to disable the minion as an "Ansible control node"
56s 216ms 4

Given I am on the Systems overview page of this "ssh_minion" 909ms

When I follow "States" in the content area 68ms

And I click on "Apply Highstate" 59ms

And I wait until event "Apply highstate scheduled" is completed 55s 178ms

@scope_monitoring @scope_res @deblike_minion
Feature:Monitor MLM environment with Prometheus on a Debian-like Salt minion 1m 29s 489ms 10

In order to monitor Uyuni server
As an authorized user
I want to enable Prometheus exporters

Scenario:
Log in as org admin user
1s 646ms 1

Given I am authorized 1s 646ms

Scenario:
Apply Prometheus exporter formulas on the Debian-like minion
2s 525ms 7

Given I am on the Systems overview page of this "deblike_minion" 1s 293ms

When I follow "Formulas" in the content area 73ms

Then I should see a "Choose formulas:" text 60ms

And I should see a "Monitoring" text 264ms

When I check the "prometheus-exporters" formula 75ms

And I click on "Save" 67ms

And I wait until I see "Formula saved" text 690ms

Scenario:
Configure Prometheus exporter formula on the Debian-like minion
1s 935ms 9

When I follow "Formulas" in the content area 60ms

And I follow "Prometheus Exporters" in the content area 235ms

And I click on "Expand All Sections" 236ms

Then I should see a "Enable and configure Prometheus exporters for managed systems." text 105ms

When I check "node" exporter 43ms

And I check "apache" exporter 82ms

And I check "postgres" exporter 81ms

And I click on "Save" 63ms

Then I should see a "Formula saved" text 1s 27ms

Scenario:
Enable tools_update_repo tools_pool_repo so the exporters packages are available
1s 356ms 1

When I enable the repositories "tools_update_repo tools_pool_repo" on this "deblike_minion" without error control 1s 356ms

@skip_if_github_validation
Scenario:
Apply highstate for Prometheus exporters on the Debian-like minion
55s 637ms 4

When I follow "States" in the content area 69ms

And I click on "Apply Highstate" 56ms

Then I should see a "Applying the highstate has been scheduled." text 340ms

And I wait until event "Apply highstate scheduled" is completed 55s 170ms

@skip_if_github_validation
Scenario:
Wait for services
910ms 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" 217ms

And I wait until "postgres" exporter service is active on "deblike_minion" 213ms

Scenario:
Visit monitoring endpoints on the Debian-like minion
648ms 3

And I visit "Prometheus node exporter" endpoint of this "deblike_minion" 218ms

And I visit "Prometheus apache exporter" endpoint of this "deblike_minion" 214ms

And I visit "Prometheus postgres exporter" endpoint of this "deblike_minion" 215ms

Scenario:
Cleanup: undo Prometheus exporter formulas on the Debian-like minion
1s 468ms 4

When I follow "Formulas" in the content area 78ms

And I uncheck the "prometheus-exporters" formula 249ms

And I click on "Save" 65ms

Then I wait until I see "Formula saved" text 1s 74ms

@skip_if_github_validation
Scenario:
Cleanup: apply highstate after test monitoring on the Debian-like minion
22s 373ms 4

When I follow "States" in the content area 65ms

And I click on "Apply Highstate" 56ms

Then I should see a "Applying the highstate has been scheduled." text 407ms

And I wait until event "Apply highstate scheduled" is completed 21s 843ms

Scenario:
Cleanup: Disable tools_update_repo tools_pool_repo because they are no longer needed
988ms 1

When I disable the repositories "tools_update_repo tools_pool_repo" on this "deblike_minion" without error control 988ms

@deblike_minion @scope_deblike @scope_content_staging
Feature:Install a package on the Debian-like minion with staging enabled 3m 44s 235ms 7 1

Scenario:
Pre-requisite: install virgo-dummy-1.0 package, make sure orion-dummy is not present on Debian-like minion
1s 605ms 4

When I enable repository "test_repo_deb_pool" on this "deblike_minion" 218ms

And I run "apt update" on "deblike_minion" 859ms

And I remove package "orion-dummy" from this "deblike_minion" 244ms

And I install old package "virgo-dummy=1.0" on this "deblike_minion" 282ms

Scenario:
Pre-requisite: refresh package list on Debian-like minion
11s 787ms 3

When I refresh packages list via spacecmd on "deblike_minion" 2s 519ms

And I wait until refresh package list on "deblike_minion" is finished 6s 990ms

Then spacecmd should show packages "virgo-dummy-1.0" installed on "deblike_minion" 2s 276ms

Scenario:
Log in as admin user
1s 834ms 1

Given I am authorized for the "Admin" section 1s 834ms

Scenario:
Pre-requisite: ensure the errata cache is computed for Debian-like minion
6s 558ms 6

When I follow the left menu "Admin > Task Schedules" 122ms

And I follow "errata-cache-default" 1s 368ms

And I follow "errata-cache-bunch" 1s 271ms

Then I click on "Single Run Schedule" 1s 512ms

And I should see a "bunch was scheduled" text 269ms

Then I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 2s 13ms

Scenario:
Enable content staging for Debian-like minion
1s 148ms 6

When I follow the left menu "Admin > Organizations" 67ms

And I follow first "SUSE Test" 277ms

And I follow first "Configuration" 293ms

And I check "staging_content_enabled" 39ms

And I click on "Update Organization" 409ms

Then I should see a "was successfully updated." text 61ms

Scenario:
Install package in the future and check for staging on Debian-like minion
2m 55s 337ms 13

Given I am on the Systems overview page of this "deblike_minion" 813ms

And I follow "Software" in the content area 70ms

And I follow "Packages" in the content area 61ms

And I follow "Install" in the content area 64ms

And I enter "orion-dummy-1.1-X" as the filtered package name 54ms

And I click on the filter button 499ms

When I check "orion-dummy-1.1-X" in the list 58ms

And I click on "Install Packages" 585ms

And I pick 3 minutes from now as schedule time 90ms

And I click on "Confirm" 668ms

Then I should see a "1 package install has been scheduled for" text 77ms

And I wait until the package "orion-dummy_1.1" has been cached on this "deblike_minion" 54s 416ms

And I wait for "orion-dummy-1.1" to be installed on "deblike_minion" 1m 57s 877ms

Scenario:
Install patch in the future and check for staging on Debian-like minion
23s 760ms 3 8 1

When I follow "Software" in the content area 86ms

And I follow "Patches" in the content area 94ms

And I enter "virgo" as the filtered synopsis 10s 4ms Show Error + 
                                            
 Unable to find css "input[placeholder='Filter by Synopsis: ']" (Capybara::ElementNotFound)
./features/step_definitions/navigation_steps.rb:935: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

13s 576ms Show Info + 
15:35:07:000 - 15:35:18:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/ErrataList.do?sid=1000010009&
Screenshot +

Scenario:
Cleanup: remove virgo-dummy and orion-dummy packages from Debian-like minion
2s 203ms 4

And I remove package "orion-dummy" from this "deblike_minion" 614ms

And I remove package "virgo-dummy" from this "deblike_minion" 358ms

And I disable repository "test_repo_deb_pool" on this "deblike_minion" 208ms

And I run "apt update" on "deblike_minion" 1s 21ms

@scope_deblike @scope_salt @deblike_minion
Feature:Install and upgrade package on the Debian-like minion via Salt through the UI 1m 28s 113ms 9 1 1

Scenario:
Pre-requisite: enable test_repo_deb_pool repository on the Debian-like minion
211ms 1

When I enable repository "test_repo_deb_pool" on this "deblike_minion" 211ms

Scenario:
Pre-requisite: install virgo-dummy-1.0 package on Debian-like minion
2s 917ms 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 (6,225 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 903ms

And I install old package "virgo-dummy=1.0" on this "deblike_minion" 2s 13ms

Scenario:
Pre-requisite: remove andromeda-dummy package from Debian-like minion
357ms 1

When I remove package "andromeda-dummy" from this "deblike_minion" 357ms

Scenario:
Log in as org admin user
1s 713ms 1

Given I am authorized 1s 713ms

Scenario:
Pre-requisite: refresh package list and check newly installed packages on Debian-like minion
32s 385ms 7

Given I am on the Systems overview page of this "deblike_minion" 1s 431ms

When I follow "Software" in the content area 76ms

And I click on "Update Package List" 577ms

And I follow "Events" in the content area 68ms

And I wait until I do not see "Package List Refresh scheduled" text, refreshing the page 24s 242ms

And I wait until package "virgo-dummy" is installed on "deblike_minion" via spacecmd 2s 626ms

And I wait until package "andromeda-dummy" is removed from "deblike_minion" via spacecmd 3s 362ms

Scenario:
Install a patch on the Debian-like minion
23s 659ms 3 4 1

When I follow "Software" in the content area 74ms

And I follow "Patches" in the content area 62ms

When I check "3456-1" in the list 10s 12ms 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:1007: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

13s 510ms Show Info + 
15:36:15:000 - 15:36:26:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/ErrataList.do?sid=1000010009&
Screenshot +

@susemanager
Scenario:
Install a package on the Debian-like minion
< 1ms 8

When I follow "Software" in the content area 0s

And I follow "Install" 0s

And I check "andromeda-dummy-2.0" in the list 0s

And I click on "Install Packages" 0s

And I click on "Confirm" 0s

And I should see a "1 package install has been scheduled for" text 0s

When I wait until event "Package Install/Upgrade scheduled" is completed 0s

Then Deb package "andromeda-dummy" with version "2.0" should be installed on "deblike_minion" 0s

@uyuni
Scenario:
Install a package on the Debian-like minion
24s 883ms 8

When I follow "Software" in the content area 75ms

And I follow "Install" 495ms

And I check "andromeda-dummy-2.0" in the list 58ms

And I click on "Install Packages" 649ms

And I click on "Confirm" 653ms

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 21s 918ms

Then Deb package "andromeda-dummy" with version "2.0" should be installed on "deblike_minion" 970ms

Scenario:
Cleanup: disable test_repo_deb_pool on Debian-like minion
215ms 1

When I disable repository "test_repo_deb_pool" on this "deblike_minion" 215ms

Scenario:
Cleanup: remove virgo-dummy package from Debian-like minion
360ms 1

When I remove package "virgo-dummy" from this "deblike_minion" 360ms

Scenario:
Cleanup: remove andromeda-dummy package from Debian-like minion
1s 407ms 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" 350ms

And I run "apt update" on "deblike_minion" with logging 1s 57ms

@skip_if_github_validation @sle_minion @scope_onboarding
Feature:Negative tests for bootstrapping normal minions 21s 475ms 5

In order to register only valid minions
As an authorized user
I want to avoid registration with invalid input parameters

Scenario:
Log in as org admin user
1s 677ms 1

Given I am authorized 1s 677ms

Scenario:
Bootstrap should fail when minion already exists
949ms 10

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 125ms

Then I should see a "Bootstrap Minions" text 81ms

When I enter the hostname of "sle_minion" as "hostname" 130ms

And I enter "22" as "port" 49ms

And I enter "root" as "user" 54ms

And I enter "linux" as "password" 53ms

And I click on "Bootstrap" 64ms

And I wait until I see "A salt key for this host" text 264ms

Then I should not see a "GenericSaltError" text 64ms

And I should see a "seems to already exist, please check!" text 60ms

Scenario:
Bootstrap a SLES minion with wrong hostname
2s 954ms 14

When I follow the left menu "Systems > Bootstrapping" 64ms

Then I should see a "Bootstrap Minions" text 63ms

When I enter "not-existing-name" as "hostname" 80ms

And I enter "22" as "port" 58ms

And I enter "root" as "user" 50ms

And I enter "linux" as "password" 53ms

And I click on "Bootstrap" 54ms

And I wait until I see "An error has occurred during salt execution: unable to establish ssh connection." text 2s 291ms

Then I should see a "Details" button 16ms

When I click on "Details" 68ms

And I wait at most 10 seconds until I see modal containing "Error Details" text 10ms

Then I should see a "Standard Error" text 69ms

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 56ms

Scenario:
Bootstrap a SLES minion with wrong SSH credentials
13s 8ms 14

The hostname of localhost is uyuni-master-controller.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 59ms

Then I should see a "Bootstrap Minions" text 62ms

When I enter the hostname of "localhost" as "hostname" 116ms

And I enter "22" as "port" 45ms

And I enter "FRANZ" as "user" 54ms

And I enter "KAFKA" as "password" 54ms

And I click on "Bootstrap" 54ms

And I wait until I see "An error has occurred during salt execution: unable to establish ssh connection." text 12s 357ms

Then I should see a "Details" button 14ms

When I click on "Details" 57ms

And I wait at most 10 seconds until I see modal containing "Error Details" text 7ms

Then I should see a "Standard Error" text 69ms

And I should see "Permission denied (publickey" or "Password authentication failed" in the stderr textarea 12ms

When I close the modal dialog 43ms

Scenario:
Bootstrap a SLES minion with wrong SSH port number
2s 885ms 14

The hostname of localhost is uyuni-master-controller.sumaci.aws

When I follow the left menu "Systems > Bootstrapping" 57ms

Then I should see a "Bootstrap Minions" text 64ms

When I enter the hostname of "localhost" as "hostname" 115ms

And I enter "11" as "port" 44ms

And I enter "root" as "user" 50ms

And I enter "linux" as "password" 52ms

And I click on "Bootstrap" 52ms

And I wait until I see "An error has occurred during salt execution: unable to establish ssh connection." text 2s 242ms

Then I should see a "Details" button 13ms

When I click on "Details" 57ms

And I wait at most 10 seconds until I see modal containing "Error Details" text 7ms

Then I should see a "Standard Error" text 68ms

And I should see "port 11: Connection refused" or "port 11: Network is unreachable" in the stderr textarea 12ms

When I close the modal dialog 45ms

@skip_if_github_validation @scope_formulas @new_issue
Feature:Use salt formulas 4m 4s 95ms 20 2

In order to use simple forms to apply changes to minions
As an authorized user
I want to be able to install and use salt formulas

Scenario:
Log in as org admin user
1s 593ms 1

Given I am authorized 1s 593ms

@skip_if_containerized_server
Scenario:
Install the locale formula package on the server
< 1ms 1

When I manually install the "locale" formula on the server 0s

Scenario:
I synchronize all Salt dynamic modules on "sle_minion"
3s 182ms 1

When I synchronize all Salt dynamic modules on "sle_minion" 3s 182ms

Scenario:
The new formula appears on the server
251ms 2

When I follow the left menu "Salt > Formula Catalog" 124ms

Then I should see a "locale" text in the content area 127ms

Scenario:
Enable the formula on the minion
12s 85ms 9

Given I am on the Systems overview page of this "sle_minion" 824ms

When I follow "Formulas" in the content area 70ms

Then I should see a "Choose formulas:" text 59ms

And I should see a "General System Configuration" text 180ms

And I should see a "Locale" text 87ms

When I check the "locale" formula 84ms

And I click on "Save" 63ms

And I wait until I see "Formula saved." text 684ms

Then the "locale" formula should be checked 10s 30ms

Scenario:
Parametrize the formula on the minion
1s 413ms 8

When I follow "Formulas" in the content area 58ms

And I follow first "Locale" in the content area 222ms

And I click on "Expand All Sections" 231ms

And I select "Etc/GMT-5" in timezone name field 62ms

And I select "French" in language field 46ms

And I select "French (Canada)" in keyboard layout field 41ms

And I click on "Save Formula" 59ms

Then I should see a "Formula saved" text 690ms

Scenario:
Check the pillar data after saving the formula
8s 720ms 5

When I refresh the pillar data 2s 459ms

Then the pillar data for "formulas" should be "- locale" on "sle_minion" 1s 572ms

And the pillar data for "timezone:name" should be "Etc/GMT-5" on "sle_minion" 1s 581ms

And the pillar data for "keyboard_and_language:keyboard_layout" should be "French (Canada)" on "sle_minion" 1s 556ms

And the pillar data for "keyboard_and_language:language" should be "French" on "sle_minion" 1s 551ms

@ssh_minion
Scenario:
No other minion is affected by the formula
21s 611ms 3

Then the pillar data for "formulas" should be empty on "ssh_minion" 7s 744ms

And the pillar data for "timezone" should be empty on "ssh_minion" 6s 965ms

And the pillar data for "keyboard_and_language" should be empty on "ssh_minion" 6s 902ms

Scenario:
Use the parametrized formula in test mode
23s 560ms 7

Given I am on the Systems overview page of this "sle_minion" 874ms

And I follow "States" in the content area 67ms

Then I should see the toggler "disabled" 11ms

When I click on the "disabled" toggler 45ms

And I click on "Apply Highstate" 60ms

Then I should see a "Applying the highstate has been scheduled." text 325ms

And I wait at most 300 seconds until event "Apply highstate in test-mode scheduled" is completed 22s 175ms

Scenario:
Apply the parametrized formula via the highstate
42s 377ms 9

When I enable repository "sle_update_repo" on this "sle_minion" without error control 828ms

And I follow "States" in the content area 60ms

And I click on "Apply Highstate" 52ms

Then I should see a "Applying the highstate has been scheduled." text 315ms

When I wait until event "Apply highstate scheduled" is completed 38s 631ms

Then the timezone on "sle_minion" should be "+05" 749ms

And the keymap on "sle_minion" should be "ca" 441ms

And the language on "sle_minion" should be "fr_FR.UTF-8" 833ms

And I disable repository "sle_update_repo" on this "sle_minion" without error control 465ms

Scenario:
Reset the formula on the minion
1s 206ms 5

When I follow "Formulas" in the content area 76ms

And I follow first "Locale" in the content area 238ms

And I click on "Clear values" and confirm alert box 247ms

And I click on "Save Formula" 64ms

Then I should see a "Formula saved" text 579ms

Scenario:
Check the pillar data after resetting the formula
8s 674ms 5

When I refresh the pillar data 2s 455ms

Then the pillar data for "formulas" should be "- locale" on "sle_minion" 1s 564ms

And the pillar data for "timezone:name" should be "CET" on "sle_minion" 1s 552ms

And the pillar data for "keyboard_and_language:keyboard_layout" should be "English (US)" on "sle_minion" 1s 544ms

And the pillar data for "keyboard_and_language:language" should be "English (US)" on "sle_minion" 1s 557ms

Scenario:
Apply the reset formula via the highstate
41s 53ms 7

And I follow "States" in the content area 68ms

And I click on "Apply Highstate" 59ms

Then I should see a "Applying the highstate has been scheduled." text 334ms

When I wait until event "Apply highstate scheduled" is completed 38s 575ms

Then the timezone on "sle_minion" should be "CET" 743ms

And the keymap on "sle_minion" should be "us" 415ms

And the language on "sle_minion" should be "en_US.UTF-8" 856ms

Scenario:
Disable the formula on the minion
11s 286ms 8

When I follow "Formulas" in the content area 79ms

Then I should see a "Choose formulas:" text 66ms

And I should see a "General System Configuration" text 177ms

And I should see a "Locale" text 91ms

When I uncheck the "locale" formula 73ms

And I click on "Save" 61ms

And I wait until I see "Formula saved." text 707ms

Then the "locale" formula should be unchecked 10s 29ms

Scenario:
Check the pillar data after disabling the formula
7s 6ms 4

When I refresh the pillar data 2s 351ms

Then the pillar data for "formulas" should be empty on "sle_minion" 1s 544ms

And the pillar data for "timezone" should be empty on "sle_minion" 1s 556ms

And the pillar data for "keyboard_and_language" should be empty on "sle_minion" 1s 555ms

Scenario:
Assign locale formula to minion via group formula
3s 562ms 17

When I follow the left menu "Systems > System Groups" 71ms

When I follow "Create Group" 267ms

And I enter "locale-formula-group" as "name" 83ms

And I enter "Test group with locale formula added" as "description" 73ms

And I click on "Create Group" 58ms

Then I should see a "System group locale-formula-group created." text 485ms

When I follow "Formulas" in the content area 69ms

Then I should see a "Choose formulas:" text 59ms

And I should see a "General System Configuration" text 180ms

And I should see a "Locale" text 88ms

When I check the "locale" formula 70ms

And I click on "Save" 62ms

And I wait until I see "Formula saved." text 448ms

And I follow "Target" 417ms

And I check the "sle_minion" client 60ms

And I click on "Add Systems" 964ms

Then I should see a "1 systems were added to locale-formula-group server group." text 101ms

Scenario:
Check the pillar data after assigning group formula
8s 423ms 5

When I refresh the pillar data 2s 199ms

Then the pillar data for "formulas" should be "- locale" on "sle_minion" 1s 544ms

And the pillar data for "timezone:name" should be "CET" on "sle_minion" 1s 543ms

And the pillar data for "keyboard_and_language:keyboard_layout" should be "English (US)" on "sle_minion" 1s 585ms

And the pillar data for "keyboard_and_language:language" should be "English (US)" on "sle_minion" 1s 549ms

@ssh_minion
Scenario:
No other minion is affected by the group formula
21s 199ms 3

Then the pillar data for "formulas" should be empty on "ssh_minion" 7s 340ms

And the pillar data for "timezone" should be empty on "ssh_minion" 6s 884ms

And the pillar data for "keyboard_and_language" should be empty on "ssh_minion" 6s 975ms

Scenario:
Cleanup: remove "locale-formula-group" system group
1s 484ms 7

When I follow the left menu "Systems > System Groups" 78ms

And I follow "locale-formula-group" in the content area 86ms

And I follow "Delete Group" in the content area 67ms

When I click on "Confirm Deletion" 1s 66ms

Then I should see a "System group" text 59ms

And I should see a "locale-formula-group" text 58ms

And I should see a "deleted" text 68ms

Scenario:
Cleanup: reset locale values on the minion
25s 331ms 8

Given I am on the Systems overview page of this "sle_minion" 944ms

And I follow "States" in the content area 77ms

And I click on "Apply Highstate" 64ms

Then I should see a "Applying the highstate has been scheduled." text 325ms

When I wait until event "Apply highstate scheduled" is completed 21s 927ms

Then the timezone on "sle_minion" should be "CET" 734ms

And the keymap on "sle_minion" should be "us" 419ms

And the language on "sle_minion" should be "en_US.UTF-8" 837ms

@skip_if_containerized_server
Scenario:
Cleanup: uninstall formula package from the server
< 1ms 1

When I manually uninstall the "locale" formula from the server 0s

Scenario:
Cleanup: remove remaining systems from SSM after formula tests
67ms 1

When I click on the clear SSM button 67ms

@flaky @scope_formulas
Feature:Use advanced features of Salt formulas 3m 27s 694ms 12

In order to use forms to apply changes to minions
As an authorized user
I want to be able to install and use Salt formulas

Scenario:
Log in as org admin user
1s 690ms 1

Given I am authorized 1s 690ms

Scenario:
Install a test formula package on the server
5s 732ms 5

When I install "form.yml" to custom formula metadata directory "testform" 3s 32ms

And I install "metadata.yml" to custom formula metadata directory "testform" 2s 415ms

When I follow the left menu "Salt > Formula Catalog" 137ms

And I enter "testform" as the filtered formula name 78ms

Then I should see a "testform" text 68ms

Scenario:
Assign test formula to minion via group formula
3s 597ms 17

When I follow the left menu "Systems > System Groups" 126ms

When I follow "Create Group" 274ms

And I enter "test-formula-group" as "name" 69ms

And I enter "Test group with testform formula added" as "description" 82ms

And I click on "Create Group" 455ms

Then I should see a "System group test-formula-group created." text 65ms

When I follow "Formulas" in the content area 80ms

Then I should see a "Choose formulas:" text 57ms

And I should see a "General System Configuration" text 108ms

And I should see a "Testform" text 89ms

When I check the "testform" formula 81ms

And I click on "Save" 67ms

And I wait until I see "Formula saved." text 482ms

And I follow "Target Systems" 421ms

And I check the "sle_minion" client 64ms

And I click on "Add Systems" 970ms

Then I should see a "1 systems were added to test-formula-group server group." text 98ms

Scenario:
Verify default values
39s 640ms 25

When I refresh the pillar data 2s 130ms

Then the pillar data for "testing:str" should be "" on "sle_minion" 1s 548ms

And the pillar data for "testing:str_def" should be "defvalue" on "sle_minion" 1s 555ms

And the pillar data for "testing:str_or_null" should be "None" on "sle_minion" 1s 556ms

And the pillar data for "testing" should not contain "str_opt" on "sle_minion" 1s 563ms

And the pillar data for "testing:num" should be "" on "sle_minion" 1s 571ms

And the pillar data for "testing:num_def" should be "0" on "sle_minion" 1s 554ms

And the pillar data for "testing:num_or_null" should be "None" on "sle_minion" 1s 555ms

And the pillar data for "testing" should not contain "num_opt" on "sle_minion" 1s 561ms

And the pillar data for "testing:pw" should be "" on "sle_minion" 1s 566ms

And the pillar data for "testing:pw_or_null" should be "None" on "sle_minion" 1s 576ms

And the pillar data for "testing" should not contain "pw_opt" on "sle_minion" 1s 550ms

And the pillar data for "testing:list_of_strings" should contain "def_item1" on "sle_minion" 1s 593ms

And the pillar data for "testing:list_of_strings" should contain "def_item2" on "sle_minion" 1s 552ms

And the pillar data for "testing:dict_of_strings:name1" should be "def_value1" on "sle_minion" 1s 556ms

And the pillar data for "testing:dict_of_strings:name2" should be "def_value2" on "sle_minion" 1s 547ms

And the pillar data for "testing:list_of_dicts:0:name" should be "def_user" on "sle_minion" 1s 570ms

And the pillar data for "testing:list_of_dicts:0:password" should be "secret1" on "sle_minion" 1s 562ms

And the pillar data for "testing:list_of_dicts:0" should not contain "full_name" on "sle_minion" 1s 599ms

And the pillar data for "testing:dict_of_dicts:def_user:name" should be "root" on "sle_minion" 1s 589ms

And the pillar data for "testing:dict_of_dicts:def_user:password" should be "secret2" on "sle_minion" 1s 562ms

And the pillar data for "testing:dict_of_dicts:def_user:full_name" should be "None" on "sle_minion" 1s 554ms

And the pillar data for "testing:recursive_dict_of_dicts:def_gr1:group_name" should be "default group 1" on "sle_minion" 1s 555ms

And the pillar data for "testing:recursive_dict_of_dicts:def_gr1:entries:def_entry1:entry_name" should be "default entry 1" on "sle_minion" 1s 562ms

And the pillar data for "testing:recursive_dict_of_dicts:def_gr1:entries:def_entry1:entry_desc" should be "some text" on "sle_minion" 1s 542ms

Scenario:
Fill in and verify non-default values in group formula
20s 704ms 30

When I follow the left menu "Systems > System Groups" 64ms

When I follow "test-formula-group" in the content area 79ms

And I follow "Formulas" in the content area 69ms

And I follow first "Testform" in the content area 233ms

And I click on "Expand All Sections" 245ms

And I enter "text1" as "testing#str" 120ms

And I enter "text2" as "testing#str_def" 142ms

And I enter "text3" as "testing#str_or_null" 88ms

And I enter "text4" as "testing#str_opt" 98ms

And I enter "1" as "testing#num" 63ms

And I enter "2" as "testing#num_def" 72ms

And I enter "3" as "testing#num_or_null" 82ms

And I enter "4" as "testing#num_opt" 65ms

And I enter "pw1" as "testing#pw" 100ms

And I enter "pw2" as "testing#pw_or_null" 94ms

And I enter "pw3" as "testing#pw_opt" 84ms

And I click on "Save Formula" 105ms

Then I should see a "Formula saved" text 732ms

When I wait for "1" seconds 1s

Then the pillar data for "testing:str" should be "text1" on "sle_minion" 1s 548ms

And the pillar data for "testing:str_def" should be "text2" on "sle_minion" 1s 571ms

And the pillar data for "testing:str_or_null" should be "text3" on "sle_minion" 1s 549ms

And the pillar data for "testing:str_opt" should be "text4" on "sle_minion" 1s 554ms

And the pillar data for "testing:num" should be "1" on "sle_minion" 1s 548ms

And the pillar data for "testing:num_def" should be "2" on "sle_minion" 1s 571ms

And the pillar data for "testing:num_or_null" should be "3" on "sle_minion" 1s 558ms

And the pillar data for "testing:num_opt" should be "4" on "sle_minion" 1s 559ms

And the pillar data for "testing:pw" should be "pw1" on "sle_minion" 1s 570ms

And the pillar data for "testing:pw_or_null" should be "pw2" on "sle_minion" 1s 565ms

And the pillar data for "testing:pw_opt" should be "pw3" on "sle_minion" 1s 562ms

Scenario:
Clear values in group formula and verify the defaults again
40s 21ms 32

When I follow the left menu "Systems > System Groups" 84ms

When I follow "test-formula-group" in the content area 70ms

And I follow "Formulas" in the content area 74ms

And I follow first "Testform" in the content area 239ms

And I click on "Clear values" and confirm alert box 317ms

And I click on "Save Formula" 64ms

Then I should see a "Formula saved" text 643ms

When I wait for "1" seconds 1s

Then the pillar data for "testing:str" should be "" on "sle_minion" 1s 563ms

And the pillar data for "testing:str_def" should be "defvalue" on "sle_minion" 1s 556ms

And the pillar data for "testing:str_or_null" should be "None" on "sle_minion" 1s 548ms

And the pillar data for "testing" should not contain "str_opt" on "sle_minion" 1s 548ms

And the pillar data for "testing:num" should be "" on "sle_minion" 1s 545ms

And the pillar data for "testing:num_def" should be "0" on "sle_minion" 1s 598ms

And the pillar data for "testing:num_or_null" should be "None" on "sle_minion" 1s 560ms

And the pillar data for "testing" should not contain "num_opt" on "sle_minion" 1s 557ms

And the pillar data for "testing:pw" should be "" on "sle_minion" 1s 547ms

And the pillar data for "testing:pw_or_null" should be "None" on "sle_minion" 1s 572ms

And the pillar data for "testing" should not contain "pw_opt" on "sle_minion" 1s 568ms

And the pillar data for "testing:list_of_strings" should contain "def_item1" on "sle_minion" 1s 565ms

And the pillar data for "testing:list_of_strings" should contain "def_item2" on "sle_minion" 1s 594ms

And the pillar data for "testing:dict_of_strings:name1" should be "def_value1" on "sle_minion" 1s 555ms

And the pillar data for "testing:dict_of_strings:name2" should be "def_value2" on "sle_minion" 1s 549ms

And the pillar data for "testing:list_of_dicts:0:name" should be "def_user" on "sle_minion" 1s 551ms

And the pillar data for "testing:list_of_dicts:0:password" should be "secret1" on "sle_minion" 1s 604ms

And the pillar data for "testing:list_of_dicts:0" should not contain "full_name" on "sle_minion" 1s 589ms

And the pillar data for "testing:dict_of_dicts:def_user:name" should be "root" on "sle_minion" 1s 555ms

And the pillar data for "testing:dict_of_dicts:def_user:password" should be "secret2" on "sle_minion" 1s 571ms

And the pillar data for "testing:dict_of_dicts:def_user:full_name" should be "None" on "sle_minion" 1s 566ms

And the pillar data for "testing:recursive_dict_of_dicts:def_gr1:group_name" should be "default group 1" on "sle_minion" 1s 544ms

And the pillar data for "testing:recursive_dict_of_dicts:def_gr1:entries:def_entry1:entry_name" should be "default entry 1" on "sle_minion" 1s 559ms

And the pillar data for "testing:recursive_dict_of_dicts:def_gr1:entries:def_entry1:entry_desc" should be "some text" on "sle_minion" 1s 549ms

Scenario:
Fill in and verify mix of default and non-default values in group formula
19s 997ms 23

When I follow the left menu "Systems > System Groups" 71ms

When I follow "test-formula-group" in the content area 57ms

And I follow "Formulas" in the content area 62ms

And I follow first "Testform" in the content area 252ms

And I click on "Expand All Sections" 226ms

And I enter "text1" as "testing#str" 122ms

And I enter "1" as "testing#num" 57ms

And I enter "2" as "testing#num_def" 89ms

And I enter "pw1" as "testing#pw" 78ms

And I click on "Save Formula" 85ms

Then I should see a "Formula saved" text 717ms

When I wait for "1" seconds 1s

Then the pillar data for "testing:str" should be "text1" on "sle_minion" 1s 546ms

And the pillar data for "testing:str_def" should be "defvalue" on "sle_minion" 1s 564ms

And the pillar data for "testing:str_or_null" should be "None" on "sle_minion" 1s 566ms

And the pillar data for "testing" should not contain "str_opt" on "sle_minion" 1s 557ms

And the pillar data for "testing:num" should be "1" on "sle_minion" 1s 563ms

And the pillar data for "testing:num_def" should be "2" on "sle_minion" 1s 561ms

And the pillar data for "testing:num_or_null" should be "None" on "sle_minion" 1s 592ms

And the pillar data for "testing" should not contain "num_opt" on "sle_minion" 1s 563ms

And the pillar data for "testing:pw" should be "pw1" on "sle_minion" 1s 545ms

And the pillar data for "testing:pw_or_null" should be "None" on "sle_minion" 1s 557ms

And the pillar data for "testing" should not contain "pw_opt" on "sle_minion" 1s 557ms

Scenario:
Verify that minion form inherits the values from group form
19s 172ms 16

Given I am on the Systems overview page of this "sle_minion" 864ms

When I follow "Formulas" in the content area 73ms

And I follow first "Testform" in the content area 236ms

And I click on "Save Formula" 204ms

Then I should see a "Formula saved" text 615ms

And the pillar data for "testing:str" should be "text1" on "sle_minion" 1s 612ms

And the pillar data for "testing:str_def" should be "defvalue" on "sle_minion" 1s 541ms

And the pillar data for "testing:str_or_null" should be "None" on "sle_minion" 1s 552ms

And the pillar data for "testing" should not contain "str_opt" on "sle_minion" 1s 553ms

And the pillar data for "testing:num" should be "1" on "sle_minion" 1s 542ms

And the pillar data for "testing:num_def" should be "2" on "sle_minion" 1s 556ms

And the pillar data for "testing:num_or_null" should be "None" on "sle_minion" 1s 562ms

And the pillar data for "testing" should not contain "num_opt" on "sle_minion" 1s 558ms

And the pillar data for "testing:pw" should be "pw1" on "sle_minion" 1s 565ms

And the pillar data for "testing:pw_or_null" should be "None" on "sle_minion" 1s 547ms

And the pillar data for "testing" should not contain "pw_opt" on "sle_minion" 1s 586ms

Scenario:
Fill in and verify non-default values in minion formula
20s 565ms 28

When I follow "Formulas" in the content area 59ms

And I follow first "Testform" in the content area 228ms

And I click on "Expand All Sections" 206ms

And I enter "min_text1" as "testing#str" 160ms

And I enter "min_text2" as "testing#str_def" 163ms

And I enter "min_text3" as "testing#str_or_null" 100ms

And I enter "min_text4" as "testing#str_opt" 98ms

And I enter "101" as "testing#num" 75ms

And I enter "102" as "testing#num_def" 75ms

And I enter "103" as "testing#num_or_null" 68ms

And I enter "104" as "testing#num_opt" 68ms

And I enter "min_pw1" as "testing#pw" 116ms

And I enter "min_pw2" as "testing#pw_or_null" 109ms

And I enter "min_pw3" as "testing#pw_opt" 91ms

And I click on "Save Formula" 70ms

Then I should see a "Formula saved" text 681ms

When I wait for "1" seconds 1s

Then the pillar data for "testing:str" should be "min_text1" on "sle_minion" 1s 562ms

And the pillar data for "testing:str_def" should be "min_text2" on "sle_minion" 1s 556ms

And the pillar data for "testing:str_or_null" should be "min_text3" on "sle_minion" 1s 565ms

And the pillar data for "testing:str_opt" should be "min_text4" on "sle_minion" 1s 597ms

And the pillar data for "testing:num" should be "101" on "sle_minion" 1s 581ms

And the pillar data for "testing:num_def" should be "102" on "sle_minion" 1s 551ms

And the pillar data for "testing:num_or_null" should be "103" on "sle_minion" 1s 562ms

And the pillar data for "testing:num_opt" should be "104" on "sle_minion" 1s 564ms

And the pillar data for "testing:pw" should be "min_pw1" on "sle_minion" 1s 548ms

And the pillar data for "testing:pw_or_null" should be "min_pw2" on "sle_minion" 1s 554ms

And the pillar data for "testing:pw_opt" should be "min_pw3" on "sle_minion" 1s 546ms

Scenario:
Clear values in minion formula and verify that the pillar is set to group values
19s 337ms 17

When I follow "Formulas" in the content area 79ms

And I follow first "Testform" in the content area 206ms

And I click on "Clear values" and confirm alert box 274ms

And I click on "Save Formula" 57ms

Then I should see a "Formula saved" text 545ms

When I wait for "1" seconds 1s

Then the pillar data for "testing:str" should be "text1" on "sle_minion" 1s 557ms

And the pillar data for "testing:str_def" should be "defvalue" on "sle_minion" 1s 564ms

And the pillar data for "testing:str_or_null" should be "None" on "sle_minion" 1s 548ms

And the pillar data for "testing" should not contain "str_opt" on "sle_minion" 1s 559ms

And the pillar data for "testing:num" should be "1" on "sle_minion" 1s 562ms

And the pillar data for "testing:num_def" should be "2" on "sle_minion" 1s 570ms

And the pillar data for "testing:num_or_null" should be "None" on "sle_minion" 1s 552ms

And the pillar data for "testing" should not contain "num_opt" on "sle_minion" 1s 556ms

And the pillar data for "testing:pw" should be "pw1" on "sle_minion" 1s 580ms

And the pillar data for "testing:pw_or_null" should be "None" on "sle_minion" 1s 555ms

And the pillar data for "testing" should not contain "pw_opt" on "sle_minion" 1s 565ms

Scenario:
Cleanup: remove formula from minion
10s 892ms 5

When I follow "Formulas" in the content area 59ms

And I uncheck the "testform" formula 143ms

And I click on "Save" 59ms

And I wait until I see "Formula saved." text 598ms

Then the "testform" formula should be unchecked 10s 31ms

Scenario:
Cleanup: remove "test-formula-group" system group
6s 341ms 9

When I follow the left menu "Systems > System Groups" 74ms

And I follow "test-formula-group" in the content area 73ms

And I follow "Delete Group" in the content area 64ms

When I click on "Confirm Deletion" 1s 57ms

Then I should see a "System group" text 59ms

Then I should see a "test-formula-group" text 53ms

And I should see a "deleted" text 52ms

And I wait until there is no pillar refresh salt job active 3s 328ms

Then the pillar data for "testing" should be empty on "sle_minion" 1s 577ms

@skip_if_github_validation @scope_openscap @test_issue
Feature:OpenSCAP audit of Salt minion 1m 19s 336ms 5 7 3

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 862ms 2

Given I am authorized for the "Admin" section 1s 515ms

And I am on the Systems overview page of this "sle_minion" 1s 347ms

@Uyuni
Scenario:
Enable required repositories
794ms 1

When I enable repository "os_pool_repo" on this "sle_minion" without error control 794ms

Scenario:
Install the OpenSCAP packages on the SLE minion
15s 104ms 2 3 1

When I refresh the metadata for "sle_minion" 852ms

And I install OpenSCAP dependencies on "sle_minion" 683ms Show Error + 
                                            
 FAIL: zypper --non-interactive install -y openscap-utils openscap-content scap-security-guide returned status code = 104.
Output:
Loading repository data...
Reading installed packages...
'openscap-content' not found in package names. Trying capabilities.
'openscap-utils' not found in package names. Trying capabilities.
'scap-security-guide' not found in package names. Trying capabilities.
 (ScriptError)
./features/support/remote_node.rb:169:in `run_local'
./features/support/remote_node.rb:117:in `run'
./features/step_definitions/command_steps.rb:993:in `/^I install packages? "([^"]*)" on this "([^"]*)"((?: without error control)?)$/'
./features/step_definitions/command_steps.rb:971:in `/^I (install|remove) OpenSCAP dependencies (on|from) "([^"]*)"$/'
features/secondary/min_salt_openscap_audit.feature:23: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

13s 567ms Show Info + 
15:45:33:000 - 15:45:34: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 257ms 3 5 1

When I follow "Audit" in the content area 69ms

And I follow "OpenSCAP" in the content area 61ms

And I follow "Schedule" in the content area 62ms

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 62ms Show Error + 
                                            
 execution expired (Timeout::Error)
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/step_definitions/navigation_steps.rb:69:in `/^I wait at most (\d+) seconds until I do not see "([^"]*)" text, refreshing the page$/'
features/secondary/min_salt_openscap_audit.feature:45: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
55ms 8 1

When I follow "Audit" in the content area 55ms Show Error + 
                                            
 undefined method `map' for true (NoMethodError)
./features/support/commonlib.rb:198:in `click_link_and_wait'
./features/step_definitions/navigation_steps.rb:339:in `/^I follow "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:361:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:360:in `/^I follow "([^"]*)" in the (.+)$/'
features/secondary/min_salt_openscap_audit.feature:66:in `I follow "Audit" in the content area'

And I follow "OpenSCAP" in the content area 0s

And I follow "xccdf_org.open-scap_testresult" 0s

Then I should see a "Details of XCCDF Scan" text 0s

And I should see a "profile standard" text 0s

And I should see a "XCCDF Rule Results" text 0s

When I enter "pass" as the filtered XCCDF result type 0s

And I click on the filter button 0s

Then I should see a "xccdf_org.ssgproject.content_rule_file_permissions_etc_passwd" link 0s

@susemanager
Scenario:
Create a second, almost identical, audit job
< 1ms 9

When I follow "Audit" in the content area 0s

And I follow "OpenSCAP" in the content area 0s

And I follow "Schedule" in the content area 0s

And I wait at most 30 seconds until I do not see "This system does not yet have OpenSCAP scan capability." text, refreshing the page 0s

And I enter "--profile standard" as "params" 0s

And I enter "/usr/share/xml/scap/ssg/content/ssg-sle15-ds.xml" as "path" 0s

And I click on "Schedule" 0s

Then I should see a "XCCDF scan has been scheduled" text 0s

When I wait for the OpenSCAP audit to finish 0s

@uyuni
Scenario:
Create a second, almost identical, audit job
9ms 8 1

When I follow "Audit" in the content area 9ms Show Error + 
                                            
 undefined method `map' for true (NoMethodError)
./features/support/commonlib.rb:198:in `click_link_and_wait'
./features/step_definitions/navigation_steps.rb:339:in `/^I follow "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:361:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:360:in `/^I follow "([^"]*)" in the (.+)$/'
features/secondary/min_salt_openscap_audit.feature:90:in `I follow "Audit" in the content area'

And I follow "OpenSCAP" in the content area 0s

And I follow "Schedule" in the content area 0s

And I wait at most 30 seconds until I do not see "This system does not yet have OpenSCAP scan capability." text, refreshing the page 0s

And I enter "--profile standard" as "params" 0s

And I enter "/usr/share/xml/scap/ssg/content/ssg-opensuse-ds.xml" as "path" 0s

And I click on "Schedule" 0s

Then I should see a "XCCDF scan has been scheduled" text 0s

When I wait for the OpenSCAP audit to finish 0s

Scenario:
Compare audit results
9ms 6 1

When I follow "Audit" in the content area 9ms Show Error + 
                                            
 undefined method `map' for true (NoMethodError)
./features/support/commonlib.rb:198:in `click_link_and_wait'
./features/step_definitions/navigation_steps.rb:339:in `/^I follow "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:361:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:360:in `/^I follow "([^"]*)" in the (.+)$/'
features/secondary/min_salt_openscap_audit.feature:101: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
406ms 5 1

The browser session could not be cleaned because there is no browser available: undefined method `first' for an instance of String

When I follow the left menu "Admin > Organizations" 406ms Show Error + 
                                            
 undefined method `map' for nil (NoMethodError)
./features/step_definitions/navigation_steps.rb:594:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:460:in `/^I am authorized for the "([^"]*)" section$/'
./features/step_definitions/navigation_steps.rb:420:in `rescue in block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:413:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:406:in `each'
./features/step_definitions/navigation_steps.rb:406:in `each_with_index'
./features/step_definitions/navigation_steps.rb:406:in `/^I follow the left menu "([^"]*)"$/'
features/secondary/min_salt_openscap_audit.feature:110: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
24s 459ms 5 3 1

Given I am on the Systems overview page of this "sle_minion" 822ms

When I follow "Audit" in the content area 70ms

And I follow "OpenSCAP" in the content area 61ms

And I follow "List Scans" in the content area 62ms

And I click on "Select All" 10s Show Error + 
                                            
 Unable to find button "Select All" that is not disabled (Capybara::ElementNotFound)
./features/support/commonlib.rb:184:in `click_button_and_wait'
./features/step_definitions/navigation_steps.rb:293:in `/^I click on "([^"]*)"$/'
features/secondary/min_salt_openscap_audit.feature:122:in `I click on "Select All"'

And I click on "Remove" 0s

And I click on "Confirm" 0s

Then I should see a "2 SCAP Scan(s) deleted. 0 SCAP Scan(s) retained" text 0s

13s 442ms Show Info + 
15:46:34:000 - 15:46:46:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/audit/ListScap.do?sid=1000010023&
Screenshot +

Scenario:
Cleanup: restore audit scans retention period
790ms 6

When I follow the left menu "Admin > Organizations" 118ms

When I follow "SUSE Test" in the content area 70ms

And I follow "Configuration" in the content area 61ms

And I enter "90" as "scap_retention_period" 54ms

And I click on "Update Organization" 421ms

Then I should see a "Organization SUSE Test was successfully updated." text 63ms

Scenario:
Cleanup: remove the OpenSCAP packages from the SLE minion
1s 141ms 1

When I remove OpenSCAP dependencies from "sle_minion" 1s 141ms

@Uyuni
Scenario:
Cleanup: Disable required repositories
445ms 1

When I disable repository "os_pool_repo" on this "sle_minion" without error control 445ms

@flaky @scope_salt
Feature:Coexistence with user-defined states 54s 248ms 4

Scenario:
Log in as org admin user
1s 535ms 1

Given I am authorized 1s 535ms

Scenario:
Create a user-defined state
11s 385ms 7

Given I am on the Systems overview page of this "sle_minion" 1s 310ms

When I follow "States" in the content area 65ms

And I install a user-defined state for "sle_minion" on the server 3s 621ms

And I follow "Highstate" in the content area 65ms

And I click on "Show full highstate output" 278ms

And I wait for "6" seconds 6s

Then I should see a "user_defined_state" or "running as PID" text in element "highstate" 44ms

Scenario:
Trigger highstate from API
23s 430ms 3

When I schedule a highstate for "sle_minion" via API 707ms

And I wait until event "Apply highstate scheduled" is completed 21s 997ms

Then file "/tmp/test_user_defined_state" should exist on "sle_minion" 725ms

Scenario:
Cleanup: remove user-defined state and the file it created
17s 897ms 7

When I follow "States" in the content area 77ms

And I uninstall the user-defined state from the server 1s 126ms

And I uninstall the managed file from "sle_minion" 408ms

And I follow "Highstate" in the content area 66ms

And I click on "Show full highstate output" 182ms

And I wait for "6" seconds 6s

Then I should not see a "user_defined_state" text in element "highstate" 10s 36ms

@scope_salt
Feature:Verify the minion registration 29s 988ms 5

In order to validate the completeness of minion registration
I want to see minion details and installed packages

Scenario:
Log in as org admin user
1s 577ms 1

Given I am authorized 1s 577ms

Scenario:
Check the Salt entitlement
1s 450ms 2

Given I am on the Systems overview page of this "sle_minion" 1s 361ms

Then I should see a "[Salt]" text 89ms

Scenario:
Check that installed packages are visible
926ms 3

When I follow "Software" in the content area 75ms

And I follow "List / Remove" 720ms

Then I should see a "aaa_base" text 131ms

Scenario:
Check that Hardware Refresh button works on a SLES Salt minion
25s 225ms 6

When I follow "Details" in the content area 64ms

And I follow "Hardware" in the content area 61ms

And I click on "Schedule Hardware Refresh" 742ms

Then I should see a "You have successfully scheduled a hardware profile refresh" text 110ms

When I wait until event "Hardware List Refresh scheduled" is completed 21s 971ms

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "sle_minion" 2s 274ms

Scenario:
Check that Update Properties button works
808ms 4

When I follow "Details" in the content area 74ms

And I follow "Hardware" in the content area 64ms

And I click on "Update Properties" 553ms

Then I should see a "Networking properties updated." text 116ms

@sle_minion @scope_configuration_channels
Feature:Configuration state channels 1m 31s 183ms 17

In order to configure systems through Salt
I want to be able to use the state channels

Scenario:
Log in as org admin user
1s 556ms 1

Given I am authorized 1s 556ms

Scenario:
Create a state channel
2s 260ms 12

When I follow the left menu "Configuration > Channels" 873ms

And I follow "Create State Channel" 268ms

Then I should see a "New Config State Channel" text 55ms

When I enter "My State Channel" as "cofName" 65ms

And I enter "statechannel" as "cofLabel" 56ms

And I enter "This is a state channel" as "cofDescription" 64ms

And I enter "touch /root/foobar:\n cmd.run:\n - creates: /root/foobar" in the editor 4ms

And I click on "Create Config State Channel" 636ms

Then I should see a "State Channel" text 61ms

And I should see a "Channel Properties" text 58ms

And I should see a "Channel Information" text 56ms

And I should see a "Configuration Actions" text 58ms

Scenario:
Subscribe a minion to the state channel
2s 489ms 8

When I am on the Systems overview page of this "sle_minion" 803ms

And I follow "Configuration" in the content area 65ms

And I follow "Manage Configuration Channels" in the content area 71ms

And I follow first "Subscribe to Channels" in the content area 66ms

And I check "My State Channel" in the list 59ms

And I click on "Continue" 590ms

And I click on "Update Channel Rankings" 762ms

Then I should see a "Channel Subscriptions successfully changed for" text 70ms

Scenario:
Salt state details
1s 409ms 7

When I follow the left menu "Configuration > Channels" 341ms

And I follow "My State Channel" 395ms

Then I should see a "1 system subscribed" text 69ms

When I follow "View/Edit 'init.sls' File" 377ms

Then I should see a "Revision 1 of /init.sls from channel My State Channel" text 77ms

And I should see a "File Contents" text 74ms

And I should see a "touch /root/foobar:" text 73ms

Scenario:
Apply the new state
24s 299ms 8

When I am on the Systems overview page of this "sle_minion" 892ms

And I follow "States" in the content area 68ms

And I follow "Configuration Channels" in the content area 60ms

Then I should see a "Execute States" button 259ms

When I click on "Execute States" 51ms

Then I should see a "Applying the config channels has been scheduled" text 249ms

When I wait until event "Apply states [custom] scheduled" is completed 21s 949ms

And I wait until file "/root/foobar" exists on "sle_minion" 766ms

Scenario:
Try to remove init.sls file
2s 154ms 7

When I follow the left menu "Configuration > Channels" 348ms

And I follow "My State Channel" 394ms

And I follow "View/Edit 'init.sls' File" 380ms

When I follow "Delete" 321ms

And I click on "Delete Configuration Revision" 553ms

Then I should see a "Cannot delete the only revision for the init.sls file" text 79ms

And I should see a "Revision 1 of /init.sls from channel My State Channel" text 77ms

Scenario:
Cleanup: remove the state channel and the file
1s 845ms 7

When I follow the left menu "Configuration > Channels" 78ms

And I follow "My State Channel" 399ms

And I follow "Delete Channel" 356ms

Then I should see a "Are you sure you want to delete this config channel?" text 52ms

When I click on "Delete Config Channel" 480ms

Then I should see a "Channel 'My State Channel' has been deleted." text 51ms

And I remove "/root/foobar" from "sle_minion" 426ms

Scenario:
Create the 1st state channel
1s 496ms 12

When I follow the left menu "Configuration > Channels" 60ms

And I follow "Create State Channel" 336ms

Then I should see a "New Config State Channel" text 50ms

When I enter "My State Channel" as "cofName" 68ms

And I enter "statechannel" as "cofLabel" 54ms

And I enter "This is a state channel" as "cofDescription" 63ms

And I enter "touch /root/statechannel:\n cmd.run:\n - creates: /root/statechannel" in the editor 4ms

And I click on "Create Config State Channel" 617ms

Then I should see a "State Channel" text 61ms

And I should see a "Channel Properties" text 59ms

And I should see a "Channel Information" text 61ms

And I should see a "Configuration Actions" text 58ms

Scenario:
Create the 2nd state channel with same name
1s 498ms 12

When I follow the left menu "Configuration > Channels" 79ms

And I follow "Create State Channel" 330ms

Then I should see a "New Config State Channel" text 52ms

When I enter "My State Channel" as "cofName" 57ms

And I enter "statechannel2" as "cofLabel" 55ms

And I enter "This is a state channel" as "cofDescription" 58ms

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" 617ms

Then I should see a "State Channel" text 63ms

And I should see a "Channel Properties" text 58ms

And I should see a "Channel Information" text 59ms

And I should see a "Configuration Actions" text 60ms

Scenario:
Create the 3rd state channel with spacecmd
9s 31ms 9

When I create channel "statechannel3" from spacecmd of type "state" 1s 449ms

And I follow the left menu "Configuration > Channels" 59ms

Then I should see a "statechannel3" text 59ms

When I update init.sls from spacecmd with content "touch /tmp/statechannel3:\n cmd.run:\n - creates: /tmp/statechannel3" for channel "statechannel3" 2s 512ms

And I get "/init.sls" file details for channel "statechannel3" via spacecmd 1s 217ms

Then I should see "Revision: 2" in the output < 1ms

When I update init.sls from spacecmd with content "touch /root/statechannel3:\n cmd.run:\n - creates: /root/statechannel3" for channel "statechannel3" and revision "100" 2s 518ms

And I get "/init.sls" file details for channel "statechannel3" via spacecmd 1s 213ms

Then I should see "Revision: 100" in the output < 1ms

Scenario:
Subscribe a minion to 1st and 2nd state channels
2s 127ms 15

When I am on the Systems overview page of this "sle_minion" 809ms

And I follow "States" in the content area 80ms

And I follow "Configuration Channels" in the content area 76ms

And I click on "Search" in element "search-row" 66ms

Then I should see a "My State Channel" text 262ms

And I should see a "statechannel" text 68ms

And I should see a "statechannel2" text 67ms

When I check "statechannel-cbox" 81ms

And I check "statechannel2-cbox" 74ms

And I click on "Save Changes" 61ms

And I wait until I see "Edit Channel Ranks" text 58ms

Then I should see a "My State Channel (statechannel)" text 56ms

And I should see a "My State Channel (statechannel2)" text 58ms

When I click on "Confirm" 55ms

Then I should see a "State assignments have been saved." text 250ms

Scenario:
Apply the Configuration channel state
23s 447ms 9

When I follow "States" in the content area 56ms

And I follow "Configuration Channels" in the content area 55ms

And I click on "Search" in element "search-row" 57ms

And I wait until I see "Execute States" text 61ms

And I click on "Execute States" 59ms

Then I should see a "Applying the config channels has been scheduled" text 274ms

And I wait until event "Apply states [custom] scheduled" is completed 21s 752ms

And I wait until file "/root/statechannel" exists on "sle_minion" 726ms

And I wait until file "/root/statechannel2" exists on "sle_minion" 402ms

Scenario:
Subscribe a minion to the 3rd state channel
1s 197ms 12

When I follow "States" in the content area 75ms

And I follow "Configuration Channels" in the content area 91ms

Then I should see a "My State Channel" text 252ms

And I should see a "statechannel3" text 63ms

When I check "statechannel3-cbox" 96ms

And I click on "Save Changes" 63ms

And I wait until I see "Edit Channel Ranks" text 57ms

And I should see a "My State Channel (statechannel)" text 59ms

And I should see a "My State Channel (statechannel2)" text 59ms

And I should see a "statechannel3 (statechannel3)" text 67ms

When I click on "Confirm" 57ms

Then I should see a "State assignments have been saved." text 252ms

Scenario:
Apply the Configuration channel state with spacecmd
10s 681ms 2

When I schedule apply configchannels for "sle_minion" 2s 602ms

And I wait until file "/root/statechannel3" exists on "sle_minion" 8s 78ms

Scenario:
Cleanup: remove the 1st state channel and the deployed file
2s 84ms 7

When I follow the left menu "Configuration > Channels" 342ms

And I follow first "My State Channel" 385ms

And I follow "Delete Channel" 293ms

Then I should see a "Are you sure you want to delete this config channel?" text 53ms

When I click on "Delete Config Channel" 60ms

Then I should see a "Channel 'My State Channel' has been deleted." text 527ms

When I remove "/root/statechannel" from "sle_minion" 421ms

Scenario:
Cleanup: remove the 2nd state channel and the deployed file
1s 760ms 7

When I follow the left menu "Configuration > Channels" 60ms

And I follow first "My State Channel" 418ms

And I follow "Delete Channel" 289ms

Then I should see a "Are you sure you want to delete this config channel?" text 52ms

When I click on "Delete Config Channel" 468ms

Then I should see a "Channel 'My State Channel' has been deleted." text 57ms

When I remove "/root/statechannel2" from "sle_minion" 415ms

Scenario:
Cleanup: remove the 3rd state channel and the deployed file
1s 842ms 7

When I follow the left menu "Configuration > Channels" 59ms

And I follow first "statechannel3" 548ms

And I follow "Delete Channel" 276ms

Then I should see a "Are you sure you want to delete this config channel?" text 53ms

When I click on "Delete Config Channel" 461ms

Then I should see a "Channel 'statechannel3' has been deleted." text 47ms

When I remove "/root/statechannel3" from "sle_minion" 395ms

Feature:Configuration state channels via API 1s 930ms 3

Scenario:
Create a state channel via API
668ms 3

When I create state channel "statechannel1" via API 354ms

And I call configchannel.get_file_revision() with file "/init.sls", revision "1" and channel "statechannel1" via API 314ms

Then I should get file contents "" < 1ms

Scenario:
Create a state channel with contents via API
648ms 3

When I create state channel "statechannel2" containing "touch /root/foobar:\n cmd.run:\n - creates: /root/foobar" via API 331ms

And I call configchannel.get_file_revision() with file "/init.sls", revision "1" and channel "statechannel2" via API 317ms

Then I should get file contents "touch /root/foobar:\n cmd.run:\n - creates: /root/foobar" < 1ms

Scenario:
Cleanup: remove state channels via API
612ms 2

Then I delete channel "statechannel1" via API without error control 302ms

And I delete channel "statechannel2" via API without error control 309ms

@skip_if_github_validation @scope_salt
Feature:System package list is updated if packages are manually installed or removed 1m 12s 936ms 7

Scenario:
Pre-requisite: install milkyway-dummy-1.0 package
3s 13ms 3

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 459ms

And I refresh the metadata for "sle_minion" 873ms

And I install old package "milkyway-dummy-1.0" on this "sle_minion" without error control 1s 681ms

Scenario:
Pre-requisite: refresh package list and check installed packages on SLE minion client
10s 681ms 3

When I refresh packages list via spacecmd on "sle_minion" 3s 410ms

And I wait until refresh package list on "sle_minion" is finished 4s 931ms

Then spacecmd should show packages "milkyway-dummy-1.0" installed on "sle_minion" 2s 339ms

Scenario:
Log in as org admin user
1s 619ms 1

Given I am authorized for the "Admin" section 1s 619ms

Scenario:
Pre-requisite: ensure the errata cache is computed before package list tests
18s 989ms 11

Given I am on the Systems overview page of this "sle_minion" 1s 201ms

When I follow "Software" in the content area 71ms

And I follow "List / Remove" in the content area 61ms

And I enter "milkyway-dummy" as the filtered package name 142ms

And I click on the filter button until page does contain "milkyway-dummy-1.0" text 10s 977ms

And I follow the left menu "Admin > Task Schedules" 115ms

And I follow "errata-cache-default" 1s 341ms

And I follow "errata-cache-bunch" 1s 300ms

And I click on "Single Run Schedule" 1s 512ms

Then I should see a "bunch was scheduled" text 272ms

When I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 1s 991ms

Scenario:
Remove manually a package on a minion
21s 824ms 8

Given I am on the Systems overview page of this "sle_minion" 823ms

When I follow "Software" in the content area 69ms

And I follow "List / Remove" 622ms

And I enter "milkyway-dummy" as the filtered package name 142ms

And I click on the filter button 810ms

Then I should see a "milkyway-dummy" text 74ms

When I remove package "milkyway-dummy" from this "sle_minion" 1s 851ms

And I click on the filter button until page does not contain "milkyway-dummy" text 17s 429ms

Scenario:
Install manually a package on a minion
13s 801ms 7

When I follow "Software" in the content area 68ms

And I follow "List / Remove" 652ms

And I enter "milkyway-dummy" as the filtered package name 153ms

And I click on the filter button 782ms

Then I should not see a "milkyway-dummy" text 65ms

When I install package "milkyway-dummy" on this "sle_minion" 2s 28ms

And I click on the filter button until page does not contain "milkyway-dummy" text 10s 50ms

Scenario:
Cleanup: remove milkyway-dummy packages from SLES minion
3s 6ms 3

When I disable repository "test_repo_rpm_pool" on this "sle_minion" 794ms

And I remove package "milkyway-dummy" from this "sle_minion" without error control 1s 438ms

And I refresh the metadata for "sle_minion" 774ms

@sle_minion @scope_monitoring @skip_if_github_validation
Feature:Monitor MLM environment with Prometheus on a SLE Salt minion 10m 31s 315ms 6 3

In order to monitor Uyuni server
As an authorized user
I want to enable Prometheus exporters

Scenario:
Log in as org admin user
1s 510ms 1

Given I am authorized 1s 510ms

Scenario:
Apply Prometheus and Prometheus exporter formulas
2s 848ms 8

Given I am on the Systems overview page of this "sle_minion" 1s 497ms

When I follow "Formulas" in the content area 68ms

And I should see a "Choose formulas:" text 71ms

And I should see a "Monitoring" text 291ms

And I check the "prometheus" formula 80ms

And I check the "prometheus-exporters" formula 85ms

And I click on "Save" 62ms

Then I wait until I see "Formula saved" text 690ms

Scenario:
Configure Prometheus formula
1s 620ms 7

When I follow "Formulas" in the content area 63ms

And I follow "Prometheus" in the content area 291ms

And I click on "Expand All Sections" 292ms

And I enter "admin" as "Username" 111ms

And I enter "admin" as "Password" 86ms

And I click on "Save Formula" 80ms

Then I should see a "Formula saved" text 693ms

Scenario:
Configure Prometheus exporter formula
1s 912ms 9

When I follow "Formulas" in the content area 63ms

And I follow "Prometheus Exporters" in the content area 236ms

And I click on "Expand All Sections" 224ms

And I should see a "Enable and configure Prometheus exporters for managed systems." text 103ms

And I check "node" exporter 43ms

And I check "apache" exporter 80ms

And I check "postgres" exporter 79ms

And I click on "Save" 56ms

Then I should see a "Formula saved" text 1s 24ms

Scenario:
Apply highstate for Prometheus exporters
1m 12s 515ms 4 1

Event Details: Failed to apply state(s): highstate ---------- ID: sync_states Function: saltutil.sync_states Name: sync_states Result: true Comment: No updates to sync Started: 15:52:01.066761 Duration: 254.467 SLS: util.syncstates Changed: {} ---------- ID: mgr_absent_ca_package Function: pkg.removed Name: rhn-org-trusted-ssl-cert Result: true Comment: All specified packages are already absent Started: 15:52:06.576127 Duration: 11.197 SLS: certs Changed: {} ---------- ID: mgr_ca_cert Function: file.managed Name: /etc/pki/trust/anchors/RHN-ORG-TRUSTED-SSL-CERT Result: true Comment: File /etc/pki/trust/anchors/RHN-ORG-TRUSTED-SSL-CERT is in the correct state Started: 15:52:06.590095 Duration: 43.578 SLS: certs Changed: {} ---------- ID: update-ca-certificates Function: cmd.run Name: /usr/sbin/update-ca-certificates Result: true Comment: State was not run because none of the onchanges reqs changed Started: 15:52:06.635576 Duration: 0.008 SLS: certs Changed: {} ---------- ID: mgr_proxy_ca_cert_symlink Function: file.symlink Name: /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT Result: true Comment: onlyif condition is false Started: 15:52:06.635705 Duration: 739.292 SLS: certs Changed: {} ---------- ID: mgr_deploy_tools_uyuni_key Function: file.managed Name: /etc/pki/rpm-gpg/uyuni-tools-gpg-pubkey-0d20833e.key Result: true Comment: File /etc/pki/rpm-gpg/uyuni-tools-gpg-pubkey-0d20833e.key is in the correct state Started: 15:52:07.375190 Duration: 43.914 SLS: channels.gpg-keys Changed: {} ---------- ID: mgr_deploy_suse_addon_key Function: file.managed Name: /etc/pki/rpm-gpg/suse-addon-97a636db0bad8ecc.key Result: true Comment: File /etc/pki/rpm-gpg/suse-addon-97a636db0bad8ecc.key is in the correct state Started: 15:52:07.419283 Duration: 43.433 SLS: channels.gpg-keys Changed: {} ---------- ID: mgr_deploy_suse16_gpg_key Function: file.managed Name: /etc/pki/rpm-gpg/suse16-gpg-pubkey-09d9ea69.key Result: true Comment: File /etc/pki/rpm-gpg/suse16-gpg-pubkey-09d9ea69.key is in the correct state Started: 15:52:07.462878 Duration: 47.981 SLS: channels.gpg-keys Changed: {} ---------- ID: file_///etc/pki/rpm-gpg/uyuni-tools-gpg-pubkey-0d20833e.key Function: mgrcompat.module_run Name: pkg.add_repo_key Result: true Comment: Module function pkg.add_repo_key executed Started: 15:52:07.511016 Duration: 30.428 SLS: channels.gpg-keys Changed: ret: true ---------- ID: file_///usr/lib/rpm/gnupg/keys/gpg-pubkey-29b700a4-62b07e22.asc Function: mgrcompat.module_run Name: pkg.add_repo_key Result: true Comment: Module function pkg.add_repo_key executed Started: 15:52:07.541599 Duration: 28.74 SLS: channels.gpg-keys Changed: ret: true ---------- ID: mgrchannels_repo Function: file.managed Name: /etc/zypp/repos.d/susemanager:channels.repo Result: true Comment: File /etc/zypp/repos.d/susemanager:channels.repo is in the correct state Started: 15:52:07.570749 Duration: 173.524 SLS: channels Changed: {} ---------- ID: pkg_installed Function: pkg.installed Name: pkg_installed Result: true Comment: No packages to install provided Started: 15:52:07.744907 Duration: 0.915 SLS: packages.packages_ffd88a30e1b9de063f27f5c769805e9e Changed: {} ---------- ID: pkg_removed Function: pkg.removed Name: pkg_removed Result: true Comment: All specified packages are already absent Started: 15:52:07.746081 Duration: 10.687 SLS: packages.packages_ffd88a30e1b9de063f27f5c769805e9e Changed: {} ---------- ID: pkg_latest Function: pkg.latest Name: pkg_latest Result: true Comment: No packages to install provided Started: 15:52:07.757044 Duration: 0.639 SLS: packages.packages_ffd88a30e1b9de063f27f5c769805e9e Changed: {} ---------- ID: os_not_supported Function: test.fail_without_changes Name: OS not supported! Result: false Comment: Failure! Started: 15:52:07.757774 Duration: 0.799 SLS: prometheus Changed: {} ---------- ID: exporter_exporter Function: service.dead Name: prometheus-exporter_exporter Result: true Comment: The named service prometheus-exporter_exporter is not available Started: 15:52:07.758695 Duration: 21.765 SLS: prometheus-exporters Changed: {} ---------- ID: node_exporter Function: pkg.installed Name: golang-github-prometheus-node_exporter Result: true Comment: 1 targeted package was installed/updated. Started: 15:52:07.780605 Duration: 4078.842 SLS: prometheus-exporters Changed: system-user-prometheus: old: '' new: 1.0.0-1.15 golang-github-prometheus-node_exporter: old: '' new: 1.10.2-1.1 ---------- ID: node_exporter Function: file.managed Name: /etc/sysconfig/prometheus-node_exporter Result: true Comment: File /etc/sysconfig/prometheus-node_exporter updated Started: 15:52:11.863711 Duration: 126.581 SLS: prometheus-exporters Changed: diff: "--- \n+++ \n@@ -1,11 +1,9 @@\n-## Path: Network/Monitors/Prometheus/node_exporter\n-## Description: Prometheus node exporter startup parameters\n\ -## Type: string\n-## Default: ''\n+## Path: Applications/NodeExporter\n+## Description: Prometheus exporter for machine metrics\n\ +## Type: string()\n+## Default: \"\"\n+## ServiceRestart: prometheus-node_exporter\n #\n-# Additional arguments for the node_exporter.\n\ -# Please call: /usr/bin/node_exporter --help\n-# for a full list of possible options. \n-# Note: Please keep the list on one line, of possible.\n+#\ \ Arguments for running prometheus-node_exporter\n #\n-ARGS=''\n+ARGS=--collector.systemd --web.listen-address=:9100\n" ---------- ID: node_exporter Function: service.running Name: prometheus-node_exporter Result: true Comment: Service prometheus-node_exporter has been enabled, and is running Started: 15:52:16.873988 Duration: 569.999 SLS: prometheus-exporters Changed: prometheus-node_exporter: true ---------- ID: apache_exporter Function: pkg.installed Name: golang-github-lusitaniae-apache_exporter Result: true Comment: 1 targeted package was installed/updated. Started: 15:52:17.447469 Duration: 2747.501 SLS: prometheus-exporters Changed: golang-github-lusitaniae-apache_exporter: old: '' new: 1.0.10-3.1 ---------- ID: apache_exporter Function: file.managed Name: /etc/sysconfig/prometheus-apache_exporter Result: true Comment: File /etc/sysconfig/prometheus-apache_exporter updated Started: 15:52:20.199321 Duration: 91.798 SLS: prometheus-exporters Changed: diff: New file mode: '0644' ---------- ID: apache_exporter Function: service.running Name: prometheus-apache_exporter Result: true Comment: Service prometheus-apache_exporter has been enabled, and is running Started: 15:52:25.304725 Duration: 555.587 SLS: prometheus-exporters Changed: prometheus-apache_exporter: true ---------- ID: postgres_exporter Function: pkg.installed Name: prometheus-postgres_exporter Result: true Comment: 1 targeted package was installed/updated. Started: 15:52:25.862004 Duration: 2822.435 SLS: prometheus-exporters Changed: prometheus-postgres_exporter: old: '' new: 0.10.1-4.5 ---------- ID: postgres_exporter Function: file.managed Name: /etc/systemd/system/prometheus-postgres_exporter.service.d/60-suse-salt-formula.conf Result: true Comment: File /etc/systemd/system/prometheus-postgres_exporter.service.d/60-suse-salt-formula.conf updated Started: 15:52:28.689394 Duration: 123.491 SLS: prometheus-exporters Changed: diff: New file mode: '0644' ---------- ID: postgres_exporter Function: file.managed Name: /etc/postgres_exporter/pg_passwd Result: true Comment: File /etc/postgres_exporter/pg_passwd updated Started: 15:52:28.813289 Duration: 90.538 SLS: prometheus-exporters Changed: diff: New file user: prometheus ---------- ID: postgres_exporter Function: module.run Name: service.systemctl_reload Result: true Comment: Module function service.systemctl_reload executed Started: 15:52:28.905690 Duration: 423.509 SLS: prometheus-exporters Changed: ret: true ---------- ID: postgres_exporter Function: service.running Name: prometheus-postgres_exporter Result: true Comment: Service prometheus-postgres_exporter has been enabled, and is running Started: 15:52:34.343470 Duration: 613.062 SLS: prometheus-exporters Changed: prometheus-postgres_exporter: true ---------- ID: disable_spacewalksd Function: service.dead Name: rhnsd Result: true Comment: The named service rhnsd is not available Started: 15:52:34.956691 Duration: 16.55 SLS: services.salt-minion Changed: {} ---------- ID: disable_spacewalk-update-status Function: service.dead Name: spacewalk-update-status Result: true Comment: The named service spacewalk-update-status is not available Started: 15:52:34.973415 Duration: 13.132 SLS: services.salt-minion Changed: {} ---------- ID: disable_osad Function: service.dead Name: osad Result: true Comment: The named service osad is not available Started: 15:52:34.986724 Duration: 13.587 SLS: services.salt-minion Changed: {} ---------- ID: remove_traditional_stack_all Function: pkg.removed Name: remove_traditional_stack_all Result: true Comment: All specified packages are already absent Started: 15:52:35.001969 Duration: 18.037 SLS: services.salt-minion Changed: {} ---------- ID: remove_traditional_stack Function: pkg.removed Name: remove_traditional_stack Result: true Comment: All specified packages are already absent Started: 15:52:35.020145 Duration: 279.984 SLS: services.salt-minion Changed: {} ---------- ID: /etc/sysconfig/rhn/systemid Function: file.managed Name: /etc/sysconfig/rhn/systemid Result: true Comment: File /etc/sysconfig/rhn/systemid exists with proper permissions. No changes made. Started: 15:52:35.300285 Duration: 1.679 SLS: services.salt-minion Changed: {} ---------- ID: mgr_salt_minion_inst Function: pkg.installed Name: venv-salt-minion Result: true Comment: All specified packages are already installed Started: 15:52:35.302514 Duration: 11.161 SLS: services.salt-minion Changed: {} ---------- ID: /etc/venv-salt-minion/minion.d/susemanager.conf Function: file.managed Name: /etc/venv-salt-minion/minion.d/susemanager.conf Result: true Comment: File /etc/venv-salt-minion/minion.d/susemanager.conf is in the correct state Started: 15:52:35.313917 Duration: 170.141 SLS: services.salt-minion Changed: {} ---------- ID: mgr_salt_minion_run Function: service.running Name: venv-salt-minion Result: true Comment: The service venv-salt-minion is already running Started: 15:52:35.484247 Duration: 38.97 SLS: services.salt-minion Changed: {}

When I follow "States" in the content area 69ms

And I click on "Apply Highstate" 55ms

Then I should see a "Applying the highstate has been scheduled." text 393ms

And I wait until event "Apply highstate scheduled" is completed 58s 444ms Show Error + 
                                            
 unknown error - Event failed (SystemCallError)
./features/step_definitions/navigation_steps.rb:96:in `block (2 levels) in (top (required))'
./features/support/commonlib.rb:106:in `block in repeat_until_timeout'
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/step_definitions/navigation_steps.rb:88:in `/^I wait at most (\d+) seconds until the event is completed, refreshing the page$/'
./features/step_definitions/common_steps.rb:157:in `/^I wait (\d+) seconds until the event is picked up and (\d+) seconds until the event "([^"]*)" is completed$/'
./features/step_definitions/common_steps.rb:174:in `/^I wait at most (\d+) seconds until event "([^"]*)" is completed$/'
./features/step_definitions/common_steps.rb:151:in `/^I wait until event "([^"]*)" is completed$/'
features/secondary/min_monitoring.feature:51:in `I wait until event "Apply highstate scheduled" is completed'

13s 552ms Show Info + 
15:51:54:000 - 15:52:54:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010023&aid=402
Screenshot +

Scenario:
Wait for services
4m 23s 451ms 1 3 1

When I wait until "prometheus" service is active on "sle_minion" 4m 10s Show Error + 
                                            
 execution expired (Timeout::Error)
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/support/remote_node.rb:202:in `run_until_ok'
./features/step_definitions/command_steps.rb:299:in `/^I wait until "([^"]*)" service is active on "([^"]*)"$/'
features/secondary/min_monitoring.feature:54:in `I wait until "prometheus" service is active on "sle_minion"'

And I wait until "node" exporter service is active on "sle_minion" 0s

And I wait until "apache" exporter service is active on "sle_minion" 0s

And I wait until "postgres" exporter service is active on "sle_minion" 0s

13s 451ms Show Info + 
15:53:07:000 - 15:57:17:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010023&aid=402
Screenshot +

Scenario:
Visit monitoring endpoints on the minion
4m 23s 496ms 1 3 1

When I visit "Prometheus" endpoint of this "sle_minion" 4m 10s Show Error + 
                                            
 execution expired (Timeout::Error)
./features/support/commonlib.rb:95:in `repeat_until_timeout'
./features/support/remote_node.rb:202:in `run_until_ok'
./features/step_definitions/navigation_steps.rb:1168:in `/^I visit "([^"]*)" endpoint of this "([^"]*)"$/'
features/secondary/min_monitoring.feature:60:in `I visit "Prometheus" endpoint of this "sle_minion"'

And I visit "Prometheus node exporter" endpoint of this "sle_minion" 0s

And I visit "Prometheus apache exporter" endpoint of this "sle_minion" 0s

And I visit "Prometheus postgres exporter" endpoint of this "sle_minion" 0s

13s 496ms Show Info + 
15:57:31:000 - 16:01:41:000 | Current URL: https://uyuni-master-server.sumaci.aws/rhn/systems/details/history/Event.do?sid=1000010023&aid=402
Screenshot +

Scenario:
Cleanup: undo Prometheus and Prometheus exporter formulas
1s 396ms 5

When I follow "Formulas" in the content area 73ms

And I uncheck the "prometheus" formula 227ms

And I uncheck the "prometheus-exporters" formula 64ms

And I click on "Save" 60ms

Then I wait until I see "Formula saved" text 970ms

Scenario:
Cleanup: apply highstate after test monitoring
22s 561ms 4

And I follow "States" in the content area 70ms

And I click on "Apply Highstate" 61ms

Then I should see a "Applying the highstate has been scheduled." text 433ms

And I wait until event "Apply highstate scheduled" is completed 21s 995ms

@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 921ms 4

Scenario:
Log in as org admin user
1s 577ms 1

Given I am authorized 1s 577ms

Scenario:
Check perseus-dummy-7891 patches
1s 372ms 7

When I follow the left menu "Patches > Patch List > All" 178ms

And I enter "dummy" as the filtered synopsis 41ms

And I click on the filter button 630ms

And I follow "perseus-dummy-7891" 432ms

Then I should see a "perseus-dummy-7891 - Security Advisory" text 66ms

And I should see a "CVE-1999-12345" link 11ms

And I should see a "CVE-1999-99781" link 11ms

Scenario:
Check local metadata for long CVE IDs
4s 149ms 5

When I refresh the metadata for "sle_minion" 769ms

Then I should have 'reference.*id="CVE-1999-12345' in the patch metadata for "sle_minion" 836ms

And I should have 'reference.*id="CVE-1999-99781' in the patch metadata for "sle_minion" 873ms

And I should have 'reference.*http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-1999-12345' in the patch metadata for "sle_minion" 844ms

And I should have 'reference.*http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-1999-99781' in the patch metadata for "sle_minion" 826ms

Scenario:
Search for CVE ID with the new format
822ms 5

When I follow the left menu "Patches > Advanced Search" 62ms

When I enter "CVE-1999-12345" as "search_string" in the content area 77ms

And I click on "Search" 584ms

Then I should see a "Advanced Search" text 76ms

And I should see a "perseus-dummy-7891" link in the content area 20ms

@scope_onboarding
Feature:Display patches 48s 87ms 8

Scenario:
Log in as org admin user
1s 615ms 1

Given I am authorized for the "Admin" section 1s 615ms

Scenario:
Pre-require: enable old packages to fake a possible installation
23s 323ms 10

When I enable repository "test_repo_rpm_pool" on this "sle_minion" 450ms

And I refresh the metadata for "sle_minion" 785ms

And I install old package "andromeda-dummy-1.0" on this "sle_minion" 1s 520ms

And I install old package "virgo-dummy-1.0" on this "sle_minion" 1s 833ms

When I follow the left menu "Admin > Task Schedules" 129ms

And I follow "errata-cache-default" 356ms

And I follow "errata-cache-bunch" 1s 279ms

And I click on "Single Run Schedule" 1s 521ms

Then I should see a "bunch was scheduled" text 274ms

And I wait until the table contains "FINISHED" or "SKIPPED" followed by "FINISHED" in its first rows 15s 170ms

Scenario:
Check all patches exist
725ms 8

When I follow the left menu "Patches > Patch List > Relevant" 219ms

Then I should see an update in the list 19ms

When I wait until I see "andromeda-dummy" text, refreshing the page 89ms

Then I should see a "andromeda-dummy-6789" link 11ms

When I enter "virgo-dummy" as the filtered synopsis 54ms

And I click on the filter button 252ms

And I wait until I see "virgo-dummy" text 66ms

Then I should see a "virgo-dummy-3456" link 11ms

Scenario:
Check SLES release 6789 patches
656ms 6

When I follow the left menu "Patches > Patch List > Relevant" 68ms

And I follow "andromeda-dummy-6789" 387ms

Then I should see a "andromeda-dummy-6789 - Bug Fix Advisory" text 65ms

And I should see a "Test update for andromeda-dummy" text 63ms

And I should see a "Fake-RPM-SUSE-Channel" link 10ms

And I should see a "reboot_suggested" text 62ms

Scenario:
Check packages of SLES release 6789 patches
1s 173ms 6

When I follow the left menu "Patches > Patch List > Relevant" 65ms

And I follow "andromeda-dummy-6789" 360ms

And I follow "Packages" 668ms

Then I should see a "Fake-RPM-SUSE-Channel" link 8ms

And I should see a "sha512:19940cc4a9f0d38a038a4455b0f1cf1290c4a4296b27f5a62f4aae60585ac6e2677e88c3c3127d487116ed8d9b1787379e23aafac46bc14408864926bedee693" text 56ms

And I should see a "andromeda-dummy-2.0-1.1-noarch" link 13ms

Scenario:
Check relevant patches for this client
11s 331ms 8

Given I am on the Systems overview page of this "sle_minion" 781ms

When I follow "Software" in the content area 65ms

And I follow "Patches" in the content area 61ms

Then I should see a "Relevant Patches" text 78ms

When I enter "dummy" as the filtered synopsis 36ms

And I click on the filter button 10s 157ms

Then I should see a "Test update for andromeda-dummy" text 73ms

And I should see a "Test update for virgo-dummy" text 77ms

Scenario:
Cleanup: regenerate search index for later tests
5s 22ms 1

Search by hostname: uyuni-master-suse-minion
[{"last_boot"=>"2026-02-02T12:06:46Z", "name"=>"uyuni-master-suse-minion.sumaci.aws", "id"=>1000010023, "last_checkin"=>"2026-02-02T15:02:45Z"}]

When I clean the search index on the server 5s 22ms

Scenario:
Cleanup: remove old packages
4s 238ms 4

When I disable repository "test_repo_rpm_pool" on this "sle_minion" without error control 450ms

And I refresh the metadata for "sle_minion" 875ms

And I remove package "andromeda-dummy" from this "sle_minion" without error control 1s 468ms

And I remove package "virgo-dummy" from this "sle_minion" without error control 1s 444ms

@sle_minion @susemanager @scope_project_lotus @flaky
Feature:Project Lotus < 1ms 12

In order to manage Program Temporary Fixes (PTFs)
As an authorized user
I want to be able to install and remove them through the WebUI

Scenario:
Log in as org admin user
< 1ms 1

Given I am authorized 0s

Scenario:
Pre-requisite: Create custom channel for PTFs
< 1ms 9

When I follow the left menu "Software > Manage > Channels" 0s

And I follow "Create Channel" 0s

And I enter "Custom Channel for SLES15SP7 PTFs" as "Channel Name" 0s

And I enter "sles15sp7-ptfs" as "Channel Label" 0s

And I select the parent channel for the "sle_minion" from "Parent Channel" 0s

And I enter "Custom channel for PTFs" as "Channel Summary" 0s

And I uncheck "gpg_check" 0s

And I click on "Create Channel" 0s

Then I should see a "Custom Channel for SLES15SP7 PTFs" text 0s

Scenario:
Pre-requisite: Create custom repository for PTFs
< 1ms 7

When I follow the left menu "Software > Manage > Repositories" 0s

And I follow "Create Repository" 0s

And I enter "sles15sp7_ptf_repo" as "label" 0s

And I enter "http://updates.suse.de/download/PTF/Release/A127499/SLES/15.4/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-24894-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-24894-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-24894-3-0" as the filtered package name 0s

And I click on the filter button 0s

And I check "ptf-24894-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-24894-3-0" as the filtered package name 0s

And I click on the filter button 0s

And I check "ptf-24894-3-0" in the list 0s

And I click on "Remove Packages" 0s

And I click on "Confirm" 0s

Then I should see a "1 package removal has been scheduled for" text 0s

And I wait until event "Package Removal scheduled" is completed 0s

Scenario:
Cleanup: Delete custom channel for PTFs
< 1ms 6

When I follow the left menu "Software > Manage > Channels" 0s

And I follow "Custom Channel for SLES15SP7 PTFs" 0s

And I follow "Delete Channel" 0s

And I check "unsubscribeSystems" 0s

And I click on "Delete Channel" 0s

Then I should see a "Channel Custom Channel for SLES15SP7 PTFs has been deleted" text 0s

Scenario:
Cleanup: Remove custom repository for PTFs
< 1ms 5

When I follow the left menu "Software > Manage > Repositories" 0s

And I follow "sles15sp7_ptf_repo" 0s

And I follow "Delete Repository" 0s

And I click on "Delete Repository" 0s

Then I should see a "Repository deleted successfully" text 0s

@skip_if_github_validation @skip_if_cloud @skip_if_containerized_server
Feature:Reconfigure the server's hostname < 1ms 20

As admin user
In order to change the server's hostname
I want to use the tool spacewalk-hostname-rename.

Scenario:
Log in as admin user
< 1ms 1

Given I am authorized for the "Admin" section 0s

Scenario:
Change hostname and reboot server
< 1ms 3

When I change the server's short hostname from hosts and hostname files 0s

And I reboot the server through SSH 0s

And I run spacewalk-hostname-rename command on the server 0s

@proxy
Scenario:
Copy the new server keys and configure the proxy
< 1ms 7

When I copy server's keys to the proxy 0s

And I configure the proxy 0s

Then I should see "proxy" via spacecmd 0s

When I restart the "venv-salt-minion" service on "proxy" 0s

Then service "venv-salt-minion" is active on "proxy" 0s

When I restart the "salt-broker" service on "proxy" 0s

Then service "salt-broker" is active on "proxy" 0s

@proxy
Scenario:
Apply high state on the proxy to populate new server CA
< 1ms 1

When I apply highstate on "proxy" 0s

@sle_minion
Scenario:
Apply high state on the SUSE Minion to populate new server CA
< 1ms 1

When I apply highstate on "sle_minion" 0s

@ssh_minion
Scenario:
Apply high state on the SUSE SSH Minion to populate new server CA
< 1ms 1

When I apply highstate on "ssh_minion" 0s

@rhlike_minion
Scenario:
Apply high state on the Red Hat-like Minion to populate new server CA
< 1ms 1

When I apply highstate on "rhlike_minion" 0s

@deblike_minion
Scenario:
Apply high state on the Debian-like Minion to populate new server CA
< 1ms 1

When I apply highstate on "deblike_minion" 0s

@build_host
Scenario:
Apply high state on the build host to populate new server CA
< 1ms 1

When I apply highstate on "build_host" 0s

Scenario:
Check all new server certificates on the minions
< 1ms 1

When I check all certificates after renaming the server hostname 0s

Scenario:
Do some minimal smoke test on the renamed server
< 1ms 10

Given I am on the Systems overview page of this "sle_minion" 0s

When I follow "Details" in the content area 0s

And I follow "Remote Command" in the content area 0s

And I enter as remote command this script in #!/bin/bash date 0s

And I click on "Schedule" 0s

And I follow "Events" in the content area 0s

And I follow "Pending" in the content area 0s

And I wait at most 180 seconds until I do not see "Remote Command on" text, refreshing the page 0s

And I follow "History" in the content area 0s

And I wait until I see the event "Remote Command on" completed during last minute, refreshing the page 0s

Scenario:
Change hostname back and reboot server
< 1ms 2

When I change back the server's hostname 0s

And I run spacewalk-hostname-rename command on the server 0s

@proxy
Scenario:
Copy the new server keys and configure the proxy
< 1ms 7

When I copy server's keys to the proxy 0s

And I configure the proxy 0s

Then I should see "proxy" via spacecmd 0s

When I restart the "venv-salt-minion" service on "proxy" 0s

Then service "venv-salt-minion" is active on "proxy" 0s

When I restart the "salt-broker" service on "proxy" 0s

Then service "salt-broker" is active on "proxy" 0s

@proxy
Scenario:
Apply high state on the proxy to populate new server CA
< 1ms 1

When I apply highstate on "proxy" 0s

@sle_minion
Scenario:
Apply high state on the SUSE Minion to populate new server CA
< 1ms 1

When I apply highstate on "sle_minion" 0s

@ssh_minion
Scenario:
Apply high state on the SUSE SSH Minion to populate new server CA
< 1ms 1

When I apply highstate on "ssh_minion" 0s

@rhlike_minion
Scenario:
Apply high state on the Red Hat-like Minion to populate new server CA
< 1ms 1

When I apply highstate on "rhlike_minion" 0s

@deblike_minion
Scenario:
Apply high state on the Debian-like Minion to populate new server CA
< 1ms 1

When I apply highstate on "deblike_minion" 0s

@build_host
Scenario:
Apply high state on the build host to populate new server CA
< 1ms 1

When I apply highstate on "build_host" 0s

Scenario:
Check all new server certificates on the minions
< 1ms 1

When I check all certificates after renaming the server hostname 0s

@transactional_server
Feature:SELinux debugging < 1ms 1

In order for the server to behave correctly after a reboot
I want to be sure that there is no wrong SELinux label

Scenario:
No previous operation has created wrong SELinux label
< 1ms 1

Then files on container volumes should all have the proper SELinux label 0s

@new_issue
Feature:Debug the server after the testsuite has run 41s 821ms 4 1

Scenario:
Call spacewalk-debug on server
34s 288ms 1

When I execute spacewalk-debug on the server 34s 288ms

Scenario:
Check the tomcat logs on server
826ms 1

Then the tomcat logs should not contain errors 826ms

Scenario:
Check salt event log for failures on server
5s 87ms 1

Then the salt event log on server should contain no failures 5s 87ms Show Error + 
                                            
 
Found 23 failures in salt event log:

# Failure 2 , _stamp: 2026-02-02T13:25:31.849253 {
    "__id__": "pkg_installed",
    "__run_num__": 11,
    "__sls__": "packages.pkginstall",
    "changes": {},
    "comment": "An error was encountered while installing package(s): Zypper command failure: Running as unit: run-p14113-i14114.scope; invocation ID: 39204ca084df410f99d2f7570b55f1e1Loading repository data...\nReading installed packages...\nResolving package dependencies...\n\nProblem: 1: nothing provides 'python3-defusedxml' needed by the to be installed python3-rhnlib-5.2.1-2.3.uyuni.noarch\n Solution 1: do not install mgr-push-5.2.1-2.3.uyuni.noarch\n Solution 2: break python3-rhnlib-5.2.1-2.3.uyuni.noarch by ignoring some of its dependencies\n\nChoose from above solutions by number or cancel [1/2/c/d/?] (c): c",
    "duration": 1905.259,
    "name": "pkg_installed",
    "result": false,
    "start_time": "14:25:29.934777"
}

# Failure 3 , _stamp: 2026-02-02T13:40:26.329385 {
    "__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": 14513.719,
    "name": "docker.build",
    "result": false,
    "start_time": "14:40:11.785633"
}

# Failure 4 , _stamp: 2026-02-02T13:40:26.329385 {
    "__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": "14:40:26.299834"
}

# Failure 5 , _stamp: 2026-02-02T13:40:26.329385 {
    "__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": "14:40:26.300104"
}

# Failure 6 , _stamp: 2026-02-02T13:41:37.092194 {
    "__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": 14691.578,
    "name": "docker.build",
    "result": false,
    "start_time": "14:41:22.369745"
}

# Failure 7 , _stamp: 2026-02-02T13:41:37.092194 {
    "__id__": "mgr_pushimage",
    "__run_num__": 2,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "One or more requisite failed: images.docker.mgr_buildimage",
    "duration": 0.004,
    "name": "docker.push",
    "result": false,
    "start_time": "14:41:37.061731"
}

# Failure 8 , _stamp: 2026-02-02T13:41:37.092194 {
    "__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": "14:41:37.062023"
}

# Failure 9 , _stamp: 2026-02-02T13:47:01.573570 {
    "__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": 14184.119,
    "name": "docker.build",
    "result": false,
    "start_time": "14:46:47.357291"
}

# Failure 10 , _stamp: 2026-02-02T13:47:01.573570 {
    "__id__": "mgr_pushimage",
    "__run_num__": 2,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "One or more requisite failed: images.docker.mgr_buildimage",
    "duration": 0.004,
    "name": "docker.push",
    "result": false,
    "start_time": "14:47:01.541812"
}

# Failure 11 , _stamp: 2026-02-02T13:47:01.573570 {
    "__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": "14:47:01.542103"
}

# Failure 12 , _stamp: 2026-02-02T13:47:57.030188 {
    "__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": 14676.078,
    "name": "docker.build",
    "result": false,
    "start_time": "14:47:42.325469"
}

# Failure 13 , _stamp: 2026-02-02T13:47:57.030188 {
    "__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": "14:47:57.002063"
}

# Failure 14 , _stamp: 2026-02-02T13:47:57.030188 {
    "__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": "14:47:57.002330"
}

# Failure 15 , _stamp: 2026-02-02T13:48:54.582493 {
    "__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": 14456.931,
    "name": "docker.build",
    "result": false,
    "start_time": "14:48:40.097038"
}

# Failure 16 , _stamp: 2026-02-02T13:48:54.582493 {
    "__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": "14:48:54.554384"
}

# Failure 17 , _stamp: 2026-02-02T13:48:54.582493 {
    "__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": "14:48:54.554648"
}

# Failure 18 , _stamp: 2026-02-02T13:49:47.344150 {
    "__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": 14993.504,
    "name": "docker.build",
    "result": false,
    "start_time": "14:49:32.322943"
}

# Failure 19 , _stamp: 2026-02-02T13:49:47.344150 {
    "__id__": "mgr_pushimage",
    "__run_num__": 2,
    "__sls__": "images.docker",
    "changes": {},
    "comment": "One or more requisite failed: images.docker.mgr_buildimage",
    "duration": 0.004,
    "name": "docker.push",
    "result": false,
    "start_time": "14:49:47.316852"
}

# Failure 20 , _stamp: 2026-02-02T13:49:47.344150 {
    "__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": "14:49:47.317113"
}

# Failure 21 , _stamp: 2026-02-02T13:58:03.948064 {
    "__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": 14363.307,
    "name": "docker.build",
    "result": false,
    "start_time": "14:57:49.555937"
}

# Failure 22 , _stamp: 2026-02-02T13:58:03.948064 {
    "__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": "14:58:03.919749"
}

# Failure 23 , _stamp: 2026-02-02T13:58:03.948064 {
    "__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": "14:58:03.920019"
}

# Failure 24 , _stamp: 2026-02-02T14:52:35.521844 {
    "__id__": "os_not_supported",
    "__run_num__": 14,
    "__sls__": "prometheus",
    "changes": {},
    "comment": "Failure!",
    "duration": 0.799,
    "name": "OS not supported!",
    "result": false,
    "start_time": "15:52:07.757774"
}

 (ScriptError)
./features/step_definitions/salt_steps.rb:526:in `/^the salt event log on server should contain no failures$/'
features/finishing/srv_debug.feature:15:in `the salt event log on server should contain no failures'

Scenario:
Check the taskomatic logs on server
874ms 1

Then the taskomatic logs should not contain errors 874ms

Scenario:
Check for out of memory errors
744ms 1

Then the log messages should not contain out of memory errors 744ms

Feature:Debug the clients after the testsuite has run 2m 34s 837ms 1

Scenario:
Extract the logs from all our clients
2m 34s 837ms 1

When I extract the log files from all our active nodes 2m 34s 837ms

@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