Description of problem: In the webadmin when adding a new vm pool the prestarted vms option is blocked and open only after creation when editing the pool. In API you can create a vm pool and set the number of prestarted_vms from the start: POST <vmpool> <name>test</name> <size>3</size> <cluster href= "/ovirt-engine/api/clusters/{clusted_id}" id="{clusted_id}"/> <template href= "/ovirt-engine/api/templates/{template_id}" id="{template_id}"/> <prestarted_vms>2</prestarted_vms> <max_user_vms>1</max_user_vms> </vmpool> when creating the pool this way, the 2 prestarted vms won't start up also after some waiting time, only if you edit the pool again will it invoke the start up of the vms. this might relate to this old bz: https://bugzilla.redhat.com/show_bug.cgi?id=1046421 Version-Release number of selected component (if applicable): rhevm-3.6.0-0.12.master.el6.noarch How reproducible: always Actual results: Vm pool is created with the prestarted_vms value set but no vms actually starts. Expected results: either fail the POST call with the prestarted_vms tag with a relevant error message, or allow creation with prestarted_vms and make sure that they start after creation.
Small correction to my description: when creating the pool with prestarted_vms through API, the vms will start after 5 minutes (or any set value of VmPoolMonitorIntervalInMinutes paramter).
Gil, why this is High severity? its just a mismatch between rest and ui, which happens many times (sometimes even on purpose), there is no failure in this scenario, please note that depends on the solution for bug 1046421 we might allow this in the ui as well
(In reply to Omer Frenkel from comment #2) > Gil, why this is High severity? > its just a mismatch between rest and ui, which happens many times (sometimes > even on purpose), there is no failure in this scenario, please note that > depends on the solution for bug 1046421 we might allow this in the ui as well Ok, moved to medium
I don't see any problem here. Setting prestarted_vms on pool creation works - the VMs are started after 5 minutes. VM_POOL lock now blocks editing of VM pool parameters until all VMs are created, so bug 1046421 is irrelevant. I think, setting number of prestarted VMs in the UI also can be enabled.
great, thanks! so lets enable in UI as well.
Verified with rhevm-3.6.1-0.2.el6.noarch. Created a vm pool and set prestarted vms on creation (both from UI (new option) and REST api). Both cases the pool was created successfully and the amount of defined prestarted vms were started after {VmPoolMonitorIntervalInMinutes} minutes.