-
Notifications
You must be signed in to change notification settings - Fork 7.8k
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
ECDS based Wasm filter configuration causes proxy segmentation fault #35267
Comments
Can you correlate crash with any config update, like EnvoyFilter update? It will be hard to track down without reproduce steps. cc @kyessenov |
I wrote test steps above including the whole EnvoyFilter config. I can't reproduce it by myself. If someone else meet the same problem, we can look at them together. |
The backtrace suggests it crashes on filter config update, which should happen if EXTENSION_CONFIG (i.e. ingressgateway-real-ip EnvoyFilter) has any update. So you are saying there is no update to the EnvoyFilter resource but proxy crashes? |
No update manually. I delete enovyfilter and send some test requests. Then reapply the yaml file to do the same tests but failed. |
Not stale. I can see this in my env as well. Need to figure out a way to reproduce. |
I think this is because of envoyproxy/envoy#14930 |
With the related fixes in envoy upstream, are we in a better place here now? |
My local reproduction seems to pass but I'd like @bianpengyuan to confirm since he was able to trigger it in prod. |
Still present on Envoy 1.21.2-dev (Istio-1.13.2) |
Still present on istio 1.13.7 When I update wasm filter configration, istio gateway pods all crashed.
|
Does it happen on 1.15? There's a crash fix every release of istio, and this stack trace is not specific enough to tell whether it's new or old. |
It's incidental in my pro istio 1.13 environment. Does 1.13.7 include this fix? I will test it in istio 1.15 cluster in my test environment. But the trouble is I can't reproduce the problem everytime with same steps. |
I don't think we backport Wasm fixes. We'll need a way reproduce this regardless on a debug build since the stack trace is not very useful. |
@kyessenov I test it in istio 1.14.3 and 1.15.0, it seems no problem. I close this issue since 1.13 will not be supported soon. |
You mean update the wasm configuration.value in your envoyfilter example? |
Bug Description
istio-ingressgateway got segmentation fault error when i test wasm extension.
Note that it's occasional and i can't reproduce it with the same steps.
Test steps:
ev.yaml
Last logs from istio-ingressgateway pod
Version
Additional Information
No response
Affected product area
Is this the right place to submit this?
The text was updated successfully, but these errors were encountered: