<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 19:54:05 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>[CONTROLLER-872] Flow state not written to node after it is removed and re-added</title>
                <link>https://jira.opendaylight.org/browse/CONTROLLER-872</link>
                <project id="10113" key="CONTROLLER">controller</project>
                    <description>&lt;p&gt;When flows are written to a node and it offine and returns after a few mins, the flow rules are not written to the node. Even an explicit write does not help.&lt;/p&gt;

&lt;p&gt;Here are the flows written to a node on Table #50 before the node goes offline. When the node returns, these rules are not written to the node. Sometimes I see the flow LOADBALANCER_FORWARD_FLOW1_10.0.0.5 being written. Sometimes I see LOADBALANCER_REVERSE_FLOW_10.0.0.5_10.0.0.8 written. It is not deterministic.&lt;/p&gt;


&lt;p&gt;&amp;lt;table xmlns=&quot;urn:opendaylight:flow:inventory&quot;&amp;gt;&lt;br/&gt;
&amp;lt;id&amp;gt;50&amp;lt;/id&amp;gt;&lt;br/&gt;
&amp;lt;flow&amp;gt;&lt;br/&gt;
&amp;lt;id&amp;gt;LOADBALANCER_REVERSE_FLOW_10.0.0.5_10.0.0.8&amp;lt;/id&amp;gt;&lt;br/&gt;
&amp;lt;flow-name&amp;gt;LOADBALANCER_REVERSE_FLOW_10.0.0.5_10.0.0.8&amp;lt;/flow-name&amp;gt;&lt;br/&gt;
&amp;lt;match&amp;gt;...&amp;lt;/match&amp;gt;&lt;br/&gt;
&amp;lt;priority&amp;gt;32768&amp;lt;/priority&amp;gt;&lt;br/&gt;
&amp;lt;idle-timeout&amp;gt;0&amp;lt;/idle-timeout&amp;gt;&lt;br/&gt;
&amp;lt;instructions&amp;gt;...&amp;lt;/instructions&amp;gt;&lt;br/&gt;
&amp;lt;barrier&amp;gt;true&amp;lt;/barrier&amp;gt;&lt;br/&gt;
&amp;lt;table_id&amp;gt;50&amp;lt;/table_id&amp;gt;&lt;br/&gt;
&amp;lt;hard-timeout&amp;gt;0&amp;lt;/hard-timeout&amp;gt;&lt;br/&gt;
&amp;lt;/flow&amp;gt;&lt;br/&gt;
&amp;lt;flow&amp;gt;&lt;br/&gt;
&amp;lt;id&amp;gt;DEFAULT_PIPELINE_FLOW_50&amp;lt;/id&amp;gt;&lt;br/&gt;
&amp;lt;flow-name&amp;gt;DEFAULT_PIPELINE_FLOW_50&amp;lt;/flow-name&amp;gt;&lt;br/&gt;
&amp;lt;match/&amp;gt;&lt;br/&gt;
&amp;lt;priority&amp;gt;0&amp;lt;/priority&amp;gt;&lt;br/&gt;
&amp;lt;idle-timeout&amp;gt;0&amp;lt;/idle-timeout&amp;gt;&lt;br/&gt;
&amp;lt;instructions&amp;gt;...&amp;lt;/instructions&amp;gt;&lt;br/&gt;
&amp;lt;barrier&amp;gt;true&amp;lt;/barrier&amp;gt;&lt;br/&gt;
&amp;lt;table_id&amp;gt;50&amp;lt;/table_id&amp;gt;&lt;br/&gt;
&amp;lt;hard-timeout&amp;gt;0&amp;lt;/hard-timeout&amp;gt;&lt;br/&gt;
&amp;lt;/flow&amp;gt;&lt;br/&gt;
&amp;lt;flow&amp;gt;&lt;br/&gt;
&amp;lt;id&amp;gt;LOADBALANCER_FORWARD_FLOW1_10.0.0.5&amp;lt;/id&amp;gt;&lt;br/&gt;
&amp;lt;flow-name&amp;gt;LOADBALANCER_FORWARD_FLOW1_10.0.0.5&amp;lt;/flow-name&amp;gt;&lt;br/&gt;
&amp;lt;match&amp;gt;...&amp;lt;/match&amp;gt;&lt;br/&gt;
&amp;lt;priority&amp;gt;32768&amp;lt;/priority&amp;gt;&lt;br/&gt;
&amp;lt;idle-timeout&amp;gt;0&amp;lt;/idle-timeout&amp;gt;&lt;br/&gt;
&amp;lt;instructions&amp;gt;...&amp;lt;/instructions&amp;gt;&lt;br/&gt;
&amp;lt;barrier&amp;gt;true&amp;lt;/barrier&amp;gt;&lt;br/&gt;
&amp;lt;table_id&amp;gt;50&amp;lt;/table_id&amp;gt;&lt;br/&gt;
&amp;lt;hard-timeout&amp;gt;0&amp;lt;/hard-timeout&amp;gt;&lt;br/&gt;
&amp;lt;/flow&amp;gt;&lt;br/&gt;
&amp;lt;flow&amp;gt;&lt;br/&gt;
&amp;lt;id&amp;gt;LOADBALANCER_REVERSE_FLOW_10.0.0.5_10.0.0.7&amp;lt;/id&amp;gt;&lt;br/&gt;
&amp;lt;flow-name&amp;gt;LOADBALANCER_REVERSE_FLOW_10.0.0.5_10.0.0.7&amp;lt;/flow-name&amp;gt;&lt;br/&gt;
&amp;lt;match&amp;gt;...&amp;lt;/match&amp;gt;&lt;br/&gt;
&amp;lt;priority&amp;gt;32768&amp;lt;/priority&amp;gt;&lt;br/&gt;
&amp;lt;idle-timeout&amp;gt;0&amp;lt;/idle-timeout&amp;gt;&lt;br/&gt;
&amp;lt;instructions&amp;gt;...&amp;lt;/instructions&amp;gt;&lt;br/&gt;
&amp;lt;barrier&amp;gt;true&amp;lt;/barrier&amp;gt;&lt;br/&gt;
&amp;lt;table_id&amp;gt;50&amp;lt;/table_id&amp;gt;&lt;br/&gt;
&amp;lt;hard-timeout&amp;gt;0&amp;lt;/hard-timeout&amp;gt;&lt;br/&gt;
&amp;lt;/flow&amp;gt;&lt;br/&gt;
&amp;lt;flow&amp;gt;&lt;br/&gt;
&amp;lt;id&amp;gt;LOADBALANCER_FORWARD_FLOW2_10.0.0.5_10.0.0.8&amp;lt;/id&amp;gt;&lt;br/&gt;
&amp;lt;flow-name&amp;gt;LOADBALANCER_FORWARD_FLOW2_10.0.0.5_10.0.0.8&amp;lt;/flow-name&amp;gt;&lt;br/&gt;
&amp;lt;match&amp;gt;...&amp;lt;/match&amp;gt;&lt;br/&gt;
&amp;lt;priority&amp;gt;32769&amp;lt;/priority&amp;gt;&lt;br/&gt;
&amp;lt;idle-timeout&amp;gt;0&amp;lt;/idle-timeout&amp;gt;&lt;br/&gt;
&amp;lt;instructions&amp;gt;...&amp;lt;/instructions&amp;gt;&lt;br/&gt;
&amp;lt;barrier&amp;gt;true&amp;lt;/barrier&amp;gt;&lt;br/&gt;
&amp;lt;table_id&amp;gt;50&amp;lt;/table_id&amp;gt;&lt;br/&gt;
&amp;lt;hard-timeout&amp;gt;0&amp;lt;/hard-timeout&amp;gt;&lt;br/&gt;
&amp;lt;/flow&amp;gt;&lt;br/&gt;
&amp;lt;flow&amp;gt;&lt;br/&gt;
&amp;lt;id&amp;gt;LOADBALANCER_FORWARD_FLOW2_10.0.0.5_10.0.0.7&amp;lt;/id&amp;gt;&lt;br/&gt;
&amp;lt;flow-name&amp;gt;LOADBALANCER_FORWARD_FLOW2_10.0.0.5_10.0.0.7&amp;lt;/flow-name&amp;gt;&lt;br/&gt;
&amp;lt;match&amp;gt;...&amp;lt;/match&amp;gt;&lt;br/&gt;
&amp;lt;priority&amp;gt;32769&amp;lt;/priority&amp;gt;&lt;br/&gt;
&amp;lt;idle-timeout&amp;gt;0&amp;lt;/idle-timeout&amp;gt;&lt;br/&gt;
&amp;lt;instructions&amp;gt;...&amp;lt;/instructions&amp;gt;&lt;br/&gt;
&amp;lt;barrier&amp;gt;true&amp;lt;/barrier&amp;gt;&lt;br/&gt;
&amp;lt;table_id&amp;gt;50&amp;lt;/table_id&amp;gt;&lt;br/&gt;
&amp;lt;hard-timeout&amp;gt;0&amp;lt;/hard-timeout&amp;gt;&lt;br/&gt;
&amp;lt;/flow&amp;gt;&lt;br/&gt;
&amp;lt;/table&amp;gt;&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="25426">CONTROLLER-872</key>
            <summary>Flow state not written to node after it is removed and re-added</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="-1">Unassigned</assignee>
                                    <reporter username="srini.seetharaman@gmail.com">Srini Seetharaman</reporter>
                        <labels>
                    </labels>
                <created>Sat, 20 Sep 2014 16:53:49 +0000</created>
                <updated>Thu, 19 Oct 2017 22:13:16 +0000</updated>
                            <resolved>Tue, 5 May 2015 15:17:21 +0000</resolved>
                                    <version>Helium</version>
                                                    <component>adsal</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>5</watches>
                                                                                                                <comments>
                            <comment id="49282" author="srini.seetharaman@gmail.com" created="Sat, 20 Sep 2014 16:56:33 +0000"  >&lt;p&gt;This issue was noticed in the OVSDB project.&lt;/p&gt;

