Description of problem: The system generates too many unnecessary events sample : Generated from ovirtprovider. 616 times in the last 22 minutes Updated Machine ocp4-gw774-master-0 Version-Release number of selected component (if applicable): RHV Version 4.3.9.4-11.el7 OCP 4.4 rc11 How reproducible: Create a brand new cluster and you will see all these events Steps to Reproduce: 1. 2. 3. Actual results: Events: Generated from ovirtprovider. 616 times in the last 22 minutes Updated Machine ocp4-gw774-master-0 Expected results: No Event Additional info:
moved to OCP on RHV team
A success criteria here is to see that the frequency of the updates goes to once every few minutes, instead of everyt few seconds. A regression tests will be to make sure a machine gets updated if there is indeed something to change. like shutting down the VM and starting it again, which should be reflected as a change.
Verified with: openshift-install-linux-4.5.0-0.nightly-2020-05-26-051016 Verification steps: 1. I had both OCP4.4 cluster (where this is not implemented) and OCP4.5 cluster running alongside each other 2. I ran oc get events --watch on both of them 3. I could see that OCP4.4 cluster generated machine update events every ~ 4 minutes 4. OCP4.5 cluster generated update events only when I delete/created new worker machines 34m Normal Created machine/secondary-s5zgz-worker-0-fs959 Updated Machine secondary-s5zgz-worker-0-fs959 34m Normal Update machine/secondary-s5zgz-worker-0-fs959 Updated Machine secondary-s5zgz-worker-0-fs959 28m Normal Deleted machine/secondary-s5zgz-worker-0-fs959 Updated Machine secondary-s5zgz-worker-0-fs959 26m Normal Created machine/secondary-s5zgz-worker-0-nxsdq Updated Machine secondary-s5zgz-worker-0-nxsdq 26m Normal Update machine/secondary-s5zgz-worker-0-nxsdq Updated Machine secondary-s5zgz-worker-0-nxsdq 36m Normal Update machine/secondary-s5zgz-worker-0-pd7wp Updated Machine secondary-s5zgz-worker-0-pd7wp 34m Normal Deleted machine/secondary-s5zgz-worker-0-pd7wp Node "secondary-s5zgz-worker-0-pd7wp" drained
*** Bug 1839612 has been marked as a duplicate of this bug. ***
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