@sle_minion @proxy

Feature: 0076 - Move a minion from a proxy to direct connection

File name: min_move_from_and_to_proxy.feature

Relative path: secondary/min_move_from_and_to_proxy.feature

Scenarios

Chart

Status

Progress

Passed	61.54 %
Failed	38.46 %

Total duration:

00:11:40.422

@sle_minion @proxy

Scenario: Log in as org admin user

@sle_minion @proxy

Scenario: Delete minion system profile before bootstrap

3
1
Duration: 00:00:02.809

When I delete "sle_minion" system using the api 00:00:02.809

+ Show Error + Screenshot

unknown error - API failure: Unable to find column position by name: container_runtime [The column name container_runtime was not found in this ResultSet.] [n/a] (SystemCallError)
./features/support/http_client.rb:110:in `call'
./features/support/api_test.rb:108:in `make_api_call'
./features/support/api_test.rb:78:in `block (2 levels) in call'
./features/support/api_test.rb:75:in `synchronize'
./features/support/api_test.rb:75:in `block in call'
features/secondary/min_move_from_and_to_proxy.feature:12:in `I delete "sle_minion" system using the api'

And I perform a full salt minion cleanup on "sle_minion" 0s

And I wait until Salt client is inactive on "sle_minion" 0s

Then "sle_minion" should not be registered 0s

@sle_minion @proxy

Scenario: Bootstrap a minion

1
2
9
Duration: 00:04:16.860

When I follow the left menu "Systems > Bootstrapping" 00:00:00.142

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

When I enter the hostname of "sle_minion" as "hostname" 00:00:00.127

+ Show Info

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

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

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

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

And I select "1-SUSE-KEY-x86_64" from "activationKeys" 00:00:00.072

And I select the hostname of "proxy" from "proxies" if present 00:00:00.059

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

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

+ Show Error

Text 'Bootstrap process initiated.' not found (ScriptError)
./features/step_definitions/navigation_steps.rb:40:in `/^I wait until I see "([^"]*)" text$/'
features/secondary/min_move_from_and_to_proxy.feature:27:in `I wait until I see "Bootstrap process initiated." text'

And I wait until onboarding is completed for "sle_minion" 0s

After Hook 00:00:06.175

+ Show Error

undefined method `map' for an instance of String (NoMethodError)
./features/support/env.rb:211:in `web_session_is_active?'
./features/support/env.rb:182:in `After'

@sle_minion @proxy

Scenario: Check the new bootstrapped minion in System Overview page

2
1
Duration: 00:00:10.013

When I follow the left menu "Salt > Keys" 00:00:10.013

+ Show Error

Unable to find xpath "//aside/div[@id='nav']/nav/ul/li/div/a[contains(.,'Salt')]/parent::div/parent::li" (Capybara::ElementNotFound)
./features/step_definitions/navigation_steps.rb:441:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:433:in `each'
./features/step_definitions/navigation_steps.rb:433:in `each_with_index'
./features/step_definitions/navigation_steps.rb:433:in `/^I follow the left menu "([^"]*)"$/'
features/secondary/min_move_from_and_to_proxy.feature:31:in `I follow the left menu "Salt ) Keys"'

Then I should see a "accepted" text 0s

And the Salt master can reach "sle_minion" 0s

@sle_minion @proxy

Scenario: Check initial connection from minion to proxy

2
1
1
Duration: 00:00:11.375

Given I am on the Systems overview page of this "sle_minion" 00:00:01.346

+ Show Info

Requested /rhn/systems/details/Overview.do?sid=1000010020, got https://uyuni-master-server.sumaci.aws/rhn/manager/login?url_bounce=%2Frhn%2Fsystems%2Fdetails%2FOverview.do%3Fsid%3D1000010020&request_method=GET

When I follow "Details" in the content area 00:00:10.028

+ Show Error + Screenshot

Unable to find link "Details" within #(Capybara::Node::Element tag="section" path="/HTML/BODY[1]/DIV[1]/DIV[1]/SECTION[1]") (Capybara::ElementNotFound)
./features/support/commonlib.rb:193:in `click_link_and_wait'
./features/step_definitions/navigation_steps.rb:366:in `/^I follow "([^"]*)"$/'
./features/step_definitions/navigation_steps.rb:388:in `block (2 levels) in (top (required))'
./features/step_definitions/navigation_steps.rb:387:in `/^I follow "([^"]*)" in the (.+)$/'
features/secondary/min_move_from_and_to_proxy.feature:37:in `I follow "Details" in the content area'

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

