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/NETCONF-645 netconf <p>org.opendaylight.netconf.util.messages.NetconfMessageUtil#isErrorMessage(org.opendaylight.netconf.api.xml.XmlElement)</p> <p>Method returns false if rpc-reply contains multiple error elements.</p> <p>Netconf rfc permits multiple error elements.</p> <p><a href="https://tools.ietf.org/html/rfc6241#section-4.3" class="external-link" target="_blank" rel="nofollow noopener">https://tools.ietf.org/html/rfc6241#section-4.3</a></p> <p>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.</p> NETCONF-645

Netconf client fails to detect error reply

Bug High Resolved Done Kowsalya Saravanan Andrej Mak Thu, 24 Oct 2019 07:38:53 +0000 Fri, 2 Jul 2021 04:47:58 +0000 Fri, 2 Jul 2021 04:47:58 +0000 Aluminium Magnesium SR2 Sodium SR4 netconf 0 2 <p>normally I would duplicate the newer bug to the first reported bug, but since there is more details in <a href="https://jira.opendaylight.org/browse/NETCONF-666" title="500 response without provided rpc failure details" class="issue-link" data-issue-key="NETCONF-666"><del>NETCONF-666</del></a> I'll do it the reverse way</p> <p>fixed in <a href="https://jira.opendaylight.org/browse/NETCONF-666" class="external-link" rel="nofollow">https://jira.opendaylight.org/browse/NETCONF-666</a></p> <p>fix at <a href="https://git.opendaylight.org/gerrit/c/netconf/+/89859" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/c/netconf/+/89859</a></p> <p>hence closing the ticket.</p> Duplicate NETCONF-666 Development Rank 0|i03pk7: