Symptoms
- You see an
''address'': AnsibleUndefined`
error when runningopsview-deploy
:
2022-01-12 16:10:12,401 p=41101 u=root n=ansible | fatal: [orchestrator]: FAILED! =>
msg: 'Invalid data passed to ''loop'', it requires a list, got this instead: [{''address'': AnsibleUndefined}, {''address'': AnsibleUndefined}, {''address'': AnsibleUndefined} ...
There are two known causes of this issue. Both causes relate to the SSH tunnels configuration in your user_vars.yml
file.
Cause: Undefined collectors in user_vars.yml
There are collectors defined in the SSH tunnels configuration of your user_vars.yml
file that are not defined in your opsview_deploy.yml
file.
Solution
Check the opsview_ssh_tunnels_reverse_collectors
and opsview_ssh_tunnels_forward_collectors
sections of your user_vars.yml
file for any collectors that are not defined in opsview_deploy.yml
. If you find entries for any such collectors in either of these opsview_ssh_tunnels_..._collectors
sections, remove them.
Hostnames only
Collectors should only be defined by their hostnames in theopsview_ssh_tunnels_..._collectors
sections. They should not be defined by their FQDNs.Cause: Collectors missing from setup-hosts.yml
scope
You are running the setup-hosts.yml
playbook using opsview-deploy
with the -l
flag to limit its scope to specific hosts. Collectors with SSH tunnel configuration in user_vars.yml
are being excluded from scope.
Solution
Include all collectors declared in the opsview_ssh_tunnels_..._collectors
sections of your user_vars.yml
file in the scope of opsview-deploy
when using -l
to limit the scope of the setup-hosts.yml
playbook.
Comments
0 comments
Please sign in to leave a comment.