Could you provide any stack traces or instructions for reproducing?
I couldn't find any obvious stack trace related to this. However, there are no notifications received whenever something in the config datastore changes, for the subtree we register. RPCs don't work either. Both used to work.
- Steps to reproduce
- Build the lispflowmapping project
- Start the local karaf distribution ./distribution-karaf/target/assembly/bin/karaf
- For testing RPCs, use the Postman collection mappingservice/implementation/src/main/resources/lfm_RPCs.json.postman_collection
- For Testing RESTCONF, use mappingservice/implementation/src/main/resources/lfm_RESTCONF.json.postman_collection
- In case of RESTCONF, when a key or mapping is added, it is stored to the old "DAO" datastore as well, after a change notification is received. This can be checked using "lisp:mappings" on the karaf console
If the lines added by https://git.opendaylight.org/gerrit/#/c/19303 to 01-md-sal.xml in distribution-karaf/target/assembly/etc/opendaylight/karaf/01-md-sal.xml are removed, you can observe the expected behavior for the above steps.
Building 
Question... where in the code do you catch the Notifications?
(in case I need to attach a debugger )
mappingservice/implementation/src/main/java/org/opendaylight/lispflowmapping/implementation/mdsal/AuthenticationKeyDataListener.java and mappingservice/implementation/src/main/java/org/opendaylight/lispflowmapping/implementation/mdsal/MappingDataListener.java