You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm having a little trouble even trying to identifying what the issue might be and explain it. At any rate,
I use a software named incus that runs my infra. This has an ansbile connection that I configure in the inventory file that should proxy the connection via the incus client to the lxc host . When I try to run a playbook via Semaphore with this connection configured I get some errors. They vary if I turn things on or off right now it's a long string that follows: 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......
However, When I run a ansible-playbook command right on the box i'm running semaphore on.. it works just fine. So i'm guessing there is something I might be missing when telling semaphore to run this Ansible playbook in some other type of way.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I'm having a little trouble even trying to identifying what the issue might be and explain it. At any rate,
I use a software named incus that runs my infra. This has an ansbile connection that I configure in the inventory file that should proxy the connection via the incus client to the lxc host . When I try to run a playbook via Semaphore with this connection configured I get some errors. They vary if I turn things on or off right now it's a long string that follows:
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......
However, When I run a ansible-playbook command right on the box i'm running semaphore on.. it works just fine. So i'm guessing there is something I might be missing when telling semaphore to run this Ansible playbook in some other type of way.
Beta Was this translation helpful? Give feedback.
All reactions