https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/LISPMAP-135 lispflowmapping <p>Whatever is written in the operational MD-SAL data-store is replicated in the cluster, but our ClusteredDataTreeChangeListener is only watching the configration data-store, so we don't get notifications for mappings added from the southbound. Southbound mappings don't follow the same pattern for adding to the map-cache as the other operations.</p> <p>Operating System: All<br/> Platform: All</p> LISPMAP-135

Clustering: operational data is not showing up in the in-memory map-cache on the replicas

Bug Resolved Done Vina Ermagan Lori Jakab Thu, 25 Aug 2016 23:19:29 +0000 Thu, 8 Sep 2016 18:14:14 +0000 Thu, 8 Sep 2016 18:14:14 +0000 Boron Service 0 3 <p>This seems to be a blocker bug as further testing shows after failure operational is still inconsistent. DataListener should propagate SB originated changes if the node is not Master.</p> <p>Is there an ETA for this bug and someone assigned to fix?</p> <p>Vina and Lori are working on this. Targeting Friday for fix. But for fix and post fix testing eta may likely be as long as next Tue.</p> <p>Proposed fix: <a href="https://git.opendaylight.org/gerrit/#/c/45151/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/45151/</a></p> <p>This may not be the proper long term solution, but I think we can release with this, since it fixes the issue.</p> <p>Can we cherry pick to stable/boron?</p> <p>To better assess the impact of this bug and fix, could someone from your team please help us identify the following:<br/> Severity: Could you elaborate on the severity of this bug? Is this a BLOCKER such that we cannot release Boron without it? Is there a workaround such that we can write a release note and fix in future Boron SR1?<br/> Testing: Could you also elaborate on the testing of this patch? How extensively has this patch been tested? Is it covered by any unit tests or system tests? <br/> Impact: Does this fix impact any dependent projects?</p> <p>(In reply to A H from comment #6)<br/> &gt; To better assess the impact of this bug and fix, could someone from your<br/> &gt; team please help us identify the following:<br/> &gt; Severity: Could you elaborate on the severity of this bug? Is this a<br/> &gt; BLOCKER such that we cannot release Boron without it? Is there a workaround<br/> &gt; such that we can write a release note and fix in future Boron SR1?</p> <p>I'll defer to Vina, our PTL on this question.</p> <p>&gt; Testing: Could you also elaborate on the testing of this patch? How<br/> &gt; extensively has this patch been tested? Is it covered by any unit tests or<br/> &gt; system tests?</p> <p>Since this is clustering related and we don't yet have CSIT for clustering, there is no automated testing. Unit/integration tests can't cover clustering scenarios, AFAIK. The bug was discovered, and the patch was tested manually.</p> <p>&gt; Impact: Does this fix impact any dependent projects?</p> <p>No.</p> <p>This fix is now merged and cherrypicked to stable/boron: <a href="https://git.opendaylight.org/gerrit/#/c/45188/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/45188/</a></p> <p>Has this bug been verified as fixed in the latest Boron RC 3.1 Build?</p> <p>RC 3.2 has been tested and verified as fixed for this bug.</p> Development External issue ID 6536 External issue URL Issue Type ODL SR Target Milestone Priority Rank 0|i01ny7: