SSH fine but keep getting errors running test playbook

27 views
Skip to first unread message

Shiyan Cao

unread,
Feb 6, 2017, 6:07:24 PM2/6/17
to Ansible Project
Hi,

Does anyone know why I'm getting the error? SSH connection is working fine.


# ansible-playbook -i inventory/qalabs -l xxxxxxx -u root -D test.yml


PLAY [all] *********************************************************************


TASK [setup] *******************************************************************

fatal: [xxxxxx]: FAILED! => {"failed": true, "msg": "failed to resolve remote temporary directory from ansible-tmp-1486411214.9-201171589973071: `mkdir -p \"` echo $HOME/.ansible/tmp/ansible-tmp-1486411214.9-201171589973071 `\" && echo \"` echo $HOME/.ansible/tmp/ansible-tmp-1486411214.9-201171589973071 `\"` returned empty string"}


NO MORE HOSTS LEFT *************************************************************

to retry, use: --limit @test.retry


PLAY RECAP *********************************************************************

xxxxxxx : ok=0    changed=0    unreachable=0    failed=1   



Johannes Kastl

unread,
Feb 7, 2017, 7:15:00 AM2/7/17
to ansible...@googlegroups.com
On 06.02.17 21:03 Shiyan Cao wrote:

> Does anyone know why I'm getting the error? SSH connection is
> working fine.

> fatal: [xxxxxx]: FAILED! => {"failed": true, "msg": "failed to
> resolve remote temporary directory from
> ansible-tmp-1486411214.9-201171589973071: `mkdir -p \"` echo
> $HOME/.ansible/tmp/ansible-tmp-1486411214.9-201171589973071 `\" &&
> echo \"` echo
> $HOME/.ansible/tmp/ansible-tmp-1486411214.9-201171589973071 `\"`
> returned empty string"}

Does using an ad-hoc ping work?

ansible -m ping foobar
(where foobar is your target hostname)

If yes, run your playbook with -v (or even -vvv) to get some more output.

Johannes

signature.asc
Reply all
Reply to author
Forward
0 new messages