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.

Sign up for GitHub

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

Jump to bottom

Production Readiness: Support to upgrade hedera version through solo commands #1000

Closed
JeffreyDallas opened this issue Dec 17, 2024 · 3 comments · Fixed by #1133
Closed

Production Readiness: Support to upgrade hedera version through solo commands #1000

JeffreyDallas opened this issue Dec 17, 2024 · 3 comments · Fixed by #1133
Assignees
@JeffreyDallas
Labels
Feature Enhancement Enhancing an existing feature driven by business requirements. Typically backwards compatible. P0 An issue impacting production environments or impacting multiple releases or multiple individuals. P1 High priority issue. Required to be completed in the assigned milestone. released

Comments

@JeffreyDallas
Copy link
Contributor

Feature to Enhance

Solo should be able to upgrade hedera to a new version

Requested Enhancement

TBD

Business Need

TBD

Additional Context

No response
@JeffreyDallas JeffreyDallas added Feature Enhancement Enhancing an existing feature driven by business requirements. Typically backwards compatible. Pending Triage New issue that needs to be triaged by the team labels Dec 17, 2024
@JeffreyDallas JeffreyDallas self-assigned this Dec 17, 2024
@jeromy-cannon jeromy-cannon mentioned this issue Dec 17, 2024
Open
@jeromy-cannon jeromy-cannon added P0 An issue impacting production environments or impacting multiple releases or multiple individuals. and removed Pending Triage New issue that needs to be triaged by the team labels Dec 17, 2024
@JeffreyDallas
Copy link
Contributor Author

JeffreyDallas commented Dec 23, 2024 •
edited
Loading

Need some clarification about this issue.
whether this sounds right:

  1. user provided an zipped file (new jar files or new version file)
  2. use solo to update the special file 0.0.150
  3. use solo send preppare upgrade transaction
  4. use solo freeze upgrade transaction
  5. hedera app should unzip the 0.0.150 under directory data/upgade/current
  6. solo check if nodes are in freeze mode
  7. solo download files from data/upgradecurrent/ to staging directory
  8. prepare staging directory and copy to network nodes
  9. restart network nodes

@jeromy-cannon
Copy link
Contributor

@JeffreyDallas ,

let us make it solo node upgrade, definitely a lot of potential reuse inside of the node command.

can you expand on number 7? not sure what unzipped files you are referring to. is this referring to the files in number 1?

I think overall this sounds right. I've never done a network upgrade before, other than what we do during node add/update/delete.

@nathanklick nathanklick changed the title Support to upgrade hedera version through solo commands Production Readiness: Support to upgrade hedera version through solo commands Dec 30, 2024
@jeromy-cannon jeromy-cannon added the P1 High priority issue. Required to be completed in the assigned milestone. label Jan 9, 2025
@JeffreyDallas JeffreyDallas mentioned this issue Jan 9, 2025
Merged
@swirlds-automation
Copy link
Contributor

🎉 This issue has been resolved in version 0.34.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JeffreyDallas JeffreyDallas

Labels
Feature Enhancement Enhancing an existing feature driven by business requirements. Typically backwards compatible. P0 An issue impacting production environments or impacting multiple releases or multiple individuals. P1 High priority issue. Required to be completed in the assigned milestone. released
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat: node upgrade command and new e2e tests hashgraph/solo
3 participants
@jeromy-cannon @JeffreyDallas @swirlds-automation