I'm also experiencing the same annoying issue running Ansible from Ubuntu
15.04 (from source: ansible 2.1.0 (devel ccbc7d217b) last updated
2016/02/07 19:18:50 (GMT -700)) on Virtualbox VMs running boot2docker
(python 2.7.10).
It happens on random topics. Having a play that simply pings all hosts and
fails on any error helps a little bit to mitigate, ie. most of the time, if
that passes, the error won't show up. Black magic (sort of).
Any help in identifying/solving the issue is much appreciated.
On Monday, December 28, 2015 at 1:06:50 AM UTC-8, Pradeep Reddy wrote:
>
> I keep getting this error once in every 4/5 times.
>
> fatal: [xxx]: FAILED! => {"failed": true, "msg": "ERROR! failed to resolve
> remote temporary directory from
> ansible-tmp-1451292385.49-145367138177040:
> `( umask 22 && mkdir -p \"$( echo
> $HOME/.ansible/tmp/ansible-tmp-1451292385.49-145367138177040 )\" &&
> echo \"$( echo $HOME/.ansible/tmp/ansible-tmp-1451292385.49-145367138177040
> )\" )` returned empty string"}
>
> This is happening for one of the tasks randomly, following are those tasks
>
> - name: update journald.conf to ForwardToSyslog
>> lineinfile:
>> dest: /etc/systemd/journald.conf
>> regexp: ForwardToSyslog
>> line: ForwardToSyslog=yes
>> sudo: yes
>>
>
>
> - name: create config directory
>> file: name={{config_dir}} state=directory
>> owner=core group=core mode=0755
>>
>
>
>
> I am not sure how to debug this as this doesn't happen always.
>
> Target host is CoreOS with pypy setup, on AWS EC2.
> ansible 2.1.0 (devel d5446f9804)
>
>
--
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/35a428a0-8bcf-409d-abf9-8b93e66a8c1a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
