Readme for Cloud Pak for Business Automation 21.0.1 IF004

Created by Tom Hawrylak on Wed, 08/18/2021 - 01:11

Published URL:

https://www.ibm.com/support/pages/node/6482163

6482163

Fix Readme

Abstract

The following document is the documentation for IBM Cloud Pak for Business Automation 21.0.1 IF004
Including download and installation information and the list of APARs that are resolved in this interim fix.

Content

Readme file for:	IBM Cloud Pak® Automation
Product Release:	21.0.1
Update Name:	21.0.1 IF004
Fix ID:	21.0.1-WS-CP4BA-IF004
Publication Date:	19 Aug 2021
Last modified date:	27 Sep 2021

Prerequisites
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.1-IF004, 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

Prior to installation

If you have Cloud Pak for Business Automation 21.0.1 deployed on a Kubernetes cluster that has access to the internet, then your deployment should be upgraded automatically to 21.0.1-IF004. This is a change in behavior starting with 21.0.1-IF004. In other words, when the Cloud Pak for Business Automation 21.0.1-IF004 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.1-IF004, 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.1 installed using airgap, you still need to follow this readme to upgrade to 21.0.4-IF004 as the upgrade will not occur automatically.

If you have Cloud Pak for Business Automation 20.0.3.x or older currently installed (e.g., 20.0.3-IF005 currently installed) or if you have 21.0.1 installed using airgap, you can update the deployment to 21.0.1-IF004 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.

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.1-IF004, 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.1" 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.0.4.tgz. To download the CASE package, go to https://github.com/IBM/cloud-pak/raw/master/repo/case/ibm-cp-automation-3.0.4.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.0.4.tgz
- Make sure you use the same bastion host that was previously used to deploy

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:

Colunm 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
Business Automation Application
Automation Decision Services
Business Automation Insights
Business Automation Navigator
Business Automation Studio
Business Automation Workflow
Enterprise Records
FileNet Content Manager
Operational Decision Management
User Management Service

General

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. Vulnerabilities (CVEs) for these libraries are published regularly. With 21.0.1 IF004, fixes for these libraries have been included to address: CVE-2019-10086, CVE-2020-14373, CVE-2020-16287, CVE-2020-16288, CVE-2020-16289, CVE-2020-16290, CVE-2020-16291, CVE-2020-16292, CVE-2020-16293, CVE-2020-16294, CVE-2020-16295, CVE-2020-16296, CVE-2020-16297, CVE-2020-16298, CVE-2020-16299, CVE-2020-16300, CVE-2020-16301, CVE-2020-16302, CVE-2020-16303, CVE-2020-16304, CVE-2020-16305, CVE-2020-16306, CVE-2020-16307, CVE-2020-16308, CVE-2020-16309, CVE-2020-16310, CVE-2020-17538, CVE-2020-25692, CVE-2020-27778, CVE-2020-28928, CVE-2020-36221, CVE-2020-36222, CVE-2020-36223, CVE-2020-36224, CVE-2020-36225, CVE-2020-36226, CVE-2020-36227, CVE-2020-36228, CVE-2020-36229, CVE-2020-36230, CVE-2020-8178, CVE-2021-21639, CVE-2021-21640, CVE-2021-21670, CVE-2021-21671, CVE-2021-23239, CVE-2021-23240, CVE-2021-23358, CVE-2021-23839, CVE-2021-24031, CVE-2021-24032, CVE-2021-27212, CVE-2021-28163, CVE-2021-28169, CVE-2021-28831, CVE-2021-29512, CVE-2021-29514, CVE-2021-29521, CVE-2021-29544, CVE-2021-30139, CVE-2021-33503, CVE-2021-34428, CVE-2021-36159, CVE-2021-37635, CVE-2021-37636, CVE-2021-37637, CVE-2021-37638, CVE-2021-37639, CVE-2021-37640, CVE-2021-37641, CVE-2021-37642, CVE-2021-37643, CVE-2021-37644, CVE-2021-37645, CVE-2021-37646, CVE-2021-37647, CVE-2021-37648, CVE-2021-37649, CVE-2021-37650, CVE-2021-37651, CVE-2021-37652, CVE-2021-37653, CVE-2021-37654, CVE-2021-37655, CVE-2021-37656, CVE-2021-37657, CVE-2021-37658, CVE-2021-37659, CVE-2021-37660, CVE-2021-37661, CVE-2021-37662, CVE-2021-37663, CVE-2021-37664, CVE-2021-37665, CVE-2021-37666, CVE-2021-37667, CVE-2021-37668, CVE-2021-37669, CVE-2021-37670, CVE-2021-37671, CVE-2021-37672, CVE-2021-37673, CVE-2021-37674, CVE-2021-37675, CVE-2021-37676, CVE-2021-37677, CVE-2021-37678, CVE-2021-37679, CVE-2021-37680, CVE-2021-37681, CVE-2021-37682, CVE-2021-37683, CVE-2021-37684, CVE-2021-37685, CVE-2021-37686, CVE-2021-37687, CVE-2021-37688, CVE-2021-37689, CVE-2021-37690, CVE-2021-37691, CVE-2021-37692, GHSA-x9hc-rw35-f44h, PRISMA-2021-0088

Cloud Pak for Automation Operator

APAR	Title	Sec.	Cont.	B.I.
N/A	N/A

Business Automation Application

APAR	Title	Sec.	Cont.	B.I.
N/A	N/A

Automation Decision Services

APAR	Title	Sec.	Cont.	B.I.
N/A	N/A

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.
JR63891	THE USER IS NOT ALLOWED TO PLAY BACK PROCESS EVEN IT IS ADDED TO THE TW_AUTHORS GROUP

Business Automation Workflow including Automation Workstream Services

APAR	Title	Sec.	Cont.	B.I.
N/A	N/A

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.
N/A	N/A

Known Limitations

For additional information, see the support page Cloud Pak for Business Automation Known Limitations

Document change history

19 Aug 2021: Initial publish.

27 Sep 2021: Fix incorrect reference to 21.0.2 in readme documentation

Internal Use Only

Fix Request: https://github.ibm.com/dba/icp4a-platform/issues/1212

[{"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":"21.0.1"}]