Upgrading to an Interim Fix (IF)

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.2.0 interim fixes

In addition to the regular IF upgrade procedure, you can use the following dependencies to install IBM Process Mining interim fix:

IBM Zen 6.10.3
IBM Cloud Foundational Services (CPFS) 4.19.2
ibm-pg-operator 28.4.0

Optionally, if you use metering services, you must use the following dependency:

Usage Metering Service 1.0.6

Do one of the following steps to upgrade IBM Process Mining:

Update the process mining operator with the following steps. If you are doing a fresh installation, you can skip this step and continue the installation process byInstalling the operator with command lines without Cloud Pak.
1. Update the process mining operator in Administration > CustomResourceDefinition > Catalog Source > Instances > ibm-automation-processminings .
2. Change the digest to the one mentioned and change the displayName to the case package name:
```
icr.io/cpopen/processmining-operator-catalog@sha256:9f9b93a950baaa3dc071990f8f11379ae59eaf09536136c40af88c8fd2363b38
```
3. 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.
4. 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.
5. Change the version under Spec to 2.2.0_IF00X, depending on the version you are installing.
6. Wait for the Process Mining instance status to change to Ready or UI Ready / Ready.
Alternatively, you can update the process mining operator with the following steps. If the update procedure from the previous step was successful, you can skip this step:
1. In the UI Console, go to Installed Operators and open the three-dot menu for Process Mining.
2. Uninstall the processmining operator.
3. Go to Administration > CustomResourceDefinition > Catalog Source > Instances.
4. Delete ibm-automation-processminings.
5. Create a new catalog source for ibm-automation-processminings:
```
cat <<EOF | oc apply -f -
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: ibm-automation-processminings
  namespace: ${PM_PROJECT}
spec:
  displayName: ibm-process-mining-4.2.1
  publisher: IBM
  sourceType: grpc
  image: icr.io/cpopen/processmining-operator-catalog@sha256:9f9b93a950baaa3dc071990f8f11379ae59eaf09536136c40af88c8fd2363b38
  updateStrategy:
    registryPoll:
      interval: 45m
EOF
```
6. Create a new subscription for processmining with the following command:
```
cat <<EOF | oc apply -f -
apiVersion: operators.coreos.com/v1alpha1
kind: Subscription
metadata:
  name: processmining-subscription
  namespace: ${PM_PROJECT}
spec:
  channel: v4.0
  installPlanApproval: Automatic
  name: ibm-automation-processmining
  source: ibm-automation-processminings
  sourceNamespace: ${PM_PROJECT}
EOF
```
7. 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.
8. Change the version under Spec to 2.2.0_IF00X, depending on the version you are installing.
9. Wait for the Process Mining instance status to change to Ready or UI Ready / Ready.

Do the following steps to install 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

Install IBM Zen with the following steps:

Optional: Delete the existing catalog source of IBM Zen. If you are doing a fresh installation, you can skip this step.
```
oc delete catalogsource ibm-zen-operator-catalog -n openshift-marketplace
```

Install IBM Zen 6.10.3 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
spec:
  displayName: ibm-zen-ibm-zen-6.10.3+20260713.120632.33 
  publisher: IBM
  image: icr.io/cpopen/ibm-zen-operator-catalog@sha256:1bcfdf65019d322a2d137f72bf216e80f98abfc80f8338b575d43fabf5bdebb9
  sourceType: grpc
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.10.3 with the following command:
```
oc get csv -A | grep -i "ibm-zen-operator"
```
Note: If the version does not change within 5 minutes, check the subscription, and, if needed, update the subscription channel.

Install CPFS with the following steps:

Optional: Delete the existing catalog source of CPFS If you are doing a fresh installation, you can skip this step.
```
oc delete catalogsource opencloud-operators -n openshift-marketplace
```

Install CPFS 4.19.2 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: ibm-cp-common-services-4.19.2
  publisher: IBM
  image: icr.io/cpopen/ibm-common-service-catalog@sha256:69e0b88eae426d0fcb3be2395fe20a6bf9753ba95044265e9a3f86a19bb85085
  sourceType: grpc
EOF

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

oc get catalogsource opencloud-operators -n openshift-marketplace -o jsonpath='{.status.connectionState.lastObservedState}'

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

Install ibm-pg-operator with the following steps:

Install ibm-pg-operator 28.4.0 with the following command:

cat <<EOF | oc apply -f -
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: ibm-pg-operator-catalog
  namespace: openshift-marketplace
spec:
  displayName: ibm-pg-operator-28.4.0
  publisher: IBM
  image: icr.io/cpopen/ibm-pg-operator-catalog@sha256:de4e217d062bbf110a98a5024b5e263e36673aab7262ed65423e1a6ee8304eb9
  sourceType: grpc
EOF

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

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

Wait and check if ibm-pg-operator version 28.4.0 appears with the following command:
```
oc get csv -A | grep -i "ibm-pg-operator"
```

Optional: Install Usage Metering Service 1.0.6 with the following steps:
1. Optional: Delete the existing catalog source of Usage Metering Service. If you are doing a fresh installation, you can skip this step.
```
oc delete catalogsource usage-metering-service -n openshift-marketplace
```
2. Install Usage Metering Service 1.0.6 with the following command:
```
cat <<EOF | oc apply -f -
apiVersion: operators.coreos.com/v1alpha1
kind: CatalogSource
metadata:
  name: ibm-usage-metering-catalog
  namespace: openshift-marketplace
spec:
  displayName: ibm-usage-metering-1.0.6
  publisher: IBM
  image: icr.io/cpopen/ibm-usage-metering-operator-catalog@sha256:b80738a02914c0eb08af87a7bc63226bf2b65de7add92156cc8d14673707b4dc
  sourceType: grpc
EOF
```
3. Wait and make sure the CatalogSource is in READY state with the following command:
```
oc get csv -A | grep -i "ibm-usage-metering"
```
4. Wait and check if IBM User Metering Service version changed to 1.0.6 with the following command:
```
oc get csv -A | grep -i "ibm-usage-metering-catalog"
```
  Note: If the version does not change within 5 minutes, check the subscription, and, if needed, update the subscription channel.