-
Notifications
You must be signed in to change notification settings - Fork 482
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
pull-kubernetes-dns-test broken at head #605
Comments
Interestingly, with kubelet failed, the tests can still pass, and the tests failed only when we try to killed kubelet (and found it already terminated)
|
Ref: startup command:
|
jingyuanliang
added a commit
to jingyuanliang/dns
that referenced
this issue
Oct 24, 2023
The existing E2E tests doesn't need them (proven as this commit still passing presubmit), while the existence of kubelet started to cause mysterious failures recently (kubernetes#605). Let's exclude kubelet in the mock cluster for now. Not completely removing the relevant code in case some future tests need them, then kubernetes#605 can be investigated at that time.
jingyuanliang
added a commit
to jingyuanliang/dns
that referenced
this issue
Oct 24, 2023
The existing E2E tests don't need them (proven as this commit still passing presubmit), while the existence of kubelet started to cause mysterious failures recently (kubernetes#605). Let's exclude kubelet in the mock cluster for now. Not completely removing the relevant code in case some future tests need them, then kubernetes#605 can be investigated at that time.
jingyuanliang
added a commit
to jingyuanliang/dns
that referenced
this issue
Oct 24, 2023
The existing E2E tests don't need kubelet (proven as this commit still passing presubmit), while the execution of kubelet started to cause mysterious failures recently (kubernetes#605). Let's exclude kubelet in the mock cluster for now. Not completely removing the relevant code in case some future tests need them, then kubernetes#605 can be investigated at that time.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Found in: https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/dns/603/pull-kubernetes-dns-test/1715355423860592640
Confirmed failure without code change at all: https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/dns/604/pull-kubernetes-dns-test/1716792265403273216 (1716792265403273216 #604 (eaaed71) by jingyuanliang 08:22:35 26m57s FAILURE)
Manipulated test code: https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/dns/604/pull-kubernetes-dns-test/1716834170107334656 (1716834170107334656 #604 (68b664b) by jingyuanliang 11:09:05 26m59s SUCCESS)
And extracted the failure:
cc @wewark
The text was updated successfully, but these errors were encountered: