Bug 883932 - Include traceback to anaconda.log
Include traceback to anaconda.log
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Samantha N. Bueno
Fedora Extras Quality Assurance
Depends On:
Blocks: fedora19rtt
  Show dependency treegraph
Reported: 2012-12-05 10:39 EST by Pavel Holica
Modified: 2014-02-05 08:35 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2014-02-05 08:35:13 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Pavel Holica 2012-12-05 10:39:37 EST
Description of problem:
When anaconda reaches traceback, it's not in anaconda log.

Version-Release number of selected component (if applicable):

Additional info:
Including such behaviour makes debugging and reporting much easier. I'm aware that there is /tmp/anaconda-tb-* file, but in previous versions, anaconda included this traceback to anaconda.log in previous versions.
Comment 1 Chris Lumens 2012-12-05 13:33:02 EST
A complete /tmp/anaconda-tb-* file will also include anaconda.log, so I'm not sure that we really need to do anything.  That one file contains all the information.
Comment 2 Pavel Holica 2012-12-06 02:14:58 EST
I believe, you misunderstood me. As I stated in description, I'm aware of anaconda.log being in /tmp/anaconda-tb-* (along with traceback).
But this bug is about having traceback (not whole /tmp/anaconda-tb-* file) in anaconda.log so that one, using anamon watching anaconda.log can see the traceback.
This is how it was in previous versions of anaconda and this behaviour was great. Please consider including such feature back to anaconda.
Comment 3 Fedora End Of Life 2013-12-21 04:38:59 EST
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 08:35:18 EST
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

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.