Upgrading Interim Fix (IF) dependencies

An interim fix is a code update to resolve security vulnerabilities and on some occasions includes defect fixes. In the readme file you can view the defects that are resolved with the specific IF upgrade. Follow the instructions to upgrade the dependencies for an interim fix release. For more information, see IBM Support.

Upgrading dependencies for IBM Process Mining 2.1.0 interim fixes

In addition to the regular IF upgrade procedure from IBM Support, you need to upgrade the following dependencies to upgrade IBM Process Mining interim fix:

IBM Licensing
IBM Certificate Manager
IBM Redis
IBM Db2
IBM Zen

Important: The following dependencies are required for all further interim fix upgrades for IBM Process Mining 2.1.0.

Do the following steps to upgrade the dependencies:

Log in to your Red Hat® OpenShift® Container Platform cluster with the following command:
```
oc login --token=<LOGIN TOKEN> --server=https://<SERVER URL>
```

Set environment variables with the following command:

export PM_PROJECT=processmining
oc project $PM_PROJECT

Upgrade IBM Licensing with the following steps:

Delete the existing catalog source of IBM Licensing:

oc delete catalogsource ibm-licensing-catalog -n openshift-marketplace

Install IBM Licensing Operator 4.2.18 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.18
  publisher: IBM
  image: icr.io/cpopen/ibm-licensing-catalog@sha256:42e8f5a12742742c1967568d497ff1c93aa7a78a3a7ad414da011d0c1eedb19a
  sourceType: grpc
  updateStrategy:
    registryPoll:
      interval: 30m0s
EOF

Wait and make sure the CatalogSource is in READY state with the following command:

oc get catalogsource ibm-licensing-catalog -n openshift-marketplace -o jsonpath='{.status.connectionState.lastObservedState}'

Wait and check if IBM Licensing Operator version changed to 4.2.18 with the following command:
```
oc get csv -A | grep -i "ibm-licensing-operator"
```
Note: If the version does not change within 5 minutes, check the subscription, and, if needed, update the subscription channel.

Upgrade IBM Certificate Manager with the following steps:

Delete the existing CatalogSource with the following command:

oc delete catalogsource ibm-cert-manager-catalog -n openshift-marketplace

Install IBM Certificate Manager 4.2.18 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.18
  publisher: IBM
  sourceType: grpc
  image: icr.io/cpopen/ibm-cert-manager-operator-catalog@sha256:78e1242e197ed1a2db82ea29887ff85b77ce39d15868fd26505fcfe7db0c3bba
  grpcPodConfig:
    securityContextConfig: restricted
EOF

Wait and make sure the CatalogSource is in READY state with the following command:

oc get catalogsource ibm-cert-manager-catalog -n openshift-marketplace -o jsonpath='{.status.connectionState.lastObservedState}'

Wait and check if IBM Certificate Manager version changed to 4.2.18 with the following command:
```
oc get csv -A | grep -i "ibm-cert-manager-operator"
```
Note: If the version does not change within 5 minutes, check the subscription, and, if needed, update the subscription channel.

Upgrade Redis operator with the following steps:

Delete the existing CatalogSource with the following command:

oc delete catalogsource ibm-cloud-databases-redis-operator-catalog -n ${PM_PROJECT}

Install Redis 1.6.11 with the following command:

cat <<EOF | oc apply -f -
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: ibm-cloud-databases-redis-operator-catalog
  namespace: ${PM_PROJECT}
spec:
  displayName: ibm-cloud-databases-redis-operator-catalog
  publisher: IBM
  image: icr.io/cpopen/ibm-cloud-databases-redis-catalog@sha256:dbdafdc70600a84099bd11df76b7a6728cbada513a1e06fefbc08f38406e3636
  sourceType: grpc
  updateStrategy:
    registryPoll:
      interval: 30m0s
EOF

Wait and make sure the CatalogSource is in READY state with the following command:

oc get catalogsource ibm-cloud-databases-redis-operator-catalog -n ${PM_PROJECT} -o jsonpath='{.status.connectionState.lastObservedState}'

Wait and check if Redis version changed to 1.6.11 with the following command:
```
oc get csv -A | grep -i "ibm-cloud-databases-redis"
```
Note: If the version does not change within 5 minutes, check the subscription, and, if needed, update the subscription channel.

Upgrade IBM Db2 Operator with the following command:

Delete the existing CatalogSource with the following command:

oc delete catalogsource ibm-db2uoperator-catalog -n ${PM_PROJECT}

Install IBM Db2 Operator 120102.0.0 with the following command:

cat <<EOF | oc apply -f -
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: ibm-db2uoperator-catalog
  namespace: ${PM_PROJECT}
spec:
  displayName: ibm-db2uoperator-7.5.1+20251217.121408.18568
  publisher: IBM
  image: icr.io/cpopen/ibm-db2uoperator-catalog@sha256:6d49da4d00ed5c7847dab102e281d72c5f38bdb7cf067dd7ab8bef66af838814
  sourceType: grpc
EOF

Wait and make sure the catalogSource is in READY state with the following command:

oc get catalogsource ibm-db2uoperator-catalog -n ${PM_PROJECT} -o jsonpath='{.status.connectionState.lastObservedState}'

Wait and check if IBM Db2 Operator version changed to 120102.0.0 with the following command:
```
oc get csv -A | grep -i "db2u-operator"
```
Note: If the version does not change within 5 minutes, check the subscription, and, if needed, update the subscription channel.

Upgrade IBM Zen with the following steps:

Delete the existing catalog source of IBM Zen:

oc delete catalogsource ibm-zen-operator-catalog -n openshift-marketplace

Install IBM Zen 6.2.2 with the following command:

cat <<EOF | oc apply -f -
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: ibm-zen-operator-catalog
  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:3649e630c48377b19606e28dbfe7955d87e652a4a3927bf258746b16cfea1297
  priority: 100
  grpcPodConfig:
    securityContextConfig: restricted
EOF

Wait and make sure the CatalogSource is in READY state with the following command:

oc get catalogsource ibm-zen-operator-catalog -n openshift-marketplace -o jsonpath='{.status.connectionState.lastObservedState}'

Wait and check if IBM Zen version changed to 6.2.2 with the following command:
```
oc get csv -A | grep -i "ibm-zen-operator-catalog"
```
Note: If the version does not change within 5 minutes, check the subscription, and, if needed, update the subscription channel.

Update the Process Mining Operator in Administration > CustomResourceDefinition > Catalog Source > Instances > ibm-automation-processminings . Change the digest to the one mentioned in the interim fix Readme and change the displayName to the case package name. For more information, see IBM Support.
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 to the one listed in the readme.
Once the Operator is Ready, verify that all Pods are in Running or Completed state and open Installed Operators > Process mining > instances > pminstance > yaml tab.
Change the version under Spec to 2.1.0_IF00X, depending on the version you are installing.
Wait for the Process Mining instance status to change to Ready or UI Ready / Ready.