Bug 1135983

Summary:	[Nagios] Disk utilization service need not monitor disks that are already monitored as part of brick utilization service
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	Shruti Sampat <ssampat>
Component:	gluster-nagios-addons	Assignee:	Darshan <dnarayan>
Status:	CLOSED ERRATA	QA Contact:	Shruti Sampat <ssampat>
Severity:	medium	Docs Contact:
Priority:	high
Version:	rhgs-3.0	CC:	dnarayan, dpati, knarra, nsathyan, rhsc-qe-bugs, rnachimu, sgraf, sharne
Target Milestone:	---	Keywords:	ZStream
Target Release:	RHGS 3.0.4
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	gluster-nagios-addons-0.1.16-1.el6rhs	Doc Type:	Bug Fix
Doc Text:	Previously, disks that form bricks were monitored redundantly in both disk utilization and brick utilization service as Disk utilization service monitored all the disks available in the system. With this fix, redundant monitoring of disks is avoided as disk utilization monitors only / , /boot , /home , /var, and /usr mount points.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-26 06:32:53 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:	1182947

Description Shruti Sampat 2014-09-01 12:01:32 UTC

Description of problem:
-------------------------

Currently the disk utilization service monitors all mounted partitions on the RHS node being monitored by nagios. The disks that are used as bricks are monitored also by the brick utilization service. So it would be a good idea not to monitor these disks using the disk utilization service in addition to the brick utilization service.

Version-Release number of selected component (if applicable):
--------------------------------------------------------------
gluster-nagios-addons-0.1.10-2.el6rhs.x86_64
nagios-server-addons-0.1.6-1.el6rhs.noarch

How reproducible:
Always

Steps to Reproduce:
1. Monitor an RHS node using nagios.
2. Observe the brick utilization service and the disk utilization service.

Actual results:
Disks that are being used as bricks are monitored both using the brick utilization service as well as the disk utilization service.

Expected results:
Nagios need not monitor disks that are used as bricks using the disk utilization service as they are already monitored using the brick utilization service.

Additional info:

Comment 3 RamaKasturi 2014-12-31 09:17:55 UTC

This issue causes disk utilization to show older bricks even after a snapshot is restored.

Consider a case where there is a volume called "vol1".

1) User takes a snapshot of the volume.
2) Once the snap is taken, the volume has been filled with data so that utilization is reached to 100 percent.
3) Now user restores the volume and the restored volume does not have data in it.
4) Volume utilization, brick utilization goes to zero percent once the restore is performed.
5) Disk utilization still shows as critical.

Comment 4 Dusmant 2015-01-12 09:54:14 UTC

monitor only the 4 mount points, which are needed for the system operation

Comment 6 Darshan 2015-02-18 06:47:26 UTC

Disk utilization service is modified to monitor only the following mount points: / , /boot , /home , /var , /usr.

Comment 7 Darshan 2015-02-18 09:27:49 UTC

patch: http://review.gluster.org/#/c/9673/

Comment 9 Shruti Sampat 2015-03-05 09:24:46 UTC

Verified as fixed in gluster-nagios-addons-0.1.16-1.el6rhs.x86_64

Disk utilization service now monitors the following mount points -
/, /boot, /home, /var and /usr

Tested for space and inode utilization monitoring for the above partitions.

Comment 10 Shalaka 2015-03-13 07:13:27 UTC

Please review and sign-off edited doc text.

Comment 11 Darshan 2015-03-16 05:42:41 UTC

looks good.

Comment 13 errata-xmlrpc 2015-03-26 06:32:53 UTC

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://rhn.redhat.com/errata/RHBA-2015-0681.html