Bug 5428: Ovsdb Termination Point is null issue

- adding condition to check if TP is null,then log and skip processing.

Change-Id: Idd4c7fbbe5398d15dc153927338421ffc3fef67c
Signed-off-by: Michal Cmarada <mcmarada@cisco.com>

diff --git a/neutron-ovsdb/src/main/java/org/opendaylight/groupbasedpolicy/neutron/ovsdb/OvsdbNodeListener.java b/neutron-ovsdb/src/main/java/org/opendaylight/groupbasedpolicy/neutron/ovsdb/OvsdbNodeListener.java
index acf3603d7a378edcdc16ba9478a54ae315e5930f..0794b77d6cc908979beca146d1c001ef902f707a 100644 (file)
--- a/neutron-ovsdb/src/main/java/org/opendaylight/groupbasedpolicy/neutron/ovsdb/OvsdbNodeListener.java
+++ b/neutron-ovsdb/src/main/java/org/opendaylight/groupbasedpolicy/neutron/ovsdb/OvsdbNodeListener.java
@@ -143,6 +143,12 @@ public class OvsdbNodeListener extends DataTreeChangeHandler<Node> {
             }
             for (DataObjectModification<OvsdbTerminationPointAugmentation> ovsdbTpModification : ovsdbTpModifications) {
                 OvsdbTerminationPointAugmentation newOvsdbTp = ovsdbTpModification.getDataAfter();
+
+                if (newOvsdbTp == null) {
+                    LOG.trace("Termination Point is null. Not processing");
+                    continue;
+                }
+
                 if (ovsdbBridge.getBridgeName().getValue().equals(newOvsdbTp.getName())) {
                     LOG.trace("Termination Point {} same as Bridge {}. Not processing", newOvsdbTp.getName(),
                             ovsdbBridge.getBridgeName().getValue());