Update from 1.3.4 or 1.4.0-H1 to 1.4.1 (OCP)

You can update your existing CDP Private Cloud Data Services 1.3.4 or 1.4.0-H1 to 1.4.1 without requiring an uninstall. After the update is complete, you can then upgrade the underlying OpenShift Container Platform to 4.7.x or 4.8.x.

If you are upgrading the OCP version, while the CDE service is enabled, it can cause database corruption in the embedded MySQL database used for CDE. Hence, only if you are using CDE Data Services, you must perform certain additional steps before starting the OCP version upgrade. Otherwise, you can directly update your CDP Private Cloud Data Services.

Ensure that you have the following before you update:

Ensure that this kubeconfig has permissions to create Kubernetes namespaces.
Back up all the external databases used by CDP Private Cloud Data Services.
CDP Private Cloud Base 7.1.8 or 7.1.7 SP1 with a Data Lake cluster.
Cloudera Manager 7.8.1
Single instance of CDP Private Cloud Data Services 1.3.4 or 1.4.1 installed on your OCP cluster.
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.
Kubeconfig file for the OCP 4.7 or 4.8 cluster
Access to the Cloudera Private Cloud repositories (archive.cloudera.com)
Administrator access to OCP 4.7 or 4.8 and Privileged access to your external Vault
note
There is no direct upgrade from 1.0, 1.1, 1.2, 1.3.1, or 1.3.2 to 1.4.1.

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, upgrade the underlying OpenShift Container Platform from 4.5.x or 4.6.x to 4.7.x or 4.8.x.