[NETVIRT-388] InterVpnLink: some routes are being leaked even when not needed Created: 21/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 |
||
| External issue ID: | 7423 |
| Description |
|
In the InterVpnLink mobility use case, when the InterVpnLink is re-created in a new DPN, some routes are 'leaked' when it is not even needed. Functionality is Ok, ping works in this case, but there are some flows and fibEntries that are left as garbage. |
| Comments |
| Comment by Alon Kochba [ 07/Jan/17 ] |