-
Notifications
You must be signed in to change notification settings - Fork 14.7k
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
avoid retrying after KubernetesPodOperator has been marked as failed #36749
avoid retrying after KubernetesPodOperator has been marked as failed #36749
Conversation
a7573f7
to
6b0f18f
Compare
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.
Nice Work. It would be great if possible then, add the test cases.
4f3b55b
to
141b7a8
Compare
141b7a8
to
c10f762
Compare
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.
Looks good to me! Pending comments from @dirrao.
@hussein-awala WDYT?
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.
We should also add some test coverage to make sure we don't accidentally reintroduce this.
b3eeab9
to
1eeeb3e
Compare
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
1eeeb3e
to
a7f25ed
Compare
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.
On second though, I think we are okay without test coverage on this. LGTM.
…een marked as failed apache#36471
Co-authored-by: Jed Cunningham <[email protected]>
if the task has been killed, do not cleanup again
f7f9935
to
ca60adc
Compare
After marking the task as failed, KPO still has a
finally
section to run, which causes #36471. In this PR, I tried to check whetheron_killed
is called and do not raise exception in thefinally
section as it'll overwrite the "Mark as failed" behavior^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rst
or{issue_number}.significant.rst
, in newsfragments.