Fix needed to avoid Node Add/Update/Delete breaking in future version #541
Labels
Feature Enhancement
Enhancing an existing feature driven by business requirements. Typically backwards compatible.
P1
High priority issue. Required to be completed in the assigned milestone.
released
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: