[Bug 1274944] Re: maas-dhcp-server should be configured to start after all network interfaces it serves are up

[Dan Poler]

So if I'm reading James' comments correctly, this bug is not a little
deal. Both Akash and I have encountered this in customer environments,
and it leads to dhcpd not coming up when the interface is configured in
MAAS. This is a non-obvious failure state and subsequently leads to
several hours of hair-tearing-out trying to figure out why MAAS isn't
booting a client system... Until you says to yourself, you says, "nah,
it couldn't be something as silly as dhcpd not starting up when I
configured the interface..."

It's not _necessarily_ a packaging bug as I would think that dhcpd needs
to be told to Do The Right Thing (tm) whenever a network configuration
is adjusted for any reason - add interface, remove interface, change IP
range, etc.

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1274944

Title:
  maas-dhcp-server should be configured to start after all network
  interfaces it serves are up

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