General known issues
This topic describes the general platform-wide known issues for Cloudera Data Warehouse (CDW) Private Cloud.
- OPSAPS-58019: “SERVICE_PRINCIPAL is required for kinit” error while activating a new environment
- If the
/etc/krb5.conf
file on the Cloudera Manager host contains "include" or "includedir" directives, then you may encounter Kerberos-related failures on both Embedded Container Service and Red Hat OpenShift platforms. You may see the following error in the Database Catalog's metastore pod logs: SERVICE_PRINCIPAL is required for kinit. - DWX-10403: Executor pods get stuck in pending state with a warning
- In rare circumstances, when Impala or Hive executors start up either due to autoscaling or by manually restarting the executors, the pods may get stuck in a pending state with a warning such as "volume node affinity conflict". This happens due to a race condition in the storage class that provides local volumes.
- DWX-8525 and DWX-8526: CDW does not support upgrades from CDW 1.2 to 1.3.2
- You may encounter issues while creating a new Virtual Warehouse on an existing Database Catalog (version 1.2) in an environment that is upgraded from 1.2 to 1.3.1.
- DWX-8502: HMS health check does not check port 9083
- The HMS health check script does not check the health of its service port 9083 and may provide incorrect health status.
- DOCS-7431: LDAP limitations in CDW Private Cloud Virtual Warehouses
- CDW Private Cloud workloads in Hive, Impala, Hue, and Data Analytics Studio (DAS) use simple bind authentication without filters. However, Management Console control plane uses search bind.
- DWX-5496: If Cloudera Manager truststore or the external database/vault is updated, CDW environment activation fails
- Problem:If you have activated environments in CDW Private Cloud 1.1
and you update the Cloudera Manager truststore or the external database/vault truststore,
you must update all of your CDW Private Cloud components else environment activation fails
in CDW Private Cloud 1.1.
For example, you might perform truststore updates for the following use cases:
- To rotate the database certificate.
- To add a new CA certificate for a secure connection to an external vault.
- To rotate the Cloudera Manager certificate.
For information about these tasks, see Updating TLS certificates in the Management Console documentation set.