General known issues
This topic describes the general service-wide known issues for Cloudera Data Warehouse (CDW) Private Cloud.
Known Issues identified in 1.5.0
- FreeIPA is not supported
- Cloudera does not support FreeIPA as a certified identity management system for CDW data service on CDP Private Cloud 1.5.0.
- DWX-18903: Service "postgres-service-default-warehouse" is invalid: spec.externalName error
- You see the following error during the Database Catalog creation
stage after activating the environment in CDW:
Service "postgres-service-default-warehouse" is invalid: spec.externalName a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')
. This could happen because if the value of the Hive Metastore Database Host (hive_metastore_database_host) property on the base cluster is not specified in lowercase.
Known Issues identified in 1.4.1
- DWX-13759: DAS server and DAS WebApp pods exists even after disabling DAS
- After you disable DAS from the Advanced Settings page, you may still see the DAS server and DAS WebApp pods running in the Database Catalog and Virtual Warehouse namespaces respectively.
Known Issues identified before 1.4.1
- 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-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.