Bug 1068884

Summary: wrong memory usage report
Product: [Retired] oVirt Reporter: Koen <vanoppen.koen>
Component: ovirt-engine-apiAssignee: Martin Sivák <msivak>
Status: CLOSED CURRENTRELEASE QA Contact: bugs <bugs>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.3CC: acathrow, gklein, iheim, msivak, s.kieske, yeylon
Target Milestone: ---   
Target Release: 3.3.4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: ovirt-3.3.4-ga Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-03-31 12:28:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
memory goes in negative value none

Description Koen 2014-02-22 21:14:09 UTC
Created attachment 866484 [details]
memory goes in negative value

Description of problem:
When we monitor one of our machines, we noticed that there was one vm that was constantly giving a error of memory usage. But when we took a look at it, there is actually nothing wrong with it. Now we looked furhter then that. We looked at the API of the machine and noticed something very strange:

<statistic href="/api/vms/3b9aa245-75ff-42e8-b921-1c9ce61826bf/statistics/b7499508-c1c3-32f0-8174-c1783e57bb08" id="b7499508-c1c3-32f0-8174-c1783e57bb08"><name>memory.used</name><description>Memory used (agent)</description><values type="INTEGER"><value><datum>-944892806</datum></value></values><type>GAUGE</type><unit>BYTES</unit>

It's a negative...

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Itamar Heim 2014-02-23 08:28:35 UTC
Setting target release to current version for consideration and review. please
do not push non-RFE bugs to an undefined target release to make sure bugs are
reviewed for relevancy, fix, closure, etc.

Comment 2 Juan Hernández 2014-02-24 10:12:35 UTC
In fact this has already been fixed by Martin Sivák in the master branch:

http://gerrit.ovirt.org/24859

Martin, can you please assign to yourself and backport 3.4 and to 3.3?

Comment 3 Sandro Bonazzola 2014-03-03 14:40:25 UTC
This BZ should be fixed in oVirt 3.4.0 RC

Comment 4 Sandro Bonazzola 2014-03-31 12:28:54 UTC
This is an automated message. Moving to Closed CURRENTRELEASE since oVirt 3.3.4 has been released.