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
Re-enable click_deploy_test #2364
Comments
An easy approach is to make e2e test clean up before each run, we can reuse what prober test is doing today: |
It looks like it should be running in kubeflow-ci/kubeflow-testing cluster: @kunmingg If it's quota problem, shouldn't the test still be run, and then failed? |
Let's setup a dedicated cluster for it. |
From this run: https://gubernator.k8s.io/build/kubernetes-jenkins/logs/kubeflow-periodic-master/719 The log shows: the container main in pod XXX is not available: Bad Request |
manually launched the workflow. Saw: CreateContainerConfigError: secrets "kubeflow-oauth" not found |
The plan is to deploy to a new project (kubflow_ci_bootstrap or something under kubeflow.org) so that quotas/resources are easier to cleanup. |
Created project: kubeflow-ci-deployment |
Still failing:
The cleanup also failed:
|
Verify the error is the same when building locally. The problem is one dependency needs hg to clone |
Now the error is this line: While it's waiting for the deployment manager, got an error |
https://gubernator.k8s.io/build/kubernetes-jenkins/logs/kubeflow-periodic-master/756 |
https://github.com/kubeflow/kubeflow/blob/master/prow_config.yaml#L6
I think it's not being run:
https://k8s-testgrid.appspot.com/sig-big-data#kubeflow-periodic-master
@kunmingg mentioned the cluster might need more quota.
The text was updated successfully, but these errors were encountered: