Fixed Issues in Cloudera Manager 7.11.3 Cumulative hotfix 6 for Data Services 1.5.4

Fixed issues in Cloudera Manager 7.11.3 CHF6 (version: 7.11.3.9-53216725) for Data Services 1.5.4 release.

OPSAPS-70207: Cloudera Manager Agents sending the Impala profile data with an incorrect header: Fixed an issue where Impala query profile data was not visible in Cloudera Observability with Cloudera Manager Agents running on Python 3. This was caused by Cloudera Manager Agents sending the profile data with an incorrect Content-Type in the HTTP header. Telemetry Publisher responded to the issue with incorrect Content-Type stopping the data flow. The issue was fixed by correcting the Content-Type header. No further action is required.
OPSAPS-65460: The current RetryWrapper implementation does not work as expected when the transient database error appears: Hive replication policies no longer fail with the javax.persistence.OptimisticLockException error on the source cluster during the Hive export step.
OPSAPS-60832: Decommissioning process for HDFS DataNodes is not completed in Cloudera Manager: This issue has been fixed by renewing the Kerberos ticket, which addresses Kerberos expiration issues during the DataNode decommissioning process.
OPSAPS-68418: Partition missing during column statistics import operation: A data-race issue found during the Hive metadata export step during the Hive external table replication policy run has been fixed so that concurrent modifications made to the partitions during the export operation does not result in import failure.
OPSAPS-70079: NPE appears during the directory creation process in the Isilon clusters because the sourceRoleForKerberos value is null: After you configure the Dell EMC Isilon clusters, you must ensure that you configure the following options on the Cloudera Manager > Administration > Settings page:

Custom Kerberos Keytab Location (to be used for replication for secure clusters on this Cloudera Manager)

Custom Kerberos Principal Name (to be used for replication for secure clusters on this Cloudera Manager); tip
Use the configured Custom Kerberos Principal Name value in the Run As Username field during the replication policy creation process when using Isilon storage clusters. For more information, see How to resolve replication policies that fail with the “Custom keytab configuration is required for this service” error.