-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
test: fix compat integration error from new access log api #15827
Conversation
@DanStough , thanks for fixing this. Having a question about what caused the problem: I observed that the error occurs when the test code constructs clusters using images of old version
So should the root cause be
|
I'm having a hard time with the fact that new fields in the request cause failures, but that's a separate issue altogether. We should definitely revisit this at some point. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was able to get this working by pinning a version of the api submodule and using that instead of the local version. I will link to the PR shortly.
See #15830. |
Closing this PR in favor of #15831 |
Description
This fixes failures in the integration test suite for upgrades. The problem was caused by using the latest version of
api
module, with new fields, against the upgrade source of Consul, resulting in a 400 error. This causes the tests to timeout.This isn't a fix for the problem so much as removing a nice-to-have step. All the values in the proxy-default are assumed to be the fault, so the effect is negligible.