Cumulative hotfix CDP PvC Base 7.1.8.46-1 (Cumulative hotfix14)

Know more about the cumulative hotfix 14 for 7.1.8. This cumulative hotfix was released on September 7, 2023.

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

CDPD-60781: SMM UI fails to start on Ubuntu 18 & SLES12
CDPD-60680: Backport IMPALA-11195 to 7.1.8 CHF
CDPD-60625: Backport SPARK-40617 into Spark2
CDPD-60221: Backport CDPD-59692 to CDH 7.1.x
CDPD-60120: [7.1.8 CLONE] Addressing Vulnerability Type:HTTP Security Header Not Detected only for default HTTPS Port 8484 of RMS
CDPD-59903: [Backport 7.1.8 CHFx] Use unofficial node build with glibc 2.17 on centos7
CDPD-59730: Backport IMPALA-11557 and IMPALA-11558 to CDH-7.1.8.x

Table 1. Cloudera Runtime 7.1.8.46 (Cumulative Hotfix 14) download URL:
Parcel Repository Location
`https://[username]:[password]@archive.cloudera.com/p/cdh7/7.1.8.46/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