<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:35:48 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-215] East-west traffic (with different network)does not work after a compute node is unstacked and re-stacked</title>
                <link>https://jira.opendaylight.org/browse/OVSDB-215</link>
                <project id="10158" key="OVSDB">ovsdb</project>
                    <description>&lt;p&gt;Build#: Lithium-SR1 Build&lt;br/&gt;
Openstack: stable/kilo&lt;br/&gt;
ODL config (on etc/custom.properties)&lt;br/&gt;
===========&lt;br/&gt;
ovsdb.of.version=1.3&lt;br/&gt;
ovsdb.l3.fwd.enabled=yes&lt;/p&gt;

&lt;p&gt;local.conf snip&lt;br/&gt;
=======&lt;br/&gt;
enable_plugin networking-odl &lt;a href=&quot;https://github.com/stackforge/networking-odl&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://github.com/stackforge/networking-odl&lt;/a&gt; stable/kilo&lt;br/&gt;
Q_PLUGIN=ml2&lt;br/&gt;
ENABLE_TENANT_TUNNELS=True&lt;br/&gt;
Q_ML2_TENANT_NETWORK_TYPE=vxlan&lt;br/&gt;
PUBLIC_INTERFACE=em3&lt;br/&gt;
ODL_MODE=compute&lt;br/&gt;
ODL_MGR_IP=&amp;lt;ODL_IP&amp;gt;&lt;br/&gt;
ODL_LOCAL_IP=&amp;lt;DATA_NET_IP&amp;gt;&lt;br/&gt;
ODL_PROVIDER_MAPPINGS=br-ex:&amp;lt;EXT_INT&amp;gt;&lt;br/&gt;
disable_service q-l3&lt;br/&gt;
Q_L3_ENABLED=True&lt;br/&gt;
ODL_L3=True&lt;/p&gt;


&lt;p&gt;Openstack setup&lt;br/&gt;
=================&lt;br/&gt;
 eth0 =&amp;gt; Mgmt Network   eth1=&amp;gt; Data Network   eth3 =&amp;gt; External Network&lt;br/&gt;
 1 openstack controller &amp;amp; 3 compute node&lt;/p&gt;


&lt;p&gt;Problem:&lt;br/&gt;
============&lt;br/&gt;
East-West traffic not working in between subnets in specific restack scenario.&lt;/p&gt;

&lt;p&gt;Step to Recreate:&lt;br/&gt;
===============&lt;br/&gt;
1.Router Gateway contains interface of both 1.1.1.x &amp;amp; 2.1.1.x with 8.1.1.1 External Gateway.&lt;br/&gt;
2.Spawn 2 VM&apos;s each 1.1.1.x &amp;amp; 2.1.1.x network on both compute nodes.&lt;br/&gt;
Compute Node1 =&amp;gt;  VM1: 1.1.1.3  VM3: 2.1.1.3  &lt;br/&gt;
Compute Node2 =&amp;gt;  VM2: 1.1.1.4  VM4: 2.1.1.4&lt;br/&gt;
3.Associate Floating IP Address on following way&lt;br/&gt;
Compute Node1 =&amp;gt;  VM1: 1.1.1.3  Floating IP : 8.1.1.3  &lt;br/&gt;
Compute Node2 =&amp;gt;  VM2: 1.1.1.4  Floating IP : 8.1.1.4&lt;/p&gt;

&lt;p&gt;5.Disassociated floating IP,Deleted all VM&apos;s spwaned on compute node-2 and un-stacked &lt;/p&gt;

&lt;p&gt;6.Restacked and provisioned new VM(s) with private ip on 2.1.1.x network and associated the floating IP address.&lt;br/&gt;
Compute Node2 =&amp;gt; VM5: 2.1.1.5  Floating IP Address=&amp;gt; 8.1.1.5&lt;/p&gt;

&lt;p&gt;Try following test:&lt;br/&gt;
1.ping between 2.1.1.5(compute node 2) to 2.1.1.3 (compute node 1) - successful &lt;br/&gt;
2.ping between 2.1.1.5 private ip /8.1.1.5-floating ip  to  8.1.1.1 (ext Gateway),8.1.1.3(compute node 1 VM) successful&lt;br/&gt;
3.ping between 2.1.1.5 (compute node2) to 1.1.1.3 (compute node1) -Unsuccessful.&lt;/p&gt;

&lt;p&gt;3rd Test needs to passed via Private IP of VM as well.Since RouterGateway Interface contains 1.1.1.x Network.&lt;/p&gt;


&lt;p&gt;Workaround:&lt;br/&gt;
==========&lt;br/&gt;
Provision new VM on restacked compute node with 1.1.1.x network,then 1.1.1.x network will be reachable from 2.1.1.5 VM&lt;/p&gt;

&lt;p&gt;Associated defect #4408,4346&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="21907">OVSDB-215</key>
            <summary>East-west traffic (with different network)does not work after a compute node is unstacked and re-stacked</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="jhershbe">Josh Hershberg</assignee>
                                    <reporter username="vasanthan_balasubram@dell.com">Vasanthan Balasubramaniyan</reporter>
                        <labels>
                    </labels>
                <created>Tue, 6 Oct 2015 05:03:50 +0000</created>
                <updated>Tue, 29 May 2018 14:57:25 +0000</updated>
                            <resolved>Tue, 15 Mar 2016 13:39:47 +0000</resolved>
                                    <version>unspecified</version>
                                                    <component>openstack.net-virt</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>6</watches>
                                                                                                                <comments>
                            <comment id="40996" author="vasanthan_balasubram@dell.com" created="Mon, 1 Feb 2016 11:05:36 +0000"  >&lt;p&gt;On Bery-RC1 Build,Openstack-Kilo&lt;/p&gt;

&lt;p&gt;While re-stack the compute node and create new VM&apos;s on existing network and associate the floating IP address,Unable to communicate via private IP&apos;s.However its managed to communicated via Floating IP to other compute node VM&apos;s floating IP address.&lt;/p&gt;

&lt;p&gt;Until hard-reboot of existing VM&apos;s(with existing network),VM cannot communicate with each-other with same private network IP&apos;s (spawn across different compute node).&lt;/p&gt;

&lt;p&gt;Hence this defect visible,with workaround as &quot;reboot of existing VM&quot;&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10002">
                    <name>Duplicate</name>
                                            <outwardlinks description="duplicates">
                                        <issuelink>
            <issuekey id="21905">OVSDB-213</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>4417</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=4417]]></customfieldvalue>

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

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

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