-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
[BUG] mixed cluster bwc tests are failing for elasticsearch version v7.10.2 #922
Comments
I can reproduce the failure, though different 2 test failures out of 3 during my 2 test runs. Some logs in my test runs:
|
This bug was introduced here in #656. The bwc cat.health test was unilaterally changed without bwc support. So a response is coming from a 7.10.2 node that doesn't include the |
…-client (opensearch-project#922) * Bump io.github.classgraph:classgraph in /java-client Bumps [io.github.classgraph:classgraph](https://github.com/classgraph/classgraph) from 4.8.168 to 4.8.170. - [Release notes](https://github.com/classgraph/classgraph/releases) - [Commits](classgraph/classgraph@classgraph-4.8.168...classgraph-4.8.170) --- updated-dependencies: - dependency-name: io.github.classgraph:classgraph dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <[email protected]> * Update changelog Signed-off-by: dependabot[bot] <[email protected]> --------- Signed-off-by: dependabot[bot] <[email protected]> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: dependabot[bot] <dependabot[bot]@users.noreply.github.com>
Describe the bug
The backwards compatibility tests for Elasticsearch version v7.10.2 are failing for the mixed-cluster tests. These tests verify that the current version is wire compatible with a BWC version.
Failing Tests:
To Reproduce
./gradlew :qa:mixed-cluster:v7.10.2#mixedClusterTest
Expected behavior
The tests should pass.
Host/Environment (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: