deletes fail when instance in RESIZED
Bug #1056601 reported by
Chris Behrens
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Chris Behrens | ||
Folsom |
Fix Released
|
High
|
Chuck Short | ||
nova (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Quantal |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
db.migration_
compute/api.py _delete() will call this method if instance is in RESIZED state with a non-elevated context.
I don't think we should be calling a DB API call like this that requires elevated context, however.
revert_resize and confirm_resize elevate the context when calling this method.
I think we should make this method not require admin context, verify matching project_id if non-admin... but the other calls of this need to be audited.
Changed in nova: | |
assignee: | nobody → Chris Behrens (cbehrens) |
status: | New → In Progress |
Changed in nova: | |
importance: | Undecided → High |
tags: | added: folsom-backport-potential |
tags: | removed: folsom-backport-potential |
Changed in nova: | |
milestone: | none → grizzly-1 |
status: | Fix Committed → Fix Released |
Changed in nova (Ubuntu): | |
status: | New → Fix Released |
Changed in nova (Ubuntu Quantal): | |
status: | New → Confirmed |
Changed in nova: | |
milestone: | grizzly-1 → 2013.1 |
To post a comment you must log in.
The use of elevated context in nova/compute/ manager. py confuses me a bit. I think every method in there elevates the context before continuing. I guess I don't fully understand the use of it if every method requires an elevated context.