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.

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

Merged
merged 7 commits into from
Sep 25, 2020
Merged

Onetechnical/relstable2.1.6 #1552

merged 7 commits into from
Sep 25, 2020

Conversation

onetechnical
Copy link
Contributor

@onetechnical onetechnical commented Sep 23, 2020

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

  1. Other
    • Bug Fixes
      • Use DEFAULT_RELEASE_NETWORK genesis file in debian package
      • Attempt to fix bad genesis file on 2.1.5 debian install

Test Plan

Standard release testing.

clean install 2.1.4, upgrade 2.1.5, upgrade 2.1.6 (scenario #1)

  • verify mainnet config (after 2.1.4)
  • verify testnet config (after 2.1.5)
  • verify mainnet config (after 2.1.6)

clean install 2.1.4, testnet config, upgrade 2.1.5, upgrade 2.1.6 (scenario #2)

  • verify mainnet config (after 2.1.4)
  • implement testnet config
  • verify testnet config (after 2.1.5)
  • verify testnet config (after 2.1.6)

clean install 2.1.5, mainnet config, upgrade 2.1.6 (scenario #3)

  • verify testnet config (after 2.1.5)
  • implement mainnet config
  • verify mainnet config (after 2.1.6)

clean install 2.1.5, upgrade 2.1.6 (scenario #4)

  • verify testnet config (after 2.1.5)
  • verify testnet config (after 2.1.6)

clean install 2.1.6

  • verify mainnet config

clean install 2.1.4, upgrade 2.1.6

  • verify mainnet config (after 2.1.4)
  • verify mainnet config (after 2.1.6)

clean install 2.1.4, testnet config, upgrade 2.1.6

  • verify mainnet config (after 2.1.4)
  • implement testnet config
  • verify testnet config (after 2.1.6)

@onetechnical onetechnical requested a review from btoll September 23, 2020 23:26
@onetechnical onetechnical self-assigned this Sep 23, 2020
@onetechnical
Copy link
Contributor Author

Waiting for betanet validation before changing from draft mode.

sudo apt-get remove $INSTALLED_PKG\n\
sudo apt-get install $PKG_NAME\n"
exit 1
if [[ "$ALGO_TIMESTAMP" != 1600456830 ||
Copy link
Contributor

@bricerisingalgorand bricerisingalgorand Sep 25, 2020

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?

Copy link

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.

@onetechnical onetechnical marked this pull request as ready for review September 25, 2020 00:50
@onetechnical
Copy link
Contributor Author

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.

@algojohnlee algojohnlee merged commit df65da2 into algorand:rel/stable Sep 25, 2020
@btoll
Copy link

btoll commented Sep 25, 2020

Tested all scenarios with a 2.1.6 build on both 18.04 and 20.04 and they worked as expected.

@onetechnical
Copy link
Contributor Author

Re-verified all test cases on ubuntu 20.04 on EC2.

@onetechnical onetechnical deleted the onetechnical/relstable2.1.6 branch April 16, 2021 21:31
tsachiherman pushed a commit to tsachiherman/go-algorand that referenced this pull request Jul 7, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants