IBM Support

Readme for IBM Cloud Pak for Business Automation 24.0.0 IF008

Fix Readme


Abstract

The following document is for IBM Cloud Pak for Business Automation 24.0.0 IF008. 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 IF008
Fix ID:24.0.0-WS-CP4BA-IF008
Publication Date:29 January 2026
 

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-IF008
  • Cloud Pak Foundational Services 4.6.20
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. If you are upgrading from 21.0.3.x or 23.0.2.x, it is recommended to first upgrade to 24.0.0 GA before 24.0.0 IF008. This is to ensure a smooth migration for the embedded Mongo instance with minimal manual interventions. After upgrading to 24.0.0 GA, then proceed with the following steps below.

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 IF008 branch by using the following git clone command.

    git clone -b 24.0.0-IF008 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-IF008.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-IF008.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-IF008.txt mirror file. 

      export CASE_NAME=ibm-cp-automation
                                export CASE_VERSION=24.0.8
                                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-IF008.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-IF008.txt mirror file. 

        export CASE_NAME=ibm-cp-automation
                                                export CASE_VERSION=24.0.8
                                                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-2007-5686, CVE-2010-4756, CVE-2011-3374, CVE-2011-3389, CVE-2011-4116, CVE-2011-4969, CVE-2012-2663, CVE-2012-6708, CVE-2013-4392, CVE-2014-6071, CVE-2015-3276, CVE-2015-9251, CVE-2017-14159, CVE-2017-17740, CVE-2017-18018, CVE-2018-1000654, CVE-2018-1000879, CVE-2018-1000880, CVE-2018-1121, CVE-2018-19211, CVE-2018-20225, CVE-2018-20657, CVE-2018-20786, CVE-2018-20796, CVE-2018-20839, CVE-2018-5709, CVE-2018-6829, CVE-2019-1010022, CVE-2019-1010023, CVE-2019-1010024, CVE-2019-1010025, CVE-2019-11358, CVE-2019-12904, CVE-2019-14250, CVE-2019-16866, CVE-2019-19244, CVE-2019-7317, CVE-2019-8905, CVE-2019-8906, CVE-2019-9192, CVE-2019-9674, CVE-2019-9923, CVE-2019-9936, CVE-2019-9937, CVE-2020-11022, CVE-2020-11023, CVE-2020-15138, CVE-2020-15719, CVE-2020-19185, CVE-2020-19186, CVE-2020-19187, CVE-2020-19188, CVE-2020-19189, CVE-2020-19190, CVE-2020-20703, CVE-2020-35512, CVE-2020-7656, CVE-2021-20193, CVE-2021-24032, CVE-2021-24112, CVE-2021-3236, CVE-2021-39537, CVE-2021-3997, CVE-2021-4209, CVE-2021-45346, CVE-2022-0235, CVE-2022-0391, CVE-2022-0563, CVE-2022-23990, CVE-2022-29458, CVE-2022-30241, CVE-2023-23931, CVE-2023-27534, CVE-2023-28642, CVE-2023-29483, CVE-2023-29499, CVE-2023-2953, CVE-2023-31437, CVE-2023-31438, CVE-2023-31439, CVE-2023-31486, CVE-2023-32611, CVE-2023-32665, CVE-2023-36807, CVE-2023-36810, CVE-2023-4016, CVE-2023-45288, CVE-2023-45853, CVE-2023-46250, CVE-2023-4733, CVE-2023-4750, CVE-2023-4752, CVE-2023-49083, CVE-2023-52355, CVE-2023-52356, CVE-2023-52426, CVE-2024-0397, CVE-2024-10041, CVE-2024-1013, CVE-2024-11079, CVE-2024-11168, CVE-2024-12797, CVE-2024-12798, CVE-2024-12801, CVE-2024-20952, CVE-2024-21626, CVE-2024-22365, CVE-2024-2410, CVE-2024-24786, CVE-2024-24791, CVE-2024-25621, CVE-2024-26130, CVE-2024-26458, CVE-2024-26461, CVE-2024-28219, CVE-2024-28757, CVE-2024-33655, CVE-2024-34155, CVE-2024-34156, CVE-2024-34158, CVE-2024-43167, CVE-2024-43168, CVE-2024-4531, CVE-2024-45310, CVE-2024-45336, CVE-2024-45338, CVE-2024-45341, CVE-2024-47554, CVE-2024-52533, CVE-2024-53899, CVE-2024-55459, CVE-2024-5569, CVE-2024-56201, CVE-2024-56326, CVE-2024-5642, CVE-2024-57699, CVE-2024-57970, CVE-2024-58251, CVE-2024-6345, CVE-2024-7592, CVE-2024-7598, CVE-2024-8775, CVE-2024-9287, CVE-2024-9902, CVE-2025-0913, CVE-2025-0938, CVE-2025-10966, CVE-2025-11226, CVE-2025-11411, CVE-2025-12058, CVE-2025-12060, CVE-2025-12758, CVE-2025-13281, CVE-2025-1352, CVE-2025-1365, CVE-2025-13699, CVE-2025-1372, CVE-2025-14847, CVE-2025-15284, CVE-2025-1550, CVE-2025-1767, CVE-2025-22866, CVE-2025-22868, CVE-2025-22870, CVE-2025-22871, CVE-2025-22872, CVE-2025-25724, CVE-2025-27516, CVE-2025-27587, CVE-2025-27817, CVE-2025-29088, CVE-2025-29481, CVE-2025-31133, CVE-2025-32365, CVE-2025-32414, CVE-2025-32415, CVE-2025-32988, CVE-2025-32989, CVE-2025-32990, CVE-2025-40777, CVE-2025-40778, CVE-2025-40780, CVE-2025-4138, CVE-2025-4330, CVE-2025-4373, CVE-2025-4435, CVE-2025-4517, CVE-2025-4565, CVE-2025-46394, CVE-2025-4673, CVE-2025-46836, CVE-2025-47906, CVE-2025-47907, CVE-2025-4878, CVE-2025-48913, CVE-2025-48976, CVE-2025-52565, CVE-2025-52881, CVE-2025-52999, CVE-2025-53057, CVE-2025-53066, CVE-2025-5318, CVE-2025-5351, CVE-2025-5372, CVE-2025-53864, CVE-2025-53905, CVE-2025-53906, CVE-2025-55197, CVE-2025-56200, CVE-2025-58056, CVE-2025-58057, CVE-2025-58098, CVE-2025-5914, CVE-2025-59375, CVE-2025-6020, CVE-2025-6141, CVE-2025-62707, CVE-2025-62708, CVE-2025-62727, CVE-2025-6297, CVE-2025-6395, CVE-2025-64329, CVE-2025-64512, CVE-2025-65082, CVE-2025-65945, CVE-2025-66019, CVE-2025-66034, CVE-2025-66200, CVE-2025-66221, CVE-2025-67221, CVE-2025-6965, CVE-2025-7425, CVE-2025-7458, CVE-2025-7709, CVE-2025-8058, CVE-2025-8114, CVE-2025-8176, CVE-2025-8194, CVE-2025-8277, CVE-2025-8677, CVE-2025-8732, CVE-2025-8747, CVE-2025-8885, CVE-2025-9230, CVE-2025-9624, CVE-2025-9900, CVE-2025-9906, CVE-2026-1299, CVE-2026-21860, CVE-2026-22997, CVE-2026-23003, CVE-2026-23004, CVE-2026-24515, GHSA-f83h-ghpp-7wcc, GHSA-h4gh-qq45-vh27, GHSA-qr4w-53vh-m672, PRISMA-2023-0067, RHSA-2025:11140, RHSA-2025:12447, RHSA-2025:12748, RHSA-2025:12876, RHSA-2025:13428, RHSA-2025:14130, RHSA-2025:16116, RHSA-2025:17715, RHSA-2025:18286, RHSA-2025:20559, RHSA-2025:20801, RHSA-2025:20936, RHSA-2025:20945, RHSA-2025:20956, RHSA-2025:21110, RHSA-2025:21111, RHSA-2025:21255, RHSA-2025:21776, RHSA-2025:21977, RHSA-2025:22175, RHSA-2025:23323, RHSA-2025:23342, RHSA-2025:23343, RHSA-2025:23383, RHSA-2025:23530, RHSA-2025:23919, RHSA-2026:0126, RHSA-2026:0238, RHSA-2026:0241, RHSA-2026:0337, RHSA-2026:0491, RHSA-2026:0728, RHSA-2026:0991
 
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.
DT456117Multiple CVEs in golang affect Business Automation Workflow, Process Federation Server and Workflow Process Service operatorsX  
DT455215During deployment of Business Automation Studio, the Task fails with unclear error: Error if target_env_name for default TOS is not dev_env_connection_definition   
DT455329Tuning IBM® WebSphere Liberty for FileNet Content Manager components   
DT460243Default self-signed certificates for legacy routes do not get renewed automatically when expired   
DT456607Update the syntax to retrieve subscriptions from "oc get subscription" to "oc get subscriptions.operators.coreos.com"   

 

Back to top

Automation Document Processing
Known IssueTitleSec.Cont.B.I.
N/AN/A   

 

Back to top

Automation Decision Services
Known IssueTitleSec.Cont.B.I.
DT458145Missing Pod Disruption Budgets management in ADS components   
DT456062UI Regression: Colour Formatting Missing in Column Output After Upgrade to ADS 24.0.0+   

 

Back to top

Known IssueTitleSec.Cont.B.I.
DT391449Single select view with typeahead behavior enabled does not set the typed or selected value when used in a Table view   
DT452348Some fields are unexpectedly highlighted as having an error in process portal tasks after upgrade to IBM Business Automation Workflow 24.0.1.0   
DT456476BatchUpdateExceptions are seen when indexing tasks which have been created by Business Automation Workflow 19.0.0.1 or older are not updated   

 

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.
DT448632CVE-2025-48924 in Apache commons-lang may affect IBM Business Automation WorkflowX  
DT456229CVE-2025-13096 - XML Entity Expansion vulnerability in IBM Business Automation WorkflowX  
DT457061Server side Request Forgery affects IBM Business Automation Workflow and Cloud Pak for Business AutomationX  
DT391449Single select view with typeahead behavior enabled does not set the typed or selected value when used in a Table view   
DT393307Unable to view complex object while debugging a process in web Process Designer   
DT449006Unable to copy/Paste text or select hyperlinks when using Rich Text Editor in read-only Mode   
DT452348Some fields are unexpectedly highlighted as having an error in process portal tasks after upgrade to IBM Business Automation Workflow 24.0.1.0   
DT454461The bpm-dtp-date-active-color theme property is not used by the Date/time picker view from the UI Toolkit   
DT455215During deployment of Business Automation Studio, the Task fails with unclear error: Error if target_env_name for default TOS is not dev_env_connection_definition   
DT456476BatchUpdateExceptions are seen when indexing tasks which have been created by Business Automation Workflow 19.0.0.1 or older are not updated   

 

Back to top

Business Automation Workflow including Automation Workstream Services
Known IssueTitleSec.Cont.B.I.
DT448632CVE-2025-48924 in Apache commons-lang may affect IBM Business Automation WorkflowX  
DT449298Case comments section executes payload (BAW)X  
DT450355CVE-2025-41242 - Update Spring framework in Business Automation WorkflowX  
DT451477CVE-2025-58754 reported for axios-1.11.0X  
DT455668CVE-2025-57352 in min-documentX  
DT456117Multiple CVEs in golang affect Business Automation Workflow, Process Federation Server and Workflow Process Service operatorsX  
DT456229CVE-2025-13096 - XML Entity Expansion vulnerability in IBM Business Automation WorkflowX  
DT457061Server side Request Forgery affects IBM Business Automation Workflow and Cloud Pak for Business AutomationX  
DT454003Persistent Object cache optimization is enabled by default in versions prior to 25.0.0.0  X
DT391449Single select view with typeahead behavior enabled does not set the typed or selected value when used in a Table view   
DT409005IBM Case Client throws an error when opening Case Comments widget containing a case comment from a user in the past but that user is later deleted from LDAP   
DT436090- CWLLG2156W: The database connection pool size (200) of the Workflow Server data source might be too small tuning queue capacity and cm_max_pool_size (CP4BA)   
DT443993The ECM File Uploader view in the Content Management toolkit regressed while trying to select multiple documents   
DT446517Federated Process Portal throws an error indicating the Design object store cannot be found on a Business Automation Workflow instance that doesn't have Case enabled   
DT447474Security vulnerability (CVE-2025-7783) in form-data-4.0.0.tgz affects Workplace   
DT449006Unable to copy/Paste text or select hyperlinks when using Rich Text Editor in read-only Mode   
DT452348Some fields are unexpectedly highlighted as having an error in process portal tasks after upgrade to IBM Business Automation Workflow 24.0.1.0   
DT453431Snapshot status not getting updated in Process Admin console   
DT454461The bpm-dtp-date-active-color theme property is not used by the Date/time picker view from the UI Toolkit   
DT454846When updating an existing document to newer version(s) of the document having a different mime type, the mime type of the document always reflects the mime type of the first version   
DT456476BatchUpdateExceptions are seen when indexing tasks which have been created by Business Automation Workflow 19.0.0.1 or older are not updated   
DT456678In Cloud Pak For Business Automation 23.0.2, there is an invalid target environment found on Workplace toolkit   
DT456678In Cloud Pak For Business Automation 23.0.2, there is an invalid target environment found on Workplace toolkit   
DT457499Optimization in the task completion   

 

Back to top

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

 

Back to top

FileNet Content Manager
Operational Decision Manager (based on ODM-9.0.0.1-IF019)
Known IssueTitleSec.Cont.B.I.
DT453050DECISION CENTER SIMULATION PRINT FEATURE IS NOT WORKING   
DT452100COMPARE OF DECISION CENTER SIMULATION CONFIGURATION WITH OLDER VERSION FAILED WITH NPE   
DT454985INCORRECT VALUES POPULATED IN THE EXCEL REPORT GENERATED WHEN RUNNING THE TEST SUITE   
DT454837UNEXPECTED CAST EXCEPTION FOR BOOLEAN PROPERTY DURING RUNTIME RULE SELECTION   
DT458155CANNOT OPEN PROJECT IN BUSINESS CONSOLE   
DT457379SIMULATION CONFIGURATION COMPARISON DISPLAYS UNIX EPOCH FORMAT FOR DATE FIELD   
DT454896UNABLE TO SELECT A DATE IN THE DECISION TABLE EDITOR IN RULE DESIGNER   
DT458698RULE UPDATE USING REMOTE API MIGHT NOT APPLY TO WORKING BASELINE PREVIOUSLY SET   
DT454103NON-ADMIN USERS UNABLE TO LOGIN DECISION CENTER   
DT456707RTSUSER CANNOT EXPORT SNAPSHOT FROM REST-API   
DT454134CODE INJECTION IN THE SIMULATION FIELDS   
DT454242CODE INJECTION IN REPORT FORMATS KPI EDITOR   
DT457400RTSUSERS ARE UNABLE TO LOG IN DECISION CENTER   
DT459790OUTPUT EXCEL FILE CONTAINS THE RULESET PARAMETERS IN AN INCORRECT ORDER   
DT458139UNABLE TO UPDATE STRUCT CUSTOM PROPERTY USING QUERY ACTION   
DT425576DECISION SERVICE PROJECT HEADLESS BUILD FAILS WITH NPE   
DT452944CLASSCASTEXCEPTION WHEN USING XSD:TIME IN XOM MAPPED TO ILRTIME IN BOM   
DT452830DECISION TABLE EDITOR AUTOMATIC FIT TO SCREEN PRODUCES UNEXPECTED OUTCOME   
DT455504COMPARE VERSIONS PAGE DOES NOT LOAD RESULTS   
DT456480DECISION SERVICE WITH INTERCEPTOR ENABLED LEAKS MANAGEMENT SESSION   
DT453379UNABLE TO VIEW DEPLOYMENT REPORT AFTER CLEANUP   

 

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.
DT455668CVE-2025-57352 in min-documentX  
DT456117Multiple CVEs in golang affect Business Automation Workflow, Process Federation Server and Workflow Process Service operatorsX  
DT456229CVE-2025-13096 - XML Entity Expansion vulnerability in IBM Business Automation WorkflowX  
DT454003Persistent Object cache optimization is enabled by default in versions prior to 25.0.0.0  X
DT453431Snapshot status not getting updated in Process Admin console   
DT456413The Workflow Process Service datasave PVC should allow for RWX PV to be used, not just RWO   
DT456476BatchUpdateExceptions are seen when indexing tasks which have been created by Business Automation Workflow 19.0.0.1 or older are not updated   
DT457499Optimization in the task completion   
DT458098DOC: Missing documentation on maxPool connection configuration for Workflow Process Service   

 

Back to top

Known Limitations

Document change history

  • 29 January 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:
    31 January 2026

    UID

    ibm17254201

    Page Feedback