ArgoCD When connecting to Private Repo (via HTTPS), we are getting "repository not found" #15623
Replies: 3 comments 2 replies
-
when you mean private, you mean just a repo in github, or is there a network thing? |
Beta Was this translation helpful? Give feedback.
-
If this is still active. I had the same behaviour.
Its the github.com setting for each repository. In this context, it means that the repository can only be accessed by someone within the github organisation that has been granted explicit access.
The problem occurs only the first time to try to connect to any repository configured. After you get the error when testing the connection in argocd, navigate to the github.com repositories setttings. Once this is validated, retrying the argocd connection works. Not only for this repo, but all other repositories that your Github App is permitted to access. My guess is just that the http response code and/or error message sent by Github is either misleading, or the message is poorly handled in argocd's error stack. It's a bit of an edge case. |
Beta Was this translation helpful? Give feedback.
-
I faced the same issue and found that button here: At the Repository Level under Settings -> GitHub Apps -> Configure and near 'Permissions a prompt was there asking me to review the permission change request. |
Beta Was this translation helpful? Give feedback.
-
When Connecting from ArgoCD to HTTPS GitHub Private Repo, we are getting the below error:
time="2023-09-21T13:43:56-04:00" level=fatal msg="rpc error: code = Unknown desc = error testing repository connectivity: repository not found"
When I change the repo visibility from Private to Public, the connection is working fine. But the compliance standards are we need all of our repo's to be Private.
I had the root cert added for the authentication purposes, but ArgoCD should be able to connect to Private Repo's right?
Any info here will help my cause.
Beta Was this translation helpful? Give feedback.
All reactions