Bug 1177611

Summary: HA routers interact badly with l2pop
Product: Red Hat OpenStack Reporter: Toni Freger <tfreger>
Component: openstack-neutronAssignee: Mike Kolesnik <mkolesni>
Status: CLOSED ERRATA QA Contact: Alexander Stafeyev <astafeye>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.0 (Juno)CC: adahms, amuller, chrisw, jschluet, lpeer, mkolesni, mlopes, nyechiel, oblaut, sclewis, yeylon
Target Milestone: beta   
Target Release: 8.0 (Liberty)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-neutron-7.0.0-4.el7ost Doc Type: Known Issue
Doc Text:
A known issue has been identified for interactions between High Availability (VRRP) routers and L2 Population. Currently, when connecting a HA router to a subnet, HA routers use a distributed port by design. Each router has the same port details on each node that it's scheduled on, and only the master router has IPs configured on that port; all the slaves have the port without any IPs configured. Consequently, L2Population uses the stale information to advise that the router is present on the node (which it states in the port binding information for that port). As a result, each node that has a port on that logical network has a tunnel created only to the node where the port is presumably bound. In addition, a forwarding entry is set so that any traffic to that port is sent through the created tunnel. However, this action may not succeed as there is not guarantee that the master router is on the node specified in the port binding. Furthermore, in the event that the master router is in fact on the node, a failover event would cause it to migrate to another node and result in a loss of connectivity with the router.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-07 21:00:02 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:
Bug Depends On:    
Bug Blocks: 1271974    

Description Toni Freger 2014-12-29 13:03:14 UTC 
Description of problem:

Since internal HA router interfaces are created on more than a single agent, this interacts badly with l2pop that assumes that a Neutron port is located in a certain place in the network. We'll need to report to l2pop when a HA router transitions to an active state, so the port location is changed.
Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 lpeer 2014-12-29 13:45:46 UTC 
This bug implies we can not activate L2pop with HA routers for now. a documentation bug was reported bug 1177623
Comment 3 Martin Lopes 2015-01-29 05:55:00 UTC 
*** Bug 1177623 has been marked as a duplicate of this bug. ***
Comment 5 lpeer 2015-04-30 07:17:21 UTC 
The fix won't be available in Kilo it would first go to liberty.
After the patch is merged we need to look into backporting it both u/s and d/s.
If a backport is feasible then we should clone this bug to OSP-7
Comment 6 Nir Yechiel 2015-08-11 14:52:53 UTC 
The patch was merged and will be available with Liberty.
Comment 7 Assaf Muller 2015-08-11 14:56:30 UTC 
Attached u/s Kilo backport patch:
https://review.openstack.org/#/c/211166/
Comment 14 Alexander Stafeyev 2015-12-01 09:16:55 UTC 
Verified after testing on Liberty
Comment 16 errata-xmlrpc 2016-04-07 21:00:02 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://rhn.redhat.com/errata/RHEA-2016-0603.html