Bug 1107998

Summary: [Nagios] Auto-config removes all the configuration if the host used for discovery is detached from the cluster
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Kanagaraj <kmayilsa>
Component: nagios-server-addonsAssignee: Ramesh N <rnachimu>
Status: CLOSED ERRATA QA Contact: Shruti Sampat <ssampat>
Severity: high Docs Contact:
Priority: high    
Version: rhgs-3.0CC: asrivast, dpati, esammons, kmayilsa, knarra, sankarshan
Target Milestone: ---   
Target Release: RHGS 3.0.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: nagios-server-addons-0.1.3-2.el6rhs.x86_64 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1139228 (view as bug list) Environment:
Last Closed: 2014-09-22 19:11:13 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: 1139228    

Description Kanagaraj 2014-06-11 09:23:25 UTC
Description of problem:
Auto configuration removes all the configurations(hosts,volumes, bricks) from Nagios if the host used for discovery is no longer part of the cluster

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Create a cluster with 3 nodes (HostA, HostB, HostC).
2. Create some volumes and start them
3. Run discovery script by providing name of the cluster and ip of HostA
4. Make sure all the volumes/hosts show up in nagios UI
5. Detach HostA from the cluster using "gluster peer detach" command
6. Re-schedule the auto-config in nagios ui

Actual results:
Except HostA all other hosts/volumes removed from the nagios configuration.

Expected results:
hosts/volumes should not removed from the nagios configuration. User should run the discovery by providing the ip of HostB.

Additional info:

Comment 1 Ramesh N 2014-06-11 10:39:22 UTC
Patch sent upstrean : http://review.gluster.org/#/c/8024/

Comment 2 Shruti Sampat 2014-06-17 11:50:44 UTC
Verified as fixed in nagios-server-addons-0.1.4-1.el6rhs.x86_64

Performed the following steps -

1. Created a cluster of four nodes, host1, host2, host3 and host4.
2. Created a couple of volumes, and started them.
3. Configured this cluster to be monitored via nagios server, which is also one of the RHS nodes.
4. Removed host4 from the cluster using gluster peer detach command.
5. Attempted to run cluster auto-config service using the Nagios UI. Saw the status of the service change to critical with the following status information -

Can't remove all hosts except sync host in 'auto' mode. Run auto discovery manually

6. Ran auto-discovery at the nagios server using command line, manually -

# /usr/lib64/nagios/plugins/gluster/discovery.py -c cluster_auto -H host1

Cluster configurations changed

Changes :
Hostgroup cluster_auto - UPDATE
Host cluster_auto - UPDATE
         Service - Cluster Auto Config -UPDATE 
Host host4 - REMOVE
Are you sure, you want to commit the changes? (Yes, No) [Yes]: 
Cluster configurations synced successfully from host host1
Do you want to restart Nagios to start monitoring newly discovered entities? (Yes, No) [Yes]: 
Nagios re-started successfully

In the Nagios UI, the host host4 was removed, and the status of the cluster auto-config service changed to OK.

Comment 3 errata-xmlrpc 2014-09-22 19:11:13 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.

http://rhn.redhat.com/errata/RHEA-2014-1277.html