-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
Check the HTTP response code when downloading URLs #7611
Check the HTTP response code when downloading URLs #7611
Conversation
I noticed that the recent container-selinux issue on centos was reporting a hash mismatch rather than a 404. See the error message here: kubernetes#7608 and the "actual" sha1 response is that of the 404 page: ``` curl http://mirror.centos.org/centos/7/extras/x86_64/Packages/container-selinux-2.68-1.el7.noarch.rpm curl http://mirror.centos.org/centos/7/extras/x86_64/Packages/container-selinux-2.68-1.el7.noarch.rpm | shasum -a 1 ```
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.
Great idea. Thanks for the quick fix @rifelpet!
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mikesplain, rifelpet 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 |
/test pull-kops-e2e-kubernetes-aws |
/retest |
…11-origin-release-1.13 Automated cherry pick of #7611: Check the HTTP response code when downloading URLs
…11-origin-release-1.15 Automated cherry pick of #7611: Check the HTTP response code when downloading URLs
…11-origin-release-1.14 Automated cherry pick of #7611: Check the HTTP response code when downloading URLs
I noticed that the recent container-selinux issue on centos was reporting a hash mismatch rather than a 404.
See the error message here: #7608 and the "actual" sha1 reported in the current error message is that of the 404 page:
This should now report a more descriptive error message if this happens again.