Skip to content

release-25.3: upgrades: fix order of AddHotRangeLoggerJob migration #149359

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

rafiss
Copy link
Collaborator

@rafiss rafiss commented Jul 1, 2025

Backport 1/1 commits from #149341 on behalf of @rafiss.


The V25_3_AddHotRangeLoggerJob cluster version comes after the V25_3_AddEstimatedLastLoginTime version. Yet, the corresponding upgrade for adding the hot ranges logger was incorrectly being done before the last login time column.

informs: #148981
informs: #148998

Release note: None


Release justification: fixes the ordering of upgrades which should be preserved should it happen that the ordering matters.

The V25_3_AddHotRangeLoggerJob cluster version comes _after_ the
V25_3_AddEstimatedLastLoginTime version. Yet, the corresponding upgrade
for adding the hot ranges logger was incorrectly being done _before_ the
last login time column.

Release note: None
@rafiss rafiss force-pushed the blathers/backport-release-25.3-149341 branch from 826ea63 to aa25693 Compare July 1, 2025 17:44
@rafiss rafiss requested review from a team as code owners July 1, 2025 17:44
@blathers-crl blathers-crl bot added blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot. labels Jul 1, 2025
Copy link

blathers-crl bot commented Jul 1, 2025

Thanks for opening a backport.

Before merging, please confirm that the change does not break backwards compatibility and otherwise complies with the backport policy. Include a brief release justification in the PR description explaining why the backport is appropriate. All backports must be reviewed by the TL for the owning area. While the stricter LTS policy does not yet apply, please exercise judgment and consider gating non-critical changes behind a disabled-by-default feature flag when appropriate.

@blathers-crl blathers-crl bot added the backport Label PR's that are backports to older release branches label Jul 1, 2025
Copy link

blathers-crl bot commented Jul 1, 2025

It looks like your PR touches production code but doesn't add or edit any test code. Did you consider adding tests to your PR?

🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.

@rafiss rafiss merged commit 0246034 into cockroachdb:release-25.3 Jul 1, 2025
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport Label PR's that are backports to older release branches blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot. target-release-25.3.0
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants