• Business Automation Insights 23.0.2-IF002
• Cloud Pak Foundational Services 4.4

tar -xvzf ibm-cp-automation-5.1.2.tgz
cd ibm-cp-automation/inventory/cp4aOperatorSdk/files/deploy/crs
tar -xvf cert-k8s-23.0.2.tar
cd cert-kubernetes

• Scenario 1: You are installing a Production deployment
  Actions: 
  You can use this interim fix content to perform a Production deployment.  To deploy a Production deployment using the content of this interim fix, please see install a new Production environment  and use the CASE package from this interim fix.
  Note: If you have an existing Cloud Pak Foundation Services instance installed in the cluster 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.
• Scenario 2:  Your installed Production deployment is 23.0.2 GA and is online.
  Actions: 
  Perform the following steps and then the upgrade of operators and deployments will start.
  1. Upgrade the CP4BA operators using one of two methods. 
     • Option 1: Running the operator upgrade script from the case package.

       ./scripts/cp4a-deployment.sh -m upgradeOperator -n <project_name>

     • Option 2: Manually deploy the catalog source and update the CPFS channels using the CPFS upgrade script.
       1. Apply the new catalog sources.

          oc apply -f ./descriptors/op-olm/catalog_source.yaml

       2. Update the cert manager and license service channels to the appropriate level with this script:

          ./scripts/cpfs/installer_scripts/cp3pt0-deployment/setup_singleton.sh --enable-licensing --cert-manager-source ibm-cert-manager-catalog --licensing-source ibm-licensing-catalog --license-accept -v 1 -c v4.2

       3. Update the channels to the appropriate levels for the rest of the CPFS subscriptions.

          ./scripts/cpfs/installer_scripts/cp3pt0-deployment/setup_tenant.sh --operator-namespace <CP4BA Namespace> -s opencloud-operators-v4-4 -c v4.4 --license-accept -v 1

          Note: Be sure to replace the namespace with the appropriate 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.
     1. Run the script in [upgradeOperatorStatus] mode to check that the upgrade of the CP4BA operator and its dependencies is successful.

        ./scripts/cp4a-deployment.sh -m upgradeOperatorStatus -n <project_name>

        Warning: The script will scale the CP4BA deployments down to zero. You must execute the upgradeDeploymentStatus command to scale them back up.
     2. Run the script in [upgradeDeploymentStatus] mode to check that the upgrade of the CP4BA deployment is successful.

        ./scripts/cp4a-deployment.sh -m upgradeDeploymentStatus -n <project_name>

• Scenario 3:  Your installed Production deployment is 23.0.2 GA and using airgap/offline.
  Actions: 
  Perform the following steps and then the upgrade of operators and deployments will start.
  1. Download the case package mirror file, cp4ba-case-to-be-mirrored-23.0.2-IF002.txt, for this interim fix and you must rename the file to cp4ba-case-to-be-mirrored-23.0.2-IF002.yaml. Then execute this command to download the case files:

     oc ibm-pak get -c file://(absolute path to file)/cp4ba-case-to-be-mirrored-23.0.2-IF002.yaml

     The (absolute path to file) needs to be a path starting from "/". For example, "/opt"
     For more information, see Downloading the CASE files.
  2. You will need to mirror the images associated with the new case package. Follow the instructions for either mirroring option in Mirroring images to the private registry using the new version values associated with this fix.

     export CASE_NAME=ibm-cp-automation
     export CASE_VERSION=5.1.2

  3. Update the catalog with the new version.

     cat $HOME/.ibm-pak/data/mirror/$CASE_NAME/$CASE_VERSION/catalog-sources.yaml | sed 's/opencloud-operators/opencloud-operators-v4-4/g' | oc apply -f -

  4. Update the cert manager and license service channels to the appropriate level with this script:

     ./scripts/cpfs/installer_scripts/cp3pt0-deployment/setup_singleton.sh --enable-licensing --cert-manager-source ibm-cert-manager-catalog --licensing-source ibm-licensing-catalog --license-accept -v 1 -c v4.2

  5. Update the channels to the appropriate levels for the rest of the CPFS subscriptions.

     ./scripts/cpfs/installer_scripts/cp3pt0-deployment/setup_tenant.sh --operator-namespace <CP4BA Namespace> -s opencloud-operators-v4-4 -c v4.4 --license-accept -v 1

     Note: Be sure to replace the namespace with the appropriate CP4BA namespace.
  6. 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 oc get installPlan to see the current status of the install plans.
     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 can make the upgrade more error prone.

Performing the necessary tasks after installation