Update fetcher errors to include full registry error#11669
Update fetcher errors to include full registry error#11669dmcgowan merged 1 commit intocontainerd:mainfrom
Conversation
|
Skipping CI for Draft Pull Request. |
Currently the registry error does not include details or allow the caller access to the original error body. Signed-off-by: Derek McGowan <[email protected]>
513a009 to
af068ff
Compare
|
Updated and should be ready for review. Marked as cherry-pick for 2.1 since there are currently cases in which the client cannot fully access the registry error. This also makes the error result more consistent across resolve/fetch/push. |
austinvazquez
left a comment
There was a problem hiding this comment.
Giving the thumbs up on this. Some registries are having a bad time today and causing the CI issues.
|
/cherry-pick release/2.1 |
|
@dmcgowan: new pull request created: #11997 DetailsIn response to this:
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. |
Currently the registry error does not include details or allow the caller access to the original error body.