Comment 12 for bug 1006553

Adrien, I agree, something less destructive than juju destroy-environment would be helpful for people that run into this. The "lxc-list" command will show which containers exist, but juju destroy-service fails for me after a reboot also. It's still unclear how to avoid cpu churning but also preserve the environment.

Is there a workaround to cleanly resume after reboot, restarting the zookeeper, agents, etc?