Virtualization, Cloud, Infrastructure and all that stuff in-between
My ramblings on the stuff that holds it all together
Why can’t I add a new VM to my vCAC blueprint
If you are trying to add a blueprint using the clone or linked clone methods in vCloud Automation Center 6.x (vCAC) using a recently created VM or template from vCenter you won’t be able to find it in the search box no matter how hard you try or esoteric your search strings.
This is because by default the vCAC server only inventories the VMs on your vCenter every 24hrs, you can either manually perform an inventory update or increase the frequency.
It was confusing (to me) as the agent logs showed by vSphere IaaS server polling the vCenter service sucessfully, frequently so I assumed it would be looking for new VMs etc, alas no.
You can see the polling & inventory activities in the agent’s log file at the following location
c:\program files (x86)\VMware\vCAC\Agents\\Logs\vSphereAgent.log
To resolve this you can either A) wait 24hrs (hmm) or B) go to Home/Infrastructure/Compute Resources
Right click on your compute resource (e.g vCenter)
And click Data Collection
Under the inventory section you can update the frequency, or click request now to force an immediate update
This took 5-10mins to complete on my fairly large test cluster.
Thanks for this; I was getting frustrated that vCAC wasn’t finding my new templates in vCenter immediately.