Repository invalid? skipping loading invalid entry for chart "airflow" "" from https://charts.bitnami.com/bitnami: validation: chart.metadata.name is require

[violuke]

Name and Version

all

What architecture are you using?

None

What steps will reproduce the bug?

$ helm repo update
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!⎈

It seems to happen if you have the repo. I'm not using airflow but it's preventing other charts from being processed properly. In case it matters, from Bitnami I'm using elasticsearch, zookeeper and rabbitmq.

Thank you.

Are you using any custom parameters or values?

No response

What is the expected behavior?

No response

What do you see instead?

See above.

Additional information

No response

[lorantalas]

#31348 (comment)

[uakhponomarov]

During the deployment of the Helm Chart for Fluentd, the following error was encountered:
Error: chart "fluentd" version "6.5.13" not found in https://charts.bitnami.com/bitnami repository

[ThorstenDev]

During the deployment of the Helm Chart for Fluentd, the following error was encountered: Error: chart "fluentd" version "6.5.13" not found in https://charts.bitnami.com/bitnami repository

Yes, the index.yaml only contains airflow entries and nothing else...

[violuke]

Seems to be resolved for me now 🤔

[carrodher]

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

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

[rorynickolls-skyral]

@carrodher while attempting to diagnose this issue, I came across this blog post: https://blog.bitnami.com/2024/10/bitnami-helm-charts-moving-to-oci.html

Should we be looking to use the OCI registry instead of charts.bitnami.com and is there a timeline for when the latter will be disabled?

[uakhponomarov]

During the deployment of the Helm Chart for Fluentd, the following error was encountered: Error: chart "fluentd" version "6.5.13" not found in https://charts.bitnami.com/bitnami repository

It has been resolved for me

[carrodher]

@carrodher while attempting to diagnose this issue, I came across this blog post: https://blog.bitnami.com/2024/10/bitnami-helm-charts-moving-to-oci.html

Should we be looking to use the OCI registry instead of charts.bitnami.com and is there a timeline for when the latter will be disabled?

At this moment, there are no plans to modify how the index.yaml is served concerning OCI. In fact, it is already configured to point to Helm charts stored as OCI packages, rather than simple tgz files served from S3 (which was the previous method).

The changes will primarily affect the Bitnami Helm charts in tgz format, as these will no longer receive updates moving forward.

[diegocastagnek]

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

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

Hello, for me the issue is still present, are you rolling out the update?

[traviswt]

Still have the issue.

[jseletz-rave]

We also still have the issue

[flowjo-shaunr]

I still see only airflow entries under https://charts.bitnami.com/bitnami/index.yaml

[wodka]

for me there is a redirect happening to https://repo.broadcom.com/bitnami-files/index.yaml - also containing only airflow entries.

last-modified: Tue, 14 Jan 2025 20:57:25 GMT
server: cloudflare
server-timing: cfCacheStatus;desc="HIT"

does not seem like the original issue has been solved :/

Update: in case you are applying helm charts directly, the repository url can be changed: https://charts.bitnami.com/bitnami to oci://registry-1.docker.io/bitnamicharts

[beltran-rubo]

Looks intermittent issues with CDN, it looks solved again.

[ad-m-ss]

Two requests in a short time give two different responses; it looks like a caching issue.

$ curl 'https://charts.bitnami.com/bitnami/index.yaml' -v -L | yq '.entries | keys'
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0* Host charts.bitnami.com:443 was resolved.
* IPv6: (none)
* IPv4: 18.244.102.94, 18.244.102.10, 18.244.102.68, 18.244.102.113
*   Trying 18.244.102.94:443...
* Connected to charts.bitnami.com (18.244.102.94) port 443
* ALPN: curl offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
} [323 bytes data]
*  CAfile: /etc/ssl/cert.pem
*  CApath: none
* (304) (IN), TLS handshake, Server hello (2):
{ [122 bytes data]
* (304) (IN), TLS handshake, Unknown (8):
{ [19 bytes data]
* (304) (IN), TLS handshake, Certificate (11):
{ [3811 bytes data]
* (304) (IN), TLS handshake, CERT verify (15):
{ [264 bytes data]
* (304) (IN), TLS handshake, Finished (20):
{ [36 bytes data]
* (304) (OUT), TLS handshake, Finished (20):
} [36 bytes data]
* SSL connection using TLSv1.3 / AEAD-AES128-GCM-SHA256 / [blank] / UNDEF
* ALPN: server accepted h2
* Server certificate:
*  subject: CN=charts.bitnami.com
*  start date: Oct 15 00:00:00 2024 GMT
*  expire date: Nov 12 23:59:59 2025 GMT
*  subjectAltName: host "charts.bitnami.com" matched cert's "charts.bitnami.com"
*  issuer: C=US; O=Amazon; CN=Amazon RSA 2048 M03
*  SSL certificate verify ok.
* using HTTP/2
* [HTTP/2] [1] OPENED stream for https://charts.bitnami.com/bitnami/index.yaml
* [HTTP/2] [1] [:method: GET]
* [HTTP/2] [1] [:scheme: https]
* [HTTP/2] [1] [:authority: charts.bitnami.com]
* [HTTP/2] [1] [:path: /bitnami/index.yaml]
* [HTTP/2] [1] [user-agent: curl/8.7.1]
* [HTTP/2] [1] [accept: */*]
> GET /bitnami/index.yaml HTTP/2
> Host: charts.bitnami.com
> User-Agent: curl/8.7.1
> Accept: */*
>
* Request completely sent off
< HTTP/2 302
< server: CloudFront
< date: Tue, 14 Jan 2025 21:47:33 GMT
< content-length: 0
< location: https://repo.broadcom.com/bitnami-files/index.yaml
< x-cache: FunctionGeneratedResponse from cloudfront
< via: 1.1 44a23a2f4d4e9659f5b008d1f39e1318.cloudfront.net (CloudFront)
< x-amz-cf-pop: WAW51-P3
< x-amz-cf-id: hpdVHxua7W4p8tZjiB15eRrRLff8AZvfKTxaxs1a1RUcc5X58gosPw==
<
* Ignoring the response-body
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
* Connection #0 to host charts.bitnami.com left intact
* Issue another request to this URL: 'https://repo.broadcom.com/bitnami-files/index.yaml'
* Host repo.broadcom.com:443 was resolved.
* IPv6: (none)
* IPv4: 162.159.140.167, 172.66.0.165
*   Trying 162.159.140.167:443...
* Connected to repo.broadcom.com (162.159.140.167) port 443
* ALPN: curl offers h2,http/1.1
* (304) (OUT), TLS handshake, Client hello (1):
} [322 bytes data]
* (304) (IN), TLS handshake, Server hello (2):
{ [122 bytes data]
* (304) (IN), TLS handshake, Unknown (8):
{ [19 bytes data]
* (304) (IN), TLS handshake, Certificate (11):
{ [2527 bytes data]
* (304) (IN), TLS handshake, CERT verify (15):
{ [80 bytes data]
* (304) (IN), TLS handshake, Finished (20):
{ [36 bytes data]
* (304) (OUT), TLS handshake, Finished (20):
} [36 bytes data]
* SSL connection using TLSv1.3 / AEAD-CHACHA20-POLY1305-SHA256 / [blank] / UNDEF
* ALPN: server accepted h2
* Server certificate:
*  subject: CN=repo.broadcom.com
*  start date: Dec  7 10:17:06 2024 GMT
*  expire date: Mar  7 11:17:03 2025 GMT
*  subjectAltName: host "repo.broadcom.com" matched cert's "repo.broadcom.com"
*  issuer: C=US; O=Google Trust Services; CN=WE1
*  SSL certificate verify ok.
* using HTTP/2
* [HTTP/2] [1] OPENED stream for https://repo.broadcom.com/bitnami-files/index.yaml
* [HTTP/2] [1] [:method: GET]
* [HTTP/2] [1] [:scheme: https]
* [HTTP/2] [1] [:authority: repo.broadcom.com]
* [HTTP/2] [1] [:path: /bitnami-files/index.yaml]
* [HTTP/2] [1] [user-agent: curl/8.7.1]
* [HTTP/2] [1] [accept: */*]
> GET /bitnami-files/index.yaml HTTP/2
> Host: repo.broadcom.com
> User-Agent: curl/8.7.1
> Accept: */*
>
* Request completely sent off
< HTTP/2 200
< date: Tue, 14 Jan 2025 21:47:33 GMT
< content-type: text/plain
< content-length: 20331510
< cf-ray: 9020d33cac74bf42-WAW
< cf-cache-status: HIT
< accept-ranges: bytes
< age: 7
< cache-control: public, max-age=86400
< content-disposition: inline
< etag: "f8dea96e7e176b1c08c90a4f9c794780"
< expires: Wed, 15 Jan 2025 21:47:33 GMT
< last-modified: Tue, 14 Jan 2025 21:47:24 GMT
< strict-transport-security: max-age=31536000; includeSubDomains
< server: cloudflare
<
{ [1360 bytes data]
100 19.3M  100 19.3M    0     0  10.3M      0  0:00:01  0:00:01 --:--:-- 11.8M
* Connection #1 to host repo.broadcom.com left intact
- airflow
- apache
- apisix
- appsmith
- argo-cd
- argo-workflows
- aspnet-core
- cassandra
- cert-manager
- chainloop
- cilium
- clickhouse
- common
- concourse
- consul
- contour
- contour-operator
- dataplatform-bp2
- deepspeed
- discourse
- dokuwiki
- dremio
- drupal
- ejbca
- elasticsearch
- etcd
- external-dns
- flink
- fluent-bit
- fluentd
- flux
- geode
- ghost
- gitea
- grafana
- grafana-loki
- grafana-mimir
- grafana-operator
- grafana-tempo
- haproxy
- haproxy-intel
- harbor
- influxdb
- jaeger
- janusgraph
- jasperreports
- jenkins
- joomla
- jupyterhub
- kafka
- keycloak
- keydb
- kiam
- kibana
- kong
- kube-prometheus
- kube-state-metrics
- kubeapps
- kuberay
- kubernetes-event-exporter
- logstash
- magento
- mariadb
- mariadb-galera
- mastodon
- matomo
- mediawiki
- memcached
- metallb
- metrics-server
- milvus
- minio
- mlflow
- mongodb
- mongodb-sharded
- moodle
- multus-cni
- mxnet
- mysql
- nats
- neo4j
- nessie
- nginx
- nginx-ingress-controller
- nginx-intel
- node
- node-exporter
- oauth2-proxy
- odoo
- opencart
- opensearch
- osclass
- owncloud
- parse
- phpbb
- phpmyadmin
- pinniped
- postgresql
- postgresql-ha
- prestashop
- prometheus
- pytorch
- rabbitmq
- rabbitmq-cluster-operator
- redis
- redis-cluster
- redmine
- schema-registry
- scylladb
- sealed-secrets
- seaweedfs
- solr
- sonarqube
- spark
- spring-cloud-dataflow
- suitecrm
- supabase
- tensorflow-resnet
- thanos
- tomcat
- valkey
- valkey-cluster
- vault
- wavefront
- wavefront-adapter-for-istio
- wavefront-hpa-adapter
- wavefront-prometheus-storage-adapter
- whereabouts
- wildfly
- wordpress
- wordpress-intel
- zipkin
- zookeeper