[NETCONF-314] Reject messages with missing attributes with correct rpc-error reply Created: 14/Nov/16  Updated: 15/Mar/19  Resolved: 29/Nov/16

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

Type: Bug
Reporter: Jakub Morvay Assignee: Jakub Morvay
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: 7172

 Description   

Netconf server rejects messages with missing attributes with incorrect rpc error information.

rpc-error generated in such events are described in https://tools.ietf.org/html/rfc6241#section-4.3 and https://tools.ietf.org/html/rfc6241#appendix-A

 Comments   
Comment by Jakub Morvay [ 14/Nov/16 ]

According to RFC, rpc-error generated when we are processing rpc-message that is missing some attributes should look like this:

<rpc-error>
<error-type>rpc</error-type>
<error-tag>missing-attribute</error-tag>
<error-severity>error</error-severity>
<error-info>
<bad-attribute>message-id</bad-attribute>
<bad-element>rpc</bad-element>
</error-info>
</rpc-error>

Example of rpc-error, when rpc element's message-id attribute is missing.

In this particular case ODL generates rpc-error with following error-info.

<error-info>
<MISSING_ATTRIBUTE>message-id</MISSING_ATTRIBUTE>
</error-info>

Comment by Jakub Morvay [ 14/Nov/16 ]

https://git.opendaylight.org/gerrit/48320

Comment by Jakub Morvay [ 29/Nov/16 ]

Boron:
https://git.opendaylight.org/gerrit/#/c/48785/

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