Supervisor Strategy caught unexpected exception because of NPE in NormalizedNodeInputStreamReader

I am getting following exception during net-virt clustering test.

2016-01-20 03:55:32,386 | WARN | lt-dispatcher-27 | ShardManager | 161 - org.opendaylight.controller.sal-distributed-datastore - 1.3.0.SNAPSHOT | Supervisor Strategy caught unexpected exception - resuming
java.lang.NullPointerException
at com.google.common.base.Preconditions.checkNotNull(Preconditions.java:210)[61:com.google.guava:18.0.0]
at org.opendaylight.yangtools.yang.data.api.YangInstanceIdentifier$AbstractPathArgument.<init>(YangInstanceIdentifier.java:413)[76:org.opendaylight.yangtools.yang-data-api:0.8.0.SNAPSHOT]
at org.opendaylight.yangtools.yang.data.api.YangInstanceIdentifier$NodeWithValue.<init>(YangInstanceIdentifier.java:584)[76:org.opendaylight.yangtools.yang-data-api:0.8.0.SNAPSHOT]
at org.opendaylight.controller.cluster.datastore.node.utils.stream.NormalizedNodeInputStreamReader.readNormalizedNodeInternal(NormalizedNodeInputStreamReader.java:138)[157:org.opendaylight.controller.sal-clustering-commons:1.3.0.SNAPSHOT]
at org.opendaylight.controller.cluster.datastore.node.utils.stream.NormalizedNodeInputStreamReader.readNormalizedNode(NormalizedNodeInputStreamReader.java:97)[157:org.opendaylight.controller.sal-clustering-commons:1.3.0.SNAPSHOT]
at org.opendaylight.controller.cluster.datastore.DataTreeCandidatePayload.readNode(DataTreeCandidatePayload.java:184)[161:org.opendaylight.controller.sal-distributed-datastore:1.3.0.SNAPSHOT]
at org.opendaylight.controller.cluster.datastore.DataTreeCandidatePayload.readChildren(DataTreeCandidatePayload.java:146)[161:org.opendaylight.controller.sal-distributed-datastore:1.3.0.SNAPSHOT]
at org.opendaylight.controller.cluster.datastore.DataTreeCandidatePayload.readModifiedNode(DataTreeCandidatePayload.java:161)[161:org.opendaylight.controller.sal-distributed-datastore:1.3.0.SNAPSHOT]

Dumping debug message in NormalizedNodeInputStreamReader, shows that it's throwing exception while reading ip_address leaf of the flow.
Following gist has full exception and debug messages before this exception occures

https://gist.githubusercontent.com/vishnoianil/0fab6f95c5f6824891cd/raw/f46ae667f9a8aef94f789a81c2480c4480cfac22/gistfile1.txt

I am seeing this exception in inventory shard leader controller instance log as well as one of the follower.
But the flow that is causing this exception, successfully getting installed on the switch.