Skip to content
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

xds: revert setting set_node_on_first_message_only to true when generating envoy bootstrap config #8440

Merged
merged 1 commit into from
Aug 5, 2020

Conversation

rboyer
Copy link
Member

@rboyer rboyer commented Aug 5, 2020

When consul is restarted and an envoy that had already sent DiscoveryRequests to the previous consul process sends a request to the new process it doesn't respect the set_node_on_first_message_only setting and never populates DiscoveryRequest.Node for the life of the new consul process due to this bug: envoyproxy/envoy#9682

Fixes #8430

…ating envoy bootstrap config

When consul is restarted and envoy that had already sent
DiscoveryRequests to the previous consul process sends a request to the
new process it doesn't respect the setting and never populates
DiscoveryRequest.Node for the life of the new consul process due to this
bug: envoyproxy/envoy#9682

Fixes #8430
@rboyer rboyer added type/bug Feature does not function as expected theme/envoy/xds Related to Envoy support labels Aug 5, 2020
@rboyer rboyer requested a review from a team August 5, 2020 19:35
@rboyer rboyer self-assigned this Aug 5, 2020
Copy link
Contributor

@freddygv freddygv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@rboyer rboyer merged commit 397019d into master Aug 5, 2020
@rboyer rboyer deleted the revert-envoy-node-setting branch August 5, 2020 20:00
@hashicorp-ci
Copy link
Contributor

🍒✅ Cherry pick of commit 397019d onto release/1.8.x succeeded!

hashicorp-ci pushed a commit that referenced this pull request Aug 5, 2020
…ating envoy bootstrap config (#8440)

When consul is restarted and an envoy that had already sent
DiscoveryRequests to the previous consul process sends a request to the
new process it doesn't respect the setting and never populates
DiscoveryRequest.Node for the life of the new consul process due to this
bug: envoyproxy/envoy#9682

Fixes #8430
@hashicorp-ci
Copy link
Contributor

🍒❌ Cherry pick of commit 397019d onto release/1.7.x failed! Build Log

rboyer added a commit that referenced this pull request Aug 5, 2020
…o true when generating envoy bootstrap config

This is a backport of #8440 to 1.7.x
rboyer added a commit that referenced this pull request Aug 5, 2020
…o true when generating envoy bootstrap config (#8441)

This is a backport of #8440 to 1.7.x
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
theme/envoy/xds Related to Envoy support type/bug Feature does not function as expected
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Segfault in 1.8.x and 1.7.5 with Consul Connect
3 participants