PerconaDB pod Being in "CrashLoopBackOff" State

Problem

  • Cluster details seem missing via GUI.
  • The Neutron and Watcher-Api pods were in the error state due to Liveness and Readiness probe failures.
  • PerconaDB in CrashLoopBackOff state.

Environment

  • Self-Hosted Private Cloud Director Virtualisation – v2025.4 and Higher.

Cause

The PVC for PerconaDB has reached its current 6Gi limit; increasing the storage is necessary to ensure smooth operation.

Resolution

This issue is resolved in the Self-Hosted Private Cloud Director Virtualisation version- v2025.6 release.

Workaround

Update the PerconaDB persistent volume claim to use a minimum of 30Gi, rather than the default 6Gi.

To make these changes, proceed as follows:

Make sure storage class must support volume expansion.
  1. Update the PVCs for all the PerconaDB pods
Command on Master Node
Copy
  1. Ensure the modified PVC size is reflected in the PVCs.
Command On Master node
Copy

Additional Information

An internal Jira PCD-2365 has been filed to track this issue. For more details, kindly reach out to the Platform9 Support Team mentioning in the Jira ID.

Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard
Next to read:
PerconaDB Pods are Restarting Frequently due to OOMKilled Errors
On This Page
PerconaDB pod Being in "CrashLoopBackOff" StateProblemEnvironmentCauseResolutionWorkaroundAdditional Information