-
Notifications
You must be signed in to change notification settings - Fork 39.4k
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
Failing Kubeadm Test: https://k8s-gubernator.appspot.com/build/kubernetes-jenkins/logs/ci-kubernetes-e2e-kubeadm-gce-master/524 #70058
Comments
/milestone v1.13 |
sent possible fix PR: |
sent new PR kubernetes/test-infra#9884 |
Reopening, because the test isn't passing yet. /reopen |
@jberkus: Reopening this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
true, i was almost sure that the solution in that last PR won't be sufficient... |
/assign |
@neolit123 I see https://k8s-testgrid.appspot.com/sig-release-master-blocking#kubeadm-gce-stable-on-master job failing as well. Will the 2 open PRs address this failure as well? |
@AishSundar all the kubeadm-gce-x tests are broken at the moment due to the e2e refactor. |
latest efforts: |
the tests are working on the cluster up/down side, except that they fail when dumping the node logs. looking into it. |
should be green by tomorrow. |
Looks good, thanks! One flake in the last run - let's keep an eye on it but it should be fine. /cc @jberkus @AishSundar @mortent /close |
@mariantalla: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Testgrid; https://k8s-testgrid.appspot.com/sig-release-master-blocking#kubeadm-gce-master
Sample Failure:
The problem seems to be that Kube-anywhere isn't working since commit aae438e
/sig cluster-lifecycle
/kind failing-test
/priority important-soon
cc: @timothysc
@kubernetes/sig-cluster-lifecycle
The text was updated successfully, but these errors were encountered: