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:

Warning

Make sure storage class must support volume expansion.

  1. Update the PVCs for all the PerconaDB pods

$ kubectl edit pvc datadir-percona-db-pxc-db-pxc-* ... spec: resources: requests: storage: 6Gi # Replace this value to 30Gi

  1. Ensure the modified PVC size is reflected in the PVCs.

Before region-1 datadir-percona-db-pxc-db-pxc-0 Bound pvc-[..] 6Gi RWO pcd-sc <unset> 32d region-1 datadir-percona-db-pxc-db-pxc-1 Bound pvc-[..] 6Gi RWO pcd-sc <unset> 32d region-1 datadir-percona-db-pxc-db-pxc-2 Bound pvc-[..] 6Gi RWO pcd-sc <unset> 32d After region-1 datadir-percona-db-pxc-db-pxc-0 Bound pvc-[..] 300Gi RWO pcd-sc <unset> 32d region-1 datadir-percona-db-pxc-db-pxc-1 Bound pvc-[..] 300Gi RWO pcd-sc <unset> 32d region-1 datadir-percona-db-pxc-db-pxc-2 Bound pvc-[..] 300Gi RWO pcd-sc <unset> 32d

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.

Next to read:
PerconaDB Pods are Restarting Frequently due to OOMKilled Errors
null
On This Page
PerconaDB pod Being in "CrashLoopBackOff" StateProblemEnvironmentCauseResolutionWorkaroundAdditional Information