# async tasks not following remote\_tmp settings

**URL:** <https://forum.ansible.com/t/async-tasks-not-following-remote-tmp-settings/24982>\
**Category:** Ansible Project\
**Created:** [July 14, 2017, 8:09am UTC](https://forum.ansible.com/t/async-tasks-not-following-remote-tmp-settings/24982 "2017-07-14T08:09:00Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![alan](https://avatars.discourse-cdn.com/v4/letter/a/a87d85/32.png) [@alan](https://forum.ansible.com/u/alan)\
**Post date:** [July 14, 2017, 8:09am UTC](https://forum.ansible.com/t/async-tasks-not-following-remote-tmp-settings/24982/1 "2017-07-14T08:09:00Z")

</div>

Greetings,

I think I’m having the same issue reported in [#10054](https://github.com/ansible/ansible/issues/10054), but using Ansible-2.3.0.

A little background: I’m running an Ansible playbook on remote systems where the root directory (which includes /home dirs) is in read-only mode, so I changed the configuration for running the playbook as follows:

`  
[defaults]

ansible\_managed = Ansible managed: last seen on %Y-%m-%d %H:%M:%S

# /home dirs are not writable. Use /tmp instead

local\_tmp = /tmp  
remote\_tmp = /tmp

[ssh\_connection]

pipelining = True  
ssh\_args = -o ControlMaster=auto -o ControlPersist=60s -o ConnectTimeout=30  
`

I’m trying to run some tasks asynchronously, but they all fail with this error message: “could not create: /home/user/.ansible\_async”, so it seems like the remote\_tmp setting is ignored in async tasks.

Does anybody have the same issue as me?

---

<div class="post-metadata">

**Author:** ![alan](https://avatars.discourse-cdn.com/v4/letter/a/a87d85/32.png) [@alan](https://forum.ansible.com/u/alan)\
**Post date:** [August 17, 2017, 8:49am UTC](https://forum.ansible.com/t/async-tasks-not-following-remote-tmp-settings/24982/2 "2017-08-17T08:49:10Z")

</div>

Created new issue [#28318](https://github.com/ansible/ansible/issues/28318).
