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.
Should be fixed by https://gerrit.ovirt.org/#/c/67005/
Indeed, should arrive in 4.0.6-2.
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.
Created attachment 1224753 [details] screenshots
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).
Created attachment 1224754 [details] screenshot
(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?)
(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?
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..
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.
Verified on version: 4.0.6.3-0.1.el7ev