Created attachment 609298 [details] log Description of problem: the engine log is showing only vds id in the logs. since the users do not know what the vds id is without checking the db it makes it really hard to debug. Version-Release number of selected component (if applicable): si16 How reproducible: 100% Steps to Reproduce: 1. look at commands like GetDeviceList 2. 3. Actual results: we only see vds id Expected results: vds name should be added to all commands as well as the vds id - it will make it easier to debug when there is more than one host in the cluster. Additional info: backend log example - GetDeviceList is sent to vds - how do we know which one it is? 2012-09-03 11:15:56,731 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.GetDeviceListVDSCommand] (ajp-/127.0.0.1:8009-8) [4a7e0b1f] START, GetDeviceListVDSCommand(vdsId = 8c28 9d3a-f4d7-11e1-8cda-001a4a169741, storageType=ISCSI), log id: 3acd1676
upstream patch: http://gerrit.ovirt.org/#/c/7861/ and additional fix: http://gerrit.ovirt.org/#/c/7865/
verified on si19