search
Ctrlk

PerconaDB pod Being in "CrashLoopBackOff" State

hashtag
Problem

  • Cluster details seem to be 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.

hashtag
Environment

  • Self-Hosted Private Cloud Director Virtualisation – v2025.4 [ONLY]

  • Component: Percona

hashtag
Cause

The PVC for PerconaDB has reached its current 6Gi limit; increasing the storage is necessary to ensure smooth operation. An enhancement request PCD-2365 was created to fix this in the next release.

hashtag
Resolution

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

hashtag
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

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

PreviousMultiple Instance Creation Failed Due to Max Scheduling Attempts Exceeded for Cinder VolumeNextPerconaDB Pods are Restarting Frequently due to OOMKilled Errors

Last updated