-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Deployment fails #14204
Comments
Seeing the same issue on my end. |
I'm seeing the same issue today. I deployed another host with an identical config a couple of days ago and it succeeded. I think the release of jinja2 3.0.0 has caused a problem with this step. See the differences in dependencies:
To confirm, I tried adding
|
Another thing to try is to just delete the directory permissions check from main.yml. |
I tried it after restarting the ssh session. The deployment proceeds without error |
I can reproduce this on my machine. I am not connected through SSH. Editing out the check from
|
Yup this works for me, though I just commented out line 10-15. |
Same problem; like others, commenting out lines 10–15 in main.yml works. |
thanks that solves the issue |
didn't comment the check out but added jinja2==2.8 to requirements.txt at the start which worked for me it seems |
Describe the bug
Deployment from WSL fails during "TASK [Ensure Ansible is not being run in a world writable directory]" due to "template error while templating string: expected token 'end of statement block', got 'integer'." I am baffled to not see this error anywhere else
To Reproduce
Steps to reproduce the behavior:
./algo
Alternately:
./algo -e "provider=gce" -e "gce_credentials_file=$(pwd)/configs/gce.json"
Expected behavior
TASK [Ensure Ansible is not being run in a world writable directory] passes because the directory has correct permissions. Deployment continues.
Additional context
This happens in google cloud shell in addition to WSL, so I don't believe it is related to #1637 despite failing at a similar point.
Output of
pip list
in both:Output of
ansible --version
in WSL:Output of
ansible --version
in GCShell:Full log
WSL output:
GCShell output:
The text was updated successfully, but these errors were encountered: