IBM Support

Readme for IBM Cloud Pak for Business Automation 24.0.0 IF003

Fix Readme


Abstract

The following document is for IBM Cloud Pak for Business Automation 24.0.0 IF003. 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 IF003
Fix ID: 24.0.0-WS-CP4BA-IF003
Publication Date: 28 October 2024

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-IF003
  • Cloud Pak Foundational Services 4.6.6
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.
Step 1: Download the installation and upgrade scripts
  1. Ensure that the client that you intend to use to connect to the Red Hat OpenShift cluster has a supported operating system and all the necessary tools. For more information, see Preparing a client to connect to the cluster.
  2. Download the 24.0.0 IF003 branch by using the following git clone command. 
    git clone -b 24.0.0-IF003 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-scoped Supported (This is the recommended approach if your current deployment is using cluster-scoped CPFs)
Namespace-scoped to Namespace-scoped Supported (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_2"
    Actions:
    1. To deploy an airgap/offline Production deployment, find mirror file cp4ba-case-to-be-mirrored-24.0.0-IF003.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-IF003.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-IF003.txt mirror file.  
      export CASE_NAME=ibm-cp-automation
export CASE_VERSION=24.0.3
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 (If you do not have 21.0.3 IF031 or newer, you need to upgrade to 21.0.3 IF031 or newer before proceeding with this upgrade).
    Note: Direct upgrade from 21.0.3 IF031 or newer to 24.0.0 IF003 is not supported.  For this scenario, complete an upgrade to 24.0.0 IF001 first, and then perform an upgrade from 24.0.0 IF001 to this current interim fix.
    Actions:  
    1. Follow the instructions in 24.0.0 IF001 readme to perform a direct upgrade to 24.0.0 IF001 first.
    2. Then perform an upgrade from 24.0.0 IF001 to the current interim fix.
      • For online upgrade, follow the instructions listed in Scenario 7.
      • For offline upgrade, follow the instructions listed in Scenario 8.
  • Scenario 5: Your installed Production deployment version is 22.0.2 IF006 (If you do not have 22.0.2 IF006, you need to upgrade to 22.0.2 IF006 before proceeding with this upgrade).
    Note: Direct upgrade from 22.0.2 IF006 to 24.0.0 IF003 is not supported.  For this scenario, complete an upgrade to 24.0.0 IF001 first, and then perform an upgrade from 24.0.0 IF001 to this current interim fix.
    Actions: 
    1. Follow the instructions in 24.0.0 IF001 readme to perform a direct upgrade to 24.0.0 IF001 first.
    2. Perform an upgrade from 24.0.0 IF001 to the current interim fix.
      • For online upgrade, follow the instructions listed in Scenario 7.
      • For offline upgrade, follow the instructions listed in Scenario 8.
  • 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).
    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.
    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 up. 
      • Actions:
        Run the cp4a-deployment.sh script with the upgradeOperator option to upgrade the IBM Cloud Pak foundational services/CP4BA operators:
        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.
          
        ./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>
  • 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. 
    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 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-IF003.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-IF003.yaml
      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-IF003.txt mirror file.  
      export CASE_NAME=ibm-cp-automation
export CASE_VERSION=24.0.3
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_2"
    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 up. 
      • Actions:
        Run the cp4a-deployment.sh script with the upgradeOperator option to upgrade the IBM Cloud Pak foundational services/CP4BA operators:
        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.
          
        ./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.
      • 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>
    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>

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.

Known Issue with upgrade on some Openshift clusters:

  • When upgrading from 24.0.0 to any iFix or 24.0.0 IF001 to any iFix, the Flink job pods failed with 502 Bad Gateway error.
    • Cause: This issue reported on some Openshift clusters with "no cipher suites in common" had problems with missing cipher suites, hence Flink was denying a handshake with it.
    • Workaround: 
      • Update the FlinkDeployment CR on the cluster by adding the "security.ssl.algorithms" under the  flinkConfiguration section with below.
security.ssl.algorithms: TLS_DHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_DHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
For example:
1. ie_cr=$(oc get FlinkDeployment --no-headers | awk {'print $1'})
2. kubectl patch flinkdeployment $ie_cr -n <namespace> --type='json' -p='[{"op": "add", "path": "/spec/flinkConfiguration/security.ssl.algorithms", "value": "TLS_DHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_DHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384"}]'

List of Fixes

APARs/Known Issues fixed by this interim fix are listed in the following tables.
The columns are defined as follows: 
Column title Column description
APAR/Known Issue The defect number
Title A 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 Issue Title Sec. 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-2017-15691, CVE-2019-10086, CVE-2020-13936, CVE-2020-13959, CVE-2021-26291, CVE-2021-46984, CVE-2021-47097, CVE-2021-47101, CVE-2021-47287, CVE-2021-47289, CVE-2021-47321, CVE-2021-47338, CVE-2021-47352, CVE-2021-47383, CVE-2021-47384, CVE-2021-47385, CVE-2021-47386, CVE-2021-47393, CVE-2021-47412, CVE-2021-47432, CVE-2021-47441, CVE-2021-47455, CVE-2021-47466, CVE-2021-47497, CVE-2021-47527, CVE-2021-47560, CVE-2021-47582, CVE-2021-47609, CVE-2022-26336, CVE-2022-48619, CVE-2022-48754, CVE-2022-48760, CVE-2022-48804, CVE-2022-48836, CVE-2022-48866, CVE-2023-24329, CVE-2023-40217, CVE-2023-41105, CVE-2023-48795, CVE-2023-50387, CVE-2023-50868, CVE-2023-52470, CVE-2023-52476, CVE-2023-52478, CVE-2023-52522, CVE-2023-52605, CVE-2023-52683, CVE-2023-52817, CVE-2023-52840, CVE-2023-6040, CVE-2023-6597, CVE-2024-0450, CVE-2024-0760, CVE-2024-22018, CVE-2024-22020, CVE-2024-23848, CVE-2024-26595, CVE-2024-26645, CVE-2024-26649, CVE-2024-26665, CVE-2024-26717, CVE-2024-26720, CVE-2024-26769, CVE-2024-26855, CVE-2024-26880, CVE-2024-26894, CVE-2024-26923, CVE-2024-26939, CVE-2024-27013, CVE-2024-27042, CVE-2024-28180, CVE-2024-28834, CVE-2024-28835, CVE-2024-28863, CVE-2024-29018, CVE-2024-35809, CVE-2024-35877, CVE-2024-35884, CVE-2024-35944, CVE-2024-35989, CVE-2024-36137, CVE-2024-36883, CVE-2024-36901, CVE-2024-36902, CVE-2024-36920, CVE-2024-36939, CVE-2024-36953, CVE-2024-3727, CVE-2024-37356, CVE-2024-38558, CVE-2024-38559, CVE-2024-38570, CVE-2024-38581, CVE-2024-38619, CVE-2024-38809, CVE-2024-39331, CVE-2024-39338, CVE-2024-39471, CVE-2024-39499, CVE-2024-39501, CVE-2024-39506, CVE-2024-40094, CVE-2024-4076, CVE-2024-40901, CVE-2024-40904, CVE-2024-40911, CVE-2024-40912, CVE-2024-40929, CVE-2024-40931, CVE-2024-40941, CVE-2024-40954, CVE-2024-40958, CVE-2024-40959, CVE-2024-40960, CVE-2024-40972, CVE-2024-40977, CVE-2024-40978, CVE-2024-40988, CVE-2024-40989, CVE-2024-40995, CVE-2024-40997, CVE-2024-40998, CVE-2024-41005, CVE-2024-41007, CVE-2024-41008, CVE-2024-41012, CVE-2024-41013, CVE-2024-41014, CVE-2024-41023, CVE-2024-41035, CVE-2024-41038, CVE-2024-41039, CVE-2024-41040, CVE-2024-41041, CVE-2024-41044, CVE-2024-41055, CVE-2024-41056, CVE-2024-41060, CVE-2024-41064, CVE-2024-41071, CVE-2024-41076, CVE-2024-41090, CVE-2024-41091, CVE-2024-41097, CVE-2024-42084, CVE-2024-42090, CVE-2024-42094, CVE-2024-42096, CVE-2024-42114, CVE-2024-42124, CVE-2024-42131, CVE-2024-42152, CVE-2024-42154, CVE-2024-42226, CVE-2024-42228, CVE-2024-42237, CVE-2024-42238, CVE-2024-42240, CVE-2024-42246, CVE-2024-42265, CVE-2024-42322, CVE-2024-43871, CVE-2024-7348, DSA-5759-1, DSA-5764-1, GHSA-jq35-85cj-fj4p, RHSA-2024:3626, RHSA-2024:4264, RHSA-2024:5814, RHSA-2024:5962, RHSA-2024:6020, RHSA-2024:6962
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 Issue Title Sec. Cont. B.I.
DT399834 The Workflow Operator get stuck when a Business Automation Workflow instance does not have case configured
DT397641 Setting up external Elasticsearch for Workflow Process Service Runtime requires the use of the Elastic superuser
DT399918 Using baw_configuration[x].liberty_custom_xml to customize the Business Automation Workflow Runtime Liberty server fails
DT400133 workflow-runtime-operator pod crashes if CASE custom_package_names is set

