You can roll back the OpenContrail nodes and the OpenContrail packages on the compute nodes if the upgrade fails. You can find a full log of the specific upgrade build using Build History > Console Output > Full Log in Jenkins UI.
To roll back the OpenContrail nodes:
Log in to the Salt Master node.
Revert the changes made in Prepare the cluster model section.
If you are rolling back only the compute nodes while having
the OpenContrail controller nodes already upgraded to v4.x,
add the system.opencontrail.compute.upgrade class to
cluster/<name>/opencontrail/compute.yml.
Log in to the Jenkins web UI.
Open the Deploy - upgrade Opencontrail to 4.x pipeline.
Specify the following parameters as required:
| Parameter | Description and values |
|---|---|
| SALT_MASTER_CREDENTIALS | The Salt Master credentials to use for connection, defaults to
salt. |
| SALT_MASTER_URL | The Salt Master node host URL with the salt-api port,
defaults to the jenkins_salt_api_url parameter.
For example, http://172.18.170.27:6969. |
| COMPUTE_TARGET_SERVERS | Add the same string that you used during the upgrade that failed. |
| COMPUTE_TARGET_SUBSET_LIVE | Add the same string that you used during the upgrade that failed. |
| STAGE_CONTROLLERS_ROLLBACK | Select this check box to roll back the OpenContrail controller nodes. |
| STAGE_COMPUTES_ROLLBACK | Select this check box to roll back the compute nodes. |
Click Deploy. For details on how to monitor the deployment process, see: MCP Deployment Guide: View the deployment details.
The Deploy - upgrade Opencontrail to 4.x pipeline rollback stages are as follows:
ntw and nal nodes
and starts the OpenContrail services.
The process requires manual confirmations that are based on the output
of the nodetool status and contrail-status commands.