Red Hat Bugzilla – Bug 1309272
Value of "Used Size" field is always blank
Last modified: 2017-08-16 10:09:31 EDT
Description of problem:
In rhev, "Thin Provisioned" disks consist two sizes actual size and virtual size. The virtual Machine page in cloudforms dashboard has section named " Datastore Actual Usage Summary " but it doesnt show the correct data.
Used Size filed is always set blank due to which cloudforms doesnt show
"Percent Used of Provisioned Size"
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Add a rhev provider, Go to virtual machine tab and select a virtual machine to open its property page.
2. Look for "Datastore Allocation Summary" section, Select the "Number of Disks"
to open disk information tab.
3. Check "Percent Used of Provisioned Size" and "Used Size" fields.
"Percent Used of Provisioned Size" and "Used Size" fields are blank
"Used Size" should reflect the actual storage size utilized by disk on the storage. Percent Used of Provisioned Size should show the same value in percentage.
#qemu-img info 5360be1d-4a2c-4623-be3e-3c4e81bf22a3
file format: raw
virtual size: 10G (10737418240 bytes) < Provisioned size
disk size: 1.8G < Used size
Reproducer system :
Fixed as part of fixing bug 1309275
Verified on cfme downstream version 184.108.40.206-beta2.6.20160516171555_b1be31f.
Reproduced first on cfme 220.127.116.11.20151201120956_653c0d4,
for a rhel7.2 VM, both thin & thick disks has empty content under "Used size",
and and 0 content under "Percent Used of Provisioned Size".
However, on cfme 18.104.22.168-beta2.6.20160516171555_b1be31f,
these 2 fields seem to have a valid content, for exact same VM disks.
Created attachment 1162796 [details]
cfme 22.214.171.124 screenshot
Created attachment 1162797 [details]
cfme 126.96.36.199 screenshot
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.