@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.757
When
I store the current last event id for "sle_minion"
00:00:02.758
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.111
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.918
When
I wait until a new "Refresh Ansible inventories scheduled by (system)" event is completed for "sle_minion"
00:00:04.816
+ Show Error
+ Screenshot
Action 282 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.880
When
I follow "States" in the content area
00:00:00.071
And
I click on "Apply Highstate"
00:00:00.062
And
I wait until event "Apply highstate scheduled" is completed
00:01:12.871
Then
"ansible" should be installed on "sle_minion"
00:00:00.917
@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.975
When
I follow "Ansible" in the content area
00:00:00.081
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.846
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.062
And
I enter "/srv/playbooks/" as "new_playbook_path_input"
00:00:00.150
And
I click on "new_playbook_path_save"
00:00:00.061
And
I enter "/srv/playbooks/orion_dummy/hosts" as "new_inventory_path_input"
00:00:00.103
And
I click on "new_inventory_path_save"
00:00:00.060
@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.843
When
I follow "Ansible" in the content area
00:00:00.065
And
I follow "Inventories" in the content area
00:00:00.066
And
I wait until I see "/srv/playbooks/orion_dummy/hosts" text
00:00:00.247
And
I click on the inventory accordion for "/srv/playbooks/orion_dummy/hosts"
00:00:00.049
Then
I wait until I see "myself" text
00:00:07.482
@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.884
When
I follow "Ansible" in the content area
00:00:00.061
And
I follow "Playbooks" in the content area
00:00:00.067
And
I wait until I see "/srv/playbooks" text
00:00:00.246
And
I click on "/srv/playbooks"
00:00:00.053
Then
I wait until I see "/srv/playbooks/orion_dummy/playbook_orion_dummy.yml" text
00:00:05.690
And
I wait until I see "/srv/playbooks/basic_tests.yml" text
00:00:00.070
@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.712
When
I follow "Ansible" in the content area
00:00:00.065
And
I follow "Playbooks" in the content area
00:00:00.060
And
I wait until I see "/srv/playbooks" text
00:00:00.248
And
I click on "/srv/playbooks"
00:00:00.073
And
I wait until I see "/srv/playbooks/orion_dummy/playbook_orion_dummy.yml" text
00:00:05.372
And
I click on "orion_dummy/playbook_orion_dummy.yml"
00:00:00.062
And
I wait until I see "Playbook Content" text
00:00:01.084
And
I select "/srv/playbooks/orion_dummy/hosts" from "inventory-path-select"
00:00:01.127
And
I click on "Schedule"
00:00:00.071
Then
I should see a "Playbook execution has been scheduled" text
00:00:00.364
And
I wait until event "Execute playbook 'playbook_orion_dummy.yml' scheduled" is completed
00:00:39.045
And
file "/tmp/file.txt" should exist on "sle_minion"
00:00:00.875
@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.815
When
I follow "Ansible" in the content area
00:00:00.083
And
I follow "Playbooks" in the content area
00:00:00.067
And
I wait until I see "/srv/playbooks" text
00:00:00.256
And
I click on "/srv/playbooks"
00:00:00.060
And
I wait until I see "/srv/playbooks/basic_tests.yml" text
00:00:05.774
And
I click on "basic_tests.yml"
00:00:00.059
And
I wait until I see "Playbook Content" text
00:00:01.000
And
I click on "Schedule"
00:00:00.071
And
I wait until I see "Playbook execution has been scheduled" text
00:00:00.463
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.578
When
I follow "1 system"
00:00:00.290
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.475
Then
I should see a "42" text
00:00:00.068
And
I should see a "101010" text
00:00:00.078
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.824
When
I follow "Ansible" in the content area
00:00:00.076
And
I follow "Playbooks" in the content area
00:00:00.064
And
I wait until I see "/srv/playbooks" text
00:00:00.251
And
I click on "/srv/playbooks"
00:00:00.060
And
I wait until I see "/srv/playbooks/basic_tests.yml" text
00:00:05.337
And
I click on "basic_tests.yml"
00:00:00.061
And
I wait until I see "Playbook Content" text
00:00:01.023
And
I click on "Edit variables"
00:00:00.092
And
I enter data from table with value as field name
00:00:00.853
And
I click on "Save"
00:00:00.099
And
I click on "Schedule"
00:00:00.063
And
I wait until I see "Playbook execution has been scheduled" text
00:00:00.477
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.533
When
I follow "1 system"
00:00:00.300
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.373
Then
I should see a "4200" 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
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.749
When
I follow "Ansible" in the content area
00:00:00.078
And
I follow "Playbooks" in the content area
00:00:00.066
And
I wait until I see "/srv/playbooks" text
00:00:00.251
And
I click on "/srv/playbooks"
00:00:00.060
And
I wait until I see "/srv/playbooks/basic_tests.yml" text
00:00:05.486
And
I click on "basic_tests.yml"
00:00:00.063
And
I wait until I see "Playbook Content" text
00:00:01.006
And
I click on "Edit variables"
00:00:00.093
And
I enter data from table with value as field name
00:00:01.075
And
I click on "Save"
00:00:00.103
And
I click on "Schedule"
00:00:00.069
And
I wait until I see "Playbook execution has been scheduled" text
00:00:00.314
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.520
When
I follow "1 system"
00:00:00.289
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.388
Then
I should see a "42000" text
00:00:00.074
And
I should see a "4242" text
00:00:00.067
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 while editing the NULL variable and changing its value
Given
I am on the Systems overview page of this "sle_minion"
00:00:01.717
When
I follow "Ansible" in the content area
00:00:00.076
And
I follow "Playbooks" in the content area
00:00:00.065
And
I wait until I see "/srv/playbooks" text
00:00:00.245
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.247
And
I click on "basic_tests.yml"
00:00:00.062
And
I wait until I see "Playbook Content" text
00:00:01.029
And
I click on "Edit variables"
00:00:00.085
And
I enter data from table with value as field name
00:00:01.055
And
I click on "Save"
00:00:00.100
And
I click on "Schedule"
00:00:00.069
And
I wait until I see "Playbook execution has been scheduled" text
00:00:00.312
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.578
When
I follow "1 system"
00:00:00.297
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.377
Then
I should see a "65536" text
00:00:00.071
And
I should see a "(code 0)" text
00:00:00.076
@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.781
When
I follow "Ansible" in the content area
00:00:00.075
And
I follow "Playbooks" in the content area
00:00:00.067
And
I wait until I see "/srv/playbooks" text
00:00:00.248
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.431
And
I click on "basic_tests.yml"
00:00:00.063
And
I wait until I see "Playbook Content" text
00:00:01.030
And
I click on "Edit variables"
00:00:00.084
And
I click on "Edit YAML"
00:00:00.059
And
I click on "Save"
00:00:00.106
And
I click on "Schedule"
00:00:00.069
And
I wait until I see "Playbook execution has been scheduled" text
00:00:00.311
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.623
When
I follow "1 system"
00:00:00.291
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.457
Then
I should see a "42" text
00:00:00.071
And
I should see a "101010" text
00:00:00.065
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 on SAVE operation of YAML editor with safe values
Given
I am on the Systems overview page of this "sle_minion"
00:00:02.285
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.246
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.747
And
I click on "basic_tests.yml"
00:00:00.060
And
I wait until I see "Playbook Content" text
00:00:00.981
And
I click on "Edit variables"
00:00:00.097
And
I enter data from table with value as field name
00:00:00.909
And
I click on "Edit YAML"
00:00:00.069
And
I click on "Save"
00:00:00.105
And
I click on "Schedule"
00:00:00.070
And
I wait until I see "Playbook execution has been scheduled" text
00:00:00.303
And
I wait for "2" seconds
00:00:02.000
And
I follow "scheduled" in the content area
00:00:00.078
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.607
When
I follow "1 system"
00:00:00.290
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.382
Then
I should see a "abc" text
00:00:00.071
And
I should see a "def" text
00:00:00.066
And
I should see a "ghi" text
00:00:00.067
And
I should see a "jkl" text
00:00:00.069
And
I should see a "4096" text
00:00:00.070
And
I should see a "(code 0)" text
00:00:00.073
@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.732
When
I follow "Properties" in the content area
00:00:00.079
And
I uncheck "ansible_control_node"
00:00:10.090
And
I click on "Update Properties"
00:00:01.315
Then
I should see a "System properties changed" text
00:00:00.101
And
I remove package "orion-dummy" from this "sle_minion" without error control
00:00:02.967
And
I remove "/tmp/file.txt" from "sle_minion"
00:00:00.468
@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.680
When
I follow "States" in the content area
00:00:00.078
And
I click on "Apply Highstate"
00:00:00.062
And
I wait until event "Apply highstate scheduled" is completed
00:00:38.894