Master node upgrade stuck at SchedulingDisabled during cluster upgrade to 4.13
Issue
- Master nodes fail to
upgrade
and are stuck inSchedulingDisabled
state with mastermcp
in degraded state. - Master nodes fail to upgrade even after deleting the current configuration and forcing the validation using the file
touch /host/run/machine-config-daemon-force
. - There is not file mismatch thereby pausing the node upgrade.
- Rebooting the nodes does not fix the upgrade issue and the node still remains in degraded state.
- The
machine-config-daemon
logs for the pods show bellow error and gets degraded.
2023-08-21T12:57:37.481924251Z [2023-08-21T12:57:37Z INFO nmstatectl::persist_nic] Device ens192 has static address
2023-08-21T12:57:37.481924251Z [2023-08-21T12:57:37Z INFO nmstatectl::persist_nic] NOTE: would persist the interface with MAC 00:50:56:A3:C6:27 to interface name ens192
2023-08-21T12:57:37.481950581Z
2023-08-21T12:57:37.499493696Z W0821 12:57:37.499088 710336 daemon.go:1369] failed to query for deployment failure: error querying for previous finalization via journalctl: exit status 1
Environment
- Red Hat OpenShift Container Platform 4.13
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.