[NETCONF-121] Asynchronous configuration of connectors through restconf failing due to No transaction found for session Created: 08/Jan/16 Updated: 15/Mar/19 Resolved: 13/Oct/17 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Tomas Cere | Assignee: | Unassigned |
| Resolution: | Won't Do | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 4905 |
| Priority: | Normal |
| Description |
|
When configuring netconf connectors with controller-config loopback connection through restconf asynchronously, the messages sent to the netconf server can interfere with each other. Since a configuration consists of lock-edit-commit-unlock, if mulitple configurations are being sent asynchronously through one session the operations can interfere and 2 commits can be called after each other for example. |
| Comments |
| Comment by Tomas Cere [ 11/Jan/16 ] |
|
Discussed with Tony: this is a limitation of the current mount point implementation. Mountpoints should behave more like transaction chains instead of databrokers. |
| Comment by Tomas Cere [ 13/Oct/17 ] |
|
Only a problem with the old configuration type via config subsystem, datastore can handle this without an issue |