All Scenarios

21

Passed Scenarios

15

Failed Scenarios

1

Skipped Scenarios

5

Execution Time: 3m 9s 788ms

Expand All | Collapse All

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

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

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

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

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

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

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

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

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

Then it should be possible to use the HTTP proxy 0s

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

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

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

In order for the server to behave correctly after a reboot
I want to be sure that there is no wrong SELinux label

Then files on container volumes should all have the proper SELinux label 0s

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

Then the tomcat logs should not contain errors 636ms

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

Then the taskomatic logs should not contain errors 644ms

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

Then the word "scc.suse.com" does not occur more than 100 times in "/var/log/rhn/rhn_web_ui.log" on "server" 0s

Then the word "scc.suse.com" does not occur more than 50 times in "/var/log/rhn/rhn_taskomatic_daemon.log" on "server" 0s