Aborting playbook execution during rolling updates?

[Michael Mahemoff]

I have parallel hosts configured with "serial" to ensure rolling updates. But if one fails, I believe the next one will unconditionally still execute, causing the whole cluster to fail. Is there any way to abort the entire playbook execution (or that for serial hosts anyway) if any one host should fail?

[James Tanner]

I'd send you the link to the docsite, but this will have to do for now:

https://github.com/ansible/ansible/blob/devel/docsite/rst/playbooks_delegation.rst#maximum-failure-percentage

On Mon, Mar 31, 2014 at 3:07 PM, Michael Mahemoff <mic...@mahemoff.com> wrote:

I have parallel hosts configured with "serial" to ensure rolling updates. But if one fails, I believe the next one will unconditionally still execute, causing the whole cluster to fail. Is there any way to abort the entire playbook execution (or that for serial hosts anyway) if any one host should fail?

--
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-proje...@googlegroups.com.
To post to this group, send email to ansible...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/05d841af-d9f2-4e6c-92b1-ed7a8bbd5fbd%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Michael Mahemoff]

Thanks, sorry I missed that in the docs!

http://docs.ansible.com/playbooks_delegation.html#rolling-update-batch-size for future reference