Fix Readme
Abstract
The following document is for IBM Cloud Pak for Business Automation 21.0.3 IF035. 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: | 21.0.3 |
Update Name: | 21.0.3 IF035 |
Fix ID: | 21.0.3-WS-CP4BA-IF035 |
Publication Date: | 1 August 2024 |
Contents
Components impacted
Before upgrading
Installing the interim fix
Performing the necessary tasks after installation
Uninstalling
List of fixes
Known Limitations
Document change history
Prerequisites and supersedes
- Supersedes all prior interim fixes for Cloud Pak for Business Automation 21.0.3.
Components impacted
- General
- Cloud Pak for Business Automation Operator
- Automation Document Processing
- Automation Decision Services
- Business Automation Application
- Business Automation Insights
- Business Automation Navigator
- Business Automation Studio
- Business Automation Workflow including Automation Workstream Services
- Enterprise Records
- FileNet Content Manager
- Operational Decision Management
- User Management Service
- Workflow Process Service
Before upgrading
- Ensure you take regular backups of any databases associated with the environment.
- 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:oc get icp4acluster -o yaml oc get AutomationUIConfig -o yaml oc get Cartridge -o yaml oc get AutomationBase -o yaml oc get CartridgeRequirements -o yaml
- Required when you are using Business Automation Insights
If Business Automation Insights is deployed, prune the Business Automation Insights deployment, and jobs, before you apply the updated custom resource YAML file.
$ oc delete Deployment,Job -l \ > 'app.kubernetes.io/name=ibm-business-automation-insights'
Tip: For Flink event processing to resume from its previous state, make sure that savepoints are created before the upgrade and specified in the updated CR. For more information see Restarting from a checkpoint or savepoint
Installing the interim fix
- Starting with 21.0.3-IF012 interim fix, the URLs for Content Management Interoperability Services (CMIS) have changed (i.e., "cmis" context root was introduced):
- The previous CPD route for CMIS has changed
- from: https://cpd-<cp4ba-namespace>.xxxx.xxxx.xxxx/openfncmis_wlp
- to: https://cpd-<cp4ba-namespace>.xxxx.xxxx.xxxx/cmis/openfncmis_wlp
- The previous Openshift route for CMIS has changed
- from: https://cmis-<cp4ba-namespace>.xxxx.xxxx.xxxx/openfncmis_wlp
- to: https://cmis-<cp4ba-namespace>.xxxx.xxxx.xxxx/cmis/openfncmis_wlp
- The previous CPD route for CMIS has changed
- Cloud Pak for Business Automation – 21.0.3-IF035
- Automation Foundation – 1.3.15
- Cloud Pak Foundational Services – 3.19.22
Installing IBM Cloud Pak foundational services in multiple namespaces is now possible starting with 21.0.3 iFix019.
If the cp4a-clusteradmin-setup.sh script is used, a namespace-scoped instance of foundational services is installed in the same namespace as the CP4BA deployment. If you do not want this configuration, you must use the OpenShift Container Platform (OCP) console to install Cloud Pak for Business Automation. A CP4BA deployment installed from the OCP console uses a cluster-scoped instance of foundational services in the ibm-common-services
namespace.
For more information, see Installing IBM Cloud Pak foundational services in multiple namespaces.
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. If the FCV version is 4.4, you need to upgrade to FCV version to 5.0 following the commands below after upgrading to 21.0.3-IF031.
Warning: If you are upgrading from 21.0.3-IF024 and before with FCV version is 4.2, please first go to 21.0.3-IF025 readme and upgrade to 21.0.3-IF025 along with upgrading FCV version to 4.4.
- Identify the the MongoDB pod by running the command below to get the podID.
kubectl get pods | grep icp4adeploy-mongo
- Check the FCV version by running the command below.
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})"'
- If the FCV version is 4.4, skip to step 7. If the FCV version is 4.2, and you are on 21.0.3-IF025+. Please execute the commands to upgrade FCV version to 4.4, then upgrade to 21.0.3-IF031. Once your deployment is on FCV version 4.4 and 21.0.3-IF031 then you can upgrade FCV version to 5.0 by following step 8 to finish the upgrade.
-
Upgrade to FCV version to 4.4. Note: If the command is successful, the last line of the output is { "ok" : 1 }.
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: \"4.4\" })"'
- Verify the FCV version is 4.4.
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})"'
- If the FCV version is 4.4, you need to set the FCV version to 5.0. If FCV version is 5.0, you do not need to perform the following commands.
- Upgrade FCV version to 5.0. Note: If the command is successful, the last line of the output is { "ok" : 1 }.
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: \"5.0\" })"'
- Check FCV version again to confirm upgrade.
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})"'
- Download the CASE package provided with this interim fix to a Linux based machine (RHEL or macOS).
- Use the tar command to extract the cert-kubernetes directory.
tar -xvzf ibm-cp-automation-3.2.35.tgz
cd ibm-cp-automation/inventory/cp4aOperatorSdk/files/deploy/crs
tar -xvf cert-k8s-21.0.3.tar
cd cert-kubernetes
-
Scenario 1: You are installing a Starter deployment online or have an existing online Starter deploymentWarning: 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: Starter deployments do not support upgrades. Although 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 CASE package from this interim fix. -
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: You can use this interim fix content to perform a Production deployment. To deploy an online Production deployment using the content of this interim fix, please follow Preparing for a production deployment and use the CASE package from this interim fix. -
Scenario 3: You are installing offline/airgap Production deploymentWarning: 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 a host to mirror images to a private registry and further to set up the private registry .Actions:
-
Set up the environment variables for CASE.
export CASE_NAME=ibm-cp-automation export CASE_VERSION=3.2.35 export CASE_INVENTORY_SETUP=cp4aOperatorSetup export CASE_ARCHIVE=${CASE_NAME}-${CASE_VERSION}.tgz export OFFLINEDIR=/opt/cp4ba2103-if035 export CASE_LOCAL_PATH=${OFFLINEDIR}/${CASE_ARCHIVE}
Note: The values are specific to the interim fix, however, you can choose a different empty directory for the OFFLINEDIR if you need to put the files somewhere else. -
Save this specific set of case packages
cloudctl case save --case docker://icr.io/cpopen/ibm-cp-automation-case-cache@sha256:55ca1655dd43d47d586a62b2ff7b8fdc78c492b8633a1b5154dca6336d66f514 --outputdir ${OFFLINEDIR}
Once the command completes, all the Case archive and inventory are saved under /opt/cp4ba2103-if035.
For more information about step 1 and 2, see Setting up the CASE archive and inventory. - Mirror the entitled registry images to the local registry by completing the same steps used during installation. For more information about mirroring, see Mirroring images to the private registry.
Make sure to use the CASE image OFFLINEDIR (/opt/cp4ba2103-if035) from step 1. - Install the Cloud Pak catalog and operator. For more information about installing the catalog and operator, see Installing the Cloud Pak catalog and an operator instance.
-
- Scenario 4: Your installed Production deployment version is 21.0.2-IF012 or newer (If you do not have 21.0.3 IF012 or newer, you need to upgrade to 21.0.3 IF012 or newer before proceeding with this upgrade).
Note: You can only upgrade to 21.0.3-IF00x from the latest 21.0.2-IF012
Actions: To upgrade your environment, follow the Upgrading automation containers instructions.- When you perform the upgrade, you can substitute the CASE package from this interim fix for the 21.0.3 CASE package while you follow the instructions. For air gap, you can use the case save command in step 2 of scenario 5.
- Note: If you are using versions before 21.0.2, then you must incrementally upgrade and follow the instructions for each version between your source version and 21.0.3
- Scenario 5: Your installed Production deployment version is 21.0.3-IFxxx and you're using pinned catalog (note that pinned catalog was available with 21.0.3-IF007 or later)
Actions: Apply the updated catalog sources below (Note: you are not require to execute the "update_subscription.sh" script to change the subscription).- Apply the catalog sources to pin to the specified versions for IBM Automation Foundation, IBM Foundational Services with Cloud Pak for Business Automation.
You can apply the catalog sources below from a command line by creating a YAML file (for example, cp4ba_catalog_sources.yaml) with the catalog sources below and performing "oc apply -f cp4ba_catalog_sources.yaml", or you can apply the catalog sources using the OCP console
Note, you can apply only one catalog source at a time using the OCP console.
Note: The DB2, IBM Business Team Service, and Postgres catalog sources are dependent components of Cloud Pak for Business Automation.################################################################################ # # Licensed Materials - Property of IBM # # (C) Copyright IBM Corp. 2019. All Rights Reserved. # # US Government Users Restricted Rights - Use, duplication or # disclosure restricted by GSA ADP Schedule Contract with IBM Corp. # ############################################################################### # CP4BA 21.0.3-IF035 catalog apiVersion: operators.coreos.com/v1alpha1 kind: CatalogSource metadata: name: ibm-cp4a-operator-catalog namespace: openshift-marketplace spec: displayName: ibm-cp4a-operator publisher: IBM sourceType: grpc image: icr.io/cpopen/ibm-cp-automation-catalog@sha256:6e2002f57c75cc8b9a63ca5ade2fb5c6d8959a87cf1ab8d56a501cd7c8ff28cf updateStrategy: registryPoll: interval: 45m --- # IBM Automation Foundation Base 1.3.15 apiVersion: operators.coreos.com/v1alpha1 kind: CatalogSource metadata: name: ibm-cp-automation-foundation-catalog namespace: openshift-marketplace spec: displayName: IBM Automation Foundation Operators publisher: IBM sourceType: grpc image: icr.io/cpopen/ibm-cp-automation-foundation-catalog@sha256:64d7dafb687a6f965c605b8d1dac6147d55d851d81c296b7090487042634c099 updateStrategy: registryPoll: interval: 45m --- # IBM Automation Foundation Core 1.3.15 apiVersion: operators.coreos.com/v1alpha1 kind: CatalogSource metadata: name: ibm-automation-foundation-core-catalog namespace: openshift-marketplace spec: displayName: IBM Automation Foundation Core Operators publisher: IBM sourceType: grpc image: icr.io/cpopen/ibm-automation-foundation-core-catalog@sha256:1f80c5f43ffa6d00dfa776b140e19e2db36c4c731da255a4e042fd7ba73e0eeb updateStrategy: registryPoll: interval: 45m --- # IBM Cloud Foundational Services 3.19.22 apiVersion: operators.coreos.com/v1alpha1 kind: CatalogSource metadata: name: opencloud-operators namespace: openshift-marketplace annotations: bedrock_catalogsource_priority: '1' spec: displayName: IBMCS Operators publisher: IBM sourceType: grpc #3.19.22 #image: icr.io/cpopen/ibm-common-service-catalog@sha256:638cf8467f17122e0238a5dfca9cfc445e189c4cd57971faebbe6c31b6be0ab0 image: icr.io/cpopen/ibm-common-service-catalog@sha256:cc770f7c03cb00d70d143a2f42107f1e3b034c2c795952b0cc01dfec249ad60b updateStrategy: registryPoll: interval: 45m priority: 100 --- # DB2 Operator Case version 5.6.3+20240329.120225.56.8634 apiVersion: operators.coreos.com/v1alpha1 kind: CatalogSource metadata: name: ibm-db2uoperator-catalog namespace: openshift-marketplace spec: displayName: IBM Db2U Catalog #5.1.3 #image: icr.io/cpopen/ibm-db2uoperator-catalog@sha256:269b92119828b09069df70f61f0032262eee7bae413e08935b2d0d68f65062d1 image: icr.io/cpopen/ibm-db2uoperator-catalog@sha256:0f0f735f3b91cfd32f8a17eb6a9f003f0030bfc862c8d7d76bcfce535fb9ad0f imagePullPolicy: Always publisher: IBM sourceType: grpc updateStrategy: registryPoll: interval: 45m --- # IBM Business Teams Service version 3.33.1 apiVersion: operators.coreos.com/v1alpha1 kind: CatalogSource metadata: name: bts-operator namespace: openshift-marketplace annotations: bedrock_catalogsource_priority: '1' spec: displayName: BTS Operator publisher: IBM sourceType: grpc #image: icr.io/cpopen/ibm-bts-operator-catalog@sha256:aa49b78da11e3f072537b05b84494db55b2e2b1558fac59217ff8e651b57120e image: icr.io/cpopen/ibm-bts-operator-catalog@sha256:866f0212eab7bc70cc7fcf7ebdbb4dfac561991f6d25900bd52f33cd90846adf updateStrategy: registryPoll: interval: 45m --- # Cloud Native PostgresSQL 1.18.12 (4.25.0) apiVersion: operators.coreos.com/v1alpha1 kind: CatalogSource metadata: annotations: bedrock_catalogsource_priority: '1' name: cloud-native-postgresql-catalog namespace: openshift-marketplace spec: displayName: Cloud Native Postgresql Catalog publisher: IBM sourceType: grpc #image: icr.io/cpopen/ibm-cpd-cloud-native-postgresql-operator-catalog@sha256:642aba4b78bcadd8f1d5e1f9d05d8484e2934d914a5b6d67435f3e98082d7592 image: icr.io/cpopen/ibm-cpd-cloud-native-postgresql-operator-catalog@sha256:0b46a3ec66622dd4a96d96243602a21d7a29cd854f67a876ad745ec524337a1f updateStrategy: registryPoll: interval: 45m priority: 100
- If you have any subscriptions set to manual, then you need to approve any pending operator updates.
- If some of the many operator updates are not approved, it is not recommended to set subscriptions to manual, this makes the upgrade more error prone. By default all subscriptions are set to automatic.
- Apply the catalog sources to pin to the specified versions for IBM Automation Foundation, IBM Foundational Services with Cloud Pak for Business Automation.
-
Scenario 6: If you are not using "pinned" catalog and your installation is version 21.0.3-IFxxxx (where xxxx is the latest iFix of 21.0.3). Your 21.0.3 installation has the latest iFix because you are using the IBM Operator Catalog and the CP4BA Operator will automatically upgrades to the latest iFix when it is available.
Actions: Apply the updated catalog sources above in scenario #3. Then execute the "update_subscription.sh" script to change the subscriptions.-
Update the existing subscriptions of Cloud Pak for Business Automation, Automation Foundation, and Cloud Pak Foundational Services to change from IBM Operator Catalog to the individual catalogs applied above.
- Find the update_subscription.sh script from the extracted CASE package under "../ibm-cp-automation/inventory/cp4aOperatorSdk/files/deploy/crs/cert-kubernetes/scripts" Note, at the root of the CASE package is a nested archive that needs to be extracted as well.
- Log in to your OCP cluster as a cluster administrator
- Execute the update_subscription.sh -n <your cp4ba namespace>
Note, at this point, the environment will be updated to use the new "pinned" catalogs. Your environment will no longer auto-update the operators when new versions are released.
- If you have any subscriptions set to manual, then you need to approve any pending operator updates.
If some of the many operator updates are not approved, it is not recommended to set subscriptions to manual, this makes the upgrade more error prone. By default all subscriptions are set to automatic.
-
-
Scenario 7: Your installed Production deployment is 21.0.3.x and using airgap/offline.
Actions:After the operators are upgraded, it will trigger the upgrade of the related deployments and pods. See the items mentioned in "Performing the necessary tasks after installation" for more actions that can be needed after the upgrade is completed.-
Set up the environment variables for CASE.
export CASE_NAME=ibm-cp-automation export CASE_VERSION=3.2.35 export CASE_INVENTORY_SETUP=cp4aOperatorSetup export CASE_ARCHIVE=${CASE_NAME}-${CASE_VERSION}.tgz export OFFLINEDIR=/opt/cp4ba2103-if035 export CASE_LOCAL_PATH=${OFFLINEDIR}/${CASE_ARCHIVE}
Note: The values are specific to the interim fix, however, you can choose a different empty directory for the OFFLINEDIR if you need to put the files somewhere else. -
Save this specific set of case packages
cloudctl case save --case docker://icr.io/cpopen/ibm-cp-automation-case-cache@sha256:55ca1655dd43d47d586a62b2ff7b8fdc78c492b8633a1b5154dca6336d66f514 --outputdir ${OFFLINEDIR}
Once the command completes, all the Case archive and inventory are saved under /opt/cp4ba2103-if035. - Mirror the entitled registry images to the local registry by completing the same steps used during installation. For more information about mirroring, see Mirroring images to the private registry.
Make sure to use the CASE image OFFLINEDIR (/opt/cp4ba2103-if035) from step 1. - Update the catalog with the new version by running the install-catalog action.
cloudctl case launch \ --case ${OFFLINEDIR}/${CASE_ARCHIVE} \ --inventory ${CASE_INVENTORY_SETUP} \ --action install-catalog \ --namespace ${NAMESPACE} \ --args "--registry ${LOCAL_REGISTRY} --inputDir ${OFFLINEDIR} --recursive"
-
If you have any subscriptions set to manual, then you need to approve any pending operator updates.If some of the many operator updates are not approved, it is not recommended to set subscriptions to manual as it can make the upgrade more error prone. By default all subscriptions would be set to automatic.
-
Performing the necessary tasks after installation
- Update Kafka certificates when you are using Business Automation Insights
If you are using Business Automation Insights and upgrading from an IBM Automation Foundation version before 1.3, the operator will fail to become ready after the upgrade, and kafka/zookeeper pods show SSL errors. To resolve the issue, follow the "To renew the leaf certificates for Kafka" instructions in Changes to CA certificate and key does not automatically rotate Kafka leaf certificates. - 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 -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 theibm-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. - Required when you are using Workflow Process Service OCP deployment
If you used any individual image tag settings in your WfPSRuntime CR, it could prevent the operator from updating the images to the appropriate version. Ensure you remove any of these settings when you upgrade. - Required when you are using Workflow Process Service Docker Compose Edition
- Follow the step 2 of section "3. Running your environment" in Installing Workflow Process Service to log in to the entitled registry with your entitlement key.
- Back up your database backup, docker-compose.yml and folder for docker volumes “production_workflow_runtime_data” and “production_workflow_runtime_logs”.
- (Optional) Push the images to your docker registry. Log in to your docker registry, and push the docker images into your docker registry by using the following commands:
docker login <server> docker tag cp.icr.io/cp/cp4a/workflow-ps/workflow-ps-server:<tag> \ <server>/workflow-ps-server:<tag> docker tag cp.icr.io/cp/cp4a/workflow-ps/workflow-ps-authoring:<tag> \ <server>/workflow-ps-authoring:<tag> docker push <server>/workflow-ps-server:<tag> docker push <server>/workflow-ps-authoring:<tag>
- Run
docker-compose down
command to stop the Workflow Process Server container. - Update the image url's tags in docker-compose.yml.
<server>/workflow-ps-server:<tag> <server>/workflow-ps-authoring:<tag>
Where <tag> is the corresponding tag matching this interim fix's tag in the form of <release>-IFxxx, for example, 21.0.3-IF035. - Run
docker-compose up
command to start the Workflow Process Server container
For more detail on Workflow Process Service, refer to Installing Workflow Process Service .Troubleshooting: If you are using a Docker Desktop version 4.3.0 or greater, you might get an out of memory error when you start the server. For more details and possible resolution to this issue, and other troubleshooting guidance, refer to Installing IBM Workflow Process Service Trial. - Required when you are using Operational Decision Manager
You must update your Rule Designer:
- Open Eclipse
- Open menu Help > Check for Updates
- Select IBM Operational Decision Manager for Developers v8.11.x - Rule Designer
- Proceed with installation.
Uninstalling
List of Fixes
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
- Cloud Pak for Business Automation Operator
- Automation Document Processing
- Automation Decision Services
- Business Automation Application
- Business Automation Insights
- Business Automation Navigator
- Business Automation Studio
- Business Automation Workflow including Automation Workstream Services
- Enterprise Records
- FileNet Content Manager
- Operational Decision Management
- User Management Service
- Workflow Process Service
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-2019-25162, CVE-2020-26555, CVE-2020-36777, CVE-2021-46909, CVE-2021-46934, CVE-2021-46972, CVE-2021-47013, CVE-2021-47055, CVE-2021-47069, CVE-2021-47073, CVE-2021-47118, CVE-2021-47153, CVE-2021-47171, CVE-2021-47185, CVE-2021-47236, CVE-2021-47310, CVE-2021-47311, CVE-2021-47353, CVE-2021-47356, CVE-2021-47456, CVE-2021-47495, CVE-2022-48627, CVE-2022-48669, CVE-2023-38709, CVE-2023-39326, CVE-2023-45283, CVE-2023-5090, CVE-2023-52439, CVE-2023-52445, CVE-2023-52464, CVE-2023-52477, CVE-2023-52513, CVE-2023-52520, CVE-2023-52528, CVE-2023-52560, CVE-2023-52565, CVE-2023-52578, CVE-2023-52594, CVE-2023-52595, CVE-2023-52598, CVE-2023-52606, CVE-2023-52607, CVE-2023-52610, CVE-2023-52615, CVE-2023-52626, CVE-2023-52667, CVE-2023-52669, CVE-2023-52675, CVE-2023-52686, CVE-2023-52700, CVE-2023-52703, CVE-2023-52781, CVE-2023-52813, CVE-2023-52835, CVE-2023-52877, CVE-2023-52878, CVE-2023-52881, CVE-2023-6240, CVE-2024-0340, CVE-2024-21131, CVE-2024-21138, CVE-2024-21140, CVE-2024-21144, CVE-2024-21145, CVE-2024-21147, CVE-2024-23307, CVE-2024-25744, CVE-2024-26583, CVE-2024-26584, CVE-2024-26585, CVE-2024-26593, CVE-2024-26603, CVE-2024-26610, CVE-2024-26615, CVE-2024-26642, CVE-2024-26643, CVE-2024-26656, CVE-2024-26659, CVE-2024-26664, CVE-2024-26675, CVE-2024-26693, CVE-2024-26694, CVE-2024-26735, CVE-2024-26743, CVE-2024-26744, CVE-2024-26759, CVE-2024-26779, CVE-2024-26801, CVE-2024-26804, CVE-2024-26826, CVE-2024-26859, CVE-2024-26872, CVE-2024-26892, CVE-2024-26897, CVE-2024-26901, CVE-2024-26906, CVE-2024-26907, CVE-2024-26919, CVE-2024-26933, CVE-2024-26934, CVE-2024-26964, CVE-2024-26973, CVE-2024-26974, CVE-2024-26982, CVE-2024-26993, CVE-2024-27014, CVE-2024-27048, CVE-2024-27052, CVE-2024-27056, CVE-2024-27059, CVE-2024-27397, CVE-2024-27410, CVE-2024-28752, CVE-2024-35235, CVE-2024-35789, CVE-2024-35835, CVE-2024-35838, CVE-2024-35845, CVE-2024-35852, CVE-2024-35853, CVE-2024-35854, CVE-2024-35855, CVE-2024-35888, CVE-2024-35890, CVE-2024-35958, CVE-2024-35959, CVE-2024-35960, CVE-2024-36004, CVE-2024-36007, CVE-2024-6387, GO-2023-2153, PRISMA-2023-0056, RHSA-2024:4058, RHSA-2024:4197, RHSA-2024:4247, RHSA-2024:4567
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.
|
Known Issue | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
N/A | N/A |
Known Issue | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
N/A | N/A |
Known Issue | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
N/A | N/A |
Known Issue | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
DT228436 | TYPE AHEAD TEXT VIEW FROM THE UI TOOLKIT IS THROWING AN ERROR WHEN USING ITEMS FROM SERVICE |
Known Issue | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
N/A | N/A |
Known Issue | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
N/A | N/A |
Known Issue | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
DT386834 | CVE-2023-33008 in BAStudio and Workflow Authoring image | X | ||
DT228436 | TYPE AHEAD TEXT VIEW FROM THE UI TOOLKIT IS THROWING AN ERROR WHEN USING ITEMS FROM SERVICE | |||
DT390925 | Start service REST API might not start the service with the specified snapshot |
Known Issue | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
DT386834 | CVE-2023-33008 in BAStudio and Workflow Authoring image | X | ||
DT173923 | THE ORDER OF VARIABLES IN EXPOSED PROCESS VALUES IS NOT PRESERVED IN THE PROCESS EDITOR | |||
DT179122 | DBUPGRADE NEED SUPPORT SAME VERSION UPGRADE FOR SOME SPECIAL FIXES | |||
DT228436 | TYPE AHEAD TEXT VIEW FROM THE UI TOOLKIT IS THROWING AN ERROR WHEN USING ITEMS FROM SERVICE | |||
DT389264 | Workflow Center console is loading too many snapshots even when JR64203 is applied | |||
DT390925 | Start service REST API might not start the service with the specified snapshot |
Known Issue | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
N/A | N/A |
Known Issue | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
See FileNet Content Manager Release Fix List APARs for IBM Cloud Pak for Business Automation technote |
Known Issue | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
DT387048 | RULEAPP GENERATION FAILS WHEN USING CONCURRENTHASHMAP | |||
DT389858 | ERROR MESSAGE ON RELEASE DELETION | |||
DT390866 | ACTIVE ATTRIBUTE DEPRECATED MESSAGE IN RULE DESIGNER |
Known Issue | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
N/A | N/A |
Known Issue | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
DT387339 | Information disclosure security vulnerability in IBM Business Automation Workflow - CVE-2024-38321 | X | ||
DT173923 | THE ORDER OF VARIABLES IN EXPOSED PROCESS VALUES IS NOT PRESERVED IN THE PROCESS EDITOR | |||
DT390925 | Start service REST API might not start the service with the specified snapshot |
Known Limitations
Document change history
Related Information
[Supersedes 21.0.3-IF034] Readme for Cloud Pak for Business Automation 21.0.3 I…
[Supersedes 21.0.3-IF033] Readme for Cloud Pak for Business Automation 21.0.3 I…
[Supersedes 21.0.3-IF032] Readme for Cloud Pak for Business Automation 21.0.3 I…
Fix list for Cloud Pak for Business Automation 21.0.3
Was this topic helpful?
Document Information
Modified date:
11 September 2024
UID
ibm17159788