Failed to resolve remote temporary directory from ansible-tmp...

61 views
Skip to first unread message

Adam Shand

unread,
May 24, 2019, 12:49:24 AM5/24/19
to Ansible Project
Enter code here...

Hey,

I submitted a bug but got told "it wasn't a bug" and to ask here.  So I'm asking here. :-)

I'm an Ansible newbie, I've just setup some playbooks to manage about a dozen Linux servers.  All going fine except that Ansible will not connect to two of my servers.  No matter what I try it gives this error every single time I try and connect.

fatal: [docker.xxx.nz]: FAILED! => {"msg": "failed to resolve remote temporary directory from ansible-tmp-1558058780.1613991-43401714620441: `( umask 77 && mkdir -p \"` echo ~/.ansible/tmp/ansible-tmp-1558058780.1613991-43401714620441 `\" && echo ansible-tmp-1558058780.1613991-43401714620441=\"` echo ~/.ansible/tmp/ansible-tmp-1558058780.1613991-43401714620441 `\" )` returned empty string"}


I'm running from my Mac with the latest version of Ansible available from Homebrew.  If you want additional details they are here on the ticket I created:


I get this error with with a very basic playbook which is only doing a ping.

On the ticket they suggested that it might be $HOME (it's the same on working and non-working hosts) or it might be a weird shell (it's bash on all the hosts).

If anyone has any other suggestions I'd would greatly appreciate it.

Cheers,
Adam.

Adam Shand

unread,
May 29, 2019, 10:48:58 PM5/29/19
to Ansible Project
Bump, I could really use some assistance here.  

Can anyone help out?

Thanks,
Adam.

Adam Shand

unread,
May 29, 2019, 11:23:21 PM5/29/19
to Ansible Project
Never mind, just got it to work.

I haven't figured out why, but deleting my home directory and recreating it empty solved the problem.

It wasn't a permissions problem, permissions are identical.  My best guess is maybe something in my .bash* files which it didn't like.
Reply all
Reply to author
Forward
0 new messages