Dnsmasq 2.81 broke neutron's DHCP service
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Harald Jensås |
Bug Description
With dnsmasq 2.81 DHCP for instances connected to network with both IPv4 and IPv6 dhcp-stateful networks will not work as it should. Dnsmasq is processing "host" file's entries from the bottom to the top and as neutron always places first IPv4 and then IPv6 addresses for same MAC, DHCP for IPv4 will not work now.
Details are in Harald's email: http://
Basically it's not Neutron's fault but regression in dnsmasq, but we can workaround it by changing how we generate host file. If it will be one line per mac address, like:
fa:16:3e:
fa:16:3e:
fa:16:3e:
fa:16:3e:
fa:16:3e:
then it should works fine in both dnsmasq 2.81 and older versions.
Changed in neutron: | |
assignee: | nobody → Slawek Kaplonski (slaweq) |
tags: | added: l3-ipam-dhcp |
Changed in neutron: | |
importance: | Undecided → High |
tags: | added: neutron-proactive-backport-potential |
tags: | removed: neutron-proactive-backport-potential |
It is also broken in dnsmasq-2.79-11.el8 which is available in Centos 8