Files
Matt Heon 8f1e58d9f8 [v4.4.1-rhel] Ensure that containers do not get stuck in stopping
The scenario for inducing this is as follows:
1. Start a container with a long stop timeout and a PID1 that
   ignores SIGTERM
2. Use `podman stop` to stop that container
3. Simultaneously, in another terminal, kill -9 `pidof podman`
   (the container is now in ContainerStateStopping)
4. Now kill that container's Conmon with SIGKILL.
5. No commands are able to move the container from Stopping to
   Stopped now.

The cause is a logic bug in our exit-file handling logic. Conmon
being dead without an exit file causes no change to the state.
Add handling for this case that tries to clean up, including
stopping the container if it still seems to be running.

Fixes #19629

Addresses: https://issues.redhat.com/browse/ACCELFIX-250

Signed-off-by: Matt Heon <mheon@redhat.com>
Signed-off-by: tomsweeneyredhat <tsweeney@redhat.com>
2024-06-24 18:37:06 -04:00
..
2022-01-18 12:47:07 +01:00
2017-11-01 11:24:59 -04:00
2022-12-15 13:39:56 +01:00
2022-10-17 09:19:41 +02:00
2022-01-18 12:47:07 +01:00
2023-01-27 09:14:12 +00:00
2022-09-20 15:34:27 -04:00
2022-09-10 07:52:00 -04:00
2022-09-10 07:52:00 -04:00
2022-09-10 07:52:00 -04:00
2023-01-27 19:48:26 +00:00
2022-04-25 13:23:20 +02:00
2024-02-02 09:25:17 -05:00
2022-09-01 13:02:01 -04:00
2022-10-17 09:19:41 +02:00
2022-12-15 13:39:56 +01:00
2022-01-18 12:47:07 +01:00
2022-07-21 14:50:01 -04:00
2022-09-10 07:52:00 -04:00
2022-01-18 12:47:07 +01:00