Etcd IP misconfigured due to multiple network interfaces on etcd nodes.

Solution Verified - Updated -

Issue

  • Etcd IP can get misconfigured if etcd nodes have multiple network interfaces.
  • When etcd nodes have two interfaces and IPs, etcd should use Openshift IP.
  • Example: The etcd cluster should use 10.2.X.x which is Openshift IP, but for one etcd member is using 10.9.X.X OR peerURLs for this etcd member is using 10.2.X.X and clientURLs is using 10.9.X.X.
# etcdctl2 member list
xx: name=master0.abc.com peerURLs=https://10.9.X.X:2380 clientURLs=https://10.9.X.X:2379 isLeader=false    <---[The peerURLs and  clientURLs  are using 10.9.X.X]
yy: name=master1.abc.com peerURLs=https://10.2.X.Y:2380 clientURLs=https://10.2.X.Y:2379 isLeader=true
zz: name=master2.abc.com peerURLs=https://10.2.X.Z:2380 clientURLs=https://10.2.X.Z:2379 isLeader=false

 [OR]

# etcdctl2 member list
xx: name=master0.abc.com peerURLs=https://10.2.X.X:2380 clientURLs=https://10.9.X.X:2379 isLeader=false    <---[The peerURLs is using 10.2.X.X and clientURLs is using 10.9.X.X]
yy: name=master1.abc.com peerURLs=https://10.2.X.Y:2380 clientURLs=https://10.2.X.Y:2379 isLeader=true
zz: name=master2.abc.com peerURLs=https://10.2.X.Z:2380 clientURLs=https://10.2.X.Z:2379 isLeader=false

# etcdctl2 cluster-health
member xx is unreachable: [https://10.9.X.X:2379] are all unreachable
member yy is healthy: got healthy result from https://10.2.X.Y:2379
member zz is healthy: got healthy result from https://10.2.X.Z:2379

Environment

  • OpenShift Container Platform (OCP)
    • 3.11

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