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.751
And
reverse resolution should work for "server"
00:00:01.519
And
the clock from "server" should be exact
00:00:01.535
And
service "apache2" is active on "server"
00:00:01.687
And
service "cobblerd" is active on "server"
00:00:01.483
And
service "rhn-search" is active on "server"
00:00:01.473
And
service "salt-api" is active on "server"
00:00:01.519
And
service "salt-master" is active on "server"
00:00:01.478
And
service "taskomatic" is active on "server"
00:00:01.549
And
socket "tftp" is active on "server"
00:00:01.498
And
service "tomcat" is active on "server"
00:00:01.576
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.704
And
service "spacewalk-wait-for-tomcat" is active on "server"
00:00:01.202
And
service "spacewalk-wait-for-salt" is active on "server"
00:00:00.922
And
service "spacewalk-wait-for-taskomatic" is active on "server"
00:00:00.907
And
service "salt-secrets-config" is active on "server"
00:00:00.897
And
service "cobbler-refresh-mkloaders" is active on "server"
00:00:00.925
@containerized_server
@skip_if_rke2
Scenario: Podman containers are running
Then
podman container "uyuni-db" should be running on "server"
00:00:00.615
And
podman container "uyuni-db" should be healthy on "server"
00:00:00.605
And
podman container "uyuni-server" should be running on "server"
00:00:00.600
And
podman container "uyuni-server" should be healthy on "server"
00:00:00.681
And
podman container "uyuni-saline-0" should be running on "server"
00:00:00.597
And
podman container "uyuni-tftpd" should be running on "server"
00:00:00.599
And
podman container "uyuni-server-attestation-0" should be running on "server"
00:00:00.599
And
podman container "uyuni-hub-xmlrpc-0" should be running on "server"
00:00:00.601
Then
"proxy" should have a FQDN
00:00:04.143
And
reverse resolution should work for "proxy"
00:00:00.394
And
"proxy" should communicate with the server using public interface
00:00:01.309
And
the clock from "proxy" should be exact
00:00:00.391
Then
"sle_minion" should have a FQDN
00:00:06.551
And
reverse resolution should work for "sle_minion"
00:00:00.614
And
"sle_minion" should communicate with the server using public interface
00:00:01.510
And
the clock from "sle_minion" should be exact
00:00:00.591
Then
"build_host" should have a FQDN
00:00:04.495
And
reverse resolution should work for "build_host"
00:00:00.498
And
"build_host" should communicate with the server using public interface
00:00:01.370
And
the clock from "build_host" should be exact
00:00:00.410
Then
"sshminion" should have a FQDN
00:00:06.284
And
reverse resolution should work for "sshminion"
00:00:00.602
And
"sshminion" should communicate with the server using public interface
00:00:01.653
And
the clock from "sshminion" should be exact
00:00:00.604
Then
"rhlike_minion" should have a FQDN
00:00:02.267
And
reverse resolution should work for "rhlike_minion"
00:00:00.203
And
"rhlike_minion" should communicate with the server using public interface
00:00:01.114
And
the clock from "rhlike_minion" should be exact
00:00:00.200
Then
"deblike_minion" should have a FQDN
00:00:05.052
And
reverse resolution should work for "deblike_minion"
00:00:00.235
And
"deblike_minion" should communicate with the server using public interface
00:00:01.207
And
the clock from "deblike_minion" should be exact
00:00:00.248