Bug 1025398
| Summary: | insufficient error reporting when configuring repositories | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Karel Volný <kvolny> |
| Component: | anaconda | Assignee: | Anaconda Maintenance Team <anaconda-maint-list> |
| Status: | CLOSED INSUFFICIENT_DATA | QA Contact: | Release Test Team <release-test-team-automation> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 7.0 | CC: | dshea, kvolny |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-12-11 15:16:58 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: | 986217 | ||
Please attach the log files from /tmp to this bug (In reply to David Shea from comment #2) > Please attach the log files from /tmp to this bug /tmp has been wiped since ... is it really needed? Yes, it's really needed, because we have no idea what's going on with this message, either. If the installation completed, the log files are in /var/log/anaconda. It's been over a month and no logs. If you can provide them, feel free to reopen the bug. |
Description of problem: Trying to set up installation source, I'm getting "Chyba při nastavování zdroje software" ("error setting repository" or something like that). This is insufficient to debug and fix the problem. Version-Release number of selected component (if applicable): latest nightly How reproducible: always Steps to Reproduce: 1. trigger some error condition while setting up repositories Actual results: all you get is "Chyba při nastavování zdroje software" ("error setting repository" or something like that) Expected results: more comprehensive error message giving a clue what is wrong, like "networking not configured" "can't resolve 'the.hostname.entered'" "server responded 404 not found" etc. Additional info: