Troubleshoot MachineConfigPool Updating¶
Introduction¶
MachineConfigPools apply node-level configuration. Updating or Degraded states often mean a node failed to drain, reboot, or apply rendered configuration.
Why This Matters¶
OpenShift administration relies on operators and cluster-scoped resources. A bad change can affect many projects, so inspect status and events before applying fixes.
Practical Examples¶
oc get machineconfigpool
oc describe mcp worker
oc get nodes -l node-role.kubernetes.io/worker
oc adm drain worker-1 --ignore-daemonsets --delete-emptydir-data
Example output:
NAME CONFIG UPDATED UPDATING DEGRADED MACHINECOUNT READY UPDATEDMACHINECOUNT DEGRADEDMACHINECOUNT
worker rendered-worker-9c7d8f5b2a1c4e6f8d0a True False False 3 3 3 0
Verification¶
oc get mcp worker
oc describe mcp worker
oc get nodes
Troubleshooting¶
Read the operator message, check the namespace where the component runs, inspect related events, and confirm whether the condition is Available, Progressing, or Degraded.
Common Mistakes¶
- Forcing node changes while the MCP is already degraded.
- Ignoring PodDisruptionBudgets during drains.
- Editing rendered MachineConfig objects directly.
Quick Checklist¶
- Confirm the active project.
- Inspect the exact object named in the error.
- Read recent events.
- Apply one focused fix.
- Verify status after the change.
Related Guides¶
Summary¶
Troubleshoot MachineConfigPool Updating is an administration task that should be driven by cluster status, operator conditions, and component logs instead of broad restarts.