Comment 49 for bug 1519527

Looks like you guys reproduced it, but just to make it clear, here are the steps I took:

- fresh deploy MAAS 1.9.0~rc2+bzr4509-0ubuntu1~trusty1
- register a node with it
- use juju 1.25.1 from proposed, and agent-stream proposed (important)
- juju bootstrap
- juju deploy ubuntu --to lxc:0
- juju add-unit ubuntu --to lxc:0

This is the result:

andreas@nsn7:~$ juju status --format=tabular
[Services]
NAME STATUS EXPOSED CHARM
ubuntu error false cs:trusty/ubuntu-4

[Units]
ID WORKLOAD-STATE AGENT-STATE VERSION MACHINE PORTS PUBLIC-ADDRESS MESSAGE
ubuntu/0 unknown lost 1.25.1 0/lxc/0 10.0.5.152 agent is lost, sorry! See 'juju status-history ubuntu/0'
ubuntu/1 error lost 1.25.1 0/lxc/1 10.0.5.152 hook failed: "leader-settings-changed"

[Machines]
ID STATE VERSION DNS INS-ID SERIES HARDWARE
0 started 1.25.1 ruddy-legs.kvmmaas /MAAS/api/1.0/nodes/node-4ef315b8-9ccb-11e5-8ae1-52540042c56f/ trusty arch=amd64 cpu-cores=1 mem=2048M tags=virtual