Description of problem: ERROR message showed in engine.log as INFO message For example: 2013-09-16 09:48:17,553 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (DefaultQuartzScheduler_Worker-22) Correlation ID: null, Call Stack: null, Custom Event ID: -1, Message: VM vm_1 is down. Exit message: internal error process exited while connecting to monitor: ((null):21350): Spice-Warning **: reds.c:3236:reds_init_ssl: Could not load certificates from /etc/pki/vdsm/libvirt-spice/server-cert.pem failed to initialize spice server. Version-Release number of selected component (if applicable): rhevm - is14, rhel6.5 host - vdsm-4.12.0-127.gitedb88bf.el6ev.x86_64, rhel6.5 How reproducible: Always for this error case Steps to Reproduce: 1. try to run vm on host with spice as console 2. 3. Actual results: ERROR message showed in engine.log as INFO message Expected results: ERROR message showed in engine.log as ERROR message Additional info:
Artyom, When does is this message triggered, on what event? Does the VM actually start/running ?
Message triggered when I try to start vm, vm is not running it's bug that up this message: https://bugzilla.redhat.com/show_bug.cgi?id=1008328
The descision if to generate a INFO or ERROR event depends on the way the VM went down , if it failed to run or failed after migration , it will be logged as an ERROR message , if Vm moved safely to down status it will be and INFO message This status is kep inside the VmDynamic class ExitStatus property. In other words, the message relates to the status of the VM after getting to the DOWN state.