Known issues

This section lists known issues that you might run into while using the CDP Private Cloud Management Console service.

CLI and SDKs are not supported in the current release

Problem: CLI and SDKs are not supported in the current CDP Private Cloud release.

Workaround: Use the Management Console user interface instead to perform your tasks.

The error message indicating an invalid storage class name when registering an environment pops up only once

Problem: When you try registering an environment multiple times after specifying an invalid storage class name, the corresponding error message popup window displays only after the first attempt and not after every attempt to register the environment.

Workaround:
  • Validate the storage class name that you specify when registering the environment. This is also part of the pre-installation checklist.
  • If you do not see the error message popup window or if the environment registration fails, then validate the class name on the OpenShift container deployment.

Environment registration is possible without specifying a storage class name or without configuring a default storage class

Problem: Management Console allows you to register an environment without providing a storage class, even if no default storage class is configured on the OpenShift cluster. Therefore, the scheduling does not work on the pods when the environment is created.

Workaround: When registering an environment, you must ensure that you have either provided a valid storage class, or that a default storage class is configured on the OpenShift cluster. Otherwise, you must register the environment again by providing the correct configuration details.

Cannot delete an environment when the registration of the compute cluster fails

Problem: If the CA certificates that you upload for the external database or vault are incorrect, when you attempt to register an environment, the registration succeeds but the corresponding compute cluster is not created. Deleting the environment then fails with the message "Compute cluster deregistration failed with error."

Workaround: Upload the correct CA certificates from the Administration tab of the Management Console, and then delete the environment.

Management Console allows registration of two environments of the same name

Problem: If two users attempt to register environments of the same name at the same time, this might result in an unusable environment.

Workaround: Delete the environment and ensure that only one user attempts to register a new environment.

Environment creation might fail when Ozone is present in the cluster and is in a degraded state

Problem: When trying to create an environment on a Private Cloud deployment with Ozone configured for storing logs, and if the cluster is in a degraded state, the process of creation might occasionally fail.

Workaround: When trying to create the environment, stop Ozone temporarily on the Private Cloud base cluster. This prevents Management Console from using Ozone as a logging destination.

Kerberos service does not always handle Cloudera Manager downtime

Problem: The Cloudera Manager Server in the base cluster must be running to generate Kerberos principals for CDP Private Cloud. If there is downtime, you might observe Kerberos-related errors.

Workaround: Resolve downtime issues on Cloudera Manager. If you encounter Kerberos errors, you can retry the concerned operation such as creating Virtual Warehouses.

Configuring PagerDuty or webhook alert receivers fails with an incorrect response message if the endpoint URL is inaccessible

Problem: When configuring PagerDuty or webhook alert receivers, if the endpoint URL is not accessible, the user interface incorrectly prefixes the failure response message with an 'Unknown Error' statement.

Workaround: There is currently no workaround for the issue.

Updating or creating alert receivers does not always result in success notifications

Problem: Management Console does not always display messages indicating the success of updating or creating alert receivers.

Workaround: There is currently no workaround for the issue.

The alert-admin logs are flooded with error messages during control plane upgrade

Problem: When upgrading the control plane services, the alert-admin logs are flooded with error messages.

Workaround: There is currently no workaround for the issue.

The upgrade process of the monitoring platform is not retried after two unsuccessful attempts

Problem: The upgrade process of the monitoring platform is not retried after two unsuccessful attempts.

Workaround:
  1. Ensure that you fix the root cause of the upgrade failure.
  2. Delete the monitoring-platform-upgrade config map from the Management Console workspace.
  3. Restart the monitoring-pvcservice pod within the Management Console namespace.

User role changes are reflected in the monitoring components after a delay of about 10 minutes

Problem: CDP Private Cloud monitoring components (such as Dashboard, Grafana, Alerts settings and so on) cache the user's authorization role. If there is a role change, there could be a 10-minute time delay until the monitoring components reflect the change.

Workaround: After a role change, wait for about 10 minutes at the most for the change to be propagated across the monitoring components.

A CDP Private Cloud instance might not display the status of a data lake that is also used in another instance

Problem: If multiple CDP Private Cloud instances are installed with the same data lake and there are two environments with the same name, one of the CDP instances might not display the data lake status.

Additionally, creating a new environment that shares its name with another environment that was manually deleted might also lead to the data lake status being not displayed.

Workaround: Create an environment with a different name.