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

[James Page]

Public bug reported:

The maas-dhcp-server upstart configuration starts on the standard
runlevels, but the dhcpd daemon is configured to listen on specific
network interfaces only.

If this is not the first network interface, the dhcpd server can fail to
start correct.

'start on net-device-up IFACE=<the right one>' would make sense -
probably as an override (/etc/init/maas-dhcp-server.override)

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: maas 1.4+bzr1820+dfsg-0ubuntu1
ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
Uname: Linux 3.13.0-5-generic x86_64
ApportVersion: 2.13.1-0ubuntu2
Architecture: amd64
Date: Fri Jan 31 13:52:28 2014
InstallationDate: Installed on 2014-01-23 (8 days ago)
InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 (20131016)
PackageArchitecture: all
SourcePackage: maas
UpgradeStatus: Upgraded to trusty on 2014-01-23 (8 days ago)

** Affects: maas
     Importance: Undecided
         Status: New

** Affects: maas (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug micro-cluster trusty

-- 
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