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	83.33 %
Failed	0.00 %
Skipped	16.67 %

Total duration:

00:01:22.006

Scenario: The server is healthy

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

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

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

And service "apache2" is active on "server" 00:00:02.489

And service "cobblerd" is active on "server" 00:00:02.492

And service "rhn-search" is active on "server" 00:00:02.501

And service "salt-api" is active on "server" 00:00:04.908

And service "salt-master" is active on "server" 00:00:02.860

And service "taskomatic" is active on "server" 00:00:02.420

And socket "tftp" is active on "server" 00:00:02.500

And service "tomcat" is active on "server" 00:00:02.600

@proxy

Scenario: The proxy is healthy

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

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

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

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

@sle_minion

Scenario: The minion is healthy

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

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

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

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

@build_host

Scenario: The build host is healthy

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

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

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

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

@ssh_minion

Scenario: The SSH minion is healthy

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

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

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

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

@rhlike_minion

Scenario: The Red Hat-like minion is healthy

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

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

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

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

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

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

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

@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