fix: update Elasticsearch to 8.5.0 and ES_VERSION to v8#316
Closed
fix: update Elasticsearch to 8.5.0 and ES_VERSION to v8#316
Conversation
The docker-compose smoke test ("Ensure images work") was failing because
auto-setup had ES_VERSION=v7 while running ES 8.0.0. This mismatch caused
the auto-setup container to get stuck waiting for Elasticsearch.
This fix was applied to release/v1.29.x in PR #309 but was never applied
to main, causing CI failures on all release branch PRs since
docker-build-only.yml checks out main.
Made-with: Cursor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
ELASTICSEARCH_VERSIONfrom8.0.0to8.5.0in.envES_VERSIONfromv7tov8indocker-compose.ymlThis fix was applied to
release/v1.29.xin PR #309 but was never applied tomain. Sincedocker-build-only.yml(used by thefeatures-integrationCI) always checks outmain, this has been causing CI failures on all release branch PRs — including the v1.28.3 release (PR #315).The auto-setup container was configured with
ES_VERSION=v7while running ES 8.0.0, causing it to get stuck waiting for Elasticsearch during the smoke test.Test plan
Made with Cursor