Bug 1450213
| Summary: | python-urllib3 possibly not up to date in EL repo - SSL error with default ca cert path | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Shreyas Bhat <shreyb> | ||||
| Component: | python-urllib3 | Assignee: | Python Maintainers <python-maint> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Anna Khaitovich <akhaitov> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 7.3 | CC: | akhaitov, bnater, cstratak, hhorak, pviktori, riehecky, shreyb | ||||
| Target Milestone: | rc | ||||||
| Target Release: | --- | ||||||
| Hardware: | noarch | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | python-urllib3-1.10.2-4.el7 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2018-04-10 11:45:16 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1465891 | ||||||
| Attachments: |
|
||||||
|
Description
Shreyas Bhat
2017-05-11 20:52:47 UTC
Hello. You are correct in that. The correct path for RHEL for the certificates should be "/etc/ssl/certs/ca-bundle.crt", however urllib3 searches at "/etc/ssl/certs/ca-certificates.crt" This is due to a downstream modification for bug 855320 , however when the path changed [0], the fix for it did not propagate into RHEL. This is easy to test it as well. You can go to /usr/lib/python2.7/site-packages/urllib3 , remove the connectionpool.pyc and .pyo files and modify the lines at connectionpool.py as indicated by [0]. Your script should work by then. [0] http://pkgs.fedoraproject.org/cgit/rpms/python-urllib3.git/commit/?id=4670672fa3bc24459a1a4468ab073a102f4d4a1c Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2018:0731 |