Make errors on removing exec sessions nonfatal #14258
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Removing exec sessions is guaranteed to evict them from the DB, but in the case of a zombie process (or similar) it may error and
block removal of the container. A subsequent run of
podman rm
would succeed (because the exec sessions have been purged from the DB), which is potentially confusing to users. So let's just continue, instead of erroring out, if removing exec sessions fails.[NO NEW TESTS NEEDED] I wouldn't want to spawn a zombie in our test VMs even if I could.
Fixes #14252
Signed-off-by: Matthew Heon [email protected]