Why is CDH 5.4 not set as the latest parcels at http://archive.cloudera.com/cdh5/parcels/latest/ ?

[#1]

Looking at http://archive.cloudera.com/cdh5/parcels/latest/ it still holds CDH 5.3.   When will it change to CDH 5.4?  I can point directly at the CDH 5.4 parcels via http://archive.cloudera.com/cdh5/parcels/5.4/  but wanted to know if there was reason why the latest archive is not hosting the CDH 5.4 parcels?

[#2 · Accepted solution]

Shailesh, here is a draft of an upcoming KB we are working on that explains the change in behavior of why we are no longer linking latest to the latest version of CDH.    The primary reason for the change is to prevent admins from accidentally upgrading to a version of CDH higher than CM which the CM version may not support.

Symptoms: The CDH 5.4 parcel is not visible or downloadable in Cloudera Manager versions lower than CM 5.4.0.

Applies to: All versions of Cloudera Manager <5.4.0

Cause: To reinforce the documented requirement and Best Practice to maintain the Cloudera Manager version at or higher than the cluster CDH version, using Cloudera Manager versions lower than 5.4.0 will cause the Parcel management page not to find - or display for download/distribution - any CDH parcels higher than 5.3.x when the configured remote parcel repository URL is the configured default http://archive.cloudera.com/cdh5/parcels/latest.

This is not a defect of archive.cloudera.com symlinks or the Cloudera Manager product, but rather is intended to protect from upgrading to a version of CDH that cannot be properly deployed, activated and managed.

Administrators may be accustomed to the /latest parcel repository URL continually tracking the latest dot-release of CDH. As of CDH 5.3.x, the /latest endpoint on archive.cloudera.com is frozen and will not track beyond the latest release of CDH 5.3.x.

As a replacement for this symlink-based solution, Cloudera Manager versions 5.4 and above will negotiate the highest-supported CDH version permissible to download and activate with that specific deployment version of Cloudera Manager. This facilitates remaining within support matrix software combinations.

Instructions: If you wish to install CDH 5.4.0 or higher, you must upgrade Cloudera Manager to version 5.4.0 or higher first.

To simplify this transition away from a /latest symlink mechanism, CM 5.4 and higher make use of a Remote Parcel Repository URL configuration variable that lets the Cloudera Manager Server negotiate and determine the Highest-Supported CDH version using this {latest_supported} variable. If you upgrade to Cloudera Manager 5.4.0 or higher and wish to see all supported CDH parcel versions, ensure your parcel settings for Report Parcel Repository URLs contains a property similar to the following (assuming your cluster can contact archive.cloudera.com😞

http://archive.cloudera.com/cdh5/parcels/{latest_supported}

If you host CDH parcels in an internal repository adapt the URL to point to your properly-populated Parcel Repository.

[#3]

I recently upgraded CM to 5.10.0. Trying to upgrade CDH from the Manager from 5.8.0 throws up the same issue. I cannot see or select the CDH. Attached is a screenshot. Any help in figuring out next steps to get this running will help.