[systemd-bugs] [Bug 51301] New: ignore_errors ineffective when daemon_reload performed while relevant process is running

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=51301

             Bug #: 51301
           Summary: ignore_errors ineffective when daemon_reload performed
                    while relevant process is running
    Classification: Unclassified
           Product: systemd
           Version: unspecified
          Platform: x86-64 (AMD64)
        OS/Version: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: general
        AssignedTo: systemd-bugs at lists.freedesktop.org
        ReportedBy: ataraxia937 at gmail.com
         QAContact: systemd-bugs at lists.freedesktop.org


Created attachment 63309
  --> https://bugs.freedesktop.org/attachment.cgi?id=63309
test case

When using a leading '-' in ExecStart, if a daemon-reload is performed while
the command in question is still running, and it then exits with an abnormal
status, the unit will enter the failed state, just as if the '-' had not been
present.

This is easily reproduced by a trivial service unit and an equally trivial
shell script, which I will attach as a test case.

I'm running systemd 185 on Arch Linux.

Detailed steps to reproduce:
1. Download the attachment and unpack it under /. This will put a shell script
in /tmp/tf and a unit in /etc/systemd/system/tf.service .
2. Start tf.service. Check its status after 10 seconds have gone by. Observe
that it exited with code 1, and systemd correctly ignored this exit-code.
2. Start tf.service again. Do a daemon-reload within the next 10 seconds
(before /tmp/tf exits). Again check its status after 10 seconds have gone by.
Observe that it again exited with code 1, but this time, systemd didn't ignore
the exit-code, and the job incorrectly entered the failed state.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA Contact for the bug.
You are the assignee for the bug.