Created attachment 1500058 [details] evm.log Description of problem: If the 'Storage Allocated Rate' field is included in a vm chargeback report, then report generation fails, with a traceback in evm.log (full traceback attached to BZ): [----] W, [2018-11-01T11:25:45.466379 #11829:93af80] WARN -- : <AuditFailure> MIQ(Async.rescue in _async_generate_table) userid: [admin] - invalid value for Float(): "1.0/1.0" [----] E, [2018-11-01T11:25:45.469593 #11829:93af80] ERROR -- : MIQ(MiqQueue#deliver) Message id: [82718], Error: [invalid value for Float(): "1.0/1.0"] [----] E, [2018-11-01T11:25:45.469757 #11829:93af80] ERROR -- : [ArgumentError]: invalid value for Float(): "1.0/1.0" Method:[block (2 levels) in <class:LogProxy>] [----] E, [2018-11-01T11:25:45.469900 #11829:93af80] ERROR -- : /opt/rh/cfme-gemset/bundler/gems/cfme-ui-classic-75b755f67a94/app/helpers/number_helper.rb:53:in `Float' /opt/rh/cfme-gemset/bundler/gems/cfme-ui-classic-75b755f67a94/app/helpers/number_helper.rb:53:in `handling_negatives' /opt/rh/cfme-gemset/bundler/gems/cfme-ui-classic-75b755f67a94/app/helpers/number_helper.rb:4:in `number_to_human_size' /var/www/miq/vmdb/app/models/miq_report/formatting.rb:122:in `format_bytes_to_human_size' /var/www/miq/vmdb/app/models/miq_report/formatting.rb:90:in `apply_format_function' /var/www/miq/vmdb/app/models/miq_report/formatting.rb:75:in `format' Version-Release number of selected component (if applicable): 5.10.0.21 How reproducible: 100% Steps to Reproduce: 1.) Create vm chargeback report with the 'Storage Allocated Rate' field included. 2.) Run the report. Actual results: Report generation fails. Expected results: Report generation succeeds, correct rate shown in Storage Allocated Rate column. Additional info: No error occurs for the other rate-related fields (added in 5.10).
Verified on 5.11.0.11.
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-2019:4199