Comment 7 for bug 1430049

The only 2 changes juju-core changes between beta4 and beta5 were: a fix to allow lxc containers to start on PPC64 hosts, and this one: https://github.com/juju/juju/pull/1707/files

I don't know much about how the deployer interfaces with the allwatcher in core, but this line from the log seems suspicious:

user-admin@local 153.352us {"RequestId":1,"Error":"unit \"ceph/0\" is not assigned to a machine","ErrorCode":"not assigned","Response":{}} AllWatcher["1"].Next

Getting the next unit from the watcher will trigger the unit's open ports to be loaded which will fail if the unit is not assigned, but the code seems to handle that and continues without error.

The changes in PR 1707 seem innocuous in relation to the issue but would be interesting to test with that change backed out to see if the issue goes away.

There were some changes to introduce a new NotAssigned error but these were done around 10th Feb, well before beta4 was released.