[NETVIRT-345] DOMNotificationRouterEvent | Delivery of notification Created: 11/Dec/16  Updated: 15/Dec/16  Resolved: 15/Dec/16

Status: Resolved
Project: netvirt
Component/s: General
Affects Version/s: Carbon
Fix Version/s: None

Type: Bug
Reporter: Tal Rosenzweig Assignee: Tal Rosenzweig
Resolution: Won't Do Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

Operating System: All
Platform: All

External issue ID: 7337

 Description   

2016-12-11 09:36:33,523 | ERROR | pool-27-thread-1 | DOMNotificationRouterEvent | 176 - org.opendaylight.controller.sal-broker-impl - 1.4.2.SNAPSHOT | Delivery of notification org.opendaylight.controller.md.sal.binding.impl.LazySerializedDOMNotification@5c2235b caused an error in listener org.opendaylight.controller.md.sal.binding.impl.BindingDOMNotificationListenerAdapter@2b406d9d
java.lang.NullPointerException
at org.opendaylight.netvirt.vpnmanager.ArpNotificationHandler.getFloatingInternalInterface(ArpNotificationHandler.java:414)[360:org.opendaylight.netvirt.vpnmanager-impl:0.3.2.SNAPSHOT]
at org.opendaylight.netvirt.vpnmanager.ArpNotificationHandler.handleArpRequestFromExternalInterface(ArpNotificationHandler.java:299)[360:org.opendaylight.netvirt.vpnmanager-impl:0.3.2.SNAPSHOT]
at org.opendaylight.netvirt.vpnmanager.ArpNotificationHandler.onArpRequestReceived(ArpNotificationHandler.java:169)[360:org.opendaylight.netvirt.vpnmanager-impl:0.3.2.SNAPSHOT]
at org.opendaylight.yangtools.yang.binding.util.NotificationListenerInvoker.invokeNotification(NotificationListenerInvoker.java:91)[82:org.opendaylight.mdsal.yang-binding:0.9.2.SNAPSHOT]
at org.opendaylight.controller.md.sal.binding.impl.BindingDOMNotificationListenerAdapter.onNotification(BindingDOMNotificationListenerAdapter.java:44)[178:org.opendaylight.controller.sal-binding-broker-impl:1.4.2.SNAPSHOT]
at org.opendaylight.controller.md.sal.dom.broker.impl.DOMNotificationRouterEvent.deliverNotification(DOMNotificationRouterEvent.java:56)[176:org.opendaylight.controller.sal-broker-impl:1.4.2.SNAPSHOT]
at org.opendaylight.controller.md.sal.dom.broker.impl.DOMNotificationRouter$1.onEvent(DOMNotificationRouter.java:68)[176:org.opendaylight.controller.sal-broker-impl:1.4.2.SNAPSHOT]
at org.opendaylight.controller.md.sal.dom.broker.impl.DOMNotificationRouter$1.onEvent(DOMNotificationRouter.java:65)[176:org.opendaylight.controller.sal-broker-impl:1.4.2.SNAPSHOT]
at com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:129)[163:com.lmax.disruptor:3.3.4]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)[:1.8.0_111]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)[:1.8.0_111]
at java.lang.Thread.run(Thread.java:745)[:1.8.0_111]

 Comments   
Comment by Tali Ben-Meir [ 11/Dec/16 ]

Also looks like a duplicate of https://bugs.launchpad.net/networking-odl/+bug/1637828
You should not encounter the same exception since ARP responder for FIP has been moved to the datapath but if you encounter FIP with misssing ARP responder flow check if it has associated port in the neutron model

Comment by Tal Rosenzweig [ 12/Dec/16 ]

Duplicate

Comment by Koby Aizer [ 15/Dec/16 ]

Closing as wontfix because impossible to mark on duplicate outside of bugzilla.

Generated at Wed Feb 07 20:21:20 UTC 2024 using Jira 8.20.10#820010-sha1:ace47f9899e9ee25d7157d59aa17ab06aee30d3d.