ovn vip should not be tied to haproxy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Michele Baldessari |
Bug Description
At the time we merged the OVN work in tripleo we thought that there was value in just leveraging the haproxy VIP code bits.
This means that OVS-DB will simply reuse the VIP that is being created for the network on which it is running (typically internal_api).
This was largely a mistake and we should not have done that because that VIP is bound to the haproxy service (i.e. that VIP can only be on the role where haproxy is, aka the controller). That means that 1) we currently cannot split off ovn-dbs to a separate role/node and 2) we have an extra unneeded constraint on this VIP with haproxy, which is something we prolly do not
want.
This was actually caught as real-world problem in rhbz#1728118 because during a deploy when the OVN resource gets created at step3 it will force a move of the internal VIP which then makes all connections to mysql (amongst others) fail.
Changed in tripleo: | |
milestone: | train-3 → ussuri-1 |
Related fix proposed to branch: master /review. opendev. org/679244
Review: https:/