Bug 1258380
Summary: | [VM Pools][REST-API] setting prestarted vms upon vmPool creation is blocked in UI but not in API | ||
---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | sefi litmanovich <slitmano> |
Component: | ovirt-engine | Assignee: | Shmuel Melamud <smelamud> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | sefi litmanovich <slitmano> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3.6.0 | CC: | bazulay, gklein, lsurette, mavital, michal.skrivanek, rbalakri, Rhev-m-bugs, srevivo, ykaul |
Target Milestone: | ovirt-3.6.1 | ||
Target Release: | 3.6.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-04-20 01:30:41 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | Virt | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
sefi litmanovich
2015-08-31 09:02:29 UTC
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. |