Random 401 using hard refresh againt OCI repository

[dpiraud]

Checklist:

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

Describe the bug

When using the "hard-refresh" btn on ArgoCD, I randomly get 401 error. If no 401 error occurred, everything works fine.

We declare severals OCI repo for our HelmChart in our ArgoCD:

• all are hosted on the same OCI server
• each use a dedicated login/password with limited right on the OCI repo

registry.net/staging-team1/helm team1Login team1Password
registry.net/staging-team2/helm team2Login team2Password
registry.net//staging-team3/helm team3Login team3Password
...

It seems that ArgoCD something pick the wrong login/password: I was able to confirm this idea by changing our configuration to use the same login/password (Of a user with right on all repo) for all our ArgoCD OCI repository

registry.net/staging-team1/helm masterLogin masterPassword
registry.net/staging-team2/helm masterLogin masterPassword
registry.net/staging-team3/helm masterLogin masterPassword
...

Doing this, I get no more 401 when using "hard refresh"

Expected behavior

When i hit hard refresh, ArgoCD pick the "good" credentials of the app oci repo ( More precisely: ArgoCD should perform a "helm login" with the right creds ;) )

Screenshots

Version

2.4.4

[fe80]

Hello,

Same issue on 2.4.11

[mmerickel]

I believe the issue is with helm itself, I opened a bug report here https://github.com/helm/helm/issues/11286. You can see in the argocd-repo-server log output the trace where it does a helm registry login multiple times - if you remove the other registries then things work.

[dpiraud]

Sounds good, thx!