[HONEYVBD-6] Error when removing nodes from bridge domain Created: 23/Jun/16  Updated: 20/Nov/17  Resolved: 14/Sep/16

Status: Resolved
Project: honeycomb-vbd
Component/s: General
Affects Version/s: unspecified
Fix Version/s: None

Type: Bug
Reporter: Michal Cmarada Assignee: Tyler Levine
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 6105
Priority: Highest

 Description   

If we have created a bridge domain and then assigned some nodes to this Bridge domain a VXLAN tunnel is created (like in tutorial: https://wiki.fd.io/view/Honeycomb/VBD_API).

But after removing these nodes from BD everything in operational DS is still configured as if these nodes are still present.

Nodes were deleted using: DELETE http://localhost:8181/restconf/config/network-topology:network-topology/network-topology:topology/testBD/node/dut1 (dut2)

Nodes were successfully deleted from config DS, but there has been no change in operational DS.

config DS before removing all nodes from BD:
http://pastebin.com/Uv1FxiUz

config DS after removing all nodes from BD:
http://pastebin.com/711r1Z3D

operational DS before/after removing nodes:
http://pastebin.com/4bF3UM2S

 Comments   
Comment by Michal Cmarada [ 24/Jun/16 ]

Found out that this feature is not yet implemented. see BridgeDomain.java line 341.

Comment by A H [ 08/Sep/16 ]

To better assess the impact of this bug and fix, could someone from your team please help us identify the following:
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?
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?
Impact: Does this fix impact any dependent projects?

Comment by A H [ 08/Sep/16 ]

Bumping to blocker so that release can track.

Comment by Michal Cmarada [ 11/Sep/16 ]

fix for stable/boron:
https://git.opendaylight.org/gerrit/#/c/45404

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)

Comment by Michal Cmarada [ 11/Sep/16 ]

(In reply to A H from comment #2)
> To better assess the impact of this bug and fix, could someone from your
> team please help us identify the following:
> 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?
> 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?
> Impact: Does this fix impact any dependent projects?

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.
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.
There is no known workaround.
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.
Currently there are no unit tests covering this area. There are Functests, Yardstick and other automated tests for FDS scenario in progress.

Comment by A H [ 12/Sep/16 ]

Has this bug been verified as fixed in the latest Boron RC 3.5 Build?

Comment by Juraj Linkeš [ 13/Sep/16 ]

(In reply to A H from comment #6)
> Has this bug been verified as fixed in the latest Boron RC 3.5 Build?

I have verified this bug. All resources are properly deleted - the bug resolved the issue.
Image used to verify: https://nexus.opendaylight.org/content/repositories/autorelease-1495/org/opendaylight/integration/distribution-karaf/0.5.0-Boron/

Generated at Wed Feb 07 20:01:41 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.