[NETCONF-92] changes to notifications yang models break external Netconf devices Created: 27/Oct/15 Updated: 15/Mar/19 Resolved: 24/Nov/15 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Giles Heron | Assignee: | Unassigned |
| Resolution: | Duplicate | 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: | 4536 | ||||||||
| Description |
|
the notifications.yang, nc-notifications.yang and ietf-netconf-notifications.yang modules in ODL do import by revision (unlike the standard IETF models). this breaks external NETCONF servers which support these models unless they also support the same revisions of ietf-inet-types.yang and ietf-yang-types.yang as referenced in those ODL models (2010-09-24). Is there a reason for the ODL models to import by revision? The IETF versions don't. |
| Comments |
| Comment by Tomas Cere [ 24/Nov/15 ] |
|
Marking as a duplicate of 4577 since the reason for adding the import by revision has the same reason as the other model |