All Scenarios

26

Passed Scenarios

22

Failed Scenarios

0

Skipped Scenarios

4

Execution Time: 1m 54s 170ms

Expand All | Collapse All

Metadata

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

Feature:Sanity checks 43s 993ms 10 2

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

Scenario:
The server is healthy
11s 748ms 19

Then "server" should have a FQDN 382ms

And reverse resolution should work for "server" 626ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

And reverse resolution should work for "proxy" 283ms

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

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

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

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

And reverse resolution should work for "sle_minion" 397ms

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

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

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

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

And reverse resolution should work for "build_host" 230ms

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

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

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

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

And reverse resolution should work for "ssh_minion" 408ms

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

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

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

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

And reverse resolution should work for "rhlike_minion" 190ms

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

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

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

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

And reverse resolution should work for "deblike_minion" 216ms

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

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

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

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

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

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

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

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

Feature:Very first settings 49s 135ms 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
639ms 1

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

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

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

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

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

Scenario:
Create testing username
1s 380ms 12

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

And I follow "Create User" 633ms

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

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

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

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

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

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

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

And I click on "Create Login" 63ms

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

And I should see a "testing" link 12ms

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

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

And I follow "testing" 653ms

And I check "role_org_admin" 82ms

And I check "role_system_group_admin" 79ms

And I check "role_channel_admin" 75ms

And I check "role_activation_key_admin" 77ms

And I check "role_config_admin" 79ms

And I click on "Update" 1s 122ms

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

And I should see a "testing" text 78ms

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

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

* Wed Jan 14 2026 Marek Czernek
- Use internal deb classes instead of external aptsource lib
- Speed up wheel key.finger call (bsc#1240532)
- Backport security patches for Salt vendored tornado:
* CVE-2025-67724: missing validation of supplied reason phrase (bsc#1254903)
* CVE-2025-67725: fix DoS via malicious HTTP request (bsc#1254905)
* CVE-2025-67726: fix HTTP header parameter parsing algorithm (bsc#1254904)
- Simplify and speed up utils.find_json function (bsc#1246130)

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

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

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

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

In order to set up my personal preferences
As admin
I want to navigate through "Home" submenus changing some settings

Scenario:
Change page size to 100 per page in admin user
1s 501ms 5

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

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

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

And I click on "Save Preferences" 736ms

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

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

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

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

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

And I click on "Save Preferences" 659ms

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

Feature:Prepare server for using Kiwi 5s 922ms 1

Scenario:
Create a Kiwi user with image administrators rights
5s 922ms 2

New user kiwikiwi created with roles: image_admin

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

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

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

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

New user docker created with roles: image_admin

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

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

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

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

And I follow "Create" 529ms

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

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

And I click on "create-btn" 210ms

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

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