Comment 8 for bug 1523031

Is this bug fixed in Mitaka, or am I just lucky to not be able to reproduce it here?

Setup is as follows:

Router: .1, :1
DHCP agent 1: .2, :913b
DHCP agent 2: .3, :36a9
Instance: .4, :1296

On the network node running the active L3 agent and a DHCP agent, I see:

$ ip neigh show dev vxlan-65601
2a02:c0:4f0:1600:f816:3eff:fe5c:1296 lladdr fa:16:3e:5c:12:96 PERMANENT
2a02:c0:4f0:1600:f816:3eff:feb4:36a9 lladdr fa:16:3e:b4:36:a9 PERMANENT
192.168.0.4 lladdr fa:16:3e:5c:12:96 PERMANENT
192.168.0.3 lladdr fa:16:3e:b4:36:a9 PERMANENT

On the network node running a passive L3 agent and another DHCP agent:

$ ip neigh show dev vxlan-65601
2a02:c0:4f0:1600:f816:3eff:fe5c:1296 lladdr fa:16:3e:5c:12:96 PERMANENT
2a02:c0:4f0:1600:f816:3eff:feb4:36a9 lladdr fa:16:3e:b4:36:a9 PERMANENT
192.168.0.4 lladdr fa:16:3e:5c:12:96 PERMANENT
192.168.0.3 lladdr fa:16:3e:b4:36:a9 PERMANENT

On the compute node hosting the instance:

$ ip neigh show dev vxlan-65601
2a02:c0:4f0:1600:f816:3eff:feb4:36a9 lladdr fa:16:3e:b4:36:a9 PERMANENT
2a02:c0:4f0:1600:f816:3eff:fe31:913b lladdr fa:16:3e:31:91:3b PERMANENT
2a02:c0:4f0:1600::1 lladdr fa:16:3e:dd:b4:8c PERMANENT
192.168.0.1 lladdr fa:16:3e:c6:57:9f PERMANENT
192.168.0.2 lladdr fa:16:3e:31:91:3b PERMANENT
192.168.0.3 lladdr fa:16:3e:b4:36:a9 PERMANENT

Multicast doesn't work between the compute node and the two network nodes, and in any case "ip -d link show dev vxlan-65601" does not mention "group" at all.

It all seems to work just fine, but since it's not "supposed to" per this bug, I'm kind of wary of putting it into production until I fully understand why.

Running openstack-neutron-*-8.0.0-1.el7.noarch, for what it's worth.