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

Kubemark density test failing because kubelet doesn't have a ClusterDNS #18056

Closed
fabioy opened this issue Dec 2, 2015 · 3 comments
Closed
Labels
area/kubelet area/test area/test-infra priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. sig/node Categorizes an issue or PR as relevant to SIG Node.

Comments

@fabioy
Copy link
Contributor

fabioy commented Dec 2, 2015

The Kubemark Jenkins Density tests started failing around 2:14pm PST today. Looking at test logs, it seems all pods are scheduled, but remain in "Pending" state forever. Digging into the container logs, found all the containers with similar error of the format:

"kubelet does not have ClusterDNS IP configured and cannot create Pod using ClusterFirst policy."

Still investigating.

@fabioy fabioy added area/test priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. area/kubelet sig/node Categorizes an issue or PR as relevant to SIG Node. area/test-infra labels Dec 2, 2015
@fabioy
Copy link
Contributor Author

fabioy commented Dec 2, 2015

CC @gmarek I thought it may have been your PR #17942, but doesn't seem like it. I'm not as familiar with this test -- do you have any ideas?

@fabioy
Copy link
Contributor Author

fabioy commented Dec 2, 2015

I think the culprit was PR #15645. Started a revert for it (unless it's determined that a test change is simpler).

@fabioy
Copy link
Contributor Author

fabioy commented Dec 2, 2015

Closing issue with merge of #18057 (revert of #15645).

@fabioy fabioy closed this as completed Dec 2, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/kubelet area/test area/test-infra priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. sig/node Categorizes an issue or PR as relevant to SIG Node.
Projects
None yet
Development

No branches or pull requests

1 participant