Bug 1118184

Summary:	[Nagios] [RFE] - Start nagios as part of auto discovery script if it was not already started.
Product:	[Red Hat Storage] Red Hat Gluster Storage	Reporter:	RamaKasturi <knarra>
Component:	nagios-server-addons	Assignee:	Sahina Bose <sabose>
Status:	CLOSED CANTFIX	QA Contact:	RHS-C QE <rhsc-qe-bugs>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	rhgs-3.0	CC:	sabose
Target Milestone:	---	Keywords:	FutureFeature, ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-01-30 07:54:59 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 RamaKasturi 2014-07-10 07:26:33 UTC

Description of problem:
Start nagios as part of auto discovery script if it was not already started.

Version-Release number of selected component (if applicable):
nagios-server-addons-0.1.5-1.el6rhs.noarch

How reproducible:
Always.

Steps to Reproduce:
1. Install Nagios on RHS nodes.
2. Stop nagios server by running the command 'service nagios stop'
3. Now run the auto discovery script. 


Actual results:
Auto discovery script will display a message saying Cluster configurations synced successfully from host <IP-address-of-RHS-server>
'Start the Nagios service to monitor'

Expected results:
Instead of explicitly asking the user to start nagios, discovery.py should be able to start it automatically if it was not already started.

Additional info:

Comment 3 Sahina Bose 2018-01-30 07:54:59 UTC

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.