commit 14e2ed3ace769c4deaca3c48a2fa59863f637a5f
Author: Chris Behrens <email address hidden>
Date: Thu Oct 25 22:09:55 2012 -0700
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..)
Reviewed: https:/ /review. openstack. org/14872 github. com/openstack/ nova/commit/ 14e2ed3ace769c4 deaca3c48a2fa59 863f637a5f
Committed: http://
Submitter: Jenkins
Branch: master
commit 14e2ed3ace769c4 deaca3c48a2fa59 863f637a5f
Author: Chris Behrens <email address hidden>
Date: Thu Oct 25 22:09:55 2012 -0700
Fix use of elevated context for resize methods
elevated contexts were being passed over RPC to confirm_resize, revert_ resize methods. If those methods need
revert_resize, and finish_
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: I907889502f19fb a8059253e52dca0 84a123016e2