Accept 142 as an exit code
In the same fashion we accepted 137 and 143 exit code status in
I8f19a80016a67ccad0371c5d108516aec640f031, we also accept 142.
It represents the SIGALRM exit status - it happens when podman reaches
the set timeout (currently 60s) when trying to cleanly stop a container.
Change-Id: Ie4f72308fdd81ac69fd198f484a781cc43b84a73
Closes-Bug: #1922179
Resolves: rhbz#1939910
(cherry picked from commit d89f5697b9
)
This commit is contained in:
parent
68e5206abc
commit
9b6bef498a
|
@ -102,7 +102,7 @@ ExecStart=%(start_cmd)s
|
|||
ExecReload=/usr/bin/podman kill --signal HUP %(name)s
|
||||
ExecStop=/usr/bin/podman stop -t %(stop_grace_period)s %(name)s
|
||||
ExecStopPost=/usr/bin/podman stop -t %(stop_grace_period)s %(name)s
|
||||
SuccessExitStatus=137 143
|
||||
SuccessExitStatus=137 142 143
|
||||
KillMode=none
|
||||
Type=forking
|
||||
PIDFile=/var/run/%(name)s.pid
|
||||
|
|
Loading…
Reference in New Issue