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.767
And
reverse resolution should work for "server"
00:00:01.516
And
the clock from "server" should be exact
00:00:01.729
And
service "apache2" is active on "server"
00:00:01.571
And
service "cobblerd" is active on "server"
00:00:01.779
And
service "rhn-search" is active on "server"
00:00:01.829
And
service "salt-api" is active on "server"
00:00:01.653
And
service "salt-master" is active on "server"
00:00:01.653
And
service "taskomatic" is active on "server"
00:00:01.497
And
socket "tftp" is active on "server"
00:00:01.560
And
service "tomcat" is active on "server"
00:00:01.472
And
service "uyuni-update-config" is active on "server"
00:00:01.587
And
service "uyuni-check-database" is active on "server"
00:00:01.701
And
service "spacewalk-wait-for-tomcat" is active on "server"
00:00:01.336
And
service "spacewalk-wait-for-salt" is active on "server"
00:00:01.210
And
service "spacewalk-wait-for-taskomatic" is active on "server"
00:00:00.962
And
service "salt-secrets-config" is active on "server"
00:00:00.922
And
service "cobbler-refresh-mkloaders" is active on "server"
00:00:00.934
@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.604
And
podman container "uyuni-server" should be running on "server"
00:00:00.614
And
podman container "uyuni-server" should be healthy on "server"
00:00:00.653
And
podman container "uyuni-saline-0" should be running on "server"
00:00:00.619
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.617
And
podman container "uyuni-hub-xmlrpc-0" should be running on "server"
00:00:00.640
Then
"proxy" should have a FQDN
00:00:04.243
And
reverse resolution should work for "proxy"
00:00:00.406
And
"proxy" should communicate with the server using public interface
00:00:01.332
And
the clock from "proxy" should be exact
00:00:00.403
Then
"sle_minion" should have a FQDN
00:00:06.401
And
reverse resolution should work for "sle_minion"
00:00:00.611
And
"sle_minion" should communicate with the server using public interface
00:00:01.552
And
the clock from "sle_minion" should be exact
00:00:00.640
Then
"build_host" should have a FQDN
00:00:04.522
And
reverse resolution should work for "build_host"
00:00:00.480
And
"build_host" should communicate with the server using public interface
00:00:01.401
And
the clock from "build_host" should be exact
00:00:00.403
Then
"sshminion" should have a FQDN
00:00:06.711
And
reverse resolution should work for "sshminion"
00:00:00.608
And
"sshminion" should communicate with the server using public interface
00:00:01.680
And
the clock from "sshminion" should be exact
00:00:00.656
Then
"rhlike_minion" should have a FQDN
00:00:02.193
And
reverse resolution should work for "rhlike_minion"
00:00:00.200
And
"rhlike_minion" should communicate with the server using public interface
00:00:01.127
And
the clock from "rhlike_minion" should be exact
00:00:00.198
Then
"deblike_minion" should have a FQDN
00:00:04.783
And
reverse resolution should work for "deblike_minion"
00:00:00.205
And
"deblike_minion" should communicate with the server using public interface
00:00:01.165
And
the clock from "deblike_minion" should be exact
00:00:00.206