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

integration test: connection timed out; no servers could be reached #3163

Closed
tstromberg opened this issue Sep 26, 2018 · 1 comment
Closed
Assignees
Labels
area/dns DNS issues area/testing kind/flake Categorizes issue or PR as related to a flaky test.

Comments

@tstromberg
Copy link
Contributor

Example: https://storage.googleapis.com/minikube-builds/logs/3161/Linux-VirtualBox.txt

--- FAIL: TestFunctional/DNS (101.69s)
util.go:185: Error ;; connection timed out; no servers could be reached

		command terminated with exit code 1
		 running command [exec busybox-qf5m4 nslookup kubernetes]. Return code: exit status 1
	util.go:185: Error ;; connection timed out; no servers could be reached
		
		command terminated with exit code 1
		 running command [exec busybox-qf5m4 nslookup kubernetes]. Return code: exit status 1
	util.go:185: Error ;; connection timed out; no servers could be reached
		
		command terminated with exit code 1
		 running command [exec busybox-qf5m4 nslookup kubernetes]. Return code: exit status 1
	cluster_dns_test.go:62: running nslookup in pod:Temporary Error: Error running command. Error  exit status 1. Output: ;; connection timed out; no servers could be reached
		
		command terminated with exit code 1
		
		Temporary Error: Error running command. Error  exit status 1. Output: ;; connection timed out; no servers could be reached
		
		command terminated with exit code 1
		
		Temporary Error: Error running command. Error  exit status 1. Output: ;; connection timed out; no servers could be reached
@tstromberg
Copy link
Contributor Author

git bisect points to this change, after which the test no longer waits for the pods to be running:

0a5efe1

I'll see what I can do to extend the timeout, or better yet, improve the error message.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/dns DNS issues area/testing kind/flake Categorizes issue or PR as related to a flaky test.
Projects
None yet
Development

No branches or pull requests

1 participant