MAAS 1.8rc3 broken bind's zone files

[Ante Karamatić]

Upon successful commissioning and (almost) successful 'juju bootstrap', I noticed that nodes can't resolve their own hostnames. Quick look at MAAS's bind files revealed source of the problem. I'm attaching both zone files.

I will try to reproduce it. So far it happened in one out of one attempts.

[Ante Karamatić (ivoks)]

On the second attempt, it generated hostname in zonefile just fine.

[Ante Karamatić (ivoks)]

I've managed to reproduce this. It looks like there's a race condition. I destroyed juju environment with hundreds of nodes, MAAS started moving those nodes from Deployed into Ready state. While it was doing that, I've started another juju bootstrap (I had plenty of nodes in Ready state already) and zone file was being updated all along (probably because nodes were being released). It looks like it wrote a state of the zone file as if I didn't bootstrap again (as if there are no atomic bind updates).

[Gavin Panella (allenap)]

Ante, thanks for that update. Given what I can remember about the DNS writers, that scenario is plausible.

We may want to do what we've long threatened to do: move the DNS service into maas-regiond. Keep BIND around, but only as a caching forwarder.

[Ante Karamatić (ivoks)]

It's also wort nothing that I reproduced this behavior only when I didn't had 'static pool' defined.