I am having a very odd problem with some servers.
I have a common role (roles/common/task/main.yml) with this task:
- name: Snmp configuration
template:
src=snmpd.conf.j2
dest=/etc/snmp/snmpd.conf
owner=root
group=root
mode=0600
Before that task I have yum tasks that work as expected. On some servers
that task fails showing:
TASK: [common | Snmp configuration]
*******************************************
fatal: [server] => Traceback (most recent call last):
File
"/usr/local/Cellar/ansible/1.9.3/libexec/lib/python2.7/site-packages/ansible/runner/__init__.py",
line 586, in _executor
exec_rc = self._executor_internal(host, new_stdin)
File
"/usr/local/Cellar/ansible/1.9.3/libexec/lib/python2.7/site-packages/ansible/runner/__init__.py",
line 789, in _executor_internal
return self._executor_internal_inner(host, self.module_name,
self.module_args, inject, port, complex_args=complex_args)
File
"/usr/local/Cellar/ansible/1.9.3/libexec/lib/python2.7/site-packages/ansible/runner/__init__.py",
line 1036, in _executor_internal_inner
result = handler.run(conn, tmp, module_name, module_args, inject,
complex_args)
File
"/usr/local/Cellar/ansible/1.9.3/libexec/lib/python2.7/site-packages/ansible/runner/action_plugins/template.py",
line 114, in run
remote_checksum = self.get_checksum(conn, tmp, dest, inject, not
directory_prepended, source=source)
File
"/usr/local/Cellar/ansible/1.9.3/libexec/lib/python2.7/site-packages/ansible/runner/action_plugins/template.py",
line 34, in get_checksum
remote_checksum = self.runner._remote_checksum(conn, tmp, dest, inject)
File
"/usr/local/Cellar/ansible/1.9.3/libexec/lib/python2.7/site-packages/ansible/runner/__init__.py",
line 1250, in _remote_checksum
python_interp =
inject['hostvars'][host].get('ansible_python_interpreter', 'python')
File
"/usr/local/Cellar/ansible/1.9.3/libexec/lib/python2.7/site-packages/ansible/runner/__init__.py",
line 105, in __getitem__
result.update(self.vars_cache.get(host, {}))
ValueError: dictionary update sequence element #0 has length 1; 2 is
required
FATAL: all hosts have already failed -- aborting
This happens as I said not in all cases, and I haven't been able to
identify nothing particularly different, so I could use some help.
Is this a bug in 1.9.3 ?
Thanks
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/ansible-project/02989a56-2af9-4abb-bb32-1565714f296e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
