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:19.936

Scenario: The server is healthy

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

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

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

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

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

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

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

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

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

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

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

@proxy

Scenario: The proxy is healthy

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

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

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

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

@sle_minion

Scenario: The minion is healthy

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

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

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

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

@build_host

Scenario: The build host is healthy

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

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

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

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

@ssh_minion

Scenario: The SSH minion is healthy

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

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

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

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

@rhlike_minion

Scenario: The Red Hat-like minion is healthy

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

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

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

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

@deblike_minion

Scenario: The Debian-like minion is healthy

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

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

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

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

@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