<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:14:15 UTC 2024

It is possible to restrict the fields that are returned in this document by specifying the 'field' parameter in your request.
For example, to request only the issue key and summary append 'field=key&field=summary' to the URL of your request.
-->
<rss version="0.92" >
<channel>
    <title>OpenDaylight JIRA</title>
    <link>https://jira.opendaylight.org</link>
    <description>This file is an XML representation of an issue</description>
    <language>en-us</language>    <build-info>
        <version>8.20.10</version>
        <build-number>820010</build-number>
        <build-date>22-06-2022</build-date>
    </build-info>


<item>
            <title>[NETCONF-132] Incorrect error response after user sends invalid data</title>
                <link>https://jira.opendaylight.org/browse/NETCONF-132</link>
                <project id="10142" key="NETCONF">netconf</project>
                    <description>&lt;p&gt;When the user sends invalid data to controller configuration via Netconf MDSAL Northbound, the returned error response is (the &quot;message-id&quot; attribute can vary and the number at the end of the &amp;lt;error-message&amp;gt; element can vary as well):&lt;/p&gt;

&lt;p&gt;&amp;lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot; standalone=&quot;no&quot;?&amp;gt; &amp;lt;rpc-reply message-id=&quot;71&quot; xmlns=&quot;urn:ietf:params:xml:ns:netconf:base:1.0&quot;&amp;gt; &amp;lt;rpc-error&amp;gt; &amp;lt;error-type&amp;gt;application&amp;lt;/error-type&amp;gt; &amp;lt;error-tag&amp;gt;operation-failed&amp;lt;/error-tag&amp;gt; &amp;lt;error-severity&amp;gt;error&amp;lt;/error-severity&amp;gt; &amp;lt;error-message&amp;gt;Transaction commit failed on canCommit encountered an unexpected failure 3&amp;lt;/error-message&amp;gt; &amp;lt;/rpc-error&amp;gt; &amp;lt;/rpc-reply&amp;gt;&lt;/p&gt;

&lt;p&gt;It is not clear from the error message that the problem here is invalid data. Actually, the error message suggests that the ODL suffered some scary internal error.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="21145">NETCONF-132</key>
            <summary>Incorrect error response after user sends invalid data</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                                <status id="5" iconUrl="https://jira.opendaylight.org/images/icons/statuses/resolved.png" description="A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed.">Resolved</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10000">Done</resolution>
                                        <assignee username="andrej.mak@pantheon.tech">Andrej Mak</assignee>
                                    <reporter username="jbehran@cisco.com">Jozef Behran</reporter>
                        <labels>
                    </labels>
                <created>Tue, 26 Jan 2016 10:03:36 +0000</created>
                <updated>Fri, 15 Mar 2019 22:22:19 +0000</updated>
                            <resolved>Fri, 12 Feb 2016 10:02:27 +0000</resolved>
                                                                    <component>netconf</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                                                                <comments>
                            <comment id="39150" author="jbehran@cisco.com" created="Tue, 26 Jan 2016 10:07:48 +0000"  >&lt;p&gt;... and it turns out that indeed ODL suffered an internal error as described by &lt;a href=&quot;https://jira.opendaylight.org/browse/NETCONF-133&quot; title=&quot;&amp;quot;Transaction ... is no longer running&amp;quot; after user sends invalid data.&quot; class=&quot;issue-link&quot; data-issue-key=&quot;NETCONF-133&quot;&gt;&lt;del&gt;NETCONF-133&lt;/del&gt;&lt;/a&gt;.&lt;/p&gt;</comment>
                            <comment id="39151" author="vrpolak" created="Tue, 26 Jan 2016 16:17:23 +0000"  >&lt;p&gt;So is this just a duplicate of &lt;a href=&quot;https://jira.opendaylight.org/browse/NETCONF-133&quot; title=&quot;&amp;quot;Transaction ... is no longer running&amp;quot; after user sends invalid data.&quot; class=&quot;issue-link&quot; data-issue-key=&quot;NETCONF-133&quot;&gt;&lt;del&gt;NETCONF-133&lt;/del&gt;&lt;/a&gt; or are you requesting the Netconf system to be more robust also against different unexpected errors in future?&lt;/p&gt;</comment>
                            <comment id="39152" author="andrej.mak@pantheon.tech" created="Thu, 4 Feb 2016 15:23:06 +0000"  >&lt;p&gt;&lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/34089/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/34089/&lt;/a&gt;&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                    </attachments>
                <subtasks>
                    </subtasks>
                <customfields>
                                                                            <customfield id="customfield_11400" key="com.atlassian.jira.plugins.jira-development-integration-plugin:devsummary">
                        <customfieldname>Development</customfieldname>
                        <customfieldvalues>
                            
                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10208" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>External issue ID</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>5095</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                <customfield id="customfield_10201" key="com.atlassian.jira.plugin.system.customfieldtypes:url">
                        <customfieldname>External issue URL</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue><![CDATA[https://bugs.opendaylight.org/show_bug.cgi?id=5095]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                                                                                <customfield id="customfield_10204" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>ODL SR Target Milestone</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10329"><![CDATA[Beryllium-RC3]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                    <customfield id="customfield_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i01wnj:</customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                </customfields>
    </item>
</channel>
</rss>