yahoo-eng-team team mailing list archive

[Mark McClain <1202641@xxxxxxxxxxxxxxxxxx>]

Overwriting the file contents vs using replace (which is atomic on
posix) will actually cause more issues.

** Changed in: neutron
       Status: Incomplete => 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/1202641

Title:
  using replace_file in _output_hosts_file and _output_opts_file causes
  issues with some dnsmasq versions

Status in OpenStack Neutron (virtual network service):
  Won't Fix

Bug description:
  Inside the methods _output_opts_file and _output_hosts_file the method
  utils.replace_file is used to write the new options/hosts.
  utils.replace_file first creates a temporary file and afterwards
  renames this temporary file to the name of the destination file. We
  had the issue that dnsmasq doesn't recognize that the used file
  totally changed (new inode after the renaming). As result dnsmasq is
  still using the old file (the file handle inside dnsmasq is still
  open) after receiving the HUP signal from reload_allocations. This
  results in a dnsmasq process not having the latest opts/hosts.

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