@containerized_server
@scope_containerized_proxy
@proxy
@transactional_server
@skip_if_cloud
@transactional_proxy
@skip_if_transactional_proxy
Feature: 0019 - Setup containerized proxy
Description: In order to use a containerized proxy with the server
As the system administrator
I want to register the containerized proxy on the server
File name: proxy_container.feature
Relative path: proxy/proxy_container.feature
@containerized_server
@scope_containerized_proxy
@proxy
Scenario: Bootstrap the proxy host as a salt minion
When
I follow the left menu "Systems > Bootstrapping"
00:00:01.517
Then
I should see a "Bootstrap Minions" text
00:00:00.010
The hostname of proxy is uyuni-master-proxy.sumaci.aws
And
I enter "22" as "port"
00:00:00.019
And
I enter "root" as "user"
00:00:00.018
And
I enter "linux" as "password"
00:00:00.019
And
I select "1-PROXY-KEY-x86_64" from "activationKeys"
00:00:00.032
And
I click on "Bootstrap"
00:00:00.352
And
I wait until I see "Bootstrap process initiated." text
00:00:39.371
@containerized_server
@scope_containerized_proxy
@proxy
@skip_if_cloud
@transactional_proxy
Scenario: Reboot the proxy host again to activate the registration states
When
I wait at most 600 seconds until "proxy" is registered and its refreshes are completed
0s
And
I wait until I see "There is a pending transaction for this system, please reboot it to activate the changes." text, refreshing the page
0s
And
I wait until no Salt job is running on "proxy"
0s
And
I reboot the "proxy" host through SSH, waiting until it comes back
0s
@containerized_server
@scope_containerized_proxy
@proxy
Scenario: Generate containerized proxy configuration
When
I generate the configuration "/tmp/proxy_container_config.tar.gz" of containerized proxy on the server
00:00:08.290
And
I copy the configuration "/tmp/proxy_container_config.tar.gz" of containerized proxy from the server to the proxy
00:00:03.250
@containerized_server
@scope_containerized_proxy
@proxy
Scenario: Set up the containerized proxy service to support Avahi
Record not added - avahi domain was not detected
@containerized_server
@scope_containerized_proxy
@proxy
Scenario: Wait until containerized proxy service is active
And
I wait until "uyuni-proxy-pod" service is active on "proxy"
00:00:00.714
And
I wait until "uyuni-proxy-httpd" service is active on "proxy"
00:00:00.959
And
I wait until "uyuni-proxy-salt-broker" service is active on "proxy"
00:00:00.879
And
I wait until "uyuni-proxy-squid" service is active on "proxy"
00:00:00.433
And
I wait until "uyuni-proxy-ssh" service is active on "proxy"
00:00:00.393
And
I wait until "uyuni-proxy-tftpd" service is active on "proxy"
00:00:00.410
And
I check that "proxy" host is listening on TCP port "8022"
00:00:00.402
And
I check that "proxy" host is listening on TCP port "80"
00:00:00.482
And
I check that "proxy" host is listening on TCP port "443"
00:00:00.403
And
I visit "Proxy" endpoint of this "proxy"
00:00:00.551
@containerized_server
@scope_containerized_proxy
@proxy
Scenario: Podman containers are running on the proxy
Then
podman container "uyuni-proxy-httpd" should be running on "proxy"
00:00:00.425
And
podman container "uyuni-proxy-salt-broker" should be running on "proxy"
00:00:00.429
And
podman container "uyuni-proxy-squid" should be running on "proxy"
00:00:00.421
And
podman container "uyuni-proxy-ssh" should be running on "proxy"
00:00:00.426
And
podman container "uyuni-proxy-tftpd" should be running on "proxy"
00:00:00.421
@containerized_server
@scope_containerized_proxy
@proxy
Scenario: Check if Monitoring can be enabled on the containerized proxy
Given
I am on the Systems overview page of this "proxy"
00:00:01.116
When
I follow "Properties" in the content area
00:00:00.372
Then
the "monitoring_entitled" checkbox should be disabled
00:00:10.005