search

luxas / kubeadm-workshop

Showcasing a bare-metal multi-platform kubeadm setup with persistent storage and monitoring
MIT License
680 stars 190 forks source link

Deploying dependencies of Rook causes PersistentVolumeClaim is not bound errors #10

Closed carlosedp closed 7 years ago

carlosedp commented 7 years ago

After I deploy dependencies of the Persistent Volumes, I get the following errors. The pods are in Pending state. This happens to Influx-Grafana and Prometheus:


[SchedulerPredicates failed due to PersistentVolumeClaim is not bound: "grafana-pv-claim", which is unexpected., SchedulerPredicates failed due to PersistentVolumeClaim is not bound: "grafana-pv-claim", which is unexpected., SchedulerPredicates failed due to PersistentVolumeClaim is not bound: "grafana-pv-claim", which is unexpected.]

---------

[SchedulerPredicates failed due to PersistentVolumeClaim is not bound: "influxdb-pv-claim", which is unexpected., SchedulerPredicates failed due to PersistentVolumeClaim is not bound: "influxdb-pv-claim", which is unexpected., SchedulerPredicates failed due to PersistentVolumeClaim is not bound: "influxdb-pv-claim", which is unexpected.]

---------

[SchedulerPredicates failed due to PersistentVolumeClaim is not bound: "prometheus-sample-metrics-prom-db-prometheus-sample-metrics-prom-0", which is unexpected., SchedulerPredicates failed due to PersistentVolumeClaim is not bound: "prometheus-sample-metrics-prom-db-prometheus-sample-metrics-prom-0", which is unexpected., SchedulerPredicates failed due to PersistentVolumeClaim is not bound: "prometheus-sample-metrics-prom-db-prometheus-sample-metrics-prom-0", which is unexpected.]
luxas commented 7 years ago

Hmm, that's strange. Will try to reproduce on a fresh cluster, hang on...

carlosedp commented 7 years ago

I'm actually deploying a new cluster here. Let me try it again and I report back. I found it too strange as well.

Another thing is that the secret is not called "rook-rbd-user". Rook creates it as rook-rook-user. Maybe the README needs an update.

carlosedp commented 7 years ago

Yep, not worked here. I've followed the pre-reqs (installed the Ceph docker image) but same error.

luxas commented 7 years ago

Ok, so now I've fixed it Turned out Rook renamed their Secret from rook-rbd-secret to rook-rook-secret, updated the instructions.

Thanks for the bug report!

carlosedp commented 7 years ago

Even after the fix, I still got problems related to the PVC being not bound.

I fixed by adding " storageClassName: rook-block" into the PVC "spec:" block.

luxas commented 7 years ago

@carlosedp Did you remember to execute this command?

kubectl patch storageclass rook-block -p '{"metadata":{"annotations": {"storageclass.kubernetes.io/is-default-class": "true"}}}'
carlosedp commented 7 years ago

@luxas Yes, I did. I have redeployed Rook and wanted to test this.