ComparisonError rpc error: code = Unknown desc = helm dependency build failed signal: killed

[s7an-it]

Asked - no reply -> https://cloud-native.slack.com/archives/C01TSERG0KZ/p1661211863236989, in fact asked multiple times.

Checklist:

• I've searched in the docs and FAQ for my answer: https://bit.ly/argocd-faq.
• I've included steps to reproduce the bug.
• I've pasted the output of argocd version.

Describe the bug

On refresh of app repo server throws above errors on ui and doesn't retry in any sane window (30+ min), probably related to current auto-sync.

To Reproduce

Jenkins CI on each build updates a private mono repo in Bitbucket that consist of env folder with application referencing OTS Helm Chart Folder with external values.yaml, the apps in the application folder are watched by app of apps app.
Self-heal is enabled and Jenkins job is to issue app refresh on each CI build so argo can sync against proper chart.
I am using HA setup with 10 repo servers.
Expected behavior

I expect to not get stuck state in unknown without any retry.
If I click refresh app get fixed, so it means retry is not attempted.

Screenshots

Version
{
"Version": "v2.4.9+1ba9008",
"BuildDate": "2022-08-11T15:22:41Z",
"GitCommit": "1ba9008536b7e61414784811c431cd8da356065e",
"GitTreeState": "clean",
"GoVersion": "go1.18.5",
"Compiler": "gc",
"Platform": "linux/amd64",
"KustomizeVersion": "v4.4.1 2021-11-11T23:36:27Z",
"HelmVersion": "v3.8.1+g5cb9af4",
"KubectlVersion": "v0.23.1",
"JsonnetVersion": "v0.18.0"
}

Paste the output from `argocd version` here.

Logs

Paste any relevant application logs here.

[StepanKuksenko]

we faced the same issue, in our case it was argocd-repo-server lack of CPU issue

also check this advice #7104 (comment)

[foxutech]

Is there any fix for this issue?

[adeniyistephen]

@foxutech have you found the solution yet?

[vl-kp]

we have the same issue

[patricklubach]

We had the same issue with argoCD version 2.3.3. I built a custom helm chart with helm v3.12.1 on Windows 10 and this error appeared. A colleague built the same helm chart on his mac with helm v3.11.1 and it worked out of the box. Hope this info helps somehow in debugging the error. @s7an-it did you find a solution or workaround for this?

[hofq]

I ran into this issue when using 2 or more helm charts in the multiple sources feature (this limitation is also documented here):
https://argo-cd.readthedocs.io/en/stable/user-guide/multiple_sources/