Bug 1053744 - Faulty storage check when adding a template from a VM with disks
Summary: Faulty storage check when adding a template from a VM with disks
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: 3.4
Hardware: Unspecified
OS: All
medium
medium
Target Milestone: ---
: 3.5.1
Assignee: Vered Volansky
QA Contact: Aharon Canan
URL:
Whiteboard: storage
Depends On: 1053742
Blocks: 1178011 1193195
TreeView+ depends on / blocked
 
Reported: 2014-01-15 17:20 UTC by Allon Mureinik
Modified: 2016-02-10 19:43 UTC (History)
15 users (show)

Fixed In Version: ovirt-3.5.1_rc1
Clone Of: 1053742
: 1178011 (view as bug list)
Environment:
Last Closed: 2015-01-19 07:13:24 UTC
oVirt Team: Storage
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 15378 0 master MERGED core: AddVmTemplateCommand storage allocation Never
oVirt gerrit 33695 0 ovirt-engine-3.5 MERGED core: AddVmTemplateCommand storage allocation Never

Description Allon Mureinik 2014-01-15 17:20:22 UTC
+++ This bug was initially created as a clone of Bug #1053742 +++

+++ This bug was initially created as a clone of Bug #1053704 +++

+++ This bug was initially created as a clone of Bug #960934 +++

Description of problem:

For each disk of the template, the required space validations should be:
      | File Domain                             | Block Domain
 -----|-----------------------------------------|-------------
 qcow | preallocated : 1.1 * disk capacity      |1.1 * min(used ,capacity) 
      | sparse: 1.1 * min(used ,capacity)       |
 -----|-----------------------------------------|-------------
 raw  | preallocated: disk capacity             |disk capacity
      | sparse: min(used,capacity)

Comment 1 Sandro Bonazzola 2015-01-15 14:15:19 UTC
This is an automated message: 
This bug should be fixed in oVirt 3.5.1 RC1, moving to QA

Comment 2 Aharon Canan 2015-01-19 07:13:24 UTC
verified downstream already


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