Fixed possible NumericValueOutOfRange error on hardwares.memory_mb column

[yrudman]

Custom report was throwing error when trying to convert value frommemory_mb to bytes

https://bugzilla.redhat.com/show_bug.cgi?id=1464154

@miq-bot add-label bug

\cc @gtanzillo

[miq-bot]

@yrudman unrecognized command 'bug', ignoring...

Accepted commands are: add_label, assign, close_issue, move_issue, remove_label, rm_label, set_milestone

[miq-bot]

Checked commit yrudman@67ee4d6 with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0
1 file checked, 0 offenses detected
Everything looks fine. 🏆

[yrudman]

there is alternative solution for reported bug in ManageIQ/manageiq#15554 - Cast virtual attribute Hardware#ram_size_in_bytes to bigint.

[Fryguy]

This feels like the wrong fix for the problem. While I don't mind changing this, the current columns holds the value in MB, so the max value it can hold is 2147483647 megabytes => 2.147483647 petabytes, which is way more memory that any computer system I've ever heard of.

I think your alternative solution handles it better.

[Fryguy]

Closing in favor of ManageIQ/manageiq#15554

[yrudman]

right, for keeping value integer is OK, error thrown when trying to execute report and show virtual column defined as memory_mb * 1.megabyte ( = memory_mb * 1048576) and max value it can hold before out of range is 2147483647 / 1048576 = 2048 MB