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-1197 controller <p><a href="https://wiki.opendaylight.org/view/BGP_LS_PCEP:Programmer_Guide#Creating_LSP_2" class="external-link" target="_blank" rel="nofollow noopener">https://wiki.opendaylight.org/view/BGP_LS_PCEP:Programmer_Guide#Creating_LSP_2</a><br/> specifies the new way of add-lsp using XML input, the change from Helium is that<br/> top-level &lt;input&gt; needs to have namespace specified explicitly (required in Lithium).</p> <p>This format looks like it should also work on Helium, but it leads to an error on sub-element "lsp":<br/> &lt;?xml version="1.0" encoding="UTF-8" standalone="no"?&gt;<br/> &lt;errors xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf"&gt;<br/> &lt;error&gt;<br/> &lt;error-type&gt;application&lt;/error-type&gt;<br/> &lt;error-tag&gt;unknown-element&lt;/error-tag&gt;<br/> &lt;error-message&gt;Schema node "lsp" was not found in module.&lt;/error-message&gt;<br/> &lt;/error&gt;<br/> &lt;/errors&gt;</p> <p>Analogous error is present also in master branch, but Helium-SR3 has deadline sooner.</p> <p>Operating System: All<br/> Platform: All</p> CONTROLLER-1197

Restconf RPC: XML sub-element namespace error when top-level namespace is specified

Bug Resolved Cannot Reproduce Unassigned Vratko Polak Thu, 12 Mar 2015 19:21:49 +0000 Thu, 19 Oct 2017 21:26:35 +0000 Thu, 14 May 2015 14:29:04 +0000 Helium restconf 0 2 <p>Is the lsp element augmented to the input or it is from pcep model?</p> <p>(In reply to Tony Tkacik from comment #1)<br/> &gt; Is the lsp element augmented to the input or it is from pcep model?</p> <p>Augmented. Here are top-level and sub-level elements used:</p> <p>Original Helium guide (works correctly):<br/> &lt;input&gt;<br/> &lt;arguments&gt;<br/> &lt;lsp xmlns:stateful="urn:opendaylight:params:xml:ns:yang:pcep:ietf:stateful"&gt;</p> <p>Current Lithium guide (this bug):<br/> &lt;input xmlns="urn:opendaylight:params:xml:ns:yang:topology:pcep"&gt;<br/> &lt;arguments&gt;<br/> &lt;lsp xmlns:stateful="urn:opendaylight:params:xml:ns:yang:pcep:ietf:stateful"&gt;</p> <p>And todays news: it works again when :stateful after xmlns is removed (future Lithium guide I guess):<br/> &lt;input xmlns="urn:opendaylight:params:xml:ns:yang:topology:pcep"&gt;<br/> &lt;arguments&gt;<br/> &lt;lsp xmlns="urn:opendaylight:params:xml:ns:yang:pcep:ietf:stateful"&gt;</p> <p>Strange thing is that there is also another sub-element (same level as arguments) which does not have problem with namespace alias:<br/> &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;</p> <p>As the "future Lithium guide" way works also for master branch builds, I am decreasing importance to Minor.</p> <p>Namespace aliasing is not problem:</p> <p>&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;</p> <p>network-topology-ref is from default namespace of parent - urn:opendaylight:params:xml:ns:yang:topology:pcep</p> <p>xmlns:topo="urn:TBD:params:xml:ns:yang:network-topology" is only used in instance identifier and not on XML Elements.</p> <p>So, the bug was in the previous guide,<br/> &lt;lsp xmlns:stateful="urn:opendaylight:params:xml:ns:yang:pcep:ietf:stateful"&gt;<br/> defined namespace alias, but it did not tell restconf that "lsp" is not in namespace "urn:opendaylight:params:xml:ns:yang:topology:pcep", right?</p> <p>Seems so</p> Development External issue ID 2833 External issue URL Issue Type ODL SR Target Milestone Rank 0|i02p33: