@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:10:04.245

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

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

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

When I follow "Hardware" 00:00:01.596

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

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

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

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

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

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

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

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

When I follow "Hardware" 00:00:00.645

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

+ Show Info

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

And I follow "Hardware" 00:00:00.624

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

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

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

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

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

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

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

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

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

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

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

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

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

+ Show Info

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

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

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

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

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

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

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

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

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