You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
create a deployment which uses csi-s3 to provision filesystem PV
then shutdown the node ltaucenw8ridob54 which hosts the first pod nginx-deployment-7d94b7b565-2rrqr
after a while, the pod nginx-deployment-7d94b7b565-2rrqr goes to Terminating state, a new pod is launched on another node xalp9fb32t4idmcz. This is expected behavior
then start node ltaucenw8ridob54, I am expecting the terminating pod nginx-deployment-7d94b7b565-2rrqr should be removing automatically in short time. But it stays Terminating state even after 2 hours. The csi-s3 log as below
Root cause
I think it is because the origin pod mount path disappear, so the umount command fails which blocks NodeUnpublishVolume process. CSI need to implement some error handling here
The text was updated successfully, but these errors were encountered:
MingZhang-YBPS
changed the title
Shutdown node and wait some minutes to start it again, the pod using csi-s3 stucks in Terminating state
[Bug] Shutdown node and wait some minutes to start it again, the pod using csi-s3 stucks in Terminating state
Dec 18, 2024
MingZhang-YBPS
changed the title
[Bug] Shutdown node and wait some minutes to start it again, the pod using csi-s3 stucks in Terminating state
[Bug] Shutdown node and wait some minutes to start it again, the pod stucks in Terminating state
Dec 18, 2024
Steps to reproduce
Root cause
I think it is because the origin pod mount path disappear, so the umount command fails which blocks NodeUnpublishVolume process. CSI need to implement some error handling here
The text was updated successfully, but these errors were encountered: