yahoo-eng-team team mailing list archive

[Aaron Rosen <aaronorosen@xxxxxxxxx>]

Public bug reported:

Previously, if one had more than one dhcp port configured on a network
the host booted on this network got a resolv.conf that contains
a nameserver entry for both dhcp-ports. If there is only 1 dhcp port
it would get the dns-server configured as cfg.CONF.dnsmasq_dns_servers.
This patch removes this code that sets the nameserver to be the dhcp-agent
instead of the one configured.

** Affects: neutron
     Importance: Undecided
     Assignee: Aaron Rosen (arosen)
         Status: In Progress

** Changed in: neutron
     Assignee: (unassigned) => Aaron Rosen (arosen)

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

Title:
  Do not use dnsmasq process as nameserver

Status in OpenStack Neutron (virtual network service):
  In Progress

Bug description:
  Previously, if one had more than one dhcp port configured on a network
  the host booted on this network got a resolv.conf that contains
  a nameserver entry for both dhcp-ports. If there is only 1 dhcp port
  it would get the dns-server configured as cfg.CONF.dnsmasq_dns_servers.
  This patch removes this code that sets the nameserver to be the dhcp-agent
  instead of the one configured.

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