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.
- 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.
- 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.
-
- 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.
-
- 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.
-
- 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 java.net.ConnectException: Unsupported ciphersuite TLS_EDH_RSA_WITH_3DES_EDE_CBC_SHA
-
- 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:https://username:password@archive.cloudera.com/p/cm7/patch/7.7.1-h4-39235984/redhat8/yum
https://username:password@archive.cloudera.com/p/cm7/patch/7.7.1-h4-39235984/redhat8/yum/cloudera-manager.repo
RHEL 7 Compatible Repository:
Repository File:https://username:password@archive.cloudera.com/p/cm7/patch/7.7.1-h4-39235984/redhat7/yum
https://username:password@archive.cloudera.com/p/cm7/patch/7.7.1-h4-39235984/redhat7/yum/cloudera-manager.repo
SLES 12 Repository:
Repository File:https://username:password@archive.cloudera.com/p/cm7/patch/7.7.1-h4-39235984/sles12/yum
https://username:password@archive.cloudera.com/p/cm7/patch/7.7.1-h4-39235984/sles12/yum/cloudera-manager.repo
Ubuntu 20 Repository:
Repository file:https://username:password@archive.cloudera.com/p/cm7/patch/7.7.1-h4-39235984/ubuntu2004/apt
https://username:password@archive.cloudera.com/p/cm7/patch/7.7.1-h4-39235984/ubuntu2004/apt/cloudera-manager.list
Ubuntu 18 Repository:
Repository file:https://username:password@archive.cloudera.com/p/cm7/patch/7.7.1-h4-39235984/ubuntu1804/apt
https://username:password@archive.cloudera.com/p/cm7/patch/7.7.1-h4-39235984/ubuntu1804/apt/cloudera-manager.list
IBM PowerPC RHEL 8 https://username:password@archive.cloudera.com/p/cm7/patch/7.7.1-h4-39235984/redhat8-ppc/yum
IBM PowerPC RHEL 7 https://username:password@archive.cloudera.com/p/cm7/patch/7.7.1-h4-39235984/redhat7-ppc/yum