[YANGTOOLS-811] yang parser problem with refine or augment of yang node, which is not supported per feature statement Created: 13/Sep/17  Updated: 10/Apr/22  Resolved: 14/Sep/17

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

Type: Bug
Reporter: Mirko Deckert 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

Attachments: Zip Archive test_model.zip    
External issue ID: 9156

 Description   

With the attached minimized two yang modules the following error message is printed:

my-model-1:
[main] WARN org.opendaylight.yangtools.yang.parser.stmt.reactor.BuildGlobalContext - Unexpected error processing source RevisionSourceIdentifier [name=my-model-1@1970-01-01]. Please file an issue with this model attached.
java.lang.IllegalArgumentException: Refine target node Relative

{path=[(my-model-1-ns?revision=1970-01-01)my-grouping-container]}

not found. At null:16:6

my-model-2:
[main] ERROR org.opendaylight.yangtools.yang.parser.stmt.reactor.BuildGlobalContext - Failed to parse YANG from source SourceSpecificContext [source=null, current=EFFECTIVE_MODEL, finished=FULL_DECLARATION]: Augment target 'Relative

{path=[(my-model-2-ns?revision=1970-01-01)my-container, (my-model-2-ns?revision=1970-01-01)my-grouping-container]}

' not found [at null:18:2]

The full stacktraces are available inside the attachment.

Tested with released version 1.0.4-Boron-SR4.

 Comments   
Comment by Mirko Deckert [ 13/Sep/17 ]

Attachment test_model.zip has been added with description: minimized yang modules and stacktraces

Comment by Peter Kajsa [ 14/Sep/17 ]

I believe yang parser behavior is correct in both attached cases, because the augment and the refine should also be marked with the same "if-feature my-feature;". Otherwise the yang models are not consistent. Therefore I am closing this bug as invalid.

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