Add a pod status check after EOF detection - #1333
Closed
lranjbar wants to merge 1 commit into
Closed
Conversation
|
Contributor
Author
|
Changes have been rolled into #1332 |
This file contains hidden or 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
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.



In researching the bug: AAP-46484
Jobs are in failed status with message "Receptor detail: Finished"
Receptor is returning a WorkStateSuccessful with a truncated stdout. This causes parsing JSON errors by ansible-runner.
The reproducer we have so far is shows that when a container exits with a failure exit code (non-zero exit code) receptor will pass the truncated stdout as a success. We can force this path by creating a container with low memory that causes k8s to OOMKill the container and pod.
This adds a check to grab the terminated state of the container and sends an error message if the container exited with a failure of some kind.