Looks like https://bugs.launchpad.net/juju-core/+bug/1376246 wasn't fully fixed, or it regressed.
I have a case with maas 1.7.5+bzr3369-0ubuntu1~trusty1 and juju 1.24.1 (tools and client) where 3 maas nodes failed, yet juju just reports them as pending:
"1":
agent-state: pending
dns-name: barley.scapestack
instance-id: /MAAS/api/1.0/nodes/node-65d52b5c-546c-11e4-821d-2c59e54ace74/
series: trusty
hardware: arch=amd64 cpu-cores=4 mem=16384M
"2":
agent-state: pending
dns-name: kyogre.scapestack
instance-id: /MAAS/api/1.0/nodes/node-9f389a16-1b7a-11e5-846c-2c59e54ace74/
series: trusty
hardware: arch=amd64 cpu-cores=12 mem=16384M
"3":
agent-state: pending
dns-name: bibarel.scapestack
instance-id: /MAAS/api/1.0/nodes/node-2ff8a47e-1b7b-11e5-846c-2c59e54ace74/
series: trusty
hardware: arch=amd64 cpu-cores=12 mem=16384M
But in MAAS:
$ maas admin-atlas nodes list hostname=barley hostname=kyogre hostname=bibarel|grep status
"status": 6,
"substatus": 11,
"status": 6,
"substatus": 11,
"status": 6,
"substatus": 11,
Full juju status and maas nodes list output attached.
We can see the fix is delivered in https:/ /github. com/juju/ juju/commit/ 9a7f42182e9311c fa0775488468d80 a416856deb . Maybe the fix is incomplete, or amore recent change broke the new behaviour.