<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 19:52:28 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-216] Unable to see the flow stats after adding a flow for OpenDaylight Clustering project</title>
                <link>https://jira.opendaylight.org/browse/CONTROLLER-216</link>
                <project id="10113" key="CONTROLLER">controller</project>
                    <description>&lt;p&gt;Given C1 and C2 controllers in cluster of two controllers, flows statistics are not present after recovering a controller from failure.&lt;/p&gt;

&lt;p&gt;Steps for reproducing the issue:&lt;/p&gt;

&lt;p&gt;1. Download the latest controller wget &lt;a href=&quot;https://jenkins.opendaylight.org/integration/job/integration-project-centralized-integration/lastSuccessfulBuild/artifact/distributions/base/target/distributions-base-0.1.0-SNAPSHOT-osgipackage.zip&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://jenkins.opendaylight.org/integration/job/integration-project-centralized-integration/lastSuccessfulBuild/artifact/distributions/base/target/distributions-base-0.1.0-SNAPSHOT-osgipackage.zip&lt;/a&gt;  in two different VMs&lt;br/&gt;
2. Start a controller say C1 using ./run.sh -Dsupernodes=10.125.136.38:10.125.136.43 -start&lt;br/&gt;
3. Start another controller say C2 using ./run.sh -Dsupernodes=10.125.136.38:10.125.136.43 -start&lt;br/&gt;
4. Start mininet, ${start}=  sudo mn --controller=remote,ip=${CONTROLLER_C1} --topo tree,2&lt;br/&gt;
5. Set the bridges for bringing up C2 controller at mininet:&lt;br/&gt;
$ ovs-vsctl set-controller s1 tcp:Controller1_IP:6633 tcp:Controller2_IP:6633&lt;br/&gt;
$ ovs-vsctl set-controller s2 tcp:Controller1_IP:6633 tcp:Controller2_IP:6633&lt;br/&gt;
$ ovs-vsctl set-controller s3 tcp:Controller1_IP:6633 tcp:Controller2_IP:6633&lt;br/&gt;
5. Use PUT request for adding a flow in C1&lt;br/&gt;
PUT &lt;a href=&quot;http://Controller1_IP:8080/controller/nb/v2/flowprogrammer/default/node/OF/00:00:00:00:00:00:00:02/staticFlow/flow1&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://Controller1_IP:8080/controller/nb/v2/flowprogrammer/default/node/OF/00:00:00:00:00:00:00:02/staticFlow/flow1&lt;/a&gt; + flow1 body&lt;/p&gt;

&lt;p&gt;flow 1 body:&lt;/p&gt;

&lt;p&gt;&amp;lt;flowConfig&amp;gt;&lt;br/&gt;
   &amp;lt;installInHw&amp;gt;true&amp;lt;/installInHw&amp;gt;&lt;br/&gt;
   &amp;lt;name&amp;gt;flow1&amp;lt;/name&amp;gt;&lt;br/&gt;
   &amp;lt;node&amp;gt;&lt;br/&gt;
      &amp;lt;id&amp;gt;00:00:00:00:00:00:00:02&amp;lt;/id&amp;gt;&lt;br/&gt;
      &amp;lt;type&amp;gt;OF&amp;lt;/type&amp;gt;&lt;br/&gt;
   &amp;lt;/node&amp;gt; &lt;br/&gt;
   &amp;lt;priority&amp;gt;1&amp;lt;/priority&amp;gt;&lt;br/&gt;
   &amp;lt;etherType&amp;gt;0x800&amp;lt;/etherType&amp;gt;&lt;br/&gt;
   &amp;lt;nwDst&amp;gt;10.0.0.1/32&amp;lt;/nwDst&amp;gt;&lt;br/&gt;
   &amp;lt;actions&amp;gt;OUTPUT=1&amp;lt;/actions&amp;gt;&lt;br/&gt;
&amp;lt;/flowConfig&amp;gt;&lt;/p&gt;

&lt;p&gt;6. Verify the flow stats in both the controllers (C1 &amp;amp; C2)&lt;/p&gt;

&lt;p&gt;See flow1 on Controller1 (i.e. GET &lt;a href=&quot;http://Controller1_IP:8080/controller/nb/v2/statistics/default/flow&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://Controller1_IP:8080/controller/nb/v2/statistics/default/flow&lt;/a&gt;) and check flow is present&lt;br/&gt;
See flow1 on Controller2 (i.e. GET &lt;a href=&quot;http://Controller2_IP:8080/controller/nb/v2/statistics/default/flow&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://Controller2_IP:8080/controller/nb/v2/statistics/default/flow&lt;/a&gt;) and check the same flow is present&lt;/p&gt;

&lt;p&gt;7. Bring down the controller C1 (use ./run.sh -stop)&lt;br/&gt;
8. See flow1 on Controller2 (i.e. GET &lt;a href=&quot;http://Controller2_IP:8080/controller/nb/v2/statistics/default/flow&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://Controller2_IP:8080/controller/nb/v2/statistics/default/flow&lt;/a&gt;) and check the same flow is present&lt;br/&gt;
9. Bring up the controller C1 (./run.sh -start)&lt;br/&gt;
10. See flow1 on Controller1 (i.e. GET &lt;a href=&quot;http://Controller1_IP:8080/controller/nb/v2/statistics/default/flow&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://Controller1_IP:8080/controller/nb/v2/statistics/default/flow&lt;/a&gt;) and check the same flow is present. &lt;/p&gt;
{Note: I am unable to see the flows stats. Sometimes it is showing up but not frequently stable}
&lt;p&gt;11.See flow1 on Controller2 (i.e. GET &lt;a href=&quot;http://Controller2_IP:8080/controller/nb/v2/statistics/default/flow&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;http://Controller2_IP:8080/controller/nb/v2/statistics/default/flow&lt;/a&gt;) and check the same flow is present. &lt;/p&gt;
{Note: I am unable to see the flows stats. Sometimes it is showing up but not frequently stable}
&lt;p&gt;12. Bring down the controller C2&lt;br/&gt;
13. Check the same flow in controller C1 &lt;/p&gt;
{Note: I am unable to see the flows stats}

&lt;p&gt;Thanks,&lt;br/&gt;
Madhusudhan&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: Windows&lt;br/&gt;
Platform: PC&lt;/p&gt;</environment>
        <key id="24770">CONTROLLER-216</key>
            <summary>Unable to see the flow stats after adding a flow for OpenDaylight Clustering project</summary>
                <type id="10100" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10310&amp;avatarType=issuetype">Improvement</type>
                                                <status id="10004" iconUrl="https://jira.opendaylight.org/images/icons/status_generic.gif" description="">Verified</status>
                    <statusCategory id="3" key="done" colorName="green"/>
                                    <resolution id="10003">Cannot Reproduce</resolution>
                                        <assignee username="ykhodork@cisco.com">Yevgeny Khodorkovsky</assignee>
                                    <reporter username="madhusudhan.opendaylight@yahoo.com">Madhusudhan Ananderi</reporter>
                        <labels>
                    </labels>
                <created>Mon, 17 Mar 2014 22:06:10 +0000</created>
                <updated>Tue, 25 Jul 2023 08:23:14 +0000</updated>
                            <resolved>Thu, 17 Apr 2014 18:45:21 +0000</resolved>
                                                                    <component>clustering</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>2</watches>
                                                                                                                <comments>
                            <comment id="47764" author="madhusudhan.opendaylight@yahoo.com" created="Fri, 4 Apr 2014 18:00:33 +0000"  >&lt;p&gt;Hello, &lt;/p&gt;

&lt;p&gt;I would like to follow-up with this bug. Can you please let me know if there is any resolution.&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br/&gt;
Madhusudhan&lt;/p&gt;</comment>
                            <comment id="47765" author="ykhodork@cisco.com" created="Thu, 17 Apr 2014 18:05:48 +0000"  >

&lt;p&gt;From: Madhusudhan Kandadai &amp;lt;madhusudhan.opendaylight@yahoo.com&amp;gt;&lt;br/&gt;
Date: Wednesday, April 16, 2014 at 12:56 PM&lt;br/&gt;
To: &quot;Alessandro Boch (aboch)&quot; &amp;lt;aboch@cisco.com&amp;gt;&lt;br/&gt;
Cc: Luis Gomez &amp;lt;ecelgp@gmail.com&amp;gt;, Yevgeny Khodorkovsky &amp;lt;ykhodork@cisco.com&amp;gt;&lt;br/&gt;
Subject: Re: Clustering test&lt;/p&gt;

&lt;p&gt;Hi Alessandro/Luis,&lt;/p&gt;

&lt;p&gt;Thank you for your email.&lt;/p&gt;

&lt;p&gt;I have tested against new ODL controller and found that it is working as expected and could not see any errors. Have tested the following scenarios:&lt;/p&gt;

&lt;p&gt;1. Give a cluster of two controllers C1 &amp;amp; C2&lt;br/&gt;
2. Start both the controllers with supernode&lt;br/&gt;
3. Add a flow in C1 and verify the flow stats in C1 &amp;amp; C2&lt;br/&gt;
4. Bring C1 down and verify the flow stats in C2&lt;br/&gt;
5. Bring C1 back to the normal and check the flow in C1&lt;/p&gt;

&lt;p&gt;Regards,&lt;br/&gt;
Madhusudhan&lt;/p&gt;


&lt;p&gt;On Wed, Apr 16, 2014 at 9:31 AM, Alessandro Boch (aboch) &amp;lt;aboch@cisco.com&amp;gt; wrote:&lt;br/&gt;
Hi Luis, Madhusudhan,&lt;/p&gt;

&lt;p&gt;Last week I had time for this and tried few times to reproduce, but was not able to.&lt;/p&gt;

&lt;p&gt;When the bug was opened, I was able to consistently reproduce.&lt;/p&gt;

&lt;p&gt;I am guessing this got fixed by a fix from Yevgeny.&lt;/p&gt;



&lt;p&gt;Just to clarify, I tested latest ODL code, not H release one.&lt;/p&gt;

&lt;p&gt;Please let me know if you still see the issue with latest code.&lt;/p&gt;

&lt;p&gt;Thanks,&lt;br/&gt;
Alessandro&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>530</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=530]]></customfieldvalue>

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

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