I suggest you delegate your rescue tasks to localhost - when things go wrong on remote hosts, the local host, where ansible is running, is the most likely thing to still be working. Documentation about delegation is here if you aren't familiar with it: http://docs.ansible.com/ansible/latest/playbooks_delegation.html
You may need to adjust what you rescue actually does because of this - perhaps send a mail or message to get a human involved. Hope this helps, Jon On Friday, January 19, 2018 at 2:59:35 PM UTC, Graham Dougan wrote: > > Hi Vlad, > > Struggling with the same issue, did you get anywhere with it? > > Thanks, > Graham > > On Sunday, March 19, 2017 at 10:29:48 PM UTC, kaufma...@gmail.com wrote: >> >> Hello everyone, >> >> For error handling I'm trying to use "block - rescue". I looked im >> internet and found out that rescue doesn't have any effekt if tasks in >> block failed because of unreachable host. Does anyone any workaround or >> idea how to manage it anyway? >> >> Thank you very much! >> >> Vlad >> > -- 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/623c771f-f9a7-4bd6-9cf3-ab827f2c7da9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
