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.814
And
reverse resolution should work for "server"
00:00:01.267
And
the clock from "server" should be exact
00:00:01.279
And
service "apache2" is active on "server"
00:00:01.233
And
service "cobblerd" is active on "server"
00:00:01.430
And
service "rhn-search" is active on "server"
00:00:01.282
And
service "salt-api" is active on "server"
00:00:01.372
And
service "salt-master" is active on "server"
00:00:01.233
And
service "taskomatic" is active on "server"
00:00:01.380
And
socket "tftp" is active on "server"
00:00:01.383
And
service "tomcat" is active on "server"
00:00:01.291
And
service "uyuni-update-config" is active on "server"
00:00:01.270
And
service "uyuni-check-database" is active on "server"
00:00:01.466
And
service "spacewalk-wait-for-tomcat" is active on "server"
00:00:01.074
And
service "spacewalk-wait-for-salt" is active on "server"
00:00:01.322
And
service "spacewalk-wait-for-taskomatic" is active on "server"
00:00:01.400
And
service "salt-secrets-config" is active on "server"
00:00:00.988
And
service "cobbler-refresh-mkloaders" is active on "server"
00:00:00.788
@containerized_server
@skip_if_rke2
Scenario: Podman containers are running
Then
podman container "uyuni-db" should be running on "server"
00:00:00.600
And
podman container "uyuni-db" should be healthy on "server"
00:00:00.573
And
podman container "uyuni-server" should be running on "server"
00:00:00.572
And
podman container "uyuni-server" should be healthy on "server"
00:00:00.573
And
podman container "uyuni-saline-0" should be running on "server"
00:00:00.563
And
podman container "uyuni-tftpd" should be running on "server"
00:00:00.557
And
podman container "uyuni-server-attestation-0" should be running on "server"
00:00:00.560
And
podman container "uyuni-hub-xmlrpc-0" should be running on "server"
00:00:00.598
Then
"proxy" should have a FQDN
00:00:04.101
And
reverse resolution should work for "proxy"
00:00:00.392
And
"proxy" should communicate with the server using public interface
00:00:01.193
And
the clock from "proxy" should be exact
00:00:00.384
Then
"sle_minion" should have a FQDN
00:00:06.378
And
reverse resolution should work for "sle_minion"
00:00:00.609
And
"sle_minion" should communicate with the server using public interface
00:00:01.491
And
the clock from "sle_minion" should be exact
00:00:00.583
Then
"build_host" should have a FQDN
00:00:04.542
And
reverse resolution should work for "build_host"
00:00:00.412
And
"build_host" should communicate with the server using public interface
00:00:01.242
And
the clock from "build_host" should be exact
00:00:00.417
Then
"sshminion" should have a FQDN
00:00:06.297
And
reverse resolution should work for "sshminion"
00:00:00.619
And
"sshminion" should communicate with the server using public interface
00:00:01.446
And
the clock from "sshminion" should be exact
00:00:00.583
Then
"rhlike_minion" should have a FQDN
00:00:02.241
And
reverse resolution should work for "rhlike_minion"
00:00:00.201
And
"rhlike_minion" should communicate with the server using public interface
00:00:00.986
And
the clock from "rhlike_minion" should be exact
00:00:00.192
Then
"deblike_minion" should have a FQDN
00:00:04.849
And
reverse resolution should work for "deblike_minion"
00:00:00.211
And
"deblike_minion" should communicate with the server using public interface
00:00:01.001
And
the clock from "deblike_minion" should be exact
00:00:00.212