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/NIC-14 nic <p>While passing source and destination node ID to graph service to find the shortest path, but service not able to listen the Node ID's.</p> <p>Please find the log in below,</p> <p>2016-01-26 01:27:53,241 | ERROR | pool-28-thread-1 | DOMNotificationRouterEvent | 138 - org.opendaylight.controller.sal-broker-impl - 1.3.0.SNAPSHOT | Delivery of notification org.opendaylight.controller.md.sal.binding.impl.LazySerializedDOMNotification@ffd1889 caused an error in listener org.opendaylight.controller.md.sal.binding.impl.BindingDOMNotificationListenerAdapter@3155d292<br/> java.lang.IllegalArgumentException: Specified source vertex Uri <span class="error">&#91;_value=openflow:1&#93;</span> is not part of graph Vertices<br/> Edges:<br/> at edu.uci.ics.jung.algorithms.shortestpath.DijkstraShortestPath.getPath(DijkstraShortestPath.java:160)<span class="error">&#91;279:org.opendaylight.controller.thirdparty.net.sf.jung2:2.0.1&#93;</span><br/> at edu.uci.ics.jung.algorithms.shortestpath.DijkstraShortestPath.getPath(DijkstraShortestPath.java:204)<span class="error">&#91;279:org.opendaylight.controller.thirdparty.net.sf.jung2:2.0.1&#93;</span><br/> at org.opendaylight.nic.of.renderer.impl.NetworkGraphManager.getShortestPath(NetworkGraphManager.java:68)<span class="error">&#91;280:org.opendaylight.nic.of-renderer:1.1.0.SNAPSHOT&#93;</span><br/> at org.opendaylight.nic.of.renderer.impl.RedirectFlowManager.generateRedirectFlows(RedirectFlowManager.java:256)<span class="error">&#91;280:org.opendaylight.nic.of-renderer:1.1.0.SNAPSHOT&#93;</span><br/> at org.opendaylight.nic.of.renderer.impl.RedirectFlowManager.redirectFlowEntry(RedirectFlowManager.java:232)<span class="error">&#91;280:org.opendaylight.nic.of-renderer:1.1.0.SNAPSHOT&#93;</span><br/> at org.opendaylight.nic.of.renderer.impl.RedirectFlowManager.addMacNodeToCache(RedirectFlowManager.java:442)<span class="error">&#91;280:org.opendaylight.nic.of-renderer:1.1.0.SNAPSHOT&#93;</span><br/> at org.opendaylight.nic.of.renderer.impl.RedirectFlowManager.onPacketReceived(RedirectFlowManager.java:122)<span class="error">&#91;280:org.opendaylight.nic.of-renderer:1.1.0.SNAPSHOT&#93;</span><br/> at org.opendaylight.yangtools.yang.binding.util.NotificationListenerInvoker.invokeNotification(NotificationListenerInvoker.java:91)<span class="error">&#91;69:org.opendaylight.mdsal.yang-binding:0.8.0.SNAPSHOT&#93;</span><br/> at org.opendaylight.controller.md.sal.binding.impl.BindingDOMNotificationListenerAdapter.onNotification(BindingDOMNotificationListenerAdapter.java:44)<span class="error">&#91;140:org.opendaylight.controller.sal-binding-broker-impl:1.3.0.SNAPSHOT&#93;</span><br/> at org.opendaylight.controller.md.sal.dom.broker.impl.DOMNotificationRouterEvent.deliverNotification(DOMNotificationRouterEvent.java:56)<span class="error">&#91;138:org.opendaylight.controller.sal-broker-impl:1.3.0.SNAPSHOT&#93;</span><br/> at org.opendaylight.controller.md.sal.dom.broker.impl.DOMNotificationRouter$1.onEvent(DOMNotificationRouter.java:68)<span class="error">&#91;138:org.opendaylight.controller.sal-broker-impl:1.3.0.SNAPSHOT&#93;</span><br/> at org.opendaylight.controller.md.sal.dom.broker.impl.DOMNotificationRouter$1.onEvent(DOMNotificationRouter.java:65)<span class="error">&#91;138:org.opendaylight.controller.sal-broker-impl:1.3.0.SNAPSHOT&#93;</span><br/> at com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:128)<span class="error">&#91;135:com.lmax.disruptor:3.3.0&#93;</span><br/> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)<span class="error">&#91;:1.7.0_40&#93;</span><br/> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)<span class="error">&#91;:1.7.0_40&#93;</span><br/> at java.lang.Thread.run(Thread.java:724)<span class="error">&#91;:1.7.0_40&#93;</span></p> <p>Operating System: All<br/> Platform: All</p> NIC-14

Graph service - not able to listen the service in redirect action

Bug Resolved Done Unassigned Vinothkumar Mon, 25 Jan 2016 12:53:28 +0000 Thu, 19 Oct 2017 21:26:34 +0000 Fri, 12 Feb 2016 09:27:30 +0000 unspecified General 0 2 <p>We have tested RC0 build for redirect action, and working fine. We tested recent master/stable beryllium patch on today, but redirect action is not working due to recent changes.</p> <p>Hi Vinoth,</p> <p>A regression was introduced causing a bug in the MPLS functionality.<br/> This patch (<a href="https://git.opendaylight.org/gerrit/gitweb?p=nic.git;a=commit;h=f4521b6454bdcabda2e44a05c7c41eca3035ae00" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/gitweb?p=nic.git;a=commit;h=f4521b6454bdcabda2e44a05c7c41eca3035ae00</a>) fixed: </p> <ul class="alternate" type="square"> <li>NetworkGraph was being reinitialized, causing IndexOutOfBoundsException;</li> <li>MPLS labels were not working properly, since NetworkGraph was empty;</li> </ul> <p>You can find here the steps to reproduce the MPLS functionality: <a href="https://wiki.opendaylight.org/view/Network_Intent_Composition:Use_Cases#MPLS_Intents" class="external-link" target="_blank" rel="nofollow noopener">https://wiki.opendaylight.org/view/Network_Intent_Composition:Use_Cases#MPLS_Intents</a></p> <p>Hi Team,</p> <p>we found that root cause of this bug, when we revert this patch (<a href="https://git.opendaylight.org/gerrit/#/c/33399/" class="external-link" target="_blank" rel="nofollow noopener">https://git.opendaylight.org/gerrit/#/c/33399/</a>) in stable beryllium the redirect action code is working fine. and by default master beryllium working fine.</p> <p>hi nic-dev,</p> <p>On further analysis its found that the handleEvent() of TopologyLinkNotificationSubscriberImpl is not getting invoked. This resulted in the graph links not updated. </p> <p>Its also observed that the LinkUp notification of NodeConnectorNotificationSupplierImpl is getting invoked and the handleEvent() of NodeNotificationSubscriberImpl is called successfully. </p> <p>our understanding is that the TopologyLinkUp notification is not generated.<br/> Would like to understand is there is any change in the way topology events are handled between li and he openflow plugins.</p> Development External issue ID 5082 External issue URL Rank 0|i02e3r: