Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Grafana Kubernetes Pod stuck in Container Init

Open
#276 2 comments 0 reactions 1 assignee View on GitHub

@ZhangNing10 is already working on this.

Since Apr 24, 2024.

Assessment

This issue has not been assessed yet.

Description

Release : 1.0.0-beta5

Post upgrade of Devlake using Helm Chart, I encountered the following error.

Events:
  Type     Reason              Age                    From                     Message
  ----     ------              ----                   ----                     -------
  Normal   Scheduled           6m47s                  default-scheduler        Successfully assigned devlake/devlake-grafana-6554869b4-czhzw to ip-10-85-44-217.ap-south-1.compute.internal
  Warning  FailedAttachVolume  6m47s                  attachdetach-controller  Multi-Attach error for volume "pvc-fff59316-7f48-406d-abb1-9c02c0895571" Volume is already used by pod(s) devlake-grafana-79775f95f8-4ksq9
  Warning  FailedMount         2m28s (x2 over 4m44s)  kubelet                  Unable to attach or mount volumes: unmounted volumes=[storage], unattached volumes=[storage kube-api-access-sh8m6 config]: timed out waiting for the condition
  Warning  FailedMount         10s                    kubelet                  Unable to attach or mount volumes: unmounted volumes=[storage], unattached volumes=[kube-api-access-sh8m6 config storage]: timed out waiting for the condition

Workaround:

➜  ~ k -n devlake scale deployment/devlake-grafana --replicas=0
deployment.apps/devlake-grafana scaled
➜  ~ k -n devlake scale deployment/devlake-grafana --replicas=1
deployment.apps/devlake-grafana scaled
Dominant language
Go Template
Stars
52
Forks
71
Avg merge
16h 15m
Merged PRs (30d)
1

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from apache/devlake-helm-chart

All issues in apache/devlake-helm-chart

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.