Last active
June 4, 2025 07:37
-
-
Save ikurni/067ea20449588008de4e19a07f0de5f4 to your computer and use it in GitHub Desktop.
How to force openshift MCP to update machine config
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| ### Create file called machine-config-daemon-force in /run ### | |
| ssh [email protected] sudo touch /run/machine-config-daemon-force | |
| ### Edit node annotations ### | |
| oc edit node <node-name> | |
| ### Check Annotations, change like below sample ### | |
| machineconfiguration.openshift.io/currentConfig: rendered-worker-ab4a1e7216bf3da2a5203f09c871b456 | |
| machineconfiguration.openshift.io/desiredConfig: rendered-worker-ab4a1e7216bf3da2a5203f09c871b456 | |
| machineconfiguration.openshift.io/reason: "" | |
| machineconfiguration.openshift.io/ssh: accessed | |
| machineconfiguration.openshift.io/state: Done | |
| ### If the machine config is updated during rolling, due to any revision, delete the machine-config-controller pods first and then | |
| ### delete the current expected machine config to read the latest revision, and make sure old machine config is backed up before | |
| ### performing this action |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment