<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:36:17 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>[OVSDB-399] ODL does not reconcile pre-created OVS ports</title>
                <link>https://jira.opendaylight.org/browse/OVSDB-399</link>
                <project id="10158" key="OVSDB">ovsdb</project>
                    <description>&lt;p&gt;When connecting OVS to ODL - if ports already exist that ODL would want to create, it will fail to reconcile and result in errors.  This was seen in Boron.  For example, if vxlan tunnel ports already exist, I see ODL create 2 more vxlan ports, instead of using the ones that already exist:&lt;/p&gt;


&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;root@overcloud-novacompute-1 ~&amp;#93;&lt;/span&gt;# ovs-vsctl show&lt;br/&gt;
be5e9b0f-2a00-4b71-beae-2279c1826525&lt;br/&gt;
    Manager &quot;tcp:192.0.2.4:6640&quot;&lt;br/&gt;
        is_connected: true&lt;br/&gt;
    Bridge br-int&lt;br/&gt;
        Controller &quot;tcp:192.0.2.4:6653&quot;&lt;br/&gt;
            is_connected: true&lt;br/&gt;
        Controller None&lt;br/&gt;
        fail_mode: secure&lt;br/&gt;
        Port &quot;tap4a993a0d-12&quot;&lt;br/&gt;
            Interface &quot;tap4a993a0d-12&quot;&lt;br/&gt;
        Port &quot;tune12ce5d9e46&quot;&lt;br/&gt;
            Interface &quot;tune12ce5d9e46&quot;&lt;br/&gt;
                type: vxlan&lt;br/&gt;
                options: &lt;/p&gt;
{key=flow, local_ip=&quot;11.0.0.26&quot;, remote_ip=&quot;11.0.0.21&quot;}&lt;br/&gt;
        Port &quot;tun55eac6c4536&quot;&lt;br/&gt;
            Interface &quot;tun55eac6c4536&quot;&lt;br/&gt;
                type: vxlan&lt;br/&gt;
                options: {key=flow, local_ip=&quot;11.0.0.26&quot;, remote_ip=&quot;11.0.0.27&quot;}&lt;br/&gt;
        Port &quot;tune230956df1c&quot;&lt;br/&gt;
            Interface &quot;tune230956df1c&quot;&lt;br/&gt;
                type: vxlan&lt;br/&gt;
                options: {key=flow, local_ip=&quot;11.0.0.26&quot;, remote_ip=&quot;11.0.0.21&quot;}
&lt;p&gt;        Port &quot;tapdf0e53b9-59&quot;&lt;br/&gt;
            Interface &quot;tapdf0e53b9-59&quot;&lt;br/&gt;
        Port &quot;tunad8086e8030&quot;&lt;br/&gt;
            Interface &quot;tunad8086e8030&quot;&lt;br/&gt;
                type: vxlan&lt;br/&gt;
                options: &lt;/p&gt;
{key=flow, local_ip=&quot;11.0.0.26&quot;, remote_ip=&quot;11.0.0.21&quot;}

&lt;p&gt;In another example, if I am using br-ex as my external network provider mapping.  ODL usually will come up and create a patch port between br-ex and br-int.  However, if that patch port already exists - ODL will error (in netvirt):&lt;br/&gt;
2017-01-30 13:50:19,051 | ERROR | pool-47-thread-1 | NatInterfaceStateChangeListener  | 326 - org.opendaylight.netvirt.natservice-impl - 0.3.3.Boron-SR3 | Unable to process add for interface 192152954067022:br-ex-patch ,since Interface ConfigDS entry absent for the same&lt;br/&gt;
2017-01-30 14:15:49,096 | ERROR | pool-46-thread-1 | SubnetOpDpnManager               | 317 - org.opendaylight.netvirt.vpnmanager-impl - 0.3.3.Boron-SR3 | Cannot get, portOp for port 192152954067022:br-ex-patch:flat is not available in datastore&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="22091">OVSDB-399</key>
            <summary>ODL does not reconcile pre-created OVS ports</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="10001">Won&apos;t Do</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="trozet">Tim Rozet</reporter>
                        <labels>
                    </labels>
                <created>Mon, 30 Jan 2017 19:57:14 +0000</created>
                <updated>Thu, 19 Oct 2017 21:26:36 +0000</updated>
                            <resolved>Thu, 20 Jul 2017 16:44:20 +0000</resolved>
                                    <version>unspecified</version>
                                                    <component>Southbound.Open_vSwitch</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>5</watches>
                                                                                                                <comments>
                            <comment id="41632" author="vorburger" created="Wed, 1 Feb 2017 11:26:15 +0000"  >&lt;p&gt;From: Sam Hague &amp;lt;shague@redhat.com&amp;gt;&lt;br/&gt;
