___
From: ansible-project@googlegroups.com on
behalf of Go Away
Sent: Saturday, June 19, 2021 9:59:37 PM
To: Ansible Project
Subject: Re: [ansible-project] Batch size (serial) and playbook failing
Hmm. Would be great if the docs said so ;-)
But how to circumvent it? I can try using random or
roject@googlegroups.com on
behalf of Go Away
Sent: Saturday, June 19, 2021 9:59:37 PM
To: Ansible Project
Subject: Re: [ansible-project] Batch size (serial) and playbook failing
Hmm. Would be great if the docs said so ;-)
But how to circumvent it? I can try using random order in order to redu
Hmm. Would be great if the docs said so ;-)
But how to circumvent it? I can try using random order in order to reduce
the probability of the same hosts failing every time but is there any other
way?
pt., 18 cze 2021, 16:56 użytkownik Brian Coca napisał:
> This is by design, if all hosts in a ba
This is by design, if all hosts in a batch fail, the playbook is
failed. The logic was that in rolling releases it makes sense to stop
in the case of a batch failing.
--
--
Brian Coca
--
You received this message because you are subscribed to the Google Groups
"Ansible Project" group.
Hi.
I have a list of hosts of which some will always be unreachable or the
tasks in playbook will otherwise fail. I have no problem with it. I cannot
however understand why if I add "serial: 4" in my playbook and first four
hosts fail, the playbook stops completely not even starting rest of the
