Volume cannot be attached to the node
Event FailedAttachVolume, often a volume still attached elsewhere.
ImpactThe pod stays in ContainerCreating
Can it be seen coming?No
RupturaCovered
How to detect it
Event reason FailedAttachVolume.
Metrics and signals to watch:
Kubernetes event FailedAttachVolume
Can you see it coming?
No This failure arrives without a reliable warning sign, so the goal is to detect it fast and explain it.
What it hits next
callers of the workload.
What to do
Detach the volume from the old node or fix the storage driver.
Sources
- Kubernetes event reason FailedAttachVolume
Where Ruptura stands
Ruptura reports this failure as the startup_stuck failure mode. A pre-registered lab test is not published yet.
Related failures
- Image cannot be pulled
- Image name is not valid
- Volume cannot be mounted
- Pod cannot be scheduled
- Pod sandbox cannot be created
See it coming instead of reading about it
Ruptura is an open-source operator for Kubernetes and OpenShift that predicts the failures in this catalog that can be predicted, detects the others, and sends them to Alertmanager. Watch an OOM crash predicted 21 minutes early · ★ GitHub
Ruptura is an open-source operator for Kubernetes and OpenShift that predicts the failures in this catalog that can be predicted, detects the others, and sends them to Alertmanager. Watch an OOM crash predicted 21 minutes early · ★ GitHub