ArgoCD fails initial refresh (resync) from private repos after clean install despite having secrets inplace

[spkane]

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 included the argocd server version.

Describe the bug

I am installing ArgoCD (v2.4.2 via chart v4.9.8) via Helm and Terraform into a brand new EKS cluster, that already has an "argocd" namespace created which contains a kubernets secret for a private Github repo.

An ArgoCD application using the App of Apps model is also installed.

ArgoCD fails to refresh the repo the first time, and then must wait for the app resync period to pass before trying again.

That first refresh should work, as going into the UI and simply forcing a refresh works just fine.

To Reproduce

• create the argocd namespace
• Apply a Github App secret for access to a private Github Repo into the namespace
• Install ArgoCD via the helm chart
• Immediately after helm completes, install an ArgoCD application that points at the private Github repo.
• The application will be stuck in an unknown state, as the initial refresh fails.
• Going to the UI and forcing a refresh will fix it, or waiting for the app resync period to pass.

Expected behavior

The very first app refresh should work

Screenshots

Version

v2.4.2

Logs

Paste any relevant application logs here.