Don't re-fetch all containers for "cleanup" event #1329
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This does not mean that the container goes away, that will only happen for the "remove" event. "cleanup" will also happen (twice!) between "died" and "init" for restarting a container. This avoids two parallel getContainer() calls with possibly inconsistent information, and generally reduces the number of getContainer() calls.
jelly
approved these changes
Jul 4, 2023
There was a problem hiding this comment.
Sounds logical, sadly the events are not documented https://docs.podman.io/en/latest/_static/api.html#tag/system/operation/SystemEventsLibpod
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This does not mean that the container goes away, that will only happen for the "remove" event. "cleanup" will also happen (twice!) between "died" and "init" for restarting a container.
This avoids two parallel getContainer() calls with possibly inconsistent information, and generally reduces the number of getContainer() calls.
This fixes testLifecycleOperations failures like this and this. debugging notes, stress-tested in #1324