Comment 6 for bug 1450191

This issue isn't maas specific, but probably shows up there due to the fact that MAAS runs faster on real hardware compared with cloud deployments.

megawatcher reports that the unit is started before it is ready because older charms which don't yet set status don't set the status to active and so a best guess is made. Clearly the guess is sometimes wrong.