Update from 1.3.3 to 1.3.4
You can update your existing CDP Private Cloud Data Services 1.3.3 to 1.3.4 without requiring an uninstall.
In Cloudera Manager, navigate to CDP Private Cloud Data Services 1.3.3 and
click . Click
On the Getting Started page, you can select the Install
method - Air Gapped or Internet
Internet install method
Air Gapped install method
On the Collect Information page, click
On the Install Parcels page, click
On the Update Progress page, you can see the
progress of your update. Click Continue after
the update is complete .
If you encounter an error message in the Upgrade Cluster Command output, during the Execute command Install Tolerations Webhook on service ECS-3 step that mentions a failure waiting for kube-proxy to come up, do the following:
- Log in using ssh to one of the ECS Server nodes and run
the following command:
The output will look similar to the following:
/var/lib/rancher/rke2/bin/kubectl get nodes
If any of the version numbers in the last column are lower than the expected version, reboot those nodes. (For example,
NAME STATUS ROLES AGE VERSION ecs-abc-1.vpc.myco.com Ready control-plane,etcd,master 4h50m v1.21.8+rke2r2 ecs-abc-2.vpc.myco.com NotReady <none> 4h48m v1.20.8+rke2r1 ecs-abc-3.vpc.myco.com Ready <none> 4h48m v1.21.8+rke2r2 ecs-abc-4.vpc.myco.com NotReady <none> 4h48m v1.20.8+rke2r1 ecs-abc-5.vpc.myco.com NotReady <none> 4h48m v1.20.8+rke2r1
v1.20.8in the output above.)
- In the Command Output window, in the step that failed, click Resume.
- Log in using ssh to one of the ECS Server nodes and run the following command:
After the update is complete, the Summary
page appears. You can now Launch CDP Private
Cloud from here.
If you see a Longhorn Health Test message about a degraded Longhorn volume, wait for the cluster repair to complete.
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.