Red Hat Bugzilla – Bug 1111828
[Nagios] - Brick Utilization graphs gives Framework error once the volume is restored using its snapshot.
Last modified: 2018-01-30 02:54:52 EST
Created attachment 911061 [details] Attachment for brick utilization graph once the volume is restored. Description of problem: When volume is restored using its snapshot, graph for brick utilization gives 'FrameWork' error. Version-Release number of selected component (if applicable): nagios-server-addons-0.1.3-3.el6rhs.x86_64 How reproducible: Always Steps to Reproduce: 1. Create a volume and take snapshot of it by running the command "gluster snapshot create <snap_name> <vol_name>" 2. Now mount the volume and fill data in it. 3. Now restore the volume by using it snapshot by running the command "gluster snapshot restore <snap_name>". 4. Click on the brick utilization graph for the newly restored bricks. Actual results: Clicking on brick utilization gives 'FrameWork Error'. Expected results: Brick utilization graph should be displayed properly. Additional info:
What is the status of the brick shown in Nagios UI in this case?
Shubhendu, status of the brick is down. However i think utilization does not depend on the status of the brick AFAIK.
Please review and signoff edited doc text.
I feel it should be as below "In Nagios UI, Brick Utilization graph displays an error when volume is restored using its snapshot."
Removed from known issues
Hi kanagaraj, I see that this bug has been removed from the known issue list, if a fix is been available for this bug could you please fill in the FIV and move the bug to on_qa? Thanks kasturi.
Created attachment 919571 [details] Brick utilization graph after snapshot restore
Name of the brick does not appear correctly on the graph once the snapshot is restored.
Moving it to 3.0.3
Thank you for the bug report. However, closing this as the bug is filed against gluster nagios monitoring for which no further new development is being undertaken.