Upgrading Cloudera Private Cloud Base to a higher version

An upgrade from Cloudera Private Cloud Base to a higher version of Cloudera Private Cloud Base has the following high-level workflow:

Prepare to upgrade:
1. Review the Supported Upgrade Paths for your upgrade.
2. Review the Requirements and Supported Versions for your upgrade
3. Review the Release Notes for the version of Cloudera Private Cloud Base you are upgrading to.
4. Review the CDP Upgrade/Migrate Troubleshooting Articles. These Cloudera Knowledge Base articles describe common issues encountered by Cloudera customers during upgrades and migrations. (Cloudera login required.)
5. Gather information on your deployment. See Step 1: Getting Started Upgrading Cloudera Manager 7 and Step 1: Getting Started Upgrading a Cluster.
6. Plan how and when to begin your upgrade.
If necessary, Upgrade the JDK.
If necessary, Upgrade the Operating System.
Upgrade Cloudera Manager to version 7.1.1 or higher. After upgrading to Cloudera Manager 7.1.1 or higher, Cloudera Manager can manage upgrading your cluster to a higher version. See Upgrading Cloudera Manager 7.
Use Cloudera Manager to upgrade from lower version of Cloudera Runtime to a higher version of Cloudera Runtime. See Upgrading a Cluster.

note

[Applicable on SLES 15 SP4 and Ubuntu 22] If you are upgrading to Cloudera 7.1.9 SP1, and using MySQL as a backend database for Hue, then you must install Python 3.10 and the MySQL Client before you upgrade Cloudera Manager and Cloudera Private Cloud Base. You must perform the upgrade tasks in the following order to avoid potential issues:

Install Python 3.10 on all Hue hosts.
Install the MySQL Client package.
Stop the Hue service.
Upgrade Cloudera Manager to CM 7.11.3 CHF7.
Start Cloudera Manager.
Upgrade Cloudera Private Cloud Base to 7.1.9 SP1.
Start the Hue service.

For detailed instructions about each step, see Upgrading CDP Private Cloud Base to a higher version.

important

[Applicable on RHEL 8.8 and RHEL 8.10]

Cloudera recommends you to install Python 3.9 before upgrading Cloudera Manager to Cloudera Manager 7.13.1 version to ensure smooth transition with minimal downtime. For information about migrating from Python 3.8 to Python 3.9, see Migrating from Python 3.8 to Python 3.9 on RHEL 8.8 or RHEl 8.10.

Install Python 3.9 before upgrading Cloudera Manager to Cloudera Manager 7.13.1 version to avoid performing a Cloudera Manager Agent restart later. If you install Python 3.9 after upgrading Cloudera Manager to Cloudera Manager 7.13.1 version, then you must perform Cloudera Manager Agent restart after installing Python 3.9.
Install Python 3.9 before upgrading Cloudera Runtime to Cloudera Runtime 7.3.1 version as Hue requires Python 3.9 and does not start until you install Python 3.9. If you want to upgrade Cloudera Runtime to Cloudera Runtime 7.3.1, then you must install Python 3.9 on all Hue servers before you upgrade Cloudera Runtime to Cloudera Runtime 7.3.1 version.