Bug 1167305
| Summary: | [RHSC] Trends tab for volumes does not show thin-pool utilization graphs in addition to brick utilization graphs | ||
|---|---|---|---|
| Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Shruti Sampat <ssampat> |
| Component: | rhsc | Assignee: | Ramesh N <rnachimu> |
| Status: | CLOSED CANTFIX | QA Contact: | RHS-C QE <rhsc-qe-bugs> |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | rhgs-3.0 | CC: | anbabu, asriram, nlevinki, rhs-bugs, rhsc-qe-bugs, rnachimu, sankarshan, shtripat |
| Target Milestone: | --- | Keywords: | ZStream |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Known Issue | |
| Doc Text: |
The Trends tab on the Red Hat Storage Console does not display the thin-pool utilization graphs in addition to the brick utilization graphs. Currently, there is no mechanism for the UI plugin to detect if the volume is provisioned using thin provisioning
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-01-29 15:13:03 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1153907 | ||
|
Description
Shruti Sampat
2014-11-24 12:40:02 UTC
Hi Shubhendu, I see this bug added as a known issue in the known issue tracker bug (1153907) for the 3.0.3 release. Can you please change the doc type field to Known Issue add the doc text for this? Hi Anmol, Can you please review the edited doc text for technical accuracy and sign off? Looks good to me In addition to thin-pool space utilization graphs, the inode usage and thin-pool metadata usage graphs are also missing in the RHSC trends tab for volumes. The inode usage and thin-pool metadata usage graphs were added as part of fix for BZ #1167771 Thank you for your report. This bug is filed against a component for which no further new development is being undertaken |