-
Notifications
You must be signed in to change notification settings - Fork 718
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
E2E tests leaking GKE clusters #80
Comments
|
Here's one failure mode I see DAG run 2017-12-25T05:33:44 SetupCluster runs. On attempt #1 the cluster is created and the helm package for the operator is installed; but then there's a problem getting the status while waiting for the deployment to be ready
Airflow retries the setup cluster task (attempt 2) and that fails due to a problem creating the GCS output.
Now teardown_cluster runs and that fails with
So teardown_cluster is failing because it got None for the cluster name. So there's a couple problems in setup_cluster
I think there is a relatively easy fix
|
* setup_cluster needs to push the cluster name so that it is available to the teardown step before we try to setup the cluster so that the name is available even if setup_cluster fails. * setup_cluster also needs to handle the case where setup_cluster might already have been attempted; in which case we should reuse that cluster.
* setup_cluster needs to push the cluster name so that it is available to the teardown step before we try to setup the cluster so that the name is available even if setup_cluster fails. * setup_cluster also needs to handle the case where setup_cluster might already have been attempted; in which case we should reuse that cluster. * Fix #80
E2E tests seem to be leaking GKE clusters
(Clusters are listed as stopping because I manually deleted them).
The text was updated successfully, but these errors were encountered: