[NETCONF-132] Incorrect error response after user sends invalid data Created: 26/Jan/16  Updated: 15/Mar/19  Resolved: 12/Feb/16

Status: Resolved
Project: netconf
Component/s: netconf
Affects Version/s: None
Fix Version/s: None

Type: Bug
Reporter: Jozef Behran Assignee: Andrej Mak
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 5095

 Description   

When the user sends invalid data to controller configuration via Netconf MDSAL Northbound, the returned error response is (the "message-id" attribute can vary and the number at the end of the <error-message> element can vary as well):

<?xml version="1.0" encoding="UTF-8" standalone="no"?> <rpc-reply message-id="71" xmlns="urn:ietf:params:xml:ns:netconf:base:1.0"> <rpc-error> <error-type>application</error-type> <error-tag>operation-failed</error-tag> <error-severity>error</error-severity> <error-message>Transaction commit failed on canCommit encountered an unexpected failure 3</error-message> </rpc-error> </rpc-reply>

It is not clear from the error message that the problem here is invalid data. Actually, the error message suggests that the ODL suffered some scary internal error.

 Comments   
Comment by Jozef Behran [ 26/Jan/16 ]

... and it turns out that indeed ODL suffered an internal error as described by NETCONF-133.

Comment by Vratko Polak [ 26/Jan/16 ]

So is this just a duplicate of NETCONF-133 or are you requesting the Netconf system to be more robust also against different unexpected errors in future?

Comment by Andrej Mak [ 04/Feb/16 ]

https://git.opendaylight.org/gerrit/#/c/34089/

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