[Bug]: Nimbus & Teku Shared Validator Client Error

[daGscheid]

Environment

Release

Bug Description

Using the Exit & Withdrawal on an individual key & exit all with the Nimbus & Teku Validator Client throws the following error

Teku

Nimbus

Launcher Version

2.2.2

Operating System

Windows

Affected Service (if applicable)

24.10.1

Logs (if applicable)

TEKU

TASK: Exiting Account Failed
ACTION: Exiting Account Failed
CATEGORY: FAILED
DATA: Exiting Account Failed 0xaae97e122519c49a924363bc434e58961231f1f45f862dd85d9e9eeca062fae3e3fea2241fbcad08dd53736add163d5f:
Error: 404 NOT_FOUND: 0xaae97e122519c49a924363bc434e58961231f1f45f862dd85d9e9eeca062fae3e3fea2241fbcad08dd53736add163d5f is disabled or not managed by this validator client



TASK: Getting signed voluntary exit message Failed
ACTION: Getting signed voluntary exit message Failed
CATEGORY: FAILED
DATA: Getting signed voluntary exit message 0xaae97e122519c49a924363bc434e58961231f1f45f862dd85d9e9eeca062fae3e3fea2241fbcad08dd53736add163d5f Failed:
404 NOT_FOUND: 0xaae97e122519c49a924363bc434e58961231f1f45f862dd85d9e9eeca062fae3e3fea2241fbcad08dd53736add163d5f is disabled or not managed by this validator client

NIMBUS

TASK: Getting signed voluntary exit message Failed
ACTION: Getting signed voluntary exit message Failed
CATEGORY: FAILED
DATA: Getting signed voluntary exit message 0x86d32e43bec97364babf6ea3fa6499713213e1b40cee55d03e72b53d753c451433d09a4e2d9243ea1b0849438f03a405 Failed:
404 NOT_FOUND: 0x86d32e43bec97364babf6ea3fa6499713213e1b40cee55d03e72b53d753c451433d09a4e2d9243ea1b0849438f03a405 is disabled or not managed by this validator client


TASK: Exiting Account Failed
ACTION: Exiting Account Failed
CATEGORY: FAILED
DATA: Exiting Account Failed 0xb81300b1067f9bb75daf7e9029f69b760197110aac560d43750b6554b691512b3379b1b2000b9f2dcc036e36ac14022b:
Error: 404 NOT_FOUND: 0xb81300b1067f9bb75daf7e9029f69b760197110aac560d43750b6554b691512b3379b1b2000b9f2dcc036e36ac14022b is disabled or not managed by this validator client

Acknowledgment

• I have checked the existing bugs and confirmed this issue is not already reported.