Failed proposal: invalid `eth-consensus-block-value` header

[olegshmuelov]

The following error occurred during proposal processing:

failed to get proposal: proposal header Eth-Consensus-Block-Value not a valid integer

This issue could potentially be related to a beacon node (BN) or go-eth2-client. Further investigation is required to confirm the root cause.

Occurred on stage cluster 275-278 v2.0.1

[anatolie-ssv]

After inspecting go-eth2-client and prysm code it seems that the error is on the prysm side when it's trying to get the block value but fails with an internal server error, then sets the mentioned header to empty string, which in turn causes the eth2 client to fail when trying to cast it to an int:

https://github.com/prysmaticlabs/prysm/blob/develop/beacon-chain/rpc/eth/validator/handlers_block.go...

Because the logs containing these errors (in stage) are no longer accessible, this task will be put on hold. The logs are important because there are 3 cases when prysm fails to get the block and in all cases it will log the cause before setting the value of the header to "".

[MatusKysel]

we had same issue on Hoodi, it was Prysm bug they fixed. I am closing it and we can re-open if we see it again

[MatusKysel]

OffchainLabs/prysm#15174
attestantio/go-eth2-client#221