[LISPMAP-168] When lazy removing expired mappings, the mapping system doesn't check for less specifics Created: 15/Sep/17 Updated: 13/Dec/17 Resolved: 13/Dec/17 |
|
| Status: | Resolved |
| Project: | lispflowmapping |
| Component/s: | General |
| Affects Version/s: | unspecified |
| Fix Version/s: | Oxygen, Nitrogen-SR2 |
| Type: | Bug | ||
| Reporter: | Lori Jakab | 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: | 9171 |
| Priority: | Normal |
| Description |
|
If a mapping lookup result is an expired mapping, it is removed and null returned from the mapping system, resulting in a negative mapping. However, a less specific positive may exist, so instead of returning null, a new lookup should be performed. |
| Comments |
| Comment by Lori Jakab [ 28/Nov/17 ] |
|
Proposed fix: https://git.opendaylight.org/gerrit/#/c/66001/ |