Bug 1714119 - Unable to use "Highly available VIPs on OpenStack VMs with VRRP" in OVN based deployment
Summary: Unable to use "Highly available VIPs on OpenStack VMs with VRRP" in OVN based...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-networking-ovn
Version: 14.0 (Rocky)
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
: 14.0 (Rocky)
Assignee: Maciej Józefczyk
QA Contact: Roman Safronov
URL:
Whiteboard:
Depends On: 1722792
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-27 07:18 UTC by Maciej Józefczyk
Modified: 2019-09-09 14:32 UTC (History)
11 users (show)

Fixed In Version: python-networking-ovn-5.0.2-0.20190430191337.e673daf.el7ost
Doc Type: Bug Fix
Doc Text:
This patch fixes an issue wherein the floating IP address on a router configured with VRRP (Virtual Router Redundancy Protocol) on OVN would fail to work. This was due to an additional flow in router ingress pipeline blocking ARP resolution for the floating IP. This has been resolved by not having an address on unbound logical switch ports.
Clone Of: 1707241
: 1722792 (view as bug list)
Environment:
Last Closed: 2019-07-02 19:47:42 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 660258 0 'None' MERGED Do not set port addresses on LSP while port not bound 2020-09-29 08:33:25 UTC
Red Hat Product Errata RHBA-2019:1680 0 None None None 2019-07-02 19:47:47 UTC

Comment 11 Maciej Józefczyk 2019-06-19 13:25:37 UTC 
With Daniels patch it works properly. I've checked it with openvswitch version: 2.10.0-55 that includes it. It works properly on osp14 then.
https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=896920
Comment 16 errata-xmlrpc 2019-07-02 19:47:42 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-2019:1680
Note You need to log in before you can comment on or make changes to this bug.