VMware Cloud Community
solgaeDK
VMware Employee
VMware Employee
Jump to solution

vCAC 6.0 clone blueprint - selected template has been updated, now it does not appear in vCAC

Hello everyone,

I have been playing around with vCAC 6.0 for quite some time (now updated to vCAC 6.0.1), and have created a blueprint that will clone from the template with Windows Server 2012 R2. Guest agent was not installed as I was only interested in getting the machine up and running with the customization spec created in vCenter.

The blueprint was working as expected after I created the service, catalog item, and entitlements. After that, I converted the template to VM in order to update the template with new Windows patches, and then convert it back to template. Now when I try to create a new blueprint, selected the clone workflow, and browse for template, the template I updated does not exist in the list. Curious, I also went to edit the existing blueprint and tried to browse for the template, and it doesn't appear on the list anymore. In fact, I have created a linux template (CentOS) at one point after installing vCAC, and I can't see that from the list as well.


Any idea on what's going on? The logs in Infrastructure tab -> Monitoring -> Log wasn't indicating any errors, and I already tried rebooting all vCAC components, including a restart of all services in the IaaS server.

0 Kudos
1 Solution

Accepted Solutions
qc4vmware
Virtuoso
Virtuoso
Jump to solution

You likely need to manually kick off the inventory data collection on the compute resource where the template lives.

View solution in original post

0 Kudos
2 Replies
qc4vmware
Virtuoso
Virtuoso
Jump to solution

You likely need to manually kick off the inventory data collection on the compute resource where the template lives.

0 Kudos
solgaeDK
VMware Employee
VMware Employee
Jump to solution

Yes, in fact, I just found out that data collection of the inventory happens once per day by default. Had to login as fabric admin to see the data collection option since I had it added as a vSphere endpoint.

0 Kudos