[NETVIRT-216] When router is associated to L3VPN , VRF entry creations takes long time. Created: 25/Oct/16  Updated: 19/Oct/17  Resolved: 04/Nov/16

Status: Verified
Project: netvirt
Component/s: General
Affects Version/s: Boron
Fix Version/s: None

Type: Bug
Reporter: Hanamantagoud V Kandagal Assignee: Unassigned
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 7024

 Description   

When router is associated to L3VPN and dis-associated it took long time for VRF entries to get created and also table=21 to appear.

When swap from internal-to-external VPN or vice-versa , VpnInterfaceManager waited on notify task for 50sec eventhough FIB has already cleaned up. It was due to notification not fired from VpnInterface Oplistner.

 Comments   
Comment by A H [ 25/Oct/16 ]

A patch was submitted to fix this bug in Boron SR1: https://git.opendaylight.org/gerrit/#/c/47540/

To better assess the impact of this bug and fix, could someone from your team please help us identify the following:
Severity: Could you elaborate on the severity of this bug? Is this a BLOCKER such that we cannot release Boron SR1 without it? Is there a workaround such that we can write a release note and fix in Carbon?
Testing: Could you also elaborate on the testing of this patch? How extensively has this patch been tested? Is it covered by any unit tests or system tests?
Impact: Does this fix impact any dependent projects?

Comment by Sam Hague [ 25/Oct/16 ]

(In reply to A H from comment #1)
> A patch was submitted to fix this bug in Boron SR1:
> https://git.opendaylight.org/gerrit/#/c/47540/
>
> To better assess the impact of this bug and fix, could someone from your
> team please help us identify the following:
> Severity: Could you elaborate on the severity of this bug? Is this a
> BLOCKER such that we cannot release Boron SR1 without it?
BGP VPN use cases fail completely.

Is there a workaround such that we can write a release note and fix in Carbon? No

Testing: Could you also elaborate on the testing of this patch? How
> extensively has this patch been tested? Is it covered by any unit tests or
> system tests?
There are downstream CSIT tests and manual tests that caught this issue. The same tests have been ran to verify the fix.

> Impact: Does this fix impact any dependent projects? No.

Comment by Sam Hague [ 26/Oct/16 ]

b: https://git.opendaylight.org/gerrit/47562
c: https://git.opendaylight.org/gerrit/47540

Comment by A H [ 01/Nov/16 ]

Has this bug been verified as fixed in the latest Boron SR1 Build 20161030?

Comment by Vivekanandan Narasimhan [ 04/Nov/16 ]

Yes, this has been verified in the SR1..

Generated at Wed Feb 07 20:21:00 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.