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.751
And
reverse resolution should work for "server"
00:00:01.469
And
the clock from "server" should be exact
00:00:01.287
And
service "apache2" is active on "server"
00:00:01.288
And
service "cobblerd" is active on "server"
00:00:01.338
And
service "rhn-search" is active on "server"
00:00:01.194
And
service "salt-api" is active on "server"
00:00:01.278
And
service "salt-master" is active on "server"
00:00:01.237
And
service "taskomatic" is active on "server"
00:00:01.303
And
socket "tftp" is active on "server"
00:00:01.505
And
service "tomcat" is active on "server"
00:00:01.413
And
service "uyuni-update-config" is active on "server"
00:00:01.277
And
service "uyuni-check-database" is active on "server"
00:00:01.193
And
service "spacewalk-wait-for-tomcat" is active on "server"
00:00:01.235
And
service "spacewalk-wait-for-salt" is active on "server"
00:00:01.217
And
service "spacewalk-wait-for-taskomatic" is active on "server"
00:00:00.829
And
service "salt-secrets-config" is active on "server"
00:00:00.769
And
service "cobbler-refresh-mkloaders" is active on "server"
00:00:00.755
@containerized_server
@skip_if_rke2
Scenario: Podman containers are running
Then
podman container "uyuni-db" should be running on "server"
00:00:00.550
And
podman container "uyuni-db" should be healthy on "server"
00:00:00.561
And
podman container "uyuni-server" should be running on "server"
00:00:00.558
And
podman container "uyuni-server" should be healthy on "server"
00:00:00.615
And
podman container "uyuni-saline-0" should be running on "server"
00:00:00.556
And
podman container "uyuni-tftpd" should be running on "server"
00:00:00.562
And
podman container "uyuni-server-attestation-0" should be running on "server"
00:00:00.553
And
podman container "uyuni-hub-xmlrpc-0" should be running on "server"
00:00:00.551
Then
"proxy" should have a FQDN
00:00:04.215
And
reverse resolution should work for "proxy"
00:00:00.403
And
"proxy" should communicate with the server using public interface
00:00:01.282
And
the clock from "proxy" should be exact
00:00:00.401
Then
"sle_minion" should have a FQDN
00:00:06.057
And
reverse resolution should work for "sle_minion"
00:00:00.575
And
"sle_minion" should communicate with the server using public interface
00:00:01.351
And
the clock from "sle_minion" should be exact
00:00:00.569
Then
"build_host" should have a FQDN
00:00:04.383
And
reverse resolution should work for "build_host"
00:00:00.412
And
"build_host" should communicate with the server using public interface
00:00:01.218
And
the clock from "build_host" should be exact
00:00:00.423
Then
"sshminion" should have a FQDN
00:00:06.161
And
reverse resolution should work for "sshminion"
00:00:00.583
And
"sshminion" should communicate with the server using public interface
00:00:01.418
And
the clock from "sshminion" should be exact
00:00:00.583
Then
"rhlike_minion" should have a FQDN
00:00:02.345
And
reverse resolution should work for "rhlike_minion"
00:00:00.208
And
"rhlike_minion" should communicate with the server using public interface
00:00:01.022
And
the clock from "rhlike_minion" should be exact
00:00:00.205
Then
"deblike_minion" should have a FQDN
00:00:05.355
And
reverse resolution should work for "deblike_minion"
00:00:00.246
And
"deblike_minion" should communicate with the server using public interface
00:00:01.105
And
the clock from "deblike_minion" should be exact
00:00:00.272