@rhlike_minion
@proxy
Feature: 0023 - Bootstrap a Red Hat-like minion and do some basic operations on it
File name: min_rhlike_salt.feature
Relative path: init_clients/min_rhlike_salt.feature
When
I follow the left menu "Systems > Bootstrapping"
00:00:01.591
Then
I should see a "Bootstrap Minions" text
00:00:00.021
The hostname of rhlike_minion is uyuni-master-rhlike-minion.sumaci.aws
And
I enter "22" as "port"
00:00:00.044
And
I enter "root" as "user"
00:00:00.063
And
I enter "linux" as "password"
00:00:00.049
And
I select "1-RH-LIKE-KEY" from "activationKeys"
00:00:00.113
And
I select the hostname of "proxy" from "proxies" if present
00:00:03.904
And
I click on "Bootstrap"
00:00:00.344
And
I wait until I see "Bootstrap process initiated." text
00:00:42.224
And
I follow the left menu "Systems > System List > All"
00:00:01.235
And
I wait until I see the name of "rhlike_minion", refreshing the page
00:01:10.101
And
I wait at most 300 seconds until onboarding is completed for "rhlike_minion"
00:00:13.977
+ Show Error
+ Show Info
+ Screenshot
unknown error - Event failed (SystemCallError) ./features/step_definitions/navigation_steps.rb:120:in 'block (2 levels) in (top (required))' ./features/support/commonlib.rb:177:in 'block in Object#repeat_until_timeout' ./features/support/commonlib.rb:166:in 'Object#repeat_until_timeout' ./features/step_definitions/navigation_steps.rb:112:in `/^I wait at most (\d+) seconds until the event is completed, refreshing the page$/' ./features/step_definitions/common_steps.rb:165:in `/^I wait at most (\d+) seconds until the event "([^"]*)" is completed in the history$/' ./features/step_definitions/setup_steps.rb:250:in `/^I wait (?:at most (\d+) seconds )?until onboarding is completed for "([^"]*)"$/' ./features/support/env.rb:455:in 'block in (top (required))' features/init_clients/min_rhlike_salt.feature:26:in `I wait at most 300 seconds until onboarding is completed for "rhlike_minion"'
Event Details: Failure
@rhlike_minion
@proxy
Scenario: Check connection from Red Hat-like minion to proxy
Given
I am on the Systems overview page of this "rhlike_minion"
00:00:01.856
When
I follow "Details" in the content area
00:00:00.397
And
I follow "Connection" in the content area
00:00:00.362
Then
I should see "proxy" short hostname
00:00:00.031
@rhlike_minion
@proxy
Scenario: Check registration on proxy of Red Hat-like minion
Given
I am on the Systems overview page of this "proxy"
00:00:01.778
When
I follow "Details" in the content area
00:00:00.379
And
I follow "Proxy" in the content area
00:00:00.363
Then
I should see "rhlike_minion" hostname
00:00:00.023
@rhlike_minion
Scenario: Subscribe the Red Hat-like minion to a base channel
Given
I am on the Systems overview page of this "rhlike_minion"
00:00:02.106
When
I follow "Software" in the content area
00:00:00.378
And
I follow "Software Channels" in the content area
00:00:00.364
And
I wait until I do not see "Loading..." text
00:00:00.082
Warning: Radio button 'Fake-Base-Channel-RH-like' is already checked
And
I wait until I do not see "Loading..." text
00:00:00.312
And
I click on "Next"
00:00:00.360
Then
I should see a "Confirm Software Channel Change" text
00:00:00.051
When
I click on "Confirm"
00:00:00.355
Then
I should see a "Changing the channels has been scheduled." text
00:00:00.088
And
I wait until event "Subscribe channels scheduled by admin" is completed
00:00:17.237
@rhlike_minion
Scenario: Detect latest Salt changes on the Red Hat-like minion
* Tue Oct 27 2026 Marek Czernek- Ignore network status when comparing docker networks - Fix Git state comment formatting - Fix surogateescape encoding typo in openscap module - Prevent schedule loss during master connection loss (bsc#1280583) - Added: * fix-docker-tests-785.patch * repair-git-state-comment-formatting-788.patch * fix-surogateescape-typo-in-openscap-module-790.patch * prevent-schedule-loss-when-minion-loses-master-conne.patch * Thu Oct 15 2026 Victor Zhestkov - Bundled python was updated to 3.11.17 with CVE fixes: * CVE-2025-13462: Don't change tarfile.TarInfo type from AREGTYPE to DIRTYPE when parsing GNU long name or link headers
@rhlike_minion
Scenario: Check events history for failures on Red Hat-like minion
Given
I am on the Systems overview page of this "rhlike_minion"
00:00:01.726
Failures in event history found: Hardware List Refresh scheduled by (system) 2026-11-19 09:12:07 CET 7 (ScriptError) ./features/step_definitions/setup_steps.rb:526:in `/^I check for failed events on history event page$/' ./features/support/env.rb:455:in 'block in (top (required))' features/init_clients/min_rhlike_salt.feature:60:in `I check for failed events on history event page'