Bug 917387 – If quota limits are changed, when disk is moving between storagedomains, then exceed value is remembered.

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 917387 - If quota limits are changed, when disk is moving between storagedomains, then exceed value is remembered.

Summary:	If quota limits are changed, when disk is moving between storagedomains, then...

Status:	CLOSED NEXTRELEASE

Aliases:	None

Product:	Red Hat Enterprise Virtualization Manager
Classification:	Red Hat
Component:	ovirt-engine (Show other bugs)
Sub Component:
Version:	3.2.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity unspecified
Target Milestone:	---
Target Release:	3.2.0
Assigned To:	ofri
QA Contact:	Ondra Machacek
Docs Contact:

URL:
Whiteboard:	sla
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2013-03-03 15:18 EST by Ondra Machacek
Modified:	2016-02-10 15:18 EST (History)
CC List:	12 users (show)

See Also:
Fixed In Version:
Doc Type:	Release Note
Doc Text:	When moving a disk between two storage domains with different quotas (or the same quota set for each specific storage domain) the source quota resources are released while the destination quota resources are consumed. If the quota is refreshed or edited, or if the engine is restarted, the quota accounting is rolled back until the move operation is done.
Story Points:	---
Clone Of:
Environment:
Last Closed:	2013-04-18 03:30:27 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	SLA
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Flags:	sgrinber: Triaged+

Attachments	(Terms of Use)
engine.log (19.83 KB, application/octet-stream) 2013-03-03 15:18 EST, Ondra Machacek	no flags	Details
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
oVirt gerrit	13559	None	None	None	Never

Groups: None (edit)

Description Ondra Machacek 2013-03-03 15:18:00 EST

Created attachment 704638 [details]
engine.log

Description of problem:


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

How reproducible:
always

Steps to Reproduce:
1. Create SD1 and SD2.
2. Create quota with storage limit SD1 to 10GB and SD2 to unlimited.
3. Set DC to enforce mode.
4. Create 10GB disk on SD1.
5. Move disk from SD1 to SD2.
6. Right after move action begin, change quota SD1 storage value to 5GB.
  
Actual results:
After disk is moved quota storage resources are still exceeded on SD1.

Expected results:
SD1 should be have quota storage resources freed.

Additional info:

Comment 1 ofri 2013-04-04 02:57:48 EDT

Please refer to bz#917382.
Quota consumption and release are calculated only at the end of the move process.

Fixed in the patch: the correct status of the quota will be shown even if no change is done to the quota limitations.

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