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.885
And
reverse resolution should work for "server"
00:00:01.190
And
the clock from "server" should be exact
00:00:01.363
And
service "apache2" is active on "server"
00:00:01.241
And
service "cobblerd" is active on "server"
00:00:01.253
And
service "rhn-search" is active on "server"
00:00:01.251
And
service "salt-api" is active on "server"
00:00:01.300
And
service "salt-master" is active on "server"
00:00:01.264
And
service "taskomatic" is active on "server"
00:00:01.468
And
socket "tftp" is active on "server"
00:00:01.278
And
service "tomcat" is active on "server"
00:00:01.367
And
service "uyuni-update-config" is active on "server"
00:00:01.254
And
service "uyuni-check-database" is active on "server"
00:00:01.272
And
service "spacewalk-wait-for-tomcat" is active on "server"
00:00:01.120
And
service "spacewalk-wait-for-salt" is active on "server"
00:00:01.202
And
service "spacewalk-wait-for-taskomatic" is active on "server"
00:00:00.922
And
service "salt-secrets-config" is active on "server"
00:00:00.854
And
service "cobbler-refresh-mkloaders" is active on "server"
00:00:00.850
@containerized_server
@skip_if_rke2
Scenario: Podman containers are running
Then
podman container "uyuni-db" should be running on "server"
00:00:00.685
And
podman container "uyuni-db" should be healthy on "server"
00:00:00.562
And
podman container "uyuni-server" should be running on "server"
00:00:00.559
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.587
And
podman container "uyuni-tftpd" should be running on "server"
00:00:00.566
And
podman container "uyuni-server-attestation-0" should be running on "server"
00:00:00.563
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.165
And
reverse resolution should work for "proxy"
00:00:00.396
And
"proxy" should communicate with the server using public interface
00:00:01.179
And
the clock from "proxy" should be exact
00:00:00.393
Then
"sle_minion" should have a FQDN
00:00:06.363
And
reverse resolution should work for "sle_minion"
00:00:00.602
And
"sle_minion" should communicate with the server using public interface
00:00:01.421
And
the clock from "sle_minion" should be exact
00:00:00.594
Then
"build_host" should have a FQDN
00:00:04.667
And
reverse resolution should work for "build_host"
00:00:00.431
And
"build_host" should communicate with the server using public interface
00:00:01.212
And
the clock from "build_host" should be exact
00:00:00.414
Then
"sshminion" should have a FQDN
00:00:06.032
And
reverse resolution should work for "sshminion"
00:00:00.577
And
"sshminion" should communicate with the server using public interface
00:00:01.437
And
the clock from "sshminion" should be exact
00:00:00.567
Then
"rhlike_minion" should have a FQDN
00:00:02.465
And
reverse resolution should work for "rhlike_minion"
00:00:00.214
And
"rhlike_minion" should communicate with the server using public interface
00:00:00.987
And
the clock from "rhlike_minion" should be exact
00:00:00.217
Then
"deblike_minion" should have a FQDN
00:00:04.715
And
reverse resolution should work for "deblike_minion"
00:00:00.211
And
"deblike_minion" should communicate with the server using public interface
00:00:01.065
And
the clock from "deblike_minion" should be exact
00:00:00.206