[YANGTOOLS-890] XML parsing issue for XML configuration via netconf/restconf in MPLS model Created: 04/Jul/18  Updated: 31/Jul/18  Resolved: 13/Jul/18

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

Type: Bug Priority: Medium
Reporter: Michal Cmarada Assignee: Michal Cmarada
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: Text File hc.log     Text File netconf-get-config-after-restconf-json-configuration.txt     Text File netconf-message.txt     Text File netconf-response.txt     Text File restconf-json.txt     Text File restconf-xml-response.txt     Text File restconf-xml.txt    

 Description   

When I tried to configure MPLS using netconf(netconf-message.txt) or restconf(restconf-xml.txt) in XML format I am getting error responses( netconf-response.txt or restconf-xml-response.txt)

If I configure the same using restconf with json (restconf-json.txt) it works. Seems there is a problem only when XML format is parsed. When configured using restcon+json I am able to read back the configuration with both restconf or netconf(netconf-get-config-after-restconf-json-configuration.txt).

I compared the netconf output of get-config after writing the json data using restconf with data that I was trying to write using netconf and they look the same. the issue seems to be happening only when the data are written using edit-config in netconf.

I suspect that the issue is with outgoing-labels which is also a container and a list in ietf-mpls-static model (https://gerrit.fd.io/r/gitweb?p=hc2vpp.git;a=blob;f=mpls/api/src/main/yang/hc2vpp-ietf-mpls-static@2017-07-02.yang;h=9da4bb942f040d57ffffacd2ced930105e6a2e29;hb=refs/heads/master#l185)

When I try to configure it without outgoing-labels everything works. Probably there are naming conflicts when the same name is used for list and container that encapsulates the list.

I am attaching honeycomb log file (hc.log) with stack trace.


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