-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
No such file or directory : ~/.ansible/tmp/ansible-tmp-.../wait_for.py #25
Comments
What version of ansible are you using manually? Maybe try testing with StackStorm's copy of ansible: |
That error looks familiar to me from Ansible, see reports:
where people are still having this issue. I think it depends on a mix of local/remote server configuration, Ansible version, ssh settings and so on. As @cognifloyd noted, first thing is that StackStorm runs Ansible binary directly, installed into isolated virtualenv:
The main idea is: if you could run that binary, - StackStorm would be able to run too. Having that path to executable, - try to run the same command with your params from CLI, add more verbosity to reveal what's happening behind the hood. Is the same command running manually failing or not? Hope that helps as a starting point for debugging this. |
What version of ansible is installed with StackStorm? I'm testing using the Docker image and it looks like it uses 2.5.1
And just to let you know, running the playbook just using the ansible-playbook on the virtualenv it works:
|
That's a good start! Add more verbosity Try to run the same virtualenv command from |
Hi Eugen, Thanks for your help, here is the information you have requested: run: virtualenvs-ansible-playbook.txt Im not sure what you meant about running it as from stanley user, but I did the following and it failed:
Regards, |
@cdggcali Returning back to Ansible issue. Try this. Create
Re-run the st2 ansible.playbook command and let us know. |
@armab, that solved the issue. I have a couple questions:
I'm trying to determine if I fail to follow the installation instructions, if is assumed that you will have Ansible installed on the servers or if it should be added to the installation instructions? Regards, |
@cdggcali Thanks for confirming! Yes, you'll probably need to add this workaround to your container + any custom st2 installation. First time I was caught by this issue when added This is a bug in Ansible (ansible/ansible#21562) and they got really a lot of reports. They're trying to put everything together and fix it in some future release: ansible/ansible#31022 I'll dig a bit further and see if we could provide workarounds in st2 as well, but we really do pass |
@cdggcali Since the workaround works for you, I've updated the first message in this issue to include possible solutions (3) - so it'll be easier for others to find it: #25 (comment) Let's also gather more feedback, - maybe someone has a better idea why it's happening. @brainstorm looks like had the same issue before (ansible/ansible#21562 (comment)) |
Hi,
Im testing to stackstorm-ansible to test if we could use it to update Ubuntu servers.
I have a good know playbook that I can successfully run using the standard ansible-playbook command, to run that playbook using Strackstorm Im using the following command:
The task is the following:
And it is failing with the following error:
Is it possible the path is not correct since Im using Stackstrom?
Regards,
Carlos
Update: The Workaround/Solution
There is a bug in Ansible (ansible/ansible#21562) and they got really a lot of reports like this. They're trying to put everything together and fix it in some future release: ansible/ansible#31022
Until that:
Workaround 1
Set in
ansible.cfg
:Workaround 2
Pass those environment variables to ansible command:
Workaround 3
Downgrade of Ansible to version
2.2.0
.The text was updated successfully, but these errors were encountered: