IBM Support

Readme for IBM Cloud Pak for Business Automation 24.0.0 IF007

Fix Readme


Abstract

The following document is for IBM Cloud Pak for Business Automation 24.0.0 IF007. It includes the CASE package download, installation information, and the list of APARs/Known Issues that are resolved in this interim fix.

Content

Readme file for:IBM Cloud Pak® for Business Automation
Product Release:24.0.0
Update Name:24.0.0 IF007
Fix ID:24.0.0-WS-CP4BA-IF007
Publication Date:30 October 2025
 

Before installation

  1. Ensure you take regular backups of any databases associated with the environment.
  2. Ensure your operators are in a healthy state, before upgrading.   
    If one or more operators are failing, then it can prevent the system from completing an upgrade.  
    It is recommended to check a few of the important CR statuses to ensure there are not failures and the statuses appear ready for the various installed components. Check the status of the following CRs when they exist:
  3. oc get icp4acluster -o yaml 
            oc get content -o yaml
            oc get Foundation -o yaml
  4. Remove any image settings in CRs  
    If you used any individual image tag settings in your CRs, it could prevent the operator from updating the images to the appropriate version. Ensure you remove any of these settings when you upgrade. This doesn't apply to starter installation as it requires a new install.
 

Installing the interim fix

This interim fix contains the following version of Cloud Pak for Business Automation and Cloud Pak Foundational Services (CPFS):
  • Cloud Pak for Business Automation 24.0.0-IF007
  • Cloud Pak Foundational Services 4.6.18
Note:  This interim fix only supports the Cloud Pak Foundational Services listed above. It is important that you deploy or upgrade Cloud Pak for Business Automation using the catalog sources in this readme document.  If you have other Cloud Paks installed on the same OCP cluster, be sure to check the compatibility of the Cloud Pak Foundational Services versions listed above with other Cloud Paks' specifications.
 
 
Cloud Pak for Business Automation (CP4BA) 24.0.0 interim fixes are released to the v24.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.
 

Upgrading with MongoDB embedded services.
If you are upgrading with embedded MongoDB database of IBM Automation Decision Services or IBM Automation Document Processing. Please check the FCV(FeatureCompatibilityVersion) version before upgrading. If the FCV version is 5.0, you will need to manually set the FCV version to 6.0. If FCV version is 6.0, you do not need to perform the following commands.

Note: The appropriate MongoDB client binary (mongo or mongosh) depends on the version of CP4BA installed currently. If any of the commands below return a mongo: command not found error, re-run them using the alternate client (mongosh).

  1. Identify the the MongoDB pod by running the command below to get the podID.

    kubectl get pods | grep icp4adeploy-mongo

  2. Check the FCV version by running the command below.
    Note: $MONGO_INITDB_ROOT_USERNAME is the value from file /etc/credentials/admin/MONGO_ROOT_USERNAME and $MONGO_INITDB_ROOT_PASSWORD is the value from file /etc/credentials/admin/MONGO_ROOT_PASSWORD. You can find the MONGO_ROOT_USERNAME and MONGO_ROOT_PASSWORD files in the Mongo pod.

    For Automation Document Processing:

    kubectl exec icp4adeploy-mongo-deploy-<podID> –- bash -c 'mongo -u "$MONGO_INITDB_ROOT_USERNAME" -p "$MONGO_INITDB_ROOT_PASSWORD" --eval "db.adminCommand({getParameter: 1, featureCompatibilityVersion: 1})"'

    For Automation Decision Services:

    kubectl exec icp4adeploy-mongo-deploy-<podID> -- bash -c 'mongo --norc --tls --tlsAllowInvalidCertificates -u "$MONGO_INITDB_ROOT_USERNAME" -p "$MONGO_INITDB_ROOT_PASSWORD" --eval "db.adminCommand({getParameter: 1, featureCompatibilityVersion: 1})"'
  3. If the FCV version is 5.0 you need to set the FCV version to 6.0. If FCV version is 6.0, you do not need to perform the following commands. 

  4.  Upgrade to FCV version to 6.0.

    kubectl exec icp4adeploy-mongo-deploy-<podID> -- bash -c 'mongo --norc --tls --tlsAllowInvalidCertificates -u "$MONGO_INITDB_ROOT_USERNAME" -p "$MONGO_INITDB_ROOT_PASSWORD" --eval "db.adminCommand({ setFeatureCompatibilityVersion: \"6.0\" })"'

  5. Verify the FCV version is 6.0.

    kubectl exec icp4adeploy-mongo-deploy-<podID> -- bash -c 'mongo --norc --tls --tlsAllowInvalidCertificates -u "$MONGO_INITDB_ROOT_USERNAME" -p "$MONGO_INITDB_ROOT_PASSWORD" --eval "db.adminCommand({getParameter: 1, featureCompatibilityVersion: 1})"'
 
 
 
NOTE :  

If you have deployed Automation Document Processing as a part of your CP4BA deployment and the deployment is configured with a IBM Security Directory Server ( SDS / TDS) LDAP , do not upgrade to this interim fix.The issue is likely to be resolved in an upcoming interim fix, so regularly review the Automation Document Processing Known Limitations for this update.  

If you have deployed Automation Document Processing as a part of your CP4BA deployment and the deployment is configured with a Microsoft Active Directory ( MSAD) LDAP , you must follow the post upgrade steps listed in Completing the IBM Automation Document Processing upgrade after upgrading to this 24.0.0 interim fix.
 
Automation Document Processing is not supported for a CP4BA Starter Deployment with this interim fix.
 
 
Step 1: Download the installation and upgrade scripts

  1. Download the 24.0.0 IF007 branch by using the following git clone command.

    git clone -b 24.0.0-IF007 https://github.com/icp4a/cert-kubernetes.git
 
Step 2:  Perform an online/offline fresh installation or an upgrade on an existing online/offline deployment.
 
Depending on the current setup and state of your existing environment, there are various actions that need to be taken. The following scenarios cover what actions might be needed for a particular setup.  
 

For an upgrade scenario, these are the Cloud Pak foundational services migration modes supported -

Migration Mode Support
Cluster-scoped to Namespace-scopedSupported (This is the recommended approach if your current deployment is using cluster-scoped CPFs)
Namespace-scoped to Namespace-scopedSupported (If your CPFs deployment is already namespace-scoped, then continue to remain at namespace-scoped)
Cluster-scoped to Cluster-scoped Not Supported (Please follow the recommended upgrade from Cluster-scoped to Namespace-scoped for CPFs)
Cluster-scoped ("All namespaces") to Cluster-scoped ("All namespaces")Supported  ( There is no migration path from Cluster-scoped ("All namespaces") to Namespace-scoped )


Note: The recommended migration mode for an instance with cluster scoped Cloud Pak foundational services is to namespace scoped Cloud Pak foundational services.

 
  • Scenario 1: You are installing a Starter deployment online or have an existing online Starter deployment
    Warning: If you have an existing Cloud Pak Foundation Services instance installed at the cluster scoped level or in the namespace where CP4BA is being installed, then it is not supported. The Starter deployment of CP4BA is only supported when deploying into a new namespace without CPFs.  
    Actions: Starter deployments do not support upgrades; however, you can use this interim fix content to perform a Starter deployment. To deploy a Starter deployment using the content of this interim fix, please see install a new Starter environment and use the installation scripts from the branch that you cloned above.
  • Scenario 2: You are installing online Production deployment  
    Warning: If you have an existing Cloud Pak Foundation Services instance installed at the cluster scoped level or in the namespace where CP4BA is being installed, then it is not supported. The Production deployment of CP4BA is only supported when deploying into a new namespace without CPFs.
    Actions: To deploy an online Production deployment without using a local registry, please follow steps in install a new online Production environment and use the installation scripts from the branch that you cloned above.
  • Scenario 3: You are installing offline/airgap Production deployment
    Warning: If you have an existing Cloud Pak Foundation Services instance installed at the cluster scoped level or in the namespace where CP4BA is being installed, then it is not supported. The Production deployment of CP4BA is only supported when deploying into a new namespace without CPFs.
    Note: As prerequisites for this scenario, you must follow steps here to set up the bastion host to mirror images to the registry and further to set up the private registry. The mirroring of images can be completed using "oc mirror" for the mirroring images process. If you are looking to install only a set of capabilities then you can make use of filters listed in Table 1 so that you can only download the specific set of images that you require. Please note that if the set of capabilities includes Business Automation Workflow,Process Federation Server,Workflow Process Service or Business Automation Insights make sure to include the filter "ibm_es_1_1_2470" .
    Actions:

    1. To deploy an airgap/offline Production deployment, find mirror file cp4ba-case-to-be-mirrored-24.0.0-IF007.txt for this interim fix from the branch that you cloned above under the scripts/airgap directory. Execute this command from your bastion host to download the CASE files.

      oc ibm-pak get -c file://(absolute path to file)/cp4ba-case-to-be-mirrored-24.0.0-IF007.txt

      The absolute path to file needs to be a path starting from "/". For example, "/opt".

    2. You will need to mirror the images associated with the new cp4ba-case-to-be-mirrored-24.0.0-IF007.txt mirror file. 

      export CASE_NAME=ibm-cp-automation
                                export CASE_VERSION=24.0.7
                                export CASE_INVENTORY_SETUP=cp4aOperatorSetup
                                export TARGET_REGISTRY=<target-registry>
                                export NAMESPACE=<cp4ba_namespace_name>

      Follow the instructions for either mirroring option in Mirroring images to the private registry using the new CASE version associated with this interim fix.

    3. Login to the cluster and go to namespace for the operator from the bastion host.

      oc login https://<CLUSTERIP>:<port> -u <ADMINISTRATOR>
                                oc project ${NAMESPACE}
    4. From your bastion host, install the catalog sources and operators using the steps listed in Install Catalog Source and Operators using cluster admin script.
    5. Follow the remaining steps from Question 6 listed here to complete the installations of offline/airgap Production deployment.
  • Scenario 4: Your installed Production deployment version is 21.0.3 IF031 or newer.  
    Note: Direct upgrade from versions prior to 21.0.3 IF031 are not supported. If you are upgrading from a prior version then you would need to perform incremental upgrading using the instructions from each prior version to 21.0.3 IF031 or newer.  
    Warning:  
    All instructions to download the installation and upgrade scripts in the Knowledge Center links referenced below can be ignored. Instead use the installation and upgrade scripts downloaded in Step 1.  
    Actions:    
    For online upgrade, follow the upgrade instructions documented in Upgrading CP4BA multi-pattern clusters from 21.0.3.  
    For offline upgrade, you must first complete the prerequisites by following steps here to set up the bastion host to mirror images to the registry and further to set up the private registry. The mirroring of images can be completed using "oc mirror" for the mirroring images process. Once the mirroring of images is completed, follow the upgrade instructions documented in Upgrading CP4BA multi-pattern clusters from 21.0.3.
  • Scenario 5: Your installed Production deployment version is 22.0.2 IF006 .  
    Note: Direct upgrade from versions prior to 22.0.2 IF006 are not supported. If you are upgrading from a prior version then you would need to perform incremental upgrading using the instructions from each prior version to 22.0.2 IF006.  
    Warning:  
    All instructions to download the installation and upgrade scripts in the Knowledge Center links referenced below can be ignored. Instead use the installation and upgrade scripts downloaded in Step 1.  
    Actions:    
    For online upgrade, follow the upgrade instructions documented in Upgrading CP4BA multi-pattern clusters from 22.0.2 in online environment.  
    For offline upgrade, you must first complete the prerequisites by following steps here to set up the bastion host to mirror images to the registry and further to set up the private registry. The mirroring of images can be completed using "oc mirror" for the mirroring images process. Once the mirroring of images is completed, follow the upgrade instructions documented in Upgrading CP4BA multi-pattern clusters from 22.0.2 in online environment.
  • Scenario 6: Your installed Production deployment version is 23.0.2 IF006 (If you do not have 23.0.2 IF006 you need to upgrade to 23.0.2 IF006 before proceeding with this upgrade).  
    Warning:  
    All instructions to download the installation and upgrade scripts in the Knowledge Center links referenced below can be ignored. Instead use the installation and upgrade scripts downloaded in Step 1.  
    Actions:    
    For online upgrade, follow the upgrade instructions documented in Upgrading CP4BA multi-pattern clusters from 23.0.2 in online environment.  
    For offline upgrade, you must first complete the prerequisites by following steps here to set up the bastion host to mirror images to the registry and further to set up the private registry. The mirroring of images can be completed using "oc mirror" for the mirroring images process. Once the mirroring of images is completed, follow the upgrade instructions documented in in Upgrading CP4BA multi-pattern clusters from 23.0.2 in online environment.
  • Scenario 7:  Your installed Production deployment is 24.0.0 GA or newer and is online.

    Note:  
    For a dedicated deployment or namespace scoped deployment, the value for < CP4BA Namespace >  should be the namespace where all IBM Cloud Pak foundational services/CP4BA Operators and Services are deployed. If the CP4BA Operators and Services are deployed in different namespaces( separation of duties), the value for < CP4BA Namespace > should be the namespace where all IBM Cloud Pak foundational services/CP4BA Operators are deployed in.  
    Warning:  
    For a CP4BA Deployment with BAI ( Business Automation Insights ) selected as an optional component, it is recommended to create BAI savepoints before starting the upgrade process to this interim fix. For Flink event processing to resume from its previous state, savepoints are required to be created before the upgrade and specified in the updated CR. BAI savepoints can be created by following the below steps.

    •  Retrieve the name of the InsightsEngine custom resource file.

      InsightsEngine_CR=$(kubectl get InsightsEngine --no-headers --ignore-not-found -n <CP4BA-Namespace> -o name)
      Retrieve and export the below details.
      export MANAGEMENT_URL=$(kubectl get ${InsightsEngine_CR} --no-headers --ignore-not-found -n <CP4BA Namespace> -o jsonpath='{.status.components.management.endpoints[?(@.scope=="External")].uri}')
                                            export MANAGEMENT_AUTH_SECRET=$(kubectl get ${InsightsEngine_CR} --no-headers --ignore-not-found -n <CP4BA Namespace> -o jsonpath='{.status.components.management.endpoints[?(@.scope=="External")].authentication.secret.secretName}')
                                            export MANAGEMENT_USERNAME=$(kubectl get secret ${MANAGEMENT_AUTH_SECRET} --no-headers --ignore-not-found -n <CP4BA Namespace> -o jsonpath='{.data.username}' | base64 -d)
                                            export MANAGEMENT_PASSWORD=$(kubectl get secret ${MANAGEMENT_AUTH_SECRET} --no-headers --ignore-not-found -n <CP4BA Namespace> -o jsonpath='{.data.password}' | base64 -d)

      Create BAI savepoints and store them in a temporary file called bai.json.

      curl -X POST -k -u ${MANAGEMENT_USERNAME}:${MANAGEMENT_PASSWORD} "${MANAGEMENT_URL}/api/v1/processing/jobs/savepoints" -o ./bai.json

       Scale down the CP4BA and Insights Engine Operator.

      oc scale --replicas=0 deployment ibm-cp4a-operator
                                                oc scale --replicas=0 deployment ibm-insights-engine-operator

    • Retrieve the recovery path locations for each BAI component for which BAI savepoints are created from ./bai.json and update the bai_configuration section of the custom resource file. For Example: If there is a BAI savepoint being created for navigator component, then the updated custom resource file should have the below configuration.

      bai_configuration:
                                    navigator:
                                       recovery_path: /mnt/pv/savepoints/dba/bai-navigator/savepoint-fb88f4-42027046b73b
                                    ... 
                                    # Add recovery_path for all other components
    • Once the upgrade has been completed, make sure to remove all instances of the recovery_path parameters from the updated custom resource file.

    Actions:   
    From the branch that you cloned above navigate to the scripts directory and perform the following steps to upgrade the CP4BA operators and deployment.

    1. Upgrade the CP4BA operators.
      • Warning:   
        The script with the upgradeOperator option will scale the CP4BA Operators down to zero. You must execute the script with the upgradeDeploymentStatus mode to scale them back in. 

      • Actions:  
        Run the cp4a-deployment.sh script with the upgradeOperator option to upgrade the IBM Cloud Pak foundational services/CP4BA operators:  
         

        ./scripts/cp4a-deployment.sh -m upgradeOperator -n <CP4BA Namespace>

    2. Wait for the operators to complete their upgrades.  
      By default all subscriptions are set to automatic, but if you have any subscriptions set to manual then you need to approve any pending InstallPlans.  
      Use the below command to see the current status of the install plans.

      oc get installPlan

      The upgrade will be blocked, if any of the needed InstallPlans are not approved. It is not recommended to set subscriptions to manual as this makes the upgrade more error prone.

    3. You can use the following scripts to check the status of the upgrades.
      • Warning:  
        The script will scale the CP4BA deployments down to zero. You must execute the cp4a-deployment.sh script with upgradeDeploymentStatus option to scale them back up.

      • Actions:  
        [OPTIONAL] Run the cp4a-deployment.sh script with upgradeOperatorStatus option to check that the upgrade of the CP4BA operator and its dependencies is successful:

        ./scripts/cp4a-deployment.sh -m upgradeOperatorStatus -n <CP4BA Namespace>

    4. Start up the upgraded CP4BA Operators.  
      Run the cp4a-deployment.sh script with upgradeDeploymentStatus option to check that the upgrade of the CP4BA deployment is successful:

      ./scripts/cp4a-deployment.sh -m upgradeDeploymentStatus -n <CP4BA Namespace>


      Note: If you are using the P8BPMREST CPE end point, you must wait for the CPE components status to display "Done" and then execute the below command to make it accessible.

      kubectl patch zenextension <CUSTOM_RESOURCE_FILENAME>-cpe-zen-extension -n <CP4BA NAMESPACE> --type=merge -p '{"metadata": {"annotations": {"checksum_cpe_ips": "0"}}}'
    • Scenario 8:  Your installed Production deployment is 24.0.0  GA or newer and using airgap/offline.

      Note:  
      As prerequisites for this scenario, you must follow steps here to set up the bastion host to mirror images to the registry and further to set up the private registry.  
      For a dedicated deployment or namespace scoped deployment, the value for < CP4BA Namespace >  should be the namespace where all IBM Cloud Pak foundational services/CP4BA Operators and Services are deployed. If the CP4BA Operators and Services are deployed in different namespaces( separation of duties), the value for < CP4BA Namespace > should be the namespace where all IBM Cloud Pak foundational services/CP4BA Operators are deployed in.   
      Warning:  
      For a CP4BA Deployment with BAI ( Business Automation Insights ) selected as an optional component, it is recommended to create BAI savepoints before starting the upgrade process to this interim fix.  For Flink event processing to resume from its previous state, savepoints are required to be created before the upgrade and specified in the updated CR. BAI savepoints can be created by following the below steps.

      •  Retrieve the name of the InsightsEngine custom resource file.

        InsightsEngine_CR=$(kubectl get InsightsEngine --no-headers --ignore-not-found -n <CP4BA-Namespace> -o name)
        Retrieve and export the below details.
        export MANAGEMENT_URL=$(kubectl get ${InsightsEngine_CR} --no-headers --ignore-not-found -n <CP4BA Namespace> -o jsonpath='{.status.components.management.endpoints[?(@.scope=="External")].uri}')
                                                    export MANAGEMENT_AUTH_SECRET=$(kubectl get ${InsightsEngine_CR} --no-headers --ignore-not-found -n <CP4BA Namespace> -o jsonpath='{.status.components.management.endpoints[?(@.scope=="External")].authentication.secret.secretName}')
                                                    export MANAGEMENT_USERNAME=$(kubectl get secret ${MANAGEMENT_AUTH_SECRET} --no-headers --ignore-not-found -n <CP4BA Namespace> -o jsonpath='{.data.username}' | base64 -d)
                                                    export MANAGEMENT_PASSWORD=$(kubectl get secret ${MANAGEMENT_AUTH_SECRET} --no-headers --ignore-not-found -n <CP4BA Namespace> -o jsonpath='{.data.password}' | base64 -d)

        Create BAI savepoints and store them in a temporary file called bai.json.

        curl -X POST -k -u ${MANAGEMENT_USERNAME}:${MANAGEMENT_PASSWORD} "${MANAGEMENT_URL}/api/v1/processing/jobs/savepoints" -o ./bai.json

         Scale down the CP4BA and Insights Engine Operator.

        oc scale --replicas=0 deployment ibm-cp4a-operator
                                                        oc scale --replicas=0 deployment ibm-insights-engine-operator

      • Retrieve the recovery path locations for each BAI component for which BAI savepoints are created from ./bai.json and update the bai_configuration section of the custom resource file. For Example: If there is a BAI savepoint being created for navigator component, then the updated custom resource file should have the below configuration.

        bai_configuration:
                                          navigator:
                                            recovery_path: /mnt/pv/savepoints/dba/bai-navigator/savepoint-fb88f4-42027046b73b
                                          ... 
                                          # Add recovery_path for all other components
      • Once the upgrade has been completed, make sure to remove all instances of the recovery_path parameters from the updated custom resource file.

      Actions:    
      Perform the following steps and then the upgrade of operators and deployments will start.

      1. To upgrade an airgap/offline Production deployment, find mirror file cp4ba-case-to-be-mirrored-24.0.0-IF007.txt for this interim fix from the branch that you cloned above under the scripts/airgap directory. Execute this command from your bastion host to download the CASE files:

        oc ibm-pak get -c file://(absolute path to file)/cp4ba-case-to-be-mirrored-24.0.0-IF007.txt

        The (absolute path to file) needs to be a path starting from "/". For example, "/opt".

      2. You will need to mirror the images associated with the new cp4ba-case-to-be-mirrored-24.0.0-IF007.txt mirror file. 

        export CASE_NAME=ibm-cp-automation
                                                export CASE_VERSION=24.0.7
                                                export CASE_INVENTORY_SETUP=cp4aOperatorSetup
                                                export TARGET_REGISTRY=<target-registry>
                                                export NAMESPACE=<cp4ba_namespace_name>

        Follow the instructions for either mirroring option in Mirroring images to the private registry using the new CASE version associated with this interim fix. If you are looking to install only a set of capabilities then you can make use of filters listed in Table 1 so that you can only download the specific set of images that you require.Please note that if the set of capabilities includes Business Automation Workflow,Process Federation Server,Workflow Process Service or Business Automation Insights make sure to include the filter "ibm_es_1_1_2470"

         
      3.  From the branch that you cloned above navigate to the scripts directory and perform the following steps to upgrade the CP4BA operators.
        • Warning:   
          The script with the upgradeOperator option will scale the CP4BA Operators down to zero. You must execute the script with the upgradeDeploymentStatus mode to scale them back in. 

        • Actions:  
          Run the cp4a-deployment.sh script with the upgradeOperator option to upgrade the IBM Cloud Pak foundational services/CP4BA operators:  
           

          ./scripts/cp4a-deployment.sh -m upgradeOperator -n <CP4BA Namespace>

      4. Wait for the operators to complete their upgrades.  
        By default all subscriptions are set to automatic, but if you have any subscriptions set to manual then you need to approve any pending InstallPlans.  
        Use the below command to see the current status of the install plans.

        oc get installPlan

        The upgrade will be blocked, if any of the needed InstallPlans are not approved. It is not recommended to set subscriptions to manual as this makes the upgrade more error prone.

      5. You can use the following scripts to check the status of the upgrades.

        • Actions:  
          [OPTIONAL] Run the cp4a-deployment.sh script with upgradeOperatorStatus option to check that the upgrade of the CP4BA operator and its dependencies is successful:

          ./scripts/cp4a-deployment.sh -m upgradeOperatorStatus -n <CP4BA Namespace>

      6. Start up the upgraded CP4BA Operators.  
        Run the cp4a-deployment.sh script with upgradeDeploymentStatus option to check that the upgrade of the CP4BA deployment is successful:

        ./scripts/cp4a-deployment.sh -m upgradeDeploymentStatus -n <CP4BA Namespace>


        Note: If you are using the P8BPMREST CPE end point, you must wait for the CPE components status to display "Done" and then execute the below command to make it accessible.

        kubectl patch zenextension <CUSTOM_RESOURCE_FILENAME>-cpe-zen-extension -n <CP4BA NAMESPACE> --type=merge -p '{"metadata": {"annotations": {"checksum_cpe_ips": "0"}}}'
 

Performing the necessary tasks after installation

 
a. Review the installation
It is recommended that you review the CR yaml status section and operator logs after the upgrade to ensure there are no failures preventing your pods from upgrading.
oc get icp4acluster icp4adeploy -o yaml > CP4BAconfig.yaml
                oc logs deployment/ibm-cp4a-operator -c operator > operator.log
If you are interested in verifying the expected image digest for a particular image, then you can review the ibm-cp-automation\inventory\cp4aOperatorSdk\resources.yaml file in the CASE package. This file has a listing of the images managed by the CP4BA operator and their expected digest for this particular interim fix level.
 
 

Uninstalling

There is no procedure to uninstall the interim fix.
 

List of Fixes

APARs/Known Issues fixed by this interim fix are listed in the following tables.
 
The columns are defined as follows: 
 
Column titleColumn description
APAR/Known IssueThe defect number
TitleA short description of the defect
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 APAR/Known Issue document
 
General
Known IssueTitleSec.Cont.B.I.
N/A
Cloud Pak for Business Automation 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-2021-3200,CVE-2021-33928,CVE-2021-33929,CVE-2021-33930,CVE-2021-33938,CVE-2021-44568,CVE-2021-46877,CVE-2022-1705,CVE-2022-25883,CVE-2022-48303,CVE-2022-48468,CVE-2023-2727,CVE-2023-2728,CVE-2023-31484,CVE-2023-4039,CVE-2023-43804,CVE-2023-52969,CVE-2023-52970,CVE-2023-52971,CVE-2024-23337,CVE-2024-28863,CVE-2024-38816,CVE-2024-38819,CVE-2024-38827,CVE-2024-40635,CVE-2024-47252,CVE-2024-52615,CVE-2024-7143,CVE-2024-9042,CVE-2025-0426,CVE-2025-10059,CVE-2025-10060,CVE-2025-10061,CVE-2025-10148,CVE-2025-1634,CVE-2025-22227,CVE-2025-22228,CVE-2025-22233,CVE-2025-22874,CVE-2025-23048,CVE-2025-23166,CVE-2025-27553,CVE-2025-30474,CVE-2025-30693,CVE-2025-30722,CVE-2025-30749,CVE-2025-30754,CVE-2025-4575,CVE-2025-48060,CVE-2025-4877,CVE-2025-48795,CVE-2025-49574,CVE-2025-49795,CVE-2025-49812,CVE-2025-50059,CVE-2025-50106,CVE-2025-5115,CVE-2025-5187,CVE-2025-5222,CVE-2025-54410,CVE-2025-55163,CVE-2025-5702,CVE-2025-58050,CVE-2025-58058,CVE-2025-58457,CVE-2025-58754,CVE-2025-59343,CVE-2025-59937,CVE-2025-5994,CVE-2025-61911,CVE-2025-61912,CVE-2025-6707,CVE-2025-7338,CVE-2025-7339,CVE-2025-7783,CVE-2025-9231,DSA-6015-1,RHSA-2025:10699,RHSA-2025:11402,RHSA-2025:11804,RHSA-2025:11884,RHSA-2025:12083,RHSA-2025:12519,RHSA-2025:12746,RHSA-2025:13578,RHSA-2025:14420,RHSA-2025:14557,RHSA-2025:14862,RHSA-2025:14900,RHSA-2025:15007,RHSA-2025:15010,RHSA-2025:15019,RHSA-2025:15023,RHSA-2025:15099,RHSA-2025:4244,RHSA-2025:7067,RHSA-2025:7076,RHSA-2025:7077,RHSA-2025:8655,RHSA-2025:9430,RHSA-2025:9431,RHSA-2025:9877
 
