Known Issues in Cloudera Manager 7.7.3

Known issues in Cloudera Manager 7.7.3

Cloudera bug: OPSAPS-66235 Diagnostic bundle missing host statistics
Diagnostic bundles do not include host statistics. The following error message displays in the command output: Collect Host Statistics sub-command has failed.
None
Cloudera bug: OPSAPS-65243 Diagnostic data collection for YARN fails
Selecting Collect Diagnostic Data from the YARN > Applications page fails to generate the diagnostic data.
None
Cloudera bug: OPSAPS-65269 Hosts report no heartbeat after upgrading to Cloudera Manager 7.7.3 and then rolling back to Cloudera Manager 7.7.1.
After upgrading Cloudera Manager 7.7.1 to 7.7.3 and then rolling back to 7.7.1 Cloudera Manager may report no heartbeat from one or more hosts and also reports bad health for services.
Reboot the hosts.
Cloudera bug: OPSAPS-65189: Accessing Cloudera Manager through Knox displays the following error:

Bad Message 431 reason: Request Header Fields Too Large

Workaround: Modify the Cloudera Manager Server configuration /etc/default/cloudera-scm-server file to increase the header size from 8 KB, which is the default value, to 65 KB in the Java options as shown below:
export CMF_JAVA_OPTS="...existing options...
-Dcom.cloudera.server.cmf.WebServerImpl.HTTP_HEADER_SIZE_BYTES=65536
-Dcom.cloudera.server.cmf.WebServerImpl.HTTPS_HEADER_SIZE_BYTES=65536"
OPSAPS-65213: Ending the maintenance mode for a commissioned host with either an Ozone DataNode role or a Kafka Broker role running on it, might result in an error.

You may see the following error if you end the maintenance mode for Ozone and Kafka services from Cloudera Manager when the roles are not decommissioned on the host.

Execute command Recommission and Start on service OZONE-1
Failed to execute command Recommission and Start on service OZONE-1
Recommission and Start
Command Recommission and Start is not currently available for execution.
To resolve this issue, use the API support feature to take the host out of maintenance mode.
  1. Log into Cloudera Manager as an Administrator.
  2. Go to Hosts > All Hosts.
  3. Select the host for which you need to end the maintenance mode from the available list and click the link to open the host details page.
  4. Copy the Host ID from the Details section.
  5. Go to Support > API Explorer.
  6. Locate and click the /hosts/{hostId}/commands/exitMaintenanceMode endpoint for HostsResource API to view the API parameters.
  7. Click Try it out.
  8. Enter the ID of your host in the hostId field.
  9. Click Execute.
  10. Verify that the maintenance mode status is cleared for the host by checking the Server response code.

    The operation is successful if the API response code is 200.

If you need any guidance during this process, contact Cloudera support for further assistance.