Feature: 0001 - Sanity checks

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

File name: allcli_sanity.feature

Relative path: core/allcli_sanity.feature

Scenarios

Chart

Status

Progress

Passed	75.00 %
Failed	8.33 %
Skipped	16.67 %

Total duration:

00:00:59.653

Scenario: The server is healthy

8
1
2
Duration: 00:00:07.339

Then "server" should have a FQDN 00:00:00.380

And reverse resolution should work for "server" 00:00:02.483

And the clock from "server" should be exact 00:00:04.476

+ Show Error

clocks differ by -2 seconds (StandardError)
./features/step_definitions/command_steps.rb:51:in `/^the clock from "([^"]*)" should be exact$/'
features/core/allcli_sanity.feature:11:in `the clock from "server" should be exact'

And service "apache2" is active on "server" 0s

And service "cobblerd" is active on "server" 0s

And service "rhn-search" is active on "server" 0s

And service "salt-api" is active on "server" 0s

And service "salt-master" is active on "server" 0s

And service "taskomatic" is active on "server" 0s

And socket "tftp" is active on "server" 0s

And service "tomcat" is active on "server" 0s

@proxy

Scenario: The proxy is healthy

Then "proxy" should have a FQDN 00:00:03.153

And reverse resolution should work for "proxy" 00:00:00.289

And "proxy" should communicate with the server using public interface 00:00:02.745

And the clock from "proxy" should be exact 00:00:00.289

@sle_minion

Scenario: The minion is healthy

Then "sle_minion" should have a FQDN 00:00:04.761

And reverse resolution should work for "sle_minion" 00:00:00.442

And "sle_minion" should communicate with the server using public interface 00:00:03.119

And the clock from "sle_minion" should be exact 00:00:00.460

@build_host

Scenario: The build host is healthy

Then "build_host" should have a FQDN 00:00:02.575

And reverse resolution should work for "build_host" 00:00:00.249

And "build_host" should communicate with the server using public interface 00:00:02.845

And the clock from "build_host" should be exact 00:00:00.239

@ssh_minion

Scenario: The SSH minion is healthy

Then "ssh_minion" should have a FQDN 00:00:04.668

And reverse resolution should work for "ssh_minion" 00:00:00.429

And "ssh_minion" should communicate with the server using public interface 00:00:03.285

And the clock from "ssh_minion" should be exact 00:00:00.416

@rhlike_minion

Scenario: The Red Hat-like minion is healthy

Then "rhlike_minion" should have a FQDN 00:00:02.329

And reverse resolution should work for "rhlike_minion" 00:00:00.215

And "rhlike_minion" should communicate with the server using public interface 00:00:02.818

And the clock from "rhlike_minion" should be exact 00:00:00.216

@deblike_minion

Scenario: The Debian-like minion is healthy

Then "deblike_minion" should have a FQDN 00:00:04.606

And reverse resolution should work for "deblike_minion" 00:00:00.209

And "deblike_minion" should communicate with the server using public interface 00:00:04.203

And the clock from "deblike_minion" should be exact 00:00:00.211

@skip_if_cloud

Scenario: The external resources can be reached

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

@auth_registry

Scenario: The registry with authentication is healthy

@no_auth_registry

Scenario: The registry without authentication is healthy

@custom_download_endpoint