<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:32:25 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>[OPNFLWPLUG-419] When a device is configured to to connect to a controller before the controller is started, the device may not show up in inventory</title>
                <link>https://jira.opendaylight.org/browse/OPNFLWPLUG-419</link>
                <project id="10155" key="OPNFLWPLUG">OpenFlowPlugin</project>
                    <description>&lt;p&gt;This happens because the openflowplugin connects to the device and issues nodeUpdated notification before the InventoryManager is even started. Thus the inventory manager misses those notifications and does not add the node to inventory. &lt;/p&gt;

&lt;p&gt;This has been observed with Helium code and may no longer happen with the rewrite in Lithium. We should however add a test where we have the device pointed to the controller before it is started to ensure that this does not happen anymore.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="27687">OPNFLWPLUG-419</key>
            <summary>When a device is configured to to connect to a controller before the controller is started, the device may not show up in inventory</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="kramesha@cisco.com">Kamal Rameshan</assignee>
                                    <reporter username="moraja@cisco.com">Moiz Raja</reporter>
                        <labels>
                    </labels>
                <created>Mon, 27 Apr 2015 03:28:11 +0000</created>
                <updated>Mon, 27 Sep 2021 09:01:29 +0000</updated>
                            <resolved>Thu, 10 Mar 2016 20:58:34 +0000</resolved>
                                                                    <component>General</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>1</watches>
                                                                                                                <comments>
                            <comment id="56785" author="kramesha@cisco.com" created="Wed, 3 Jun 2015 22:24:38 +0000"  >&lt;p&gt;This was happening in Helium as the clustered datastore was not the default. &lt;br/&gt;
When the clustered datastore was loaded, odl-mdsal-broker gets reloaded there by re-instantiating and rewiring the ofp and other managers.&lt;/p&gt;

&lt;p&gt;In Li, CDS was made the default and hence the odl-mdsal-broker points to odl-mdsal-clustering. OFP and other managers have a dependency on odl-mdsal-broker and hence they are not re-instantiated and re-wired.&lt;/p&gt;

&lt;p&gt;I tested installing odl-openflowplugin-all (He, and not odl-openflowplugin-all-li) and this issue was not seen.&lt;/p&gt;

&lt;p&gt;I can write an integration test, but i am lowering the priority for this one.&lt;/p&gt;</comment>
                            <comment id="56786" author="kramesha@cisco.com" created="Thu, 4 Jun 2015 22:02:17 +0000"  >&lt;p&gt;Had a discussion with Moiz. Seems the problem can arise in Li as well.&lt;/p&gt;

&lt;p&gt;The inventory-manager gets loaded as part of Southbound but is not guaranteed to load after openflowplugin.&lt;/p&gt;

&lt;p&gt;This seems to be a classic producer-consumer issue, where the consumer needs to be updated with the latest state if loaded later than the producer.&lt;/p&gt;

&lt;p&gt;This is true for any client apps which might be dependent on inv notifications and might get loaded (or reloaded) later than OFP.&lt;/p&gt;

&lt;p&gt;Moving this to Be.&lt;/p&gt;</comment>
                            <comment id="56787" author="kramesha@cisco.com" created="Thu, 10 Mar 2016 20:58:34 +0000"  >&lt;p&gt;As part of the Li design, the inventory manager does not exist.&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>3064</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=3064]]></customfieldvalue>

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

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

                        </customfieldvalues>
                    </customfield>
                                                                                                                        <customfield id="customfield_10202" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Priority</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10301"><![CDATA[Normal]]></customfieldvalue>

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

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