[#TOPOPROCES-19] Overlay topology present in datastore even after deletion request is made

[TOPOPROCES-19] Overlay topology present in datastore even after deletion request is made Created: 27/May/15 Updated: 19/Oct/17 Resolved: 03/Jul/15
Status:	Resolved
Project:	topoprocessing
Component/s:	General
Affects Version/s:	unspecified
Fix Version/s:	None

Type:

Bug

Reporter:

Michal Polkorab

Assignee:

Unassigned

Resolution:

Done

Votes:

Labels:

None

Remaining Estimate:

Not Specified

Time Spent:

Not Specified

Original Estimate:

Not Specified

Environment:

Operating System: All
Platform: All

External issue ID:

3391

Description

When Delete overlay topology request is made, topoprocessing resources are closed. But data that the framework produced are still present in operational datastore.

These data should be removed after an deletion request

Comments

Comment by Michal Polkorab [ 02/Jun/15 ]

Change pushed here: https://git.opendaylight.org/gerrit/#/c/21217/

Comment by Michal Polkorab [ 03/Jul/15 ]

one small update here: https://git.opendaylight.org/gerrit/#/c/23727/
In some cases main thread shuts down transactionChain before delete overlay topology transaction is submitted.

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

[TOPOPROCES-19] Overlay topology present in datastore even after deletion request is made Created: 27/May/15 Updated: 19/Oct/17 Resolved: 03/Jul/15