Bug 1392209 - VM statistics always show zero consumption via REST API
Summary: VM statistics always show zero consumption via REST API
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.1.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ovirt-4.1.0-alpha
: 4.1.0.2
Assignee: Arik
QA Contact: Artyom
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-06 09:06 UTC by Artyom
Modified: 2017-02-01 14:40 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-01 14:40:13 UTC
oVirt Team: Virt
Embargoed:
rule-engine: ovirt-4.1+
rule-engine: blocker+
rule-engine: planning_ack+
tjelinek: devel_ack+
mavital: testing_ack+

Attachments (Terms of Use)
screenshot and REST response (35.44 KB, application/zip)
2016-11-06 09:06 UTC, Artyom 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 65825 0 master MERGED core: use cached vm statistics also for rest-api 2016-11-14 15:14:28 UTC
oVirt gerrit 65854 0 master MERGED core: do not instantiate vm-manager when not needed 2016-11-14 14:13:38 UTC
oVirt gerrit 66178 0 master ABANDONED core: added the statistics into VM for GetVmByVmIdQuery 2016-11-09 10:46:42 UTC

Description Artyom 2016-11-06 09:06:18 UTC 
Created attachment 1217704 [details]
screenshot and REST response

Description of problem:
VM statistics always show zero consumption via REST API

Version-Release number of selected component (if applicable):
ovirt-engine-4.1.0-0.0.master.20161102211241.git5724b88.el7.centos.noarch

How reproducible:
Always

Steps to Reproduce:
1. Start the VM
2. Create CPU load on the VM
3. 

Actual results:
UI show me correct CPU usage for VM and REST show me 0

Expected results:
REST show correct CPU and memory usage

Additional info:
You can see REST and UI output under the attachment
Comment 1 Sandro Bonazzola 2016-12-12 13:58:39 UTC 
The fix for this issue should be included in oVirt 4.1.0 beta 1 released on December 1st. If not included please move back to modified.
Comment 2 Artyom 2016-12-13 14:45:18 UTC 
Verified on ovirt-engine-4.1.0-0.2.master.20161212172238.gitea103bd.el7.centos.noarch

<statistic href="/ovirt-engine/api/vms/52dba9b9-0e10-4f03-b160-3635e78e70f1/statistics/ef802239-b74a-329f-9955-be8fea6b50a4" id="ef802239-b74a-329f-9955-be8fea6b50a4">
<name>cpu.current.guest</name>
<description>CPU used by guest</description>
<kind>gauge</kind>
<type>decimal</type>
<unit>percent</unit>
<values>
<value>
<datum>0.54</datum>
</value>
</values>
<vm href="/ovirt-engine/api/vms/52dba9b9-0e10-4f03-b160-3635e78e70f1" id="52dba9b9-0e10-4f03-b160-3635e78e70f1" />
 </statistic>
...
Comment 3 Red Hat Bugzilla Rules Engine 2016-12-27 16:39:44 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.
Note You need to log in before you can comment on or make changes to this bug.