Created attachment 1434482 [details]
Description of problem:
Persistent Volumes Report outputs Capacity in hash
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create a report utilizing Persistent Volumes
2. Use Capacity as one of the columns
You get a hash instead of just the number:
Can also look at example in attached screenshot
You just get the number.
It also just fails to find any records if you try to use the format "Suffixed Bytes"
New commit detected on ManageIQ/manageiq/master:
Author: Yuri Rudman <firstname.lastname@example.org>
AuthorDate: Fri May 11 14:43:27 2018 -0400
Commit: Yuri Rudman <email@example.com>
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.
app/models/persistent_volume.rb | 6 +
1 file changed, 6 insertions(+)
Created attachment 1490433 [details]
Tested on 220.127.116.11
NOT FIXED. Tested on version: 18.104.22.168.20181003162715_dfcff5a.
See attachment - https://bugzilla.redhat.com/attachment.cgi?id=1490433
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]
22.214.171.124 verified bug
I verified the bug again on 126.96.36.199.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.
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.