The aws-controller is writing the "Updated machine zzzzzzz" events out every ~10 minutes for every single machine. I do not see any actual update to the Machine object occurring. This results in about 200 unnecessary events a day per machine. We should only be writing events when we are actually persisting updates to the Machine object.
Example of one of the events: Name: jforrest-demo-qqtgd-worker-us-east-2c-gwpg9.160122a5d5ec35c7 Namespace: openshift-machine-api Labels: <none> Annotations: <none> API Version: v1 Count: 192 Event Time: <nil> First Timestamp: 2020-03-30T16:43:59Z Involved Object: API Version: machine.openshift.io/v1beta1 Kind: Machine Name: jforrest-demo-qqtgd-worker-us-east-2c-gwpg9 Namespace: openshift-machine-api Resource Version: 1799350 UID: f936a8e3-7f00-485e-bf50-8fcbec30ec97 Kind: Event Last Timestamp: 2020-04-01T00:05:13Z Message: Updated machine jforrest-demo-qqtgd-worker-us-east-2c-gwpg9 Metadata: Creation Timestamp: 2020-03-30T16:43:59Z Resource Version: 2474472 Self Link: /api/v1/namespaces/openshift-machine-api/events/jforrest-demo-qqtgd-worker-us-east-2c-gwpg9.160122a5d5ec35c7 UID: 05b20a76-b741-43fa-86f0-ac66f074614b Reason: Updated Reporting Component: Reporting Instance: Source: Component: aws-controller Type: Normal Events: <none>
Looking in the web console, I am able to see the updating events that were seen before for any of the machines in my cluster. I am able to see the text "No events in the past hour" for all my worker machines. $oc version -o yaml clientVersion: buildDate: "2020-04-20T06:10:05Z" compiler: gc gitCommit: 4fb2d4d96e6b604f7d4ee49080238a5aec04dc4f gitTreeState: dirty gitVersion: openshift-clients-4.3.14-202004180552 goVersion: go1.12.12 major: "" minor: "" platform: linux/amd64 openshiftVersion: 4.5.0-0.nightly-2020-05-08-095803 releaseClientVersion: 4.3.15 serverVersion: buildDate: "2020-05-06T21:10:44Z" compiler: gc gitCommit: dfd05bf gitTreeState: clean gitVersion: v1.18.0-rc.1 goVersion: go1.13.4 major: "1" minor: 18+ platform: linux/amd64
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:2409