I'm not sure if this applies to dnsmasq or not, but some services does not bind to new interfaces during a reload. Meaning you'll have to be sure the reason you're reloading isn't because of something that added a device (say adding a new tier or similar).
-- Erik On Fri, Nov 24, 2017 at 9:05 PM, Pierre-Luc Dion <pd...@cloudops.com> wrote: > Hi, > > We recently found a way to reload dnsmasq process instead of doing a > restart. > Does anyone see a problem with that? Basically we have to change where the > file /etc/dhcphosts.txt is define in the config so it would be define via > "--dhcp-hostsfile=/etc/dhcphosts.txt" when the process is start so it would > be re-read in a kill -HUP. > > The problem to solve here is that during VM.CREATE in a VPC, the dns > service is restarted and cause DNS service interruption to VM inside the > VPC. > > We are preparing a PR for this. > > is this could be problematic for rVR ? > > Thanks, > > PL