&lt;p&gt;Here is the DEBUG log when the flow is attempted to be rewritten on an InventoryListen.notifyNode() call when the node is added back. It says TransactionSuccess worked, but not rules written to the node.&lt;/p&gt;

&lt;p&gt;2014-09-20 09:46:14.177 PDT &lt;span class=&quot;error&quot;&gt;&amp;#91;md-sal-binding-notification-182&amp;#93;&lt;/span&gt; DEBUG o.o.o.openstack.netvirt.LBaaSHandler  - notifyNode: Node OF|00:00:4a:a8:82:09:59:48 update CHANGED from Controller&apos;s invente&lt;br/&gt;
2014-09-20 09:46:14.178 PDT &lt;span class=&quot;error&quot;&gt;&amp;#91;md-sal-binding-notification-182&amp;#93;&lt;/span&gt; DEBUG o.o.o.o.n.api.LoadBalancerProvider  - Performing ADD rules for VIP 10.0.0.5 and 2 members&lt;br/&gt;
2014-09-20 09:46:14.179 PDT &lt;span class=&quot;error&quot;&gt;&amp;#91;md-sal-binding-notification-182&amp;#93;&lt;/span&gt; DEBUG o.o.o.o.n.p.o.AbstractServiceInstance  - Transaction success for write of Flow LOADBALANCER_FORWARD_FLOW1_10.0.0.5&lt;br/&gt;
2014-09-20 09:46:14.670 PDT &lt;span class=&quot;error&quot;&gt;&amp;#91;pool-28-thread-1&amp;#93;&lt;/span&gt; DEBUG o.o.o.o.n.p.o.AbstractServiceInstance  - Transaction success for write of Flow DEFAULT_PIPELINE_FLOW_90&lt;br/&gt;
2014-09-20 09:46:14.682 PDT &lt;span class=&quot;error&quot;&gt;&amp;#91;md-sal-binding-notification-182&amp;#93;&lt;/span&gt; DEBUG o.o.o.o.n.p.o.AbstractServiceInstance  - Transaction success for write of Flow LOADBALANCER_FORWARD_FLOW2_10.0.0.5_10.0.0.7&lt;br/&gt;
2014-09-20 09:46:14.684 PDT &lt;span class=&quot;error&quot;&gt;&amp;#91;nioEventLoopGroup-13-3&amp;#93;&lt;/span&gt; WARN  o.o.o.p.i.c.ResponseExpectedRpcListener  - Request for RpcResultKey [xid=41, outputClazz=org.opendaylight.yang.gen.v1.urn.opendaylige&lt;br/&gt;
2014-09-20 09:46:15.172 PDT &lt;span class=&quot;error&quot;&gt;&amp;#91;pool-28-thread-1&amp;#93;&lt;/span&gt; DEBUG o.o.o.o.n.p.o.AbstractServiceInstance  - Transaction success for write of Flow DEFAULT_PIPELINE_FLOW_100&lt;br/&gt;
2014-09-20 09:46:15.185 PDT &lt;span class=&quot;error&quot;&gt;&amp;#91;md-sal-binding-notification-182&amp;#93;&lt;/span&gt; DEBUG o.o.o.o.n.p.o.AbstractServiceInstance  - Transaction success for write of Flow LOADBALANCER_FORWARD_FLOW2_10.0.0.5_10.0.0.8&lt;br/&gt;
2014-09-20 09:46:15.187 PDT &lt;span class=&quot;error&quot;&gt;&amp;#91;nioEventLoopGroup-13-3&amp;#93;&lt;/span&gt; WARN  o.o.o.p.i.c.ResponseExpectedRpcListener  - Request for RpcResultKey [xid=43, outputClazz=org.opendaylight.yang.gen.v1.urn.opendaylige&lt;br/&gt;
2014-09-20 09:46:15.674 PDT &lt;span class=&quot;error&quot;&gt;&amp;#91;pool-28-thread-1&amp;#93;&lt;/span&gt; DEBUG o.o.o.o.n.p.o.AbstractServiceInstance  - Transaction success for write of Flow DEFAULT_PIPELINE_FLOW_110&lt;br/&gt;
2014-09-20 09:46:15.686 PDT &lt;span class=&quot;error&quot;&gt;&amp;#91;md-sal-binding-notification-182&amp;#93;&lt;/span&gt; DEBUG o.o.o.o.n.p.o.AbstractServiceInstance  - Transaction success for write of Flow LOADBALANCER_REVERSE_FLOW_10.0.0.5_10.0.0.7&lt;br/&gt;
2014-09-20 09:46:16.188 PDT &lt;span class=&quot;error&quot;&gt;&amp;#91;md-sal-binding-notification-182&amp;#93;&lt;/span&gt; DEBUG o.o.o.o.n.p.o.AbstractServiceInstance  - Transaction success for write of Flow LOADBALANCER_REVERSE_FLOW_10.0.0.5_10.0.0.8&lt;/p&gt;</comment>
                            <comment id="49283" author="srini.seetharaman@gmail.com" created="Sat, 20 Sep 2014 17:47:03 +0000"  >&lt;p&gt;Attached is the wireshark pcap of the OpenFlow messages. I see only the OFPFC_MODIFY for two of the flows:&lt;/p&gt;
