- When deploying a new MCP configuration on the nodes, the Machine Config Daemon (MCD) is restarting, leading the currentconfig in an undesired state.
- Creating the flag
/run/machine-config-daemon-forceon the node does not help the MCD to update the node.
Machine Config Daemon is restarting and failing to apply the new config
Solution verified - Updated on
Request a new translation or translation update
A translation for your language preference does not exist. Click below to request a translation for your selected language.
Issue
Subscriber Exclusive Content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.