<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:08:59 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>[MDSAL-197] Switch connection bounce results in wrong ownership change in Singleton</title>
                <link>https://jira.opendaylight.org/browse/MDSAL-197</link>
                <project id="10137" key="MDSAL">mdsal</project>
                    <description>&lt;p&gt;In Carbon, sometimes, when switch is disconnected and reconnected with very small delay between these actions, it&apos;s role is incorrectly set (should be MASTER, but is SLAVE).&lt;/p&gt;

&lt;p&gt;Reproduction steps (from Luis from bug &lt;a href=&quot;https://bugs.opendaylight.org/show_bug.cgi?id=6672):&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://bugs.opendaylight.org/show_bug.cgi?id=6672):&lt;/a&gt;&lt;br/&gt;
1) start mininet 1 switch (s1) pointing to any of the cluster instances (e.g. 10.13.11.207)&lt;br/&gt;
2) Run the following script in the mininet system to bounce connection quickly:&lt;/p&gt;

&lt;p&gt;#!/bin/bash&lt;br/&gt;
sudo ovs-vsctl del-controller s1&lt;br/&gt;
sleep 0.2&lt;br/&gt;
sudo ovs-vsctl set-controller s1 &quot;tcp:192.168.0.101&quot;&lt;/p&gt;

&lt;p&gt;In local cluster test, I did step 2 twice. First time, role MASTER was successfully set, but second time, role was SLAVE, what is incorrect.&lt;/p&gt;

&lt;p&gt;I attached logs from my local testing from node 10.13.11.207.&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: Linux&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="27019">MDSAL-197</key>
            <summary>Switch connection bounce results in wrong ownership change in Singleton</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="vdemcak@cisco.com">Vaclav Demcak</assignee>
                                    <reporter username="tomas.slusny@pantheon.tech">Tomas Slusny</reporter>
                        <labels>
                    </labels>
                <created>Tue, 13 Sep 2016 15:57:05 +0000</created>
                <updated>Fri, 9 Mar 2018 18:00:17 +0000</updated>
                            <resolved>Mon, 14 Nov 2016 12:06:05 +0000</resolved>
                                                                        <due></due>
                            <votes>0</votes>
                                    <watches>8</watches>
                                                                                                                <comments>
                            <comment id="54476" author="tomas.slusny@pantheon.tech" created="Tue, 13 Sep 2016 15:57:05 +0000"  >&lt;p&gt;Attachment 1722_10.13.11.207.log has been added with description: Karaf log from 10.13.11.207 cluster node&lt;/p&gt;</comment>
                            <comment id="54463" author="tpantelis" created="Thu, 15 Sep 2016 18:03:33 +0000"  >&lt;p&gt;I see this ex:&lt;/p&gt;

&lt;p&gt;2016-09-13 17:21:40,055 | ERROR | ult-dispatcher-4 | ClusterSingletonServiceGroupImpl | 169 - org.opendaylight.mdsal.singleton-dom-impl - 2.2.0.SNAPSHOT | Unexpected exception state for service Provider openflow:1 in LostLeadership&lt;br/&gt;
com.google.common.base.VerifyException&lt;br/&gt;
	at com.google.common.base.Verify.verify(Verify.java:98)&lt;span class=&quot;error&quot;&gt;&amp;#91;70:com.google.guava:18.0.0&amp;#93;&lt;/span&gt;&lt;br/&gt;
	at org.opendaylight.mdsal.singleton.dom.impl.ClusterSingletonServiceGroupImpl.lostOwnership(ClusterSingletonServiceGroupImpl.java:308)&lt;span class=&quot;error&quot;&gt;&amp;#91;169:org.opendaylight.mdsal.singleton-dom-impl:2.2.0.SNAPSHOT&amp;#93;&lt;/span&gt;&lt;br/&gt;
	at org.opendaylight.mdsal.singleton.dom.impl.ClusterSingletonServiceGroupImpl.ownershipChanged(ClusterSingletonServiceGroupImpl.java:213)&lt;span class=&quot;error&quot;&gt;&amp;#91;169:org.opendaylight.mdsal.singleton-dom-impl:2.2.0.SNAPSHOT&amp;#93;&lt;/span&gt;&lt;br/&gt;
	at org.opendaylight.mdsal.singleton.dom.impl.AbstractClusterSingletonServiceProviderImpl.ownershipChanged(AbstractClusterSingletonServiceProviderImpl.java:145)&lt;span class=&quot;error&quot;&gt;&amp;#91;169:org.opendaylight.mdsal.singleton-dom-impl:2.2.0.SNAPSHOT&amp;#93;&lt;/span&gt;&lt;br/&gt;
	at org.opendaylight.mdsal.singleton.dom.impl.DOMClusterSingletonServiceProviderImpl.ownershipChanged(DOMClusterSingletonServiceProviderImpl.java:23)&lt;span class=&quot;error&quot;&gt;&amp;#91;169:org.opendaylight.mdsal.singleton-dom-impl:2.2.0.SNAPSHOT&amp;#93;&lt;/span&gt;&lt;br/&gt;
	at org.opendaylight.controller.cluster.datastore.entityownership.EntityOwnershipListenerActor.onEntityOwnershipChanged(EntityOwnershipListenerActor.java:46)&lt;span class=&quot;error&quot;&gt;&amp;#91;205:org.opendaylight.controller.sal-distributed-datastore:1.5.0.SNAPSHOT&amp;#93;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;It had local ownership of the ServiceEntityType and AsycnCloseEntityType. Then it got an unregister from the app:&lt;/p&gt;

