<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:36:26 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-450] Deleting a bridge in OVS deletes the ProtocolEntry for all bridges</title>
                <link>https://jira.opendaylight.org/browse/OVSDB-450</link>
                <project id="10158" key="OVSDB">ovsdb</project>
                    <description>&lt;p&gt;Hello,&lt;/p&gt;

&lt;p&gt;I found a bug when using ODL to manage multiple bridges on a single OVS.&lt;/p&gt;

&lt;p&gt;The problem is as follows:&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;I create two bridges br1 and br2 on an OVS node and set them to use OpenFlow 1.3 by setting a ProtocolEntry with&#160;OvsdbBridgeProtocolOpenflow13.class in&#160;OvsdbBridgeAugmentationBuilder.&lt;/li&gt;
	&lt;li&gt;Setting the ProtocolEntry is required because OVS&#160;2.8.1 defaults to a version of OpenFlow not supported by ODL&lt;/li&gt;
	&lt;li&gt;I then delete bridge br2 through the OVSDB REST API&lt;/li&gt;
	&lt;li&gt;At that point, br2 is correctly deleted but br1 gets disconnected from ODL OpenFlow plugin&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;The following line appears in the log:&lt;/p&gt;

&lt;p&gt;2018-02-09 17:41:42,787 | INFO | on-dispatcher-61 | ProtocolRemovedCommand | 345 - org.opendaylight.ovsdb.southbound-impl - 1.4.2.Carbon | Removed ProtocolEntry : OpenFlow13 for OVSDB Bridge : null&lt;/p&gt;

&lt;p&gt;instead of something like&lt;/p&gt;

&lt;p&gt;2018-02-09 17:41:42,787 | INFO | on-dispatcher-61 | ProtocolRemovedCommand | 345 - org.opendaylight.ovsdb.southbound-impl - 1.4.2.Carbon | Removed ProtocolEntry : OpenFlow13 for OVSDB Bridge : br2&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;When checking the ovsdb topology through the REST API, it appears that the ProtocolEntry has been removed for br1 as well&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;It is possible to get back the connectivity using&#160;&lt;/p&gt;

&lt;p&gt;ovs-vsctl set bridge&#160;br1 protocols=OpenFlow13&lt;/p&gt;

&lt;p&gt;but that requires manual action on the OVS.&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;Do not hesitate to contact me if more info is required.&lt;/p&gt;

&lt;p&gt;Thanks&lt;/p&gt;

&lt;p&gt;Thomas&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;</description>
                <environment>&lt;p&gt;OS: Linux 4.2.0-34-generic #39~14.04.1-Ubuntu SMP Fri Mar 11 11:38:02 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux&lt;/p&gt;

&lt;p&gt;Open vSwitch: 2.8.1&lt;/p&gt;

&lt;p&gt;Opendaylight: Carbon-SR2&lt;/p&gt;</environment>
        <key id="29174">OVSDB-450</key>
            <summary>Deleting a bridge in OVS deletes the ProtocolEntry for all bridges</summary>
                <type id="10104" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10303&amp;avatarType=issuetype">Bug</type>
                                            <priority id="2" iconUrl="https://jira.opendaylight.org/images/icons/priorities/critical.svg">High</priority>
                        <status id="1" iconUrl="https://jira.opendaylight.org/images/icons/statuses/open.png" description="The issue is open and ready for the assignee to start work on it.">Open</status>
                    <statusCategory id="2" key="new" colorName="blue-gray"/>
                                    <resolution id="-1">Unresolved</resolution>
                                        <assignee username="-1">Unassigned</assignee>
                                    <reporter username="tferrandiz">Thomas Ferrandiz</reporter>
                        <labels>
                            <label>openflow</label>
                            <label>ovsdb</label>
                    </labels>
                <created>Fri, 9 Feb 2018 17:10:45 +0000</created>
                <updated>Wed, 1 May 2019 23:55:31 +0000</updated>
                                            <version>Oxygen-SR1</version>
                                                    <component>Southbound.Open_vSwitch</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="63067" author="thapar" created="Wed, 23 May 2018 04:22:21 +0000"  >&lt;p&gt;Can you confirm if it works on Nitrogen or latest Master. Could you also share the REST URI and JSON used to delete the bridge?&lt;/p&gt;</comment>
                            <comment id="63330" author="tferrandiz" created="Wed, 6 Jun 2018 15:19:44 +0000"  >&lt;p&gt;I tested with Oxygen SR1, the bug is still present.&lt;/p&gt;

&lt;p&gt;The REST URI and JSON used to create the bridges, then delete one of them are provided in the attached file odl_ovsdb_bug_report.sh&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;

&lt;p&gt;&#160;&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                            <attachment id="14672" name="odl_ovsdb_bug_report.sh" size="2621" author="tferrandiz" created="Wed, 6 Jun 2018 15:18:23 +0000"/>
                    </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_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i03a4v:</customfieldvalue>

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