Windows Machine stuck in provisioned state in OpenShift 4.x

Solution Verified - Updated -


  • After the Windows Machine Config Operator 3.0.0 Install Succeeded, Windows machines were provisioned using machinesets and they are running, however they do not get Provisioned as node.
  • SSH connection from WMCO (Windows Machine Config Operator) to the windows machine is timing out.


  • OpenShift Container Platform (OCP) 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