Validators not working when one is failing to sign AGGREGATION_SLOT

[rrazvan1]

Describe the bug

When the Prysm client has multiple validators, if one of them cannot sign AGGREGATION_SLOT message type, the error will stop other validators to sign in that epoch. Other validators shouldn't be impacted by the inability of others to sign.

This use case was occurred in development of a DVT protocol, where the Prysm client is used with Web3Signer remote signing.

More specific, isAggregator(..) method handling in subscribeToSubnets(..). Could be also in RolesAt(..) method.

Has this worked before in a previous version?

No response

🔬 Minimal Reproduction

Steps to reproduce:

1. Start Prysm Client with multiple validators using web3signer remote signer.
2. Reject signatures in one of the signatures
3. Intermittently, other validators are not working properly.

Error

time="2023-09-15 13:11:48" level=error msg="Could not get validator roles" error="could not check if a validator is an aggregator: http: ContentLength=346 with Body length 0"

time="2023-09-15 13:15:12" level=error msg="Failed to subscribe to subnets" error="could not check if a validator is an aggregator: http: ContentLength=346 with Body length 0"

Platform(s)

No response

What version of Prysm are you running? (Which release)

No response

Anything else relevant (validator index / public key)?

No response

[YuXiaoCoder]

I'm having the same problem.

Prysm: 4.0.8
Web3Signer: 23.9.0

[bert2002]

Was there any solution to this? Somehow I am experiencing the same for new validators (same error message)