@scope_salt_ssh
@scope_onboarding
@ssh_minion
@skip_if_github_validation
@proxy
@susemanager
@uyuni
Feature: 0048 - Register a salt-ssh system via API
File name: minssh_bootstrap_api.feature
Relative path: secondary/minssh_bootstrap_api.feature
@scope_salt_ssh
@scope_onboarding
@ssh_minion
@skip_if_github_validation
Scenario: Delete SSH minion system profile before API bootstrap test
When
I delete "ssh_minion" system using the api
00:00:04.861
And
I perform a full salt minion cleanup on "ssh_minion"
00:00:05.017
And
I wait until Salt client is inactive on "ssh_minion"
00:00:00.450
Then
"ssh_minion" should not be registered
00:00:01.179
@scope_salt_ssh
@scope_onboarding
@ssh_minion
@skip_if_github_validation
Scenario: Check new API bootstrapped salt-ssh system in System Overview page
When
I follow the left menu "Systems > System List > All"
00:00:00.234
And
I wait until I see the name of "ssh_minion", refreshing the page
00:00:30.976
And
I wait until onboarding is completed for "ssh_minion"
00:01:12.357
@scope_salt_ssh
@scope_onboarding
@ssh_minion
@skip_if_github_validation
@proxy
Scenario: Check registration on proxy of SSH minion bootstrapped via API
Given
I am on the Systems overview page of this "proxy"
00:00:01.863
When
I follow "Details" in the content area
00:00:00.083
And
I follow "Proxy" in the content area
00:00:00.072
Then
I should see "ssh_minion" hostname
00:00:00.098
@scope_salt_ssh
@scope_onboarding
@ssh_minion
@skip_if_github_validation
Scenario: Check spacecmd system ID of SSH minion bootstrapped via API
Given
I am on the Systems overview page of this "ssh_minion"
00:00:01.943
Then
I run spacecmd listeventhistory for "ssh_minion"
00:00:07.405
@scope_salt_ssh
@scope_onboarding
@ssh_minion
@skip_if_github_validation
Scenario: Check events history for failures on SSH minion after API bootstrap
Given
I am on the Systems overview page of this "ssh_minion"
00:00:01.790
Then
I check for failed events on history event page
00:00:40.917
@scope_salt_ssh
@scope_onboarding
@ssh_minion
@skip_if_github_validation
@susemanager
Scenario: API bootstrap: subscribe SSH minion to base channel
Given
I am on the Systems overview page of this "ssh_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
@scope_salt_ssh
@scope_onboarding
@ssh_minion
@skip_if_github_validation
@uyuni
Scenario: API bootstrap: subscribe SSH minion to base channel
Given
I am on the Systems overview page of this "ssh_minion"
00:00:01.827
When
I follow "Software" in the content area
00:00:00.086
And
I follow "Software Channels" in the content area
00:00:00.077
And
I wait until I do not see "Loading..." text
00:00:00.074
Warning: Radio button 'openSUSE Tumbleweed (x86_64)' is already checked
And
I wait until I do not see "Loading..." text
00:00:00.425
And
I check "Uyuni Client Tools for openSUSE Tumbleweed (x86_64) (Development)"
00:00:00.045
And
I check "Fake-RPM-SUSE-Channel"
00:00:00.042
And
I click on "Next"
00:00:00.068
Then
I should see a "Confirm Software Channel Change" text
00:00:00.065
When
I click on "Confirm"
00:00:00.078
Then
I should see a "Changing the channels has been scheduled." text
00:00:00.431
And
I wait until event "Subscribe channels scheduled" is completed
00:00:38.649