ArgoCD Sync Issue with Private Helm Repository on Amazon ECR in Version 2.11.0

[sassdavid]

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

I am experiencing an issue with ArgoCD sync in version 2.11.0. I have a private Helm repository on Amazon ECR, and I created an application based on a chart stored in this repository. When I try to sync this application in the UI, the following error message appears: Unable to sync: error resolving repo revision: rpc error: code = Unknown desc = repository not found

There was no similar behavior in version 2.10.9. Is it possible that I missed something during the upgrade to 2.11.0?

To Reproduce

• Create a new private Helm OCI repository that connects to AWS-ECR.
• Create a new application based on the newly created repository.
  • It is a multi-source application; the chart comes from AWS-ECR, and the values for the chart come from another Git repository.
• Try to sync the newly created application.
• The following error appears: Unable to sync: error resolving repo revision: rpc error: code = Unknown desc = repository not found

Expected behavior

When I click sync, the application should sync successfully.

Screenshots

Version

argocd: v2.11.0+d3f33c0
  BuildDate: 2024-05-07T16:21:23Z
  GitCommit: d3f33c00197e7f1d16f2a73ce1aeced464b07175
  GitTreeState: clean
  GoVersion: go1.21.9
  Compiler: gc
  Platform: linux/amd64
argocd-server: v2.11.0+d3f33c0
  BuildDate: 2024-05-07T16:01:41Z
  GitCommit: d3f33c00197e7f1d16f2a73ce1aeced464b07175
  GitTreeState: clean
  GoVersion: go1.21.9
  Compiler: gc
  Platform: linux/amd64
  Kustomize Version: v5.2.1 2023-10-19T20:13:51Z
  Helm Version: v3.14.3+gf03cc04
  Kubectl Version: v0.26.11
  Jsonnet Version: v0.20.0

Logs

time="2024-05-16T06:55:39Z" level=info msg="received unary call /application.ApplicationService/Sync" grpc.method=Sync grpc.request.claims="{\"exp\":1715928212,\"iat\":1715841812,\"iss\":\"argocd\",\"jti\":\"9b5d22ee-689f-47db-b35e-232610c37940\",\"nbf\":1715841812,\"sub\":\"admin\"}" grpc.request.content="name:\"tepee-storage-class\" revision:\"1.0.0\" dryRun:false prune:false strategy:<hook:<syncStrategyApply:<force:false > > > syncOptions:<items:\"CreateNamespace=true\" > appNamespace:\"argocd\" " grpc.service=application.ApplicationService grpc.start_time="2024-05-16T06:55:39Z" span.kind=server system=grpc
time="2024-05-16T06:55:39Z" level=warning msg="finished unary call with code FailedPrecondition" error="rpc error: code = FailedPrecondition desc = error resolving repo revision: rpc error: code = Unknown desc = repository not found" grpc.code=FailedPrecondition grpc.method=Sync grpc.service=application.ApplicationService grpc.start_time="2024-05-16T06:55:39Z" grpc.time_ms=34.079 span.kind=server system=grpc

[sassdavid]

Has it been fixed in #18194?

[abwelt]

Has it been fixed in #18194?

this has been fixed in master. Can confirm. You'll need to update your helm values to override the tag and pull latest.

[sassdavid]

2.11.1 solves this