<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 19:56:35 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-1839] leader vs follower data</title>
                <link>https://jira.opendaylight.org/browse/CONTROLLER-1839</link>
                <project id="10113" key="CONTROLLER">controller</project>
                    <description>&lt;p&gt;check results of jobs to see if there is any correlation between the passing and&lt;br/&gt;
failing jobs and whether the follower that is chosen to talk with (car-adding&lt;br/&gt;
script &lt;b&gt;and&lt;/b&gt; robot rest calls) is the one that becomes the leader or stays as&lt;br/&gt;
follower when the initial leader is isolated.&lt;/p&gt;</description>
                <environment></environment>
        <key id="30182">CONTROLLER-1839</key>
            <summary>leader vs follower data</summary>
                <type id="10102" iconUrl="https://jira.opendaylight.org/secure/viewavatar?size=xsmall&amp;avatarId=10316&amp;avatarType=issuetype">Sub-task</type>
                            <parent id="30151">CONTROLLER-1838</parent>
                                    <priority id="3" iconUrl="https://jira.opendaylight.org/images/icons/priorities/major.svg">Medium</priority>
                        <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="10000">Done</resolution>
                                        <assignee username="jluhrsen">Jamo Luhrsen</assignee>
                                    <reporter username="jluhrsen">Jamo Luhrsen</reporter>
                        <labels>
                    </labels>
                <created>Fri, 22 Jun 2018 17:13:19 +0000</created>
                <updated>Sat, 23 Jun 2018 23:02:30 +0000</updated>
                            <resolved>Sat, 23 Jun 2018 23:02:25 +0000</resolved>
                                                                    <component>clustering</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>4</watches>
                                                                                                                <comments>
                            <comment id="63648" author="jluhrsen" created="Sat, 23 Jun 2018 23:01:26 +0000"  >&lt;p&gt;TL;DR, There is no pattern in the jobs that pass or fail regarding which follower will end up being the&lt;br/&gt;
leader when the initial leader is isolated.&lt;/p&gt;

&lt;p&gt;I looked at the most recent 10 jobs, 4 of which passed. one of those passing jobs was sending&lt;br/&gt;
the car creation script to the follower that ended up being the leader, while the other 3 were&lt;br/&gt;
talking to the follower that remained the follower.&lt;/p&gt;

&lt;p&gt;also, in the 6 jobs that failed, one (job 123) saw a &quot;read timed out&quot; in the final test case, but&lt;br/&gt;
everything else was fine in that suite. We have a &lt;a href=&quot;https://jira.opendaylight.org/browse/GENIUS-166&quot; class=&quot;external-link&quot; rel=&quot;nofollow&quot;&gt;genius bug&lt;/a&gt; that was seeing this similar&lt;br/&gt;
thing. That actually had a fix merged though, so now I wonder what could have cause it.&lt;br/&gt;
This is not specific to this &lt;a href=&quot;https://jira.opendaylight.org/browse/CONTROLLER-1839&quot; title=&quot;leader vs follower data&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CONTROLLER-1839&quot;&gt;&lt;del&gt;CONTROLLER-1839&lt;/del&gt;&lt;/a&gt; issue though, just noting it here.&lt;/p&gt;

&lt;p&gt;The other 5 jobs that failed all say the python tool get the 401 unauthorized problem,&lt;br/&gt;
which we think should be expected in the ask-based protocol (which is what these jobs&lt;br/&gt;
were running). Two of those were talking to the follower that would become the leader&lt;br/&gt;
and the other three were talking to the follower that stayed follower.&lt;/p&gt;

&lt;p&gt;So, all said and done, there is no pattern or anything to zero in on &lt;img class=&quot;emoticon&quot; src=&quot;https://jira.opendaylight.org/images/icons/emoticons/sad.png&quot; height=&quot;16&quot; width=&quot;16&quot; align=&quot;absmiddle&quot; alt=&quot;&quot; border=&quot;0&quot;/&gt;&lt;/p&gt;


&lt;p&gt;Below are my notes as I went through the jobs. might not make sense, but I wanted&lt;br/&gt;
to keep them.&lt;/p&gt;

&lt;p&gt;A      RTO on last TC&lt;br/&gt;
B   	python tool 401, but completed without traceback&lt;br/&gt;
C	PASS new leader is dst&lt;br/&gt;
D	PASS new leader is not dst&lt;/p&gt;

&lt;p&gt;123	A . D&lt;br/&gt;
122	B . C&lt;br/&gt;
121	C&lt;br/&gt;
120 	D&lt;br/&gt;
119	B . D&lt;br/&gt;
118	D&lt;br/&gt;
117	D&lt;br/&gt;
116	B . C&lt;br/&gt;
115	B . C&lt;br/&gt;
114	B . D&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_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i03fvj:</customfieldvalue>

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