← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1417057] [NEW] dnsmasq should run in "authoritative mode"

 

Public bug reported:

When dnsmasq is restarted, it forgets about all leases (since it runs
with leasefile-ro option).  When client tries to renew its lease,
dnsmasq sends DHCPNAK reply with message "lease not found".  Then client
shuts down the network and re-request lease from DHCP server (and gets
exactly same IP address).  There's a small network downtime which
affects services, like zookeeper, running in VMs.

dnsmasq have special option, --dhcp-authoritative, which makes it think
it's the only DHCP server on network.  In this particular case, when
lease not found and client renews address, operation is completed
successfully.  Although, several DHCP agents may exist for a single
network, they all share same configuration and can be considered as "the
only DHCP server".

TL;DR - option "--dhcp-authoritative" should be added to dnsmasq's
command line.

** Affects: neutron
     Importance: Undecided
         Status: New

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

Title:
  dnsmasq should run in "authoritative mode"

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  When dnsmasq is restarted, it forgets about all leases (since it runs
  with leasefile-ro option).  When client tries to renew its lease,
  dnsmasq sends DHCPNAK reply with message "lease not found".  Then
  client shuts down the network and re-request lease from DHCP server
  (and gets exactly same IP address).  There's a small network downtime
  which affects services, like zookeeper, running in VMs.

  dnsmasq have special option, --dhcp-authoritative, which makes it
  think it's the only DHCP server on network.  In this particular case,
  when lease not found and client renews address, operation is completed
  successfully.  Although, several DHCP agents may exist for a single
  network, they all share same configuration and can be considered as
  "the only DHCP server".

  TL;DR - option "--dhcp-authoritative" should be added to dnsmasq's
  command line.

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


Follow ups

References