-
Notifications
You must be signed in to change notification settings - Fork 8
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
Fix needed to avoid Node Add/Update/Delete breaking in future version #541
Comments
Do we still need this issue since we already updated to version 0.54 ? |
@JeffreyDallas , yes, it is still needed, I think it sometimes works because we copy the new keys to staging, but we really should be pulling them from the upgrade directory. It is sometimes causing me errors. Here is the sysout now that I'm using v0.54.0-alpha.4:
|
🎉 This issue has been resolved in version 0.30.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
current code for
solo node add
/update/delete leverages the following directory:.../data/upgrade/current
however, Nathan pointed out that NMT has always used the following:
../data/upgrade/current/data/keys
A patch has been made to the code, which is currently in
develop
forhashgraph/hedera-services
: hashgraph/hedera-services@37d1891My proposal is to check if the
../data/upgrade/current/data/keys
directory exists, if so proceed with that, if not revert to the.../data/upgrade/current
directory. Once we get past the versions with the bad directory v0.53 + v0.54? then we can remove the check.The text was updated successfully, but these errors were encountered: