Bug 973149 - for snapshot based volumes, size should be enforced to be at least on par with the snapshot size
Summary: for snapshot based volumes, size should be enforced to be at least on par wit...
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-cinder   
(Show other bugs)
Version: 4.0
Hardware: Unspecified Unspecified
Target Milestone: Upstream M1
: 4.0
Assignee: Eric Harney
QA Contact: Yogev Rabl
Keywords: TestOnly
Depends On:
TreeView+ depends on / blocked
Reported: 2013-06-11 11:28 UTC by Giulio Fidente
Modified: 2016-04-27 00:35 UTC (History)
7 users (show)

Fixed In Version: openstack-cinder-2013.2-0.4.b2.el6ost
Doc Type: Bug Fix
Doc Text:
Previously, the Block Storage service incorrectly allowed users to attempt cloning a snapshot into a smaller volume. The attempt only failed when the volume filled up as expected during the volume creation process. With this fix, the Block Storage service will now check the volume size argument whenever users attempt to clone a snapshot. As a result, the Block Storage service will automatically fail any attempts to clone a snapshot into a smaller volume before even initiating the clone.
Story Points: ---
Clone Of:
Last Closed: 2013-12-20 00:05:27 UTC
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2013:1859 normal SHIPPED_LIVE Red Hat Enterprise Linux OpenStack Platform Enhancement Advisory 2013-12-21 00:01:48 UTC
OpenStack gerrit 25783 None None None Never
Launchpad 1161841 None None None Never
Launchpad 1189779 None None None Never

Description Giulio Fidente 2013-06-11 11:28:27 UTC
Description of problem:
when creating a snapshot based volume, it is currently permitted to pass as size argument a value smaller than the actual snapshot size

the volume creation terminates with an error as soon as the backing volume is filled

the API could get smarter and enforce the user to use as size a value greater or identical to the snapshot size

Version-Release number of selected component (if applicable):

Steps to Reproduce:
1. create a 2g volume (vol1)
2. create a snap of vol1 (snap1)
3. create a 1g volume from snap1 (vol2)

Actual results:
creation starts and reports failure when the backing LV is full

Expected results:
API returns error and doesn't initiate the operation

Comment 1 Eric Harney 2013-06-11 12:23:04 UTC
It's not clear to me that this is severe enough to be worth backporting.

Comment 5 Giulio Fidente 2013-10-10 15:06:43 UTC
verified using openstack-cinder-2013.2-0.9.b3.el6ost

Comment 8 errata-xmlrpc 2013-12-20 00:05:27 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.