Revert to the Previous Version of the Software

You can use the rollback.sh script to revert the software to the previous installed version, for reasons such as an upgrade failure.

About this task

Note the following best practices:

Perform this procedure immediately after an upgrade failure.
Do not perform any Visibility Manager activities during the period between an upgrade failure and completion of the rollback.

Copy the build directory of the previous installed version to the same path on the Linux system where you untarred the new build directory.
Change to the new build directory.
This directory contains several items. Of relevance to this procedure are the rollback directory and clusterDetails.sh.
Open the clusterDetails.sh script in a text editor and provide the following information for the cluster nodes.
- ARRAY_CONTROLPLANE_IP=<controlplane-ip-addr>
- CONTROLPLANE_USERNAME=<controlplane-username>
- CONTROLPLANE_PASSWORD=<controlplane-user-password>
- ARRAY_REGION_IP=<list-of-all-region-ip-addr>
- REGION_USERNAME=<region-username>
- REGION_PASSWORD=<region-user-password>
- ARRAY_ZONE_IP=<list-of-all-zone-ip-addr>
- ZONE_USERNAME=<zone-username>
- ZONE_PASSWORD=<zone-user-password>
Save and close the clusterDetails.sh script.
Change to the rollback directory.
This directory contains the rollback.sh and downgrade_dbs.sh scripts.
Run the rollback script using the path of the previous build directory as the argument.
For example:
```
# ./rollback.sh -p /home/user1/xvm-<version-build>.tar
```
Verify that the pods have the previous version.
```
# kubectl get pods -n xvm --show-labels
```
The LABELS column in the command results shows the version that is running on each pod.