https://jira.opendaylight.org This file is an XML representation of an issue en-us 8.20.10 820010 22-06-2022 https://jira.opendaylight.org/browse/VTN-120 vtn <p>The following CSIT for Beryllium VTN Manager failed to verify data flows.<br/> <a href="https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-manager-only-beryllium/148/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-manager-only-beryllium/148/</a></p> <p>At the failed test case, the CSIT verified if data flows were created.<br/> <a href="https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-manager-only-beryllium/148/robot/report/log.html#s1-s2-s3-t11" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-manager-only-beryllium/148/robot/report/log.html#s1-s2-s3-t11</a><br/> However, CSIT could not find data flows, it marked the test case as failed.</p> <p>Considering that the CSIT passes this test case almost every time, the failure on that job (build #148) could be a kind of timming issue.</p> <p>Operating System: All<br/> Platform: All</p> VTN-120

CSIT for VTN Manager failed to verify data flow

Bug Resolved Done Karthik Sivasamy Hideyuki Tai Fri, 12 Feb 2016 18:45:04 +0000 Mon, 21 Mar 2016 13:47:06 +0000 Mon, 21 Mar 2016 13:47:06 +0000 unspecified VTN Manager 0 1 <p>I guess this is a bug of the CSIT.<br/> Therefore I think the CSIT needs to be modified.</p> <p>I've found out that the CSIT uses the following data store to get data flows from VTN Manager in the failed test case.</p> <p> restconf/operational/vtn-flow-impl:vtn-flows/</p> <p>However, this data model (vtn-flow-impl) should not be used in the CSIT, since this data model is an internal model in VTN Manager and not assumed to be used by applications.<br/> This is explicitly mentioned in vtn-flow-impl.yang file.</p> <p><a href="https://git.opendaylight.org/gerrit/gitweb?p=vtn.git;a=blob;f=manager/implementation/src/main/yang/vtn-flow-impl.yang;h=aeb318fd209a843f6106a515352dfe88d3c2179c;hb=refs/heads/stable/beryllium" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/gitweb?p=vtn.git;a=blob;f=manager/implementation/src/main/yang/vtn-flow-impl.yang;h=aeb318fd209a843f6106a515352dfe88d3c2179c;hb=refs/heads/stable/beryllium</a></p> <p> 66 description<br/> 67 "The internal module for entities implementing the VTN data flow.<br/> 68 Application other than VTN Manager must not use models defined in<br/> 69 this module.";</p> <p>Instead of that, please use public data stores and RPCs provided by VTN Manager.<br/> The explanation for all public models are available at the Jenkins server.<br/> <a href="https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/</a></p> <p>First, I think the failed test case should use the get-data-flow RPC provided by VTN Manager to verify if target data flows exist.<br/> <a href="https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-flow.html#get-data-flow" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-flow.html#get-data-flow</a></p> <p>Second, since anyway VTN Manager needs some time to be ready to return the target data flow information, I think the CSIT needs to add some sleep time before the verification or needs to repeat the verification a few times.</p> <p>Third, I'm not sure but specifying the "UPDATESTATS" into the "mode" parameter of the get-data-flow RPC might solve the timing issue, since the get-data-flow PRC in the "UPDATESTATS" mode makes requests to OpenFlow switch to get up-to-date information.</p> <p>I've found out that the same issue (<a href="https://jira.opendaylight.org/browse/VTN-120" title="CSIT for VTN Manager failed to verify data flow" class="issue-link" data-issue-key="VTN-120"><del>VTN-120</del></a>) happened in the build #129 of the vtn-csit-1node-manager-only-beryllium job.</p> <p><a href="https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-manager-only-beryllium/129/robot/report/log.html#s1-s1-s2-t18" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-manager-only-beryllium/129/robot/report/log.html#s1-s1-s2-t18</a></p> <p>Modifed VTN Manager CSIT Keyword file. To use get-data-flow RPC provided by VTN manager.</p> <p>Pushed patch and merged in to integration/test,<br/> <a href="https://git.opendaylight.org/gerrit/#/c/34735" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/34735</a></p> <p>Tested in Sandbox now verify dataflow which uses get-data-flow RPC works fine.<br/> <a href="https://jenkins.opendaylight.org/sandbox/job/vtn-csit-1node-manager-only-beryllium/19/console" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/sandbox/job/vtn-csit-1node-manager-only-beryllium/19/console</a></p> <p>After the patch is merged to git, the below job failed once in the below </p> <p><a href="https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-manager-all-beryllium/88/robot/report/log.html#s1-s2-s3-t11" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-manager-all-beryllium/88/robot/report/log.html#s1-s2-s3-t11</a></p> <p>Before pushing the patch to git, i have tested 5 times in sandbox but i didn't see this error. <br/> The failure see only once in all-beryllium job. Other jobs are working fine without any issue.</p> <p>I think, vtn manager need some time to return dataflow information. We can add some "Wait Until Keyword"(sleep) for Verify dataflow test cases.</p> <p>CSIT for Beryllium VTN Manager failed to verify data flows.</p> <p>Topology used<br/> h1,h2 &lt;--<del>&gt; s2 &lt;</del>-<del>&gt; s1 &lt;</del>-<del>&gt; s3 &lt;</del>--&gt; h3,h4</p> <p>Following are the steps followed in the CSIT test script.</p> <p>1) Create Tenant1<br/> 2) Create vBridge1<br/> 3) Create interfaces if1 and if2<br/> 4) Create Portmapping for interfaces if1 and if2<br/> 5) Ping h1 and h3.  Ping success<br/> 6) Verify Dataflows.  Success. Here verifying dataflow output for “Tenant1, vBridge1 , if1 and PORTMAPPED” <br/> 7) Create vBridge2<br/> 8) Create interfaces if3 and if4<br/> 9) Create Portmapping for interfaces if3 and if4<br/> 10) Ping h2 and h4.  Ping success<br/> 11) Verify Dataflows.  failure. Here verifying dataflow output for “Tenant1, vBridge2 , if3 and PORTMAPPED”</p> <p>From the Karaf Logs it is observed that when the get vtn data flow request is made for<br/> • vbridge 1 - The relevant stats request are seen.<br/> • vBridge 2 – The relevant stats request are not seen.</p> <p>One more observation - Sometimes Verify dataflow for vbridge2 is successful after some retries. In such a case the status requests are seen in the logs.</p> <p>Request VTN Manager teams support to analyze the logs and inform if there is any issue in the CSIT test procedure.</p> <p>Log files are attached<br/> vtndf_karaf.log<br/> vtndf_karaf.log.1</p> <p>Attachment vtndf_karaf.log has been added with description: Karaf log enabled TRACE</p> <p>Attachment vtndf_karaf_log.zip has been added with description: Karaf log enabled TRACE</p> <p>(In reply to Karthik Sivasamy from comment #6)<br/> &gt; CSIT for Beryllium VTN Manager failed to verify data flows.<br/> &gt; <br/> &gt; Topology used<br/> &gt; h1,h2 &lt;--<del>&gt; s2 &lt;</del>-<del>&gt; s1 &lt;</del>-<del>&gt; s3 &lt;</del>--&gt; h3,h4<br/> &gt; <br/> &gt; Following are the steps followed in the CSIT test script.<br/> &gt; <br/> &gt; 1) Create Tenant1<br/> &gt; 2) Create vBridge1<br/> &gt; 3) Create interfaces if1 and if2<br/> &gt; 4) Create Portmapping for interfaces if1 and if2<br/> &gt; 5) Ping h1 and h3.  Ping success<br/> &gt; 6) Verify Dataflows.  Success. Here verifying dataflow output for<br/> &gt; “Tenant1, vBridge1 , if1 and PORTMAPPED” <br/> &gt; 7) Create vBridge2<br/> &gt; 8) Create interfaces if3 and if4<br/> &gt; 9) Create Portmapping for interfaces if3 and if4<br/> &gt; 10) Ping h2 and h4.  Ping success<br/> &gt; 11) Verify Dataflows.  failure. Here verifying dataflow output for<br/> &gt; “Tenant1, vBridge2 , if3 and PORTMAPPED”<br/> &gt; <br/> &gt; From the Karaf Logs it is observed that when the get vtn data flow request<br/> &gt; is made for<br/> &gt; • vbridge 1 - The relevant stats request are seen.<br/> &gt; • vBridge 2 – The relevant stats request are not seen.<br/> &gt; <br/> &gt; One more observation - Sometimes Verify dataflow for vbridge2 is successful<br/> &gt; after some retries. In such a case the status requests are seen in the logs.<br/> &gt; <br/> &gt; Request VTN Manager teams support to analyze the logs and inform if there is<br/> &gt; any issue in the CSIT test procedure.<br/> &gt; <br/> &gt; Log files are attached<br/> &gt; vtndf_karaf.log<br/> &gt; vtndf_karaf.log.1</p> <p>Ignore the above log files. attached the zip file vtndf_karaf_log.zip with includes both the files</p> <p>Exceptions in karaf.log<br/> 016-03-07 06:53:27,969 | ERROR | er Task Thread-0 | StatsReaderService | 188 - org.opendaylight.vtn.manager.implementation - 0.4.0.Beryllium | get-flow-stats: Caught an exception: canceled=false, input=GetFlowStatisticsFromFlowTableInput [_cookie=FlowCookie <span class="error">&#91;_value=9175521290813964288&#93;</span>, _cookieMask=FlowCookie <span class="error">&#91;_value=18446462598732840960&#93;</span>, _node=NodeRef [_value=KeyedInstanceIdentifier</p> {targetType=interface org.opendaylight.yang.gen.v1.urn.opendaylight.inventory.rev130819.nodes.Node, path=[org.opendaylight.yang.gen.v1.urn.opendaylight.inventory.rev130819.Nodes, org.opendaylight.yang.gen.v1.urn.opendaylight.inventory.rev130819.nodes.Node[key=NodeKey [_id=Uri [_value=openflow:1]]]]} <p>], _tableId=0, augmentation=[]]<br/> java.util.concurrent.ExecutionException: org.opendaylight.controller.md.sal.dom.api.DOMRpcImplementationNotAvailableException: No local or remote implementation available for rpc AbsoluteSchemaPath</p> {path=[(urn:opendaylight:flow:statistics?revision=2013-08-19)get-flow-statistics-from-flow-table]} <p> at com.google.common.util.concurrent.AbstractFuture$Sync.getValue(AbstractFuture.java:299)<span class="error">&#91;64:com.google.guava:18.0.0&#93;</span><br/> at com.google.common.util.concurrent.AbstractFuture$Sync.get(AbstractFuture.java:272)<span class="error">&#91;64:com.google.guava:18.0.0&#93;</span><br/> at com.google.common.util.concurrent.AbstractFuture.get(AbstractFuture.java:96)<span class="error">&#91;64:com.google.guava:18.0.0&#93;</span><br/> at org.opendaylight.vtn.manager.internal.util.rpc.RpcInvocation.getResult(RpcInvocation.java:82)<span class="error">&#91;188:org.opendaylight.vtn.manager.implementation:0.4.0.Beryllium&#93;</span><br/> at org.opendaylight.vtn.manager.internal.util.flow.GetFlowStatsRpc.getTransactionId(GetFlowStatsRpc.java:56)<span class="error">&#91;188:org.opendaylight.vtn.manager.implementation:0.4.0.Beryllium&#93;</span><br/> at org.opendaylight.vtn.manager.internal.flow.stats.StatsReaderService.startTransaction(StatsReaderService.java:546)<span class="error">&#91;188:org.opendaylight.vtn.manager.implementation:0.4.0.Beryllium&#93;</span><br/> at org.opendaylight.vtn.manager.internal.flow.stats.StatsReaderService.access$400(StatsReaderService.java:61)<span class="error">&#91;188:org.opendaylight.vtn.manager.implementation:0.4.0.Beryllium&#93;</span><br/> at org.opendaylight.vtn.manager.internal.flow.stats.StatsReaderService$RpcTask.run(StatsReaderService.java:234)<span class="error">&#91;188:org.opendaylight.vtn.manager.implementation:0.4.0.Beryllium&#93;</span><br/> at org.opendaylight.vtn.manager.internal.util.concurrent.VTNThreadPool$WorkerThread.run(VTNThreadPool.java:400)<span class="error">&#91;188:org.opendaylight.vtn.manager.implementation:0.4.0.Beryllium&#93;</span><br/> Caused by: org.opendaylight.controller.md.sal.dom.api.DOMRpcImplementationNotAvailableException: No local or remote implementation available for rpc AbsoluteSchemaPath</p> {path=[(urn:opendaylight:flow:statistics?revision=2013-08-19)get-flow-statistics-from-flow-table]} <p> at org.opendaylight.controller.remote.rpc.RemoteRpcImplementation$1.onComplete(RemoteRpcImplementation.java:65)<span class="error">&#91;163:org.opendaylight.controller.sal-remoterpc-connector:1.3.0.Beryllium&#93;</span><br/> at org.opendaylight.controller.remote.rpc.RemoteRpcImplementation$1.onComplete(RemoteRpcImplementation.java:56)<span class="error">&#91;163:org.opendaylight.controller.sal-remoterpc-connector:1.3.0.Beryllium&#93;</span><br/> at akka.dispatch.OnComplete.internal(Future.scala:248)<span class="error">&#91;149:com.typesafe.akka.actor:2.3.14&#93;</span><br/> at akka.dispatch.OnComplete.internal(Future.scala:245)<span class="error">&#91;149:com.typesafe.akka.actor:2.3.14&#93;</span><br/> at akka.dispatch.japi$CallbackBridge.apply(Future.scala:175)<span class="error">&#91;149:com.typesafe.akka.actor:2.3.14&#93;</span><br/> at akka.dispatch.japi$CallbackBridge.apply(Future.scala:172)<span class="error">&#91;149:com.typesafe.akka.actor:2.3.14&#93;</span><br/> at scala.concurrent.impl.CallbackRunnable.run(Promise.scala:32)<span class="error">&#91;146:org.scala-lang.scala-library:2.11.7.v20150622-112736-1fbce4612c&#93;</span><br/> at scala.concurrent.impl.ExecutionContextImpl$AdaptedForkJoinTask.exec(ExecutionContextImpl.scala:121)<span class="error">&#91;146:org.scala-lang.scala-library:2.11.7.v20150622-112736-1fbce4612c&#93;</span><br/> at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)<span class="error">&#91;146:org.scala-lang.scala-library:2.11.7.v20150622-112736-1fbce4612c&#93;</span><br/> at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)<span class="error">&#91;146:org.scala-lang.scala-library:2.11.7.v20150622-112736-1fbce4612c&#93;</span><br/> at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)<span class="error">&#91;146:org.scala-lang.scala-library:2.11.7.v20150622-112736-1fbce4612c&#93;</span><br/> at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)<span class="error">&#91;146:org.scala-lang.scala-library:2.11.7.v20150622-112736-1fbce4612c&#93;</span><br/> 2016-03-07 06:53:27,975 | ERROR | er Task Thread-0 | StatsReaderService | 188 - org.opendaylight.vtn.manager.implementation - 0.4.0.Beryllium | Failed to issue flow stats RPC: get-flow-stats<br/> org.opendaylight.vtn.manager.VTNException: No local or remote implementation available for rpc AbsoluteSchemaPath</p> {path=[(urn:opendaylight:flow:statistics?revision=2013-08-19)get-flow-statistics-from-flow-table]} <p> at org.opendaylight.vtn.manager.internal.util.concurrent.AbstractVTNFuture.getException(AbstractVTNFuture.java:75)<span class="error">&#91;188:org.opendaylight.vtn.manager.implementation:0.4.0.Beryllium&#93;</span><br/> at org.opendaylight.vtn.manager.internal.util.rpc.RpcInvocation.getResult(RpcInvocation.java:89)<span class="error">&#91;188:org.opendaylight.vtn.manager.implementation:0.4.0.Beryllium&#93;</span><br/> at org.opendaylight.vtn.manager.internal.util.flow.GetFlowStatsRpc.getTransactionId(GetFlowStatsRpc.java:56)<span class="error">&#91;188:org.opendaylight.vtn.manager.implementation:0.4.0.Beryllium&#93;</span><br/> at org.opendaylight.vtn.manager.internal.flow.stats.StatsReaderService.startTransaction(StatsReaderService.java:546)<span class="error">&#91;188:org.opendaylight.vtn.manager.implementation:0.4.0.Beryllium&#93;</span><br/> at org.opendaylight.vtn.manager.internal.flow.stats.StatsReaderService.access$400(StatsReaderService.java:61)<span class="error">&#91;188:org.opendaylight.vtn.manager.implementation:0.4.0.Beryllium&#93;</span><br/> at org.opendaylight.vtn.manager.internal.flow.stats.StatsReaderService$RpcTask.run(StatsReaderService.java:234)<span class="error">&#91;188:org.opendaylight.vtn.manager.implementation:0.4.0.Beryllium&#93;</span><br/> at org.opendaylight.vtn.manager.internal.util.concurrent.VTNThreadPool$WorkerThread.run(VTNThreadPool.java:400)<span class="error">&#91;188:org.opendaylight.vtn.manager.implementation:0.4.0.Beryllium&#93;</span><br/> Caused by: org.opendaylight.controller.md.sal.dom.api.DOMRpcImplementationNotAvailableException: No local or remote implementation available for rpc AbsoluteSchemaPath</p> {path=[(urn:opendaylight:flow:statistics?revision=2013-08-19)get-flow-statistics-from-flow-table]} <p> at org.opendaylight.controller.remote.rpc.RemoteRpcImplementation$1.onComplete(RemoteRpcImplementation.java:65)<span class="error">&#91;163:org.opendaylight.controller.sal-remoterpc-connector:1.3.0.Beryllium&#93;</span><br/> at org.opendaylight.controller.remote.rpc.RemoteRpcImplementation$1.onComplete(RemoteRpcImplementation.java:56)<span class="error">&#91;163:org.opendaylight.controller.sal-remoterpc-connector:1.3.0.Beryllium&#93;</span><br/> at akka.dispatch.OnComplete.internal(Future.scala:248)<span class="error">&#91;149:com.typesafe.akka.actor:2.3.14&#93;</span><br/> at akka.dispatch.OnComplete.internal(Future.scala:245)<span class="error">&#91;149:com.typesafe.akka.actor:2.3.14&#93;</span><br/> at akka.dispatch.japi$CallbackBridge.apply(Future.scala:175)<span class="error">&#91;149:com.typesafe.akka.actor:2.3.14&#93;</span><br/> at akka.dispatch.japi$CallbackBridge.apply(Future.scala:172)<span class="error">&#91;149:com.typesafe.akka.actor:2.3.14&#93;</span><br/> at scala.concurrent.impl.CallbackRunnable.run(Promise.scala:32)<span class="error">&#91;146:org.scala-lang.scala-library:2.11.7.v20150622-112736-1fbce4612c&#93;</span><br/> at scala.concurrent.impl.ExecutionContextImpl$AdaptedForkJoinTask.exec(ExecutionContextImpl.scala:121)<span class="error">&#91;146:org.scala-lang.scala-library:2.11.7.v20150622-112736-1fbce4612c&#93;</span><br/> at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:260)<span class="error">&#91;146:org.scala-lang.scala-library:2.11.7.v20150622-112736-1fbce4612c&#93;</span><br/> at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:1339)<span class="error">&#91;146:org.scala-lang.scala-library:2.11.7.v20150622-112736-1fbce4612c&#93;</span><br/> at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1979)<span class="error">&#91;146:org.scala-lang.scala-library:2.11.7.v20150622-112736-1fbce4612c&#93;</span><br/> at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:107)<span class="error">&#91;146:org.scala-lang.scala-library:2.11.7.v20150622-112736-1fbce4612c&#93;</span><br/> 2016-03-07 06:53:27,976 | WARN | er Task Thread-0 | ClearNodeFlows</p> <p>(In reply to Venkatrangan Govindarajan from comment #10)<br/> &gt; Exceptions in karaf.log<br/> &gt; 016-03-07 06:53:27,969 | ERROR | er Task Thread-0 | StatsReaderService <br/> &gt; | 188 - org.opendaylight.vtn.manager.implementation - 0.4.0.Beryllium |<br/> &gt; get-flow-stats: Caught an exception: canceled=false,</p> <p>I've filed that ERROR message as <a href="https://jira.opendaylight.org/browse/OPNFLWPLUG-605" title="He: Failed to issue flow stats; get-flow-statistics-from-flow-table" class="issue-link" data-issue-key="OPNFLWPLUG-605"><del>OPNFLWPLUG-605</del></a>.<br/> <a href="https://bugs.opendaylight.org/show_bug.cgi?id=5090" class="external-link" target="_blank" rel="nofollow noopener">https://bugs.opendaylight.org/show_bug.cgi?id=5090</a></p> <p>And, I don't think that ERROR message is related to the problem of the <a href="https://jira.opendaylight.org/browse/VTN-120" title="CSIT for VTN Manager failed to verify data flow" class="issue-link" data-issue-key="VTN-120"><del>VTN-120</del></a>.</p> <p>Thanks for clarifying, Just looking at the exception, felt like the stats for some switch is failing hence added it here. Will look further and update</p> <p>Since VTN Manager needs some time to be ready to return data flow information after it receives new packets, I think the CSIT needs to add some sleep time before the verification or needs to repeat the verification a few times.</p> <p>I think the patch for <a href="https://jira.opendaylight.org/browse/VTN-121" title="CSIT for VTN Manager failed to test flow filter" class="issue-link" data-issue-key="VTN-121"><del>VTN-121</del></a> also fixes the <a href="https://jira.opendaylight.org/browse/VTN-120" title="CSIT for VTN Manager failed to verify data flow" class="issue-link" data-issue-key="VTN-120"><del>VTN-120</del></a> since the root cause of these issues could be the same.<br/> <a href="https://git.opendaylight.org/gerrit/#/c/36039/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/36039/</a></p> <p>The following CSIT for Beryllium to verify Dataflows are working fine.<br/> <a href="https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-manager-only-beryllium/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-manager-only-beryllium/</a><br/> <a href="https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-manager-all-beryllium/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-manager-all-beryllium/</a></p> <p>Since after the following patch was merged,<br/> <a href="https://git.opendaylight.org/gerrit/#/c/36039/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/36039/</a></p> <p>To fix the CSIT test failure, we have used the get-data-flow RPC provided by VTN Manager to verify if target data flows exist.</p> <p><a href="https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-flow.html#get-data-flow" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-merge-beryllium/lastSuccessfulBuild/artifact/manager/model/target/site/models/vtn-flow.html#get-data-flow</a></p> <p>After fixing the CSIT we got some other issue, that is verify dataflow fails and the issue is fixed with the following patch.<br/> <a href="https://git.opendaylight.org/gerrit/#/c/36039/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/36039/</a></p> <p>From 11/03/2016, since after the above patch was merged, we dont see any issue related to Verify Dataflow tests in the follwing CSIT Beryllium jobs.</p> <p><a href="https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-manager-only-beryllium/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-manager-only-beryllium/</a><br/> <a href="https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-manager-all-beryllium/" class="external-link" target="_blank" rel="nofollow noopener">https://jenkins.opendaylight.org/releng/view/vtn/job/vtn-csit-1node-manager-all-beryllium/</a></p> Development External issue ID 5343 External issue URL Rank 0|i02tpj: