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
test: Wait for kube-dns before starting test #16411
test: Wait for kube-dns before starting test #16411
Conversation
test-1.21-4.9 |
test/k8sT/fqdn.go
Outdated
@@ -85,6 +85,11 @@ var _ = SkipDescribeIf(helpers.RunsOn54Kernel, "K8sFQDNTest", func() { | |||
err = kubectl.WaitforPods(helpers.DefaultNamespace, "-l zgroup=testapp", helpers.HelperTimeout) | |||
Expect(err).Should(BeNil(), "Testapp is not ready after timeout") | |||
|
|||
// Validate that coredns is reachable from test pods | |||
err = kubectl.NslookupInPod(helpers.DefaultNamespace, appPods[helpers.App2], | |||
fmt.Sprintf("kube-dns.%s.svc.cluster.local", helpers.CiliumNamespace)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe kube-dns
always runs in kube-system
, is it not true?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You must be right, will fix :-)
Wait for kube-dns to become reachable before running test in fqdn.go. Fixes: cilium#16409 Signed-off-by: Jarno Rajahalme <jarno@isovalent.com>
81aff2f
to
82ec0b9
Compare
test-me-please |
test-1.20-4.19 had timed out |
test-1.20-4.19 |
test-1.20-4.19 |
test-1.20-4.19 |
The two CI flakes are unrelated to this change, flagging as ready-to-merge. |
Should we be backporting this to v1.10 to help stabilize CI? |
@joestringer Yeah, I was just going to comment the same based on the comment I posted in #16671. You beat me to it. :) /cc @jrajahalme |
Wait for kube-dns to become reachable from test pod before running test in fqdn.go.
Fixes: #16409