-
Notifications
You must be signed in to change notification settings - Fork 34
Update Ansible to 2.9.2 version #1142
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
Comments
P.S. And now it also conflicts with |
One more point: in order to use |
…rent dir. This change makes deployment work on Ansible >2.1.10 See also related issue: ansible/ansible#29618 Prerequisite for #1142
I think that we shouldn't unpin but just update to the latest version. Having a fixed version is good for stable builds. |
New warnings after update to 2.2.30:
This was a bug (see ansible/ansible#23764) that has been fixed in newer versions. |
It seems like we should try |
Warning on 2.9.0 when I run
and
|
Additional changes have been made: 1) remove get_md5 parameter from stat module. From https://docs.ansible.com/ansible/latest/porting_guides/porting_guide_2.5.html#noteworthy-module-changes % The stat and win_stat modules have changed the default of the option get_md5 from true to false. This option will be removed starting with Ansible version 2.9 % 2) rewrite the way we pass variables to roles. Use "vars" parameter for for that. Inspired by https://docs.ansible.com/ansible/latest/porting_guides/porting_guide_2.5.html#fixed-handling-of-keywords-and-inline-variables 3) migrate "with_items" to "loop" as this is "the recommended way to perform loops". Details: https://docs.ansible.com/ansible/latest/porting_guides/porting_guide_2.5.html#migrating-from-with-x-to-loop Changelogs: - https://github.com/ansible/ansible/blob/stable-2.5/changelogs/CHANGELOG-v2.5.rst - https://docs.ansible.com/ansible/latest/porting_guides/porting_guide_2.5.html Part of #1142
Done. New warning after updating to 2.8.x:
|
I'll create an issue for that. |
Finally fixed in 1ebedcd commit. /spent 9h36m |
The pinned and outdated version of Ansible brought too much headaches and it seems it's easier to update Ansible rather than continue to put more workarounds.
Also my initial assumption was that it's a regression and but it's turned out that it was actually a fix for buggy behaviour that we use: ansible/ansible#29618
History:
@asm0dey JFYI
The text was updated successfully, but these errors were encountered: