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.806
And
reverse resolution should work for "server"
00:00:01.109
And
the clock from "server" should be exact
00:00:01.308
And
service "apache2" is active on "server"
00:00:01.249
And
service "cobblerd" is active on "server"
00:00:01.237
And
service "rhn-search" is active on "server"
00:00:01.254
And
service "salt-api" is active on "server"
00:00:01.269
And
service "salt-master" is active on "server"
00:00:01.292
And
service "taskomatic" is active on "server"
00:00:01.339
And
socket "tftp" is active on "server"
00:00:01.485
And
service "tomcat" is active on "server"
00:00:01.285
And
service "uyuni-update-config" is active on "server"
00:00:01.188
And
service "uyuni-check-database" is active on "server"
00:00:01.218
And
service "spacewalk-wait-for-tomcat" is active on "server"
00:00:01.098
And
service "spacewalk-wait-for-salt" is active on "server"
00:00:01.125
And
service "spacewalk-wait-for-taskomatic" is active on "server"
00:00:01.066
And
service "salt-secrets-config" is active on "server"
00:00:01.112
And
service "cobbler-refresh-mkloaders" is active on "server"
00:00:01.006
@containerized_server
@skip_if_rke2
Scenario: Podman containers are running
Then
podman container "uyuni-db" should be running on "server"
00:00:00.622
And
podman container "uyuni-db" should be healthy on "server"
00:00:00.594
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.569
And
podman container "uyuni-saline-0" should be running on "server"
00:00:00.561
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.557
And
podman container "uyuni-hub-xmlrpc-0" should be running on "server"
00:00:00.564
Then
"proxy" should have a FQDN
00:00:04.163
And
reverse resolution should work for "proxy"
00:00:00.392
And
"proxy" should communicate with the server using public interface
00:00:01.349
And
the clock from "proxy" should be exact
00:00:00.394
Then
"sle_minion" should have a FQDN
00:00:06.364
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.463
And
the clock from "sle_minion" should be exact
00:00:00.595
Then
"build_host" should have a FQDN
00:00:04.724
And
reverse resolution should work for "build_host"
00:00:00.448
And
"build_host" should communicate with the server using public interface
00:00:01.213
And
the clock from "build_host" should be exact
00:00:00.419
Then
"sshminion" should have a FQDN
00:00:06.351
And
reverse resolution should work for "sshminion"
00:00:00.607
And
"sshminion" should communicate with the server using public interface
00:00:01.937
And
the clock from "sshminion" should be exact
00:00:00.611
Then
"rhlike_minion" should have a FQDN
00:00:02.723
And
reverse resolution should work for "rhlike_minion"
00:00:00.237
And
"rhlike_minion" should communicate with the server using public interface
00:00:01.006
And
the clock from "rhlike_minion" should be exact
00:00:00.217
Then
"deblike_minion" should have a FQDN
00:00:05.688
And
reverse resolution should work for "deblike_minion"
00:00:00.245
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.242