Performance - NeutronVPN is not updating Neutron entities to cache upon DS read

Performance - NeutronVPN is not updating Neutron entities to cache upon DS read

Upon a config shard reelection, and a different one being selected, NeutronVPN caches are not performing true lazy loading.
Cache read will fail followed by a neutron northbound config DS read, but once it's done, cache is not repopulated.
So any subsequent get() calls for such entities created before reelection will result in a config DS read, leading to a significant performance hit on scale tests.