[YANGTOOLS-643] augmenting unknown statement results in error Created: 02/Aug/16  Updated: 10/Apr/22  Resolved: 23/Oct/16

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

Type: Bug
Reporter: Martin Bobak Assignee: Peter Kajsa
Resolution: Done 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: 6329

 Description   

augmenting :

augment "disconnect/input" {
leaf no-remote

{ type empty; description "Do not perform this action on remote cluster node"; }

}

defined as :

grouping disconnect-grouping {
ns:action disconnect

{ description "Close all sessions to all devices."; }

}

results into error :

Error 1: Augment target 'Relative

{path=[(http://some/ns?revision=2016-01-01)disconnect, (http://some/ns?revision=2016-01-01)input]}

' not found [at null:1245:6]

 Comments   
Comment by Peter Kajsa [ 26/Sep/16 ]

Please, try to test with using this patch
https://git.opendaylight.org/gerrit/#/c/46118/

Comment by Robert Varga [ 27/Sep/16 ]

I think the model is buggy, as the original definition does not include 'input'. If the modeling intent is to allow augmentation, the disconnect action should include an empty input statement.

Comment by Peter Kajsa [ 28/Sep/16 ]

Yes, the example from Martin is buggy, because there are omitted some relevant nodes and parts from original yang model.

Correct example of this issue should be:

grouping my-grouping {
ext:my-extension my-extension-name {
description
"Extension.";
input {
leaf my-leaf

{ type string; description "my-leaf in extension body."; }

}
}
}

container my-container {
uses my-grouping {
augment "my-extension-name/input" {
leaf-list my-leaf-list

{ type string; }

}
}
}

This issue is well known, so proposed fix solves of course this correct example.

Comment by Robert Varga [ 23/Oct/16 ]

boron: https://git.opendaylight.org/gerrit/47404

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