Created attachment 958020 [details] agent and vdsm logs Description of problem: Start two engine VMs on two hosts not show any info messages and fail with -243 error, because second host try to acquire sanlock to start vm, but fail, first host still hold lease. Version-Release number of selected component (if applicable): ovirt-hosted-engine-setup-1.2.1-3.el6ev.noarch How reproducible: Always Steps to Reproduce: 1. Have hosted-engine environment with two hosts 2. Run vm on first host 3. Try to run vm also on second host(hosted-engine --vm-start) Actual results: Command show create vm(vdsClient format) and no any info message, also in vdsm log I see error -243 Expected results: Info message that vm already run on another host. Additional info:
Martin, after recent changes in metadata file, what's the best way for getting the real status of the env after such error?
Sandro: what changes? the real status is still reported, we just do not know how to detect that VM could not be started because of sanlock conflict (which is not a bug in some cases). We need some improved error code reporting from libvirt to do that probably.. or logfile parsing.
*** This bug has been marked as a duplicate of bug 1150087 ***