vCenter 5 U1b released (Updated)

[Update]
As mentioned in the comments below, the bug shown here was fixed in a previous release (apparently U1) of the vSphere client. The trick seems to be the bug only existed in the client and unlike previous versions the client does not prompt to be updated along with vSphere and ESXi. I have tested the GA ESXi (build 469512) and vCenter (build 455964) with a U1b client without seeing the bug.

[Original, unedited post]
This bug has been known for a while and while U1 contained some mentions about fixing it – we now have U1b and the problem still exists.

How to Lose your HA/DRS Cluster in one easy step:
Make sure you have a cluster with HA and/or DRS turned on. Feel free to set any option or enter advanced settings – note that they will all be returned to the defaults.

Navigate to Management > VM Storage Profiles and click Enable VM Storage Profiles

When the “Enable VM Storage Profiles” opens, select your cluster and hit “Enable”

Click Refresh to make sure Storage Profiles are enabled on the cluster.

Now return to your cluster summary to verify HA and DRS have been turned off and all settings have been lost.

Note that you can now set HA/DRS up with no further issues – assuming you don’t disable/enable VM Storage Profiles which will wipe you out again.

Note also that existing FT VMs and Resource Pools will continue to function – but you’ll want to fix HA/DRS if you want to manage those features.

This entry was posted in Computing, Storage, Virtualization, VMware and tagged , , . Bookmark the permalink.

9 Responses to vCenter 5 U1b released (Updated)

  1. Pingback: Quick-Take: vCenter Server 5.0 Update 1b, Appliance Replaced DB2 with Postgres « SolutionOriented Blog

  2. Pingback: VMware Engineering, Are You Fixing Anything? - The Lone Sysadmin

  3. Cormac says:

    Can you change the title of the post? 5.1 is not yet released, so this should be 5.0U1b I guess. It may lead to confusion.

  4. According to this KB the problem should have been solved and I can’t reproduce it in my lab. http://kb.vmware.com/kb/2008203

    Are you sure you upgraded all components as the KB suggests?

  5. mdineen says:

    Have you updated the vSphere Client to 5.0 Update 1 or later,
    if you haven’t this is likely the cause of this issue !

  6. With all due respect, I believe you are mistaken. The fix had always been in the Client itself and not VC Server. There’s no indication here whether you upgraded your Client, as per KB article:
    HA and DRS appear disabled when a Storage Profile is enabled or disabled on a cluster (2008203)

    • JAndrews says:

      When I get access to my test lab I’ll verify the client status, tho this begs the question – why doesn’t the RTM-version client prompt to upgrade when it connects to a U1/U1a/U1b vCenter or host?

Leave a Reply