Bug 1136721 - Faulty storage allocation checks when importing a VM template
Summary: Faulty storage allocation checks when importing a VM template
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: oVirt
Classification: Retired
Component: ovirt-engine-core
Version: 3.4
Hardware: Unspecified
OS: All
medium
high
Target Milestone: ---
: 3.5.0
Assignee: Vered Volansky
QA Contact: Kevin Alon Goldblatt
URL:
Whiteboard: storage
Depends On: 1053746
Blocks: 960934 1136734
TreeView+ depends on / blocked
 
Reported: 2014-09-03 07:15 UTC by Vered Volansky
Modified: 2016-02-10 18:53 UTC (History)
17 users (show)

Fixed In Version: ovirt-3.5.0_rc4
Doc Type: Bug Fix
Doc Text:
Clone Of: 1053746
: 1136734 (view as bug list)
Environment:
Last Closed: 2014-10-17 12:27:35 UTC
oVirt Team: Storage
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 33044 0 master MERGED core: ImportVmTemplateCommand storage allocation Never
oVirt gerrit 33477 0 ovirt-engine-3.5 MERGED core: Use Collections instead of Lists Never
oVirt gerrit 33478 0 ovirt-engine-3.5 MERGED core: ImportVmTemplateCommand storage allocation Never

Description Vered Volansky 2014-09-03 07:15:37 UTC 
The storage requirements for each disk in the imported template:

      | 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 2014-10-17 12:27:35 UTC 
oVirt 3.5 has been released and should include the fix for this issue.
Note You need to log in before you can comment on or make changes to this bug.