@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

Scenarios

Chart

Status

Progress

Passed	91.67 %
Failed	0.00 %
Skipped	8.33 %

Total duration:

00:04:12.519

@scope_salt_ssh @scope_onboarding @ssh_minion @skip_if_github_validation

Scenario: Log in as org admin user

@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:05.505

And I perform a full salt minion cleanup on "ssh_minion" 00:00:04.631

And I wait until Salt client is inactive on "ssh_minion" 00:00:00.428

Then "ssh_minion" should not be registered 00:00:00.995

@scope_salt_ssh @scope_onboarding @ssh_minion @skip_if_github_validation @proxy

Scenario: Block direct access from server to sshminion to test proxy as jumphost

@scope_salt_ssh @scope_onboarding @ssh_minion @skip_if_github_validation

Scenario: Bootstrap a SLES SSH minion via API

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

And I wait until I see the name of "ssh_minion", refreshing the page 00:00:31.002

And I wait until onboarding is completed for "ssh_minion" 00:00:54.083

@scope_salt_ssh @scope_onboarding @ssh_minion @skip_if_github_validation

Scenario: Check contact method of this Salt SSH system

Given I am on the Systems overview page of this "ssh_minion" 00:00:01.634

Then I should see a "Push via SSH" text 00:00:00.218

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

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

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

Then I should see "ssh_minion" hostname 00:00:00.215

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

Then I run spacecmd listeventhistory for "ssh_minion" 00:00:09.214

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

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

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

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

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

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

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

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

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

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

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

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

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

@scope_salt_ssh @scope_onboarding @ssh_minion @skip_if_github_validation @proxy

Feature: 0048 - Register a salt-ssh system via API

Scenarios

Scenario: Log in as org admin user

Scenario: Delete SSH minion system profile before API bootstrap test

Scenario: Block direct access from server to sshminion to test proxy as jumphost

Scenario: Bootstrap a SLES SSH minion via API

Scenario: Check new API bootstrapped salt-ssh system in System Overview page

Scenario: Check contact method of this Salt SSH system

Scenario: Check registration on proxy of SSH minion bootstrapped via API

Scenario: Check spacecmd system ID of SSH minion bootstrapped via API

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

Scenario: API bootstrap: subscribe SSH minion to base channel

Scenario: API bootstrap: subscribe SSH minion to base channel

Scenario: Cleanup and flush the firewall rules