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.696
And
reverse resolution should work for "server"
00:00:01.358
And
the clock from "server" should be exact
00:00:01.484
And
service "apache2" is active on "server"
00:00:01.453
And
service "cobblerd" is active on "server"
00:00:01.669
And
service "rhn-search" is active on "server"
00:00:01.631
And
service "salt-api" is active on "server"
00:00:01.542
And
service "salt-master" is active on "server"
00:00:01.590
And
service "taskomatic" is active on "server"
00:00:01.573
And
socket "tftp" is active on "server"
00:00:01.487
And
service "tomcat" is active on "server"
00:00:01.389
And
service "uyuni-update-config" is active on "server"
00:00:01.595
And
service "uyuni-check-database" is active on "server"
00:00:01.402
And
service "spacewalk-wait-for-tomcat" is active on "server"
00:00:01.209
And
service "spacewalk-wait-for-salt" is active on "server"
00:00:00.984
And
service "spacewalk-wait-for-taskomatic" is active on "server"
00:00:00.928
And
service "salt-secrets-config" is active on "server"
00:00:00.905
And
service "cobbler-refresh-mkloaders" is active on "server"
00:00:00.902
@containerized_server
@skip_if_rke2
Scenario: Podman containers are running
Then
podman container "uyuni-db" should be running on "server"
00:00:00.633
And
podman container "uyuni-db" should be healthy on "server"
00:00:00.612
And
podman container "uyuni-server" should be running on "server"
00:00:00.602
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.613
And
podman container "uyuni-tftpd" should be running on "server"
00:00:00.640
And
podman container "uyuni-server-attestation-0" should be running on "server"
00:00:00.623
And
podman container "uyuni-hub-xmlrpc-0" should be running on "server"
00:00:00.629
Then
"proxy" should have a FQDN
00:00:04.202
And
reverse resolution should work for "proxy"
00:00:00.401
And
"proxy" should communicate with the server using public interface
00:00:01.391
And
the clock from "proxy" should be exact
00:00:00.399
Then
"sle_minion" should have a FQDN
00:00:06.098
And
reverse resolution should work for "sle_minion"
00:00:00.581
And
"sle_minion" should communicate with the server using public interface
00:00:01.537
And
the clock from "sle_minion" should be exact
00:00:00.584
Then
"build_host" should have a FQDN
00:00:04.416
And
reverse resolution should work for "build_host"
00:00:00.421
And
"build_host" should communicate with the server using public interface
00:00:01.750
And
the clock from "build_host" should be exact
00:00:00.431
Then
"sshminion" should have a FQDN
00:00:07.113
And
reverse resolution should work for "sshminion"
00:00:00.698
And
"sshminion" should communicate with the server using public interface
00:00:01.688
And
the clock from "sshminion" should be exact
00:00:00.654
Then
"rhlike_minion" should have a FQDN
00:00:02.330
And
reverse resolution should work for "rhlike_minion"
00:00:00.211
And
"rhlike_minion" should communicate with the server using public interface
00:00:01.182
And
the clock from "rhlike_minion" should be exact
00:00:00.206
Then
"deblike_minion" should have a FQDN
00:00:04.636
And
reverse resolution should work for "deblike_minion"
00:00:00.208
And
"deblike_minion" should communicate with the server using public interface
00:00:01.216
And
the clock from "deblike_minion" should be exact
00:00:00.212