-
Notifications
You must be signed in to change notification settings - Fork 491
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
Onetechnical/relstable2.1.6 #1552
Onetechnical/relstable2.1.6 #1552
Conversation
…1544) The current debian package will incorrectly package the testnet genesis file. This fix addresses that issue.
onetechnical/relbeta2.1.6
Waiting for betanet validation before changing from draft mode. |
Hot fix for fixing bad genesis file on 2.1.5 install (#1553)
sudo apt-get remove $INSTALLED_PKG\n\ | ||
sudo apt-get install $PKG_NAME\n" | ||
exit 1 | ||
if [[ "$ALGO_TIMESTAMP" != 1600456830 || |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is this stuff checking that the last time the genesis file was edited is the right date and checksum?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That timestamp is the timestamp of the 2.1.5 genesis files only, and we're using to check if the install was prior to or after 2.1.5.
BetaNet updated successfully. Tested running a BetaNet node using debian package, RPM package, and ARM binary. Considering this safe enough to move to build phase. |
Tested all scenarios with a 2.1.6 build on both 18.04 and 20.04 and they worked as expected. |
Re-verified all test cases on ubuntu 20.04 on EC2. |
…able2.1.6 Onetechnical/relstable2.1.6
Summary
Highlights
A bug in the algorand debian package would result in the genesis.json for TestNet being applied instead of MainNet. Debian users who upgraded to 2.1.5 should verify that
/var/lib/algorand/genesis.json
is pointing to the correct network after upgrading to this version.Changes
Test Plan
Standard release testing.
clean install 2.1.4, upgrade 2.1.5, upgrade 2.1.6 (scenario #1)
clean install 2.1.4, testnet config, upgrade 2.1.5, upgrade 2.1.6 (scenario #2)
clean install 2.1.5, mainnet config, upgrade 2.1.6 (scenario #3)
clean install 2.1.5, upgrade 2.1.6 (scenario #4)
clean install 2.1.6
clean install 2.1.4, upgrade 2.1.6
clean install 2.1.4, testnet config, upgrade 2.1.6