Bitten again

This is another “note to self”. I’ve been bitten again by a vCloud Director problem that I first encountered last November. Laughably, when I was Googling for a solution I turned up the Vmware communities page where I posted the problem before solving it myself.

I’m not totally sure what triggers this but various “odd” symptoms eventually boil down to the error message: “The operation failed because VirtualCenter server is not connected. vCD, as noted on the communities post, is not good at spotting this error and will happily carry on until it needs to call the vsphere API to do something at which point it generates an error like this one:

One odd vCD error

A similar error might appear as follows:

To fix this, go to the “Manage & Monitor” pane of the System tab. Click on “”vCenters” under “vSphere Resources” and you will see the not connected error under the Status column. Simply right-click on the virtual center and choose “Reconnect vCenter”. That should fix all the odd problems.

One thought on “Bitten again

  1. Thank you for the tip
    my VC goes down for a reason or the other [still in research] , it looks that vCD does not Auto-reconnect if the connection to VC was interrupted for any reason ! which is rather strange as Front-end to Back-End relation

Leave a Reply

Your email address will not be published. Required fields are marked *