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.189
And
the clock from "server" should be exact
00:00:01.379
And
service "apache2" is active on "server"
00:00:01.448
And
service "cobblerd" is active on "server"
00:00:01.399
And
service "rhn-search" is active on "server"
00:00:01.366
And
service "salt-api" is active on "server"
00:00:01.461
And
service "salt-master" is active on "server"
00:00:01.502
And
service "taskomatic" is active on "server"
00:00:01.433
And
socket "tftp" is active on "server"
00:00:01.441
And
service "tomcat" is active on "server"
00:00:01.515
And
service "uyuni-update-config" is active on "server"
00:00:01.435
And
service "uyuni-check-database" is active on "server"
00:00:01.447
And
service "spacewalk-wait-for-tomcat" is active on "server"
00:00:01.278
And
service "spacewalk-wait-for-salt" is active on "server"
00:00:01.294
And
service "spacewalk-wait-for-taskomatic" is active on "server"
00:00:01.005
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.935
@containerized_server
@skip_if_rke2
Scenario: Podman containers are running
Then
podman container "uyuni-db" should be running on "server"
00:00:00.621
And
podman container "uyuni-db" should be healthy on "server"
00:00:00.617
And
podman container "uyuni-server" should be running on "server"
00:00:00.627
And
podman container "uyuni-server" should be healthy on "server"
00:00:00.613
And
podman container "uyuni-saline-0" should be running on "server"
00:00:00.597
And
podman container "uyuni-tftpd" should be running on "server"
00:00:00.607
And
podman container "uyuni-server-attestation-0" should be running on "server"
00:00:00.599
And
podman container "uyuni-hub-xmlrpc-0" should be running on "server"
00:00:00.622
Then
"proxy" should have a FQDN
00:00:04.209
And
reverse resolution should work for "proxy"
00:00:00.396
And
"proxy" should communicate with the server using public interface
00:00:01.313
And
the clock from "proxy" should be exact
00:00:00.401
Then
"sle_minion" should have a FQDN
00:00:07.621
And
reverse resolution should work for "sle_minion"
00:00:00.683
And
"sle_minion" should communicate with the server using public interface
00:00:01.655
And
the clock from "sle_minion" should be exact
00:00:00.638
Then
"build_host" should have a FQDN
00:00:05.137
And
reverse resolution should work for "build_host"
00:00:00.517
And
"build_host" should communicate with the server using public interface
00:00:01.395
And
the clock from "build_host" should be exact
00:00:00.480
Then
"sshminion" should have a FQDN
00:00:06.373
And
reverse resolution should work for "sshminion"
00:00:00.606
And
"sshminion" should communicate with the server using public interface
00:00:01.586
And
the clock from "sshminion" should be exact
00:00:00.606
Then
"rhlike_minion" should have a FQDN
00:00:02.777
And
reverse resolution should work for "rhlike_minion"
00:00:00.272
And
"rhlike_minion" should communicate with the server using public interface
00:00:01.181
And
the clock from "rhlike_minion" should be exact
00:00:00.230
Then
"deblike_minion" should have a FQDN
00:00:05.565
And
reverse resolution should work for "deblike_minion"
00:00:00.229
And
"deblike_minion" should communicate with the server using public interface
00:00:01.138
And
the clock from "deblike_minion" should be exact
00:00:00.220