Avoid exceptions with IPv6 subnets 53/30253/4
authorSridharG <sgaddam@redhat.com>
Thu, 26 Nov 2015 15:18:21 +0000 (15:18 +0000)
committerFlavio Fernandes <ffernand@redhat.com>
Mon, 30 Nov 2015 22:45:59 +0000 (17:45 -0500)
commit9af85819b9f6154b5f645ff71dccf3571a787332
tree38de64d8649acfc624bfa778b5fc2dfa001da3d0
parenta12f8afc5edf2c826f7ec3d4da926ba54cb03f4d
Avoid exceptions with IPv6 subnets

In a setup where ODL is used for L2 support and Neutron L3 agent
is used for Routing, we see some Java exceptions when IPv6 subnets
are created. Because of the Java exception, Layer2 connectivity
is lost and we are unable to work with IPv6 subnets. In this patch,
we log an error instead of exception.

Patch set 2: add other places in netvirt code where ipv6 (address and prefix)
             could be used and it would be improperly interpreted.

Patch set 3: minor code review changes.

Change-Id: I4e253f8f86a1a3f027e57861549e9a1f98ff5fbf
Signed-off-by: Sridhar Gaddam <sgaddam@redhat.com>
Signed-off-by: SridharG <sgaddam@redhat.com>
openstack/net-virt-providers/src/main/java/org/opendaylight/ovsdb/openstack/netvirt/providers/openflow13/services/EgressAclService.java
openstack/net-virt-providers/src/main/java/org/opendaylight/ovsdb/openstack/netvirt/providers/openflow13/services/IngressAclService.java