Ansible - Failed to create temporary directory.

horseinthesky · 2020-04-27 20:22:32

Hello.
I have some issues with Ansible.
```
[horseinthesky@HAL8700K dotfiles]$ ansible-playbook install.yml -K
BECOME password:
[WARNING]: No inventory was parsed, only implicit localhost is available
[WARNING]: provided hosts list is empty, only localhost is available. Note that the implicit localhost does not match
'all'

PLAY [localhost] *******************************************************************************************************

TASK [Gathering Facts] *************************************************************************************************
fatal: [localhost]: UNREACHABLE! => {"changed": false, "msg": "Failed to create temporary directory.In some cases, you may have been able to authenticate and did not have permissions on the target directory. Consider changing the remote tmp path in ansible.cfg to a path rooted in \"/tmp\", for more error information use -vvv. Failed command was: ( umask 77 && mkdir -p \"` echo /home/horseinthesky/.ansible/tmp `\"&& mkdir /home/horseinthesky/.ansible/tmp/ansible-tmp-1588014593.2600286-822-23976181027159 && echo ansible-tmp-1588014593.2600286-822-23976181027159=\"` echo /home/horseinthesky/.ansible/tmp/ansible-tmp-1588014593.2600286-822-23976181027159 `\" ), exited with result 1, stdout output: ansible-tmp-1588014593.2600286-822-23976181027159=/home/horseinthesky/.ansible/tmp/ansible-tmp-1588014593.2600286-822-23976181027159\n", "unreachable": true}

PLAY RECAP *************************************************************************************************************
localhost : ok=0 changed=0 unreachable=1 failed=0 skipped=0 rescued=0 ignored=0
```

The same issue with regular modules:
```
[horseinthesky@HAL8700K ~]$ ansible localhost -m setup
[WARNING]: No inventory was parsed, only implicit localhost is available
localhost | UNREACHABLE! => {
"changed": false,
"msg": "Failed to create temporary directory.In some cases, you may have been able to authenticate and did not have permissions on the target directory. Consider changing the remote tmp path in ansible.cfg to a path rooted in \"/tmp\", for more error information use -vvv. Failed command was: ( umask 77 && mkdir -p \"` echo /home/horseinthesky/.ansible/tmp `\"&& mkdir /home/horseinthesky/.ansible/tmp/ansible-tmp-1588018824.3005164-998-101905006439807 && echo ansible-tmp-1588018824.3005164-998-101905006439807=\"` echo /home/horseinthesky/.ansible/tmp/ansible-tmp-1588018824.3005164-998-101905006439807 `\" ), exited with result 1, stdout output: ansible-tmp-1588018824.3005164-998-101905006439807=/home/horseinthesky/.ansible/tmp/ansible-tmp-1588018824.3005164-998-101905006439807\n",
"unreachable": true
}
```

What confuses me the most is that Ansible created these tmp directories successfully but says that it didn't:
```
[horseinthesky@HAL8700K dotfiles]$ tree ~/.ansible/
/home/horseinthesky/.ansible/
└── tmp
└── ansible-tmp-1588018882.724-1047-266338398970543
```

horseinthesky · 2020-04-30 14:56:54

The bug in glibc was the culprit.

Downgrade to
pacman -U /mnt/d/glibc-2.30-3-x86_64.pkg.tar.xz
solve it.

WorMzy · 2020-04-30 15:22:37

Downgrading glibc is not something that should be done without VERY good reason, and even then you need to know what you're doing. You're better off downgrading your entire system to a date when that version of glibc was current.

https://wiki.archlinux.org/index.php/Ar … cific_date

Do you have a link to the bug report?

Arch Linux

#1 2020-04-27 20:22:32

Ansible - Failed to create temporary directory.

#2 2020-04-30 14:56:54

Re: Ansible - Failed to create temporary directory.

#3 2020-04-30 15:22:37

Re: Ansible - Failed to create temporary directory.

Board footer