etcd-metrics Pod is continuously logging "grpc: addrConn.createTransport failed to connect"

Solution Verified - Updated -

Issue

  • On OpenShift Container Platform, every "etcd" Pod is continuously logging the lines below within the etcd-metrics container:

    {"level":"info","ts":"2022-07-11T13:57:37.975Z","caller":"zapgrpc/zapgrpc.go:174","msg":"[core] Subchannel Connectivity change to CONNECTING"}
    {"level":"info","ts":"2022-07-11T13:57:37.976Z","caller":"zapgrpc/zapgrpc.go:174","msg":"[core] Subchannel picks a new address \"127.0.0.1:23790\" to connect"}
    {"level":"info","ts":"2022-07-11T13:57:37.977Z","caller":"zapgrpc/zapgrpc.go:174","msg":"[balancer] base.baseBalancer: handle SubConn state change: 0xc00017e150, CONNECTING"}
    {"level":"warn","ts":"2022-07-11T13:57:37.977Z","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..."}
    {"level":"info","ts":"2022-07-11T13:57:37.977Z","caller":"zapgrpc/zapgrpc.go:174","msg":"[core] Subchannel Connectivity change to TRANSIENT_FAILURE"}
    {"level":"info","ts":"2022-07-11T13:57:37.977Z","caller":"zapgrpc/zapgrpc.go:174","msg":"[balancer] base.baseBalancer: handle SubConn state change: 0xc00017e150, TRANSIENT_FAILURE"}
    

Environment

  • Red Hat OpenShift Container Platform (RHOCP) 4.10

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content