your issue was in " but it boils down to the fact that the 'upgrade' was unintentional and cost us three weeks of head scratching.". Ansible docs, changelogs and release announcements talk about all the changes that happened. If its something that happened in your environment then its not really ansible's fault.
On Thu, Aug 16, 2018 at 5:40 PM Karl Auer <ka...@2pisoftware.com> wrote: > In three weeks of head-scratching you didn't realise the version of > A > nsible had changed, meaning you allow uncontrolled upgrades to your > production systems? > > Or in three weeks of head-scratching, knowing that Ansible had upgraded, > it didn't occur to you to read the release notes? > > It's a bit rough to blame Ansible for those... > > Regards, K. > > > > > On Fri, Aug 17, 2018 at 7:30 AM, Ilsa Loving <ilsadlov...@gmail.com> > wrote: > >> I'll skip the story since it's long, convoluted, and frustrating, but it >> boils down to the fact that the 'upgrade' was unintentional and cost us >> three weeks of head scratching. >> >> Thanks for the info. Now that I know how capricious Ansible is, we will >> need to reconsider how it is used, and how heavily. This kind of >> fundamental instability make Ansible a very high risk product to use. >> >> Thanks! >> >> >> >> On Thursday, 16 August 2018 16:53:53 UTC-4, Kai Stian Olstad wrote: >>> >>> On Thursday, 16 August 2018 22.36.17 CEST Ilsa Loving wrote: >>> > This should theoretically add the instance to inventory so that when >>> we >>> > perform the following task later: >>> > # Perform server default tasks >>> > - include_tasks: set_server_defaults.yml >>> > delegate_to: "ec2_instance_host" >>> > become: true >>> > >>> > >>> > The task applies a number of changes such as yum updates, etc. >>> > >>> > But as soon as ansible is updated to 2.5+, this behaviour breaks and >>> > instead applies all those server settings to the local host running >>> the >>> > playbook. >>> > >>> > So far our only solution has been to block updates and to keep Ansible >>> at >>> > 2.4, which is far from ideal. >>> > >>> > Does anyone have any insight as to why Ansible's behaviour would >>> change so >>> > fundamentally? This is a catastrophic disruption that has seriously >>> shaken >>> > our confidence in Ansible. >>> >>> Before upgrading it is crucial to read the porting guide >>> >>> https://docs.ansible.com/ansible/2.5/porting_guides/porting_guide_2.5.html >>> >>> for you, especial this >>> >>> https://docs.ansible.com/ansible/2.5/porting_guides/porting_guide_2.5.html#dynamic-includes-and-attribute-inheritance >>> >>> The short answer (for the long one read the links) the delegate_to only >>> applies to the include_tasks, not the tasks inside the include. >>> >>> >>> -- >>> Kai Stian Olstad >>> >>> >>> -- >> You received this message because you are subscribed to the Google Groups >> "Ansible Project" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to ansible-project+unsubscr...@googlegroups.com. >> To post to this group, send email to ansible-project@googlegroups.com. >> To view this discussion on the web visit >> https://groups.google.com/d/msgid/ansible-project/804d6159-b9bb-4283-a848-a6a30a82eb72%40googlegroups.com >> <https://groups.google.com/d/msgid/ansible-project/804d6159-b9bb-4283-a848-a6a30a82eb72%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > Karl Auer > > Email : ka...@2pisoftware.com > Website: http://2pisoftware.com > > GPG/PGP : 958A 2647 6C44 D376 3D63 86A5 FFB2 20BC 0257 5816 > Previous: F0AB 6C70 A49D 1927 6E05 81E7 AD95 268F 2AB6 40EA > > -- > You received this message because you are subscribed to the Google Groups > "Ansible Project" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to ansible-project+unsubscr...@googlegroups.com. > To post to this group, send email to ansible-project@googlegroups.com. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/CA%2B%2BT08R4vDm%3Dr5AGUUNox2yC-aPzO%3DAhfK_vP-orLHzaLVoGpg%40mail.gmail.com > <https://groups.google.com/d/msgid/ansible-project/CA%2B%2BT08R4vDm%3Dr5AGUUNox2yC-aPzO%3DAhfK_vP-orLHzaLVoGpg%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- Jonathan lozada de la matta AUTOMATION CONSULTANT - AUTOMATION PRACTICE Red Hat Consulting Services <https://www.redhat.com/> jloza...@redhat.com -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-project+unsubscr...@googlegroups.com. To post to this group, send email to ansible-project@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAFYJA%2BJZTirnLGrewowBvikHERGcTwJJY7QKNtgt%3DdoCJUaomw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
