7.2

Table Of Contents
Cause
There are multiple possible causes for common clone and linked clone blueprint problems.
Table 429. 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.
Provisioning failure with a shared
blueprint
For blueprints, no validation is available to ensure
that the template you select exists in the reservation
used to provision a machine from your shared clone
blueprint.
Consider using entitlements to
restrict the blueprint to users who
have a reservation on the compute
resource where the template exists.
Provisioning failure with a guest
agent
The virtual machine might be rebooting immediately
after the guest operating system customization is
completed, but before the guest agent work items are
completed, causing provisioning to fail. You can use
the custom property
VirtualMachine.Admin.CustomizeGuestOSDelay
to increase the time delay.
Verify that you have added the
custom property
VirtualMachine.Admin.Customi
zeGuestOSDelay. The value must
be in HH:MM:SS format. If the value
is not set, the default value is one
minute (00:01:00).
Configuring vRealize Automation
VMware, Inc. 358