Fix Readme
Abstract
The following document is the documentation for IBM Cloud Pak for Business Automation 21.0.2 IF002,
Including download and installation information and the list of APARs that are resolved in this interim fix.
Content
Readme file for: | IBM Cloud Pak® for Business Automation |
---|---|
Product Release: | 21.0.2 |
Update Name: | 21.0.2 IF002 |
Fix ID: | 21.0.2-WS-CP4BA-IF002 |
Publication Date: | 17 Aug 2021 |
Last modified date: | 17 Aug 2021 |
Contents
Prerequisites and Supersedes
Components impacted
Prior to installation
Installing
Performing the necessary tasks after installation
Uninstalling
List of fixes
Known Limitations
Document change history
Components impacted
Prior to installation
Installing
Performing the necessary tasks after installation
Uninstalling
List of fixes
Known Limitations
Document change history
Prerequisites and Supersedes
- Upgrading the dependencies. If upgrading from an earlier version 20.0.3.x to 21.0.2-IF002, follow the steps described here in Knowledge Center to upgrade the dependencies: https://www.ibm.com/docs/en/cloud-paks/cp-biz-automation/21.0.x?topic=containers-upgrading-dependencies
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
Prior to installation
If you have Cloud Pak for Business Automation 21.0.2 deployed on a Kubernetes cluster that has access to the internet, then the deployment should be upgraded automatically to 21.0.2-IF002. This upgrade behavior is the same when 21.0.2-IF001 was released and published. In other words, when the Cloud Pak for Business Automation 21.0.2-IF002 is released and published, the CP4BA Operator will automatically be updated to the latest published iFix. After the CP4BA Operator is successfully upgraded to 21.0.2-IF002, then the components that you have installed on your cluster will automatically be upgraded (unless you changed the Approval Strategy for CP4BA Operator from "Automatic" (default) to "Manual"). Note: if you have 21.0.2 installed using airgap, you still need to follow this readme to upgrade to 21.0.2-IF002.
If you have Cloud Pak for Business Automation 21.0.1.x or older currently installed (e.g., 21.0.1-IF001 currently installed) or if you have 21.0.2 installed using airgap, you can update the deployment to 21.0.2-IF002 by following this readme starting with the Installing section and the instructions in the Knowledge Center.
If you want to use this interim fix as a part of a new deployment, refer to IBM Knowledge Center IBM Cloud Pak for Business Automation 21.0.x.
Installing
Step 1: Get access to the interim fix container images
You can access the container images in the IBM image registry with your IBMid. You should already have admin.registrykey secret and ibm-entitlement-key secret (if you have BAW and/or BAI installed) already created from the current deployment. If these secrets no longer exist, then follow the steps below to create them.
You can access the container images in the IBM image registry with your IBMid. You should already have admin.registrykey secret and ibm-entitlement-key secret (if you have BAW and/or BAI installed) already created from the current deployment. If these secrets no longer exist, then follow the steps below to create them.
Create a pull secret for the IBM Cloud Entitled Registry
- Log in to MyIBM Container Software Library with the IBMid and password that is associated with the entitled software.
- In the Container software library tile, click "View library" and then click "Copy key" to copy the entitlement key to the clipboard.
- Log in to your Kubernetes cluster and set the context to the project/namespace for your existing deployment.
- Create image pull secrets by running kubectl create secret commands below.
$ kubectl create secret docker-registry admin.registrykey --docker-server=cp.icr.io --docker-username=cp --docker-password="<API_KEY_GENERATED>" --docker-email=<USER_EMAIL>
$ kubectl create secret docker-registry ibm-entitlement-key --docker-server=cp.icr.io --docker-username=cp --docker-password="<API_KEY_GENERATED>" --docker-email=<USER_EMAIL>
Note: The "cp.icr.io" value for the docker-server parameter is the only registry domain name that contains the images. Use "cp" for the docker-username. The docker-email must be a valid email address (associated to your IBM ID). Make sure you are copying the Entitlement Key in the docker-password field within double quotation marks. - Take a note of the secret and the server values so that you can set them to the "pullSecrets" and "repository" parameters when you update the operator for your containers.
Step 2: Update the installed CP4BA operator
- Updating using the Operator Hub:
- To upgrade the CP4BA Operator to 21.0.2-IF002, simply follow the Upgrading the operator in Operator Hub section in KC. Be sure to complete all the Upgrade steps in KC and change the appVersion in the CR to "21.0.2" as documented in one of the steps here: https://www.ibm.com/docs/en/cloud-paks/cp-biz-automation/21.0.x?topic=upgrade-checking-version-deployment-type-license.
- Updating using deployment script:
- The deployment script resides in the Container Application Software for Enterprises (CASE) package: ibm-cp-automation-3.1.2.tgz. To download the CASE package, go to ibm-cp-automation-3.1.2.tgz
- Then follow the instructions in KC here: https://www.ibm.com/docs/en/cloud-paks/cp-biz-automation/21.0.x?topic=operator-upgrading-by-running-script
- Updating using airgap:
- Follow the instructions in KC here: https://www.ibm.com/docs/en/cloud-paks/cp-biz-automation/21.0.x?topic=environment-installing-cloud-pak-catalog-operator-instance and replace the CASE package with the
CASE package for this iFix, which is ibm-cp-automation-3.1.2.tgz - Make sure you use the same bastion host that was previously used to deploy
- Follow the instructions in KC here: https://www.ibm.com/docs/en/cloud-paks/cp-biz-automation/21.0.x?topic=environment-installing-cloud-pak-catalog-operator-instance and replace the CASE package with the
Performing the necessary tasks after installation
For more information, see IBM Cloud Pak for Business Automation 21.0.x.
Uninstalling
For more information, see IBM Cloud Pak for Business Automation 21.0.x.
List of Fixes
APARs are listed in tables, columns are defined as follows:
Column title | Column description |
APAR | 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 document |
- General
- Cloud Pak for 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
General
APAR | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
N/A | X | X | X |
Cloud Pak for Automation Operator
APAR | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
N/A |
Cloud Pak for Business Automation delivers container images include many operating system level and other open source libraries. Vulnerability (CVEs) fixes for these libraries are published regularly.
With 21.0.2 IF002, fixes for these libraries have been included to address:
CVE-2019-14751, CVE-2019-19911, CVE-2019-25032, CVE-2019-25034, CVE-2019-25035, CVE-2019-25036, CVE-2019-25037, CVE-2019-25038, CVE-2019-25039, CVE-2019-25040, CVE-2019-25041, CVE-2019-25042, CVE-2020-10177, CVE-2020-10378, CVE-2020-10379, CVE-2020-10994, CVE-2020-11538, CVE-2020-24330, CVE-2020-24331, CVE-2020-24332, CVE-2020-28935, CVE-2020-35653, CVE-2020-35654, CVE-2020-35655, CVE-2020-5310, CVE-2020-5311, CVE-2020-5312, CVE-2020-5313, CVE-2021-2341, CVE-2021-2369, CVE-2021-25287, CVE-2021-25288, CVE-2021-25289, CVE-2021-25290, CVE-2021-25291, CVE-2021-25292, CVE-2021-25293, CVE-2021-27921, CVE-2021-27922, CVE-2021-27923, CVE-2021-28675, CVE-2021-28676, CVE-2021-28677, CVE-2021-28678, CVE-2021-29505, PRISMA-2021-0010, PRISMA-2021-0015, PRISMA-2021-0088 |
Automation Document Processing
APAR | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
JR64052 | EXCESSIVE DATABASE CONNECTIONS FROM BACKEND | X | X | |
JR64053 | DUPLICATED TRAINING SAMPLES LOWERING EXTRACTION MODEL ACCURACY | X | X | |
JR64054 | MISSING KEYCLASSID CAUSES INCORRECT KVP RESULTS | X | X | |
JR64055 | FAILED TO UPDATE KEYCLASS ERROR WITH TRAILING SPACE | X | X | |
JR64056 | REDEPLOYING PROJECTS WITH SHARED DATA DEFINITIONS FAIL | X | X | |
JR64057 | CHECKBOX INCORRECTLY IDENTIFIED AS CHECKED | X | X | |
JR64058 | DATA EXTRACTION TRAINING FAILS WITH DEADLOCK ERROR | X | X | |
JR64061 | VIEWONE POD DEPLOYMENT GIVES IMAGEPULLBACKOFF ERROR | X | X |
Automation Decision Services
APAR | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
N/A | N/A |
Business Automation Application
APAR | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
JR63994 | WALKME FAILS FOR APPLICATION DESIGNER USERS | X |
Business Automation Insights
APAR | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
N/A |
N/A |
Business Automation Navigator
APAR | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
N/A |
N/A
|
Business Automation Studio
APAR | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
JR63963 | THE DEPLOYED PODS CRASHED WITH SEGMENTATION ERROR | |||
JR63891 | THE USER IS NOT ALLOWED TO PLAY BACK PROCESS EVEN IT IS ADDED TO THE TW_AUTHORS GROUP | |||
JR63994 | WALKME FAILS FOR APPLICATION DESIGNER USERS | X |
Business Automation Workflow including Automation Workstream Services
APAR | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
JR63749 | YOU AREN'T ABLE TO ADD MORE THAN 10 VALUES TO A BUSINESS OBJECT PROPERTY ON A CASE THAT IS USING A CUSTOM CSHS VIEW | X | ||
JR63953 | YOU MIGHT FIND IMAGE PULL ERROR WHEN YOU DEPLOY BUSINESS AUTOMATION WORKFLOW USING THE FORM UI | |||
JR63960 | MULTIPLE ADD REQUESTS ARE MADE RESULTING WITH MULTIPLE CASES WHEN YOU CLICK THE ADD CASE BUTTON MULTIPLE TIMES | |||
JR63973 | YOU CANNOT OPEN A CASE INSTANCE FROM WORKPLACE BECAUSE THE WORKFLOW AUTHORING URL HAS AN INCORRECT HOSTNAME | |||
JR63974 | YOU MIGHT RECEIVE CONTENT SECURITY POLICY ERROR WHEN YOU OPEN TASKS ON PORTAL AFTER UPGRADING | |||
JR63963 | THE DEPLOYED PODS CRASHED WITH SEGMENTATION ERROR |
Enterprise Records
APAR | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
N/A
|
N/A
|
FileNet Content Manager
APAR | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
N/A | N/A |
Operational Decision Management
APAR | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
N/A | N/A |
User Management Service
APAR | Title | Sec. | Cont. | B.I. |
---|---|---|---|---|
JR63963 | THE DEPLOYED PODS CRASHED WITH SEGMENTATION ERROR |
Known Limitations
For additional information, see the support page Cloud Pak for Business Automation Known Limitations
Document change history
[{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SS2JQC","label":"IBM Cloud Pak for Automation"},"ARM Category":[{"code":"a8m0z0000001gWWAAY","label":"CloudPak4Automation Platform"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Versions"}]
Was this topic helpful?
Document Information
Modified date:
31 July 2023
UID
ibm16481961