Resource reservation isn't rolled back properly for certain failures during Volume Create
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Cinder |
Fix Released
|
High
|
Rongze Zhu |
Bug Description
This bug is the same as https:/
The resources are reserved at the start of the volume creation, but are never rolled back/removed if certain exceptions occur, for example if you pass an image_id which its size is larger than the size of the volume , the reservation counter will increase and not be removed.
You can recreate this pretty simply by performing the following (assuming that the size of image is larger than 1):
zhu@ubuntu:
ERROR: Invalid input received: Size of specified image is larger than volume size. (HTTP 400) (Request-ID: req-6f6d5ca3-
...................
zhu@ubuntu:
ERROR: Invalid input received: Size of specified image is larger than volume size. (HTTP 400) (Request-ID: req-4f4ee5f0-
zhu@ubuntu:
ERROR: VolumeLimitExce
Changed in cinder: | |
assignee: | nobody → Rongze Zhu (zrzhit) |
Changed in cinder: | |
importance: | Undecided → High |
tags: | added: folsom-backport-potential |
Changed in cinder: | |
milestone: | none → grizzly-1 |
status: | Fix Committed → Fix Released |
Changed in cinder: | |
milestone: | grizzly-1 → 2013.1 |
Fix proposed to branch: master /review. openstack. org/14670
Review: https:/