Skip to content
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

Closed
jingyuanliang opened this issue Oct 24, 2023 · 2 comments
Closed

pull-kubernetes-dns-test broken at head #605

jingyuanliang opened this issue Oct 24, 2023 · 2 comments

Comments

@jingyuanliang
Copy link
Contributor

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:

2023/10/24 15:35:43 �[1mLOG: �[0mdocker | Flag --api-servers has been deprecated, Use --kubeconfig instead. Will be removed in a future version.
2023/10/24 15:35:43 �[1mLOG: �[0mdocker | Flag --config has been deprecated, Use --pod-manifest-path instead. Will be removed in a future version.
2023/10/24 15:35:43 �[1mLOG: �[0mdocker | I1024 15:35:22.119199  199402 feature_gate.go:181] feature gates: map[]
2023/10/24 15:35:43 �[1mLOG: �[0mdocker | W1024 15:35:22.119532  199402 server.go:605] Could not load kubeconfig file /var/lib/kubelet/kubeconfig: stat /var/lib/kubelet/kubeconfig: no such file or directory. Using default client config instead.
2023/10/24 15:35:43 �[1mLOG: �[0mdocker | I1024 15:35:22.665666  199402 server.go:536] Using self-signed cert (/var/run/kubernetes/kubelet.crt, /var/run/kubernetes/kubelet.key)
2023/10/24 15:35:43 �[1mLOG: �[0mdocker | I1024 15:35:22.665796  199402 server.go:124] Running kubelet in containerized mode (experimental)
2023/10/24 15:35:43 �[1mLOG: �[0mdocker | I1024 15:35:22.665986  199402 docker.go:356] Connecting to docker on unix:///var/run/docker.sock
2023/10/24 15:35:43 �[1mLOG: �[0mdocker | I1024 15:35:22.666057  199402 docker.go:376] Start docker client with request timeout=2m0s
2023/10/24 15:35:43 �[1mLOG: �[0mdocker | I1024 15:35:22.680891  199402 iptables.go:176] Could not connect to D-Bus system bus: dial unix /var/run/dbus/system_bus_socket: connect: no such file or directory
2023/10/24 15:35:43 �[1mLOG: �[0mdocker | I1024 15:35:22.683548  199402 iptables.go:176] Could not connect to D-Bus system bus: dial unix /var/run/dbus/system_bus_socket: connect: no such file or directory
2023/10/24 15:35:43 �[1mLOG: �[0mdocker | Error: failed to run Kubelet: mountpoint for cpu not found
2023/10/24 15:35:43 �[1mLOG: �[0mdocker | failed to run Kubelet: mountpoint for cpu not found

cc @wewark

@jingyuanliang
Copy link
Contributor Author

jingyuanliang commented Oct 24, 2023

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)

�[1mLOG: �[0mdocker [-H unix:///var/run/docker.sock kill 3f4260312b43f505b7d3c9c3dbdcc3e6367a0e67f276dbef07aea25f6cc438fb]
2023/10/24 15:35:43 �[1mLOG: �[0mdocker | Error response from daemon: Cannot kill container: 3f4260312b43f505b7d3c9c3dbdcc3e6367a0e67f276dbef07aea25f6cc438fb: Container 3f4260312b43f505b7d3c9c3dbdcc3e6367a0e67f276dbef07aea25f6cc438fb is not running

@jingyuanliang
Copy link
Contributor Author

Ref: startup command:

2023/10/24 15:35:21 �[1mLOG: �[0mdocker | 
�[1mLOG: �[0mdocker run [-H unix:///var/run/docker.sock run -d --volume=/:/rootfs:ro --volume=/sys:/sys:ro --volume=/dev:/dev --volume=/home/prow/go/src/k8s.io/dns:/src:ro --volume=/tmp/k8s-dns:/data:rw --volume=/home/prow/go/src/k8s.io/dns/test/e2e/cluster/manifests:/etc/kubernetes/manifests-e2e:ro --volume=/var/lib/docker:/var/lib/docker:rw --volume=/var/run:/var/run:rw --volume=/var/lib/kubelet:/var/lib/kubelet:shared --net=host --pid=host --privileged=true registry.k8s.io/hyperkube:v1.5.1 /hyperkube kubelet --v=4 --containerized --hostname-override=0.0.0.0 --address=0.0.0.0 --cluster_dns=10.0.0.10 --cluster_domain=cluster.local --api-servers=http://localhost:8080 --config=/etc/kubernetes/manifests-e2e]

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
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant