Bug 1417459

Summary:	systemctl enable --now don't start the service
Product:	Red Hat Enterprise Linux 7	Reporter:	Gal Ben Haim <gbenhaim>
Component:	systemd	Assignee:	Jan Synacek <jsynacek>
Status:	CLOSED ERRATA	QA Contact:	Branislav Blaškovič <bblaskov>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	7.3	CC:	bblaskov, jsynacek, systemd-maint-list, ykaul
Target Milestone:	rc	Keywords:	EasyFix, Patch
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	systemd-219-32.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-01 09:14:52 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 Gal Ben Haim 2017-01-29 15:13:10 UTC

Description of problem:

If a service is already enabled, running "systemctl enable --now" will not start it.

Version-Release number of selected component (if applicable):
systemd-219-30.el7.x86_64

How reproducible:


Steps to Reproduce:
1. run "systemctl enable --now" on a service which is already enabled.

Actual results:
The service won't start and the exit code is 0.

Expected results:
Start the service or return an exit code different from 0. 

Additional info:

Comment 2 Jan Synacek 2017-02-02 14:14:16 UTC

https://github.com/systemd/systemd/pull/5209

Comment 3 Jan Synacek 2017-02-09 11:39:21 UTC

https://github.com/lnykryn/systemd-rhel/pull/90

Comment 5 Lukáš Nykrýn 2017-02-20 11:03:44 UTC

fix merged to upstream staging branch ->
https://github.com/lnykryn/systemd-rhel/commit/10bf9c070764d09a4b39aa65ccba8b7501918a34
-> post

Comment 8 errata-xmlrpc 2017-08-01 09:14:52 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.

https://access.redhat.com/errata/RHBA-2017:2297