-
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
CI: pod-to-ingress-service-allow-ingress-identity/pod-to-ingress-service: exit code 22 #29468
Comments
@sayboras does this look familiar to you at all? I saw that you had written these tests originally. |
The tests were added a while back, but not enabled in any of GHA CI jobs until recently. So I am kind of keeping an eye on for any flake. Let me take a closer loop, thanks for the ping. Related PR: #29130 |
Another hit here
Logs: logs_2036808.zip |
There is no reliable way to check if the new policy in envoy has been applied, this causes the flake in our CI for L7/Ingress related policy. One point worth mentioning is that envoy update is not incremental (i.e. it's state of the world every time), so the updating time is sometimes longer even only for one single policy. |
Hit on - https://github.com/cilium/cilium/actions/runs/8287906154/job/22681325788
|
CI failure
Failure: https://github.com/cilium/cilium/actions/runs/7025266863/job/19115742712
Example failure:
...
man curl
describes exit code 22 as:I have a copy of the zip files that I can share, but apparently they're 60MB per failure these days 🙈 .
The text was updated successfully, but these errors were encountered: