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
CI: Conformance Ginkgo: Client pods not ready after timeout: timed out waiting for pods with filter -l type=client to be ready: 8m0s timeout expired
#32404
Comments
catched another one and detected the following in the sysdump https://github.com/cilium/cilium/actions/runs/9107971706/job/25037869655 (inner sysdump cilium-sysdump.zip)
another one (https://github.com/cilium/cilium/actions/runs/9101307271) with the same ending loglines in the
=> clang issue? (maybe also red herring as cilium seems to print the status of long-running clang every 5 seconds) |
maybe the timeout of 240s from creating the Cilium Agent DaemonSet to readiness of all its Pods is no longer enough? 🫤 We also have similar ci flake issues - e.g. #32431 it seems to take quite a long time until the health endpoint is up and ready - and this is used for the Pods readiness probe. |
CI failure
Sysdump is too large to upload here.
https://github.com/cilium/cilium/actions/runs/8980253691
The text was updated successfully, but these errors were encountered: