Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1199216

Summary: hardware.memory.used metric is inaccurate
Product: Red Hat OpenStack Reporter: Tzu-Mainn Chen <tzumainn>
Component: openstack-ceilometerAssignee: Mehdi ABAAKOUK <mabaakou>
Status: CLOSED ERRATA QA Contact: Yurii Prokulevych <yprokule>
Severity: unspecified Docs Contact:
Priority: low    
Version: 6.0 (Juno)CC: fbaudin, jruzicka, lsmola, mabaakou, srevivo, tzumainn, yprokule
Target Milestone: ---Keywords: Triaged, ZStream
Target Release: 6.0 (Juno)   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openstack-ceilometer-2014.2.3-10.el7ost Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1335473 (view as bug list) Environment:
Last Closed: 2016-10-05 19:16:35 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:
Bug Depends On:    
Bug Blocks: 1335473    

Description Tzu-Mainn Chen 2015-03-05 16:35:04 UTC
Description of problem:

Right now, the hardware.memory.used metric is inaccurate, measuring available memory instead.

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

openstack-ceilometer-central-2014.2.2-1.el7ost.noarch

How reproducible:

Look at hardware.memory.used in ceilometer.

Steps to Reproduce:
1.
2.
3.

Actual results:

hardware.memory.used measures available memory

Expected results:

hardware.memory.used measures used memory

Additional info:

Fixed by https://github.com/openstack/ceilometer/commit/22783a47258688cdfb4e916488182868827c52a4

Comment 3 Ladislav Smola 2015-03-05 16:37:30 UTC
this needs to be backported to rhos 6

https://github.com/openstack/ceilometer/commit/22783a47258688cdfb4e916488182868827c52a4

Comment 12 errata-xmlrpc 2016-10-05 19:16:35 UTC
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.

https://rhn.redhat.com/errata/RHBA-2016-2022.html