Skip to content

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

Merged
merged 2 commits into from
Apr 29, 2025

Conversation

samxbr
Copy link
Contributor

@samxbr samxbr commented Apr 28, 2025

Test was failing due to unable to parse failure store template, this enables the failure store feature flag for the test cluster.

Caused by: org.elasticsearch.xcontent.XContentParseException: [-1:45511] [data_stream_template] unknown field [failure_store]

Closes #126967

@samxbr samxbr added >test-failure Triaged test failures from CI :Data Management/Data streams Data streams and their lifecycles labels Apr 28, 2025
@samxbr samxbr marked this pull request as ready for review April 28, 2025 22:35
@elasticsearchmachine elasticsearchmachine added Team:Data Management Meta label for data/management team needs:risk Requires assignment of a risk label (low, medium, blocker) labels Apr 28, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-data-management (Team:Data Management)

@samxbr samxbr added >test Issues or PRs that are addressing/adding tests and removed >test-failure Triaged test failures from CI needs:risk Requires assignment of a risk label (low, medium, blocker) labels Apr 28, 2025
Copy link
Contributor

@nielsbauman nielsbauman left a 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.

@samxbr samxbr added auto-backport Automatically create backport pull requests when merged v9.1.0 v8.18.1 v8.19.0 v8.18.0 labels Apr 29, 2025
@samxbr samxbr merged commit 71a6c7f into elastic:9.0 Apr 29, 2025
16 checks passed
@elasticsearchmachine
Copy link
Collaborator

💔 Backport failed

Status Branch Result
8.18 Commit could not be cherrypicked due to conflicts
8.19 Commit could not be cherrypicked due to conflicts
main Commit could not be cherrypicked due to conflicts

You can use sqren/backport to manually backport by running backport --upstream elastic/elasticsearch --pr 127480

samxbr added a commit to samxbr/elasticsearch that referenced this pull request Apr 29, 2025
…IT (elastic#127480)

(cherry picked from commit 71a6c7f)

# Conflicts:
#	muted-tests.yml
samxbr added a commit to samxbr/elasticsearch that referenced this pull request Apr 29, 2025
…IT (elastic#127480)

(cherry picked from commit 71a6c7f)

# Conflicts:
#	muted-tests.yml
@samxbr
Copy link
Contributor Author

samxbr commented Apr 29, 2025

💚 All backports created successfully

Status Branch Result
main
8.19
8.18

Questions ?

Please refer to the Backport tool documentation

samxbr added a commit to samxbr/elasticsearch that referenced this pull request Apr 29, 2025
…IT (elastic#127480)

(cherry picked from commit 71a6c7f)

# Conflicts:
#	muted-tests.yml
samxbr added a commit that referenced this pull request Apr 29, 2025
samxbr added a commit that referenced this pull request Apr 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto-backport Automatically create backport pull requests when merged backport pending :Data Management/Data streams Data streams and their lifecycles Team:Data Management Meta label for data/management team >test Issues or PRs that are addressing/adding tests v8.18.0 v8.18.1 v8.19.0 v9.0.1 v9.1.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants