Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1356488 - Edit VM Pool show wrong storage domain
Edit VM Pool show wrong storage domain
Status: CLOSED CURRENTRELEASE
Product: ovirt-engine
Classification: oVirt
Component: Backend.Core (Show other bugs)
4.0.0
Unspecified Unspecified
medium Severity high (vote)
: ovirt-4.0.2
: 4.0.2
Assigned To: Shahar Havivi
sefi litmanovich
:
Depends On: 1356492
Blocks: 1081536
  Show dependency treegraph
 
Reported: 2016-07-14 05:04 EDT by Shahar Havivi
Modified: 2016-08-16 00:55 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
With this update, a new option been added to the options for a virtual machine pool for disk storage. This option allows the user to select Auto Select Disk Target, instead of a specific domain. This means that every new virtual machine in the pool will use the storage domain with the most available space.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2016-08-12 10:24:13 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Virt
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
rule-engine: ovirt‑4.0.z+
rule-engine: planning_ack+
tjelinek: devel_ack+
mavital: testing_ack+


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 60713 master MERGED Edit VM Pool always shows the first storage domain 2016-07-19 02:46 EDT
oVirt gerrit 61003 ovirt-engine-4.0 MERGED Edit VM Pool always shows the first storage domain 2016-07-19 04:40 EDT

  None (edit)
Description Shahar Havivi 2016-07-14 05:04:09 EDT
If template exists in more then one storage domain, edit vm pool always points to the first logical storage domain. (edit pool->resource allocation->disks allocation).

When increase VMs to the pool the disks will be allocated always in the first logical storage domain.
Comment 1 Red Hat Bugzilla Rules Engine 2016-07-14 05:04:47 EDT
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.
Comment 2 sefi litmanovich 2016-08-02 04:56:15 EDT
Verified with rhevm-4.0.2.3-0.1.el7ev.noarch.

1. Have 2 SDs in DC.
2. Created template.
3. Copied template disk to 2nd SD.
4. Created vm pool: in resource allocation->disks allocation choose the 2nd logical SD.
5. Edit vm pool: increase by 1 vm, verified that in 'esource allocation->disks allocation' the SD is still the 2nd.
6. Verified the new vm was created under the 2nd SD.

Note You need to log in before you can comment on or make changes to this bug.