Heapster Complains About Not Finding a Node

Environment

• OpenShift Enterprise 3.1+

Issue

• In Heapster I see the following error message over and over:

I0809 <TIME>       1 manager.go:79] Scraping metrics start: <DATE_TIME_TZ>, end: <DATE_TIME_TZ>
I0809 <TIME>       1 manager.go:152] ScrapeMetrics: time: 93.739353ms size: 180
W0809 <TIME>       1 node_aggregator.go:44] Failed to find node: node:<HOSTNAME>
W0809 <TIME>       1 node_aggregator.go:44] Failed to find node: node:<HOSTNAME>
W0809 <TIME>       1 node_aggregator.go:44] Failed to find node: node:<HOSTNAME>
W0809 <TIME>       1 node_aggregator.go:44] Failed to find node: node:<HOSTNAME>
W0809 <TIME>       1 node_aggregator.go:44] Failed to find node: node:<HOSTNAME>
W0809 <TIME>       1 node_aggregator.go:44] Failed to find node: node:<HOSTNAME>
W0809 <TIME>       1 node_aggregator.go:44] Failed to find node: node:<HOSTNAME>
W0809 <TIME>       1 node_aggregator.go:44] Failed to find node: node:<HOSTNAME>
W0809 <TIME>       1 node_aggregator.go:44] Failed to find node: node:<HOSTNAME>
W0809 <TIME>       1 node_aggregator.go:44] Failed to find node: node:<HOSTNAME>
W0809 <TIME>       1 node_aggregator.go:44] Failed to find node: node:<HOSTNAME>

Resolution

The Metric's Engineering Team has indicated that it is a warning message that is not accurate.

• It is not that it can't connect to the node, it's that it can't find a particular node metric. That node metric is not used currently so its not a problem that it doesn't exist.

There is work being done to remove this message, or at least make it accurate, so until that is corrected, feel free to ignore this warning message.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.