Bug 1395532 - l2pop fdb flows for HA router ports
Summary: l2pop fdb flows for HA router ports
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron
Version: 8.0 (Liberty)
Hardware: x86_64
OS: Linux
high
high
Target Milestone: async
: 8.0 (Liberty)
Assignee: anil venkata
QA Contact: Eran Kuris
URL:
Whiteboard:
Depends On: 1302921
Blocks: 1395533
TreeView+ depends on / blocked
 
Reported: 2016-11-16 05:56 UTC by anil venkata
Modified: 2017-06-20 12:56 UTC (History)
11 users (show)

Fixed In Version: openstack-neutron-7.2.0-9.el7ost
Doc Type: Enhancement
Doc Text:
With this enhancement, L3 HA failover is not dependent on neutron components. This update also reduces HA failover time, as there is no dependency on neutron to create any OVS flows during failover. There is a known issue when both `l2pop` and `arp_responder` are enabled for the linuxbridge agent: the instance will fail to communicate with the router. The temporary workaround is to set `arp_responder=false`. This issue only occurs with the linuxbridge agent; the OVS agent is not affected.
Clone Of: 1302921
: 1395533 (view as bug list)
Environment:
Last Closed: 2017-06-20 12:56:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 255237 0 None None None 2016-11-16 05:56:36 UTC
OpenStack gerrit 369382 0 None None None 2016-11-16 05:56:36 UTC
Red Hat Product Errata RHBA-2017:1540 0 normal SHIPPED_LIVE openstack-neutron bug fix advisory 2017-06-20 16:55:20 UTC

Comment 3 Eran Kuris 2017-06-06 06:08:25 UTC 
verified rhos 8   -p 2017-06-01.1
$ rpm -qa |grep openstack-neutron-7
openstack-neutron-7.2.0-10.el7ost.noarch
Comment 5 errata-xmlrpc 2017-06-20 12:56:53 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-2017:1540
Note You need to log in before you can comment on or make changes to this bug.