Description of problem:
Our customer is unable to delete an encrypted volume due to the above error in the issue.

It is possible the issue is due to the environment having another domain that the project/user resides in that created the Barbican secret.

Version-Release number of selected component (if applicable):
13.0.16

How reproducible:
Always

Steps to Reproduce:
(Wasn't able to reproduce this on a regular environment in a single project, so believe this must have to do with a project across domains).
1. Attempt to delete an encrypted volume either as the DEFAULT/admin account, or as the domain/${secret-owner}
2. The secret volume fails to delete.

Actual results:
- User tries to delete the encrypted volume
- Cinder reports a HTTP 200 OK for confirming the volume exists, and a HTTP 202 Accepted for the request to delete the volume.
- The request for deletion then fails due to the Barbican error.

Expected results:
- We expect the encrypted volume at least to delete, and if Keystone notifications are being listened on [1], we also expect the secret to be self-cleaned.

Additional info:
- See private notes.