Bug 1371723

Summary:	nsca init script is not lsb compliant
Product:	[Fedora] Fedora EPEL	Reporter:	ellison.marks
Component:	nsca	Assignee:	Xavier Bachelot <xavier>
Status:	CLOSED WORKSFORME	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	el6	CC:	marianne, xavier
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-09-29 19:31:37 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:

Description ellison.marks 2016-08-31 00:01:40 UTC

Description of problem:

When running any actions using the nsca init script, the return value is always 0. This is due to the last line in the file being `exit 0`. This is affecting us when trying to manage nsca with puppet. No matter what state nsca is actually in, puppet believes it is running, as `service nsca status` returns 0.

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

2.7.2-8

How reproducible:

Always

Steps to Reproduce:
1. ensure nsca is stopped
2. run `service nsca status`
3. run `echo $?`

Actual results:

0

Expected results:

3

Additional info:

Comment 1 ellison.marks 2016-09-29 19:31:37 UTC

Looks like this is fixed in the version in epel-testing, 2.9.1-4 at the time of this writing. Closing.