Bug 1719481
| Summary: | Project status page resource usage is not optimal | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Clayton Coleman <ccoleman> | ||||||
| Component: | Management Console | Assignee: | Jon Jackson <jonjacks> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Yadan Pei <yapei> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 4.2.0 | CC: | aos-bugs, jokerman, mmccomas, spadgett, xiaocwan | ||||||
| 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:31:56 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
Clayton Coleman
2019-06-11 23:01:46 UTC
Putting x-axis ticks at the left and right edges of the graph would show values that aren't round numbers. We opted to add the timestamp to the tooltip instead. The one item we didn't address is the OpenShift Console health widget. We'll look at that in a follow on. According to the expect fixing (https://github.com/openshift/console/pull/1727) The usage graph is correctly display now. Please refer to the screenshot. Verified on 4.2.0-0.nightly-2019-06-25-222454 Image: quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:18555084be5def960d447d20ce5074052bf6c012197e610f9d2ac947b1ddaea2 Created attachment 1584612 [details]
resource usage graph
Created attachment 1584613 [details]
Pod usage graph
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 |