Luis,
thanks for responding. th issue occurs whenever the owner of the switches changes from ODL1. The mininet connects to only one node ODL1. VTN invokes the ofplugin rpc's to remove-flow, send-barrier request. They seem to fail most of the times. Regards, Venkat G ________________________________ From: Luis Gomez <[email protected]> Sent: Friday, April 7, 2017 8:57:12 AM To: Venkatrangan G - ERS, HCL Tech Cc: [email protected]; [email protected] Subject: Re: Routed RPC invocations Failing (Openflowplugin) FYI I see send RPC to non-owner after original owner is killed is not stable in carbon: https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-3node-clustering-only-carbon/584/robot/openflowplugin-clustering.txt/Cluster%20HA%20Owner%20Failover/Send%20RPC%20Add%20to%20Successor%20and%20Verify%20After%20Fail/ But boron works: https://jenkins.opendaylight.org/releng/view/openflowplugin/job/openflowplugin-csit-3node-clustering-only-boron/1032/robot/openflowplugin-clustering.txt/Cluster%20HA%20Owner%20Failover/Send%20RPC%20Add%20to%20Successor%20and%20Verify%20After%20Fail/ BR/Luis On Apr 7, 2017, at 5:10 AM, Venkatrangan G - ERS, HCL Tech <[email protected]<mailto:[email protected]>> wrote: Hi Luis, In VTN 3node jobs, we are observing routed rpc invocations to openflowplugin failing [1] . Is there any CSIT job that tests the OFplugin RPC? This happens only ion situation of 3node where the RPC is invoked by a ODL node that is not the provider. These are the log messages that we are observing. 4-07 02:38:45,302 | ERROR | Runner: VTN Main | SendBarrierRpc | 214 - org.opendaylight.vtn.manager.implementation - 0.5.3.Boron-SR3 | send-barrier RPC has thrown an exception: node=openflow:1 org.opendaylight.controller.md.sal.dom.api.DOMRpcImplementationNotAvailableException: No implementation of RPC AbsoluteSchemaPath{path=[(urn:opendaylight:flow:transaction?revision=2015-03-04)send-barrier]} available at org.opendaylight.vtn.manager.internal.util.concurrent.VTNThreadPool$WorkerThread.run(VTNThreadPool.java:400)[214:org.opendaylight.vtn.manager.implementation:0.5.3.Boron-SR3] Caused by: org.opendaylight.controller.md.sal.dom.api.DOMRpcImplementationNotAvailableException: No implementation of RPC AbsoluteSchemaPath{path=[(urn:opendaylight:flow:service?revision=2013-08-19)remove-flow]} available at org.opendaylight.controller.md.sal.dom.broker.impl.DOMRpcRoutingTable.invokeRpc(DOMRpcRoutingTable.java:173) [1] https://logs.opendaylight.org/releng/jenkins092/vtn-csit-3node-manager-only-boron/303/archives/odl3_karaf.log.gz Regards, Venkat G ::DISCLAIMER:: ---------------------------------------------------------------------------------------------------------------------------------------------------- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. E-mail transmission is not guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or may contain viruses in transmission. The e mail and its contents (with or without referred errors) shall therefore not attach any liability on the originator or HCL or its affiliates. Views or opinions, if any, presented in this email are solely those of the author and may not necessarily reflect the views or opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of authorized representative of HCL is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any email and/or attachments, please check them for viruses and other defects. ----------------------------------------------------------------------------------------------------------------------------------------------------
_______________________________________________ openflowplugin-dev mailing list [email protected] https://lists.opendaylight.org/mailman/listinfo/openflowplugin-dev
