Bug 1177623 - [Documentation] VRRP - HA router feature with l2pop is not working properly.
Summary: [Documentation] VRRP - HA router feature with l2pop is not working properly.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: doc-Installation_and_Configuration_Guide
Version: 6.0 (Juno)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ga
: 6.0 (Juno)
Assignee: Martin Lopes
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On:
Blocks: 1186518
TreeView+ depends on / blocked
 
Reported: 2014-12-29 13:40 UTC by Toni Freger
Modified: 2015-02-13 05:56 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-01-29 05:54:59 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1177611 0 medium CLOSED HA routers interact badly with l2pop 2021-02-22 00:41:40 UTC

Description Toni Freger 2014-12-29 13:40:00 UTC
Description of problem:

VRRP - HA router feature with l2pop is not working properly.
The bug #1177611 should be documented in release notes of RHOS6  

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Mike Kolesnik 2014-12-30 11:41:55 UTC
The technical details:

* When connecting an 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.
* Only the master router would have IPs set on that port while all the slaves have the port without any IPs on it.
* Stale information is kept on the "port binding" field that specifies on which node that port is bound.
* L2Population uses the stale information to instruct whomever is interested that the router sits on the node (which is states in the port binding for that port).
* This results in the following on each node that has a port on that logical network:
** A tunnel is created only to the node where the port is presumably bound.
** A forwarding entry is set so that any traffic to that port is sent through the created tunnel.

This would usually not work since there's no guarantee that the master router is on the node specified in the port binding. I.E. if the master is not on the node then the traffic would be sent to a backup instance of the router which would drop it as it has no IPs on the port.
Furthermore even if by chance the master router is on the node, a failover would cause it to migrate to another node (resulting in loss of communication with the router, as explained).

Comment 2 Martin Lopes 2015-01-29 05:54:59 UTC
Wrote up doc text based on the above comment and added to the original dev bug BZ#1177611.
In addition, I've set the flags on BZ#1177611 to ensure it gets picked up for the RHELOSP 6 GA release notes.

Closing this bug as a duplicate.

*** This bug has been marked as a duplicate of bug 1177611 ***


Note You need to log in before you can comment on or make changes to this bug.