No, you actually use that after. If you had a failure and you needed a handler to run on the next run because something should have triggered but did not, you can use that flag.
The retry suggestion has been made before. On Thu, Dec 11, 2014 at 11:54 AM, Petros Moisiadis <[email protected]> wrote: > On 12/11/14 18:15, Michael DeHaan wrote: > > Don't see how this is a bug. Can you elaborate. > > Tried --force-handlers ? > > > The option --force-handlers will work only proactively. You must use it > _before_ the failure occurs. However, this is almost never the case. > Normally, you don't expect your playbook tasks to fail. > A much better solution would be to extend retry files to include handlers > that have already been notified before the failure, so that when using the > retry files, these handlers are pre-notified regardless of the results of > the tasks that notify them normally. I guess that would be a nice feature > for v2. :) > > > > On Tue, Dec 9, 2014 at 10:00 PM, Kevin Burton <[email protected]> > wrote: > >> this is a bug... >> >> TASK: [pdns-recursor | recursor.conf file] >>> ************************************ >>> changed: [10.56.252.12] >>> ERROR: change handler (restart pdns-recursor) is not defined >> >> >> ... so my issue was that the handler wasn't defined (typo). So now it >> has a new file, and the daemon NEEDS to be restarted , but it isn't. >> >> Now, when I run ansible again, it does NOT restart the daemon, because >> the template is already updated. >> >> The solution here would obviously need to restart the daemon and properly >> run the handler. >> >> I think the fix is to revert the 'template' so that the previous file was >> used. >> -- >> 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/de02e7e4-b996-4f1c-b4df-0bd773512d7f%40googlegroups.com >> <https://groups.google.com/d/msgid/ansible-project/de02e7e4-b996-4f1c-b4df-0bd773512d7f%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > > -- > 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/CA%2BnsWgyv%3DeMYD9aWe%2B%3DZT6rPUDT7X2T0PNLK6FT6RYTbPfQn1w%40mail.gmail.com > <https://groups.google.com/d/msgid/ansible-project/CA%2BnsWgyv%3DeMYD9aWe%2B%3DZT6rPUDT7X2T0PNLK6FT6RYTbPfQn1w%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > > > -- 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/CA%2BnsWgyXeOxYO6%3DG0E8f1sK7urAbMQT8%3D9BSHVLViWfnz6bjjw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
