5 Rolling Back SEPP

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

You can roll back SEPP from a target release to any supported source release using CDCS or CLI procedures as outlined in the following table:

Table 5-1 SEPP Rollback Sequence

Sequence Rollback Task References Supported for CDCS Supported for CLI
1 Rolling back process Rollback Steps Refer to Oracle Communications CD Control Server User Guide. Yes

5.1 Supported Rollback Paths

The following table lists the supported rollback paths for SEPP:

Note:

  • SEPP delpoyed in SEPP mode can be rolled back only to SEPP mode.
  • SEPP deployed in Roaming Hub mode can be rolled back only to Roaming Hub mode.

Table 5-2 Supported Rollback Paths

Source SEPP Release Target SEPP Release
23.4.3 23.4.x, 23.3.x, 23.2.x

Table 5-3 Supported Rollback Paths

Source Roaming Hub Release Target Roaming Hub Release
23.4.3 23.4.x, 23.3.x, 23.2.x

5.2 Rollback Steps

Perform this procedure to roll back SEPP deployment from 24.2.0 to the previously supported versions:

Caution:

  • No configuration should be performed during rollback.
  • Do not exit from helm rollback command manually. After running the helm rollback command, it takes some time (depending upon number of pods to rollback) to rollback all of the services. In the meantime, you must not press "ctrl+c" to come out from helm rollback command. It may lead to anomalous behavior.
  • Ensure that no SEPP pod is in the failed state.
  • If the Helm rollback results in failure and displays Rollback "ocsepp" failed: no ConfigMap with the name "rss-ratelimit-map" found error, it indicates that Helm is not able to merge current and rollback charts. Then run the Helm rollback again with --force.
  • If the Helm rollback results in failure and displays ConfigMap <Egress Rate Limiting ConfigMap Name> in namespace <Namespace> exists and cannot be imported into the current release: invalid ownership metadata error, do the following:

    Delete the Egress Rate Limit ConfigMap using the following command: kubectl delete cm <Egress Rate Limiting ConfigMap Name> -n <namespace> and run the Helm rollback again.

Note:

SEPP might raise alerts while performing rollback. To clear any alert, see "Alerts" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy User Guide.

  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 namespace where SEPP is deployed.

    For example:

    helm history ocsepp --namespace seppsvc
  2. Run the command to rollback to the required revision: 
    helm rollback <release_name> <revision_number> --namespace <release_namespace>

    Where, <revision_number> is the release number to which SEPP needs to be rolled back.

    For example:

    helm rollback ocsepp 1 --namespace seppsvc
  3. If the rollback fails, see "Upgrade or Rollback Failure" section in Oracle Communications Cloud Native Core, Security Edge Protection Proxy Troubleshooting Guide.

5.3 Post Rollback Tasks

After performing rollback, restore preupgrade data obtained earlier through manual backup.

GET API for different resources can be used to see current values in SEPP, then accordingly if any update required, individual service APIs defined for different resources can be used to reconfigure the data backup taken before upgrade.

Caution:

Run the following command to delete the rateLimitingConfigMap ConfigMap manually, post rollback (applicable only for the roll back to 22.4.x or previous versions):
kubectl delete cm <rateLimitingConfigMap> -n <release-namespace>

See Oracle Communications Cloud Native Core, Security Edge Protection Proxy (SEPP) Rest Specification for API details.