SOLO-5084

PvcMountVerificationFailedSoloError

Description

Thrown when PVC mount verification finds that a pod’s PersistentVolumeClaim mounts are not backed by the storage the claims requested, and verification was configured to fail rather than warn. Provisioners that hand out directories on an existing filesystem do not enforce the requested size, so this condition is invisible to Kubernetes: the claim binds, the pod runs, and the shortfall only surfaces later as a full disk. The usual cause is that the directory tree the provisioner writes into is not the mount point it was meant to be — a data array that failed to mount at boot leaves the path on the system disk instead.

Troubleshooting Steps

1. Check what the claims bound to and how large they really are: kubectl get pvc,pv -n
2. Identify the provisioner and the host directory it writes into: kubectl get storageclass -o yaml
3. On the node, confirm that directory is on the intended device and not the system disk: df -h ; lsblk; findmnt
4. If an intended data array or disk failed to mount at boot, mount it and redeploy so the claims are provisioned onto it
5. To deploy anyway and only warn, omit –verify-pvc-mounts