-
Notifications
You must be signed in to change notification settings - Fork 40
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
Consensus couldn't catchup blocks after node rotation on staying node #1488
Labels
Comments
oleksandrSydorenkoJ
added
bug
Something isn't working
proposal
Proposal for next release
labels
Feb 17, 2023
Marked to 2.2 |
DmytroNazarenko
added
release:2.2
and removed
proposal
Proposal for next release
labels
Apr 10, 2023
github-project-automation
bot
moved this from Code Review
to Ready For Release Candidate
in SKALE Engineering 🚀
Jun 20, 2023
Merged
skaled: 3.17.0-beta.1 |
DmytroNazarenko
moved this from Ready For Release Candidate
to Merged To Release Candidate
in SKALE Engineering 🚀
Jun 21, 2023
Verified on regression network |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version:
skalenetwork/schain:3.16.0-beta.8
Environment
17 active nodes
at least 1 active schain medium type
Preconditions
All nodes have enough balance for node rotation
Steps to reproduce
Expected behavior:
Skaled on both nodes B and C should catchup blocks with rotation's delay timestamp, gracefully self-stopped, and wait for sale admin regenerates schain config with new BLS key and recreated skaled container.
Actual state:
Skaled from node B catching up all blocks before 1st mined block with new BLS keys
Skaled from node C failed to catching up the batch of blocks that contains blocks with previous public keys and new public keys.
Note
Discussed with @kladkogex and @olehnikolaiev - there are 2 solution options:
Logs:
timestamp and block number for the rotation delay
logs from skaled
The text was updated successfully, but these errors were encountered: