@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	91.67 %
Failed	0.00 %
Skipped	8.33 %

Total duration:

00:04:10.577

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

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

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

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

@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

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

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

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

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

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

Then the Salt master can reach "sle_minion" 00:00:03.847

+ Show Info

It took 4 seconds to contact the minion

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

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

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

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

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

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

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

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

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

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

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

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

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

+ 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.507

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

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

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

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

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

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

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

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

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

@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