Bug 1914424

Summary:	Cluster utilization pod count shows terminal pods
Product:	OpenShift Container Platform	Reporter:	Derek Carr <decarr>
Component:	Management Console	Assignee:	Rastislav Wagner <rawagner>
Status:	CLOSED DUPLICATE	QA Contact:	Yadan Pei <yapei>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.7	CC:	abraren, aos-bugs, jokerman, spadgett
Target Milestone:	---
Target Release:	4.7.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-01-08 20:10:46 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 Derek Carr 2021-01-08 19:42:51 UTC

Description of problem:
Cluster utilization pod count shows terminal pods in count

Version-Release number of selected component (if applicable):
4.7-nightly

How reproducible:
Always

Steps to Reproduce:
1. install openshift
2. visit console overview page
3. see cluster utilization "pods" count

Actual results:
Pod count includes pods in terminal state that should not count to utilization.  


Expected results:
Pod count should only include pods that did not reach a terminal state as they represent actual utilization.


Additional info:
Including terminal pods may confuse users when wondering why a cluster may not autoscale, or how number of pods used exceed schedulable pod capacity.

Comment 1 Samuel Padgett 2021-01-08 19:44:56 UTC

Andy, let me know if you have any concerns with this change.

Comment 2 Derek Carr 2021-01-08 19:58:45 UTC

Clayton has a new metric that appears to give the right output.

Comment 3 Samuel Padgett 2021-01-08 20:10:46 UTC

Looks like Clayton is handling this under bug 1914427.

*** This bug has been marked as a duplicate of bug 1914427 ***