Yep, this is a thing, there's no way to force running all of the handlers.
There's a feature request open for something like --force-handlers that would be super easy to add. But would you generically want to run all of them in every case? Might not work for everyone. Might though. On Fri, Nov 29, 2013 at 7:19 AM, nafg <[email protected]> wrote: > Hi. I have a playbook which had a task (template) with a handler (restart > a service), and another task (copy), which had a typo. When I ran > ansible-playbook, it reported the error and did not trigger the handler. > However the template was updated. I then fixed the typo and ran > ansible-playbook again. The second task now succeeded, however this time > there was no change detected in the first task and so again the handler was > not run. > > I think that should never happen. The service should have been restarted, > probably the first time, since the error really had nothing to do with the > first task or its handler. > > This is with ansible 1.4. > > Thanks! > > -- > 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 [email protected]. > For more options, visit https://groups.google.com/groups/opt_out. > -- Michael DeHaan <[email protected]> CTO, AnsibleWorks, Inc. http://www.ansibleworks.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 [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
