argo-cd: helm repo add is using the repository as the alias and its not working

Describe the bug

After updating this morning I’m getting an error in all of my applications similar to this:

rpc error: code = Unknown desc = Manifest generation error (cached): `helm repo add https://charts.bitnami.com/bitnami https://charts.bitnami.com/bitnami` failed exit status 1: Error: repository name (https://charts.bitnami.com/bitnami) contains '/', please specify a different name without '/'

This error is from this in a Chart.yaml:

dependencies:
- name: nginx-ingress-controller
  version: 9.1.5
  repository: https://charts.bitnami.com/bitnami

To Reproduce

I’m applying an application which refers to a location in git A, at that location there is a Chart.yaml with the above dependency. I have added the git location A in argocd, but I have not added the location specified in the dependency.

Expected behavior

Everything was working before, so I would have expected things to keep working, unless there has been a breaking change and I now need to update all of my Chart.yaml files.

Screenshots

Version

$ argocd version
argocd: v2.3.1+b65c169
  BuildDate: 2022-03-11T00:19:54Z
  GitCommit: b65c1699fa2a2daa031483a3890e6911eac69068
  GitTreeState: clean
  GoVersion: go1.17.8
  Compiler: gc
  Platform: linux/amd64

About this issue

Original URL
State: open
Created 2 years ago
Reactions: 6
Comments: 16 (6 by maintainers)

Most upvoted comments

Is the issue here only with chart urls that do not have a subpath? it looks like ArgoCD tries to use the subpath as the repository name, but if no subpath exists, it uses the URL, which the updated version of helm does not like.

Adding the helm repository manually solved the issue, however, I had to do a Hard Refresh on all of our applications in order to clear out the repo server and prevent the manifest generation error.

spyder007 on Jun 22, 2022

@MeNsaaH @alexmt There is a PR for this already https://github.com/argoproj/argo-cd/pull/8804

chetan-rns on Apr 4, 2022