Cloudera Manager 7.7.1 Cumulative hotfix 6

Know more about the Cloudera Manager 7.7.1 cumulative hotfixes 6.

This cumulative hotfix was released on April 13, 2023.

Following are the list of known issues and their corresponding workarounds that are shipped for Cloudera Manager 7.7.1 CHF6 (version: 7.7.1-h4-39235984):
OPSAPS-68689: Unable to emit the LDAP Bind password in core-site.xml for client configurations

If the CDP cluster has LDAP group to OS group mapping enabled, then applications running in Spark or Yarn would fail to authenticate to the LDAP server when trying to use the LDAP bind account during the LDAP group search.

This is because the LDAP bind password was not passed to the /etc/hadoop/conf/core-site.xml file. This was intended behavior to prevent leaking the LDAP bind password in a clear text field.

Set the LDAP Bind password through the HDFS client configuration safety valve.
  1. On the Cloudera Manager UI, navigate to the HDFS service, by clicking on the HDFS service under the Cluster.
  2. Click the Configuration tab. Search for the HDFS Client Advanced Configuration Snippet (Safety Valve) for hdfs-site.xml configuration parameter.

  3. Add an entry with the following values:
    • Name =
    • Value = (Enter the LDAP bind password here)
    • Description = Password for LDAP bind account
  4. Then click the Save Changes button to save the safety valve entry.

  5. Perform the instructions from the Manually Redeploying Client Configuration Files to manually deploy client configuration files to the cluster.

OPSAPS-68452: Azul Open JDK 8 and 11 are not supported with Cloudera Manager

Azul Open JDK 8 and 11 are not supported with Cloudera Manager. To use Azul Open JDK 8 or 11 for Cloudera Manager RPM/DEBs, you must manually create a symlink between the Zulu JDK installation path and the default JDK path.

After installing Azul Open JDK8 or 11, you must run the following commands on all the hosts in the cluster:
Azul Open JDK 8
# sudo ln -s /usr/lib/jvm/java-8-zulu-openjdk-jdk /usr/lib/jvm/java-8-openjdk
Ubuntu or Debian
# sudo ln -s /usr/lib/jvm/zulu-8-amd64 /usr/lib/jvm/java-8-openjdk
Azul Open JDK 11
For DEBs only
# sudo ln -s /usr/lib/jvm/zulu-11-amd64 /usr/lib/jvm/java-11
Following are the list of fixes that were shipped for Cloudera Manager 7.7.1 CHF6 (version: 7.7.1-h4-39235984):
  • OPSAPS-63558
    Previously, DistCp did not correctly report renames and deletes in case of snapshot diff-based HDFS replications. This change extends DistCp's output report to contain counters related to snapshot diff-based replications beside the already reported counters. These counters are added to the following group: com.cloudera.enterprise.distcp.DistCpSyncCounter.
    The following new counters are added:
    • FILES_MOVED_TO_COMMON_TEMP_DIR: Number of files and directories moved to a common temporary directory to be renamed or deleted later in the process. This counter is the sum of FILES_DELETED_VIA_COMMON_TEMP_DIR and FILES_RENAMED_VIA_COMMON_TEMP_DIR.
    • FILES_DELETED_VIA_COMMON_TEMP_DIR: Number of files moved to a common temporary directory to be deleted later.
    • FILES_RENAMED_VIA_COMMON_TEMP_DIR: Number of files moved to a common temporary directory first, then moved to their final place.
    • FILES_DIRECT_DELETED: Number of files deleted directly. This is a feature introduced in OPSAPS-63759.
    • FILES_DIRECT_RENAMED: Number of files renamed directly, without moving to an intermediate temporary directory. This is a feature introduced in OPSAPS-63930.
    • FILES_DIRECT_RENAMED_VIA_TEMP_LOCATION: Number of files moved to an intermediate temporary directory and then renamed. This intermediate temporary directory is different from the common temporary directory referenced in the FILES_RENAMED_VIA_COMMON_TEMP_DIR counter's description. This is also related to OPSAPS-63930.
    The common temporary directory is a sibling of the replication target directory.
    The values of FILES_DELETED_VIA_COMMON_TEMP_DIR and FILES_DIRECT_DELETED are also aggregated in the replication result as the number of files deleted.
  • OPSAPS-65131
    When you enter incorrect volume or bucket details in an Ozone replication policy, an error appears and you are logged out of Cloudera Manager. This issue is fixed.
    When you enter incorrect volume or bucket details, an error appears and you are not logged out of Cloudera Manager.
  • OPSAPS-66023: Error message about an unsupported ciphersuite while upgrading or installing cluster with the latest FIPS compliance

    When upgrading or installing a FIPS enabled cluster, Cloudera Manager is unable to download the new CDP parcel from the Cloudera parcel archive.

    Cloudera Manager displays the following error message:

    HTTP ERROR 400 Unsupported ciphersuite TLS_EDH_RSA_WITH_3DES_EDE_CBC_SHA

    This issue is fixed now by correcting the incorrect ciphersuite selection.
  • OPSAPS-66107
    Avoiding unnecessary Resource Manager scheduled refresh in Global Pools Refresh command. During Autoscaling in the public cloud, the scheduled Global Pools refresh command was causing conflicts with the Resource Manager refresh command that is triggered by commission and decommission commands of Yarn service (which caused Autoscale failures as the Resource Manager refresh command was not available). This issue is fixed now.
  • The repositories for Cloudera Manager 7.7.1-CHF6 are listed in the following table:

    Table 1. Cloudera Manager 7.7.1-CHF6
    Repository Type Repository Location
    RHEL 8 Compatible Repository:
    Repository File:
    RHEL 7 Compatible Repository:
    Repository File:
    SLES 12 Repository:
    Repository File:
    Ubuntu 20 Repository:
    Repository file:
    Ubuntu 18 Repository:
    Repository file:
    IBM PowerPC RHEL 8
    IBM PowerPC RHEL 7