Bug 692118
| Summary: | Misleading error message when using self-signed SSL certificate for repository | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Alexander Todorov <atodorov> | ||||||||
| Component: | yum | Assignee: | Nils Philippsen <nphilipp> | ||||||||
| Status: | CLOSED NOTABUG | QA Contact: | Karel Srot <ksrot> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | high | ||||||||||
| Version: | 6.1 | CC: | akozumpl, james.antill, jzeleny, kdudka, kengert, ksrot, nphilipp, ovasik, pknirsch, prc, rcritten, rwilliam, thoger | ||||||||
| Target Milestone: | rc | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | 678580 | ||||||||||
| : | 738367 (view as bug list) | Environment: | |||||||||
| Last Closed: | 2013-04-09 21:13:01 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: | |||||||||||
| Bug Depends On: | 678580, 738367 | ||||||||||
| Bug Blocks: | 670159, 705163 | ||||||||||
| Attachments: |
|
||||||||||
|
Description
Alexander Todorov
2011-03-30 13:15:09 UTC
I believe the original bug against curl has been fixed. With anaconda 13.21.107 the repo wasn't silently accepted but instead a big error message telling me that repo metadata can't be read was shown. Is it possible to show error message telling the user that the SSL certificate of the repository is not trusted instead of showing a generic read error? Big error message? What exactly? Did you try libcurl verbose mode? I've just realized this bug is against Anaconda. Feel free to ignore my questions if this is not about libcurl... atodorov, Can you see if RHEL 6.1 GA is still showing this problem? Hi David, 6.1 GA no longer silently accepts the repository but issues errors which I'm not sure a bug or not. Anaconda says unable to read metadata for the repository and when you select to "Continue" it doesn't simply ignore it but shows another error message and the user has to exit the installer. I'm attaching screenshots and a tarball of logs from stage2. Created attachment 501281 [details]
1st error message
Created attachment 501282 [details]
2nd error message
Created attachment 501283 [details]
tarball with logs from stage2
The exception is raised by yum with the explanatory error message: "Cannot retrieve repository metadata (repomd.xml) for repository: %s. Please verify its path and try again" Besides this no indication is given on why exactly the access has failed, therefore Anaconda can not do any better than displaying a generic message that access to the repo has failed and redisplaying whatever yum gave us. Reassigning to yum, yum maintainers please provide a flag in the exception or similar that will allow us to deduce that the call failed because an ssl connection with unverifiable peer certificate has been attempted. FYI Fedora bugs: 738566 - python-urlgrabber 738367 - yum 738568 - anaconda Given that this likely requires backports for libcurl/pycurl and urlgrabber, and maybe yum. How late it is in RHEL-6, and how little it should happen in real life, I'm going to close this. It should be fixed in RHEL-7. |