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.996
And
reverse resolution should work for "server"
00:00:01.314
And
the clock from "server" should be exact
00:00:01.358
And
service "apache2" is active on "server"
00:00:01.361
And
service "cobblerd" is active on "server"
00:00:01.472
And
service "rhn-search" is active on "server"
00:00:01.330
And
service "salt-api" is active on "server"
00:00:01.362
And
service "salt-master" is active on "server"
00:00:01.416
And
service "taskomatic" is active on "server"
00:00:01.602
And
socket "tftp" is active on "server"
00:00:01.362
And
service "tomcat" is active on "server"
00:00:01.379
And
service "uyuni-update-config" is active on "server"
00:00:01.368
And
service "uyuni-check-database" is active on "server"
00:00:01.446
And
service "spacewalk-wait-for-tomcat" is active on "server"
00:00:01.351
And
service "spacewalk-wait-for-salt" is active on "server"
00:00:01.279
And
service "spacewalk-wait-for-taskomatic" is active on "server"
00:00:01.104
And
service "salt-secrets-config" is active on "server"
00:00:00.974
And
service "cobbler-refresh-mkloaders" is active on "server"
00:00:00.902
@containerized_server
@skip_if_rke2
Scenario: Podman containers are running
Then
podman container "uyuni-db" should be running on "server"
00:00:00.614
And
podman container "uyuni-db" should be healthy on "server"
00:00:00.607
And
podman container "uyuni-server" should be running on "server"
00:00:00.611
And
podman container "uyuni-server" should be healthy on "server"
00:00:00.598
And
podman container "uyuni-saline-0" should be running on "server"
00:00:00.604
And
podman container "uyuni-tftpd" should be running on "server"
00:00:00.596
And
podman container "uyuni-server-attestation-0" should be running on "server"
00:00:00.596
And
podman container "uyuni-hub-xmlrpc-0" should be running on "server"
00:00:00.603
Then
"proxy" should have a FQDN
00:00:04.175
And
reverse resolution should work for "proxy"
00:00:00.398
And
"proxy" should communicate with the server using public interface
00:00:01.404
And
the clock from "proxy" should be exact
00:00:00.388
Then
"sle_minion" should have a FQDN
00:00:06.588
And
reverse resolution should work for "sle_minion"
00:00:00.603
And
"sle_minion" should communicate with the server using public interface
00:00:01.616
And
the clock from "sle_minion" should be exact
00:00:00.620
Then
"build_host" should have a FQDN
00:00:04.886
And
reverse resolution should work for "build_host"
00:00:00.580
And
"build_host" should communicate with the server using public interface
00:00:01.427
And
the clock from "build_host" should be exact
00:00:00.442
Then
"sshminion" should have a FQDN
00:00:06.336
And
reverse resolution should work for "sshminion"
00:00:00.595
And
"sshminion" should communicate with the server using public interface
00:00:01.529
And
the clock from "sshminion" should be exact
00:00:00.574
Then
"rhlike_minion" should have a FQDN
00:00:02.410
And
reverse resolution should work for "rhlike_minion"
00:00:00.223
And
"rhlike_minion" should communicate with the server using public interface
00:00:01.138
And
the clock from "rhlike_minion" should be exact
00:00:00.211
Then
"deblike_minion" should have a FQDN
00:00:04.571
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.127
And
the clock from "deblike_minion" should be exact
00:00:00.216