-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Minikube v0.21.0 hostPath PVCs do not bind (Pending forever). #1783
Comments
@bgehman I ran into the same issue, delete the default storageclass and recreating it fixed this.
|
Could you please run I ran into a similar issue and resolved it by explicitly defining the storage class in my pv definition.
|
@jacobfederer Defining the Minikube v0.20.0 (working)
Minikube v0.21.0 (broken -- with and without adding storageClassName standard to PV))
|
I figured it out. My kubectl client was backlevel at version Also, had to add the I guess devs can close this, or suggest upstream warning if client/server version mismatches if compatibility can't be guaranteed. Thanks for all that helped. |
I'm going to leave this open and tag it as something we should add some documentation for. |
Issues go stale after 90d of inactivity. Prevent issues from auto-closing with an If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale |
I'm facing this issue now.
minikube version: v0.25.0
kubectl version #=> Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.3", GitCommit:"d2835416544f298c919e2ead3be3d0864b52323b", GitTreeState:"clean", BuildDate:"2018-02-07T12:22:21Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"", Minor:"", GitVersion:"v1.9.0", GitCommit:"925c127ec6b946659ad0fd596fa959be43f0cc05", GitTreeState:"clean", BuildDate:"2018-01-26T19:04:38Z", GoVersion:"go1.9.1", Compiler:"gc", Platform:"linux/amd64"}
Docker version 18.02.0-ce, build fc4de44 |
/remove-lifecycle rotten |
@elgalu couple things to check:
Failure to bind hostPaths typically fall into one or both of those cases. |
kubectl version --short=true
#=> Client Version: v1.9.3
#=> Server Version: v1.9.0 |
I'm hitting this problem too, and my versions match exactly:
... this seems to be a general issue with pvcs since 0.21? |
... and, nuked the minikube vm, started everything over from scratch, and now it runs without the PVC issue. No changes to manifests. Clearly there's some other triggering condition here I don't know about. |
Same here, I moved away from the
|
I also meet this issue. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
VM: none
|
Chowning ~/.docker/config.json helped. |
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
BUG REPORT
Minikube version (use
minikube version
):minikube version: v0.21.0
Environment:
OS (e.g. from /etc/os-release):
Red Hat Enterprise Linux Workstation release 7.3 (Maipo)
VM Driver (e.g.
cat ~/.minikube/machines/minikube/config.json | grep DriverName
):kvm
ISO version (e.g.
cat ~/.minikube/machines/minikube/config.json | grep -i ISO
orminikube ssh cat /etc/VERSION
):minikube-v0.23.0.iso
Install tools:
Others:
What happened:
HostPath PVCs will not bind to PVs -- PVCs stuck in
Pending
forever.What you expected to happen:
HostPath PVCs successfully bind, as it did in Minikube v0.20.0
How to reproduce it (as minimally and precisely as possible):
Create test.yml:
Execute:
kubectl apply -f test.yml
Anything else do we need to know:
This worked fine in v0.20.0 of minikube -- seems to be a regression in newest version. Any ideas, work-arounds would be greatly appreciated!
The text was updated successfully, but these errors were encountered: