<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:21:37 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>[NETVIRT-463] L2GW Connection Utils does not see connected HWVTEP device</title>
                <link>https://jira.opendaylight.org/browse/NETVIRT-463</link>
                <project id="10144" key="NETVIRT">netvirt</project>
                    <description>&lt;p&gt;I have a HWVTEP emulator connected to ODL. When the HWVTEP manager is set to point to the ODL Controller, both controller and HWVTEP see the node as &quot;connected&quot;. Configuring L2GW and L2GW connections works, as long as the set-manager config is performed on the HWVTEP AFTER ODL is up and running.&lt;/p&gt;

&lt;p&gt;In this same setup, if I unstack/stack (using devstack), and leave the HWVTEP manager config in place, the connection between the HWVTEP and OVSDB on the control node stays connected (via vtep-ctl show, and dumping MDSAL OVSDB connection info for hwvtep dev).&lt;/p&gt;

&lt;p&gt;Now, if I configure a L2GW and L2GW connection, the config will not be pushed from the ODL control node to the HWVTEP device. Debugging in the logs shows that L2GW Connection utils doesn&apos;t see that the HWVTEP device is connected, even though the HWVTEP DB shows connected, and OVSDB SB MDSAL shows connected. &lt;/p&gt;

&lt;p&gt;I don&apos;t have the log handy at the moment, will add it to this bug next time I see it.&lt;/p&gt;

&lt;p&gt;Suneelu has observed the same behavior. The thinking is that there is possibly some timing issue between OVSDB Connection manager and OVSDB clients. &lt;/p&gt;

&lt;p&gt;The workaround for this bug, is to del-manager on HWVTEP device, wait about 30-45 secs, then do a set-manager on HWVTEP device. At this point, L2GW and L2GW Connection config will be sent from ODL to HWVTEP device.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="20384">NETVIRT-463</key>
            <summary>L2GW Connection Utils does not see connected HWVTEP device</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="-1">Unassigned</assignee>
                                    <reporter username="vpickard@redhat.com">Victor Pickard</reporter>
                        <labels>
                    </labels>
                <created>Mon, 6 Feb 2017 18:41:00 +0000</created>
                <updated>Thu, 19 Oct 2017 21:28:09 +0000</updated>
                            <resolved>Tue, 4 Apr 2017 12:46:38 +0000</resolved>
                                    <version>Boron</version>
                                                    <component>General</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="37189" author="shague@redhat.com" created="Mon, 3 Apr 2017 20:42:59 +0000"  >&lt;p&gt;vic, Suneelu, is this still an issue?&lt;/p&gt;</comment>
                            <comment id="37190" author="k.v.suneelu.verma@ericsson.com" created="Tue, 4 Apr 2017 06:06:40 +0000"  >&lt;p&gt;This should be fixed after the patch.&lt;br/&gt;
&lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/53337/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/53337/&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="37191" author="vpickard@redhat.com" created="Tue, 4 Apr 2017 12:46:38 +0000"  >&lt;p&gt;(In reply to Sam Hague from comment #1)&lt;br/&gt;
&amp;gt; vic, Suneelu, is this still an issue?&lt;/p&gt;

&lt;p&gt;I have been testing with patch &lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/53555&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/53555&lt;/a&gt;, and I no longer see this issue.&lt;/p&gt;

&lt;p&gt;What I saw during my testing (without above patch) is that multiple updates would arrive from hwvtep device, resulting in callback(s) with multiple updates.&lt;br/&gt;
During processing of the updates, an unhandled exception would occur (NPE), and any other updates would not be processed (Physical_Switch update, in case of connection update, resulting in L2GW cache not being updated).&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10002">
                    <name>Duplicate</name>
                                            <outwardlinks description="duplicates">
                                        <issuelink>
            <issuekey id="20395">NETVIRT-474</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>7744</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=7744]]></customfieldvalue>

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

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