-
Notifications
You must be signed in to change notification settings - Fork 110
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
InternalError connection reset by peer #595
Comments
@praveenrewar please triage |
Hmm, this definitely seems like an internal error which should have been caught by IsInternalError. I will take a deeper look into it to see why it's being missed. Meanwhile please do let me know if there are any details that you could share which would help me in debugging this (like kapp version, logs, etc,.) |
kapp version 0.52 (using the cli, not the kube controller) |
here is a full log:
|
@devthejo Thank you so much! We will try to figure out why this is not part of retry-able errors. |
I also have this one:
|
And this one today:
|
I think I know why you are still seeing these. isGeneralRetryableErr is used only while creating, updating or patching resources, but not while getting/listing them which is where you are getting this error. |
cc: @cppforlife |
One potential risk of retrying |
Hello, here's an example of requests that are not retried :
In my case i sometimes get |
@revolunet Thanks for sharing these. This probably is an indication that we should add the retries in the waiting stage as well. Another reason to do so would be that the default |
Describe the problem/challenge you have
Hello, sometimes I get this kind of error using kapp deploy
Describe the solution you'd like
Maybe this kind of error could be detected and retried automatically because it's a classical network error and rerun almost always solve the problem.
Anything else you would like to add:
I saw that this problem was adressed here
#258
and solved here
#278
But it's not completely solved,
maybe need to resolve at another level ?
cc @revolunet
Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.
The text was updated successfully, but these errors were encountered: