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.787
And
reverse resolution should work for "server"
00:00:01.115
And
the clock from "server" should be exact
00:00:01.509
And
service "apache2" is active on "server"
00:00:01.285
And
service "cobblerd" is active on "server"
00:00:01.422
And
service "rhn-search" is active on "server"
00:00:01.364
And
service "salt-api" is active on "server"
00:00:01.244
And
service "salt-master" is active on "server"
00:00:01.282
And
service "taskomatic" is active on "server"
00:00:01.326
And
socket "tftp" is active on "server"
00:00:01.257
And
service "tomcat" is active on "server"
00:00:01.356
And
service "uyuni-update-config" is active on "server"
00:00:01.345
And
service "uyuni-check-database" is active on "server"
00:00:01.423
And
service "spacewalk-wait-for-tomcat" is active on "server"
00:00:01.101
And
service "spacewalk-wait-for-salt" is active on "server"
00:00:01.073
And
service "spacewalk-wait-for-taskomatic" is active on "server"
00:00:01.081
And
service "salt-secrets-config" is active on "server"
00:00:00.801
And
service "cobbler-refresh-mkloaders" is active on "server"
00:00:00.768
@containerized_server
@skip_if_rke2
Scenario: Podman containers are running
Then
podman container "uyuni-db" should be running on "server"
00:00:00.548
And
podman container "uyuni-db" should be healthy on "server"
00:00:00.553
And
podman container "uyuni-server" should be running on "server"
00:00:00.564
And
podman container "uyuni-server" should be healthy on "server"
00:00:00.950
And
podman container "uyuni-saline-0" should be running on "server"
00:00:00.614
And
podman container "uyuni-tftpd" should be running on "server"
00:00:00.556
And
podman container "uyuni-server-attestation-0" should be running on "server"
00:00:00.554
And
podman container "uyuni-hub-xmlrpc-0" should be running on "server"
00:00:00.563
Then
"proxy" should have a FQDN
00:00:04.193
And
reverse resolution should work for "proxy"
00:00:00.401
And
"proxy" should communicate with the server using public interface
00:00:01.228
And
the clock from "proxy" should be exact
00:00:00.392
Then
"sle_minion" should have a FQDN
00:00:07.074
And
reverse resolution should work for "sle_minion"
00:00:00.661
And
"sle_minion" should communicate with the server using public interface
00:00:01.473
And
the clock from "sle_minion" should be exact
00:00:00.629
Then
"build_host" should have a FQDN
00:00:04.452
And
reverse resolution should work for "build_host"
00:00:00.447
And
"build_host" should communicate with the server using public interface
00:00:01.227
And
the clock from "build_host" should be exact
00:00:00.400
Then
"sshminion" should have a FQDN
00:00:06.772
And
reverse resolution should work for "sshminion"
00:00:00.657
And
"sshminion" should communicate with the server using public interface
00:00:01.495
And
the clock from "sshminion" should be exact
00:00:00.650
Then
"rhlike_minion" should have a FQDN
00:00:02.370
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:00.996
And
the clock from "rhlike_minion" should be exact
00:00:00.215
Then
"deblike_minion" should have a FQDN
00:00:04.692
And
reverse resolution should work for "deblike_minion"
00:00:00.208
And
"deblike_minion" should communicate with the server using public interface
00:00:01.037
And
the clock from "deblike_minion" should be exact
00:00:00.219