-
Notifications
You must be signed in to change notification settings - Fork 24.8k
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
BWC test failures for health/10_basic/cluster health basic test #105923
Comments
Pinging @elastic/es-data-management (Team:Data Management) |
@nielsbauman I am going to remute the test failure. This prevents full-bwc from passing. |
I have tried to replicate, but it doesn't reliably. Is there an internal race condition or something that tries to create the index incorrectly? |
I'm looking at this right now, but I'm having a hard time figuring out why this could happen. This test doesn't do anything with indices... |
@benwtrent the repro line you pasted in the issue seems to deviate from the one in the build scan. Is that correct? |
@nielsbauman I might have copied from the wrong one. Each bwc build is its own build scan and 5 different versions all failed. Let me enumerate the ones that failed:
Here is a full trace that is easier to read than the above one I pasted (I replaced the \n and \t):
|
@nielsbauman I see the API is called Are we sure this API is available via clusters before 8.7.0? I keep seeing failures for <= 8.6.2. |
@nielsbauman I see the API changed names. 8.6:
8.7:
This makes me think this thing should be muted in 8.6 or before as the NEW (8.7+) yaml REST API definition just won't work in earlier versions |
#92879 relevant PR. |
@benwtrent ah sorry I didn't know that about bwc builds. And I'm looking at the API name change right now as well. It's interesting that there are no issues in other builds, but maybe I'm missing something. I'm down to update the mute-version of the test right now, and I'll take a closer look tomorrow at what's happening exactly. Does that work for you? |
Seems like the test you unmuted was broken by that PR, but since it was muted, we never caught it. |
Your plan seems good to me. I would suggest us having two tests in that file that was unmuted. One for the new version (8.7+) One for the old version (if its supported, IDK if it is or not that test was muted for over a year). |
The health report API changed names in elastic#92879, which causes this YAML REST test to fail in versions < 8.7.0. Closes elastic#105923
CI Link
https://gradle-enterprise.elastic.co/s/j2zhn5js47wcy
Repro line
./gradlew ':qa:mixed-cluster:v8.5.3#mixedClusterTest' -Dtests.class="org.elasticsearch.backwards.MixedClusterClientYamlTestSuiteIT" -Dtests.method="test {p0=health/10_basic/cluster health basic test}" -Dtests.seed=72A1B4518E0C3ECD -Dtests.bwc=true -Dtests.locale=es-UY -Dtests.timezone=America/Blanc-Sablon -Druntime.java=21
Does it reproduce?
No
Applicable branches
8.13, main
Failure history
No response
Failure excerpt
This is likely due to #105789
The text was updated successfully, but these errors were encountered: