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.722
And
reverse resolution should work for "server"
00:00:01.490
And
the clock from "server" should be exact
00:00:01.613
And
service "apache2" is active on "server"
00:00:01.857
And
service "cobblerd" is active on "server"
00:00:01.551
And
service "rhn-search" is active on "server"
00:00:01.545
And
service "salt-api" is active on "server"
00:00:01.547
And
service "salt-master" is active on "server"
00:00:01.536
And
service "taskomatic" is active on "server"
00:00:01.925
And
socket "tftp" is active on "server"
00:00:01.860
And
service "tomcat" is active on "server"
00:00:01.646
And
service "uyuni-update-config" is active on "server"
00:00:01.560
And
service "uyuni-check-database" is active on "server"
00:00:01.491
And
service "spacewalk-wait-for-tomcat" is active on "server"
00:00:01.790
And
service "spacewalk-wait-for-salt" is active on "server"
00:00:01.298
And
service "spacewalk-wait-for-taskomatic" is active on "server"
00:00:00.962
And
service "salt-secrets-config" is active on "server"
00:00:00.927
And
service "cobbler-refresh-mkloaders" is active on "server"
00:00:00.975
@containerized_server
@skip_if_rke2
Scenario: Podman containers are running
Then
podman container "uyuni-db" should be running on "server"
00:00:00.617
And
podman container "uyuni-db" should be healthy on "server"
00:00:00.610
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.628
And
podman container "uyuni-saline-0" should be running on "server"
00:00:00.621
And
podman container "uyuni-tftpd" should be running on "server"
00:00:00.622
And
podman container "uyuni-server-attestation-0" should be running on "server"
00:00:00.618
And
podman container "uyuni-hub-xmlrpc-0" should be running on "server"
00:00:00.624
Then
"proxy" should have a FQDN
00:00:04.141
And
reverse resolution should work for "proxy"
00:00:00.394
And
"proxy" should communicate with the server using public interface
00:00:01.344
And
the clock from "proxy" should be exact
00:00:00.394
Then
"sle_minion" should have a FQDN
00:00:06.400
And
reverse resolution should work for "sle_minion"
00:00:00.618
And
"sle_minion" should communicate with the server using public interface
00:00:01.586
And
the clock from "sle_minion" should be exact
00:00:00.604
Then
"build_host" should have a FQDN
00:00:04.879
And
reverse resolution should work for "build_host"
00:00:00.520
And
"build_host" should communicate with the server using public interface
00:00:01.456
And
the clock from "build_host" should be exact
00:00:00.435
Then
"sshminion" should have a FQDN
00:00:06.121
And
reverse resolution should work for "sshminion"
00:00:00.587
And
"sshminion" should communicate with the server using public interface
00:00:01.496
And
the clock from "sshminion" should be exact
00:00:00.575
Then
"rhlike_minion" should have a FQDN
00:00:02.239
And
reverse resolution should work for "rhlike_minion"
00:00:00.207
And
"rhlike_minion" should communicate with the server using public interface
00:00:01.153
And
the clock from "rhlike_minion" should be exact
00:00:00.201
Then
"deblike_minion" should have a FQDN
00:00:04.792
And
reverse resolution should work for "deblike_minion"
00:00:00.204
And
"deblike_minion" should communicate with the server using public interface
00:00:01.132
And
the clock from "deblike_minion" should be exact
00:00:00.206