Deployment failures in any phase of application provisioning flow always require an application deployment tear down. Because deployment failures occur frequently and result in critical issues, they must be fixed without requiring a new deployment. The Resume Deployment operation lets you restart the failed deployments by fixing the error conditions.

Pre-Provisioning Failures

Pre-provisioning failures occur at an early stage in a deployment. Whenever a deployment fails in this phase, an error message appears. Correct the error before you trigger the resume deployment operation in the same deployment. You can then restart the pre-provisoning process.

In a pre-provisioning failure, errors often occur because of policy and template validation.

Provisioning Failure

Provisioning failure can occur when the host provisioning or agent bootstrap fails. A red icon appears in the host or agent bootstrap node. When the bootstrap fails in one of the virtual machines due to an Application Services agent installation issue or any issues related to the agent, the system tears down the newly provisioned virtual machine and reprovisions it. When the deployment resumes, the virtual machines that are not working correctly are torn down and provisioned again.

Note:

Network Bootstrap failure is not supported.

Execution

Execution failures can occur due to content download failure or script failure. When the resume option is enabled, you can edit the properties and script for the failed component. When you resume the deployment, execution starts with the first script of the component such as install, configure, or start scripts. When you resume the virtual machine or script, it might not reinstall or start the installation as it is already installed. You must modify the script to get the virtual machine to a clean state to start installing.