ci: solo pd node reset on point release #4459
Comments
conorsch
added
the
A-CI/CD
github-actions
bot
added
the
needs-refinement
conorsch
added
_P-low
|
I manually deployed v0.77.1 via a script, to avoid this reset: for now, let's just snip out the erroneously resetting workflow mention, because it's more work to resync from scratch than to upgrade the standalone node manually. |
conorsch
added a commit
that referenced
this issue
Jun 4, 2024
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.
1 task
conorsch
added a commit
that referenced
this issue
Jun 4, 2024
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.
conorsch
added a commit
that referenced
this issue
Jun 4, 2024
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
added a commit
that referenced
this issue
Jun 4, 2024
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)
|
Worked well on 0.77.2 deploy: https://github.com/penumbra-zone/penumbra/actions/runs/9375323905/job/25813550110
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Notes for later: the point-release CI job doesn't handle the solo pd nodes (#3336) gracefully: https://solo-pd.testnet.plinfra.net/ was reset and now must sync from scratch. Let's circle back and make that nicer.
Originally posted by @conorsch in #4448 (comment)
The text was updated successfully, but these errors were encountered: