Files
openstack-ansible-haproxy_s…/releasenotes/notes/haproxy_rise_fall-64ba2e6d7e206973.yaml
Dmitriy Rabotyagov 6532898a3c Make use of haproxy_rise and haproxy_fall variables
At the moment for some reason we're not taking into account default
variables haproxy_rise/haproxy_fall but instead trying to count
based on amount of backends. This makes quite little sense to
depend amount of backend rechecks on amount of backends overall,
so we're chaning behaviour to pre-defined variables that already exist.

Change-Id: I1e53a997f6f443718ea2c6bdfbe8a0b98c44896d
2022-12-09 15:44:29 +01:00

9 lines
350 B
YAML

---
fixes:
- |
Variables ``haproxy_fall`` and ``haproxy_rise`` are now respected again
and will be used for defining amount of checks before haproxy will mark
backend as UP or DOWN. Keys ``backend_rise`` and ``haproxy_fall`` that are
set inside service definition are still respected and will have
prescedence over global ones.