@skip_if_github_validation @scope_onboarding @proxy @susemanager @uyuni

Feature: 0053 - Register a Salt minion via API

File name: min_bootstrap_api.feature

Relative path: secondary/min_bootstrap_api.feature

Scenarios

Chart

Status

Progress

Passed	83.33 %
Failed	8.33 %
Skipped	8.33 %

Total duration:

00:07:34.399

@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 before API bootstrap test

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

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

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

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

@skip_if_github_validation @scope_onboarding

Scenario: Bootstrap a SLES minion via API

@skip_if_github_validation @scope_onboarding

Scenario: Check new minion bootstrapped via API in System Overview page

1
1
4
Duration: 00:05:15.241

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

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

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

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

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

+ 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/secondary/min_bootstrap_api.feature:29:in `I wait until onboarding is completed for "sle_minion"'

Then the Salt master can reach "sle_minion" 0s

@skip_if_github_validation @scope_onboarding

Scenario: Check contact method of this minion

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

Then I should see a "Default" text 00:00:00.082

@skip_if_github_validation @scope_onboarding @proxy

Scenario: Check registration on proxy of minion bootstrapped via API

Given I am on the Systems overview page of this "proxy" 00:00:01.843

When I follow "Details" in the content area 00:00:00.088

And I follow "Proxy" in the content area 00:00:00.063

Then I should see "sle_minion" hostname 00:00:00.091

@skip_if_github_validation @scope_onboarding

Scenario: Check spacecmd system ID of minion bootstrapped via API

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

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

@skip_if_github_validation @scope_onboarding @susemanager

Scenario: API bootstrap: subscribe to base channel

Given I am on the Systems overview page of this "sle_minion" 0s

When I follow "Software" in the content area 0s

And I follow "Software Channels" in the content area 0s

And I wait until I do not see "Loading..." text 0s

And I check radio button "SLE-Product-SLES15-SP7-Pool for x86_64" 0s

And I wait until I do not see "Loading..." text 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 "Next" 0s

Then I should see a "Confirm Software Channel Change" text 0s

When I click on "Confirm" 0s

Then I should see a "Changing the channels has been scheduled." text 0s

And I wait until event "Subscribe channels scheduled" is completed 0s

@skip_if_github_validation @scope_onboarding @uyuni

Scenario: API bootstrap: subscribe to base channel

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

When I follow "Software" in the content area 00:00:00.069

And I follow "Software Channels" in the content area 00:00:00.062

And I wait until I do not see "Loading..." text 00:00:00.064

And I check radio button "openSUSE Tumbleweed (x86_64)" 00:00:00.191

+ Show Info

Warning: Radio button 'openSUSE Tumbleweed (x86_64)' is already checked

And I wait until I do not see "Loading..." text 00:00:00.392

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

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

And I click on "Next" 00:00:00.077

Then I should see a "Confirm Software Channel Change" text 00:00:00.059

When I click on "Confirm" 00:00:00.072

Then I should see a "Changing the channels has been scheduled." text 00:00:00.488

And I wait until event "Subscribe channels scheduled" is completed 00:00:22.836

@skip_if_github_validation @scope_onboarding

Scenario: Check events history for failures on SLES minion after API bootstrap

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

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

@skip_if_github_validation @scope_onboarding

Scenario: Bootstrap via API a non-existing system

@skip_if_github_validation @scope_onboarding

Feature: 0053 - Register a Salt minion via API

Scenarios

Scenario: Log in as org admin user

Scenario: Delete SLES minion system profile before API bootstrap test

Scenario: Bootstrap a SLES minion via API

Scenario: Check new minion bootstrapped via API in System Overview page

Scenario: Check contact method of this minion

Scenario: Check registration on proxy of minion bootstrapped via API

Scenario: Check spacecmd system ID of minion bootstrapped via API

Scenario: API bootstrap: subscribe to base channel

Scenario: API bootstrap: subscribe to base channel

Scenario: Check events history for failures on SLES minion after API bootstrap

Scenario: Bootstrap via API a non-existing system

Scenario: Bootstrap a salt-ssh system with activation key and default contact method