Bug 563009 - No logging type for "loader" messages
Summary: No logging type for "loader" messages
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ales Kozumplik
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-09 00:44 UTC by James Laska
Modified: 2014-09-30 23:38 UTC (History)
4 users (show)

Fixed In Version: anaconda-13.31
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-27 14:55:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
/tmp/anaconda.log (8.29 KB, text/plain)
2010-02-09 00:44 UTC, James Laska
no flags Details

Description James Laska 2010-02-09 00:44:15 UTC
Created attachment 389651 [details]
/tmp/anaconda.log

Description of problem:

/tmp/anaconda.log now includes a logtype in the message to indicate where the message is coming from.  For example ...

    21:48:17,253 INFO anaconda: using only installclass _Fedora
    21:48:17,377 INFO anaconda: Running kickstart %%pre script(s)
    21:48:17,601 INFO anaconda: All kickstart %%pre script(s) have been run
    21:48:17,883 INFO anaconda: ISCSID is /usr/sbin/iscsid
    21:48:17,973 INFO anaconda: no initiator set
    21:48:18,445 INFO anaconda: no /tmp/fcpconfig; not configuring zfcp

For early /tmp/anaconda.log messages, there is not logtype set.  For example ...

    21:47:48,253 INFO    : kernel command line:  updates=http://jlaska.fedorapeople.org/traceback.img stage2=http://serverbeach1.fedoraproject.org/pub/alt/stage/rawhide-testing/i386/os//images/install.img serial console=ttyS0 ks=file:/ks.cfg

    21:47:48,253 DEBUG   : no ifcfg files found in /etc/sysconfig/network-scripts
    21:47:48,253 INFO    : anaconda version 13.25 on i386 starting
    21:47:48,253 INFO    : text mode forced due to serial/virtpconsole
    ...
    21:48:13,120 INFO    : Running anaconda script /usr/bin/anaconda
    21:48:17,253 INFO anaconda: using only installclass _Fedora

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

* anaconda-13.25

How reproducible:

Everytime

Steps to Reproduce:
1. Initiate an install of rawhide  (see URL's above)
2. Proceed to stage#2
  
Actual results:

Examine /tmp/anaconda.log and note the log format for early anaconda.log messages is not set

Expected results:

Perhaps some log format for those early log messages?

Additional info:

* See attached /tmp/anaconda.log

Comment 1 Ales Kozumplik 2010-02-10 07:55:32 UTC
Yes,

I know about this. The early messages are produced by the loader (C code), that's why I haven't fixed that at the same time like the python logging. But I am going to fix it, good to have a BZ for this.

Ales

Comment 2 Ales Kozumplik 2010-02-24 09:53:47 UTC
Fixed by commit b1314ffe9f158c6b4f7c2ee39707bd60575134fb. Included since anaconda-13.31.

Comment 3 Fedora Update System 2010-02-24 18:57:27 UTC
anaconda-13.31-1.fc13 has been submitted as an update for Fedora 13.
http://admin.fedoraproject.org/updates/anaconda-13.31-1.fc13

Comment 4 Fedora Update System 2010-02-25 12:45:28 UTC
anaconda-13.31-1.fc13 has been pushed to the Fedora 13 testing repository.  If problems still persist, please make note of it in this bug report.
 If you want to test the update, you can install it with 
 su -c 'yum --enablerepo=updates-testing update anaconda'.  You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F13/FEDORA-2010-2843

Comment 5 Bug Zapper 2010-03-15 14:27:51 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 13 development cycle.
Changing version to '13'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 6 Bug Zapper 2011-06-02 16:38:10 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  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 '13'.

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 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 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 please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 7 Bug Zapper 2011-06-27 14:55:02 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.

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.