This is somewhat of continuation of https://bugs.launchpad.net/juju-core/+bug/1415517. As this issue still persists. I can bootstrap an armhf system inconsistantly. I have been able to bootstrap sometimes once, and at other times twice in a row but then it typically hangs again. Oddly enough the status in maas is that the system is in a "deployed" state.
botarmhf@qa:~$ juju bootstrap --show-log --constraints tags=slayton
2015-09-15 19:34:24 INFO juju.cmd supercommand.go:37 running juju [1.24.5-trusty-amd64 gc]
2015-09-15 19:34:24 INFO juju.network network.go:194 setting prefer-ipv6 to false
Bootstrapping environment "maas"
2015-09-15 19:34:24 INFO juju.environs.tools tools.go:86 reading tools with major.minor version 1.24
Starting new instance for initial state server
2015-09-15 19:34:27 INFO juju.provider.maas environ.go:130 address allocation feature disabled; using "juju-br0" bridge for all containers
Launching instance
2015-09-15 19:34:27 WARNING juju.provider.maas environ.go:706 no architecture was specified, acquiring an arbitrary node
2015-09-15 19:34:32 INFO juju.provider.maas environ.go:1088 could not acquire a node in zone "avaton", trying another zone
2015-09-15 19:34:32 WARNING juju.provider.maas environ.go:706 no architecture was specified, acquiring an arbitrary node
2015-09-15 19:34:37 INFO juju.provider.maas environ.go:1088 could not acquire a node in zone "default", trying another zone
2015-09-15 19:34:37 WARNING juju.provider.maas environ.go:706 no architecture was specified, acquiring an arbitrary node
2015-09-15 19:34:42 INFO juju.provider.maas environ.go:1088 could not acquire a node in zone "mcdivitt", trying another zone
2015-09-15 19:34:42 WARNING juju.provider.maas environ.go:706 no architecture was specified, acquiring an arbitrary node
- /MAAS/api/1.0/nodes/node-9ae91a7e-5bbe-11e5-b69c-00163ec335e8/
2015-09-15 19:44:13 INFO juju.environs.bootstrap bootstrap.go:184 newest version: 1.24.5
2015-09-15 19:44:13 INFO juju.environs.bootstrap bootstrap.go:212 picked bootstrap tools version: 1.24.5
Installing Juju agent on bootstrap instance
Waiting for address
Attempting to connect to ms10-18n4-slayton.1ss:22
Attempting to connect to ms10-18n4-slayton.1ss: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
7b:6e:38:33:14:de:57:cd:24:3b:c1:d4:9c:ac:9c:76.
Please contact your system administrator.
Add correct host key in /home/botarmhf/.ssh/known_hosts to get rid of this message.
Offending ECDSA key in /home/botarmhf/.ssh/known_hosts:1
remove with: ssh-keygen -f "/home/botarmhf/.ssh/known_hosts" -R ms10-18n4-slayton.1ss
Keyboard-interactive authentication is disabled to avoid man-in-the-middle attacks.
Logging to /var/log/cloud-init-output.log on remote host
Running apt-get update
Running apt-get upgrade
Installing package: curl
Installing package: cpu-checker
Installing package: bridge-utils
Installing package: rsyslog-gnutls
Installing package: cloud-utils
Installing package: cloud-image-utils
Installing package: tmux
Fetching tools: curl -sSfw 'tools from %{url_effective} downloaded: HTTP %{http_code}; time %{time_total}s; size %{size_download} bytes; speed %{speed_download} bytes/s ' --retry 10 -o $bin/tools.tar.gz <[https://streams.canonical.com/juju/tools/releases/juju-1.24.5-trusty-armhf.tgz]>
Bootstrapping Juju machine agent
Starting Juju machine agent (jujud-machine-0)
Bootstrap agent installed
2015-09-15 19:46:48 ERROR juju.cmd supercommand.go:430 saving bootstrap endpoint address: failed to get connection info: environment "maas" not found
bootstrapping is inconsistent. It sometimes works.