Helm OCI repository is in 'Failed' condition, if it has been created with k8s secret.

[kvendingoldo]

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

The OCI repository connection failed when I added it for the first time via Kubernetes Secrets. It will not be updated to the "Successful" state unless I manually create it and then re-create it using secret.
I checked my secret and the secret that ArgoCD generated automatically after adding the repository via the UI. The Base64 values are identical.

To Reproduce

1. Create OCI Helm repository via K8S secret
2. Check that the repository status is 'Failed'
3. Delete K8S secret
4. Create repository with the same options manually via ArgoCD UI
5. Check that the repository status is 'Successful'
6. Delete repository via UI
7. Re-apply K8S secret
8. Check that the repository status is 'Successful'

Expected behavior

1. Repository status should be Successful, if I add repository via K8S Secret without any additional operations

Screenshots

Version

v2.13.1+af54ef8

Logs

time="2025-02-05T14:39:15Z" level=info msg=Trace args="[helm registry login XXYY.com --username ****** --password ******" dir=/tmp/helm1192506191 operation_name="exec helm" time_ms=232.556344
time="2025-02-05T14:39:15Z" level=error msg="finished unary call with code Unknown" error="error testing repository connectivity: error logging into OCI registry: failed to login to registry: failed to get command args to log: `helm registry login XXYY.com --username ****** --password ******` failed exit status 1: WARNING: Using --password ****** the CLI is insecure. Use --password-stdin.\nError: Get \"https://XXYY.com/v2/\": unauthorized:" grpc.code=Unknown grpc.method=TestRepository grpc.service=repository.RepoServerService grpc.start_time="2025-02-05T14:39:14Z" grpc.time_ms=232.933 span.kind=server system=grpc