<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 19:54:09 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-898] Switches not removed from Operational after clearing mininet topo</title>
                <link>https://jira.opendaylight.org/browse/CONTROLLER-898</link>
                <project id="10113" key="CONTROLLER">controller</project>
                    <description>&lt;p&gt;Steps to reproduce:&lt;/p&gt;

&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;Download integration karaf and install odl-integration-compatible-with-all feature&lt;/li&gt;
	&lt;li&gt;Start mininet tree,6 topology&lt;/li&gt;
	&lt;li&gt;Stop mininet&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;Check Operational:&lt;/p&gt;

&lt;p&gt;GET restconf/operational/opendaylight-inventory:nodes&lt;/p&gt;

&lt;p&gt;See if there is any dummy &quot;switch&quot;&lt;/p&gt;

&lt;p&gt;BR/Luis&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="25452">CONTROLLER-898</key>
            <summary>Switches not removed from Operational after clearing mininet topo</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="-1">Unassigned</assignee>
                                    <reporter username="ecelgp">Luis Gomez</reporter>
                        <labels>
                    </labels>
                <created>Thu, 25 Sep 2014 16:06:00 +0000</created>
                <updated>Thu, 19 Oct 2017 22:33:49 +0000</updated>
                            <resolved>Tue, 5 May 2015 15:17:29 +0000</resolved>
                                    <version>Helium</version>
                                                    <component>adsal</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>5</watches>
                                                                                                                <comments>
                            <comment id="49409" author="colin@colindixon.com" created="Thu, 25 Sep 2014 21:08:24 +0000"  >&lt;p&gt;Setting severity to critical.&lt;/p&gt;</comment>
                            <comment id="49410" author="tony.tkacik@gmail.com" created="Fri, 26 Sep 2014 22:26:11 +0000"  >&lt;p&gt;This requires additional analysis, please provide data which were present for dummy switch, since there were similar bugs for stats manager and inventory which were fixed,&lt;br/&gt;
but quick search on l2switch showed that they are writing data to&lt;br/&gt;
operational store with createParents=true,&lt;br/&gt;
which could introduce dummy node after inventory manager deleted it.&lt;/p&gt;

&lt;p&gt;Without leaving dangling data is hard to reason who is offender be it stats manager,&lt;br/&gt;
inventory manager or l2switch project.&lt;/p&gt;

&lt;p&gt;Moved to other, since this is not MD-SAL bug, but probably bug in one of mentioned applications.&lt;/p&gt;</comment>
                            <comment id="49411" author="ecelgp" created="Fri, 26 Sep 2014 22:30:16 +0000"  >&lt;p&gt;Hi Tony,&lt;/p&gt;

&lt;p&gt;This issue was addressed in this patch:&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/11591/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/11591/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;So we can clos this one. Bad news is the above patch introduced other issue discovering switches that I plan to report in a different bug.&lt;/p&gt;

&lt;p&gt;BR/Luis&lt;/p&gt;</comment>
                            <comment id="49412" author="carolsand@gmail.com" created="Tue, 5 May 2015 15:17:29 +0000"  >&lt;p&gt;This bug is part of the project to Move all ADSAL associated component bugs to ADSAL.&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10002">
                    <name>Duplicate</name>
                                                                <inwardlinks description="is duplicated by">
                                        <issuelink>
            <issuekey id="27567">OPNFLWPLUG-299</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </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>2089</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=2089]]></customfieldvalue>

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

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