Handle container terminated but pod still running in conditions #10175
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.
Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1360626
Upstream kubernetes/kubernetes#29952
Sometimes when you have a pod with more than one container, and the container runs and terminates really fast,
PodContainerRunning
can go into a state where the pod indicates it's still running, but the container is already terminated sooc debug
never returns until it times out.Handle that condition by returning
ErrContainerTerminated
when it happens.