@skip_if_github_validation @scope_onboarding @susemanager @uyuni

Feature: 0052 - Bootstrap a Salt minion via the GUI with an activation key

File name: min_bootstrap_activation_key.feature

Relative path: secondary/min_bootstrap_activation_key.feature

Scenarios

Chart

Status

Progress

Passed	87.50 %
Failed	0.00 %
Skipped	12.50 %

Total duration:

00:04:05.867

@skip_if_github_validation @scope_onboarding

Scenario: Log in as org admin user

@skip_if_github_validation @scope_onboarding

Scenario: Delete SLES minion system profile

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

And I perform a full salt minion cleanup on "sle_minion" 00:00:11.562

And I wait until Salt client is inactive on "sle_minion" 00:00:00.453

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

@skip_if_github_validation @scope_onboarding

Scenario: Create a configuration channel for the activation key

When I follow the left menu "Configuration > Channels" 00:00:00.137

And I follow "Create Config Channel" 00:00:00.465

And I enter "Key Channel" as "cofName" 00:00:00.058

And I enter "keychannel" as "cofLabel" 00:00:00.055

And I enter "This is a configuration channel for the activation key" as "cofDescription" 00:00:00.091

And I click on "Create Config Channel" 00:00:01.371

Then I should see a "Key Channel" text 00:00:00.059

@skip_if_github_validation @scope_onboarding

Scenario: Add a configuration file to the key configuration channel

When I follow the left menu "Configuration > Channels" 00:00:00.064

And I follow "Key Channel" 00:00:00.510

And I follow "Create Configuration File or Directory" 00:00:00.368

And I enter "/etc/euler.conf" as "cffPath" 00:00:00.063

And I enter "e^i.pi=-1" in the editor 00:00:00.005

And I click on "Create Configuration File" 00:00:00.735

@skip_if_github_validation @scope_onboarding @susemanager

Scenario: Create a complete minion activation key

When I follow the left menu "Systems > Activation Keys" 0s

And I follow "Create Key" 0s

And I wait for child channels to appear 0s

And I enter "Minion testing" as "description" 0s

And I enter "MINION-TEST" as "key" 0s

And I enter "20" as "usageLimit" 0s

And I select "SLE-Product-SLES15-SP7-Pool for x86_64" from "selectedBaseChannel" 0s

And I wait for child channels to appear 0s

And I include the recommended child channels 0s

And I check "SLE-Module-DevTools15-SP7-Pool for x86_64" 0s

And I check "Fake-RPM-SUSE-Channel" 0s

And I click on "Create Activation Key" 0s

And I follow "Configuration" in the content area 0s

And I follow first "Subscribe to Channels" in the content area 0s

And I check "Key Channel" in the list 0s

And I click on "Continue" 0s

And I follow "Packages" 0s

And I enter "orion-dummy perseus-dummy" as "packages" 0s

And I click on "Update Activation Key" 0s

Then I should see a "Activation key Minion testing has been modified" text 0s

@skip_if_github_validation @scope_onboarding @uyuni

Scenario: Create a complete minion activation key

When I follow the left menu "Systems > Activation Keys" 00:00:00.134

And I follow "Create Key" 00:00:00.341

And I wait for child channels to appear 00:00:01.364

And I enter "Minion testing" as "description" 00:00:00.083

And I enter "MINION-TEST" as "key" 00:00:00.083

And I enter "20" as "usageLimit" 00:00:00.052

And I select "openSUSE Tumbleweed (x86_64)" from "selectedBaseChannel" 00:00:00.080

And I wait for child channels to appear 00:00:00.369

And I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)" 00:00:00.105

And I check "Fake-RPM-SUSE-Channel" 00:00:00.075

And I click on "Create Activation Key" 00:00:00.574

And I follow "Configuration" in the content area 00:00:00.070

And I follow first "Subscribe to Channels" in the content area 00:00:00.060

And I check "Key Channel" in the list 00:00:00.057

And I click on "Continue" 00:00:00.459

And I follow "Packages" 00:00:00.323

And I enter "orion-dummy perseus-dummy" as "packages" 00:00:00.067

And I click on "Update Activation Key" 00:00:00.470

Then I should see a "Activation key Minion testing has been modified" text 00:00:00.054

@skip_if_github_validation @scope_onboarding

Scenario: Bootstrap a SLES minion with an activation key

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

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

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

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

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

And I select "1-MINION-TEST" from "activationKeys" 00:00:00.058

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

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

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

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

@skip_if_github_validation @scope_onboarding

Scenario: Verify that minion bootstrapped with Salt key and packages

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

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

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

+ Show Info

It took 4 seconds to contact the minion

When I wait for "orion-dummy" to be installed on "sle_minion" 00:00:01.266

And I wait for "perseus-dummy" to be installed on "sle_minion" 00:00:00.912

@skip_if_github_validation @scope_onboarding

Scenario: Check system ID of bootstrapped minion

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

Then I run spacecmd listeventhistory for "sle_minion" 00:00:08.257

@skip_if_github_validation @scope_onboarding @susemanager

Scenario: Verify that minion bootstrapped with base channel

Given I am on the Systems page 0s

Then I should see a "SLE-Product-SLES15-SP7-Pool for x86_64" text 0s

@skip_if_github_validation @scope_onboarding @uyuni

Scenario: Verify that minion bootstrapped with base channel

Given I am on the Systems page 00:00:00.249

Then I should see a "openSUSE Tumbleweed (x86_64)" text 00:00:00.521

@skip_if_github_validation @scope_onboarding

Scenario: Verify that minion bootstrapped with configuration channel

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

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

Then I should see a "1 configuration channel" text 00:00:00.065

When I follow "View Files" in the content area 00:00:00.068

Then I should see a "/etc/euler.conf" text 00:00:00.073

And I should see a "Key Channel" text 00:00:00.069

@skip_if_github_validation @scope_onboarding

Scenario: Cleanup: remove the package states

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

When I follow "States" in the content area 00:00:00.067

And I follow "Packages" 00:00:00.689

Then I should see a "Package States" text 00:00:00.060

When I change the state of "orion-dummy" to "Unmanaged" and "" 00:00:00.181

And I change the state of "perseus-dummy" to "Unmanaged" and "" 00:00:00.039

Then I should see a "2 Changes" text 00:00:00.066

When I click save 00:00:00.048

Then I wait until I see "Package states have been saved." text 00:00:00.261

And I click apply 00:00:00.046

And I remove package "orion-dummy" from this "sle_minion" 00:00:02.401

And I remove package "perseus-dummy" from this "sle_minion" 00:00:02.691

@skip_if_github_validation @scope_onboarding

Scenario: Cleanup: remove the key configuration channel

When I follow the left menu "Configuration > Channels" 00:00:00.124

And I follow "Key Channel" 00:00:00.649

And I follow "Delete Channel" 00:00:00.361

And I click on "Delete Config Channel" 00:00:00.062

@skip_if_github_validation @scope_onboarding

Scenario: Cleanup: delete the activation key

When I follow the left menu "Systems > Activation Keys" 00:00:00.695

And I follow "Minion testing" in the content area 00:00:00.069

And I follow "Delete Key" 00:00:00.442

And I click on "Delete Activation Key" 00:00:00.609

Then I should see a "Activation key Minion testing has been deleted." text 00:00:00.077

@skip_if_github_validation @scope_onboarding

Scenario: Check events history for failures on SLES minion with activation key

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

Then I check for failed events on history event page 00:01:01.295