"pod has unbound immediate PersistentVolumeClaims" for helm charts(redis, mysql, postgresql) #3869
Labels
area/storage
storage bugs
kind/bug
Categorizes issue or PR as related to a bug.
priority/awaiting-more-evidence
Lowest priority. Possibly useful, but not yet enough support to actually get it done.
triage/needs-information
Indicates an issue needs more information in order to work on it.
Comments
|
This sounds bad. I haven't had a chance to sort out the reproduction steps for it yet however. To my knowledge, nothing has changed with PVC's recently. https://stackoverflow.com/questions/54923806/why-do-i-get-unbound-immediate-persistentvolumeclaims-on-minikube has some steps which might be helpful. Do you mind looking through it to see if there are any hints which may help uncover the root cause? |
tstromberg
added
kind/bug
|
Hi, I revisited simple config files that I have before(worked fine before). I did change the pvc config accessMode to ReadWriteMany and retry too, following https://stackoverflow.com/questions/54923806/why-do-i-get-unbound-immediate-persistentvolumeclaims-on-minikube. pvc.yaml: service.yaml: deployment.yaml: Gave me same error, "pod has unbound immediate PersistentVolumeClaims" when i did kubectl apply -f . The pv and pvc seems initiated just fine, and the storageClass also seems configured properly. Then I tried to remove just deployment.yaml(kubectl delete -f deployments.yaml) and do kubectl apply -f deployment.yaml. Still to no avail. minikube logs: I used to be able to use redis, mysql, and postgresql helm charts just fine. So first I suspect it was something to do with my minikube config, but further read through forums and reinstalling, seems like the minikube config just fine. I still having hard time to figure out the root cause, more help appreciated. Thank you. |
|
Update: steps:
minikube logs: I'm not sure why I got some of these error from minikube logs: kube-scheduler: I've been trying to find solution for this from things I can find from internet, still not able to make it work until now. |
|
+1, same issue on mac os |
|
Steps to reproduce:
Workaround: |
|
+1 jenkinsx install after prev install deleted |
|
seems the trick is just to wait..... it goes away... eventually.. dependencies |
|
The issue resolved itself, I don't know what changed. But now it worked as expected, no such error anymore. |
|
I can reproduce this when using the postgres helm chart |
|
Still having this issue while trying to deploy MinIO. Changing the YAML to say ReadWriteMany instead of ReadWriteOnce does not fix the problem. |
pranav-patil
referenced
this issue
in pranav-patil/spring-kubernetes-microservices
Sep 2, 2019
|
I see this error in minishift, changing from ReadWriteOnce to ReadWriteMany fixed the problem for me. |
|
Im still having the same issue as #3869 (comment), changing access mode to |
|
Can this issue be re-opened or is there a need for a new issue? |
|
I have previously run the elasticsearch operator quickstart on minikube without issue. I upgraded minikube and deleted my old hyperkit based minikube server. Running through ES quickstart gave me this exact same error. I've since changed the version of kubernetes in minikube via |
|
I'm encountering the same issue with redis-ha from helm/charts, with minikube 1.9.0, and kubectl version v1.18.0. Do I need to raise a new issue here for this? |
|
Getting the same error when trying to install rabbitmq from bitnami's chart. Using minikube 1.9.2 and kubectl 1.18.0. |
|
same issue with minikube 1.9.2 and latest elasticsearch operator |
I hit the exact same problem. And, am a first timer to Minikube and ECK. Your post helped me to revert back to older kubernetes version and then the ECK/elasticsearch cluster got running. Thanks a lot for posting. |
|
any update on it? |
|
Same here. incubator/solr |
|
Can you execute |
|
I'm having the same issue attempting to create a dynamic PVC in Argo Workflows on minikube (Kubernetes 1.18.x). Reverting to Kubernetes 1.16 solved the problem, so there seems to be an issue with 1.18 on minikube. |
|
My $0.02: After kicking the addon: Not guaranteed to work for everyone. But worked for me. |
|
changing from ReadWriteOnce to ReadWriteMany fixed the problem for me. |
|
Hi guys I run elasticsearch helm in m1 mac docker desktop kubernetes I fix this promblem ... 제 상황설명좀 할게요 SO ,, there is value.yaml file like https://github.com/elastic/helm-charts/blob/master/elasticsearch/values.yaml podSecurityPolicy: and i fix create to true Finally, i can successfully reach my own data (remaining PVC volume) and get back my kibana dashboard.. So i don't know this is right way but try it if you when uninstall helm ( didn't delete PVC volume) and re install same thing |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
Hi, I tried to do helm install stable/postgresql. but it gave me "pod has unbound immediate PersistentVolumeClaims" using minikube v0.35.0, worked just fine before on minikube v0.33(tried redis and mysql chart too, gave same error). I did reinstall minikube. Also, tried to start with fresh minikube. I don't understand where I'm doing it wrong. Many thanks for the help. Here are some details:
kubectl version:
minikube addons list:
minikube config view:
minikube logs:
kubectl get pv,pvc:
kubectl describe pv,pvc:
kubectl get all:
kubectl describe sc:
kubectl describe statefulset:
kubectl describe pods:
The text was updated successfully, but these errors were encountered: