On Wed, 2014-04-09 at 17:46 +0100, Jonathan Gowar wrote: > * all guests have stopped > * ha guest is STILL trying to start > * hv-1 is attempting to connect > * hv-2 alerting > * virtual router running > * ssvm + proxy running
It was the HA guest holding the cluster to ransom. The only way to deal with it was to update the DB vm_instance state to Stopped. The cluster then slowly came back to life. Is there a was to avoid this behaviour from crippling the cluster? Perhaps a quorum of 3 hypervisors would be better. Thanks, Jon
