Description of problem: Delete a node, machine still has nodeRef to the node, remediation does not trigger Version-Release number of selected component (if applicable): 4.3.0-0.ci-2019-10-24-213642 How reproducible: Always Steps to Reproduce: 1. Create a machinehealthcheck apiVersion: healthchecking.openshift.io/v1alpha1 kind: MachineHealthCheck metadata: name: test namespce: openshift-machine-api spec: selector: matchLabels: machine.openshift.io/cluster-api-cluster: jhou-m9xln machine.openshift.io/cluster-api-machine-role: worker machine.openshift.io/cluster-api-machine-type: worker machine.openshift.io/cluster-api-machineset: jhou-m9xln-w-a unhealthyConditions: - type: "Ready" status: "False" timeout: "300s" - type: "Ready" status: "Unknown" timeout: "300s" 2. Delete a node that is linked to a machine of the machineset in the above 3. Monitor mhc logs Actual results: I1025 03:34:26.017131 1 machinehealthcheck_controller.go:200] Reconciling openshift-machine-api/test/jhou-m9xln-w-a-v8w98/jhou-m9xln-w-a-v8w98.c.openshift-gce-devel.internal: health checking I1025 03:34:26.024572 1 machinehealthcheck_controller.go:135] Reconciling openshift-machine-api/test: monitoring MHC: total targets: 1, maxUnhealthy: <nil>, unhealthy: 0. Remediations are allowed I1025 03:34:26.024866 1 machinehealthcheck_controller.go:163] Reconciling openshift-machine-api/test: no more targets meet unhealthy criteria E1025 03:34:28.453846 1 machinehealthcheck_controller.go:303] No-op: Unable to retrieve node "/jhou-m9xln-w-a-v8w98.c.openshift-gce-devel.internal" from store: Node "jhou-m9xln-w-a-v8w98.c.openshift-gce-devel.internal" not found Expected results: MHC logged no-op. Additional info:
Verified in 4.3.0-0.nightly-2019-11-17-224250, machine is remediated when it has nodeRef but node is deleted.
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, 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:0062