Mar 12 12:12:11 trusty-maas9 systemd[1]: maas-dhcpd.service: Failed with result 'signal'.
Mar 12 12:12:11 trusty-maas9 systemd[1]: Starting MAAS instance of ISC DHCP server for IPv4...
Mar 12 12:12:11 trusty-maas9 systemd[1]: Started MAAS instance of ISC DHCP server for IPv4.
Mar 12 12:12:11 trusty-maas9 dhcpd[6644]: Wrote 0 class decls to leases file.
Mar 12 12:12:11 trusty-maas9 dhcpd[6644]: Wrote 0 deleted host decls to leases file.
Mar 12 12:12:11 trusty-maas9 dhcpd[6644]: Wrote 0 new dynamic host decls to leases file.
Mar 12 12:12:11 trusty-maas9 dhcpd[6644]: Wrote 43 leases to leases file.
Mar 12 12:12:11 trusty-maas9 dhcpd[6644]: Server starting service.
Mar 12 12:12:12 trusty-maas9 systemd[1]: Stopping MAAS instance of ISC DHCP server for IPv4...
It seems like eveyr single time, right after it gets a lease, the dhcp server dies for some reason. It may be because the rack controller is messing up with service tracking or it is getting disconnecting causing issues. but this is very critical.
Given bug #1556358 (having to do with the incomplete MAC seen when notifying MAAS of the lease update), I wonder if this has something to do with the new notification code... just guessing.