164fac75a0
When update tasks runs in a HA controller node, pacemaker is stopped, along with all HA resources hosted on the node. If any VIP is hosted on that node, it is moved to another node prior to stopping pacemaker to limit service downtime. If the HA controller node doesn't manage VIP (no HAProxy) or the control plane only has 1 node, there is no need to try and move VIP away before stopping pacemaker. Tested on a 1-node HA control plane, and also on a control plane with external balancer (no HAproxy service, thus no VIP managed in pacemaker). The dedicated ansible task no longer tries to move VIP if it doesn't need to. Closes-Bug: #1892570 Change-Id: Id9b9c413ee37dcda422e69ebef4aca81e4877156 |
||
---|---|---|
.. | ||
clustercheck-container-puppet.yaml | ||
compute-instanceha-baremetal-puppet.yaml | ||
ovn-dbs-baremetal-puppet.yaml | ||
pacemaker-baremetal-puppet.yaml | ||
pacemaker-remote-baremetal-puppet.yaml |