Multi-Attach error for volume "pvc-xxxx". Volume is already exclusively attached to one node and can't be attached

[JnMik]

Hey guys !

Describe the feature

We've all probably ever see this error message, when an ASG is refreshing instances, but the pod is not able to respawn on the new instance because it's volume seems to be stuck in a state attached to the previous machine. Well, this can be fixed by manually finding the PVCID and deleting the kubernetes volumeattachments corresponding, or simply wait for a couple minutes that feels like forever.

I was thinking, wouldn't it be nice if aws-node-termination-handler handles that ? Or is it supposed to be handling it already ?

Or is there another automated way that I am not aware of ?

Cheers