7.3

Table Of Contents
Troubleshooting Blueprints for Clone and Linked Clone
When creating a linked clone or clone blueprint, machine or templates are missing. Using your shared
clone blueprint to request machines fails to provision machines.
Problem
When working with clone or linked clone blueprints, you might encounter one of the following problems:
n
When you create a linked clone blueprint, no machines appear in the list to clone, or the machine you
want to clone does not appear.
n
When you create a clone blueprint, no templates appear in the list of templates to clone, or the
template you want does not appear.
n
When machines are requested by using your shared clone blueprint, provisioning fails.
n
Because of data collection timing, a template that has been removed is still visible to users as they
create or edit linked clone blueprints.
Cause
There are multiple possible causes for common clone and linked clone blueprint problems.
For related information about the Clone from and Clone from snapshot with Use current snapshot
options that are available when you create blueprints, see vSphere Machine Component Settings.
Table 330. Causes for Common Clone and Linked Clone Blueprints Problems
Problem Cause Solution
Machines missing You can only create linked clone blueprints by using
machines you manage as a tenant administrator or
business group manager.
A user in your tenant or business
group must request a vSphere
machine. If you have the
appropriate roles, you can do this
yourself.
You can also see unmanaged
machines in this dialog.
Managed machines may have been
imported. There is no requirement
that machines be provisioned from
vRealize Automation to be visible in
this dialog.
Templates missing Data collection has failed on a given endpoint or no
endpoints are available for the component's platform.
n
If your endpoints are clustered
and contain multiple compute
resources, verify that your IaaS
administrator added the cluster
containing the templates to your
fabric group.
n
For new templates, verify that IT
placed the templates on the
same cluster included in your
fabric group.
Configuring vRealize Automation
VMware, Inc. 382