@skip_if_github_validation @sle_minion @scope_salt

Feature: 0059 - Verify that Salt mgrcompat state works when the new module.run syntax is enabled

File name: min_salt_mgrcompat_state.feature

Relative path: secondary/min_salt_mgrcompat_state.feature

Scenarios

Chart

Status

Progress

Passed	100.00 %
Failed	0.00 %

Total duration:

00:12:12.985

@skip_if_github_validation @sle_minion @scope_salt

Scenario: Log in as org admin user

@skip_if_github_validation @sle_minion @scope_salt

Scenario: Remove mgrcompat module from minion synced modules and schedule Hardware Refresh

Given I remove "minion/extmods/states/mgrcompat.py" from salt cache on "sle_minion" 00:00:00.800

And I remove "minion/extmods/states/__pycache__/mgrcompat*" from salt cache on "sle_minion" 00:00:00.507

And I am on the Systems overview page of this "sle_minion" 00:00:01.794

When I follow "Hardware" 00:00:00.718

And I click on "Schedule Hardware Refresh" 00:00:00.781

Then I should see a "You have successfully scheduled a hardware profile refresh" text 00:00:00.119

When I wait until event "Hardware List Refresh scheduled" is completed 00:00:38.907

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "sle_minion" 00:00:02.508

@skip_if_github_validation @sle_minion @scope_salt

Scenario: Remove saltutil grain and mgrcompat module from minion and schedule Hardware Refresh

Given I remove "minion/extmods/states/mgrcompat.py" from salt cache on "sle_minion" 00:00:00.450

And I remove "minion/extmods/states/__pycache__/mgrcompat*" from salt cache on "sle_minion" 00:00:00.486

And I store "grains: {__suse_reserved_saltutil_states_support: False}" into file "custom_grains.conf" in salt minion config directory on "sle_minion" 00:00:00.460

And I refresh salt-minion grains on "sle_minion" 00:00:02.286

And I am on the Systems overview page of this "sle_minion" 00:00:02.273

When I follow "Hardware" 00:00:00.725

And I click on "Schedule Hardware Refresh" 00:00:00.775

Then I should see a "You have successfully scheduled a hardware profile refresh" text 00:00:00.121

When I wait until event "Hardware List Refresh scheduled" is completed 00:00:38.775

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "sle_minion" 00:00:02.422

@skip_if_github_validation @sle_minion @scope_salt

Scenario: Delete SLES minion system profile before mgrcompat test

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

When I follow "Delete System" 00:00:00.579

Then I should see a "Confirm System Profile Deletion" text 00:00:00.063

When I click on "Delete Profile" 00:00:00.062

And I wait until I see "has been deleted" text 00:04:03.096

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

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

@skip_if_github_validation @sle_minion @scope_salt

Scenario: Enable new module.run syntax on the minion and perform registration

Given I store "use_superseded: [module.run]" into file "custom_modulerun.conf" in salt minion config directory on "sle_minion" 00:00:00.456

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

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

When I enter the hostname of "sle_minion" as "hostname" 00:00:00.148

+ Show Info

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

And I enter "22" as "port" 00:00:00.061

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

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

And I select the hostname of "proxy" from "proxies" if present 00:00:00.077

And I click on "Bootstrap" 00:00:00.065

And I wait until I see "Bootstrap process initiated." text 00:00:29.142

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

@skip_if_github_validation @sle_minion @scope_salt

Scenario: Check if onboarding for the minion with the new module.run syntax was successful

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

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

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

@skip_if_github_validation @sle_minion @scope_salt

Scenario: Check that installed packages are visible with the new module.run syntax

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

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

And I follow "List / Remove" 00:00:00.672

Then I should see a "aaa_base" text 00:00:00.130

@skip_if_github_validation @sle_minion @scope_salt

Scenario: Check that Hardware Refresh button works on a SLE minion with new module.run syntax

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

And I follow "Hardware" 00:00:00.701

And I click on "Schedule Hardware Refresh" 00:00:01.683

Then I should see a "You have successfully scheduled a hardware profile refresh" text 00:00:00.113

When I wait until event "Hardware List Refresh scheduled" is completed 00:00:22.105

And I wait until there is no Salt job calling the module "hardware.profileupdate" on "sle_minion" 00:00:02.328

@skip_if_github_validation @sle_minion @scope_salt

Scenario: Cleanup: Delete profile of the minion and disable new module.run syntax

When I remove "custom_modulerun.conf" from salt minion config directory on "sle_minion" 00:00:00.456

And I remove "custom_grains.conf" from salt minion config directory on "sle_minion" 00:00:00.444

And I delete "sle_minion" system using the api 00:00:04.320

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

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

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

@skip_if_github_validation @sle_minion @scope_salt

Scenario: Cleanup: bootstrap again the minion after mgrcompat tests

When I perform a full salt minion cleanup on "sle_minion" 00:00:04.869

And I follow the left menu "Systems > Bootstrapping" 00:00:00.077

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

When I enter the hostname of "sle_minion" as "hostname" 00:00:00.151

+ Show Info

The hostname of sle_minion is uyuni-master-suse-minion.sumaci.aws

And I enter "22" as "port" 00:00:00.052

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

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

And I select "1-SUSE-KEY-x86_64" from "activationKeys" 00:00:00.071

And I select the hostname of "proxy" from "proxies" if present 00:00:00.061

And I click on "Bootstrap" 00:00:00.062

And I wait until I see "Bootstrap process initiated." text 00:00:44.513

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