-
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
base-images: Use https for yum repo #14451
base-images: Use https for yum repo #14451
Conversation
buildlogs.centos.org is now on https. yum failed to follow the http to https redirect, so change the URL to https to avoid the redirect: http://buildlogs.centos.org/centos/7/paas/x86_64/openshift-origin36/repodata/repomd.xml: [Errno 14] HTTPS Error 302 - Found
Just to comment on this : we always had redirect in place for more than one year (just for the CDN backend) and we enforced https already on Jan 30 2017 (just had a look at puppet/git) |
The problem with handling redirects in yum is only an issue when there's a TLS content inspection proxy in place. Still, the site is now https so there's no point in having it use http in the config file. |
[test] |
@chlunde thanks for the contribution! Let's see this pass tests and merge. Would you mind doing PRs to the |
Evaluated for origin test up to 1684e8f |
continuous-integration/openshift-jenkins/test SUCCESS (https://ci.openshift.redhat.com/jenkins/job/test_pull_request_origin/2017/) (Base Commit: c824f5c) |
[merge][severity: bug] |
Evaluated for origin merge up to 1684e8f |
continuous-integration/openshift-jenkins/merge SUCCESS (https://ci.openshift.redhat.com/jenkins/job/merge_pull_request_origin/933/) (Base Commit: 1257438) (Extended Tests: bug) (Image: devenv-rhel7_6333) |
buildlogs.centos.org is now on https. yum failed to follow the
http to https redirect, so change the URL to https to avoid the redirect: