All Scenarios

24

Passed Scenarios

18

Failed Scenarios

1

Skipped Scenarios

5

Execution Time: 6m 7s 163ms

Expand All | Collapse All

Metadata

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

Feature:Sanity checks 32s 477ms 10 2

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

Scenario:
The server is healthy
7s 48ms 19

Then "server" should have a FQDN 201ms

And reverse resolution should work for "server" 383ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

And reverse resolution should work for "proxy" 177ms

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

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

@sle_minion
Scenario:
The minion is healthy
5s 320ms 4

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

And reverse resolution should work for "sle_minion" 283ms

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

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

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

Then "build_host" should have a FQDN 1s 994ms

And reverse resolution should work for "build_host" 199ms

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

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

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

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

And reverse resolution should work for "ssh_minion" 235ms

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

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

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

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

And reverse resolution should work for "rhlike_minion" 209ms

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

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

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

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

And reverse resolution should work for "deblike_minion" 221ms

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

Scenario:
Check the tomcat logs on server
411ms 1

Then the tomcat logs should not contain errors 411ms

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

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

Scenario:
Check the taskomatic logs on server
423ms 1

Then the taskomatic logs should not contain errors 423ms

Scenario:
Check for out of memory errors
412ms 1

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

Feature:Debug the clients after the testsuite has run 59s 909ms 1

Scenario:
Extract the logs from all our clients
59s 909ms 1

When I extract the log files from all our active nodes 59s 909ms

@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