@containerized_server @scope_containerized_proxy @proxy @private_net

Feature: 0020 - Prepare the containerized branch server for PXE booting

Description: In order to use a containerized proxy as a Retail Branch server
As the system administrator
I make sure the network setup is as expected

File name: proxy_rbs_container_branch_network.feature

Relative path: proxy/proxy_rbs_container_branch_network.feature

Scenarios

Chart

Status

Progress

Passed	0.00 %
Failed	0.00 %
Skipped	100.00 %

Total duration:

00:00:00.000

@containerized_server @scope_containerized_proxy @proxy @private_net

Scenario: Adapt the proxy for Retail

When I rename the proxy for Retail 0s

And I connect the second interface of the proxy to the private network 0s

And I restart all proxy containers 0s

@containerized_server @scope_containerized_proxy @proxy @private_net

Scenario: Check the branch network

Then the "dhcp_dns" host should be present on private network 0s

And name resolution should work on private network 0s

@containerized_server @scope_containerized_proxy @proxy @private_net

Scenario: Let the server know about the new IP and FQDN of the containerized proxy

Given I am authorized for the "Admin" section 0s

When I am on the Systems overview page of this "proxy" 0s

And I follow "Details" in the content area 0s

And I follow "Hardware" in the content area 0s

And I click on "Schedule Hardware Refresh" 0s

Then I should see a "You have successfully scheduled a hardware profile refresh" text 0s

When I wait until event "Hardware List Refresh scheduled by admin" is completed 0s

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "proxy" 0s

And I follow "Details" in the content area 0s

And I follow "Hardware" in the content area 0s

Then I should see a "proxy.example.org" text 0s