All Scenarios

21

Passed Scenarios

15

Failed Scenarios

1

Skipped Scenarios

5

Execution Time: 3m 9s 788ms

Expand All | Collapse All

Metadata

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

Feature:Sanity checks 1m 36s 242ms 9 1 2

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

Scenario:
The server is healthy
54s 634ms 19

Then "server" should have a FQDN 383ms

And reverse resolution should work for "server" 29s 252ms

And the clock from "server" should be exact 1s 238ms

And service "apache2" is enabled on "server" 1s 43ms

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

And service "cobblerd" is enabled on "server" 1s 35ms

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

And service "rhn-search" is enabled on "server" 1s 389ms

And service "rhn-search" is active on "server" 1s 565ms

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

And service "salt-api" is active on "server" 1s 154ms

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

And service "salt-master" is active on "server" 1s 285ms

And service "taskomatic" is enabled on "server" 1s 184ms

And service "taskomatic" is active on "server" 1s 852ms

And socket "tftp" is enabled on "server" 1s 158ms

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

And service "tomcat" is enabled on "server" 4s 210ms

And service "tomcat" is active on "server" 1s 633ms

@proxy
Scenario:
The proxy is healthy
14s 604ms 2 1 1

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

And reverse resolution should work for "proxy" 357ms

And "proxy" should communicate with the server using public interface 11s 325ms Show Error + 
                                            
 FAIL: mgrctl exec -i 'ping -n -c 1 172.16.3.7' returned status code = 1.
Output:
PING 172.16.3.7 (172.16.3.7) 56(84) bytes of data.

--- 172.16.3.7 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms

 (ScriptError)
./features/support/remote_node.rb:169:in `run_local'
./features/support/remote_node.rb:117:in `run'
./features/step_definitions/retail_steps.rb:55:in `/^"([^"]*)" should communicate with the server using public interface$/'
features/core/allcli_sanity.feature:33:in `"proxy" should communicate with the server using public interface'

And the clock from "proxy" should be exact 0s

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

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

And reverse resolution should work for "sle_minion" 408ms

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

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

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

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

And reverse resolution should work for "build_host" 212ms

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

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

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

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

And reverse resolution should work for "ssh_minion" 385ms

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

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

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

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

And reverse resolution should work for "rhlike_minion" 183ms

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

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

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

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

And reverse resolution should work for "deblike_minion" 222ms

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

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

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

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

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

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

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

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

@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 13s 350ms 5

Scenario:
Call spacewalk-debug on server
9s 713ms 1

When I execute spacewalk-debug on the server 9s 713ms

Scenario:
Check the tomcat logs on server
636ms 1

Then the tomcat logs should not contain errors 636ms

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

Then the salt event log on server should contain no failures 1s 686ms

Scenario:
Check the taskomatic logs on server
644ms 1

Then the taskomatic logs should not contain errors 644ms

Scenario:
Check for out of memory errors
669ms 1

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

Feature:Debug the clients after the testsuite has run 1m 20s 194ms 1

Scenario:
Extract the logs from all our clients
1m 20s 194ms 1

When I extract the log files from all our active nodes 1m 20s 194ms

@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