<!-- 
RSS generated by JIRA (8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d) at Wed Feb 07 20:33:20 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>[OPNFLWPLUG-765] No local or remote implementation available for OF plugin&apos;s RPC</title>
                <link>https://jira.opendaylight.org/browse/OPNFLWPLUG-765</link>
                <project id="10155" key="OPNFLWPLUG">OpenFlowPlugin</project>
                    <description>&lt;p&gt;The issue happened in the CSIT for the stable/boron branches on 09/07.&lt;br/&gt;
I&apos;ve never seen this failure before, so I&apos;m gussing this is a regression which was introduced recently.&lt;/p&gt;

&lt;p&gt;&lt;span class=&quot;error&quot;&gt;&amp;#91;VTN CSIT&amp;#93;&lt;/span&gt;&lt;/p&gt;
&lt;ul&gt;
	&lt;li&gt;build #66 - &lt;a href=&quot;https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-3node-manager-all-boron/66/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-3node-manager-all-boron/66/&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;


&lt;p&gt;The test failure was that the VTN feature failed to control OpenFlow switches.&lt;br/&gt;
That&apos;s because the implmentation was not available for OF plugin&apos;s RPC.&lt;/p&gt;

&lt;p&gt;I&apos;ve seen the following log messages with the issue.&lt;/p&gt;

&lt;p&gt;2016-09-07 13:00:43,142 | WARN (snip) org.opendaylight.controller.sal-remoterpc-connector - 1.4.0.SNAPSHOT | Timed out finding routers for RouteIdentifierImpl{context=null, type=(urn:opendaylight:packet:service?revision=2013-07-09)transmit-packet, route=/(urn:opendaylight:inventory?revision=2013-08-19)nodes/node/node[&lt;/p&gt;
{(urn:opendaylight:inventory?revision=2013-08-19)id=openflow:1}
&lt;p&gt;]}&lt;/p&gt;

&lt;p&gt;2016-09-07 13:00:43,189 | WARN (snip)  org.opendaylight.controller.sal-remoterpc-connector - 1.4.0.SNAPSHOT | Timed out finding routers for RouteIdentifierImpl{context=null, type=(urn:opendaylight:flow:service?revision=2013-08-19)remove-flow, route=/(urn:opendaylight:inventory?revision=2013-08-19)nodes/node/node[&lt;/p&gt;
{(urn:opendaylight:inventory?revision=2013-08-19)id=openflow:2}
&lt;p&gt;]}&lt;/p&gt;

&lt;p&gt;2016-09-07 13:00:43,189 | WARN (snip) org.opendaylight.controller.sal-remoterpc-connector - 1.4.0.SNAPSHOT | Timed out finding routers for RouteIdentifierImpl{context=null, type=(urn:opendaylight:flow:transaction?revision=2015-03-04)send-barrier, route=/(urn:opendaylight:inventory?revision=2013-08-19)nodes/node/node[&lt;/p&gt;
{(urn:opendaylight:inventory?revision=2013-08-19)id=openflow:2}
&lt;p&gt;]}&lt;/p&gt;

&lt;p&gt;2016-09-07 13:00:43,190 | ERROR (snip) org.opendaylight.vtn.manager.implementation - 0.5.0.SNAPSHOT | send-barrier RPC has thrown an exception: node=openflow:2&lt;br/&gt;
org.opendaylight.controller.md.sal.dom.api.DOMRpcImplementationNotAvailableException: No local or remote implementation available for rpc AbsoluteSchemaPath&lt;/p&gt;
{path=[(urn:opendaylight:flow:transaction?revision=2015-03-04)send-barrier]}
&lt;p&gt;	at org.opendaylight.controller.remote.rpc.RemoteRpcImplementation$1.onComplete(RemoteRpcImplementation.java:66)&lt;span class=&quot;error&quot;&gt;&amp;#91;167:org.opendaylight.controller.sal-remoterpc-connector:1.4.0.SNAPSHOT&amp;#93;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;2016-09-07 13:00:43,190 | ERROR (snip) org.opendaylight.vtn.manager.implementation - 0.5.0.SNAPSHOT | Failed to remove VTN flows in openflow:2&lt;br/&gt;
org.opendaylight.vtn.manager.VTNException: No local or remote implementation available for rpc AbsoluteSchemaPath&lt;/p&gt;
{path=[(urn:opendaylight:flow:service?revision=2013-08-19)remove-flow]}
&lt;p&gt;    (snip)&lt;br/&gt;
Caused by: org.opendaylight.controller.md.sal.dom.api.DOMRpcImplementationNotAvailableException: No local or remote implementation available for rpc AbsoluteSchemaPath&lt;/p&gt;
{path=[(urn:opendaylight:flow:service?revision=2013-08-19)remove-flow]}
&lt;p&gt;	at org.opendaylight.controller.remote.rpc.RemoteRpcImplementation$1.onComplete(RemoteRpcImplementation.java:66)&lt;span class=&quot;error&quot;&gt;&amp;#91;167:org.opendaylight.controller.sal-remoterpc-connector:1.4.0.SNAPSHOT&amp;#93;&lt;/span&gt;&lt;br/&gt;
	at org.opendaylight.controller.remote.rpc.RemoteRpcImplementation$1.onComplete(RemoteRpcImplementation.java:56)&lt;span class=&quot;error&quot;&gt;&amp;#91;167:org.opendaylight.controller.sal-remoterpc-connector:1.4.0.SNAPSHOT&amp;#93;&lt;/span&gt;&lt;/p&gt;

&lt;p&gt;You can find the complete log messages in the following location:&lt;br/&gt;
&lt;a href=&quot;https://logs.opendaylight.org/releng/jenkins092/vtn-csit-3node-manager-all-boron/66/archives/odl3_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/vtn-csit-3node-manager-all-boron/66/archives/odl3_karaf.log.gz&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="28033">OPNFLWPLUG-765</key>
            <summary>No local or remote implementation available for OF plugin&apos;s RPC</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="10003">Cannot Reproduce</resolution>
                                        <assignee username="Hideyuki1985">Hideyuki Tai</assignee>
                                    <reporter username="Hideyuki1985">Hideyuki Tai</reporter>
                        <labels>
                    </labels>
                <created>Thu, 8 Sep 2016 00:25:50 +0000</created>
                <updated>Mon, 27 Sep 2021 09:01:53 +0000</updated>
                            <resolved>Tue, 25 Oct 2016 22:39:26 +0000</resolved>
                                                                    <component>General</component>
                        <due></due>
                            <votes>0</votes>
                                    <watches>5</watches>
                                                                                                                <comments>
                            <comment id="58281" author="tomas.slusny@pantheon.tech" created="Fri, 9 Sep 2016 08:21:03 +0000"  >&lt;p&gt;This issue is similar to one of issues in &lt;a href=&quot;https://bugs.opendaylight.org/show_bug.cgi?id=6176&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://bugs.opendaylight.org/show_bug.cgi?id=6176&lt;/a&gt;, and that was when logging was not set to ERROR, then logger was logging too much data and was blocking other threads.&lt;br/&gt;
