Error: Looks like "https://charts.deis.com/workflow" is not a valid chart repository about workflow HOT 7 OPEN

From @bacongobbler on April 24, 2017 6:31

Seeing this too:

><> helm repo up
Hang tight while we grab the latest from your chart repositories...
...Skip local chart repository
Writing to /Users/bacongobbler/.helm/repository/cache/stable-index.yaml
...Successfully got an update from the "stable" chart repository
...Unable to get an update from the "deis" chart repository (https://charts.deis.com/workflow):
	Get https://charts.deis.com/workflow/index.yaml: dial tcp: lookup charts.deis.com on 172.20.16.1:53: read udp 172.20.18.14:51010->172.20.16.1:53: i/o timeout
Update Complete. ⎈ Happy Helming!⎈

from workflow.

From @vdice on April 24, 2017 14:15

The issue seems to have been a temporary. I'm able to add and update the repo:

 $ helm repo add workflow https://charts.deis.com/workflow
"workflow" has been added to your repositories
 $ helm repo update
Hang tight while we grab the latest from your chart repositories...
...
...Successfully got an update from the "workflow" chart repository

Nevertheless, this is still an issue warranting further investigation.

from workflow.

From @pfeodrippe on April 25, 2017 10:22

Yes, it's working for me now. Maybe it was something temporary at the servers, maybe has to do with the migration to Azure Services? Just guessing

from workflow.

From @sbulman on June 22, 2017 12:42

I am seeing this issue today? Any clues?

from workflow.

From @ampsarfraz on August 18, 2017 3:19

I am getting this error as well when I try >helm repo add deis https://charts.deis.com/workflow
How to solve this?
Error: Looks like "https://charts.deis.com/workflow" is not a valid chart repository or cannot be reached

from workflow.

From @mboersma on August 18, 2017 5:17

@ampsarfraz I'm not seeing problems here. Maybe just a transient network error? Helm doesn't always report those errors in a useful way--for example if you unplug from the network and try the same thing you can see misleading errors about missing x509 certs...
I tried it with the debug flag as well but it doesn't seem to add any output:

$ helm repo add --debug deis https://charts.deis.com/workflow
"deis" has been added to your repositories

😕

from workflow.

From @sbulman on August 18, 2017 5:50

@ampsarfraz I was having this problem on Windows. It appears to be more reliable if I explicitly set the HELM_HOME environment variable. e.g. in PowerShell $env:HELM_HOME = "C:\.helm". Try setting this and then adding the repo again.

from workflow.