IBM Support

Readme for IBM Process Mining 2.0.2 IF001

Fix Readme


Abstract

The following document is for IBM Process Mining 2.0.2 IF001. It includes the CASE package download, installation information, and the list of Known Issues that are resolved in this fix.

Content

Readme file for: IBM Process Mining
Product Release: 2.0.2
Update Name: 2.0.2 IF001
Fix ID: IBM Process Mining 2.0.2-IF001
Publication Date: 29 August 2025

Before installation
  1. Ensure you take regular backups of any databases associated with the environment.
  2. Ensure that your operators and pods are in a healthy state before upgrading.
    If one or more operators or pods are failing, then it can prevent the system from completing an upgrade.
    Check status of Pods, Operators, Routes
    It is recommended to check statuses to ensure there are no failures and the statuses appear ready for the various installed components. Check the status of the following instances when they exist: Processmining

Installing the interim fix

This interim fix contains the following versions of IBM Process Mining, Cloud Pak Foundational Services (CPFS) and DB2:
  • IBM Process Mining 2.0.2 IF001 
    icr.io/cpopen/processmining-operator-catalog@sha256:9af62debf337ac5ad2dcbecdfec0283f9c38b1c0c9d3f3f15a73e4efb0b7d33e
  • Cloud Pak Foundational Services 4.12
  • DB2 11.5.9.0
Note:  This interim fix only supports the Cloud Pak Foundational Services and DB2 listed above. It is important that you deploy or upgrade IBM Process Mining by using the catalog sources in this readme document (the same catalog sources are also in the referenced CASE package).  If you have other Cloud Paks installed on the same OCP cluster, be sure to check the compatibility of the Cloud Pak Foundational Services and DB2 versions listed above, with other Cloud Paks' specifications.
Important interim fix details:
IBM Process Mining 2.0.2 IF001 fixes are released to the v3.0 operator channel. Once the operators are upgraded, it triggers rolling updates for all the pods it manages, to ensure they are updated to the appropriate version to match the operator.
 
Depending on the current setup and state of your existing environment, there are various upgrade actions that need to be taken. The following scenarios cover what actions might be needed for a particular setup.
  • Scenario 1: You are installing a Production deployment
    Actions: You can use this interim fix content to perform a Production deployment.  To deploy a Production deployment that uses the content of this fix, see installing on Red Hat OpenShift Container Platform environments and use the CASE package from this fix.
  • Scenario 2:  Your installation is 2.0.2 and is online
    Actions: 
    You can use this interim fix content to perform an upgrade of a Production deployment. To deploy an upgrade of a Production deployment using the content of this interim fix, see upgrading in Red Hat OpenShift Container Platform environments and use the CASE package from this interim fix. Ensure you use the correct operator-catalog digest (see above) .

Performing the necessary tasks after installation

Review the installation
If you are interested in verifying the expected image digest for a particular image, then you can review the ibm-process-mining/inventory/processMiningOperatorSetup/resources.yaml file in the CASE package. This file has a listing of the images managed by the Process Mining operator and their expected digest for this particular interim fix level.

Uninstalling

There is no procedure to uninstall the interim fix.

List of Fixes

Known Issues fixed by this interim fix are listed in the following tables.
The columns are defined as follows: 
Column title Column description
Known Issue -
Title -
Sec. A mark indicates a defect related to security
Cont. A mark indicates a defect specific to the Cloud Pak integration of the component
B.I. A mark indicates the fix has a business impact. Details are found in the title column or the Known Issue document
IBM Process Mining
Known Issue Title Sec. Cont. B.I.
N/A
IBM Process Mining delivers container images that include operating system level and other open source libraries. Vulnerabilities (CVEs) for these libraries are published regularly.
 
This interim fix includes fixes for these libraries to address: 
 CVE-2025-5889, CVE-2025-48924, CVE-2025-5878, CVE-2025-7783, CVE-2025-30749, CVE-2025-30754, CVE-2025-50059, CVE-2025-50106, CVE-2025-27817, CVE-2025-53864, CVE-2025-48379, CVE-2025-31672, CVE-2025-4565, CVE-2024-47081  CVE-2025-41234, CVE-2025-54121, CVE-2025-49125, CVE-2025-48988, CVE-2025-52520, CVE-2025-48976, CVE-2025-53506

Known Limitations

Document change history

  • 29th August 2025: Initial publish.

    • [{"Type":"MASTER","Line of Business":{"code":"LOB76","label":"Data Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSB8W0H","label":"IBM Process Mining"},"ARM Category":[{"code":"a8m3p0000006whjAAA","label":"IBM Process Mining"}],"ARM Case Number":"","Platform":[{"code":"PF016","label":"Linux"}],"Version":"All Versions"}]

    Document Information

    Modified date:
    29 August 2025

    UID

    ibm17242544

    Page Feedback