OpenShift 4 node become "NotReady" after VMware vMotion

Solution Verified - Updated -

Issue

  • After or during a vMotion virtual machine migration, a node becomes NotReady and/or the OpenShift API becomes unstable.

Environment

  • Red Hat OpenShift Container Platform (RHOCP)
    • 4
  • VMware vSphere
  • vMotion

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