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.674
And
reverse resolution should work for "server"
00:00:01.356
And
the clock from "server" should be exact
00:00:01.519
And
service "apache2" is active on "server"
00:00:01.563
And
service "cobblerd" is active on "server"
00:00:01.848
And
service "rhn-search" is active on "server"
00:00:01.499
And
service "salt-api" is active on "server"
00:00:01.548
And
service "salt-master" is active on "server"
00:00:01.500
And
service "taskomatic" is active on "server"
00:00:01.675
And
socket "tftp" is active on "server"
00:00:01.514
And
service "tomcat" is active on "server"
00:00:01.555
And
service "uyuni-update-config" is active on "server"
00:00:01.545
And
service "uyuni-check-database" is active on "server"
00:00:01.376
And
service "spacewalk-wait-for-tomcat" is active on "server"
00:00:01.248
And
service "spacewalk-wait-for-salt" is active on "server"
00:00:01.008
And
service "spacewalk-wait-for-taskomatic" is active on "server"
00:00:00.904
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.905
@containerized_server
@skip_if_rke2
Scenario: Podman containers are running
Then
podman container "uyuni-db" should be running on "server"
00:00:00.609
And
podman container "uyuni-db" should be healthy on "server"
00:00:00.599
And
podman container "uyuni-server" should be running on "server"
00:00:00.604
And
podman container "uyuni-server" should be healthy on "server"
00:00:00.605
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.601
And
podman container "uyuni-server-attestation-0" should be running on "server"
00:00:00.619
And
podman container "uyuni-hub-xmlrpc-0" should be running on "server"
00:00:00.607
Then
"proxy" should have a FQDN
00:00:04.128
And
reverse resolution should work for "proxy"
00:00:00.403
And
"proxy" should communicate with the server using public interface
00:00:01.332
And
the clock from "proxy" should be exact
00:00:00.392
Then
"sle_minion" should have a FQDN
00:00:06.186
And
reverse resolution should work for "sle_minion"
00:00:00.594
And
"sle_minion" should communicate with the server using public interface
00:00:01.518
And
the clock from "sle_minion" should be exact
00:00:00.578
Then
"build_host" should have a FQDN
00:00:04.596
And
reverse resolution should work for "build_host"
00:00:00.423
And
"build_host" should communicate with the server using public interface
00:00:01.371
And
the clock from "build_host" should be exact
00:00:00.406
Then
"sshminion" should have a FQDN
00:00:06.296
And
reverse resolution should work for "sshminion"
00:00:00.622
And
"sshminion" should communicate with the server using public interface
00:00:01.511
And
the clock from "sshminion" should be exact
00:00:00.588
Then
"rhlike_minion" should have a FQDN
00:00:02.263
And
reverse resolution should work for "rhlike_minion"
00:00:00.210
And
"rhlike_minion" should communicate with the server using public interface
00:00:01.119
And
the clock from "rhlike_minion" should be exact
00:00:00.202
Then
"deblike_minion" should have a FQDN
00:00:04.644
And
reverse resolution should work for "deblike_minion"
00:00:00.207
And
"deblike_minion" should communicate with the server using public interface
00:00:01.127
And
the clock from "deblike_minion" should be exact
00:00:00.208