<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 19:56:13 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-1700] Timeout waiting for task from writer started after heal after long isolation</title>
                <link>https://jira.opendaylight.org/browse/CONTROLLER-1700</link>
                <project id="10113" key="CONTROLLER">controller</project>
                    <description>&lt;p&gt;This symptom is very similar to &lt;a href=&quot;https://jira.opendaylight.org/browse/CONTROLLER-1674&quot; title=&quot;Timeout waiting for task in producer when moving shard leader&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CONTROLLER-1674&quot;&gt;&lt;del&gt;CONTROLLER-1674&lt;/del&gt;&lt;/a&gt; but happens in a different scenario.&lt;/p&gt;

&lt;p&gt;Still three writers (module-based shards, tell-based protocol) and leader is isolated, for more than request timeout. The isolated writer fails (with TimeoutException instead of RequestTimeoutException, that might be a separate bug or a cause of this one). Then the member is rejoined and it is verified each shard has a Leader and two Followers.&lt;/p&gt;

&lt;p&gt;At the end of the scenario, we start a writer on the rejoined node, and we expect it to finish writing without errors. Instead finishing after 67 seconds, TimeoutException is seen. The other two writers finish correctly.&lt;/p&gt;

&lt;p&gt;In a recent Sandbox test &lt;span class=&quot;error&quot;&gt;&amp;#91;0&amp;#93;&lt;/span&gt; (which failed to upload archive with logs) the response starts with:&lt;br/&gt;
{&quot;errors&quot;:{&quot;error&quot;:[{&quot;error-type&quot;:&quot;application&quot;,&quot;error-tag&quot;:&quot;operation-failed&quot;,&quot;error-message&quot;:&quot;Unexpected-exception&quot;,&quot;error-info&quot;:&quot;java.util.concurrent.TimeoutException: Timeout waiting for task.\n\tat com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:269)\n\tat com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:96)\n\tat com.google.common.util.concurrent.ForwardingFuture.get(ForwardingFuture.java:69)\n\tat org.opendaylight.yangtools.util.concurrent.MappingCheckedFuture.get(MappingCheckedFuture.java:85)\n\tat com.google.common.util.concurrent.AbstractCheckedFuture.checkedGet(AbstractCheckedFuture.java:107)\n\tat org.opendaylight.controller.clustering.it.provider.impl.WriteTransactionsHandler.ensureListExists(WriteTransactionsHandler.java:146)\n\tat org.opendaylight.controller.clustering.it.provider.impl.WriteTransactionsHandler.start(WriteTransactionsHandler.java:126)\n\tat org.opendaylight.controller.clustering.it.provider.MdsalLowLevelTestProvider.writeTransactions(MdsalLowLevelTestProvider.java:250)\n\tat org.opendaylight.yangtools.yang.binding.util.RpcMethodInvokerWithInput.invokeOn(RpcMethodInvokerWithInput.java:31)\n\tat&lt;/p&gt;


&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;0&amp;#93;&lt;/span&gt; &lt;a href=&quot;https://jenkins.opendaylight.org/sandbox/job/controller-csit-3node-clustering-only-carbon/6/robot/report/log.html#s1-s10-t3-k2-k25-k1-k8&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://jenkins.opendaylight.org/sandbox/job/controller-csit-3node-clustering-only-carbon/6/robot/report/log.html#s1-s10-t3-k2-k25-k1-k8&lt;/a&gt;&lt;/p&gt;</description>
                <environment>&lt;p&gt;Operating System: All&lt;br/&gt;
Platform: All&lt;/p&gt;</environment>
        <key id="26254">CONTROLLER-1700</key>
            <summary>Timeout waiting for task from writer started after heal after long isolation</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="vrpolak">Vratko Polak</reporter>
                        <labels>
                    </labels>
                <created>Mon, 29 May 2017 14:57:12 +0000</created>
                <updated>Tue, 25 Jul 2023 08:24:41 +0000</updated>
                            <resolved>Mon, 26 Jun 2017 09:27:50 +0000</resolved>
                                                                    <component>clustering</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>3</watches>
                                                                                                                <comments>
                            <comment id="52317" author="vrpolak" created="Mon, 5 Jun 2017 12:28:14 +0000"  >&lt;p&gt;The same behavior is now seen &lt;span class=&quot;error&quot;&gt;&amp;#91;1&amp;#93;&lt;/span&gt; in production Jenkins.&lt;/p&gt;

&lt;p&gt;Karaf.log &lt;span class=&quot;error&quot;&gt;&amp;#91;2&amp;#93;&lt;/span&gt; from the isolated member-1 shows two suspicious messages.&lt;br/&gt;
First, there was an additional UnreachableMember at 14:39:41,438 even though the test started isolation only at 14:39:41,475 (but the difference is small enough so that it might be explained by insufficient clock synchronization and asynchronous loging).&lt;/p&gt;

&lt;p&gt;Second, there was a failure from the second writer (started after rejoin). If it is an error in the writer, we can change the suite to use different list item id.&lt;/p&gt;

&lt;p&gt;2017-06-04 14:44:12,349 | WARN  | qtp1030155268-77 | WriteTransactionsHandler         | 256 - org.opendaylight.controller.samples.clustering-it-provider - 1.5.1.SNAPSHOT | Unable to ensure IdInts list for id: prefix-1 exists.&lt;br/&gt;
java.util.concurrent.TimeoutException: Timeout waiting for task.&lt;/p&gt;

&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;1&amp;#93;&lt;/span&gt; &lt;a href=&quot;https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-clustering-only-carbon/733/log.html.gz#s1-s28-t3-k2-k25-k1-k1&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-clustering-only-carbon/733/log.html.gz#s1-s28-t3-k2-k25-k1-k1&lt;/a&gt;&lt;br/&gt;
&lt;span class=&quot;error&quot;&gt;&amp;#91;2&amp;#93;&lt;/span&gt; &lt;a href=&quot;https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-clustering-only-carbon/733/odl1_karaf.log.gz&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-clustering-only-carbon/733/odl1_karaf.log.gz&lt;/a&gt;&lt;/p&gt;</comment>
                            <comment id="52318" author="rovarga" created="Mon, 5 Jun 2017 14:56:41 +0000"  >&lt;p&gt;The test failed because the previous test case ended up not cleaning up properly:&lt;/p&gt;

&lt;p&gt;2017-06-04 13:40:57,384 | ERROR | ult-dispatcher-7 | ClusterAdminRpcService           | 201 - org.opendaylight.controller.sal-cluster-admin-impl - 1.5.1.SNAPSHOT | Failed to remove replica for shard /(tag:opendaylight.org,2017:controller&lt;br/&gt;
:yang:lowlevel:target?revision=2017-02-15)id-ints&lt;br/&gt;
org.opendaylight.controller.cluster.datastore.exceptions.NoShardLeaderException: Shard member-1-shard-id-ints!-config currently has no leader. Try again later.&lt;br/&gt;
        at org.opendaylight.controller.cluster.datastore.shardmanager.ShardManager.createNoShardLeaderException(ShardManager.java:944)&lt;span class=&quot;error&quot;&gt;&amp;#91;199:org.opendaylight.controller.sal-distributed-datastore:1.5.1.SNAPSHOT&amp;#93;&lt;/span&gt;&lt;br/&gt;
        at org.opendaylight.controller.cluster.datastore.shardmanager.ShardManager.onShardNotInitializedTimeout(ShardManager.java:772)&lt;span class=&quot;error&quot;&gt;&amp;#91;199:org.opendaylight.controller.sal-distributed-datastore:1.5.1.SNAPSHOT&amp;#93;&lt;/span&gt;&lt;br/&gt;
        at org.opendaylight.controller.cluster.datastore.shardmanager.ShardManager.handleCommand(ShardManager.java:251)&lt;span class=&quot;error&quot;&gt;&amp;#91;199:org.opendaylight.controller.sal-distributed-datastore:1.5.1.SNAPSHOT&amp;#93;&lt;/span&gt;&lt;br/&gt;
        at org.opendaylight.controller.cluster.common.actor.AbstractUntypedPersistentActor.onReceiveCommand(AbstractUntypedPersistentActor.java:31)&lt;span class=&quot;error&quot;&gt;&amp;#91;192:org.opendaylight.controller.sal-clustering-commons:1.5.1.SNAPSHOT&amp;#93;&lt;/span&gt;&lt;br/&gt;
        at akka.persistence.UntypedPersistentActor.onReceive(PersistentActor.scala:170)&lt;span class=&quot;error&quot;&gt;&amp;#91;180:com.typesafe.akka.persistence:2.4.18&amp;#93;&lt;/span&gt;&lt;br/&gt;
        at org.opendaylight.controller.cluster.common.actor.MeteringBehavior.apply(MeteringBehavior.java:104)&lt;span class=&quot;error&quot;&gt;&amp;#91;192:org.opendaylight.controller.sal-clustering-commons:1.5.1.SNAPSHOT&amp;#93;&lt;/span&gt;&lt;br/&gt;
        at akka.actor.ActorCell$$anonfun$become$1.applyOrElse(ActorCell.scala:544)&lt;span class=&quot;error&quot;&gt;&amp;#91;173:com.typesafe.akka.actor:2.4.18&amp;#93;&lt;/span&gt;&lt;br/&gt;
        at akka.actor.Actor$class.aroundReceive(Actor.scala:502)&lt;span class=&quot;error&quot;&gt;&amp;#91;173:com.typesafe.akka.actor:2.4.18&amp;#93;&lt;/span&gt;&lt;br/&gt;
        at akka.persistence.UntypedPersistentActor.akka$persistence$Eventsourced$$super$aroundReceive(PersistentActor.scala:168)&lt;span class=&quot;error&quot;&gt;&amp;#91;180:com.typesafe.akka.persistence:2.4.18&amp;#93;&lt;/span&gt;&lt;br/&gt;
        at akka.persistence.Eventsourced$$anon$1.stateReceive(Eventsourced.scala:727)&lt;span class=&quot;error&quot;&gt;&amp;#91;180:com.typesafe.akka.persistence:2.4.18&amp;#93;&lt;/span&gt;&lt;br/&gt;
        at akka.persistence.Eventsourced$class.aroundReceive(Eventsourced.scala:183)&lt;span class=&quot;error&quot;&gt;&amp;#91;180:com.typesafe.akka.persistence:2.4.18&amp;#93;&lt;/span&gt;&lt;br/&gt;
        at akka.persistence.UntypedPersistentActor.aroundReceive(PersistentActor.scala:168)&lt;span class=&quot;error&quot;&gt;&amp;#91;180:com.typesafe.akka.persistence:2.4.18&amp;#93;&lt;/span&gt;&lt;br/&gt;
        at akka.actor.ActorCell.receiveMessage(ActorCell.scala:526)&lt;span class=&quot;error&quot;&gt;&amp;#91;173:com.typesafe.akka.actor:2.4.18&amp;#93;&lt;/span&gt;&lt;br/&gt;
        at akka.actor.ActorCell.invoke(ActorCell.scala:495)&lt;span class=&quot;error&quot;&gt;&amp;#91;173:com.typesafe.akka.actor:2.4.18&amp;#93;&lt;/span&gt;&lt;br/&gt;
        at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:257)&lt;span class=&quot;error&quot;&gt;&amp;#91;173:com.typesafe.akka.actor:2.4.18&amp;#93;&lt;/span&gt;&lt;br/&gt;
        at akka.dispatch.Mailbox.run(Mailbox.scala:224)&lt;span class=&quot;error&quot;&gt;&amp;#91;173:com.typesafe.akka.actor:2.4.18&amp;#93;&lt;/span&gt;&lt;br/&gt;
        at akka.dispatch.Mailbox.exec(Mailbox.scala:234)&lt;span class=&quot;error&quot;&gt;&amp;#91;173:com.typesafe.akka.actor:2.4.18&amp;#93;&lt;/span&gt;&lt;br/&gt;
        at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)&lt;span class=&quot;error&quot;&gt;&amp;#91;169:org.scala-lang.scala-library:2.11.11.v20170413-090219-8a413ba7cc&amp;#93;&lt;/span&gt;&lt;br/&gt;
        at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)&lt;span class=&quot;error&quot;&gt;&amp;#91;169:org.scala-lang.scala-library:2.11.11.v20170413-090219-8a413ba7cc&amp;#93;&lt;/span&gt;&lt;br/&gt;
        at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)&lt;span class=&quot;error&quot;&gt;&amp;#91;169:org.scala-lang.scala-library:2.11.11.v20170413-090219-8a413ba7cc&amp;#93;&lt;/span&gt;&lt;br/&gt;
        at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)&lt;span class=&quot;error&quot;&gt;&amp;#91;169:org.scala-lang.scala-library:2.11.11.v20170413-090219-8a413ba7cc&amp;#93;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;Which means the frontend was instantiated multiple times:&lt;/p&gt;

