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.709
And
reverse resolution should work for "server"
00:00:01.246
And
the clock from "server" should be exact
00:00:01.306
And
service "apache2" is active on "server"
00:00:01.242
And
service "cobblerd" is active on "server"
00:00:01.315
And
service "rhn-search" is active on "server"
00:00:01.230
And
service "salt-api" is active on "server"
00:00:01.197
And
service "salt-master" is active on "server"
00:00:01.285
And
service "taskomatic" is active on "server"
00:00:01.372
And
socket "tftp" is active on "server"
00:00:01.462
And
service "tomcat" is active on "server"
00:00:01.187
And
service "uyuni-update-config" is active on "server"
00:00:01.251
And
service "uyuni-check-database" is active on "server"
00:00:01.184
And
service "spacewalk-wait-for-tomcat" is active on "server"
00:00:01.081
And
service "spacewalk-wait-for-salt" is active on "server"
00:00:01.541
And
service "spacewalk-wait-for-taskomatic" is active on "server"
00:00:01.162
And
service "salt-secrets-config" is active on "server"
00:00:00.792
And
service "cobbler-refresh-mkloaders" is active on "server"
00:00:00.803
@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.568
And
podman container "uyuni-server" should be running on "server"
00:00:00.558
And
podman container "uyuni-server" should be healthy on "server"
00:00:00.567
And
podman container "uyuni-saline-0" should be running on "server"
00:00:00.552
And
podman container "uyuni-tftpd" should be running on "server"
00:00:00.550
And
podman container "uyuni-server-attestation-0" should be running on "server"
00:00:00.551
And
podman container "uyuni-hub-xmlrpc-0" should be running on "server"
00:00:00.555
Then
"proxy" should have a FQDN
00:00:04.102
And
reverse resolution should work for "proxy"
00:00:00.387
And
"proxy" should communicate with the server using public interface
00:00:01.264
And
the clock from "proxy" should be exact
00:00:00.388
Then
"sle_minion" should have a FQDN
00:00:06.153
And
reverse resolution should work for "sle_minion"
00:00:00.591
And
"sle_minion" should communicate with the server using public interface
00:00:01.398
And
the clock from "sle_minion" should be exact
00:00:00.575
Then
"build_host" should have a FQDN
00:00:04.342
And
reverse resolution should work for "build_host"
00:00:00.487
And
"build_host" should communicate with the server using public interface
00:00:01.260
And
the clock from "build_host" should be exact
00:00:00.410
Then
"sshminion" should have a FQDN
00:00:06.512
And
reverse resolution should work for "sshminion"
00:00:00.639
And
"sshminion" should communicate with the server using public interface
00:00:01.434
And
the clock from "sshminion" should be exact
00:00:00.615
Then
"rhlike_minion" should have a FQDN
00:00:02.302
And
reverse resolution should work for "rhlike_minion"
00:00:00.229
And
"rhlike_minion" should communicate with the server using public interface
00:00:01.001
And
the clock from "rhlike_minion" should be exact
00:00:00.206
Then
"deblike_minion" should have a FQDN
00:00:05.488
And
reverse resolution should work for "deblike_minion"
00:00:00.277
And
"deblike_minion" should communicate with the server using public interface
00:00:01.011
And
the clock from "deblike_minion" should be exact
00:00:00.285