[OPNFLWPLUG-233] RESTCONF POST fails with java.lang.IllegalArgumentException (Child is not present in tree) Created: 12/Aug/14  Updated: 27/Sep/21  Resolved: 15/Jun/15

Status: Resolved
Project: OpenFlowPlugin
Component/s: General
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Madhu Venugopal Assignee: Madhu Venugopal
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: Mac OS
Platform: PC


External issue ID: 1526
Priority: High

 Description   

While trying to install a Flow using RESTCONF with the following
POST data : https://gist.github.com/mavenugo/cec685c166ffa695dded
POST URL : http://localhost:8080/restconf/config/opendaylight-inventory:nodes/node/openflow:165173587440207/table/0

Error : https://gist.github.com/e474e0374e6b0e285a11



 Comments   
Comment by Jozef Gloncak [ 12/Aug/14 ]

I think that this problem was solved with patch set
https://git.opendaylight.org/gerrit/#/c/9684/ which was merged on 11AUG2014

I downloaded latest ODL distribution and tried to replicate your problem. Because models openflowplugin-extension-nicira-action and openflowplugin-extension-general are missing in ODL I got error

<errors xmlns="urn:ietf:params:xml:ns:yang:ietf-restconf">
<error>
<error-type>application</error-type>
<error-tag>unknown-element</error-tag>
<error-message>Schema node "nx-reg-load" was not found in module.</error-message>
</error>
</errors>

therefore I deleted subtrees

<nx-reg-load xmlns="urn:opendaylight:openflowplugin:extension:nicira:action">
<dst>
<nx-reg xmlns:nxSB="urn:opendaylight:openflowjava:nx:match">nxSB:nxm-nx-reg0</nx-reg>
<start>0</start>
<end>5</end>
</dst>
<value>55</value>
</nx-reg-load>

and

<extension-list xmlns="urn:opendaylight:openflowplugin:extension:general">
<extension-key xmlns:nxNB="urn:opendaylight:openflowplugin:extension:nicira:match">nxNB:nxm-nx-reg0-key</extension-key>
<extension>
<nxm-nx-reg xmlns="urn:opendaylight:openflowplugin:extension:nicira:match">
<reg xmlns:nxSB="urn:opendaylight:openflowjava:nx:match">nxSB:nxm-nx-reg0</reg>
<value>42</value>
</nxm-nx-reg>
</extension>
</extension-list>

and post finished successfuly.

Please try to with ODL distribution which contains commit
CONTROLLER-547 - problem to post list data (mentioned above)

Comment by Abhijit Kumbhare [ 18/Aug/14 ]

Jozef - can u mark it as fixed?

Comment by Jozef Gloncak [ 19/Aug/14 ]

(In reply to Abhijit Kumbhare from comment #2)
> Jozef - can u mark it as fixed?

I am waiting for response from Madhu. I do not know if his problem still persists or if it was solved by steps which I described.

Comment by Abhijit Kumbhare [ 20/Aug/14 ]

Madhu,

Can you please respond on whether your problem persists or is solved after trying with the steps Jozef provided?

Thanks,
Abhijit

Comment by Abhijit Kumbhare [ 02/Sep/14 ]

Any update Madhu?

Comment by Madhu Venugopal [ 02/Sep/14 ]

Havent got a chance to test it out guys. Will do it today and update this bug.

Comment by Abhijit Kumbhare [ 22/Sep/14 ]

Since Madhu has not had a chance to retest this for some time - assume this is not blocking for Helium September release & hence moving to Helium-1.

Comment by George Zhao [ 19/Jan/15 ]

move out of Helium-2

Comment by Jamo Luhrsen [ 09/Jun/15 ]

I'm not really up to speed on how to use these extensions, but I do know that the same error reported here in the bug originally is no longer there.

there is a malformed-message error though:

{
"errors": {
"error": [

{ "error-type": "protocol", "error-tag": "malformed-message", "error-message": "Error parsing input: Unknown child(ren) node(s) detected, identified by: (urn:opendaylight:flow:inventory)barrier, in: list table" }

]
}
}

I'm connecting with an OVS switch and using the same exact flow as given in this bug.

I do see that the plugin now does have the models for openflowplugin-extension-nicira-action and openflowplugin-extension-general in the code base.

that's all I can provide for now.

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