Bug 2107070

Summary:	etcd-metrics container is flooding logs
Product:	OpenShift Container Platform	Reporter:	OpenShift BugZilla Robot <openshift-bugzilla-robot>
Component:	Etcd	Assignee:	Thomas Jungblut <tjungblu>
Status:	CLOSED ERRATA	QA Contact:	ge liu <geliu>
Severity:	low	Docs Contact:
Priority:	low
Version:	4.11	CC:	tjungblu
Target Milestone:	---
Target Release:	4.11.z
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-08-29 06:46:55 UTC	Type:	---
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:	2107068
Bug Blocks:	2116624

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 \"127.0.0.1:23790\" 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 {127.0.0.1:23790 127.0.0.1 <nil> 0 <nil>}. Err: connection error: desc = \"transport: Error while dialing dial tcp 127.0.0.1:23790: connect: connection refused\". Reconnecting..."}
there's a typo in the pod yaml, with an excessive "s" it uses the default value from:
https://github.com/etcd-io/etcd/blob/main/server/etcdmain/grpc_proxy.go#L130

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.

https://access.redhat.com/errata/RHBA-2022:6143