Rolling Back OCNADD

5 Rolling Back OCNADD

This chapter describes the OCNADD rollback procedure from a target release to a previous supported version.

Table 5-1 Supported Rollback Paths

Source Release	Target Release
23.3.0	23.2.0.0.x

Note:

23.2.0.0.x is the latest patch release on 23.2.0.

Rollback Steps

To roll back to a previous version, follow the steps as mentioned:

Note:

(Optional) A timeout interval of 15 minutes can be set while performing an upgrade as only one POD of the OCNADD services is upgraded at a time.
Ensure the status for the target version in the helm history is not in failed or error state.
Ensure to delete the Kafka feed if enabled on 23.3.0, before attempting the rollback, follow the section 'Disable Kafka Feed Configuration Support' of the Oracle Communications Network Analytics Data Director User Guide.
Direct Rollback to 23.2.0 is not supported, in such cases firstly rollback to the previous patch 23.2.0.0.x, and then rollback to 23.2.0.

To rollback to a previous version:

Run the following command to check the revision to rollback:

$ helm history <release_name> -n <release_namespace>

Where,

<release_name> is the release name used by the Helm command.

<release_namespace> is the OCNADD release name, for example, ocnadd.

Example:

helm history ocnadd --namespace ocnadd-deploy

Sample Helm history output with patch 23.2.0.0.2 example:


REVISION        UPDATED                         STATUS          CHART                           APP VERSION     DESCRIPTION
1               Fri May 12 04:57:43 2023        superseded      ocnadd-0.0.0-23.2.0             23.2.0          Install complete
2               Fri May 12 05:21:52 2023        superseded      ocnadd-23.2.0                   23.2.0.0.2      Upgrade complete
3               Fri May 12 05:35:15 2023        deployed        ocnadd-23.3.0                   23.3.0.0.0      Upgrade complete

Run the command to rollback to the required revision:
```
helm rollback <release_name> <REVISION_number> --namespace <release_namespace>
    --timeout=15m
```
Where, <REVISION_number> is the release version to which Data Director needs to be rolled back is obtained in the previous step.

For example:
```
helm rollback ocnadd 2 --namespace ocnadd-deploy --timeout=15m
```

Run the following command in the charts of previous version to roll back the Adapter service to the previous version:

helm upgrade <release_name> -f ocnadd-custom-values-<previous_release>.yaml <helm_chart_previous_release> --namespace <namespace-name> --set global.env.admin.OCNADD_ADAPTER_UPGRADE_ENABLE=true --timeout=15m

For example:

helm upgrade ocnadd -f ocnadd-custom-values-23.2.0.0.2.yaml ocnadd --namespace ocnadd-deploy --set global.env.admin.OCNADD_ADAPTER_UPGRADE_ENABLE=true --timeout=15m

Verify if the rollback is successful
1. All the pods that has been respawned after upgrade, have the latest age (in secs)
2. The Adapter pods also gets respawned for any upgrade. The status can also be verified from GUI for respective data feeds.
  If the rollback is not successful, perform the troubleshooting steps mentioned in Oracle Communications Network Analytics Data Director Troubleshooting Guide.