-
Notifications
You must be signed in to change notification settings - Fork 24.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
[CI] ':x-pack:qa:full-cluster-restart:v7.5.0#upgradedClusterTest' #84869
Comments
The actual problem here looks to be an assertion error causing the node to exit.
|
Pinging @elastic/es-core-infra (Team:Core/Infra) |
The reason I pinged core/infra is that based on a quick look I had in #84844 (comment) I think this could be a follow on problem after #84780 was merged. Apologies if I'm wrong and it's a more generic index metadata problem. |
|
Looks like update settings is not matching. |
I'm going to move this over to distributed based on the settings versions not matching. |
Pinging @elastic/es-distributed (Team:Distributed) |
I have added message with some details to the failing assertion:
New settings have |
My current assumption is that this setting is added by Lines 105 to 108 in 87bd2eb
however settings version is not incremented (I am not sure why) and this result in assertion failure. |
CI Link
https://gradle-enterprise.elastic.co/s/j4ilhrcoxxn64
Repro line
./gradlew ':x-pack:qa:full-cluster-restart:v7.5.0#upgradedClusterTest'
Does it reproduce?
Yes
Applicable branches
master
Failure history
https://gradle-enterprise.elastic.co/scans/failures?failures.failureClassification=all_failures&failures.failureMessage=Execution%20failed%20for%20task%20*%0A%3E%20process%20was%20found%20dead%20while%20waiting%20for%20cluster%20health%20yellow%2C%20*&search.relativeStartTime=P7D&search.timeZoneId=America/Chicago
Failure excerpt
The text was updated successfully, but these errors were encountered: