Upgrading interim fix (IF) dependencies

To upgrade IBM Cloud Pak foundational services, you first need to upgrade the following dependencies:

• IBM Cert Manager 4.13
• IBM Licensing 4.13
• IBM Zen Service 6.1.3
• EDB Postgres 1.22.7

Do the following steps to upgrade IBM Cloud Pak foundational services from version 4.10.0 to version 4.12.0:

1. Log in to your Red Hat® OpenShift® Container Platform cluster with the following command:

   oc login --token=<LOGIN TOKEN> --server=https://<SERVER URL>
   

2. Upgrade IBM Certificate Manager with the following command:

   cat <<EOF | oc apply -f -
   apiVersion: operators.coreos.com/v1alpha1
   kind: CatalogSource
   metadata:
     name: ibm-cert-manager-catalog
     namespace: openshift-marketplace
   spec:
     displayName: ibm-cert-manager-4.2.13
     publisher: IBM
     sourceType: grpc
     image: icr.io/cpopen/ibm-cert-manager-operator-catalog@sha256:21866a45719eef50764c421c349a539262147d215ef87c8cc2174fdf2c269346
     updateStrategy:
       registryPoll:
         interval: 45m
   EOF
   

3. Upgrade IBM License manager with the following command:

   cat <<EOF | oc apply -f -
   apiVersion: operators.coreos.com/v1alpha1
   kind: CatalogSource
   metadata:
     name: ibm-licensing-catalog
     namespace: openshift-marketplace
   spec:
     displayName: ibm-licensing-4.2.13
     publisher: IBM
     image: icr.io/cpopen/ibm-licensing-catalog@sha256:17980ccacb1aeae19729e7d5129ad0b69e0f18a2c30f9f1a0db1daf9ae7c2e92
     sourceType: grpc
     updateStrategy:
       registryPoll:
         interval: 45m
   EOF
   

4. Upgrate the Cloud Native PostgreSQL with the following command:

   cat <<EOF | oc apply -f -
   apiVersion: operators.coreos.com/v1alpha1
   kind: CatalogSource
   metadata:
     name: cloud-native-postgresql-catalog
     namespace: openshift-marketplace
     annotations:
       bedrock_catalogsource_priority: '1'
   spec:
     displayName: Cloud Native Postgresql Catalog
     publisher: IBM
     sourceType: grpc
     image: icr.io/cpopen/ibm-cpd-cloud-native-postgresql-operator-catalog@sha256:3b867e7e0879ec24b5058e5db01c0a9be8d9d8d5ef2b7bb1bb7e247babb8b96d
     updateStrategy:
       registryPoll:
         interval: 45m
     priority: 100
   EOF
   

5. Create the catalog to upgrade IBM Cloud Pak foundational services with the following command:

   cat <<EOF | oc apply -f -
   apiVersion: operators.coreos.com/v1alpha1
   kind: CatalogSource
   metadata:
     name: opencloud-operators
     namespace: openshift-marketplace
   spec:
     displayName: IBMCS Operators
     publisher: IBM
     sourceType: grpc
     image: icr.io/cpopen/ibm-common-service-catalog:4.12.0
     updateStrategy:
       registryPoll:
         interval: 45m
   EOF
   

6. Wait for a while and verify if the catalog source is in READY state with the following command:

   echo "Catalog Source Status = $(oc get catalogsource opencloud-operators -n openshift-marketplace -o jsonpath='{.status.connectionState.lastObservedState}')"
   

7. Check which namespace the ibm-common-service-operator.v4.10.0 is installed in with the following command:

   oc get csv --all-namespaces | grep ibm-common-service-operator.v4.10.0
   

8. Update the source and channel in subscription:

   1. Go to Installed operators > IBM Cloud Pak foundational services.
   2. Open the Subscription tab.
   3. Click the pencil icon.
   4. Choose version 4.12 and save your changes.
   5. Wait for a while and check if IBM Cloud Pak foundational services are updated to version 4.12 in the Installed Operators tab or with the following command:

      oc get csv --all-namespaces | grep ibm-common-service-operator
      

9. Upgrade IBM Zen Service with the following command:

   cat <<EOF | oc apply -f -
   apiVersion: operators.coreos.com/v1alpha1
   kind: CatalogSource
   metadata:
     name: ibm-zen-operator-catalog-6-1-0
     namespace: openshift-marketplace
     annotations:
       bedrock_catalogsource_priority: '1'
   spec:
     displayName: IBM Zen Operator Catalog
     publisher: IBM
     sourceType: grpc
     image: icr.io/cpopen/ibm-zen-operator-catalog@sha256:209ea4b77b3b0863c591bcdec6f53c4c39dafcb10ff13e27ae4e1cb986a59727
     updateStrategy:
       registryPoll:
         interval: 45m
     priority: 100
   EOF
   

10. Verify that IBM Operator is updated to version 6.1.3 in Installed Operators > Zen Operator.

11. Update the Process Mining Operator in Administration > CustomResourceDefinition > Catalog Source > Instances > ibm-automation-processminings . Change the image to the one mentioned in the interim fix Readme. For more information, see IBM Support for Process Mining.

12. Wait for the status of ibm-automation-processminings to change from TRANSIENT_FAILURE to READY and for the version of Process Mining Operator to change from version 3.5.1 to 3.5.2.

13. Change the .yaml file of the Process Mining instance from 2.0.1 to 2.0.1_IF001.

14. Wait for the Process Mining instance status to change to Ready / UI Ready to complete the Interim Fix upgrade.