Bug 1461346
| Summary: | Old statefulset resources'event displayed for new statefulset of same name | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | shahan <hasha> | ||||
| Component: | Management Console | Assignee: | Samuel Padgett <spadgett> | ||||
| Status: | CLOSED ERRATA | QA Contact: | XiaochuanWang <xiaocwan> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 3.6.0 | CC: | aos-bugs, jforrest, jokerman, mmccomas, spadgett, wmeng | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
When deleting a resource and creating a new resource with the same name, it was possible to see events for the old, deleted resource in the web console on the new resource's page. This has been fixed. Now only events for the new resource will display in the web console even when the name is reused.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-08-10 05:28:09 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
shahan
2017-06-14 09:22:00 UTC
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 |