Container ACL not handling NotFound properly
Bug #1441555 reported by
Thomas Herve
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Barbican |
Fix Released
|
Medium
|
Thomas Herve | ||
Bug Description
Since 237f7674cc73c66
I believe the behavior can be easily fixed by mirroring what's been done for secrets (ie, not create the controller when the order doesn't exist).
| Changed in barbican: | |
| assignee: | nobody → Thomas Herve (therve) |
| Changed in barbican: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to barbican (master) | #1 |
| Changed in barbican: | |
| status: | In Progress → Fix Committed |
| Changed in barbican: | |
| milestone: | none → kilo-rc1 |
| Changed in barbican: | |
| importance: | Undecided → Medium |
| Changed in barbican: | |
| status: | Fix Committed → Fix Released |
| Changed in barbican: | |
| milestone: | kilo-rc1 → 2015.1.0 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 21efb841b052442
Author: Thomas Herve <email address hidden>
Date: Wed Apr 8 12:01:22 2015 +0200
Return container not found before ACL checks
This fixes a recent regression where one user would get a 403 when
trying to retrieve a unknown container, instead of a 404.
Change-Id: I59c6b806591ca4
Closes-Bug: #1441555