[LISPMAP-47] RPC get-mapping returns only one locator, when multiple locators are present Created: 17/Jun/15  Updated: 19/Oct/17  Resolved: 07/Jul/15

Status: Resolved
Project: lispflowmapping
Component/s: Service
Affects Version/s: Lithium
Fix Version/s: None

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
Platform: All


External issue ID: 3781
Priority: Low

 Description   

Summary says it all.



 Comments   
Comment by Vina Ermagan [ 18/Jun/15 ]

When using the RPC interface to retrieve mappings, the DAO backend is
queried for the data. Howver, the DAO doesn't store the 'name' list key
for a mapping, and so far the string "Autogenerated" was returned for
each locator. It looks like the ODL RPC implementation doesn't allow
list entries with duplicate keys, so only one locator was returned to
the user (even though the LISP code handled all).

The current fix changes to "Autogenerated" string to be the textual
representation of the locator. This does not fully solve the bug,
since it is theoretically possible to list the same locator more than
once in a mapping. That is not the case for normal operation however,
so at least we can lower the severity of the bug from 'critical' to
'minor'.

The proper fix is to store the user supplied key for the locator in the
DAO.

Change-Id: Icdfeb4a7ce9a79c16e854e8e92ebd6d1f7d30ed5
Signed-off-by: Lorand Jakab <lojakab@cisco.com>
https://git.opendaylight.org/gerrit/#/c/22828/

Comment by Lori Jakab [ 06/Jul/15 ]

Full fix submitted: https://git.opendaylight.org/gerrit/#/c/23797/

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