• EN
Solved

Grafana Pod - Init:CrashLoopBackOff

S
Userlevel 2

I have freshly installed K10 and after the installation Grafana works and after a restart (Of the Cluster or Pod) I get the following error message. Can anyone explain this to me? 

pod/k10-grafana-856b5d6b5f-nqczn         0/1     Init:CrashLoopBackOff
Events:
  Type     Reason                  Age                From                     Message
  ----     ------                  ----               ----                     -------
  Normal   Scheduled               32s                default-scheduler        Successfully assigned kasten-io/k10-grafana-856b5d6b5f-n7x4g to mh-k8s-w3
  Warning  FailedAttachVolume      32s                attachdetach-controller  Multi-Attach error for volume "pvc-40666f4b-e505-4e66-9d2d-2cff4090982f" Volume is already exclusively attached to one node and can't be attached to another
  Normal   SuccessfulAttachVolume  30s                attachdetach-controller  AttachVolume.Attach succeeded for volume "pvc-40666f4b-e505-4e66-9d2d-2cff4090982f"
  Normal   Pulled                  11s (x3 over 27s)  kubelet                  Container image "registry.access.redhat.com/ubi8/ubi-minimal:8.6-751" already present on machine
  Normal   Created                 11s (x3 over 26s)  kubelet                  Created container init-chown-data
  Normal   Started                 11s (x3 over 26s)  kubelet                  Started container init-chown-data
  Warning  BackOff                 11s (x3 over 25s)  kubelet                  Back-off restarting failed container

 

icon

Best answer by jaiganeshjk 1 June 2022, 14:48

View original

2 comments

jaiganeshjk
Userlevel 6
Badge +2

@Smugness2774 Thank you for posting this question.

While looking at the event messages, the attach-detach controller is failing to attach the volume to the node where `k10-grafana` pod is scheduled.

Do you still see the older instance of K10-grafana pod in terminating state ?

Jaiganesh
S
Userlevel 2

@Smugness2774 Thank you for posting this question.

While looking at the event messages, the attach-detach controller is failing to attach the volume to the node where `k10-grafana` pod is scheduled.

Do you still see the older instance of K10-grafana pod in terminating state ?

Sry for the late reply, but no… Also, using another storage class doesn't work. Also, reinstalling the whole thing doesn’t change anything.

Comment


Terms & Conditions