Exposed by HELP-38218.
During replication rollback, the KeyManagerCache was reset, then not immediately refreshed before the next client operation, causing the client operation to fail with KeyNotFound.

KeyManagerCache keys will still be valid upon rollback; refresh with read-majority may not be possible while rolling back.