https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/YANGTOOLS-851 yangtools <p>The attached files include the YANG models used and the test file I posted to the nrothbound.</p> <p>To re-create, create a dummy project. put the attached files in api/src/main/yang</p> <p>Build the project and POST the json file ( see attached tar.gz) to the northbound</p> <p>curl -v -X PUT -u admin:admin --header "Content-Type:application/json" --data @access-control-list.json <a href="http://127.0.0.1:8181/restconf/config/ietf-access-control-list:access-lists" class="external-link" target="_blank" rel="nofollow noopener">http://127.0.0.1:8181/restconf/config/ietf-access-control-list:access-lists</a></p> <p> Attached error.log (stdout  error returned when I use CURL to post )</p> <p>Attached karaf-logs.tar.gz the server logs from Karaf. I set these to DEBUG and repeated the experiment above.</p> <p>OpenDaylight Nitrogen release version.</p> YANGTOOLS-851

MDSAL rejects valid json file when YANG model has a container that crosses a Choice

Bug High Resolved Cannot Reproduce Unassigned M. Ranganathan Wed, 14 Feb 2018 21:06:11 +0000 Fri, 23 Feb 2018 18:14:47 +0000 Fri, 23 Feb 2018 09:55:21 +0000 codecs 0 4 <p>Can you quote the error (with a stack trace, if possible) and attach logs, please?</p> <p>Attached:</p> <ol> <li>Karaf logs</li> <li>returned error message from the northbound.</li> </ol> <p>Attached updated error logs. ( I had included the wrong yang model in my previous report. Sorry about the confusion. )</p> <p>No problem, thanks. We also need the JSON input.</p> <p>Attached access-control-list.json. Thanks</p> <p>At first glance the JSON looks okay, but this has nothing to do with bindings.</p> <p>Looks like the codecs are doing something bad. More investigation is needed.</p> <p>This actually is not an ODL bug, but a mismatch between ietf-acldns and input data. ietf-acldns adds leaves to the ipv4 case, the data assumes it is added to the ipv4 container.</p> <p>Robert, I'm the person that designed the generation tool.  Can you explain a bit more as to what the mismatch is?  acldns augments the ipv4 and ipv4 containers of the ACL model.  The data seems labeled appropriately and wrapped in "ipv4": { }.  What am I doing wrong?</p> Development Rank 0|i03af3: