-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
Envoy 1.17.1 crashes when a ratelimit cluster is configured, but is unavailable #15747
Comments
I'll take a look. I was able to reproduce this locally with Envoy v1.17.0, but not with a build of Envoy based on v1.15.1. Either way, I'm waiting for a recent build from main and then I'll figure out why this is crashing. |
The real error is this exception:
This works for me once I set transport_api_version to "V3":
Starting with v1.17, Let me know if setting this field works for you, too. |
/assign |
@mattklein123 I've updated #15548, fixed the fuzz issue. |
I can confirm that this fixes it for me too, thanks! |
If you are reporting any crash or any potential security issue, do not
open an issue in this repo. Please report the issue via emailing
envoy-security@googlegroups.com where the issue will be triaged appropriately.
Title: Envoy 1.17.1 crashes when a ratelimit cluster is configured, but is unavailable
Description:
I believe there is a regression in Envoy 1.17.x where if ratelimiting is configured for a cluster but the rate limit service is unavailable then a request to that cluster will cause Envoy to crash. This does not happen in 1.16.0.
This was reported to envoy-security@googlegroups.com and triaged and it was determined that an issue could be opened.
Repro steps:
You can find a reproducible demo here: https://github.com/petedmarsh/envoycrashdemo.
Admin and Stats Output:
Config:
Logs:
Call Stack:
(I will attempt to get this for you)
The text was updated successfully, but these errors were encountered: