Recovering a node that has lost all networking in OpenShift 4

Solution Verified - Updated -

Issue

  • During network upgrades/changes to your cluster or node, the network scripts failed to configure or the node stays in NotReady and is not bound to it's expected IP address
  • Node is unreachable/not pingable and subsequent remote reboots do not recover the host
  • Debugging access is required on a node with failed networking to grab a SOSreport or repair the network configuration

Environment

  • Red Hat OpenShift Container Platform (RHOCP) 4.x

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