-
Notifications
You must be signed in to change notification settings - Fork 16.4k
[AIRFLOW-2966] Catch ApiException in the Kubernetes Executor #3960
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
|
This build will fail because the recent release of |
Codecov Report
@@ Coverage Diff @@
## master #3960 +/- ##
===========================================
- Coverage 76.67% 63.65% -13.02%
===========================================
Files 199 199
Lines 16186 20018 +3832
===========================================
+ Hits 12410 12743 +333
- Misses 3776 7275 +3499
Continue to review full report at Codecov.
|
|
Travis passes in my environment, but the incubator-airflow build times-out on an unrelated test. Restarting the build may pass, since this seems to be a symptom of a flaky kubernetes test environment. |
|
@johnhofman Can you rebase onto master? |
Creating a pod that exceeds a namespace's resource quota throws an ApiException. This change catches the exception and the task is re-queued inside the Executor instead of killing the scheduler.
|
@Fokko I have rebased. Is this failing test something I need to look into? |
|
Sorry @johnhofman, I was a bit busy. I've restarted the failing test, let's see if it passes now. The Kubernetes tests can sometimes be a bit flaky. |
|
@Fokko tests passed |
Fokko
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.
Thanks @johnhofman LGTM
…pache#3960)" This reverts commit 03de9ee.
|
@johnhofman I had to revert the commit again. The CI wasn't happy. Please take a look and open a new PR: https://travis-ci.org/apache/incubator-airflow/jobs/456661023 |
…3960) Creating a pod that exceeds a namespace's resource quota throws an ApiException. This change catches the exception and the task is re-queued inside the Executor instead of killing the scheduler.
…pache#3960)" This reverts commit 03de9ee.
…3960) Creating a pod that exceeds a namespace's resource quota throws an ApiException. This change catches the exception and the task is re-queued inside the Executor instead of killing the scheduler.
…pache#3960)" This reverts commit 03de9ee.
…3960) Creating a pod that exceeds a namespace's resource quota throws an ApiException. This change catches the exception and the task is re-queued inside the Executor instead of killing the scheduler.
…pache#3960)" This reverts commit 03de9ee.
…3960) Creating a pod that exceeds a namespace's resource quota throws an ApiException. This change catches the exception and the task is re-queued inside the Executor instead of killing the scheduler.
…pache#3960)" This reverts commit 03de9ee.
Description
Creating a pod that exceeds a namespace's resource quota throws an ApiException. This change catches the exception and the task is re-queued inside the Executor instead of killing the scheduler.
click 7.0was recently released butflask-appbuilder 1.11.1 has requirement click==6.7. I have pinnedclick==6.7to make the dependencies resolve.Tests
This adds a single test
TestKubernetesExecutor. test_run_next_exceptionthat covers this single scenario. Without the changes this test fails when the ApiException is not caught.This is the first test case for the
KubernetesExecutor, so I needed to add the[kubernetes]section todefault_test.cfgso that theKubernetesExecutorcan be built without exceptions.Jira ticket: https://issues.apache.org/jira/browse/AIRFLOW-2966