As Jeff said, I believe this is fixed in MAAS 1.7.
I worked on a related race condition having to do with migrating MAAS-
managed BIND variables to the MAAS database.
If you are installing MAAS on a machine which will *not* host the MAAS
database, there is still somewhat of a race condition, in that we cannot
fully migrate the BIND configuration to the MAAS database unless the
database is up and running.
On MAAS 1.7, if you hit this situation, you can run:
sudo maas-region-admin edit_named_options --migrate-conflicting-options
This will rewrite the BIND configuration to ensure that MAAS does not
duplicate any BIND options (which would result in the symptom above:
BIND failing to start).
** Changed in: maas (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: maas
Status: New => Fix Released
--
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/1266840
Title:
maas-dns failed to install completely on Trusty
To manage notifications about this bug go to:
https://bugs.launchpad.net/maas/+bug/1266840/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
