Cinder

Volume size is not updated when cloning a volume with SolidFire

Bug #1219105 reported by Mathieu Gagné
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Fix Released
High
Mathieu Gagné
Cinder 2013.2 "havana"
Grizzly
Fix Released
High
Mathieu Gagné
Cinder 2013.1.4

Bug Description

When cloning a volume, a new size can be specified.

When using the SolidFire driver, the new size is not properly transmitted to SolidFire when sending the clone request.

The newly cloned volume has the correct size according to Cinder but the actual volume on SolidFire still has the old size.

John Griffith (john-griffith)
Changed in cinder:
status: New → Triaged
importance: Undecided → High
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/44574

Changed in cinder:
assignee: nobody → Mathieu Gagné (mgagne)
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to cinder (master)

Reviewed: https://review.openstack.org/44574
Committed: http://github.com/openstack/cinder/commit/0a87ff988cd21586daeb6ed886e44aedaa49c320
Submitter: Jenkins
Branch: master

commit 0a87ff988cd21586daeb6ed886e44aedaa49c320
Author: Mathieu Gagné <email address hidden>
Date: Fri Aug 30 21:59:59 2013 -0400

    Clone volume with right size with SolidFire

    It is possible to clone a volume with a size greater than
    the source volume. When using the SolidFire driver, the volume size
    was not passed in the call made to the SolidFire API when
    cloning a volume.

    It resulted in a cloned volume having the same size as the source
    volume but the correct size in the Cinder database.

    This changes makes sure the cloned volume has the correct size
    by explicitly passing the requested size when calling
    the SolidFire API and cloning the volume.

    Fixes: bug #1219105
    Change-Id: I5628c7fa922780d6b0601e2daa79310a61085edc

Changed in cinder:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (stable/grizzly)

Fix proposed to branch: stable/grizzly
Review: https://review.openstack.org/45143

Thierry Carrez (ttx)
Changed in cinder:
milestone: none → havana-3
status: Fix Committed → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to cinder (stable/grizzly)

Reviewed: https://review.openstack.org/45143
Committed: http://github.com/openstack/cinder/commit/19e92af7eff54fd75e2a91b772812da46c60b3cc
Submitter: Jenkins
Branch: stable/grizzly

commit 19e92af7eff54fd75e2a91b772812da46c60b3cc
Author: Mathieu Gagné <email address hidden>
Date: Fri Aug 30 21:59:59 2013 -0400

    Clone volume with right size with SolidFire

    It is possible to clone a volume with a size greater than
    the source volume. When using the SolidFire driver, the volume size
    was not passed in the call made to the SolidFire API when
    cloning a volume.

    It resulted in a cloned volume having the same size as the source
    volume but the correct size in the Cinder database.

    This changes makes sure the cloned volume has the correct size
    by explicitly passing the requested size when calling
    the SolidFire API and cloning the volume.

    Fixes: bug #1219105
    Change-Id: I5628c7fa922780d6b0601e2daa79310a61085edc
    (cherry picked from commit 0a87ff988cd21586daeb6ed886e44aedaa49c320)

tags: added: in-stable-grizzly
Thierry Carrez (ttx)
Changed in cinder:
milestone: havana-3 → 2013.2
Alan Pevec (apevec)
tags: removed: in-stable-grizzly
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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