Bug 1178532
| Summary: | ipsilon-server-install log omits essential messages | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | John Dennis <jdennis> |
| Component: | ipsilon | Assignee: | Patrick Uiterwijk <puiterwijk> |
| Status: | CLOSED UPSTREAM | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 21 | CC: | mkosek, puiterwijk, rcritten, ssorce |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-05-27 21:28:46 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: | |||
This has been fixed upsteam and is in the 1.0.0 release. |
There are many places in the python install code which look like this: print >> sys.stdout, msg, Unfortunately these messages only go to the console and are not also included in the log file. If something goes wrong in the installation and you're trying to read the log file to trace what occurred the absence of these messages is a problem. It's as if only half the information is in the log file. A lot of the time the log file only contains a stacktrace from the failed operation but very little contextual information on what preceded the operation, you have to go back the terminal session and try to correlate the different output streams.