you can try *ignore_errors: yes *in your handler. On Thursday, 7 May 2015 16:25:05 UTC+2, Shawn Ferry wrote: > > I've recently experienced the case where a handler has failed stopping the > remaining handler execution in a playbook. > > Once the triggering change has completed subsequent playbook execution > will not notify the handlers again even if they didn't finish the last time. > > Is there any way to capture the handlers which would have been run and run > them on a subsequent playbook execution? Clearly the best thing would be > not failing in the first place but I can't always ensure that will be the > case. > > > > >
-- 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]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/0c057a5c-63ed-492d-af20-6c3276a48743%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
