Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Helm repo update failing due to airflow #31354

Closed
alvarogaroconstella opened this issue Jan 14, 2025 · 5 comments
Closed

Helm repo update failing due to airflow #31354

alvarogaroconstella opened this issue Jan 14, 2025 · 5 comments
Assignees
Labels
solved tech-issues The user has a technical issue about an application triage Triage is needed

Comments

@alvarogaroconstella
Copy link

Name and Version

bitnami/airflow

What architecture are you using?

None

What steps will reproduce the bug?

In my local I run helm repo update and I get:

Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "python-app-chart" chart repository
...Successfully got an update from the "metrics-server" chart repository
...Successfully got an update from the "open" chart repository
...Successfully got an update from the "eugenmayer" chart repository
...Successfully got an update from the "aws-efs-csi-driver" chart repository
...Successfully got an update from the "apache-airflow" chart repository
...Successfully got an update from the "nginx-stable" chart repository
...Successfully got an update from the "aws-ebs-csi-driver" chart repository
...Successfully got an update from the "ingress-nginx" chart repository
...Successfully got an update from the "elastic" chart repository
...Successfully got an update from the "wiremind" chart repository
index.go:366: 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
...Successfully got an update from the "grafana" chart repository
...Successfully got an update from the "prometheus-community" chart repository

The fact is that I am using a dependency on my chart of postgresql but due to this airflow error i cannot even deploy other applications that uses bitnami charts

Are you using any custom parameters or values?

No response

What is the expected behavior?

No response

What do you see instead?

I face problems in postgresql dependency due to this airflow error

Additional information

No response

@chaosi-zju
Copy link

same problem

@bencat-sixense
Copy link

bencat-sixense commented Jan 14, 2025

Same here

Getting updates for unmanaged Helm repositories... ...Successfully got an update from the "https://maikumori.github.io/helm-charts/" chart repository index.go:354: 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 "https://charts.bitnami.com/bitnami" chart repository Hang tight while we grab the latest from your chart repositories... ...Successfully got an update from the "beyond" chart repository Update Complete. ⎈Happy Helming!⎈ index.go:354: skipping loading invalid entry for chart "airflow" "" from /home/runner/.cache/helm/repository/helm-manager-54d26[20])bbb6f1bb3f35d4c7f945bfa25077949488dcbb0a4d01c90f2c35baa59-index.yaml: validation: chart.metadata.name is required Error: redis chart not found in repo https://charts.bitnami.com/bitnami Error: Process completed with exit code 1.

@jerome-morgado
Copy link

Same problem here

@chaosi-zju
Copy link

it seems has been fixed, just run helm repo update and try again

@carrodher
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
solved tech-issues The user has a technical issue about an application triage Triage is needed
Projects
None yet
Development

No branches or pull requests

6 participants