Red Hat Bugzilla – Bug 1326461
VMware provider doesn't report actual disk usage in VM details
Last modified: 2017-08-29 22:08:10 EDT
New commit detected on cfme/5.5.z: https://code.engineering.redhat.com/gerrit/gitweb?p=cfme.git;a=commitdiff;h=91a373ec6969e70f20124f9d6dc4db0c1d435e20 commit 91a373ec6969e70f20124f9d6dc4db0c1d435e20 Author: Adam Grare <agrare@redhat.com> AuthorDate: Mon Apr 11 10:15:39 2016 -0400 Commit: Adam Grare <agrare@redhat.com> CommitDate: Tue Apr 12 14:01:33 2016 -0400 Fix for used disk size not showing up on vms Fix a broken require which was throwing an exception when running SSA on a VM. This caused no XML to be returned for the disks section of VmConfig, so the "Used Size" and "Partitions Aligned" were always empty for a VM. https://bugzilla.redhat.com/show_bug.cgi?id=1326461 gems/pending/metadata/VmConfig/VmConfig.rb | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-)
New commit detected on cfme/5.5.z: https://code.engineering.redhat.com/gerrit/gitweb?p=cfme.git;a=commitdiff;h=d289fc1efd89a0f4e4320b4f1dddf65b1a76f7a0 commit d289fc1efd89a0f4e4320b4f1dddf65b1a76f7a0 Merge: d94c67a 91a373e Author: Greg Blomquist <gblomqui@redhat.com> AuthorDate: Mon Apr 25 11:07:15 2016 -0400 Commit: Greg Blomquist <gblomqui@redhat.com> CommitDate: Mon Apr 25 11:07:15 2016 -0400 Merge branch 'bz_1326461_ssa_vm_used_size' into '5.5.z' Fix for used disk size not showing up on vms Fix a broken require which was throwing an exception when running SSA on a VM. This caused no XML to be returned for the disks section of VmConfig, so the "Used Size" and "Partitions Aligned" were always empty for a VM. https://bugzilla.redhat.com/show_bug.cgi?id=1326461 Upstream PR https://github.com/ManageIQ/manageiq/pull/7865 See merge request !892 gems/pending/metadata/VmConfig/VmConfig.rb | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-)
Able to see actual disk usage for VM as well as for Datastores after running SmartStateAnalysis on it. Verified Version:- 5.5.4.0.20160426160942_629f93b
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. https://access.redhat.com/errata/RHBA-2016:1101