-
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
SharedClusterSnapshotRestoreIT#testGetSnapshotsRequest fails #31054
Comments
Pinging @elastic/es-distributed |
@tlrx does this ring a bell to you? |
@bleskes Yes, this is the same issue as #26480 which has been fixed in 6.0 and later by #28130. We decided to not backport the fix to 5.x because it was non trivial, but it's annoying that this failure comes up from time to time on 5.6. So maybe I should try to backport the change on this branch too. |
@tlrx thanks. Another potential strategy is to weeken the test a bit in 5.6 to not bump into it. I'm not sure if it's relevant, but it might be less hassle. |
@bleskes this is not limited to the above test I think
to
The reason is only for reporting purposes, but we need a non-null value for serialization purposes. |
* Fix assertion by workaround for `5.6` * Reenable test that tripped this assertion * Closes elastic#31054
* Fix assertion by workaround for `5.6` * Reenable test that tripped this assertion * Closes #31054
Fixed in d61e45d |
CI link: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+5.6+multijob-unix-compatibility/os=oraclelinux/1127/consoleFull
(does not reproduce locally)
Failure output:
The assertion in
ShardSnapshotStatus
indicates that we tried to initialize it with a failure but did not provide a reason.The text was updated successfully, but these errors were encountered: