Cloudera Docs

Cloudera Manager 7.13.1 Release Notes

This document provides a summary of the latest updates in Cloudera Manager 7.13.1 and its Cumulative hotfixes. You can review the Release Notes of Cloudera Manager 7.13.1 associated with unified Cloudera Runtime 7.3.1 (includes Cloudera Base on premises and Cloudera on cloud) for release-specific information related to new features and improvements, bug fixes, deprecated features and components, known issues, and changed features that can affect product behavior.

Repository Package differences across Cloudera Manager Cumulative Hotfixes (CHFs)

When reviewing direct file listings for Cloudera Manager Cumulative Hotfix (CHF) repositories (for example, comparing version 7.13.1.700 (CHF 7) to 7.13.1.900 (CHF 9)), specific RPM packages present in an earlier CHF repository might not appear in a later CHF repository.

Common examples of packages removed from later builds include:

  • cloudera-manager-support-cdh6-7.13.1.700-*.el8.x86_64.rpm

  • openjdk8-8.0+372_1-cloudera.x86_64.rpm

This repository package variation is expected behavior in Cloudera Manager. The absence of these packages in later patch builds does not indicate repository corruption, incomplete mirror synchronizations, or broken dependencies.

Why Packages differ between CHF releases

  • Package consolidation and restructuring: Cloudera periodically repackages legacy support tools (such as cloudera-manager-support-cdh6) or integrates them directly into core components (cloudera-manager-daemons or cloudera-manager-agent). Later standalone patch listings exclude any sub-package that requires no updates or is superseded by newer components.

  • Runtime dependency decoupling: Cloudera unbundles standalone Java RPMs (such as openjdk8) in later patch builds when the release relies on system-provided OpenJDK or managed JDK paths rather than bundling a dedicated RPM payload in every hotfix build.

  • Cumulative minimal distribution: Cloudera repository builds deliver active delta binaries required for specific build levels to optimize and reduce the overall repository footprint.

Impact and required action

  • No manual action required: Standard package managers (yum / dnf) resolve active dependencies automatically during yum update cloudera-manager-server cloudera-manager-agent.

  • Standard upgrade path: Point your repository configuration (.repo file) to the target CHF URL (for example, cm7/7.13.1.900) and proceed with the standard upgrade workflow.