-
-
Notifications
You must be signed in to change notification settings - Fork 606
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
Finalizing deploys broken on Ansible 2.x #469
Comments
Do you recommend any kind of quick patch for this? This is happening to me on Ansible 2.0.0.1 Downgrading to Ansible 2.0.0.0 supposedly resolves the issue for now. I'm wrestling with homebrew to see if that works but I wanted to know if you thought it would be better to comment out that task and manually symlink the current directory until the patch is included |
2.0.0 won't work either. That comment meant they "downgraded" to the dev build. A workaround would be to remove the
It's just 2 simple tasks. If you end up doing it maybe we'd add it to Trellis as a stop-gap. |
I updated my OS last night and my package manager moved to Ansible 2.0.0.2. Deploys are now failing due to unset subtree paths (not in use):
I've moved back to 1.9.4 for now. |
@davenaylor could you tell what OS and how you manage ansible on your system? Example:
For example using OSX with homebrew you can uninstall ansible and install homebrew/versions/ansible19 and use that until fix for 2.x is announced. |
For people looking for a quick fix, it's super easy to just find the file deploy_helper.py on your system ( |
@16nsk Linux Arch. Like I say though, I moved back to 1.9.4 for now. |
Still not fixed? |
PR's accepted Sent from my iPhone
|
I got this error, then tried to dowgrade to 1.9.4. When running the deploy script, I get
This is from a brand new trellis checkout from earlier this week. I am going to just use the current Ansible release and try @baptistmarchand suggestion |
Temporary fix until Ansible releases a version which includes this version of the `deploy_helper` module.
Hi. What is a reliable workaround for this? On Ansible 2 I get the error about 'vars_files' is not a valid attribute for a PlaybookInclude and on Ansible 1.9, the "fail is not a legal parameter." I tried the workaround in ansible/ansible-modules-extras@1dd62b1 with no luck. Is there a version of Ansible that this works on, and/or a workaround that I could apply despite being quite new to Ansible usage? |
@JohnKelty this has been fixed for a while in Trellis. The version requirements are in the README. |
Indeed it has. I saw the error was the same as what I was working on and forgot to notice that the playbook in question was different, so please ignore my comment and sorry for the inconvenience I'll follow this up in the right place. |
Creating here so we can track it even though it's a bug within Ansible. We use the
deploy_helper
and the deploy will fail on the last step during finalizing (symlinkingcurrent
).The bug was fixed in ansible/ansible-modules-extras@1dd62b1 but the latest Ansible 2.0.0.2 hasn't updated their "extras" module to include that commit yet.
The text was updated successfully, but these errors were encountered: