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.

Sign up for GitHub

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

Jump to bottom

error message: "multiple filter chains with the same matching rules are defined" is hard to debug in large filters without context #11753

Open
howardjohn opened this issue Jun 25, 2020 · 0 comments · Fixed by #12405
Open

error message: "multiple filter chains with the same matching rules are defined" is hard to debug in large filters without context #11753

howardjohn opened this issue Jun 25, 2020 · 0 comments · Fixed by #12405
Labels
area/configuration help wanted Needs help!

Comments

@howardjohn
Copy link
Contributor

Its (unfortunately) not uncommon for us to run across bugs resulting in "multiple filter chains with the same matching rules are defined". These are pretty hard to debug when we have 100s of filter chains. It would be useful to get some sort of indication about which filter chain is duplicated, whether its the index of the filter chain or some other identifier.
@howardjohn howardjohn mentioned this issue Jul 28, 2020
Closed
@ramaraochavali ramaraochavali mentioned this issue Jul 31, 2020
Merged
kailun-qin added a commit to kailun-qin/envoy that referenced this issue Jan 28, 2021
@kailun-qin
listener: allocate UUID for unnamed filter chains
fcdf797 
According to the proto desc of `FilterChain` - if no name is provided, Envoy
will allocate an internal UUID for the filter chain.

This patch introduces this function for unnamed filter chains, which can help
some debugging of errors like `error adding listener '0.0.0.0:8443': filter
chain '' has the same matching rules defined as ''`.

Related to:
envoyproxy#11753
istio/istio#27480

Signed-off-by: Kailun Qin <kailun.qin@intel.com>
@kailun-qin kailun-qin mentioned this issue Jan 28, 2021
Closed
@lizan lizan reopened this Feb 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/configuration help wanted Needs help!
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

add additional debug context for filter chain errors ramaraochavali/envoy
3 participants
@howardjohn @lizan @asraa