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	84.62 %
Failed	0.00 %
Skipped	15.38 %

Total duration:

00:00:50.658

Scenario: The server is healthy

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

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

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

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

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

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

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

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

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

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

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

@containerized_server

Scenario: Podman containers are running

Then podman container "uyuni-db" should be running on "server" 00:00:00.672

And podman container "uyuni-db" should be healthy on "server" 00:00:00.637

And podman container "uyuni-server" should be running on "server" 00:00:00.656

And podman container "uyuni-server" should be healthy on "server" 00:00:00.653

And podman container "uyuni-saline-0" should be running on "server" 00:00:00.633

And podman container "uyuni-tftpd" should be running on "server" 00:00:00.654

And podman container "uyuni-server-attestation-0" should be running on "server" 00:00:00.604

And podman container "uyuni-hub-xmlrpc-0" should be running on "server" 00:00:00.653

@proxy

Scenario: The proxy is healthy

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

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

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

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

@sle_minion

Scenario: The minion is healthy

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

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

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

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

@build_host

Scenario: The build host is healthy

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

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

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

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

@sshminion

Scenario: The SSH minion is healthy

Then "sshminion" should have a FQDN 00:00:04.680

And reverse resolution should work for "sshminion" 00:00:00.473

And "sshminion" should communicate with the server using public interface 00:00:01.105

And the clock from "sshminion" should be exact 00:00:00.440

@rhlike_minion

Scenario: The Red Hat-like minion is healthy

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

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

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

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

@deblike_minion

Scenario: The Debian-like minion is healthy

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

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

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

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

@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