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.
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:
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.
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: