yahoo-eng-team team mailing list archive

[Rodolfo Alonso <1739219@xxxxxxxxxxxxxxxxxx>]

Bug closed due to lack of activity, please feel free to reopen if
needed.

** Changed in: neutron
       Status: In Progress => Won't Fix

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

Title:
  Old dnsmasq listed as option:dns-server

Status in neutron:
  Won't Fix

Bug description:
  Pike, regular Neutron LinuxBridge, I have the following situation:

  Went from a 4 network nodes setup to a 3 networks nodes setup, so one
  dhcp agent was dropped. It was shut down as well as removed using
  `openstack network agent delete`.

  Issue is about the generated list of DNS servers for a subnet that
  doesn't explicitly define DNS servers. After the removal of the fourth
  dhcp agent, the corresponding dnsmasq IP address is still included in
  the option:dns-server parameter of the generated dnsmasq dhcp config.

  As a result, instances in such a subnet get a list of DNS servers with
  one that is down.

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