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

test: Wait for kube-dns before starting test #16411

Merged

Conversation

jrajahalme
Copy link
Member

@jrajahalme jrajahalme commented Jun 2, 2021

Wait for kube-dns to become reachable from test pod before running test in fqdn.go.

Fixes: #16409

@jrajahalme jrajahalme added the area/CI-improvement Topic or proposal to improve the Continuous Integration workflow label Jun 2, 2021
@jrajahalme jrajahalme requested review from a team as code owners June 2, 2021 20:42
@maintainer-s-little-helper maintainer-s-little-helper bot added the dont-merge/needs-release-note-label The author needs to describe the release impact of these changes. label Jun 2, 2021
@jrajahalme jrajahalme added the release-note/ci This PR makes changes to the CI. label Jun 2, 2021
@maintainer-s-little-helper maintainer-s-little-helper bot removed the dont-merge/needs-release-note-label The author needs to describe the release impact of these changes. label Jun 2, 2021
@jrajahalme
Copy link
Member Author

test-1.21-4.9

@@ -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))
Copy link
Contributor

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?

Copy link
Member Author

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>
@jrajahalme jrajahalme force-pushed the pr/jrajahalme/test-isolate-coredns-flakes branch from 81aff2f to 82ec0b9 Compare June 3, 2021 20:41
@jrajahalme
Copy link
Member Author

test-me-please

@jrajahalme
Copy link
Member Author

test-1.20-4.19 had timed out

@jrajahalme
Copy link
Member Author

test-1.20-4.19
without garbage on the first line this time :-)

@jrajahalme
Copy link
Member Author

test-1.20-4.19
run had failed in 7.5 seconds

@nebril
Copy link
Member

nebril commented Jun 14, 2021

test-1.20-4.19

@jrajahalme
Copy link
Member Author

The two CI flakes are unrelated to this change, flagging as ready-to-merge.

@jrajahalme jrajahalme added the ready-to-merge This PR has passed all tests and received consensus from code owners to merge. label Jun 16, 2021
@jibi jibi merged commit d790f8f into cilium:master Jun 17, 2021
@joestringer
Copy link
Member

Should we be backporting this to v1.10 to help stabilize CI?

@aditighag
Copy link
Member

aditighag commented Jun 28, 2021

@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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/CI-improvement Topic or proposal to improve the Continuous Integration workflow ready-to-merge This PR has passed all tests and received consensus from code owners to merge. release-note/ci This PR makes changes to the CI.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

CI: K8sFQDNTest Validate that multiple specs are working correctly
7 participants