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.730
And
reverse resolution should work for "server"
00:00:01.109
And
the clock from "server" should be exact
00:00:01.385
And
service "apache2" is active on "server"
00:00:01.204
And
service "cobblerd" is active on "server"
00:00:01.263
And
service "rhn-search" is active on "server"
00:00:01.130
And
service "salt-api" is active on "server"
00:00:01.141
And
service "salt-master" is active on "server"
00:00:01.343
And
service "taskomatic" is active on "server"
00:00:01.525
And
socket "tftp" is active on "server"
00:00:01.254
And
service "tomcat" is active on "server"
00:00:01.219
And
service "uyuni-update-config" is active on "server"
00:00:01.315
And
service "uyuni-check-database" is active on "server"
00:00:01.163
And
service "spacewalk-wait-for-tomcat" is active on "server"
00:00:01.169
And
service "spacewalk-wait-for-salt" is active on "server"
00:00:01.543
And
service "spacewalk-wait-for-taskomatic" is active on "server"
00:00:01.277
And
service "salt-secrets-config" is active on "server"
00:00:00.750
And
service "cobbler-refresh-mkloaders" is active on "server"
00:00:00.780
@containerized_server
@skip_if_rke2
Scenario: Podman containers are running
Then
podman container "uyuni-db" should be running on "server"
00:00:00.547
And
podman container "uyuni-db" should be healthy on "server"
00:00:00.548
And
podman container "uyuni-server" should be running on "server"
00:00:00.551
And
podman container "uyuni-server" should be healthy on "server"
00:00:00.549
And
podman container "uyuni-saline-0" should be running on "server"
00:00:00.565
And
podman container "uyuni-tftpd" should be running on "server"
00:00:00.558
And
podman container "uyuni-server-attestation-0" should be running on "server"
00:00:00.549
And
podman container "uyuni-hub-xmlrpc-0" should be running on "server"
00:00:00.551
Then
"proxy" should have a FQDN
00:00:04.142
And
reverse resolution should work for "proxy"
00:00:00.392
And
"proxy" should communicate with the server using public interface
00:00:01.234
And
the clock from "proxy" should be exact
00:00:00.394
Then
"sle_minion" should have a FQDN
00:00:06.961
And
reverse resolution should work for "sle_minion"
00:00:00.763
And
"sle_minion" should communicate with the server using public interface
00:00:01.598
And
the clock from "sle_minion" should be exact
00:00:00.890
Then
"build_host" should have a FQDN
00:00:04.414
And
reverse resolution should work for "build_host"
00:00:00.495
And
"build_host" should communicate with the server using public interface
00:00:01.269
And
the clock from "build_host" should be exact
00:00:00.414
Then
"sshminion" should have a FQDN
00:00:06.293
And
reverse resolution should work for "sshminion"
00:00:00.596
And
"sshminion" should communicate with the server using public interface
00:00:01.446
And
the clock from "sshminion" should be exact
00:00:00.586
Then
"rhlike_minion" should have a FQDN
00:00:02.368
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.144
And
the clock from "rhlike_minion" should be exact
00:00:00.203
Then
"deblike_minion" should have a FQDN
00:00:04.718
And
reverse resolution should work for "deblike_minion"
00:00:00.207
And
"deblike_minion" should communicate with the server using public interface
00:00:01.080
And
the clock from "deblike_minion" should be exact
00:00:00.204