Cloudera Docs

Cloudera Manager 7.7.3 Cumulative hotfix 1

This Cloudera Manager 7.7.3 CHF1 lists the known issues that are affecting Cloudera Manager 7.7.3 and Cloudera Manager 7.7.3 CHF1 during installation or upgrade.

This cumulative hotfix was released on October 28, 2022.

Following known issues and their corresponding workarounds are shipped for Cloudera Manager 7.7.3 CHF1 (version: 7.7.3-33365545). For information about workarounds and long term resolutions, see KB article.
  • OPSAPS-65578 - Cloudera Manager 7.7.3 dependency on Python 2
  • OPSAPS-65557 - Cloudera Manager agent fails to upgrade when you upgrade Cloudera Manager server from version 7.7.1 to 7.7.3
  • OPSAPS-65589 - Cloudera Manager 7.7.3 is unable to start Apache Ranger and Apache Atlas services
  • OPSAPS-65443 - Apache Phoenix service does not start in Cloudera Data Platform (CDP) Private Cloud Base 7.1.8
  • OPSAPS-65623 - Cloudera Manager 7.7.3 does not detect Python 3.8 from Redhat 7 Software Collections (SCL) repository
  • OPSAPS-65648 - Data Analytics Studio, Query Processor, Key Trustee Server services do not start without Python 2

Additional Known issues related to Cloudera Manager 7.7.3 CHF1 (version: 7.7.3-33365545)

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
RHEL or SLES
# 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
OPSAPS-64153: Core Settings service is getting added twice during cluster provisioning using a cluster template.

None.

OPSAPS-64614: Cloudera Manager server fails to complete the upgrade and will not start, if a cluster had a legacy Core Configuration service with any number of Storage Operations roles.

Cloudera Manager upgrade fails with the following error: ERROR MainThread:com.cloudera.server.cmf.Main: Server failed.java.lang.IllegalStateException: Revision was already prepared

Upgrading Cloudera Manager might fail if Cloudera Manager is running the Core Configuration service and is managing a compute cluster.

Before upgrading Cloudera Manager, you must remove any Storage Operations roles from the Core Configuration service as follows:
  1. Log in to the Cloudera Manager server host.
  2. Run the following command to stop the Cloudera Manager Server.
    sudo systemctl stop cloudera-scm-server
  3. Open the CLI for the Cloudera Manager database using one of the following commands:
    • MySQL/MariaDB: mysql -u root -p
    • PostgreSQL: sudo -u postgres psql
    • Oracle: sqlplus system@localhost
  4. Run the following SQL queries:
    1. select ROLE_ID from ROLES where ROLE_TYPE='STORAGEOPERATIONS';
      The query returns a set of ROLD_ID values. For each ROLE_ID, run the following SQL commands:
      delete from CONFIGS where ROLE_ID=<ROLE_ID>;
delete from ROLE_STALENESS_STATUS where ROLE_ID=<ROLE_ID>;
delete from ROLES where ROLE_TYPE='STORAGEOPERATIONS';

The repositories for Cloudera Manager 7.7.3-CHF1 are listed in the following table:

Table 1. Cloudera Manager 7.7.3-CHF1
Repository Type Repository Location
RHEL 8 Compatible Repository:
https://username:password@archive.cloudera.com/p/cm7/7.7.3-33365545/redhat8/yum
Repository File:
https://username:password@archive.cloudera.com/p/cm7/7.7.3-33365545/redhat8/yum/cloudera-manager.repo
RHEL 7 Compatible Repository:
https://username:password@archive.cloudera.com/p/cm7/7.7.3-33365545/redhat7/yum
Repository File:
https://username:password@archive.cloudera.com/p/cm7/7.7.3-33365545/redhat7/yum/cloudera-manager.repo