Kafka PersistentVolumeClaim is not bound in Minikube

[jengo]

I am running macOS 10.12.6 with Minikube 0.22.2 and helm 2.6.1.

I tried to setup Kafka using the commands:

helm repo add incubator http://storage.googleapis.com/kubernetes-charts-incubator
helm install --name my-kafka incubator/kafka

The first 2 pods that try to launch report the errors:

PersistentVolumeClaim is not bound: "datadir-my-kafka-kafka-0"
Back-off restarting failed container
Error syncing pod

PersistentVolumeClaim is not bound: "datadir-my-kafka-zookeeper-0"
Back-off restarting failed container
Error syncing pod

I do see both of the referenced Persistent Volume Claims being created along with both Persistent Volumes. The pods never finish setting up and keep restarting.

[ginkel]

@jengo Hitting the same issue. Have you been able to figure out a workaround?

[sammerry]

@jellonek @ginkel any luck? Same problem using stable/sentry chart.

[skunkwerk]

I'm having the same issue on Google Container Engine - keep getting these errors with the Helm installation.

[pablorsk]

I have this error only with minikube, with GCE works fine

[ShahNewazKhan]

I am facing the same issue:

Events:
  FirstSeen     LastSeen        Count   From                    SubObjectPath                          Type             Reason                  Message
  ---------     --------        -----   ----                    -------------                          -------- ------                  -------
  7s            7s              2       default-scheduler                                              Warning          FailedScheduling        PersistentVolumeClaim is not bound: "datadir-dev-zookeeper-0"
  6s            6s              1       default-scheduler                                              Normal           Scheduled               Successfully assigned dev-zookeeper-0 to minikube
  6s            6s              1       kubelet, minikube                                              Normal           SuccessfulMountVolume   MountVolume.SetUp succeeded for volume "pvc-4b088ee5-f5a1-11e7-95f1-52540028db7a" 
  6s            6s              1       kubelet, minikube                                              Normal           SuccessfulMountVolume   MountVolume.SetUp succeeded for volume "default-token-bnjcp" 
  5s            5s              2       kubelet, minikube       spec.containers{zookeeper-server}      Normal           Pulled                  Container image "gcr.io/google_samples/k8szk:v2" already present on machine
  5s            5s              2       kubelet, minikube       spec.containers{zookeeper-server}      Warning          Failed                  Error: lstat /tmp/hostpath-provisioner/pvc-4b088ee5-f5a1-11e7-95f1-52540028db7a: no such file or directory
  5s            5s              2       kubelet, minikube                                              Warning          FailedSync              Error syncing pod

Could possibly be a race condition, as I see

Error: lstat /tmp/hostpath-provisioner/pvc-4b088ee5-f5a1-11e7-95f1-52540028db7a: no such file or directory

MountVolume.SetUp succeeded for volume "pvc-4b088ee5-f5a1-11e7-95f1-52540028db7a"

[kevinohara80]

Has anyone found a workaround to this issue?

[feffi]

anyone? BUMP?

[ghost]

Also seeing this problem, trying to install into minkube

[gexinworks]

Hello,has anyone found a solution to this issue?

[AmundsenJunior]

Addressed via kubernetes/minikube#2256. I upgraded my minikube setup to latest version (v.0.25.2), and the whole chart started up successfully.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[stale]

This issue is being automatically closed due to inactivity.