[NETVIRT-392] Internal VPNs must not be considered by InterVpnLink Created: 23/Dec/16  Updated: 19/Oct/17  Resolved: 07/Jan/17

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

Type: Bug
Reporter: Miguel Perez 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: 7439

 Description   

At InterVpnLink creation, al Routers are scanned to see if there is any static route in any of them whose nextHop points to an InterVpnLink endpoint. When one of those routes are found, it must be checked that the router belongs to the right VPN (the one oppossite to the endpoint/nexthop).

However the code is currently considering the internal VPNs that could possible be attached to the router, and some routes are not being considered by the InterVpnLink since the router is being wrongly found as belonging to the internal VPN, not to the external one that is being configured in the InterVpnLink.



 Comments   
Comment by Alon Kochba [ 07/Jan/17 ]

https://git.opendaylight.org/gerrit/#/c/49659

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