Bug 1386838
| Summary: | Old metrics displayed for new pod of same name | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Justin Pierce <jupierce> |
| Component: | Management Console | Assignee: | Samuel Padgett <spadgett> |
| Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.3.0 | CC: | aos-bugs, jokerman, mmccomas, tdawson, yanpzhan, zhezli |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
If you deleted a pod and created a new pod with the same name, you would see metrics for the previous pod when viewing metrics. We now only show metrics for the new pod.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2017-01-18 12:43:42 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: | |||
|
Description
Justin Pierce
2016-10-19 17:07:41 UTC
openshift v3.3.1.3 kubernetes v1.3.0+52492b4 etcd 2.3.0+git Checked on OCP 3.3.1.3, the bug can be reproduced. This has been merged into ose and is in OSE v3.4.0.16 or newer. Tested on OCP 3.4.0.16, Metrics deploying failed due to bug: https://bugzilla.redhat.com/show_bug.cgi?id=1388833, will continue to verify the after metrics works. Checked on OCP v3.4.0.18, metrics is deployed. Create a pod, after some time, view the metrics of the pod, then delete the pod, create a new pod with the same name, view the metrics of the new pod, the metrics charts are new for the pod, not using the old pod's metrics. The bug is fixed, so move it to Verified. 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-2017:0066 |