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.676
And
reverse resolution should work for "server"
00:00:01.187
And
the clock from "server" should be exact
00:00:01.384
And
service "apache2" is active on "server"
00:00:01.393
And
service "cobblerd" is active on "server"
00:00:01.357
And
service "rhn-search" is active on "server"
00:00:01.340
And
service "salt-api" is active on "server"
00:00:01.443
And
service "salt-master" is active on "server"
00:00:01.605
And
service "taskomatic" is active on "server"
00:00:01.426
And
socket "tftp" is active on "server"
00:00:01.369
And
service "tomcat" is active on "server"
00:00:01.433
And
service "uyuni-update-config" is active on "server"
00:00:01.421
And
service "uyuni-check-database" is active on "server"
00:00:01.332
And
service "spacewalk-wait-for-tomcat" is active on "server"
00:00:01.432
And
service "spacewalk-wait-for-salt" is active on "server"
00:00:01.239
And
service "spacewalk-wait-for-taskomatic" is active on "server"
00:00:01.180
And
service "salt-secrets-config" is active on "server"
00:00:00.902
And
service "cobbler-refresh-mkloaders" is active on "server"
00:00:00.895
@containerized_server
@skip_if_rke2
Scenario: Podman containers are running
Then
podman container "uyuni-db" should be running on "server"
00:00:00.618
And
podman container "uyuni-db" should be healthy on "server"
00:00:00.595
And
podman container "uyuni-server" should be running on "server"
00:00:00.608
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.599
And
podman container "uyuni-tftpd" should be running on "server"
00:00:00.595
And
podman container "uyuni-server-attestation-0" should be running on "server"
00:00:00.594
And
podman container "uyuni-hub-xmlrpc-0" should be running on "server"
00:00:00.599
Then
"proxy" should have a FQDN
00:00:04.161
And
reverse resolution should work for "proxy"
00:00:00.396
And
"proxy" should communicate with the server using public interface
00:00:01.339
And
the clock from "proxy" should be exact
00:00:00.392
Then
"sle_minion" should have a FQDN
00:00:06.631
And
reverse resolution should work for "sle_minion"
00:00:00.632
And
"sle_minion" should communicate with the server using public interface
00:00:01.623
And
the clock from "sle_minion" should be exact
00:00:00.614
Then
"build_host" should have a FQDN
00:00:04.439
And
reverse resolution should work for "build_host"
00:00:00.432
And
"build_host" should communicate with the server using public interface
00:00:01.339
And
the clock from "build_host" should be exact
00:00:00.422
Then
"sshminion" should have a FQDN
00:00:06.562
And
reverse resolution should work for "sshminion"
00:00:00.668
And
"sshminion" should communicate with the server using public interface
00:00:01.579
And
the clock from "sshminion" should be exact
00:00:00.667
Then
"rhlike_minion" should have a FQDN
00:00:02.430
And
reverse resolution should work for "rhlike_minion"
00:00:00.231
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.207
Then
"deblike_minion" should have a FQDN
00:00:04.526
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.120
And
the clock from "deblike_minion" should be exact
00:00:00.207