@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.756
When
I store the current last event id for "sle_minion"
00:00:02.331
And
I follow "Properties" in the content area
00:00:00.084
And
I check "ansible_control_node"
00:00:00.081
And
I click on "Update Properties"
00:00:01.782
Then
I wait until I see "Ansible Control Node type has been applied." text
00:00:00.095
@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:02.838
When
I wait until a new "Refresh Ansible inventories scheduled by (system)" event is completed for "sle_minion"
00:00:04.693
+ Show Error
+ Screenshot
Action 283 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.713
When
I follow "States" in the content area
00:00:00.072
And
I click on "Apply Highstate"
00:00:00.065
And
I wait until event "Apply highstate scheduled" is completed
00:00:55.703
Then
"ansible" should be installed on "sle_minion"
00:00:00.801
@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.661
When
I follow "Ansible" in the content area
00:00:00.088
Then
I should see a "Ansible Control Node Configuration" text
00:00:00.063
@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:02.073
When
I follow "Ansible" in the content area
00:00:00.062
Then
I should see a "Ansible Control Node Configuration" text
00:00:00.065
And
I enter "/srv/playbooks/" as "new_playbook_path_input"
00:00:00.139
And
I click on "new_playbook_path_save"
00:00:00.060
And
I enter "/srv/playbooks/orion_dummy/hosts" as "new_inventory_path_input"
00:00:00.098
And
I click on "new_inventory_path_save"
00:00:00.064
@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:02.235
When
I follow "Ansible" in the content area
00:00:00.068
And
I follow "Inventories" in the content area
00:00:00.067
And
I wait until I see "/srv/playbooks/orion_dummy/hosts" text
00:00:00.259
And
I click on the inventory accordion for "/srv/playbooks/orion_dummy/hosts"
00:00:00.050
Then
I wait until I see "myself" text
00:00:06.705
@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.762
When
I follow "Ansible" in the content area
00:00:00.065
And
I follow "Playbooks" in the content area
00:00:00.064
And
I wait until I see "/srv/playbooks" text
00:00:00.254
And
I click on "/srv/playbooks"
00:00:00.077
Then
I wait until I see "/srv/playbooks/orion_dummy/playbook_orion_dummy.yml" text
00:00:04.676
And
I wait until I see "/srv/playbooks/basic_tests.yml" text
00:00:00.065
@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.678
When
I follow "Ansible" in the content area
00:00:00.063
And
I follow "Playbooks" in the content area
00:00:00.059
And
I wait until I see "/srv/playbooks" text
00:00:00.244
And
I click on "/srv/playbooks"
00:00:00.054
And
I wait until I see "/srv/playbooks/orion_dummy/playbook_orion_dummy.yml" text
00:00:04.962
And
I click on "orion_dummy/playbook_orion_dummy.yml"
00:00:00.080
And
I wait until I see "Playbook Content" text
00:00:00.895
And
I select "/srv/playbooks/orion_dummy/hosts" from "inventory-path-select"
00:00:01.124
And
I click on "Schedule"
00:00:00.075
Then
I should see a "Playbook execution has been scheduled" text
00:00:00.376
And
I wait until event "Execute playbook 'playbook_orion_dummy.yml' scheduled" is completed
00:00:22.525
And
file "/tmp/file.txt" should exist on "sle_minion"
00:00:00.720
@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.661
When
I follow "Ansible" in the content area
00:00:00.083
And
I follow "Playbooks" in the content area
00:00:00.071
And
I wait until I see "/srv/playbooks" text
00:00:00.254
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.647
And
I click on "basic_tests.yml"
00:00:00.061
And
I wait until I see "Playbook Content" text
00:00:01.017
And
I click on "Schedule"
00:00:00.071
And
I wait until I see "Playbook execution has been scheduled" text
00:00:00.308
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.584
When
I follow "1 system"
00:00:00.304
And
I wait until I see the system name of "sle_minion"
00:00:00.071
And
I follow this "sle_minion" link
00:00:00.392
Then
I should see a "42" text
00:00:00.076
And
I should see a "101010" text
00:00:00.067
And
I should see a "(code 0)" text
00:00:00.068
@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.712
When
I follow "Ansible" in the content area
00:00:00.078
And
I follow "Playbooks" in the content area
00:00:00.065
And
I wait until I see "/srv/playbooks" text
00:00:00.249
And
I click on "/srv/playbooks"
00:00:00.059
And
I wait until I see "/srv/playbooks/basic_tests.yml" text
00:00:04.805
And
I click on "basic_tests.yml"
00:00:00.061
And
I wait until I see "Playbook Content" text
00:00:01.110
And
I click on "Edit variables"
00:00:00.093
And
I enter data from table with value as field name
00:00:00.868
And
I click on "Save"
00:00:00.099
And
I click on "Schedule"
00:00:00.071
And
I wait until I see "Playbook execution has been scheduled" text
00:00:00.298
And
I wait for "2" seconds
00:00:02.000
And
I follow "scheduled" in the content area
00:00:00.080
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.553
When
I follow "1 system"
00:00:00.295
And
I wait until I see the system name of "sle_minion"
00:00:00.074
And
I follow this "sle_minion" link
00:00:00.385
Then
I should see a "4200" text
00:00:00.079
And
I should see a "(code 0)" text
00:00:00.068
@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.762
When
I follow "Ansible" in the content area
00:00:00.081
And
I follow "Playbooks" in the content area
00:00:00.075
And
I wait until I see "/srv/playbooks" text
00:00:00.250
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.722
And
I click on "basic_tests.yml"
00:00:00.061
And
I wait until I see "Playbook Content" text
00:00:01.035
And
I click on "Edit variables"
00:00:00.087
And
I enter data from table with value as field name
00:00:01.099
And
I click on "Save"
00:00:00.099
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.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.547
When
I follow "1 system"
00:00:00.295
And
I wait until I see the system name of "sle_minion"
00:00:00.068
And
I follow this "sle_minion" link
00:00:00.379
Then
I should see a "42000" text
00:00:00.073
And
I should see a "4242" text
00:00:00.067
And
I should see a "(code 0)" text
00:00:00.077
@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.658
When
I follow "Ansible" in the content area
00:00:00.077
And
I follow "Playbooks" in the content area
00:00:00.070
And
I wait until I see "/srv/playbooks" text
00:00:00.259
And
I click on "/srv/playbooks"
00:00:00.060
And
I wait until I see "/srv/playbooks/basic_tests.yml" text
00:00:04.730
And
I click on "basic_tests.yml"
00:00:00.063
And
I wait until I see "Playbook Content" text
00:00:00.945
And
I click on "Edit variables"
00:00:00.086
And
I enter data from table with value as field name
00:00:01.051
And
I click on "Save"
00:00:00.101
And
I click on "Schedule"
00:00:00.069
And
I wait until I see "Playbook execution has been scheduled" text
00:00:00.468
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.562
When
I follow "1 system"
00:00:00.288
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.460
Then
I should see a "65536" text
00:00:00.079
And
I should see a "(code 0)" text
00:00:00.071
@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:02.575
When
I follow "Ansible" in the content area
00:00:00.079
And
I follow "Playbooks" in the content area
00:00:00.071
And
I wait until I see "/srv/playbooks" text
00:00:00.252
And
I click on "/srv/playbooks"
00:00:00.057
And
I wait until I see "/srv/playbooks/basic_tests.yml" text
00:00:04.697
And
I click on "basic_tests.yml"
00:00:00.061
And
I wait until I see "Playbook Content" text
00:00:00.916
And
I click on "Edit variables"
00:00:00.090
And
I click on "Edit YAML"
00:00:00.075
And
I click on "Save"
00:00:00.092
And
I click on "Schedule"
00:00:00.069
And
I wait until I see "Playbook execution has been scheduled" text
00:00:00.309
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.596
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.388
Then
I should see a "42" text
00:00:00.083
And
I should see a "101010" text
00:00:00.066
And
I should see a "(code 0)" text
00:00:00.065
@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:01.728
When
I follow "Ansible" in the content area
00:00:00.083
And
I follow "Playbooks" in the content area
00:00:00.069
And
I wait until I see "/srv/playbooks" text
00:00:00.162
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.728
And
I click on "basic_tests.yml"
00:00:00.062
And
I wait until I see "Playbook Content" text
00:00:00.965
And
I click on "Edit variables"
00:00:00.085
And
I enter data from table with value as field name
00:00:00.873
And
I click on "Edit YAML"
00:00:00.070
And
I click on "Save"
00:00:00.113
And
I click on "Schedule"
00:00:00.072
And
I wait until I see "Playbook execution has been scheduled" text
00:00:00.308
And
I wait for "2" seconds
00:00:02.000
And
I follow "scheduled" in the content area
00:00:00.074
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.536
When
I follow "1 system"
00:00:00.301
And
I wait until I see the system name of "sle_minion"
00:00:00.070
And
I follow this "sle_minion" link
00:00:00.384
Then
I should see a "abc" text
00:00:00.077
And
I should see a "def" text
00:00:00.075
And
I should see a "ghi" text
00:00:00.069
And
I should see a "jkl" text
00:00:00.068
And
I should see a "4096" text
00:00:00.069
And
I should see a "(code 0)" text
00:00:00.069
@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.685
When
I follow "Properties" in the content area
00:00:00.083
And
I uncheck "ansible_control_node"
00:00:10.076
And
I click on "Update Properties"
00:00:01.371
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.506
And
I remove "/tmp/file.txt" from "sle_minion"
00:00:00.433
@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.640
When
I follow "States" in the content area
00:00:00.079
And
I click on "Apply Highstate"
00:00:00.078
And
I wait until event "Apply highstate scheduled" is completed
00:00:39.259