Comment 17 for bug 1412621

fwiw, i thought I would add my findings as well in regards to this particular issue,

I just ran into this while doing some various tests and bringup on new hardware. I'm in a private vlan with my own dns/dhcp server everything is on arm64.

JuJu-core 1.24.5
MaaS 1.8 (recently enabled)

I had found a small mistake that caused dhcp to hand out the remote dns server first and not use my local dhcp server as the primary. This caused the issue to manifest itself during juju bootstrap attempts, since the local client could not be resolved.

Since fixing that issue with dhcp I have not seen this problem since. So if the end user if maintaining their own network, then the sanity of that environment can very much come into play here.