Barbican secret get request returns deleted objects

[Peter Razumovsky]

If get secret, which is already deleted, with API secrets.get, get request return secret object, which on every calling attr raises NotFound error.

Way to reproduce:

1. Create Secret object with API: secrets.create
2. Get Secret object with API: secrets.get (Expected status: return secret object; Real status: return secret object)
3. Delete Secret object with secrets.delete
4. Get Secret object with API: secrets.get (Expected status: raises NotFound exception; Real status: return secret object)
  4.1 getattr some attr of secret object, e.g. algorithm - it raises NotFound.

So, after deleting get request should raises NotFound and not return incorrect stub object.

[ting.wang (bx-wang)]

seems not affect me.
my operation:
1. barbican secret store
2. barbican secret get URI
3. barbican secret delete URI
4. barbican secret get URI
and Not Found returned.

Is my operation right?

What version of barbican do you use?

[Elvin Tubillara (edtubill)]

It seems that I can reproduce it if I use the barbican client library api. I'm not sure if this bug is valid, as the contents of the secret are lazy loaded when an attribute is referenced.