5 Rolling Back SCP

You can roll back SCP from a target release to any supported source release using procedures outlined in this chapter.

5.1 Supported Rollback Paths

The following table lists the supported rollback paths for SCP:

Table 5-1 SCP Supported Rollback Paths

Source Release	Target Release
25.1.202	24.3.x
25.1.202	25.1.1xx
25.1.202	25.1.201

5.2 Rollback Tasks

To roll back from SCP 25.1.202 to a previous version:

Note:

• SCP might raise alerts while performing rollback. To clear any alert, see "Alerts" in Oracle Communications Cloud Native Core, Service Communication Proxy User Guide.
• SCP uses the upgraderollbackevents resource to retrieve the list of upgrade and rollback events. For more information, see "Fetching Upgrade and Rollback Events" in Oracle Communications Cloud Native Core, Service Communication Proxy REST Specification Guide.
• A timeout interval of 30 minutes is set while performing rollback because only one instance of scp-worker is rolled back at a time.
• Ensure that no SCP pod is in the failed state.
• While performing the rollback, you may observe some deviation in SCP traffic processing rate for some of the data plane services, such as SCP-Worker, SCP-nrfProxy, SCP-Mediation, and so on, on Grafana as the pods are scaling down and scaling up. To verify whether there is any actual traffic deviation, it is recommended to check the traffic rate for the same time duration at the consumer NF's side.

1. To obtain the release number to which SCP has to be rolled back, check the revision by running the following command:

   helm history <release_name> --namespace <release_namespace

   Where,

   • <release_name> is the release name used by the Helm command.
   • <release_namespace> is the SCP release name, for example, ocscp.

   Example:

   helm history ocscp --namespace ocscp

2. Rollback to the required revision:

   helm rollback <release_name> <revision_number> --namespace <release_namespace> --timeout=30m

   Where, <revision_number> is the release number which SCP can be rolled back to.

   Example:

   helm rollback ocscp 1 --namespace ocscp --timeout=30m

3. If the rollback fails, see Oracle Communications Cloud Native Core, Service Communication Proxy Troubleshooting Guide.

   Note:

   You must clean up any residual job from the SCP deployment after the rollback is complete.

5.3 Postrollback 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 SCP, then accordingly, if any update is required, individual service APIs defined for different resources can be used to reconfigure the data backup taken before the upgrade.

For information about REST APIs, see Oracle Communications Cloud Native Core, Service Communication Proxy REST Specification Guide.