简体   繁体   中英

Pods stuck containercreating

previously my MySQL pod stuck at terminating status, and then I tried to force delete using command like this

kubectl delete pods <pod> --grace-period=0 --force

Later I tried to helm upgrade again, my pod was stuck at containercreating status, and this event from pod

17s         Warning   FailedMount   pod/db-mysql-primary-0     MountVolume.SetUp failed for volume "pvc-f32a6f84-d897-4e35-9595-680302771c54" : kubernetes.io/csi: mount
er.SetUpAt failed to check for STAGE_UNSTAGE_VOLUME capability: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial unix
/var/lib/kubelet/plugins/dobs.csi.digitalocean.com/csi.sock: connect: no such file or directory"

17s         Warning   FailedMount   pod/db-mysql-secondary-0   MountVolume.SetUp failed for volume "pvc-61fc6eda-97fa-455f-ac2c-df8ebcb90f1c" : kubernetes.io/csi: mount
er.SetUpAt failed to check for STAGE_UNSTAGE_VOLUME capability: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial unix
/var/lib/kubelet/plugins/dobs.csi.digitalocean.com/csi.sock: connect: no such file or directory"

anyone please can help me to resolve this issue, thanks a lot.

When you run the command

kubectl delete pods <pod> --grace-period=0 --force

you ask kubernetes to forget the Pod, not to delete it. You have to be careful while using this command. You have to make sure that the containers of the Pod are not running in the host especially when they are mounted to a PVC. Probably the containers is still running and attached to the PVC.

pool-product-8jd40 0

spec: drivers: null

and on my some pool the driver csi not ready (null), it's supposed to be equal 1 (ready)

*sorry i can't attach the image yet

The technical post webpages of this site follow the CC BY-SA 4.0 protocol. If you need to reprint, please indicate the site URL or the original address.Any question please contact:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM