Description of problem: machine-api-operator panics after resyncing Version-Release number of selected component (if applicable): ocp/4.6:base How reproducible: Found in https://prow.ci.openshift.org/view/gcs/origin-ci-test/pr-logs/pull/openshift_cluster-network-operator/709/pull-ci-openshift-cluster-network-operator-master-e2e-ovn-step-registry/1290117649933537280 Log with the panic https://storage.googleapis.com/origin-ci-test/pr-logs/pull/openshift_cluster-network-operator/709/pull-ci-openshift-cluster-network-operator-master-e2e-ovn-step-registry/1290117649933537280/artifacts/e2e-ovn-step-registry/gather-extra/pods/openshift-machine-api_machine-api-operator-79f8978b9b-zd55z_machine-api-operator_previous.log
This error[1] isn't being checked properly, causing the `existing` to be nil and leading to this panic. Handling the error properly should solve this issue. We also need to make sure we add tests for this code as it isn't tested currently. [1]: https://github.com/openshift/machine-api-operator/blob/79ac5f8a00976701665f8cc42f324cd5a810fcd0/pkg/operator/webhook_configuration.go#L172-L177
From the test result, didn't meet this again, move this to verified. https://prow.ci.openshift.org/pr-history/?org=openshift&repo=machine-api-operator&pr=684
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