This issue is resolved in VMware vCenter Server 5.5.0b
If you are running the older version of vCenter Server, please upgrade.