<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 19:54:50 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>[CONTROLLER-1162] wrong xml post response when data already exists</title>
                <link>https://jira.opendaylight.org/browse/CONTROLLER-1162</link>
                <project id="10113" key="CONTROLLER">controller</project>
                    <description>&lt;p&gt;when i post new resource twice (same request) behind mountpoint in json, i get first response: &quot;204 No Content&quot; and second response: &quot;409 Conflict, Data already exists...&quot;&lt;/p&gt;

&lt;p&gt;when i try same in xml i get first response: &quot;204 No Content&quot; and second response: &quot;204 No Content&quot;. it should be &quot;409 Conflict, Data already exists...&quot;&lt;/p&gt;

&lt;p&gt;similar bug was here &lt;a href=&quot;https://bugs.opendaylight.org/show_bug.cgi?id=1002&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://bugs.opendaylight.org/show_bug.cgi?id=1002&lt;/a&gt;&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="25716">CONTROLLER-1162</key>
            <summary>wrong xml post response when data already exists</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="10002">Duplicate</resolution>
                                        <assignee username="vdemcak@cisco.com">Vaclav Demcak</assignee>
                                    <reporter username="amarcine@cisco.com">Andrej Marcinek</reporter>
                        <labels>
                    </labels>
                <created>Wed, 18 Feb 2015 10:20:31 +0000</created>
                <updated>Tue, 25 Jul 2023 08:23:54 +0000</updated>
                            <resolved>Thu, 23 Jul 2015 11:23:35 +0000</resolved>
                                                                    <component>restconf</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>6</watches>
                                                                                                                <comments>
                            <comment id="50161" author="amarcine@cisco.com" created="Wed, 18 Feb 2015 13:12:27 +0000"  >&lt;p&gt;additionally:&lt;br/&gt;
if delete is performed, then restconf does not check if data exists. some check and then error message should be returned if data does not exists&lt;/p&gt;</comment>
                            <comment id="50162" author="vrpolak" created="Wed, 18 Feb 2015 13:21:33 +0000"  >&lt;p&gt;&amp;gt; if delete is performed, then restconf does not check if data exists.&lt;/p&gt;

&lt;p&gt;So should this be re-opened?&lt;br/&gt;
&lt;a href=&quot;https://bugs.opendaylight.org/show_bug.cgi?id=1839&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://bugs.opendaylight.org/show_bug.cgi?id=1839&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="50163" author="giheron@cisco.com" created="Tue, 3 Mar 2015 11:11:14 +0000"  >&lt;p&gt;Note that if the data is modified from the original POST (e.g. change the IP address for a NETCONF node) then both JSON and XML will accept the new POST and give a 204.&lt;/p&gt;

&lt;p&gt;From my reading of the restconf draft that&apos;s incorrect.  They should fail as POST is only supposed to create state, not replace it.&lt;/p&gt;</comment>
                            <comment id="50164" author="ricjhill@gmail.com" created="Thu, 23 Jul 2015 11:23:35 +0000"  >&lt;p&gt;Bug was raised against  Helium RC4 , fix  was post  helium.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10002">
                    <name>Duplicate</name>
                                            <outwardlinks description="duplicates">
                                        <issuelink>
            <issuekey id="25842">CONTROLLER-1288</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <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>2730</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=2730]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10206" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Issue Type</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10300"><![CDATA[Bug]]></customfieldvalue>

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

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

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