Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 906499

Summary:	Quota limit on the destination storage domain is not enforced when moving a disk.
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Ondra Machacek <omachace>
Component:	ovirt-engine	Assignee:	ofri <omasad>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Ondra Machacek <omachace>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.2.0	CC:	acathrow, dfediuck, dyasny, iheim, lpeer, Rhev-m-bugs, sgrinber, yeylon, ykaul
Target Milestone:	---	Keywords:	Reopened
Target Release:	3.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	sla
Fixed In Version:	sf9	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-13 14:54:36 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	SLA	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	917401

Description Ondra Machacek 2013-01-31 17:52:07 UTC

Description of problem:


Version-Release number of selected component (if applicable):
3.3.0-0.1

How reproducible:
always

Steps to Reproduce:
1. Create two SDs. SD1, SD2.
2. Create quota, with limit SD1 20GB, SD2 5GB.
3. Set DC to enforced mode.
4. Create disk 10GB disk on SD1.
5. Move disk from SD1 to SD2.
  
Actual results:
Success.

Expected results:
Fail, not enough storage resources

Additional info:

Comment 1 Doron Fediuck 2013-02-13 14:54:36 UTC

Ondra, this is working by design.
You need to understand that quota is an upper limit (max) constraint, and not a lower one (min). It's abstracted from the physical entities, which may change over time.
For example, as a university admin, I may be able to define students quota of 50 GB, even if my storage has only 30 GB. Later on I may increase this storage regardless of quota allocations which should still function as defined.
For the same reason, on a storage with 10 GB, I may define students quota of 6 GB, and faculty quota of 6 GB. It's an upper limit and the responsibility of the admin to assure relevant resources are available when needed.

Comment 2 Ondra Machacek 2013-02-14 14:01:10 UTC

I did not decribe it right, sorry for that. For claryfing:

Steps to reproduce are same.
The issue is not that storage has not enough resources but quota has not.

So the results should be:

Actual results:
Succeeded moving 10 GB disk to a DC enfocing a 5 GB quota.

Expected results:
Fail, Quota exceeded

Comment 3 Itamar Heim 2013-06-11 08:57:32 UTC

3.2 has been released

Comment 4 Itamar Heim 2013-06-11 08:57:40 UTC

3.2 has been released

Comment 5 Itamar Heim 2013-06-11 08:57:43 UTC

3.2 has been released

Comment 6 Itamar Heim 2013-06-11 08:59:46 UTC

3.2 has been released

Comment 7 Itamar Heim 2013-06-11 09:29:17 UTC

3.2 has been released