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

invalid virtual service causes entire gateway to be invalidated #3538

Closed
ilackarms opened this issue Aug 21, 2020 · 1 comment · Fixed by #3854
Closed

invalid virtual service causes entire gateway to be invalidated #3538

ilackarms opened this issue Aug 21, 2020 · 1 comment · Fixed by #3854
Assignees
Labels
Type: Bug Something isn't working

Comments

@ilackarms
Copy link
Member

auth configuration is provided on the VirtualService level. When the virtual service has an invalid auth config, the following line reports an error on the Gateway (not the VS):

validation.AppendHTTPListenerError(

This causes the VS to be improperly reported as "accepted", while the Gateway will be reported with an error (and stripped from the resulting Proxy). This means that a single invalid VS can take down an entire gateway which serves multiple VirtaulServices

We should report the error to the VirtualService, not the Gateway

@ilackarms ilackarms added the Type: Bug Something isn't working label Aug 21, 2020
@ilackarms
Copy link
Member Author

for context: i came across this bug when working on developer portal. i created a VirtualService with a pointer to an AuthConfig which didn't exist. I noticed that the generated Proxy did not contain the virtualservice (which was marked accepted) or the gateway (listener) which was supposed to capture the virtual service. i ran gloo locally and discovered the gateway was being trimmed from the proxy by validation, which was reporting an error on the gateway rather than the virtualservice

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants