Comment 28 for bug 1412621

I am running a virtual MAAS and I hit this issue again once I rebooted my host machine. I think there's some merit with your suspicion around this being DNS related. I see that in the failed cases, we get this message during bootstrap: "sudo: unable to resolve host node2"

$ juju bootstrap --upload-tools
Bootstrapping environment "maas"
Starting new instance for initial state server
Launching instance
WARNING no architecture was specified, acquiring an arbitrary node
 - /MAAS/api/1.0/nodes/node-bddd96e6-686a-11e5-8b12-525400c6c9e6/
Building tools to upload (1.25.0.1-trusty-amd64)
Installing Juju agent on bootstrap instance
Waiting for address
Attempting to connect to node2.maas:22
Attempting to connect to node2.maas:22
Attempting to connect to 192.168.100.103:22
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that a host key has just been changed.
The fingerprint for the ECDSA key sent by the remote host is
12:a5:c2:22:44:98:f3:7e:bf:f3:33:22:7c:11:3b:c1.
Please contact your system administrator.
Add correct host key in /home/cherylj/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /home/cherylj/.ssh/known_hosts:306
  remove with: ssh-keygen -f "/home/cherylj/.ssh/known_hosts" -R 192.168.100.103
Keyboard-interactive authentication is disabled to avoid man-in-the-middle attacks.
sudo: unable to resolve host node2
Logging to /var/log/cloud-init-output.log on remote host
Running apt-get update
Running apt-get upgrade

After doing a destroy-environment --force and re-bootstrapping, I do not see that particular error.