I think a AnsibleError on one host won't be enough. It may be required to add some flag to a ReturnData and then when that is processed back in playbook code land, that might need to throw the error there.
Should be easy to experiment though. On Sat, Aug 2, 2014 at 2:22 AM, Amr Ali <[email protected]> wrote: > Yeah me neither, will have a look tonight, we can't just throw/raise an > ansible error right? > > -- > 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/17a50efc-12a6-42d2-baf6-7139a634d54c%40googlegroups.com > . > 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%2BnsWgx-az6O_M17yrmdHLM8NdDiPwVjt4-qGgWATt8M0sWJTQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
