-
Notifications
You must be signed in to change notification settings - Fork 40k
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
KEP-3926: storage.InternalError should retain the inner error #127984
KEP-3926: storage.InternalError should retain the inner error #127984
Conversation
This is so we can do proper error handling, at the same time we want to maintain backward compatibility
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the The Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/assign @sttts |
/remove-sig api-machinery |
Looks straight forward. /lgtm |
LGTM label has been added. Git tree hash: ac81790a8bcc5abab1f4afa73244927dc415ec62
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sttts, tkashem 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 |
What type of PR is this?
/kind bug
/kind cleanup
What this PR does / why we need it:
storage.InternalError
does not retain the inner error or implementUnwrap
to maintain the error tree. This PR accomplishes that.Needed for #127513, the registry layer needs to determine if the error from the storage represents a corrupt object, with proper error wrapping in place, the registry can do
errors.As(err, ...)
to determine if the error represents a corrupt object.Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:
KEP: kubernetes/enhancements#3927