commit af6e1ca4fd3366c1ae936d225b2835e95a4191fc
Author: Mark Goddard <email address hidden>
Date: Mon Aug 16 17:03:22 2021 +0100
Support Ansible max_fail_percentage
This allows us to continue execution until a certain proportion of hosts
to fail. This can be useful at scale, where failures are common, and
restarting a deployment is time-consuming.
The default max failure percentage is 100, keeping the default
behaviour. A global max failure percentage may be set via
kolla_max_fail_percentage, and individual services may define a max
failure percentage via <service>_max_fail_percentage.
Note that all hosts in the inventory must be reachable for fact
gathering, even those not included in a --limit.
Reviewed: https:/ /review. opendev. org/c/openstack /kolla- ansible/ +/805598 /opendev. org/openstack/ kolla-ansible/ commit/ af6e1ca4fd3366c 1ae936d225b2835 e95a4191fc
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit af6e1ca4fd3366c 1ae936d225b2835 e95a4191fc
Author: Mark Goddard <email address hidden>
Date: Mon Aug 16 17:03:22 2021 +0100
Support Ansible max_fail_percentage
This allows us to continue execution until a certain proportion of hosts
to fail. This can be useful at scale, where failures are common, and
restarting a deployment is time-consuming.
The default max failure percentage is 100, keeping the default max_fail_ percentage, and individual services may define a max _max_fail_ percentage.
behaviour. A global max failure percentage may be set via
kolla_
failure percentage via <service>
Note that all hosts in the inventory must be reachable for fact
gathering, even those not included in a --limit.
Closes-Bug: #1833737 8b539dc0421374b 06cea44be4f
Change-Id: I808474a75c0f0e