[NETCONF-281] Forgotten config DS changes when no clustered topology owner Created: 21/Sep/16 Updated: 13/Aug/19 |
|
| Status: | Confirmed |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Vratko Polak | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Issue Links: |
|
||||||||
| External issue ID: | 6774 | ||||||||
| Description |
|
When there is no Owner for topology-manager entity, changes in config topology-netconf are not processed. When new owner appears, it does not examine state of topology-netconf. That means some user-configured connections are never opened, and some user-deconfigured connections are never torn down. As lack of owner is not visible in Restconf output, current users can never be sure whether their changes will ever be applied. Similar behavior was present in Openflowplugin project for Forwarding Rules Manager (FRM). They created FRS, S meaning Synchronize. For Netconf, I recommend to add synchronization ability directly to odl-netconf-clustered_topology. |
| Comments |
| Comment by Jakub Morvay [ 17/Oct/16 ] |
|
This should be fixed in new refactored clustered netconf topology implementation. Please see |
| Comment by Vratko Polak [ 17/Oct/16 ] |
|
INVALID means the reported issue was a user error and not a real Bug. If this is will be fixed together with another Bug, this should be kept CONFIRMED or perhaps marked as DUPLICATE. |
| Comment by Jakub Morvay [ 17/Oct/16 ] |
|
Sorry, We will have to try to replicate this on new clustered topology to see if the bug is still present.. |