@scope_ansible @scope_salt_ssh @ssh_minion @bug_reported @susemanager

Feature: 0126 - Operate an Ansible control node in SSH minion

Description: * Related GitHub Card: https://github.com/SUSE/spacewalk/issues/30806

File name: minssh_ansible_control_node.feature

Relative path: secondary/minssh_ansible_control_node.feature

Scenarios

Chart

Status

Progress

Passed	71.43 %
Failed	14.29 %
Skipped	14.29 %

Total duration:

00:03:57.719

@scope_ansible @scope_salt_ssh @ssh_minion @bug_reported

Scenario: Log in as org admin user

@scope_ansible @scope_salt_ssh @ssh_minion @bug_reported

Scenario: Pre-requisite: Deploy test playbooks and inventory file

@scope_ansible @scope_salt_ssh @ssh_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 "ssh_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

@scope_ansible @scope_salt_ssh @ssh_minion @bug_reported

Scenario: Enable "Ansible control node" system type

Given I am on the Systems overview page of this "ssh_minion" 00:00:01.586

When I follow "Properties" in the content area 00:00:00.070

And I check "ansible_control_node" 00:00:00.080

And I click on "Update Properties" 00:00:01.791

Then I wait until I see "Ansible Control Node type has been applied." text 00:00:00.089

@scope_ansible @scope_salt_ssh @ssh_minion @bug_reported @bug_reported

Scenario: Apply highstate and check that Ansible is installed

1
4
Duration: 00:01:14.676

Given I am on the Systems overview page of this "ssh_minion" 00:00:02.284

When I follow "States" in the content area 00:00:00.068

And I click on "Apply Highstate" 00:00:00.057

And I wait until event "Apply highstate scheduled" is completed 00:01:11.787

Then "ansible" should be installed on "ssh_minion" 00:00:00.478

+ Show Error + Screenshot

FAIL: rpm -q ansible returned status code = 1.
Output:
package ansible is not installed
 (ScriptError)
./features/support/remote_node.rb:172:in `run_local'
./features/support/remote_node.rb:120:in `run'
./features/step_definitions/command_steps.rb:217:in `/^"([^"]*)" should be installed on "([^"]*)"$/'
features/secondary/minssh_ansible_control_node.feature:42:in `"ansible" should be installed on "ssh_minion"'

@scope_ansible @scope_salt_ssh @ssh_minion @bug_reported

Scenario: The Ansible tab appears in the system overview page

Given I am on the Systems overview page of this "ssh_minion" 00:00:01.545

When I follow "Ansible" in the content area 00:00:00.078

Then I should see a "Ansible Control Node Configuration" text 00:00:00.062

@scope_ansible @scope_salt_ssh @ssh_minion @bug_reported

Scenario: Configure some inventory and playbooks path

Given I am on the Systems overview page of this "ssh_minion" 00:00:01.553

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

And I enter "/srv/playbooks/" as "new_playbook_path_input" 00:00:00.141

And I click on "new_playbook_path_save" 00:00:00.057

And I enter "/srv/playbooks/orion_dummy/hosts" as "new_inventory_path_input" 00:00:00.102

And I click on "new_inventory_path_save" 00:00:00.060

@scope_ansible @scope_salt_ssh @ssh_minion @bug_reported

Scenario: Display inventories

Given I am on the Systems overview page of this "ssh_minion" 00:00:02.085

When I follow "Ansible" in the content area 00:00:00.062

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

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

@scope_ansible @scope_salt_ssh @ssh_minion @bug_reported

Scenario: Discover playbooks and display them

Given I am on the Systems overview page of this "ssh_minion" 00:00:01.540

When I follow "Ansible" in the content area 00:00:00.081

And I follow "Playbooks" in the content area 00:00:00.065

And I wait until I see "/srv/playbooks" text 00:00:00.244

And I click on "/srv/playbooks" 00:00:00.059

Then I wait until I see "/srv/playbooks/orion_dummy/playbook_orion_dummy.yml" text 00:00:06.594

@scope_ansible @scope_salt_ssh @ssh_minion @bug_reported

Scenario: Run a playbook using custom inventory

