-
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
Can't initializate Envoy v1.16+ with CDS message #14119
Comments
It's hard to tell what is going on here from the stack trace, though this may be a regression from #12833. I will take a look. |
is this a permissions issue with the cds.json file ? |
@phlax I have no permission issues - my case: docker 19.03.13 - darwin/amd64 all files in /tmp/envoy-issue folder
I thinks, its some dns issue on initialising secondary cluster |
ah, k - apologies for noise |
@mattklein123 could this be a result of this capture. Would this be easily transitioned to a |
I'm not sure. I don't see why that would be broken when that is what it was before, but I haven't debugged yet. |
Fair point. For what it's worth we've been seeing a crash in Istio from the same pointer |
I will look at this tomorrow. I have a related change I'm working on and can probably fix this at the same time. |
@EItanya @mattklein123 I've been debugging this a bit, it's not result of the capture. It's a misuse of TLS slot in aggregate cluster implementation, it never call |
Ok. I can fix this tomorrow if you don't get to it tonight. Seems like we need better tests for this cluster? Is there an integration test? |
Final follow up from #13906. This PR does: 1) Simplify the logic during startup by making thread local clusters only appear after a cluster has been initialized. This is now uniform both for bootstrap clusters as well as CDS clusters, making the logic simpler to follow. 2) Aggregate cluster needed fixes due to assumptions on startup existence of the thread local cluster. This change also fixes #14119 3) Make TLS mocks verify that set() is called before other functions. Signed-off-by: Matt Klein <[email protected]>
Fixes #14119 Signed-off-by: Matt Klein <[email protected]>
Final follow up from #13906. This PR does: 1) Simplify the logic during startup by making thread local clusters only appear after a cluster has been initialized. This is now uniform both for bootstrap clusters as well as CDS clusters, making the logic simpler to follow. 2) Aggregate cluster needed fixes due to assumptions on startup existence of the thread local cluster. This change also fixes #14119 3) Make TLS mocks verify that set() is called before other functions. Signed-off-by: Matt Klein <[email protected]>
Additional Description: Based on #14388 Risk Level: Low Testing: Build and run the repro from #14119 without crashing, `bazel test test/extensions/clusters/aggregate:cluster_test` Docs Changes: N/A Release Notes: #14119 Signed-off-by: Taylor Barrella <[email protected]>
* backport to 1.16: http: fixing a bug with IPv6 hosts (envoyproxy#14238) Fixing a bug where HTTP parser offsets for IPv6 hosts did not include [] and Envoy assumed it did. This results in mis-parsing addresses for IPv6 CONNECT requests and IPv6 hosts in fully URLs over HTTP/1.1 Risk Level: low Testing: new unit, integration tests Docs Changes: n/a Release Notes: inline Signed-off-by: Shikugawa <[email protected]> Co-authored-by: alyssawilk <[email protected]> * backport to 1.16: vrp: allow supervisord to open its log file (envoyproxy#14066) (envoyproxy#14279) Commit Message: Allow supervisord to open its log file Additional Description: Change the default location of the log file and give supervisord permissions to write to it. Risk Level: low Testing: built image locally Docs Changes: n/a Release Notes: n/a Platform Specific Features: n/a Signed-off-by: Alex Konradi <[email protected]> Signed-off-by: Christoph Pakulski <[email protected]> * Closing release 1.16.2. (envoyproxy#14308) Signed-off-by: Christoph Pakulski <[email protected]> * Kick-off rel 1.16.3. (envoyproxy#14321) Signed-off-by: Christoph Pakulski <[email protected]> * lua: reset downstream_ssl_connection in StreamInfoWrapper when object is marked dead by Lua GC (envoyproxy#14092) (envoyproxy#14449) Co-authored-by: Marcin Falkowski <[email protected]> * backport to 1.16: tls: fix detection of the upstream connection close event. (envoyproxy#13858) (envoyproxy#14452) Fixes envoyproxy#13856. This change also contains the following backports: - build: Fix some unused variable warnings (envoyproxy#13987) - test: Check in all TLS test certs (envoyproxy#13702) Signed-off-by: Piotr Sikora <[email protected]> Signed-off-by: Christoph Pakulski <[email protected]> * backport to 1.16: aggregate cluster: fix TLS init issue (envoyproxy#14456) Additional Description: Based on envoyproxy#14388 Risk Level: Low Testing: Build and run the repro from envoyproxy#14119 without crashing, `bazel test test/extensions/clusters/aggregate:cluster_test` Docs Changes: N/A Release Notes: envoyproxy#14119 Signed-off-by: Taylor Barrella <[email protected]> Co-authored-by: Rei Shimizu <[email protected]> Co-authored-by: Christoph Pakulski <[email protected]> Co-authored-by: Marcin Falkowski <[email protected]>
Final follow up from #13906. This PR does: 1) Simplify the logic during startup by making thread local clusters only appear after a cluster has been initialized. This is now uniform both for bootstrap clusters as well as CDS clusters, making the logic simpler to follow. 2) Aggregate cluster needed fixes due to assumptions on startup existence of the thread local cluster. This change also fixes envoyproxy/envoy#14119 3) Make TLS mocks verify that set() is called before other functions. Signed-off-by: Matt Klein <[email protected]>
We have our implementation of go-control-plane, it's work great on envoy v1.15.2 - but upgrading to envoy v1.16.0 - got a Caught Segmentation fault on CDS message with aggregated cluster
envoy.yaml
cds.json
rds.json
envoy output
The text was updated successfully, but these errors were encountered: