When you deploy an application to the cloud or update a deployed application in the cloud, virtual machines are created and software is provisioned in the virtual machines. During these processes, deployment failures can occur that can affect your deployment.

Failures can occur in several deployment phases. In Application Services, you can identify where failures occurred by viewing the execution plan. You can use the Resume Deployment option, which is available in the Execution Plan panel in the Deployment View, to resume a failed deployment.

Table 1. Deployment Phases

Deployment Phases

Kinds of Failure

Pre-Provisioning

  • Policy validation

  • Template validation

  • DE reachability validation

Provisioning

Boot Strap failure occurs for the following reasons:

  • Maximum virtual machines exhausted

  • OS install

  • IP setup

  • Storage issue

Agent bootstrap failure occurs for the following reasons:

  • Firewall issue in the template

  • Gateway issue in the template

  • Timeout occurs during communication from agent to Application Services due to network and firewall issues

Pre-Execution

vRealize Automation network bootstrap issues.

Execution

  • Content download failure during install or configure phase

  • Script failures during install or configure start phase

Post-Execution

Deprovisioning failures can occur when external services are part of deployment.

Custom tasks cannot be added or deleted in the resume operation. Deployment failures that occur due to custom task failures cannot be resumed.