As a blueprint architect or administrator, you want to ensure that you deliver working blueprints to your user.

Catalog requests might fail for several reasons. It might be due to network traffic, insufficient endpoint resources, or a flawed blueprint specification. Or, the provisioning request succeeded, but the deployment does not appear to be working. As a blueprint architect, you want to avoid providing blueprints that your users cannot successfully deploy.

You can create a testing service and entitlement so that you can deploy the blueprint from the catalog. See Checklist for Configuring the Service Catalog.

If the resources are not successfully provisioned, you can use vRealize Automation to troubleshooting the failed deployment.

Possible Failure States

If a provisioning request fails, you see one of the following states.

  • Failed. A request can fail for several reasons. One cause is that the provisioning process did not work due to a lack of resources on the target endpoint, insufficient resources to support the blueprint, or a badly designed blueprint that must be fixed. Another cause is that the request required approval from someone in your organization, and approver rejected the request. It is also possible that an action that you ran on a deployment failed. The failure can be caused by the environmental or approval reasons already mentioned.

    Use the following troubleshooting workflow to investigate the cause of the problem. If you are able the resolve the problem, review your action options regarding Dismiss and Resubmit. See Action Menu Commands for Provisioned Resources.

  • Partially Successful. A request can be partially successful, meaning some components were deployed but not all of the provisioning steps completed successfully.

    Use the following troubleshooting workflow to determine which components were only partially successful and investigate the cause of the problem. If you are able the resolve the problem, review your action options regarding Dismiss and whether you can use Resume. See Action Menu Commands for Provisioned Resources and How the Resume Action Works.

Troubleshooting Workflow

You can use this workflow to begin investigating a failed deployment. If your investigation reveals that the failure was due to a transient environmental problem, you can resolve the error and resubmit the request. If the problem is with the request specification, you can update the blueprint and submit a new request.

Table 1. How to Begin Troubleshooting Errors
Workflow Troubleshooting Step Example
Number 1

On the Deployments tab, failed deployments are indicated on the status bar. The card includes the last failure message. For more information, click the deployment name or progress bar.

Error message on the deployments card
Number 2

On the deployment details History tab, you can use the events workflow to see where the provisioning process failed. This workflow is also useful when you run an action on a deployment, but the change fails.

Deployment details with error message in the workflow.
Number 3

The failed status indicates where the workflow failed.

Number 4

The information provides a more verbose version of the error message.

If this information in the signpost help is not sufficient to identify and resolve the problem, you can do additional research in the event logs.

Number 5

The following steps require an administrator role.

To locate an error in the context of other errors and warnings, select Administation > Events > View event logs.

Searching for the error in the event log.
Number 6

You can use the advanced search to locate the error based on the message in the deployment details.

Number 7

To view the event details, click the Target ID link.

Number 8

The event details provide additional provisioning information that might assist you with your troubleshooting efforts.

Review the event details
Number 9 As an administrator, you can also view the request in the context of other requests by your users.

Select Administration > Requests and click the request number to examine the request inputs and events.

Requests page with event details.