All Scenarios

24

Passed Scenarios

18

Failed Scenarios

1

Skipped Scenarios

5

Execution Time: 6m 5s 965ms

Expand All | Collapse All

Metadata

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

Feature:Sanity checks 32s 986ms 10 2

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

Scenario:
The server is healthy
7s 164ms 19

Then "server" should have a FQDN 188ms

And reverse resolution should work for "server" 416ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

@proxy
Scenario:
The proxy is healthy
2s 746ms 4

Then "proxy" should have a FQDN 1s 836ms

And reverse resolution should work for "proxy" 158ms

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

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

@sle_minion
Scenario:
The minion is healthy
4s 273ms 4

Then "sle_minion" should have a FQDN 3s

And reverse resolution should work for "sle_minion" 284ms

And "sle_minion" should communicate with the server using public interface 721ms

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

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

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

And reverse resolution should work for "build_host" 174ms

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

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

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

Then "ssh_minion" should have a FQDN 2s 891ms

And reverse resolution should work for "ssh_minion" 250ms

And "ssh_minion" should communicate with the server using public interface 687ms

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

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

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

And reverse resolution should work for "rhlike_minion" 215ms

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

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

@deblike_minion
Scenario:
The Debian-like minion is healthy
6s 646ms 4

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

And reverse resolution should work for "deblike_minion" 283ms

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

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

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

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

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

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

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

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

Feature:Very first settings 4m 26s 274ms 1 1 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
427ms 1

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

@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
4m 25s 846ms 1

Given I am authorized for the "Admin" section 4m 25s 846ms Show Error + 
                                            
 Net::ReadTimeout with #(TCPSocket:(closed)) (Net::ReadTimeout)
./features/step_definitions/navigation_steps.rb:568:in `/^I am authorized as "([^"]*)" with password "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:439:in `/^I am authorized for the "([^"]*)" section$/'
features/core/srv_first_settings.feature:41:in `I am authorized for the "Admin" section'

Feature:SELinux debugging 174ms 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
174ms 1

Then files on container volumes should all have the proper SELinux label 174ms

@under_debugging
Feature:Debug the server after the testsuite has run 8s 391ms 5

Scenario:
Call spacewalk-debug on server
6s 127ms 1

When I execute spacewalk-debug on the server 6s 127ms

Scenario:
Check the tomcat logs on server
426ms 1

Then the tomcat logs should not contain errors 426ms

Scenario:
Check salt event log for failures on server
984ms 1

Then the salt event log on server should contain no failures 984ms

Scenario:
Check the taskomatic logs on server
432ms 1

Then the taskomatic logs should not contain errors 432ms

Scenario:
Check for out of memory errors
419ms 1

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

Feature:Debug the clients after the testsuite has run 58s 138ms 1

Scenario:
Extract the logs from all our clients
58s 138ms 1

When I extract the log files from all our active nodes 58s 138ms

@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