&lt;p&gt;2016-09-13 17:21:40,031 | DEBUG | on-dispatcher-52 | ClusterSingletonServiceGroupImpl | 169 - org.opendaylight.mdsal.singleton-dom-impl - 2.2.0.SNAPSHOT | UnregisterService method call for ClusterSingletonServiceGroup openflow:1&lt;/p&gt;

&lt;p&gt;2016-09-13 17:21:40,036 | DEBUG | on-dispatcher-52 | ClusterSingletonServiceGroupImpl | 169 - org.opendaylight.mdsal.singleton-dom-impl - 2.2.0.SNAPSHOT | Close method for service Provider openflow:1&lt;/p&gt;

&lt;p&gt;This closes the serviceEntityCandidateReg and sets it to null.&lt;/p&gt;

&lt;p&gt;Then it got the LOCAL_OWNERSHIP_LOST_NEW_OWNER notification for the ServiceEntityType:&lt;/p&gt;

&lt;p&gt;2016-09-13 17:21:40,046 | DEBUG | ult-dispatcher-4 | sterSingletonServiceProviderImpl | 169 - org.opendaylight.mdsal.singleton-dom-impl - 2.2.0.SNAPSHOT | Ownership change for ClusterSingletonService Provider DOMEntityOwnershipChange [entity=DOMEntity [type=org.opendaylight.mdsal.ServiceEntityType, id=/(urn:opendaylight:params:xml:ns:yang:mdsal:core:general-entity?revision=2015-09-30)entity/entity[&lt;/p&gt;
{(urn:opendaylight:params:xml:ns:yang:mdsal:core:general-entity?revision=2015-09-30)name=openflow:1}
&lt;p&gt;]], state=LOCAL_OWNERSHIP_LOST_NEW_OWNER &lt;span class=&quot;error&quot;&gt;&amp;#91;wasOwner=true, isOwner=false, hasOwner=true&amp;#93;&lt;/span&gt;, inJeopardy=false]&lt;/p&gt;

&lt;p&gt;This leads to the call to lostOwnership which fails this verify on line 308 b/c the serviceEntityCandidateReg was already nulled out:&lt;/p&gt;

&lt;p&gt;Verify.verify(serviceEntityCandidateReg != null);&lt;/p&gt;

&lt;p&gt;There&apos;s either logic flaw somewhere else or the code is being unnecessarily paranoid in verifying serviceEntityCandidateReg != null.&lt;/p&gt;</comment>
                            <comment id="54464" author="vdemcak@cisco.com" created="Wed, 28 Sep 2016 10:33:04 +0000"  >&lt;p&gt;&lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/46175/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/46175/&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="54465" author="tomas.slusny@pantheon.tech" created="Fri, 30 Sep 2016 08:40:09 +0000"  >&lt;p&gt;So I was testing connection bounce again on patch &lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/46175/7&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/46175/7&lt;/a&gt; above (also, with controller on this patch &lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/45638/3&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/45638/3&lt;/a&gt; by Tom Pantelis) and eveything is working almost great, except that sometimes I see VerifyException when device is closing in tryToTakeOwnership method. I attached full log from main node. So I think that sometimes when in closing state, also TryToTakeOwnership is called, so serviceEntityCandidateReg can be null there too.&lt;/p&gt;</comment>
                            <comment id="54477" author="tomas.slusny@pantheon.tech" created="Fri, 30 Sep 2016 08:40:09 +0000"  >&lt;p&gt;Attachment 0841_10.13.11.207.log has been added with description: TryToTakeOwnership VerifyException in closing&lt;/p&gt;</comment>
                            <comment id="54466" author="tomas.slusny@pantheon.tech" created="Fri, 30 Sep 2016 09:06:13 +0000"  >&lt;p&gt;After further testing, this VerifyException is also appearing in TakeOwnership on Verify.verify(serviceEntityCandidateReg != null); when in closing.&lt;/p&gt;</comment>
                            <comment id="54467" author="vdemcak@cisco.com" created="Fri, 30 Sep 2016 14:55:27 +0000"  >&lt;p&gt;It looks like you don&apos;t wait correctly for a closing process. Or I&apos;m not guarding a closing process correctly. Logs show, you&apos;re closing your service in same time as registration. So EOS response first registration role but your service is in a closing state. Propably a verification exception is not here the right approach. I have to think about it. Could you describe here exactly your steps for closing / re-registration process from your code please?&lt;/p&gt;</comment>
                            <comment id="54468" author="vdemcak@cisco.com" created="Tue, 11 Oct 2016 12:29:45 +0000"  >&lt;p&gt;master&lt;br/&gt;
&lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/46175/14&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/46175/14&lt;/a&gt;&lt;br/&gt;
stable boron cherry-pick&lt;br/&gt;
&lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/46761/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/46761/&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="54469" author="tomas.slusny@pantheon.tech" created="Thu, 13 Oct 2016 16:10:17 +0000"  >&lt;p&gt;So I was testing these problems again with patch by Vaclav, what is posted above, and everything is now working fine, so closing this issue.&lt;/p&gt;</comment>
                            <comment id="54470" author="bertrandlow" created="Tue, 18 Oct 2016 23:09:58 +0000"  >&lt;p&gt;Hi Vaclav and Tomas,&lt;/p&gt;

&lt;p&gt;the cherry-pick to Boron (&lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/46761/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/46761/&lt;/a&gt;) is not passing the distribution-check and it appears to be due to this error:&lt;/p&gt;

&lt;p&gt;2016-10-18 22:22:53,853 | ERROR | config-pusher    | ConfigTransactionControllerImpl  | 128 - org.opendaylight.controller.config-manager - 0.5.1.SNAPSHOT | Commit failed on ModuleIdentifier&lt;/p&gt;
{factoryName=&apos;bgp-reachability-ipv4&apos;, instanceName=&apos;example-ipv4-topology&apos;}
&lt;p&gt; in transaction TransactionIdentifier&lt;/p&gt;
{name=&apos;ConfigTransaction-282-284&apos;}
&lt;p&gt;java.lang.RuntimeException: com.google.common.base.VerifyException&lt;br/&gt;
	at org.opendaylight.mdsal.singleton.dom.impl.ClusterSingletonServiceGroupImpl.registerService(ClusterSingletonServiceGroupImpl.java:170)&lt;br/&gt;
	at org.opendaylight.mdsal.singleton.dom.impl.AbstractClusterSingletonServiceProviderImpl.registerClusterSingletonService(AbstractClusterSingletonServiceProviderImpl.java:106)&lt;br/&gt;
	at Proxyd030c118_68d9_4469_aef9_a99fb46b9175.registerClusterSingletonService(Unknown Source)&lt;br/&gt;
	at Proxy9705fcab_39eb_4b61_ac74_0c4dab9a7c4c.registerClusterSingletonService(Unknown Source)&lt;/p&gt;

&lt;p&gt;This seems different from the causes tracked below (lostleadership and takeownership) - any ideas why the patch is passing in master but not in Boron?&lt;/p&gt;

&lt;p&gt;If I understand correctly, the fix for &lt;a href=&quot;https://jira.opendaylight.org/browse/MDSAL-197&quot; title=&quot;Switch connection bounce results in wrong ownership change in Singleton&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MDSAL-197&quot;&gt;&lt;del&gt;MDSAL-197&lt;/del&gt;&lt;/a&gt; will have to be merged into boron before the fix for &lt;a href=&quot;https://jira.opendaylight.org/browse/OPNFLWPLUG-767&quot; title=&quot;Switch connection bounce generates wrong entity owner in cluster env&quot; class=&quot;issue-link&quot; data-issue-key=&quot;OPNFLWPLUG-767&quot;&gt;&lt;del&gt;OPNFLWPLUG-767&lt;/del&gt;&lt;/a&gt; / 5271 (which is awaiting Luis verification) can be merged.&lt;/p&gt;

&lt;p&gt;Thanks&lt;/p&gt;</comment>
                            <comment id="54471" author="vdemcak@cisco.com" created="Wed, 19 Oct 2016 12:10:01 +0000"  >&lt;p&gt;(In reply to Bertrand Low from comment #8)&lt;br/&gt;
&amp;gt; Hi Vaclav and Tomas,&lt;br/&gt;
&amp;gt; &lt;br/&gt;
&amp;gt; the cherry-pick to Boron (&lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/46761/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/46761/&lt;/a&gt;) is&lt;br/&gt;
&amp;gt; not passing the distribution-check and it appears to be due to this error:&lt;br/&gt;
&amp;gt; &lt;br/&gt;
&amp;gt; 2016-10-18 22:22:53,853 | ERROR | config-pusher    |&lt;br/&gt;
&amp;gt; ConfigTransactionControllerImpl  | 128 -&lt;br/&gt;
&amp;gt; org.opendaylight.controller.config-manager - 0.5.1.SNAPSHOT | Commit failed&lt;br/&gt;
&amp;gt; on ModuleIdentifier&lt;/p&gt;
{factoryName=&apos;bgp-reachability-ipv4&apos;,
&amp;gt; instanceName=&apos;example-ipv4-topology&apos;}
&lt;p&gt; in transaction&lt;br/&gt;
&amp;gt; TransactionIdentifier&lt;/p&gt;
{name=&apos;ConfigTransaction-282-284&apos;}
&lt;p&gt;&amp;gt; java.lang.RuntimeException: com.google.common.base.VerifyException&lt;br/&gt;
&amp;gt; 	at&lt;br/&gt;
&amp;gt; org.opendaylight.mdsal.singleton.dom.impl.ClusterSingletonServiceGroupImpl.&lt;br/&gt;
&amp;gt; registerService(ClusterSingletonServiceGroupImpl.java:170)&lt;br/&gt;
&amp;gt; 	at&lt;br/&gt;
&amp;gt; org.opendaylight.mdsal.singleton.dom.impl.&lt;br/&gt;
&amp;gt; AbstractClusterSingletonServiceProviderImpl.&lt;br/&gt;
&amp;gt; registerClusterSingletonService(AbstractClusterSingletonServiceProviderImpl.&lt;br/&gt;
&amp;gt; java:106)&lt;br/&gt;
&amp;gt; 	at&lt;br/&gt;
&amp;gt; Proxyd030c118_68d9_4469_aef9_a99fb46b9175.&lt;br/&gt;
&amp;gt; registerClusterSingletonService(Unknown Source)&lt;br/&gt;
&amp;gt; 	at&lt;br/&gt;
&amp;gt; Proxy9705fcab_39eb_4b61_ac74_0c4dab9a7c4c.&lt;br/&gt;
&amp;gt; registerClusterSingletonService(Unknown Source)&lt;br/&gt;
&amp;gt; &lt;br/&gt;
&amp;gt; This seems different from the causes tracked below (lostleadership and&lt;br/&gt;
&amp;gt; takeownership) - any ideas why the patch is passing in master but not in&lt;br/&gt;
&amp;gt; Boron?&lt;br/&gt;
&amp;gt; &lt;br/&gt;
&amp;gt; If I understand correctly, the fix for &lt;a href=&quot;https://jira.opendaylight.org/browse/MDSAL-197&quot; title=&quot;Switch connection bounce results in wrong ownership change in Singleton&quot; class=&quot;issue-link&quot; data-issue-key=&quot;MDSAL-197&quot;&gt;&lt;del&gt;MDSAL-197&lt;/del&gt;&lt;/a&gt; will have to be merged into&lt;br/&gt;
&amp;gt; boron before the fix for &lt;a href=&quot;https://jira.opendaylight.org/browse/OPNFLWPLUG-767&quot; title=&quot;Switch connection bounce generates wrong entity owner in cluster env&quot; class=&quot;issue-link&quot; data-issue-key=&quot;OPNFLWPLUG-767&quot;&gt;&lt;del&gt;OPNFLWPLUG-767&lt;/del&gt;&lt;/a&gt; / 5271 (which is awaiting Luis&lt;br/&gt;
&amp;gt; verification) can be merged.&lt;br/&gt;
&amp;gt; &lt;br/&gt;
&amp;gt; Thanks&lt;/p&gt;

&lt;p&gt;yes, because &lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/46761/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/46761/&lt;/a&gt; pacht indirectly depends on &lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/47018/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/47018/&lt;/a&gt; , but it is a part of diferent issue.&lt;/p&gt;</comment>
                            <comment id="54472" author="vinh.nguyen@hcl.com" created="Wed, 19 Oct 2016 17:21:02 +0000"  >&lt;p&gt;Hi Vaclat, the &lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/46761/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/46761/&lt;/a&gt; patch indirectly depends on &lt;a href=&quot;https://git.opendaylight.org/gerrit/#/c/47018/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://git.opendaylight.org/gerrit/#/c/47018/&lt;/a&gt;. However there seems to be a circular dependency between the two patches since the 47018 mentions that it indirectly depends on the 46761. Is that correct?&lt;/p&gt;

&lt;p&gt;Do you have any idea when the above patches will be merged?&lt;br/&gt;
Thanks&lt;/p&gt;</comment>
                            <comment id="54473" author="rovarga" created="Wed, 26 Oct 2016 10:16:08 +0000"  >&lt;p&gt;Reopen as the issue has not been merged yet.&lt;/p&gt;</comment>
                            <comment id="54474" author="rovarga" created="Wed, 26 Oct 2016 10:18:32 +0000"  >&lt;p&gt;This is still waiting for merge. Boron is throttled for SR1 release, so unless this issue becomes a blocker for SR1, it will need to be postponed to SR2.&lt;/p&gt;

&lt;p&gt;Raising to blocker for SR2. If you feel it needs to be delivered in SR1, feel free to retarget and notify release manager of a blocker.&lt;/p&gt;</comment>
                            <comment id="54475" author="martin.ciglan" created="Mon, 7 Nov 2016 15:20:22 +0000"  >&lt;p&gt;Hi all&lt;/p&gt;

&lt;p&gt;Having Boron-SR1 released, can we move on with this issue? Thank you.&lt;/p&gt;

&lt;p&gt;   Martin&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                            <outwardlinks description="blocks">
                                        <issuelink>
            <issuekey id="23780">BGPCEP-540</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="27884">OPNFLWPLUG-616</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="28027">OPNFLWPLUG-759</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="28035">OPNFLWPLUG-767</issuekey>
        </issuelink>
                            </outwardlinks>
                                                        </issuelinktype>
                    </issuelinks>
                <attachments>
                            <attachment id="13817" name="0841_10.13.11.207.log" size="917504" author="tomas.slusny@pantheon.tech" created="Fri, 30 Sep 2016 08:40:09 +0000"/>
                            <attachment id="13816" name="1722_10.13.11.207.log" size="442460" author="tomas.slusny@pantheon.tech" created="Tue, 13 Sep 2016 15:57:05 +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>6710</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=6710]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                            <customfield id="customfield_10206" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>Issue Type</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10300"><![CDATA[Bug]]></customfieldvalue>

                        </customfieldvalues>
                    </customfield>
                                                                                                                                                                                                                                                                                                                                                        <customfield id="customfield_10204" key="com.atlassian.jira.plugin.system.customfieldtypes:select">
                        <customfieldname>ODL SR Target Milestone</customfieldname>
                        <customfieldvalues>
                                <customfieldvalue key="10335"><![CDATA[Boron-2]]></customfieldvalue>

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

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