argo-cd: v2.3.4 throws context deadline exceeded (Client.Timeout exceeded while awaiting headers)

Checklist:

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.
I’ve pasted the output of argocd version.

Describe the bug

command “argocd app create istio --repo https://github.intuit.com/services-mesh/services-mesh-release.git” throws repository not accessible

To Reproduce

On an EKS cluster after verifying the GitHub is reachable

kubectl create namespace argocd
kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml
kubectl port-forward svc/argocd-server -n argocd 8080:443
argocd login localhost:8080
argocd app create istio --repo https://github.intuit.com/services-mesh/services-mesh-release.git --path istio/yamls --dest-server https://kubernetes.default.svc --dest-namespace default

Expected behavior

application is able to get created successfully

Screenshots

Version

argocd version argocd: v2.3.4+ac8b7df BuildDate: 2022-05-18T13:00:56Z GitCommit: ac8b7df9467ffcc0920b826c62c4b603a7bfed24 GitTreeState: clean GoVersion: go1.17.9 Compiler: gc Platform: darwin/amd64 argocd-server: v2.3.4+ac8b7df BuildDate: 2022-05-18T11:41:37Z GitCommit: ac8b7df9467ffcc0920b826c62c4b603a7bfed24 GitTreeState: clean GoVersion: go1.17.10 Compiler: gc Platform: linux/amd64 Ksonnet Version: v0.13.1 Kustomize Version: v4.4.1 2021-11-11T23:36:27Z Helm Version: v3.8.0+gd141386 Kubectl Version: v0.23.1 Jsonnet Version: v0.18.0

Logs

Paste any relevant application logs here.

[0015] rpc error: code = InvalidArgument desc = application spec for istio is invalid: InvalidSpecError: repository not accessible: rpc error: code = Unknown desc = error testing repository connectivity: Get “https://github.intuit.com/services-mesh/services-mesh-release.git/info/refs?service=git-upload-pack”: context deadline exceeded (Client.Timeout exceeded while awaiting headers)

About this issue

Original URL
State: open
Created 2 years ago
Reactions: 14
Comments: 20 (2 by maintainers)

Most upvoted comments

I had the same promblem with V2.4.6, this problem is making me crack up.

argocd: v2.4.6+a48bca0
  BuildDate: 2022-07-12T22:56:26Z
  GitCommit: a48bca03c79b6d63be0c34d6094831bc6916b3bc
  GitTreeState: clean
  GoVersion: go1.18.3
  Compiler: gc
  Platform: linux/amd64
argocd-server: v2.4.6+a48bca0
  BuildDate: 2022-07-12T22:31:17Z
  GitCommit: a48bca03c79b6d63be0c34d6094831bc6916b3bc
  GitTreeState: clean
  GoVersion: go1.18.3
  Compiler: gc
  Platform: linux/amd64
  Kustomize Version: v4.4.1 2021-11-11T23:36:27Z
  Helm Version: v3.8.1+g5cb9af4
  Kubectl Version: v0.23.1
  Jsonnet Version: v0.18.0

wgzhao on Jul 22, 2022

Still no one found a solution for this issue? Then how do you add a private repo to ArgoCD?

behniafb on Oct 18, 2023

@mdfaizsiddiqui context deadline exceeded is a generic error message in golang. It can appear in many contexts. I’m guessing most folks here are getting that error when the repo-server tries to communicate with some git host.

crenshaw-dev on Mar 14, 2023