Open Omnipresent opened 7 years ago
Sorry for the lack of response. In this case, the "Unable to get deployment lock" typically means something else is trying to work on the deployment. I suspect health monitor was jumping in to help bring things back since I notice mysql_z2/0
is already running.
The bosh cck
approach is the correct way to get things back up and running. If you run into that lock error, you can do bosh task -a
to see what other tasks are running (like health monitor) and reattach to that resurrection task to watch the progress (e.g. bosh task 12345
).
I am running bosh-lite on AWS using the vagrant aws plugin. Sometimes I need to stop the instance so I run
vagrant halt
and to bring it back up I dovagrant up
.After halting and upping an instance there are certain VMs in various deployments that need to be recreated/restarted.
For
cf-release
I runbosh cck
and press option 2 for the following 12 VMS. This gets CF running again.I also have cf-mysql-release on this boshlite and I can't seem to be able to run
bosh cck
on itbosh vms
shows the following vms inunresponsive
state. How can I get the VMs recreate/restarted again after donigvagrant halt
followed byvagrant up
(followed bybosh target <public ip>
?