Bug 1900067

Summary:	Console Node Details uses incorrect filesystem size for utilitzation summary graph
Product:	OpenShift Container Platform	Reporter:	Naveen Malik <nmalik>
Component:	Management Console	Assignee:	Rastislav Wagner <rawagner>
Status:	CLOSED DUPLICATE	QA Contact:	Yadan Pei <yapei>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.5	CC:	aos-bugs, jhadvig, jokerman
Target Milestone:	---	Keywords:	UpcomingSprint
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-04 10:00: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:

Description Naveen Malik 2020-11-20 17:44:50 UTC

Created attachment 1731356 [details]
Node Details screenshot showing incorrect Utilization

Description of problem:
OSD customer cluster on 4.5.11 shows incorrect utilization in Node Details page.  This is causing confusion and concern.  This is not happening on other clusters.

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

How reproducible:
Unknown

Steps to Reproduce:
1. Unknown
2.
3.

Actual results:
Filesystem summary utilization is based on incorrect available root filesystem bytes.  Causes graph to be RED and total available bytes to be NEGATIVE.

Expected results:
Filesystem summary utilization is based on correct available root filesystem bytes.  Graph is blue and total bytes is positive assuming sufficient storage.

Additional info:
Investigation is open on a master restart that occurred on the cluster.
Remediation on OSD for https://bugzilla.redhat.com/show_bug.cgi?id=1891815 restarts prometheus-operator pod on all 4.5.z clusters.  This is noted in case it impacts this issue though it's not expected to be related.

Must gather will be added after it is completed.

Comment 4 Jakub Hadvig 2020-12-23 16:17:07 UTC

We did not have time to fix this issue this sprint. Will reevaluate and try to fix in next sprint.

Comment 5 Rastislav Wagner 2021-01-04 10:00:52 UTC

I think this is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1893601 which is fixed for 4.7, 4.6 and there's also pending backport for 4.5

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