Description of problem:
VM is stuck in power down state since it don't have host.
Version-Release number of selected component (if applicable):
oVirt Engine Version: 3.6.0-0.0.master.20150519172219.git9a2e2b3.el6
How reproducible:
Set VM to power off from GUI
Actual results:
VM is stuck in power off
Expected results:
VM down
Additional info:
From Engine log: FullListVDSCommandParameters return empty after destroy VM.
2015-06-10 10:38:21,434 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (org.ovirt.thread.pool-12-thread-36) [5fb9ab8e] START, DestroyVDSCommand(HostName = 10.35.160.45, DestroyVmVDSCommandParameters:{runAsync='true', hostId='186153a7-9837-456c-bbb0-655462517c64', vmId='b99b6152-0455-43c3-ab91-fba56fcc9b28', force='false', secondsToWait='0', gracefully='false', reason=''}), log id: 5ae5a60f
2015-06-10 10:38:21,856 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FullListVdsCommand] (DefaultQuartzScheduler_Worker-13) [1875c06e] START, FullListVdsCommand(HostName = , FullListVDSCommandParameters:{runAsync='true', hostId='186153a7-9837-456c-bbb0-655462517c64', vds='Host[,186153a7-9837-456c-bbb0-655462517c64]', vmIds='[b99b6152-0455-43c3-ab91-fba56fcc9b28]'}), log id: 6a0948dd
2015-06-10 10:38:21,857 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (org.ovirt.thread.pool-12-thread-36) [5fb9ab8e] FINISH, DestroyVDSCommand, log id: 5ae5a60f
2015-06-10 10:38:21,867 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FullListVdsCommand] (DefaultQuartzScheduler_Worker-13) [1875c06e] FINISH, FullListVdsCommand, return: [], log id: 6a0948dd
currently looks like a race between vm monitoring and stop vm
suspect is VmAnalyzer.prepareGuestAgentNetworkDevicesForUpdate()
that saves the vdsmVm to the db which is wrong because the host parameter is not initialized there.
in addition to the referenced patch (ovirt gerrit 42552)
the following patch might be related as it introduce sync between monitoring and commands that change vm dynamic data:
gerrit.ovirt.org/41520
Description of problem: VM is stuck in power down state since it don't have host. Version-Release number of selected component (if applicable): oVirt Engine Version: 3.6.0-0.0.master.20150519172219.git9a2e2b3.el6 How reproducible: Set VM to power off from GUI Actual results: VM is stuck in power off Expected results: VM down Additional info: From Engine log: FullListVDSCommandParameters return empty after destroy VM. 2015-06-10 10:38:21,434 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (org.ovirt.thread.pool-12-thread-36) [5fb9ab8e] START, DestroyVDSCommand(HostName = 10.35.160.45, DestroyVmVDSCommandParameters:{runAsync='true', hostId='186153a7-9837-456c-bbb0-655462517c64', vmId='b99b6152-0455-43c3-ab91-fba56fcc9b28', force='false', secondsToWait='0', gracefully='false', reason=''}), log id: 5ae5a60f 2015-06-10 10:38:21,856 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FullListVdsCommand] (DefaultQuartzScheduler_Worker-13) [1875c06e] START, FullListVdsCommand(HostName = , FullListVDSCommandParameters:{runAsync='true', hostId='186153a7-9837-456c-bbb0-655462517c64', vds='Host[,186153a7-9837-456c-bbb0-655462517c64]', vmIds='[b99b6152-0455-43c3-ab91-fba56fcc9b28]'}), log id: 6a0948dd 2015-06-10 10:38:21,857 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.DestroyVDSCommand] (org.ovirt.thread.pool-12-thread-36) [5fb9ab8e] FINISH, DestroyVDSCommand, log id: 5ae5a60f 2015-06-10 10:38:21,867 INFO [org.ovirt.engine.core.vdsbroker.vdsbroker.FullListVdsCommand] (DefaultQuartzScheduler_Worker-13) [1875c06e] FINISH, FullListVdsCommand, return: [], log id: 6a0948dd