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.701
And
reverse resolution should work for "server"
00:00:01.368
And
the clock from "server" should be exact
00:00:01.606
And
service "apache2" is active on "server"
00:00:01.461
And
service "cobblerd" is active on "server"
00:00:01.561
And
service "rhn-search" is active on "server"
00:00:01.419
And
service "salt-api" is active on "server"
00:00:01.466
And
service "salt-master" is active on "server"
00:00:01.915
And
service "taskomatic" is active on "server"
00:00:01.539
And
socket "tftp" is active on "server"
00:00:01.499
And
service "tomcat" is active on "server"
00:00:01.408
And
service "uyuni-update-config" is active on "server"
00:00:01.413
And
service "uyuni-check-database" is active on "server"
00:00:02.007
And
service "spacewalk-wait-for-tomcat" is active on "server"
00:00:01.139
And
service "spacewalk-wait-for-salt" is active on "server"
00:00:00.935
And
service "spacewalk-wait-for-taskomatic" is active on "server"
00:00:00.912
And
service "salt-secrets-config" is active on "server"
00:00:00.921
And
service "cobbler-refresh-mkloaders" is active on "server"
00:00:00.904
@containerized_server
@skip_if_rke2
Scenario: Podman containers are running
Then
podman container "uyuni-db" should be running on "server"
00:00:00.610
And
podman container "uyuni-db" should be healthy on "server"
00:00:00.614
And
podman container "uyuni-server" should be running on "server"
00:00:00.603
And
podman container "uyuni-server" should be healthy on "server"
00:00:00.614
And
podman container "uyuni-saline-0" should be running on "server"
00:00:00.605
And
podman container "uyuni-tftpd" should be running on "server"
00:00:00.609
And
podman container "uyuni-server-attestation-0" should be running on "server"
00:00:00.597
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.166
And
reverse resolution should work for "proxy"
00:00:00.398
And
"proxy" should communicate with the server using public interface
00:00:01.297
And
the clock from "proxy" should be exact
00:00:00.388
Then
"sle_minion" should have a FQDN
00:00:06.427
And
reverse resolution should work for "sle_minion"
00:00:00.627
And
"sle_minion" should communicate with the server using public interface
00:00:01.524
And
the clock from "sle_minion" should be exact
00:00:00.612
Then
"build_host" should have a FQDN
00:00:04.461
And
reverse resolution should work for "build_host"
00:00:00.498
And
"build_host" should communicate with the server using public interface
00:00:01.400
And
the clock from "build_host" should be exact
00:00:00.420
Then
"sshminion" should have a FQDN
00:00:06.337
And
reverse resolution should work for "sshminion"
00:00:00.606
And
"sshminion" should communicate with the server using public interface
00:00:01.533
And
the clock from "sshminion" should be exact
00:00:00.586
Then
"rhlike_minion" should have a FQDN
00:00:02.842
And
reverse resolution should work for "rhlike_minion"
00:00:00.252
And
"rhlike_minion" should communicate with the server using public interface
00:00:01.349
And
the clock from "rhlike_minion" should be exact
00:00:00.226
Then
"deblike_minion" should have a FQDN
00:00:05.345
And
reverse resolution should work for "deblike_minion"
00:00:00.234
And
"deblike_minion" should communicate with the server using public interface
00:00:01.145
And
the clock from "deblike_minion" should be exact
00:00:00.243