Why the VMs were not started automatically on other nodes after a node failure in Openshift Virtualization

Solution Verified - Updated -

Issue

  • The cluster is configured using Openshift Baremetal IPI method and is configured with machine health checks. However, after a node failure, the workload was not automatically moved to other nodes and the node remains in NotReady status.
  • The machine object of the node has got the annotation host.metal3.io/external-remediation: "".

Environment

  • Openshift Container Platform 4.7.

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