All Scenarios

24

Passed Scenarios

18

Failed Scenarios

1

Skipped Scenarios

5

Execution Time: 6m 7s 996ms

Expand All | Collapse All

Metadata

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

Feature:Sanity checks 32s 297ms 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 186ms

And reverse resolution should work for "server" 401ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

And reverse resolution should work for "proxy" 175ms

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

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

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

Then "sle_minion" should have a FQDN 2s 915ms

And reverse resolution should work for "sle_minion" 257ms

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

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

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

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

And reverse resolution should work for "build_host" 171ms

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

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

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

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

And reverse resolution should work for "ssh_minion" 282ms

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

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

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

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

And reverse resolution should work for "rhlike_minion" 215ms

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

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

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

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

And reverse resolution should work for "deblike_minion" 237ms

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

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

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

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

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

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

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

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

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

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

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

Given I am authorized for the "Admin" section 4m 25s 828ms 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 177ms 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
177ms 1

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

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

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

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

Scenario:
Check the tomcat logs on server
430ms 1

Then the tomcat logs should not contain errors 430ms

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

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

Scenario:
Check the taskomatic logs on server
425ms 1

Then the taskomatic logs should not contain errors 425ms

Scenario:
Check for out of memory errors
436ms 1

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

Feature:Debug the clients after the testsuite has run 1m 922ms 1

Scenario:
Extract the logs from all our clients
1m 922ms 1

When I extract the log files from all our active nodes 1m 922ms

@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