-
Notifications
You must be signed in to change notification settings - Fork 3.7k
Update fetcher errors to include full registry error #11669
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
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 <derek@mcg.dev>
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. |
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.
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 In 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.