-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
[v1.9] CI: K8sConformance Portmap Chaining: connectivity-check pods are not ready after timeout #16873
Comments
I can reproduce it locally with:
(takes a few runs to hit the flake). Looking at Cilium logs I see a lot of errors related to the ipcache:
and waiting a bit and killing the pods that were crashing was enough to bring them back to a healthy state:
|
The ipcache errors might be a red herring, but they seem to correlate with a pod being able to run or not:
Here |
Just noticed that #16381 was not backported to 1.9 🤔 |
Unless it's expected to cause non-trivial conflicts, I'd just leave it to the backporters. There are already several v1.9 backport PRs opened so adding more ad-hoc backports will just complicate the rebasing. |
After backporting #16381 to v1.9 I'm not able anymore to reproduce this locally 🎉 |
I wonder if we should just backport #16381 to v1.8 as well to mitigate CI issues there? |
I don't think I can take a look at the failed test in v1.8 backports PR, but if @jrajahalme observed |
This issue has been automatically marked as stale because it has not |
First saw in #16781
Stacktrace
Standard Output
Standard Error
Click here to see.
The text was updated successfully, but these errors were encountered: