Rollback OCNADD

5 Rollback OCNADD

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

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 Data Director services is upgraded at a time.
Ensure the status for the target version is not in failed or error state.
Before Rollback from target release to source release, the configurations created with the new data feed and synthetic packets should be deleted manually using the GUI.

Run the following command to check the revision you must roll back to:
```
$ 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:
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.

Example:

helm rollback ocnadd 1 --namespace ocnadd --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..