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/CONTROLLER-333 controller <p>code:<br/> trans.putOperationalData(this.topologyAugment, ta);<br/> LOG.debug("Peer data {} set to {}", this.topologyAugment, ta);</p> <p>log output:<br/> 2014-04-17 03:11:39.264 PDT <span class="error">&#91;nettyThreadgroupModule$NioEventLoopGroupCloseable-6-4&#93;</span> DEBUG o.o.b.p.t.p.AbstractTopologySessionListener - Peer data InstanceIdentifier [path=[org.opendaylight.yang.gen.v1.urn.tbd.params.xml.ns.yang.network.t<br/> opology.rev131021.NetworkTopology, org.opendaylight.yang.gen.v1.urn.tbd.params.xml.ns.yang.network.topology.rev131021.network.topology.Topology[key=TopologyKey [_topologyId=Uri <span class="error">&#91;_value=pcep-topology&#93;</span>]], org.opendaylight.yang.gen.v1.urn.t<br/> bd.params.xml.ns.yang.network.topology.rev131021.network.topology.topology.Node[key=NodeKey [_nodeId=Uri <span class="error">&#91;_value=pcc://39.39.39.39&#93;</span>]], org.opendaylight.yang.gen.v1.urn.opendaylight.params.xml.ns.yang.topology.pcep.rev131024.Node1]] </p> <p>set to </p> <p>.... ero=Ero [_subobject=[Subobject [_loose=false, _subobjectType=IpPrefixCase [_ipPrefix=IpPrefix [_ipPrefix=IpPrefix [_ipv4Pr<br/> efix=Ipv4Prefix <span class="error">&#91;_value=195.20.160.40/32&#93;</span>], augmentation=[]], augmentation=[]], augmentation=[]], Subobject [_loose=false, _subobjectType=IpPrefixCase [_ipPrefix=IpPrefix [_ipPrefix=IpPrefix [_ipv4Prefix=Ipv4Prefix [_value=201.20.160.43/<br/> 32]], augmentation=[]], augmentation=[]], augmentation=[]], Subobject [_loose=false, _subobjectType=IpPrefixCase [_ipPrefix=IpPrefix [_ipPrefix=IpPrefix [_ipv4Prefix=Ipv4Prefix <span class="error">&#91;_value=43.43.43.43/32&#93;</span>], augmentation=[]], augmentation=[]]<br/> , augmentation=[]]], _ignore=false, ....</p> <p>restconf reports only last ero prefix:</p> <p>&lt;ero&gt;<br/> &lt;processing-rule&gt;false&lt;/processing-rule&gt;<br/> &lt;subobject&gt;<br/> &lt;loose&gt;false&lt;/loose&gt;<br/> &lt;ip-prefix&gt;&lt;ip-prefix&gt;43.43.43.43/32&lt;/ip-prefix&gt;&lt;/ip-prefix&gt;<br/> &lt;/subobject&gt;<br/> &lt;ignore&gt;false&lt;/ignore&gt;<br/> &lt;/ero&gt;</p> <p>Operating System: Linux<br/> Platform: PC</p> CONTROLLER-333

Possible overriding list data

