Skip to content

envoy: update submodule 46b646c -> 33cf6cd#1481

Merged
goaway merged 7 commits intoenvoyproxy:mainfrom
phlax:envoy-bump-head
May 22, 2021
Merged

envoy: update submodule 46b646c -> 33cf6cd#1481
goaway merged 7 commits intoenvoyproxy:mainfrom
phlax:envoy-bump-head

Conversation

@phlax
Copy link
Copy Markdown
Member

@phlax phlax commented May 19, 2021

Signed-off-by: Ryan Northey ryan@synca.io

Description:

When testing #1475 tests were failing as the envoy submodule was behind envoy main

This PR also:

  • updates the protobuf patch to make it work with v3.16.0
  • adds the envoy.http.original_ip_detection.xff extension as tests seemed to indicate it as necessary

Risk Level:
Testing:
Docs Changes:
Release Notes:
[Optional Fixes #Issue]
[Optional Deprecated:]

Signed-off-by: Ryan Northey <ryan@synca.io>
@phlax
Copy link
Copy Markdown
Member Author

phlax commented May 19, 2021

not sure if failing tests are flakes - im struggling to get any info when clicking on the "details" link

@buildbreaker
Copy link
Copy Markdown

The python one might be a flake that @crockeo was looking into but the core test likely is unexpected. I just reran both the jobs and am hoping that makes it green

@phlax
Copy link
Copy Markdown
Member Author

phlax commented May 19, 2021

@buildbreaker checking the swift_helloworld test it seems to be failing with:

[2021-05-19 17:15:15.447][31938][critical][main] [external/envoy/source/server/server.cc:113] error initializing configuration '': Original IP detection extension not found: 'envoy.http.original_ip_detection.xff'

this was the reason that i added in the xff extension in the build config.

its not clear to me why this is still failing, where the config is coming from, or why the envoy binary doesnt have the extension added

im guessing that the problem is related to the ip detection extension being listed as required in envoy's all_extensions.bzl but its just a guess

any ideas ?

@goaway
Copy link
Copy Markdown
Contributor

goaway commented May 20, 2021

@phlax sorry I didn't see this sooner - if you're adding an extension, it will need to be registered here:
https://github.com/envoyproxy/envoy-mobile/blob/c8ef0d13643e54141e1bfd5ad4fd9018885a0101/envoy_build_config/extension_registry.cc

@goaway
Copy link
Copy Markdown
Contributor

goaway commented May 20, 2021

This has to do with differences in static initialization order when running as a process vs. running as a statically-linked library.

@phlax
Copy link
Copy Markdown
Member Author

phlax commented May 20, 2021

great, thanks - ill update shortly

@phlax phlax force-pushed the envoy-bump-head branch from 279c83b to fb8b6b4 Compare May 20, 2021 11:15
@phlax phlax force-pushed the envoy-bump-head branch from fb8b6b4 to 29491f1 Compare May 20, 2021 11:16
Signed-off-by: Ryan Northey <ryan@synca.io>
@phlax phlax force-pushed the envoy-bump-head branch from fa53d5e to deb0b1c Compare May 20, 2021 12:59
@phlax
Copy link
Copy Markdown
Member Author

phlax commented May 20, 2021

@goaway ive tried registering the extension - unfortunately it causes an error - something to do with namespacing and factories

im afraid this is about my limit of c++ knowledge - if you can lmk what else is required i would be happy to add

goaway added 2 commits May 22, 2021 02:43
Signed-off-by: Mike Schore <mike.schore@gmail.com>
Signed-off-by: Mike Schore <mike.schore@gmail.com>
@goaway goaway changed the title envoy: Update submodule 46b646cbfa87 -> 84138f7 envoy: update submodule 46b646c -> 33cf6cd May 21, 2021
Signed-off-by: Mike Schore <mike.schore@gmail.com>
@goaway goaway merged commit 700f558 into envoyproxy:main May 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants