verified on 4.2.0-0.nightly-2020-03-16-055952 apiVersion: v1 kind: Node metadata: annotations: machine.openshift.io/machine: openshift-machine-api/ci-ln-q7xk1g2-d5d6b-dtm64-worker-us-west-1a-6drrq machineconfiguration.openshift.io/currentConfig: rendered-worker-4605cb9bf152301e9b58405831c365f0 machineconfiguration.openshift.io/reason: machineconfiguration.openshift.io/desiredConfig annotation not found on node 'ip-10-0-133-186.us-west-1.compute.internal' machineconfiguration.openshift.io/state: Degraded volumes.kubernetes.io/controller-managed-attach-detach: "true" creationTimestamp: "2020-03-16T15:09:40Z" labels: beta.kubernetes.io/arch: amd64 beta.kubernetes.io/instance-type: m4.xlarge beta.kubernetes.io/os: linux
(In reply to Michael Nguyen from comment #4) > verified on 4.2.0-0.nightly-2020-03-16-055952 > > > apiVersion: v1 > kind: Node > metadata: > annotations: > machine.openshift.io/machine: > openshift-machine-api/ci-ln-q7xk1g2-d5d6b-dtm64-worker-us-west-1a-6drrq > machineconfiguration.openshift.io/currentConfig: > rendered-worker-4605cb9bf152301e9b58405831c365f0 > machineconfiguration.openshift.io/reason: > machineconfiguration.openshift.io/desiredConfig > annotation not found on node > 'ip-10-0-133-186.us-west-1.compute.internal' wait, wait, wait, why there's no desiredConfig annotation here? where did it go? > machineconfiguration.openshift.io/state: Degraded > volumes.kubernetes.io/controller-managed-attach-detach: "true" > creationTimestamp: "2020-03-16T15:09:40Z" > labels: > beta.kubernetes.io/arch: amd64 > beta.kubernetes.io/instance-type: m4.xlarge > beta.kubernetes.io/os: linux
(In reply to Antonio Murdaca from comment #5) It was explicitly deleted to trigger the bug. I don't think it's possible to get into this situation without user error (right now), but the problem is that it prevents the controller from recovering and can block other important functions by blocking all annotation updates.
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:0826