Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1731859

Summary: Donut data is 0% instead of "No Data" or "No Request/Limit" when the resource does not have quota
Product: OpenShift Container Platform Reporter: XiaochuanWang <xiaocwan>
Component: Management ConsoleAssignee: Jon Jackson <jonjacks>
Status: CLOSED ERRATA QA Contact: Yadan Pei <yapei>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 4.2.0CC: aos-bugs, jokerman, mmccomas
Target Milestone: ---   
Target Release: 4.2.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: 2019-10-16 06:30:16 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 Flags
Verified and correct gauge for empty data none

Description XiaochuanWang 2019-07-22 08:39:47 UTC 
Description of problem:
Cluster admin go to Resource Quotas page and create a compute resource quota without "requests.cpu". The donut data displays "0%" instead of "No Data" or "No Request"

Version-Release number of selected component (if applicable):
4.2.0-0.nightly-2019-07-21-222447

How reproducible:
Always

Steps to Reproduce:
1. Cluster admin go to Resource Quotas page
2. Create a compute resource quota without "requests.cpu" for a project
3. After created, check the data in center of the "CPU Request" donut

Actual results:
3. Data is 0%. 
There is no text "used" under the 0%

Expected results:
3. It should be "No Data" or "No Request"

Additional info:
Comment 1 Jon Jackson 2019-07-23 16:41:37 UTC 
I have a design question about this: Why are we even displaying an empty gauge for resource types that don't exist on a quota? Could we just omit resource types that are not included in a quota?
Comment 3 XiaochuanWang 2019-08-12 08:10:49 UTC 
This is verified on latest console from Payload 4.2.0-0.nightly-2019-08-10-002649
Image: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:ddc29d8fa071edfedc9ef1051db3d84efb13815cc74ab88c0ec597bccbee34e2
Comment 4 XiaochuanWang 2019-08-12 08:11:35 UTC 
Created attachment 1602751 [details]
Verified and correct gauge for empty data
Comment 5 errata-xmlrpc 2019-10-16 06:30:16 UTC 
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-2019:2922