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.697
And
reverse resolution should work for "server"
00:00:01.474
And
the clock from "server" should be exact
00:00:01.653
And
service "apache2" is active on "server"
00:00:01.650
And
service "cobblerd" is active on "server"
00:00:01.532
And
service "rhn-search" is active on "server"
00:00:01.654
And
service "salt-api" is active on "server"
00:00:01.728
And
service "salt-master" is active on "server"
00:00:01.552
And
service "taskomatic" is active on "server"
00:00:01.580
And
socket "tftp" is active on "server"
00:00:01.618
And
service "tomcat" is active on "server"
00:00:01.635
And
service "uyuni-update-config" is active on "server"
00:00:01.503
And
service "uyuni-check-database" is active on "server"
00:00:01.855
And
service "spacewalk-wait-for-tomcat" is active on "server"
00:00:01.150
And
service "spacewalk-wait-for-salt" is active on "server"
00:00:00.921
And
service "spacewalk-wait-for-taskomatic" is active on "server"
00:00:00.913
And
service "salt-secrets-config" is active on "server"
00:00:00.907
And
service "cobbler-refresh-mkloaders" is active on "server"
00:00:00.930
@containerized_server
@skip_if_rke2
Scenario: Podman containers are running
Then
podman container "uyuni-db" should be running on "server"
00:00:00.636
And
podman container "uyuni-db" should be healthy on "server"
00:00:00.684
And
podman container "uyuni-server" should be running on "server"
00:00:00.609
And
podman container "uyuni-server" should be healthy on "server"
00:00:00.602
And
podman container "uyuni-saline-0" should be running on "server"
00:00:00.619
And
podman container "uyuni-tftpd" should be running on "server"
00:00:00.616
And
podman container "uyuni-server-attestation-0" should be running on "server"
00:00:00.613
And
podman container "uyuni-hub-xmlrpc-0" should be running on "server"
00:00:00.613
Then
"proxy" should have a FQDN
00:00:04.165
And
reverse resolution should work for "proxy"
00:00:00.397
And
"proxy" should communicate with the server using public interface
00:00:01.308
And
the clock from "proxy" should be exact
00:00:00.391
Then
"sle_minion" should have a FQDN
00:00:06.085
And
reverse resolution should work for "sle_minion"
00:00:00.579
And
"sle_minion" should communicate with the server using public interface
00:00:01.501
And
the clock from "sle_minion" should be exact
00:00:00.570
Then
"build_host" should have a FQDN
00:00:04.416
And
reverse resolution should work for "build_host"
00:00:00.499
And
"build_host" should communicate with the server using public interface
00:00:01.436
And
the clock from "build_host" should be exact
00:00:00.429
Then
"sshminion" should have a FQDN
00:00:06.079
And
reverse resolution should work for "sshminion"
00:00:00.579
And
"sshminion" should communicate with the server using public interface
00:00:01.488
And
the clock from "sshminion" should be exact
00:00:00.571
Then
"rhlike_minion" should have a FQDN
00:00:02.310
And
reverse resolution should work for "rhlike_minion"
00:00:00.216
And
"rhlike_minion" should communicate with the server using public interface
00:00:01.156
And
the clock from "rhlike_minion" should be exact
00:00:00.217
Then
"deblike_minion" should have a FQDN
00:00:04.869
And
reverse resolution should work for "deblike_minion"
00:00:00.219
And
"deblike_minion" should communicate with the server using public interface
00:00:01.191
And
the clock from "deblike_minion" should be exact
00:00:00.230