&lt;ul class=&quot;alternate&quot; type=&quot;square&quot;&gt;
	&lt;li&gt;LOADBALANCER_FORWARD_FLOW2_10.0.0.5_10.0.0.7&lt;/li&gt;
	&lt;li&gt;LOADBALANCER_FORWARD_FLOW2_10.0.0.5_10.0.0.8&lt;/li&gt;
&lt;/ul&gt;
</comment>
                            <comment id="49286" author="srini.seetharaman@gmail.com" created="Sat, 20 Sep 2014 17:47:03 +0000"  >&lt;p&gt;Attachment dummy1.pcap has been added with description: Pcap of OpenFlow messages&lt;/p&gt;</comment>
                            <comment id="49284" author="srini.seetharaman@gmail.com" created="Wed, 24 Sep 2014 04:44:30 +0000"  >&lt;p&gt;It looks like the bug is resolved.&lt;/p&gt;

&lt;p&gt;Previously, when a switch with the default OVSDB pipeline rules was disconnected by doing del-manager and del-controller, and then connected by doing set-mananger, the full rule set was not written. &lt;/p&gt;

&lt;p&gt;But, now it works fine.&lt;/p&gt;</comment>
                            <comment id="49285" author="carolsand@gmail.com" created="Tue, 5 May 2015 15:17:21 +0000"  >&lt;p&gt;This bug is part of the project to Move all ADSAL associated component bugs to ADSAL.&lt;/p&gt;</comment>
                    </comments>
                    <attachments>
                            <attachment id="13437" name="dummy1.pcap" size="36108" author="srini.seetharaman@gmail.com" created="Sat, 20 Sep 2014 17:47:03 +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_10208" key="com.atlassian.jira.plugin.system.customfieldtypes:textfield">
                        <customfieldname>External issue ID</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>2000</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=2000]]></customfieldvalue>

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

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