Rolling back to a specific Operator version

To roll back or install a specific Operator version, update the catalog source, uninstall the existing Operator, and then install a new version of the Operator.

The following procedure explains the steps to roll back in detail.

1. Based on the edition that you want to install, click any of the following cases to download the case.
   • IBM® Sterling Order Management System Software Professional case
   • IBM Sterling Order Management System Software Enterprise case
2. Go to <case>/inventory/ibmOms<Pro/Ent>ProdSetup/resources.yaml to access information for Operator images. You can see this path only after you have downloaded and extracted the case.
   Note: Replace <case> and <Pro/Ent> with the case and edition that you are using.
3. Copy the Operator catalog image repository and tag. For example, cp.icr.io/cpopen/ibm-oms-<pro/ent>-case-catalog:<tag>.
4. Update catalog source spec.image by replacing the <updated_catalog_image> in the following example with the copied image.

   Alternatively, see the List of Operator versions, image names, and tags table to install or rollback to a specific Operator version.

   apiVersion: operators.coreos.com/v1alpha1
   kind: CatalogSource
   metadata:
     name: <name>
     namespace: <namespace>
   spec:
     displayName: <My CS Display Name>
     image: <updated_catalog_image>
     publisher: IBM
     sourceType: grpc
     updateStrategy:
       registryPoll:
         interval: <interval>
   

5. Uninstall the existing Operator.
6. Delete the existing custom resource definitions by running the following commands:

   oc delete crd omenvironments.apps.oms.ibm.com 
   oc delete crd omservers.apps.oms.ibm.com
   oc delete crd orderhubs.apps.oms.ibm.com
   oc delete crd orderservices.apps.oms.ibm.com
   oc delete crd callcenters.apps.oms.ibm.com

7. Install the new Operator from the updated catalog source. For more information about installing the Operator, see Installing Sterling Order Management System Software Operator online.
   Note: While installing the Operator, the deployment pods may restart. However, it does not impact anything.