Bug 1613527
| Summary: | Description of Capacity Available panel on Brick dashboards refers to a volume by mistake | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Martin Bukatovic <mbukatov> | ||||||
| Component: | web-admin-tendrl-monitoring-integration | Assignee: | gowtham <gshanmug> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Elena Bondarenko <ebondare> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | rhgs-3.4 | CC: | apaladug, ebondare, mbukatov, nthomas, rhinduja, rhs-bugs, sankarshan | ||||||
| Target Milestone: | --- | Keywords: | ZStream | ||||||
| Target Release: | RHGS 3.4.z Batch Update 1 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | tendrl-monitoring-integration-1.6.3-13.el7rhgs | Doc Type: | If docs needed, set a value | ||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2018-10-31 08:45:18 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
Martin Bukatovic
2018-08-07 18:33:06 UTC
Created attachment 1474075 [details]
screenshot 1: "Capacity Available" panel on Brick dashboard with wrong description
Created attachment 1479438 [details]
Brick dashboard
please check this screenshot, is this the expectation? Proposed description: Utilization over a period of time for the device where the brick is mounted. Looks ok (technically correct) to me. julim need your suggestion on this The description now is
> The Capacity Available panel displays the available capacity for a given brick.
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-2018:3427 |