Windows Machine Config Operator (WMCO) upgrade stuck on draining RHOCP 4.11
Issue
After RHOCP 4.11 upgrade, the Windows Machine Config Operator (WMCO) was unable to update the Windows nodes, throwing the following error :
{"level":"info","ts":1682079851.2253845,"logger":"controllers.configmap","msg":"processing","instances in":"windows-instances"}
{"level":"info","ts":1682079851.6878572,"logger":"controllers.configmap","msg":"instance requires upgrade","node":"win-byoh-2","version":"5.1.0+b49f451","expected version":"6.0.0-f3ad235"}
{"level":"error","ts":1682079861.7732017,"msg":"Reconciler error","controller":"certificatesigningrequest","controllerGroup":"certificates.k8s.io","controllerKind":"CertificateSigningRequest","configMap":{"name":"windows-instances",
"namespace":"openshift-windows-machine-config-operator"},"namespace":"openshift-windows-machine-config-operator","name":"windows-instances","reconcileID":"xxxx-xxx-xx-xxx-xxxx","error":"error configuring host with ad
dress win-xxx-x.xx.xx.xxx: unable to drain node win-xxx-x.xx.xx.xxx: cannot delete DaemonSet-managed Pods (use --ignore-daemonsets to ignore): xx-xx-xx/xx-xx","errorVerbose":"cannot delete Dae
monSet-managed Pods
Environment
- Red Hat OpenShift Container Platform 4.11 [RHOCP]
- Windows Machine Config Operator (WMCO)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.