Previous interim fixes have included fixes which are also addressed with this interim fix. Consult the Related links section for readmes of previous interim fixes, at the bottom of this document.
   

 

Back to top

Cloud Pak for Business Automation Operator
Known IssueTitleSec.Cont.B.I.
N/AN/A   

 

Back to top

Automation Document Processing
Known IssueTitleSec.Cont.B.I.
DT449468Content Analyzer custom annotations not working XX
DT452617AxiosError: Request failed with status code 500 when deploying a project XX

 

Back to top

Automation Decision Services
Known IssueTitleSec.Cont.B.I.
DT454442No support for podAntiAffinity   

 

Back to top

Known IssueTitleSec.Cont.B.I.
N/AN/A   

 

Back to top

Business Automation Insights
Known IssueTitleSec.Cont.B.I.
N/AN/A   

 

Back to top

Business Automation Navigator
Business Automation Studio
Known IssueTitleSec.Cont.B.I.
DT446595Security vulnerability (CVE-2025-7783) in form-data-4.0.0.tgz affects Workflow centre and Process DesignerX  
DT447031CVE-2025-36172 Cross-Site Scripting vulnerability in Case ClientX  
DT451598Security vulnerability in axios javascript Library affects IBM Process Designer, IBM Workflow center and IBM Business Automation StudioX  
DT421803Add an automation service search filed yields no results when searching for a name containing a space in IBM Business Automation Studio   
DT422724Process Admin Console Group Management member list does not show user display names   
DT435499Coach UI is not displayed correctly in Workflow server after snapshot deployment   
DT448726Data mappings of an activity in a service flow might not be shown   

 

Back to top

Business Automation Workflow including Automation Workstream Services
Known IssueTitleSec.Cont.B.I.
DT446595Security vulnerability (CVE-2025-7783) in form-data-4.0.0.tgz affects Workflow centre and Process DesignerX  
DT443492Cross-Site scripting via Unauthenticated Endpoint - IBM Process Federation ServerX  
DT445908CVE-2025-27817, CVE-2025-27818 in kafka-clients-3.8.1.jar affecting eventX  
DT446350CVE-2025-7783 - form-data-4.0.0.tgz affects Process Admin ConsoleX  
DT447031CVE-2025-36172 Cross-Site Scripting vulnerability in Case ClientX  
DT393473Navigator Business Automation Workflow desktop is not fully accessible due to user permission error   
DT422724Process Admin Console Group Management member list does not show user display names   
DT435499Coach UI is not displayed correctly in Workflow server after snapshot deployment   
DT438061Quick Task Assignment Disposal Policy throws error:   
DT439845Lack of security or owner on Quick Task Attachment Collection class leads to Quick Task Attachment Collection Disposal Policy throwing error E_ACCESS_DENIED   
DT446772Process instance status can end in status completed even if the end node is a terminate one if there is a subprocess marked as reusable   
DT447017Case Activity fails to complete due to DB deadlock   
DT448347tw.system.currentProcessInstance.parentCase.terminateActivities() API does not terminate failed workflow instances   
DT448726Data mappings of an activity in a service flow might not be shown   
DT450088After upgrading from ICM 5.3.3 to CP4BA , error message FNRCE0066E: E_UNEXPECTED_EXCEPTION: Failed to update case properties into PFS. : jms/TWClientConnectionFactory is seen   
DT450303Uninitialized complex type business object variables cannot be updated in Process Inspector   
DT451052Process Instances cannot be deleted due to incorrect CAN_DELETE_INSTANCE value   
DT453431Snapshot status not getting updated in Process Admin console   
DT445873Load on IM pods spike when Process Admin Console user and group search is performed   

 

Back to top

Enterprise Records
Known IssueTitleSec.Cont.B.I.
N/AN/A   

 

Back to top

FileNet Content Manager
Operational Decision Management
Known IssueTitleSec.Cont.B.I.
DT447568IN BUSINESS CONSOLE THE PRE-CONDITION WINDOW FOR DECISION TABLE MAY BE TOO SMALL   
DT451817INCORRECT RULE EXECUTION USING A BUILD COMMAND RULESET   
DT450239PASTE IN DECISION TABLE IN VIEW MODE WORKS   
DT449841RES CONSOLE DOES NOT REPORT RESOURCES USAGE PROPERLY   
DT448982WARNING MESSAGE WHEN DELETING SIMULATION REPORT IN DECISION CENTER   
DT442820BASELINE NOT FOUND ERROR WHEN DELETING A DECISION SERVICE   
DT445850MULTIPLE ECLIPSE ISSUES AFTER INSTALLING RULE DESIGNER   
DT449931IMPLEMENT DECISION TABLE DISPLAY OPTION TO AUTOMATICALLY FIT TO SCREEN   
DT444680DATABASE LOCKING EXCEPTION DURING SYNCHRONISATION   
DT450802NEW DECISION TABLE EDITOR STAYS STUCK ON LOADING   
DT450600WEBHOOK NOTIFICATION FAILS WITH CLASSNOTFOUNDEXCEPTION WHEN USING DECISIONCENTER APIS   
DT445979EDITING AN EMPTY VALUE REFACTORS OTHER VALUES   
DT449071RULETASK WARNING AND OLD RULE PACKAGE NAME DISPLAY IN PROPERTIES VIEW AFTER REFACTORING RULE PACKAGES   
DT451143AFTER BRANCH DELETION SOME ARTIFACTS MAY NOT BE ACCESSIBLE   
DT450179DC SCHEMA MIGRATION FAILING WITH INFINITE LOOPS   
DT451854IMPORT EXCEL FAILS WITH ERROR MESSAGE   
DT448795EXCEL IMPORT OF EMPTY STRING CELLS TURNS THEM INTO PLACEHOLDERS   
DT450580OUTOFMEMORY EXCEPTION WHILE DOING A RES BACKUP   
DT442262MAVEN PLUGIN GETS UNINSTALLED AFTER RULE DESIGNER INSTALLATION   
DT451862DECISION CENTER DELETION SERVICE IS BLOCKED   

 

Back to top

User Management Service
Known IssueTitleSec.Cont.B.I.
N/AN/A   

Back to top

Workflow Process Service
Known IssueTitleSec.Cont.B.I.
DT445908CVE-2025-27817, CVE-2025-27818 in kafka-clients-3.8.1.jar affecting eventX  
DT446350CVE-2025-7783 - form-data-4.0.0.tgz affects Process Admin ConsoleX  
DT446772Process instance status can end in status completed even if the end node is a terminate one if there is a subprocess marked as reusable   
DT447017Case Activity fails to complete due to DB deadlock   
DT448726Data mappings of an activity in a service flow might not be shown   
DT450303Uninitialized complex type business object variables cannot be updated in Process Inspector   
DT451052Process Instances cannot be deleted due to incorrect CAN_DELETE_INSTANCE value   
DT453431Snapshot status not getting updated in Process Admin console   

 

Back to top

Known Limitations

Document change history

  • 30 October 2025: Initial publish.

  • 31 July 2025: Initial publish.

    • [{"Type":"MASTER","Line of Business":{"code":"LOB76","label":"Data Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSBYVB","label":"IBM Cloud Pak for Business Automation"},"ARM Category":[{"code":"a8m0z0000001gWWAAY","label":"Other-\u003ECloudPak4Automation Platform"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"24.0.0"}]

    Document Information

    Modified date:
    09 December 2025

    UID

    ibm17245057

    Page Feedback