Bug 1565563

Summary: OVN L3HA - Not rescheduling gateways upon chassis addition can lead to routers not being in HA
Product: Red Hat OpenStack Reporter: Daniel Alvarez Sanchez <dalvarez>
Component: python-networking-ovnAssignee: Maciej Józefczyk <mjozefcz>
Status: CLOSED ERRATA QA Contact: Eran Kuris <ekuris>
Severity: high Docs Contact:
Priority: medium    
Version: 13.0 (Queens)CC: amuller, apevec, bcafarel, jlibosva, lhh, majopela
Target Milestone: ---Keywords: Triaged, ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-networking-ovn-4.0.3-20.el7ost Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-10 11:26:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Daniel Alvarez Sanchez 2018-04-10 10:17:30 UTC 
When we are scheduling a gateway on the available chassis, it can happen that only one node is available at that time (because the rest of then network nodes may be down for whatever reason). Therefore, the router will be scheduled on it becoming the active chassis for its gateway.

When the rest of the nodes come up back again in the cluster, no rescheduling happens and the previous router is not effectively in HA. If the active node goes down, North-South traffic to that router will be disrupted as it won't be failed over to any of the network nodes available.

The solution would be to schedule all routers which have been scheduled in less than MAX_GW_CHASSIS [0] chassis in the new nodes (perhaps with a lower priority to avoid failovers although it may cause some unbalance).

[0] http://git.openstack.org/cgit/openstack/networking-ovn/tree/networking_ovn/l3/l3_ovn_scheduler.py?id=d40470a51314fc0c60353c9882e0d2d44c9d2aa5#n31
Comment 6 Miguel Angel Ajo 2018-09-04 14:56:39 UTC 
Updated, Reedip is handling this one.
Comment 14 errata-xmlrpc 2020-03-10 11:26:10 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0770