That is one heck of a dangerous VMware bug

Pre vSphere 5.1b

virtualization.info | Release: vCenter Server 5.1 Update 1b

When you attempt to delete a virtual machine folder while the virtual machine is powered on, a message similar toCannot delete file. [VMFS] <virtual_Machine_Name> is displayed. If you click the Delete button again without closing the datastore browser or changing the selection, and attempt to delete the same virtual machine folder that failed to delete earlier, all virtual machine folders on the VMFS volume might now get deleted.

Scary ..........

Find more posts tagged with

Free for TechExams community: Cybersecurity salary guide

Compare cert salaries and plan your next career move

Button

Comments

TheProf

Hmmm interesting... good to know, thanks for posting.

DevilWAH

I am off to try to recreate it in the production environment

sratakhin

It's a feature, not a bug. How would you otherwise delete all VMs at once?

jibbajabba

sratakhin wrote: »

It's a feature, not a bug. How would you otherwise delete all VMs at once?

Dang, haven't seen it that way .. a shame it is being patched

dave330i

Another reason to stay with 5.0.

whatthehell

That is nasty!!!! Thx for heads up!

puertorico1985

DevilWAH wrote: »

I am off to try to recreate it in the production environment

Let us know how that turns out for you

jibbajabba

dave330i wrote: »

Another reason to stay with 5.0.

One of many ....

DevilWAH

puertorico1985 wrote: »

Let us know how that turns out for you

its been a really quite day, no emails, no phones, not help desk cases.... lot of angry people banging on the door shouting about something or other not working. but just turning up the volume on the headphones and watching you tube clips about an old dear falling down a hole.. See nothing to that bug!

dave330i

jibbajabba wrote: »

One of many ....

When people start threads on upgrading to 5.1, I used to tell them 5.1 isn't that great. They should upgrade/stick with 5.0. After serveral futile attempts, I gave up. Now I think of all the "fun" they'll have trying to get 5.1 working.

jibbajabba

The "best" fail we had was upgrading vCloud Director. Nowhere in the vSphere documentation does it say you need to upgrade the vShield manager first before upgrading the vCenter... They've added it to the vCloud documentation now - but it is nowhere mentioned in the upgrade guides .. Especially the ones saying "vCenter First" ...

QHalo

Yeah, so glad 5.1 wasn't GA when I did my design. Stuck with 5.0 and haven't regretted it yet.

DevilWAH

have to say using 5.1 and with out issue, mind you we arnt pushing for the advanced feature so it pretty much an out of the box solution.

dave330i

jibbajabba wrote: »

The "best" fail we had was upgrading vCloud Director. Nowhere in the vSphere documentation does it say you need to upgrade the vShield manager first before upgrading the vCenter... They've added it to the vCloud documentation now - but it is nowhere mentioned in the upgrade guides .. Especially the ones saying "vCenter First" ...

Wait until you start playing around with vCAC. You'll wish the documentation is as good as vCloud.

QHalo

Dave you make me nervous about looking at their other products when I have some time lol

dave330i

QHalo wrote: »

Dave you make me nervous about looking at their other products when I have some time lol

Working with vCAC is sort of like trying to open a can w/out a can opener. There are all sorts of goodies inside. Just not sure how to access it.