@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

Scenarios

Chart

Status

Progress

Passed	100.00 %
Failed	0.00 %

Total duration:

00:04:23.580

@skip_if_github_validation @sle_minion @scope_onboarding

Scenario: Log in as org admin user

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

When I follow "Reactivation" 00:00:00.593

And I click on "Generate New Key" 00:00:00.712

Then I should see a "Key:" text 00:00:00.066

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

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.131

+ Show Info

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

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

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

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

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

And I wait until I see "A salt key for this host" text 00:00:00.264

Then I should not see a "GenericSaltError" text 00:00:00.062

And I should see a "seems to already exist, please check!" text 00:00:00.064

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

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

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

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

+ Show Info

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

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

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

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

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

And I wait until I see "seems to already exist, please check!" text 00:00:00.262

Then I should not see a "GenericSaltError" text 00:00:00.062

And I should see a "with minion id" text 00:00:00.065

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

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

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

+ Show Info

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

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

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

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

And I enter the reactivation key of "sle_minion" 00:00:02.253

+ Show Info

Reactivation Key: re-1-d24dc553a7a4460f8c23a8461d9acecc

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

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

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

And I follow the left menu "Systems > System List > All" 00:00:00.152

And I wait until I see the name of "sle_minion", refreshing the page 00:00:00.713

And I wait until onboarding is completed for "sle_minion" 00:01:23.177

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

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

And I follow "History" in the content area 00:00:00.074

And I wait until I see "Server reactivated as Salt minion" text, refreshing the page 00:00:00.094

And I wait until event "Apply states [certs, channels, packages, services.salt-minion] scheduled" is completed 00:00:02.274

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

Then "sle_minion" should not be registered 00:00:00.949

When I perform a full salt minion cleanup on "sle_minion" 00:00:07.879

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

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

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

+ Show Info

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

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

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

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

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

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

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

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

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

And I wait until I see the name of "sle_minion", refreshing the page 00:01:11.475

And I wait until onboarding is completed for "sle_minion" 00:00:08.692