Created attachment 911308 [details] screensot of Trends Description of problem: Volume utilization graph for a particular volume is NOT showing the graph for all the bricks of that volume. Version-Release number of selected component (if applicable): rhsc-3.0.0-0.11.el6_5.noarch nagios-server-addons-0.1.4-1.el6rhs.x86_64 pnp4nagios-0.6.20-1.1.el6rhs.x86_64 How reproducible: 100% Steps to Reproduce: 1. Login to RHSC 2. From the 'Tree' mode, Select any secific Volume and click on the "Trends" tab Actual results: Trends is currently showing the last-24-hours volume utilization graph for that volume. Expected results: As per the Acceptance Criteria, along with the last-24-hours volume utilization graph for a specific volume, Trends tab should also show graph for all the bricks of that volume. Additional info: Screenshot attached.
This I could reproduce only when the graphs were not even available in pnp4nagios. Can you please confirm if this happens even when graphs are available in pnp4nagios.
(In reply to anmol babu from comment #1) > This I could reproduce only when the graphs were not even available in > pnp4nagios. Can you please confirm if this happens even when graphs are > available in pnp4nagios. You are right, I think this also got fixed as part of the Brick Utilization bug. Is that correct?? Now I'm able to see the graphs for all the bricks in a volume as the graphs are available in pnp4nagios!
Yes you are correct.
(In reply to anmol babu from comment #3) > Yes you are correct. Thanks for confirming the same. If that is the case, this bug actually depends on the Brick Utilization bug as the fix is the same, which we identified a bit later. However since the reproducer is different for these 2 issues, I would suggest you to target this bug also for 3.0 and move it to ON_QA for further verification from QE side.
Anmol, Are you sure that the FIV is rhsc-3.0.0-12.el6rhs?? I'm asking because, I don't see a build called "rhsc-3.0.0-12.el6rhs" attached to the Errata. Please clarify.
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. http://rhn.redhat.com/errata/RHEA-2014-1277.html