&lt;p&gt;2017-06-04 13:40:57,486 | INFO  | h for user karaf | command                          | 265 - org.apache.karaf.log.command - 3.0.8 | ROBOT MESSAGE: Starting test Remove_Follower_Prefix_Shard_Replica_And_Add_It_Back&lt;br/&gt;
2017-06-04 13:41:17,996 | INFO  | h for user karaf | command                          | 265 - org.apache.karaf.log.command - 3.0.8 | ROBOT MESSAGE: Starting test Produce_Transactions_One_Node_Leader&lt;br/&gt;
2017-06-04 13:41:19,125 | ERROR | lt-dispatcher-26 | ClientActorBehavior              | 197 - org.opendaylight.controller.cds-access-client - 1.1.1.SNAPSHOT | member-1-frontend-datastore-Shard-id-ints!: current generation ClientIdentifier&lt;/p&gt;
{frontend=member-1-frontend-datastore-Shard-id-ints!, generation=0}
&lt;p&gt; has been superseded&lt;br/&gt;
org.opendaylight.controller.cluster.access.concepts.RetiredGenerationException: Originating generation was superseded by 1&lt;br/&gt;
        at org.opendaylight.controller.cluster.datastore.Shard.getFrontend(Shard.java:402)&lt;span class=&quot;error&quot;&gt;&amp;#91;199:org.opendaylight.controller.sal-distributed-datastore:1.5.1.SNAPSHOT&amp;#93;&lt;/span&gt;&lt;br/&gt;
        at org.opendaylight.controller.cluster.datastore.Shard.handleRequest(Shard.java:466)&lt;span class=&quot;error&quot;&gt;&amp;#91;199:org.opendaylight.controller.sal-distributed-datastore:1.5.1.SNAPSHOT&amp;#93;&lt;/span&gt;&lt;br/&gt;
        at org.opendaylight.controller.cluster.datastore.Shard.handleNonRaftCommand(Shard.java:293)&lt;span class=&quot;error&quot;&gt;&amp;#91;199:org.opendaylight.controller.sal-distributed-datastore:1.5.1.SNAPSHOT&amp;#93;&lt;/span&gt;&lt;br/&gt;
        at org.opendaylight.controller.cluster.raft.RaftActor.handleCommand(RaftActor.java:270)&lt;span class=&quot;error&quot;&gt;&amp;#91;193:org.opendaylight.controller.sal-akka-raft:1.5.1.SNAPSHOT&amp;#93;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;further down it lead to a failure to bind the producer:&lt;/p&gt;

