Created attachment 825560 [details] active_vms_by_os_br18.pdf Description of problem: See att PDF file. I've DC/Cl with 7VMs, where 1x RH_64b, 1x win7_64b 1x SLES11. From report is obvious, that it reports wrongly: 1) RHEL vs other Linux OSes (also RHEL vs Win OSs) 2) VMs with known OS vs Unknown OS The RHEL VM is up & running (with OS installed) for ~18hrs now. Version-Release number of selected component (if applicable): is23 How reproducible: Steps to Reproduce: 1. have VM with RHEL OS set 2. from DC or Cluster tab show report BR18 3. Actual results: see att Expected results: Additional info:
This shows number of vm that were up and relative to their uptime. So since it's a avg, this can make sense. What is the test scenario? Yaniv
Do we want this fixed for 3.2.z? yaniv
Created attachment 838334 [details] images of the report In tha attached image, can be seen - 1) the windows version is not specified in the legend 2) 5 out of 8 VMs are not installed and configured as other OS, but from the graph it can be understood that most vms have known OS.
is27, rhevm-reports-3.3.0-25.el6ev.noarch. Is it a new one, or re-opened if the same one ?
Verification failed: is27, rhevm-reports-3.3.0-25.el6ev.noarch. Can be seen that all 8 VMs have known OS, while actually all of the "old" ones, connected to pther OS: "select vm_name, vm_os, vm_type, vm_creation_date from vms;" vm_name | vm_os | vm_type | vm_creation_date -------------+-------+---------+---------------------------- rhel_65_x64 | 19 | 1 | 2013-12-19 15:31:45.706+02 w7 | 11 | 1 | 2013-12-19 15:35:34.725+02 VM-0 | 0 | 0 | 2013-12-17 20:07:24.488+02 suse11 | 1193 | 1 | 2013-12-19 15:39:25.252+02 VM-1 | 0 | 0 | 2013-12-17 20:07:41.045+02 VM-2 | 0 | 0 | 2013-12-17 20:07:54.731+02 VM-3 | 0 | 0 | 2013-12-17 20:08:07.967+02 VM-4 | 0 | 0 | 2013-12-17 20:08:21.139+02
Created attachment 838988 [details] images of the report
Please add z stream flag. Yaniv
*** Bug 1045869 has been marked as a duplicate of this bug. ***
*** Bug 1045870 has been marked as a duplicate of this bug. ***
Verification failed o av3. Can be seen that there are 8 vms of different types: 2 rhels, suse, ubuntu, 2 wins, linux, other vm_name | vm_os | vm_type | vm_creation_date ---------+-------+---------+---------------------------- vm0 | 18 | 1 | 2014-03-18 15:10:46.468+02 vm1 | 19 | 1 | 2014-03-18 15:11:37.266+02 vm2 | 1193 | 1 | 2014-03-18 15:12:13.181+02 vm3 | 1252 | 1 | 2014-03-18 15:12:45.885+02 vm4 | 10 | 1 | 2014-03-18 15:13:20.822+02 vm5 | 16 | 1 | 2014-03-18 15:13:52.887+02 vm6 | 5 | 1 | 2014-03-18 15:14:21.027+02 vm7 | 0 | 1 | 2014-03-18 15:14:38.057+02 but in the graph there are two unknown groups 1 & 7.
Created attachment 876037 [details] br18 18.3.2014
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.
Verified on av4.1 rhevm-3.4.0-0.10.beta2.el6ev.noarch rhevm-dwh-3.4.0-6.el6ev.noarch rhevm-reports-3.4.0-2.el6ev.noarch jasperreports-server-pro-5.5.0-9.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/RHEA-2014-0602.html