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-local-e2e-containerized is failing #72726

Open
cadeniyi opened this Issue Jan 9, 2019 · 9 comments

Comments

Projects
None yet
5 participants
@cadeniyi
Copy link

cadeniyi commented Jan 9, 2019

pull-kubernetes-local-e2e-containerized is failing and has been failing consistently since 2018-12-18

Looks like something happened between build 1648 and 1649 and the cluster is not coming up.

https://testgrid.k8s.io/conformance-all#local-up-cluster-containerized,%20master%20(dev)

@cadeniyi

This comment has been minimized.

Copy link

cadeniyi commented Jan 9, 2019

/sig testing
/sig node

@dims

This comment has been minimized.

Copy link
Member

dims commented Jan 9, 2019

Hopefully when the following merges, it will be better

kubernetes/test-infra#10488
kubernetes/test-infra#10664

@danielqsj

This comment has been minimized.

Copy link
Member

danielqsj commented Jan 15, 2019

@dims pull-kubernetes-local-e2e-containerized always failing again: https://testgrid.k8s.io/sig-testing-misc#pull-kubernetes-local-e2e-containerized

@dims

This comment has been minimized.

Copy link
Member

dims commented Jan 15, 2019

@danielqsj looks like that test fails in other jobs too, lets watch it for a couple of more days to see what frequency it fails: https://storage.googleapis.com/k8s-gubernator/triage/index.html?pr=1&test=should%20run%20and%20stop%20complex%20daemon

@danielqsj

This comment has been minimized.

Copy link
Member

danielqsj commented Jan 15, 2019

@dims sure, thanks.

@therc

This comment has been minimized.

Copy link
Contributor

therc commented Jan 17, 2019

It failed five out of five times for me on #72993 yesterday

@dims

This comment has been minimized.

Copy link
Member

dims commented Jan 17, 2019

@therc if you notice, it's not a mandatory job, which means even if this job fails fails, the PR itself is merge-able. Looks like the daemonset test is very problematic. will have to look

@dims

This comment has been minimized.

Copy link
Member

dims commented Jan 17, 2019

kubernetes/test-infra#10810 will ensure that all the ci/pull local-e2e jobs use the same cpu/mem so they stop timing out, then we can check if daemonset test issue happens in both local-e2e-containerized and local-e2e or just one of them.

@dims

This comment has been minimized.

Copy link
Member

dims commented Jan 18, 2019

Logged a specific bug in #73073

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment