Bug 1053752

Summary:	Faulty storage allocation checks when taking a snapshot
Product:	[Retired] oVirt	Reporter:	Allon Mureinik <amureini>
Component:	ovirt-engine-core	Assignee:	Vered Volansky <vered>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Ori Gofen <ogofen>
Severity:	high	Docs Contact:
Priority:	medium
Version:	3.4	CC:	acanan, amureini, bugs, dfediuck, eedri, gklein, jkt, lpeer, nlevinki, obasan, rbalakri, Rhev-m-bugs, scohen, vered, yeylon, ylavi
Target Milestone:	---	Keywords:	Reopened
Target Release:	3.5.2
Hardware:	Unspecified
OS:	All
Whiteboard:	storage
Fixed In Version:	ovirt-3.5.0-beta1.1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:	1053733	Environment:
Last Closed:	2015-04-29 06:17:07 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	960934, 1119022, 1193058, 1196662, 1197441

Description Allon Mureinik 2014-01-15 17:38:33 UTC

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

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

The storage requirement for taking a new snapshot, for each disk:

For new empty disks, the required space validations should be:
      | File Domain                             | Block Domain
 -----|-----------------------------------------|-------------
 qcow | 1M (header size)                        | 1G
 -----|-----------------------------------------|-------------

Comment 1 Allon Mureinik 2014-07-13 11:22:40 UTC

Fix merged to master, still requires backport to ovirt-engine-3.5 branch.

Note that this fix only covers the storage allocation checks for the missing disks. It does NOT cover allocation checks for the space required by the snapshot's memory volumes - those will be covered in bug 1119022.

Comment 2 Ori Gofen 2014-08-18 15:25:35 UTC

verified on rc1.

** The test cases didn't include multiprocessing | domains threshold changing **

Comment 3 Sandro Bonazzola 2014-10-17 12:34:14 UTC

oVirt 3.5 has been released and should include the fix for this issue.

Comment 4 Eyal Edri 2015-02-26 12:32:02 UTC

this ovirt bug was fixed during 3.5.1 cycle and is included in the build, and therefore should be verified.

Comment 5 Ori Gofen 2015-03-02 16:35:51 UTC

verified on vt14.

Comment 6 Ori Gofen 2015-03-03 09:30:49 UTC

Sorry, this was a human mistake.please ignore comment #5

Comment 7 Allon Mureinik 2015-03-19 11:43:59 UTC

vt14 is a RHEV build, which corrolates to oVirt 3.5.2.

Comment 8 Eyal Edri 2015-04-29 06:17:07 UTC

ovirt 3.5.2 was GA'd. closing current release.