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-511 netconf <p>The new 8040 code returns bogus errors when trying to create data resources which already exist via post.</p> <p>Instead of returning 409 (same as the old code) or another appropriate 4xx code for a conflict it returns 503 - server failed. This is broken, there is no server failure, the server did its job and determined that a conflict is in place. It should neither pollute the logs nor return bogus error codes to the client.</p> <p> </p> <p>Tested with json rpc but shows with other data too too.</p> NETCONF-511

Incorrect Error mappings in 8040 code

Bug High Resolved Done Anton Ivanov Anton Ivanov Fri, 23 Feb 2018 16:47:07 +0000 Wed, 16 Jan 2019 12:44:48 +0000 Wed, 16 Jan 2019 12:44:48 +0000 Oxygen Fluorine Neon Fluorine SR1 Neon Fluorine SR2 restconf-nb 0 5 <p>Can you provide the full error response? Also any error logged in the karaf.log? I don't see anywhere in the 8040 code where it would throw a RestconfDocumentedException with RestconfError.RESOURCE_DENIED_TRANSPORT which maps to 503 so I suspect the 503 (Service Unavailable) was returned from higher up - perhaps restconf throw an ISE or some other unchecked ex from somewhere. </p> <p>Looking at TransactionUtil.checkItemDoesNotExists which is called by PostDataTransactionUtil, it does throw a RestconfDocumentedException with RestconfError.DATA_EXISTS which maps to 409 so it should work as expected..</p> <p><a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=aivanov" class="user-hover" rel="aivanov">aivanov</a> can you provide the input Tom asked for, please?</p> <p>I unicasted it back at the time. In fact, it needs a retest - Tom and Ryan were working on a fix and it may have been merged along with other patches.</p> <p> </p> <p><a href="https://jira.opendaylight.org/secure/ViewProfile.jspa?name=aivanov" class="user-hover" rel="aivanov">aivanov</a> do you have some spare cycles to retest this and confirm if it is still present?</p> <p>Quick check revealed this was still present, cause was that the status code from RestconfDocumentedException was not forwarded to the WebApplicationException</p> Development Rank 0|i03apz: