Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Repos Inaccessible from within cluster #18187

Open
Nathan-Nesbitt opened this issue May 13, 2024 · 0 comments
Open

Repos Inaccessible from within cluster #18187

Nathan-Nesbitt opened this issue May 13, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@Nathan-Nesbitt
Copy link

Nathan-Nesbitt commented May 13, 2024

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 getting the following when adding a private repository using a PAT:

image

There's no errors in the logs, or on creation of the private repository. But when I go to create the application I get the following:

FATA[0015] rpc error: code = InvalidArgument desc = application spec for <REDACTED> is invalid: InvalidSpecError: repository not accessible: repositories not accessible: &Repository{Repo: "https://github.com/<REDACTED>", Type: "git", Name: "", Project: ""}: repo client error while testing repository: rpc error: code = Unknown desc = error testing repository connectivity: Get "https://github.com/<REDACTED>/info/refs?service=git-upload-pack": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

I was curious if this was an issue with permissions, I can navigate to the requested URL and authenticate with the USER/PAT provided and it downloads the file. I think something may be going wrong with the authentication process.

I set up the PAT auth and repo connection using these instructions.

I have ran this both in the UI via the steps, and also via the CLI using the argocd repo add command. No difference between the two.

EDIT

I tried connecting to the bitnami public repo instead, seems that I am still getting an error:

image

Unable to create application: application spec for mongodb is invalid: InvalidSpecError: repository not accessible: repositories not accessible: &Repository{Repo: "https://charts.bitnami.com/bitnami", Type: "helm", Name: "https://charts.bitnami.com/bitnami", Project: "default"}: repo client error while testing repository: rpc error: code = Unavailable desc = connection error: desc = "error reading server preface: EOF"

There's no other logs indicating what is going wrong, so curious to know if there's anything I can check?

Thanks!

To Reproduce

  1. Set up argoCD
  2. Try to add a private repository
  3. Try to create a new application

Expected behavior

The application should start

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:21:23Z
  GitCommit: d3f33c00197e7f1d16f2a73ce1aeced464b07175
  GitTreeState: clean
  GoVersion: go1.21.9
  Compiler: gc
  Platform: linux/amd64
  Kustomize Version: could not get kustomize version: exec: "kustomize": executable file not found in $PATH
  Helm Version: v3.14.2+gc309b6f
  Kubectl Version: v0.26.11
  Jsonnet Version: v0.20.0
@Nathan-Nesbitt Nathan-Nesbitt added the bug Something isn't working label May 13, 2024
@Nathan-Nesbitt Nathan-Nesbitt changed the title Private Repo Inaccessible with PAT Repos Inaccessible from within cluster May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant