You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We run an ArgoCD instance with some 300 applications and are regularly seeing the following error on different helm applications.
failed exit status 1: Error: An error occurred while checking for chart dependencies. You may need to run `helm dependency build` to fetch missing dependencies: found in Chart.yaml, but missing in charts/ directory: vault-gke-integration" execID=b5f8a
What I've noticed is that whenever this error occurs then the ordering of operations seems incorrect for example.
helm template < This should be last
helm repo add X
helm dependency build
Note: It happens on all different git repositories as well as helm repositories so I don't believe it's unique to any particular setup, just happens more commonly with higher number of applications.
I assume that it's to do with this code running in parallel in another thread which causes the operations to be in the incorrect order.
Checklist:
argocd version
.Describe the bug
We run an ArgoCD instance with some 300 applications and are regularly seeing the following error on different helm applications.
What I've noticed is that whenever this error occurs then the ordering of operations seems incorrect for example.
helm template
< This should be lasthelm repo add X
helm dependency build
Note: It happens on all different git repositories as well as helm repositories so I don't believe it's unique to any particular setup, just happens more commonly with higher number of applications.
I assume that it's to do with this code running in parallel in another thread which causes the operations to be in the incorrect order.
Possibly related issues: #11564 #11564
To Reproduce
It's quite difficult for this to be replicated as I believe it to be due to a timing issue, but a suggested way might be to do the following.
For us it triggers a few hundred times an hour with out 300+ applications.
Expected behavior
helm template
should never run beforehelm dependency build
1Screenshots
N/A
Version
Logs
Easier to read Log
Full Log
The text was updated successfully, but these errors were encountered: