Contents

• Each interim fix typically supersedes all other previous interim fixes shipped for 22.0.1, and compliments a simultaneously delivered interim fix for IBM Cloud Pak for Business Automation 22.0.1. Consult the following table for specific relationships.
• Business Automation Workflow on containers delivers container images that include operating system level and other open source libraries. Vulnerabilities (CVEs) for these libraries are published regularly. These interim fixes include fixes for these libraries. Consult the superseded and related Cloud Pak for Business Automation 22.0.1 Readmes for specific information about vulnerabilities and other defects that have been addressed.

• Business Automation Workflow

oc get icp4acluster -o yaml

Installing the interim fix

• Scenario 1: Your installation is version 21.0.2.x or earlier.
  Actions: If you are using a version earlier than 21.0.3, you must upgrade first. 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 22.0.1 CASE package while you follow the instructions. For air-gapped environments, you can use the case save command in step 1 of scenario 3.
  Note: If you are using versions that are earlier than 21.0.2, you must incrementally upgrade and follow the instructions for each version between your source version and 22.0.1.
•  Scenario 2:  Your installation is online and 22.0.1.x.
  Actions: After these steps are completed, the operators are automatically upgraded.
  You can apply the following catalog sources from a command line by creating a YAML file (for example, cp4ba_catalog_sources.yaml) with the following catalog sources and performing "oc apply -f cp4ba_catalog_sources.yaml", or you can apply the catalog sources by using the OCP console.

  apiVersion: operators.coreos.com/v1alpha1
  kind: CatalogSource
  metadata:
    name: ibm-operator-catalog
    namespace: openshift-marketplace
  spec:
    displayName: "IBM Operator Catalog"
    image: icr.io/cpopen/ibm-operator-catalog
    publisher: IBM
    sourceType: grpc
    updateStrategy:
      registryPoll:
        interval: 45m

• Scenario 3:  Your installation is air gapped and 22.0.1.x.
  1. Set up the environment variables for CASE, taking 22.0.1-IF001 as example:
     • export CASE_NAME=ibm-cs-bawautomation 
     • export OFFLINEDIR=/tmp/cp4ba2201-if001
     • export CASE_VERSION=2.3.1
     • export CASE_INVENTORY_SETUP=cp4aOperatorSetup 
     • export CASE_ARCHIVE=${CASE_NAME}/${CASE_VERSION}/${CASE_NAME}-${CASE_VERSION}.tgz 
     • export CASE_LOCAL_PATH=${OFFLINEDIR}/${CASE_ARCHIVE}
     Note: The values are specific to the interim fix, for instance, the value for CASE_VERSION, however, you can choose a different empty directory for the OFFLINEDIR if you need to put the files somewhere else.
  2. Download the Cloud Pak archives and image inventory, and put them in the offline store

     cloudctl case save \
       --case https://github.com/IBM/cloud-pak/raw/master/repo/case/${CASE_ARCHIVE} \
       --outputdir ${OFFLINEDIR}

     and  then unpack the case file: 

     cd ${OFFLINEDIR}
     tar -xvzf ${CASE_ARCHIVE}
     cd cert-kubernetes

  3. Mirror images to trigger the operator upgrades. 
  4. Mirror the entitled registry images to the local registry by completing the same steps you followed during installation. For more information, see Mirroring images to the private registry.
     Important: Ensure you use the CASE image outputdir (/tmp/cp4ba-231) from step 1.
  5. If you have subscriptions set to manual, you must approve all the pending operator updates. 
     Important: Do not set subscriptions to manual because it can make the the upgrade more error prone if some of the many operator updates are not approved. By default all subscriptions are set to automatic.