Hemant Kumar
Hemant Kumar
/remove-lifecycle rotten I can still see this error. Results in following error: ``` 2022-10-05T17:19:38.949683736Z vanilla/controller.go:567 failed to create volume. Error: failed to create volume with fault: "(*types.LocalizedMethodFault)(0xc0005d9820)({\n DynamicData: (types.DynamicData) {\n...
/reopen /remove-lifecycle rotten
@Quentin-M when Kubernetes can not detach the volume - is the volume still mounted on the node? It sounds like this could be a problem somewhere in EBS stack rather...
Why do you have to force detach the volume if it is not mounted on the node? a normal detach should do the job. Can you post output of `ls...
So it appears that - although EC2 thinks volume is attached on the node, but when you login to the node - you can't see the disk? The disk is...
I think the issue happens when volume is stuck in detaching state on one instance and then it eventually detaches and if attaches somewhere else, the device does not show...
issue @jsafrane created in k/k repo has summary of discussion so far - https://github.com/kubernetes/kubernetes/issues/94929
/remove-lifecycle stale
/unassign /assign @humblec
But `GetCapacityResponse` is a controller call, without attaching the volume somewhere it may be tough for storageProvider to say how much is available capacity. For example - I don't recall...