Description of problem: it would be nice if we can pass correlation id param in to otopi logs so we can correlate between engine and vdsm.
Good idea. commit 956b9ccda2db345630ebb6c149d40c56a137b14c Author: Alon Bar-Lev <alonbl> Date: Tue Jan 22 21:42:10 2013 +0200 host-deploy: utilize engine correlation id 1. Apply correlation id to events. 2. Add correlation id to deploy log file name. 3. Add correlation id eye catcher to otopi environment, it is ignored by otopi and ovirt-host-deploy, but usable for debugging. Bug-Url: https://bugzilla.redhat.com/show_bug.cgi?id=902949 Change-Id: I5dba5b6d1319f0b4caa6f0d3e77683a098df31e5 Signed-off-by: Alon Bar-Lev <alonbl> http://gerrit.ovirt.org/#/c/11287/1
verified on sf8: host-deploy log 2013-02-27 11:03:50 DEBUG otopi.context context.dumpEnvironment:401 ENV OVIRT_ENGINE/correlationId=str:'a8188' engine log 2013-02-26 23:05:57,299 INFO [org.ovirt.engine.core.bll.InstallVdsCommand] (pool-3-thread-50) [a8188] After Installation host gold-vdsc, VDS
3.2 has been released