KusionStack / KusionStack/karpor

FailedAttachVolume

Open
#550 18 comments 0 reactions 1 assignee Assigned to @danielstankw View on GitHub
area/installation priority/important-longterm
Dominant language
Go
Stars
1.7k
Forks
113
PR merge metrics
No merged PRs in 30d

Description

### What happened?

There is an issue with the helm chart deployment and Volume.
`The volume 'vol-03e1c30abe533984b' does not exist.` - seems like a misconfiguration of volume name on the helm site

When deploying the helm chart the following happens:

```bashrc
elasticsearch-5654f4f8c5-8xjkj 1/1 Running 0 16m
etcd-0 0/1 ContainerCreating 0 13m
karpor-server-d9d477955-9gb4t 0/1 CrashLoopBackOff 7 (3m ago) 16m
karpor-syncer-64d449f4c-fbzjv 0/1 Error 8 (5m7s ago) 16m
```

This is due:
`k describe pod etcd-0`

```bashrc
Warning FailedAttachVolume 12m attachdetach-controller AttachVolume.Attach failed for volume "pvc-f28692d1-1d3e-4b8a-b2fc-1980dc2c1eee" : InvalidVolume.NotFound: The volume 'vol-03e1c30abe533984b' does not exist.
status code: 400, request id: ef0543fb-03dd-4a9c-82ab-06f2cca0faa2
```

`k get pvc`
```bashrc
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
data-etcd-0 Bound pvc-f28692d1-1d3e-4b8a-b2fc-1980dc2c1eee 10Gi RWO gp2 3h59m

```

### What did you expect to happen?

....

### How can we reproduce it (as minimally and precisely as possible)?

Run the default helm chart with unchanged values.

### Anything else we need to know?

_No response_

### Karpor version

```console
$ karpor -V
# paste output here
```

### OS version

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

### Install tools

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.