Do not use dnsmasq process as nameserver

Bug #1472433 reported by Aaron Rosen
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
neutron
Expired
Undecided
Unassigned

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.

Aaron Rosen (arosen)
Changed in neutron:
assignee: nobody → Aaron Rosen (arosen)
Changed in neutron:
status: New → In Progress
Revision history for this message
yong sheng gong (gongysh) wrote :

so what if cfg.CONF.dnsmasq_dns_servers not configured?

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on neutron (master)

Change abandoned by Aaron Rosen (<email address hidden>) on branch: master
Review: https://review.openstack.org/199346

Revision history for this message
Armando Migliaccio (armando-migliaccio) wrote :

This bug is > 172 days without activity. We are unsetting assignee and milestone and setting status to Incomplete in order to allow its expiry in 60 days.

If the bug is still valid, then update the bug status.

Changed in neutron:
assignee: Aaron Rosen (arosen) → nobody
status: In Progress → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for neutron because there has been no activity for 60 days.]

Changed in neutron:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.