Details
-
Bug
-
Status: Verified
-
Medium
-
Resolution: Unresolved
-
None
-
None
-
None
-
None
Description
When a node (or an entire topo) is deleted from the Config DS, it was deleted from the operational DS only partly. I.e. its non-sxp-augmented counterparts are left untouched. This effectively creates a "DB-memory leak" : The SXP controller would write a new network topology node stub to the DS when adding an SXP node, but would not clean it up when removing the node afterwards.
Attachments
Gerrit Reviews
| # | Subject | Branch | Project | Status | CR | V |
|---|---|---|---|---|---|---|
| 64614,3 | SXP-130 Delete entire node from Operational DS | master | sxp | Status: MERGED | +2 | +1 |
| 64649,1 | SXP-130 Delete entire node from Operational DS | stable/nitrogen | sxp | Status: MERGED | +2 | +1 |