I ran into an issue the other day with my demo vCloud environment where any change I tried to make to vms in the cloud would return “error” and seeming not interact with vSphere at all.
VMware support pointed out this in the error stack :
2013-01-18 11:15:07,840 | ERROR | LocalTaskScheduler-Pool-5 | FutureUtil | Error updating vm storage profile
and mentioned there was an issue using the storage profile “any” with vCD 5.0. But I’m using 5.1 so I kept digging and noticed on my vCenter server the VMware vSphere Profile-Driven Storage Service has stopped running for whatever reason. Restarting the service (and enabling the recovery options) resolved the issue.