&lt;p&gt;2017-06-04 13:43:20,754 | INFO  | h for user karaf | command                          | 265 - org.apache.karaf.log.command - 3.0.8 | ROBOT MESSAGE: Starting test Produce_Transactions&lt;br/&gt;
2017-06-04 13:43:22,169 | ERROR | tp1878068729-321 | ContainerResponse                | 68 - com.sun.jersey.jersey-server - 1.17.0 | The RuntimeException could not be mapped to a response, re-throwing to the HTTP container&lt;br/&gt;
java.lang.IllegalArgumentException: Subtree DOMDataTreeIdentifier{datastore=CONFIGURATION, root=/(tag:opendaylight.org,2017:controller:yang:lowlevel:target?revision=2017-02-15)id-ints/id-int/id-int[&lt;/p&gt;
{(tag:opendaylight.org,2017:controller:yang:lowlevel:target?revision=2017-02-15)id=prefix-1}
&lt;p&gt;]} is attached to producer org.opendaylight.mdsal.dom.broker.ShardedDOMDataTreeProducer@517147f9&lt;br/&gt;
        at com.google.common.base.Preconditions.checkArgument(Preconditions.java:145)&lt;span class=&quot;error&quot;&gt;&amp;#91;57:com.google.guava:18.0.0&amp;#93;&lt;/span&gt;&lt;br/&gt;
        at org.opendaylight.mdsal.dom.broker.ShardedDOMDataTree.createProducer(ShardedDOMDataTree.java:144)&lt;br/&gt;
        at org.opendaylight.controller.cluster.sharding.DistributedShardedDOMDataTree.createProducer(DistributedShardedDOMDataTree.java:302)&lt;br/&gt;
        at Proxy6a0a520a_b713_4500_a5c7_f00e5cc1496b.createProducer(Unknown Source)&lt;br/&gt;
        at Proxycb991ad6_d042_4d13_a04c_2afd2767f9f4.createProducer(Unknown Source)&lt;br/&gt;
        at org.opendaylight.controller.clustering.it.provider.impl.ProduceTransactionsHandler.fillInitialList(ProduceTransactionsHandler.java:134)&lt;br/&gt;
        at org.opendaylight.controller.clustering.it.provider.impl.ProduceTransactionsHandler.start(ProduceTransactionsHandler.java:115)&lt;br/&gt;
        at org.opendaylight.controller.clustering.it.provider.MdsalLowLevelTestProvider.produceTransactions(MdsalLowLevelTestProvider.java:562)&lt;/p&gt;</comment>
                            <comment id="52319" author="tcere" created="Tue, 6 Jun 2017 13:52:23 +0000"  >&lt;p&gt;(In reply to Robert Varga from comment #2)&lt;/p&gt;

&lt;p&gt;&amp;gt; Which means the frontend was instantiated multiple times:&lt;br/&gt;
&amp;gt; &lt;/p&gt;

&lt;p&gt;I checked the logs, and I dont see how the frontend can be instantiated twice.&lt;br/&gt;
Only place where the datastoreClient is created when we plug the shard frontend into the ShardingService and this only happens in the create-shard rpc.&lt;br/&gt;
When the replica is removed the frontend still remains and should reconnect, but both of the removals fail because there is no shard leader present.&lt;/p&gt;

&lt;p&gt;Once the removal of the replica fails the test doesnt attempt to add the replica back, but even if it did, when you add a replica of a shard you dont create new frontend since this is completely separated from the layer that handles the interaction with the ShardingService.&lt;/p&gt;</comment>
                            <comment id="52320" author="vrpolak" created="Mon, 12 Jun 2017 11:51:31 +0000"  >&lt;p&gt;A symptom similar to this (except the restconf call did not finish, instead of returning TimeoutException) happened together with &lt;a href=&quot;https://jira.opendaylight.org/browse/CONTROLLER-1708&quot; title=&quot;write-transactions does not respond (no evident reason)&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CONTROLLER-1708&quot;&gt;&lt;del&gt;CONTROLLER-1708&lt;/del&gt;&lt;/a&gt; and &lt;a href=&quot;https://jira.opendaylight.org/browse/CONTROLLER-1718&quot; title=&quot;Binary data in karaf log: transaction not tracked in&quot; class=&quot;issue-link&quot; data-issue-key=&quot;CONTROLLER-1718&quot;&gt;&lt;del&gt;CONTROLLER-1718&lt;/del&gt;&lt;/a&gt; in a recent RelEng test &lt;span class=&quot;error&quot;&gt;&amp;#91;3&amp;#93;&lt;/span&gt;.&lt;/p&gt;

&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;3&amp;#93;&lt;/span&gt; &lt;a href=&quot;https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-clustering-only-carbon/739/log.html.gz#s1-s28-t3-k2-k25-k1-k8&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://logs.opendaylight.org/releng/jenkins092/controller-csit-3node-clustering-only-carbon/739/log.html.gz#s1-s28-t3-k2-k25-k1-k8&lt;/a&gt;&lt;/p&gt;</comment>
                    </comments>
                <issuelinks>
                            <issuelinktype id="10000">
                    <name>Blocks</name>
                                                                <inwardlinks description="is blocked by">
                                        <issuelink>
            <issuekey id="26219">CONTROLLER-1665</issuekey>
        </issuelink>
            <issuelink>
            <issuekey id="26241">CONTROLLER-1687</issuekey>
        </issuelink>
                            </inwardlinks>
                                    </issuelinktype>
                    </issuelinks>
                <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>8562</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=8562]]></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_10000" key="com.pyxis.greenhopper.jira:gh-lexo-rank">
                        <customfieldname>Rank</customfieldname>
                        <customfieldvalues>
                            <customfieldvalue>0|i02s6v:</customfieldvalue>

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