-
Feature Request
-
Resolution: Unresolved
-
Normal
-
None
-
2.4
-
False
-
-
False
1. What is the nature and description of the request?
> Add a precheck to Validate if the receptor peer name is DNS resolvable.
2. Why does the customer need this? (List the business requirements here)
As suggested in AAP-23054, opening an RFE.
The initial task to validate if receptor peer nodes are DNS resolvable fails with a failure to evaluate the conditional and then is ignored:
TASK [ansible.automation_platform_installer.receptor : Validate if receptor peer name is DNS resolvable] *** fatal: [automationnode.example.org]: FAILED! => {"msg": "The conditional check 'hostvars[item]['node_state'] == 'active'' failed. The error was: error while evaluating conditional (hostvars[item]['node_state'] == 'active'): 'ansible.vars.hostvars.HostVarsVars object' has no attribute 'node_state'. 'ansible.vars.hostvars.HostVarsVars object' has no attribute 'node_state'\n\nThe error appears to be in '/root/ansible-automation-platform-setup-bundle-2.4-6.1-x86_64/collections/ansible_collections/ansible/automation_platform_installer/roles/receptor/tasks/assert_dns.yml': line 5, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n# and thefore breaking the mesh\n- name: Validate if receptor peer name is DNS resolvable\n ^ here\n"} ...ignoring
Then this task fails the install when the 'item' variable is undefined due to no return code:
TASK [ansible.automation_platform_installer.receptor : Report error when a receptor node cannot resolve a connected peer name] *** The conditional check 'item.rc != 0' failed. The error was: error while evaluating conditional (item.rc != 0): 'item' is undefined. 'item' is undefined
