upgrade-16rc2 causing 'failed to load latest version' #9682
Assignees
Labels
bug
Something isn't working
Comments
mhofman
added a commit
that referenced
this issue
Jul 10, 2024
closes: #9682 ## Description Add logic to check if the upgrade plan name is a "primary name", and only run store migrations for those. Check in the upgrade handler that the first upgrade is using a primary name to ensure store migrations were run. ### Security Considerations None ### Scaling Considerations None ### Documentation Considerations None ### Testing Considerations a3p test for primary upgrade will run on this PR [mhofman/9682-test-double-upgrade](https://github.com/Agoric/agoric-sdk/tree/mhofman/9682-test-double-upgrade) tests applying primary followed by secondary upgrade ### Upgrade Considerations Fixes cosmos store upgrade logic during chain software upgrades
|
Fix for u16 release landed in #9683, will need to be posted to master, adapting the |
mhofman
added a commit
that referenced
this issue
Jul 10, 2024
## Packages that have NEWS.md updates ```diff --- a/golang/cosmos/CHANGELOG.md +++ b/golang/cosmos/CHANGELOG.md @@ -3,6 +3,15 @@ All notable changes to this project will be documented in this file. See [Conventional Commits](https://conventionalcommits.org) for commit guidelines. +## [0.35.0-u16.2](https://github.com/Agoric/agoric-sdk/compare/@agoric/cosmos@0.35.0-u16.1...@agoric/cosmos@0.35.0-u16.2) (2024-07-10) + + +### Bug Fixes + +* **cosmos:** don't rerun store migrations on upgrade ([#9683](#9683)) ([12b78e3](12b78e3)), closes [#9682](#9682) + + + ## [0.35.0-u16.1](https://github.com/Agoric/agoric-sdk/compare/@agoric/cosmos@0.35.0-u16.0...@agoric/cosmos@0.35.0-u16.1) (2024-07-10) **Note:** Version bump only for package @agoric/cosmos ```
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Upgrade-16-RC2 causes the node not to be able to start with the following error message.
Ref: https://github.com/Agoric/agoric-sdk/releases/tag/agoric-upgrade-16-rc2
To Reproduce
Steps to reproduce the behavior:
Upgrade the validator node using container tag: 46
Restart the node, and wait for it to generate blocks
Results in the node process exit with above error message
Expected behavior
A clear and concise description of what you expected to happen.
Platform Environment
git describe --tags --always)Additional context
Add any other context about the problem here.
Screenshots
If applicable, add screenshots to help explain your problem, especially for UI interactions.
The text was updated successfully, but these errors were encountered: