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.728
And
reverse resolution should work for "server"
00:00:01.617
And
the clock from "server" should be exact
00:00:01.391
And
service "apache2" is active on "server"
00:00:01.896
And
service "cobblerd" is active on "server"
00:00:01.585
And
service "rhn-search" is active on "server"
00:00:01.541
And
service "salt-api" is active on "server"
00:00:01.685
And
service "salt-master" is active on "server"
00:00:01.586
And
service "taskomatic" is active on "server"
00:00:01.618
And
socket "tftp" is active on "server"
00:00:01.977
And
service "tomcat" is active on "server"
00:00:01.619
And
service "uyuni-update-config" is active on "server"
00:00:01.571
And
service "uyuni-check-database" is active on "server"
00:00:01.428
And
service "spacewalk-wait-for-tomcat" is active on "server"
00:00:01.306
And
service "spacewalk-wait-for-salt" is active on "server"
00:00:01.117
And
service "spacewalk-wait-for-taskomatic" is active on "server"
00:00:00.997
And
service "salt-secrets-config" is active on "server"
00:00:01.011
And
service "cobbler-refresh-mkloaders" is active on "server"
00:00:01.044
@containerized_server
@skip_if_rke2
Scenario: Podman containers are running
Then
podman container "uyuni-db" should be running on "server"
00:00:00.663
And
podman container "uyuni-db" should be healthy on "server"
00:00:00.606
And
podman container "uyuni-server" should be running on "server"
00:00:00.605
And
podman container "uyuni-server" should be healthy on "server"
00:00:00.611
And
podman container "uyuni-saline-0" should be running on "server"
00:00:00.606
And
podman container "uyuni-tftpd" should be running on "server"
00:00:00.610
And
podman container "uyuni-server-attestation-0" should be running on "server"
00:00:00.622
And
podman container "uyuni-hub-xmlrpc-0" should be running on "server"
00:00:00.603
Then
"proxy" should have a FQDN
00:00:04.148
And
reverse resolution should work for "proxy"
00:00:00.398
And
"proxy" should communicate with the server using public interface
00:00:01.495
And
the clock from "proxy" should be exact
00:00:00.392
Then
"sle_minion" should have a FQDN
00:00:06.179
And
reverse resolution should work for "sle_minion"
00:00:00.583
And
"sle_minion" should communicate with the server using public interface
00:00:01.555
And
the clock from "sle_minion" should be exact
00:00:00.576
Then
"build_host" should have a FQDN
00:00:04.402
And
reverse resolution should work for "build_host"
00:00:00.475
And
"build_host" should communicate with the server using public interface
00:00:01.414
And
the clock from "build_host" should be exact
00:00:00.400
Then
"sshminion" should have a FQDN
00:00:06.280
And
reverse resolution should work for "sshminion"
00:00:00.591
And
"sshminion" should communicate with the server using public interface
00:00:01.592
And
the clock from "sshminion" should be exact
00:00:00.583
Then
"rhlike_minion" should have a FQDN
00:00:02.503
And
reverse resolution should work for "rhlike_minion"
00:00:00.209
And
"rhlike_minion" should communicate with the server using public interface
00:00:01.137
And
the clock from "rhlike_minion" should be exact
00:00:00.210
Then
"deblike_minion" should have a FQDN
00:00:05.240
And
reverse resolution should work for "deblike_minion"
00:00:00.232
And
"deblike_minion" should communicate with the server using public interface
00:00:01.142
And
the clock from "deblike_minion" should be exact
00:00:00.223