Known Issues in Azure environments
Learn about the known issues in Cloudera Data Warehouse service in Azure environments, the impact or changes to the functionality, and the workaround.
- Changed environment credentials not propagated to CDW AKS
Problem: When you change the credentials of a running cloud environment using Cloudbreak, the changes are not automatically propagated to the corresponding active Cloudera Data Warehouse (CDW) environment. As a result, CDW Azure Kubernetes Service (AKS) uses old credentials and may not function as expected resulting in inaccessible Hive or Impala Virtual Warehouses.
Workaround: To resolve this issue, you must manually synchronize the changes with the CDW AKS resources. To synchronize the updated credentials, see Update AKS cluster with new service principal credentials in the Azure product documentation.
- DWX-4356: For Azure environments only, enabling Log Analytics with Azure Monitor causes CDW to stall in a pending state
- Problem: If the Log Analytics agent (
OMS-Agent-for-Linux) is enabled with Azure Monitor, it causes scheduling issues with CDW that in turn cause the Virtual Warehouse to stall in a pending state. For more information about Log Analytics in Azure, see the Azure documentation for Azure Monitor and the description of OMS-Agent-for-Linux in GitHub.
- Workaround: Do not enable the Log Analytics agent. If it has been enabled by accident, turn off monitoring, which should remove the agent. For information about how to turn off monitoring, see How to stop monitoring your Azure Kubernetes Service (AKS) with Azure Monitor for containers in the Azure documentation.