Description of problem: When the report "Vendor and Guest OS" is run, the graph shows different valus than expected against the list. Version-Release number of selected component (if applicable): 5.3.1.10 How reproducible: always Steps to Reproduce: 1. Add some providers (vSphere and RHEV-M) 2. I think the credentials of the hosts should be set up too but I am not sure about this point. 3. Run the 'Configuration Management/Virtual Machines/Vendor and Guest OS' report Actual results: The graph shows far less values (as it will be shown in the attachments) Expected results: The graph shows values that conform to the list. Additional info:
I am thinking this is a issue with the report. We can see the provider data and its been collected. Re-assigning to Dan for further investigation. Dan, ping me if you need access to the environment.
https://github.com/ManageIQ/manageiq/pull/1215
New commit detected on manageiq/master: https://github.com/ManageIQ/manageiq/commit/794ca1696b49d5a018d37c6ef0bf55c41459d963 commit 794ca1696b49d5a018d37c6ef0bf55c41459d963 Author: Milan Zazrivec <mzazrivec> AuthorDate: Thu Dec 11 15:22:30 2014 +0100 Commit: Milan Zazrivec <mzazrivec> CommitDate: Thu Dec 11 15:45:27 2014 +0100 Fix counts in multi-dimensional charts Whenever the second sort field changes, we need to change its nonblank counterpart accordingly, otherwise we'd be updating incorrect value in the 'counts' hash. That would lead to incorrect charting numbers being returned by the build_reporting_chart_dim2() method. https://bugzilla.redhat.com/show_bug.cgi?id=1169351 vmdb/lib/report_formatter/chart_common.rb | 1 + 1 file changed, 1 insertion(+)
*** Bug 1183804 has been marked as a duplicate of this bug. ***
Waiting for error 'size of BinaryBlobPart id [26] is incorrect [report/tree_select]' to be resolved. Should be resolved in the next build.
Checked in 5.4.0.0.12 against the "Guest OS Information - any OS" graph. The "vendor and Guest OS" showed some not-quite-sensible informations. So moving to VERIFIED but putting a needinfo and a screenshot for verification.
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://rhn.redhat.com/errata/RHBA-2015-1100.html