Cucumber Feature Report

All Scenarios

35

Passed Scenarios

28

Failed Scenarios

0

Skipped Scenarios

7

Execution Time: 4m 54s 417ms

Expand All | Collapse All

Metadata

App Version: Uyuni/Head

Browser: Chrome

Platform: x86_64

Parallel: Disabled

Feature:Sanity checks 1m 22s 392ms 10 2

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

Scenario:
The server is healthy

28s 949ms 11

Then "server" should have a FQDN 406ms

And reverse resolution should work for "server" 3s 704ms

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

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

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

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

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

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

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

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

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

@proxy

Scenario:
The proxy is healthy

6s 844ms 4

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

And reverse resolution should work for "proxy" 288ms

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

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

@sle_minion

Scenario:
The minion is healthy

9s 38ms 4

Then "sle_minion" should have a FQDN 5s 95ms

And reverse resolution should work for "sle_minion" 482ms

And "sle_minion" should communicate with the server using public interface 3s 9ms

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

@build_host

Scenario:
The build host is healthy

5s 699ms 4

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

And reverse resolution should work for "build_host" 214ms

And "build_host" should communicate with the server using public interface 2s 798ms

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

@ssh_minion

Scenario:
The SSH minion is healthy

8s 380ms 4

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

And reverse resolution should work for "ssh_minion" 420ms

And "ssh_minion" should communicate with the server using public interface 3s 68ms

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

@rhlike_minion

Scenario:
The Red Hat-like minion is healthy

6s 410ms 4

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

And reverse resolution should work for "rhlike_minion" 264ms

And "rhlike_minion" should communicate with the server using public interface 3s 764ms

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

@deblike_minion

Scenario:
The Debian-like minion is healthy

7s 861ms 4

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

And reverse resolution should work for "deblike_minion" 224ms

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

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

2s 513ms 1

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

@no_auth_registry

Scenario:
The registry without authentication is healthy

4s 89ms 1

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

@custom_download_endpoint

Scenario:
The custom download endpoint is working

2s 604ms 1

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

Feature:Very first settings 1m 2s 549ms 6 1

In order to use the product
As the admin user
I want to create the organisation, the first users and set the HTTP proxy

Scenario:
Cleanup Salt files

4s 389ms 1

When I run "rm -Rf /srv/salt/*" on "server" 4s 389ms

Scenario:
Log in as admin user

39s 832ms 1

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

Scenario:
Wait for refresh of list of products to finish

7s 871ms 1

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

Scenario:
Create testing username

3s 779ms 12

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

And I follow "Create User" 789ms

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

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

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

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

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

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

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

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

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

And I should see a "testing" link 12ms

Scenario:
Grant testing user administrative priviledges

2s 240ms 10

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

And I follow "testing" 522ms

And I check "role_org_admin" 85ms

And I check "role_system_group_admin" 77ms

And I check "role_channel_admin" 81ms

And I check "role_activation_key_admin" 77ms

And I check "role_config_admin" 76ms

And I click on "Update" 1s 86ms

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

And I should see a "testing" text 74ms

@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

4s 435ms 1

* Mon Apr 27 2026 Marek Czernek
- BDSA-2025-60810: Harden Tornado from invalid HTTP reason phrases
- Read full URI from ldap pillar config (bsc#1254900)
- Added:
* bdsa-2025-60810-harden-against-invalid-http-reason-p.patch
* read-full-uri-from-ldap-pillar-config-753.patch

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

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

When I query latest Salt changes on "server" 4s 435ms

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

7s 519ms 1

When I turn off disable_local_repos for all clients 7s 519ms

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

785ms 5

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

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

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

And I click on "Save Preferences" 61ms

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

Scenario:
Change page size to 100 per page in testing user

4s 39ms 5

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

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

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

And I click on "Save Preferences" 1s 141ms

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

Feature:Prepare server for using Kiwi 7s 444ms 1

Scenario:
Create a Kiwi user with image administrators rights

7s 444ms 2

New user kiwikiwi created with roles: image_admin

Given I am authorized for the "Admin" section 3s 414ms

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

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

Scenario:
Create a Docker user with image administrators rights

3s 945ms 2

New user docker created with roles: image_admin

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

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

@no_auth_registry

Scenario:
Create an image store without credentials

3s 541ms 7

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

And I follow "Create" 518ms

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

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

And I click on "create-btn" 150ms

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

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

@transactional_server @test_issue
Feature:SELinux debugging < 1ms 1

* Related GitHub Card: https://github.com/SUSE/spacewalk/issues/24319
In order for the server to behave correctly after a reboot
I want to be sure that there is no wrong SELinux label