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
{{ message }}
This repository has been archived by the owner on Jun 18, 2019. It is now read-only.
TASK [duffy : Provision duffy resources by looping on count] *******************
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: ImportError: No module named jinja2
fatal: [localhost]: FAILED! => {"changed": false, "module_stderr": "Traceback (most recent call last):\n File "/tmp/ansible_1dNcq_/ansible_module_duffy.py", line 75, in \n from ansible.constants import mk_boolean\n File "/usr/lib/python2.6/site-packages/ansible/constants.py", line 12, in \n from jinja2 import Template\nImportError: No module named jinja2\n", "module_stdout": "", "msg": "MODULE FAILURE", "rc": 0}
the issue is in ansible but the overly aggresive import is showing the problem.
from ansible.module_utils.basic import *
If that were limited to just what is needed we may not hit the problem.
The text was updated successfully, but these errors were encountered:
herlo
changed the title
centos6 python2.6 fails on jija2
centos6 python2.6 fails on jinja2
Feb 14, 2018
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
TASK [duffy : Provision duffy resources by looping on count] *******************
An exception occurred during task execution. To see the full traceback, use -vvv. The error was: ImportError: No module named jinja2
fatal: [localhost]: FAILED! => {"changed": false, "module_stderr": "Traceback (most recent call last):\n File "/tmp/ansible_1dNcq_/ansible_module_duffy.py", line 75, in \n from ansible.constants import mk_boolean\n File "/usr/lib/python2.6/site-packages/ansible/constants.py", line 12, in \n from jinja2 import Template\nImportError: No module named jinja2\n", "module_stdout": "", "msg": "MODULE FAILURE", "rc": 0}
the issue is in ansible but the overly aggresive import is showing the problem.
from ansible.module_utils.basic import *
If that were limited to just what is needed we may not hit the problem.
The text was updated successfully, but these errors were encountered: