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

Scenario: The server is healthy

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

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

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

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

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

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

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

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

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

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

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

@proxy

Scenario: The proxy is healthy

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

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

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

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

@sle_minion

Scenario: The minion is healthy

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

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

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

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

@build_host

Scenario: The build host is healthy

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

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

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

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

@ssh_minion

Scenario: The SSH minion is healthy

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

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

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

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

@rhlike_minion

Scenario: The Red Hat-like minion is healthy

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

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

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

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

@deblike_minion

Scenario: The Debian-like minion is healthy

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

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

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

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

@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