wbrawner/ansible
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

fix issue with no_log in py3

Browse source 
the error percolates differently from undefined vars in jinja2,
so fallback to use play_context as it is not involved in current templating
This commit is contained in:
Brian Coca 2018-08-27 14:19:06 -04:00 committed by Matt Clay
parent 26be68dd1c
commit 4dea9d84ed
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
lib/ansible/executor/task_executor.py
View file

@ -171,10 +171,10 @@ class TaskExecutor:
display.debug("done dumping result, returning")
return res
except AnsibleError as e:
return dict(failed=True, msg=wrap_var(to_text(e, nonstring='simplerepr')), _ansible_no_log=self._task.no_log)
return dict(failed=True, msg=wrap_var(to_text(e, nonstring='simplerepr')), _ansible_no_log=self._play_context.no_log)
except Exception as e:
return dict(failed=True, msg='Unexpected failure during module execution.', exception=to_text(traceback.format_exc()),
stdout='', _ansible_no_log=self._task.no_log)
stdout='', _ansible_no_log=self._play_context.no_log)
finally:
try:
self._connection.close()