Bug 913452 - [webadmin] After template is deleted quota storage resources are not released.
Summary: [webadmin] After template is deleted quota storage resources are not released.
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-webadmin-portal
Version: 3.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3.2.0
Assignee: ofri
QA Contact: Ondra Machacek
URL:
Whiteboard: sla
Depends On:
Blocks: 917401
TreeView+ depends on / blocked
 
Reported: 2013-02-21 09:41 UTC by Ondra Machacek
Modified: 2016-02-10 20:15 UTC (History)
8 users (show)

Fixed In Version: sf9
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
oVirt Team: SLA
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
engine.log (28.97 KB, application/octet-stream)
2013-02-21 09:41 UTC, Ondra Machacek
no flags Details


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 12396 0 None None None Never

Description Ondra Machacek 2013-02-21 09:41:47 UTC
Created attachment 700415 [details]
engine.log

Description of problem:
After template is deleted quota storage resources are not released.

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


How reproducible:
always sf7

Steps to Reproduce:
1. Create quota with storage limit 30GB.
2. Create vm with disk[5GB].
3. Make template from this vm.
4. Remove template.
  
Actual results:
After template is removed quota storage resources are same as if template still exists.

Expected results:
Quota storage resources are released.


Additional info:
In db is correct value, so seems as ui problem:
select storage_size_gb_usage from quota_global_view;

 storage_size_gb_usage 
-----------------------
                     5

Comment 1 Itamar Heim 2013-06-11 09:09:32 UTC
3.2 has been released

Comment 2 Itamar Heim 2013-06-11 09:09:32 UTC
3.2 has been released

Comment 3 Itamar Heim 2013-06-11 09:37:33 UTC
3.2 has been released


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