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
name is reserved: give more informative error #4002
name is reserved: give more informative error #4002
Conversation
even if cri-o perfectly cleans up its state after failures, name is reserved errors are still possbile. Mainly: when cri-o times out attempting to provision networking or disk resources. Given this is the most likely scenerio, print this as a debug message, rather than the cryptic "name is reserved" Signed-off-by: Peter Hunt <pehunt@redhat.com>
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: haircommander The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
| @@ -529,7 +529,7 @@ func (s *Server) CreateContainer(ctx context.Context, req *pb.CreateContainerReq | |||
| } | |||
|
|
|||
| if _, err = s.ReserveContainerName(ctr.ID(), ctr.Name()); err != nil { | |||
| return nil, errors.Wrap(err, "reserving container name") | |||
| return nil, errors.Wrap(err, "Kubelet may be retrying requests that are timing out in CRI-O due to system load") | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should retain the original error. Is it contained in the wrapped err?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah it says error reserving pod name %s for id %s: %v or container
/retest |
Codecov Report
@@ Coverage Diff @@
## master #4002 +/- ##
=======================================
Coverage 40.76% 40.76%
=======================================
Files 109 109
Lines 8876 8876
=======================================
Hits 3618 3618
Misses 4928 4928
Partials 330 330 |
|
/lgtm |
|
/retest |
|
LGTM |
|
/test integration_rhel |
|
|
/retest |
|
/test e2e-aws |
|
LGTM |
|
/test e2e-aws |
|
/retest |
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
even if cri-o perfectly cleans up its state after failures, name is reserved errors are still possbile.
Mainly: when cri-o times out attempting to provision networking or disk resources.
Given this is the most likely scenerio, print this as a debug message, rather than the cryptic "reserving * name"
Which issue(s) this PR fixes:
Special notes for your reviewer:
Does this PR introduce a user-facing change?