Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
$subject

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

How reproducible:
always

Steps to Reproduce:
1. Have following unit file,

$ cat /etc/systemd/system/crasher.service
[Service]
ExecStartPre=/bin/sleep 10
ExecStart=/bin/true

2. Reload systemd
$ systemctl daemon-reload

3. Start the service, remove unit file and reload systemd
$ systemctl --no-block start crasher.service && rm -f /etc/systemd/system/crasher.service && systemctl daemon-reload

4. Wait for 10 seconds

Actual results:
Feb 13 06:30:16 qeos-82.lab.eng.rdu2.redhat.com systemd[1]: Caught <ABRT>, dumped core as pid 1377.
Feb 13 06:30:16 qeos-82.lab.eng.rdu2.redhat.com systemd[1]: Freezing execution.

Above messages in journal, systemd is not responding to requests.

Expected results:
systemd can handle situation gracefully

Additional info:
upstream fix, 

https://github.com/systemd/systemd/commit/47fffb3530af3e3ad4048570611685635fde062e

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

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

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