5 Rolling Back BSF

This chapter provides information about rolling back Oracle Communications Cloud Native Core, Binding Support Function (BSF) deployment to the previous release. It is recommended to perform BSF rollback in a specific order. For more information about the rollback order, see Oracle Communications Cloud Native Core Solution Upgrade Guide.

5.1 Supported Rollback Paths

The following table lists the supported rollback paths for BSF:

Source Release	Target Release
25.2.100	25.1.200

If georedundancy feature was disabled before upgrading to 25.2.100, then rolling back to a previous version will automatically disable this feature. However, the database will still have records of the NfInstances and NfSubscriptions from the mated sites. For more information, contact My Oracle Support.

5.2 Rollback Tasks

Note:

Ensure that no pod is in the failed state.

To roll back from BSF 25.2.100 to a previous version, perform the following steps:

1. To check which revision you need to roll back to, run any of the following commands:

   Using Helm:

   helm history <release_name> -n <release_namespace>

2. Run either of the following commands to roll back to the required version:
   1. Using Helm:

      helm rollback <release_name> <revision_number> -n <release_namespace>

      Note:

      The following warnings must be ignored for BSF rollback to CNE 25.1.2xx and 25.2.1xx:

      
      helm rollback <release_name> <revision-version> -n <namespace>
      W0910 07:39:23.637460 3540122 warnings.go:70] spec.template.spec.containers[0].ports[3]: duplicate port definition with spec.template.spec.containers[0].ports[2]
      W0910 07:39:26.437684 3540122 warnings.go:70] spec.template.spec.containers[0].ports[3]: duplicate port definition with spec.template.spec.containers[0].ports[1]
      Rollback was a success! Happy Helming!

3. <Applicable for release 22.2.0 and later > If you are rolling back from BSF 22.2.0 and later release to 22.1.0 or earlier releases, then run the following command to delete the database that is not applicable:

   DROP DATABASE ocbsf_LeaderPodDb;

Note:

If the rollback is not successful, perform the troubleshooting steps mentioned in Oracle Communications Cloud Native Core, Binding Support Function Troubleshooting Guide.

Note:

When rolling back from 23.4.0, Audit Service must be disabled and re-enabled after the rollback is completed. As the audit registration request is resent after the Audit Service pod comes up and the data gets updated in Audit Service tables.