The latest dnsmasq no longer accepts hostnames which begin with a number. This
affects Fedora 19 right now, and will mean Fedora 19 will not work with Neutron
DHCP. dnsmasq should work with hostnames beginning with a number (RFC 1123 says
this is valid), but until this is fixed, many users will be left unable to use
Fedora 19 with Neutron.
This patch adds a "host-" prefix to each hostname entry generated by the DHCP
agent. This fixes the issue in Neutron.
Reviewed: https:/ /review. openstack. org/39167 github. com/openstack/ neutron/ commit/ 61d131999281abf fa6489c72c9fb7e 637008e0ee
Committed: http://
Submitter: Jenkins
Branch: stable/grizzly
commit 61d131999281abf fa6489c72c9fb7e 637008e0ee
Author: Kyle Mestery <email address hidden>
Date: Tue Jul 23 15:17:20 2013 +0000
Fix DHCP agent to work with latest dnsmasq
The latest dnsmasq no longer accepts hostnames which begin with a number. This
affects Fedora 19 right now, and will mean Fedora 19 will not work with Neutron
DHCP. dnsmasq should work with hostnames beginning with a number (RFC 1123 says
this is valid), but until this is fixed, many users will be left unable to use
Fedora 19 with Neutron.
This patch adds a "host-" prefix to each hostname entry generated by the DHCP
agent. This fixes the issue in Neutron.
Fixes bug 1204125
Change-Id: I0e29ec033969c3 fb958ed3a12b896 2b73b0e3d94 5cdc6789bf4962e a64cf87773)
(cherry picked from commit acebf769a41a9a5