This repository has been archived by the owner on Apr 17, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
cluster-autoscaler: Unable to look up PVC info #2507
Labels
Comments
I also see the same, and when the autoscaler should have executed a scale up it didn't happen.
Last line came after I swapped the 0.5.0 for the 0.4.0 of cluster-autoscaler. Using Kops - if that has something to do with this. |
Which version of K8S are you on? |
1.5.4 |
and im on v1.5.3 |
k8s-github-robot
pushed a commit
to kubernetes/kubernetes
that referenced
this issue
Apr 25, 2017
Automatic merge from submit-queue (batch tested with PRs 40060, 44860, 44865, 44825, 44162) Bump Cluster Autoscaler to 0.5.2 Fixes PVC issue in Cluster Autoscaler (kubernetes-retired/contrib#2507). cc: @MaciekPytel @fgrzadkowski
This has been fixed in cluster-autoscaler 0.5.2. Since CA image has now been released I'm closing the issue. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
cluster-autoscaler works fine but im seeing multiple lines of this error in the logs:
E0328 18:14:57.140465 1 predicates.go:234] Unable to look up PVC info for logging/datadir-elasticsearch-data-ss-1, assuming PVC matches predicate when counting limits: persistentvolumeclaim "datadir-elasticsearch-data-ss-1" not found
I've confirmed the pvc datadir-elasticsearch-data-ss-1does exist in the logging namespace
The text was updated successfully, but these errors were encountered: