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/HONEYVBD-6 honeycomb-vbd <p>If we have created a bridge domain and then assigned some nodes to this Bridge domain a VXLAN tunnel is created (like in tutorial: <a href="https://wiki.fd.io/view/Honeycomb/VBD_API" class="external-link" target="_blank" rel="nofollow noopener">https://wiki.fd.io/view/Honeycomb/VBD_API</a>). </p> <p>But after removing these nodes from BD everything in operational DS is still configured as if these nodes are still present.</p> <p>Nodes were deleted using: DELETE <a href="http://localhost:8181/restconf/config/network-topology:network-topology/network-topology:topology/testBD/node/dut1" class="external-link" target="_blank" rel="nofollow noopener">http://localhost:8181/restconf/config/network-topology:network-topology/network-topology:topology/testBD/node/dut1</a> (dut2)</p> <p>Nodes were successfully deleted from config DS, but there has been no change in operational DS.</p> <p>config DS before removing all nodes from BD:<br/> <a href="http://pastebin.com/Uv1FxiUz" class="external-link" target="_blank" rel="nofollow noopener">http://pastebin.com/Uv1FxiUz</a></p> <p>config DS after removing all nodes from BD:<br/> <a href="http://pastebin.com/711r1Z3D" class="external-link" target="_blank" rel="nofollow noopener">http://pastebin.com/711r1Z3D</a></p> <p>operational DS before/after removing nodes:<br/> <a href="http://pastebin.com/4bF3UM2S" class="external-link" target="_blank" rel="nofollow noopener">http://pastebin.com/4bF3UM2S</a></p> <p>Operating System: All<br/> Platform: All</p> HONEYVBD-6

Error when removing nodes from bridge domain

Bug Resolved Done Tyler Levine Michal Cmarada Thu, 23 Jun 2016 11:57:28 +0000 Mon, 20 Nov 2017 16:54:29 +0000 Wed, 14 Sep 2016 14:51:49 +0000 unspecified General 0 4 <p>Found out that this feature is not yet implemented. see BridgeDomain.java line 341.</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>Bumping to blocker so that release can track.</p> <p>fix for stable/boron:<br/> <a href="https://git.opendaylight.org/gerrit/#/c/45404" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/45404</a></p> <p>This fix was verified on local environment and also in UCS-B side 1 lab. BDs can now be removed and recreated again (verified by Pings, cross node pings worked, ping on the same node worked, ping to DHCP and Qrouter worked)</p> <p>(In reply to A H from comment #2)<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?<br/> &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? <br/> &gt; Impact: Does this fix impact any dependent projects?</p> <p>This bug impacts the deletion of BDs and nodes belonging to BDs. Because of this after deleting nodes from BDs we get corrupted configuration and therefore the running system is corrupted and not working properly. <br/> Currently it is used in FDS scenario in cooperation with GBP, Honeycomb and VPP. Its a blocker because FDS cannot work correctly without the fix for this bug. <br/> There is no known workaround.<br/> The fix was tested several times on local virtual environment and several times in UCS-B side 1 lab environment (bare metal). Tests were done using whole setup including GBP,Honeycomb and VPP and there is no impact on other projects.<br/> Currently there are no unit tests covering this area. There are Functests, Yardstick and other automated tests for FDS scenario in progress.</p> <p>Has this bug been verified as fixed in the latest Boron RC 3.5 Build?</p> <p>(In reply to A H from comment #6)<br/> &gt; Has this bug been verified as fixed in the latest Boron RC 3.5 Build?</p> <p>I have verified this bug. All resources are properly deleted - the bug resolved the issue.<br/> Image used to verify: <a href="https://nexus.opendaylight.org/content/repositories/autorelease-1495/org/opendaylight/integration/distribution-karaf/0.5.0-Boron/" class="external-link" target="_blank" rel="nofollow noopener">https://nexus.opendaylight.org/content/repositories/autorelease-1495/org/opendaylight/integration/distribution-karaf/0.5.0-Boron/</a></p> Development External issue ID 6105 External issue URL Issue Type ODL SR Target Milestone Priority Rank 0|i024ev: