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

[BUG] mixed cluster bwc tests are failing for elasticsearch version v7.10.2 #922

Closed
adnapibar opened this issue Jul 1, 2021 · 2 comments · Fixed by #928
Closed

[BUG] mixed cluster bwc tests are failing for elasticsearch version v7.10.2 #922

adnapibar opened this issue Jul 1, 2021 · 2 comments · Fixed by #928
Labels
backwards-compatibility bug Something isn't working v1.0.0 Version 1.0.0 v2.0.0 Version 2.0.0

Comments

@adnapibar
Copy link
Contributor

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:

MixedClusterClientYamlTestSuiteIT.test {p0=cat.health/10_basic/Empty cluster}
MixedClusterClientYamlTestSuiteIT.test {p0=cat.health/10_basic/Help}
MixedClusterClientYamlTestSuiteIT.test {p0=cat.health/10_basic/With ts parameter}

To Reproduce

./gradlew :qa:mixed-cluster:v7.10.2#mixedClusterTest

Expected behavior
The tests should pass.

Host/Environment (please complete the following information):

  • OS: Amazon Linux 2
  • Version 2

Additional context
Add any other context about the problem here.

@tlfeng
Copy link
Collaborator

tlfeng commented Jul 2, 2021

I can reproduce the failure, though different 2 test failures out of 3 during my 2 test runs.

Some logs in my test runs:

test {p0=cat.health/10_basic/Empty cluster}

java.lang.AssertionError: Failure at [cat.health/10_basic:34]: field [$body] was expected to match the provided regex but didn't
Expected: ^
  ( \d+            \s+ # epoch
    \d\d:\d\d:\d\d \s+ # timestamp
    \S+            \s+ # cluster
    \w+            \s+ # status
    \d+            \s+ # node.total
    \d+            \s+ # node.data
    \w+            \s+ # discovered_master
    \d+            \s+ # shards
    \d+            \s+ # pri
    \d+            \s+ # relo
    \d+            \s+ # init
    \d+            \s+ # unassign
    \d+            \s+ # pending_tasks
    (-|\d+(?:[.]\d+)?m?s) \s+ # max task waiting time
    \d+\.\d+%             # active shards percent
    \n
  )+
$
     but: was "1625182044 23:27:24 v7.10.2 green 4 4 0 0 0 0 0 0 - 100.0%\n"
	at __randomizedtesting.SeedInfo.seed([64755F9C74EE4E2E:EC216046DA1223D6]:0)
	at org.opensearch.test.rest.yaml.OpenSearchClientYamlSuiteTestCase.executeSection(OpenSearchClientYamlSuiteTestCase.java:427)
...
test {p0=cat.health/10_basic/With ts parameter}

java.lang.AssertionError: Failure at [cat.health/10_basic:64]: field [$body] was expected to match the provided regex but didn't
Expected: ^
  ( \S+            \s+ # cluster
    \w+            \s+ # status
    \d+            \s+ # node.total
    \d+            \s+ # node.data
    \w+            \s+ # discovered_master
    \d+            \s+ # shards
    \d+            \s+ # pri
    \d+            \s+ # relo
    \d+            \s+ # init
    \d+            \s+ # unassign
    \d+            \s+ # pending_tasks
    (-|\d+(?:[.]\d+)?m?s) \s+ # max task waiting time
    \d+\.\d+%             # active shards percent
    \n
  )+
$
     but: was "v7.10.2 green 4 4 0 0 0 0 0 0 - 100.0%\n"
	at __randomizedtesting.SeedInfo.seed([64755F9C74EE4E2E:EC216046DA1223D6]:0)
	at org.opensearch.test.rest.yaml.OpenSearchClientYamlSuiteTestCase.executeSection(OpenSearchClientYamlSuiteTestCase.java:427)
...

@nknize
Copy link
Collaborator

nknize commented Jul 2, 2021

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 discovered_master parameter and the regex fails. We need to be careful that we change the rest api spec tests so it correctly tests breaking changes or the bwc tests will sporadically fail. /cc @mgodwan

@nknize nknize added v1.0.0 Version 1.0.0 v2.0.0 Version 2.0.0 and removed Beta untriaged labels Jul 3, 2021
ritty27 pushed a commit to ritty27/OpenSearch that referenced this issue May 12, 2024
…-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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backwards-compatibility bug Something isn't working v1.0.0 Version 1.0.0 v2.0.0 Version 2.0.0
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants