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

Peer fails to validate blocks after migration from Raft to BFT #4999

Open
dviejokfs opened this issue Oct 1, 2024 · 1 comment
Open

Peer fails to validate blocks after migration from Raft to BFT #4999

dviejokfs opened this issue Oct 1, 2024 · 1 comment
Labels

Comments

@dviejokfs
Copy link

Description

After the migration from Raft to BFT, peers are not able to validate the blocks:

�[33m2024-09-26 19:52:56.664 UTC 0393 WARN�[0m [peer.blocksprovider] �[33;1mProcessIncoming�[0m -> Got error while attempting to receive blocks: block [12] from orderer [Address: orderer02.localho.st:443, CertHash: D604508DEF6A7DFBCEF728B032A5A4FF] could not be verified: signature set did not satisfy policy channel=deploy2 orderer-address=orderer02.localho.st:443

Steps to reproduce

I'm not sure if this will reproduce the issue, but I got this issue when migrating a network from Raft to BFT, get a block in maintenance mode without restarting the orderers.

@dviejokfs dviejokfs added the bug label Oct 1, 2024
@yacovm
Copy link
Contributor

yacovm commented Oct 3, 2024

Can you please post how your blockchain section from entering migration to exiting it looks like? If you can post the JSONs of the blocks in that section, it would help to analyze what happened.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants