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.712
And
reverse resolution should work for "server"
00:00:01.083
And
the clock from "server" should be exact
00:00:01.392
And
service "apache2" is active on "server"
00:00:01.358
And
service "cobblerd" is active on "server"
00:00:01.186
And
service "rhn-search" is active on "server"
00:00:01.239
And
service "salt-api" is active on "server"
00:00:01.341
And
service "salt-master" is active on "server"
00:00:01.221
And
service "taskomatic" is active on "server"
00:00:01.335
And
socket "tftp" is active on "server"
00:00:01.187
And
service "tomcat" is active on "server"
00:00:01.266
And
service "uyuni-update-config" is active on "server"
00:00:01.531
And
service "uyuni-check-database" is active on "server"
00:00:01.153
And
service "spacewalk-wait-for-tomcat" is active on "server"
00:00:01.308
And
service "spacewalk-wait-for-salt" is active on "server"
00:00:01.155
And
service "spacewalk-wait-for-taskomatic" is active on "server"
00:00:01.142
And
service "salt-secrets-config" is active on "server"
00:00:00.843
And
service "cobbler-refresh-mkloaders" is active on "server"
00:00:00.765
@containerized_server
@skip_if_rke2
Scenario: Podman containers are running
Then
podman container "uyuni-db" should be running on "server"
00:00:00.563
And
podman container "uyuni-db" should be healthy on "server"
00:00:00.575
And
podman container "uyuni-server" should be running on "server"
00:00:00.557
And
podman container "uyuni-server" should be healthy on "server"
00:00:00.562
And
podman container "uyuni-saline-0" should be running on "server"
00:00:00.570
And
podman container "uyuni-tftpd" should be running on "server"
00:00:00.558
And
podman container "uyuni-server-attestation-0" should be running on "server"
00:00:00.565
And
podman container "uyuni-hub-xmlrpc-0" should be running on "server"
00:00:00.558
Then
"proxy" should have a FQDN
00:00:04.248
And
reverse resolution should work for "proxy"
00:00:00.409
And
"proxy" should communicate with the server using public interface
00:00:01.214
And
the clock from "proxy" should be exact
00:00:00.401
Then
"sle_minion" should have a FQDN
00:00:06.260
And
reverse resolution should work for "sle_minion"
00:00:00.636
And
"sle_minion" should communicate with the server using public interface
00:00:01.409
And
the clock from "sle_minion" should be exact
00:00:00.591
Then
"build_host" should have a FQDN
00:00:04.363
And
reverse resolution should work for "build_host"
00:00:00.492
And
"build_host" should communicate with the server using public interface
00:00:01.270
And
the clock from "build_host" should be exact
00:00:00.399
Then
"sshminion" should have a FQDN
00:00:06.415
And
reverse resolution should work for "sshminion"
00:00:00.603
And
"sshminion" should communicate with the server using public interface
00:00:01.405
And
the clock from "sshminion" should be exact
00:00:00.590
Then
"rhlike_minion" should have a FQDN
00:00:02.194
And
reverse resolution should work for "rhlike_minion"
00:00:00.205
And
"rhlike_minion" should communicate with the server using public interface
00:00:00.985
And
the clock from "rhlike_minion" should be exact
00:00:00.190
Then
"deblike_minion" should have a FQDN
00:00:04.884
And
reverse resolution should work for "deblike_minion"
00:00:00.235
And
"deblike_minion" should communicate with the server using public interface
00:00:01.020
And
the clock from "deblike_minion" should be exact
00:00:00.231