Comment 4 for bug 1515444

Brian,

1. You're in a DVR setup, so what does "create DVR" mean? Do you just mean router-create? Maybe it's just best if you supply the exact commands since I'd like to know which IPv6 address you are pinging - link-local vs global.
>> yes, just router-create.
neutron net-create net1
neutron net-create net2
neutron subnet-create net2 2:2::2/64 --name sub2 --enable-dhcp --ip-version 6 --ipv6-ra-mode dhcpv6-stateful --ipv6-address-mode dhcpv6-stateful
neutron subnet-create net1 1:1::1/64 --name sub1 --enable-dhcp --ip-version 6 --ipv6-ra-mode dhcpv6-stateful --ipv6-address-mode dhcpv6-stateful
neutron subnet-create net2 2.2.2.0/24 --name v4sub2 --enable-dhcp
neutron subnet-create net1 1.1.1.0/24 --name v4sub1 --enable-dhcp
neutron router-create dvr
neutron router-interface-add dvr sub1
neutron router-interface-add dvr sub2
neutron router-interface-add dvr v4sub2
neutron router-interface-add dvr v4sub1

>> Using link local address
$
$ ping6 2:2::f816:3eff:fe19:9182
PING 2:2::f816:3eff:fe19:9182 (2:2::f816:3eff:fe19:9182): 56 data bytes
64 bytes from 2:2::f816:3eff:fe19:9182: seq=0 ttl=63 time=2.759 ms
64 bytes from 2:2::f816:3eff:fe19:9182: seq=1 ttl=63 time=1.874 ms
64 bytes from 2:2::f816:3eff:fe19:9182: seq=2 ttl=63 time=2.014 ms

2. Do both of these VMs wind-up on the same compute node or different?
>> They end up on different compute nodes.

3. Could not get the conntrack table output in error state.

Sean,
I had just tried Ping6.

I restacked a few hours back and do not see the issue anymore.