diff options
| author | Valentin Rothberg <vrothberg@redhat.com> | 2022-07-27 15:24:02 +0200 |
|---|---|---|
| committer | Matthew Heon <mheon@redhat.com> | 2022-08-10 16:46:05 -0400 |
| commit | 5b5e53d70414aafdc6e9bddfe49c23f6a789b1c6 (patch) | |
| tree | 82f2aa09860994f5525cf5a79ceffac4f6307e12 /OWNERS | |
| parent | b7feafcb063bd152e4637b80684c82a4afbf9a98 (diff) | |
| download | podman-5b5e53d70414aafdc6e9bddfe49c23f6a789b1c6.tar.gz podman-5b5e53d70414aafdc6e9bddfe49c23f6a789b1c6.tar.bz2 podman-5b5e53d70414aafdc6e9bddfe49c23f6a789b1c6.zip | |
syncContainer: transition from `stopping` to `exited`
Allow the cleanup process (and others) to transition the container from
`stopping` to `exited`. This fixes a race condition detected in #14859
where the cleanup process kicks in _before_ the stopping process can
read the exit file. Prior to this fix, the cleanup process left the
container in the `stopping` state and removed the conmon files, such
that the stopping process also left the container in this state as it
could not read the exit files. Hence, `podman wait` timed out (see the
23 seconds execution time of the test [1]) due to the unexpected/invalid
state and the test failed.
Further turn the warning during stop to a debug message since it's a
natural race due to the daemonless/concurrent architecture and nothing
to worry about.
[NO NEW TESTS NEEDED] since we can only monitor if #14859 continues
flaking or not.
[1] https://storage.googleapis.com/cirrus-ci-6707778565701632-fcae48/artifacts/containers/podman/6210434704343040/html/sys-remote-fedora-36-rootless-host.log.html#t--00205
Fixes: #14859
Signed-off-by: Valentin Rothberg <vrothberg@redhat.com>
Diffstat (limited to 'OWNERS')
0 files changed, 0 insertions, 0 deletions