Hello, I am using standard way for creating persistent volume and claims. And I use these as mounts for deployments.
And this works. But sporadically, pod goes into ContainerCreating state with error message: Unable to mount volumes for pod "mo-es-client-deployment-867101036-asbfk_mo-system(371736a3-9544-11e6-97c7-06dd1c3e4225)": timeout expired waiting for volumes to attach/mount for pod "mo-es-client-deployment-867101036-asbfk"/"mo-system". list of unattached/unmounted volumes=[storage] Even an attempt to delete and recreate the deployment with the same EBS vlumes fails. It seems that the EBS volumes are not getting released (let's say when the pod or minion terminated or recreated) from the minion to which those were attached initially. Please refer this troubleshooting guide by AWS - https://aws.amazon.com/premiumsupport/knowledge-center/ebs-stuck-attaching/ It seems that “block device driver of the EC2 instance” is not releasing “device name” which was given to secondary EBS. If my understanding is correct then k8s deployments with persistent volume on AWS cannot be relied on. Am I doing something wrong? What care should I take so that the persistent volume should not get unmounted from the cluster (as the minion may come and go) at first place; and if it is still gets unmounted then it's really free for tilization again. Best Regards, Manoj -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
