@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	76.92 %
Failed	23.08 %

Total duration:

00:10:49.959

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

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

+ 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
1
9
Duration: 00:04:10.723

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

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

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

+ Show Info

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

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

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

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

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

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

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

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

+ Show Error + Screenshot

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

@sle_minion @proxy

Scenario: Check the new bootstrapped minion in System Overview page

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

Then I should see a "accepted" text 00:00:00.338

And the Salt master can reach "sle_minion" 00:00:03.379

+ Show Info

It took 3 seconds to contact the minion

@sle_minion @proxy

Scenario: Check initial connection from minion to proxy

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

And I follow "Events" 00:00:00.404

And I follow "History" 00:00:00.423

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

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

@sle_minion @proxy

Scenario: Check direct connection

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

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

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

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

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

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

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

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

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

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

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

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

@sle_minion @proxy

Scenario: Check events on the minion

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

And I follow "Events" 00:00:00.459

And I follow "History" 00:00:00.430

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

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

@sle_minion @proxy

Scenario: Check registration on proxy of minion

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

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

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

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

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

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

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

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:03.033

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

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

+ Show Error + Screenshot

Failures in event history found:

Execute playbook 'basic_tests.yml' scheduled by admin 2026-05-30 03:46:55 CEST 294
Execute playbook 'basic_tests.yml' scheduled by admin 2026-05-30 03:45:32 CEST 293
Execute playbook 'basic_tests.yml' scheduled by admin 2026-05-30 03:43:50 CEST 292
Execute playbook 'basic_tests.yml' scheduled by admin 2026-05-30 03:42:25 CEST 291
Execute playbook 'basic_tests.yml' scheduled by admin 2026-05-30 03:41:14 CEST 290
Execute playbook 'playbook_orion_dummy.yml' scheduled by admin 2026-05-30 03:40:23 CEST 289
Refresh Ansible inventories scheduled by (system) 2026-05-30 03:38:27 CEST 285
 (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'