@containerized_server @scope_containerized_proxy @proxy @transactional_server @skip_if_cloud

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

Scenarios

Chart

Status

Progress

Passed	66.67 %
Failed	16.67 %
Skipped	16.67 %

Total duration:

00:37:28.010

@containerized_server @scope_containerized_proxy @proxy

Scenario: Clean up sumaform leftovers on proxy

@containerized_server @scope_containerized_proxy @proxy @transactional_server

Scenario: Reboot after clean up

@containerized_server @scope_containerized_proxy @proxy

Scenario: Log in as admin user

@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:00.149

Then I should see a "Bootstrap Minions" text 00:00:00.070

When I enter the hostname of "proxy" as "hostname" 00:00:00.116

+ Show Info

The hostname of proxy is uyuni-master-proxy.sumaci.aws

And I enter "22" as "port" 00:00:00.051

And I enter "root" as "user" 00:00:00.058

And I enter "linux" as "password" 00:00:00.057

And I select "1-PROXY-KEY-x86_64" from "activationKeys" 00:00:00.071

And I click on "Bootstrap" 00:00:00.062

And I wait until I see "Bootstrap process initiated." text 00:00:36.794

@containerized_server @scope_containerized_proxy @proxy @skip_if_cloud @transactional_server

Scenario: Reboot the proxy host

@containerized_server @scope_containerized_proxy @proxy

Scenario: Wait until the proxy host appears

@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:12.927

And I copy the configuration "/tmp/proxy_container_config.tar.gz" of containerized proxy from the server to the proxy 00:00:02.788

@containerized_server @scope_containerized_proxy @proxy

Scenario: Set up the containerized proxy service to support Avahi

@containerized_server @scope_containerized_proxy @proxy

Scenario: Run a containerized proxy

When I run "mgrpxy install podman /tmp/proxy_container_config.tar.gz" on "proxy" 00:30:03.741

+ Show Error + Screenshot

FAIL: mgrpxy install podman /tmp/proxy_container_config.tar.gz returned status code = -1.
Output:
 (ScriptError)
./features/support/remote_node.rb:172:in `run_local'
./features/support/remote_node.rb:120:in `run'
./features/step_definitions/command_steps.rb:792:in `/^I run "([^"]*)" on "([^"]*)"$/'
features/proxy/proxy_container.feature:55:in `I run "mgrpxy install podman /tmp/proxy_container_config.tar.gz" on "proxy"'

@containerized_server @scope_containerized_proxy @proxy

Scenario: Wait until containerized proxy service is active

9
1
Duration: 00:04:10.000

And I wait until "uyuni-proxy-pod" service is active on "proxy" 00:04:10.000

+ Show Error + Screenshot

execution expired (Timeout::Error)
./features/support/commonlib.rb:89:in `repeat_until_timeout'
./features/support/remote_node.rb:189:in `run_until_ok'
./features/step_definitions/command_steps.rb:314:in `/^I wait until "([^"]*)" service is active on "([^"]*)"$/'
features/proxy/proxy_container.feature:58:in `I wait until "uyuni-proxy-pod" service is active on "proxy"'

And I wait until "uyuni-proxy-httpd" service is active on "proxy" 0s

And I wait until "uyuni-proxy-salt-broker" service is active on "proxy" 0s

And I wait until "uyuni-proxy-squid" service is active on "proxy" 0s

And I wait until "uyuni-proxy-ssh" service is active on "proxy" 0s

And I wait until "uyuni-proxy-tftpd" service is active on "proxy" 0s

And I wait until port "8022" is listening on "proxy" container 0s

And I wait until port "80" is listening on "proxy" container 0s

And I wait until port "443" is listening on "proxy" container 0s

And I visit "Proxy" endpoint of this "proxy" 0s

@containerized_server @scope_containerized_proxy @proxy

Scenario: The containerized proxy should be registered automatically

When I follow the left menu "Systems" 00:00:00.063

And I wait until I see the name of "proxy", refreshing the page 00:00:00.673

@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.691

When I follow "Properties" in the content area 00:00:00.069

Then the "monitoring_entitled" checkbox should be disabled 00:00:10.013