[SXP-130] SXP does not cleanup operational DS nodes after removal Created: 24/Oct/17 Updated: 06/Nov/17 |
|
| Status: | Verified |
| Project: | sxp |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Medium |
| Reporter: | Martin Dindoffer | Assignee: | Martin Dindoffer |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| 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. |
| Comments |
| Comment by Martin Dindoffer [ 06/Nov/17 ] |
|
Nitrogen: https://git.opendaylight.org/gerrit/#/c/64649/ |