Skip to content

Tolerate incompatible versions with different build hash #128589

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

Conversation

mosche
Copy link
Contributor

@mosche mosche commented May 28, 2025

Tolerate incompatible versions with different build hash.
I'm keeping the serverless feature flag to not create warnings there.

Relates to ES-11869

@mosche mosche requested review from rjernst and a team May 28, 2025 17:07
@mosche mosche added >non-issue :Core/Infra/Core Core issues without another label labels May 28, 2025
@mosche mosche removed the request for review from rjernst May 28, 2025 17:08
@elasticsearchmachine elasticsearchmachine added v9.1.0 Team:Core/Infra Meta label for core/infra team labels May 28, 2025
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra (Team:Core/Infra)

Copy link
Contributor

@ldematte ldematte left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you need to update TransportServiceHandshakeTests accordingly

Copy link
Contributor

@ldematte ldematte left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

@DaveCTurner DaveCTurner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hang on, I don't think we can safely remove this without adding more testing of the new upgrade paths that it enables.

@mosche mosche changed the title Tolerate incompatible versions with different build hash [DO NOT MERGE YET] Tolerate incompatible versions with different build hash May 30, 2025
@mosche
Copy link
Contributor Author

mosche commented May 30, 2025

We're working on adding these tests at the moment. Though, we can definitely use the serverless flag initially for these tests and only remove the check once all tests are in place 👍

@mosche mosche marked this pull request as draft May 30, 2025 08:27
@ldematte
Copy link
Contributor

++
We can hold off this change off ATM, but rest assured that we are actively working on adding these tests.

@DaveCTurner
Copy link
Contributor

I see ok, yes I'd prefer we held off on merging this until we have that test coverage in place. Either that'll be quick (in which case nbd) or it'll take a while (in which case this change will cause a mess with 9.1.0 BCs)

@DaveCTurner DaveCTurner dismissed their stale review May 30, 2025 08:42

tests are WIP elsewhere

@mark-vieira
Copy link
Contributor

I see ok, yes I'd prefer we held off on merging this until we have that test coverage in place. Either that'll be quick (in which case nbd) or it'll take a while (in which case this change will cause a mess with 9.1.0 BCs)

There's a little bit of a chicken/egg though, we can't merge the testing w/o this change (as the tests would fail). But we can potentially hold off on merging this until the tests are ready and then merge both together.

@DaveCTurner
Copy link
Contributor

hold off on merging this until the tests are ready and then merge both together

That would be my preference. Really I just want to avoid creating any 9.1.0 BCs without this check until there's sufficient test coverage. If we can't get the test coverage in place for 9.1.0-BC1 then maybe it'd be better to delay this until after 9.1.0 is fully released.

@ldematte ldematte changed the title [DO NOT MERGE YET] Tolerate incompatible versions with different build hash Tolerate incompatible versions with different build hash Jun 18, 2025
@ldematte ldematte marked this pull request as ready for review June 18, 2025 10:07
@ldematte
Copy link
Contributor

Now that we have same-version upgrade tests on every PR and intake build, this is safe to merge.
I will let the intake/PR builds run for today, and if there are no problems I'll merge this.

@ldematte ldematte enabled auto-merge (squash) June 19, 2025 15:05
@ldematte ldematte merged commit 9b2ca99 into elastic:main Jun 20, 2025
27 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Core/Infra/Core Core issues without another label >non-issue Team:Core/Infra Meta label for core/infra team v9.1.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants