Upgrading to Fix Pack 2 - scenario 2

If your Red Hat OpenShift Container Platform version is 4.6, IBM Cloud Pak foundational services (previously called Common services) version is 3.6.x, Red Hat® Advanced Cluster Management for Kubernetes version is 2.2, and IBM Cloud Pak® for Multicloud Management version is 2.3 Fixpack 1, you want to upgrade as follows:

Red Hat OpenShift Container Platform 4.6
IBM Cloud Pak foundational services 3.6.x -> 3.12
Red Hat® Advanced Cluster Management 2.2 -> 2.3
IBM Cloud Pak for Multicloud Management 2.3 Fix Pack 1 -> Fix Pack 2

Notes:

In this upgrading scenario, IBM Cloud Pak foundational services, Red Hat® Advanced Cluster Management for Kubernetes, and IBM Cloud Pak® for Multicloud Management are upgraded to their later versions. The only service that is not upgraded is Red Hat OpenShift Container Platform, which remains version 4.6.
You are recommended to upgrade IBM Cloud Pak® for Multicloud Management first, then upgrade IBM Cloud Pak foundational services, and then upgrade Red Hat® Advanced Cluster Management for Kubernetes.

Online upgrading

For online installations, follow the steps:

To upgrade your IBM Cloud Pak® for Multicloud Management from Fix Pack 1 to Fix Pack 2, ensure that the CatalogSource for IBM Cloud Pak® for Multicloud Management has the following image value:
```
quay.io/cp4mcm/cp4mcm-orchestrator-catalog:2.3-latest
```
Then, IBM Cloud Pak® for Multicloud Management 2.3 Fix Pack 1 can be upgraded to IBM Cloud Pak® for Multicloud Management 2.3 Fix Pack 2 automatically.
Upgrade IBM Cloud Pak foundational services to version 3.12:

Note: Because IBM Cloud Pak foundational services 3.6 doesn't support Red Hat® Advanced Cluster Management for Kubernetes 2.3, you need to upgrade IBM Cloud Pak foundational services to version 3.12 before you upgrade Red Hat® Advanced Cluster Management for Kubernetes to 2.3.
1. Edit the CatalogSource for IBM Cloud Pak foundational services by running the following command:
```
oc -n openshift-marketplace edit catalogsource opencloud-operators
```
  In the result screen, modify the value of the imgae field to the following value:
```
  image: docker.io/ibmcom/ibm-common-service-catalog:3.12
```
  Check whether quay.io/opencloudio/* is in the clusterimagepolicy repository by running the following command:
```
oc get clusterimagepolicy ibmcloud-default-cluster-image-policy -o yaml -n management-security-services
```
  Note: The clusterimagepolicy exists only after you enabled securityServices and ibm-management-image-security-enforcement in the previous installation or upgrading process.
  
  If not, you need to add quay.io/opencloudio/* to the clusterimagepolicy repository.
2. Edit the Subscription for IBM Cloud Pak foundational services by running the following command:
```
oc edit -n openshift-operators sub ibm-common-service-operator
```
  In the result screen, modify the value of the channel field to the following value:
```
channel: v3
```
3. Wait for about ten minutes for the IBM Cloud Pak foundational services operators to complete the upgrading process. Verify whether all IBM Cloud Pak foundational services pods are in running status by running the following command:
```
oc get pods -n ibm-common-services
```
To upgrade Red Hat® Advanced Cluster Management for Kubernetes to version 2.3, edit the Subscription for Red Hat® Advanced Cluster Management for Kubernetes by running the following command:
```
oc edit -n open-cluster-management sub acm-operator-subscription
```
In the result screen, modify the value of the channel field to the following value:
```
channel: release-2.3
```
Note: After Red Hat® Advanced Cluster Management for Kubernetes is upgraded, the ibm-cert-manager-operator needs to be restarted.

Offline upgrading

For offline (airgap) installations, follow the steps:

Upgrade IBM Cloud Pak® for Multicloud Management in an airgap environment from Fix Pack 1 to Fix Pack 2. For more information, see Offline (airgap) upgrade.

Note: You need to download the ibm-cp-management-100.3.22+2.3.21.tgz archive file for Fix Pack 2.
Upgrade IBM Cloud Pak foundational services in an airgap environment to version 3.12. Follow the steps:

Note: Because IBM Cloud Pak foundational services 3.6 doesn't support Red Hat® Advanced Cluster Management for Kubernetes 2.3, you need to upgrade IBM Cloud Pak foundational services to version 3.12 before you upgrade Red Hat® Advanced Cluster Management for Kubernetes to 2.3.
1. Log in to your OpenShift Container Platform console.
2. Delete the IBM Cloud Pak foundational services catalog source by running the following command:
```
oc delete catalogsource opencloud-operators -n openshift-marketplace
```
3. Create the catalog source.
```
cloudctl case launch \
--case $OFFLINE_DIR/${CASE_ARCHIVE} \
--inventory ${CASE_INVENTORY_SETUP} \
--action install-catalog \
--namespace ${NAMESPACE} \
--args "--registry ${LOCAL_DOCKER_REGISTRY} --inputDir $OFFLINE_DIR --recursive" \
--tolerance 1
```
  Note: The variable $OFFLINE_DIR is set in Preparing for installation by using a bastion host, and is the directory that serves as the offline store to store this current release installer and image inventory.
Upgrade Red Hat® Advanced Cluster Management for Kubernetes to 2.3.

Note: After Red Hat® Advanced Cluster Management for Kubernetes is upgraded, the ibm-cert-manager-operator needs to be restarted.