Description of problem: In contrast to engine-config which uses log4j.xml file from a well-defined location on the file system - (/etc/rhevm/engine-config/log4j.xml) , engine-manage-domains has no such functionality and requires log4j.xml to reside in the classpath, which currently does not take place. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: engine-manage-domains should use a log4j.xml file defined at /etc/rhevm/engine-manage-domains/log4j.xml Additional info:
QE should test the following - a. /etc/rhevm/engine-manage-domains/log4j.xml is located at the file system, and when running engine-manage-domains the log file is created at /var/log/engine/engine-manage-domains/engine-manage-domains.log b. Change log4j.xml configuration and see how it effects the log. For example - change priority value to "DEBUG" at the category of org.ovirt.engine.core.utils.kerberos
*** This bug has been marked as a duplicate of bug 825994 ***