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.778
And
reverse resolution should work for "server"
00:00:01.114
And
the clock from "server" should be exact
00:00:01.342
And
service "apache2" is active on "server"
00:00:01.151
And
service "cobblerd" is active on "server"
00:00:01.210
And
service "rhn-search" is active on "server"
00:00:01.200
And
service "salt-api" is active on "server"
00:00:01.303
And
service "salt-master" is active on "server"
00:00:01.286
And
service "taskomatic" is active on "server"
00:00:01.219
And
socket "tftp" is active on "server"
00:00:01.415
And
service "tomcat" is active on "server"
00:00:01.238
And
service "uyuni-update-config" is active on "server"
00:00:01.218
And
service "uyuni-check-database" is active on "server"
00:00:01.224
And
service "spacewalk-wait-for-tomcat" is active on "server"
00:00:01.210
And
service "spacewalk-wait-for-salt" is active on "server"
00:00:01.152
And
service "spacewalk-wait-for-taskomatic" is active on "server"
00:00:01.752
And
service "salt-secrets-config" is active on "server"
00:00:01.012
And
service "cobbler-refresh-mkloaders" is active on "server"
00:00:00.777
@containerized_server
@skip_if_rke2
Scenario: Podman containers are running
Then
podman container "uyuni-db" should be running on "server"
00:00:00.616
And
podman container "uyuni-db" should be healthy on "server"
00:00:00.560
And
podman container "uyuni-server" should be running on "server"
00:00:00.566
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.552
And
podman container "uyuni-tftpd" should be running on "server"
00:00:00.574
And
podman container "uyuni-server-attestation-0" should be running on "server"
00:00:00.552
And
podman container "uyuni-hub-xmlrpc-0" should be running on "server"
00:00:00.550
Then
"proxy" should have a FQDN
00:00:04.149
And
reverse resolution should work for "proxy"
00:00:00.395
And
"proxy" should communicate with the server using public interface
00:00:01.166
And
the clock from "proxy" should be exact
00:00:00.391
Then
"sle_minion" should have a FQDN
00:00:06.456
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.478
And
the clock from "sle_minion" should be exact
00:00:00.611
Then
"build_host" should have a FQDN
00:00:04.280
And
reverse resolution should work for "build_host"
00:00:00.477
And
"build_host" should communicate with the server using public interface
00:00:01.258
And
the clock from "build_host" should be exact
00:00:00.393
Then
"sshminion" should have a FQDN
00:00:06.901
And
reverse resolution should work for "sshminion"
00:00:00.599
And
"sshminion" should communicate with the server using public interface
00:00:01.404
And
the clock from "sshminion" should be exact
00:00:00.583
Then
"rhlike_minion" should have a FQDN
00:00:02.325
And
reverse resolution should work for "rhlike_minion"
00:00:00.218
And
"rhlike_minion" should communicate with the server using public interface
00:00:01.015
And
the clock from "rhlike_minion" should be exact
00:00:00.205
Then
"deblike_minion" should have a FQDN
00:00:05.250
And
reverse resolution should work for "deblike_minion"
00:00:00.239
And
"deblike_minion" should communicate with the server using public interface
00:00:01.026
And
the clock from "deblike_minion" should be exact
00:00:00.218