Fix a corner case in associating QoS Specs with Volumt types that was
not handled well: Raise HTTPBadRequest() to client if associate volume
type, which is already associated one qos specs other than specified
qos specs. Previously such operation will proceed without error which
results overwriting original association.
Also refactor DB API volume_type_qos_specs_get() to return qos specs
in consistent dict format as other qos specs related APIs.
Reviewed: https:/ /review. openstack. org/45635 github. com/openstack/ cinder/ commit/ 5aa6ca2e80631a3 2e429bcacbd031d daa6e5bfb1
Committed: http://
Submitter: Jenkins
Branch: master
commit 5aa6ca2e80631a3 2e429bcacbd031d daa6e5bfb1
Author: Zhiteng Huang <email address hidden>
Date: Mon Sep 9 14:53:37 2013 +0800
Fix Qos Specs association corner case
Fix a corner case in associating QoS Specs with Volumt types that was
not handled well: Raise HTTPBadRequest() to client if associate volume
type, which is already associated one qos specs other than specified
qos specs. Previously such operation will proceed without error which
results overwriting original association.
Also refactor DB API volume_ type_qos_ specs_get( ) to return qos specs
in consistent dict format as other qos specs related APIs.
Fix bug: # 1222692
Change-Id: I9db66d1e3a7469 620ba542f538742 2685a2d828f