5 Rollback 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.2.0.0.3 23.2.0
23.2.0.0.3 23.2.0.0.2

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 is not in failed or error state.
  • Before Rollback from target release to source release, it is advisable to manually remove the filter configurations and their association with the feeds by using the OCNADD GUI.
  1. 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:

    helm history ocnadd --namespace ocnadd

    Sample Helm history output: Example is with 23.2.0 release rollback

    
REVISION        UPDATED                         STATUS          CHART                   APP VERSION     DESCRIPTION
1               Fri Dec 29 07:17:59 2023        superseded      ocnadd-0.0.0-23.2.0     23.2.0          Install complete
2               Fri Dec 29 07:26:15 2023        superseded      ocnadd-23.2.0           23.2.0.0.3      Upgrade complete
  2. 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, or the REVISION at which the ocnaddcache replicas 'ocnaddcache.replicas' was set to 3.

    Example:

    helm rollback ocnadd 1 --namespace ocnadd --timeout=15m

    Note:

    After the rollback, the existing feeds may not work correctly due to new Kafka consumer group creation. To avoid this issue, perform the following steps to recreate all the existing feeds:
    • Delete an existing feed.
    • Create a new feed with the same name, attributes, and "Connection Failure setting" set to "Resume from point of failure".
    • Verify that end-to-end traffic is flowing between the OCNADD and the corresponding third party application.
  3. 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.