Fail-fast for invalid read_deleted values
Bug #961588 reported by
Rick Harris
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Compute (nova) |
Fix Released
|
Medium
|
Rick Harris | ||
Bug Description
`read_deleted` is a tri-valued variable ('yes', 'no', 'only').
Somehow it's getting set to True, but grep'ing through the code, it's not obvious where this is happening.
Moreover, the tracebacks we're getting are pretty useless b/c it looks like it's taking on the invalid way before the exception is triggered.
To fix this, I suggest making `read_deleted` a property so that we can fail immediately if an invalid value is attempted.
| Changed in nova: | |
| assignee: | nobody → Rick Harris (rconradharris) |
| importance: | Undecided → Medium |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to nova (master) | #1 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to nova (master) | #2 |
| Changed in nova: | |
| status: | In Progress → Fix Committed |
| Changed in nova: | |
| milestone: | none → folsom-1 |
| Changed in nova: | |
| status: | Fix Committed → Fix Released |
| Changed in nova: | |
| milestone: | folsom-1 → 2012.2 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/