New commit detected on ManageIQ/manageiq/hammer: https://github.com/ManageIQ/manageiq/commit/331132f8c8821c8d1042047aa36f6c63ea9241b6 commit 331132f8c8821c8d1042047aa36f6c63ea9241b6 Author: Jason Frey <fryguy9> AuthorDate: Wed Apr 3 15:32:44 2019 -0400 Commit: Jason Frey <fryguy9> CommitDate: Wed Apr 3 15:32:44 2019 -0400 Merge pull request #18623 from kbrock/disk_usage_report fix: swap makes vms out of disk space report false positive (cherry picked from commit 629474ca44471d34b19f0ec4682eaece5f79394e) Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1696420 product/reports/100_Configuration Management - Virtual Machines/028_VMs with Volume Free Space -= 20%.yaml | 6 +- 1 file changed, 3 insertions(+), 3 deletions(-)
Tested on 5.10.3.2. NOT FIXED.
Thank you Parthvi, The root volume on sbulage has 18.8% free. pvala has unknown volume usage. Is the expectation that sbulage is shown and pvala is hidden?
Hello Parthvi, Following up: pvala_test_rest_vm has a root partition with 0% free - this causes it to show on the report. All the VMs on the report have a partition that has less than 20% free. Please share which elements you are not expecting. The volumes are sorted by cluster and free space, and not by name. So a vm's partitions are not necessarily grouped together. This may be confusing as to why a vm would be on the list. Also, this is a vm report, so all volumes are displayed for each vm. Is the desire to convert this into a report based upon volume? (I can research if this can be done) Then all volumes over the threshold would be displayed. But only volumes. This is working as designed, but obviously not as you would like. I will track down the business owner to see how we wish this to behave. Thank you, Keenan