[NETCONF-91] ODL assumes netconf interleave capability Created: 27/Oct/15 Updated: 10/May/22 |
|
| Status: | Confirmed |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Wojciech Dec | 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: | 4532 | ||||||||
| Description |
|
The ODL Netconf client isn't checking for "interleave" (RFC 5277) capability being in the server offered capabilities, and assumes it to be there. This causes failures when ODL sends RPCs and Notification requests on the same session (the server device rejects these). Issue observed in Lithium SR2. |
| Comments |
| Comment by wang senxiao [ 11/Nov/16 ] |
|
(In reply to Wojciech Dec from comment #0) Hi Wojciech, |
| Comment by Wojciech Dec [ 11/Nov/16 ] |
|
Last tried with Be, where it still wasn't fixed. However a quick search of the latest netconf master shows no relevant hits for the "interleave" keyword, so it does not appear to be solved. To be specific: urn:ietf:params:netconf:capability:interleave:1.0 capability, |