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

Scenario: The server is healthy

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

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

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

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

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

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

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

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

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

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

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

@proxy

Scenario: The proxy is healthy

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

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

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

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

@sle_minion

Scenario: The minion is healthy

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

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

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

@build_host

Scenario: The build host is healthy

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

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

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

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

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

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

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

@rhlike_minion

Scenario: The Red Hat-like minion is healthy

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

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

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

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

@deblike_minion

Scenario: The Debian-like minion is healthy

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

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

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

@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