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
LivenessandReadinessprobe failures. - PerconaDB in
CrashLoopBackOffstate.
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.
- 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- Ensure the modified PVC size is reflected in the PVCs.
x
Beforeregion-1 datadir-percona-db-pxc-db-pxc-0 Bound pvc-[..] 6Gi RWO pcd-sc <unset> 32dregion-1 datadir-percona-db-pxc-db-pxc-1 Bound pvc-[..] 6Gi RWO pcd-sc <unset> 32dregion-1 datadir-percona-db-pxc-db-pxc-2 Bound pvc-[..] 6Gi RWO pcd-sc <unset> 32d Afterregion-1 datadir-percona-db-pxc-db-pxc-0 Bound pvc-[..] 300Gi RWO pcd-sc <unset> 32dregion-1 datadir-percona-db-pxc-db-pxc-1 Bound pvc-[..] 300Gi RWO pcd-sc <unset> 32dregion-1 datadir-percona-db-pxc-db-pxc-2 Bound pvc-[..] 300Gi RWO pcd-sc <unset> 32dAdditional 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.
Was this page helpful?