Bug 8926: Fix instance doesn't get an IP after deployment 95/61995/1
authorSridhar Gaddam <sgaddam@redhat.com>
Fri, 18 Aug 2017 16:59:09 +0000 (22:29 +0530)
committerSridhar Gaddam <sgaddam@redhat.com>
Fri, 18 Aug 2017 16:59:14 +0000 (22:29 +0530)
commitae32206c80e83517dbbad974907f9508c47a11c9
tree1483f1ac7e3f4089e1e46daba31c5c1385475084
parent64fddf7a002709d6057529551521e4229ca47e5c
Bug 8926: Fix instance doesn't get an IP after deployment

In a fresh multinode deployment with Controller node running
ODL + dhcp-agent and a Compute node, when we spawn a first VM
on the compute node, it was seen that VM does not acquire the
IPAddress.

On debugging, it turns out that the remote broadcast group
entries were not programmed on the Compute node. This is a
timing/sync issue between Netvirt (Elan) and GENIUS. The
bug description explains the issue in detail and this patch
addresses the issue.

Change-Id: Ifee63e13cf330dd3056468eba95e6451e173e30b
Signed-off-by: Sridhar Gaddam <sgaddam@redhat.com>
vpnservice/elanmanager/elanmanager-impl/src/main/java/org/opendaylight/netvirt/elan/internal/ElanInterfaceManager.java