Rollback Scenarios

When a deployment task is wrong or configuration of the deployment task is incorrect, the deployment has to be cancelled. In this case, the deployment task has to be rolled back. Typical scenarios are as follows:

1.After the deployment task is executed, it is found that one configuration is incorrect and it causes the service to fail to start, then it has to be rolled back. 2.After the deployment task is executed, it is found that the deployment does not achieve the expected results, and it has to be rolled back.

Definition of Rollback

Rollback of a deployment task essentially means returning the target device on which the deployment task is effective to the Deployment status before the deployment task. To achieve such status, the precondition is that the previous deployment task still exists. Therefore, you have to be careful about deleting a deployment task. If a deployment task is deleted, the device may fail to roll back to such Deployment status.

Steps to Rollback

1.Confirm that the previous deployment task still exists and has not been deleted. 2.Modify the current deployment task: 1.Plan 1: Leave the target condition of the current deployment task blank so that it cannot match any device. 2.Plan 2: Modify the priority of the current deployment task and set its priority to -1, so that the previous deployment task with a higher priority is used by default. 3.Solution 3: If the current deployment task is confirmed to delete, delete the current deployment task. 3.View the deployment status to confirm that the previous deployment task takes effect.

Note: If it rolls back is to clear all configuration information, you can create an empty template without any service and storage volume configuration information, and then create a deployment task using the empty template to clear the configuration information of the previous incorrect deployment task.