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
Then
"server" should have a FQDN
00:00:00.729
And
reverse resolution should work for "server"
00:00:01.387
And
the clock from "server" should be exact
00:00:01.532
And
service "apache2" is active on "server"
00:00:01.673
And
service "cobblerd" is active on "server"
00:00:01.644
And
service "rhn-search" is active on "server"
00:00:01.512
And
service "salt-api" is active on "server"
00:00:01.497
And
service "salt-master" is active on "server"
00:00:01.529
And
service "taskomatic" is active on "server"
00:00:01.493
And
socket "tftp" is active on "server"
00:00:01.491
And
service "tomcat" is active on "server"
00:00:01.657
And
service "uyuni-update-config" is active on "server"
00:00:01.603
And
service "uyuni-check-database" is active on "server"
00:00:01.885
And
service "spacewalk-wait-for-tomcat" is active on "server"
00:00:01.347
And
service "spacewalk-wait-for-salt" is active on "server"
00:00:00.893
And
service "spacewalk-wait-for-taskomatic" is active on "server"
00:00:00.909
And
service "salt-secrets-config" is active on "server"
00:00:00.898
And
service "cobbler-refresh-mkloaders" is active on "server"
00:00:00.916
@containerized_server
@skip_if_rke2
Scenario: Podman containers are running
Then
podman container "uyuni-db" should be running on "server"
00:00:00.591
And
podman container "uyuni-db" should be healthy on "server"
00:00:00.604
And
podman container "uyuni-server" should be running on "server"
00:00:00.625
And
podman container "uyuni-server" should be healthy on "server"
00:00:00.604
And
podman container "uyuni-saline-0" should be running on "server"
00:00:00.608
And
podman container "uyuni-tftpd" should be running on "server"
00:00:00.608
And
podman container "uyuni-server-attestation-0" should be running on "server"
00:00:00.647
And
podman container "uyuni-hub-xmlrpc-0" should be running on "server"
00:00:00.593
Then
"proxy" should have a FQDN
00:00:04.129
And
reverse resolution should work for "proxy"
00:00:00.397
And
"proxy" should communicate with the server using public interface
00:00:01.384
And
the clock from "proxy" should be exact
00:00:00.388
Then
"sle_minion" should have a FQDN
00:00:06.279
And
reverse resolution should work for "sle_minion"
00:00:00.598
And
"sle_minion" should communicate with the server using public interface
00:00:01.539
And
the clock from "sle_minion" should be exact
00:00:00.588
Then
"build_host" should have a FQDN
00:00:04.503
And
reverse resolution should work for "build_host"
00:00:00.426
And
"build_host" should communicate with the server using public interface
00:00:01.385
And
the clock from "build_host" should be exact
00:00:00.447
Then
"sshminion" should have a FQDN
00:00:06.252
And
reverse resolution should work for "sshminion"
00:00:00.590
And
"sshminion" should communicate with the server using public interface
00:00:01.522
And
the clock from "sshminion" should be exact
00:00:00.593
Then
"rhlike_minion" should have a FQDN
00:00:02.744
And
reverse resolution should work for "rhlike_minion"
00:00:00.241
And
"rhlike_minion" should communicate with the server using public interface
00:00:01.144
And
the clock from "rhlike_minion" should be exact
00:00:00.218
Then
"deblike_minion" should have a FQDN
00:00:05.324
And
reverse resolution should work for "deblike_minion"
00:00:00.236
And
"deblike_minion" should communicate with the server using public interface
00:00:01.128
And
the clock from "deblike_minion" should be exact
00:00:00.227