7.4

Table 3‑29. Causes for Common Clone and Linked Clone Blueprints Problems (Continued)
Problem Cause Solution
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).
Linked clone provisioning fails when
using SDRS
When using linked clone provisioning and SDRS, the
new machine must reside on the same cluster. A
provisioning error occurs if the source machine's
disks are on one cluster and you request to provision
a machine on a different cluster.
When using SDRS and linked clone
provisioning, provision machines to
the same cluster as the linked clone
source. Do not provision to a
different cluster.
Clone or linked clone blueprint
provisioning fails because the
template on which the clone is
based cannot be found
It is not possible to provision machines from a
blueprint that is cloned from a template that no longer
exists.
vRealize Automation runs data collection periodically,
default every 24 hours. If a template is removed, the
change is not reflected until the next data collection
and so it is possible to create a blueprint based on a
non-existent template.
Redefine the blueprint using an
existing template and then request
provisioning.
As a precaution and as applicable,
you can run data collection before
defining the clone or linked clone
blueprint.
Designing Blueprints with NSX Settings
If you have an NSX instance integrated with vRealize Automation, you can configure your vSphere
blueprints to leverage NSX for network and security virtualization.
If you have configured vRealize Automation integration with NSX, you can use network, security, and load
balancer components in the design canvas to configure your blueprint for machine provisioning. You can
also add the following NSX network and security settings to the overall blueprint when you create a new
blueprint or edit an existing blueprint.
n
Transport zone - contains the networks used for the provisioned machine deployment
n
Edge and routed gateway reservation policy - manages network communication for the provisioned
machine deployment
n
App isolation - allows only internal traffic between machines used in the provisioned machine
deployment
For additional information about vRealize Automation and NSX integration and the use of the NSX
network and security components in the vRealize Automation blueprint, see this vRA and NSX - Intro to
Network and Security Automation blog article.
NSX settings are only applicable to vSphere machine component types.
Configuring vRealize Automation
VMware, Inc. 379