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.871

Scenario: The server is healthy

8
1
2
Duration: 00:00:07.920

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

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

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

+ 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.047

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

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

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

@sle_minion

Scenario: The minion is healthy

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

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

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

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

@build_host

Scenario: The build host is healthy

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

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

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

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

@ssh_minion

Scenario: The SSH minion is healthy

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

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

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

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

@rhlike_minion

Scenario: The Red Hat-like minion is healthy

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

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

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

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

@deblike_minion

Scenario: The Debian-like minion is healthy

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

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

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

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

@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