Then I should see "proxy" short hostname 0s

@sle_minion @proxy

Scenario: Check initial registration on proxy of minion

Given I am on the Systems overview page of this "proxy" 00:00:01.598

When I follow "Details" in the content area 00:00:00.071

And I follow "Proxy" in the content area 00:00:00.065

Then I should see "sle_minion" hostname 00:00:00.089

@sle_minion @proxy

Scenario: Change from proxy to direct connection

Given I am on the Systems overview page of this "sle_minion" 00:00:01.601

When I follow "Details" in the content area 00:00:00.063

And I follow "Connection" in the content area 00:00:00.065

And I follow "Change" in the content area 00:00:00.064

And I select "None" from "proxies" 00:00:00.070

And I click on "Change Proxy" 00:00:00.072

And I wait until I see "scheduled" text 00:00:00.334

And I follow "Events" 00:00:00.387

And I follow "History" 00:00:00.559

And I wait until I see the event "Apply states [bootstrap.set_proxy] scheduled" completed during last minute, refreshing the page 00:00:23.116

And I wait until I see the event "Apply states [channels] scheduled" completed during last minute, refreshing the page 00:00:11.509

@sle_minion @proxy

Scenario: Check direct connection

Given I am on the Systems overview page of this "sle_minion" 00:00:01.568

When I follow "Details" in the content area 00:00:00.062

And I follow "Connection" in the content area 00:00:00.060

Then I should see a "This system connects directly and not through a Proxy" text 00:00:00.059

@sle_minion @proxy

Scenario: Change connection back to a proxy via SSM

Given I wait for "120" seconds 00:02:00.000

When I follow the left menu "Systems > System List > All" 00:00:00.144

And I click on the clear SSM button 00:00:00.069

And I check the "sle_minion" client 00:00:00.466

And I should see "1" systems selected for SSM 00:00:00.130

And I follow the left menu "Systems > System Set Manager > Overview" 00:00:00.514

And I follow "proxy server" in the content area 00:00:00.071

And I select the hostname of "proxy" from "proxies" if present 00:00:00.077

And I click on "Change Proxy" 00:00:00.057

And I wait until I see "scheduled" text 00:00:00.359

@sle_minion @proxy

Scenario: Check events on the minion

Given I am on the Systems overview page of this "sle_minion" 00:00:01.650

And I follow "Events" 00:00:00.446

And I follow "History" 00:00:00.433

And I wait until I see the event "Apply states [bootstrap.set_proxy] scheduled" completed during last minute, refreshing the page 00:00:00.012

And I wait until I see the event "Apply states [channels] scheduled" completed during last minute, refreshing the page 00:00:34.590

@sle_minion @proxy

Scenario: Check registration on proxy of minion

Given I am on the Systems overview page of this "proxy" 00:00:01.933

When I follow "Details" in the content area 00:00:00.070

And I follow "Proxy" in the content area 00:00:00.064

Then I should see "sle_minion" hostname 00:00:00.091

@sle_minion @proxy

Scenario: Check connection from minion to proxy

Given I am on the Systems overview page of this "sle_minion" 00:00:01.575

When I follow "Details" in the content area 00:00:00.060

And I follow "Connection" in the content area 00:00:00.064

Then I should see "proxy" short hostname 00:00:00.067

@sle_minion @proxy

Scenario: Check events history for failures on the minion

1
1
Duration: 00:03:32.876

Given I am on the Systems overview page of this "sle_minion" 00:00:01.602

Then I check for failed events on history event page 00:03:31.273

+ Show Error + Screenshot

Failures in event history found:

Apply highstate scheduled by admin 2026-05-30 15:44:59 CEST 285
Refresh Ansible inventories scheduled by (system) 2026-05-30 15:16:29 CEST 284
Apply highstate scheduled by admin 2026-05-30 15:15:26 CEST 283
Refresh Ansible inventories scheduled by (system) 2026-05-30 15:14:52 CEST 282
 (ScriptError)
./features/step_definitions/setup_steps.rb:476:in `/^I check for failed events on history event page$/'
features/secondary/min_move_from_and_to_proxy.feature:100:in `I check for failed events on history event page'