example.zip
[YANGTOOLS-1133] Config list checking still not entirely correct Created: 01/Sep/20 Updated: 21/Sep/20 Resolved: 21/Sep/20 |
|
| Status: | Resolved |
| Project: | yangtools |
| Component/s: | parser |
| Affects Version/s: | 3.0.16 |
| Fix Version/s: | 6.0.0, 4.0.14, 5.0.7 |
| Type: | Bug | Priority: | Medium |
| Reporter: | Peter Verthez | Assignee: | Robert Varga |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
YANG parser 3.0.16 |
||
| Attachments: |
example.zip
|
| Description |
|
In But there is still a case where it produces a warning where it shouldn't: when the non-config list is added via an augment. See the attached yang model, this produces the following warning: 2020-09-01 16:50:29,742 INFO [org.broadband_forum.obbaa.netconf.api.parser.YangParserUtilTest.main()] list.AbstractListStatementSupport (AbstractListStatementSupport.java:137) - Configuration list (http://www.example.com/example2)values does not define any keys in violation of RFC7950 section 7.8.2. While this is fine with OpenDaylight, it can cause interoperability issues with other systems [defined at /home/verthezp/tmp/odlwarning/example2.yang:11:4] Since this list is added to a container with config false, the warning should not be there. |
| Comments |
| Comment by Robert Varga [ 21/Sep/20 ] |
|
Right, so this happens for the case of the augment itself, i.e. we need to understand that this is a not a uses-augment. |