You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm new to ansible so I'm still figuring out how the pieces all fit together, but when I try using this role I get the following error:
TASK [engonzal.proxmox : Container already exists] ****************************************************************
fatal: [bobik]: FAILED! => {"msg": "The conditional check 'pve_hostname in pve_ct_list_clean|json_query('[*].name')' failed. The error was: You need to install "jmespath" prior to running json_query filter\n\nThe error appears to be in '/home/ldh/.local/share/ansible/roles/engonzal.proxmox/tasks/inventory.yml': line 45, column 3, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n- name: Container already exists\n ^ here\n"}
If "jmespath" is a requirement of the role, maybe you could mention that in the Readme?
I'm also unclear on the best way to proceed; I manually did a pip install jmespath, but ad-hoc manual fixes like that feel contrary to the spirit of trying to manage infrastructure in a declarative manner. Is there a way to express and manage that dependency within ansible itself?
Thanks!
edit: added mention of "proxmoxer" module which is required on the node being managed
The text was updated successfully, but these errors were encountered:
lhanson
changed the title
Implicit requirement on "jmespath"
Implicit requirement on "jmespath" and "proxmoxer"
Jan 16, 2020
I'm new to ansible so I'm still figuring out how the pieces all fit together, but when I try using this role I get the following error:
If "jmespath" is a requirement of the role, maybe you could mention that in the Readme?
I'm also unclear on the best way to proceed; I manually did a
pip install jmespath
, but ad-hoc manual fixes like that feel contrary to the spirit of trying to manage infrastructure in a declarative manner. Is there a way to express and manage that dependency within ansible itself?Thanks!
edit: added mention of "proxmoxer" module which is required on the node being managed
The text was updated successfully, but these errors were encountered: