Bug 1157938

Summary:	service or init.d invoke systemd-run which does not exist in FC-19
Product:	[Fedora] Fedora	Reporter:	vishalcdac07
Component:	ceph	Assignee:	Boris Ranto <branto>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	19	CC:	branto, david, fedora, johannbg, jsynacek, lnykryn, msekleta, s, steve, systemd-maint, vishalcdac07, vpavlin, zbyszek
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	ceph-0.80.5-11.fc19	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-11-12 02:41:17 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 vishalcdac07 2014-10-28 04:53:25 UTC

Description of problem:
"service" or init.d tries to be replaced with systemd-run command, though the latest version on FC-19 (i.e. systemd-204-21) does not contain systemd-run command. The support is started from systemd-205.  

Version-Release number of selected component (if applicable):
FC-19 and systemd-204-21

How reproducible:
Always (when subcommand is used to start daemon inside some upper level service) using "service" or "init.d"

Steps to Reproduce:
1. Start monitor daemon of ceph 
$ sudo service ceph restart mon.localhost.localdomain
2. Following output is received:
=== mon.localhost.localdomain === 
Starting Ceph mon.localhost.localdomain on localhost...
bash: systemd-run: command not found

Above outcome is also encountered when used with 
$ sudo /etc/init.d/ceph start mon.localhost.localdomain

Actual results:
Starting the daemon returns with error systemd-run: command not found.  

Expected results:
Either supported systemd package should contain systemd-run utility or it should use the other method (traditional) for starting daemon inside some service. 

Additional info:

Comment 1 vishalcdac07 2014-10-28 05:04:42 UTC

$ sudo service ceph restart mon.localhost.localdomain

Above command is actually 
$ sudo service ceph start mon.localhost.localdomain

Comment 2 Fedora Update System 2014-10-31 03:56:07 UTC

ceph-0.80.5-11.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/ceph-0.80.5-11.fc19

Comment 3 Fedora Update System 2014-11-01 01:39:58 UTC

Package ceph-0.80.5-11.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing ceph-0.80.5-11.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2014-14026/ceph-0.80.5-11.fc19
then log in and leave karma (feedback).

Comment 4 vishalcdac07 2014-11-05 09:52:52 UTC

I would be interested to know the cause for this issue.
Thanks

Comment 5 Boris Ranto 2014-11-05 10:06:39 UTC

It is quite simple -- the ceph init script tries to detect whether the init system is systemd (whether the pid 1 is systemd) and in that case it runs the daemon via systemd-run. However, that binary first appeared in post-f19 systemd version. The fix is to not run the daemon via systemd-run in f19.

btw: Were you able to test the latest packages to see if they fixed your issue?

Comment 6 Fedora Update System 2014-11-12 02:41:17 UTC

ceph-0.80.5-11.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.