Back to top

Automation Document Processing
Known Issue Title Sec. Cont. B.I.
DT392013 Rows from second table on page getting appended to first table X X
DT394357 Special characters in passwords break the cpds deploy to runtime scripts X X
DT400371 Error distributed: command not found when running prerequisites script X X

Back to top

Automation Decision Services
Known Issue Title Sec. Cont. B.I.
DT397693 When parsing a test, java.lang.Long incompatible with java.math.BigDecimal
DT397696 Long should be removed from primitive types
DT400095 Performance issue in rule creation wizard
DT400098 When creating dependencies there are issues that are not reported
DT400102 Too many BAL parsing requests may be running at the same time
DT400117 Unable to upgrade decision services that have errors
DT400119 Configuration options required in the rule editor for performance
DT400217 Faster editing required
DT400219 Model validation should not be triggered while editing a rule

Back to top

Known Issue Title Sec. Cont. B.I.
N/A N/A

Back to top

Business Automation Insights
Known Issue Title Sec. Cont. B.I.
N/A N/A

Back to top

Business Automation Navigator
Business Automation Studio
Known Issue Title Sec. Cont. B.I.
DT395404 CVE-2024-39338 in axios affects Process Admin Console X
DT396474 CVE-2024-45296 in path-to-regexp affects IBM Business Automation Workflow X

Back to top

Business Automation Workflow including Automation Workstream Services
Known Issue Title Sec. Cont. B.I.
DT395404 CVE-2024-39338 in axios affects Process Admin Console X
DT396474 CVE-2024-45296 in path-to-regexp affects IBM Business Automation Workflow X
DT393042 THE START TIME AND END TIME MAY BE CONVERTED INCORRECTLY WHEN YOU CREATE A DATE/TIME RANGE PERIOD IN THE BLACKOUT PERIODS PAGE IN THE PROCESS ADMIN CONSOLE
DT399834 The Workflow Operator get stuck when a Business Automation Workflow instance does not have case configured
DT399918 Using baw_configuration[x].liberty_custom_xml to customize the Business Automation Workflow Runtime Liberty server fails
DT400133 workflow-runtime-operator pod crashes if CASE custom_package_names is set

Back to top

Enterprise Records
Known Issue Title Sec. Cont. B.I.
N/A N/A

Back to top

FileNet Content Manager
Operational Decision Management
Known Issue Title Sec. Cont. B.I.
DT392338 IN RULE DESIGNER V9 MAVEN M2E PLUGIN IS UNUSABLE
DT392428 ERROR MESSAGES REGARDING DOMAIN VALUES IN BOM TO XOM MAPPING
DT396432 NULLPOINTEREXCEPTION EXECUTING A QUERY

Back to top

User Management Service
Known Issue Title Sec. Cont. B.I.
DT390952 User Management Service certificate is incompatible with Azure AGIC - IBM Cloud Pak for Business Automation

Back to top

Workflow Process Service
Known Issue Title Sec. Cont. B.I.
DT395404 CVE-2024-39338 in axios affects Process Admin Console X
DT396474 CVE-2024-45296 in path-to-regexp affects IBM Business Automation Workflow X
DT393042 THE START TIME AND END TIME MAY BE CONVERTED INCORRECTLY WHEN YOU CREATE A DATE/TIME RANGE PERIOD IN THE BLACKOUT PERIODS PAGE IN THE PROCESS ADMIN CONSOLE
DT394459 Importing an app into the IBM Workflow Process Server Trial on Docker fails with an Import Project Error - IBM Workflow Process Server
DT397641 Setting up external Elasticsearch for WFPS install in 24.0.0 requires the use of the Elastic super user - Cloud Pak for Business Automation

Back to top

Known Limitations

Document change history

  • 28 October 2024: 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:
    30 April 2025

    UID

    ibm17167010

    Page Feedback