@skip_if_github_validation
@sle_minion
@scope_onboarding
Feature: 0054 - Bootstrapping with reactivation key
Description: In order to re-register valid minions
As an authorized user
I want to avoid re-registration with invalid input parameters
File name: min_bootstrap_reactivation.feature
Relative path: secondary/min_bootstrap_reactivation.feature
@skip_if_github_validation
@sle_minion
@scope_onboarding
Scenario: Generate a re-activation key
Given
I am on the Systems overview page of this "sle_minion"
00:00:02.382
When
I follow "Reactivation"
00:00:00.503
And
I click on "Generate New Key"
00:00:00.629
Then
I should see a "Key:" text
00:00:00.070
@skip_if_github_validation
@sle_minion
@scope_onboarding
Scenario: Bootstrap should fail when minion already exists
When
I follow the left menu "Systems > Bootstrapping"
00:00:00.086
Then
I should see a "Bootstrap Minions" text
00:00:00.064
The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws
And
I enter "22" as "port"
00:00:00.054
And
I enter "root" as "user"
00:00:00.060
And
I enter "linux" as "password"
00:00:00.060
And
I click on "Bootstrap"
00:00:00.067
And
I wait until I see "A salt key for this host" text
00:00:00.274
Then
I should not see a "GenericSaltError" text
00:00:00.064
And
I should see a "seems to already exist, please check!" text
00:00:00.065
@skip_if_github_validation
@sle_minion
@scope_onboarding
Scenario: Bootstrap should fail when system already exists in the server
Given
I delete "sle_minion" key in the Salt master
00:00:03.666
When
I follow the left menu "Systems > Bootstrapping"
00:00:00.064
Then
I should see a "Bootstrap Minions" text
00:00:00.073
The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws
And
I enter "22" as "port"
00:00:00.055
And
I enter "root" as "user"
00:00:00.058
And
I enter "linux" as "password"
00:00:00.059
And
I click on "Bootstrap"
00:00:00.063
And
I wait until I see "seems to already exist, please check!" text
00:00:00.272
Then
I should not see a "GenericSaltError" text
00:00:00.065
And
I should see a "with minion id" text
00:00:00.067
@skip_if_github_validation
@sle_minion
@scope_onboarding
Scenario: Bootstrap a SLES minion with reactivation key
When
I follow the left menu "Systems > Bootstrapping"
00:00:00.066
Then
I should see a "Bootstrap Minions" text
00:00:00.067
The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws
And
I enter "22" as "port"
00:00:00.052
And
I enter "root" as "user"
00:00:00.058
And
I enter "linux" as "password"
00:00:00.060
Reactivation Key: re-1-5e44ed676fde4beea5e2cae880dda3cd
And
I select "1-SUSE-KEY-x86_64" from "activationKeys"
00:00:00.078
And
I click on "Bootstrap"
00:00:00.059
And
I wait until I see "Bootstrap process initiated." text
00:00:27.731
And
I follow the left menu "Systems > System List > All"
00:00:00.170
And
I wait until I see the name of "sle_minion", refreshing the page
00:00:00.712
And
I wait until onboarding is completed for "sle_minion"
00:01:20.477
@skip_if_github_validation
@sle_minion
@scope_onboarding
Scenario: Check the events history for the reactivation
Given
I am on the Systems overview page of this "sle_minion"
00:00:01.722
When
I follow "Events" in the content area
00:00:00.085
And
I follow "History" in the content area
00:00:00.090
And
I wait until I see "Server reactivated as Salt minion" text, refreshing the page
00:00:00.098
And
I wait until event "Apply states [certs, channels, packages, services.salt-minion] scheduled" is completed
00:00:02.357
@skip_if_github_validation
@sle_minion
@scope_onboarding
Scenario: Cleanup: delete SLES minion after reactivation tests
When
I delete "sle_minion" system using the api
00:00:03.459
Then
"sle_minion" should not be registered
00:00:00.949
When
I perform a full salt minion cleanup on "sle_minion"
00:00:10.314
@skip_if_github_validation
@sle_minion
@scope_onboarding
Scenario: Cleanup: bootstrap a SLES minion after reactivation tests
And
I follow the left menu "Systems > Bootstrapping"
00:00:00.078
Then
I should see a "Bootstrap Minions" text
00:00:00.067
The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws
And
I enter "22" as "port"
00:00:00.057
And
I enter "root" as "user"
00:00:00.062
And
I enter "linux" as "password"
00:00:00.065
And
I select "1-SUSE-KEY-x86_64" from "activationKeys"
00:00:00.082
And
I select the hostname of "proxy" from "proxies" if present
00:00:00.067
And
I click on "Bootstrap"
00:00:00.067
And
I wait until I see "Bootstrap process initiated." text
00:00:38.875
When
I follow the left menu "Systems > System List > All"
00:00:00.165
And
I wait until I see the name of "sle_minion", refreshing the page
00:00:58.144
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/secondary/min_bootstrap_reactivation.feature:86:in `I wait until onboarding is completed for "sle_minion"'