Bug 1136717 - Faulty storage allocation checks when exporting a VM template
Summary: Faulty storage allocation checks when exporting 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
low
Target Milestone: ---
: 3.5.0
Assignee: Vered Volansky
QA Contact: Kevin Alon Goldblatt
URL:
Whiteboard: storage
Depends On: 1053747
Blocks: 960934
TreeView+ depends on / blocked
 
Reported: 2014-09-03 07:07 UTC by Vered Volansky
Modified: 2016-02-10 19:43 UTC (History)
18 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 1053747
Environment:
Last Closed: 2014-10-17 12:26:02 UTC
oVirt Team: Storage
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 32257 0 master MERGED core: ExportVmTemplateCommand storage allocations Never
oVirt gerrit 33049 0 ovirt-engine-3.5 MERGED core: ExportVmTemplateCommand storage allocations Never

Description Vered Volansky 2014-09-03 07:07:49 UTC 
The storage requirements for each disk in the exported VM:
(note that an export domain can only be a file domain)

 qcow | preallocated : 1.1 * disk capacity      
      | sparse: 1.1 * min(used ,capacity)       
 -----|-----------------------------------------
 raw  | preallocated: disk capacity             
      | sparse: min(used,capacity)
Comment 1 Vered Volansky 2014-09-03 08:12:59 UTC 
(In reply to Vered Volansky from comment #0)
> The storage requirements for each disk in the exported VM:
Correction: in the exported template.
Comment 2 Allon Mureinik 2014-09-18 12:52:22 UTC 
Vered, from what I can see the patch was not backported to 3.5 - moving back to POST.
Either confirm (and backport!) or refute (and add the link to the relevant patch).
Comment 3 Vered Volansky 2014-09-21 04:40:59 UTC 
Fell through the cracks, now really backported.
Comment 4 Vered Volansky 2014-09-29 08:28:32 UTC 
Moved to POST by mistake
Comment 5 Sandro Bonazzola 2014-10-17 12:26:02 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.