1
1
11
Duration: 00:00:57.934

Given I am on the Systems overview page of this "ssh_minion" 00:00:01.617

When I follow "Ansible" in the content area 00:00:00.064

And I follow "Playbooks" in the content area 00:00:00.059

And I wait until I see "/srv/playbooks" text 00:00:00.187

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

And I click on "orion_dummy/playbook_orion_dummy.yml" 00:00:00.059

And I wait until I see "Playbook Content" text 00:00:06.198

And I select "/srv/playbooks/orion_dummy/hosts" from "inventory-path-select" 00:00:01.128

And I click on "Schedule" 00:00:00.074

Then I should see a "Playbook execution has been scheduled" text 00:00:00.374

And I wait until event "Execute playbook 'playbook_orion_dummy.yml' scheduled" is completed 00:00:41.545

+ Show Error + Show Info + Screenshot

unknown error - Event failed (SystemCallError)
./features/step_definitions/navigation_steps.rb:107:in `block (2 levels) in (top (required))'
./features/support/commonlib.rb:100:in `block in repeat_until_timeout'
./features/support/commonlib.rb:89:in `repeat_until_timeout'
./features/step_definitions/navigation_steps.rb:99:in `/^I wait at most (\d+) seconds until the event is completed, refreshing the page$/'
./features/step_definitions/common_steps.rb:157:in `/^I wait (\d+) seconds until the event is picked up and (\d+) seconds until the event "([^"]*)" is completed$/'
./features/step_definitions/common_steps.rb:174:in `/^I wait at most (\d+) seconds until event "([^"]*)" is completed$/'
./features/step_definitions/common_steps.rb:151:in `/^I wait until event "([^"]*)" is completed$/'
features/secondary/minssh_ansible_control_node.feature:86:in `I wait until event "Execute playbook 'playbook_orion_dummy.yml' scheduled" is completed'

Event Details:
module_|-run_ansible_playbook_|-ansible.playbooks_|-run:
    name: ansible.playbooks
    changes:
        ret:
            pid: 20139.0
            retcode: 4.0
            stdout: ''
            stderr: |-
                [WARNING]: Error loading plugin 'community.general.zypper': No module named 'ansible_collections.community'
                [ERROR]: couldn't resolve module/action 'zypper'. This often indicates a misspelling, missing collection, or incorrect module path.
                Origin: /srv/playbooks/orion_dummy/playbook_orion_dummy.yml:5:5

                3
                4   tasks:
                5   - name: Install Orion dummy package
                      ^ column 5
    comment: Module function ansible.playbooks executed
    result: false
    __sls__: ansible.runplaybook
    __run_num__: 0.0
    start_time: '06:07:09.452287'
    duration: 2355.579
    __id__: run_ansible_playbook

And file "/tmp/file.txt" should exist on "ssh_minion" 0s

@scope_ansible @scope_salt_ssh @ssh_minion @bug_reported

Scenario: Cleanup: Disable Ansible and remove test playbooks and inventory file

Given I am on the Systems overview page of this "ssh_minion" 00:00:01.656

When I follow "Properties" in the content area 00:00:00.079

And I uncheck "ansible_control_node" 00:00:10.078

And I click on "Update Properties" 00:00:01.368

Then I should see a "System properties changed" text 00:00:00.087

And I remove package "orion-dummy" from this "ssh_minion" without error control 00:00:01.224

And I remove "/tmp/file.txt" from "ssh_minion" 00:00:00.466

@scope_ansible @scope_salt_ssh @ssh_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 "ssh_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

@scope_ansible @scope_salt_ssh @ssh_minion @bug_reported

Scenario: Cleanup: Disable "Ansible control node" system type

Given I am on the Systems overview page of this "ssh_minion" 00:00:01.553

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

And I uncheck "ansible_control_node" 00:00:10.041

And I click on "Update Properties" 00:00:00.983

@scope_ansible @scope_salt_ssh @ssh_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 "ssh_minion" 00:00:01.581

When I follow "States" in the content area 00:00:00.083

And I click on "Apply Highstate" 00:00:00.091

And I wait until event "Apply highstate scheduled" is completed 00:00:38.404