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

Scenario: The server is healthy

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

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

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

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

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

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

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

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

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

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

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

@proxy

Scenario: The proxy is healthy

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

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

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

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

@sle_minion

Scenario: The minion is healthy

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

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

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

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

@build_host

Scenario: The build host is healthy

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

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

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

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

@ssh_minion

Scenario: The SSH minion is healthy

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

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

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

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

@rhlike_minion

Scenario: The Red Hat-like minion is healthy

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

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

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

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

@deblike_minion

Scenario: The Debian-like minion is healthy

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

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

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

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

@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