[YANGTOOLS-677] ietf-ipv4-unicast-routing/ietf-ipv6-unicast-routing bad relative paths Created: 06/Oct/16  Updated: 10/Apr/22  Resolved: 28/Feb/18

Status: Resolved
Project: yangtools
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Jan Srnicek 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
Platform: All


External issue ID: 6881

 Description   

Model

http://dld.netconfcentral.org/src/ietf-ipv4-unicast-routing@2014-05-24.yang

Errors

Line 166-167 - Provided relative path is wrong, can't be found in ietf-routing.yang

Line 200-201 - Same as above

Model

http://dld.netconfcentral.org/src/ietf-ipv6-unicast-routing@2014-05-25.yang

Line 567-568 - Same as above

Line 601-602 - Same as above

Works while providing absolute paths like this

path "/rt:routing-state/rt:routing-instance/rt:interfaces/"
+ "rt:interface/rt:name";

And there is probably no need to define this leaf explicitly, because grouping outgoing-interface in ietf-routing.yang seems to be identical.



 Comments   
Comment by Vratko Polak [ 13/Oct/16 ]

This seems similar to a more specific case reported in https://bugs.opendaylight.org/show_bug.cgi?id=6141

Comment by Robert Varga [ 28/Feb/18 ]

RFC8020's ietf-ipv4-unicast-routing@2016-11-04.yang seems to be working just fine with Oxygen. Feel free to reopen if this issue persists.

Generated at Wed Feb 07 20:53:58 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.