Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 882132 - [RFE] dracut anaconda part should provide log files
Summary: [RFE] dracut anaconda part should provide log files
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 18
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Will Woods
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: fedora19rtt
TreeView+ depends on / blocked
 
Reported: 2012-11-30 08:30 UTC by Martin Banas
Modified: 2014-02-05 13:26 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-02-05 13:26:09 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Martin Banas 2012-11-30 08:30:50 UTC 
Description of problem:
Anaconda part in dracut doesn't provide any log file. (this could be useful for example for checking output while mounting nfs, etc..)

Version-Release number of selected component (if applicable):
dracut-024-10.git20121121
anaconda-18.29.2-1  

  
Actual results:
There's no log file from anaconda part of dracut

Expected results:
Anaconda part in dracut should provide a log file from it's run

Additional info:
Comment 1 Martin Banas 2012-12-12 11:58:16 UTC 
Will, any update on this bug?
Comment 2 Will Woods 2013-03-12 21:14:09 UTC 
All output from all dracut scripts gets saved in the systemd journal, so 'journalctl' will show you any logged messages from dracut while the installer is still running.

We could pretty easily write the journal (or a formatted copy thereof) to the target system's disk before rebooting. But there hasn't been any work on this.
Comment 3 Fedora End Of Life 2013-12-21 09:34:16 UTC 
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 4 Fedora End Of Life 2014-02-05 13:26:13 UTC 
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.
Note You need to log in before you can comment on or make changes to this bug.