commit 2e7f71738d2f695e8079ef0cd3b6c248ee67187e
Author: John Griffith <email address hidden>
Date: Thu Feb 28 19:01:39 2013 +0000
Elevate context for delete volume with no host.
So in the case of a volume that is placed in error state
on create and never actually deployed, the cinder.volume.api delete
call does a short cut call to db.destroy_volume which is fine because
all we have is a DB entry (scheduler never deployed the volume).
Unfortunately, this requires admin context, so just add an elevate
context to the db.destroy_volume call.
Fixes bug: 1084273
Change-Id: I0ef8bf4356047c385bef703b8dce7d5edf537bf6
(cherry picked from commit a2830e5417539980249e3ab12d8bf9538d8956c4)
Reviewed: https:/ /review. openstack. org/25571 github. com/openstack/ cinder/ commit/ 2e7f71738d2f695 e8079ef0cd3b6c2 48ee67187e
Committed: http://
Submitter: Jenkins
Branch: stable/folsom
commit 2e7f71738d2f695 e8079ef0cd3b6c2 48ee67187e
Author: John Griffith <email address hidden>
Date: Thu Feb 28 19:01:39 2013 +0000
Elevate context for delete volume with no host.
So in the case of a volume that is placed in error state
on create and never actually deployed, the cinder.volume.api delete
call does a short cut call to db.destroy_volume which is fine because
all we have is a DB entry (scheduler never deployed the volume).
Unfortunately, this requires admin context, so just add an elevate
context to the db.destroy_volume call.
Fixes bug: 1084273
Change-Id: I0ef8bf4356047c 385bef703b8dce7 d5edf537bf6 0249e3ab12d8bf9 538d8956c4)
(cherry picked from commit a2830e541753998