Bug 660565
| Summary: | cannot send a bug report to Customer Portal when exception occurs during installation | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Masahiro Matsuya <mmatsuya> |
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
| Status: | CLOSED DUPLICATE | QA Contact: | Release Test Team <release-test-team-automation> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.0 | CC: | akozumpl |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-01-06 14:13:56 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: | |||
|
Description
Masahiro Matsuya
2010-12-07 06:30:06 UTC
What installation method was used when this was reproduced (DVD, NFS, HTTP, etc)? I used http installation. I'm reassigning this to Anaconda. This code is using libcurl and libssl to communicate with RHT (api.access.redhat.com). The error message indicates that either libcurl or libssl within the installer can't find the CA certs, or the CA certs don't contain the needed cert for api.access.redhat.com. This code works fine on installed RHEL6. What package and what files in that package contain the certs needed? This could be a dup of 667122. Masahiro can you retest with libnsspem.so in /usr/lib* directory of the install image? The howto-do-that is described here: https://bugzilla.redhat.com/show_bug.cgi?id=667122#c8 Thanks. Ales Hi Ales, I added libnsspem.so into install.img, and I confirmed I could report a bug to Customer Portal without any errors. Thanks! Masahiro *** This bug has been marked as a duplicate of bug 667122 *** Masahiro, Thanks for confirming this. The 667122 fix (and thus fix for this bug) is coming soon. |