yahoo-eng-team team mailing list archive

[Brian Haley <1848738@xxxxxxxxxxxxxxxxxx>]

** Changed in: neutron
       Status: In Progress => Fix Released

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

Title:
  Sometimes dnsmasq may not be restarted after adding new subnet

Status in neutron:
  Fix Released

Bug description:
  Tested on stable/queens but this code isn't changed a lot since than
  so probably may happen also on newer releases.

  Sometimes (probably due to some race condition) dhcp agent spawns
  dnsmasq process and sets first "tag0" for the dhcp-range option and in
  opts file for subnet but later, when second subnet is added it may
  happend that this new subnet will "take" tag0 and old subnet should
  have "tag1" - it's based on subnets list order which is orderer based
  on subnet uuid.

  Usually in such case dnsmasq process should be just restarted, tag in opts file should be changed and all should works fine.
  But in some cases (quite rare) it may happen that tag is adjusted in opts file but not in dhcp-range command line option. Than such options are not send properly to the instances.

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