Node in degraded state because of the use of a deleted machineconfig:; rendered-$[custom-machine-config] not found.

Solution Verified - Updated -


  • Assigning a machine-config-pool to a node and then, deleting by accident the machine-config in used will put the node in a loop-back trying to render the deleted config pool. It will cause discrepancies with the existing machine config pool to be in a degraded state.
  • Deletion of a rendered config in use should never be done since it will lead to a degraded status of the node associated.
  • The only other reason to lose a rendered config is a drift during install between the bootstrap and master generation.


  • Openshift Container Platform 4.x (OCP).

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