How do I retry a failed deployment?

Purpose

Use this procedure when deployment has failed due to a downstream problem that is now resolved. The retry operation sends the configured values again; see How do I edit a deployment? to try again with different values.

If the deployment failed because the API pushed a configuration that was not valid for the intent type, the retry operation retries the last valid configuration in the Network Intents database.

Example scenario:

  • The intent type requires one value for attribute A.

  • Deployment 1 has been deployed to the NE with a value of 1 for attribute A.

    Deployment 1 succeeds, and attribute A is configured to 1.

  • The API pushes Deployment 2 to the NE, with values of 4 and 2 for attribute A.

    Deployment 2 fails because it is invalid for the intent type.

  • NSP updates attribute A in Deployment 2 to 1, the last valid value configured using the intent type. The deployment status is still Deployment Failed.

When you click Retry on Deployment 2, the operation retries the deployment with a value of 1 for attribute A.

Steps
 
1 

Open Device Management, Configuration Deployments.

2 

Filter the list if needed: in the Deployment Status drop-down list, choose Deployment Failed.

3 

Choose one or more deployments with the Deployment Failed status. You can use Shift-click to choose a range of deployments.

4 

Retry the deployment:

  1. To retry a single deployment:

    • From the png1.png (Table row actions) menu, choose Retry deployment.

    • From the Deployment Details panel, click Retry Deployment.

  2. To retry multiple deployments, click png21.png Retry selected deployments above the details panel.

The retry operation proceeds.

End of steps