yahoo-eng-team team mailing list archive

[Bertrand Lallau <bertrand.lallau@xxxxxxxxx>]

Public bug reported:

A previous fix as already been done to manage an empty dhcp_domain:
https://bugs.launchpad.net/neutron/+bug/1099625 

Hence in case of an empty dhcp_domain  it remains a bug on Dnsmasq
config files.

With an empty dhcp_domain Dnsmasq launch command line will be:

 dnsmasq --no-hosts --no-resolv --strict-order --bind-interfaces
--interface=tapbdb96782-bb --except-interface=lo --pid-
file=/var/lib/neutron/dhcp/c80662aa-9550-44e6-97f5-a1628b3fca0e/pid
--dhcp-
hostsfile=/var/lib/neutron/dhcp/c80662aa-9550-44e6-97f5-a1628b3fca0e/host
--addn-
hosts=/var/lib/neutron/dhcp/c80662aa-9550-44e6-97f5-a1628b3fca0e/addn_hosts
--dhcp-
optsfile=/var/lib/neutron/dhcp/c80662aa-9550-44e6-97f5-a1628b3fca0e/opts
--leasefile-ro --dhcp-range=set:tag0,20.0.0.0,static,86400s --dhcp-
lease-max=256 --conf-file=

"addn_hosts" file contains:
20.0.0.3	host-20-0-0-3. host-20-0-0-3
20.0.0.4	host-20-0-0-4. host-20-0-0-4

"host" file contains:
fa:16:3e:bf:e1:e4,host-20-0-0-3.,20.0.0.3
fa:16:3e:5f:88:81,host-20-0-0-4.,20.0.0.4

=> for both "addn_hosts" and "host" files the hostname (2nd parameter) is ended with an extra dot char.
(it should be "host-20-0-0-3" instead of "host-20-0-0-3." )

So generated files should be:

"addn_hosts" file:
20.0.0.3	host-20-0-0-3 host-20-0-0-3
20.0.0.4	host-20-0-0-4 host-20-0-0-4

"host" file:
fa:16:3e:bf:e1:e4,host-20-0-0-3,20.0.0.3
fa:16:3e:5f:88:81,host-20-0-0-4,20.0.0.4

** Affects: neutron
     Importance: Undecided
     Assignee: Bertrand Lallau (bertrand-lallau)
         Status: New


** Tags: icehouse-backport-potential

** Changed in: neutron
     Assignee: (unassigned) => Bertrand Lallau (bertrand-lallau)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1326256

Title:
  Dnsmasq config files syntax issue when dhcp_domain is empty

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  A previous fix as already been done to manage an empty dhcp_domain:
  https://bugs.launchpad.net/neutron/+bug/1099625 

  Hence in case of an empty dhcp_domain  it remains a bug on Dnsmasq
  config files.

  With an empty dhcp_domain Dnsmasq launch command line will be:

   dnsmasq --no-hosts --no-resolv --strict-order --bind-interfaces
  --interface=tapbdb96782-bb --except-interface=lo --pid-
  file=/var/lib/neutron/dhcp/c80662aa-9550-44e6-97f5-a1628b3fca0e/pid
  --dhcp-
  hostsfile=/var/lib/neutron/dhcp/c80662aa-9550-44e6-97f5-a1628b3fca0e/host
  --addn-
  hosts=/var/lib/neutron/dhcp/c80662aa-9550-44e6-97f5-a1628b3fca0e/addn_hosts
  --dhcp-
  optsfile=/var/lib/neutron/dhcp/c80662aa-9550-44e6-97f5-a1628b3fca0e/opts
  --leasefile-ro --dhcp-range=set:tag0,20.0.0.0,static,86400s --dhcp-
  lease-max=256 --conf-file=

  "addn_hosts" file contains:
  20.0.0.3	host-20-0-0-3. host-20-0-0-3
  20.0.0.4	host-20-0-0-4. host-20-0-0-4

  "host" file contains:
  fa:16:3e:bf:e1:e4,host-20-0-0-3.,20.0.0.3
  fa:16:3e:5f:88:81,host-20-0-0-4.,20.0.0.4

  => for both "addn_hosts" and "host" files the hostname (2nd parameter) is ended with an extra dot char.
  (it should be "host-20-0-0-3" instead of "host-20-0-0-3." )

  So generated files should be:

  "addn_hosts" file:
  20.0.0.3	host-20-0-0-3 host-20-0-0-3
  20.0.0.4	host-20-0-0-4 host-20-0-0-4

  "host" file:
  fa:16:3e:bf:e1:e4,host-20-0-0-3,20.0.0.3
  fa:16:3e:5f:88:81,host-20-0-0-4,20.0.0.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1326256/+subscriptions