@scope_ansible @sle_minion @bug_reported @susemanager @skip_if_github_validation

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

Scenarios

Chart

Status

Progress

Passed	36.84 %
Failed	52.63 %
Skipped	10.53 %

Total duration:

00:39:28.712

@scope_ansible @sle_minion @bug_reported

Scenario: Log in as org admin user

@scope_ansible @sle_minion @bug_reported

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

@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

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

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

And I check "ansible_control_node" 00:00:00.080

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

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

@scope_ansible @sle_minion @bug_reported

Scenario: Apply highstate and check that Ansible is installed

1
1
3
Duration: 00:00:45.181

Given I am on the Systems overview page of this "sle_minion" 00:00:01.651

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

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

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

+ 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/min_ansible_control_node.feature:39:in `I wait until event "Apply highstate scheduled" is completed'

Event Details:
Failed to apply state(s): highstate
----------
          ID: sync_states
    Function: saltutil.sync_states
        Name: sync_states
      Result: true
     Comment: No updates to sync
     Started: 01:10:26.912751
    Duration: 251.257
         SLS: util.syncstates
     Changed: {}
----------
          ID: mgr_absent_ca_package
    Function: pkg.removed
        Name: rhn-org-trusted-ssl-cert
      Result: true
     Comment: All specified packages are already absent
     Started: 01:10:28.555420
    Duration: 12.459
         SLS: certs
     Changed: {}
----------
          ID: mgr_ca_cert
    Function: file.managed
        Name: /etc/pki/trust/anchors/RHN-ORG-TRUSTED-SSL-CERT
      Result: true
     Comment: File /etc/pki/trust/anchors/RHN-ORG-TRUSTED-SSL-CERT is in the correct state
     Started: 01:10:28.570692
    Duration: 43.861
         SLS: certs
     Changed: {}
----------
          ID: update-ca-certificates
    Function: cmd.run
        Name: /usr/sbin/update-ca-certificates
      Result: true
     Comment: State was not run because none of the onchanges reqs changed
     Started: 01:10:28.616739
    Duration: 0.008
         SLS: certs
     Changed: {}
----------
          ID: mgr_proxy_ca_cert_symlink
    Function: file.symlink
        Name: /usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT
      Result: true
     Comment: onlyif condition is false
     Started: 01:10:28.616868
    Duration: 831.324
         SLS: certs
     Changed: {}
----------
          ID: mgr_deploy_tools_uyuni_key
    Function: file.managed
        Name: /etc/pki/rpm-gpg/uyuni-tools-gpg-pubkey-0d20833e.key
      Result: true
     Comment: File /etc/pki/rpm-gpg/uyuni-tools-gpg-pubkey-0d20833e.key is in the correct state
     Started: 01:10:29.448394
    Duration: 39.973
         SLS: channels.gpg-keys
     Changed: {}
----------
          ID: mgr_deploy_suse_addon_key
    Function: file.managed
        Name: /etc/pki/rpm-gpg/suse-addon-97a636db0bad8ecc.key
      Result: true
     Comment: File /etc/pki/rpm-gpg/suse-addon-97a636db0bad8ecc.key is in the correct state
     Started: 01:10:29.488518
    Duration: 39.248
         SLS: channels.gpg-keys
     Changed: {}
----------
          ID: mgr_deploy_suse16_gpg_key
    Function: file.managed
        Name: /etc/pki/rpm-gpg/suse16-gpg-pubkey-09d9ea69.key
      Result: true
     Comment: File /etc/pki/rpm-gpg/suse16-gpg-pubkey-09d9ea69.key is in the correct state
     Started: 01:10:29.527917
    Duration: 44.022
         SLS: channels.gpg-keys
     Changed: {}
----------
          ID: file_///etc/pki/rpm-gpg/uyuni-tools-gpg-pubkey-0d20833e.key
    Function: module.run
        Name: pkg.add_repo_key
      Result: true
     Comment: Module function pkg.add_repo_key executed
     Started: 01:10:29.572200
    Duration: 39.397
         SLS: channels.gpg-keys
     Changed: ret: true
              
----------
          ID: file_///usr/lib/rpm/gnupg/keys/gpg-pubkey-29b700a4-62b07e22.asc
    Function: module.run
        Name: pkg.add_repo_key
      Result: true
     Comment: Module function pkg.add_repo_key executed
     Started: 01:10:29.611751
    Duration: 43.684
         SLS: channels.gpg-keys
     Changed: ret: true
              
----------
          ID: mgrchannels_repo
    Function: file.managed
        Name: /etc/zypp/repos.d/susemanager:channels.repo
      Result: true
     Comment: File /etc/zypp/repos.d/susemanager:channels.repo is in the correct state
     Started: 01:10:29.655704
    Duration: 169.736
         SLS: channels
     Changed: {}
----------
          ID: pkg_installed
    Function: pkg.installed
        Name: pkg_installed
      Result: true
     Comment: No packages to install provided
     Started: 01:10:29.826078
    Duration: 0.952
         SLS: packages.packages_3564d85229afa12863f1175f6a148cdd
     Changed: {}
----------
          ID: pkg_removed
    Function: pkg.removed
        Name: pkg_removed
      Result: true
     Comment: All specified packages are already absent
     Started: 01:10:29.827241
    Duration: 13.991
         SLS: packages.packages_3564d85229afa12863f1175f6a148cdd
     Changed: {}
----------
          ID: pkg_latest
    Function: pkg.latest
        Name: pkg_latest
      Result: true
     Comment: No packages to install provided
     Started: 01:10:29.841518
    Duration: 0.817
         SLS: packages.packages_3564d85229afa12863f1175f6a148cdd
     Changed: {}
----------
          ID: disable_spacewalksd
    Function: service.dead
        Name: rhnsd
      Result: true
     Comment: The named service rhnsd is not available
     Started: 01:10:29.842444
    Duration: 19.258
         SLS: services.salt-minion
     Changed: {}
----------
          ID: disable_spacewalk-update-status
    Function: service.dead
        Name: spacewalk-update-status
      Result: true
     Comment: The named service spacewalk-update-status is not available
     Started: 01:10:29.861849
    Duration: 12.76
         SLS: services.salt-minion
     Changed: {}
----------
          ID: disable_osad
    Function: service.dead
        Name: osad
      Result: true
     Comment: The named service osad is not available
     Started: 01:10:29.874753
    Duration: 12.405
         SLS: services.salt-minion
     Changed: {}
----------
          ID: remove_traditional_stack_all
    Function: pkg.removed
        Name: remove_traditional_stack_all
      Result: true
     Comment: All specified packages are already absent
     Started: 01:10:29.887347
    Duration: 12.548
         SLS: services.salt-minion
     Changed: {}
----------
          ID: remove_traditional_stack
    Function: pkg.removed
        Name: remove_traditional_stack
      Result: true
     Comment: All specified packages are already absent
     Started: 01:10:29.900027
    Duration: 51.861
         SLS: services.salt-minion
     Changed: {}
----------
          ID: /etc/sysconfig/rhn/systemid
    Function: file.managed
        Name: /etc/sysconfig/rhn/systemid
      Result: true
     Comment: File /etc/sysconfig/rhn/systemid exists with proper permissions. No changes made.
     Started: 01:10:29.952023
    Duration: 1.567
         SLS: services.salt-minion
     Changed: {}
----------
          ID: mgr_ansible_installed
    Function: pkg.installed
        Name: mgr_ansible_installed
      Result: false
     Comment: An error was encountered while installing package(s): Zypper command failure: Running as unit: run-p11483-i13886.scope; invocation ID: 0b5a2ad0645d46cda919611dc4086f8c
Package 'ansible' not found.Loading repository data...
Reading installed packages...
     Started: 01:10:29.953706
    Duration: 1997.569
         SLS: ansible
     Changed: {}
----------
          ID: mgr_salt_minion_inst
    Function: pkg.installed
        Name: venv-salt-minion
      Result: true
     Comment: All specified packages are already installed
     Started: 01:10:31.952007
    Duration: 13.853
         SLS: services.salt-minion
     Changed: {}
----------
          ID: /etc/venv-salt-minion/minion.d/susemanager.conf
    Function: file.managed
        Name: /etc/venv-salt-minion/minion.d/susemanager.conf
      Result: true
     Comment: File /etc/venv-salt-minion/minion.d/susemanager.conf is in the correct state
     Started: 01:10:31.966072
    Duration: 135.481
         SLS: services.salt-minion
     Changed: {}
----------
          ID: mgr_salt_minion_run
    Function: service.running
        Name: venv-salt-minion
      Result: true
     Comment: The service venv-salt-minion is already running
     Started: 01:10:32.101709
    Duration: 34.469
         SLS: services.salt-minion
     Changed: {}

Then "ansible" should be installed on "sle_minion" 0s

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

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

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

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

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

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

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

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

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

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

@scope_ansible @sle_minion @bug_reported @bug_reported

Scenario: Display inventories

1
5
Duration: 00:04:12.229

Given I am on the Systems overview page of this "sle_minion" 00:00:01.706

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

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

And I click on the inventory accordion for "/srv/playbooks/orion_dummy/hosts" 00:00:00.048

Then I wait until I see "myself" text 00:04:10.118

+ Show Error + Screenshot

Text 'myself' not found (ScriptError)
./features/step_definitions/navigation_steps.rb:40:in `/^I wait until I see "([^"]*)" text$/'
features/secondary/min_ansible_control_node.feature:63:in `I wait until I see "myself" text'

@scope_ansible @sle_minion @bug_reported

Scenario: Discover playbooks and display them

1
1
5
Duration: 00:04:12.686

Given I am on the Systems overview page of this "sle_minion" 00:00:02.161

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

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

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

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

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

+ Show Error + Screenshot

Text '/srv/playbooks/orion_dummy/playbook_orion_dummy.yml' not found (ScriptError)
./features/step_definitions/navigation_steps.rb:40:in `/^I wait until I see "([^"]*)" text$/'
features/secondary/min_ansible_control_node.feature:71:in `I wait until I see "/srv/playbooks/orion_dummy/playbook_orion_dummy.yml" text'

And I wait until I see "/srv/playbooks/basic_tests.yml" text 0s

@scope_ansible @sle_minion @bug_reported

Scenario: Run a playbook using custom inventory

7
1
5
Duration: 00:04:12.097

Given I am on the Systems overview page of this "sle_minion" 00:00:01.609

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

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

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

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

And I wait until I see "/srv/playbooks/orion_dummy/playbook_orion_dummy.yml" text 00:04:10.153

+ Show Error + Screenshot

Text '/srv/playbooks/orion_dummy/playbook_orion_dummy.yml' not found (ScriptError)
./features/step_definitions/navigation_steps.rb:40:in `/^I wait until I see "([^"]*)" text$/'
features/secondary/min_ansible_control_node.feature:80:in `I wait until I see "/srv/playbooks/orion_dummy/playbook_orion_dummy.yml" text'

And I click on "orion_dummy/playbook_orion_dummy.yml" 0s

And I wait until I see "Playbook Content" text 0s

And I select "/srv/playbooks/orion_dummy/hosts" from "inventory-path-select" 0s

And I click on "Schedule" 0s

Then I should see a "Playbook execution has been scheduled" text 0s

And I wait until event "Execute playbook 'playbook_orion_dummy.yml' scheduled" is completed 0s

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

@scope_ansible @sle_minion @bug_reported

Scenario: Run the basic tests playbook

13
1
5
Duration: 00:04:12.110

Given I am on the Systems overview page of this "sle_minion" 00:00:01.578

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

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

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

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

And I wait until I see "/srv/playbooks/basic_tests.yml" text 00:04:10.102

+ Show Error + Screenshot

Text '/srv/playbooks/basic_tests.yml' not found (ScriptError)
./features/step_definitions/navigation_steps.rb:40:in `/^I wait until I see "([^"]*)" text$/'
features/secondary/min_ansible_control_node.feature:95:in `I wait until I see "/srv/playbooks/basic_tests.yml" text'

And I click on "basic_tests.yml" 0s

And I wait until I see "Playbook Content" text 0s

And I click on "Schedule" 0s

And I wait until I see "Playbook execution has been scheduled" text 0s

And I wait for "2" seconds 0s

And I follow "scheduled" in the content area 0s

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 0s

When I follow "1 system" 0s

And I wait until I see the system name of "sle_minion" 0s

And I follow this "sle_minion" link 0s

Then I should see a "42" text 0s

And I should see a "101010" text 0s

And I should see a "(code 0)" text 0s

@scope_ansible @sle_minion @bug_reported

Scenario: Run the basic tests playbook while editing variables and changing their values

15
1
5
Duration: 00:04:12.132

Given I am on the Systems overview page of this "sle_minion" 00:00:01.544

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

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

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

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

And I wait until I see "/srv/playbooks/basic_tests.yml" text 00:04:10.138

+ Show Error + Screenshot

Text '/srv/playbooks/basic_tests.yml' not found (ScriptError)
./features/step_definitions/navigation_steps.rb:40:in `/^I wait until I see "([^"]*)" text$/'
features/secondary/min_ansible_control_node.feature:116:in `I wait until I see "/srv/playbooks/basic_tests.yml" text'

And I click on "basic_tests.yml" 0s

And I wait until I see "Playbook Content" text 0s

And I click on "Edit variables" 0s

And I enter data from table with value as field name 0s

And I click on "Save" 0s

And I click on "Schedule" 0s

And I wait until I see "Playbook execution has been scheduled" text 0s

And I wait for "2" seconds 0s

And I follow "scheduled" in the content area 0s

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 0s

When I follow "1 system" 0s

And I wait until I see the system name of "sle_minion" 0s

And I follow this "sle_minion" link 0s

Then I should see a "4200" text 0s

And I should see a "(code 0)" text 0s

@scope_ansible @sle_minion @bug_reported

Scenario: Run the basic tests playbook while editing the EMPTY variables and changing their values

16
1
5
Duration: 00:04:12.164

@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

15
1
5
Duration: 00:04:12.330

Given I am on the Systems overview page of this "sle_minion" 00:00:01.716

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

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

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

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

And I wait until I see "/srv/playbooks/basic_tests.yml" text 00:04:10.103

+ Show Error + Screenshot

Text '/srv/playbooks/basic_tests.yml' not found (ScriptError)
./features/step_definitions/navigation_steps.rb:40:in `/^I wait until I see "([^"]*)" text$/'
features/secondary/min_ansible_control_node.feature:176:in `I wait until I see "/srv/playbooks/basic_tests.yml" text'

And I click on "basic_tests.yml" 0s

And I wait until I see "Playbook Content" text 0s

And I click on "Edit variables" 0s

And I enter data from table with value as field name 0s

And I click on "Save" 0s

And I click on "Schedule" 0s

And I wait until I see "Playbook execution has been scheduled" text 0s

And I wait for "2" seconds 0s

And I follow "scheduled" in the content area 0s

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 0s

When I follow "1 system" 0s

And I wait until I see the system name of "sle_minion" 0s

And I follow this "sle_minion" link 0s

Then I should see a "65536" text 0s

And I should see a "(code 0)" text 0s

@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

16
1
5
Duration: 00:04:12.142

@scope_ansible @sle_minion @bug_reported

Scenario: Run the basic tests playbook on SAVE operation of YAML editor with safe values

20
1
5
Duration: 00:04:12.175

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

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

And I uncheck "ansible_control_node" 00:00:10.069

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

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

And I remove package "orion-dummy" from this "sle_minion" without error control 00:00:01.427

And I remove "/tmp/file.txt" from "sle_minion" 00:00:00.442

@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

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

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

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

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