Fixed issues for Cloudera Data Services on premises Replication Manager

OPSAPS-68698: Replication command type is incorrectly reported for Ozone incremental replications

When you create an Ozone replication policy using “Incremental only” or “Incremental with fallback to full file listing” Listing types, sometimes the Ozone replication command type is incorrectly reported for different types of runs.

OPSAPS-69752: Bad Ozone service health causes replication failure

After you set the ozone.om.snapshot.load.native.lib property to false in the ozone-site.xml file, the incremental Ozone replication policies do not fail during the replication policy run.

DMX-4070: The Hive replication policy edit wizard allows you to change the source and destination clusters which is incorrect

When you click the Replication Policies > Actions > Edit option for a Hive replication policy, the Edit Replication Policy wizard no longer allows you to edit the source and target cluster details.

DMX-3323: Cloud credentials create, edit, and validate error responses are parsed incorrectly

The cloud credentials operation errors show the correct message on the Replication Manager UI.

DMX-3474: Error appears when you edit a Hive replication policy

When you click the Actions > Edit on the Replication Policies page for a Hive replication policy, a misleading policy does not exist error notification appears. This issue is fixed.

DMX-3704: The 'download-diagnostic-bundle' CDP CLI command fails with UNSUPPORTED_CM_API_VERSION error

For supported Cloudera Manager versions, you can download the diagnostic bundle for the replication policy jobs. For unsupported versions, a download link is provided for the diagnostic bundle Sometimes, the direct download operation returns ‘Unsupported CM API version error. This issue is fixed.

DMX-3375: Hive policy validation error handler fails with TypeError

During the Hive replication policy creation process, when the validate action failed, some errors were omitted. Now the validation errors appear with the correct messages which you can use to troubleshoot the errors.

DMX-3479: The Trackinginfo string is not set for OzoneReplicationResults

You can now view all the available replication results for all the job runs for an Ozone replication policy on the Replication Policies page. You can also view the copied data statistics if the statistics are available for Replication Manager to collect.

DMX-3603: Replication result errors are not shown on the Replication Manager UI

The Replication Manager UI shows the correct error messages if a replication policy report cannot be downloaded.

DMX-3720: Revisiting the source step resets values when editing a policy

When you edited a replication policy, some changes were lost during the source step. Now, the update request contains all the changed inputs.

DMX-3790: Improving network efficiency using cache static assets

The cache control HTTP headers are now set to cache static assets (which is rarely changed) for one year which increases network efficiency.

DMX-3393: JSON library to use for read operations

The latest JSON library improves the backend read performance which helps to list a large number of replication policies on the Replication Policies page.

DMX-3422: New error messages for diagnostic bundle failures

The latest error messages for the diagnostic bundle download operations provide a more comprehensive feedback about the reason for the failure.

DMX-3306: Improved status code when the request input is not acceptable

The response HTTP 400 Bad Request status code appears when the request content sent to the Replication Manager REST API is incorrect.

DMX-3642: Reduced the cutoff time for the policy listing operation

You can set the timeout limit which ensures that the Replication Manager lists all the replication policies on the unreachable and unresponsive clusters during the policy listing operation. The results from the responsive clusters are retrieved faster, and the policies from the slow responding clusters are retrieved in the background. Therefore, the page shows all the retrieved replication policies after you refresh the Replication Policies page.

DMX-4186: Queue names with character '.' was rejected

Replication Manager could not use the specified YARN queue for a replication policy if the hierarchical queue name had a child queue that was referenced as parent-queue.child-queue. This issue is fixed.

DMX-4038: Remediated Netty CVE for Replication Manager

Upgraded to com.amazonaws.aws-java-sdk:1.12.780 and com.fasterxml.jackson.module.jackson-module-scala:2.17.2 to fix CVE-2024-29025 and CVE-2024-47535.

DMX-4099: Upgraded logback-core in Replication Manager to resolve CVE-2024-12798

Upgraded to ch.qos.logback.logback-classic:1.5.16 to fix CVE-2024-12798.

DMX-4142: Upgraded netty-handler in Replication Manager to resolve CVE-2025-24970

Upgraded to io.netty.netty-handler:4.1.118.Final to fix CVE-2025-24970.

DMX-4005: Upgraded protobuf-java library to fix CVE-2024-7254

Upgraded to com.google.protobuf.protobuf-java:3.25.5 to fix CVE-2024-7254.