Pivotal Knowledge Base


Insufficient User Privileges when Deploying Ops Manager to vCenter


Pivotal Cloud Foundry® (PCF) versions 1.5.x, 1.6.x, and 1.7.x


When clicking "apply changes to deploy Ops Manager", it will fail to create a disk. However, in vCenter, it appears that the disk has been successfully created. In the install logs, you might see errors similar to the following:

Started deploying 
Creating VM for instance 'bosh/0' from stemcell 'sc-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx'... Finished (00:00:19)
Waiting for the agent on VM 'vm-xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx' to be ready... Finished (00:00:32)
Creating disk... Failed (00:04:27)
Failed deploying (00:05:19)

When you look in vCenter, you might see logs saying that the disk has been successfully created and attached. However, the deployment still didn't go through.


The cause of this issue is that the vCenter user attempting to deploy the Ops Manager VM doesn't have sufficient privileges. You can see more on the necessary privileges in this Knowledge Base Article on privileges for vCenter/vSphere. You can see the following error in your install logs further indicating this is a privilege error:

...should have the following properties: ["info.progress", "info.state", "info.result", "info.error"] (VSphereCloud::CloudSearcher::MissingPropertiesException), but they were missing these: #<Set: {"info.state"}>


The user who is deploying the Ops Manager Director VM needs to have System.View privileges on the vCenter server-level so that the persistent disks can be moved between datastores. See more on in the docs on bosh on vCenter/vSphere here.

 You can see the entire list of Required vSphere Privileges at this github, which is now linked from the vSphere/vCenter requirements Pivotal Doc.



Powered by Zendesk