glusterfs pod does not start for storage-provisioner-gluster addon

[koh-osug]

What Happened?

The pod "gluster" does not starts and complains about "Failed to get D-Bus connection: Operation not permitted"

Attach the log file

NAME READY STATUS RESTARTS AGE
glusterfile-provisioner-549b4d8768-5r6sl 1/1 Running 0 8m1s
glusterfs-mmwxz 0/1 Running 0 8m1s
heketi-5fb66969ff-kwjsx 1/1 Running 0 8m1s

Warning Unhealthy 5m52s (x26 over 13m) kubelet Readiness probe failed: Failed to get D-Bus connection: Operation not permitted
Warning Unhealthy 51s (x32 over 13m) kubelet Liveness probe failed: Failed to get D-Bus connection: Operation not permitted

Operating System

Ubuntu

Driver

Docker

[tchia04]

Got the same error when I tried to enable the storage-provisioner-gluster in minikube with "minikube addons enable storage-provisioner-gluster"

output from "kubectl -n storage-gluster describe pod glusterfs-tj96"

                             node.kubernetes.io/unschedulable:NoSchedule op=Exists
Events:
  Type     Reason     Age                From               Message
  ----     ------     ----               ----               -------
  Normal   Scheduled  2m14s              default-scheduler  Successfully assigned storage-gluster/glusterfs-tj962 to minikube
  Normal   Pulling    2m14s              kubelet            Pulling image "docker.io/gluster/gluster-centos:latest@sha256:8167034b9abf2d16581f3f4571507ce7d716fb58b927d7627ef72264f802e908"
  Normal   Pulled     91s                kubelet            Successfully pulled image "docker.io/gluster/gluster-centos:latest@sha256:8167034b9abf2d16581f3f4571507ce7d716fb58b927d7627ef72264f802e908" in 43.169s (43.169s including waiting). Image size: 392303616 bytes.
  Normal   Created    90s                kubelet            Created container glusterfs
  Normal   Started    90s                kubelet            Started container glusterfs
  Warning  Unhealthy  21s (x2 over 46s)  kubelet            Liveness probe failed: Failed to get D-Bus connection: Operation not permitted
  Warning  Unhealthy  20s (x3 over 44s)  kubelet            Readiness probe failed: Failed to get D-Bus connection: Operation not p

[dalcorta]

Same thing heppens to me, I only know by the error that the container doesnt have previledge to connect to Dbus. Since docker doen't allow previledge containers by default I think that is where the error is.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale