Comment 3 for bug 1484698

Other attempts to replicate the issue, by forcing a MAAS DHCP failure to start (moving the /var/lib/maas/dhcpd.conf file) we'll have a log output similar to this:

==> /var/log/maas/maas.log <==
Oct 16 20:38:50 maas-1484698 maas.node: [INFO] meaty-ball: Releasing node
Oct 16 20:38:50 maas-1484698 maas.node: [INFO] meaty-ball: Status transition from DEPLOYED to RELEASING
Oct 16 20:38:51 maas-1484698 maas.power: [INFO] Changing power state (off) of node: meaty-ball (node-958b88a4-73f7-11e5-bbc4-525400111c6c)
Oct 16 20:38:56 maas-1484698 maas.node: [INFO] meaty-ball: Status transition from RELEASING to READY
Oct 16 20:38:56 maas-1484698 maas.power: [INFO] Changed power state (off) of node: meaty-ball (node-958b88a4-73f7-11e5-bbc4-525400111c6c)
Oct 16 20:38:57 maas-1484698 maas.service_monitor: [INFO] Service 'maas-dhcpd' is not on, it will be started.
Oct 16 20:38:57 maas-1484698 maas.service_monitor: [ERROR] Service 'maas-dhcpd' failed to start. Its current state is 'off' and 'dead'.