helm / helm/chartmuseum

Error saving index-cache.yaml with Microsoft Azure as storage backend

Open
#759 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
3.8k
Forks
407
PR merge metrics
No merged PRs in 30d

Description

```
Helm Chart: chartmuseum/chartmuseum@3.10.2
Docker image: ghcr.io/helm/chartmuseum:v0.16.1

---

STORAGE: microsoft
DISABLE_STATEFILES: false
```

We have a workflow using [changesets](https://github.com/changesets/changesets) where we occasionally release a bunch of our applications at once. Through a series of GitHub Actions each application gets built, packaged & uploaded to ChartMuseum, which uploads the Charts to an Azure Storage Account (blob).

We noticed a bunch of these GitHub Actions fail with the following error:
```
Error saving index-cache.yaml

storage: service returned error: StatusCode=409, ErrorCode=InvalidBlobType, ErrorMessage=The blob type is invalid for this operation.\nRequestId:...\nTime:..., RequestInitiated=..., RequestId=..., API Version=2018-03-28, QueryParameterName=, QueryParameterValue=
```

---

I assume the issue might be caused by the fact that ChartMuseum is trying to update `index-cache.yaml` multiple times at the same time, causing Azure to throw a 409 error.

What do you suggest we do to resolve this?
Should we just disable the `index-cache.yaml` statefile or is there an alternative solution? What is the exact effect if we do this?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.