@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.755
When
I store the current last event id for "sle_minion"
00:00:02.360
And
I follow "Properties" in the content area
00:00:00.077
And
I check "ansible_control_node"
00:00:00.095
And
I click on "Update Properties"
00:00:01.717
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.994
When
I wait until a new "Refresh Ansible inventories scheduled by (system)" event is completed for "sle_minion"
00:04:10.000
+ Show Error
+ Screenshot
execution expired (Timeout::Error) ./features/support/commonlib.rb:89:in `repeat_until_timeout' ./features/step_definitions/command_steps.rb:1876: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.846
When
I follow "States" in the content area
00:00:00.080
And
I click on "Apply Highstate"
00:00:00.064
And
I wait until event "Apply highstate scheduled" is completed
00:00:42.425
+ 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:45: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: 12:33:10.425912
Duration: 355.509
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: 12:33:10.805754
Duration: 15.792
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: 12:33:10.824851
Duration: 53.568
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: 12:33:10.880084
Duration: 0.01
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: 12:33:10.880244
Duration: 685.154
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: 12:33:11.565715
Duration: 38.779
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: 12:33:11.604673
Duration: 40.734
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: 12:33:11.645663
Duration: 37.218
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: 12:33:11.683081
Duration: 36.959
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: 12:33:11.720208
Duration: 38.058
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: 12:33:11.758521
Duration: 145.624
SLS: channels
Changed: {}
----------
ID: pkg_installed
Function: pkg.installed
Name: pkg_installed
Result: true
Comment: No packages to install provided
Started: 12:33:11.904777
Duration: 0.794
SLS: packages.packages_6c405618ad98417510f05ada6a45f6ae
Changed: {}
----------
ID: pkg_removed
Function: pkg.removed
Name: pkg_removed
Result: true
Comment: All specified packages are already absent
Started: 12:33:11.905756
Duration: 10.512
SLS: packages.packages_6c405618ad98417510f05ada6a45f6ae
Changed: {}
----------
ID: pkg_latest
Function: pkg.latest
Name: pkg_latest
Result: true
Comment: No packages to install provided
Started: 12:33:11.916512
Duration: 0.71
SLS: packages.packages_6c405618ad98417510f05ada6a45f6ae
Changed: {}
----------
ID: disable_spacewalksd
Function: service.dead
Name: rhnsd
Result: true
Comment: The named service rhnsd is not available
Started: 12:33:11.917316
Duration: 17.314
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: 12:33:11.934778
Duration: 11.894
SLS: services.salt-minion
Changed: {}
----------
ID: disable_osad
Function: service.dead
Name: osad
Result: true
Comment: The named service osad is not available
Started: 12:33:11.946835
Duration: 11.425
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: 12:33:11.958398
Duration: 11.063
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: 12:33:11.969592
Duration: 46.201
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: 12:33:12.015923
Duration: 1.596
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-p11444-i13797.scope; invocation ID: 77e6873a6b714c7c99f9c9f9aabcef2b
ansible-core-2.21.1-1.1.noarch (openSUSE Tumbleweed (x86_64)): Signature verification failed [5-File does not exist or signature can't be checked]
Problem occurred during or after installation or removal of packages:
Installation has been aborted as directed.
Please see the above error message for a hint.Loading repository data...
Reading installed packages...
Resolving package dependencies...
The following 6 NEW packages are going to be installed:
ansible ansible-core librpmbuild10 python313-packaging python313-resolvelib python313-rpm
6 new packages to install.
Package download size: 50.2 MiB
Package install size change:
| 347.5 MiB required by packages that will be installed
347.5 MiB | - 0 B released by packages that will be removed
Backend: classic_rpmtrans
Continue? [y/n/v/...? shows all options] (y): y
Preloading Packages [..
Preloading: python313-rpm-4.20.1-7.1.x86_64.rpm [done]
.
Preloading: python313-packaging-26.2-1.1.noarch.rpm [done]
.
Preloading: python313-resolvelib-1.2.1-1.3.noarch.rpm [done]
.
Preloading: librpmbuild10-4.20.1-7.1.x86_64.rpm [done]
.
Preloading: ansible-core-2.21.1-1.1.noarch.rpm [done]
..
Preloading: ansible-14.1.0-1.1.noarch.rpm [done]
.done]
Retrieving: python313-resolvelib-1.2.1-1.3.noarch (openSUSE Tumbleweed (x86_64)) (1/6), 52.6 KiB
Retrieving: python313-packaging-26.2-1.1.noarch (openSUSE Tumbleweed (x86_64)) (2/6), 99.7 KiB
Retrieving: librpmbuild10-4.20.1-7.1.x86_64 (openSUSE Tumbleweed (x86_64)) (3/6), 103.0 KiB
Retrieving: python313-rpm-4.20.1-7.1.x86_64 (openSUSE Tumbleweed (x86_64)) (4/6), 58.1 KiB
Retrieving: ansible-core-2.21.1-1.1.noarch (openSUSE Tumbleweed (x86_64)) (5/6), 3.1 MiB
ansible-core-2.21.1-1.1.noarch.rpm:
Header V3 RSA/SHA512 Signature, key ID 35a2f86e29b700a4: NOTTRUSTED
V3 RSA/SHA512 Signature, key ID 35a2f86e29b700a4: NOTTRUSTED
Abort, retry, ignore? [a/r/i] (a): a
Started: 12:33:12.017612
Duration: 5891.903
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: 12:33:17.910139
Duration: 13.76
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: 12:33:17.924152
Duration: 121.189
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: 12:33:18.045594
Duration: 49.494
SLS: services.salt-minion
Changed: {}
Then
"ansible" should be installed on "sle_minion"
0s
@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.715
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.066
@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.814
When
I follow "Ansible" in the content area
00:00:00.064
Then
I should see a "Ansible Control Node Configuration" text
00:00:00.059
And
I enter "/srv/playbooks/" as "new_playbook_path_input"
00:00:00.143
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.104
And
I click on "new_inventory_path_save"
00:00:00.061
@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.863
When
I follow "Ansible" in the content area
00:00:00.062
And
I follow "Inventories" in the content area
00:00:00.065
And
I wait until I see "/srv/playbooks/orion_dummy/hosts" text
00:00:00.237
And
I click on the inventory accordion for "/srv/playbooks/orion_dummy/hosts"
00:00:00.049
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:69:in `I wait until I see "myself" text'
@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.767
When
I follow "Ansible" in the content area
00:00:00.082
And
I follow "Playbooks" in the content area
00:00:00.083
And
I wait until I see "/srv/playbooks" text
00:00:00.431
And
I click on "/srv/playbooks"
00:00:00.058
Then
I wait until I see "/srv/playbooks/orion_dummy/playbook_orion_dummy.yml" text
00:04:10.898
+ 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:77: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
@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.803
When
I follow "Ansible" in the content area
00:00:00.080
And
I follow "Playbooks" in the content area
00:00:00.068
And
I wait until I see "/srv/playbooks" text
00:00:00.248
And
I click on "/srv/playbooks"
00:00:00.060
And
I wait until I see "/srv/playbooks/orion_dummy/playbook_orion_dummy.yml" text
00:04:10.648
+ 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:86: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
@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.743
When
I follow "Ansible" in the content area
00:00:00.080
And
I follow "Playbooks" in the content area
00:00:00.070
And
I wait until I see "/srv/playbooks" text
00:00:00.249
And
I click on "/srv/playbooks"
00:00:00.057
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:101: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
@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.716
When
I follow "Ansible" in the content area
00:00:00.078
And
I follow "Playbooks" in the content area
00:00:00.064
And
I wait until I see "/srv/playbooks" text
00:00:00.246
And
I click on "/srv/playbooks"
00:00:00.058
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:122: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
@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.820
When
I follow "Ansible" in the content area
00:00:00.078
And
I follow "Playbooks" in the content area
00:00:00.067
And
I wait until I see "/srv/playbooks" text
00:00:00.247
And
I click on "/srv/playbooks"
00:00:00.059
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:150: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 "42000" text
0s
And
I should see a "4242" text
0s
And
I should see a "(code 0)" text
0s
@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.844
When
I follow "Ansible" in the content area
00:00:00.082
And
I follow "Playbooks" in the content area
00:00:00.065
And
I wait until I see "/srv/playbooks" text
00:00:00.248
And
I click on "/srv/playbooks"
00:00:00.058
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:182: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
@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.794
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.245
And
I click on "/srv/playbooks"
00:00:00.063
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:214: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 click on "Edit YAML"
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 "42" text
0s
And
I should see a "101010" text
0s
And
I should see a "(code 0)" text
0s
@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.909
When
I follow "Ansible" in the content area
00:00:00.081
And
I follow "Playbooks" in the content area
00:00:00.072
And
I wait until I see "/srv/playbooks" text
00:00:00.252
And
I click on "/srv/playbooks"
00:00:00.059
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:238: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 "Edit YAML"
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 "abc" text
0s
And
I should see a "def" text
0s
And
I should see a "ghi" text
0s
And
I should see a "jkl" text
0s
And
I should see a "4096" text
0s
And
I should see a "(code 0)" text
0s
@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.767
When
I follow "Properties" in the content area
00:00:00.079
And
I uncheck "ansible_control_node"
00:00:10.069
And
I click on "Update Properties"
00:00:01.293
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:01.732
And
I remove "/tmp/file.txt" from "sle_minion"
00:00:00.446
@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.718
When
I follow "States" in the content area
00:00:00.071
And
I click on "Apply Highstate"
00:00:00.070
And
I wait until event "Apply highstate scheduled" is completed
00:00:38.817