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.667
And
reverse resolution should work for "server"
00:00:01.426
And
the clock from "server" should be exact
00:00:01.675
And
service "apache2" is active on "server"
00:00:01.539
And
service "cobblerd" is active on "server"
00:00:01.443
And
service "rhn-search" is active on "server"
00:00:01.576
And
service "salt-api" is active on "server"
00:00:01.664
And
service "salt-master" is active on "server"
00:00:01.566
And
service "taskomatic" is active on "server"
00:00:01.532
And
socket "tftp" is active on "server"
00:00:01.913
And
service "tomcat" is active on "server"
00:00:01.589
And
service "uyuni-update-config" is active on "server"
00:00:01.471
And
service "uyuni-check-database" is active on "server"
00:00:01.195
And
service "spacewalk-wait-for-tomcat" is active on "server"
00:00:01.006
And
service "spacewalk-wait-for-salt" is active on "server"
00:00:00.899
And
service "spacewalk-wait-for-taskomatic" is active on "server"
00:00:00.907
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.903
@containerized_server
@skip_if_rke2
Scenario: Podman containers are running
Then
podman container "uyuni-db" should be running on "server"
00:00:00.597
And
podman container "uyuni-db" should be healthy on "server"
00:00:00.688
And
podman container "uyuni-server" should be running on "server"
00:00:01.222
And
podman container "uyuni-server" should be healthy on "server"
00:00:00.662
And
podman container "uyuni-saline-0" should be running on "server"
00:00:00.647
And
podman container "uyuni-tftpd" should be running on "server"
00:00:00.660
And
podman container "uyuni-server-attestation-0" should be running on "server"
00:00:00.603
And
podman container "uyuni-hub-xmlrpc-0" should be running on "server"
00:00:00.600
Then
"proxy" should have a FQDN
00:00:04.187
And
reverse resolution should work for "proxy"
00:00:00.400
And
"proxy" should communicate with the server using public interface
00:00:01.479
And
the clock from "proxy" should be exact
00:00:00.396
Then
"sle_minion" should have a FQDN
00:00:06.216
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.550
And
the clock from "sle_minion" should be exact
00:00:00.589
Then
"build_host" should have a FQDN
00:00:04.486
And
reverse resolution should work for "build_host"
00:00:00.509
And
"build_host" should communicate with the server using public interface
00:00:01.409
And
the clock from "build_host" should be exact
00:00:00.445
Then
"sshminion" should have a FQDN
00:00:06.925
And
reverse resolution should work for "sshminion"
00:00:00.629
And
"sshminion" should communicate with the server using public interface
00:00:01.517
And
the clock from "sshminion" should be exact
00:00:00.613
Then
"rhlike_minion" should have a FQDN
00:00:02.251
And
reverse resolution should work for "rhlike_minion"
00:00:00.210
And
"rhlike_minion" should communicate with the server using public interface
00:00:01.116
And
the clock from "rhlike_minion" should be exact
00:00:00.201
Then
"deblike_minion" should have a FQDN
00:00:04.882
And
reverse resolution should work for "deblike_minion"
00:00:00.223
And
"deblike_minion" should communicate with the server using public interface
00:00:01.124
And
the clock from "deblike_minion" should be exact
00:00:00.223