L2 web3signer has fewer than 4 keys loaded

Probable cause web3signer-l2

33m

to resolve

alerts, all cleared

0/19

checklist

—

next update

acked 60s

paging

Follow-up added (P1 prevent): Validate the key count in CI before a web3signer Secret change merges
10-13 11:52 UTC · bob
state resolved → postmortem
10-13 11:52 UTC · bob
state mitigated → resolved
10-13 11:52 UTC · bob
summary: All 4 keys loaded since 01:28; blob submission caught up
10-13 11:52 UTC · bob
state declared → mitigated
10-13 11:39 UTC · bob
Restore the previous key Secret and restart web3signer
Why
fastest way back to 4 keys; the rotation can be redone in a window
Instead of
fix the mount and keep the new keys
Revert when
rotation re-planned
10-13 11:36 UTC · bob
web3signer started with 2 of 4 keys: the new key files were mounted under the old Secret name.
10-13 11:32 UTC · bob
Acknowledged the page, 60s after it was sent
10-13 11:24 UTC · bob
Paged via ntfy (step 1, mock)
10-13 11:23 UTC · paging
state candidate → declared
10-13 11:23 UTC · bob
SEV — → 2
10-13 11:23 UTC · bob
Deployed Kustomization lineth-l2-signing main@9f8e7d6
Deployment/lineth-l2/web3signer configured
10-13 11:12 UTC · flux

Loading…