All Scenarios

36

Passed Scenarios

28

Failed Scenarios

0

Skipped Scenarios

8

Execution Time: 3m 41s 499ms

Expand All | Collapse All

Metadata

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

Feature:Sanity checks 43s 973ms 10 2

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

Scenario:
The server is healthy
11s 955ms 19

Then "server" should have a FQDN 386ms

And reverse resolution should work for "server" 676ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

And reverse resolution should work for "proxy" 277ms

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

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

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

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

And reverse resolution should work for "sle_minion" 448ms

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

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

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

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

And reverse resolution should work for "build_host" 219ms

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

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

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

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

And reverse resolution should work for "ssh_minion" 414ms

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

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

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

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

And reverse resolution should work for "rhlike_minion" 189ms

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

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

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

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

And reverse resolution should work for "deblike_minion" 212ms

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

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

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

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

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

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

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

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

Feature:Very first settings 48s 744ms 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
670ms 1

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

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

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

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

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

Scenario:
Create testing username
2s 228ms 12

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

And I follow "Create User" 658ms

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

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

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

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

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

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

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

And I click on "Create Login" 866ms

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

And I should see a "testing" link 12ms

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

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

And I follow "testing" 526ms

And I check "role_org_admin" 85ms

And I check "role_system_group_admin" 76ms

And I check "role_channel_admin" 81ms

And I check "role_activation_key_admin" 80ms

And I check "role_config_admin" 77ms

And I click on "Update" 645ms

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

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

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

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

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 480ms 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 373ms 5

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

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

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

And I click on "Save Preferences" 592ms

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

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

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

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

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

And I click on "Save Preferences" 56ms

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

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

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

New user kiwikiwi created with roles: image_admin

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

When I create a user with name "kiwikiwi" and password "kiwikiwi" with roles "image_admin" 2s 38ms

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

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

New user docker created with roles: image_admin

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

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

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

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

And I follow "Create" 615ms

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

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

And I click on "create-btn" 147ms

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

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

@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 26s 199ms 5

Scenario:
Call spacewalk-debug on server
19s 873ms 1

When I execute spacewalk-debug on the server 19s 873ms

Scenario:
Check the tomcat logs on server
1s 42ms 1

Then the tomcat logs should not contain errors 1s 42ms

Scenario:
Check salt event log for failures on server
3s 304ms 1

Then the salt event log on server should contain no failures 3s 304ms

Scenario:
Check the taskomatic logs on server
1s 5ms 1

Then the taskomatic logs should not contain errors 1s 5ms

Scenario:
Check for out of memory errors
973ms 1

Then the log messages should not contain out of memory errors 973ms

Feature:Debug the clients after the testsuite has run 1m 24s 821ms 1

Scenario:
Extract the logs from all our clients
1m 24s 821ms 1

When I extract the log files from all our active nodes 1m 24s 821ms

@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