summaryrefslogtreecommitdiffstats
path: root/nova/openstack
diff options
context:
space:
mode:
authorChris Behrens <cbehrens@codestud.com>2012-10-25 22:09:55 -0700
committerChris Behrens <cbehrens@codestud.com>2012-10-27 00:35:53 -0700
commit14e2ed3ace769c4deaca3c48a2fa59863f637a5f (patch)
tree259b7d48c4664d65f5e0ffb53d84daab3a0399a0 /nova/openstack
parent27a5753dd3766b5535e0248d48c9bb555379dd12 (diff)
downloadnova-14e2ed3ace769c4deaca3c48a2fa59863f637a5f.tar.gz
nova-14e2ed3ace769c4deaca3c48a2fa59863f637a5f.tar.xz
nova-14e2ed3ace769c4deaca3c48a2fa59863f637a5f.zip
Fix use of elevated context for resize methods
elevated contexts were being passed over RPC to confirm_resize, revert_resize, and finish_revert_resize methods. If those methods need to elevate context, they should do so themselves. There was 1 case (when deleting an instance in RESIZED) when we'd send a non-elevated context to confirm_resize(). This would fail because the migration_get() call there requires admin context and confirm_resize() on the manager side did not elevate the context itself. This fixes bug 1071600 and removes sending elevated contexts for these methods over RPC. (Ultimately we need some work to make the migration* DB API calls verify project_id vs requiring admin context..) Change-Id: I907889502f19fba8059253e52dca084a123016e2
Diffstat (limited to 'nova/openstack')
0 files changed, 0 insertions, 0 deletions