Known Issues in Cloudera Manager 7.10.1

OPSAPS-68558: Cloudera Manager upgrade fails with the following error:There are 1 active commands of type GetClientConfigFiles

After upgrading from Cloudera Manager 7.9.5 to 7.11.3.0 version, the Cloudera Manager server does not start. Cloudera Manager server log displays an error about active commands. This scenario might occur when the Private Cloud Data Service Control Plane is actively issuing requests to Cloudera Manager while performing an upgrade.

Before Cloudera Manager upgrade make sure there are no active commands such as getClientConfig. If there are any active commands, then allow them to complete before kicking off the Cloudera Manager upgrade process.

Post upgrade, inspect the Cloudera Manager server log for the following error message: There are 1 active commands of type GetClientConfigFiles. This error might block Cloudera Manager to restart after the upgrade process. If Cloudera Manager restart fails due to the presence of active getClientConfig command, then to resolve this issue, perform the following steps:

Login to Cloudera Manager database.

Search for any active GetClientConfigFiles command in COMMANDS table.

SELECT NAME, ACTIVE  , COMMAND_ID FROM COMMANDS WHERE ACTIVE <> 0 AND NAME='GetClientConfigFiles';

Update the entry for the command_id found in step 2.

UPDATE COMMANDS SET active=0,success=false,state='CANCELLED' where command_id=<command_id>;

Restart the Cloudera Manager server by running the following command:
```
sudo systemctl restart cloudera-scm-server
```

OPSAPS-67152: Cloudera Manager does not allow you to update some configuration parameters.

Cloudera Manager does not allow you to set to "0" for the dfs_access_time_precision and dfs_namenode_accesstime_precision configuration parameters.

You will not be able to update dfs_access_time_precision and dfs_namenode_accesstime_precision to "0". If you try to enter "0" in these configuration input fields, then the field gets cleared off and results in a validation error: This field is required.

To fix this issue, perform the workaround steps as mentioned in the KB article.

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

OPSAPS-67213: The log files are hitting 403 error.

Accessing the process logs from the command page returns a 403 error: HTTP ERROR 403 Received fatal alert: internal_error The server declined access to the page or resource.

Refreshing the page returns the relevant output.

OPSX-2713: ECS Installation: Failed to perform First Run of services.

If an issue is encountered during the Install Control Plane step of Containerized Cluster First Run, installation will be re-attempted infinitely rather than the command failing.

Since the control plane is installed and uninstalled in a continuous cycle, it is often possible to address the cause of the failure while the command is still running, at which point the next attempted installation should succeed. If this is not successful, abort the First Run command, delete the Containerized Cluster, address the cause of the failure, and retry from the beginning of the Add Cluster wizard. Any nodes that are re-used must be cleaned before re-attempting installation.

OPSX-735: Kerberos service should handle Cloudera Manager downtime

The Cloudera Manager Server in the base cluster must be running in order to generate Kerberos principals for Private Cloud. If there is downtime, you may observe Kerberos-related errors.

Resolve downtime on Cloudera Manager. If you encounter Kerberos errors, you can retry the operation (such as retrying creation of the Virtual Warehouse).

OPSAPS-68629: HDFS HTTPFS GateWay is not able to start with custom krb5.conf location set in Cloudera Manager.

On a cluster with a custom krb5.conf file location configured in Cloudera Manager, HDFS HTTPFS role is not able to start because it does not have the custom Kerberos configuration file setting properly propagated to the service, and therefore it fails with a Kerberos related exception:

in thread "main"
          java.io.IOException: Unable to initialize WebAppContext at
          org.apache.hadoop.http.HttpServer2.start(HttpServer2.java:1240) at
          org.apache.hadoop.fs.http.server.HttpFSServerWebServer.start(HttpFSServerWebServer.java:131)
          at org.apache.hadoop.fs.http.server.HttpFSServerWebServer.main(HttpFSServerWebServer.java:162)
          Caused by: java.lang.IllegalArgumentException: Can't get Kerberos realm at
          org.apache.hadoop.security.HadoopKerberosName.setConfiguration(HadoopKerberosName.java:71) at
          org.apache.hadoop.security.UserGroupInformation.initialize(UserGroupInformation.java:329) at
          org.apache.hadoop.security.UserGroupInformation.setConfiguration(UserGroupInformation.java:380)
          at
          org.apache.hadoop.lib.service.hadoop.FileSystemAccessService.init(FileSystemAccessService.java:166)
          at org.apache.hadoop.lib.server.BaseService.init(BaseService.java:71) at
          org.apache.hadoop.lib.server.Server.initServices(Server.java:581) at
          org.apache.hadoop.lib.server.Server.init(Server.java:377) at
          org.apache.hadoop.fs.http.server.HttpFSServerWebApp.init(HttpFSServerWebApp.java:100) at
          org.apache.hadoop.lib.servlet.ServerWebApp.contextInitialized(ServerWebApp.java:158) at
          org.eclipse.jetty.server.handler.ContextHandler.callContextInitialized(ContextHandler.java:1073)
          at
          org.eclipse.jetty.servlet.ServletContextHandler.callContextInitialized(ServletContextHandler.java:572)
          at
          org.eclipse.jetty.server.handler.ContextHandler.contextInitialized(ContextHandler.java:1002)
          at org.eclipse.jetty.servlet.ServletHandler.initialize(ServletHandler.java:765) at
          org.eclipse.jetty.servlet.ServletContextHandler.startContext(ServletContextHandler.java:379)
          at org.eclipse.jetty.webapp.WebAppContext.startWebapp(WebAppContext.java:1449) at
          org.eclipse.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1414) at
          org.eclipse.jetty.server.handler.ContextHandler.doStart(ContextHandler.java:916) at
          org.eclipse.jetty.servlet.ServletContextHandler.doStart(ServletContextHandler.java:288) at
          org.eclipse.jetty.webapp.WebAppContext.doStart(WebAppContext.java:524) at
          org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73) at
          org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169) at
          org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:117) at
          org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97) at
          org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73) at
          org.eclipse.jetty.util.component.ContainerLifeCycle.start(ContainerLifeCycle.java:169) at
          org.eclipse.jetty.server.Server.start(Server.java:423) at
          org.eclipse.jetty.util.component.ContainerLifeCycle.doStart(ContainerLifeCycle.java:110) at
          org.eclipse.jetty.server.handler.AbstractHandler.doStart(AbstractHandler.java:97) at
          org.eclipse.jetty.server.Server.doStart(Server.java:387) at
          org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:73) at
          org.apache.hadoop.http.HttpServer2.start(HttpServer2.java:1218) ... 2 more Caused by:
          java.lang.IllegalArgumentException: KrbException: Cannot locate default realm at
          java.security.jgss/javax.security.auth.kerberos.KerberosPrincipal.<init>(KerberosPrincipal.java:174)
          at
          org.apache.hadoop.security.authentication.util.KerberosUtil.getDefaultRealm(KerberosUtil.java:108)
          at org.apache.hadoop.security.HadoopKerberosName.setConfiguration(HadoopKerberosName.java:69)
          ...

Log in to Cloudera Manager.
Select the HDFS service.
Select Configurations tab.
Search for HttpFS Environment Advanced Configuration Snippet (Safety Valve)
Add to or extend the HADOOP_OPTS environment variable with the following value: -Djava.security.krb5.conf=<the custom krb5.conf location>
Click Save Changes.