-
Notifications
You must be signed in to change notification settings - Fork 16.4k
Fix KubernetesPodOperator xcom push when get_logs=False
#29052
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
LGTM but I think I need also second opinion (@jedcunningham :) again )? I also think having unit tests covering the cases that would have failed previously are needed here. I am always suspicious about changes introducing behavioural change where no tests are touched. |
potiuk
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved. @jedcunningham @dstandish ?
jedcunningham
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, but yes we should add test coverage.
|
@eladkal is it too late to add this fix to cncf.kubernetes release? |
It will be in next release |
closes: #29002
When
get_logs=False, we should wait thebasecontainer completion before reading the xcom file, to do that we are checking if the container is running, but there is a possibility that the container is in waiting state, and in the currentawait_container_completionmethod, we consider it as completed.Instead, I'm checking if the container has the state
terminatedand if not I wait 1s.