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.691
And
reverse resolution should work for "server"
00:00:01.332
And
the clock from "server" should be exact
00:00:01.434
And
service "apache2" is active on "server"
00:00:01.493
And
service "cobblerd" is active on "server"
00:00:01.425
And
service "rhn-search" is active on "server"
00:00:01.439
And
service "salt-api" is active on "server"
00:00:01.461
And
service "salt-master" is active on "server"
00:00:01.378
And
service "taskomatic" is active on "server"
00:00:01.450
And
socket "tftp" is active on "server"
00:00:01.385
And
service "tomcat" is active on "server"
00:00:01.366
And
service "uyuni-update-config" is active on "server"
00:00:01.492
And
service "uyuni-check-database" is active on "server"
00:00:01.276
And
service "spacewalk-wait-for-tomcat" is active on "server"
00:00:01.419
And
service "spacewalk-wait-for-salt" is active on "server"
00:00:01.331
And
service "spacewalk-wait-for-taskomatic" is active on "server"
00:00:00.996
And
service "salt-secrets-config" is active on "server"
00:00:00.901
And
service "cobbler-refresh-mkloaders" is active on "server"
00:00:00.923
@containerized_server
@skip_if_rke2
Scenario: Podman containers are running
Then
podman container "uyuni-db" should be running on "server"
00:00:00.607
And
podman container "uyuni-db" should be healthy on "server"
00:00:00.597
And
podman container "uyuni-server" should be running on "server"
00:00:00.599
And
podman container "uyuni-server" should be healthy on "server"
00:00:00.615
And
podman container "uyuni-saline-0" should be running on "server"
00:00:00.601
And
podman container "uyuni-tftpd" should be running on "server"
00:00:00.626
And
podman container "uyuni-server-attestation-0" should be running on "server"
00:00:00.598
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.226
And
reverse resolution should work for "proxy"
00:00:00.402
And
"proxy" should communicate with the server using public interface
00:00:01.307
And
the clock from "proxy" should be exact
00:00:00.399
Then
"sle_minion" should have a FQDN
00:00:06.816
And
reverse resolution should work for "sle_minion"
00:00:00.652
And
"sle_minion" should communicate with the server using public interface
00:00:01.640
And
the clock from "sle_minion" should be exact
00:00:00.662
Then
"build_host" should have a FQDN
00:00:04.459
And
reverse resolution should work for "build_host"
00:00:00.455
And
"build_host" should communicate with the server using public interface
00:00:01.365
And
the clock from "build_host" should be exact
00:00:00.407
Then
"sshminion" should have a FQDN
00:00:06.297
And
reverse resolution should work for "sshminion"
00:00:00.588
And
"sshminion" should communicate with the server using public interface
00:00:01.542
And
the clock from "sshminion" should be exact
00:00:00.586
Then
"rhlike_minion" should have a FQDN
00:00:02.162
And
reverse resolution should work for "rhlike_minion"
00:00:00.198
And
"rhlike_minion" should communicate with the server using public interface
00:00:01.106
And
the clock from "rhlike_minion" should be exact
00:00:00.194
Then
"deblike_minion" should have a FQDN
00:00:04.679
And
reverse resolution should work for "deblike_minion"
00:00:00.227
And
"deblike_minion" should communicate with the server using public interface
00:00:01.188
And
the clock from "deblike_minion" should be exact
00:00:00.212