VMware vSAN (All Versions)
This is caused due to the vSAN disks not being able to decrypt themselves due to communication issues to the KMS cluster resulting in not being able to validate the KEKs with the KMS cluster.
From vmkernel you see:
2025-04-06T20:56:02.376Z In(182) vmkernel: cpu0:2131939 opID=195ee45e)KeyCache: 924: Trying to resolve key for keyId 5######5-####-####-####-d##########e
2025-04-06T20:56:02.376Z In(182) vmkernel: cpu0:2131939 opID=195ee45e)KeyCache: 860: Request to populate 5######5-####-####-####-d##########e in keycache
2025-04-06T20:56:02.376Z In(182) vmkernel: cpu0:2131939 opID=195ee45e)KeyCache: 880: RPC_SendAndGetReply() reply result: Not found
2025-04-06T20:56:02.376Z In(182) vmkernel: cpu0:2131939 opID=195ee45e)KeyCache: 930: Did not find keyID 5######5-####-####-####-d##########e in key cache
Engage your KMS administrator/vendor for further investigation.