Date: Tue, Jan 31, 2017 at 4:59 PM&lt;br/&gt;
Subject: Re: OpenDaylight upgrading schemas of config data store YANG models - examples?&lt;/p&gt;

&lt;p&gt;Tim can you add the karaf logs to that bug? The logs will show exceptions in models where something is inconsistent.&lt;/p&gt;</comment>
                            <comment id="41633" author="trozet@redhat.com" created="Wed, 1 Feb 2017 15:26:50 +0000"  >&lt;p&gt;(In reply to Michael Vorburger from comment #1)&lt;br/&gt;
&amp;gt; From: Sam Hague &amp;lt;shague@redhat.com&amp;gt;&lt;br/&gt;
&amp;gt; Date: Tue, Jan 31, 2017 at 4:59 PM&lt;br/&gt;
&amp;gt; Subject: Re: OpenDaylight upgrading schemas of config data store YANG models&lt;br/&gt;
&amp;gt; - examples?&lt;br/&gt;
&amp;gt; &lt;br/&gt;
&amp;gt; Tim can you add the karaf logs to that bug? The logs will show exceptions in&lt;br/&gt;
&amp;gt; models where something is inconsistent.&lt;/p&gt;

&lt;p&gt;Sorry I don&apos;t have that setup anymore, and I don&apos;t have time to test it right now.  I just filed it to track.  Easy way to test is just setup ODL deployment, then stop ODL, disconnect switches, rm -rf $ODL/, copy new ODL there and start it, wait till netvirt is up, reconnect switches (ports will remain on switches from previous deployment), observe the bug&lt;/p&gt;</comment>
                            <comment id="41634" author="vinh.nguyen@hcl.com" created="Fri, 7 Jul 2017 00:48:46 +0000"  >&lt;p&gt;With the following reproduction steps, I can reproduce this issue in Boron SR3 BUT the problem is not observed in in most recent Carbon release (as of July 6 2017)&lt;/p&gt;

&lt;p&gt;1) Start Control and Compute node&lt;br/&gt;
2) Start ODL&lt;br/&gt;
3) Create network 1&lt;br/&gt;
4) Create two instances VM1 on control node and VM2 on compute node for network 1&lt;br/&gt;
5) Stop ODL&lt;br/&gt;
6) Disconnect OVS, (ovs-vsctl del-manager on control and compute nodes)&lt;/p&gt;

&lt;p&gt;7) rm ODL directory&lt;br/&gt;
8) Install and start fresh ODL setup&lt;br/&gt;
9) create network 2&lt;br/&gt;
10) Create two instances VM3 on control node and VM4 on compute node for network 2&lt;/p&gt;

&lt;p&gt;11) Observe, only with BORON release, the two tunnel ports for the same vxlan tunnel between control and compute node. The problem is not observed if Carbon release is used&lt;/p&gt;</comment>
                            <comment id="41635" author="shague@redhat.com" created="Thu, 20 Jul 2017 16:44:20 +0000"  >&lt;p&gt;This works in carbon and boron will not be receiving updates.&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>7707</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=7707]]></customfieldvalue>

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

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