teamhephy / workflow

Hephy Workflow - An open source fork of Deis Workflow - The open source PaaS for Kubernetes.
MIT License
410 stars 37 forks source link

ssh_exchange_identification: read: Connection reset by peer #107

Closed eugenewww closed 4 years ago

eugenewww commented 4 years ago
$ git push deis-staging master
ssh_exchange_identification: read: Connection reset by peer
fatal: Could not read from remote repository.

Workflow was installed 2 years ago on GKE. How can I debug it and resolve the issue? This issue happened several days ago.

eugenewww commented 4 years ago

Looks like this issue is related to teamhephy/builder. Should I open the issue there and close it here?

Cryptophobia commented 4 years ago

Looks like an ssh connectivity problem. Can you check the SSH key that you are using is valid in pushing to the git deis-builder remote?

Also, it could be that the IP or domain has not changed for the deis-builder git remote:

git remote get-url deis-staging

Another thing to check is to see if the deis remote url is correct and the name of the app is still correct in the above output.

Also check if the deis-builder is up and running:

kubectl get pods -n deis | grep -i "deis-builder"
eugenewww commented 4 years ago

Hi @Cryptophobia. Key is correct. Remote is correct. I can't deploy changes for any app. No one from my team can do it too.

$ kubectl get pods -n deis | grep -i "deis-builder"
deis-builder-1364651073-tmkzz                            0/1     CrashLoopBackOff   2107       548d
Снимок экрана 2019-11-17 в 18 44 26 Снимок экрана 2019-11-17 в 18 44 56 Снимок экрана 2019-11-17 в 18 45 59
eugenewww commented 4 years ago

$ kubectl --namespace=deis logs deis-builder-1364651073-tmkzz 2019/11/17 19:29:17 Error creating storage driver (googleapi: got HTTP response code 400 with body: )

Cryptophobia commented 4 years ago

This seems to be the same error some users are experiencing with deis-builder on off-cluster Google Storage objectstore. Some of them have migrated to S3 in order to mitigate the issue while it is being investigated by the Google Cloud support team.

Are you able to join our Slack channel and see what the latest is on this issue? https://slack.teamhephy.com

eugenewww commented 4 years ago

@Cryptophobia thanks.

Cryptophobia commented 4 years ago

Haven't heard any more information related to this issue so I will go ahead and close it for now. Join our Slack or report another issue if this persists.