Bug 1471230

Summary: [backport request] Multiple ExecStarts do no work properly
Product: Red Hat Enterprise Linux 7 Reporter: Frank Hirtz <fhirtz>
Component: systemdAssignee: systemd-maint
Status: CLOSED ERRATA QA Contact: Frantisek Sumsal <fsumsal>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 7.3CC: fsumsal, msekleta, systemd-maint-list
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: systemd-219-47.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-10 11:21:21 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:
Bug Depends On:    
Bug Blocks: 1420851    

Description Frank Hirtz 2017-07-14 18:37:56 UTC
What problem/issue/behavior are you having trouble with?  What do you expect to see?

Multiple ExecStarts don't work properly in the systemd version presently in RHEL7

Where are you experiencing the behavior?  What environment?

All systemd versions in RHEL7

When does the behavior occur? Frequently?  Repeatedly?   At certain times?

Repeatedly, always.

What information can you provide on timeframes and the business impact?

The client has to work around this my making wrapper scripts rather than using systemd as intended. 

To correct this, the client has requested that we backport the upstream fix outlined in:

https://github.com/systemd/systemd/issues/518

Via the commit in:

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

The client would be happy to validate if that's needed.

Comment 3 Lukáš Nykrýn 2017-11-09 15:20:17 UTC
fix merged to staging branch -> https://github.com/lnykryn/systemd-rhel/pull/153 -> post

Comment 8 errata-xmlrpc 2018-04-10 11:21:21 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-2018:0711