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.867
And
reverse resolution should work for "server"
00:00:01.080
And
the clock from "server" should be exact
00:00:01.338
And
service "apache2" is active on "server"
00:00:01.166
And
service "cobblerd" is active on "server"
00:00:01.282
And
service "rhn-search" is active on "server"
00:00:01.416
And
service "salt-api" is active on "server"
00:00:01.277
And
service "salt-master" is active on "server"
00:00:01.194
And
service "taskomatic" is active on "server"
00:00:01.478
And
socket "tftp" is active on "server"
00:00:01.324
And
service "tomcat" is active on "server"
00:00:01.148
And
service "uyuni-update-config" is active on "server"
00:00:01.190
And
service "uyuni-check-database" is active on "server"
00:00:01.188
And
service "spacewalk-wait-for-tomcat" is active on "server"
00:00:01.452
And
service "spacewalk-wait-for-salt" is active on "server"
00:00:01.078
And
service "spacewalk-wait-for-taskomatic" is active on "server"
00:00:01.187
And
service "salt-secrets-config" is active on "server"
00:00:01.397
And
service "cobbler-refresh-mkloaders" is active on "server"
00:00:00.973
@containerized_server
@skip_if_rke2
Scenario: Podman containers are running
Then
podman container "uyuni-db" should be running on "server"
00:00:00.605
And
podman container "uyuni-db" should be healthy on "server"
00:00:00.577
And
podman container "uyuni-server" should be running on "server"
00:00:00.551
And
podman container "uyuni-server" should be healthy on "server"
00:00:00.553
And
podman container "uyuni-saline-0" should be running on "server"
00:00:00.549
And
podman container "uyuni-tftpd" should be running on "server"
00:00:00.560
And
podman container "uyuni-server-attestation-0" should be running on "server"
00:00:00.555
And
podman container "uyuni-hub-xmlrpc-0" should be running on "server"
00:00:00.549
Then
"proxy" should have a FQDN
00:00:04.153
And
reverse resolution should work for "proxy"
00:00:00.398
And
"proxy" should communicate with the server using public interface
00:00:01.330
And
the clock from "proxy" should be exact
00:00:00.394
Then
"sle_minion" should have a FQDN
00:00:06.417
And
reverse resolution should work for "sle_minion"
00:00:00.617
And
"sle_minion" should communicate with the server using public interface
00:00:01.405
And
the clock from "sle_minion" should be exact
00:00:00.589
Then
"build_host" should have a FQDN
00:00:04.753
And
reverse resolution should work for "build_host"
00:00:00.496
And
"build_host" should communicate with the server using public interface
00:00:01.284
And
the clock from "build_host" should be exact
00:00:00.444
Then
"sshminion" should have a FQDN
00:00:06.518
And
reverse resolution should work for "sshminion"
00:00:00.617
And
"sshminion" should communicate with the server using public interface
00:00:01.440
And
the clock from "sshminion" should be exact
00:00:00.616
Then
"rhlike_minion" should have a FQDN
00:00:02.403
And
reverse resolution should work for "rhlike_minion"
00:00:00.207
And
"rhlike_minion" should communicate with the server using public interface
00:00:00.983
And
the clock from "rhlike_minion" should be exact
00:00:00.202
Then
"deblike_minion" should have a FQDN
00:00:05.027
And
reverse resolution should work for "deblike_minion"
00:00:00.218
And
"deblike_minion" should communicate with the server using public interface
00:00:00.989
And
the clock from "deblike_minion" should be exact
00:00:00.213