Bug 1231616
Summary: | [abrt] koji: ssl.py:808:do_handshake:SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590) | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Sandro Bonazzola <sbonazzo> | ||||||||
Component: | koji | Assignee: | Mike McLean <mikem> | ||||||||
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
Severity: | unspecified | Docs Contact: | |||||||||
Priority: | unspecified | ||||||||||
Version: | 22 | CC: | dennis, fabian.arrotin, hguemar, hhorak, mikem | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | x86_64 | ||||||||||
OS: | Unspecified | ||||||||||
URL: | https://retrace.fedoraproject.org/faf/reports/bthash/f9b46f655789a64ce54a401fbcabdee53ab12282 | ||||||||||
Whiteboard: | abrt_hash:36f35da304805620d59249aea51d399b55536111 | ||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2016-07-19 14:50:12 UTC | Type: | --- | ||||||||
Regression: | --- | Mount Type: | --- | ||||||||
Documentation: | --- | CRM: | |||||||||
Verified Versions: | Category: | --- | |||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||
Embargoed: | |||||||||||
Attachments: |
|
Description
Sandro Bonazzola
2015-06-15 05:35:43 UTC
Created attachment 1038769 [details]
File: backtrace
Created attachment 1038770 [details]
File: environ
I think this issue is related to python. If downgrade to F21 python package (2.7.8), it does not fail on F22 and F23. Created attachment 1075613 [details]
Workaround to make koji client working against CBS instance when using python >= 2.7.9
Needs CBS admin input, I don't get why the same koji client works fine with Fedora Koji instance and not CBS. This could a configuration issue.
The workaround works for me as well. Just to add that the current certificate presented by that koji instance doesn't seem to be the right one : it's CN is actually "kojihub" which isn't correct and so doesn't match with hostname cbs.centos.org, reason why python complains (and for a good reason) Just to verify : can someone update is local resolver ( /etc/hosts is fine) with 66.187.224.194 kojihub and then ~/.koji/config with kojihub instead of cbs.centos.org and verify that "koji moshimoshi" then works fine without that patch ? Well, when I try the "koji moshimoshi", I get correct output even without changing the host. What doesn't work for me is for example "koji list-targets". So, I've added "66.187.224.194 kojihub" into /etc/hosts and used the following values in the koji config: server = https://kojihub/kojihub/ weburl = https://kojihub/koji topurl = https://kojihub/kojifiles But I still get the same output for both "koji moshimoshi" (works) and "koji list-targets", which prints: SSLError: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590) Just worth noting that the distributed/given config has http://cbs.centos.org/{kojihub,koji,kojifiles} and not https. I know it can be confusing, as we give a http url, but then koji switches to TLS for cert validation. Just curious, why have you updated your config to not be the same given by the guy maintaining that koji environment ? Can you give it a try please ? Also worth noting that we'll also change all the current Koji TLS cert validation once we'll migrate to FAS (and it's now ready) so all those bad certs will go away (as it's true that there is still an misconfiguration issue at the cbs/koji level) This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component. Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |