DRDB driver does not honor clone volume size

Bug #1554756 reported by Sean McGinnis
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Cinder
Fix Released
Medium
Danny Al-Gaaf

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.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (master)

Fix proposed to branch: master
Review: https://review.openstack.org/291150

Changed in cinder:
assignee: nobody → Danny Al-Gaaf (danny-al-gaaf)
status: New → In Progress
Changed in cinder:
milestone: none → mitaka-rc1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to cinder (master)

Reviewed: https://review.openstack.org/291150
Committed: https://git.openstack.org/cgit/openstack/cinder/commit/?id=0532c1583ba761a1a67b9608b46408827edec299
Submitter: Jenkins
Branch: master

commit 0532c1583ba761a1a67b9608b46408827edec299
Author: Danny Al-Gaaf <email address hidden>
Date: Thu Mar 10 13:45:09 2016 +0100

    DRBD driver: resize volume if cloned image is larger

    Extend volume if during create_cloned_volume() the new
    volume is larger than the image it was cloned from.

    Closes-Bug: #1554756

    Change-Id: Id43e18c32c241a30cb35effe1fab8effe4517ba9
    Signed-off-by: Danny Al-Gaaf <email address hidden>

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.