Bug 678294

Summary:	/var/log/dracut.log is missing
Product:	Red Hat Enterprise Linux 6	Reporter:	Alexander Todorov <atodorov>
Component:	dracut	Assignee:	Harald Hoyer <harald>
Status:	CLOSED ERRATA	QA Contact:	Release Test Team <release-test-team-automation>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.1	CC:	borgan, pholica, pknirsch
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	dracut-004-40.el6	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-05-19 11:54:19 UTC	Type:	---
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:	670159

Description Alexander Todorov 2011-02-17 13:40:47 UTC

Description of problem:

# rpm -ql dracut | grep dracut.log
/var/log/dracut.log

# ls -l /var/log/dracut.log
ls: cannot access /var/log/dracut.log: No such file or directory

Version-Release number of selected component (if applicable):
dracut-004-38.el6.noarch

How reproducible:
Always


As a result dracut will not write its log to this file because it doesn't exist. If root does `touch /var/log/dracut.log' then dracut successfully writes to this file.

Also related to bug #676018.

Comment 1 Alexander Todorov 2011-02-17 14:12:31 UTC

While trying to test bug #676018. Harald instructed me to create $HOME/dracut.log before testing. 

dracut should automatically create its log files if they are not present:
/var/log/dracut.log and $HOME/dracut.log if invoked with -l.

Comment 3 Pavel Holica 2011-04-07 11:16:48 UTC

Reproduced on RHEL6.0 GA x86_64 Server.

Verified on RHEL6.1-20110330.2 x86_64 Server.
dracut-004-46.el6.noarch

Comment 6 errata-xmlrpc 2011-05-19 11:54:19 UTC

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2011-0523.html