[NETCONF-645] Netconf client fails to detect error reply Created: 24/Oct/19 Updated: 02/Jul/21 Resolved: 02/Jul/21 |
|
| Status: | Resolved |
| Project: | netconf |
| Component/s: | netconf |
| Affects Version/s: | None |
| Fix Version/s: | Aluminium, Magnesium SR2, Sodium SR4 |
| Type: | Bug | Priority: | High |
| Reporter: | Andrej Mak | Assignee: | Kowsalya Saravanan |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Description |
|
org.opendaylight.netconf.util.messages.NetconfMessageUtil#isErrorMessage(org.opendaylight.netconf.api.xml.XmlElement) Method returns false if rpc-reply contains multiple error elements. Netconf rfc permits multiple error elements. https://tools.ietf.org/html/rfc6241#section-4.3 Because of this bug, netconf rpc service doesn't return parsed rpc-error list from reply, but fails with IllegalArgumentException when it tries to parse reply. Api user must parse exception message to get error list. |
| Comments |
| Comment by Jamo Luhrsen [ 28/May/20 ] |
|
normally I would duplicate the newer bug to the first reported bug, but since there is more details in |
| Comment by Manoj Chokka [ 02/Jul/21 ] |
|
fixed in https://jira.opendaylight.org/browse/NETCONF-666 fix at https://git.opendaylight.org/gerrit/c/netconf/+/89859 hence closing the ticket. |