haproxy restarts can break cluster init
Bug #1348931 reported by
Julia Kreger
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Ben Nemec |
Bug Description
When control scale is set to greater than 2 and the MySQL configuration has been updated to point to the remote VIP, there is a possibility that the controller that takes ownership of the VIP may not be the same controller node as the controller bootstrap node. With this, there is a slim possibility that initialization steps may be connected to the VIP and loose connectivity during the initialization process due to the other node re-attempting initialization and restarting haproxy. This occurring can effectively break the initialization sequence possibly leaving it in a state that cannot be recovered from.
Changed in tripleo: | |
status: | Fix Committed → Fix Released |
Changed in tripleo: | |
assignee: | Julia Kreger (juliaashleykreger) → Ben Nemec (bnemec) |
status: | Triaged → In Progress |
Changed in tripleo: | |
assignee: | Ben Nemec (bnemec) → Julia Kreger (juliaashleykreger) |
Changed in tripleo: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/109963
Review: https:/