I experienced a similar issue when playing around with a test installation of MAAS earlier.
Appearently I had disabled "managed allocation", which I believe needed to be re-enabled before my controller would start dhpcd. Hopefully this will turn up in search results for others facing the same problem where just restarting the controller/service isn't enough :-) - MAAS 2.5.0 (7442-gdf68e30a5-0ubuntu1) on 19.04 - Pretty fresh all-in-one regiond/rackd installation - Simple untagged VLAN with DHCP enabled with the primary controller configured - Was able to commission/deploy machines previously - /var/lib/maas/dhpcd-interfaces had the correct interface from earlier - Service wouldn't start due to ConditionPathExists=/var/lib/maas/dhpcd.conf (by design) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1649397 Title: maas-dhcpd.service won't start To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1649397/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
