[NETCONF-54] Websockets: Scope ONE doesn't work correctly Created: 03/Jul/15 Updated: 15/Mar/19 Due: 28/Jan/16 Resolved: 22/Feb/16 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | restconf-nb |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Jan Hajnar | Assignee: | Martin Ciglan |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 3934 |
| Description |
|
Scope variable for data change listener is directly passed from notification subscription Rpc to data store listener. This causes unexpected behavior when registering notifications for scope 'ONE'. For example if we listen on "nodes" container with scope 'ONE' expected behavior would be to get change events for individual nodes but we get nothing. This is because on yang data tree level, scope ONE would listen on "nodes" container and mixin MapNode "node" underneath it. Since this node is not representable in restconf we wont't get any notifications. |
| Comments |
| Comment by Robert Varga [ 13/Nov/15 ] |
|
Move to NETCONF project |
| Comment by Martin Ciglan [ 04/Jan/16 ] |
|
work starting this week... |
| Comment by Ryan Goulding [ 26/Jan/16 ] |
|
Is there a plan to cherry-pick this back to stable/lithium? |
| Comment by Martin Ciglan [ 27/Jan/16 ] |
|
fix pushed: |
| Comment by Martin Ciglan [ 27/Jan/16 ] |
|
cherry-pick to stable/beryllium: |
| Comment by Martin Ciglan [ 01/Feb/16 ] |
|
fix for vcmts: |
| Comment by Martin Ciglan [ 22/Feb/16 ] |
|
port for stable/lithium: |