Troubleshooting problems in the Cloud Pak for Data platform

If you encounter an issue in the Cloud Pak for Data platform, you can use the following information to resolve the problem.

Cannot log in to the web client
You get an error when you try to log in to the Cloud Pak for Data web client.
Cannot load the list of services or provision service instances from the web client
If a zen-metastoredb pod is not running, you might not be able to access the Services catalog page or provision service instances from the web client.
Cannot create or edit users
You get an error when you attempt to create a new users or edit or delete an existing user from the Manage users page.
The option to enforce quotas is not available
If you install the scheduling service after you install the Cloud Pak for Data control plane, the Enforce quotas option is not enabled for the platform or for individual services.
Cluster imbalance overwhelms worker nodes
An imbalance of resource allocation across the cluster can cause single worker nodes to be overwhelmed.
Worker nodes show status of disk pressure
On IBM® Cloud, you might notice that pods consume more local storage and worker nodes show a status of disk pressure.
File storage on persistent volume not available
When you install IBM Cloud Pak for Data with IBM Cloud File Storage (ibmc-file-gold-gid storage class) on IBM Cloud, the persistent volume is created with the minimum storage as specified by the installer. This minimum amount might not be enough storage for all applications.
Requests time out when you upload or download files from volumes
If you are working with large files, you might encounter errors when you try to upload or download the files from storage volumes.
Recovering access to projects
When a user creates a project, they are automatically added to the project as an Administrator. If the user leaves the company without adding another user as an Administrator, you cannot complete tasks such as managing project collaborators, removing assets from projects, and stopping all active runtimes.
Troubleshooting global search when Elasticsearch pods are not ready
The global search pods might not be ready due to problems with Elasticsearch pods.

Parent topic: Troubleshooting problems in Cloud Pak for Data