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.695
And
reverse resolution should work for "server"
00:00:01.450
And
the clock from "server" should be exact
00:00:01.514
And
service "apache2" is active on "server"
00:00:01.749
And
service "cobblerd" is active on "server"
00:00:01.460
And
service "rhn-search" is active on "server"
00:00:01.555
And
service "salt-api" is active on "server"
00:00:01.575
And
service "salt-master" is active on "server"
00:00:01.670
And
service "taskomatic" is active on "server"
00:00:01.418
And
socket "tftp" is active on "server"
00:00:01.492
And
service "tomcat" is active on "server"
00:00:01.888
And
service "uyuni-update-config" is active on "server"
00:00:01.618
And
service "uyuni-check-database" is active on "server"
00:00:01.365
And
service "spacewalk-wait-for-tomcat" is active on "server"
00:00:01.391
And
service "spacewalk-wait-for-salt" is active on "server"
00:00:01.486
And
service "spacewalk-wait-for-taskomatic" is active on "server"
00:00:01.432
And
service "salt-secrets-config" is active on "server"
00:00:00.923
And
service "cobbler-refresh-mkloaders" is active on "server"
00:00:00.933
@containerized_server
@skip_if_rke2
Scenario: Podman containers are running
Then
podman container "uyuni-db" should be running on "server"
00:00:00.671
And
podman container "uyuni-db" should be healthy on "server"
00:00:00.627
And
podman container "uyuni-server" should be running on "server"
00:00:00.625
And
podman container "uyuni-server" should be healthy on "server"
00:00:00.603
And
podman container "uyuni-saline-0" should be running on "server"
00:00:00.610
And
podman container "uyuni-tftpd" should be running on "server"
00:00:00.601
And
podman container "uyuni-server-attestation-0" should be running on "server"
00:00:00.606
And
podman container "uyuni-hub-xmlrpc-0" should be running on "server"
00:00:00.606
Then
"proxy" should have a FQDN
00:00:04.260
And
reverse resolution should work for "proxy"
00:00:00.407
And
"proxy" should communicate with the server using public interface
00:00:01.502
And
the clock from "proxy" should be exact
00:00:00.399
Then
"sle_minion" should have a FQDN
00:00:07.220
And
reverse resolution should work for "sle_minion"
00:00:00.710
And
"sle_minion" should communicate with the server using public interface
00:00:01.739
And
the clock from "sle_minion" should be exact
00:00:00.666
Then
"build_host" should have a FQDN
00:00:04.628
And
reverse resolution should work for "build_host"
00:00:00.522
And
"build_host" should communicate with the server using public interface
00:00:01.483
And
the clock from "build_host" should be exact
00:00:00.428
Then
"sshminion" should have a FQDN
00:00:06.322
And
reverse resolution should work for "sshminion"
00:00:00.614
And
"sshminion" should communicate with the server using public interface
00:00:01.541
And
the clock from "sshminion" should be exact
00:00:00.602
Then
"rhlike_minion" should have a FQDN
00:00:02.394
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.144
And
the clock from "rhlike_minion" should be exact
00:00:00.204
Then
"deblike_minion" should have a FQDN
00:00:04.866
And
reverse resolution should work for "deblike_minion"
00:00:00.223
And
"deblike_minion" should communicate with the server using public interface
00:00:01.118
And
the clock from "deblike_minion" should be exact
00:00:00.217