Fixed issues in Ozone

Review the list of Ozone issues that are resolved in Cloudera Runtime 7.1.7.

CDPD-15268: Support for S3 Multipart upload on encrypted buckets. To use this feature buckets need to be created in s3v volume using ozone shell with encryption key.
This issue is resolved.
OPSAPS-61133: Enabling GRPC TLS for Ozone causes issues starting up SCM in upgraded clusters (7.1.6 -> 7.1.7).
Disable GRPC TLS by default in Ozone. This issue is resolved.
OPSAPS-60996:Ozone decommisioning was fixed by correctly assigning rack names.
This issue is resolved.
OPSAPS-60484: Select 3 SCM nodes by default while adding ozone as a service in Cloudera Manager has been merged successfully.
This issue is resolved.
OPSAPS-60410: Added two configurationss that is ozone.fs.trash.interval and ozone.fs.trash.checkpoints.interval to Cloudera Manager. You can now configure Ozone filesystem trash interval and checkpoint interval from Cloudera Manager. These configurations are populated into ozone-site.xml.
Added Ozone Filesystem Trash configurations to Cloudera Manager. This issue is resolved.
OPSAPS-60366: Handle Ozone Datanode Decommissioning with SCM-HA CM changes. As per the current CM code, SCM is handled for a single node, it must handle 3 nodes.
This issue is resolved.