Skip to content
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

backports point-release support for solo node #4556

Merged
merged 1 commit into from
Jun 4, 2024

Conversation

conorsch
Copy link
Contributor

@conorsch conorsch commented Jun 4, 2024

Describe your changes

Backports PR #4551 for 0.77.2 (#4545).

Issue ticket number and link

Checklist before requesting a review

  • If this code contains consensus-breaking changes, I have added the "consensus-breaking" label. Otherwise, I declare my belief that there are not consensus-breaking changes, for the following reason:

    ci-only

The solo node, run outside the cluster, was being fully reset on
point releases, due to the aggressive reset logic that was written
during the days of frequent chain resets. We're performing
point-releases more regularly now, so let's make sure to avoid resetting
the solo node in those cases. Still unsupported is chain-migration logic
specifically for the solo node, but that's fine: we're handling chain
upgrades out of band for now anyway.

Closes #4459.

(cherry picked from commit 0b02ec3)
@conorsch conorsch merged commit 9e680ff into release/v0.77.x Jun 4, 2024
11 checks passed
@conorsch conorsch deleted the backport-solo-node-fixes branch June 4, 2024 22:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants