argoproj / argo-cd

Declarative Continuous Deployment for Kubernetes
https://argo-cd.readthedocs.io
Apache License 2.0
17.39k stars 5.29k forks source link

Argo CD Release v2.11.3 FATA[0005] rpc error: code = Unknown desc = error testing repository connectivity #19370

Open hbhe0316 opened 1 month ago

hbhe0316 commented 1 month ago

[root@k8s-master ~]# cat /etc/hosts 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 192.168.56.200 k8s-master 192.168.56.201 k8s-node01 192.168.56.202 k8s-node02

[root@k8s-master ~]# kubectl get pod -n argocd -o wide NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES argocd-application-controller-0 1/1 Running 1 (20h ago) 23h 10.244.85.214 k8s-node01 argocd-applicationset-controller-7987dbcb4d-hqkk5 1/1 Running 1 (20h ago) 23h 10.244.85.219 k8s-node01 argocd-dex-server-64477bb68-hmwxp 1/1 Running 1 (20h ago) 23h 10.244.58.217 k8s-node02 argocd-notifications-controller-5db6d8669d-rg899 1/1 Running 1 (20h ago) 23h 10.244.85.216 k8s-node01 argocd-redis-6cdb45bb94-jllsq 1/1 Running 1 (20h ago) 23h 10.244.58.215 k8s-node02 argocd-repo-server-767965b8cd-bnxdc 1/1 Running 1 (20h ago) 23h 10.244.58.213 k8s-node02 argocd-server-667cfb6599-w8dx7 1/1 Running 1 (20h ago) 23h 10.244.85.217 k8s-node01

[root@k8s-master ~]# argocd repo add https://gitee.com/hbhe0316/test123.git FATA[0005] rpc error: code = Unknown desc = error testing repository connectivity: Get "https://gitee.com/hbhe0316/test123.git/info/refs?service=git-upload-pack": read tcp 10.244.58.213:50860->180.76.198.225:443: read: connection reset by peer

My question: I do not know why k8s use read tcp 10.244.58.213:50860->180.76.198.225:443, 10.244.58.213 is argocd-repo-server on node02, what should I do can solve the question.

hbhe0316 commented 1 month ago

Hi brothers, What should I do now ?

hbhe0316 commented 1 month ago

[root@k8s-master 0807]# docker images REPOSITORY TAG IMAGE ID CREATED SIZE quay.io/argoproj/argocd v2.12.0 b7856bf32251 2 days ago 442MB redis 7.0.15-alpine b496c54101d9 2 months ago 32.9MB ghcr.io/dexidp/dex v2.38.0 f94213d142aa 6 months ago 98.3MB calico/kube-controllers v3.23.1 4d33632489a4 2 years ago 135MB calico/cni v3.23.1 90d97aa939bb 2 years ago 262MB calico/node v3.23.1 fbfd04bbb7f4 2 years ago 219MB registry.aliyuncs.com/google_containers/kube-apiserver v1.23.0 e6bf5ddd4098 2 years ago 135MB registry.aliyuncs.com/google_containers/kube-controller-manager v1.23.0 37c6aeb3663b 2 years ago 125MB registry.aliyuncs.com/google_containers/kube-scheduler v1.23.0 56c5af1d00b5 2 years ago 53.5MB registry.aliyuncs.com/google_containers/kube-proxy v1.23.0 e03484a90585 2 years ago 112MB registry.aliyuncs.com/google_containers/etcd 3.5.1-0 25f8c7f3da61 2 years ago 293MB registry.aliyuncs.com/google_containers/coredns v1.8.6 a4ca41631cc7 2 years ago 46.8MB registry.aliyuncs.com/google_containers/pause 3.6 6270bb605e12 2 years ago 683kB

I update argocd 2.11.3 to 2.12.0 solved the problem.