You can rollback the VMware Telco Cloud Service Assurance patch to the base version or the previous version of the patch using the helm rollback command.

Procedure

You can perform rollback by executing the following commands inside the Deployment Container.
  1. Determine the Helm release name.
    helm list
  2. Rollback to the immediately previous version.
    helm rollback <helm release name>
  3. If you want to rollback to a specific version:
    1. Determine the version number by checking the Helm history.
      helm history <helm release name>
    2. If required, check the configuration of your desired version using the following command:
      helm get all <helm release name> --revision <desired version>
    3. Rollback to the required version.
      helm rollback <helm release name> --revision <desired version>

Patch Rollback using CLI Mode of Deployment

For example, in CLI based patch rollback, Revision number 1 refers to VMware Telco Cloud Service Assurance 2.0.1 GA, Revision number 2 refers to VMware Telco Cloud Service Assurance 2.0.1 Patch 1, and Revision 3 refers to VMware Telco Cloud Service Assurance 2.0.1 Patch 2.
root [ ~/.kube ]# helm list
NAME    NAMESPACE    REVISION  UPDATED                                  STATUS    CHART       APP VERSION
tcsa    default      4         2022-11-07 13:52:51.726793961 +0000 UTC  deployed  tcsa-2.0.1  0.0.0
[root@Smarts-Automation-ESM-VM .kube]# helm history tcsa
REVISION   UPDATED                 STATUS      CHART       APP VERSION   DESCRIPTION
1          Mon Nov 7 05:26:35 2022 superseded  tcsa-2.0.1  0.0.0         Install complete
2          Mon Nov 7 06:36:20 2022 superseded  tcsa-2.0.1  0.0.0         Upgrade complete
3          Mon Nov 7 07:56:45 2022 deployed    tcsa-2.0.1  0.0.0         Upgrade complete
  • If you want to rollback to the base version, you must select Revision number 1. For example:
    root [ ~/tcx-deployer/scripts ]# helm rollback tcsa 1
  • If you want to rollback to the previously installed patch version, you must select Revision number 2. For example:
    root [ ~/tcx-deployer/scripts ]# helm rollback tcsa 2

Patch Rollback on VMware Telco Cloud Automation Based Deployment using CLI

For example, in VMware Telco Cloud Automation based patch rollback, Revision number 1 refers to VMware Telco Cloud Service Assurance 2.0.1 GA, Revision number 2 refers to VMware Telco Cloud Service Assurance 2.0.1 Patch 1, and Revision 3 refers to VMware Telco Cloud Service Assurance 2.0.1 Patch 2. The following snippet shows the list of all the CNFs:

  • If you want to rollback to the base version, you must select Revision number 1. For example:
    root [ ~/tcx-deployer/scripts ]# helm rollback tcsa-201-214c6-gcjiv 1
  • If you want to rollback to the previously installed patch version, you must select Revision number 2. For example:
    root [ ~/tcx-deployer/scripts ]# helm rollback tcsa-201-214c6-gcjiv 2