Bug 2107070 - etcd-metrics container is flooding logs
Summary: etcd-metrics container is flooding logs
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Etcd
Version: 4.11
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.11.z
Assignee: Thomas Jungblut
QA Contact: ge liu
Depends On: 2107068
Blocks: 2116624
TreeView+ depends on / blocked
Reported: 2022-07-14 09:19 UTC by OpenShift BugZilla Robot
Modified: 2022-08-29 06:47 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2022-08-29 06:46:55 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift cluster-etcd-operator pull 889 0 None open [release-4.11] Bug 2107070: etcd-metrics container is flooding logs 2022-07-14 09:19:58 UTC
Red Hat Product Errata RHBA-2022:6143 0 None None None 2022-08-29 06:47:13 UTC

Description OpenShift BugZilla Robot 2022-07-14 09:19:33 UTC
+++ This bug was initially created as a clone of Bug #2107068 +++

I can observe on all OCP 4.10 cluster that the etcd-metrics container is flooding logs with a connection to a port which does not listening on any etcd container.

{"level":"info","ts":"2022-06-22T12:59:19.139Z","caller":"zapgrpc/zapgrpc.go:174","msg":"[core] Subchannel picks a new address \"\" to connect"}
{"level":"warn","ts":"2022-06-22T12:59:19.146Z","caller":"zapgrpc/zapgrpc.go:191","msg":"[core] grpc: addrConn.createTransport failed to connect to { <nil> 0 <nil>}. Err: connection error: desc = \"transport: Error while dialing dial tcp connect: connection refused\". Reconnecting..."}
there's a typo in the pod yaml, with an excessive "s" it uses the default value from:

Comment 2 ge liu 2022-08-18 09:06:06 UTC
verified with 4.11.0-0.nightly-2022-08-17-091649, there is not msg about '23790' in etcd-metrics log

Comment 5 errata-xmlrpc 2022-08-29 06:46: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 (OpenShift Container Platform 4.11.2 bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.