Bug 835794 - Log configuration for config-tool should be improved
Summary: Log configuration for config-tool should be improved
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-config
Version: 3.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.1.0
Assignee: Yair Zaslavsky
QA Contact: Pavel Stehlik
URL:
Whiteboard: infra
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-27 07:03 UTC by Yair Zaslavsky
Modified: 2016-02-10 19:04 UTC (History)
5 users (show)

Fixed In Version: s12
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-12-04 19:58:04 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Yair Zaslavsky 2012-06-27 07:03:20 UTC
Description of problem:

A log4j file appender that will enable logging to file should be added to the log4j configuration.
The file appender should be set to DEBUG (users will be able to edit it) in order to provide by default logging to file at DEBUG level.
This can help in troubleshooting problems when running the engine-config tool.



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


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Yaniv Kaul 2012-07-02 15:03:34 UTC
Please elaborate how to test this fix.

Comment 2 Yair Zaslavsky 2012-07-02 18:58:33 UTC
A log file should be created under - /var/log/engine/engine-config and named engine.config
It should contain DEBUG entries for the engine-config tool.
Of course, It will possible to edit the log4j.xml file and to change the logging level (for example, change it to INFO) and see that debug entries are not logged anymore.

Comment 7 Yair Zaslavsky 2012-07-24 12:28:55 UTC
engine-config.log will be created under /var/log/ovirt-engine/engine-config.log

Suggested patch -

http://gerrit.ovirt.org/#/c/6569/


Note You need to log in before you can comment on or make changes to this bug.