-
Notifications
You must be signed in to change notification settings - Fork 25.2k
Enable FAILURE_STORE feature flag for LogsIndexModeFullClusterRestartIT #127480
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
Conversation
Pinging @elastic/es-data-management (Team:Data Management) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks @samxbr!
I think we should backport this to more branches. I see some failures on main
as well. And since the failure occurs during the upgrade from 8.17
to 8.18
, I think we should backport to 8.19
and maybe even 8.18
to be sure.
I think you should be able to backport "forward' (i.e. by keeping the PR as-is and adding the auto-backport
and 9.1.0
labels), but you can also change the target branch of the PR and rebase/cherry-pick the commit.
💔 Backport failed
You can use sqren/backport to manually backport by running |
…IT (elastic#127480) (cherry picked from commit 71a6c7f) # Conflicts: # muted-tests.yml
…IT (elastic#127480) (cherry picked from commit 71a6c7f) # Conflicts: # muted-tests.yml
💚 All backports created successfully
Questions ?Please refer to the Backport tool documentation |
…IT (elastic#127480) (cherry picked from commit 71a6c7f) # Conflicts: # muted-tests.yml
Test was failing due to unable to parse failure store template, this enables the failure store feature flag for the test cluster.
Closes #126967