Description of problem: Shortly after creating a vmpool, before VMs creation is over, it is possible to edit vmpool, and mark VMs, as "prestarted". As a result, the VMs are not started, with error in in engine.log: "No Vms avaialable for prestarting" From engine.log: 2013-12-24 11:35:39,788 INFO [org.ovirt.engine.core.bll.VmPoolMonitor] (DefaultQuartzScheduler_Worker-7) VmPool 8bdea682-f449-458e-9993-d3d0305a9fc3 is missing 3 prestarted Vms, attempting to prestart 3 Vms 2013-12-24 11:35:39,790 INFO [org.ovirt.engine.core.bll.VmPoolMonitor] (DefaultQuartzScheduler_Worker-7) No Vms avaialable for prestarting 2013-12-24 11:35:40,059 INFO [org.ovirt.engine.core.bll.AsyncTaskManager] (DefaultQuartzScheduler_Worker-18) Polling and updating Async Tasks: 3 tasks, 3 tasks to poll now Version-Release number of selected component (if applicable): is28.1 How reproducible: Always
Created attachment 841407 [details] engine log
but afterwards, when pool is added, the vms are started automatically, right? if so, i dont think its a bug, its ok for prestarted job to fail start vms if there aren't any available at some point, as long as it keep trying and succeed when its possible.
when pool is added, the VMs are not started. There is no retry to start the VMs in the pool.
this bug won't fit into 3.5 release and is being deferred to a later release. If you deeply care about this bug and deserves to be re-evaluated please let me know
Since introduction of VM_POOL lock in UpdateVmPoolWithVmsCommand and AddVmCommand it's not possible to edit VM pool parameters before completion of all AddVm commands.