@deblike_minion
@proxy
Feature: 0022 - Bootstrap a Debian-like minion and do some basic operations on it
File name: min_deblike_salt.feature
Relative path: init_clients/min_deblike_salt.feature
When
I follow the left menu "Systems > Bootstrapping"
00:00:00.161
Then
I should see a "Bootstrap Minions" text
00:00:00.073
The hostname of deblike_minion is uyuni-master-deblike-minion
And
I enter "22" as "port"
00:00:00.065
And
I enter "root" as "user"
00:00:00.086
And
I enter "linux" as "password"
00:00:00.072
And
I select "1-DEBLIKE-KEY" from "activationKeys"
00:00:00.078
And
I select the hostname of "proxy" from "proxies" if present
00:00:03.021
And
I click on "Bootstrap"
00:00:00.077
And
I wait until I see "Bootstrap process initiated." text
00:00:44.541
And
I follow the left menu "Systems > System List > All"
00:00:00.299
And
I wait until I see the name of "deblike_minion", refreshing the page
00:00:59.391
And
I wait until onboarding is completed for "deblike_minion"
00:04:22.550
+ Show Error
+ Screenshot
execution expired (Timeout::Error) ./features/support/commonlib.rb:89:in `repeat_until_timeout' ./features/step_definitions/navigation_steps.rb:70:in `/^I wait until I see "([^"]*)" (text|regex), refreshing the page$/' ./features/step_definitions/common_steps.rb:157:in `/^I wait (\d+) seconds until the event is picked up and (\d+) seconds until the event "([^"]*)" is completed$/' ./features/step_definitions/setup_steps.rb:218:in `/^I wait at most (\d+) seconds until onboarding is completed for "([^"]*)"$/' ./features/step_definitions/setup_steps.rb:230:in `/^I wait until onboarding is completed for "([^"]*)"$/' features/init_clients/min_deblike_salt.feature:26:in `I wait until onboarding is completed for "deblike_minion"'
And
I query latest Salt changes on Debian-like system "deblike_minion"
0s
@deblike_minion
@proxy
Scenario: Check connection from the Debian-like minion to proxy
Given
I am on the Systems overview page of this "deblike_minion"
00:00:01.577
When
I follow "Details" in the content area
00:00:00.079
And
I follow "Connection" in the content area
00:00:00.065
Then
I should see "proxy" short hostname
00:00:00.066
@deblike_minion
@proxy
Scenario: Check registration on proxy of the Debian-like minion
Given
I am on the Systems overview page of this "proxy"
00:00:01.721
When
I follow "Details" in the content area
00:00:00.060
And
I follow "Proxy" in the content area
00:00:00.066
Then
I should see "deblike_minion" hostname
00:00:00.095
@deblike_minion
Scenario: Subscribe the Debian-like minion to a base channel
Given
I am on the Systems overview page of this "deblike_minion"
00:00:01.847
When
I follow "Software" in the content area
00:00:00.068
And
I follow "Software Channels" in the content area
00:00:00.066
And
I wait until I do not see "Loading..." text
00:00:00.070
Warning: Radio button 'Fake-Base-Channel-Debian-like' is already checked
And
I wait until I do not see "Loading..." text
00:00:00.382
And
I click on "Next"
00:00:00.060
Then
I should see a "Confirm Software Channel Change" text
00:00:00.060
When
I click on "Confirm"
00:00:00.074
Then
I should see a "Changing the channels has been scheduled." text
00:00:00.290
And
I wait until event "Subscribe channels scheduled by admin" is completed
00:00:18.581
@deblike_minion
Scenario: Detect latest Salt changes on the Debian-like minion
* Thu May 14 2026 Victor Zhestkov- Use non vendored tornado with Python 3.11 (bsc#1257583, bsc#1259700) - Added: * use-non-vendored-tornado-with-python-3.11.patch * Thu May 7 2026 Pablo Suárez Hernández - Specify .SO ver explicitly in BuildRequire for libsodium * Mon Apr 27 2026 Marek Czernek - BDSA-2025-60810: Harden Tornado from invalid HTTP reason phrases - Read full URI from ldap pillar config (bsc#1254900) - Added: * bdsa-2025-60810-harden-against-invalid-http-reason-p.patch * read-full-uri-from-ldap-pillar-config-753.patch * Tue Apr 14 2026 Marek Czernek - Fix testsuite failures - Added: