Bug 736249

Summary:	ups service report failure if started via systemd in netclient mode
Product:	[Fedora] Fedora	Reporter:	Sergey Kryzhny <sergey.kryzhny>
Component:	nut	Assignee:	Michal Hlavinka <mhlavink>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	14	CC:	mhlavink, sergey.kryzhny
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-09-09 08:55:27 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Sergey Kryzhny 2011-09-07 07:10:25 UTC

Description of problem:
After configure nut to run in netclient mode, any attempt to start ups service in systemd-enabled OS result in reporting that service failed.


Version-Release number of selected component (if applicable):
nut-client.x86_64                   2.6.1-1.fc14                      @updates

How reproducible:
Always

Steps to Reproduce:
1. configure nut to use netclient mode. set SERVER=no in /etc/sysconfig/ups 
2. start ups service: sudo /etc/init.d/ups start
3.
  
Actual results:
systemd report service failure.

Expected results:
Running service with "active" status.

Additional info:
It fixed by adding RETVAL=0 in line 40 of /etc/init.d/ups
Script use uninitialized value in case of netclient mode.
Same problem must be also in Upstart-based systems, but without reporting error to logs.
Fedora15 has same bug.

Comment 1 Michal Hlavinka 2011-09-09 08:55:27 UTC

this is already fixed. Package is in updates-testing repository right now.

*** This bug has been marked as a duplicate of bug 732151 ***