Bug 1824445
| Summary: | inner circle of resource quota donut show wrong available value | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Yadan Pei <yapei> |
| Component: | Management Console | Assignee: | Joe Caiani <jcaiani> |
| Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 4.5 | CC: | aos-bugs, dtaylor, jokerman, spadgett, yapei |
| Target Milestone: | --- | ||
| Target Release: | 4.6.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: | 2020-10-27 15:57:47 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: | |||
moved to upcoming sprint: will investigate and fix in the upcoming bug fix sprint low priority will investigate in upcoming sprint I believe this is the same bug with bug 1848512, so also move 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 (OpenShift Container Platform 4.6 GA Images), 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-2020:4196 |
Description of problem: When we hover the inner circle of resource quota donut, it shows 'xxx available' but the value is wrong, currently the value is the same as used value Version-Release number of selected component (if applicable): 4.5.0-0.nightly-2020-04-15-194358 How reproducible: Always Steps to Reproduce: 1. cluster admin creates resource quota for project # cat resource-quota.yaml apiVersion: v1 kind: ResourceQuota metadata: creationTimestamp: null name: quota spec: hard: cpu: "1" memory: 750Mi pods: "10" replicationcontrollers: "10" resourcequotas: "1" services: "10" status: {} # oc create -f resource-quota.yaml -n yapei-1 resourcequota/quota created 2. before we create workloads, check resource quota usage at Administration -> Resource Quotas -> quota details page, it shows 0% used 3. create some workloads, such as Deployment Config from console using example YAML, after pods are running, check resource quota usage again, it shows 60% used for CPU Request, 40% used for Memory Request in chart 4. hover the inner circle of the chart 5. hover the outer circle of the chart Actual results: 4. it shows '60 available', '40 available' 5. nothing shows Expected results: 4. If inner circle presents usage, it should show correct usage used in this project. 5. Not sure what's the usage of outer circle Additional info: