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.709
And
reverse resolution should work for "server"
00:00:01.549
And
the clock from "server" should be exact
00:00:01.576
And
service "apache2" is active on "server"
00:00:01.554
And
service "cobblerd" is active on "server"
00:00:01.510
And
service "rhn-search" is active on "server"
00:00:01.584
And
service "salt-api" is active on "server"
00:00:01.386
And
service "salt-master" is active on "server"
00:00:01.476
And
service "taskomatic" is active on "server"
00:00:01.721
And
socket "tftp" is active on "server"
00:00:01.575
And
service "tomcat" is active on "server"
00:00:01.610
And
service "uyuni-update-config" is active on "server"
00:00:01.411
And
service "uyuni-check-database" is active on "server"
00:00:01.323
And
service "spacewalk-wait-for-tomcat" is active on "server"
00:00:01.130
And
service "spacewalk-wait-for-salt" is active on "server"
00:00:00.987
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.946
And
service "cobbler-refresh-mkloaders" is active on "server"
00:00:00.926
@containerized_server
@skip_if_rke2
Scenario: Podman containers are running
Then
podman container "uyuni-db" should be running on "server"
00:00:00.608
And
podman container "uyuni-db" should be healthy on "server"
00:00:00.602
And
podman container "uyuni-server" should be running on "server"
00:00:00.648
And
podman container "uyuni-server" should be healthy on "server"
00:00:00.600
And
podman container "uyuni-saline-0" should be running on "server"
00:00:00.598
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.596
And
podman container "uyuni-hub-xmlrpc-0" should be running on "server"
00:00:00.613
Then
"proxy" should have a FQDN
00:00:04.147
And
reverse resolution should work for "proxy"
00:00:00.395
And
"proxy" should communicate with the server using public interface
00:00:01.316
And
the clock from "proxy" should be exact
00:00:00.391
Then
"sle_minion" should have a FQDN
00:00:06.353
And
reverse resolution should work for "sle_minion"
00:00:00.597
And
"sle_minion" should communicate with the server using public interface
00:00:01.538
And
the clock from "sle_minion" should be exact
00:00:00.584
Then
"build_host" should have a FQDN
00:00:04.535
And
reverse resolution should work for "build_host"
00:00:00.422
And
"build_host" should communicate with the server using public interface
00:00:01.341
And
the clock from "build_host" should be exact
00:00:00.414
Then
"sshminion" should have a FQDN
00:00:06.170
And
reverse resolution should work for "sshminion"
00:00:00.596
And
"sshminion" should communicate with the server using public interface
00:00:01.574
And
the clock from "sshminion" should be exact
00:00:00.582
Then
"rhlike_minion" should have a FQDN
00:00:02.322
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.116
And
the clock from "rhlike_minion" should be exact
00:00:00.202
Then
"deblike_minion" should have a FQDN
00:00:04.658
And
reverse resolution should work for "deblike_minion"
00:00:00.218
And
"deblike_minion" should communicate with the server using public interface
00:00:01.153
And
the clock from "deblike_minion" should be exact
00:00:00.206