Bug 1513002
Summary: | Disk load utilization | ||
---|---|---|---|
Product: | [Red Hat Storage] Red Hat Gluster Storage | Reporter: | Lubos Trilety <ltrilety> |
Component: | web-admin-tendrl-monitoring-integration | Assignee: | Ankush Behl <anbehl> |
Status: | CLOSED ERRATA | QA Contact: | Bala Konda Reddy M <bmekala> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | rhgs-3.3 | CC: | bmekala, ltrilety, mkudlej, nthomas, ppenicka, sankarshan |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | tendrl-monitoring-integration-1.5.4-4.el7rhgs.noarch | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2017-12-18 04:39:57 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: |
Description
Lubos Trilety
2017-11-14 15:03:28 UTC
@ltrilety >> The Disk load utilization displays zero. The Disk load utilization issue has been fixed and now the panel has got the value. But the label Issue is not fixed and we can track all the label related issues in a single bug. I think in this https://bugzilla.redhat.com/show_bug.cgi?id=1511687 we can track it. I am fine with that if the title of the bug will be changed accordingly. Adding PM ack for 3.3.z since dev provided theirs. Verified in tendrl-monitoring-integration-1.5.4-5.el7rhgs.noarch On an imported gluster cluster, pumped IO's on multiple volumes in the cluster. The information on the Bricks Dashboard, for disk utilization is showing correct information with time for different bricks. Hence marking the bug as 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, 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/RHEA-2017:3478 |