[LISPMAP-46] Inconsistency between DAO and MD-SAL config datastore at startup Created: 17/Jun/15 Updated: 19/Oct/17 Resolved: 18/Jun/15 |
|
| Status: | Resolved |
| Project: | lispflowmapping |
| Component/s: | Service |
| Affects Version/s: | Lithium |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Florin Coras | 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: | 3765 |
| Description |
|
After a controller restart, with a non-empty set of registered mappings, the mdsal config datastore is correctly restored, however the dao is empty. Apart from the inconsistency, this also prevents manually re-registering the mappings to dao via either rpc/restconf calls. That is, because the mappings are already in the config datastore, overwritting them with identical mappings will not generate notifications needed for replicating these mappings to dao. |
| Comments |
| Comment by Florin Coras [ 17/Jun/15 ] |
|
Fix submitted https://git.opendaylight.org/gerrit/#/c/22751/ |