@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:11:33.790

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

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

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

When I follow "Hardware" 00:00:00.598

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

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

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

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

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

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

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

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

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

When I follow "Hardware" 00:00:00.659

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

And I follow "Hardware" 00:00:00.603

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

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

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

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

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

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

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

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

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

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

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

And 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.143

+ Show Info

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

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

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

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

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

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

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

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

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