@skip_if_github_validation
@scope_ansible
@sle_minion
@bug_reported
@susemanager
Feature: 0075 - Operate an Ansible control node in a normal minion
Description: * Related GitHub Card: https://github.com/SUSE/spacewalk/issues/30427
File name: min_ansible_control_node.feature
Relative path: secondary/min_ansible_control_node.feature
@skip_if_github_validation
@scope_ansible
@sle_minion
@bug_reported
@susemanager
Scenario: Pre-requisite: Subscribe SUSE minions to SLE-Module-Python3-15-SP7-Pool for x86_64
Given
I am on the Systems overview page of this "sle_minion"
0s
When
I follow "Software" in the content area
0s
And
I follow "Software Channels" in the content area
0s
And
I check "SLE-Module-Python3-15-SP7-Pool for x86_64" by label
0s
And
I click on "Next"
0s
And
I click on "Confirm"
0s
And
I wait until I see "Changing the channels has been scheduled." text
0s
And
I follow "scheduled"
0s
And
I wait until I see "1 system successfully completed this action" text, refreshing the page
0s
@skip_if_github_validation
@scope_ansible
@sle_minion
@bug_reported
Scenario: Enable "Ansible control node" system type
Given
I am on the Systems overview page of this "sle_minion"
00:00:01.585
When
I store the current last event id for "sle_minion"
00:00:02.171
And
I follow "Properties" in the content area
00:00:00.072
And
I check "ansible_control_node"
00:00:00.081
And
I click on "Update Properties"
00:00:02.013
Then
I wait until I see "Ansible Control Node type has been applied." text
00:00:00.094
@skip_if_github_validation
@scope_ansible
@sle_minion
@bug_reported
Scenario: Check that the automatic Ansible inventory refresh succeeds
Given
I am on the Systems overview page of this "sle_minion"
00:00:01.792
When
I wait until a new "Refresh Ansible inventories scheduled by (system)" event is completed for "sle_minion"
00:00:04.188
+ Show Error
+ Screenshot
Action 288 failed: uyuni-master-suse-minion.sumaci.aws: 'ansible.targets' is not available. (RuntimeError) ./features/support/commonlib.rb:951:in `block in wait_action_complete' ./features/support/commonlib.rb:100:in `block in repeat_until_timeout' ./features/support/commonlib.rb:89:in `repeat_until_timeout' ./features/support/commonlib.rb:946:in `wait_action_complete' ./features/step_definitions/command_steps.rb:1873:in `/^I wait until a new "([^"]*)" event is completed for "([^"]*)"$/' features/secondary/min_ansible_control_node.feature:39:in `I wait until a new "Refresh Ansible inventories scheduled by (system)" event is completed for "sle_minion"'
@skip_if_github_validation
@scope_ansible
@sle_minion
@bug_reported
Scenario: Apply highstate and check that Ansible is installed
Given
I am on the Systems overview page of this "sle_minion"
00:00:01.533
When
I follow "States" in the content area
00:00:00.072
And
I click on "Apply Highstate"
00:00:00.060
And
I wait until event "Apply highstate scheduled" is completed
00:00:55.310
Then
"ansible" should be installed on "sle_minion"
00:00:00.799
@skip_if_github_validation
@scope_ansible
@sle_minion
@bug_reported
Scenario: The Ansible tab appears in the system overview page
Given
I am on the Systems overview page of this "sle_minion"
00:00:01.555
When
I follow "Ansible" in the content area
00:00:00.079
Then
I should see a "Ansible Control Node Configuration" text
00:00:00.061
@skip_if_github_validation
@scope_ansible
@sle_minion
@bug_reported
Scenario: Configure some inventory and playbooks path
Given
I am on the Systems overview page of this "sle_minion"
00:00:01.724
When
I follow "Ansible" in the content area
00:00:00.063
Then
I should see a "Ansible Control Node Configuration" text
00:00:00.058
And
I enter "/srv/playbooks/" as "new_playbook_path_input"
00:00:00.183
And
I click on "new_playbook_path_save"
00:00:00.056
And
I enter "/srv/playbooks/orion_dummy/hosts" as "new_inventory_path_input"
00:00:00.100
And
I click on "new_inventory_path_save"
00:00:00.063
@skip_if_github_validation
@scope_ansible
@sle_minion
@bug_reported
@bug_reported
Scenario: Display inventories
Given
I am on the Systems overview page of this "sle_minion"
00:00:01.725
When
I follow "Ansible" in the content area
00:00:00.064
And
I follow "Inventories" in the content area
00:00:00.062
And
I wait until I see "/srv/playbooks/orion_dummy/hosts" text
00:00:00.241
And
I click on the inventory accordion for "/srv/playbooks/orion_dummy/hosts"
00:00:00.051
Then
I wait until I see "myself" text
00:00:07.254
@skip_if_github_validation
@scope_ansible
@sle_minion
@bug_reported
Scenario: Discover playbooks and display them
Given
I am on the Systems overview page of this "sle_minion"
00:00:01.627
When
I follow "Ansible" in the content area
00:00:00.064
And
I follow "Playbooks" in the content area
00:00:00.069
And
I wait until I see "/srv/playbooks" text
00:00:00.247
And
I click on "/srv/playbooks"
00:00:00.062
Then
I wait until I see "/srv/playbooks/orion_dummy/playbook_orion_dummy.yml" text
00:00:05.202
And
I wait until I see "/srv/playbooks/basic_tests.yml" text
00:00:00.066
@skip_if_github_validation
@scope_ansible
@sle_minion
@bug_reported
Scenario: Run a playbook using custom inventory
Given
I am on the Systems overview page of this "sle_minion"
00:00:01.622
When
I follow "Ansible" in the content area
00:00:00.062
And
I follow "Playbooks" in the content area
00:00:00.057
And
I wait until I see "/srv/playbooks" text
00:00:00.245
And
I click on "/srv/playbooks"
00:00:00.050
And
I wait until I see "/srv/playbooks/orion_dummy/playbook_orion_dummy.yml" text
00:00:05.170
And
I click on "orion_dummy/playbook_orion_dummy.yml"
00:00:00.060
And
I wait until I see "Playbook Content" text
00:00:00.948
And
I select "/srv/playbooks/orion_dummy/hosts" from "inventory-path-select"
00:00:01.128
And
I click on "Schedule"
00:00:00.073
Then
I should see a "Playbook execution has been scheduled" text
00:00:00.365
And
I wait until event "Execute playbook 'playbook_orion_dummy.yml' scheduled" is completed
00:00:38.871
And
file "/tmp/file.txt" should exist on "sle_minion"
00:00:00.781
@skip_if_github_validation
@scope_ansible
@sle_minion
@bug_reported
Scenario: Run the basic tests playbook
Given
I am on the Systems overview page of this "sle_minion"
00:00:01.528
When
I follow "Ansible" in the content area
00:00:00.081
And
I follow "Playbooks" in the content area
00:00:00.066
And
I wait until I see "/srv/playbooks" text
00:00:00.244
And
I click on "/srv/playbooks"
00:00:00.058
And
I wait until I see "/srv/playbooks/basic_tests.yml" text
00:00:05.011
And
I click on "basic_tests.yml"
00:00:00.060
And
I wait until I see "Playbook Content" text
00:00:00.979
And
I click on "Schedule"
00:00:00.084
And
I wait until I see "Playbook execution has been scheduled" text
00:00:00.294
And
I wait for "2" seconds
00:00:02.000
And
I follow "scheduled" in the content area
00:00:00.072
Then
I wait until I see "1 system successfully completed this action" text or "1 system failed to complete this action" text, refreshing the page
00:00:33.453
When
I follow "1 system"
00:00:00.354
And
I wait until I see the system name of "sle_minion"
00:00:00.065
And
I follow this "sle_minion" link
00:00:00.577
Then
I should see a "42" text
00:00:00.073
And
I should see a "101010" text
00:00:00.066
And
I should see a "(code 0)" text
00:00:00.067
@skip_if_github_validation
@scope_ansible
@sle_minion
@bug_reported
Scenario: Run the basic tests playbook while editing variables and changing their values
Given
I am on the Systems overview page of this "sle_minion"
00:00:01.519
When
I follow "Ansible" in the content area
00:00:00.080
And
I follow "Playbooks" in the content area
00:00:00.066
And
I wait until I see "/srv/playbooks" text
00:00:00.156
And
I click on "/srv/playbooks"
00:00:00.058
And
I wait until I see "/srv/playbooks/basic_tests.yml" text
00:00:04.963
And
I click on "basic_tests.yml"
00:00:00.061
And
I wait until I see "Playbook Content" text
00:00:00.982
And
I click on "Edit variables"
00:00:00.090
And
I enter data from table with value as field name
00:00:00.859
And
I click on "Save"
00:00:00.096
And
I click on "Schedule"
00:00:00.060
And
I wait until I see "Playbook execution has been scheduled" text
00:00:00.479
And
I wait for "2" seconds
00:00:02.000
And
I follow "scheduled" in the content area
00:00:00.075
Then
I wait until I see "1 system successfully completed this action" text or "1 system failed to complete this action" text, refreshing the page
00:00:33.503
When
I follow "1 system"
00:00:00.294
And
I wait until I see the system name of "sle_minion"
00:00:00.069
And
I follow this "sle_minion" link
00:00:00.375
Then
I should see a "4200" text
00:00:00.074
And
I should see a "(code 0)" text
00:00:00.072
@skip_if_github_validation
@scope_ansible
@sle_minion
@bug_reported
Scenario: Run the basic tests playbook while editing the EMPTY variables and changing their values
Given
I am on the Systems overview page of this "sle_minion"
00:00:01.493
When
I follow "Ansible" in the content area
00:00:00.095
And
I follow "Playbooks" in the content area
00:00:00.066
And
I wait until I see "/srv/playbooks" text
00:00:00.250
And
I click on "/srv/playbooks"
00:00:00.059
And
I wait until I see "/srv/playbooks/basic_tests.yml" text
00:00:05.009
And
I click on "basic_tests.yml"
00:00:00.062
And
I wait until I see "Playbook Content" text
00:00:01.103
And
I click on "Edit variables"
00:00:00.087
And
I enter data from table with value as field name
00:00:01.062
And
I click on "Save"
00:00:00.098
And
I click on "Schedule"
00:00:00.074
And
I wait until I see "Playbook execution has been scheduled" text
00:00:00.491
And
I wait for "2" seconds
00:00:02.000
And
I follow "scheduled" in the content area
00:00:00.071
Then
I wait until I see "1 system successfully completed this action" text or "1 system failed to complete this action" text, refreshing the page
00:00:33.576
When
I follow "1 system"
00:00:00.294
And
I wait until I see the system name of "sle_minion"
00:00:00.066
And
I follow this "sle_minion" link
00:00:00.370
Then
I should see a "42000" text
00:00:00.075
And
I should see a "4242" text
00:00:00.067
And
I should see a "(code 0)" text
00:00:00.070
@skip_if_github_validation
@scope_ansible
@sle_minion
@bug_reported
@skip_if_github_validation
Scenario: Run the basic tests playbook while editing the NULL variable and changing its value
Given
I am on the Systems overview page of this "sle_minion"
00:00:01.541
When
I follow "Ansible" in the content area
00:00:00.080
And
I follow "Playbooks" in the content area
00:00:00.066
And
I wait until I see "/srv/playbooks" text
00:00:00.250
And
I click on "/srv/playbooks"
00:00:00.057
And
I wait until I see "/srv/playbooks/basic_tests.yml" text
00:00:05.163
And
I click on "basic_tests.yml"
00:00:00.060
And
I wait until I see "Playbook Content" text
00:00:00.970
And
I click on "Edit variables"
00:00:00.118
And
I enter data from table with value as field name
00:00:01.010
And
I click on "Save"
00:00:00.098
And
I click on "Schedule"
00:00:00.069
And
I wait until I see "Playbook execution has been scheduled" text
00:00:00.305
And
I wait for "2" seconds
00:00:02.000
And
I follow "scheduled" in the content area
00:00:00.069
Then
I wait until I see "1 system successfully completed this action" text or "1 system failed to complete this action" text, refreshing the page
00:00:33.496
When
I follow "1 system"
00:00:00.287
And
I wait until I see the system name of "sle_minion"
00:00:00.069
And
I follow this "sle_minion" link
00:00:00.376
Then
I should see a "65536" text
00:00:00.071
And
I should see a "(code 0)" text
00:00:00.067
@skip_if_github_validation
@scope_ansible
@sle_minion
@bug_reported
@skip_if_github_validation
Scenario: Run the basic tests playbook on SAVE operation of YAML editor with pre-crafted strings
Given
I am on the Systems overview page of this "sle_minion"
00:00:01.566
When
I follow "Ansible" in the content area
00:00:00.091
And
I follow "Playbooks" in the content area
00:00:00.068
And
I wait until I see "/srv/playbooks" text
00:00:00.249
And
I click on "/srv/playbooks"
00:00:00.057
And
I wait until I see "/srv/playbooks/basic_tests.yml" text
00:00:05.158
And
I click on "basic_tests.yml"
00:00:00.061
And
I wait until I see "Playbook Content" text
00:00:01.016
And
I click on "Edit variables"
00:00:00.086
And
I click on "Edit YAML"
00:00:00.067
And
I click on "Save"
00:00:00.094
And
I click on "Schedule"
00:00:00.071
And
I wait until I see "Playbook execution has been scheduled" text
00:00:00.304
And
I wait for "2" seconds
00:00:02.000
And
I follow "scheduled" in the content area
00:00:00.076
Then
I wait until I see "1 system successfully completed this action" text or "1 system failed to complete this action" text, refreshing the page
00:00:33.478
When
I follow "1 system"
00:00:00.294
And
I wait until I see the system name of "sle_minion"
00:00:00.067
And
I follow this "sle_minion" link
00:00:00.510
Then
I should see a "42" text
00:00:00.071
And
I should see a "101010" text
00:00:00.068
And
I should see a "(code 0)" text
00:00:00.066
@skip_if_github_validation
@scope_ansible
@sle_minion
@bug_reported
Scenario: Run the basic tests playbook on SAVE operation of YAML editor with safe values
Given
I am on the Systems overview page of this "sle_minion"
00:00:02.682
When
I follow "Ansible" in the content area
00:00:00.077
And
I follow "Playbooks" in the content area
00:00:00.064
And
I wait until I see "/srv/playbooks" text
00:00:00.244
And
I click on "/srv/playbooks"
00:00:00.056
And
I wait until I see "/srv/playbooks/basic_tests.yml" text
00:00:05.052
And
I click on "basic_tests.yml"
00:00:00.060
And
I wait until I see "Playbook Content" text
00:00:00.963
And
I click on "Edit variables"
00:00:00.087
And
I enter data from table with value as field name
00:00:00.890
And
I click on "Edit YAML"
00:00:00.069
And
I click on "Save"
00:00:00.104
And
I click on "Schedule"
00:00:00.071
And
I wait until I see "Playbook execution has been scheduled" text
00:00:00.302
And
I wait for "2" seconds
00:00:02.000
And
I follow "scheduled" in the content area
00:00:00.072
Then
I wait until I see "1 system successfully completed this action" text or "1 system failed to complete this action" text, refreshing the page
00:00:33.495
When
I follow "1 system"
00:00:00.294
And
I wait until I see the system name of "sle_minion"
00:00:00.069
And
I follow this "sle_minion" link
00:00:00.448
Then
I should see a "abc" text
00:00:00.074
And
I should see a "def" text
00:00:00.069
And
I should see a "ghi" text
00:00:00.067
And
I should see a "jkl" text
00:00:00.067
And
I should see a "4096" text
00:00:00.067
And
I should see a "(code 0)" text
00:00:00.066
@skip_if_github_validation
@scope_ansible
@sle_minion
@bug_reported
Scenario: Cleanup: Disable Ansible and remove test playbooks and inventory file
Given
I am on the Systems overview page of this "sle_minion"
00:00:01.555
When
I follow "Properties" in the content area
00:00:00.079
And
I uncheck "ansible_control_node"
00:00:10.084
And
I click on "Update Properties"
00:00:01.748
Then
I should see a "System properties changed" text
00:00:00.089
And
I remove package "orion-dummy" from this "sle_minion" without error control
00:00:02.315
And
I remove "/tmp/file.txt" from "sle_minion"
00:00:00.442
@skip_if_github_validation
@scope_ansible
@sle_minion
@bug_reported
@susemanager
Scenario: Cleanup: Unsubscribe SUSE minions from SLE-Module-Python3-15-SP7-Pool for x86_64
Given
I am on the Systems overview page of this "sle_minion"
0s
When
I follow "Software" in the content area
0s
And
I follow "Software Channels" in the content area
0s
And
I uncheck "SLE-Module-Python3-15-SP7-Pool for x86_64" by label
0s
And
I click on "Next"
0s
And
I click on "Confirm"
0s
And
I wait until I see "Changing the channels has been scheduled." text
0s
And
I follow "scheduled"
0s
And
I wait until I see "1 system successfully completed this action" text, refreshing the page
0s
@skip_if_github_validation
@scope_ansible
@sle_minion
@bug_reported
Scenario: Cleanup: Apply highstate to disable the minion as an "Ansible control node"
Given
I am on the Systems overview page of this "sle_minion"
00:00:01.722
When
I follow "States" in the content area
00:00:00.076
And
I click on "Apply Highstate"
00:00:00.061
And
I wait until event "Apply highstate scheduled" is completed
00:00:39.256