Upgrade-related known issues

Known issues identified in 1.5.5

DWX-20916: Refresh, Rebuild, and Update are disabled on pre-upgrade DBC and Virtual Warehouses: The Refresh, Rebuild, and Update operations have been disabled on DBC and Virtual Warehouse (VW) instances created before the upgrade from Cloudera Data Warehouse on premises 1.5.4 SP1 and earlier versions. This change was made to prevent service failures that previously occurred when these operations were executed.; Such failures included container errors and startup issues in Hue Query Processor and other Hue-related pods, caused by permission and directory-related problems.; Upgrade the affected DBC or Virtual Warehouse to complete the runtime upgrade. This resolves compatibility issues and allows services to function as expected.

No new known issues identified in 1.5.5

DWX-19327: Unable to upgrade the Cloudera Data Visualization instance: If you are upgrading your Cloudera Data Visualization instance from Cloudera Data Warehouseon premises 1.5.4 or earlier versions to Cloudera Data Warehouse on premises 1.5.4 SP1, the upgrade fails with a “Failed to acquire lease” error.
This issue occurs because of a missing vizCRN from some of the older Cloudera Data Visualization application objects.; Create a new Cloudera Data Visualization instance. For more information, see Deploying Cloudera Data Visualization instance in Cloudera Data Warehouse.
note
If you do not want to create a new instance, contact Cloudera support for further assistance.

DWX-18447: Virtual Warehouses go into an erroneous state after upgrading the Cloudera Control Plane: After upgrading the Cloudera Control Plane to Cloudera Data Services on premises 1.5.4, you may see that the Virtual Warehouse creation fails with the following error:
huefrontend-5888cc97b8-fxpx5 pod in compute-1716270252-fzfj namespace has an erroneous container, state: waiting, reason: RunContainerError, message: context deadline exceeded Error Code : undefined
When you run the kubectl describe command on the pod, you see the following warning:
Error: failed to create containerd task: failed to create shim task: OCI runtime create failed: runc create failed: unable to create new parent process: namespace path: lstat /proc/0/ns/ipc: no such file or directory: unknown; None. The Virtual Warehouse transitions back into the running or stopped state after the pod has initialized successfully.