But Luis already fixed this in tests and changed log level to ERROR, and also next build triggered after this log level change passed (&lt;a href=&quot;https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-3node-manager-all-boron/67/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-3node-manager-all-boron/67/&lt;/a&gt;), so can this one be marked as resolved?&lt;/p&gt;</comment>
                            <comment id="58282" author="hideyuki.tai@necam.com" created="Fri, 9 Sep 2016 16:30:45 +0000"  >&lt;p&gt;(In reply to Tomas Slusny from comment #1)&lt;br/&gt;
&amp;gt; This issue is similar to one of issues in&lt;br/&gt;
&amp;gt; &lt;a href=&quot;https://bugs.opendaylight.org/show_bug.cgi?id=6176&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://bugs.opendaylight.org/show_bug.cgi?id=6176&lt;/a&gt;, and that was when&lt;br/&gt;
&amp;gt; logging was not set to ERROR, then logger was logging too much data and was&lt;br/&gt;
&amp;gt; blocking other threads.&lt;br/&gt;
&amp;gt; But Luis already fixed this in tests and changed log level to ERROR, and&lt;br/&gt;
&amp;gt; also next build triggered after this log level change passed&lt;br/&gt;
&amp;gt; (&lt;a href=&quot;https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-3node-manager-&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-3node-manager-&lt;/a&gt;&lt;br/&gt;
&amp;gt; all-boron/67/), so can this one be marked as resolved?&lt;/p&gt;

&lt;p&gt;Thank you for your good information!!!&lt;/p&gt;

&lt;p&gt;The following CSIT just ran two times after the failed run (build #66). So I&apos;m thinking it&apos;s a little bit early to say the issue is fixed now. Therefore, I would like to wait to see more runs before we judge that the issue doesn&apos;t exist anymore.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-3node-manager-all-boron/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-3node-manager-all-boron/&lt;/a&gt;&lt;/p&gt;


&lt;p&gt;That being said, we saw this issue only once, and it has not occurred in the &quot;3node-manager-only&quot; job so far.&lt;br/&gt;
&lt;a href=&quot;https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-manager-only-boron/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-manager-only-boron/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Therefore, I&apos;m changing the importance of the bug from &quot;critical&quot; to &quot;major&quot;.&lt;/p&gt;</comment>
                            <comment id="58283" author="hideyuki.tai@necam.com" created="Mon, 19 Sep 2016 20:34:23 +0000"  >&lt;p&gt;We faced this issue again on Sep 16 in the &quot;3node-manager-only&quot; job.&lt;/p&gt;

&lt;p&gt;&lt;a href=&quot;https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-3node-manager-only-boron/112/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-3node-manager-only-boron/112/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Please see the following log file.&lt;br/&gt;
&lt;a href=&quot;https://logs.opendaylight.org/releng/jenkins092/vtn-csit-3node-manager-only-boron/112/archives/odl3_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/vtn-csit-3node-manager-only-boron/112/archives/odl3_karaf.log.gz&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Therefore, I think the issue is not fixed yet. Could you someone work on that?&lt;/p&gt;</comment>
                            <comment id="58284" author="tomas.slusny@pantheon.tech" created="Thu, 22 Sep 2016 08:17:12 +0000"  >&lt;p&gt;From that log file you provided I think that device was for some reason disconnected.&lt;br/&gt;
That error &quot;No local or remote implementation available for rpc&quot; means that target switch was disconnected during RPC processing.&lt;br/&gt;
But looking at both &lt;a href=&quot;https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-3node-manager-only-boron/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-3node-manager-only-boron/&lt;/a&gt; and &lt;a href=&quot;https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-3node-manager-only-carbon/&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-3node-manager-only-carbon/&lt;/a&gt; tests are passing since 19.09, so this can maybe be only Jenkins environment issue.&lt;/p&gt;</comment>
                            <comment id="58285" author="andrejleitner" created="Tue, 25 Oct 2016 06:07:42 +0000"  >&lt;p&gt;Hi Hideyuki, is this still the issue?&lt;/p&gt;</comment>
                            <comment id="58286" author="hideyuki.tai@necam.com" created="Tue, 25 Oct 2016 22:36:39 +0000"  >&lt;p&gt;(In reply to Tomas Slusny from comment #4)&lt;br/&gt;
&amp;gt; From that log file you provided I think that device was for some reason&lt;br/&gt;
&amp;gt; disconnected.&lt;br/&gt;
&amp;gt; That error &quot;No local or remote implementation available for rpc&quot; means that&lt;br/&gt;
&amp;gt; target switch was disconnected during RPC processing.&lt;br/&gt;
&amp;gt; But looking at both&lt;br/&gt;
&amp;gt; &lt;a href=&quot;https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-3node-manager-&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-3node-manager-&lt;/a&gt;&lt;br/&gt;
&amp;gt; only-boron/ and&lt;br/&gt;
&amp;gt; &lt;a href=&quot;https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-3node-manager-&quot; class=&quot;external-link&quot; target=&quot;_blank&quot; rel=&quot;nofollow noopener&quot;&gt;https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-3node-manager-&lt;/a&gt;&lt;br/&gt;
&amp;gt; only-carbon/ tests are passing since 19.09, so this can maybe be only&lt;br/&gt;
&amp;gt; Jenkins environment issue.&lt;/p&gt;

&lt;p&gt;Thank you for the information.&lt;/p&gt;

&lt;p&gt;Yeah, it could be only Jenkins environment issue...&lt;/p&gt;</comment>
                            <comment id="58287" author="hideyuki.tai@necam.com" created="Tue, 25 Oct 2016 22:39:26 +0000"  >&lt;p&gt;(In reply to Andrej Leitner from comment #5)&lt;br/&gt;
&amp;gt; Hi Hideyuki, is this still the issue?&lt;/p&gt;

&lt;p&gt;I&apos;ve not seen this issue recently in the Jenkins environment.&lt;/p&gt;

&lt;p&gt;So it could be only Jenkins environment temporal issue...&lt;/p&gt;

&lt;p&gt;Therefore, I&apos;ve changed the status of the bug report to the &quot;Resolved&quot; with &quot;Worksforme&quot;.&lt;/p&gt;

&lt;p&gt;If this change is not appropriate, please feel free to change the status.&lt;/p&gt;

&lt;p&gt;If I would face the same issue again, I would reopen this bug report or would issue another new one.&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>6661</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=6661]]></customfieldvalue>

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

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