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.747
And
reverse resolution should work for "server"
00:00:01.191
And
the clock from "server" should be exact
00:00:01.352
And
service "apache2" is active on "server"
00:00:01.329
And
service "cobblerd" is active on "server"
00:00:01.229
And
service "rhn-search" is active on "server"
00:00:01.516
And
service "salt-api" is active on "server"
00:00:01.261
And
service "salt-master" is active on "server"
00:00:01.245
And
service "taskomatic" is active on "server"
00:00:01.365
And
socket "tftp" is active on "server"
00:00:01.236
And
service "tomcat" is active on "server"
00:00:01.321
And
service "uyuni-update-config" is active on "server"
00:00:01.382
And
service "uyuni-check-database" is active on "server"
00:00:01.264
And
service "spacewalk-wait-for-tomcat" is active on "server"
00:00:01.243
And
service "spacewalk-wait-for-salt" is active on "server"
00:00:01.203
And
service "spacewalk-wait-for-taskomatic" is active on "server"
00:00:01.029
And
service "salt-secrets-config" is active on "server"
00:00:01.142
And
service "cobbler-refresh-mkloaders" is active on "server"
00:00:00.956
@containerized_server
@skip_if_rke2
Scenario: Podman containers are running
Then
podman container "uyuni-db" should be running on "server"
00:00:00.627
And
podman container "uyuni-db" should be healthy on "server"
00:00:00.617
And
podman container "uyuni-server" should be running on "server"
00:00:00.555
And
podman container "uyuni-server" should be healthy on "server"
00:00:00.565
And
podman container "uyuni-saline-0" should be running on "server"
00:00:00.593
And
podman container "uyuni-tftpd" should be running on "server"
00:00:00.559
And
podman container "uyuni-server-attestation-0" should be running on "server"
00:00:00.573
And
podman container "uyuni-hub-xmlrpc-0" should be running on "server"
00:00:00.564
Then
"proxy" should have a FQDN
00:00:04.169
And
reverse resolution should work for "proxy"
00:00:00.398
And
"proxy" should communicate with the server using public interface
00:00:01.248
And
the clock from "proxy" should be exact
00:00:00.397
Then
"sle_minion" should have a FQDN
00:00:06.044
And
reverse resolution should work for "sle_minion"
00:00:00.577
And
"sle_minion" should communicate with the server using public interface
00:00:01.412
And
the clock from "sle_minion" should be exact
00:00:00.571
Then
"build_host" should have a FQDN
00:00:04.643
And
reverse resolution should work for "build_host"
00:00:00.428
And
"build_host" should communicate with the server using public interface
00:00:01.226
And
the clock from "build_host" should be exact
00:00:00.408
Then
"sshminion" should have a FQDN
00:00:06.453
And
reverse resolution should work for "sshminion"
00:00:00.645
And
"sshminion" should communicate with the server using public interface
00:00:01.458
And
the clock from "sshminion" should be exact
00:00:00.610
Then
"rhlike_minion" should have a FQDN
00:00:02.364
And
reverse resolution should work for "rhlike_minion"
00:00:00.219
And
"rhlike_minion" should communicate with the server using public interface
00:00:01.015
And
the clock from "rhlike_minion" should be exact
00:00:00.206
Then
"deblike_minion" should have a FQDN
00:00:04.533
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:00.987
And
the clock from "deblike_minion" should be exact
00:00:00.205