Cloudera Docs

Cumulative hotfix CDP PvC Base 7.1.8.45-2 (Cumulative hotfix13)

Know more about the cumulative hotfix 13 for 7.1.8. This cumulative hotfix was released on August 18, 2023.

Following are the list of fixes that were shipped for CDP Private Cloud Base version 7.1.8-1.cdh7.1.8.p45.44120957

  • COMPX-14851: Backport YARN-11545 (FS2CS not converts ACLs when all users are allowed)
  • CDPD-60137: Backport IMPALA-12319 to 7.1.8 CHF
  • CDPD-60016: Backport CDPD-59245 to 718 CHFx
  • CDPD-59358: Backport CDPD-59091 to 7.1.8 CHF
  • CDPD-59128: OM crash and unable to start due to quota violation
  • CDPD-55860: Missing gunicorn_log.conf file in /etc/hue/conf folder
  • CDPD-55430: Missing DEBUG logging in Py3 Hue
  • CDPD-48893: Implement Logger Role
  • CDPD-41691: Custom Header
Table 1. Cloudera Runtime 7.1.8.45 (Cumulative Hotfix 13) download URL:
Parcel Repository Location 
https://[username]:[password]@archive.cloudera.com/p/cdh7/7.1.8.45/parcels/

Technical Service Bulletin

TSB 2024-775: FileNotFoundException for Ozone Filesystem JAR during or after CDP installation or upgrade
A potential availability issue has been found with services that have an Ozone client dependency on the ozone-filesystem-hadoop3 fat JAR file when upgrading the Cloudera Data Platform (CDP) Private Cloud Base cluster from version 7.1.8 to 7.1.9. This issue may also affect service installations, runs, and restarts during or after the CDP Private Cloud Base installation or upgrade.
The following exception appears on the Cloudera Manager User Interface (UI) or in the log files of the respective service when an installation, upgrade or other operations fail due to this issue: `java.io.FileNotFoundException: /path/to/ozone-filesystem-hadoop3-<version>.jar (No such file or directory).
The failure is caused by the broken symbolic link: /var/lib/hadoop-hdfs/ozone-filesystem-hadoop3.jar. This issue arises if the hdfs user already exists on the node before the Cloudera Runtime parcel activation. When the hdfs user already exists on the node, the Cloudera Manager agent skips the initialization related to Hadoop Distributed File System (HDFS), which includes creating the /var/lib/hadoop-hdfs directory. As the path is not created, the symbolic link cannot be created during the parcel activation process. This results in a series of broken symbolic links that point to the Ozone binaries.
Knowledge article
For the latest update on this issue see the corresponding Knowledge Article: TSB 2024-775: FileNotFoundException for the Ozone FS JAR during or after installation or upgrade