Bug 1397279

Summary: Memory, CPU and Network utilization graphs are no longer displaying info for VMs under VMs main tab
Product: [oVirt] ovirt-engine Reporter: Michael Burman <mburman>
Component: Frontend.WebAdminAssignee: Arik <ahadas>
Status: CLOSED CURRENTRELEASE QA Contact: meital avital <mavital>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.0.6CC: bugs, mburman, michal.skrivanek, tjelinek
Target Milestone: ovirt-4.0.6Keywords: Regression
Target Release: 4.0.6.2Flags: tjelinek: ovirt-4.0.z?
rule-engine: blocker?
mburman: planning_ack?
tjelinek: devel_ack+
rule-engine: testing_ack+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-18 07:24:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
record
none
screenshots
none
screenshot none

Description Michael Burman 2016-11-22 06:56:56 UTC
Created attachment 1222590 [details]
record

Description of problem:
Memory, CPU and Network utilization graphs are no longer displaying info for VMs under 'VMs' main tab. It remain on 0% and no green graph is displayed.
- But it is shown under 'Hosts' main tab > 'VMs' sub tab.

It is a regression from 4.0.5 

Version-Release number of selected component (if applicable):
4.0.6-0.1.el7ev

How reproducible:
100%

- Attaching record to describe the bug.

Comment 1 Michal Skrivanek 2016-11-23 06:45:03 UTC
Should be fixed by https://gerrit.ovirt.org/#/c/67005/

Comment 2 Tomas Jelinek 2016-11-23 07:56:05 UTC
Indeed, should arrive in 4.0.6-2.

Comment 3 Red Hat Bugzilla Rules Engine 2016-11-23 07:56:13 UTC
This bug report has Keywords: Regression or TestBlocker.
Since no regressions or test blockers are allowed between releases, it is also being identified as a blocker for this release. Please resolve ASAP.

Comment 4 Michael Burman 2016-11-27 07:50:12 UTC
Created attachment 1224753 [details]
screenshots

Comment 5 Michael Burman 2016-11-27 07:50:30 UTC
Please note that the graphs now on 4.0.6.1-0.1.el7ev look weird, they shorter and looks like someone cut them. Not sure this is how it suppose to look(it used to look different, like on master 4.1).

Comment 6 Michael Burman 2016-11-27 07:51:19 UTC
Created attachment 1224754 [details]
screenshot

Comment 7 Arik 2016-11-27 08:45:22 UTC
(In reply to Michael Burman from comment #5)
These screenshots were taken right after the engine was started for a VM that has been running for quite some time, right? If that's the case then this outcome is expected:
Consider the case a VM was started at 8:00am and its network consumption was 30% for 2 hours. Then the engine went down for an hour and started again. When the engine was started (11:00am) the network consumption changed to 70%.
Before, since we saved the statistics in the database you would get a graph of 30% for some time and then a jump to 70%.
Now that the statistics are saved in-memory, the engine doesn't know what happened on its previous run, so you'll get a graph that start with 70% right from the start.
The latter outcome is much more correct than the former (it is supposed to be that way on master btw, what did you mean by saying that it is different than master?)

Comment 8 Arik 2016-11-27 08:47:58 UTC
(In reply to Arik from comment #7)
Ah oops, you attached a screenshot from the master..
It is possible that on master the VM was started after the engine was started and on 4.0.6 the VM was already running when the engine was started?

Comment 9 Michael Burman 2016-11-27 08:56:02 UTC
In both master and 4.0.6.1 the VMs are running for a long time, few days now.

- In 4.0.6.1 the engine already running almost 4 hours after restart and i still don't see any progress with the graphs..

Comment 10 Red Hat Bugzilla Rules Engine 2016-11-27 13:59:52 UTC
Target release should be placed once a package build is known to fix a issue. Since this bug is not modified, the target version has been reset. Please use target milestone to plan a fix for a oVirt release.

Comment 11 meital avital 2016-12-12 09:16:11 UTC
Verified on version: 4.0.6.3-0.1.el7ev