+++ This bug was initially created as a clone of Bug #1366365 +++ Description of problem: When running Heapster, the logs will fill up with warning messages about "Failed to find node" as well as more verbose messages about each and every invocation to the nodes and how many metrics were returned. The warning about "Failed to find node" is confusing and has nothing to do with Heapster being able to find or connect to OpenShift nodes. These warning messages have been fixed upstream by changing the message and severity. See https://github.com/kubernetes/heapster/commit/c192564d3b551a2a632c067a9121fc6d239ebe24 We should backport this change into our images. Version-Release number of selected component (if applicable): 3.3.0, 3.2.1 How reproducible: Always Steps to Reproduce: 1. deploy metrics and view the Heapster logs Actual results: no warnings or errors in the logs unless a real error or issue has occured.
This is fixed for openshift 3.2 in rpm heapster-1.1.0-1.beta2.el7.1 That rpm is in image openshift3/metrics-heapster:3.2.1-3 and newer.
It's fixed, checked with the latest metrics images, please refer to the below testing results: <----------snip---------> The endpoint check has successfully completed. Starting Heapster with the following arguments: --source=kubernetes:https://ec2-52-90-81-201.compute-1.amazonaws.com:443?useServiceAccount=true&kubeletHttps=true&kubeletPort=10250 --sink=hawkular:https://hawkular-metrics:443?tenant=_system&labelToTenant=pod_namespace&labelNodeId=nodename&caCert=/hawkular-cert/hawkular-metrics-ca.certificate&user=hawkular&pass=6qmPC5CqtnKs-2B&filter=label(container_name:^system.slice.*|^user.slice) --tls_cert=/secrets/heapster.cert --tls_key=/secrets/heapster.key --tls_client_ca=/secrets/heapster.client-ca --allowed_users=system:master-proxy --metric_resolution=10s I0811 23:58:42.672825 1 heapster.go:65] heapster --source=kubernetes:https://ec2-52-90-81-201.compute-1.amazonaws.com:443?useServiceAccount=true&kubeletHttps=true&kubeletPort=10250 --sink=hawkular:https://hawkular-metrics:443?tenant=_system&labelToTenant=pod_namespace&labelNodeId=nodename&caCert=/hawkular-cert/hawkular-metrics-ca.certificate&user=hawkular&pass=6qmPC5CqtnKs-2B&filter=label(container_name:^system.slice.*|^user.slice) --tls_cert=/secrets/heapster.cert --tls_key=/secrets/heapster.key --tls_client_ca=/secrets/heapster.client-ca --allowed_users=system:master-proxy --metric_resolution=10s I0811 23:58:42.673766 1 heapster.go:66] Heapster version 1.1.0-beta2 I0811 23:58:42.674124 1 configs.go:60] Using Kubernetes client with master "https://ec2-52-90-81-201.compute-1.amazonaws.com:443" and version "v1" I0811 23:58:42.674161 1 configs.go:61] Using kubelet port 10250 I0811 23:58:42.743252 1 driver.go:322] Initialised Hawkular Sink with parameters {_system https://hawkular-metrics:443?tenant=_system&labelToTenant=pod_namespace&labelNodeId=nodename&caCert=/hawkular-cert/hawkular-metrics-ca.certificate&user=hawkular&pass=6qmPC5CqtnKs-2B&filter=label(container_name:^system.slice.*|^user.slice) 0xc20817b0e0 5} I0811 23:58:43.443283 1 heapster.go:92] Starting with Hawkular-Metrics Sink I0811 23:58:43.443306 1 heapster.go:92] Starting with Metric Sink I0811 23:58:43.454821 1 heapster.go:171] Starting heapster on port 8082 W0812 00:47:56.641961 1 manager.go:119] Failed to push data to sink: Hawkular-Metrics Sink
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/RHSA-2016:1853