You are not logged in.
I've recently tried to use a molecule testing environment supplied by my employer to test a ansible role. During the prepare playbook it fails with:
fatal: [instance]: 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 /tmp `\"&& mkdir \"` echo /tmp/ansible-tmp-1682087850.17104-298343-128966035379374 `\" && echo ansible-tmp-1682087850.17104-298343-128966035379374=\"` echo /tmp/ansible-tmp-1682087850.17104-298343-128966035379374 `\" ), exited with result 1", "unreachable": true}When asking around my company I've gathered that everyone who uses a arch based system (Manjaro, Parabola and Arch) is encountering this problem while the others are not and can use it. Before I open a bug report at molecule or ansible I've wanted to find out if this problem can be solved otherwise.
Already tried the following:
- Consider changing the remote tmp path in ansible.cfg to a path rooted in \"/tmp\", produces same error
- 777 permission on ~/.ansible and children
- reinstalling molecule & ansible from arch packages and pip packages
- docker pruning
- molecule destory, molecule remake the role
code: https://github.com/Jocomol/ansible-role … le/default
Versions:
molecule: 4.0.4
ansible: 2.14.4
Thank you very much
Offline