Upgrading the dependencies
-
You can back up the persistent data as described in Backing up and restoring data in Red Hat® OpenShift® Container Platform.
-
To upgrade your IBM Process Mining installation to a newer version, you must get access to the new operator images. For how to get access to the images, see Accessing Process Mining images.
Important: If you installed IBM Process Mining in a Cloud Pak for Business Autmation environment, ignore the following steps.
Your dependencies are automatically updated through CP4BA. To upgrade IBM Process Mining to version 2.2.0, see Upgrading the IBM Process Mining application.
Follow the sections in this topic to update the following dependencies:
- IBM Licensing 4.2.23
- IBM Certificate Manager 4.2.22
- IBM Redis 1.4.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 - Check the current
version:
oc get csv -A | grep -i "ibm-licensing-operator" - Install IBM Licensing Operator 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.23 publisher: IBM image: icr.io/cpopen/ibm-licensing-catalog@sha256:dc50f5d6e34b63d05e486bec83064a702fe60dd7ecaa0a827a154c4bf3a426d1 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.23 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.
- Delete the existing catalog source of IBM
Licensing:
- 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 - Check the current
version:
oc get csv -A | grep -i "ibm-cert-manager-operator" - Install 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.22 publisher: IBM image: icr.io/cpopen/ibm-cert-manager-operator-catalog@sha256:cdfefe057e75b30c50b1cf9f8c2a71a07b498d09bb5b74c454d3a0a7c11aa989 sourceType: grpc 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.22 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.
- Delete the existing CatalogSource with the following
command:
- Upgrade Redis operator with the following steps:
- Delete the existing version of Redis with the following command:Warning: Verify that no resource is using the previous version of Redis before deleting it.
oc get csv -A | grep -i "ibm-cloud-databases-redis" oc delete csv <name> -n ${PM_PROJECT} - Check if a subscription for the previous version of Redis exists with the following
command:
oc get subscription -n ${PM_PROJECT} | grep "cloud-databases-redis" - Optional: If an old subscription exists, delete it with the following
command:
oc delete subscription <name> -n ${PM_PROJECT} - Delete the existing CatalogSource with the following
command:
oc delete catalogsource ibm-cloud-databases-redis-operator-catalog -n ${PM_PROJECT} - Install Redis with the following command:
cat <<EOF | oc apply -f - apiVersion: operators.coreos.com/v1alpha1 kind: CatalogSource metadata: name: ibm-redis-cp-catalog namespace: ${PM_PROJECT} spec: displayName: ibm-redis-cp-1.4.0 publisher: IBM image: icr.io/cpopen/ibm-redis-cp-operator-catalog@sha256:d194a69150504735f5142099bcb97bd4767cf252dfe0d9fa4bb9fe4f6fb18618 sourceType: grpc EOF - Wait and make sure the CatalogSource is in READY state with the following
command:
oc get catalogsource ibm-redis-cp-catalog -n ${PM_PROJECT} -o jsonpath='{.status.connectionState.lastObservedState}' - Add the subscription with the following command:
cat <<EOF | oc apply -f - apiVersion: operators.coreos.com/v1alpha1 kind: Subscription metadata: name: redis-pm-subscription namespace: ${PM_PROJECT} spec: channel: v1.3 installPlanApproval: Automatic name: ibm-redis-cp source: ibm-redis-cp-catalog sourceNamespace: ${PM_PROJECT} EOF - Wait and check if Redis version changed to 1.4.0
with the following command:
oc get csv -A | grep -i "redis"You will see the following error in until you upgrade the processmining operator:constraints not satisfiable: bundle ibm-automation-processmining.v4.1.2 requires an operator providing an API with group: redis.databases.cloud.ibm.com, version: v1, kind: RedisSentinel, subscription processmining-subscription exists, subscription processmining-subscription requires @existing/processmining//ibm-automation-processmining.v4.1.2Once you upgrade the processmining operator, you should see the following message:processmining ibm-redis-cp.v1.4.0 ibm-redis-cp-controller1.4.0 Succeeded
- Delete the existing version of Redis with the following command:
Upgrading to an Interim Fix
When it is available, you can upgrade IBM Process Mining to an interim fix release. For more information, see interim fix readme files.
An interim fix is a code update to resolve security vulnerabilities and on some occasions includes defect fixes. The readme file documents the defects that are resolved along with instructions on how to install it.