openstack
/
tripleo-ansible
Code Issues Proposed changes

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: I2d5f4e8c11384aeff3c0b1a2fdd5abb6a586522f
Closes-Bug: #1922179
Resolves: rhbz#1939910
(cherry picked from commit abbcab7d44)
This commit is contained in:
Cédric Jeanneret 2021-04-01 08:07:29 +02:00
parent fbbf98d46f
commit c71dd68039
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
tripleo_ansible/roles/tripleo-container-manage/templates/systemd-service.j2
View File

@ -12,7 +12,7 @@ ExecStart=/usr/bin/podman start {{ lookup('dict', container_data).key }}
ExecReload=/usr/bin/podman kill --signal HUP {{ lookup('dict', container_data).key }}
ExecStop=/usr/bin/podman stop -t {{ lookup('dict', container_data).value.stop_grace_period | default(10) | int }} {{ lookup('dict', container_data).key }}
ExecStopPost=/usr/bin/podman stop -t {{ lookup('dict', container_data).value.stop_grace_period | default(10) | int }} {{ lookup('dict', container_data).key }}
SuccessExitStatus=137 143
SuccessExitStatus=137 142 143
KillMode=none
Type=forking
PIDFile=/var/run/{{ lookup('dict', container_data).key }}.pid