Known issues in Cloudera Data Warehouse

Known issues identified in the March 31, 2026 release

DWX-22295: Default Database Catalog or Hive Virtual Warehouse creation fails on Azure due to Istio validation webhook error

On Azure-based Cloudera Data Warehouse environments, default Database Catalog creation or Hive Virtual Warehouse deployment can intermittently fail during chart installation. The deployment driver is unable to install certain Helm charts such as, postgres-external, metastore, or Hive-related charts because calls to the Istio validation webhook (validation.istio.io on istiod.istio-system.svc:443) return a 500 Internal Server Error. When this occurs, the affected Database Catalog or Hive Virtual Warehouse deployment enters an error state and does not become available for use. This behavior has only been observed on Azure and is linked to transient Istio networking issues.

None

DWX-23148: Environment deactivation might fail if EKS cluster update is in progress

When deactivating a Cloudera Data Warehouse environment on AWS, the operation might fail with an error indicating that the CloudFormation stack was unable to delete the EKS cluster due to an update in progress. This issue affects environments configured with both public and private executors. The failure is temporary and typically resolves once the EKS cluster update is complete.

None

Known issues identified before the March 31, 2026 release

DWX-20712: Environment diagnostic bundle collection failure

If you are collecting diagnostic bundles for AWS or Azure environments with a time range of more than 3 hours, the diagnotsic bundle collection job fails. This issue is noticed if the data to be collected is greater than 5 GB.

None.

Known limitation: Cloudera Data Warehouse does not support S3 Express One Zone buckets

Cloudera does not recommend deploying the Data Lake on S3 Express One Zone buckets. Cloudera Data Warehouse cannot read content present in the S3 Express One Zone buckets. The following limitations apply when using S3 Express buckets:

• You can only use S3 Express buckets with Cloudera Data Hubs running Runtime 7.2.18 or newer. Data services do not support it, currently.
• S3 Express buckets may not be used for logs and backups.

DWX-15144: Virtual Warehouse naming restrictions

You cannot create a Virtual Warehouse having the same name as another Virtual Warehouse even if the like-named Virtual Warehouses are in different environments. You can create a Database Catalog having the same name as another Database Catalog if the Database Catalogs are in different environments.

None.

AWS availability zone inventory issue

In this release, you can select a preferred availability zone when you create a Virtual Warehouse; however, AWS might not be able to provide enough compute instances of the type that Cloudera Data Warehouse needs.

If you experience this AWS issue, try recreating the Virtual Warehouse and choosing a different availability zone.

Incorrect diagnostic bundle location

The path you see to the diagnostic bundle is wrong when you create a Virtual Warehouse, collect a diagnostic bundle of log files for troubleshooting, and click Edit > Diagnostic Bundle. Your storage account name is missing from the beginning of the path.

To find your diagnostic bundle, add your storage account name to the beginning of the path, for example:

my-storage-account-name/log-files/clusters/my-env/my-warehouse-xx-yy/warehouse/debug-artifacts/hive/compute-zz-mvvf/compute-zz-mvvf-0926210111-0927090111-01234.zip

To get your storage account name, in Cloudera Management Console, click Environments, select your environment, and scroll down to Logs Storage and Audits. The first part of the path is your storage account name.