Closed parseltongued closed 4 months ago
This topic is more suitable for discussion rather than as an issue. Can someone convert it? Thanks!
Personally, I would address the issues causing the update to fail, then allow the update to complete to restore the cluster to its normal state. Could you provide more details on why the update is failing?
Pausing the MachineConfigPools for longer periods of time has some consequences, you can find out more about that on The Consequences Of Pausing MachineConfig Pools In OpenShift's Machine Config Operator.
Describe the bug I am using OKD in an air-gap cluster. Currently my 3-masters are tainted because cluster update failing. All pods are scheduling to the master-1.
Running the command below was successful but doesn't have any change to the taint.
I've also paused the update on Admin Operator UI but no effect:
How to disable cluster update and more importantly remove the taint.
Version Deployment information OKD Cluster Version: 4.15.0-0.okd-2024-03-10-010116 Kernel version: v1.28.2-3598+6e2789bbd58938-dirty Installation method: Bare-metal UPI (Airgapped, self hosted quay)
Thank you