Skipping loading when adding bitnami charts repository with Helm

[Llyth]

Name and Version

bitnami/charts

What architecture are you using?

amd64

What steps will reproduce the bug?

1. helm repo add bitnami https://charts.bitnami.com/bitnami
2. helm search repo bitnami

Are you using any custom parameters or values?

No response

What is the expected behavior?

NAME CHART VERSION APP VERSION DESCRIPTION
bitnami/airflow 22.4.5 2.10.4 Apache Airflow is a tool to express and execute...
[...]

What do you see instead?

index.go:370: skipping loading invalid entry for chart "airflow" "" from /home//.cache/helm/repository/bitnami-index.yaml: validation: chart.metadata.name is required
NAME CHART VERSION APP VERSION DESCRIPTION
bitnami/airflow 22.4.5 2.10.4 Apache Airflow is a tool to express and execute...

Additional information

The error at index.go:370 is also present when you helm repo add or helm repo update.

helm version is: version.BuildInfo{Version:"v3.16.3", GitCommit:"cfd07493f46efc9debd9cc1b02a0961186df7fdf", GitTreeState:"clean", GoVersion:"go1.22.7"}

[SimonWoidig]

The issue seems larger. I cannot download any charts - not even PostgreSQL.

~/my-chart # cat Chart.yaml 
apiVersion: v2
type: application
name: my-chart
version: 0.0.1
dependencies:
  - name: postgresql
    version: 15.5.21
    repository: https://charts.bitnami.com/bitnami

~/my-chart # helm dep up
Hang tight while we grab the latest from your chart repositories...
index.go:370: skipping loading invalid entry for chart "airflow" "" from https://charts.bitnami.com/bitnami: validation: chart.metadata.name is required
...Successfully got an update from the "bitnami" chart repository
Update Complete. ⎈Happy Helming!⎈
index.go:370: skipping loading invalid entry for chart "airflow" "" from /root/.cache/helm/repository/bitnami-index.yaml: validation: chart.metadata.name is required
Error: postgresql chart not found in repo https://charts.bitnami.com/bitnami
~/my-chart # helm search repo bitnami
index.go:370: skipping loading invalid entry for chart "airflow" "" from /root/.cache/helm/repository/bitnami-index.yaml: validation: chart.metadata.name is required
NAME            CHART VERSION   APP VERSION     DESCRIPTION                                       
bitnami/airflow 22.4.5          2.10.4          Apache Airflow is a tool to express and execute...

[dlnilsson]

the helm cache file gets alot of duplicate values, invalid values of bitnami/airflow,

cat $HOME/.cache/helm/repository/bitnami-index.yaml | grep airflow | wc -l
1187

[Llyth]

It seems there is a typo somewhere and it broke the index.yaml file for the chart repository.

[Giannischri]

skipping loading invalid entry for chart "airflow" "" from https://charts.bitnami.com/bitnami: validation: chart.metadata.name is required index.go:370: skipping loading invalid entry for chart "airflow" "" from /helm-working-dir/repository/https:--charts.bitnami.com-bitnami-index.yaml: validation: chart.metadata.name is required Error: redis chart not found in repo https://charts.bitnami.com/bitnami......in argocd

[leo108]

A workaround is to replace repo with raw file in github:

helm repo add bitnami https://raw.githubusercontent.com/bitnami/charts/refs/heads/index/bitnami/

[baznikin]

This is major failure and should be fixed ASAP
@carlossm @agarcia-oss @tompizmor @dgomezleon @carrodher @migruiz4

[beltran-rubo]

Thanks for letting us know, the team is investigating the error.

[garbelini]

Seems like it's fixed from my side.

[chreichert]

I can confirm, after doing 'helm repo update' Bitnami Charts are loading again.

[RustyF]

Working for me now too, kudos for quick turnaround.

[carrodher]

Apologies for the oversight. We identified an issue in the index.yaml file and have re-pushed it. The problem should now be resolved.

To prevent similar issues in the future, we are implementing additional measures, including notifications and retry mechanisms for the GitHub Action responsible for this process.

To streamline discussions, we will funnel all conversations into the first issue created on this topic (#31350). As part of this effort, we are closing the remaining issues to avoid duplication.