Created attachment 1287573 [details] The new statefulset events Description of problem: In the same namespace, if you delete a statefulset and create a new one with the same name, the old statefulset's events will be displayed as part of the new statefulset's events. This is similar to the old-new chart issue in https://bugzilla.redhat.com/show_bug.cgi?id=1386838 Version-Release number of selected component (if applicable): OpenShift Master:v3.6.106 (online version 3.5.0.20) Kubernetes Master:v1.6.1+5115d708d7 How reproducible: Always Steps to Reproduce: 1.Create statefulset resources # oc create -f https://raw.githubusercontent.com/openshift-qe/v3-testfiles/master/statefulset/statefulset-hello.yaml 2.Enter 'Application'->'Stateful Set'-> 'Events' page, check event messages 3. Delete the Statefulset, and create new one with same yaml file 4. Do step2. Actual results: 4. You see the old statefulset events were displayed as part of the new statefulset's events(see attachment) Expected results: 4. Only display the new statefulset events. Additional info: See same issue on free-int cluster.
https://github.com/openshift/origin-web-console/pull/1719
Commit pushed to master at https://github.com/openshift/origin-web-console https://github.com/openshift/origin-web-console/commit/bed0feeac9e270f737af8f454b7de72854281d33 Bug 1461346 - Filter events by UID Use the API object UID rather than kind and name to filter events. This prevents events for showing for a previous object with the same name.
Checked this issue, it was fixed. The new statefulset's events would not display the old.
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/RHEA-2017:1716