etcd migration playbook fails with "etcd member is not healthy"

Solution Verified - Updated -

Issue

  • After upgrading from OpenShift 3.5 to 3.6, we ran the migrate etcd to V3 schema playbook and it failed. The following error message was seen but we confirmed the cluster is actually healthy:

    TASK [etcd_migrate : Check the etcd cluster health]
    Etcd member x.x.x.14 is not healthy
    
  • Trying to upgrade etcd cluster to the new v3 schema and discovered that etcdctl doesn't seem to understand network CIDR notations, thus it is trying to connect to etcd peers via the proxy server.

Environment

  • OpenShift Container Platform 3.6
  • etcd 3.2.5-1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.