Upgrade from 1.5.1 or 1.5.2 to 1.5.3 (OCP)

You can upgrade your existing CDP Private Cloud Data Services 1.5.1 or 1.5.2 to 1.5.3 without performing an uninstall. After the update is complete, you may need to upgrade the underlying OpenShift Container Platform. See the Software Support Matrix for OpenShift for more information about supported OCP versions.

If you are upgrading the OCP version to 4.10.x or higher, while the CDE service is enabled, it fails to launch the Jobs page in the old CDE virtual cluster. Hence, you must back up CDE jobs in the CDE virtual cluster, and then delete the CDE service and CDE virtual cluster. Restore it after the upgrade. For more information about backup and restore CDE jobs, see Backing up and restoring CDE jobs.

Review the Software Support Matrix for OpenShift.
Make a backup of the OpenShift routes before upgrading to 1.5.3.

Ensure that you have the following before you upgrade:

A kubeconfig file for the OCP cluster
Ensure that the kubeconfig file has permissions to create Kubernetes namespaces.
Back up all the external databases used by CDP Private Cloud Data Services.
One or more environments registered in CDP Private Cloud Data Services.
One of the registered environment has one or more Cloudera Data Warehouse (CDW) or Cloudera Machine Learning (CML) experience workspaces.
Access to the Cloudera Private Cloud repositories (archive.cloudera.com)
Administrator access to OCP and Privileged access to your external Vault

In Cloudera Manager, navigate to CDP Private Cloud Data Services and click . Click Update.
On the Getting Started page, you can select the Install method - Air Gapped or Internet and proceed.

Internet install method

Air Gapped install method

Click Continue.
On the Collect Information page, upload a Kubernetes configuration (kubeconfig) file from your existing environment. You can obtain this file from your OpenShift Container Platform administrator. Click Continue.
On the Update Progress page, you can see the progress of your update. Click Continue.
important
During the "Upgrade Control Plane" step of the CDP upgrade process, the grafana pod can get stuck in the terminating sate. This usually means that all other Control Plane pods are in the running state, but for Grafana, there is one pod that is in running state and there is one pod that is stuck in terminating state. The terminating pod has the following message:
containers with incomplete status: [multilog-init grafana-sc-datasources]
If you search for the terminating pod id in the kubelet log on the host, the following error message can be found:
E0531 2209 kuberuntime_sandbox.go:70] CreatePodSandbox for pod "<pod id>" failed: rpc error: code = Unknown desc = error reading container (probably exited) json message: EOF
If there is a granfa pod stuck in terminating state, run the following command on the ECS Server host:
<grafana-pod-id> --force --grace-period=0
After the update is complete, the Summary page appears. You can now Launch CDP Private Cloud from here.

Or you can navigate to the CDP Private Cloud Data Services page and click Open CDP Private Cloud Data Services.

CDP Private Cloud Data Services opens up in a new window.
After the update is complete, delete the old CDE service and the underlying virtual cluters. You may also need to upgrade the underlying OpenShift Container Platform. See the Software Support Matrix for OpenShift for more information about supported OCP versions.