[NETCONF-219] ONE or BASE scoped notification websockets produce 1 notification per ODL reinstall Created: 10/Jun/16 Updated: 15/Mar/19 Resolved: 10/Jun/16 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Jozef Behran | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Attachments: |
|
| External issue ID: | 6046 |
| Description |
|
1. Extract "bare ODL" and run it. In step 6 post this to create the notification stream: { } In the step 10 another message shall be seen with data from the other car The same happens when you delete the car you just created in step 9. When you stop the websocket listener on that terminal, restart the ODL and If you do the steps in the order 1-4,7,5,6,delete the car created in step 7 The correct behavior is to receive notifications for every "create" and |
| Comments |
| Comment by Jozef Behran [ 10/Jun/16 ] |
|
Attachment karaf.log.xz has been added with description: TRACE logs from the test run described in the description |
| Comment by Jozef Behran [ 10/Jun/16 ] |
|
It turns out that "this is expected behavior" (the container mentioned has only one child item which is the "car-entry" list). The real bug that I had on my mind is YANGTOOLS-622. |