Bug 1469291

Summary:	Missing node level memory/usage
Product:	OpenShift Container Platform	Reporter:	Matt Wringe <mwringe>
Component:	Hawkular	Assignee:	John Sanda <jsanda>
Status:	CLOSED ERRATA	QA Contact:	Junqi Zhao <juzhao>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.5.1	CC:	aos-bugs, javier.ramirez, jgoulding, jsanda, juzhao, lizhou, miburman, mwringe, pweil, rromerom, snegrea, trankin, whearn, xtian
Target Milestone:	---	Keywords:	OpsBlocker
Target Release:	3.5.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1441390	Environment:
Last Closed:	2017-12-14 21:01:55 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:

Comment 1 Matt Wringe 2017-07-10 21:28:14 UTC

Can we get this backported in Hawkular Metrics for our OCP 3.5 version?

Comment 5 Matt Wringe 2017-08-09 21:07:55 UTC

*** Bug 1473363 has been marked as a duplicate of this bug. ***

Comment 10 Junqi Zhao 2017-10-09 00:11:53 UTC

@pweil

Please help to verify this defect.
Thanks

Comment 11 Junqi Zhao 2017-11-15 00:10:56 UTC

@pweil

Can you show me the details on how to verify this defect?

Comment 12 Junqi Zhao 2017-11-29 01:57:08 UTC

Images:
metrics-cassandra-3.5.0-49
metrics-hawkular-metrics-3.5.0-58
metrics-heapster-3.5.0-41

# openshift version
openshift v3.5.5.31.47
kubernetes v1.5.2+43a9be4
etcd 3.1.0

Tested on 7 nodes, and created a few projects and every node had at least one running pod, let the metrics run for a day, all metrics usage could be found in metrics web console

Used the following command to check memory/usage on every node, it's not missed.

# curl -k -H "Authorization: Bearer $TOKEN" -H "Hawkular-tenant: _system" https://metrics.newscorpau01.openshift.com/hawkular/metrics/metrics?tags=nodename:${NODE} | python -m json.tool | grep -i \"id\" | grep -i machine | grep -i memory | sort

        "id": "machine/${NODE}/memory/limit",
        "id": "machine/${NODE}/memory/major_page_faults",
        "id": "machine/${NODE}/memory/major_page_faults_rate",
        "id": "machine/${NODE}/memory/node_capacity",
        "id": "machine/${NODE}/memory/node_reservation",
        "id": "machine/${NODE}/memory/node_utilization",
        "id": "machine/${NODE}/memory/page_faults",
        "id": "machine/${NODE}/memory/page_faults_rate",
        "id": "machine/${NODE}/memory/request",
        "id": "machine/${NODE}/memory/usage",
        "id": "machine/${NODE}/memory/working_set",

Comment 15 errata-xmlrpc 2017-12-14 21:01:55 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://access.redhat.com/errata/RHBA-2017:3438