minor update: only migrate HA VIP away when needed
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.
Reviewed: https:/ /review. opendev. org/746927 /git.openstack. org/cgit/ openstack/ tripleo- heat-templates/ commit/ ?id=164fac75a0f bff2130f39a5f4d 7c5931f5ea3b08
Committed: https:/
Submitter: Zuul
Branch: master
commit 164fac75a0fbff2 130f39a5f4d7c59 31f5ea3b08
Author: Damien Ciabrini <email address hidden>
Date: Wed Aug 19 15:40:00 2020 +0200
minor update: only migrate HA VIP away when needed
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 da422e69ebef4ac a81e4877156
Change-Id: Id9b9c413ee37dc