neutron ipv6 incorrect dnsmasq config

[Misha Dobrovolskyy]

Good morning Guys,

I have found that neutron dhcp agent is making a dhcp-hosts file with mistakes when network has IPv4 and IPv6 enabled:

Example:
was:

fa:16:3e:83:8e:02host-2001-bc8-32bf--3.nodes.cloud.local,2001:bc8:32bf::3
fa:16:3e:83:8e:02,host-X-X-X-X.nodes.cloud.local,X.X.X.X

should be:

id:00:01:00:01:1a:90:d2:20:fa:16:3e:83:8e:02,host-2001-bc8-32bf--3.nodes.cloud.local,[2001:bc8:32bf::3]
fa:16:3e:83:8e:02host-X-X-X-X.nodes.cloud.local,X.X.X.X

so,
a) "id:" should be at start of the string
b) ipv6 is not using mac to identify client, it should be duid instead
c) ipv6 address should be quoted in the "[]"

I don't know if it's still a bug in the new releases, but 2013.2.1 is having these issues.

Also default route is not advertised.

[Sean M. Collins (scollins)]

Is this the same issue as

https://review.openstack.org/#/c/72880/

?

[Sean M. Collins (scollins)]

Bug is https://bugs.launchpad.net/neutron/+bug/1266780

[Sridhar Gaddam (sridhargaddam)]

Sean, AFAIU they seem to be different. The current bug is about the construction of IPV6 addresses in the dhcp-hosts file for dnsmasq - like using the 'id' field, enclosing the IPV6 addresses in square braces etc (inline with the man page of dnsmasq). While the issue you have mentioned is related to IPV6 shortening/compression. Misha, please clarify if this is not the case.

[Misha Dobrovolskyy (snake-f)]

Good morning gents,

Yes, this is bug more about how neutron is building host file for dnsmasq. IPv6 instead of IPv4 is using client-id (based on mac of the host) like in my original description of the bug.

So, I don't think that issue is the same.

[Sridhar Gaddam (sridhargaddam)]

I don't think this bug is applicable anymore as the issues have been addressed in the due course. I'm marking it as Invalid - please re-open if you still see any issue.

[Sridhar Gaddam (sridhargaddam)]

Fix Committed is appropriate here than Invalid. So marked it as Fix Committed.