Created attachment 861397 [details] Report in PDF + jasper log (debug)
Verification failed, is32.1: # rpm -qa | egrep 'dwh|reports' rhevm-dwh-3.3.1-1.el6ev.noarch rhevm-reports-3.3.1-1.el6ev.noarch jasperreports-server-pro-5.5.0-4.el6ev.noarch [RHEVM shell (connected)]# list vms --show-all| egrep 'name|os-type' name : VM-0 os-type : rhel_6x64 name : VM-1 os-type : sles_11 name : VM-2 os-type : ubuntu_12_04 name : VM-3 os-type : windows_2008 name : VM-4 os-type : windows_2008x64 from garph can be seen: 1) two other linux, non rhel 2) 1 win 2008, no win 2--9 x64 (maybe one line override the 2nd ?) 3) 2 wins, no rhel (same as #1) 4) 0 known os (should be other ?)
Verification failed, is325: # rpm -qa | egrep 'dwh|reports' rhevm-dwh-3.3.2-1.el6ev.noarch rhevm-reports-3.3.2-3.el6ev.noarch jasperreports-server-pro-5.5.0-6.el6ev.noarch [RHEVM shell (connected)]# list vms --show-all| egrep 'name|os-type' name : VM-0 os-type : rhel_6 name : VM-1 os-type : rhel_6x64 name : VM-2 os-type : ubuntu_12_10 name : VM-3 os-type : sles_11 name : VM-4 os-type : windows_2008x64 name : vm5 os-type : windows_2003 name : vm6 os-type : other_linux name : vm7 os-type : other engine=# select vm_name, vm_os, vm_type, vm_creation_date from vms order by 1; vm_name | vm_os | vm_type | vm_creation_date ---------+-------+---------+---------------------------- VM-0 | 18 | 0 | 2014-03-05 19:33:44.456+02 VM-1 | 19 | 0 | 2014-03-05 19:33:48.066+02 VM-2 | 1253 | 0 | 2014-03-05 19:33:50.92+02 VM-3 | 1193 | 0 | 2014-03-05 19:33:53.75+02 VM-4 | 16 | 0 | 2014-03-05 19:33:56.677+02 vm5 | 3 | 1 | 2014-03-19 23:36:18.14+02 vm6 | 5 | 1 | 2014-03-19 23:38:22.849+02 vm7 | 0 | 1 | 2014-03-19 23:40:20.039+02 (8 rows) From the graph: 1) RHEL Vs Other Linux - 0 rhel , 0 other 2) Windows - 0 3) Rhel Vs Windows - 0 Rhel, 0 Winodows 4) Know OS Vs Unknown OS - 7 known, 1 unknown (which is the only correct one, assuming that other linux considered as known)
Created attachment 876722 [details] Report in PDF
After reviewing the report the number of OS types is correct in all of the report tables. The confusion is because the reports display only "Active" vms except for the "vms known Vs. Unknown" table that displays also Inactive vms. Also, if different OS types has same quantity the graph only display one of them because the merge to the same graph line. This bug was reopened by mistake. The data is correct.
This bug is currently attached to errata RHBA-2014:17207 If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag. Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information: * Cause: What actions or circumstances cause this bug to present. * Consequence: What happens when the bug presents. * Fix: What was done to fix the bug. * Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore') Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug. For further details on the Cause, Consequence, Fix, Result format please refer to: https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes Thanks in advance.
Verified on 3.3.2 (is35.1). rhevm-3.3.2-0.50.el6ev.noarch rhevm-dwh-3.3.2-1.el6ev.noarch rhevm-reports-3.3.2-3.el6ev.noarch jasperreports-server-pro-5.5.0-6.el6ev.noarch Verification excluded https://bugzilla.redhat.com/show_bug.cgi?id=1083636. After discussion with DEV, decided to leave it for 3.5, Dev claims that table comes to state the credibility of the other and PMs are aware of it.
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. http://rhn.redhat.com/errata/RHBA-2014-0393.html