Bug 1964322
| Summary: | UI, The status of "Used Capacity Breakdown [Pods]" is "Not available" | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | OpenShift BugZilla Robot <openshift-bugzilla-robot> | ||||
| Component: | Console Storage Plugin | Assignee: | suchita <sgatfane> | ||||
| Status: | CLOSED ERRATA | QA Contact: | suchita <sgatfane> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | urgent | ||||||
| Version: | 4.7 | CC: | aos-bugs, badhikar, jokerman, nberry, nthomas, sgatfane, skatiyar | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 4.7.z | ||||||
| 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-06-15 09:28:20 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | 1954460 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
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 (Moderate: OpenShift Container Platform 4.7.16 security and bug fix update), 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/RHSA-2021:2286 |
Created attachment 1790409 [details] Verified output of Used Capacity Breakdown The Output is tested on below version: OCP: 4.7.0-0.nightly-2021-06-10-213131 OCS: ocs-operator.v4.7.1-410.ci Verified o/p: "Used Capacity Breakdown" for "pods" is available and verified via UI on page "Home->Overview->Persistent Storage" Hence moving this bug to verified status.