Skip to content

Fix CoreDNS readiness race in integration test - #105

Open
HarshwardhanPatil07 wants to merge 1 commit into
bootc-dev:mainfrom
HarshwardhanPatil07:fix-coredns-readiness-race
Open

Fix CoreDNS readiness race in integration test#105
HarshwardhanPatil07 wants to merge 1 commit into
bootc-dev:mainfrom
HarshwardhanPatil07:fix-coredns-readiness-race

Conversation

@HarshwardhanPatil07

Copy link
Copy Markdown
Collaborator

Summary

  • Add WaitForPodReady for CoreDNS (k8s-app=kube-dns) before the nslookup registry.cluster.local test step
  • Fixes flaky Connection refused failures where CoreDNS wasn't ready when the DNS query ran
  • Uses the same pattern already established for Calico CNI readiness (line 108)

Test plan

  • Verified locally: composefs integration test passes (1 Passed, 0 Failed)
  • CI should pass the composefs integration test consistently

Wait for CoreDNS pods to be ready before attempting DNS
resolution, preventing flaky "Connection refused" failures.

Signed-off-by: HarshwardhanPatil07 <harshpat@redhat.com>
@HarshwardhanPatil07

Copy link
Copy Markdown
Collaborator Author

Lets see if integration tests pass, I saw failure here

@HarshwardhanPatil07

Copy link
Copy Markdown
Collaborator Author

@alicefr PTAL

@alicefr

alicefr commented Aug 6, 2026

Copy link
Copy Markdown
Collaborator

@HarshwardhanPatil07 many thanks for this! I'm wondering if we should move this check to the production code rather then in the tests only. I mean adding an additional check to the cluster start command to wait for the coredns pods to be fully deployed.

@HarshwardhanPatil07

Copy link
Copy Markdown
Collaborator Author

Yes @alicefr Thank you! Let me check that

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants