[NETCONF-109] NETCONF fails to ignore modules with incorrect submodule dates and gets stuck "connecting" Created: 10/Dec/15 Updated: 15/Mar/19 |
|
| Status: | Confirmed |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Giles Heron | Assignee: | Giles Heron |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| Attachments: |
|
| External issue ID: | 4754 |
| Description |
|
we have a case where a NETCONF Server erroneously reports a different revision date for submodules than for modules. The submodules are actually correct - and have the same revision date as the modules - but get-schema reports the date of the previous revision. I would expect ODL to fail to mount any such modules, but to continue mounting other modules and for the NETCONF server to reach the "connected" state. Logs attached. |
| Comments |
| Comment by Giles Heron [ 10/Dec/15 ] |
|
Attachment karaf.zip has been added with description: zipped karaf.log |
| Comment by Robert Varga [ 27/Aug/18 ] |
|
giheron@cisco.com is this still reproducible? |