Bug 1643948
Summary: | Cluster console doesn't display the real value of Crashlooping Pods (it displays 0) | ||||||
---|---|---|---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Alberto Gonzalez de Dios <algonzal> | ||||
Component: | Management Console | Assignee: | Samuel Padgett <spadgett> | ||||
Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> | ||||
Severity: | low | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 3.11.0 | CC: | aos-bugs, jokerman, mmccomas, rsandu, smunilla, spadgett, yapei | ||||
Target Milestone: | --- | ||||||
Target Release: | 3.11.z | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: |
Previously, the cluster console in OpenShift 3.11 would always show the value "0" for the Crashlooping Pods count on the cluster status page even when there were crashlooping pods. The problem has been fixed, and the count now accurately reflects the count for the selected projects.
|
Story Points: | --- | ||||
Clone Of: | Environment: | ||||||
Last Closed: | 2018-11-20 03:11:52 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
Alberto Gonzalez de Dios
2018-10-29 14:17:20 UTC
1. create dummy pods 2. check status on cluster consoleļ¼ Pods page and Home -> Status page Crashlooping Pods are NOT showing on Status page, recording in attachment apiVersion: v1 kind: Pod metadata: name: dummy-pod spec: containers: - name: dummy-pod image: ubuntu restartPolicy: Always Verify the bug on openshift v3.11.38 (In reply to Yadan Pei from comment #5) > 1. create dummy pods > > 2. check status on cluster consoleļ¼ Pods page and Home -> Status page > > Crashlooping Pods are NOT showing on Status page, recording in attachment We're querying Prometheus for pods with 5 container restarts within the last 5 minutes. It might take a few minutes to update (as you've found). Thanks for the info Sam 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-2018:3537 |