When power actions are not available, we cannot remediate host
Little bit more info: BMO is not running if there's no provisioning-configuration CR (BMO pods are running, but BMO is disabled due to missing CR).
1. Create MachineHealthCheck matching two worker nodes $ cat mhc.yaml apiVersion: machine.openshift.io/v1beta1 kind: MachineHealthCheck metadata: name: example namespace: openshift-machine-api spec: selector: matchLabels: machine.openshift.io/cluster-api-cluster: <your cluster name> machine.openshift.io/cluster-api-machine-role: worker machine.openshift.io/cluster-api-machine-type: worker machine.openshift.io/cluster-api-machineset: <your machine set> unhealthyConditions: - type: Ready status: Unknown timeout: 300s - type: Ready status: 'False' timeout: 300s maxUnhealthy: 40% $ oc create -f mhc.yaml 2. Check `Health Checks` status on Nodes -> Click on name of worker-0-1/worker-0-0 -> Check 'Health Checks' status in 'Status' card, it shows "2 conditions passing " and green ok icon 3. Delete provisioning-configuration $ oc delete provisioning.metal3.io provisioning-configuration provisioning.metal3.io "provisioning-configuration" deleted 4. Check `Health Checks` status again using same steps with step2, this time it will show 'Not available' and grey question mark ? Moving to VERIFIED 4.6.0-0.nightly-2020-09-27-075304
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:4196