ScaleIO driver does not honor clone volume size

Bug #1554777 reported by Sean McGinnis
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Cinder
Fix Released
Medium
Matan Sabag

Bug Description

It's possible to create a volume from a source volume with a different size. The create_cloned_volume call into the driver could have a larger volume['size'] than the source volume. So the driver will need to create the clone, then check if it needs to extend the volume to a new size.

Xing Yang (xing-yang)
Changed in cinder:
assignee: nobody → Matan Sabag (matan-sabag)
status: New → Triaged
Changed in cinder:
status: Triaged → In Progress
Changed in cinder:
milestone: none → newton-1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to cinder (master)

Reviewed: https://review.openstack.org/292100
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=74d67bc4f829100a2a3f1d6a5eda5c1ab5795d94
Submitter: Jenkins
Branch: master

commit 74d67bc4f829100a2a3f1d6a5eda5c1ab5795d94
Author: Matan Sabag <email address hidden>
Date: Sun Mar 13 04:19:49 2016 -0700

    Fix ScaleIO driver does not honor clone size

    Fixed a bug that when creating a volume from source the driver didn't honor the new volume size.
    Added unit test.

    Change-Id: I3a39953002432ac70a4ee2eccedd6737d9c3b019
    Closes-Bug: #1554777

Changed in cinder:
status: In Progress → Fix Released
Revision history for this message
Thierry Carrez (ttx) wrote : Fix included in openstack/cinder 8.0.0.0rc1

This issue was fixed in the openstack/cinder 8.0.0.0rc1 release candidate.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.