Barbican secret get request returns deleted objects
Bug #1540339 reported by
Peter Razumovsky
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| python-barbicanclient |
New
|
Undecided
|
Elvin Tubillara | ||
Bug Description
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.
| Changed in barbican: | |
| assignee: | nobody → tingwang (bx-wang) |
Revision history for this message
| ting.wang (bx-wang) wrote | #1 |
| Changed in barbican: | |
| assignee: | tingwang (bx-wang) → nobody |
| Changed in barbican: | |
| assignee: | nobody → Elvin Tubillara (edtubill) |
| affects: | barbican → python-barbicanclient |
Revision history for this message
| Elvin Tubillara (edtubill) wrote | #2 |
To post a comment you must log in.
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?