Bug 1322764

Summary: RHEV Used storage not correct
Product: Red Hat CloudForms Management Engine Reporter: Christian Jung <cbolz>
Component: ProvidersAssignee: Oved Ourfali <oourfali>
Status: CLOSED DUPLICATE QA Contact: Ilanit Stein <istein>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.5.0CC: bodnopoz, jfrey, jhardy, obarenbo
Target Milestone: GA   
Target Release: 5.6.0   
Hardware: All   
OS: Linux   
Whiteboard: rhev
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-30 13:18:28 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1310121    
Attachments:
Description Flags
screenshot showing usage data in CFME UI
none
screenshot showing using in RHEV UI none

Description Christian Jung 2016-03-31 09:45:33 UTC 
Description of problem:
When using CFME in combination with RHEV, the "Used" storage per VM is not shown correctly. 

Although CFME detects that the VM is using Thin Provisioning, the "Used" storage always matches the "Allocated" storage.

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

How reproducible:
tested with RHEV 3.4 and RHEV 3.5

Steps to Reproduce:
1. add a RHEV provider
2. make sure there is a least one VM with "thin provisioning"
3. navigate to the VM details and check the "Datastore Allocation Summary" and "Datastore Actual Usage Summary" section

Actual results:
"Used" always matches "Allocated"

Expected results:
"Used" should match the Actual usage shown in the RHEV UI.

Additional info:
Only tested with NFS storage!
Comment 2 Christian Jung 2016-03-31 09:50:26 UTC 
Created attachment 1142133 [details]
screenshot showing usage data in CFME UI
Comment 3 Christian Jung 2016-03-31 09:51:02 UTC 
Created attachment 1142134 [details]
screenshot showing using in RHEV UI
Comment 4 Boriso 2016-05-25 11:48:24 UTC 
This bug was actually fixed by the patch for bug 1309275
Moving to ON_QA to be verified.
Comment 5 Oved Ourfali 2016-05-30 13:18:28 UTC 

*** This bug has been marked as a duplicate of bug 1309275 ***