[PVE-User] Bug when removing a VM

[David Lawley]

Just sharing an experience..  Not trying to high jack

Had an occurrence few years back, older version of Prox, with fencing 
and HA ( it was a way older version) .  I did not stop the VM before 
enabling HA.  Guess what, had ghosts in the machine.  The VMs that I had 
enabled HA started another VM, so I had duplicate VMs.  Only one showed 
up in the control panel.  It was not until I stooped the vm and found I 
could still ping it did I discover this.  I did not think it would let 
me do it if would screw something up. It kind of backed me off of HA. 
Sure this is all better now, right?

On 6/21/2018 4:04 AM, lemonnierk at ulrar.net wrote:
> Hi,
> 
> Not sure this is a bug, but if it's not there should be a huge red
> warning in the VM removal box, I think.
> 
> We've been migrating some VMs between clusters, and for that I mounted
> the old storage on the new cluster, and just re-created the VM, stopped
> them on the old cluster and started them on the new, then used "move
> disk"
> 
> That works fine, but this morning a colleague just deleted a bunch of
> VMs on the new clusters, and we discovered with horror that when you
> delete VM 112 for example, it doesn't just remove the images/112
> directory on the storage the VM was using, it does it on all attached
> storage.
> So when he deleted a few VM on the new cluster, it deleted the hard
> drives of a bunch of other VM on the old cluster that hadn't been
> migrated yet.
> 
> Surprise ..
>