Bug 2107068
| Summary: | etcd-metrics container is flooding logs | |||
|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Thomas Jungblut <tjungblu> | |
| Component: | Etcd | Assignee: | Dean West <dwest> | |
| Status: | CLOSED ERRATA | QA Contact: | ge liu <geliu> | |
| Severity: | low | Docs Contact: | ||
| Priority: | low | |||
| Version: | 4.12 | CC: | geliu, ssonigra | |
| Target Milestone: | --- | |||
| Target Release: | 4.12.0 | |||
| Hardware: | Unspecified | |||
| OS: | Unspecified | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 2116624 (view as bug list) | Environment: | ||
| Last Closed: | 2023-01-17 19:52:40 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: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 2107070 | |||
ok let me check it again cloned bug 2116624 for 4.10 cloned bug 2116624 for 4.10 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 (Moderate: OpenShift Container Platform 4.12.0 bug fix and security 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/RHSA-2022:7399 |
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