Known issues for the CDP Private Cloud Data Services Management Console
This section lists known issues that you might run into while using the CDP Private Cloud Management Console service.
- Cloudera Manager 7.6.1 is not compatible with CDP Private Cloud Data Servicesversion 1.3.4.
- You must use Cloudera Manager version 7.5.5 with this release.
- COMPX-9980: YuniKorn upgrade fails when upgrading CDP Private Cloud Data Services from version 1.3.2 to 1.3.4
- See the Troubleshooting section on this page: Update from 1.3.2 to 1.3.4
- OPSAPS-63458: Longhorn Health Test reports degraded volume after upgrade
- If you see a Longhorn Health Test message about a degraded Longhorn volume, wait for the cluster repair to complete.
- OPSAPS-63460: Failure waiting for kube-proxy to come up during ECS upgrade
- See steps 5a and 5b in this document: Update from 1.3.3 to 1.3.4
- Recover fast in case of a Node failures with ECS HA
- When a node is deleted from cloud or made unavailable, it is observed that it takes more than two minutes until the pods were rescheduled on another node.
- It takes some time for the nodes to recover. Failure detection and pod-transitioning are not instantaneous.
- OPSX-2713: CDP Private Cloud Data Services ECS Installation: Failed to perform First Run of services.
- If an issue is encountered during the Install Control Plane step of Containerized Cluster First Run, installation will be re-attempted infinitely rather than the command failing.
- Workaround: Since the control plane is installed and uninstalled in a continuous cycle, it is often possible to address the cause of the failure while the command is still running, at which point the next attempted installation should succeed. If this is not successful, abort the First Run command, delete the Containerized Cluster, address the cause of the failure, and retry from the beginning of the Add Cluster wizard. Any nodes that are re-used must be cleaned before re-attempting installation.
- OPSX-1412: Environment creation through the CDP CLI fails when the base cluster includes Ozone
- Problem: Attempt to create an environment using the CDP command-line interface fails in a CDP Private Cloud Data Services deployment when the Private Cloud Base cluster is in a degraded state and includes Ozone service.
- Workaround: Stopping the Ozone service temporarily in the Private Cloud Base cluster during environment creation prevents the control plane from using Ozone as a logging destination, and avoids this issue.
- OPSX-2484: Filtering the diagnostic data by time range might result in a FileAlreadyExistsException
- Problem:Filtering the collected diagnostic data might result in a FileAlreadyExistsException if the /tmp directory already contains a file by that name.
- There is currently no workaround for this issue.
- OPSX-2680: Full cluster name does not display in the Register Environment Wizard
- OPSX-735: 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.
- Resolve downtime issues on Cloudera Manager. If you encounter Kerberos errors, you can retry the concerned operation such as creating Virtual Warehouses.
- OPSX-1405: 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.
- Delete the environment and ensure that only one user attempts to register a new environment.
- OPSX-2697: Not all images are pushed during upgrade
- A retry of a failed upgrade intermittently fails at the Copy Images to Docker Registry step due to images not being found locally.
- The failed images can be loaded manually (with a docker load), and the upgrade resumed. To identify which images need to be loaded take a look at the stderr file. The downloaded images are present in the Docker Data Directory.
- OPSX-2062: The Environments page on the Management Console UI for an environment in a deployment using ECS does not display the platform name
- Problem: When you view the details of an environment using the Management Console UI in a CDP Private Cloud Data Services deployment using ECS, the Platform field appears blank.
- Use the relevant CDP CLI command from
environmentsmodule to view the required details.
- OPSX-2772: Updating user roles for the admin user does not update privileges
- In the Management Console, changing roles on the User Management page does not change privileges of the admin user.
- OPSX-2698: Upgrade applies values that cannot be patched
- If the size of a persistent volume claim in a Containerized Cluster is manually modified, subsequent upgrades of the cluster will fail.
- : Incorrect warning about stale Kerberos client configurations
If Cloudera Manager is configured to manage krb5.conf, ECS clusters may display a warning that they have stale Kerberos client configurations. Clicking on the warning may show an "Access denied" error.
- No action is needed. ECS clusters do not require Kerberos client configurations to be deployed on those hosts.
- CDPVC-753: Vault becomes sealed
- If a host in an ECS cluster fails or restarts, the Vault may have become sealed. (You may see a Health Test alert in Cloudera Manager for the ECS service stating Vault instance is sealed.)
- Unseal the Vault. In the Cloudera Manager Admin Console, go to the ECS service and click .