exception when associating floating IP with mismatched tenants
Bug #1048104 reported by
dan wendlandt
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| neutron |
Fix Released
|
Medium
|
dan wendlandt | ||
Bug Description
if a port is owned by a tenant, the floating ip associated with that port must be owned by the same tenant.
the current code correctly checks for this, but there can be an exception when generating the exception reporting a tenant mismatch. This, combined with bad error reporting in the client, can lead people to think they correctly associated a floating IP when they did not.
| Changed in quantum: | |
| importance: | Undecided → Medium |
| status: | New → In Progress |
| assignee: | nobody → dan wendlandt (danwent) |
| milestone: | none → folsom-rc1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to quantum (master) | #1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to quantum (master) | #2 |
| Changed in quantum: | |
| status: | In Progress → Fix Committed |
| Changed in quantum: | |
| status: | Fix Committed → Fix Released |
| Changed in quantum: | |
| milestone: | folsom-rc1 → 2012.2 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/