Bug 7601: Cleanup Elan instances when a network is deleted 73/50673/4
authorSridhar Gaddam <sgaddam@redhat.com>
Thu, 19 Jan 2017 14:45:14 +0000 (20:15 +0530)
committerAlon Kochba <alonko@hpe.com>
Tue, 31 Jan 2017 15:00:43 +0000 (15:00 +0000)
commitca7bbce607f6f8ed06bb5e6751b9f5134544e841
treee56feeed8d3fc743eb6b8e6f45c6f3dbcf5cc535
parent1dd6d15f82b1f8f4b9897cca5c8ca71f6a49f898
Bug 7601: Cleanup Elan instances when a network is deleted

The following patch in Neutron[1] modifies the Network delete sequence.
Prior to a network delete event, we now see an update event that removes
the networkType. So, in delete event, when we try to check for the
networkType, it would be empty and there is an exception. Because of this,
elanInstances are not getting deleted. In this patch, we avoid the check
for networkType since the network itself would not be created in the first
place if its not a supported networkType.

[1] https://review.openstack.org/#/c/317358/

Change-Id: I349a51f4df666ef2c2912ee552f159b6af16de76
Signed-off-by: Sridhar Gaddam <sgaddam@redhat.com>
vpnservice/neutronvpn/neutronvpn-impl/src/main/java/org/opendaylight/netvirt/neutronvpn/NeutronNetworkChangeListener.java