Description of problem: errors on events tab of node page, the events items will disappear piece by piece. And will see errors in dev console of browser as bellow: default-resource.jsx:19 TypeError: t.resizeEvents is not a function at default-resource.jsx:19 at default-resource.jsx:19 at Array.forEach (<anonymous>) at o._invokeHandlers (default-resource.jsx:19) at o.flushMessageBuffer (default-resource.jsx:19) Version-Release number of selected component (if applicable): 4.2.0-0.nightly-2019-08-13-183722 How reproducible: Always Steps to Reproduce: 1. goto events tab of node page 2. 3. Actual results: the events items will disappear piece by piece. Expected results: should list the events correctly Additional info: 1. [hasha@fedora_pc ~]$ oc describe node zhsun2-4g7pw-m-0.c.openshift-gce-devel.internal |grep 'Events' -A 5 Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal NodeReady 159m kubelet, zhsun2-4g7pw-m-0.c.openshift-gce-devel.internal Node zhsun2-4g7pw-m-0.c.openshift-gce-devel.internal status is now: NodeReady
Created attachment 1603676 [details] record
Console error aside (which I've diagnosed and fixed in my WIP PR), this bug easily reproduces when the cluster is new (birth to 1 hour). It appears to occur when there are many (say 500) events being watched and the EventStream component is churning through them all (I think part of what the video is showing is the de-duplication of events). Further, it appears when the number of events exceeds 500, it's possible to not see *any* relevant events for a given resource (in this case, node) since the EventStream max is set to 500 and the relevant events could be being excluded by the limit. Will need @spadgett's help diagnosing when he's back from PTO tomorrow.
events page works well When events exceeds 500. Verified this bug 4.2.0-0.nightly-2019-08-15-223955
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-2019:2922