Upgrading IBM Cloud Pak foundational services offline

You can upgrade IBM Cloud Pak foundational services that were installed in a prior release in an airgap environment.

• Upgrading IBM Cloud Pak foundational services to version 3.6
  • 1. Mirror the images
  • 2. Create the new catalog source
  • 3. Post-upgrade
• Upgrade IBM Cloud Pak foundational services to 3.12 or later versions
• Troubleshooting

Upgrading IBM Cloud Pak foundational services to version 3.6

You can upgrade only the following supported path:

• IBM Cloud Pak foundational services installer version 3.5.x to common services installer version 3.6.x.

During the upgrade process, you cannot access the services management console.

1. Mirror the images

Your environment might already have a prepared bastion, a portable compute, or a portable storage device and the required Docker registries.

You must then download the ibm-cp-common-services-1.2.3.tgz image, mirror, and import the images in your airgap environment image registry.

• If you are using a bastion server, complete these steps from the Upgrading IBM Cloud Pak foundational services by using a bastion compute device topic:

  1. Create environment variables for the installer and image inventory
  2. Download the IBM Cloud Pak foundational services installer and image inventory
  3. Log in to the OpenShift Container Platform as a cluster administrator
  4. Create an environment variable for the IBM Cloud Pak foundational services namespace
  5. Mirror the images and configure the cluster

• If you are using a portable compute device, complete these steps from the Upgrading IBM Cloud Pak foundational services by using a portable compute device topic:

  1. Create environment variables for the installer and image inventory
  2. Connect the portable host to the internet
  3. Download the IBM Cloud Pak foundational services installer and image inventory
  4. Mirror the images to the portable host
  5. Connect the portable host to the airgap network
  6. Log in to the OpenShift Container Platform as a cluster administrator
  7. Create an environment variable for the IBM Cloud Pak foundational services namespace
  8. Mirror the images and configure the cluster

• If you are using a portable storage device, complete these steps from the Upgrading IBM Cloud Pak foundational services by using a portable storage device topic:

  1. Create environment variables for the installer and image inventory
  2. Download the IBM Cloud Pak foundational services installer and image inventory
  3. Mirror the images to the external host
  4. Copy the saved offline data to an external storage device
  5. Log in to the host that has access to the OpenShift Container Platform cluster
     1. Log in to the OpenShift Container Platform as a cluster administrator
     2. Create an environment variable for the IBM Cloud Pak foundational services namespace
     3. Prepare the internal host and extract images
     4. Mirror the images and configure the cluster

2. Create the new catalog source

After you mirror the images, complete these steps:

1. Log in to your OpenShift Container Platform console.

2. Remove the catalog source that you created in version 3.5.x.

   oc delete CatalogSource opencloud-operators -n openshift-marketplace
   

3. Create the IBM Cloud Pak foundational services version 3.6.x catalog source.

    cloudctl case launch \
      --case $CASE_LOCAL_PATH \
      --namespace $NAMESPACE \
      --inventory $CASE_INVENTORY_SETUP \
      --action install-catalog \
      --args "--registry $TARGET_REGISTRY --inputDir $OFFLINEDIR --recursive"
   

After the catalog source is created, the Operand Deployment Lifecycle Manager Operator updates the installed IBM Cloud Pak foundational services to their latest version. The operator also upgrades the installer version to 3.6.x.

3. Post-upgrade

Verify the upgrade by completing these steps:

Check whether the cp-console and cp-proxy routes exist in the ibm-common-services namespace by running the following command:

oc get route -n ibm-common-services

If the cp-proxy route is missing, you might see an Application not available error and be unable to access a IBM Cloud Pak® application. To add the missing route, delete the cp-console route. This action causes the ibm-management-ingress-operator to re-create both routes. To delete the cp-console route, run the following command:

oc delete route cp-console -n ibm-common-services

After the routes are re-created, you can access your IBM Cloud Pak® application.

Upgrade IBM Cloud Pak foundational services to 3.12 or later versions

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
   

   Notes:

   • 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.
   • The variable ${CASE_ARCHIVE} needs to be set with the case bundle associated with the IBM Cloud Pak foundational services version. For example, to upgrade to IBM Cloud Pak foundational services 3.18.0, run the command export CASE_ARCHIVE=ibm-cp-common-services-1.14.0.tgz. To upgrade to IBM Cloud Pak foundational services 3.14.2, run the command export CASE_ARCHIVE=ibm-cp-common-services-1.10.2.tgz.

Troubleshooting

If you encounter any issues during your upgrade, review the frequently encountered errors to help you troubleshoot your issue. For more information, see Troubleshooting IBM Cloud Pak foundational services install and upgrade.