5 Rolling Back OCCM

This chapter provides information about rolling back the OCCM deployment to the previous release.

Note:

You must backup the OCCM configmap before performing an rollback. During rollback, any configurations and certificates created during the upgrade are lost. Backup allows you to reapply these configurations and certificates in future upgrades. To backup the OCCM configuration and for restoring the configuration from a backup, see OCCM Configuration Backup.

You can rollback OCCM from a source release to a target release using CDCS or CLI procedures as outlined in the following table:

Upgrade /Rollback Task	References	Supported for CDCS	Supported for CLI
OCCM Rollback		Yes	Yes

5.1 Rollback Tasks

This section describes the procedure to roll back OCCM:

Note:

You must use the existing release name for rollback

1. Run the following command to check which revision you need to roll back:

   $ helm history <release_name> --namespace <release_namespace>

   For example:

   $ helm history occm --namespace namspace1

2. Run the following command to rollback to the required revision:

   $ helm rollback <release_name> <revision_number> --namespace
       <release_namespace>

   For example:

   $ helm rollback occm 1 --namespace namespace1

5.2 Supported Rollback paths

This section describes the supported rollback paths for OCCM:

Table 5-1 OCCM Rollback Sequence

Source Version	Target Version	Rollback Sequence	Comments
23.4.x	23.4.x	cnDBTier NF OCCM CNC Console	OCCM must be rolled back first followed by CNC Console rollback. Helm rollback OCCM using existing release name. This will rollback OCCM, if enabled.