fix the an Unexpected API Error issue in flavor API
The flavors.add_flavor_access and flavors.remove_flavor_access
require admin privilege in DB level but the policy doesn't
require it and the exception isn't catched in the api. So the
bug arise. The privilege check in DB level is not necessary,
but it need more tests and can be remove in other patch or
blue-print.
This use extension_authorizer instead of soft_extension_authorizer
in the action of flavor_access, in order to raise exception.
Reviewed: https:/ /review. openstack. org/43988 github. com/openstack/ nova/commit/ d6214f122feb99b e74b6654bf86d16 77926fa628
Committed: http://
Submitter: Jenkins
Branch: master
commit d6214f122feb99b e74b6654bf86d16 77926fa628
Author: ivan-zhu <email address hidden>
Date: Wed Aug 28 11:40:35 2013 +0800
fix the an Unexpected API Error issue in flavor API
The flavors. add_flavor_ access and flavors. remove_ flavor_ access
require admin privilege in DB level but the policy doesn't
require it and the exception isn't catched in the api. So the
bug arise. The privilege check in DB level is not necessary,
but it need more tests and can be remove in other patch or
blue-print.
This use extension_ authorizer instead of soft_extension_ authorizer
in the action of flavor_access, in order to raise exception.
Closes-Bug: #1217679
DocImpact
Change-Id: I0b1231f47fffaf 99f330de02956bf e8d7cd4b920