Fix Readme
Abstract
The following document is for IBM Process Mining 2.1.0 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.1.0 |
| Update Name: | 2.1.0 IF001 |
| Fix ID: | IBM Process Mining 2.1.0-IF001 |
| Publication Date: | 30 Jan 2026 |
Contents
Components impacted
Before installation
Installing the interim fix
Performing the necessary tasks after installation
Uninstalling
List of fixes
Known Limitations
Document change history
Prerequisites and supersedes
- 2.1.0
Components impacted
- Ensure you take regular backups of any databases associated with the environment.
- 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
IBM Process Mining 2.1.0 IF001
icr.io/cpopen/processmining-operator-catalog@sha256:553024d73af5d7cdc4f10ea58bc3155c5626075435a338e0649432562194e206
- Cloud Pak Foundational Services 4.15
- DB2 120102.0.0
- IBM Licensing 4.2.18
- IBM Certificate Manager 4.2.18
- IBM Redis 1.6.11
Note: This interim fix only supports the dependencies listed above. 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, make sure to check the compatibility with other Cloud Paks' specifications.
Important interim fix details:
- Case Package: ibm-process-mining-4.0.1.tgz
- Cloud Pak Foundational Services channel: 4.15
IBM Process Mining 2.1.0 IF001 fixes are released to the v4.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.
- Scenario 1: You are installing a Production deploymentActions: 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.1.0 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 Interim Fix Dependencies 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
Uninstalling
List of Fixes
| 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 |
| 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-2026-21860, CVE-2025-66418, CVE-2025-66471, CVE-2025-66221, CVE-2025-69277, CVE-2025-59057, CVE-2025-68470, CVE-2021-31294, CVE-2025-68146, CVE-2025-67735, CVE-2025-8291 |
Known Limitations
Document change history
Was this topic helpful?
Document Information
Modified date:
30 January 2026
UID
ibm17257033