Bug Verified Cannot Reproduce Unassigned Dana Kutenicsova Thu, 17 Apr 2014 10:21:37 +0000 Tue, 14 Nov 2017 15:18:01 +0000 Wed, 18 Jun 2014 14:55:41 +0000 Helium restconf 0 5 <p>Update: this behaviour is noticed only using new data-store:</p> <p>2014-04-17 04:43:41.709 PDT <span class="error">&#91;nettyThreadgroupModule$NioEventLoopGroupCloseable-6-2&#93;</span> TRACE o.o.c.m.s.d.s.i.InMemoryDOMDataStore - Data Tree is data {<br/> .... path {<br/> ero {<br/> processing-rule false<br/> subobject {<br/> subobject[] {<br/> loose false<br/> subobject-type {<br/> ip-prefix </p> { ip-prefix 43.43.43.43/32 } <p> }<br/> }.....</p> <p>Hello, this is my first bugzilla comment ever.<br/> <a href="https://jira.opendaylight.org/browse/CONTROLLER-333" title="Possible overriding list data" class="issue-link" data-issue-key="CONTROLLER-333"><del>CONTROLLER-333</del></a> was possibly not fixed enough, at least for Restconf RPC with JSON data.<br/> Adding piece of e-mail communication:</p> <p>From: Dana Kutenicsova -X (dkutenic - Pantheon Technologies SRO at Cisco) <br/> Sent: Friday, May 30, 2014 5:03 PM<br/> To: Vratko Polak -X (vrpolak - Pantheon Technologies SRO at Cisco); Ladislav Borak -X (lborak - Pantheon Technologies SRO at Cisco); Jozef Gloncak -X (jgloncak - Pantheon Technologies SRO at Cisco); Tony Tkacik -X (ttkacik - Pantheon Technologies SRO at Cisco)<br/> Cc: wave_demo_support(mailer list)<br/> Subject: RE: ERO in JSON</p> <p>Seems related to: <a href="https://bugs.opendaylight.org/show_bug.cgi?id=767" class="external-link" target="_blank" rel="nofollow noopener">https://bugs.opendaylight.org/show_bug.cgi?id=767</a>, except this time it's first ERO, that is visible. Not sure if restconf or data-store issue. <br/> ________________________________________<br/> From: Vratko Polak -X (vrpolak - Pantheon Technologies SRO at Cisco)<br/> Sent: Friday, May 30, 2014 4:51 PM<br/> To: Dana Kutenicsova -X (dkutenic - Pantheon Technologies SRO at Cisco)<br/> Cc: wave_demo_support(mailer list)<br/> Subject: ERO in JSON<br/> Hi.<br/> I have tried creating curl command using JSON data<br/> that would create tunnel with explicit path.<br/> This is XML data version which works ok:<br/> curl -X POST -H "Content-Type:application/yang.data+xml" -d '&lt;input&gt;&lt;node&gt;pcc://39.39.39.39&lt;/node&gt;&lt;name&gt;odveci&lt;/name&gt;&lt;network-topology-ref xmlns:topo="urn:TBD:params:xml:ns:yang:network-topology"&gt;/topo:network-topology/topo:topology<span class="error">&#91;topo:topology-id=&quot;pcep-topology&quot;&#93;</span>&lt;/network-topology-ref&gt;&lt;arguments&gt;&lt;endpoints-obj&gt;&lt;ipv4&gt;&lt;source-ipv4-address&gt;39.39.39.39&lt;/source-ipv4-address&gt;&lt;destination-ipv4-address&gt;43.43.43.43&lt;/destination-ipv4-address&gt;&lt;/ipv4&gt;&lt;/endpoints-obj&gt;&lt;ero&gt;&lt;subobject&gt;&lt;loose&gt;false&lt;/loose&gt;&lt;ip-prefix&gt;&lt;ip-prefix&gt;195.20.160.40/32&lt;/ip-prefix&gt;&lt;/ip-prefix&gt;&lt;/subobject&gt;&lt;subobject&gt;&lt;loose&gt;false&lt;/loose&gt;&lt;ip-prefix&gt;&lt;ip-prefix&gt;201.20.160.43/32&lt;/ip-prefix&gt;&lt;/ip-prefix&gt;&lt;/subobject&gt;&lt;subobject&gt;&lt;loose&gt;false&lt;/loose&gt;&lt;ip-prefix&gt;&lt;ip-prefix&gt;43.43.43.43/32&lt;/ip-prefix&gt;&lt;/ip-prefix&gt;&lt;/subobject&gt;&lt;/ero&gt;&lt;/arguments&gt;&lt;/input&gt;' 127.0.0.1:8080/restconf/operations/network-topology-pcep:add-lsp<br/> and this is JSON version which almost works:<br/> curl -X POST -H "Content-Type:application/yang.data+json" -d '{"input":{"node":"pcc://39.39.39.39","name":"odveci","network-topology-ref":"/network-topology:network-topology/network-topology:topology<span class="error">&#91;network-topology:topology-id=\&quot;pcep-topology\&quot;&#93;</span>","arguments":{"endpoints-obj":{"ipv4":{"source-ipv4-address":"39.39.39.39","destination-ipv4-address":"43.43.43.43"}},"ero":[{"subobject":{"loose":false,"ip-prefix":</p> {"ip-prefix":"195.20.160.40/32"} <p>}},{"subobject":{"loose":false,"ip-prefix":</p> {"ip-prefix":"201.20.160.43/32"} <p>}},{"subobject":{"loose":false,"ip-prefix":</p> {"ip-prefix":"43.43.43.43/32"} <p>}}]}}}' 127.0.0.1:8080/restconf/operations/network-topology-pcep:add-lsp<br/> but in this case created tunnel only has<br/> one of 3 hops, the first one to 195.20.160.40.<br/> Is this a known issue?</p> <p>Seems to Restconf / Yangtools error, not datastore related.</p> <p>I tried to do test case with list without keys but for me everything worked OK. I passed through YANG model and in pcep-types.yang I found that grouping explicit-route-object contains<br/> container ero {<br/> ...omitted....<br/> list subobject </p> { ...omitted... } <p> ...omitted...<br/> }</p> <p>You constructed your CURL for JSON as <br/> "ero": [<br/> {<br/> "subobject": </p> { ...omitted... }<br/> },<br/> {<br/> "subobject": { ...omitted... } <p> },<br/> {<br/> "subobject": </p> { ...omitted... }<br/> }<br/> ]<br/> <br/> but it should be:<br/> "ero": {<br/> "subobject":[{ ...omitted... } <p> },<br/> {<br/> "subobject": </p> { ...omitted... }<br/> },<br/> {<br/> "subobject": { ...omitted... } <p> }<br/> ]</p> <p>sorry,<br/> I submitted previous comment by mistake and I couldn't find way how to edit it so I pasted correct syntax for JSON once again</p> <p>"ero": {<br/> "subobject":[<br/> </p> { ...omitted... },<br/> { ...omitted... } <p>,</p> { ...omitted... } <p> ]</p> <p>I am going to try simulate this case.</p> <p>I can confirm that I successfully reproduced bug on YANG model<br/> container cont {<br/> container cont1 {<br/> list lst {<br/> leaf lf1 </p> { type string; } <p> }<br/> }<br/> }</p> <p>where I constructed incorrect JSON input like <br/> {<br/> "cont":{<br/> "cont1":[<br/> {<br/> "lst":</p> { "lf1":"dummy lfA" } <p> },<br/> {<br/> "lst":</p> { "lf1":"dummy lfA" } <p> }<br/> ]<br/> }<br/> }</p> <p>So conclusion is that YANG element has to be mapped to JSON:</p> <ul class="alternate" type="square"> <li>container -&gt; "container_name":{}</li> <li>list -&gt; "list_name":<span class="error">&#91;{},{},...{}&#93;</span></li> </ul> <p>and not vice versa.</p> <p>Please retest.</p> <p>After changing JSON data to correct ones, update-lsp works without issues.</p> Development External issue ID 767 External issue URL Priority Rank 0|i02jr3: