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-361 netconf <p>In Carbon, <a href="https://jira.opendaylight.org/browse/YANGTOOLS-663" title="RPC definition should implicitly define input/output" class="issue-link" data-issue-key="YANGTOOLS-663"><del>YANGTOOLS-663</del></a> introduced implicit input and output for Yang RPCs.</p> <p>Previously, Restconf RPC behavior was different between missing and empty elements. Namely, missing input statement required no data, empty input required '{"input":{}}' as data. Also, missing output resulted in no response text, empty output resulted in '{"output":{}}'.</p> <p>The output difference is not relevant to CSIT tests (the text was not checked). But the input difference is relevant, as empty data now fails <span class="error">&#91;0&#93;</span>.</p> <p>This Bug is for Restconf to decide whether empty data is to be accepted, to make calls backward compatible with Boron-SR2.</p> <p>If it is decided that Carbon will keep current backward incompatibility, the error message should be fixed anyway (from 500 to 400 with relevant message).</p> <p><span class="error">&#91;0&#93;</span> <a href="https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-clustering-all-carbon/242/archives/log.html.gz#s1-s8-t2-k2-k4-k7-k1" class="external-link" target="_blank" rel="nofollow noopener">https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-clustering-all-carbon/242/archives/log.html.gz#s1-s8-t2-k2-k4-k7-k1</a></p> <p>Operating System: All<br/> Platform: All</p> NETCONF-361

Document expected behavior with respect to RPC implicit input and output

Bug Resolved Done Unassigned Vratko Polak Tue, 7 Mar 2017 11:31:54 +0000 Fri, 15 Mar 2019 22:22:36 +0000 Tue, 7 Mar 2017 13:41:34 +0000 restconf-nb 0 1 <p>If the current <a href="https://jira.opendaylight.org/browse/YANGTOOLS-663" title="RPC definition should implicitly define input/output" class="issue-link" data-issue-key="YANGTOOLS-663"><del>YANGTOOLS-663</del></a> fix is backported to Boron-SR3, similar decision will be needed for compatibility between Boron-SR2 and Boron-SR3.</p> <p>Turns out the compatibility patches were already prepared, just not merged right away.</p> <p>Currently Carbon should be fixed (not verified): <a href="https://git.opendaylight.org/gerrit/52882" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/52882</a><br/> Boron will be fixed soon (but it is not even broken right now): <a href="https://git.opendaylight.org/gerrit/52936" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/52936</a></p> Development External issue ID 7914 External issue URL Issue Type Rank 0|i01y2f: