Chart repository not reachable (DNS Issue)
Closed this issue · 23 comments
Name and Version
All Charts
What steps will reproduce the bug?
- Try loading https://charts.bitnami.com/bitnami
- Observe DNS error
Are you using any custom parameters or values?
No
What is the expected behavior?
Chart repository is reachable at https://charts.bitnami.com/bitnami
What do you see instead?
In browser DNS_PROBE_FINISHED_NXDOMAIN, in helm dial tcp: lookup charts.bitnami.com on ... : no such host
Additional information
nslookup gives the following:
charts.bitnami.com canonical name = d1xe8nqhpmcyfh.cloudfront.net.
same issue
Does Bitnami provide some kind of status page by the way?
I googled for something like that but couldn't find anything.
Seem fix now : http://dns.squish.net/traverses/958c5af6fa063f7bb00db86b71aecb18
But CNAME are in cache for 2h
new one is "dqk9m89za31r9.cloudfront.net"
I can confirm I am now getting good DNS lookups from some locations.
I am still hitting errors too.
│ Error: looks like "https://charts.bitnami.com/bitnami" is not a valid chart repository or cannot be reached: Get "https://charts.bitnami.com/bitnami/index.yaml": dial tcp: lookup charts.bitnami.com on [fe80::1%en0]:53: no such host
Yes - you have to flush DNS. Then the issue should be solved. Having the same issue..
hello sir when will the issue be of the fix sir? my koobyneet is now in the broke??
Recommendation: LOCK, and add comment from maintainers.
DNS is repopulating, and the issue is resolved.
Flush your caches, if necessary. For confirmation, use dig pointed at a an upstream core provider.
$ dig @8.8.4.4 charts.bitnami.com
; <<>> DiG 9.18.7 <<>> @8.8.4.4 charts.bitnami.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 37738
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;charts.bitnami.com. IN A
;; ANSWER SECTION:
charts.bitnami.com. 6 IN CNAME dqk9m89za31r9.cloudfront.net.
dqk9m89za31r9.cloudfront.net. 60 IN A 52.84.52.99
dqk9m89za31r9.cloudfront.net. 60 IN A 52.84.52.117
dqk9m89za31r9.cloudfront.net. 60 IN A 52.84.52.114
dqk9m89za31r9.cloudfront.net. 60 IN A 52.84.52.119
;; Query time: 26 msec
;; SERVER: 8.8.4.4#53(8.8.4.4) (UDP)
;; WHEN: Wed Nov 02 12:03:43 EDT 2022
;; MSG SIZE rcvd: 153
$ dig @8.8.4.4 dqk9m89za31r9.cloudfront.net.
; <<>> DiG 9.18.7 <<>> @8.8.4.4 dqk9m89za31r9.cloudfront.net.
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53639
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;dqk9m89za31r9.cloudfront.net. IN A
;; ANSWER SECTION:
dqk9m89za31r9.cloudfront.net. 60 IN A 52.84.52.117
dqk9m89za31r9.cloudfront.net. 60 IN A 52.84.52.99
dqk9m89za31r9.cloudfront.net. 60 IN A 52.84.52.119
dqk9m89za31r9.cloudfront.net. 60 IN A 52.84.52.114
;; Query time: 26 msec
;; SERVER: 8.8.4.4#53(8.8.4.4) (UDP)
;; WHEN: Wed Nov 02 12:03:51 EDT 2022
;; MSG SIZE rcvd: 121
``
Had to re-run the command a few times to have the DNS propagate to the new URL, but yeah it seems fixed.
my DNS was still hitting old distribution. Updating the nameserver to 8.8.4.4 did the trick for me. thanks, guys.
When is this going to be solved?
Thanks for reporting this issue. It was a problem in the CloudFront distribution that we used for the Charts repository.
The problem is that terraform recreated the CloudFront collection, creating a new DNS endpoint that needed to replicate globally. A small number of DNS are still resolving the old CloudFront collection name, but for the most part, the issue should be fixed shortly.
I ran the following commands but still got the same issue. Am I missing anything?
dig @8.8.4.4 charts.bitnami.com
helm fetch bitnami/keycloak
I ran the commands multiple times/ fresh session.
@codablock I can resolve the host:
charts.bitnami.com canonical name = dqk9m89za31r9.cloudfront.net.
Name: dqk9m89za31r9.cloudfront.net
Address: 13.224.222.45
Name: dqk9m89za31r9.cloudfront.net
Address: 13.224.222.114
Name: dqk9m89za31r9.cloudfront.net
Address: 13.224.222.14
Name: dqk9m89za31r9.cloudfront.net
Address: 13.224.222.43
but this is what I a getting now:
This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Error>
<Code>AccessDenied</Code>
<Message>Access Denied</Message>
<RequestId>HHMZQEDQG4YQYWYN</RequestId>
<HostId>DlkCXrmgUG/XbFqq5S2pGyUULA3Q3vAYKRyzRmFLO6EkSe+btS4dA9aRlpyb2m+bivvsoy9unSU=</HostId>
</Error>
I am not sure if this is a new issue.
Same issue here:
Getting updates for unmanaged Helm repositories...
...Unable to get an update from the "https://charts.bitnami.com/bitnami/postgresql" chart repository:
failed to fetch https://charts.bitnami.com/bitnami/postgresql/index.yaml : 403 Forbidden
Same issue here:
Getting updates for unmanaged Helm repositories... ...Unable to get an update from the "https://charts.bitnami.com/bitnami/postgresql" chart repository: failed to fetch https://charts.bitnami.com/bitnami/postgresql/index.yaml : 403 Forbidden
not related, 403 Forbidden mean your reach the endpoint.
this issue was about DNS issues not permissions.
Same issue here:
Getting updates for unmanaged Helm repositories... ...Unable to get an update from the "https://charts.bitnami.com/bitnami/postgresql" chart repository: failed to fetch https://charts.bitnami.com/bitnami/postgresql/index.yaml : 403 Forbiddennot related, 403 Forbidden mean your reach the endpoint.
this issue was about DNS issues not permissions.
Thanks. Thought it is related, charts were working few days back. We are using postgres chart as a dependency. I will see if there is another ticket, or will report one for 403.
getting the same error as @sumesh-aot with the prestashop chart, nothing has changed on our end and since this morning I im getting 403
Getting error:
Getting error:
You are missing the /bitnami at the end of the URL, the proper command should be:
$ helm repo add bitnami https://charts.bitnami.com/bitnami
"bitnami" has been added to your repositories@carrodher Still getting errors:
If I'm using the --insecure-skip-tls-verify flag than it will work
The problem still exists