This scares me too. If the start operation finds a running vm and
fails, my cluster config will automatically try to start the same VM on
the next node it has available. This scenario almost guarantees
duplicate VMs even if I have the on_reboot=destroy.
Dejan, I am not sure but I don't think
I want to test the updated RA. Does anyone know how I can increase the
loglevel to warn or debug without restarting my cluster? I am not
seeing any of the new messages in my logs.
Tom
On 10/08/2013 07:52 AM, Ulrich Windl wrote:
Hi!
I thought, I'll never be bitten by this bug, but I actually
