Description of problem: There is no debug information in the engine.log to indicate which user is executing a query or action. Version-Release number of selected component (if applicable): 4.0 How reproducible: Enable debug log level and start engine Steps to Reproduce: 1. Execute a query or action Actual results: engine.log does not have debug log on which query/action is executed by user Expected results: There should be an entry in engine.log indicating that a query/action is being executed by a user
Hi, when I removed a VM, I cannot find in log which user did it. for example: 2016-04-15 15:39:47,224 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (ajp-/127.0.0.1:8702-5) [37107067] Correlation ID: 53754440, Job ID: 6ddf0b06-cc2d-44af-9a1b-223ab9acac66, Call Stack: null, Custom Event ID: -1, Message: VM foofoo was created by admin@internal. .... 2016-04-15 15:40:29,841 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-6-thread-37) [45d2fb2c] Correlation ID: 45d2fb2c, Job ID: f90bdc36-049d-459d-8013-d65e87afc507, Call Stack: null, Custom Event ID: -1, Message: VM foofoo was successfully removed. -> missing "by admin@internal"
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Its a debug log entry please test with debug enabled
Moving to ON_QA until we get feedback from Petr.
Created attachment 1156204 [details] engine log After some archaeology work, I didn't find any message in DEBUG related to missing user which deleted a VM. If you want, you can check yourself. I can provide access to a working engine with debug log level which you can use.
Sorry, I forgot to mention I'am using 3.6.6-3
Just verified that everything works fine on 3.6.6, IMO the issue during verifying the bug is caused by a bit tricky logging configuration. In order to see those debug messages following category has to be enable in ovirt-engine.xml.in: <logger category="org.ovirt.engine.core.bll"> <level name="DEBUG"/> </logger> Using the above you can see debug logs for both commands and queries, for example: 2016-05-12 10:09:19,442 DEBUG [org.ovirt.engine.core.bll.Backend] (default task-32) [] Executing command AddEmptyStoragePool for user admin@internal-authz. 2016-05-12 10:09:22,406 DEBUG [org.ovirt.engine.core.bll.Backend] (default task-54) [] Executing query GetConnectionsByDataCenterAndStorageType with isFiltered : false for user admin@internal-authz. Maybe a bit confusing is, that DEBUG logging can be turned on/off for each package (category) and we have following default in ovirt-engine.xml.in: <logger category="org.ovirt" use-parent-handlers="false"> <level name="INFO"/> ... </logger> ... <logger category="org.ovirt.engine.core.bll"> <level name="INFO"/> </logger> So if you change log level to DEBUG for category "org.ovirt", then for category "org.ovirt.engine.core.bll" it's overwritten to INFO. And to show debug logs described in the bug description, we need to have set DEBUG on category "org.ovirt.engine.core.bll" at minimum. I will try to reach Petr today, check his setup ...
Add VM command is logged, but Remove VM command isn't.
Verified on 3.6.7-1 All actions I checked had findable user id in debug log