Created attachment 1434482 [details] screenshot Description of problem: Persistent Volumes Report outputs Capacity in hash Version-Release number of selected component (if applicable): 5.9.2 How reproducible: Always Steps to Reproduce: 1. Create a report utilizing Persistent Volumes 2. Use Capacity as one of the columns 3. Actual results: You get a hash instead of just the number: Capacity {:storage=>10737418240} Can also look at example in attached screenshot Expected results: You just get the number. Additional info: It also just fails to find any records if you try to use the format "Suffixed Bytes"
https://github.com/ManageIQ/manageiq/pull/17412
New commit detected on ManageIQ/manageiq/master: https://github.com/ManageIQ/manageiq/commit/3083fcf6d3cc25de52812623d6286d68136a2c01 commit 3083fcf6d3cc25de52812623d6286d68136a2c01 Author: Yuri Rudman <yrudman> AuthorDate: Fri May 11 14:43:27 2018 -0400 Commit: Yuri Rudman <yrudman> CommitDate: Fri May 11 14:43:27 2018 -0400 added virtual column :storage which is entry in serialized Hash column :capacity. It will allow to show storage value on report as inumber instead of Hash entry. Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1576922 app/models/persistent_volume.rb | 6 + 1 file changed, 6 insertions(+)
Created attachment 1490433 [details] Tested on 5.10.0.18
NOT FIXED. Tested on version: 5.10.0.18.20181003162715_dfcff5a. See attachment - https://bugzilla.redhat.com/attachment.cgi?id=1490433
Parthvi, Fix added new column available for report - "storage". There were no any changes on "Capacity" column. Please take a look at screenshot in https://github.com/ManageIQ/manageiq/pull/17412, It shows old not modified column "Capacity" and new one - "Storage"
Created attachment 1492041 [details] 5.10.0.18 verified bug
Hey Yuri, I verified the bug again on 5.10.0.18.20181003162715_dfcff5a. I didn't realize I had to add a new column `Storage Capacity` to the report. My bad. But looks like the bug has been fixed. Thanks, Parthvi
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/RHSA-2019:0212